LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 05-24-2010, 09:50 PM   #1
TwinReverb
Member
 
Registered: Sep 2008
Location: Misawa AB, Japan
Distribution: Slackware
Posts: 191
Blog Entries: 2

Rep: Reputation: 40
Xfce LUKS handling randomly fails


Anyone else experiencing the random LUKS fails? Anyone know of a solution?

http://bugzilla.xfce.org/show_bug.cgi?id=6457

I filed a bug. Basically I have a USB hard drive with two LUKS partitions on it (sdb2, sdb3). When plugged in, it asks for the password in Xfce (like it did in Slackware 13.0), but instead of the previous "asks twice for password" bug, now it asks once, but nothing pops up on the desktop. It's rare to see either of them put an icon on the desktop (usually nothing results).

I see /dev/mapper/luks_crypto_{UUID} get populated, so they are successfully being unlocked (LUKS), but no icon appears, and no mount point for the volume label (i.e. /media/BACKUP /media/ASUS) is populated.

Does anyone know how I could produce a more useful bug report? I'm wondering if "strace startxfce" would produce anything useful or if I should alias Thunar to "strace -o /tmp/thunar-`date`.txt" would be in order.
 
Old 05-25-2010, 12:22 AM   #2
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
More discussion here: http://www.linuxquestions.org/questi...urrent-809730/

Sadly, I don't have time to investigate more at this point, but maybe mention the bug report in that other thread and you guys see what you can dig up. I've got a new baby set to arrive any day now, so I'm a bit busy :-)
 
Old 05-25-2010, 12:54 AM   #3
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,373

Rep: Reputation: 164Reputation: 164
Congrats on the new arrival!
 
Old 05-25-2010, 02:57 AM   #4
Ilgar
Member
 
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware 14.1, Slackware64 14.1
Posts: 917

Rep: Reputation: 87
First of all, congratulations Robby!

The bug on the other thread was reported to occur after the cryptsetup upgrade. Did anyone try downgrading to the version in 13.0? Or do we absolutely need the latest version for 13.1?
 
Old 05-25-2010, 04:05 AM   #5
Rupa
Member
 
Registered: Apr 2008
Location: Berlin, Germany
Distribution: Slackware, Debian, NetBSD
Posts: 80

Rep: Reputation: 25
Yes, downgrading to the cryptsetup version from 13.0 does solve this. But I would consider that rather an ugly workaround than a solution...
 
Old 05-25-2010, 06:54 AM   #6
GazL
Senior Member
 
Registered: May 2008
Posts: 3,328

Rep: Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884
Yes, good luck Robby. Hope Mrs. Workman has a smooth time of it.


The problem is fixed upstream in the just released cryptsetup 1.1.1.
 
Old 05-25-2010, 09:48 PM   #7
TwinReverb
Member
 
Registered: Sep 2008
Location: Misawa AB, Japan
Distribution: Slackware
Posts: 191
Blog Entries: 2

Original Poster
Rep: Reputation: 40
Today I tried bypassing Xfce and instead mounting the device manually. I found some interesting info:

Code:
bash-4.1# cryptsetup luksOpen /dev/sdb2 BACKUP
Enter passphrase for /dev/sdb2: 
device-mapper: remove ioctl failed: Device or resource busy
Key slot 0 unlocked.
bash-4.1# ls /media
README       cdrecorder1  cdrom1  dvd1     floppy1  hd1      memory1  zip1
cdrecorder   cdrom        dvd     floppy   hd       memory   zip
cdrecorder0  cdrom0       dvd0    floppy0  hd0      memory0  zip0
Therefore the problem may not be Xfce in the first place.
 
Old 05-25-2010, 10:00 PM   #8
TwinReverb
Member
 
Registered: Sep 2008
Location: Misawa AB, Japan
Distribution: Slackware
Posts: 191
Blog Entries: 2

Original Poster
Rep: Reputation: 40
Quote:
Originally Posted by GazL View Post
Yes, good luck Robby. Hope Mrs. Workman has a smooth time of it.


The problem is fixed upstream in the just released cryptsetup 1.1.1.
I downloaded the Slackware 13.1 official slackbuild and the cryptsetup 1.1.1 tarball and it built without errors. However, in Xfce the problem is still not fixed. I get the same error situation: I give the password but nothing happens (yet /dev/mapper/luks_crypto_$UUID gets populated for both sdb2 and sdb3).

However, when I manually open the device in a terminal as root, it appears on the desktop in Xfce.

Last edited by TwinReverb; 05-25-2010 at 10:05 PM.
 
Old 05-26-2010, 01:36 AM   #9
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
Okay, comment out this line completely in /lib/udev/rules.d/10-dm.rules

