[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
Maybe there are separate issues. Booting to a black screen after update happened on three of my machines (2 nvidia, 1 AMD). On all of them it was enough to remove the binary drivers, reboot and reinstall them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
The solution is actually easier than #60. You just need to remove and reinstall the nvidia drivers (or amd if you used those). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
There is a quite popular question on Askubuntu regarding this: https://askubuntu.com/questions/96/after-the-upgrade-to-17-10-i-only-get-a-black-screen-how-do-i-fix-this -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
@levien: I think people might be mixing both bugs up, but as I mostly use the terminal for copying and moving, I can assure you this is its own bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB Status in nautilus package in Ubuntu: Confirmed Bug description: Hi While copying many and large files to and from a USB drive, the system becomes incredibly slow and sometimes hangs. I watched the system monitor while it was running slowly but cpu was not above 50% at any time, the same for memory. I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD" laptop. Description: Ubuntu 13.04 Release: 13.04 nautilus: Installed: 1:3.6.3-0ubuntu16 Candidate: 1:3.6.3-0ubuntu16 Version table: *** 1:3.6.3-0ubuntu16 0 500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Aquire many large files (like your totally legit moviecollection) 2) Copy files to external HD 3) Open your browser and be sad when your system becomes incredibly slow after a few minutes This is my first bugreport so if I'm missing something, please tell me. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Aug 6 22:56:34 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-05-31 (67 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1208993/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666681] Re: Drop interactive_search.patch (type-ahead search)
Hey Carlos @csoriano, sorry for replying to such an old bug but I didn't know where else to do this. You mentioned use-case covered by search, so here are my usecases not covered by search (as far as I know). In research projects you often have big datasets. So e.g., when I get data from an MRT-scan with a couple of thousand images, tracker is out of the question. I need to access the data immediately and can't wait for indexing. When I want to navigate to images starting with "PBX" I just enter that for type-ahead and Nautilus jumps directly to the first file starting with that while still showing me the files before and after (according to the current sort-order). Search doesn't navigate, it searches for "PBX" and shows me all files containing PBX anywhere (after a long wait because the files aren't indexed, yet). Sometimes I need to see files in the context of their creation time. With type-ahead I just sort by date and navigate to a specific file to see which files where created before and after the file in question. Researcher who are already using newer versions of Gnome without type- ahead often just use PgUp/PgDown until the see what they need instead of directly navigating there. You see the pattern: search can't replace navigation. They are two seperate things. Thanks for taking the time to reply here. If you're interested in discussing this further, just let me know where. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/181 Title: Drop interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Confirmed Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
This problem started ocurring for me when I moved to 16.04. I also upgraded my RAM from 8 to 16GB. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB Status in nautilus package in Ubuntu: Confirmed Bug description: Hi While copying many and large files to and from a USB drive, the system becomes incredibly slow and sometimes hangs. I watched the system monitor while it was running slowly but cpu was not above 50% at any time, the same for memory. I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD" laptop. Description: Ubuntu 13.04 Release: 13.04 nautilus: Installed: 1:3.6.3-0ubuntu16 Candidate: 1:3.6.3-0ubuntu16 Version table: *** 1:3.6.3-0ubuntu16 0 500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Aquire many large files (like your totally legit moviecollection) 2) Copy files to external HD 3) Open your browser and be sad when your system becomes incredibly slow after a few minutes This is my first bugreport so if I'm missing something, please tell me. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Aug 6 22:56:34 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-05-31 (67 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1208993/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
That's another bug then, the cause of this issue is definately fixed. If you experience something similar, please open a new bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Fix Released Status in ibus source package in Trusty: Fix Released Bug description: [Impact] When first boot into Unity desktop, English keyboard layout is active while all other parts of the system language settings are set to another language (e.g. German). The bug is properly addressed in newer upstream releases in Vivid, but the changes is too intrusive and not suitable for being back ported in SRU. And changing the default to use system keyboard layout solves the problem. [Test Case] 1. Set the system language to something other than English, e.g. German. 2. Create a new user, log in to the Unity desktop of the new user. 3. Check the keyboard layout, it should be German instead of English. [Regression Potential] Since this changes the default value of the keyboard layout settings by using system defined as default, it avoids using ibus's built-in keyboard layout related functionality, so that this could be a regression for users rely on this certain behavior (e.g. use English keyboard while want to keep the system language settings to German), but such behavior is not expected for normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
@brunonova I did the same test with the same result. As to whether the setting really fixes the bug: I can confirm that for at least 50 machines of a client. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Fix Released Status in ibus source package in Trusty: Fix Committed Bug description: [Impact] When first boot into Unity desktop, English keyboard layout is active while all other parts of the system language settings are set to another language (e.g. German). The bug is properly addressed in newer upstream releases in Vivid, but the changes is too intrusive and not suitable for being back ported in SRU. And changing the default to use system keyboard layout solves the problem. [Test Case] 1. Set the system language to something other than English, e.g. German. 2. Create a new user, log in to the Unity desktop of the new user. 3. Check the keyboard layout, it should be German instead of English. [Regression Potential] Since this changes the default value of the keyboard layout settings by using system defined as default, it avoids using ibus's built-in keyboard layout related functionality, so that this could be a regression for users rely on this certain behavior (e.g. use English keyboard while want to keep the system language settings to German), but such behavior is not expected for normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
We already figured out how this was introduced and how to fix it. We just need someone to actually create the fix. The ibus package changed the default setting of desktop.ibus.general .use-system-keyboard-layout from true to false. Ever since this dconf setting was introduced, we had this error. For existing installations you need to change this manually either with dconf-editor or ibus-setup. For fresh installs we need to patch the package to revert this setting back to its old default. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Confirmed Status in ibus source package in Trusty: Triaged Bug description: [Impact] When first boot into Unity desktop, English keyboard layout is active while all other parts of the system language settings are set to another language (e.g. German). The bug is properly addressed in newer upstream releases in Vivid, but the changes is too intrusive and not suitable for being back ported in SRU. And changing the default to use system keyboard layout solves the problem. [Test Case] 1. Set the system language to something other than English, e.g. German. 2. Create a new user, log in to the Unity desktop of the new user. 3. Check the keyboard layout, it should be German instead of English. [Regression Potential] Since this changes the default value of the keyboard layout settings by using system defined as default, it avoids using ibus's built-in keyboard layout related functionality, so that this could be a regression for users rely on this certain behavior (e.g. use English keyboard while want to keep the system language settings to German), but such behavior is not expected for normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
I confirmed with @hoellp that the packages in proposed are not working. They are not reverting the dconf setting for newly created users. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Fix Released Status in ibus source package in Trusty: Triaged Bug description: [Impact] When first boot into Unity desktop, English keyboard layout is active while all other parts of the system language settings are set to another language (e.g. German). The bug is properly addressed in newer upstream releases in Vivid, but the changes is too intrusive and not suitable for being back ported in SRU. And changing the default to use system keyboard layout solves the problem. [Test Case] 1. Set the system language to something other than English, e.g. German. 2. Create a new user, log in to the Unity desktop of the new user. 3. Check the keyboard layout, it should be German instead of English. [Regression Potential] Since this changes the default value of the keyboard layout settings by using system defined as default, it avoids using ibus's built-in keyboard layout related functionality, so that this could be a regression for users rely on this certain behavior (e.g. use English keyboard while want to keep the system language settings to German), but such behavior is not expected for normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
@hoellp can you run "ibus-setup" and check the "Erweitert" (Advanced) tab? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Fix Released Status in ibus source package in Trusty: Triaged Bug description: [Impact] When first boot into Unity desktop, English keyboard layout is active while all other parts of the system language settings are set to another language (e.g. German). The bug is properly addressed in newer upstream releases in Vivid, but the changes is too intrusive and not suitable for being back ported in SRU. And changing the default to use system keyboard layout solves the problem. [Test Case] 1. Set the system language to something other than English, e.g. German. 2. Create a new user, log in to the Unity desktop of the new user. 3. Check the keyboard layout, it should be German instead of English. [Regression Potential] Since this changes the default value of the keyboard layout settings by using system defined as default, it avoids using ibus's built-in keyboard layout related functionality, so that this could be a regression for users rely on this certain behavior (e.g. use English keyboard while want to keep the system language settings to German), but such behavior is not expected for normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
How to test if the proposed package fixes this: 1. Install proposed package 2. create new user 3. login as the new user 4. run dconf read /desktop/ibus/general/use-system-keyboard-layout The result should be 'true'. I don't have a machine with 14.04 anymore so I can't test this. Please folks, lets finally get this fixed. For all non-english users this is a major annoyance. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Fix Released Status in ibus source package in Trusty: Triaged Bug description: [Impact] When first boot into Unity desktop, English keyboard layout is active while all other parts of the system language settings are set to another language (e.g. German). The bug is properly addressed in newer upstream releases in Vivid, but the changes is too intrusive and not suitable for being back ported in SRU. And changing the default to use system keyboard layout solves the problem. [Test Case] 1. Set the system language to something other than English, e.g. German. 2. Create a new user, log in to the Unity desktop of the new user. 3. Check the keyboard layout, it should be German instead of English. [Regression Potential] Since this changes the default value of the keyboard layout settings by using system defined as default, it avoids using ibus's built-in keyboard layout related functionality, so that this could be a regression for users rely on this certain behavior (e.g. use English keyboard while want to keep the system language settings to German), but such behavior is not expected for normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1498199] [NEW] Switching to fullscreen app causes unity freeze
Public bug reported: I'm reporting this for unity but it might just as well be compiz- related. Reproduce 1. Open fullscreen app (e.g. fullscreen HTML5 video, a game) 2. switch to another virtual desktop (i.e. using crtl+alt+arrow_keys) 3. switch back This started happening to me in 15.04. It does not happen all the time but can be reproduced by trying several times. If you need more info, let me know what and how to get it. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Sep 21 23:18:19 2015 InstallationDate: Installed on 2014-03-11 (559 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140302) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-05-20 (124 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Description changed: - Release: 15.04 - package: unity 7.3.2+15.04.20150420-0ubuntu1 - I'm reporting this for unity but it might just as well be compiz- related. Reproduce 1. Open fullscreen app (e.g. fullscreen HTML5 video, a game) 2. switch to another virtual desktop (i.e. using crtl+alt+arrow_keys) 3. switch back This started happening to me in 15.04. It does not happen all the time but can be reproduced by trying several times. If you need more info, let me know what and how to get it. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Sep 21 23:18:19 2015 InstallationDate: Installed on 2014-03-11 (559 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140302) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-05-20 (124 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1498199 Title: Switching to fullscreen app causes unity freeze Status in unity package in Ubuntu: New Bug description: I'm reporting this for unity but it might just as well be compiz- related. Reproduce 1. Open fullscreen app (e.g. fullscreen HTML5 video, a game) 2. switch to another virtual desktop (i.e. using crtl+alt+arrow_keys) 3. switch back This started happening to me in 15.04. It does not happen all the time but can be reproduced by trying several times. If you need more info, let me know what and how to get it. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Sep 21 23:18:19 2015 InstallationDate: Installed on 2014-03-11 (559 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140302) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-05-20 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1498199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1453336] Re: shotwell fails to import iphone photos
** Also affects: shotwell via https://bugzilla.gnome.org/show_bug.cgi?id=742295 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1453336 Title: shotwell fails to import iphone photos Status in Shotwell: Unknown Status in shotwell package in Ubuntu: Confirmed Bug description: Shotwell when view my photos on iPhone see double and fails to import. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: shotwell 0.20.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 8 21:26:59 2015 InstallationDate: Installed on 2015-05-08 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1453336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
@andrew Installing the package won't fix the bug for your current user. It will change the default for newly created users. If you want to fix it for your current user you just need to change the setting by hand by opening ibus-setup and checking the setting to Use system keyboard layout. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Fix Released Status in indicator-keyboard package in Ubuntu: Won't Fix Status in ibus source package in Trusty: Fix Committed Status in indicator-keyboard source package in Trusty: Won't Fix Bug description: [Impact] When first boot into Unity desktop, English keyboard layout is active while all other parts of the system language settings are set to another language (e.g. German). The bug is properly addressed in newer upstream releases in Vivid, but the changes is too intrusive and not suitable for being back ported in SRU. And changing the default to use system keyboard layout solves the problem. [Test Case] 1. Set the system language to something other than English, e.g. German. 2. Create a new user, log in to the Unity desktop of the new user. 3. Check the keyboard layout, it should be German instead of English. [Regression Potential] Since this changes the default value of the keyboard layout settings by using system defined as default, it avoids using ibus's built-in keyboard layout related functionality, so that this could be a regression for users rely on this certain behavior (e.g. use English keyboard while want to keep the system language settings to German), but such behavior is not expected for normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
@andrew-andrewr If you want to confirm whether the bug is fixed, create a new user and verify if the setting is checked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Fix Released Status in indicator-keyboard package in Ubuntu: Won't Fix Status in ibus source package in Trusty: Fix Committed Status in indicator-keyboard source package in Trusty: Won't Fix Bug description: [Impact] When first boot into Unity desktop, English keyboard layout is active while all other parts of the system language settings are set to another language (e.g. German). The bug is properly addressed in newer upstream releases in Vivid, but the changes is too intrusive and not suitable for being back ported in SRU. And changing the default to use system keyboard layout solves the problem. [Test Case] 1. Set the system language to something other than English, e.g. German. 2. Create a new user, log in to the Unity desktop of the new user. 3. Check the keyboard layout, it should be German instead of English. [Regression Potential] Since this changes the default value of the keyboard layout settings by using system defined as default, it avoids using ibus's built-in keyboard layout related functionality, so that this could be a regression for users rely on this certain behavior (e.g. use English keyboard while want to keep the system language settings to German), but such behavior is not expected for normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
I can definately verify (for at least 100 machines) that changing the settings DOES work. What I can't verify is that this patch modifies the default setting (or updates existing installations). If anyone can verify this, please do so. This is such an annoying bug that I need to fix on every single non-US Ubuntu installation by changing the ibus- setting -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Fix Released Status in indicator-keyboard package in Ubuntu: Won't Fix Status in ibus source package in Trusty: Fix Committed Status in indicator-keyboard source package in Trusty: Won't Fix Bug description: [Impact] When first boot into Unity desktop, English keyboard layout is active while all other parts of the system language settings are set to another language (e.g. German). The bug is properly addressed in newer upstream releases in Vivid, but the changes is too intrusive and not suitable for being back ported in SRU. And changing the default to use system keyboard layout solves the problem. [Test Case] 1. Set the system language to something other than English, e.g. German. 2. Create a new user, log in to the Unity desktop of the new user. 3. Check the keyboard layout, it should be German instead of English. [Regression Potential] Since this changes the default value of the keyboard layout settings by using system defined as default, it avoids using ibus's built-in keyboard layout related functionality, so that this could be a regression for users rely on this certain behavior (e.g. use English keyboard while want to keep the system language settings to German), but such behavior is not expected for normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 729979] Re: [nvidia] Windows appear blank white
So any chance this fix will also make it into newer versions of Ubuntu? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/729979 Title: [nvidia] Windows appear blank white Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in compiz package in Ubuntu: Fix Released Status in compiz source package in Precise: Confirmed Status in compiz source package in Trusty: Fix Committed Bug description: [ Impact ] When switching focus from one window to another, the target window may become blank. See the attached screenshot, where I opened two gnome- terminals and clicked on their titlebars alternately - the issue was triggered after about 5-10 clicks. I've had this happen on other appications too, e.g. software-centre, empathy, etc. HOW TO REPRODUCE: [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not reliably be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly. 1. Minimize a window 2. Initiate Scale and deactivate it again (press Super+W to show all windows and then press it again to go back to normal) 3. Click the window icon on the launcher to maximize it again. 4. The window contents will be white, black, or transparent depending on the Ubuntu version [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu Vivid Vervet dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 729979] Re: [nvidia] Windows appear blank white
@adconrad, is this in utopic-proposed, too? Judging by your link it doesn't look like it. The problem still exists in utopic (without proposed enabled). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/729979 Title: [nvidia] Windows appear blank white Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in compiz package in Ubuntu: Fix Released Status in compiz source package in Precise: Confirmed Status in compiz source package in Trusty: Fix Committed Bug description: [ Impact ] When switching focus from one window to another, the target window may become blank. See the attached screenshot, where I opened two gnome- terminals and clicked on their titlebars alternately - the issue was triggered after about 5-10 clicks. I've had this happen on other appications too, e.g. software-centre, empathy, etc. HOW TO REPRODUCE: [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not reliably be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly. 1. Minimize a window 2. Initiate Scale and deactivate it again (press Super+W to show all windows and then press it again to go back to normal) 3. Click the window icon on the launcher to maximize it again. 4. The window contents will be white, black, or transparent depending on the Ubuntu version [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu Vivid Vervet dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 729979] Re: [nvidia] Windows appear blank white
@adconrad, sorry for spamming. Just saw this fix is not in utopic- proposed. I've got no trusty on affected machines, sorry. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/729979 Title: [nvidia] Windows appear blank white Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in compiz package in Ubuntu: Fix Released Status in compiz source package in Precise: Confirmed Status in compiz source package in Trusty: Fix Committed Bug description: [ Impact ] When switching focus from one window to another, the target window may become blank. See the attached screenshot, where I opened two gnome- terminals and clicked on their titlebars alternately - the issue was triggered after about 5-10 clicks. I've had this happen on other appications too, e.g. software-centre, empathy, etc. HOW TO REPRODUCE: [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not reliably be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly. 1. Minimize a window 2. Initiate Scale and deactivate it again (press Super+W to show all windows and then press it again to go back to normal) 3. Click the window icon on the launcher to maximize it again. 4. The window contents will be white, black, or transparent depending on the Ubuntu version [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu Vivid Vervet dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1079731] Re: Minecraft can't go fullscreen
This was also fixed on minecraft side by automatically going fullscreen on start. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1079731 Title: Minecraft can't go fullscreen Status in Compiz: Invalid Status in compiz package in Ubuntu: Invalid Bug description: Hello , I got problems with minecraft after upgrade to 12.10 .Minecraft can't go to fullscreen .After pressing F11 i see black screen for 3 seconds and after that minecraft is in window again ( no errors in terminal ). It works in fluxbox and gnome3 without problems so i suspect this is compiz/nvidia related bug . I had this bug also in 12.04 after upgrade to nvidia 304.xx driver from stock 295.xx . Also tried upgrade to beta driver 310.14 but still the same issue . Additional info : minecraft is written in java, fresh installed 12.10 without any ccsm tweaks . Please let me know if you need additional info Thanks ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: compiz 1:0.9.8.4+bzr3407-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 310.14 Tue Oct 9 11:52:41 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Nov 16 16:02:37 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-experimental-310, 310.14, 3.5.0-18-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560] [10de:1201] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:3527] InstallationDate: Installed on 2012-11-13 (2 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=4a084bc7-c3db-4f85-9026-ba35d1a18f5e ro quiet splash SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77M-D3H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1079731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop
@jbelton1950: The problem occured when a default setting for ibus was changed. The fix just reverts the setting to the old default. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: Wrong keyboard layout active after booting into desktop Status in “ibus” package in Ubuntu: Confirmed Status in “indicator-keyboard” package in Ubuntu: Confirmed Bug description: I upgraded from raring to saucy. After booting into the desktop (unity), the english keyboard layout is active, although everything on the system is set to be german (keyboard layout, language...) Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and changes the layout to the german layout. all the time, the new input settings indicator says the german layout is active. locale says: LANG=de_DE.UTF-8 LANGUAGE=de_DE LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= /etc/default/keyboard says: # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL=pc105 XKBLAYOUT=de XKBVARIANT= XKBOPTIONS= # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:49:03 2013 InstallationDate: Installed on 2013-04-26 (171 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop
I proposed a fix for this bug for merging. Anything more I need to do? I haven't received a single comment on the merge proposal (which is 4weeks+ old now). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: Wrong keyboard layout active after booting into desktop Status in “ibus” package in Ubuntu: Confirmed Status in “indicator-keyboard” package in Ubuntu: Confirmed Bug description: I upgraded from raring to saucy. After booting into the desktop (unity), the english keyboard layout is active, although everything on the system is set to be german (keyboard layout, language...) Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and changes the layout to the german layout. all the time, the new input settings indicator says the german layout is active. locale says: LANG=de_DE.UTF-8 LANGUAGE=de_DE LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= /etc/default/keyboard says: # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL=pc105 XKBLAYOUT=de XKBVARIANT= XKBOPTIONS= # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:49:03 2013 InstallationDate: Installed on 2013-04-26 (171 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1246272] Re: Keyboard layout changing randomly
*** This bug is a duplicate of bug 1240198 *** https://bugs.launchpad.net/bugs/1240198 I can now confirm that this bug is fixed with the fix from #1240198. Marking this as a duplicate again. I will help on that building new packages. ** This bug has been marked a duplicate of bug 1240198 wrong keyboard layout active after booting into desktop, after upgrade to saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1246272 Title: Keyboard layout changing randomly Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps changing from pt_br to what I think is en_us. It seems random so I don't know what trigger this, but sometimes just alt-tabbing is enough to mess with keyboard layout in one of the windows. I already removed the en_us from my keyboard sources, double checked the use of one source for all windows, and even removed accelerators to switch between layouts but none have worked. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 30 09:12:48 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-05-20 (163 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: wrong keyboard layout active after booting into desktop, after upgrade to saucy
@hennekn I can confirm that changing the ibus-setting solves this for me, too. I'll help with builing a fixed package (got a little experience with that now). What exact package (and file) is responsible? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: wrong keyboard layout active after booting into desktop, after upgrade to saucy Status in “ibus” package in Ubuntu: Confirmed Status in “indicator-keyboard” package in Ubuntu: Confirmed Bug description: I upgraded from raring to saucy. After booting into the desktop (unity), the english keyboard layout is active, although everything on the system is set to be german (keyboard layout, language...) Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and changes the layout to the german layout. all the time, the new input settings indicator says the german layout is active. locale says: LANG=de_DE.UTF-8 LANGUAGE=de_DE LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= /etc/default/keyboard says: # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL=pc105 XKBLAYOUT=de XKBVARIANT= XKBOPTIONS= # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:49:03 2013 InstallationDate: Installed on 2013-04-26 (171 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: wrong keyboard layout active after booting into desktop, after upgrade to saucy
I just created a patched package (see linked branch above). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: wrong keyboard layout active after booting into desktop, after upgrade to saucy Status in “ibus” package in Ubuntu: Confirmed Status in “indicator-keyboard” package in Ubuntu: Confirmed Bug description: I upgraded from raring to saucy. After booting into the desktop (unity), the english keyboard layout is active, although everything on the system is set to be german (keyboard layout, language...) Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and changes the layout to the german layout. all the time, the new input settings indicator says the german layout is active. locale says: LANG=de_DE.UTF-8 LANGUAGE=de_DE LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= /etc/default/keyboard says: # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL=pc105 XKBLAYOUT=de XKBVARIANT= XKBOPTIONS= # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:49:03 2013 InstallationDate: Installed on 2013-04-26 (171 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1246272] Re: Keyboard layout changing randomly
I removed the duplicate status. The bugs might be related, but we don't know that. In the other report people have the problem after every reboot. In this bug it happens while being logged in. As the bug occurs randomly, I cannot yet confirm if the workaround from the other bug does it. If it helps: This problem was introduced with 13.10. ** This bug is no longer a duplicate of bug 1240198 wrong keyboard layout active after booting into desktop, after upgrade to saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1246272 Title: Keyboard layout changing randomly Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps changing from pt_br to what I think is en_us. It seems random so I don't know what trigger this, but sometimes just alt-tabbing is enough to mess with keyboard layout in one of the windows. I already removed the en_us from my keyboard sources, double checked the use of one source for all windows, and even removed accelerators to switch between layouts but none have worked. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 30 09:12:48 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-05-20 (163 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1246272] Re: Keyboard layout changing randomly
I have 100+ employees who have to reset the keyboard settings on a daily basis since the upgrade to 14.04. I'm pretty sure that for everyone who uses Ubuntu in a non-US corporate environment, this has highest priority. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1246272 Title: Keyboard layout changing randomly Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps changing from pt_br to what I think is en_us. It seems random so I don't know what trigger this, but sometimes just alt-tabbing is enough to mess with keyboard layout in one of the windows. I already removed the en_us from my keyboard sources, double checked the use of one source for all windows, and even removed accelerators to switch between layouts but none have worked. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 30 09:12:48 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-05-20 (163 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1246272] Re: Keyboard layout changing randomly
This also happens when there is only one keyboard layout installed. It still randomly switches to en_us. This shouldn't be classified as low importance since it is a major problem, especially in corporate environments. I have this happening on dozens of machines and have lots of annoyed users who have to use the workaround of switching layouts forth and back on a daily basis. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1246272 Title: Keyboard layout changing randomly Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps changing from pt_br to what I think is en_us. It seems random so I don't know what trigger this, but sometimes just alt-tabbing is enough to mess with keyboard layout in one of the windows. I already removed the en_us from my keyboard sources, double checked the use of one source for all windows, and even removed accelerators to switch between layouts but none have worked. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 30 09:12:48 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-05-20 (163 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1062186] Re: 'Backup Failed' message when external backup drive first inserted
I can confirm this problem still exists on a fresh install (not upgraded) of 14.04 with a freshly set up backup. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1062186 Title: 'Backup Failed' message when external backup drive first inserted Status in Déjà Dup Backup Tool: Confirmed Status in “deja-dup” package in Ubuntu: Confirmed Status in “deja-dup” package in Fedora: Unknown Bug description: An error message entitled 'Backup Failed' with the text 'An operation is already pending' is displayed when I first plug in by external backup drive and Deja Dup attempts to perform a scheduled backup, although it succeeds on subsequent attempts (either scheduled or manual). The fstab entry for the drive is as follows: /dev/disk/by-uuid/1a1374a1-4bb9-4416-b21c-9350e57b70f1 /media/thomas/Tom\040WD\040HD auto nosuid,nodev,nofail,noauto,compress=lzo,space_cache,uhelper=udisk 0 0 I presume this is either due to both Gnome and Deja Dup attempting to mount the drive, or Deja Dup not waiting until the drive has been successfully mounted. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: deja-dup 24.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Fri Oct 5 11:45:05 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha amd64(20120913) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1062186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1207812] Re: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping
Please stop it. This is not a discussion forum or a support site. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping Status in The Linux Mint Distribution: Confirmed Status in “libimobiledevice” package in Ubuntu: Fix Released Status in “libimobiledevice” package in Debian: Confirmed Bug description: The latest libimobiledevice release 1.1.5 is a year old and does not support iOS7 devices. Most iOS devices have been updated to iOS7 by now, so currently the library is broken in functionality for most users. The git snapshot has been tested to work, but there seems to be no new upstream release being prepared for the time being. The new git snapshot includes several fixes, including the security fix that was previously patched on top of 1.1.5 in Ubuntu. Packaging branch merge request attached to this bug report. --- Original report --- The iPhone reporting Trust the currently connected computer? Trust/Don't Trust. This then happens in a continous loop when clicking Trust. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1207812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1207812] Re: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping
This place is solely for reporting bugs and for developers to coordinate fixing them. You make the lives of developers harder. This place is not for support. Period. This bug was fixed and you people start an unrelated discussion about Linux Mint here. Every single one of your messages spams the inboxes of all the people listed on the right. Don't bother to reply, I'm unsubscribing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping Status in The Linux Mint Distribution: Confirmed Status in “libimobiledevice” package in Ubuntu: Fix Released Status in “libimobiledevice” package in Debian: Confirmed Bug description: The latest libimobiledevice release 1.1.5 is a year old and does not support iOS7 devices. Most iOS devices have been updated to iOS7 by now, so currently the library is broken in functionality for most users. The git snapshot has been tested to work, but there seems to be no new upstream release being prepared for the time being. The new git snapshot includes several fixes, including the security fix that was previously patched on top of 1.1.5 in Ubuntu. Packaging branch merge request attached to this bug report. --- Original report --- The iPhone reporting Trust the currently connected computer? Trust/Don't Trust. This then happens in a continous loop when clicking Trust. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1207812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 729979] Re: [nvidia] Windows appear blank white
I don't know how to do it but can someone also retarget this to trusty? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/729979 Title: [nvidia] Windows appear blank white Status in Compiz: Triaged Status in Compiz Core: Triaged Status in “compiz” package in Ubuntu: Triaged Status in “compiz” source package in Precise: Confirmed Bug description: Binary package hint: compiz When switching focus from one window to another, the target window may become blank. See the attached screenshot, where I opened two gnome- terminals and clicked on their titlebars alternately - the issue was triggered after about 5-10 clicks. I've had this happen on other appications too, e.g. software-centre, empathy, etc. HOW TO REPRODUCE: 1. Minimize a window 2. Initiate Scale and deactivate it again (press Super+W to show all windows and then press it again to go back to normal) 3. Click the window icon on the launcher to maximize it again. 4. The window contents will be white or black depending on the Ubuntu version WORKAROUND: Uncheck CCSM - Ubuntu Unity Plugin - Switcher - Show live previews of windows in the Switcher. Side-effect: scale doesn't show minimized windows. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1207812] Re: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping
libimobiledevice 1.1.6 has been officially released. There have been a lot of changes according to the NEWS file. I case this is too late for a FFe this should still be added later through trusty-updates. There are many bugfixes in this release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping Status in “libimobiledevice” package in Ubuntu: Fix Released Bug description: The latest libimobiledevice release 1.1.5 is a year old and does not support iOS7 devices. Most iOS devices have been updated to iOS7 by now, so currently the library is broken in functionality for most users. The git snapshot has been tested to work, but there seems to be no new upstream release being prepared for the time being. The new git snapshot includes several fixes, including the security fix that was previously patched on top of 1.1.5 in Ubuntu. Packaging branch merge request attached to this bug report. --- Original report --- The iPhone reporting Trust the currently connected computer? Trust/Don't Trust. This then happens in a continous loop when clicking Trust. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1207812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295797] Re: No language chooser on login screen in LightDM
@Gunnar: So by default Ubuntu does not have a language chooser? I can live with just installing lightdm-gtk-greeter, but the behavior is quite odd. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1295797 Title: No language chooser on login screen in LightDM Status in “unity-greeter” package in Ubuntu: Confirmed Bug description: There is no option to choose the language at login. I'm reporting this as a new bug (instead of LP: 803858) because this is specifically a regression in trusty. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.12-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 21 19:44:28 2014 InstallationDate: Installed on 2014-03-11 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20140302) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1295797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292262] Re: Subtitle Downloader does not open
The bug has been fixed upstream. I created a branch with a fix, can confirm that it works and proposed it for merging. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1292262 Title: Subtitle Downloader does not open Status in One Hundred Papercuts: Triaged Status in Totem Movie Player: Incomplete Status in “totem” package in Ubuntu: Triaged Bug description: In Totem 3.10.1 the subtitle downloader does not open. The terminal shows this message: Traceback (most recent call last): File /usr/lib/totem/plugins/opensubtitles/opensubtitles.py, line 516, in _show_dialog self._build_dialog () File /usr/lib/totem/plugins/opensubtitles/opensubtitles.py, line 441, in _build_dialog self) ValueError: Pointer arguments are restricted to integers, capsules, and None. See: https://bugzilla.gnome.org/show_bug.cgi?id=683599 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: totem-plugins 3.10.1-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 00:06:03 2014 InstallationDate: Installed on 2014-03-11 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20140302) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1292262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 729979] Re: [nvidia] Windows appear blank white
Can we please re-open this bug? There is no released fix that ever worked for me. I'm on 14.04 development, fresh install and I still experience this bug following the original steps to reproduce: - minimize window - show scale (super+w) - hide scale (super+w) - click on window in launcher - black empty window. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/729979 Title: [nvidia] Windows appear blank white Status in Compiz: Triaged Status in Compiz Core: Triaged Status in “compiz” package in Ubuntu: Fix Released Bug description: Binary package hint: compiz When switching focus from one window to another, the target window may become blank. See the attached screenshot, where I opened two gnome- terminals and clicked on their titlebars alternately - the issue was triggered after about 5-10 clicks. I've had this happen on other appications too, e.g. software-centre, empathy, etc. HOW TO REPRODUCE: 1. Minimize a window 2. Initiate Scale and deactivate it again (press Super+W to show all windows and then press it again to go back to normal) 3. Click the window icon on the launcher to maximize it again. 4. The window contents will be white or black depending on the Ubuntu version WORKAROUND: Uncheck CCSM - Ubuntu Unity Plugin - Switcher - Show live previews of windows in the Switcher. Side-effect: scale doesn't show minimized windows. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295797] [NEW] No language chooser on login screen in LightDM
Public bug reported: There is no option to choose the language at login. I'm reporting this as a new bug (instead of LP: 803858) because this is specifically a regression in trusty. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.12-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 21 19:44:28 2014 InstallationDate: Installed on 2014-03-11 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20140302) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1295797 Title: No language chooser on login screen in LightDM Status in “lightdm” package in Ubuntu: New Bug description: There is no option to choose the language at login. I'm reporting this as a new bug (instead of LP: 803858) because this is specifically a regression in trusty. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.12-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 21 19:44:28 2014 InstallationDate: Installed on 2014-03-11 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20140302) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1295797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1207812] Re: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping
@laney: What do you mean by subscribe to the reverse deps? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping Status in “libimobiledevice” package in Ubuntu: Fix Released Bug description: The latest libimobiledevice release 1.1.5 is a year old and does not support iOS7 devices. Most iOS devices have been updated to iOS7 by now, so currently the library is broken in functionality for most users. The git snapshot has been tested to work, but there seems to be no new upstream release being prepared for the time being. The new git snapshot includes several fixes, including the security fix that was previously patched on top of 1.1.5 in Ubuntu. Packaging branch merge request attached to this bug report. --- Original report --- The iPhone reporting Trust the currently connected computer? Trust/Don't Trust. This then happens in a continous loop when clicking Trust. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1207812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1207812] Re: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping
@Sourav Sur, the new Packages are for Ubuntu 14.04 only! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping Status in “libimobiledevice” package in Ubuntu: Triaged Bug description: The latest libimobiledevice release 1.1.5 is a year old and does not support iOS7 devices. Most iOS devices have been updated to iOS7 by now, so currently the library is broken in functionality for most users. The git snapshot has been tested to work, but there seems to be no new upstream release being prepared for the time being. The new git snapshot includes several fixes, including the security fix that was previously patched on top of 1.1.5 in Ubuntu. Packaging branch merge request attached to this bug report. --- Original report --- The iPhone reporting Trust the currently connected computer? Trust/Don't Trust. This then happens in a continous loop when clicking Trust. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1207812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1207812] Re: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping
There are three more confirmations that the packages work on reddit. Those people unfortunately don't seem to have launchpad accounts: http://www.reddit.com/r/Ubuntu/comments/20bndd/need_testing_help_to_land_ios7_fix_in_ubuntu_1404/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping Status in “libimobiledevice” package in Ubuntu: Triaged Bug description: The latest libimobiledevice release 1.1.5 is a year old and does not support iOS7 devices. Most iOS devices have been updated to iOS7 by now, so currently the library is broken in functionality for most users. The git snapshot has been tested to work, but there seems to be no new upstream release being prepared for the time being. The new git snapshot includes several fixes, including the security fix that was previously patched on top of 1.1.5 in Ubuntu. Packaging branch merge request attached to this bug report. --- Original report --- The iPhone reporting Trust the currently connected computer? Trust/Don't Trust. This then happens in a continous loop when clicking Trust. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1207812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1207812] Re: iOS 7, Trust Prompt Looping
@Timo: I can confirm that it works. Tested on an existing machine and a fresh install. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: iOS 7, Trust Prompt Looping Status in “libimobiledevice” package in Ubuntu: Confirmed Bug description: The iPhone reporting Trust the currently connected computer? Trust/Don't Trust. This then happens in a continous loop when clicking Trust. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1207812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1207812] Re: iOS 7, Trust Prompt Looping
I can also confirm that devices with older iOS versions (tested a 3GS with 6.1.3) still work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: iOS 7, Trust Prompt Looping Status in “libimobiledevice” package in Ubuntu: Confirmed Bug description: The iPhone reporting Trust the currently connected computer? Trust/Don't Trust. This then happens in a continous loop when clicking Trust. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1207812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292262] [NEW] Subtitle Downloader does not open
Public bug reported: In Totem 3.10.1 the subtitle downloader does not open. The terminal shows this message: Traceback (most recent call last): File /usr/lib/totem/plugins/opensubtitles/opensubtitles.py, line 516, in _show_dialog self._build_dialog () File /usr/lib/totem/plugins/opensubtitles/opensubtitles.py, line 441, in _build_dialog self) ValueError: Pointer arguments are restricted to integers, capsules, and None. See: https://bugzilla.gnome.org/show_bug.cgi?id=683599 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: totem-plugins 3.10.1-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 00:06:03 2014 InstallationDate: Installed on 2014-03-11 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20140302) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: totem Importance: Unknown Status: Unknown ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Bug watch added: GNOME Bug Tracker #724093 https://bugzilla.gnome.org/show_bug.cgi?id=724093 ** Also affects: totem via https://bugzilla.gnome.org/show_bug.cgi?id=724093 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1292262 Title: Subtitle Downloader does not open Status in Totem Movie Player: Unknown Status in “totem” package in Ubuntu: New Bug description: In Totem 3.10.1 the subtitle downloader does not open. The terminal shows this message: Traceback (most recent call last): File /usr/lib/totem/plugins/opensubtitles/opensubtitles.py, line 516, in _show_dialog self._build_dialog () File /usr/lib/totem/plugins/opensubtitles/opensubtitles.py, line 441, in _build_dialog self) ValueError: Pointer arguments are restricted to integers, capsules, and None. See: https://bugzilla.gnome.org/show_bug.cgi?id=683599 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: totem-plugins 3.10.1-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 00:06:03 2014 InstallationDate: Installed on 2014-03-11 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20140302) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1292262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1207812] Re: iOS 7, Trust Prompt Looping
I made packages from the current git master that work in trusty. https://launchpad.net/~mniess/+archive/libimobiledevice/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: iOS 7, Trust Prompt Looping Status in “libimobiledevice” package in Ubuntu: Triaged Bug description: The iPhone reporting Trust the currently connected computer? Trust/Don't Trust. This then happens in a continous loop when clicking Trust. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1207812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1207812] Re: iOS 7, Trust Prompt Looping
My packages are probably not up to standards. But for hardware- enablement alone this should be fixed in trusty. There won't be a release of libimobiledevice anytime soon that fixes this and the current version cannot be fixed with a trivial patch. So the only solution would be using a package build from git master. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: iOS 7, Trust Prompt Looping Status in “libimobiledevice” package in Ubuntu: Triaged Bug description: The iPhone reporting Trust the currently connected computer? Trust/Don't Trust. This then happens in a continous loop when clicking Trust. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1207812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 792085] Re: Automatic remount of safely removed drive
This problem is still present in 13.10 and trusty. As long as you use the affected nvidia chipset on the motherboard. I upgraded the computer I have with this motherboard just to see if the bug is still there. I won't be upgrading it anymore. So I can't give any more feedback and hereby unsubscribe from this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/792085 Title: Automatic remount of safely removed drive Status in “nautilus” package in Ubuntu: Confirmed Status in “udev” package in Ubuntu: Confirmed Bug description: Binary package hint: nautilus When I choose Safely remove drive context menu entry for an external USB drive within a nautilus window or directly clicking on the desktop icon, after about 10 seconds the drive is automatically remounted and a Nautilus window showing the root folder opens. I have noticed that similar already happened with a very old Ubuntu version - Bug #110589 and as that is so long time ago I thought it is better to open a new bug. Reason of the problem might even be completely different. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 Date: Thu Jun 2 23:40:08 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1236601] Re: wrong background color when editing icons on desktop
I can also confirm that this is fixed. Thanks for backporting the upstream fix to 3.8! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1236601 Title: wrong background color when editing icons on desktop Status in Nautilus: Fix Released Status in “nautilus” package in Ubuntu: Fix Released Status in “nautilus” source package in Saucy: Fix Committed Bug description: * Impact: renaming icons on the desktop has text contrast issues * Test case: rename an icon on the desktop, move the cursor, see if there is a white background color making the text easy to read or not * Regression potential: check that the rename UI looks as it should - When creating or renaming an icon on the desktop, nautilus no longers colors the background ellipse white, resulting in text being unreadable. See attached screenshot for comparison between Raring and Saucy. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Oct 7 17:24:39 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1004x670+867+75' InstallationDate: Installed on 2012-11-13 (328 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-08-19 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1236601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1236601] Re: wrong background color when editing icons on desktop
Any chance for a backport to saucy? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1236601 Title: wrong background color when editing icons on desktop Status in Nautilus: Fix Released Status in “nautilus” package in Ubuntu: Fix Released Status in “nautilus” source package in Saucy: In Progress Bug description: * Impact: renaming icons on the desktop has text contrast issues * Test case: rename an icon on the desktop, move the cursor, see if there is a white background color making the text easy to read or not * Regression potential: check that the rename UI looks as it should - When creating or renaming an icon on the desktop, nautilus no longers colors the background ellipse white, resulting in text being unreadable. See attached screenshot for comparison between Raring and Saucy. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Oct 7 17:24:39 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1004x670+867+75' InstallationDate: Installed on 2012-11-13 (328 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-08-19 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1236601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1236601] Re: wrong background color when editing icons on desktop
So as far as I can see this only happens when renaming files on the Desktop. As files on the Desktop are not supported anymore by Gnome, this is probably a wontfix from their perspective. Just saying we shouldn't expect much help from upstream with this if I'm not totally wrong. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1236601 Title: wrong background color when editing icons on desktop Status in Nautilus: Unknown Status in “nautilus” package in Ubuntu: Triaged Status in “nautilus” source package in Saucy: Triaged Bug description: When creating or renaming an icon on the desktop, nautilus no longers colors the background ellipse white, resulting in text being unreadable. See attached screenshot for comparison between Raring and Saucy. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Oct 7 17:24:39 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1004x670+867+75' InstallationDate: Installed on 2012-11-13 (328 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-08-19 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1236601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1235785] Re: Light Display Manager is offered as login option
I can confirm this bug is gone with todays round of updates. I don't know which one caused the fix but I'll attach a list of the updated packages and their versions. ** Attachment added: updated_packages.png https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1235785/+attachment/3884871/+files/updated_packages.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1235785 Title: Light Display Manager is offered as login option Status in “unity-greeter” package in Ubuntu: Confirmed Bug description: Test case: Fresh install of current image (10/05 here Log in to guest account, log out Light Display Manager is now a login option ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-greeter 13.10.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sat Oct 5 17:10:44 2013 InstallationDate: Installed on 2013-10-05 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131005) MarkForUpload: True SourcePackage: unity-greeter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1235785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
I still get the feeling that you don't see the seriousness of this bug. Any drive-by browser-exploit can now escalate to root privileges because of this. Most Ubuntu users are running it with their admin account (that has sudo privileges). Running the wrong script or visiting the wrong website will be enough. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. Status in Cinnamon: New Status in sudo: Unknown Status in Unity: Invalid Status in “gnome-control-center” package in Ubuntu: Opinion Bug description: Under unity and cinnamon, it is possible for a user to turn off network-syncronized time and then change the time on the system. It is also possible to cat /var/log/auth.log and find the last time a user authenticated with sudo, along with which pty they used. If a user had used a terminal and successfully authenticated with sudo anytime in the past, and left the sudo file in /var/lib/sudo/username/, a malicious user could walk up to an unlocked, logged in machine and gain sudo without knowing the password for the computer. To do this, a user would only need to launch a few terminals, figure out which pty they were on via tty, find the an instance in /var/log/auth.log where sudo was used on that PTY, and set the clock to that time. Once this is done, they can run (for example) sudo -s and have a full access terminal. 1) This has been observed on Ubuntu 13.04, and may work on other versions. 2) This may have an effect on various window managers, but I confirmed it on Unity and Cinnamon 3) I expected to have to authenticate when I changed the time and date, as I do on Gnome and KDE. I also expected to be denied permission to auth.log 4) I was able to change the system time to whatever I wanted, and view auth.log. This was sufficient to access sudo without having to type my password. Note: This bug also affects any version of OS X, though the mechanism is different. Some versions don't require you to authenticate to change the time through the GUI, but some do. No version I've seen requires authentication to use the systemsetup command, which can alter the time from the command line. This may be an overall bug in sudo. Why can I bypass security by changing the time?! To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
To clarify: an exploit could run code in a terminal, get the TTY of that terminal and search auth.log for that TTY to change the time, right? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. Status in Cinnamon: New Status in sudo: Unknown Status in Unity: Invalid Status in “gnome-control-center” package in Ubuntu: Opinion Bug description: Under unity and cinnamon, it is possible for a user to turn off network-syncronized time and then change the time on the system. It is also possible to cat /var/log/auth.log and find the last time a user authenticated with sudo, along with which pty they used. If a user had used a terminal and successfully authenticated with sudo anytime in the past, and left the sudo file in /var/lib/sudo/username/, a malicious user could walk up to an unlocked, logged in machine and gain sudo without knowing the password for the computer. To do this, a user would only need to launch a few terminals, figure out which pty they were on via tty, find the an instance in /var/log/auth.log where sudo was used on that PTY, and set the clock to that time. Once this is done, they can run (for example) sudo -s and have a full access terminal. 1) This has been observed on Ubuntu 13.04, and may work on other versions. 2) This may have an effect on various window managers, but I confirmed it on Unity and Cinnamon 3) I expected to have to authenticate when I changed the time and date, as I do on Gnome and KDE. I also expected to be denied permission to auth.log 4) I was able to change the system time to whatever I wanted, and view auth.log. This was sufficient to access sudo without having to type my password. Note: This bug also affects any version of OS X, though the mechanism is different. Some versions don't require you to authenticate to change the time through the GUI, but some do. No version I've seen requires authentication to use the systemsetup command, which can alter the time from the command line. This may be an overall bug in sudo. Why can I bypass security by changing the time?! To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-desktop/+bug/1219337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 972554] Re: [soundnua]: new capplet does not expose all profiles (Emu 0404 USB)
Hi. Calling in from 2013. This problem still exists in raring and saucy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/972554 Title: [soundnua]: new capplet does not expose all profiles (Emu 0404 USB) Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: With Ubuntu 12.04, the Sound menu allows to select various profiles for each sound cards via drop down list in the Hardware tab. I couldn't find this feature in the latest daily-live image of Ubuntu 12.04 (from April 1st). I'd appreciate if someone would kindly point me where to change this ? Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/972554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1062186] Re: 'Backup Failed' message when external backup drive first inserted
I added deja-dup to the bug-report so that this appears in *their* bugtracker and not the ubuntu-packages. I'm sure this is a race condition. I get the error when I plug in my slow external HDD. Leaving it plugged in I trigger the backups again by pluggin in another USB device. As the backup-drive is already mounted there is no race-condition and the backup works. ** Also affects: deja-dup Importance: Undecided Status: New ** Changed in: deja-dup Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1062186 Title: 'Backup Failed' message when external backup drive first inserted Status in Déjà Dup Backup Tool: Confirmed Status in “deja-dup” package in Ubuntu: Confirmed Bug description: An error message entitled 'Backup Failed' with the text 'An operation is already pending' is displayed when I first plug in by external backup drive and Deja Dup attempts to perform a scheduled backup, although it succeeds on subsequent attempts (either scheduled or manual). The fstab entry for the drive is as follows: /dev/disk/by-uuid/1a1374a1-4bb9-4416-b21c-9350e57b70f1 /media/thomas/Tom\040WD\040HD auto nosuid,nodev,nofail,noauto,compress=lzo,space_cache,uhelper=udisk 0 0 I presume this is either due to both Gnome and Deja Dup attempting to mount the drive, or Deja Dup not waiting until the drive has been successfully mounted. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: deja-dup 24.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Fri Oct 5 11:45:05 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha amd64(20120913) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1062186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1062186] Re: 'Backup Failed' message when external backup drive first inserted
This is the exact error I get. How can we get more detailed information to post here? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1062186 Title: 'Backup Failed' message when external backup drive first inserted Status in “deja-dup” package in Ubuntu: Confirmed Bug description: An error message entitled 'Backup Failed' with the text 'An operation is already pending' is displayed when I first plug in by external backup drive and Deja Dup attempts to perform a scheduled backup, although it succeeds on subsequent attempts (either scheduled or manual). The fstab entry for the drive is as follows: /dev/disk/by-uuid/1a1374a1-4bb9-4416-b21c-9350e57b70f1 /media/thomas/Tom\040WD\040HD auto nosuid,nodev,nofail,noauto,compress=lzo,space_cache,uhelper=udisk 0 0 I presume this is either due to both Gnome and Deja Dup attempting to mount the drive, or Deja Dup not waiting until the drive has been successfully mounted. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: deja-dup 24.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Fri Oct 5 11:45:05 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha amd64(20120913) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1062186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 743541] Re: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_build_variant()
The project is dead and bugs won't be fixed. If you check the project page the developer states this there. Sorry. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-weather in Ubuntu. https://bugs.launchpad.net/bugs/743541 Title: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_build_variant() Status in DBus Menu: Incomplete Status in Indicator-Weather: Confirmed Status in “indicator-weather” package in Ubuntu: Confirmed Bug description: Binary package hint: indicator-weather This crash just appear. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: indicator-weather 11.03.20+repack-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 NonfreeKernelModules: nvidia Architecture: i386 CrashCounter: 1 Date: Sun Mar 27 13:45:25 2011 ExecutablePath: /usr/bin/indicator-weather InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110302) InterpreterPath: /usr/bin/python2.7 ProcCmdline: /usr/bin/python /usr/bin/indicator-weather ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xd69bb9 dbusmenu_menuitem_build_variant+409: mov(%esi),%eax PC (0x00d69bb9) ok source (%esi) (0x0234) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-weather StacktraceTop: dbusmenu_menuitem_build_variant () from /usr/lib/libdbusmenu-glib.so.3 ?? () from /usr/lib/libdbusmenu-glib.so.3 ?? () from /usr/lib/libdbusmenu-glib.so.3 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_build_variant() UpgradeStatus: Upgraded to natty on 2011-03-25 (2 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/743541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1062186] Re: 'Backup Failed' message when external backup drive first inserted
This bug appeared for me every since I upgraded to quantal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1062186 Title: 'Backup Failed' message when external backup drive first inserted Status in “deja-dup” package in Ubuntu: Confirmed Bug description: An error message entitled 'Backup Failed' with the text 'An operation is already pending' is displayed when I first plug in by external backup drive and Deja Dup attempts to perform a scheduled backup, although it succeeds on subsequent attempts (either scheduled or manual). The fstab entry for the drive is as follows: /dev/disk/by-uuid/1a1374a1-4bb9-4416-b21c-9350e57b70f1 /media/thomas/Tom\040WD\040HD auto nosuid,nodev,nofail,noauto,compress=lzo,space_cache,uhelper=udisk 0 0 I presume this is either due to both Gnome and Deja Dup attempting to mount the drive, or Deja Dup not waiting until the drive has been successfully mounted. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: deja-dup 24.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Fri Oct 5 11:45:05 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha amd64(20120913) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1062186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1062186] Re: 'Backup Failed' message when external backup drive first inserted
@Tom are you sure this is another bug and not the same as #617012? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1062186 Title: 'Backup Failed' message when external backup drive first inserted Status in “deja-dup” package in Ubuntu: Confirmed Bug description: An error message entitled 'Backup Failed' with the text 'An operation is already pending' is displayed when I first plug in by external backup drive and Deja Dup attempts to perform a scheduled backup, although it succeeds on subsequent attempts (either scheduled or manual). The fstab entry for the drive is as follows: /dev/disk/by-uuid/1a1374a1-4bb9-4416-b21c-9350e57b70f1 /media/thomas/Tom\040WD\040HD auto nosuid,nodev,nofail,noauto,compress=lzo,space_cache,uhelper=udisk 0 0 I presume this is either due to both Gnome and Deja Dup attempting to mount the drive, or Deja Dup not waiting until the drive has been successfully mounted. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: deja-dup 24.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Fri Oct 5 11:45:05 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha amd64(20120913) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1062186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1080082] Re: Lightdm killed during boot (kills itself?)
*** This bug is a duplicate of bug 969489 *** https://bugs.launchpad.net/bugs/969489 ** This bug has been marked a duplicate of bug 969489 lightdm tries (and fails) to start too early? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1080082 Title: Lightdm killed during boot (kills itself?) Status in Light Display Manager: New Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: I'm running 12.10, and since installing the stable release in October I didn't install any upgrades. This week, after installing the latest upgrades, lightdm stopped working: the Xserver starts, and dies immediately, leaving me on a tty7 with remains of log messages. If I log in and manually restart lightdm, it works. I think I am not alone in this, as a user had reported exactly the same back in July in the xubuntu-users mailing list: https://lists.ubuntu.com/archives/xubuntu-users/2012-July/004252.html I've done some tests and: - If I disable plymouth (by removing splash from GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub) the bug goes away - If I press 'esc' to exit plymouth before lightdm triess to start the bug also goes away Looking at the lightdm log, it seems that it decides to kill itself: ... [+1.22s] DEBUG: Starting Light Display Manager 1.4.0, UID=0 PID=1138 (notice the pid) ... [+5.59s] DEBUG: New display ready, switching to it [+5.59s] DEBUG: Activating VT 7 [+6.53s] DEBUG: Greeter start authentication for knuckles [+6.54s] DEBUG: Started session 1862 with service 'lightdm', username 'knuckles' [+6.54s] DEBUG: Greeter start authentication for knuckles [+6.54s] DEBUG: Session 1862: Sending SIGTERM [+6.54s] DEBUG: Started session 1863 with service 'lightdm', username 'knuckles' [+6.54s] DEBUG: Got signal 15 from process 1138 (signal to die received from itself!!) [+6.54s] DEBUG: Caught Terminated signal, shutting down ... This is what leads me to believe that the bug is in lightdm. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Nov 17 14:06:16 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: fglrx-updates, 9.000, 3.5.0-18-generic, x86_64: installed fglrx-updates, 9.000, 3.5.0-19-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:397b] InstallationDate: Installed on 2012-10-21 (26 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: LENOVO 10382JG MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.5.0-19-generic root=UUID=9a791902-1e8f-4073-b59c-de19842fdff8 ro rootflags=subvol=@ crashkernel=384M-2G:64M,2G-:128M quiet SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 4BCN24WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: 109-B78210-00A dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version Unknown dmi.modalias: dmi:bvnLENOVO:bvr4BCN24WW:bd08/10/2011:svnLENOVO:pn10382JG:pvrIdeapadS205:rvnLENOVO:rnInagua:rvr109-B78210-00A:cvnLENOVO:ct10:cvrChassisVersionUnknown: dmi.product.name: 10382JG dmi.product.version: Ideapad S205 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1080082/+subscriptions --
[Desktop-packages] [Bug 416825] Re: gnome-keyring passwd should be changed on system password change
I can at least confirm the problem doesn't exist in 12.10 anymore. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/416825 Title: gnome-keyring passwd should be changed on system password change Status in GNOME Control Center: Fix Released Status in GNOME keyring services: Invalid Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Precise: Fix Committed Status in Baltix GNU/Linux: New Bug description: Impact: Leads to have login and desktop passwords out of sync which triggers confusing password prompts for users (need to enter their old login password) Test Case: 1. Install a fresh Ubuntu 2. Log in and connect to a password protected WLAN (and thus save a password in the Gnome keyring) 3. Log in again and change the password of the user using System User info Change password 4. Log in again. Now the Gnome keyring complains that it was unable to open. The computer is not connected to the protected WLAN and the user is asked both the Gnome keyring password and the WLAN password. Regression potention: Check that the keyring password is correctly updated Better description and fresh follow-up in report https://bugs.launchpad.net/ubuntu/precise/+source/gnome-control- center/+bug/911426 Original description: The default Gnome keyring manger in Ubuntu 9.04 (Seahorse 26.6.1?) asks the user to unlock his/her keyring in order to save the Ubuntu One token _if_ the user has changed his/her password after initial installation/login of Ubuntu 9.04. The actual problem seems to be that the default password for the keyring is initially and automatically set to the same password the user uses to log in into Ubuntu (GDM). The user does not know anything about the keyring, because it works automatically (and that's fine). However if the user ever changes his/her password for Ubuntu (Linux username) the password protecting the keyring is not changed. So later if the user needs to unlock the keyring, he/she needs to rembember what was his/her password when he/she started using Ubuntu in the beginning. The solution would be to set some kind of flag in the Gnome keyring (Sea Horse?) that the password has been taken automatically from the username/login. So if ever the user does change his username/login password, the Gnome keyring would know to automatically also change the password that protects the keyring. This bug does not effect new users of Ubuntu, but most likely everybody who has been using Ubuntu for a longer time (and thus has changed their login password at some time, which brakes the keyring automatics). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/416825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 416825] Re: gnome-keyring passwd should be changed on system password change
I don't have a machine with precise available at the moment. Anyone with precise can confirm the issue by using the testcase. Just change the password using the GUI tools and you won't have access to the Gnome keyring. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/416825 Title: gnome-keyring passwd should be changed on system password change Status in GNOME Control Center: Fix Released Status in GNOME keyring services: Invalid Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Precise: Fix Committed Status in Baltix GNU/Linux: New Bug description: Impact: Leads to have login and desktop passwords out of sync which triggers confusing password prompts for users (need to enter their old login password) Test Case: 1. Install a fresh Ubuntu 2. Log in and connect to a password protected WLAN (and thus save a password in the Gnome keyring) 3. Log in again and change the password of the user using System User info Change password 4. Log in again. Now the Gnome keyring complains that it was unable to open. The computer is not connected to the protected WLAN and the user is asked both the Gnome keyring password and the WLAN password. Regression potention: Check that the keyring password is correctly updated Better description and fresh follow-up in report https://bugs.launchpad.net/ubuntu/precise/+source/gnome-control- center/+bug/911426 Original description: The default Gnome keyring manger in Ubuntu 9.04 (Seahorse 26.6.1?) asks the user to unlock his/her keyring in order to save the Ubuntu One token _if_ the user has changed his/her password after initial installation/login of Ubuntu 9.04. The actual problem seems to be that the default password for the keyring is initially and automatically set to the same password the user uses to log in into Ubuntu (GDM). The user does not know anything about the keyring, because it works automatically (and that's fine). However if the user ever changes his/her password for Ubuntu (Linux username) the password protecting the keyring is not changed. So later if the user needs to unlock the keyring, he/she needs to rembember what was his/her password when he/she started using Ubuntu in the beginning. The solution would be to set some kind of flag in the Gnome keyring (Sea Horse?) that the password has been taken automatically from the username/login. So if ever the user does change his username/login password, the Gnome keyring would know to automatically also change the password that protects the keyring. This bug does not effect new users of Ubuntu, but most likely everybody who has been using Ubuntu for a longer time (and thus has changed their login password at some time, which brakes the keyring automatics). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/416825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1079196] [NEW] When selected partition is not focused, it becomes invisible.
Public bug reported: When selected partitions are out of focus, the text-color seems to be white and the out-of-focus selection-color seems to be white, too (instead of, say, gray). I attached a screencast to demonstrate the problem. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-disk-utility 3.6.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Thu Nov 15 14:40:17 2012 InstallationDate: Installed on 2012-09-16 (59 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to quantal on 2012-11-06 (8 days ago) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity ** Attachment added: 52.mp4 https://bugs.launchpad.net/bugs/1079196/+attachment/3434351/+files/52.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1079196 Title: When selected partition is not focused, it becomes invisible. Status in “gnome-disk-utility” package in Ubuntu: New Bug description: When selected partitions are out of focus, the text-color seems to be white and the out-of-focus selection-color seems to be white, too (instead of, say, gray). I attached a screencast to demonstrate the problem. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-disk-utility 3.6.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Thu Nov 15 14:40:17 2012 InstallationDate: Installed on 2012-09-16 (59 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to quantal on 2012-11-06 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1079196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1077621] Re: Privacy settings in gnome-control-center should be password protected
I concur. Shouldn't be too hard to protect with policykit, right? The same actually goes for the backup-settings, I'd say. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1077621 Title: Privacy settings in gnome-control-center should be password protected Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Currently, the privacy settings are not secured properly and allows driveby users to get a glimpse of the user's privacy settings. To make my point, if someone manages to view the list of folders that a user doesn't want Zeitgeist to log, he would be able to find the exact folders that the user does not want others to get an easy access. Hence, I suggest the privacy settings are locked by default similar to how the User Accounts work and the settings are only accessible if the user inputs the password. This would provide added security to the user's privacy settings. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu19 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 11 20:34:04 2012 InstallationDate: Installed on 2012-11-10 (0 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-11-11 (0 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu4 deja-dup24.0-0ubuntu1 gnome-control-center-signon 0.0.18-0ubuntu1 indicator-datetime 12.10.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1077621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1077621] Re: Privacy settings in gnome-control-center should be password protected
@Marc, you're right, I didn't think about that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1077621 Title: Privacy settings in gnome-control-center should be password protected Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Currently, the privacy settings are not secured properly and allows driveby users to get a glimpse of the user's privacy settings. To make my point, if someone manages to view the list of folders that a user doesn't want Zeitgeist to log, he would be able to find the exact folders that the user does not want others to get an easy access. Hence, I suggest the privacy settings are locked by default similar to how the User Accounts work and the settings are only accessible if the user inputs the password. This would provide added security to the user's privacy settings. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu19 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 11 20:34:04 2012 InstallationDate: Installed on 2012-11-10 (0 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-11-11 (0 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu4 deja-dup24.0-0ubuntu1 gnome-control-center-signon 0.0.18-0ubuntu1 indicator-datetime 12.10.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1077621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 844119] Re: Hitting Alt-Tab does not display Libre Office in list of switchable open applications
I confirm this is still present in Ubuntu 12.04. It happens to me no matter if I have lo-menubar installed or not. I can't alt-tab to libreoffice documents. This happens on all my installations of Ubuntu. The Icon correctly shows up in the launcher and in the ALT TAB view. The application just won't focus. As far as I can see this only happens when LO is opened by double- clicking a file (which is probably the way people usually open it). I also don't have the default shortcuts so LO in the launcher. ** This bug is no longer a duplicate of bug 842566 Libreoffice and unity integration broken. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/844119 Title: Hitting Alt-Tab does not display Libre Office in list of switchable open applications Status in BAMF Application Matching Framework: Confirmed Status in Unity: Confirmed Status in Unity 2D: Invalid Status in Unity Foundations: New Status in “bamf” package in Ubuntu: Confirmed Status in “libreoffice” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Confirmed Bug description: Hitting Alt-Tab to bring up a list of switchable open applications does not display the running Libre Office instance. In order to switch to Libre Office and bring it to the foreground I must move other windows around with the mouse and click the Libre Office window. To reproduce: * Open Libre Office Writer * Open a few other applications such a Firefox and Thunderbird * Hit Alt-Tab and switch to Firefox * Hit Alt-Tab again while keeping Alt depressed Expected behavior: * Libre Office should be in the list of available switchable applications Actual behavior: * Libre Office is not in the list of available switchable applications when hitting Alt-Tab and keeping Alt depressed * Libre Office is not switched back to when tapping Alt-Tab quickly (the last-used application before Libre Office is jumped to) ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libreoffice-common 1:3.4.2-2ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 NonfreeKernelModules: wl Architecture: amd64 Date: Wed Sep 7 13:47:30 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/libreoffice InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64+mac (20110901) InterpreterPath: /bin/dash PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/844119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1041054] Re: Alt+Print only works when both keys are pressed at exactly the same time
This looks like a regression. It worked for me before the last update. Now I have the same issue. Also: this bug existed in the past (HUD blocking all keycombos that use ALT) and was already fixed, as far as I remember. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1041054 Title: Alt+Print only works when both keys are pressed at exactly the same time Status in Unity: New Status in “gnome-control-center” package in Ubuntu: New Bug description: With the current unity/compiz/g-c-c/gsd packages Alt+Print only works when both keys are pressed at exactly the same time Also seen with Ctrl+Alt+Print which I never have used but see is inc. Previously one could hold Alt then press Print to get a sceenshot of a window ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu10 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 Date: Fri Aug 24 02:31:29 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120813.1) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1041054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 778070] Re: Failed to submit report/review in software-center
I've got the same problem. Here's my software-center logfile. Here's what I did: I installed LIMBO from the Humble Indie Bundle and tried to write a review. ** Attachment added: software-center logfile https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/778070/+attachment/3177390/+files/software-center.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/778070 Title: Failed to submit report/review in software-center Status in “software-center” package in Ubuntu: Confirmed Bug description: Binary package hint: software-center Trying to submit a report or review in the software-center I get an error-message: Failed to submit report/review though I am logged in to my ubuntuone-account. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: software-center 4.0 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu May 5 21:21:05 2011 ExecutablePath: /usr/share/software-center/report_review.py InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE:en LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/778070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 792085] Re: Automatic remount of safely removed drive
This only happens on certain nvidia chipsets and only with newer kernels (the nautilus-version doesn't really matter). ** Changed in: nautilus (Ubuntu) Status: Confirmed = Invalid ** Changed in: usb-creator (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/792085 Title: Automatic remount of safely removed drive Status in “nautilus” package in Ubuntu: Invalid Status in “udev” package in Ubuntu: Confirmed Status in “usb-creator” package in Ubuntu: Invalid Bug description: Binary package hint: nautilus When I choose Safely remove drive context menu entry for an external USB drive within a nautilus window or directly clicking on the desktop icon, after about 10 seconds the drive is automatically remounted and a Nautilus window showing the root folder opens. I have noticed that similar already happened with a very old Ubuntu version - Bug #110589 and as that is so long time ago I thought it is better to open a new bug. Reason of the problem might even be completely different. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 Date: Thu Jun 2 23:40:08 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
