[Bug 1882993] Re: Package needs newer version with v2 encryption policy
Be advised that this package is provided by the Debian Go Packaging Team. https://go-team.pages.debian.net The Go-Team does not use Launchpad. In stead, the package is tracked over at Debian: https://tracker.debian.org/pkg/fscrypt I did not know this at the time I opened this request. Launchpad is probably an automation. Future issues should be reported over at the Debian tracker. https://bugs.debian.org/cgi- bin/pkgreport.cgi?repeatmerged=no=fscrypt For this specific issue, I think we can assume there won't be a backport, but for Ubuntu 22.04 LTS, we will get fscrypt 0.3.1 which is quite recent. https://github.com/google/fscrypt/releases/tag/v0.3.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882993 Title: Package needs newer version with v2 encryption policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1882993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835660] Re: initramfs unpacking failed
Confirmed on Linux 5.4.0-42-generic with Linux Mint 20 (Ubuntu 20.04) clean install. Changing lz4 to gzip in /etc/initramfs-tools/initramfs.conf removed the error (after doing sudo update-initramfs -u) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842417] Re: Ubiquity needs support for fscrypt
Note that the above was added in fscrypt 0.2.6 (january 2020), and it is described here: https://github.com/google/fscrypt/pull/167 Ubuntu still packages 0.2.5 (september 2019) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842417 Title: Ubiquity needs support for fscrypt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1842417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842417] Re: Ubiquity needs support for fscrypt
> I think some problem has to be considered: as far as I understood, the folder > /.fscrypt shall not be deleted (risk to loose access to your data?) > if yes, it's a bit risky in case you re-install system on / with a separated > encrypted /home that you want to keep. When you set up your encrypted home using the fscrypt tool and it detects that /home is not the same as /, it will offer to create a recovery protector. This creates a file in your home called fscrypt- recovery-passphrase.txt (or something like that) that needs to be written down (similar to ecryptfs). This protector is stored on /home/.fscrypt. This means you can unlock the directory on a different (or new) system, and once unlocked, you can create a new login protector. I assume ubiquity can be scripted to detect a pre-existing user home was encrypted using fscrypt, query for the recovery protector passphrase, unlock the directory, and add add a login protector. > I also would like to add an other issue of full disk encryption: it need to enter password at boot on the machine. I hadn't even thought about that because I never use full disk encryption. Some will argue that this is the point as it is more secure, but I would argue that you should have the choice to use your computer in a more versatile manner while still being able to protect your personal files from raw disk reading with a bootable usb stick. Options could be presented: Encryption options: * Full Disk Encryption - (Recommended) Best security. Suitable for single user hardware. * Home Encryption - Good security. Suitable for shared family computers and WoL. * No Encryption - No security. Good for guests and internet cafes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842417 Title: Ubiquity needs support for fscrypt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1842417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842417] Re: Consider reintroducing home encryption using fscrypt
Please give this issue some love too: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1882993 ** Description changed: Home encryption using ecryptfs was removed in Ubuntu 18.04 for reasons. - Full disk encryption was recommended as an alternative. + Full disk encryption was recommended as an alternative, and set as the + one-size-fits-all solution in ubiquity. Not everyone agrees that encrypting the entire disk is the best alternative. Some prefer a more lightweight solution. Others have families and like to share a laptop, perhaps even with an unprivileged - guest account, and family members want to encrypt their home with a - personal password. + password-less guest account, and family members want to encrypt their + home with a personal password. - For some, full disk encryption is unwanted because of reasons. Linux - Mint 19, based on Ubuntu 18.04, re-introduced home encryption using - ecryptfs because users wanted it. - - Can we re-introduce home encryption, this time using fscrypt? Not only - was this suggested (way prematurely) by the Ubuntu 18.04 release notes, - it's also nearing completion with final patches scheduled for Kernel - 5.4. It would be beneficial if we could get this as an option for Ubuntu + Can we re-introduce (an option to choose) home encryption using fscrypt? + Not only was this suggested (prematurely) by the Ubuntu 18.04 release + notes, it's also feature-complete now with v2 kernel encryption policy + patches merged in kernel 5.4, which is the default kernel on Ubuntu 20.04 LTS. - Resources: - Encrypted home with fscrypt - https://askubuntu.com/a/1031509/40475 + Setup + - - Kernel patches for fs keyring - https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git/log/ + Steps that would need to be scripted in ubiquity are as simple as: - Key managemekt fixes in fscrypt tools - https://github.com/ebiggers/fscrypt/commits/fscrypt-key-mgmt-improvements + ``` + apt install fscrypt libpam-fscrypt + fscrypt setup + fscrypt setup / + fscrypt setup /home ## only if home is on a separate partition + fscrypt encrypt /home/$USERNAME + ``` + + For the rest you can probably re-use the ubiquity widgets and detection + code from the ecryptfs days. + + Keep in mind that the fscrypt packages on the Ubuntu repositories are + outdated. See: + https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1882993 + + + Resources + - + + Fscrypt ext4 native encryption documented on Kernel.org + https://www.kernel.org/doc/html/v5.4/filesystems/fscrypt.html + + Build instructions + https://github.com/ebiggers/fscrypt#fscrypt- + + Fscrypt on Arch Linux + https://wiki.archlinux.org/index.php/Fscrypt ** Summary changed: - Consider reintroducing home encryption using fscrypt + Ubiquity needs support for fscrypt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842417 Title: Ubiquity needs support for fscrypt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1842417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882993] Re: Package needs newer version with v2 encryption policy
It's time to package fscrypt 0.2.9. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882993 Title: Package needs newer version with v2 encryption policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1882993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882993] [NEW] Package needs newer version with v2 encryption policy
Public bug reported: The latest packaged version is fscrypt v0.2.5, which is almost a year old. Since then, some serious limitations have been addressed that depend on the 5.4 kernel. https://www.kernel.org/doc/html/latest/filesystems/fscrypt.html The v2 encryption policy allows for some non-trivial fixes that allow usage with docker, www-data and other situations for which multiple system users require access, that right now forces us to use LUKS rather than fscrypt, and have been released specifically before the launch of the Ubuntu focal 20.04 LTS release. Can we update this package for focal to fscrypt v0.2.8? ** Affects: fscrypt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882993 Title: Package needs newer version with v2 encryption policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1882993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
@vicamo any cold boot, right? Not specifically after having this error? For the moment I'm working at home because of reasons, but one of these weeks I'll be at the office (computer) again. But the error itself is pretty rare. I'm also encouraging @mizzao to `apport-collect 1859592` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
@mizzao that sounds a lot like my "solution" comments/2 indeed. However, during hot reboots on my dual boot setup, the Bluetooth DID work in Windows for me, but not in Linux. For Linux, a cold boot was required. So I am inclined to believe that the Linux Bluetooth driver puts the Bluetooth hardware in a certain state that persists across hot reboots but doesn't affect the Windows driver from successfully interacting with the Bluetooth hardware. I believe this to be a software bug where a certain state or signal from the Bluetooth hardware is misinterpreted by the Linux driver, causing it to stop working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
I read from previous bugs and forums on the internet that people seem to think this is BIOS _update_ related. Things don't just break from one day to the next because you suddenly need a firmware update. I tried a couple of things like going to BIOS and loading default settings. Save. Reboot. No change. What finally DID resolve the problem was removing the power cable for a couple of seconds and putting it back in. So although this issue can be closed, I have this deja vu that this kind of weird bluetooth issue happens once or twice per year, but only with Linux. Either this is a coincidence, or there is some kind of state, signal, message, or bit that Windows does or does not send, as opposed to Linux. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824703] Re: Intel 8260 Bluetooth non-functioning, command timeouts
Since this bug is now Invalid, I've opened new bug 1859592. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824703 Title: Intel 8260 Bluetooth non-functioning, command timeouts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859592] [NEW] Bluetooth unavailable after updates - Reading Intel version information failed (-110)
Public bug reported: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842417] [NEW] Consider reintroducing home encryption using fscrypt
Public bug reported: Home encryption using ecryptfs was removed in Ubuntu 18.04 for reasons. Full disk encryption was recommended as an alternative. Not everyone agrees that encrypting the entire disk is the best alternative. Some prefer a more lightweight solution. Others have families and like to share a laptop, perhaps even with an unprivileged guest account, and family members want to encrypt their home with a personal password. For some, full disk encryption is unwanted because of reasons. Linux Mint 19, based on Ubuntu 18.04, re-introduced home encryption using ecryptfs because users wanted it. Can we re-introduce home encryption, this time using fscrypt? Not only was this suggested (way prematurely) by the Ubuntu 18.04 release notes, it's also nearing completion with final patches scheduled for Kernel 5.4. It would be beneficial if we could get this as an option for Ubuntu 20.04 LTS. Resources: Encrypted home with fscrypt https://askubuntu.com/a/1031509/40475 Kernel patches for fs keyring https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git/log/ Key managemekt fixes in fscrypt tools https://github.com/ebiggers/fscrypt/commits/fscrypt-key-mgmt-improvements ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842417 Title: Consider reintroducing home encryption using fscrypt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1842417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768340] Re: fscrypt does not work for home directory encryption
Be advised that it is dangerous to use fscrypt without umask 077, as any user can read the contents of any file you access even if they don't have the security token. https://github.com/google/fscrypt/issues/132 ** Bug watch added: github.com/google/fscrypt/issues #132 https://github.com/google/fscrypt/issues/132 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768340 Title: fscrypt does not work for home directory encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1768340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I'm experiencing this on Linux Mint 19.1 fully updated and NOT encrypted disk or home. This is an LVM install though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768340] Re: fscrypt does not work for home directory encryption
The method described by @tlbdk works on Ubuntu 19.04. I'd like to get this working on a series of Ubuntu 18.04.2 LTS machines. But the packages are at 0.2.2 rather than 0.2.4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768340 Title: fscrypt does not work for home directory encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1768340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744935] Re: [i915] Display Corruption
Had this too, for the first time, on Ubuntu 18.04 LTS. [287327.941338] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [287336.517202] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [287351.237015] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [287368.900772] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Never had this before. I've been running this installation for a while. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744935 Title: [i915] Display Corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768340] Re: fscrypt does not work for home directory encryption
Ubuntu 18.04.1 is released., This issue is not fixed, not addressed, not acknowledged as being an issue by key developers, and no plans to do this in the future were announced. We have migrated our computers to Linux Mint 19 Tara, which (still) supports ecryptfs home encryption. The one drawback according to the release notes is that in order to work around bugs that were introduced upstream, the encrypted home will _not_ be unmounted when a user logs out. This is acceptable to us, first because the boot time is blazing fast (under 5 seconds), but second and more importantly, full disk encryption is not acceptable to us for multiple reasons. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768340 Title: fscrypt does not work for home directory encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1768340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335093] Re: chromium-browser closes/crashes on "Save image as..."
It was not a one time issue; it was present for about 6 months. However, at some point it disappeared. Thank you for responding. This bug can now be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335093 Title: chromium-browser closes/crashes on "Save image as..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1335093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743479] Re: [138a:0097] Validity sensor driver request
I second that. For Ubuntu 18.04 LTS. Same hardware on Lenovo X1 Yoga. Resources: https://certification.ubuntu.com/catalog/component/usb/4222/138a%3A0097/ https://github.com/nmikhailov/Validity90#status https://github.com/hrenod/libfprint#validity-sensor-138a0097-libfprint-driver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743479 Title: [138a:0097] Validity sensor driver request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1743479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726873] Re: mount.ecryptfs_private can't mount in 17.10
*** This bug is a duplicate of bug 1718658 *** https://bugs.launchpad.net/bugs/1718658 Oops sorry, I missed the duplicate warning! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726873 Title: mount.ecryptfs_private can't mount in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1726873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
#26 fixed this for me. Doing a manual mount like so (used for safely storing private data in the cloud) used to work since Ubuntu 12 or so. However, today after updating from Ubuntu 16.04 LTS to 18.04 LTS, the entire thing wouldn't mount anymore: ``` $ echo mypassphrase | sudo ecryptfs-add-passphrase --fnek - Inserted auth tok with sig [abc] into the user session keyring Inserted auth tok with sig [123] into the user session keyring $ sudo /bin/mount -it ecryptfs "/media/locked" "/media/unlocked" -o ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_sig=abc,ecryptfs_fnek_sig=123 mount: /home/local/Dropbox.unlocked: mount(2) system call failed: No such file or directory. ``` I read the following messages in `/var/log/syslog`: ``` kernel: [ 5608.396634] Could not find key with description: [abc] kernel: [ 5608.396641] Could not find valid key in user session keyring for sig specified in mount option: [abc] ``` Apparently there are different keyrings now. This fixed my script: ``` $ sudo keyctl link @u @s $ sudo /bin/mount -it ecryptfs "/media/locked" "/media/unlocked" -o ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_sig=abc,ecryptfs_fnek_sig=123 ``` For now everything works again, but the thing seems buggy. Ubuntu even dropped the encrypted home because of it. Ecryptfs seems to be eol. Looking for fresh solutions to protect the privacy of my cloud files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726873] Re: mount.ecryptfs_private can't mount in 17.10
*** This bug is a duplicate of bug 1718658 *** https://bugs.launchpad.net/bugs/1718658 Doing a manual mount like so (used for safely storing private data in the cloud) used to work since Ubuntu 12 or so. However, today after updating from Ubuntu 16.04 LTS to 18.04 LTS, the entire thing wouldn't mount anymore: ``` $ echo mypassphrase | sudo ecryptfs-add-passphrase --fnek - Inserted auth tok with sig [abc] into the user session keyring Inserted auth tok with sig [123] into the user session keyring $ sudo /bin/mount -it ecryptfs "/media/locked" "/media/unlocked" -o ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_sig=abc,ecryptfs_fnek_sig=123 mount: /home/local/Dropbox.unlocked: mount(2) system call failed: No such file or directory. ``` I read the following messages in `/var/log/syslog`: ``` kernel: [ 5608.396634] Could not find key with description: [abc] kernel: [ 5608.396641] Could not find valid key in user session keyring for sig specified in mount option: [abc] ``` Apparently there are different keyrings now. This fixed my script: ``` $ sudo keyctl link @u @s $ sudo /bin/mount -it ecryptfs "/media/locked" "/media/unlocked" -o ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_sig=abc,ecryptfs_fnek_sig=123 ``` For now everything works again, but the thing seems buggy. Ubuntu even dropped the encrypted home because of it. Ecryptfs seems to be eol. Looking for fresh solutions to protect the privacy of my cloud files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726873 Title: mount.ecryptfs_private can't mount in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1726873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756840] Re: Buggy, under-maintained, not fit for main anymore; alternatives exist
@Seth-Arnold I don't think your comment is relevant to the problem. Let expand on @savvdm Dmitry's comment, for I feel that a couple of balls were dropped, too. Some of us have caught the habit of using a separate /home partition from the early days for the convenience of data-, settings-, and project retention. We have learned - and do so for years - that we can do a fresh install of a Ubuntu, and re-use the /home partition. When /home encryption was introduced, all we needed to do on a fresh install is use the same password, and things would be fine. Now, without a clear warning, without a working alternative, and without an automatic conversion option, doing what we always did results in a broken/unusuable/reset home. There's some mention of some deprecation in the release notes for the people who read those, "but surely the installer will take care of the necessary steps involved in transcoding this once promoted and defaulted feature, no?" (Spoiler: No, it does not.) It should indeed be mentioned clearly in release notes (and in the installer imo) that you can't even log into your encryptfs-encrypted home with Ubuntu 18.04. Otherwise you'd expect something like this in the installer: "We've detected an unsupported home encryption for user foobar. Would you like to:" * Remove your prevous home (this will remove all your files); * Leave your old files in the `.ecryptfs directory` for recovery purposes; * Decrypt your previous home (all multiboot distros can use this user); * Pick a different username (other multiboot distros can keep using this user); -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756840 Title: Buggy, under-maintained, not fit for main anymore; alternatives exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1756840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768340] Re: fscrypt does not work for home directory encryption
So we cannot encrypt our home directory the old way in Ubuntu 18.04, and we cannot encrypt home the new (fscrypt) way as adviced in the release notes. Not everyone agrees that encrypting the entire disk is the best choice. Industrial progress has increased battery life and decreased power usage, but that doesn't mean we can waste these improvements on encrypting all our publicly available software just so our documents can remain private. fscrypt sounds like a great improvement over fuse ecryptfs; but apparently there are two critical bugs. I'd consider Ubuntu 18.04 finished when there's a user-friendly GUI/installer option to "encrypt (only) home". Is there a popularity contest somewhere where my colleagues and I can vote or otherwise help raise awareness for the preference to have fscrypt-type home encryption work from the installer as easily as the old home encryption used to work? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768340 Title: fscrypt does not work for home directory encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1768340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762468] Re: Cryptoswap not working in Bionic
-update- https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1310058 that is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762468 Title: Cryptoswap not working in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762468] Re: Cryptoswap not working in Bionic
At the risk of saying something completely unrelated; any change this is a regression of #1310058 where the UUID got overwritten? It came back a few times around 2015, leading me to believe that the devs don't actually use this method, and might not test for this scenario, making a regression possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762468 Title: Cryptoswap not working in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734518] [NEW] acpi-call-dkms fails to build on HWE kernel
Public bug reported:
While provisioning a brand new laptop, I found that I cannot install
`acpi-call-dkms`.
1) Ubuntu 16.04.3
2) acpi-call-dkms 1.1.0-2
```
$ sudo apt install acpi-call-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
acpi-call-dkms
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 12,9 kB of archives.
After this operation, 73,7 kB of additional disk space will be used.
Get:1 http://ubuntu.mirror.cambrium.nl/ubuntu xenial/universe amd64
acpi-call-dkms all 1.1.0-2 [12,9 kB]
Fetched 12,9 kB in 0s (341 kB/s)
Selecting previously unselected package acpi-call-dkms.
(Reading database ... 285288 files and directories currently installed.)
Preparing to unpack .../acpi-call-dkms_1.1.0-2_all.deb ...
Unpacking acpi-call-dkms (1.1.0-2) ...
Setting up acpi-call-dkms (1.1.0-2) ...
Loading new acpi-call-1.1.0 DKMS files...
First Installation: checking all kernels...
Building only for 4.13.0-17-generic
Building initial module for 4.13.0-17-generic
ERROR (dkms apport): kernel package linux-headers-4.13.0-17-generic is not
supported
Error! Bad return status for module build on kernel: 4.13.0-17-generic (x86_64)
Consult /var/lib/dkms/acpi-call/1.1.0/build/make.log for more information.
$ cat /var/lib/dkms/acpi-call/1.1.0/build/make.log
DKMS make.log for acpi-call-1.1.0 for kernel 4.13.0-17-generic (x86_64)
Sun Nov 26 11:03:42 CET 2017
make: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
AR /var/lib/dkms/acpi-call/1.1.0/build/built-in.o
CC [M] /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o
/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.c: In function ‘acpi_proc_write’:
/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.c:277:9: error: implicit
declaration of function ‘copy_from_user’ [-Werror=implicit-function-declaration]
if (copy_from_user( input, buff, len )) {
^
cc1: some warnings being treated as errors
scripts/Makefile.build:309: recipe for target
'/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o' failed
make[1]: *** [/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o] Error 1
Makefile:1546: recipe for target '_module_/var/lib/dkms/acpi-call/1.1.0/build'
failed
make: *** [_module_/var/lib/dkms/acpi-call/1.1.0/build] Error 2
make: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
```
** Affects: acpi-call (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734518
Title:
acpi-call-dkms fails to build on HWE kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1734518/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic
I have tried 3 different laptops with 3 different distro's. Ubuntu 16.04.1, Ubuntu 16.04.3 and Linux Mint 17. Also I've tried about 8 different kernels. For that reason, a bug report with apport-collect, containing all my hardware serials and stored wifi connections, seems irrelevant. I'm marking this bug confirmed, as instructed by the Kernel Bot. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: - I have two systems that have a Dropbox folder synced. One of the - subfolders contains sensitive data encrypted using ecryptfs. Both were - running linux kernel 4.4.0-53-generic. + UPDATE: + + I think the problem only exists for unencrypted filenames that would + previously pass (by default or) by passing the ecryptfs_passthrough + option. + + Unencrypted filenames work as expected on kernels <=4.4, but are + inaccessable and listed as in kernels >=4.8. + + Original report below: + + + + + I have two systems that have a Dropbox folder synced. One of the subfolders contains sensitive data encrypted using ecryptfs. Both were running linux kernel 4.4.0-53-generic. I have since upgraded one system to use linux kernel 4.8.0-41-generic. Now, the decrypted directory can no longer see groups and owners or read files. All permissions are replaced by questionmarks. 4.8.0-41-generic $ ll ls: cannot access 'Contracts': No such file or directory ls: cannot access 'Documents': No such file or directory ls: cannot access 'Work': No such file or directory total 12K drwxr-x--- 5 redsandro redsandro 4.0K Mar 31 15:54 ./ drwxr-xr-x 7 redsandro redsandro 4.0K Apr 13 13:24 ../ d? ? ? ? ?? Contracts/ d? ? ? ? ?? Documents/ d? ? ? ? ?? Work/ The other machine still works fine. 4.4.0-53-generic: $ ll total 56K drwxr-x--- 5 redsandro redsandro 12K Apr 4 16:11 ./ drwxr-xr-x 8 redsandro redsandro 4.0K Oct 18 13:25 ../ drwxr-xr-x 3 redsandro redsandro 4.0K Nov 2 18:50 Contracts/ drwxr-xr-x 11 redsandro redsandro 4.0K Mar 9 17:03 Documents/ drwxr-xr-x 3 redsandro redsandro 4.0K Mar 4 2013 Work/ For both machines: - $ apt version ecryptfs-utils + $ apt version ecryptfs-utils 111-0ubuntu1.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682410 Title: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic
I think the problem only exists for unencrypted filenames that would previously pass (by default or) by passing the ecryptfs_passthrough option. Unencrypted filenames work as expected on kernels <=4.4, but are inaccessable and listed as in kernels >=4.8. I've tried the mount option ecryptfs_passthrough=yes, ecryptfs_passthrough=y and ecryptfs_passthrough in the commandline: sudo /bin/mount -it ecryptfs /tmp/.files /tmp/files -o ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_enable_filename_crypto=yes,ecryptfs_passthrough,ecryptfs_sig=a1b2c3...,ecryptfs_fnek_sig=a1b2c3...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682410 Title: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic
** Changed in: linux (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682410 Title: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic
@jsalisbury I tried kernel 4.12.0 and the problem exists. Can we re-open this? Something clearly changed between 4.4 and 4.8. And it's not fixed in 4.10 or 4.12. Does someone know what is going on? Using the same mount options, only kernel 4.4.0 and lower will mount the ecryptfs share. Newer kernels will display the as mentioned in the original report. /tmp/test1 on /tmp/test2 type ecryptfs (rw,relatime,ecryptfs_fnek_sig=ab22c3d4e5ee,ecryptfs_sig=ab22c3d4e5ee,ecryptfs_cipher=aes,ecryptfs_key_bytes=32) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682410 Title: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic
INTERESTING: In the new kernels, you can still write new files and read them. You cannot read files written in 'old' kernels. But when booting the old kernel, you can read ALL files, including the one written using the newer kernel! Booting back in 4.8, 4.10 or 4.12, and again you can only read the new file, not the old files. Are there some kind of stricter options that are backwards compatible since 4.8? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682410 Title: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712182] [NEW] GPD Pocket crash on 1st install
Public bug reported: Unboxed my GPD Pocket, autostarting Ubuntu installer. Crash after inputting data. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.2 Uname: Linux 4.12.0-rc2+ x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Aug 21 21:33:32 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash oem-config/enable=true --- InstallationDate: Installed on 2017-07-07 (45 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oem-config ubiquity-2.21.63.2 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712182 Title: GPD Pocket crash on 1st install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1712182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic
Latest I tried was linux 4.10.0-26.30 through the hwe-edge package. ecryptfs still didn't mount properly. I switched back to 4.4.0. Ecryptfs works fine again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682410 Title: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic
(Update: 4.10.0.14.11 does not fix the problem) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682410 Title: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic
@jsalisbury is there a packaged way that takes into account drivers and virtualbox dkms builds? I'm trying out linux-generic-hwe-16.04-edge (version 4.10.0.14.11) now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682410 Title: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic
Hi @jsalisbury, absolutely. Please wait until I have access to said laptop. I will get back to this. @brad-figg I'm sorry, I've analized the logfile and decided there's too much seemingly irrelevant private information. Be more specific and I will supply more details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682410 Title: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682410] Re: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic
Additional info. Upgraded machine: $ uname -a Linux myLaptop 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Working machine: $ uname -a Linux myDesktop 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682410 Title: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682410] [NEW] ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic
Public bug reported: I have two systems that have a Dropbox folder synced. One of the subfolders contains sensitive data encrypted using ecryptfs. Both were running linux kernel 4.4.0-53-generic. I have since upgraded one system to use linux kernel 4.8.0-41-generic. Now, the decrypted directory can no longer see groups and owners or read files. All permissions are replaced by questionmarks. 4.8.0-41-generic $ ll ls: cannot access 'Contracts': No such file or directory ls: cannot access 'Documents': No such file or directory ls: cannot access 'Work': No such file or directory total 12K drwxr-x--- 5 redsandro redsandro 4.0K Mar 31 15:54 ./ drwxr-xr-x 7 redsandro redsandro 4.0K Apr 13 13:24 ../ d? ? ? ? ?? Contracts/ d? ? ? ? ?? Documents/ d? ? ? ? ?? Work/ The other machine still works fine. 4.4.0-53-generic: $ ll total 56K drwxr-x--- 5 redsandro redsandro 12K Apr 4 16:11 ./ drwxr-xr-x 8 redsandro redsandro 4.0K Oct 18 13:25 ../ drwxr-xr-x 3 redsandro redsandro 4.0K Nov 2 18:50 Contracts/ drwxr-xr-x 11 redsandro redsandro 4.0K Mar 9 17:03 Documents/ drwxr-xr-x 3 redsandro redsandro 4.0K Mar 4 2013 Work/ For both machines: $ apt version ecryptfs-utils 111-0ubuntu1.1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682410 Title: ecryptfs-utils not working properly with linux kernel 4.8.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657592] Re: Cannot set hour and minute at same time
Update: It seems that minutes past the half hour are working. 12 23 * * 1-5 command # does not work 45 23 * * 1-5 command # works -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657592 Title: Cannot set hour and minute at same time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1657592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657592] [NEW] Cannot set hour and minute at same time
Public bug reported: I'm using Linux Mint 18 Sarah, which is based on Ubuntu 16.04 LTS, which uses the Ubuntu cron package version 3.0pl1-128ubuntu2. Expectation: --- 11 23 * * 1-5 command To run command from monday to friday on 11 past 23. Observation: --- Doesn't run. * 23 * * 1-5 command # WORKS - every minute at 23 o' clock 11 * * * 1-5 command # WORKS - 11 past every hour 11 23 * * 1-5 command # Does NOT work Work around: --- Only schedule jobs in the second half hour (e.g. 44 minutes past) is possible using this hack: */44 23 * * 1-5 # WORKS ** Affects: cron (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657592 Title: Cannot set hour and minute at same time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1657592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571262] Re: my computer's name is not "Bastien's computer"
I just saw my computer was "Bastien's computer" and I freaked out a bit. I thought I was hacked. Glad it's just a bug, albeit a funky one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571262 Title: my computer's name is not "Bastien's computer" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1571262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 814380] Re: tp_smapi_dkms works one boot only - until hardware reset
Ok, let me take my time machine back to 2010 and warn everybody. O-) (I apologize in advance for this remark.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/814380 Title: tp_smapi_dkms works one boot only - until hardware reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tp-smapi/+bug/814380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301383] Re: Ubuntu installer doesn't format swap partition when selecting encrypted drive and home
*** This bug is a duplicate of bug 953875 *** https://bugs.launchpad.net/bugs/953875 @starman if you have a working setup, could you show us the following files? * /etc/fstabtab * /etc/crypttab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301383 Title: Ubuntu installer doesn't format swap partition when selecting encrypted drive and home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1301383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310058] Re: ecryptfs-setup-swap hints after reboot
A note of warning: Without swap, you are used to your laptop suspending to RAM when closing the lid. @Wetware Random Number Generator (tnrng) wrote on 2014-10-10: #22 My final solution to this problem: This causes laptops to try to hibernate when you close the lid. Failing. Losing all unsaved changes. Even though in Power Management settings are set to suspend (not hibernate). Got any clue on how to get closed laptops to suspend again in stead of hibernate? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310058 Title: ecryptfs-setup-swap hints after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1310058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308783] Re: chromium-browser: java plugin does not work
IcedTea is an NPAPI plugin and is no longer supported by the latest Chromium builds. The Java library is called `libnpjp2.so`, and I am /guessing/ that libnp means this is also NPAPI. https://en.wikipedia.org/wiki/NPAPI#Browser_support _Google Chrome / Chromium: In September 2013, Google announced that NPAPI support in Chrome would be phased out during 2014 because NPAPI’s 90s-era architecture has become a leading cause of hangs, crashes, security incidents, and code complexity._ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308783 Title: chromium-browser: java plugin does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1308783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335093] [NEW] chromium-browser closes/crashes on Save image as...
Public bug reported: Chromium closes/crashes when you right-click on a http:// image served on a https:// page and choose Save image as... $ chromium-browser [18405:18436:0627/135735:FATAL:url_request.cc(707)] Trying to send secure referrer for insecure load Aborted $ uname -a Linux RedFenix 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a Distributor ID: LinuxMint Description:Linux Mint 17 Qiana Release:17 Codename: qiana $ dpkg -s chromium-browser Package: chromium-browser Status: install ok installed Priority: optional Section: web Installed-Size: 153832 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Architecture: amd64 Version: 34.0.1847.116-0ubuntu2 Replaces: chromium-browser-inspector Provides: chromium-browser-inspector, www-browser Depends: gconf-service, libasound2 (= 1.0.16), libatk1.0-0 (= 1.12.4), libc6 (= 2.15), libcairo2 (= 1.6.0), libcap2 (= 2.10), libcomerr2 (= 1.01), libcups2 (= 1.4.0), libdbus-1-3 (= 1.2.14), libexpat1 (= 2.0.1), libfontconfig1 (= 2.9.0), libfreetype6 (= 2.3.9), libgcc1 (= 1:4.1.1), libgconf-2-4 (= 2.31.1), libgcrypt11 (= 1.5.1), libgdk-pixbuf2.0-0 (= 2.22.0), libglib2.0-0 (= 2.37.3), libgnome-keyring0 (= 3.2.2-2~), libgnutls26 (= 2.12.17-0), libgssapi-krb5-2 (= 1.6.dfsg.2), libgtk2.0-0 (= 2.24.0), libk5crypto3 (= 1.6.dfsg.2), libkrb5-3 (= 1.6.dfsg.2), libnspr4 (= 2:4.9-2~) | libnspr4-0d (= 1.8.0.10), libnss3 (= 2:3.14.3), libpango-1.0-0 (= 1.22.0), libpangocairo-1.0-0 (= 1.14.0), libpangoft2-1.0-0 (= 1.14.0), libstdc++6 (= 4.6), libudev1 (= 183), libx11-6 (= 2:1.2.99.901), libxcomposite1 (= 1:0.3-1), libxcursor1 ( 1.1.2), libxdamage1 (= 1:1.1), libxext6, libxfixes3 (= 1:5.0), libxi6 (= 2:1.2.99.4), libxrandr2 (= 2:1.2.99.2), libxrender1, libxss1, libxtst6, zlib1g (= 1:1.1.4), xdg-utils, chromium-codecs-ffmpeg-extra (= 0.6) | chromium-codecs-ffmpeg (= 0.6) Pre-Depends: dpkg (= 1.15.6) Recommends: chromium-browser-l10n Suggests: webaccounts-chromium-extension, unity-chromium-extension, pepperflashplugin-nonfree Conflicts: chromium-browser-inspector Conffiles: /etc/default/chromium-browser 00f6b60b3a6a0b3ec9816ac3bae285eb /etc/chromium-browser/default 00f6b60b3a6a0b3ec9816ac3bae285eb Description: Chromium browser Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. . Chromium serves as a base for Google Chrome, which is Chromium rebranded (name and logo) with very few additions such as usage tracking and an auto-updater system. . This package contains the Chromium browser Homepage: http://code.google.com/chromium/ $ apt-cache showpkg chromium-browser Package: chromium-browser Versions: 34.0.1847.116-0ubuntu2 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_trusty_universe_binary-amd64_Packages) (/var/lib/dpkg/status) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_trusty_universe_binary-amd64_Packages MD5: f899058e5c597ae295f6ef23b467dade Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_trusty_universe_i18n_Translation-en MD5: f899058e5c597ae295f6ef23b467dade Reverse Depends: chromium-browser:i386,chromium-browser mythbuntu-desktop,chromium-browser webaccounts-chromium-extension,chromium-browser unity-chromium-extension,chromium-browser 20.0.1132.47~r144678-0ubuntu4 ubuntukylin-default-settings,chromium-browser mozplugger,chromium-browser lxde-core,chromium-browser lxde,chromium-browser djview-plugin,chromium-browser djview-plugin,chromium-browser chromium-chromedriver,chromium-browser 4.0.203.0~ chromium-browser-l10n,chromium-browser chromium-browser-l10n,chromium-browser 34.0.1847.116-0ubuntu2.1~ chromium-browser-l10n,chromium-browser 34.0.1847.116-0ubuntu2 chromium-browser-dbg,chromium-browser 34.0.1847.116-0ubuntu2 Dependencies: 34.0.1847.116-0ubuntu2 - gconf-service (0 (null)) libasound2 (2 1.0.16) libatk1.0-0 (2 1.12.4) libc6 (2 2.15) libcairo2 (2 1.6.0) libcap2 (2 2.10) libcomerr2 (2 1.01) libcups2 (2 1.4.0) libdbus-1-3 (2 1.2.14) libexpat1 (2 2.0.1) libfontconfig1 (2 2.9.0) libfreetype6 (2 2.3.9) libgcc1 (2 1:4.1.1) libgconf-2-4 (2 2.31.1) libgcrypt11 (2 1.5.1) libgdk-pixbuf2.0-0 (2 2.22.0) libglib2.0-0 (2 2.37.3) libgnome-keyring0 (2 3.2.2-2~) libgnutls26 (2 2.12.17-0) libgssapi-krb5-2 (2 1.6.dfsg.2) libgtk2.0-0 (2 2.24.0) libk5crypto3 (2 1.6.dfsg.2) libkrb5-3 (2 1.6.dfsg.2) libnspr4 (18 2:4.9-2~) libnspr4-0d (2 1.8.0.10) libnss3 (2 2:3.14.3) libpango-1.0-0 (2 1.22.0) libpangocairo-1.0-0 (2 1.14.0) libpangoft2-1.0-0 (2 1.14.0) libstdc++6 (2 4.6) libudev1 (2 183) libx11-6 (2 2:1.2.99.901) libxcomposite1 (2 1:0.3-1) libxcursor1 (4 1.1.2) libxdamage1 (2 1:1.1) libxext6 (0 (null)) libxfixes3 (2 1:5.0) libxi6 (2 2:1.2.99.4) libxrandr2 (2 2:1.2.99.2)
[Bug 1335093] Re: chromium-browser closes/crashes on Save image as...
Similarly https://code.google.com/p/chromium/issues/detail?id=357473 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335093 Title: chromium-browser closes/crashes on Save image as... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1335093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915368] Re: udevd: failed to execute '/lib/udev/mtp-probe'
I have this problem on Ubuntu 13.10 when I try do force a disk check by touching forcefsck on the drives. failed to execute '/lib/udev/mtp-probe' [numbers] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915368 Title: udevd: failed to execute '/lib/udev/mtp-probe' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/915368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255815] [NEW] screenlock does not dpms off when screensaver is disabled
Public bug reported: Desktop Environments like OpenBox and LXDE (in Lubuntu and Debian LXDE) rely on xscreensaver-command -lock to lock the screen. When locking the screen, the screen should turn off (e.g. backlight off). But this only works if you have Blank Screen Only with a timeout selected in xscreensaver-demo. If you disable the screensaver, lock will turn the screen black but won't turn it off (backlight off) anymore. This is undesirable. In certain usecases don't want to have a screensaver or blank screen after a timeout, e.g. for a media player. But we DO want to turn the screen off (completely off) when we lock the screen. (Otherwise the HDMI channel remains 'open' and a multisource display device will keep selecting the black screen when another source/player/platform/console reboots and detaches it's HDMI signal for a few seconds.) ** Affects: xscreensaver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255815 Title: screenlock does not dpms off when screensaver is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1255815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 871093] Re: Notify-OSD and sound-indicator contradict each other after unmute
Unfortunately I sold the Thinkpad Edge laptop. I cannot reproduce on my desktop but I don't know if it was an issue on this desktop back then. So this can either be closed, or wait for someone with Thinkpad Edge to verify. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/871093 Title: Notify-OSD and sound-indicator contradict each other after unmute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/871093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019273] Re: Version Bump to 4.3
I heard the whole problem is that Eclipse 4.x requires Oracle Java 7. Ubuntu (and especially Debian) don't like Oracle, they are packaged with OpenJDK. I don't know the functional difference, I thought the whole idea was that they were compatible. Anyway, Oracle Java 7 is not in the default repos. Also I read there were licensing issues with certain parts of Eclipse 4? Not sure. Just repeating what I think I know. :P -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019273 Title: Version Bump to 4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1019273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156580] Re: Ubuntu 13.04 installer crashes when installing in Virtual Machine
Same problem. Cannot install Ubuntu Xubuntu or Lubuntu i386 guest on VirtualBox 4.2.10 using Windows 8 host. I think they're all running Ubiquity 2.14.6. syslog http://pastebin.com/zu3GbC9Z I am guessing this is the relevant part: Sep 29 17:06:41 xubuntu kernel: [ 4908.488718] lsb_release[10747]: segfault at 0 ip 081575f4 sp bf999f90 error 4 in python3.3[8048000+293000] Sep 29 17:06:42 xubuntu ubiquity: Traceback (most recent call last): Sep 29 17:06:42 xubuntu ubiquity: File /usr/share/apport/apport-gtk, line 590, in module Sep 29 17:06:42 xubuntu ubiquity: app.run_argv() Sep 29 17:06:42 xubuntu ubiquity: File /usr/lib/python3/dist-packages/apport/ui.py, line 656, in run_argv Sep 29 17:06:42 xubuntu ubiquity: return self.run_report_bug() Sep 29 17:06:42 xubuntu ubiquity: File /usr/lib/python3/dist-packages/apport/ui.py, line 458, in run_report_bug Sep 29 17:06:42 xubuntu ubiquity: self.collect_info(symptom_script) Sep 29 17:06:42 xubuntu ubiquity: File /usr/lib/python3/dist-packages/apport/ui.py, line 1009, in collect_info Sep 29 17:06:42 xubuntu ubiquity: icthread.exc_raise() Sep 29 17:06:42 xubuntu ubiquity: File /usr/lib/python3/dist-packages/apport/REThread.py, line 63, in exc_raise Sep 29 17:06:42 xubuntu ubiquity: raise self._exception[1].with_traceback(self._exception[2]) Sep 29 17:06:42 xubuntu ubiquity: File /usr/lib/python3/dist-packages/apport/REThread.py, line 33, in run Sep 29 17:06:42 xubuntu ubiquity: self._retval = self.__target(*self.__args, **self.__kwargs) Sep 29 17:06:42 xubuntu ubiquity: File /usr/lib/python3/dist-packages/apport/ui.py, line 106, in thread_collect_info Sep 29 17:06:42 xubuntu ubiquity: report.add_package_info(package) Sep 29 17:06:42 xubuntu ubiquity: File /usr/lib/python3/dist-packages/apport/report.py, line 314, in add_package_info Sep 29 17:06:42 xubuntu ubiquity: dep, v, self._customized_package_suffix(dep)) Sep 29 17:06:42 xubuntu ubiquity: File /usr/lib/python3/dist-packages/apport/report.py, line 250, in _customized_package_suffix Sep 29 17:06:42 xubuntu ubiquity: if not packaging.is_distro_package(package): Sep 29 17:06:42 xubuntu ubiquity: File /usr/lib/python3/dist-packages/apport/packaging_impl.py, line 176, in is_distro_package Sep 29 17:06:42 xubuntu ubiquity: assert lsb_release.returncode == 0 Sep 29 17:06:42 xubuntu ubiquity: AssertionError Sep 29 17:06:42 xubuntu ubiquity[2905]: log-output -t ubiquity apport-bug ubiquity Sep 29 17:06:42 xubuntu ubiquity[2905]: Reverting lockdown of the desktop environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1156580 Title: Ubuntu 13.04 installer crashes when installing in Virtual Machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1156580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 911622] Re: [12.04] GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei oder Verzeichnis nicht gefunden (file not foun
Debian Testing, the same bug: Processing triggers for hicolor-icon-theme ... (gtk-update-icon-cache:22784): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for shared-mime-info ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911622 Title: [12.04] GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei oder Verzeichnis nicht gefunden (file not found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/911622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839188] Re: Tomboy sync should not freeze note window
Looks like I have been reporting stuff to the wrong tracker. Thanks for taking it upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839188 Title: Tomboy sync should not freeze note window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/839188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152706] [NEW] Unable to restore trash if the containing directory is removed
Public bug reported: When you delete something, it goes into trash. .Trash-$UID/files/TrashedFile.ext .Trash-$UID/info/TrashedFile.ext.trashinfo The trashinfo contains the path relative to .Trash-$UID's parent directory that is the location to which the trashed file or directory should be restored. Imagine accidentally trashing 1000 files, and at some point rmdir the containing directory before you realize you need to restore the trash. In Ubuntu 12.04, no problem, the .trashinfo path would be created when restoring the trash if it didn't exist. In Ubuntu 12.10, you get 1000 popups saying There was an error getting information about the destination. Details: Error when getting information for file '/mountpoint/path/to/file': No such file or directory. For every popup, you can manually do a mkdir -p '/mountpoint/path/to/file', hit RETRY and it will work. Something has changed in the past 11 months that SERIOUSLY cripples the handling of trash. I am not sure this bug is in the right place, or that something else handles the trash for Nautilus. Nemo, fork of Nautilus, has the same problem. If not filed correctly, please think with me where to file this in the right place, because it's pretty important. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152706 Title: Unable to restore trash if the containing directory is removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1152706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152706] Re: Unable to restore trash if the containing directory is removed
Correction: I don't know if 12.04 had that problem. I just remembered I had Lubuntu, and when I try pcmanfm now (just installed on 12.10), it does NOT have this trash problem. So work-around for restoring trash when parent-directories are also removed: Use PcManFM for handling the trash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152706 Title: Unable to restore trash if the containing directory is removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1152706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152706] Re: Unable to restore trash if the containing directory is removed
Thanks for providing me with the correct bugtracker. Here's the link to the bugreport: https://bugzilla.gnome.org/show_bug.cgi?id=695460 ** Bug watch added: GNOME Bug Tracker #695460 https://bugzilla.gnome.org/show_bug.cgi?id=695460 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152706 Title: Unable to restore trash if the containing directory is removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1152706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 571371] Re: Ubuntu One sync is ridiculously slow
+1 in 2013. I have synced 3MB in 3 hours. I put the same folder (1GB of files) in Dropbox, and it was done in half an hour (!). ** Changed in: ubuntuone-client (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/571371 Title: Ubuntu One sync is ridiculously slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/571371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1144703] [NEW] Seahorse does not show name or description of gvfs keys
Public bug reported: 1) Mount a (bunch of) LUKS encrypted 'devices' in Nautilus or Nemo. 2) In the password dialogs, choose to Remember the password forever 3) Open seahorse 4) All added keys are nameless and indistinguishable. 5) Show the properties of such a key, and notice how the description is also empty. 6) With python-gnomekeyring, the discription is not empty, rather something like: Unlock password for: username@hostname 7) Add a description and close seahorse. 8) Open seahorse, and notice how the description is still empty. 9) With python-gnomekeyring, the description has changed to whatever you changed it to. Seahorse 3.6.2 here. Python example: -- #!/usr/bin/env python import gnomekeyring as gk keyring = 'login' keyItems = gk.list_item_ids_sync(keyring) for keyItem in keyItems: key = gk.item_get_info_sync(keyring, keyItem) # Just for testing if key.get_secret() == 'your_password': print Key ID:, key print \tDescription:, key.get_display_name() print \tPassword :, key.get_secret() ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1144703 Title: Seahorse does not show name or description of gvfs keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1144703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1144703] Re: Seahorse does not show name or description of gvfs keys
** Description changed: 1) Mount a (bunch of) LUKS encrypted 'devices' in Nautilus or Nemo. 2) In the password dialogs, choose to Remember the password forever 3) Open seahorse 4) All added keys are nameless and indistinguishable. 5) Show the properties of such a key, and notice how the description is also empty. 6) With python-gnomekeyring, the discription is not empty, rather something like: - Unlock password for: username@hostname - 7) Add a description and close seahorse. - 8) Open seahorse, and notice how the description is still empty. + Encryption passphrase for Seagate SG35623563VER112 (2.0 TB Hard Disk) + 7) Add a description, close, and re-open properties. + 8) Notice how the description is still empty. 9) With python-gnomekeyring, the description has changed to whatever you changed it to. Seahorse 3.6.2 here. Python example: -- #!/usr/bin/env python import gnomekeyring as gk keyring = 'login' keyItems = gk.list_item_ids_sync(keyring) for keyItem in keyItems: - key = gk.item_get_info_sync(keyring, keyItem) - # Just for testing - if key.get_secret() == 'your_password': - print Key ID:, key - print \tDescription:, key.get_display_name() - print \tPassword :, key.get_secret() + key = gk.item_get_info_sync(keyring, keyItem) + # Just for testing + if key.get_secret() == 'your_password': + print Key ID:, key + print \tDescription:, key.get_display_name() + print \tPassword :, key.get_secret() ** Description changed: 1) Mount a (bunch of) LUKS encrypted 'devices' in Nautilus or Nemo. 2) In the password dialogs, choose to Remember the password forever - 3) Open seahorse - 4) All added keys are nameless and indistinguishable. - 5) Show the properties of such a key, and notice how the description is also empty. + 3) Open Seahorse (listed as Passwords and Keys in the Shell or Cinnamon) + 4) All added keys are nameless and indistinguishable. :( x1 + 5) Show the properties of such a key, and notice how the description is also empty. :( x2 6) With python-gnomekeyring, the discription is not empty, rather something like: Encryption passphrase for Seagate SG35623563VER112 (2.0 TB Hard Disk) - 7) Add a description, close, and re-open properties. - 8) Notice how the description is still empty. - 9) With python-gnomekeyring, the description has changed to whatever you changed it to. + 7) Add a description in the Seahorse properties, close, and re-open properties. + 8) Notice how the description is still empty. :( x3 + 9) With python-gnomekeyring, you can see the actual description has changed to whatever you changed it to. Seahorse 3.6.2 here. Python example: -- #!/usr/bin/env python import gnomekeyring as gk keyring = 'login' keyItems = gk.list_item_ids_sync(keyring) for keyItem in keyItems: key = gk.item_get_info_sync(keyring, keyItem) # Just for testing if key.get_secret() == 'your_password': print Key ID:, key print \tDescription:, key.get_display_name() print \tPassword :, key.get_secret() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1144703 Title: Seahorse does not show name or description of gvfs keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1144703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1144781] [NEW] python-gnomekeyring cannot display technical properties of keys
Public bug reported: With python-gnomekeyring you can get the name and the secret of a key. But when you add LUKS passwords that are remembered forever in the gvfs- mount dialog for two or more identical harddrives (or other storage media I presume), there is a problem getting the secret manually. GnomeKeyringItemInfo at 0x1960d70 Name: Encryption passphrase for Seagate ST31000333AS (1.0 TB Hard Disk) Secret: Password001 GnomeKeyringItemInfo at 0x18cf3c0 Name: Encryption passphrase for Seagate ST31000333AS (1.0 TB Hard Disk) Secret: Password002 Searching by name has multiple results, so you can no longer loop to find the related name. In this case you would want to get the details. If you check the Details-tab in Seahorse (AKA Passwords and Keys dialog), you'll see exactly what you need: gvfs-luks-uuid: 5cf35067-5fd0-4a0f-a240-3b4725975ec9 gvfs-luks-uuid: 7fe09d7a-a68b-4776-a78d-df0ef4412e14 But how does Seahorse know this? I cannot get this from GnomeKeyringItemInfo items. ** Affects: gnome-python-desktop (Ubuntu) Importance: Undecided Status: New ** Description changed: With python-gnomekeyring you can get the name and the secret of a key. But when you add LUKS passwords that are remembered forever in the gvfs- - mount dialog for two or more of the same harddrives, there is a problem - getting the secret manually. + mount dialog for two or more identical harddrives (or other storage + media I presume), there is a problem getting the secret manually. GnomeKeyringItemInfo at 0x1960d70 Name: Encryption passphrase for Seagate ST31000333AS (1.0 TB Hard Disk) Secret: Password001 GnomeKeyringItemInfo at 0x18cf3c0 Name: Encryption passphrase for Seagate ST31000333AS (1.0 TB Hard Disk) Secret: Password002 The name has multiple results, so you can no longer loop to find the related name. In this case you would want to get the details. If you check the Details-tab in Seahorse (AKA Passwords and Keys dialog), you'll see exactly what you need: gvfs-luks-uuid: 5cf35067-5fd0-4a0f-a240-3b4725975ec9 gvfs-luks-uuid: 7fe09d7a-a68b-4776-a78d-df0ef4412e14 But how does Seahorse know this? I cannot get this from GnomeKeyringItemInfo items. ** Description changed: With python-gnomekeyring you can get the name and the secret of a key. But when you add LUKS passwords that are remembered forever in the gvfs- mount dialog for two or more identical harddrives (or other storage media I presume), there is a problem getting the secret manually. GnomeKeyringItemInfo at 0x1960d70 Name: Encryption passphrase for Seagate ST31000333AS (1.0 TB Hard Disk) Secret: Password001 GnomeKeyringItemInfo at 0x18cf3c0 Name: Encryption passphrase for Seagate ST31000333AS (1.0 TB Hard Disk) Secret: Password002 - The name has multiple results, so you can no longer loop to find the related name. In this case you would want to get the details. If you check the Details-tab in Seahorse (AKA Passwords and Keys dialog), you'll see exactly what you need: + Searching by name has multiple results, so you can no longer loop to find the related name. In this case you would want to get the details. If you check the Details-tab in Seahorse (AKA Passwords and Keys dialog), you'll see exactly what you need: gvfs-luks-uuid: 5cf35067-5fd0-4a0f-a240-3b4725975ec9 gvfs-luks-uuid: 7fe09d7a-a68b-4776-a78d-df0ef4412e14 But how does Seahorse know this? I cannot get this from GnomeKeyringItemInfo items. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1144781 Title: python-gnomekeyring cannot display technical properties of keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-python-desktop/+bug/1144781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083644] Re: Palimpsest does not support gparted GPT
I changed it to confirmed for you. ** Changed in: gnome-disk-utility (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083644 Title: Palimpsest does not support gparted GPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1083644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083644] Re: Palimpsest does not support gparted GPT
Please mention the version of the OS (and which distro) and packages involved when you get back to the relevant computer, because I did not have this problem in 12.10, however I DID have the problem in 12.04.1. Perhaps the problem got reintroduced with some update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083644 Title: Palimpsest does not support gparted GPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1083644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094187] Re: ntfs-3g keeps crashing with SIGABRT in raise()
Thank you. Unfortunately these non-Ubuntu sources are too complicated to upgrade fuse. This used to work, (until Ubuntu decided to use a buggy version of fuse if you are right). This solution is not acceptable to users. There should be a .deb, a ppa, or a package in ubuntu-proposed. 12.10 is the main distro, still supported, and gravely crippled by this. Is someone looking into this on the Ubuntu side of things? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094187 Title: ntfs-3g keeps crashing with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1094187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094187] Re: ntfs-3g keeps crashing with SIGABRT in raise()
The latest Ubuntu package contains fuse 2.9.0 while the latest upstream release is 2.9.2, am I wrong? Also in Mint, a kernel update is just a manual upgrade away, it's no problem, as long as it it in the Ubuntu repo. So with kernel 3.5.0-23-generic I practically have an up to date Ubuntu 12.10. What is a problem though is if we (users) have to manually 'retrofit' upstream into current Ubuntu because the one packaged by Ubuntu breaks ntfs-3g in certain use cases. So the bug might not be in Ubuntu, but the choice not to provide a fixed version is Ubuntu's. Unless there's an upgrade path I am missing; I would gladly try it out. However, afaik I am up to date. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094187 Title: ntfs-3g keeps crashing with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1094187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580333] Re: tomboy notes disappeared
I have now something similar. When I sync my notes, al my 140 notes get removed. So I delete ~/.config/tomboy/manifest.xml I copy my note backups to ~/.local/share/tomboy I sync, and all 140 notes are uploaded to server (Ubuntu One). I sync a 2nd time, and all notes are removed locally again. I followed this guide to purge the server: https://one.ubuntu.com/help/faq/how-can-i-delete-all-my-tomboy-notes-from-the-server/ But I still have the same behavior. Every computer I power on gets all my notes removed. I restore backup to ~/.local/share/tomboy, all notes uploaded again and removed again on 2nd sync. The part about purging your couchdb locally doesn't work as the linked script is not available anymore. Is that still relevant, or for older tomboy versions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/580333 Title: tomboy notes disappeared To manage notifications about this bug go to: https://bugs.launchpad.net/tomboy/+bug/580333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580333] Re: tomboy notes disappeared
Also I tried increasing the last-sync-date/, last-sync-rev/ and latest-revision values, but still same behavior. Is there a trick to nuke every trace of tomboy life and start over with my backup, without them getting removed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/580333 Title: tomboy notes disappeared To manage notifications about this bug go to: https://bugs.launchpad.net/tomboy/+bug/580333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083644] Re: Palimpsest does not support gparted GPT
You are right. Disk Utility in the current version (see below) from Linux Mint 12.10 does not have this problem. But maybe it has something to do with the policy of only allowing LUKS to be formatted with EXT4. That is the only option. After that's done, you have to select the unlocked EXT4 partition to format it as something else, e.g. NTFS. Sorry for getting back so late but it is not every day that I have a spare 4TB drive to format. $ sudo apt-cache show gnome-disk-utility Package: gnome-disk-utility Priority: optional Section: admin Installed-Size: 880 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Utopia Maintenance Team pkg-utopia-maintain...@lists.alioth.debian.org Architecture: amd64 Version: 3.6.1-0ubuntu1 Depends: libc6 (= 2.7), libcairo2 (= 1.2.4), libgdk-pixbuf2.0-0 (= 2.22.0), libglib2.0-0 (= 2.31.18), libgtk-3-0 (= 3.5.8), libpango1.0-0 (= 1.18.0), libpwquality1 (= 1.1.0), libsecret-1-0 (= 0.7), libudisks2-0, dconf-gsettings-backend | gsettings-backend, udisks2 Pre-Depends: dpkg (= 1.15.7.2) Filename: pool/main/g/gnome-disk-utility/gnome-disk-utility_3.6.1-0ubuntu1_amd64.deb Size: 180382 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083644 Title: Palimpsest does not support gparted GPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1083644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094187] Re: ntfs-3g keeps crashing with SIGABRT in raise()
So Jean-Pierre how do we update Fuse? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094187 Title: ntfs-3g keeps crashing with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1094187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094187] Re: ntfs-3g keeps crashing with SIGABRT in raise()
And/or can you provide us with a link to the bug on the fuse bugtracker? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094187 Title: ntfs-3g keeps crashing with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1094187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094187] Re: ntfs-3g keeps crashing with SIGABRT in raise()
The version for the distro is current. https://launchpad.net/ubuntu/+source/fuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094187 Title: ntfs-3g keeps crashing with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1094187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094187] Re: ntfs-3g keeps crashing with SIGABRT in raise()
You might be correct, the default package for Ubuntu 12.10 and the likes (Mint) is indeed Version: 2.9.0-1ubuntu2. But there are no updates in the most modern of repos, which seems weird considering this bug is a show-stopper. Anyhow, looking for the nighly PPA or updates PPA or Team FUSE or anything, I can not find a source of a more updated version. Do you know of a PPA or package for this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094187 Title: ntfs-3g keeps crashing with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1094187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094187] [NEW] ntfs-3g keeps crashing with SIGABRT in raise()
Public bug reported: ntfs-3g crashed three times so far during a long and unattended sync of ecryptfs encrypted files. I am running Linux Mint 14 and it refuses to report this after I click 'report' on the reporter, so I thought I'd mention this manually. I never experienced a problem with (older) ntfs-3g before and now a bunch of times. I thought it'd be important to mention. Package: ntfs-3g Priority: standard Section: otherosfs Installed-Size: 1428 Architecture: amd64 Version: 1:2012.1.15AR.5-4ubuntu3 Conflicts: libntfs-3g75, ntfsprogs ( 1:2011.10.9AR.1-3~) Filename: pool/main/n/ntfs-3g/ntfs-3g_2012.1.15AR.5-4ubuntu3_amd64.deb MD5sum: f2d8245a42321dcc7ecbc4539c7aa063 SHA1: 538d6ee0590eede87587f1ea05d5f9c8ace74dc1 SHA256: 57ad96912387aa1ef489cd866034892b7a3a9f1c74ea569890792b199d29f545 ProblemType: Crash Architecture: amd64 CrashCounter: 1 // Dunno why 1, this is the 3rd time in a week Date: Thu Dec 27 07:56:47 2012 DistroRelease: LinuxMint 14 ExecutablePath: /bin/ntfs-3g ExecutableTimestamp: 1347256401 ProcCmdline: /sbin/mount.ntfs /dev/sdc2 /mnt/red4t -o rw ProcCwd: / ProcEnviron: TERM=linux LANG=en_US.UTF-8 SourcePackage: ntfs-3g Stacktrace: #0 0x7f868213f425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x7f8682142b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x7f868271a305 in ?? () from /lib/x86_64-linux-gnu/libfuse.so.2 No symbol table info available. #3 0x7f868271b4dc in ?? () from /lib/x86_64-linux-gnu/libfuse.so.2 No symbol table info available. #4 0x7f868271b75f in ?? () from /lib/x86_64-linux-gnu/libfuse.so.2 No symbol table info available. #5 0x7f8682727947 in ?? () from /lib/x86_64-linux-gnu/libfuse.so.2 No symbol table info available. #6 0x7f86827241af in fuse_session_loop () from /lib/x86_64-linux-gnu/libfuse.so.2 No symbol table info available. #7 0x7f868271c1d8 in fuse_loop () from /lib/x86_64-linux-gnu/libfuse.so.2 No symbol table info available. #8 0x7f8682b75465 in main () No symbol table info available. StacktraceAddressSignature: /bin/ntfs-3g:6:x86_64:/lib/x86_64-linux-gnu/libc-2.15.so+36425:/lib/x86_64-linux-gnu/libc-2.15.so+39b8b:/lib/x86_64-linux-gnu/libfuse.so.2.9.0+8305:/lib/x86_64-linux-gnu/libfuse.so.2.9.0+94dc:/lib/x86_64-linux-gnu/libfuse.so.2.9.0+975f:/lib/x86_64-linux-gnu/libfuse.so.2.9.0+15947:/lib/x86_64-linux-gnu/libfuse.so.2.9.0+121af:/lib/x86_64-linux-gnu/libfuse.so.2.9.0+a1d8:/bin/ntfs-3g+4465 StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libfuse.so.2 ?? () from /lib/x86_64-linux-gnu/libfuse.so.2 ?? () from /lib/x86_64-linux-gnu/libfuse.so.2 Tags: third-party-packages nadia ThreadStacktrace: . Thread 1 (Thread 0x7f8682b42700 (LWP 653)): #0 0x7f868213f425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x7f8682142b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x7f868271a305 in ?? () from /lib/x86_64-linux-gnu/libfuse.so.2 No symbol table info available. #3 0x7f868271b4dc in ?? () from /lib/x86_64-linux-gnu/libfuse.so.2 No symbol table info available. #4 0x7f868271b75f in ?? () from /lib/x86_64-linux-gnu/libfuse.so.2 No symbol table info available. #5 0x7f8682727947 in ?? () from /lib/x86_64-linux-gnu/libfuse.so.2 No symbol table info available. #6 0x7f86827241af in fuse_session_loop () from /lib/x86_64-linux-gnu/libfuse.so.2 No symbol table info available. #7 0x7f868271c1d8 in fuse_loop () from /lib/x86_64-linux-gnu/libfuse.so.2 No symbol table info available. #8 0x7f8682b75465 in main () No symbol table info available. ** Affects: ntfs-3g (Ubuntu) Importance: Undecided Status: New ** Attachment added: /var/crash/_bin_ntfs-3g.0.crash https://bugs.launchpad.net/bugs/1094187/+attachment/3469570/+files/_bin_ntfs-3g.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094187 Title: ntfs-3g keeps crashing with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1094187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 741364] Re: libecryptfs_key_mod_openssl.so does not exist in ecryptfs-utils
I just noticed that the ecryptfs manual itself still mentions the optional key that was removed from the ecryptfs-utils manual: openssl_keyfile=(filename) The filename should be the filename of a file containing an RSA SSL key. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741364 Title: libecryptfs_key_mod_openssl.so does not exist in ecryptfs-utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/741364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 741364] Re: libecryptfs_key_mod_openssl.so does not exist in ecryptfs-utils
We're at 12.10 now. However, the module that should, according to the manual, be available at a minimum, still hasn't made it to the main release. Any comments about the stability and the chances of seeing this in this or the next release? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741364 Title: libecryptfs_key_mod_openssl.so does not exist in ecryptfs-utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/741364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 741364] Re: libecryptfs_key_mod_openssl.so does not exist in ecryptfs-utils
PS adding ppa:ecryptfs/ppa results in 404s, e.g.: W: Failed to fetch http://ppa.launchpad.net/ecryptfs/ppa/ubuntu/dists/quantal/main/binary-amd64/Packages 404 Not Found -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741364 Title: libecryptfs_key_mod_openssl.so does not exist in ecryptfs-utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/741364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 741364] Re: libecryptfs_key_mod_openssl.so does not exist in ecryptfs-utils
Thanks for the reply. Which man page? I don't see that stated in any of the 12.10 man pages. Sorry, I played with this at home (12.10) but I am at an old version (at work) now. :P I just assumed the manual was the same as here. It's too bad there is little to no interest. Ecryptfs is really great technology. I am using it for encrypting mountable OTFE remote backups, and I like to use a simple password at the safe local site, yet have strong key based encryption on the files. Because, as the ecryptfs manual puts it (or used to put it): Cryptographic keys derived from passphrases are generally worthless. It could be that I am using ecryptfs in a silly way, because otherwise, given the popularity of key+password based ssh login to servers for maintenance, one would think that typical devs would actually prefer keys over passwords. Am I missing a trick? Is it possible to use a crazy password and store it in your keyring permanently so the ecryptfs will mount without a password dialog when logged in and keyring opened? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741364 Title: libecryptfs_key_mod_openssl.so does not exist in ecryptfs-utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/741364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 741364] Re: libecryptfs_key_mod_openssl.so does not exist in ecryptfs-utils
PS - I think ecryptfs-manager does exactly that - setting up passwordless mounting. But the 'kernel keyring' concept of ecryptfs- manager, as opposed to 'user keyring' scared me away of using it. I want to keep keys and secrets within my user, not something system-wide. But I guess terminology on this is not my strongsuit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741364 Title: libecryptfs_key_mod_openssl.so does not exist in ecryptfs-utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/741364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083644] Re: Palimpsest does not support gparted GPT
Might take some moments. It's not often that one can displace 4 Terabytes of data to perform tests on a drive. Are you positive you tried this on a drive of minimal 3.3 Terabytes in size? I believe that is the hard limit for MBR based partition tables. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083644 Title: Palimpsest does not support gparted GPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1083644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083644] Re: Palimpsest does not support gparted GPT
PS What is the current version of this package? I have no updates in the manager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083644 Title: Palimpsest does not support gparted GPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1083644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083644] [NEW] Palimpsest does not support gparted GPT
Public bug reported: The Disk Utility cannot edit partitions (create, delete, LUKS) on GPT- based drives with a size bigger than MBR-based drives would support. I have a 4TB WD My Book 1140.1016 that requires a GPT partition table because it's 4GB, beyond MBR (MSDOS) limits. When I create a GPT partition table, I cannot add or remove partitions from the Disk Utility with this output: Error erasing: helper exited with exit code 1: In part_del_partition: device_file=/dev/sdb, offset=3145729048576 Entering MS-DOS parser (offset=0, size=4000752599040) MSDOS_MAGIC found found partition type 0xee = protective MBR for GPT Exiting MS-DOS parser Entering EFI GPT parser No GPT_MAGIC found Leaving EFI GPT parser Entering Apple parser No MAC_MAGIC found Leaving Apple parser No known partition table found got it got disk ped_disk_get_partition_by_sector() failed Distributor ID: Ubuntu Description:Ubuntu 12.04.1 LTS Release:12.04 Codename: precise Package: gnome-disk-utility Architecture: amd64 Version: 3.0.2-2ubuntu7 Depends: libc6 (= 2.2.5), libgdu-gtk0 (= 3.0.0), libgdu0 (= 2.29.90), libglib2.0-0 (= 2.22.0), libgtk-3-0 (= 3.0.0), liblaunchpad-integration-3.0-1 (= 0.1.17), libnautilus-extension1a (= 1:2.91), libnotify4 (= 0.7.0), libunique-3.0-0 (= 2.90.1) Filename: pool/main/g/gnome-disk-utility/gnome-disk-utility_3.0.2-2ubuntu7_amd64.deb Size: 464774 ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083644 Title: Palimpsest does not support gparted GPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1083644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083644] Re: Palimpsest does not support gparted GPT
Just noticed: When you remove all partitions in gparted, the partition table is still GPT. But according to Disk Utility, there is no partition table. Looks like GPT is not recognized even though there is mention of having GPT knowledge in the above error message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083644 Title: Palimpsest does not support gparted GPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1083644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070207] Re: Trackpoint doesn't work on Thinkpad L530
I have a similar problem with the brand new Lenovo Thinkpad X1 Carbon laptop. Trackpoint works in Ubuntu 12.04. In 12.10, it does not. (?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070207 Title: Trackpoint doesn't work on Thinkpad L530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1070207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873058] Re: Jockey fails to install binary ati driver (post release) version
After choosing the proposed repo in synaptic and refreshing, there was no update for jockey (or nvidia-common, if that's still relevant for amd). Unable to verify. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873058 Title: Jockey fails to install binary ati driver (post release) version To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/873058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873058] Re: Jockey fails to install binary ati driver (post release) version
@Brian My mistake, you are talking about oneiric-proposed and I am running precise lts. I conveniently assumed you were talking about precise. Anyway, doesn't it make more sense to have a fix in precise-proposed since everyone is and will be running lts while 11.10 is kinda old news? Precise error jockey.jog ** Attachment added: jockey.log https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/873058/+attachment/3301495/+files/jockey.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873058 Title: Jockey fails to install binary ati driver (post release) version To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/873058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873058] Re: Jockey fails to install binary ati driver (post release) version
FYI, although status 'Fix Released', the bug remains. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873058 Title: Jockey fails to install binary ati driver (post release) version To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/873058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873058] Re: Jockey fails to install binary ati driver (post release) version
Note on comment #84 attachment: Please ignore until DEBUG: dpkg: error: dpkg status database is locked by another process I closed synaptic and ran the update again. Refer to 2nd part of the log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873058 Title: Jockey fails to install binary ati driver (post release) version To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/873058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 873058] Re: Jockey fails to install binary ati driver (post release) version
The link is not very straightforward. How do we test this without getting every proposed update? 1) enable proposed in synaptic 2) update jockey 3) restricted drivers - install post-release updates one 4) disable proposed in synaptic Is this correct? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/873058 Title: Jockey fails to install binary ati driver (post release) version To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/873058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028518] Re: Fn keys such as brightness and volume stopped working after update
I don't know by which update, but the bug is partially fixed. SOUND The sound hotkeys work normally again. BRIGHTNESS Buggy. The hotkeys work again, but there are now 7 steps, and the indicator goes (from min to max) like this: min, middle, max, min, middle, max. When it worked fine (before this bug) I had like 10 (?) steps. Now I have 7 steps, but the indicator popup has only 3 steps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028518 Title: Fn keys such as brightness and volume stopped working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1028518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028518] Re: Fn keys such as brightness and volume stopped working after update
** Description changed: + -UPDATE- September 4 - Recent updates reintroduced functional Fn-Keys, + but the Brightness Fn-keys are behaving poorly, compared to before when + they behaved perfectly. + + See comment #13 + + Original report: + + I have a Lenovo Thinkpad Edge 15, happily running Ubuntu 12.04 + Cinnamon. Today after updating, certain Fn Function Keys didn't work anymore, like brightness, volume and mute. Other Fn keys like Play Pause Next, they still work. Tried rebooting some more. Google and Launchpad search. Appears this happened often during the years with older laptops and patches were released, but now it's back. Unfortunately, I don't know which package or which update exactly, because I don't update daily. I think the update must have been a week old at max. In short: pressing Fn + F# used to toggle or adjust something and a popup would appear, indicating the change. Now, nothing is indicated and nothing is changed either. I hope someone knows where to look. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028518 Title: Fn keys such as brightness and volume stopped working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1028518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028518] Re: Fn keys such as brightness and volume stopped working after update
@rCX: I cannot test your hypothesis, because I do not have Windows installed at the moment. However, two notes: 1) This is a brand new Edge from september 2011 (Intel), which is different from the ones made pre-2011 (AMD) which are mentioned in topics with similar problems. 2) Hotkeys have always worked, until one day they did not. How can this be BIOS/hardware related? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028518 Title: Fn keys such as brightness and volume stopped working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1028518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028518] Re: Fn keys such as brightness and volume stopped working after update
Also, I try to troubleshoot according to this guide: https://wiki.ubuntu.com/Hotkeys/Troubleshooting to narrow the problem down, but everytime I kill gnome-settings-daemon it just restarts itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028518 Title: Fn keys such as brightness and volume stopped working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1028518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028518] Re: Fn keys such as brightness and volume stopped working after update
I wish I could change gnome-settings-daemon back into ubuntu for package, because peer pressure from the Bug Bot made me choose something that I am not sure about. The truth is, when you see something not happening, it's hard to know what causes it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028518 Title: Fn keys such as brightness and volume stopped working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1028518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028518] Re: Fn keys such as brightness and volume stopped working after update
# lspci -vnn | grep -A10 VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:215a] Flags: bus master, fast devsel, latency 0, IRQ 42 Memory at f000 (64-bit, non-prefetchable) [size=4M] Memory at d000 (64-bit, prefetchable) [size=256M] I/O ports at 1800 [size=8] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028518 Title: Fn keys such as brightness and volume stopped working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1028518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028518] [NEW] Fn keys such as brightness and volume stopped working after update
Public bug reported: I have a Lenovo Thinkpad Edge 15, happily running Ubuntu 12.04 + Cinnamon. Today after updating, certain Fn Function Keys didn't work anymore, like brightness, volume and mute. Other Fn keys like Play Pause Next, they still work. Tried rebooting some more. Google and Launchpad search. Appears this happened often during the years with older laptops and patches were released, but now it's back. Unfortunately, I don't know which package or which update exactly, because I don't update daily. I think the update must have been a week old at max. In short: pressing Fn + F# used to toggle or adjust something and a popup would appear, indicating the change. Now, nothing is indicated and nothing is changed either. I hope someone knows where to look. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028518 Title: Fn keys such as brightness and volume stopped working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1028518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028518] Re: Fn keys such as brightness and volume stopped working after update
For reference purposes, here's how to set that brightness in case of emergencies without the Fn keys: Set the value of: /sys/class/backlight/acpi_video0/brightness to a value between 1 and max, where max is: /sys/class/backlight/acpi_video0/max_brightness Note that you can't just sudo echo it in there. (???) You'll need to pipe-feed it, e.g.: echo 15 | sudo tee /sys/class/backlight/acpi_video0/brightness -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028518 Title: Fn keys such as brightness and volume stopped working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1028518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028518] Re: Fn keys such as brightness and volume stopped working after update
The Brightness and Lock dialog also still works fine. (I didn't even know that dialog existed) You can find it in System Settings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028518 Title: Fn keys such as brightness and volume stopped working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1028518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028518] Re: Fn keys such as brightness and volume stopped working after update
gnome-settings-daemon, gnome-control-center? Not sure. ** Package changed: ubuntu = gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028518 Title: Fn keys such as brightness and volume stopped working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1028518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
