[Desktop-packages] [Bug 1292382] [NEW] totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory
Public bug reported: Trying to play any .mp3 file, I get: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-12-22 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221) Package: totem 3.10.1-1ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Tags: trusty Uname: Linux 3.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected trusty ** Tags added: apport-collected trusty ** Description changed: Trying to play any .mp3 file, I get: - totem: error while loading shared libraries: libwayland-egl.so.1: cannot - open shared object file: No such file or directory + totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory + --- + ApportVersion: 2.13.3-0ubuntu1 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + InstallationDate: Installed on 2013-12-22 (81 days ago) + InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221) + Package: totem 3.10.1-1ubuntu3 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 + Tags: trusty + Uname: Linux 3.13.0-17-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo + _MarkForUpload: True -- 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/1292382 Title: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory Status in “totem” package in Ubuntu: New Bug description: Trying to play any .mp3 file, I get: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-12-22 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221) Package: totem 3.10.1-1ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Tags: trusty Uname: Linux 3.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1292382/+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 1292382] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1292382/+attachment/4023352/+files/Dependencies.txt -- 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/1292382 Title: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory Status in “totem” package in Ubuntu: New Bug description: Trying to play any .mp3 file, I get: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-12-22 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221) Package: totem 3.10.1-1ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Tags: trusty Uname: Linux 3.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1292382/+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 1292382] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1292382/+attachment/4023356/+files/XorgLog.txt -- 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/1292382 Title: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory Status in “totem” package in Ubuntu: New Bug description: Trying to play any .mp3 file, I get: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-12-22 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221) Package: totem 3.10.1-1ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Tags: trusty Uname: Linux 3.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1292382/+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 1292382] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1292382/+attachment/4023355/+files/ProcEnviron.txt -- 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/1292382 Title: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory Status in “totem” package in Ubuntu: New Bug description: Trying to play any .mp3 file, I get: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-12-22 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221) Package: totem 3.10.1-1ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Tags: trusty Uname: Linux 3.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1292382/+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 1292382] GstreamerVersions.txt
apport information ** Attachment added: "GstreamerVersions.txt" https://bugs.launchpad.net/bugs/1292382/+attachment/4023353/+files/GstreamerVersions.txt -- 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/1292382 Title: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory Status in “totem” package in Ubuntu: New Bug description: Trying to play any .mp3 file, I get: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-12-22 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221) Package: totem 3.10.1-1ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Tags: trusty Uname: Linux 3.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1292382/+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 1292382] LogAlsaMixer.txt
apport information ** Attachment added: "LogAlsaMixer.txt" https://bugs.launchpad.net/bugs/1292382/+attachment/4023354/+files/LogAlsaMixer.txt -- 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/1292382 Title: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory Status in “totem” package in Ubuntu: New Bug description: Trying to play any .mp3 file, I get: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-12-22 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221) Package: totem 3.10.1-1ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Tags: trusty Uname: Linux 3.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1292382/+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 1292389] [NEW] Super + 1 does not launch first app in launcher
Public bug reported: I have a “Bépo” keyboard where the “1” key is in fact the straight doube quote “"” sign. That is, when I want to type 1, I have to type Shift + ". I remember the behavior is similar for the French Azerty keyboard layout. When I type Super + the key where there is a 1 on it, I expect Unity to open the first app in the launcher. This is not the case in Trusty, although it was in Ubuntu 13.10 and earlier. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 14 08:12:30 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-18 (146 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-05 (9 days ago) ** Affects: unity (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 unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1292389 Title: Super + 1 does not launch first app in launcher Status in “unity” package in Ubuntu: New Bug description: I have a “Bépo” keyboard where the “1” key is in fact the straight doube quote “"” sign. That is, when I want to type 1, I have to type Shift + ". I remember the behavior is similar for the French Azerty keyboard layout. When I type Super + the key where there is a 1 on it, I expect Unity to open the first app in the launcher. This is not the case in Trusty, although it was in Ubuntu 13.10 and earlier. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 14 08:12:30 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-18 (146 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-05 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292389/+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 741377] Re: Mouse Pad unusable on HP-DV7, Right Click and multitouch
yes, this bug has been fixed. it works pretty well in 14.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/741377 Title: Mouse Pad unusable on HP-DV7, Right Click and multitouch Status in “xserver-xorg-input-synaptics” package in Ubuntu: Expired Bug description: Binary package hint: xinput ubuntu-10.10-desktop-i386.iso2.6.35-28-generic-pae #49-Ubuntu SMP xinput: Installed: 1.5.2-1 HP DV7-4270 There are two problems here: 1) Right click is totally broken, it does not work at all, instead it sees a Right click as being a Left click 2) The implementation of multi-touch makes the mouse pad very unusable. the mouse cursor jumps around crazily. every time you even slightly brush the pad with another finger. I would much prefer to be able to disable multi-touch altogether, but don't see a control panel setting to do that. Playing with sensitivity did not help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/741377/+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 1292391] Re: lockscreen - wallpaper is not properly resized when unplugging monitors
** Attachment added: "IMG_0458_cropped_resized.JPG" https://bugs.launchpad.net/unity/+bug/1292391/+attachment/4023387/+files/IMG_0458_cropped_resized.JPG ** Description changed: Steps to repoduce: - Have 2 monitors/displays with different resolutions setup on your trusty installation. (In my case: Primary 1600x900 laptop screen and secondary 1920x1080 external monitor.) - Lock the screen via shortcut. - Remove one monitor. (In my case: Remove the external one.) - Result: The display setup change is detected but the wallpaper on the remaining screen shows artifacts of improper resizing. Unlocking and locking the screen again will display the wallpaper properly resized without artifacts. - Settings for background images in control center are set to resize for each screen (the 2nd option). + + + I attached photos taken of the same screen with and without aritfacts (same size, though the dots have different spacing). Wallpaper used is from the current default selection. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- 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/1292391 Title: lockscreen - wallpaper is not properly resized when unplugging monitors Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Steps to repoduce: - Have 2 monitors/displays with different resolutions setup on your trusty installation. (In my case: Primary 1600x900 laptop screen and secondary 1920x1080 external monitor.) - Lock the screen via shortcut. - Remove one monitor. (In my case: Remove the external one.) - Result: The display setup change is detected but the wallpaper on the remaining screen shows artifacts of improper resizing. Unlocking and locking the screen again will display the wallpaper properly resized without artifacts. - Settings for background images in control center are set to resize for each screen (the 2nd option). I attached photos taken of the same screen with and without aritfacts (same size, though the dots have different spacing). Wallpaper used is from the current default selection. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292391/+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 1291869] Re: xorg Edger & Libreoffice 4.2.2 & kernel mainline = logout
Fixed! I touch nothing except I do the morning "apt-get upgrade" and the bug is gone! THX... Let's work now! ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1291869 Title: xorg Edger & Libreoffice 4.2.2 & kernel mainline = logout Status in “xorg-server” package in Ubuntu: Fix Released Bug description: uname -a... Linux b4z4r 3.14.0-031400rc6-lowlatency #201403100035 SMP PREEMPT Mon Mar 10 04:45:13 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux + Xorg -version... X.Org X Server 1.14.5 Release Date: 2013-12-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu Current Operating System: Linux b4z4r 3.14.0-031400rc6-lowlatency #201403100035 SMP PREEMPT Mon Mar 10 04:45:13 UTC 2014 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc6-lowlatency root=UUID=09993a99-14f4-49d8-8a95-9c00c1abed87 ro quiet splash elavator=noop vt.handoff=7 Build Date: 17 December 2013 10:06:15AM xorg-server 2:1.14.5-1ubuntu2~saucy1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.30.2 + libreoffice --version LibreOffice 4.2.2.1 420m0(Build:1) = logout ! any idea? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1291869/+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 1244548] Re: Keyboard shortcut for changing keyboard layout does not work on lock screen
gnome-screensaver (3.6.1-0ubuntu11) - now couldn't change the keyboard layout even by clicking on the language indicator when the PC is locked -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1244548 Title: Keyboard shortcut for changing keyboard layout does not work on lock screen Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Shortcut for changing keyboard layout does not work on lock screen (to change keyboard layout for entering password). - Switch to some non-english layout (otherwise lock screen will not have layout indicator at all) - Lock the screen - Press your shortcut for changing keyboard layout (i.e. ctrl+shift) -- it will not change layout - Clicking layout indicator near password entry box works -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-screensaver 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Oct 25 11:01:10 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-10-23 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548/+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 1292396] [NEW] After upgrade Unity session is broken
Public bug reported: After yesterdays upgrade, when I log in into default session (Unity), there was no Panel, no Launcher, no windows decorations. there was Yesterday's upgrade was related to Unity packadges, so after reboot I logged into Gnome Flashback session - works as expected. Reboot - and there is no Unity session in Unity Greeter. I logged again into Flashback and launch Synaptic. I saw, that Unity package wasn't even installed, so I installed it - Unity session shows up in Greeter, but thaths all, still no Panel, no Launcher, etc. In CCSM Unity plugin was uncheck. I was able to launch window decorations, but launching Unity plugin caused CCSC crash. In another try there was info, that launch of Unity plugin is in conflict with Window Decorations plugin, but somehow launching Unity plugin does nothing, but Compiz crash (https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1292393). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,resize,gnomecompat,regex,imgpng,move,commands,mousepoll,vpswitch,animation,place,wall,unitymtgrabhandles,grid,wobbly,fade,expo,workarounds,session,scale,ezoom] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 14 08:26:59 2014 DistUpgraded: 2013-11-26 21:17:59,613 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7576] MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7576 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=23985ff5-112f-4dab-9da1-5c21397013fe ro splash quiet vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-26 (107 days ago) dmi.bios.date: 11/27/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.9 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 785G-E53 (MS-7576) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.9:bd11/27/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7576:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn785G-E53(MS-7576):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7576 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Mar 14 08:13:38 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 8 inputMicrosoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 9 inputMicrosoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 xserver.video_driver: radeon ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- 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/1292396 Title: After upgrade Unity session is broken Status in “unity” package in Ubuntu: New Bug description: After yesterdays upgrade, when I log in into default session (Unity), there was no Panel, no Launcher, no windows decorations. there was Yesterday's upgrade was related to Unity packadges, so after reboot I logged into Gnome Flashback session - works as expected. Reboot - and there is no Unity session in Unity Greeter. I logged again into Flashback and launch Synaptic. I saw, that Unity package wasn't even installed, so I installed it - Unity session shows up in Greeter, but thaths all, still no Panel, no Launcher,
[Desktop-packages] [Bug 1292398] [NEW] multi-monitor : second screen position isn't saved from one session to another
Public bug reported: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 ** Affects: gnome-control-center (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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: multi-monitor : second screen position isn't saved from one session to another Status in “gnome-control-center” package in Ubuntu: New Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1292398/+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 1292399] Re: unity-settings-daemon crashed with SIGSEGV in dconf_engine_call_handle_reply()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1292399 Title: unity-settings-daemon crashed with SIGSEGV in dconf_engine_call_handle_reply() Status in “unity-settings-daemon” package in Ubuntu: New Bug description: Dear Developers, Normal situation not happening I think this crash, but possible important. I temporary used Gnome Flashback session with Metacity window manager. I want adding system wide level with some custom keybindings with normal dconf profile, based from GNOME wiki page. Source Wiki document is following: https://wiki.gnome.org/Projects/dconf/SystemAdministrators My /etc/dconf/profile/user file containing following two lines: user-db:user system-db:keybinding My /etc/dconf/db/keybinding.d/00-keybinding file containing following lines: [org/gnome/settings-daemon/plugins/media-keys] custom-keybindings=['/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/', '/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom1/'] [org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0] binding='g' command='gedit' name='Launch Gedit' [org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom1] binding='r' command='libreoffice --writer' name='Launch Libreoffice Writer' When I ran dconf update command, without any error right created /etc/dconf/keybinding database file. I experiencing this crash after try logout and login again. I using standard dconf keys and values, so I don't understand why happened this crash. If not need fixing this issue in unity-settings- daemon package, please tell me what the standard way to add custom keybindings with system wide level (very interesting me this possibility with I readed from the wiki document). Attila ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140310-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 Date: Fri Mar 14 08:24:49 2014 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon InstallationDate: Installed on 2013-12-13 (90 days ago) InstallationMedia: BeLin 3.02 i386 ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon ProcEnviron: LANGUAGE=hu XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! Stack memory exhausted (SP below stack segment) SegvReason: executing NULL VMA Signal: 11 SourcePackage: unity-settings-daemon StacktraceTop: ?? () ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: unity-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1292399/+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 1272860] Re: gvfsd-trash crashed with SIGABRT in g_assertion_message()
** Changed in: gvfs Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1272860 Title: gvfsd-trash crashed with SIGABRT in g_assertion_message() Status in GVFS: Invalid Status in “gvfs” package in Ubuntu: Confirmed Bug description: Ubuntu prompted me thus bug when it started. It took a bit more time than usual to display the login screen. Anything went normal the last time I shut it down. Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 Impossible to find pkgname ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gvfs-daemons 1.19.4+git20140116-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic i686 ApportVersion: 2.13.1-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Sun Jan 26 09:43:53 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfsd-trash InstallationDate: Installed on 2013-12-15 (41 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.3 /org/gtk/gvfs/exec_spaw/0 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 Signal: 6 SourcePackage: gvfs StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () Title: gvfsd-trash crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2013-12-15 (41 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1272860/+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 1274890] Re: gvfsd-mtp crashed with SIGABRT in g_thread_abort()
** Changed in: gvfs Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1274890 Title: gvfsd-mtp crashed with SIGABRT in g_thread_abort() Status in GVFS: Incomplete Status in “gvfs” package in Ubuntu: Confirmed Bug description: I was plugging and unplugging a Galaxy Nexus when I got this crash. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gvfs-backends 1.18.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Fri Jan 31 10:28:26 2014 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2010-10-25 (1193 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/22 Signal: 6 SourcePackage: gvfs StacktraceTop: g_thread_abort (status=, function=function@entry=0x7f4064366fd6 "pthread_mutex_trylock") at /build/buildd/glib2.0-2.38.1/./glib/gthread-posix.c:79 g_mutex_trylock (mutex=) at /build/buildd/glib2.0-2.38.1/./glib/gthread-posix.c:261 ?? () g_timeout_dispatch (source=source@entry=0x7f4054018710, callback=, user_data=) at /build/buildd/glib2.0-2.38.1/./glib/gmain.c:4450 g_main_dispatch (context=0xbec150) at /build/buildd/glib2.0-2.38.1/./glib/gmain.c:3065 Title: gvfsd-mtp crashed with SIGABRT in g_thread_abort() UpgradeStatus: Upgraded to saucy on 2013-09-12 (140 days ago) UserGroups: adm admin audio cdrom dialout lp lpadmin plugdev sambashare video www-data To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1274890/+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 1292403] [NEW] Suspend to RAM on notebook, wake up with two screens -> solid pitch black shadows
Public bug reported: After waking from suspend to RAM all shadows are solid black. I am not sure if this is the cause, but this is how I can reproduce it: - I suspend my notebook with no monitors attached - I wake it up with two external monitors attached -> pitch black shadows Restarting unity solves the problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 14 08:48:48 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-17-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-17-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-17-generic, x86_64: installed virtualbox-guest, 4.3.6, 3.13.0-17-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationDate: Installed on 2014-03-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140312) MachineType: LENOVO 4389W1C ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-17-generic root=UUID=0ce514be-eb27-4f82-8221-4b713ed9661b ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET84WW (1.45 ) dmi.board.name: 4389W1C dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4389W1C:pvrThinkPadW510:rvnLENOVO:rn4389W1C:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4389W1C dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Mar 14 07:22:10 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.0-1ubuntu6 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- 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/1292403 Title: Suspend to RAM on notebook, wake up with two screens -> solid pitch black shadows Status in “unity” package in Ubuntu: New Bug description: After waking from suspend to RAM all shadows are solid black. I am not sure if this is the cause, but this is how I can reproduce it: - I suspend my notebook with no monitors attached - I wake it up with two external monitors attached -> pitch black shadows Restarting unity solves the problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRu
[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen
Which package implements the new lock screen? The regression is in this package. The old screensaver (gnome-screensaver?) used to power the monitor off as soon you manually activate the lock screen (eg when you press the key combination to lock the screen). The new 14.04 screen locker (which package implements this?) does NOT power the monitor off when you manually activate the lock screen. Additionally, it blocks the monitor powering off indefinitely (apparently: I've tested it for more than three hours to show that the monitor does not turn off) until you enter the password and press the enter key. At this point, the lock screen restores the normal screen, and shortly thereafter the monitor is powered off briefly (by gnome- screensaver?) before immediately turning back on. If, however, you leave the screen for the configured time before it powers off, the monitor *does* power off. The regression is only when you activate the lock screen manually. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in Unity: Invalid Status in “gnome-screensaver” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292041/+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 1289047] Re: [Trusty] hostapd package is broken
Is there any mode to disable upgrading this package from 13.10 (which works for me too)? I mean when i use "sudo apt-get upgrade" it upgrades this package to 1:2.1 version, which doesn't work (surely bugged). I get the same result on new version from hostapd: nl80211: Could not configure driver mode nl80211 driver initialization failed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1289047 Title: [Trusty] hostapd package is broken Status in “wpa” package in Ubuntu: Confirmed Bug description: When trying to create an access point, I am met with a fatal error with hostapd: nl80211: Could not configure driver mode nl80211 driver initialization failed. hostapd_free_hapd_data: Interface wlan0 wasn't started What worked before no longer works today after a package upgrade. After installing hostapd deb from Ubuntu 13.10, it works. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hostapd 1:2.1-0ubuntu1 Uname: Linux 3.14.0-031400rc5-lowlatency x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Thu Mar 6 16:57:20 2014 InstallationDate: Installed on 2014-02-01 (33 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 LANGUAGE=en_CA:en SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1289047/+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 1292407] [NEW] [lubuntu trusty] Libreoffice shows a fatal error message when trying to open every component
Public bug reported: Every time I wanto open a component of Libreoffice 1:4.2.1-0ubuntu1 on Lubuntu 14.04 (everything is up-to-date and i enabled nvidia drivers) i get this fatal error message and nothing gets opened: The application cannot be started. LibreOffice user installation could not be processed due to missing access rights. Please make sure that you have sufficient access rights for the following location and restart LibreOffice: /home/*user name*/.config/libreoffice/4 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1292407 Title: [lubuntu trusty] Libreoffice shows a fatal error message when trying to open every component Status in “libreoffice” package in Ubuntu: New Bug description: Every time I wanto open a component of Libreoffice 1:4.2.1-0ubuntu1 on Lubuntu 14.04 (everything is up-to-date and i enabled nvidia drivers) i get this fatal error message and nothing gets opened: The application cannot be started. LibreOffice user installation could not be processed due to missing access rights. Please make sure that you have sufficient access rights for the following location and restart LibreOffice: /home/*user name*/.config/libreoffice/4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1292407/+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 1289047] Re: [Trusty] hostapd package is broken
Ok, I've found it. If anyone need stop upgrading by apt, you must use "sudo apt-mark hold hostapd". ( For other update managers etc, see here: http://askubuntu.com/questions/18654/how-to-prevent-updating-of-a -specific-package ) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1289047 Title: [Trusty] hostapd package is broken Status in “wpa” package in Ubuntu: Confirmed Bug description: When trying to create an access point, I am met with a fatal error with hostapd: nl80211: Could not configure driver mode nl80211 driver initialization failed. hostapd_free_hapd_data: Interface wlan0 wasn't started What worked before no longer works today after a package upgrade. After installing hostapd deb from Ubuntu 13.10, it works. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hostapd 1:2.1-0ubuntu1 Uname: Linux 3.14.0-031400rc5-lowlatency x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Thu Mar 6 16:57:20 2014 InstallationDate: Installed on 2014-02-01 (33 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 LANGUAGE=en_CA:en SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1289047/+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 1292412] [NEW] Keyboard layout is always English(!)
Public bug reported: Keyboard layout is always English, no matter that I select a different language in the selector. It is English even if I remove English from the layouts. And layout switching via hot key doesn't work no matter what the hot key is. Both issues are fresh from upgrades that I made today: Start-Date: 2014-03-14 09:25:48 Upgrade: initscripts:amd64 (2.88dsf-41ubuntu5, 2.88dsf-41ubuntu6), pciutils:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), aptdaemon-data:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), ubuntu-session:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), unity-greeter:amd64 (14.04.3-0ubuntu2, 14.04.4-0ubuntu1), libqt4-xml:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-network:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libegl1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libqt4-sql-mysql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libopenvg1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), gnome-session-common:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libfreetype6-dev:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), gnome-session-bin:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libqt4-sql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), isc-dhcp-common:amd64 (4.2.4-7ubuntu8, 4.2.4-7ubuntu9), libegl1-mesa-drivers:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), firefox-locale-en:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), qdbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqtcore4:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-qt3support:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-svg:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-dbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-xmlpatterns:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-sql-sqlite:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-opengl:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), qt4-qtconfig:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libgl1-mesa-dri:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libgl1-mesa-dri:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), unity:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), libunity-core-6.0-9:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), ubuntu-drivers-common:amd64 (0.2.89.6, 0.2.90), firefox:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), libqt4-script:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libfreetype6:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), libfreetype6:i386 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), python-apt:amd64 (0.9.1ubuntu1, 0.9.3.2), libgs9-common:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), ubuntu-release-upgrader-gtk:amd64 (0.216, 0.216.1), libido3-0.1-0:amd64 (13.10.0+14.04.20140213-0ubuntu1, 13.10.0+14.04.20140313-0ubuntu1), libglib2.0-0:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), libglib2.0-0:i386 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), xserver-xorg-core:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), libglapi-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libglapi-mesa:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libpci3:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), gnome-screensaver:amd64 (3.6.1-0ubuntu10, 3.6.1-0ubuntu11), unity-services:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), python-aptdaemon.gtk3widgets:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), bash-completion:amd64 (2.1-2ubuntu3, 2.1-2ubuntu4), xserver-common:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), ghostscript-x:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), libunity-control-center1:amd64 (14.04.3+14.04.20140310-0ubuntu1, 14.04.3+14.04.20140313-0ubuntu1), libglib2.0-data:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), python3-aptdaemon.gtk3widgets:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), libgles2-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), usb-creator-common:amd64 (0.2.54, 0.2.55), libgl1-mesa-glx:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libgl1-mesa-glx:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libxatracker2:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libqt4-designer:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), qtcore4-l10n:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqtdbus4:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), python3-apt:amd64 (0.9.1ubuntu1, 0.9.3.2), python3-aptdaemon.pkcompat:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), xserver-xephyr:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), isc-dhcp-client:am
[Desktop-packages] [Bug 1292398] Re: multi-monitor : second screen position isn't saved from one session to another
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/1292398 Title: multi-monitor : second screen position isn't saved from one session to another Status in “gnome-control-center” package in Ubuntu: New Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1292398/+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 1292412] Re: Keyboard layout is always English(!)
Don't know which is the cause of this but probably `unity-control- center` because `gnome-control-center` wasn't upgraded. -- 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/1292412 Title: Keyboard layout is always English(!) Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-session” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: New Bug description: Keyboard layout is always English, no matter that I select a different language in the selector. It is English even if I remove English from the layouts. And layout switching via hot key doesn't work no matter what the hot key is. Both issues are fresh from upgrades that I made today: Start-Date: 2014-03-14 09:25:48 Upgrade: initscripts:amd64 (2.88dsf-41ubuntu5, 2.88dsf-41ubuntu6), pciutils:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), aptdaemon-data:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), ubuntu-session:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), unity-greeter:amd64 (14.04.3-0ubuntu2, 14.04.4-0ubuntu1), libqt4-xml:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-network:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libegl1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libqt4-sql-mysql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libopenvg1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), gnome-session-common:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libfreetype6-dev:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), gnome-session-bin:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libqt4-sql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), isc-dhcp-common:amd64 (4.2.4-7ubuntu8, 4.2.4-7ubuntu9), libegl1-mesa-drivers:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), firefox-locale-en:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), qdbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqtcore4:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-qt3support:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-svg:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-dbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-xmlpatterns:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-sql-sqlite:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-opengl:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), qt4-qtconfig:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libgl1-mesa-dri:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libgl1-mesa-dri:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), unity:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), libunity-core-6.0-9:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), ubuntu-drivers-common:amd64 (0.2.89.6, 0.2.90), firefox:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), libqt4-script:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libfreetype6:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), libfreetype6:i386 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), python-apt:amd64 (0.9.1ubuntu1, 0.9.3.2), libgs9-common:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), ubuntu-release-upgrader-gtk:amd64 (0.216, 0.216.1), libido3-0.1-0:amd64 (13.10.0+14.04.20140213-0ubuntu1, 13.10.0+14.04.20140313-0ubuntu1), libglib2.0-0:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), libglib2.0-0:i386 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), xserver-xorg-core:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), libglapi-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libglapi-mesa:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libpci3:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), gnome-screensaver:amd64 (3.6.1-0ubuntu10, 3.6.1-0ubuntu11), unity-services:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), python-aptdaemon.gtk3widgets:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), bash-completion:amd64 (2.1-2ubuntu3, 2.1-2ubuntu4), xserver-common:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), ghostscript-x:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), libunity-control-center1:amd64 (14.04.3+14.04.20140310-0ubuntu1, 14.04.3+14.04.20140313-0ubuntu1), libglib2.0-data:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), python3-aptdaemon.gtk3widgets:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), libgles2-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), usb-creator-common:amd64 (0.2.54, 0.2.55), libgl1-mesa-glx:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libgl1-mesa-glx:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libxatra
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Since the Trusty package upgrades from today, selecting a layout doesn't have any effect—it only types English! Even if English isn't present in the "Input sources to use:". Layout switching through any key combination doesn't switch layout. I reported #1292412. -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: Confirmed Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - holding left shift, press and release ctrl -> the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t -> gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a key combinaison (e.g ctrl-space) -> the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - press and release ctrl+left shift -> the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have gnome-tweak-tool installed by default because of many settings that are missed gnome-control-center (bug 1270572) * Please add ability to set keyboard shortcuts to unity-control-center launched from GNOME sessi
[Desktop-packages] [Bug 1292407] Re: [lubuntu trusty] Libreoffice shows a fatal error message when trying to open every component
** Description changed: - Every time I wanto open a component of Libreoffice 1:4.2.1-0ubuntu1 on + Every time I want to open a component of Libreoffice 1:4.2.1-0ubuntu1 on Lubuntu 14.04 (everything is up-to-date and i enabled nvidia drivers) i get this fatal error message and nothing gets opened: - The application cannot be started. + The application cannot be started. LibreOffice user installation could not be processed due to missing access rights. Please make sure that you have sufficient access rights for the following location and restart LibreOffice: /home/*user name*/.config/libreoffice/4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1292407 Title: [lubuntu trusty] Libreoffice shows a fatal error message when trying to open every component Status in “libreoffice” package in Ubuntu: New Bug description: Every time I want to open a component of Libreoffice 1:4.2.1-0ubuntu1 on Lubuntu 14.04 (everything is up-to-date and i enabled nvidia drivers) i get this fatal error message and nothing gets opened: The application cannot be started. LibreOffice user installation could not be processed due to missing access rights. Please make sure that you have sufficient access rights for the following location and restart LibreOffice: /home/*user name*/.config/libreoffice/4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1292407/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Couldn't confirm it, Shahar - the layouts are switching fine, except on the lock screen - https://bugs.launchpad.net/ubuntu/+source/gnome- screensaver/+bug/1244548/comments/24 -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: Confirmed Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - holding left shift, press and release ctrl -> the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t -> gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a key combinaison (e.g ctrl-space) -> the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - press and release ctrl+left shift -> the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have gnome-tweak-tool installed by default because of many settings that are missed gnome-control-center (bug 1270572) * Please add ability to set keyboard shortcuts to unity-control-center launched from GNOME session FlashBack (Compiz and Metacity) (bug 1282637) Separate bug reports for individual l
[Desktop-packages] [Bug 1292407] Re: [lubuntu trusty] Libreoffice shows a fatal error message when trying to open every component
i tried to do a chmod on that, but now nothing related to libreoffice starts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1292407 Title: [lubuntu trusty] Libreoffice shows a fatal error message when trying to open every component Status in “libreoffice” package in Ubuntu: New Bug description: Every time I want to open a component of Libreoffice 1:4.2.1-0ubuntu1 on Lubuntu 14.04 (everything is up-to-date and i enabled nvidia drivers) i get this fatal error message and nothing gets opened: The application cannot be started. LibreOffice user installation could not be processed due to missing access rights. Please make sure that you have sufficient access rights for the following location and restart LibreOffice: /home/*user name*/.config/libreoffice/4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1292407/+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 1292425] [NEW] apport does not specify what personal data it collects and reports
Public bug reported: apport does not specify what personal data it collects and reports. So, for example, if you want to report a bug on gedit, you've no idea if it reports your doc content, or with Thunar your file system structure, or session, the names of every document and window you have open, and content. This discourages reporting. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: apport-gtk 2.9.2-0ubuntu8.5 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportLog: ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CrashReports: 640:1000:110:8454662:2014-03-12 16:45:40.956435918 +:2014-03-12 21:09:31.301023504 +:/var/crash/_usr_bin_zathura.1000.crash 640:1000:110:4090625:2014-03-12 12:19:45.955843925 +:2014-03-12 12:19:46.955843925 +:/var/crash/_usr_bin_thunar.1000.crash 640:1000:110:1515814:2014-03-11 18:49:21.854559421 +:2014-03-11 18:49:22.854559421 +:/var/crash/_usr_bin_xpdf.real.1000.crash Date: Fri Mar 14 08:56:07 2014 InstallationDate: Installed on 2012-11-28 (470 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to raring on 2013-05-14 (303 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1292425 Title: apport does not specify what personal data it collects and reports Status in “apport” package in Ubuntu: New Bug description: apport does not specify what personal data it collects and reports. So, for example, if you want to report a bug on gedit, you've no idea if it reports your doc content, or with Thunar your file system structure, or session, the names of every document and window you have open, and content. This discourages reporting. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: apport-gtk 2.9.2-0ubuntu8.5 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportLog: ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CrashReports: 640:1000:110:8454662:2014-03-12 16:45:40.956435918 +:2014-03-12 21:09:31.301023504 +:/var/crash/_usr_bin_zathura.1000.crash 640:1000:110:4090625:2014-03-12 12:19:45.955843925 +:2014-03-12 12:19:46.955843925 +:/var/crash/_usr_bin_thunar.1000.crash 640:1000:110:1515814:2014-03-11 18:49:21.854559421 +:2014-03-11 18:49:22.854559421 +:/var/crash/_usr_bin_xpdf.real.1000.crash Date: Fri Mar 14 08:56:07 2014 InstallationDate: Installed on 2012-11-28 (470 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to raring on 2013-05-14 (303 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1292425/+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 1292412] Re: Keyboard layout is always English(!)
Thank you for your bug report, gnome-control-center/unity-control-center are interfaces to change configurations, they don't have a service/are not running into the session all the time/have no impact on keyboard layouts set a login or changed during the session. Setting as invalid for those ** Changed in: unity-control-center (Ubuntu) Status: New => Invalid ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-session (Ubuntu) Importance: Undecided => Low ** Changed in: unity-control-center (Ubuntu) Importance: Undecided => Low -- 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/1292412 Title: Keyboard layout is always English(!) Status in “gnome-control-center” package in Ubuntu: Invalid Status in “gnome-session” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: Invalid Bug description: Keyboard layout is always English, no matter that I select a different language in the selector. It is English even if I remove English from the layouts. And layout switching via hot key doesn't work no matter what the hot key is. Both issues are fresh from upgrades that I made today: Start-Date: 2014-03-14 09:25:48 Upgrade: initscripts:amd64 (2.88dsf-41ubuntu5, 2.88dsf-41ubuntu6), pciutils:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), aptdaemon-data:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), ubuntu-session:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), unity-greeter:amd64 (14.04.3-0ubuntu2, 14.04.4-0ubuntu1), libqt4-xml:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-network:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libegl1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libqt4-sql-mysql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libopenvg1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), gnome-session-common:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libfreetype6-dev:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), gnome-session-bin:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libqt4-sql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), isc-dhcp-common:amd64 (4.2.4-7ubuntu8, 4.2.4-7ubuntu9), libegl1-mesa-drivers:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), firefox-locale-en:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), qdbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqtcore4:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-qt3support:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-svg:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-dbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-xmlpatterns:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-sql-sqlite:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-opengl:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), qt4-qtconfig:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libgl1-mesa-dri:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libgl1-mesa-dri:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), unity:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), libunity-core-6.0-9:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), ubuntu-drivers-common:amd64 (0.2.89.6, 0.2.90), firefox:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), libqt4-script:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libfreetype6:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), libfreetype6:i386 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), python-apt:amd64 (0.9.1ubuntu1, 0.9.3.2), libgs9-common:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), ubuntu-release-upgrader-gtk:amd64 (0.216, 0.216.1), libido3-0.1-0:amd64 (13.10.0+14.04.20140213-0ubuntu1, 13.10.0+14.04.20140313-0ubuntu1), libglib2.0-0:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), libglib2.0-0:i386 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), xserver-xorg-core:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), libglapi-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libglapi-mesa:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libpci3:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), gnome-screensaver:amd64 (3.6.1-0ubuntu10, 3.6.1-0ubuntu11), unity-services:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), python-aptdaemon.gtk3widgets:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), bash-completion:amd64 (2.1-2ubuntu3, 2.1-2ubuntu4), xserver-common:amd64 (1.15.0-1ubu
[Desktop-packages] [Bug 1224217] Re: Switch Flashback sessions to XDG_CURRENT_DESKTOP=Unity
After updates I can not start gnome-flashback. I am not using ubuntu package! This was in .xsession-errors: init: Failed to obtain gnome-session instance: Unknown parameter: XDG_CURRENT_DESKTOP What should I do to fix it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1224217 Title: Switch Flashback sessions to XDG_CURRENT_DESKTOP=Unity Status in “gnome-panel” package in Ubuntu: Fix Released Status in “gnome-session” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “unity-settings-daemon” package in Ubuntu: Fix Released Bug description: No errors in logs, no nothing. Just a desktop with right click Tried with existing & a new user account, same thing. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-session-flashback 1:3.6.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Wed Sep 11 20:27:28 2013 GsettingsChanges: InstallationDate: Installed on 2013-08-07 (35 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130803) MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1224217/+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 1292412] Re: Keyboard layout is always English(!)
Dear Sebastien, Should I gather more information in any way to assist with this, please? -- 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/1292412 Title: Keyboard layout is always English(!) Status in “gnome-control-center” package in Ubuntu: Invalid Status in “gnome-session” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: Invalid Bug description: Keyboard layout is always English, no matter that I select a different language in the selector. It is English even if I remove English from the layouts. And layout switching via hot key doesn't work no matter what the hot key is. Both issues are fresh from upgrades that I made today: Start-Date: 2014-03-14 09:25:48 Upgrade: initscripts:amd64 (2.88dsf-41ubuntu5, 2.88dsf-41ubuntu6), pciutils:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), aptdaemon-data:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), ubuntu-session:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), unity-greeter:amd64 (14.04.3-0ubuntu2, 14.04.4-0ubuntu1), libqt4-xml:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-network:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libegl1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libqt4-sql-mysql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libopenvg1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), gnome-session-common:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libfreetype6-dev:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), gnome-session-bin:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libqt4-sql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), isc-dhcp-common:amd64 (4.2.4-7ubuntu8, 4.2.4-7ubuntu9), libegl1-mesa-drivers:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), firefox-locale-en:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), qdbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqtcore4:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-qt3support:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-svg:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-dbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-xmlpatterns:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-sql-sqlite:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-opengl:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), qt4-qtconfig:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libgl1-mesa-dri:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libgl1-mesa-dri:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), unity:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), libunity-core-6.0-9:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), ubuntu-drivers-common:amd64 (0.2.89.6, 0.2.90), firefox:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), libqt4-script:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libfreetype6:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), libfreetype6:i386 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), python-apt:amd64 (0.9.1ubuntu1, 0.9.3.2), libgs9-common:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), ubuntu-release-upgrader-gtk:amd64 (0.216, 0.216.1), libido3-0.1-0:amd64 (13.10.0+14.04.20140213-0ubuntu1, 13.10.0+14.04.20140313-0ubuntu1), libglib2.0-0:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), libglib2.0-0:i386 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), xserver-xorg-core:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), libglapi-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libglapi-mesa:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libpci3:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), gnome-screensaver:amd64 (3.6.1-0ubuntu10, 3.6.1-0ubuntu11), unity-services:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), python-aptdaemon.gtk3widgets:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), bash-completion:amd64 (2.1-2ubuntu3, 2.1-2ubuntu4), xserver-common:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), ghostscript-x:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), libunity-control-center1:amd64 (14.04.3+14.04.20140310-0ubuntu1, 14.04.3+14.04.20140313-0ubuntu1), libglib2.0-data:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), python3-aptdaemon.gtk3widgets:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), libgles2-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), usb-creator-common:amd64 (0.2.54, 0.2.55), libgl1-mesa-glx:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libgl1-mesa-glx:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libxatracker2:amd64 (10.1.0~rc3-
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Keyboard shortcuts for layout switching do not work in: a) logon screen (unity greeter); b) lock screen -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: Confirmed Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - holding left shift, press and release ctrl -> the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t -> gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a key combinaison (e.g ctrl-space) -> the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - press and release ctrl+left shift -> the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have gnome-tweak-tool installed by default because of many settings that are missed gnome-control-center (bug 1270572) * Please add ability to set keyboard shortcuts to unity-control-center launched from GNOME session FlashBack (Compiz and Metacity) (bug 1282637) Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Sp
[Desktop-packages] [Bug 1283491] Re: rendering and size issues on high-dpi screen
You can use our PPA with the Onboard releases, if you want to use version 1.0.1 immediately: https://launchpad.net/~onboard/+archive/stable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1283491 Title: rendering and size issues on high-dpi screen Status in Onboard on-screen keyboard: Fix Released Status in “onboard” package in Ubuntu: Confirmed Bug description: When the global scaling factor is set to 2, onboard is not usable for touch input. In docked mode (bottom half of screen), it draws keys too large and most of the onboard UI is not drawn at all. In windowed mode (with titlebar and resizeable), the size is correct but it does not refresh the rendering. org.gnome.desktop.interface.scaling-factor = 2 org.gnome.desktop.interface.text-scaling-factor = 1.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: onboard 1.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 22 17:44:03 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (19 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1283491/+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 1287148] Re: [Lenovo ThinkPad X1 Carbon] Clickpad + Trackpoint cannot emulate middle button scrolling
** Tags removed: needs-apport-collect needs-trusty-test ** Changed in: xorg (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1287148 Title: [Lenovo ThinkPad X1 Carbon] Clickpad + Trackpoint cannot emulate middle button scrolling Status in “xorg” package in Ubuntu: New Bug description: I'm testing with a freshly-updated Trusty Tahir daily (2014/March/2) on a Lenovo X1 Carbon (2014 refresh) laptop. IBM/Lenovo Thinkpad laptops have a "Trackpoint": a red "joystick mouse" in the middle of the keyboard. Historically this is accompanied by three mouse buttons directly below the space bar. One beloved feature: if you hold down the middle mouse button, you can scroll a window up/down/left/right with the Trackpoint. This feature is implemented in X with the "Evdev Wheel Emulation" properties of the xinput driver for the Trackpoint device. The latest Thinkpad laptops (X240, X1 Carbon 2014 refresh) remove the hard buttons, and have a "clickpad" instead of a trackpad.One must use the "soft" mouse buttons provided by the clickpad. But now we have a problem. The clickpad soft buttons are implemented in the Synaptic driver. And the Synaptic driver doesn't support middle- button-scrolling. If I run % xinput --list-props "TPPS/2 IBM TrackPoint" I see property entries starting with "Evdev Wheel Emulation". Setting them on this device doesn't enable middle-button-scrolling. And if I run % xinput --list-props "SynPS/2 Synaptics TouchPad" I don't see those property entries at all. I tried setting them manually with "xinput --set-int-prop" but they were ignored. One of the maintainers of Arch Linux got middle-button-scrolling with a Trackpoint + clickpad to work! But he had to create a new driver. It looks like he started with the evdev driver, and merged in support for the Synaptics and Trackpoint devices. The resulting driver is published here: https://bitbucket.org/esrevinu/xf86-input-evdev-trackpoint It would be fantastic if Ubuntu 14.04 also supported this feature. Thanks! --- .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2218] InstallationDate: Installed on 2014-03-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313) MachineType: LENOVO 20A7CTO1WW Package: xorg 1:7.7+1ubuntu8 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed root=UUID=265f35f3-eb2b-48a6-bbed-84255b758df9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Tags: trusty ubuntu reproducible Uname: Linux 3.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/03/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GRET29WW (1.06 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET29WW(1.06):bd12/03/2013:svnLENOVO:pn20A7CTO1WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CTO1WW:rvrSDK0E50512Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7CTO1WW dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc3-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Mar 13 11:21:03 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id
[Desktop-packages] [Bug 1267328] Re: [13.10] No headphones detected in designated jack (Alienware M14x R2 / Intel C210 / Creative CA0132)
*** This bug is a duplicate of bug 1267675 *** https://bugs.launchpad.net/bugs/1267675 ** This bug has been marked a duplicate of bug 1267675 [13.10] Alienware M14xR2 (CA0132) - External headphone/headset/microphone do not work when plugged in -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1267328 Title: [13.10] No headphones detected in designated jack (Alienware M14x R2 / Intel C210 / Creative CA0132) Status in “alsa-driver” package in Ubuntu: New Bug description: My M14x R2 comes with three jacks: one solely for a microphone, one for a headset, and one for headphones. The headset jack is detected and will play audio, but is physically damaged. The headphone jack is not detected; that is, when headphones are plugged in, they are not shown in sound settings, and sound continues to play from the speakers. I've followed the ubuntu troubleshooting guide, but found little documentation of this same issue. Thanks for any help. Please see this thread for more information related to the issue: https://answers.launchpad.net/ubuntu/+source/alsa- driver/+question/241699 Alsa settings have been changed, so the output to wget -O alsa- info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x ./alsa- info.sh && ./alsa-info.sh may not be entirely relevant. zach@zach-M14xR2:~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CA0132 Analog [CA0132 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: CA0132 Digital [CA0132 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 zach@zach-M14xR2:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1267328/+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 1267675] Re: [13.10] Alienware M14xR2 (CA0132) - External headphone/headset/microphone do not work when plugged in
** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1267675 Title: [13.10] Alienware M14xR2 (CA0132) - External headphone/headset/microphone do not work when plugged in Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: The Alienware M14xR2 has 3 left-side audio jacks. A headphone jack, and headset jack, and a microphone jack. Audio will play through the internal speakers regardless of whether a device is plugged into any of these jacks, and sound will not play in the headphones regardless of which jack they're plugged into. External microphone does not work when plugged into either jack (microphone jack or headset jack). In sound settings, plugging headphones into the headphones jack does not register any change. When plugged into the headset jack, the "Play sound through" device will change from "Speakers" to "Headphones", but sound is not funneled to the headphones; the sound continues to play through the speakers. Also, in a semi-related note, unplugging the headphones seems to change the output device from "Speakers" to "Digital Output (S/PDIF)", which does not produce any sounds through internal speakers nor headphones/headset. Furthermore, if I run gnome-control-center from terminal to launch System Settings and click Sound, the following messages appear in the terminal: (gnome-control-center:4041): sound-cc-panel-WARNING **: active_output_update - couldn't find a stream from the supposed active output (gnome-control-center:4041): sound-cc-panel-WARNING **: active_input_update - couldn't find a stream from the supposed active input I'm trying to get a headset (headphones/microphone) to work well with Ubuntu to support Steam gaming on Linux and Linux gaming in general; having a functioning headset so I can communicate with others via Mumble would be of great help. Thanks for any insight on how to get this working. Have also tried the alsa-daily ppa (dkms) with no luck. lsb_release -rd: Description: Ubuntu 13.10 Release: 13.10 apt-cache policy alsa-base alsa-base: Installed: 1.0.25+dfsg-0ubuntu4 Candidate: 1.0.25+dfsg-0ubuntu4 Version table: *** 1.0.25+dfsg-0ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: earl 1937 F pulseaudio /dev/snd/controlC0: earl 1937 F pulseaudio /dev/snd/pcmC0D0p: earl 1937 F...m pulseaudio Date: Thu Jan 9 20:31:27 2014 InstallationDate: Installed on 2013-11-16 (54 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: GK107 HDMI Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2012 dmi.bios.vendor: Alienware dmi.bios.version: A09 dmi.board.name: M14xR2 dmi.board.vendor: Alienware dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A09 dmi.modalias: dmi:bvnAlienware:bvrA09:bd06/29/2012:svnAlienware:pnM14xR2:pvrA09:rvnAlienware:rnM14xR2:rvrA09:cvnAlienware:ct8:cvrA09: dmi.product.name: M14xR2 dmi.product.version: A09 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1267675/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
@Steve: thanks for checking. When we discussed it with Robert the consensus was that we find that it's a risky change, and that it has potential to create issues for us. If that was not blocking the GNOME remix, for some of their work, we would have nacked the request, we would like to try to accomodate everyone though. In the previous testing round we had some issues, so I would like to give it again some proper testing before giving a +1 or -1. The archive has been moving since that request was filed, so the testing ppa that was set up is not usable anymore. It would be good if somebody could rebase the changes on the current archive version so we can use the ppa for testing, I don't think I'm going to have the free slots to do the rebasing/local builds myself just to be able to test those changes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Invalid Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: In Progress Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1292382] Re: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory
*** This bug is a duplicate of bug 1291761 *** https://bugs.launchpad.net/bugs/1291761 ** This bug has been marked a duplicate of bug 1291761 Depends on libhybris on the desktop -- 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/1292382 Title: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory Status in “totem” package in Ubuntu: New Bug description: Trying to play any .mp3 file, I get: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-12-22 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221) Package: totem 3.10.1-1ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Tags: trusty Uname: Linux 3.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1292382/+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 1288786] Re: pkexec does not launch graphical authentication
I first saw this after the updates to Lubuntu 14.04 yesterday morning March 13 10:15GMT. In my case it is only the Lubuntu 32bit system that is affected, not Xubuntu or Ubuntu both of which are 64 bit. I posted the problem to Ubuntuforums http://ubuntuforums.org/showthread.php?t=2210892&p=12956114#post12956114 and gave my workaround for the problem, ie changing the line Exec=synaptic-pkexec in /usr/share/applications/synaptic.desktop to Exec=gksudo synaptic but this very much a workaround which should not be needed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1288786 Title: pkexec does not launch graphical authentication Status in “policykit-1” package in Ubuntu: Confirmed Bug description: Installed Trusty Tahr Lubuntu Beta1 version and added xubuntu desktop. In buth desktops, I tried to launch synaptic to install some packages. If I try to launch from menu, nothing seems to happen. From a terminal, I ran pkexec "/usr/sbin/synaptic" and saw that it asks for password in the terminal window, instead of popping up an authentication window like previous Ubuntu version did. That was why I saw no authentication request when launching from menu.. I have a workaround)launching from Terminal window), but this should be fixed before release. ralph@minnie:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)" ralph@minnie:~$ pkexec --version pkexec version 0.105 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1288786/+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
(changing the status to "New" so it's easier to ubuntu-release to notice that it needs reviewing) ** Changed in: libimobiledevice (Ubuntu) Status: Confirmed => New -- 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: New 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 1292041] Re: Lockscreen doesn't turn off the screen
@Rocko Marco Trevisan is a Unity developer so he knows what he's doing. This apparently means that the bug is in gnome-screensaver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in Unity: Invalid Status in “gnome-screensaver” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292041/+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 519928]
Are there any known work-arounds? Zooming is more common than ever, especially now that high(ish)-DPI monitors are finally entering the PC market. Even IE11 does this correctly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/519928 Title: Firefox incorrectly renders table borders when zooming Status in The Mozilla Firefox Browser: Confirmed Status in “firefox” package in Ubuntu: Triaged Bug description: Binary package hint: mozilla-firefox Steps to reproduce: 1. Open Firefox 2. Go to http://kossick.de/test.htm 3. Zoom in and out (either using View -> Zoom, or Ctrl + Scroll) Expected Result: The table would retain its properties and still be rendered correctly, just larger or smaller in overall size. Observed Behavior: The borders of the table change thickness, sometimes disappearing because they get so thin. Confirmed on: Ubuntu 9.10 (64-bit), NVidia, Firefox 3.7 Ubuntu 9.10 (64-bit), Intel, Firefox 3.6 Ubuntu 9.10 (32-bit) Ubuntu 10.04 (alpha 2) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/519928/+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 1292438] [NEW] BETA 14.04 cant connect to PulseAudio server
Public bug reported: 1) Install Ubuntustudio 64 bit 14.04 Beta 1 (Alpha) Feb 24 2) reboot etc result: Sound system works properly 3) Install all the latest updates as of Mar 14, 3.13.0-17-lowlatency kernel 4) reboot etc result: Sound System no longer works anything that tries to connect to the PulseAudio server, including the Volume Contol, hangs... Expected: PulseAudio should still work after the update Note: JACK is still usable. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-17.37-lowlatency 3.13.6 Uname: Linux 3.13.0-17-lowlatency x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: em 1829 F pulseaudio /dev/snd/controlC0: em 1829 F pulseaudio CurrentDesktop: XFCE Date: Fri Mar 14 02:45:02 2014 InstallationDate: Installed on 2014-03-14 (0 days ago) InstallationMedia: Ubuntu-Studio 14.04 "Trusty Tahr" - Alpha amd64 (20140224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1641 dmi.board.vendor: Hewlett-Packard dmi.board.version: 67.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.23:bd11/11/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058912242B2020100:rvnHewlett-Packard:rn1641:rvr67.32:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 058912242B2020100 dmi.sys.vendor: Hewlett-Packard ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1292438 Title: BETA 14.04 cant connect to PulseAudio server Status in “pulseaudio” package in Ubuntu: New Bug description: 1) Install Ubuntustudio 64 bit 14.04 Beta 1 (Alpha) Feb 24 2) reboot etc result: Sound system works properly 3) Install all the latest updates as of Mar 14, 3.13.0-17-lowlatency kernel 4) reboot etc result: Sound System no longer works anything that tries to connect to the PulseAudio server, including the Volume Contol, hangs... Expected: PulseAudio should still work after the update Note: JACK is still usable. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-17.37-lowlatency 3.13.6 Uname: Linux 3.13.0-17-lowlatency x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: em 1829 F pulseaudio /dev/snd/controlC0: em 1829 F pulseaudio CurrentDesktop: XFCE Date: Fri Mar 14 02:45:02 2014 InstallationDate: Installed on 2014-03-14 (0 days ago) InstallationMedia: Ubuntu-Studio 14.04 "Trusty Tahr" - Alpha amd64 (20140224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1641 dmi.board.vendor: Hewlett-Packard dmi.board.version: 67.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.23:bd11/11/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058912242B2020100:rvnHewlett-Packard:rn1641:rvr67.32:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 058912242B2020100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1292438/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
(note that it should be possible to review/land the new service (that's a new source right?) while the other changes are evaluated) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Invalid Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: In Progress Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1215449] Re: triple monitor support not working on HD 4600
Andy Fraley, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal: ubuntu-bug xorg Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. For more on this, please see the official Ubuntu documentation: Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Please note, not filing a new report will delay your problem being addressed as quickly as possible. Thank you for your understanding. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1215449 Title: triple monitor support not working on HD 4600 Status in X.org xf86-video-intel: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: I have a Gigabyte GA-H87N-wifi motherboard, which explicitly supports 3 monitors at the same time from the motherboards' onboard graphics (2x HDMI, 1x DVI). The CPU is an Intel 4570S with HD4600 graphics (also supporting 3 heads at the same time). However, I can only get 2 monitors (any 2, but not all 3) working. All monitors are identical 1600x1200 (NEC LCD2070NX). The KDE systemsettings GUI helpfully shows icons for all 3 monitors, but one is always greyed out, and attempting to enable it emits "Failed to set mode: Invalid argument" in Xorg.0.log. Xrandr compians "Configure crtc 2 failed". However, it's clear that the graphics hardware can handle 3 outputs, since it refers to "pipe 0, pipe 1 and pipe 2" in the logs. Google doesn't show anything very helpful, except to warn that in older graphics hardware (definitely not this motherboard) there may be more output connectors than graphics pipelines, and that in the HD4600 there are only 2x PLL, so 2 of the monitors need to be identically clocked (as they are). This also affects the xorg-edgers packages, as of yesterday, so it seems to be an upstream problem. Xorg.0.log attached. Thanks for your help - please let me know if there's anything I can do to assist in debugging. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1215449/+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 800064] Re: touchpad rotation when monitor rotated
TomasHnyk, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal: ubuntu-bug xorg Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. For more on this, please see the official Ubuntu documentation: Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Please note, not filing a new report will delay your problem being addressed as quickly as possible. Thank you for your understanding. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/800064 Title: touchpad rotation when monitor rotated Status in “xserver-xorg-input-synaptics” package in Ubuntu: Expired Bug description: when the monitor is rotated to a portrait orientation using gnome- display-properties (changing the rotation dropdown), and then i physically rotate my laptop, any connected usb mice then move correctly across the portrait screen- there are no issues with rotation for external mice. however, ubuntu (maverick at least) does not account for the fact that if you physically rotate your monitor, then you're obviously going to need to physically rotate a laptop's touchpad as well and thus the internal touchpad does not properly work when the laptop's monitor is in a portrait mode- up on the rotated touchpad = left, etc not sure of what package the bug is in - probably x.org ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: ubuntu-desktop 1.207 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Tue Jun 21 08:52:53 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/800064/+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 1292412] Re: Keyboard layout is always English(!)
Could you describe your system configuration, what you do and what happens exactly? It might be useful to get a log of the command "unity-settings-daemon --replace --debug" as well -- 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/1292412 Title: Keyboard layout is always English(!) Status in “gnome-control-center” package in Ubuntu: Invalid Status in “gnome-session” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: Invalid Bug description: Keyboard layout is always English, no matter that I select a different language in the selector. It is English even if I remove English from the layouts. And layout switching via hot key doesn't work no matter what the hot key is. Both issues are fresh from upgrades that I made today: Start-Date: 2014-03-14 09:25:48 Upgrade: initscripts:amd64 (2.88dsf-41ubuntu5, 2.88dsf-41ubuntu6), pciutils:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), aptdaemon-data:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), ubuntu-session:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), unity-greeter:amd64 (14.04.3-0ubuntu2, 14.04.4-0ubuntu1), libqt4-xml:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-network:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libegl1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libqt4-sql-mysql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libopenvg1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), gnome-session-common:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libfreetype6-dev:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), gnome-session-bin:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libqt4-sql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), isc-dhcp-common:amd64 (4.2.4-7ubuntu8, 4.2.4-7ubuntu9), libegl1-mesa-drivers:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), firefox-locale-en:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), qdbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqtcore4:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-qt3support:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-svg:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-dbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-xmlpatterns:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-sql-sqlite:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-opengl:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), qt4-qtconfig:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libgl1-mesa-dri:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libgl1-mesa-dri:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), unity:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), libunity-core-6.0-9:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), ubuntu-drivers-common:amd64 (0.2.89.6, 0.2.90), firefox:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), libqt4-script:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libfreetype6:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), libfreetype6:i386 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), python-apt:amd64 (0.9.1ubuntu1, 0.9.3.2), libgs9-common:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), ubuntu-release-upgrader-gtk:amd64 (0.216, 0.216.1), libido3-0.1-0:amd64 (13.10.0+14.04.20140213-0ubuntu1, 13.10.0+14.04.20140313-0ubuntu1), libglib2.0-0:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), libglib2.0-0:i386 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), xserver-xorg-core:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), libglapi-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libglapi-mesa:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libpci3:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), gnome-screensaver:amd64 (3.6.1-0ubuntu10, 3.6.1-0ubuntu11), unity-services:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), python-aptdaemon.gtk3widgets:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), bash-completion:amd64 (2.1-2ubuntu3, 2.1-2ubuntu4), xserver-common:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), ghostscript-x:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), libunity-control-center1:amd64 (14.04.3+14.04.20140310-0ubuntu1, 14.04.3+14.04.20140313-0ubuntu1), libglib2.0-data:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), python3-aptdaemon.gtk3widgets:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), libgles2-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), usb-creator-common:amd64 (0.2.54, 0.2.55), libgl1-mesa-glx:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), lib
[Desktop-packages] [Bug 1292440] [NEW] I have two network indicators
Public bug reported: I have two network indicators in the indicator panel. One looks like the one in Ubuntu 13.10, the other one like the one in the current Ubuntu Touch. I installed unity-desktop-session-mir. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 14 10:47:20 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-18 (146 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-05 (9 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "The superfluous indicator" https://bugs.launchpad.net/bugs/1292440/+attachment/4023732/+files/Screenshot%20from%202014-03-14%2010%3A54%3A05.png -- 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/1292440 Title: I have two network indicators Status in “unity” package in Ubuntu: New Bug description: I have two network indicators in the indicator panel. One looks like the one in Ubuntu 13.10, the other one like the one in the current Ubuntu Touch. I installed unity-desktop-session-mir. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 14 10:47:20 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-18 (146 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-05 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292440/+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 1292442] [NEW] lockscreen: menus interactable but render behind the lockscreen
Public bug reported: With the latest unity update the lock screen is now in front of the indicator menus which are rendered on click, but behind the lock panel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 14 09:55:44 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (266 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-10 (123 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lockscreen third-party-packages trusty ** Tags added: lockscreen -- 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/1292442 Title: lockscreen: menus interactable but render behind the lockscreen Status in “unity” package in Ubuntu: New Bug description: With the latest unity update the lock screen is now in front of the indicator menus which are rendered on click, but behind the lock panel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 14 09:55:44 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (266 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-10 (123 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292442/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
@Mikhail V. Golubev (mvgolubev) >Keyboard shortcuts for layout switching do not work in: It is known but not fixed issues. >a) logon screen (unity greeter); = bug 1245137 >b) lock screen = bug 1244548 -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: Confirmed Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - holding left shift, press and release ctrl -> the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t -> gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a key combinaison (e.g ctrl-space) -> the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - press and release ctrl+left shift -> the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have gnome-tweak-tool installed by default because of many settings that are missed gnome-control-center (bug 1270572) * Please add ability to set keyboard shortcuts to unity-control-center launched from GNOME session FlashBack (Compiz and Metacity) (bug 1282637) Separate bug
[Desktop-packages] [Bug 1028617] Re: Cursor shakes violently when connected to power source - makes touchpad cursor unusable
Sam, please do not apport-collect to a report you are not the original reporter of. Despite this, so your hardware and problem may be tracked, please feel free to file a new report by executing the following in a terminal: ubuntu-bug xorg Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. For more on this, please see the official Ubuntu documentation: Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Please note, not filing a new report will delay your problem being addressed as quickly as possible. Thank you for your understanding. ** Tags removed: apport-collected saucy ubuntu ** Attachment removed: "xserver.devices.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018768/+files/xserver.devices.txt ** Attachment removed: "XorgLogOld.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018766/+files/XorgLogOld.txt ** Attachment removed: "xinput.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018767/+files/xinput.txt ** Attachment removed: "XorgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018765/+files/XorgLog.txt ** Attachment removed: "UdevLog.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018764/+files/UdevLog.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018763/+files/UdevDb.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018762/+files/ProcModules.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018761/+files/ProcInterrupts.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018760/+files/ProcEnviron.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018756/+files/ProcCpuinfo.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018755/+files/Lsusb.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018754/+files/Lspci.txt ** Attachment removed: "LightdmLog.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018753/+files/LightdmLog.txt ** Attachment removed: "LightdmGreeterLogOld.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018752/+files/LightdmGreeterLogOld.txt ** Attachment removed: "LightdmGreeterLog.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018751/+files/LightdmGreeterLog.txt ** Attachment removed: "LightdmDisplayLog.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018750/+files/LightdmDisplayLog.txt ** Attachment removed: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018749/+files/DpkgLog.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018748/+files/Dependencies.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018747/+files/CurrentDmesg.txt ** Attachment removed: "BootLog.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018746/+files/BootLog.txt ** Attachment removed: "BootDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1028617/+attachment/4018745/+files/BootDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1028617 Title: Cursor shakes violently when connected to power source - makes touchpad cursor unusable Status in “xserver-xorg-input-synaptics” package in Ubuntu: Incomplete Bug description: Using Ubuntu 12.04, 64-bit version, installed on Lenovo X220 laptop. Fresh "defau
[Desktop-packages] [Bug 1291173] Re: keyring app problem
Not a driver bug, and I do not know which package it should be transferred to. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1291173 Title: keyring app problem Status in “xserver-xorg-video-intel” package in Ubuntu: Invalid Bug description: after i upgrade to ubuntu 14.04 LTS when i start my system the request for keyring opens up. but the unlock and cancel buttons appear in the text area which is very annoying. i can still type the password and click the buttons but it doesnt look good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1291173/+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 1176415] Re: Unable to enable IPv6 Privacy Extensions on eth0
I can confirm that Ubuntu 13.10 Desktop x86_64 changes the 9th octet only! Fresh install two weeks ago. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1176415 Title: Unable to enable IPv6 Privacy Extensions on eth0 Status in “network-manager” package in Ubuntu: Confirmed Bug description: This is on a fresh install of 13.04. Network Manager keeps defaulting net.ipv6.conf.all.use_tempaddr back to 0. I'm fairly confident this problem did not exist in 12.10, but feel free to squash this ticket if it is indeed a duplicate of #990011. Confirmed net.ipv6.conf.all.use_tempaddr is also set to 0 on my laptop running 13.04. Luckily I use eth1 (wifi in this case) which seems unaffected. $ ls /proc/sys/net/ipv6/conf/ all default eth0 lo $ cat /proc/sys/net/ipv6/conf/*/use_tempaddr 2 2 0 2 $ sudo sysctl net.ipv6.conf.all.use_tempaddr=0 net.ipv6.conf.all.use_tempaddr = 0 $ cat /proc/sys/net/ipv6/conf/*/use_tempaddr 0 0 0 0 $ sudo sysctl net.ipv6.conf.all.use_tempaddr=2 net.ipv6.conf.all.use_tempaddr = 2 $ cat /proc/sys/net/ipv6/conf/*/use_tempaddr 2 2 0 2 $ sudo sysctl net.ipv6.conf.eth0.use_tempaddr=2 net.ipv6.conf.eth0.use_tempaddr = 2 $ cat /proc/sys/net/ipv6/conf/eth0/use_tempaddr 0 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sat May 4 12:25:29 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-27 (7 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.213 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1ddad2c33-3c6c-44c6-aa1a-51a13560b698 802-3-ethernet1367695468 Sat 04 May 2013 12:24:28 PM PDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1176415/+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 1292446] [NEW] lockscreen: on autolock on suspend the fade does not complete before suspend leaving desktop partially visible for a short period on resume
*** This bug is a security vulnerability *** Public security bug reported: When auto-locking as part of a suspend operation the lock screen still fades to opaque, this takes seconds and mid fade the suspend occurs. This means that on waking the machine the fade is still occurring and the desktop is partially visible potentially exposing information protected by the lock. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 14 10:02:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (266 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-10 (123 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lockscreen third-party-packages trusty ** Tags added: lockscreen -- 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/1292446 Title: lockscreen: on autolock on suspend the fade does not complete before suspend leaving desktop partially visible for a short period on resume Status in “unity” package in Ubuntu: New Bug description: When auto-locking as part of a suspend operation the lock screen still fades to opaque, this takes seconds and mid fade the suspend occurs. This means that on waking the machine the fade is still occurring and the desktop is partially visible potentially exposing information protected by the lock. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 14 10:02:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (266 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-10 (123 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292446/+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 1291326] Re: Ubuntu 14.04 fail to wakeup from sleep
The update to prime 0.6 released today does not solve this bug, the mouse still does not respond on wakeup. But the Ctrl+Alt+F6 followed by Ctrl+Alt+F7 ends with a correct login screen with mouse working, so the session can be unlocked, though some visual artifacts appears (bakground image lost is some of the desktops) and in the top bar of some apps like Chrome. Also there's some slowdowon in the system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1291326 Title: Ubuntu 14.04 fail to wakeup from sleep Status in “nvidia-prime” package in Ubuntu: Confirmed Bug description: I'm using Kubuntu 14.04 64 bit on a Dell E5440 machine. After installing the alpha2 version two weeks ago wakeup from sleep was working fine. I update the system everyday and during last week something broke this feature. From then I have updated the bios (from A00 version June 2013 to A04 January 2014) and I've seen other bugs (VGA out among others) fixed, but not this one. When the system wakes from sleep the login screen appears, but mouse/keyboard don't working. I have found that plugin something to the VGA out and unplugin it will bring mouse/keyboard alive again, but this solution only works for the first time I enter sleep mode. Ctrl+Alt+F6 followed by Ctrl+Alt+F7 to return to the graphics mode ends with a black screen (the mouse works, but no login is possible). I installed the graphics driver with Optimus support (Prime), keeping active the Nvidia card GT720M. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 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: KDE Date: Wed Mar 12 12:28:20 2014 InstallationDate: Installed on 2014-02-27 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140227) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alonso 2770 F pulseaudio /dev/snd/controlC0: alonso 2770 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1bc33d13-cf2d-4092-9768-3bc7d7602762 InstallationDate: Installed on 2014-02-27 (12 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140227) MachineType: Dell Inc. Latitude E5440 NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=es_ES TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=f23bdd16-c018-4bf4-843d-ce96a510108e ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 Tags: trusty Uname: Linux 3.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 01/22/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0WV8K7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd01/22/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn0WV8K7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1291326/+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 1292412] Re: Keyboard layout is always English(!)
Sebastien, I'm running Unity 7 in Trusty. This system has been upgraded since it was installed from Maverick on 2010-10-12. It seems that the configuration that I set with the control center don't have any effect on the keyboard layout. Using the mouse with the layout switching indicator to select a different language doesn't actually change the keyboard layout. Whatever I do with the UI, it seems I always am typing English. And layout switching via hot-key also does not change the layout, even in the UI (not to mention actually changing the layout). I haven't tried changing layout in any other way because I don't know how to (for example, using command-line). For other things—the control center works. For example, it changes my desktop background. As it is, I can't type my native language in this system. -- 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/1292412 Title: Keyboard layout is always English(!) Status in “gnome-control-center” package in Ubuntu: Invalid Status in “gnome-session” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: Invalid Bug description: Keyboard layout is always English, no matter that I select a different language in the selector. It is English even if I remove English from the layouts. And layout switching via hot key doesn't work no matter what the hot key is. Both issues are fresh from upgrades that I made today: Start-Date: 2014-03-14 09:25:48 Upgrade: initscripts:amd64 (2.88dsf-41ubuntu5, 2.88dsf-41ubuntu6), pciutils:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), aptdaemon-data:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), ubuntu-session:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), unity-greeter:amd64 (14.04.3-0ubuntu2, 14.04.4-0ubuntu1), libqt4-xml:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-network:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libegl1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libqt4-sql-mysql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libopenvg1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), gnome-session-common:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libfreetype6-dev:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), gnome-session-bin:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libqt4-sql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), isc-dhcp-common:amd64 (4.2.4-7ubuntu8, 4.2.4-7ubuntu9), libegl1-mesa-drivers:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), firefox-locale-en:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), qdbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqtcore4:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-qt3support:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-svg:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-dbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-xmlpatterns:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-sql-sqlite:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-opengl:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), qt4-qtconfig:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libgl1-mesa-dri:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libgl1-mesa-dri:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), unity:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), libunity-core-6.0-9:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), ubuntu-drivers-common:amd64 (0.2.89.6, 0.2.90), firefox:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), libqt4-script:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libfreetype6:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), libfreetype6:i386 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), python-apt:amd64 (0.9.1ubuntu1, 0.9.3.2), libgs9-common:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), ubuntu-release-upgrader-gtk:amd64 (0.216, 0.216.1), libido3-0.1-0:amd64 (13.10.0+14.04.20140213-0ubuntu1, 13.10.0+14.04.20140313-0ubuntu1), libglib2.0-0:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), libglib2.0-0:i386 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), xserver-xorg-core:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), libglapi-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libglapi-mesa:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libpci3:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), gnome-screensaver:amd64 (3.6.1-0ubuntu10, 3.6.1-0ubuntu11), unity-services:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), pyth
[Desktop-packages] [Bug 1292436] Re: NetworkManager crashed with SIGSEGV in nm_active_connection_get_state()
*** This bug is a duplicate of bug 1156345 *** https://bugs.launchpad.net/bugs/1156345 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1156345, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1292436/+attachment/4023708/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1292436/+attachment/4023710/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1292436/+attachment/4023718/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1292436/+attachment/4023719/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1292436/+attachment/4023720/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1292436/+attachment/4023722/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1292436/+attachment/4023723/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1156345 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1292436 Title: NetworkManager crashed with SIGSEGV in nm_active_connection_get_state() Status in “network-manager” package in Ubuntu: New Bug description: This happens on every boot. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Thu Mar 13 21:41:44 2014 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-01-07 (66 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) IpRoute: default via 10.8.0.13 dev tun0 proto static 10.2.69.0/24 dev wlan0 proto kernel scope link src 10.2.69.190 metric 9 10.8.0.0/24 via 10.8.0.13 dev tun0 proto static 10.8.0.13 dev tun0 proto kernel scope link src 10.8.0.14 108.171.208.18 via 10.2.69.1 dev wlan0 proto static NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: NetworkManager ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x4530b5 : mov 0x28(%rax),%eax PC (0x004530b5) ok source "0x28(%rax)" (0x0028) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: nm_active_connection_get_state () ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in nm_active_connection_get_state() UpgradeStatus: Upgraded to trusty on 2014-03-11 (3 days ago) UserGroups: nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1292436/+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 1284553] Re: [ivb] Desktop fails to display on boot up - innoculous GPU, need bisect
** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1284553 Title: [ivb] Desktop fails to display on boot up - innoculous GPU, need bisect Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: Frequently on boot the desktop is not displayed and is just black. I am able to switch to vt1 and run 'sudo service lightdm restart', and sometimes the desktop appears correctly, but more often than not I just get the black screen again. Seems like a race condition. After recent updates the problem seems to be 100% reproducible and I am unable to get a working desktop at all. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Feb 25 09:42:16 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed DuplicateSignature: GPU lockup IPEHR: 0x7a02 IPEHR: 0x0b140001 Ubuntu 14.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7850] InstallationDate: Installed on 2014-01-29 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140128) InterpreterPath: /usr/bin/python3.4 MachineType: NOVATECH LTD BB-47704 ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-12-generic.efi.signed root=UUID=4b2756ef-c935-44cb-8419-e3013cc7c0d3 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: GPU lockup IPEHR: 0x7a02 IPEHR: 0x0b140001 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: 7356821-005 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.4:bd09/18/2013:svnNOVATECHLTD:pnBB-47704:pvr1.0:rvnMSI:rnZ87-G41PCMate(MS-7850):rvr1.0:cvnNOVATECHLTD:ct3:cvr1.0: dmi.product.name: BB-47704 dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Feb 25 09:42:08 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 0 vendor GSM xserver.version: 2:1.15.0-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1284553/+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 1292442] Re: lockscreen: menus interactable but render behind the lockscreen
** Changed in: unity (Ubuntu) Importance: Undecided => High ** Changed in: unity (Ubuntu) Status: New => Confirmed ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Importance: Undecided => High -- 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/1292442 Title: lockscreen: menus interactable but render behind the lockscreen Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: With the latest unity update the lock screen is now in front of the indicator menus which are rendered on click, but behind the lock panel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 14 09:55:44 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (266 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-10 (123 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292442/+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 1292446] Re: lockscreen: on autolock on suspend the fade does not complete before suspend leaving desktop partially visible for a short period on resume
** Changed in: unity (Ubuntu) Importance: Undecided => High ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Importance: Undecided => High -- 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/1292446 Title: lockscreen: on autolock on suspend the fade does not complete before suspend leaving desktop partially visible for a short period on resume Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: When auto-locking as part of a suspend operation the lock screen still fades to opaque, this takes seconds and mid fade the suspend occurs. This means that on waking the machine the fade is still occurring and the desktop is partially visible potentially exposing information protected by the lock. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 14 10:02:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (266 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-10 (123 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292446/+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 1276379] Re: fglrx-installer 2:13.101-0ubuntu0.0.1 fails with some "legacy" devices (Radeon HD 2000 3000 4000)
Confirmed with: # lspci | grep -i vga 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96 [Mobility Radeon HD 4650/5165] # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.4 LTS Release:12.04 Codename: precise #uname -a Linux dell-studio-1747 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux To solve the problem, we have to: - download manually the proposed driver by amd official website on http://support.amd.com/fr-fr/download/ (in my case, the proposed driver is: amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run) - extract and run: amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run --listpkg # and find in the list sudo amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run --buildandinstallpkg - fix apt marks # Because this is the higher driver version we can expect for a 4xxx series sudo apt-mark hold fglrx sudo apt-mark hold fglrx-amdcccle The proposed driver by amd is 8.970 and it works like a charm. -- 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/1276379 Title: fglrx-installer 2:13.101-0ubuntu0.0.1 fails with some "legacy" devices (Radeon HD 2000 3000 4000) Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: [Updated description] Update of the fglrx-driver (version 2:13.101-0ubuntu0.0.1 on 2014-02-03) brought by update-manager (through ubuntu-updates repos) on Precise doesn't work on some "legacy" devices. The main symptom is the fallback to unity-2D. This bug seems target only Precise with no LTS Enablement Stack activated, in other words with Linux 3.2.x and XServer 7.6. ==> please : confirm or infirm using: uname -rm apt-cache policy xserver-xorg It may be in relation with #1058040, about non-support for Radeon [Mobility] HD 2xxx, 3xxx, 4xxx on Ubuntu 12.10 and higher. __ 1)Description:Ubuntu 12.04.4 LTS Release: 12.04 Architecture: amd64 2) apt-cache policy fglrx fglrx-amdcccle fglrx: Installé : 2:13.101-0ubuntu0.0.1 Candidat : 2:13.101-0ubuntu0.0.1 Table de version : *** 2:13.101-0ubuntu0.0.1 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/restricted amd64 Packages 100 /var/lib/dpkg/status 2:8.960-0ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise/restricted amd64 Packages fglrx-amdcccle: Installé : 2:13.101-0ubuntu0.0.1 Candidat : 2:13.101-0ubuntu0.0.1 3) I expected that the driver : - set up - work 4) It did'nt work : - Ubuntu was very slow - Unity fall in Unity-2d mode - when I taped CTRL+SUPER, desktops appears blue - fglrx-amdcccle failed - fans were turning at a high speed - lots of warning messages as described bellow 5) Workaround I had to downgrade manually the driver to the old 8.960, which works without problem. You could do it using Synaptics our using the CLI I tried to do an "apt-get remove fglrx fglrx-amdcccle" but apt-get gaves me fglrx-updates in replacement , with the same issues. I experimented fglrx-update some months (a year?) ago with similar problems, but at that time it was a conscient experimentation. The 13.101-0ubuntu0.0.1 could maybe stay in fglrx-updates, and no fglrx ? ~$ sudo aticonfig aticonfig: No supported adapters detected ~$ lspci -nn | grep VGA02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v] [1002:9553] ~$ grep /drivers/ /var/log/Xorg.0.log [26.888] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so [27.015] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so [27.016] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so [27.017] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [27.018] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [27.019] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [27.122] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so ~$ dmesg | grep fglrx [ 28.612217] [fglrx] Maximum main memory to use for locked dma buffers: 3657 MBytes. [ 28.613015] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 28.613021] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed [ 28.775649] [fglrx] Maximum main memory to use for locked dma buffers: 3657 MBytes. [ 28.776032] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 28.776036] [fglrx:firegl_init_module] *ERROR* f
[Desktop-packages] [Bug 1292440] Re: I have two network indicators
Thank you for your bug report, that's not really a bug though, unity8 is using a new indicator which is not feature complete yet for the desktop. When you install unity8 you get both installed and loaded. Reassigning there, the desktop profile should probably be commented from that one ** Package changed: unity (Ubuntu) => indicator-network (Ubuntu) -- 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/1292440 Title: I have two network indicators Status in “indicator-network” package in Ubuntu: New Bug description: I have two network indicators in the indicator panel. One looks like the one in Ubuntu 13.10, the other one like the one in the current Ubuntu Touch. I installed unity-desktop-session-mir. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 14 10:47:20 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-18 (146 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-05 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1292440/+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 1292451] [NEW] screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked
Public bug reported: Steps to reproduce: 1. Set screen-off timeout to 1 minute 2. Configure screen to lock immediately when screen goes off. 3. Lock screen manually (Ctrl+Alt+L) 4. Wait for 1 minute 5. Notice that screen doesn't turn off 6. Unlock screen 7. Wait a couple of seconds (~10 or so) 8. Notice that screen re-locks itself. 9. Repeat steps 6-7 and notice that the screen doesn't re-lock itself this time. There are two bugs described here: 1. Screen does not shut off if the screen is locked manually before the idle timer (see step 5). 2. Screen re-locks itself after unlocking if the idle timer goes off while the screen is locked (see step 7). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 18:19:26 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1292451 Title: screensaver re-locks itself after unlocking if the configured screen- off timer goes off while screen is locked Status in “gnome-screensaver” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: Steps to reproduce: 1. Set screen-off timeout to 1 minute 2. Configure screen to lock immediately when screen goes off. 3. Lock screen manually (Ctrl+Alt+L) 4. Wait for 1 minute 5. Notice that screen doesn't turn off 6. Unlock screen 7. Wait a couple of seconds (~10 or so) 8. Notice that screen re-locks itself. 9. Repeat steps 6-7 and notice that the screen doesn't re-lock itself this time. There are two bugs described here: 1. Screen does not shut off if the screen is locked manually before the idle timer (see step 5). 2. Screen re-locks itself after unlocking if the idle timer goes off while the screen is locked (see step 7). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 18:19:26 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292451/+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 1292451] Re: screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked
** Attachment added: "Screenshot of Brightness&Lock settings" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292451/+attachment/4023757/+files/Screenshot%20from%202014-03-14%2018%3A32%3A31.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292451 Title: screensaver re-locks itself after unlocking if the configured screen- off timer goes off while screen is locked Status in “gnome-screensaver” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: Steps to reproduce: 1. Set screen-off timeout to 1 minute 2. Configure screen to lock immediately when screen goes off. 3. Lock screen manually (Ctrl+Alt+L) 4. Wait for 1 minute 5. Notice that screen doesn't turn off 6. Unlock screen 7. Wait a couple of seconds (~10 or so) 8. Notice that screen re-locks itself. 9. Repeat steps 6-7 and notice that the screen doesn't re-lock itself this time. There are two bugs described here: 1. Screen does not shut off if the screen is locked manually before the idle timer (see step 5). 2. Screen re-locks itself after unlocking if the idle timer goes off while the screen is locked (see step 7). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 18:19:26 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292451/+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 1292451] Re: screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked
I'm also adding unity to this bug as this only appeared after a gnome- screensaver upgrade that enabled the unity screenlock. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292451 Title: screensaver re-locks itself after unlocking if the configured screen- off timer goes off while screen is locked Status in “gnome-screensaver” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: Steps to reproduce: 1. Set screen-off timeout to 1 minute 2. Configure screen to lock immediately when screen goes off. 3. Lock screen manually (Ctrl+Alt+L) 4. Wait for 1 minute 5. Notice that screen doesn't turn off 6. Unlock screen 7. Wait a couple of seconds (~10 or so) 8. Notice that screen re-locks itself. 9. Repeat steps 6-7 and notice that the screen doesn't re-lock itself this time. There are two bugs described here: 1. Screen does not shut off if the screen is locked manually before the idle timer (see step 5). 2. Screen re-locks itself after unlocking if the idle timer goes off while the screen is locked (see step 7). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 18:19:26 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292451/+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 1292365] Re: fglrx 2:13.251-0ubuntu1: fglrx kernel module failed to build
*** This bug is a duplicate of bug 1288404 *** https://bugs.launchpad.net/bugs/1288404 /var/lib/dkms/fglrx/13.251/build/2.6.x/firegl_public.c:1758:5: error: incompatible types when returning type ‘kuid_t’ but ‘KCL_TYPE_Uid’ was expected ** This bug has been marked a duplicate of bug 1288404 fglrx 2:13.350-0ubuntu1: fglrx kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘KCL_TYPE_Uid’ was expected] -- 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/1292365 Title: fglrx 2:13.251-0ubuntu1: fglrx kernel module failed to build Status in “fglrx-installer” package in Ubuntu: New Bug description: I have just installed 14.04 today. I attempted to install the AMD drivers from their site (stable verison.) These appeared to install, but there were issues, so i removed them and attempted to install the fglrx-updates package twice. It looks like it installed both times (I did a --purge after the first.) However, the normal commands: aticonfig, amdccle, fglrxinfo do not work. Bash cannot find these files. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [7.182243] tg3 :04:00.0 eth1: Flow control is on for TX and on for RX [7.182245] tg3 :04:00.0 eth1: EEE is enabled [7.184333] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready DKMSKernelVersion: 3.13.0-17-generic Date: Fri Mar 14 01:56:34 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350, 3.13.0-17-generic, x86_64: installed DuplicateSignature: dkms:fglrx:2:13.251-0ubuntu1:/var/lib/dkms/fglrx/13.251/build/2.6.x/firegl_public.c:1758:5: error: incompatible types when returning type ‘kuid_t’ but ‘KCL_TYPE_Uid’ was expected GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:2730] MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageVersion: 2:13.251-0ubuntu1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=84164116-5d70-48c7-90af-77b020ac38ce ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: fglrx 2:13.251-0ubuntu1: fglrx kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: 990FX Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd10/15/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn990FXExtreme4:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc3-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Mar 14 02:02:40 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1292365/+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 1292412] Re: Keyboard layout is always English(!)
it seems like unity-settings-daemon's keyboard plugin is not loaded, could you get the debug command output? -- 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/1292412 Title: Keyboard layout is always English(!) Status in “gnome-control-center” package in Ubuntu: Invalid Status in “gnome-session” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: Invalid Bug description: Keyboard layout is always English, no matter that I select a different language in the selector. It is English even if I remove English from the layouts. And layout switching via hot key doesn't work no matter what the hot key is. Both issues are fresh from upgrades that I made today: Start-Date: 2014-03-14 09:25:48 Upgrade: initscripts:amd64 (2.88dsf-41ubuntu5, 2.88dsf-41ubuntu6), pciutils:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), aptdaemon-data:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), ubuntu-session:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), unity-greeter:amd64 (14.04.3-0ubuntu2, 14.04.4-0ubuntu1), libqt4-xml:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-network:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libegl1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libqt4-sql-mysql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libopenvg1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), gnome-session-common:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libfreetype6-dev:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), gnome-session-bin:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libqt4-sql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), isc-dhcp-common:amd64 (4.2.4-7ubuntu8, 4.2.4-7ubuntu9), libegl1-mesa-drivers:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), firefox-locale-en:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), qdbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqtcore4:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-qt3support:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-svg:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-dbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-xmlpatterns:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-sql-sqlite:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-opengl:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), qt4-qtconfig:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libgl1-mesa-dri:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libgl1-mesa-dri:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), unity:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), libunity-core-6.0-9:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), ubuntu-drivers-common:amd64 (0.2.89.6, 0.2.90), firefox:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), libqt4-script:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libfreetype6:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), libfreetype6:i386 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), python-apt:amd64 (0.9.1ubuntu1, 0.9.3.2), libgs9-common:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), ubuntu-release-upgrader-gtk:amd64 (0.216, 0.216.1), libido3-0.1-0:amd64 (13.10.0+14.04.20140213-0ubuntu1, 13.10.0+14.04.20140313-0ubuntu1), libglib2.0-0:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), libglib2.0-0:i386 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), xserver-xorg-core:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), libglapi-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libglapi-mesa:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libpci3:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), gnome-screensaver:amd64 (3.6.1-0ubuntu10, 3.6.1-0ubuntu11), unity-services:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), python-aptdaemon.gtk3widgets:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), bash-completion:amd64 (2.1-2ubuntu3, 2.1-2ubuntu4), xserver-common:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), ghostscript-x:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), libunity-control-center1:amd64 (14.04.3+14.04.20140310-0ubuntu1, 14.04.3+14.04.20140313-0ubuntu1), libglib2.0-data:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), python3-aptdaemon.gtk3widgets:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), libgles2-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), usb-creator-common:amd64 (0.2.54, 0.2.55), libgl1-mesa-glx:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libgl1-mesa-glx:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libxatracker2:
[Desktop-packages] [Bug 1287352] Re: screen does not wake after suspend always, intel
Are you sure it is just the backlight that is off? (Does changing its brightness restore the display?) Can you please attach a drm.debug=6 dmesg from across the suspend & resume? ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1287352 Title: screen does not wake after suspend always, intel Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: Hardware is *-display:0 description: VGA compatible controller product: Mobile GM965/GL960 Integrated Graphics Controller (primary) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 03 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 thi s is a problem after upgradeing from 13.10 to 14.04 beta. System has latest 14.04 updates After suspend, the screen does not resume. There is no backlighting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1287352/+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 1288404] Re: fglrx 2:13.350-0ubuntu1: fglrx kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘KCL_TYPE_Uid’ was expected]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fglrx-installer (Ubuntu) Status: New => Confirmed -- 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/1288404 Title: fglrx 2:13.350-0ubuntu1: fglrx kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘KCL_TYPE_Uid’ was expected] Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: I tried to get fglrx working together with linux- image-3.14.0-031400rc5-generic_3.14.0-031400rc5.201403022235_amd64 trying to resolve another issue. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx 2:13.350-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 NonfreeKernelModules: wl fglrx .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 3.14.0-031400rc5-generic Date: Wed Mar 5 21:12:50 2014 DistUpgraded: 2014-02-24 10:04:39,998 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: dkms:fglrx:2:13.350-0ubuntu1:/var/lib/dkms/fglrx/13.350/build/2.6.x/firegl_public.c:1764:5: error: incompatible types when returning type ‘kuid_t’ but ‘KCL_TYPE_Uid’ was expected GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1557] InstallationDate: Installed on 2014-02-21 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUSTeK COMPUTER INC. U38N PackageVersion: 2:13.350-0ubuntu1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-15-generic.efi.signed root=UUID=d2bc6ca7-191c-4302-aeb2-9cbc60ed7b03 ro nomodeset xforcevesa SourcePackage: fglrx-installer Title: fglrx 2:13.350-0ubuntu1: fglrx kernel module failed to build UpgradeStatus: Upgraded to trusty on 2014-02-24 (9 days ago) dmi.bios.date: 05/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U38N.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U38N dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU38N.209:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnU38N:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnU38N:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: U38N dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11+14.04.20140303-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc3-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Mar 5 21:17:50 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1288404/+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
Re: [Desktop-packages] [Bug 1287352] [NEW] screen does not wake after suspend always, intel
My bug message is bad. The bug reporting indicates that it is actually a kernel panic. Please close this bug. automatic bug reporting was fixed when I changed the login user to belong to group sudo. see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1289721 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1290787 which are still marked incomplete although I have done what was asked and confirmed that various mainline kernels show the bug. ** Changed in: xserver-xorg-video-intel (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1287352 > > Title: > screen does not wake after suspend always, intel > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1287352/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1287352 Title: screen does not wake after suspend always, intel Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: Hardware is *-display:0 description: VGA compatible controller product: Mobile GM965/GL960 Integrated Graphics Controller (primary) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 03 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 thi s is a problem after upgradeing from 13.10 to 14.04 beta. System has latest 14.04 updates After suspend, the screen does not resume. There is no backlighting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1287352/+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 1292463] [NEW] rhythmbox UI issue white separator betwen Play and Next buttons
Public bug reported: Latest updates of Ubuntu 14.04, this bug is reproducible on VM and real hardware Steps to reproduce: 1. Open Rhythmbox and verify buttons Actual result: White separator shown between Play and Next buttons (see screenshot attached) Expected result: The same separator should be as between Prewious and Play buttons ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Attachment added: "rhythmboxButtons.png" https://bugs.launchpad.net/bugs/1292463/+attachment/4023772/+files/rhythmboxButtons.png -- 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/1292463 Title: rhythmbox UI issue white separator betwen Play and Next buttons Status in “compiz” package in Ubuntu: New Bug description: Latest updates of Ubuntu 14.04, this bug is reproducible on VM and real hardware Steps to reproduce: 1. Open Rhythmbox and verify buttons Actual result: White separator shown between Play and Next buttons (see screenshot attached) Expected result: The same separator should be as between Prewious and Play buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1292463/+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 1274690] Re: gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock()
Thanks, that seems a bug in the virtualbox drivers ** Information type changed from Private to Public ** Package changed: gnome-control-center (Ubuntu) => virtualbox (Ubuntu) -- 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/1274690 Title: gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock() Status in “virtualbox” package in Ubuntu: Confirmed Bug description: controle center just crash after add account of gadugadu and try to close ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu50 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Thu Jan 30 20:35:34 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2014-01-30 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha i386 (20140121.1) ProcCmdline: /usr/bin/gnome-control-center.real --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb6c1d036 <__GI___pthread_mutex_lock+22>: mov 0xc(%esi),%eax PC (0xb6c1d036) ok source "0xc(%esi)" (0x1070) not located in a known VMA region (needed readable region)! destination "%eax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: __GI___pthread_mutex_lock (mutex=0x1064) at ../nptl/pthread_mutex_lock.c:66 crLockMutex () from /usr/lib/VBoxOGLcrutil.so crHashtableLock () from /usr/lib/VBoxOGLcrutil.so ?? () from /usr/lib/i386-linux-gnu/dri/vboxvideo_dri.so rtThreadMain () from /usr/lib/i386-linux-gnu/dri/vboxvideo_dri.so Title: gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1274690/+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 1291623] Re: gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock()
*** This bug is a duplicate of bug 1274690 *** https://bugs.launchpad.net/bugs/1274690 ** This bug has been marked a duplicate of private bug 1274690 ** Information type changed from Private to Public -- 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/1291623 Title: gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock() Status in “gnome-control-center” package in Ubuntu: New Bug description: Hi there! I experienced this bug while opening gnome controlcenter (brightness and lock). The gui would open and worked, but I was showed a prompt to file this bug. Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 gnome-control-center: Installiert: 1:3.6.3-0ubuntu53 Installationskandidat: 1:3.6.3-0ubuntu53 Versionstabelle: *** 1:3.6.3-0ubuntu53 0 500 http://ftp.hawo.stw.uni-erlangen.de/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 12 21:16:26 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2014-02-28 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcCmdline: /usr/bin/gnome-control-center.real screen ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f71eb43c414 <__GI___pthread_mutex_lock+4>: mov 0x10(%rdi),%esi PC (0x7f71eb43c414) ok source "0x10(%rdi)" (0x20d8) not located in a known VMA region (needed readable region)! destination "%esi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66 ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so start_thread (arg=0x7f71c9453700) at pthread_create.c:312 Title: gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1291623/+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 1289926] Re: gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock()
*** This bug is a duplicate of bug 1274690 *** https://bugs.launchpad.net/bugs/1274690 ** This bug has been marked a duplicate of private bug 1274690 ** Information type changed from Private to Public -- 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/1289926 Title: gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock() Status in “gnome-control-center” package in Ubuntu: New Bug description: I don't know any details. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 9 03:21:55 2014 ExecutablePath: /usr/bin/gnome-control-center.real InstallationDate: Installed on 2014-03-08 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcCmdline: /usr/bin/gnome-control-center.real network SegvAnalysis: Segfault happened at: 0x7f812b6bd414 <__GI___pthread_mutex_lock+4>: mov 0x10(%rdi),%esi PC (0x7f812b6bd414) ok source "0x10(%rdi)" (0x20d8) not located in a known VMA region (needed readable region)! destination "%esi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66 ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/vboxvideo_dri.so start_thread (arg=0x7f8102371700) at pthread_create.c:312 Title: gnome-control-center.real crashed with SIGSEGV in __GI___pthread_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1289926/+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 1292467] [NEW] Lightdm on dual-screens can break 3D acceleration
Public bug reported: When booting with two screens (internal LVDS and VGA), lightdm comes up in a mode where it displays separate screen content on both displays (so no mirror mode). These screens seem to be arranged side-by-side regardless of the fact that (like in my case) the combined width can be greater than 2048 and that is not supported with 3D acceleration at least on that older i945GME graphics. This results in very poor graphics performance and compiz using a lot of cpu cycles (which are rather limited on this Atom N270 anyways). Even worse, this does not get resolved when changing the setup in system settings to either only having one screen active or arranging them on top of each other). Booting with only the internal screen and then plugging in the external one after login seems to handle this better (although I probably need to remove any previous config to get into a kind of vanilla state again). Also it seems to be ok when I had the dual monitor boot and lightdm coming up side-by-side, when unplugging the external monitor before logging in. So logging in with the dual-monitor side-by-side setup causes 3D acceleration to be broken for that session (even when it switches to single monitor by configuration). However going back to lightdm, unplugging the external monitor, then log in and reconnect the external monitor is ok. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- 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/1292467 Title: Lightdm on dual-screens can break 3D acceleration Status in “lightdm” package in Ubuntu: New Bug description: When booting with two screens (internal LVDS and VGA), lightdm comes up in a mode where it displays separate screen content on both displays (so no mirror mode). These screens seem to be arranged side- by-side regardless of the fact that (like in my case) the combined width can be greater than 2048 and that is not supported with 3D acceleration at least on that older i945GME graphics. This results in very poor graphics performance and compiz using a lot of cpu cycles (which are rather limited on this Atom N270 anyways). Even worse, this does not get resolved when changing the setup in system settings to either only having one screen active or arranging them on top of each other). Booting with only the internal screen and then plugging in the external one after login seems to handle this better (although I probably need to remove any previous config to get into a kind of vanilla state again). Also it seems to be ok when I had the dual monitor boot and lightdm coming up side-by-side, when unplugging the external monitor before logging in. So logging in with the dual-monitor side-by-side setup causes 3D acceleration to be broken for that session (even when it switches to single monitor by configuration). However going back to lightdm, unplugging the external monitor, then log in and reconnect the external monitor is ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1292467/+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 1063682] Re: Screensaver settings GUI is confusing
The text should indeed be reworked, "after a further:" would be a step. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to activity-log-manager in Ubuntu. https://bugs.launchpad.net/bugs/1063682 Title: Screensaver settings GUI is confusing Status in Ayatana Design: New Status in “activity-log-manager” package in Ubuntu: Triaged Status in “gnome-control-center” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: Triaged Bug description: The settings GUI for screensaver settings is confusing. Right now, I see: - Turn off the screen after: - Lock the screen after: Lock the screen has an option for "Screen turns off", and time internals. It never states that it'll start the countdown for the lock AFTER the screen's been turned off and if appropriate the time interval has past. The lock part's string should be changed to: "Lock the screen after screen turns off and idle for": "Immediate", "30 seconds", etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1063682/+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 1063682] Re: Screensaver settings GUI is confusing
** Also affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: unity-control-center (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1063682 Title: Screensaver settings GUI is confusing Status in Ayatana Design: New Status in “activity-log-manager” package in Ubuntu: Triaged Status in “gnome-control-center” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: Triaged Bug description: The settings GUI for screensaver settings is confusing. Right now, I see: - Turn off the screen after: - Lock the screen after: Lock the screen has an option for "Screen turns off", and time internals. It never states that it'll start the countdown for the lock AFTER the screen's been turned off and if appropriate the time interval has past. The lock part's string should be changed to: "Lock the screen after screen turns off and idle for": "Immediate", "30 seconds", etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1063682/+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 1106283] Re: [13.04, 13.10, 14.04] Nautilus crashed with SIGABRT in g_assertion_message() when trying to open file/folder's property dialog as root.
** Summary changed:
- [13.04]nautilus crashed with SIGABRT in g_assertion_message() when trying to
open file/folder's property dialog as root where file/folder belongs to user
with Unicode CJK name.
+ [13.04, 13.10, 14.04] Nautilus crashed with SIGABRT in g_assertion_message()
when trying to open file/folder's property dialog as root.
--
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/1106283
Title:
[13.04, 13.10, 14.04] Nautilus crashed with SIGABRT in
g_assertion_message() when trying to open file/folder's property
dialog as root.
Status in Nautilus:
New
Status in “nautilus” package in Ubuntu:
In Progress
Bug description:
I tried to move a file(which is the lastpass installer tarball
lplinux.tar.bz2 from http://lastpass.com ) from another user's home directory
to mine download folder(Which as been converted to "~/下載" in Traditional
Chinese), then tried to change its UID & GID to me...as root
UID changed successfully
When I clicked on the GID selection box...it hangs for a few second and
crashed:(
To move further, I tried to open the property dialog of my home
directory(/home/Vdragon)... crashed too.
It seems that any of file/directory belongs to me is affected. 100%
reproducible.
Before nautilus crashed, a error window showes instantly(then vanished).
I tried to capture it as the attachment.
I suspect this issue is related to I used UTF-8 Chinese characters("林博仁") as
my ... name
$ getent passwd Vdragon
Vdragon:x:1001:1001:林博仁,,,:/home/Vdragon:/bin/bash
then nautilus tried to grab my ...name for displaying UID, GID of my
file/folder...then BANG
There will be no issue if I don't execute nautilus as root then see my
file's properties.(however nautilus won't try to show the UID refers
to who in this case)
Backtrace(since this is my first time doing this, please tell me if I missed
something; ):
#0 0x7f675f0aae35 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:63
#1 0x7f675f0ae498 in __GI_abort () at abort.c:90
#2 0x7f675fbd9a66 in g_assertion_message (domain=domain@entry=0x0,
file=file@entry=0x4fd704 "nautilus-properties-window.c",
line=line@entry=1836,
func=func@entry=0x4fe770 <__PRETTY_FUNCTION__.50289>
"schedule_owner_change_timeout", message=)
at /build/buildd/glib2.0-2.35.4/./glib/gtestutils.c:1892
#3 0x7f675fbd9fc4 in g_assertion_message_expr (domain=domain@entry=0x0,
file=file@entry=0x4fd704 "nautilus-properties-window.c",
line=line@entry=1836,
func=func@entry=0x4fe770 <__PRETTY_FUNCTION__.50289>
"schedule_owner_change_timeout", expr=expr@entry=0x4f73d8 "NAUTILUS_IS_FILE
(file)")
at /build/buildd/glib2.0-2.35.4/./glib/gtestutils.c:1903
#4 0x0045f59e in schedule_owner_change_timeout (window=0x2954050,
window@entry=)
at nautilus-properties-window.c:1836
#5 0x7f675fbb81ab in g_timeout_dispatch (source=source@entry=0x2a37e80,
callback=, user_data=)
at /build/buildd/glib2.0-2.35.4/./glib/gmain.c:4095
#6 0x7f675fbb75a5 in g_main_dispatch (context=0x230a5d0)
at /build/buildd/glib2.0-2.35.4/./glib/gmain.c:2784
---Type to continue, or q to quit---+
#7 g_main_context_dispatch (context=context@entry=0x230a5d0)
at /build/buildd/glib2.0-2.35.4/./glib/gmain.c:3288
#8 0x7f675fbb78e8 in g_main_context_iterate (
context=context@entry=0x230a5d0, block=block@entry=1,
dispatch=dispatch@entry=1, self=)
at /build/buildd/glib2.0-2.35.4/./glib/gmain.c:3359
#9 0x7f675fbb79a4 in g_main_context_iteration (context=0x230a5d0,
context@entry=0x0, may_block=may_block@entry=1)
at /build/buildd/glib2.0-2.35.4/./glib/gmain.c:3420
#10 0x7f676015e9cc in g_application_run (application=0x22d1030,
argc=argc@entry=1, argv=argv@entry=0x7fffd6d42948)
at /build/buildd/glib2.0-2.35.4/./gio/gapplication.c:1620
#11 0x0042b6cb in main (argc=1, argv=0x7fffd6d42948)
at nautilus-main.c:103
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
Uname: Linux 3.8.0-1-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Sun Jan 27 02:42:56 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry'
b"'927x1027+66+24'"
InstallationDate: Installed on 2013-01-26 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130126)
MarkForUpload: True
ProcCmdline: nautilus
Signal: 6
SourcePackage: nautilus
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux
[Desktop-packages] [Bug 1292412] Re: Keyboard layout is always English(!)
Here's the `unity-settings-daemon --replace --debug` output but it is not from the first run because I didn't capture the output on that run by mistake. Things worked out once I did that. The issue is no longer present. I'll reopen if this occurs again. ** Attachment added: "unity-settings-daemon --replace --debug" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1292412/+attachment/4023776/+files/unity-settings-daemon-replace-debug -- 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/1292412 Title: Keyboard layout is always English(!) Status in “gnome-control-center” package in Ubuntu: Invalid Status in “gnome-session” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: Invalid Bug description: Keyboard layout is always English, no matter that I select a different language in the selector. It is English even if I remove English from the layouts. And layout switching via hot key doesn't work no matter what the hot key is. Both issues are fresh from upgrades that I made today: Start-Date: 2014-03-14 09:25:48 Upgrade: initscripts:amd64 (2.88dsf-41ubuntu5, 2.88dsf-41ubuntu6), pciutils:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), aptdaemon-data:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), ubuntu-session:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), unity-greeter:amd64 (14.04.3-0ubuntu2, 14.04.4-0ubuntu1), libqt4-xml:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-network:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libegl1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libqt4-sql-mysql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libopenvg1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), gnome-session-common:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libfreetype6-dev:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), gnome-session-bin:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libqt4-sql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), isc-dhcp-common:amd64 (4.2.4-7ubuntu8, 4.2.4-7ubuntu9), libegl1-mesa-drivers:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), firefox-locale-en:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), qdbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqtcore4:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-qt3support:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-svg:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-dbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-xmlpatterns:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-sql-sqlite:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-opengl:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), qt4-qtconfig:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libgl1-mesa-dri:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libgl1-mesa-dri:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), unity:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), libunity-core-6.0-9:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), ubuntu-drivers-common:amd64 (0.2.89.6, 0.2.90), firefox:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), libqt4-script:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libfreetype6:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), libfreetype6:i386 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), python-apt:amd64 (0.9.1ubuntu1, 0.9.3.2), libgs9-common:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), ubuntu-release-upgrader-gtk:amd64 (0.216, 0.216.1), libido3-0.1-0:amd64 (13.10.0+14.04.20140213-0ubuntu1, 13.10.0+14.04.20140313-0ubuntu1), libglib2.0-0:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), libglib2.0-0:i386 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), xserver-xorg-core:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), libglapi-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libglapi-mesa:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libpci3:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), gnome-screensaver:amd64 (3.6.1-0ubuntu10, 3.6.1-0ubuntu11), unity-services:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), python-aptdaemon.gtk3widgets:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), bash-completion:amd64 (2.1-2ubuntu3, 2.1-2ubuntu4), xserver-common:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), ghostscript-x:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), libunity-control-center1:amd64 (14.04.3+14.04.20140310-0ubuntu1, 14.04.3+14.04.20140313-0ubuntu1), libglib2.0-data:amd64
[Desktop-packages] [Bug 1253620]
Same problem. Kubuntu 13.10 Libreoffice 4.1.5 (PPA) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1253620 Title: Can't open a LibreOffice native file via CIFS share Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: Problem description: Can't open only native LibreOffice files from remote (CIFS) share with Ubuntu 12.04 and LibreOffice 4.1.3.2 (from ppa). System informations: Distributor ID: Ubuntu Description: Ubuntu 12.04.3 LTS Release: 12.04 Codename: precise LibreOffice package from ppa:libreoffice/ppa: 1:4.1.3~rc2-0ubuntu1~precise1~ppa1 Steps to reproduce: 1. Open LibreOffice 2. Select Open File from file menu 3. Select the remote share folder 4. Click to open the file Current behavior: LibreOffice trys to recover the remote file and fails. Expected behavior: LibreOffice opens the remote file correctly. Alternatives steps: 1. Open the remote path via Nautilus 2. Double click on remote LibreOffice native files Current behavior2: LibreOffice trys to recover the remote file and fails. Expected behavior2: LibreOffice opens the remote file correctly. Notes: * Remote and local MS files are opened correctly. * The problems with LibreOffice native files disappear if copying the remote files in a local path Here a workaround: sed -i 's/X-GIO-NoFuse=true/#X-GIO-NoFuse=true/' /usr/share/applications/libreoffice-* No problem present on: Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy with LibreOffice: 1:4.1.3~rc2-0ubuntu1~saucy1~ppa3 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1253620/+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 1253620]
Same problem on Ubuntu 12.04/64 with LibreOffice 4.2.1.1 (ppa) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1253620 Title: Can't open a LibreOffice native file via CIFS share Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: Problem description: Can't open only native LibreOffice files from remote (CIFS) share with Ubuntu 12.04 and LibreOffice 4.1.3.2 (from ppa). System informations: Distributor ID: Ubuntu Description: Ubuntu 12.04.3 LTS Release: 12.04 Codename: precise LibreOffice package from ppa:libreoffice/ppa: 1:4.1.3~rc2-0ubuntu1~precise1~ppa1 Steps to reproduce: 1. Open LibreOffice 2. Select Open File from file menu 3. Select the remote share folder 4. Click to open the file Current behavior: LibreOffice trys to recover the remote file and fails. Expected behavior: LibreOffice opens the remote file correctly. Alternatives steps: 1. Open the remote path via Nautilus 2. Double click on remote LibreOffice native files Current behavior2: LibreOffice trys to recover the remote file and fails. Expected behavior2: LibreOffice opens the remote file correctly. Notes: * Remote and local MS files are opened correctly. * The problems with LibreOffice native files disappear if copying the remote files in a local path Here a workaround: sed -i 's/X-GIO-NoFuse=true/#X-GIO-NoFuse=true/' /usr/share/applications/libreoffice-* No problem present on: Distributor ID: Ubuntu Description: Ubuntu 13.10 Release: 13.10 Codename: saucy with LibreOffice: 1:4.1.3~rc2-0ubuntu1~saucy1~ppa3 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1253620/+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 1292225] Re: Lockscreen focus lost when switcher is open then holding Alt down and pressing Ctrl+L
This is still reproduceable even with the fix. ** Changed in: unity (Ubuntu) Status: Fix Released => In Progress -- 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/1292225 Title: Lockscreen focus lost when switcher is open then holding Alt down and pressing Ctrl+L Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Lockscreen focus lost when switcher is open then holding Alt down and pressing Ctrl+L To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292225/+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 1285424] Re: [MIR] hunspell-fr
in main now. ** Changed in: hunspell-fr (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hunspell-fr in Ubuntu. https://bugs.launchpad.net/bugs/1285424 Title: [MIR] hunspell-fr Status in “hunspell-fr” package in Ubuntu: Fix Released Bug description: [Availability] Package is in universe. [Rationale] hunspell-fr as a source package replaces parts of the old and mostly unmaintained openoffice.org-dictionaries source pkg. The functionality was already in main, and is just replaced with modern packaging. [Security] Data-only package [Quality Assurance] The package currently has no open bugs on launchpad or Debian PTS and possibly also fixes some old bugs filed against openoffice.org-dictionaries. The package has been explicit taken over for better maintainership. The package has no open lintian warnings and has a watch file. [UI] Doesnt apply [Dependencies] Source package builds in main, binaries install in main. All suggests are in main. [Maintenance] Splitting out -fr from ooo-dicts simplifies maintenance. [Background information] Package splitout for easier maintainership by interested parties. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-fr/+bug/1285424/+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 603402]
*** Bug 712595 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/603402 Title: Thunderbird incorrectly shows some Gmail archived messages as unread via IMAP Status in Mozilla Thunderbird Mail and News: Confirmed Status in “thunderbird” package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird Steps to reproduce: 1) Wait for a few messages to arrive in Inbox, thus being marked as unread. 2) Mark all of them as read, then archive them. 3) Click on All Mail folder. Actual Results: Only one of recently archived messages is marked as read (usually the newest one), the rest must be marked as read again. Expected Results: All of recently marked as read in Inbox and archived mails should be marked as read in All Mail folder, too. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: thunderbird 3.0.5+build2+nobinonly-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic x86_64 NonfreeKernelModules: wl Architecture: amd64 Date: Fri Jul 9 02:22:30 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/603402/+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 603402]
Guess what, this isn't even limited to Gmail. It happens on my own IMAP server as well. It's running Dovecot on Linux. See bug 712595. Offline and online mode does not help. Changing folders does not work. Only restarting Thunderbird helps for sure. Until then, I regularly see unread or read messages in my inbox at home that I've already read and/or deleted through webmail or smartphone. I also have the impression that it's not a long delay, but instead it's a now or never. Disabling IDLE is definitely no option because that's the future (well, present already) and what everybody else uses successfully. I have the impression that there's some race condition inside Thunderbird that nobody will ever be able to find without rewriting the whole thing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/603402 Title: Thunderbird incorrectly shows some Gmail archived messages as unread via IMAP Status in Mozilla Thunderbird Mail and News: Confirmed Status in “thunderbird” package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird Steps to reproduce: 1) Wait for a few messages to arrive in Inbox, thus being marked as unread. 2) Mark all of them as read, then archive them. 3) Click on All Mail folder. Actual Results: Only one of recently archived messages is marked as read (usually the newest one), the rest must be marked as read again. Expected Results: All of recently marked as read in Inbox and archived mails should be marked as read in All Mail folder, too. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: thunderbird 3.0.5+build2+nobinonly-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic x86_64 NonfreeKernelModules: wl Architecture: amd64 Date: Fri Jul 9 02:22:30 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/603402/+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 327872] Re: Broken support for MPEG-TS: HDV and AVCHD (.mts/.m2ts) files
** Changed in: pitivi Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/327872 Title: Broken support for MPEG-TS: HDV and AVCHD (.mts/.m2ts) files Status in FFmpeg Multimedia Framework: Fix Released Status in The GStreamer Multimedia Framework: Expired Status in One Hundred Papercuts: Invalid Status in Novacut Video Editor: Invalid Status in PiTiVi , Non-linear video editor: Fix Released Status in shared MIME database: Fix Released Status in Totem Movie Player: Invalid Status in VLC media player: Fix Released Status in “gstreamer0.10” package in Ubuntu: Fix Released Status in “shared-mime-info” package in Ubuntu: Confirmed Status in Baltix GNU/Linux: Fix Released Bug description: MPEG transport stream (MPEG-TS) is used for HDV and AVCHD camcorders and as such, Linux users need a way to easily play, edit and see thumbnails of these videos. Video editing on Linux can't get very far when the de facto standard for high-definition video isn't well- supported, especially as more and more cameras are HD out of the box, and the prices for such camcorders are falling. Most of the problem seems to be from the MPEG-TS demuxer in GStreamer [mpegtsdemux] which needs to be fixed or rewritten to support random access better, among other things. To manage notifications about this bug go to: https://bugs.launchpad.net/ffmpeg/+bug/327872/+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 1115669] Re: GNOME Printer Setup Tool: List of discovered printers should better describe duplicate entries
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1115669 Title: GNOME Printer Setup Tool: List of discovered printers should better describe duplicate entries Status in GNOME Control Center: Fix Released Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “unity-control-center” package in Ubuntu: Triaged Bug description: When adding a printer a list of discovered printers is shown. If there are duplicate entries, for example if the same network printer is discovered with different network protocols (LPD, IPP, ...), these entries are usually grouped into one by using the D-Bus service of system-config-printer. system-config-printer groups entries coming from the network connection of the printer and groups entries coming from the USB connection of the printer, but it does not group network results with USB results, as system-config-printer separates them by a tree view. This means that when one connects one printer by both network and USB one gets two entries, one generated from all appearances under the discovered network printers and one from all appearances under the discovered USB printers (and if theis printer does Bluetooth there would be a third entry). Now the g-c-c printer tool lists these entries as -2 This way the user does not know which is the network printer and which is the USB printer. The results dhould look like (USB) (Network) To reproduce connect a printer with both network and USB (or Bluetooth) input by both network and USB, then try to set it up with the preferred connection type. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1115669/+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 1106283] Re: [13.04, 13.10, 14.04] Nautilus crashed with SIGABRT in g_assertion_message() when trying to open file/folder's property dialog as root.
Still present in 14.04 with nautilus 3.10.1. The patch above remains. It
would be nice if this were fixed in the LTS release.
--
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/1106283
Title:
[13.04, 13.10, 14.04] Nautilus crashed with SIGABRT in
g_assertion_message() when trying to open file/folder's property
dialog as root.
Status in Nautilus:
New
Status in “nautilus” package in Ubuntu:
In Progress
Bug description:
I tried to move a file(which is the lastpass installer tarball
lplinux.tar.bz2 from http://lastpass.com ) from another user's home directory
to mine download folder(Which as been converted to "~/下載" in Traditional
Chinese), then tried to change its UID & GID to me...as root
UID changed successfully
When I clicked on the GID selection box...it hangs for a few second and
crashed:(
To move further, I tried to open the property dialog of my home
directory(/home/Vdragon)... crashed too.
It seems that any of file/directory belongs to me is affected. 100%
reproducible.
Before nautilus crashed, a error window showes instantly(then vanished).
I tried to capture it as the attachment.
I suspect this issue is related to I used UTF-8 Chinese characters("林博仁") as
my ... name
$ getent passwd Vdragon
Vdragon:x:1001:1001:林博仁,,,:/home/Vdragon:/bin/bash
then nautilus tried to grab my ...name for displaying UID, GID of my
file/folder...then BANG
There will be no issue if I don't execute nautilus as root then see my
file's properties.(however nautilus won't try to show the UID refers
to who in this case)
Backtrace(since this is my first time doing this, please tell me if I missed
something; ):
#0 0x7f675f0aae35 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:63
#1 0x7f675f0ae498 in __GI_abort () at abort.c:90
#2 0x7f675fbd9a66 in g_assertion_message (domain=domain@entry=0x0,
file=file@entry=0x4fd704 "nautilus-properties-window.c",
line=line@entry=1836,
func=func@entry=0x4fe770 <__PRETTY_FUNCTION__.50289>
"schedule_owner_change_timeout", message=)
at /build/buildd/glib2.0-2.35.4/./glib/gtestutils.c:1892
#3 0x7f675fbd9fc4 in g_assertion_message_expr (domain=domain@entry=0x0,
file=file@entry=0x4fd704 "nautilus-properties-window.c",
line=line@entry=1836,
func=func@entry=0x4fe770 <__PRETTY_FUNCTION__.50289>
"schedule_owner_change_timeout", expr=expr@entry=0x4f73d8 "NAUTILUS_IS_FILE
(file)")
at /build/buildd/glib2.0-2.35.4/./glib/gtestutils.c:1903
#4 0x0045f59e in schedule_owner_change_timeout (window=0x2954050,
window@entry=)
at nautilus-properties-window.c:1836
#5 0x7f675fbb81ab in g_timeout_dispatch (source=source@entry=0x2a37e80,
callback=, user_data=)
at /build/buildd/glib2.0-2.35.4/./glib/gmain.c:4095
#6 0x7f675fbb75a5 in g_main_dispatch (context=0x230a5d0)
at /build/buildd/glib2.0-2.35.4/./glib/gmain.c:2784
---Type to continue, or q to quit---+
#7 g_main_context_dispatch (context=context@entry=0x230a5d0)
at /build/buildd/glib2.0-2.35.4/./glib/gmain.c:3288
#8 0x7f675fbb78e8 in g_main_context_iterate (
context=context@entry=0x230a5d0, block=block@entry=1,
dispatch=dispatch@entry=1, self=)
at /build/buildd/glib2.0-2.35.4/./glib/gmain.c:3359
#9 0x7f675fbb79a4 in g_main_context_iteration (context=0x230a5d0,
context@entry=0x0, may_block=may_block@entry=1)
at /build/buildd/glib2.0-2.35.4/./glib/gmain.c:3420
#10 0x7f676015e9cc in g_application_run (application=0x22d1030,
argc=argc@entry=1, argv=argv@entry=0x7fffd6d42948)
at /build/buildd/glib2.0-2.35.4/./gio/gapplication.c:1620
#11 0x0042b6cb in main (argc=1, argv=0x7fffd6d42948)
at nautilus-main.c:103
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
Uname: Linux 3.8.0-1-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Sun Jan 27 02:42:56 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry'
b"'927x1027+66+24'"
InstallationDate: Installed on 2013-01-26 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130126)
MarkForUpload: True
ProcCmdline: nautilus
Signal: 6
SourcePackage: nautilus
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
Title: nautilus crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://
[Desktop-packages] [Bug 1292412] Re: Keyboard layout is always English(!)
if that happens at logging, please attach ~/.cache/upstart/unity- settings-daemon.log to the bug ** Package changed: gnome-session (Ubuntu) => unity-settings-daemon (Ubuntu) ** Changed in: unity-settings-daemon (Ubuntu) Status: New => Incomplete -- 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/1292412 Title: Keyboard layout is always English(!) Status in “gnome-control-center” package in Ubuntu: Invalid Status in “unity-control-center” package in Ubuntu: Invalid Status in “unity-settings-daemon” package in Ubuntu: Incomplete Bug description: Keyboard layout is always English, no matter that I select a different language in the selector. It is English even if I remove English from the layouts. And layout switching via hot key doesn't work no matter what the hot key is. Both issues are fresh from upgrades that I made today: Start-Date: 2014-03-14 09:25:48 Upgrade: initscripts:amd64 (2.88dsf-41ubuntu5, 2.88dsf-41ubuntu6), pciutils:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), aptdaemon-data:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), ubuntu-session:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), unity-greeter:amd64 (14.04.3-0ubuntu2, 14.04.4-0ubuntu1), libqt4-xml:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-network:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libegl1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libqt4-sql-mysql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libopenvg1-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), gnome-session-common:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libfreetype6-dev:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), gnome-session-bin:amd64 (3.9.90-0ubuntu11, 3.9.90-0ubuntu12), libqt4-sql:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), isc-dhcp-common:amd64 (4.2.4-7ubuntu8, 4.2.4-7ubuntu9), libegl1-mesa-drivers:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), firefox-locale-en:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), qdbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqtcore4:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-qt3support:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-svg:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-dbus:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-xmlpatterns:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-sql-sqlite:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libqt4-opengl:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), qt4-qtconfig:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libgl1-mesa-dri:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libgl1-mesa-dri:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), unity:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), libunity-core-6.0-9:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), ubuntu-drivers-common:amd64 (0.2.89.6, 0.2.90), firefox:amd64 (28.0~b2+build1-0ubuntu2, 28.0+build1-0ubuntu1), libqt4-script:amd64 (4.8.5+git192-g085f851+dfsg-2ubuntu3, 4.8.5+git192-g085f851+dfsg-2ubuntu4), libfreetype6:amd64 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), libfreetype6:i386 (2.5.2-1ubuntu1, 2.5.2-1ubuntu2), python-apt:amd64 (0.9.1ubuntu1, 0.9.3.2), libgs9-common:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), ubuntu-release-upgrader-gtk:amd64 (0.216, 0.216.1), libido3-0.1-0:amd64 (13.10.0+14.04.20140213-0ubuntu1, 13.10.0+14.04.20140313-0ubuntu1), libglib2.0-0:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), libglib2.0-0:i386 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), xserver-xorg-core:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), libglapi-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libglapi-mesa:i386 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), libpci3:amd64 (3.2.1-1ubuntu3, 3.2.1-1ubuntu4), gnome-screensaver:amd64 (3.6.1-0ubuntu10, 3.6.1-0ubuntu11), unity-services:amd64 (7.1.2+14.04.20140311-0ubuntu1, 7.1.2+14.04.20140313-0ubuntu1), python-aptdaemon.gtk3widgets:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), bash-completion:amd64 (2.1-2ubuntu3, 2.1-2ubuntu4), xserver-common:amd64 (1.15.0-1ubuntu6, 1.15.0-1ubuntu7), ghostscript-x:amd64 (9.10~dfsg-0ubuntu7, 9.10~dfsg-0ubuntu8), libunity-control-center1:amd64 (14.04.3+14.04.20140310-0ubuntu1, 14.04.3+14.04.20140313-0ubuntu1), libglib2.0-data:amd64 (2.39.91-0ubuntu2, 2.39.91-0ubuntu3), python3-aptdaemon.gtk3widgets:amd64 (1.1.1-1ubuntu1, 1.1.1-1ubuntu3), libgles2-mesa:amd64 (10.1.0~rc3-0ubuntu3, 10.1.0-1ubuntu1), usb-creator-common:am
[Desktop-packages] [Bug 1130284] Re: Libreoffice crash when typing some Malayalam text using ibus
** Changed in: icu Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1130284 Title: Libreoffice crash when typing some Malayalam text using ibus Status in LibreOffice Productivity Suite: Fix Released Status in International Components for Unicode (C/C++): Fix Released Status in “icu” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Invalid Status in “icu” package in Debian: Fix Released Bug description: see upstream To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1130284/+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 1291862] Re: [soundnua]mic volume adjust bar is gray if you open sound-nua input tab earlier than plugging micphone
Ara, I install the 14.04, and find there are use 'unity-control-center sound' for change sound setting. First run 'unity-control-center sound', and insert the microphone in front panel, the input bar could be adjusted. But when I plug out the microphone, the input bar is still enabled, and you can change the input level, in next time when you insert microphone again, you will find the input level was the latest change which is we changed without inserting microphone. And I found soucecode is similar with gnome-control-center sound-nua, I'll try to made a patch for trusty. ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed -- 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/1291862 Title: [soundnua]mic volume adjust bar is gray if you open sound-nua input tab earlier than plugging micphone Status in GNOME Control Center: New Status in OEM Priority Project: Confirmed Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: gnome-control-center 1:3.4.2-0ubuntu0.13.1 in precise updates. In laptop you can't reproduce this issue, cause there have 'Internal Microphone' already. I find this issue im my PC, there are two jacks in front panel, input and output. 1. Install system and log in to Desktop 2. Connect the headphone in front panel 3. Open sound settings menu and click Input tab I made an screenshot for it. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1291862/+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 1292041] Re: Lockscreen doesn't turn off the screen
I wonder if this is related to bug 1291365 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in Unity: Invalid Status in “gnome-screensaver” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292041/+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 1291365] Re: gnome screensaver locks again shortly after unlocking
bug 1292041 seems like a duplicate of this -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1291365 Title: gnome screensaver locks again shortly after unlocking Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: When I unlock my screen, I sometimes get only a few seconds of interaction with my desktop before the screen inexplicably locks itself again. I believe this only happens when I manually lock it with my ThinkVantage key that I have bound to the lock-screen shortcut, but I can't be sure of that. I've seen this for a while now, but assumed it was some bug caused by either a borked compiz or some kind of delay catch-up happening because gnome-screensaver took too long to swap in. But I just upgraded to the latest trusty compiz that has tons of bugfixes, and the new lock screen keeps gnome-screensaver swapped in nicely. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 12 13:13:43 2014 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 600 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-02-25 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1291365/+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 1240088] Re: add network (nm-applet) to login screen
** Patch removed: "proposed patch for precise" https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1240088/+attachment/3961098/+files/nm-applet.debdiff -- 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/1240088 Title: add network (nm-applet) to login screen Status in “unity-greeter” package in Ubuntu: Fix Released Status in “unity-greeter” source package in Precise: Triaged Bug description: [Impact] * User has a hard time to login via network, (krb5) if nm-applet is not accessible via login screen. [Test Case] 1) make sure the system is configure to authenticate via krb5 2) login with user "A" and disconnect from the network via nm-applet, logout 3) Try to login with user B a. Actual Results: User B is not able to authenticate because the system is not connected to the network so we are not able to talk to the krb servers b. Expected Results: Users should be able to use network manager from within unity greater and reconnect to the network before attempting to login. [Regression Potential] * n/a . The patch is a backport from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1240088/+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 1043929] Re: FFE: Behavior when policy limits access to nm-applet functions is inconsistent / should hide disallowed actions
** Patch added: "proposed patch for precise" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1043929/+attachment/4023827/+files/nm-applet.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1043929 Title: FFE: Behavior when policy limits access to nm-applet functions is inconsistent / should hide disallowed actions Status in “network-manager-applet” package in Ubuntu: Fix Released Bug description: TL;DR: two things to be added: - Fix the inconsistencies, make sure all the locked-down functions are insensitive when disallowed; - Add support to hide rather than desensitize disallowed functions. The UI behavior is inconsistent in the applet; basically, if some functions are disallowed from the UI, some items will appear insensitive in the menu, while others will be accessible and fail due to permissions. All disallowed functions should be triggering a case where the menu items are insensitive. Also, there ought to be a way to hide these items from the menu when desired, to avoid confusing users. Not by default, because default settings don't actually currently lock any of the applet functions, but the possiblity should be allowed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1043929/+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
I can confirm that it works with iOS 7.1, on an iPhone 5. I had some problems mounting the iPhone, but they got solved with sudo mkdir /var/lib/lockdown sudo chmod 777 /va7Lib/lockdown -- 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: New 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 1292496] Re: chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()
*** This bug is a duplicate of bug 1229021 *** https://bugs.launchpad.net/bugs/1229021 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1229021, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1292496/+attachment/4023829/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1292496/+attachment/4023832/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1292496/+attachment/4023836/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1292496/+attachment/4023837/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1292496/+attachment/4023838/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1292496/+attachment/4023841/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1292496/+attachment/4023842/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1229021 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1292496 Title: chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask() Status in “chromium-browser” package in Ubuntu: New Bug description: running prerelease 14.04, this came up from apport ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: chromium-browser 32.0.1700.107-0ubuntu1~20140204.977.1 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: XFCE Date: Fri Mar 14 11:18:01 2014 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/ DiskUsage: b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda5 ext4 386G 79G 288G 22% /\nnone tmpfs 4.0K 0 4.0K 0% /sys/fs/cgroup\nudev devtmpfs 3.9G 12K 3.9G 1% /dev\ntmpfs tmpfs 787M 1.3M 785M 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 3.9G 8.6M 3.9G 1% /run/shm\nnone tmpfs 100M 28K 100M 1% /run/user\n' Inodes: b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda5 25M 857K 24M4% /\nnone 983K 2 983K1% /sys/fs/cgroup\nudev 980K 526 980K1% /dev\ntmpfs 983K 547 983K1% /run\nnone 983K 3 983K1% /run/lock\nnone 983K20 983K1% /run/shm\nnone 983K29 983K1% /run/user\n' Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2013-03-11 (367 days ago) InstallationMedia: Xubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=1765.27.1750848298\ --disable-gl-multisampling\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=0,9,23\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x8086\ --gpu-device-id=0x0152\ --gpu-driver-vendor=Mesa\ --gpu-driver-version=10.1 SegvAnalysis: Segfault happened at: 0x7f4fc3646b98:movl $0x1337,0x0 PC (0x7f4fc3646b98) ok source "$0x1337" ok destination "0x0" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: chromium-browser StacktraceTop: ?? () from /usr/lib/chromium-browser/libs/libcontent.so base::MessageLoop::RunTask(base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so base::MessageLoop::DoDelayedWork(base::TimeTicks*) () from /usr/lib/chromium-browser/libs/libbase.so ?? () from /usr/lib/chromium-browser/libs/libbase.so Title: chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask() UpgradeStatus: Upgraded to trusty on 2014-
[Desktop-packages] [Bug 1055464] Re: apport-gtk crashed with ValueError in _apt_pkg(): package rhythmbox-ubuntuone-music-store does not exist
This also affects Ubuntu 14.04 Trusty Tahr (Development Release). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1055464 Title: apport-gtk crashed with ValueError in _apt_pkg(): package rhythmbox- ubuntuone-music-store does not exist Status in “apport” package in Ubuntu: Invalid Status in “rhythmbox” package in Ubuntu: Fix Released Bug description: Apport crashed reporting a bug :) ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: apport-gtk 2.5.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic i686 ApportVersion: 2.5.2-0ubuntu4 Architecture: i386 Date: Mon Sep 24 13:00:46 2012 ExecutablePath: /usr/share/apport/apport-gtk InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100201) InterpreterPath: /usr/bin/python3.2mu PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/zsh PythonArgs: ['/usr/share/apport/apport-gtk'] SourcePackage: apport Title: apport-gtk crashed with ValueError in _apt_pkg(): package rhythmbox-ubuntuone-music-store does not exist UpgradeStatus: Upgraded to quantal on 2012-01-03 (264 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1055464/+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 214366]
Comment on attachment 8390075
patch v6 - local folders
Review of attachment 8390075:
-
::: mailnews/base/util/nsMsgDBFolder.cpp
@@ +3843,5 @@
>
> +nsresult
> +nsMsgDBFolder::ConfirmAutoFolderRename(nsIMsgWindow *msgWindow,
> + const nsString aOldName,
> + const nsString aNewName,
These should be const nsString &... to avoid unnecessary string copies.
@@ +3846,5 @@
> + const nsString aOldName,
> + const nsString aNewName,
> + bool *confirmed)
> +{
> + NS_ENSURE_ARG_POINTER(confirmed);
It is possible that confirmed never gets set, so you might then end up
with a bad value.
Additionally I don't really see the point of returning nsresult here,
when you're already warning for errors, and you treat a failure as not
confirmed anyway.
So I think it would be simpler just to change this function to return
the bool.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/214366
Title:
Can't delete a folder if Trash already contains a folder of the same
name
Status in Mozilla Thunderbird Mail and News:
In Progress
Status in “thunderbird” package in Ubuntu:
Triaged
Bug description:
Binary package hint: mozilla-thunderbird
1. Create a new folder, eg. "Temp"
2. Delete it, OK
3. Create the same folder again
4. Delete it, OK
I expect it to be moved to my Trash folder, perhaps with a suffix
appended (it being the second instance of that folder in the trash).
Thunderbird popped up an error message. On an imap host:
The current command did not succeed. The mail server responded: Mailbox
already exists.
In the local folders:
A folder with that name already exists. Please enter a different name (!)
Workarounds:
1. Empty the trash
2. Rename the folder before deletion
3. Rename the folder already in the trash
4. Delete (permanently) the folder that is already in the trash
Ubuntu 7.10 Gutsy
thunderbird 2.0.0.12+nobinonly-0ubuntu0.7.10.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/214366/+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
