[Desktop-packages] [Bug 2047737] Re: Nautilus crashes when opening folders that contain files with js or json extensions
This isn't specific to ubuntu btw. it happens on Fedora 38 too. so far i've found that any `.json` or `.js` file will cause any instance of the gnome filebrowser (nautilus, a file picker modal, etc) to crash itself and any app that uses it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2047737 Title: Nautilus crashes when opening folders that contain files with js or json extensions Status in nautilus package in Ubuntu: Incomplete Bug description: After attempting to open a folder that contains js or json files the app crashes. when testing from terminal I get a segmentation fault and no other error info. even enabling G_MESSAGES_DEBUG=all did not provide additional info. removing nautilus extensions, resetting xdg-mime for js/json, and disabling nautilus features (search, file count, etc ...) did not fix the problem either. additional info $ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 $ apt-cache policy nautilus nautilus: Installed: 1:42.6-0ubuntu1 Candidate: 1:42.6-0ubuntu1 Version table: *** 1:42.6-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:42.2-0ubuntu2.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 1:42.0-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Dec 30 14:50:09 2023 InstallationDate: Installed on 2023-02-14 (319 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu3.1 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2047737/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 574818] Re: SSL + IRC Never Uses SSL
still a problem on 12.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/574818 Title: SSL + IRC Never Uses SSL Status in Chat app, and Telepathy user interface: Expired Status in “empathy” package in Ubuntu: Invalid Bug description: Binary package hint: empathy On Lucid, when trying to use SSL + IRC to connect to Freenode, no combination of settings will ever actually use SSL. According to Freenode's docs, they support SSL on 7000, and 7070. I've tried setting up a new IRC server with chat.freenode.net:7000 and 7070, every time it connects over port 6667. I've verified with tcpdump that the connections are plain text. To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/574818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 507089] Re: thunderbird shredder always segfaults on startup with LDAP auth in nsswitch
still a problem in 12.04 amd64 desktop and the default thunderbird provided. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/507089 Title: thunderbird shredder always segfaults on startup with LDAP auth in nsswitch Status in SeaMonkey: all-in-one Internet application suite: New Status in Mozilla Thunderbird Mail and News: In Progress Status in “thunderbird” package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird If nsswitch.conf is set with: passwd: compat ldap group: compat ldap shadow: compat ldap My ldap config does work as I'm using it for login authentication. thunderbird-3.0 always segfaults: 0 % thunderbird-3.0 Segmentation fault 0 % thunderbird-3.0 --g-fatal-warnings Segmentation fault 139 % thunderbird-3.0 -options Segmentation fault 139 % thunderbird-3.0 -safe-mode Segmentation fault 139 % thunderbird-3.0 -ProfileManager Segmentation fault 139 % ...even with no .thunderbird-30 dir: % thunderbird-3.0 -ProfileManager *INFO* No /users/bedge/.thunderbird-3.0 detected. Create it from /users/bedge/.mozilla-thunderbird Segmentation fault 0 9:12:52 bedge@ice ~ 139 % Changing nsswitch back to NIS works: passwd: compat nis group: compat nis shadow: compat nis 1 % dpkg -l thunderbird\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Description +++-===-===-== ii thunderbird 2.0.0.23+build1+nobinonly-0 mail/news client with RSS and integrated spam filter support ii thunderbird-3.0 3.0~rc3~micahg+nobinonly-0u mail/news client with RSS and integrated spam filter support ii thunderbird-3.0-gnome-suppo 3.0~rc3~micahg+nobinonly-0u Support for Gnome in Mozilla Thunderbird 3.0 ii thunderbird-dispmua 1.6.4.3-1ubuntu1Display Mail User Agent extension (transitional package) ii thunderbird-gnome-support 2.0.0.23+build1+nobinonly-0 Support for Gnome in Mozilla Thunderbird ii thunderbird-locale-en-gb1:2.0.0.14+1-0ubuntu2 Thunderbird English language/region package ii thunderbird-nostalgy0.2.16+svn151-1ubuntu1 keyboard shortcut extension for thunderbird ii thunderbird-quickfile 0.17.0.0011-0ubuntu4faster mail filing for the Thunderbird mail client ii thunderbird-traybiff1.2.3-4.2ubuntu2traybiff - new mail alert for thunderbird WORKAROUND: Installing the nscd package solves this issue in most cases. To manage notifications about this bug go to: https://bugs.launchpad.net/seamonkey/+bug/507089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 507089] Re: thunderbird shredder always segfaults on startup with LDAP auth in nsswitch
although it's still a problem in ubuntu 12.04 64bit desktop and the default thunderbird (not sure if any thunderbird), applying the workaround in #7 (https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/507089/comments/7) works. we use 10 ubuntu 12.04 64bit workstations here at work, that require ldap login from a ubuntu 10.04 server managed by zentyal. I apply the zentyla-desktop.deb to each of the workstations. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/507089 Title: thunderbird shredder always segfaults on startup with LDAP auth in nsswitch Status in SeaMonkey: all-in-one Internet application suite: New Status in Mozilla Thunderbird Mail and News: In Progress Status in “thunderbird” package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird If nsswitch.conf is set with: passwd: compat ldap group: compat ldap shadow: compat ldap My ldap config does work as I'm using it for login authentication. thunderbird-3.0 always segfaults: 0 % thunderbird-3.0 Segmentation fault 0 % thunderbird-3.0 --g-fatal-warnings Segmentation fault 139 % thunderbird-3.0 -options Segmentation fault 139 % thunderbird-3.0 -safe-mode Segmentation fault 139 % thunderbird-3.0 -ProfileManager Segmentation fault 139 % ...even with no .thunderbird-30 dir: % thunderbird-3.0 -ProfileManager *INFO* No /users/bedge/.thunderbird-3.0 detected. Create it from /users/bedge/.mozilla-thunderbird Segmentation fault 0 9:12:52 bedge@ice ~ 139 % Changing nsswitch back to NIS works: passwd: compat nis group: compat nis shadow: compat nis 1 % dpkg -l thunderbird\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Description +++-===-===-== ii thunderbird 2.0.0.23+build1+nobinonly-0 mail/news client with RSS and integrated spam filter support ii thunderbird-3.0 3.0~rc3~micahg+nobinonly-0u mail/news client with RSS and integrated spam filter support ii thunderbird-3.0-gnome-suppo 3.0~rc3~micahg+nobinonly-0u Support for Gnome in Mozilla Thunderbird 3.0 ii thunderbird-dispmua 1.6.4.3-1ubuntu1Display Mail User Agent extension (transitional package) ii thunderbird-gnome-support 2.0.0.23+build1+nobinonly-0 Support for Gnome in Mozilla Thunderbird ii thunderbird-locale-en-gb1:2.0.0.14+1-0ubuntu2 Thunderbird English language/region package ii thunderbird-nostalgy0.2.16+svn151-1ubuntu1 keyboard shortcut extension for thunderbird ii thunderbird-quickfile 0.17.0.0011-0ubuntu4faster mail filing for the Thunderbird mail client ii thunderbird-traybiff1.2.3-4.2ubuntu2traybiff - new mail alert for thunderbird WORKAROUND: Installing the nscd package solves this issue in most cases. To manage notifications about this bug go to: https://bugs.launchpad.net/seamonkey/+bug/507089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 484429] Re: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists
just adding that #33 is on 11.10 64bit with gnome-shell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/484429 Title: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists Status in abstraction for enumerating and managing block devices: Fix Released Status in “cryptsetup” package in Ubuntu: Confirmed Status in “gnome-disk-utility” package in Ubuntu: Invalid Status in “udisks” package in Ubuntu: Fix Released Status in “cryptsetup” source package in Lucid: Confirmed Status in “gnome-disk-utility” source package in Lucid: Invalid Status in “udisks” source package in Lucid: Confirmed Status in “cryptsetup” source package in Maverick: Confirmed Status in “gnome-disk-utility” source package in Maverick: Invalid Status in “udisks” source package in Maverick: Fix Released Status in “cryptsetup” package in Debian: Fix Released Status in “udisks” package in Fedora: Unknown Bug description: Binary package hint: cryptsetup When creating an encrypted drive in Palimsest (Disk Utility), the application does not lock the disk when finished creating the encrypted partition. Failing to lock the drive manually without ejecting will give the appearance that the disk is no longer usable giving this error. Bringing the key to another computer works because the drive is not unlocked (luks mapper point is not already present) on that system. Steps to reproduce: 1) Go into palimsest (disk utility) and create an encrypted partition on an external disk. 2) Quit Palimsest 3) Pull the USB stick 4) Intert the USB stick Result: GNOME displays a dialog for the password. Once submitted, the following error comes up: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists This is due to the mapping being Opened when the disk is created, but never closed, which creates a conflict. Workaround: Do the following to resolve the conflict of the existing device i /dev/mapper. $ ls -al /dev/mapper (Identify the mount point for your drive, sudo blkid may help) $ sudo cryptsetup luksClose devkit-disks-luks-uuid-uuid-uid1000 What is expected: Palimsest (Disk Utility) is expected to cryptsetup luksClose the mapped device when finished creating the encrypted partition. ProblemType: Bug Architecture: i386 CheckboxSubmission: 19ba8f45e3d3d7bf348103cee5a0eeaa CheckboxSystem: 099634613a96bc3665b92c4a813055e8 Date: Tue Nov 17 15:37:09 2009 DistroRelease: Ubuntu 9.10 Package: cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: cryptsetup Uname: Linux 2.6.31-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/484429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 484429] Re: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists
I created an excrypted sdcard with palimpset. 1) Plug in a LUKS encrypted disk 2) At the password prompt unlock it (Disk will mount and be displayed on the desktop) 3) Suspend computer 4) Remove sdcard 5) On resume, no errors 6) Insert encrypted sdcard from step 4) 7) Prompted to enter password for device. 8) Error unlocking device: cryptsetup exited with exit code 239 error is shown. 9) sdcard is never mounted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/484429 Title: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists Status in abstraction for enumerating and managing block devices: Fix Released Status in “cryptsetup” package in Ubuntu: Confirmed Status in “gnome-disk-utility” package in Ubuntu: Invalid Status in “udisks” package in Ubuntu: Fix Released Status in “cryptsetup” source package in Lucid: Confirmed Status in “gnome-disk-utility” source package in Lucid: Invalid Status in “udisks” source package in Lucid: Confirmed Status in “cryptsetup” source package in Maverick: Confirmed Status in “gnome-disk-utility” source package in Maverick: Invalid Status in “udisks” source package in Maverick: Fix Released Status in “cryptsetup” package in Debian: Fix Released Status in “udisks” package in Fedora: Unknown Bug description: Binary package hint: cryptsetup When creating an encrypted drive in Palimsest (Disk Utility), the application does not lock the disk when finished creating the encrypted partition. Failing to lock the drive manually without ejecting will give the appearance that the disk is no longer usable giving this error. Bringing the key to another computer works because the drive is not unlocked (luks mapper point is not already present) on that system. Steps to reproduce: 1) Go into palimsest (disk utility) and create an encrypted partition on an external disk. 2) Quit Palimsest 3) Pull the USB stick 4) Intert the USB stick Result: GNOME displays a dialog for the password. Once submitted, the following error comes up: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists This is due to the mapping being Opened when the disk is created, but never closed, which creates a conflict. Workaround: Do the following to resolve the conflict of the existing device i /dev/mapper. $ ls -al /dev/mapper (Identify the mount point for your drive, sudo blkid may help) $ sudo cryptsetup luksClose devkit-disks-luks-uuid-uuid-uid1000 What is expected: Palimsest (Disk Utility) is expected to cryptsetup luksClose the mapped device when finished creating the encrypted partition. ProblemType: Bug Architecture: i386 CheckboxSubmission: 19ba8f45e3d3d7bf348103cee5a0eeaa CheckboxSystem: 099634613a96bc3665b92c4a813055e8 Date: Tue Nov 17 15:37:09 2009 DistroRelease: Ubuntu 9.10 Package: cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: cryptsetup Uname: Linux 2.6.31-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/484429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 484429] Re: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists
ubuntu 11.10 64bit, system76 serval laptop. dmesg output after plugging in sdcard, entering password, recieving error ** Attachment added: luks-error-dmesg.txt https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/484429/+attachment/2605403/+files/luks-error-dmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/484429 Title: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists Status in abstraction for enumerating and managing block devices: Fix Released Status in “cryptsetup” package in Ubuntu: Confirmed Status in “gnome-disk-utility” package in Ubuntu: Invalid Status in “udisks” package in Ubuntu: Fix Released Status in “cryptsetup” source package in Lucid: Confirmed Status in “gnome-disk-utility” source package in Lucid: Invalid Status in “udisks” source package in Lucid: Confirmed Status in “cryptsetup” source package in Maverick: Confirmed Status in “gnome-disk-utility” source package in Maverick: Invalid Status in “udisks” source package in Maverick: Fix Released Status in “cryptsetup” package in Debian: Fix Released Status in “udisks” package in Fedora: Unknown Bug description: Binary package hint: cryptsetup When creating an encrypted drive in Palimsest (Disk Utility), the application does not lock the disk when finished creating the encrypted partition. Failing to lock the drive manually without ejecting will give the appearance that the disk is no longer usable giving this error. Bringing the key to another computer works because the drive is not unlocked (luks mapper point is not already present) on that system. Steps to reproduce: 1) Go into palimsest (disk utility) and create an encrypted partition on an external disk. 2) Quit Palimsest 3) Pull the USB stick 4) Intert the USB stick Result: GNOME displays a dialog for the password. Once submitted, the following error comes up: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists This is due to the mapping being Opened when the disk is created, but never closed, which creates a conflict. Workaround: Do the following to resolve the conflict of the existing device i /dev/mapper. $ ls -al /dev/mapper (Identify the mount point for your drive, sudo blkid may help) $ sudo cryptsetup luksClose devkit-disks-luks-uuid-uuid-uid1000 What is expected: Palimsest (Disk Utility) is expected to cryptsetup luksClose the mapped device when finished creating the encrypted partition. ProblemType: Bug Architecture: i386 CheckboxSubmission: 19ba8f45e3d3d7bf348103cee5a0eeaa CheckboxSystem: 099634613a96bc3665b92c4a813055e8 Date: Tue Nov 17 15:37:09 2009 DistroRelease: Ubuntu 9.10 Package: cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: cryptsetup Uname: Linux 2.6.31-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/484429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 484429] Re: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists
ubuntu 11.10 64bit, system76 serval laptop. udisk dump output after plugging in sdcard, entering password, recieving error ** Attachment added: luks-error-udisk-dump.txt https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/484429/+attachment/2605404/+files/luks-error-udisk-dump.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/484429 Title: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists Status in abstraction for enumerating and managing block devices: Fix Released Status in “cryptsetup” package in Ubuntu: Confirmed Status in “gnome-disk-utility” package in Ubuntu: Invalid Status in “udisks” package in Ubuntu: Fix Released Status in “cryptsetup” source package in Lucid: Confirmed Status in “gnome-disk-utility” source package in Lucid: Invalid Status in “udisks” source package in Lucid: Confirmed Status in “cryptsetup” source package in Maverick: Confirmed Status in “gnome-disk-utility” source package in Maverick: Invalid Status in “udisks” source package in Maverick: Fix Released Status in “cryptsetup” package in Debian: Fix Released Status in “udisks” package in Fedora: Unknown Bug description: Binary package hint: cryptsetup When creating an encrypted drive in Palimsest (Disk Utility), the application does not lock the disk when finished creating the encrypted partition. Failing to lock the drive manually without ejecting will give the appearance that the disk is no longer usable giving this error. Bringing the key to another computer works because the drive is not unlocked (luks mapper point is not already present) on that system. Steps to reproduce: 1) Go into palimsest (disk utility) and create an encrypted partition on an external disk. 2) Quit Palimsest 3) Pull the USB stick 4) Intert the USB stick Result: GNOME displays a dialog for the password. Once submitted, the following error comes up: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists This is due to the mapping being Opened when the disk is created, but never closed, which creates a conflict. Workaround: Do the following to resolve the conflict of the existing device i /dev/mapper. $ ls -al /dev/mapper (Identify the mount point for your drive, sudo blkid may help) $ sudo cryptsetup luksClose devkit-disks-luks-uuid-uuid-uid1000 What is expected: Palimsest (Disk Utility) is expected to cryptsetup luksClose the mapped device when finished creating the encrypted partition. ProblemType: Bug Architecture: i386 CheckboxSubmission: 19ba8f45e3d3d7bf348103cee5a0eeaa CheckboxSystem: 099634613a96bc3665b92c4a813055e8 Date: Tue Nov 17 15:37:09 2009 DistroRelease: Ubuntu 9.10 Package: cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: cryptsetup Uname: Linux 2.6.31-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/484429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 484429] Re: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists
ubuntu 11.10 64bit, system76 serval laptop. udevadm output after plugging in sdcard, entering password, recieving error ** Attachment added: luks-error-udevadm-info-export-db.txt https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/484429/+attachment/2605405/+files/luks-error-udevadm-info-export-db.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/484429 Title: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists Status in abstraction for enumerating and managing block devices: Fix Released Status in “cryptsetup” package in Ubuntu: Confirmed Status in “gnome-disk-utility” package in Ubuntu: Invalid Status in “udisks” package in Ubuntu: Fix Released Status in “cryptsetup” source package in Lucid: Confirmed Status in “gnome-disk-utility” source package in Lucid: Invalid Status in “udisks” source package in Lucid: Confirmed Status in “cryptsetup” source package in Maverick: Confirmed Status in “gnome-disk-utility” source package in Maverick: Invalid Status in “udisks” source package in Maverick: Fix Released Status in “cryptsetup” package in Debian: Fix Released Status in “udisks” package in Fedora: Unknown Bug description: Binary package hint: cryptsetup When creating an encrypted drive in Palimsest (Disk Utility), the application does not lock the disk when finished creating the encrypted partition. Failing to lock the drive manually without ejecting will give the appearance that the disk is no longer usable giving this error. Bringing the key to another computer works because the drive is not unlocked (luks mapper point is not already present) on that system. Steps to reproduce: 1) Go into palimsest (disk utility) and create an encrypted partition on an external disk. 2) Quit Palimsest 3) Pull the USB stick 4) Intert the USB stick Result: GNOME displays a dialog for the password. Once submitted, the following error comes up: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists This is due to the mapping being Opened when the disk is created, but never closed, which creates a conflict. Workaround: Do the following to resolve the conflict of the existing device i /dev/mapper. $ ls -al /dev/mapper (Identify the mount point for your drive, sudo blkid may help) $ sudo cryptsetup luksClose devkit-disks-luks-uuid-uuid-uid1000 What is expected: Palimsest (Disk Utility) is expected to cryptsetup luksClose the mapped device when finished creating the encrypted partition. ProblemType: Bug Architecture: i386 CheckboxSubmission: 19ba8f45e3d3d7bf348103cee5a0eeaa CheckboxSystem: 099634613a96bc3665b92c4a813055e8 Date: Tue Nov 17 15:37:09 2009 DistroRelease: Ubuntu 9.10 Package: cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: cryptsetup Uname: Linux 2.6.31-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/484429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 484429] Re: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists
ubuntu 11.10 64bit, system76 serval laptop. dmesg output after pulling out sdcard ** Attachment added: luks-error-dmesg-post.txt https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/484429/+attachment/2605406/+files/luks-error-dmesg-post.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/484429 Title: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists Status in abstraction for enumerating and managing block devices: Fix Released Status in “cryptsetup” package in Ubuntu: Confirmed Status in “gnome-disk-utility” package in Ubuntu: Invalid Status in “udisks” package in Ubuntu: Fix Released Status in “cryptsetup” source package in Lucid: Confirmed Status in “gnome-disk-utility” source package in Lucid: Invalid Status in “udisks” source package in Lucid: Confirmed Status in “cryptsetup” source package in Maverick: Confirmed Status in “gnome-disk-utility” source package in Maverick: Invalid Status in “udisks” source package in Maverick: Fix Released Status in “cryptsetup” package in Debian: Fix Released Status in “udisks” package in Fedora: Unknown Bug description: Binary package hint: cryptsetup When creating an encrypted drive in Palimsest (Disk Utility), the application does not lock the disk when finished creating the encrypted partition. Failing to lock the drive manually without ejecting will give the appearance that the disk is no longer usable giving this error. Bringing the key to another computer works because the drive is not unlocked (luks mapper point is not already present) on that system. Steps to reproduce: 1) Go into palimsest (disk utility) and create an encrypted partition on an external disk. 2) Quit Palimsest 3) Pull the USB stick 4) Intert the USB stick Result: GNOME displays a dialog for the password. Once submitted, the following error comes up: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists This is due to the mapping being Opened when the disk is created, but never closed, which creates a conflict. Workaround: Do the following to resolve the conflict of the existing device i /dev/mapper. $ ls -al /dev/mapper (Identify the mount point for your drive, sudo blkid may help) $ sudo cryptsetup luksClose devkit-disks-luks-uuid-uuid-uid1000 What is expected: Palimsest (Disk Utility) is expected to cryptsetup luksClose the mapped device when finished creating the encrypted partition. ProblemType: Bug Architecture: i386 CheckboxSubmission: 19ba8f45e3d3d7bf348103cee5a0eeaa CheckboxSystem: 099634613a96bc3665b92c4a813055e8 Date: Tue Nov 17 15:37:09 2009 DistroRelease: Ubuntu 9.10 Package: cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: cryptsetup Uname: Linux 2.6.31-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/484429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 484429] Re: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists
ubuntu 11.10 64bit, system76 serval laptop. udevadm output after pulling out sdcard ** Attachment added: luks-error-udevadm-info-export-db-post.txt https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/484429/+attachment/2605407/+files/luks-error-udevadm-info-export-db-post.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/484429 Title: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists Status in abstraction for enumerating and managing block devices: Fix Released Status in “cryptsetup” package in Ubuntu: Confirmed Status in “gnome-disk-utility” package in Ubuntu: Invalid Status in “udisks” package in Ubuntu: Fix Released Status in “cryptsetup” source package in Lucid: Confirmed Status in “gnome-disk-utility” source package in Lucid: Invalid Status in “udisks” source package in Lucid: Confirmed Status in “cryptsetup” source package in Maverick: Confirmed Status in “gnome-disk-utility” source package in Maverick: Invalid Status in “udisks” source package in Maverick: Fix Released Status in “cryptsetup” package in Debian: Fix Released Status in “udisks” package in Fedora: Unknown Bug description: Binary package hint: cryptsetup When creating an encrypted drive in Palimsest (Disk Utility), the application does not lock the disk when finished creating the encrypted partition. Failing to lock the drive manually without ejecting will give the appearance that the disk is no longer usable giving this error. Bringing the key to another computer works because the drive is not unlocked (luks mapper point is not already present) on that system. Steps to reproduce: 1) Go into palimsest (disk utility) and create an encrypted partition on an external disk. 2) Quit Palimsest 3) Pull the USB stick 4) Intert the USB stick Result: GNOME displays a dialog for the password. Once submitted, the following error comes up: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists This is due to the mapping being Opened when the disk is created, but never closed, which creates a conflict. Workaround: Do the following to resolve the conflict of the existing device i /dev/mapper. $ ls -al /dev/mapper (Identify the mount point for your drive, sudo blkid may help) $ sudo cryptsetup luksClose devkit-disks-luks-uuid-uuid-uid1000 What is expected: Palimsest (Disk Utility) is expected to cryptsetup luksClose the mapped device when finished creating the encrypted partition. ProblemType: Bug Architecture: i386 CheckboxSubmission: 19ba8f45e3d3d7bf348103cee5a0eeaa CheckboxSystem: 099634613a96bc3665b92c4a813055e8 Date: Tue Nov 17 15:37:09 2009 DistroRelease: Ubuntu 9.10 Package: cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: cryptsetup Uname: Linux 2.6.31-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/484429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 484429] Re: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists
ubuntu 11.10 64bit, system76 serval laptop. udisk output after pulling out sdcard ** Attachment added: luks-error-udisk-dump-post.txt https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/484429/+attachment/2605408/+files/luks-error-udisk-dump-post.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/484429 Title: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists Status in abstraction for enumerating and managing block devices: Fix Released Status in “cryptsetup” package in Ubuntu: Confirmed Status in “gnome-disk-utility” package in Ubuntu: Invalid Status in “udisks” package in Ubuntu: Fix Released Status in “cryptsetup” source package in Lucid: Confirmed Status in “gnome-disk-utility” source package in Lucid: Invalid Status in “udisks” source package in Lucid: Confirmed Status in “cryptsetup” source package in Maverick: Confirmed Status in “gnome-disk-utility” source package in Maverick: Invalid Status in “udisks” source package in Maverick: Fix Released Status in “cryptsetup” package in Debian: Fix Released Status in “udisks” package in Fedora: Unknown Bug description: Binary package hint: cryptsetup When creating an encrypted drive in Palimsest (Disk Utility), the application does not lock the disk when finished creating the encrypted partition. Failing to lock the drive manually without ejecting will give the appearance that the disk is no longer usable giving this error. Bringing the key to another computer works because the drive is not unlocked (luks mapper point is not already present) on that system. Steps to reproduce: 1) Go into palimsest (disk utility) and create an encrypted partition on an external disk. 2) Quit Palimsest 3) Pull the USB stick 4) Intert the USB stick Result: GNOME displays a dialog for the password. Once submitted, the following error comes up: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists This is due to the mapping being Opened when the disk is created, but never closed, which creates a conflict. Workaround: Do the following to resolve the conflict of the existing device i /dev/mapper. $ ls -al /dev/mapper (Identify the mount point for your drive, sudo blkid may help) $ sudo cryptsetup luksClose devkit-disks-luks-uuid-uuid-uid1000 What is expected: Palimsest (Disk Utility) is expected to cryptsetup luksClose the mapped device when finished creating the encrypted partition. ProblemType: Bug Architecture: i386 CheckboxSubmission: 19ba8f45e3d3d7bf348103cee5a0eeaa CheckboxSystem: 099634613a96bc3665b92c4a813055e8 Date: Tue Nov 17 15:37:09 2009 DistroRelease: Ubuntu 9.10 Package: cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: cryptsetup Uname: Linux 2.6.31-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/484429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 873113] Re: package lightdm 1.0.1-0ubuntu6 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/873113 Title: package lightdm 1.0.1-0ubuntu6 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Status in “lightdm” package in Ubuntu: New Bug description: Already had lightdm installed on 11.04 prior to upgrade ProblemType: Package DistroRelease: Ubuntu 11.10 Package: lightdm 1.0.1-0ubuntu6 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic-pae 2.6.38.8 Uname: Linux 2.6.38-11-generic-pae i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Thu Oct 13 08:55:04 2011 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: lightdm Title: package lightdm 1.0.1-0ubuntu6 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to oneiric on 2011-10-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/873113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 873113] [NEW] package lightdm 1.0.1-0ubuntu6 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: Already had lightdm installed on 11.04 prior to upgrade ProblemType: Package DistroRelease: Ubuntu 11.10 Package: lightdm 1.0.1-0ubuntu6 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic-pae 2.6.38.8 Uname: Linux 2.6.38-11-generic-pae i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Thu Oct 13 08:55:04 2011 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: lightdm Title: package lightdm 1.0.1-0ubuntu6 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to oneiric on 2011-10-12 (0 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 oneiric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/873113 Title: package lightdm 1.0.1-0ubuntu6 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Status in “lightdm” package in Ubuntu: New Bug description: Already had lightdm installed on 11.04 prior to upgrade ProblemType: Package DistroRelease: Ubuntu 11.10 Package: lightdm 1.0.1-0ubuntu6 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic-pae 2.6.38.8 Uname: Linux 2.6.38-11-generic-pae i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Thu Oct 13 08:55:04 2011 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: lightdm Title: package lightdm 1.0.1-0ubuntu6 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to oneiric on 2011-10-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/873113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