Code:
ACTION=="add", ENV{STARTUP}!="1", NAME="", GOTO="dm_end"
Then do
Code:
/etc/rc.d/rc.udev reload
and see if it works for you. It didn't here, but maybe it will for you.
I just upgraded the lvm2 package to the latest 2.02.66, and my MMC card with LUKS device works fine. However, my usb thumbdrive still does not. My next trial will be commenting out these two lines:
Code:
ENV{DM_UUID}=="CRYPT-TEMP-?*", GOTO="dm_disable"
ENV{DM_UUID}!="?*", ENV{DM_NAME}=="temporary-cryptsetup-?*", GOTO="dm_disable"
but that's going to have to wait until tomorrow.
 
Old 05-26-2010, 04:44 AM   #10
GazL
Senior Member
 
Registered: May 2008
Posts: 3,328

Rep: Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884
@TwinReverb, Yes, sorry about that I was a little too quick to call 'fixed'. It was working on my box but then it broke again. Whatever the problem is it's intermittent, but frequent. At least it fixes the symlink issue though, so it's a step in the right direction.


@Robby, I tried removing that STARTUP!='1' line last night. Had no effect here either.


Found this 'defect' report for the "resource busy" thingy. The last entry is interesting:
Quote:
I've upgraded to Linux 2.6.34-rc5 and sys-fs/udev-151-r2. I don't know what made the
difference.
We're already running higher than udev 151 and the guy who posted that doesn't say what version of lvm2/mapper he was running so I'm not sure how reliable that is.

I might try going to 2.6.34 to see if it's a kernel issue or not.
 
Old 05-26-2010, 05:55 AM   #11
GazL
Senior Member
 
Registered: May 2008
Posts: 3,328

Rep: Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884
Just tried 2.6.34 and it's the same. (wasn't really expecting it to be otherwise to be honest)
 
Old 05-26-2010, 11:31 AM   #12
TwinReverb
Member
 
Registered: Sep 2008
Location: Misawa AB, Japan
Distribution: Slackware
Posts: 191
Blog Entries: 2

Original Poster
Rep: Reputation: 40
Quote:
Originally Posted by rworkman View Post
Okay, comment out this line completely in /lib/udev/rules.d/10-dm.rules

Code:
ACTION=="add", ENV{STARTUP}!="1", NAME="", GOTO="dm_end"
Then do
Code:
/etc/rc.d/rc.udev reload
and see if it works for you.
Worked like a charm on my Core2 Duo laptop (Sony Vaio VGN-C140G).

On my netbook it had an adverse affect on all devices. (LUKS SD card and USB hard drive with 2nd and 3rd partition as separate LUKS partitions both give me the error "special device /dev/mapper/luks_crypto_$UUID does not exist.)

Oh well, nothing is perfect I guess.

Last edited by TwinReverb; 05-26-2010 at 11:37 AM.
 
Old 05-26-2010, 02:22 PM   #13
Rupa
Member
 
Registered: Apr 2008
Location: Berlin, Germany
Distribution: Slackware, Debian, NetBSD
Posts: 80

Rep: Reputation: 25
Quote:
Originally Posted by rworkman View Post
Okay, comment out this line completely in /lib/udev/rules.d/10-dm.rules

Code:
ACTION=="add", ENV{STARTUP}!="1", NAME="", GOTO="dm_end"
If I do this (after upgrading to cryptsetup-1.1.0 again), my internal crypto partitions like /home are not mounted anymore. cryptsetup seems to work but after unlocking the device there is no link or file in /dev/mapper at all (besides 'control' of course). So I'm back at cryptsetup-1.0.7 once more...
 
Old 05-26-2010, 02:24 PM   #14
Rupa
Member
 
Registered: Apr 2008
Location: Berlin, Germany
Distribution: Slackware, Debian, NetBSD
Posts: 80

Rep: Reputation: 25
Quote:
Originally Posted by TwinReverb View Post
LUKS SD card and USB hard drive with 2nd and 3rd partition as separate LUKS partitions both give me the error "special device /dev/mapper/luks_crypto_$UUID does not exist.
Yes, same here. And the message is telling the truth as there is no file in /dev/mapper at all.
 
Old 05-28-2010, 04:31 PM   #15
TwinReverb
Member
 
Registered: Sep 2008
Location: Misawa AB, Japan
Distribution: Slackware
Posts: 191
Blog Entries: 2

Original Poster
Rep: Reputation: 40
Downgrading back to Slackware 13.0. Problem solved.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Other sub-menu disappears randomly in xfce samac Slackware 5 10-13-2011 12:12 PM
[SOLVED] Kernel update on LUKS and LVM encrypted Slackware, mount fails KMBS Slackware 15 02-08-2010 01:23 PM
/home randomly fails jmoschetti45 Linux - Server 3 11-20-2009 02:40 PM
Ping randomly fails AIM Systems Linux - Networking 1 09-28-2009 11:44 AM
Keyboard randomly fails when X starts reg.doug Linux - Hardware 3 08-13-2009 12:07 PM


All times are GMT -5. The time now is 08:12 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration