[Dx-packages] [Bug 1208019] Re: Eclipse menus doesn't show up in Saucy
Since the origin of the bug is the unity-gtk-module package, this is the only affected one. ** Description changed: HOW TO REPRODUCE - 1. Run Eclipse. + 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) ** No longer affects: eclipse (Ubuntu) ** No longer affects: gimp (Ubuntu) ** No longer affects: inkscape (Ubuntu) ** Also affects: unity-gtk-module Importance: Undecided Status: New ** Changed in: unity-gtk-module Status: New = Confirmed ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Status: New = Triaged ** Changed in: hundredpapercuts Importance: Undecided = Critical ** No longer affects: hundredpapercuts -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in Unity GTK+ module: Confirmed Status in “unity-gtk-module” package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-gtk-module/+bug/1208019/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 618587] Re: eclipse does not work with appmenu
I have run a debugging session from the Eclipse side. When you click the global menu it is producing event that gets handed down to the main SWT loop, there Eclipse takes the event and gives it back to GTK calling gtk_main_do_event for precise targeting of the affected component. Without the global menu the event would popout back from GTK inside the Menu widget triggering something like menuIsAboutToShow callback. With global menu however the event is swallowed and never comes back. The Java code in Eclipse has no role here nor the super-thin SWT native code. It an apparent regression in the behavior of the GTK library. In other words it is Ubuntu global menu back not being compatible with standard GTK behavior. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/618587 Title: eclipse does not work with appmenu Status in Application menu module for GTK+: Invalid Status in Audacity: Invalid Status in Eclipse: Unknown Status in The Application Menu: Invalid Status in DBus Menu: Fix Released Status in Unity Foundations: Fix Released Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “libdbusmenu” source package in Natty: Won't Fix Bug description: Binary package hint: indicator-appmenu eclipse do not work ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: indicator-appmenu 0.0.9-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1 Uname: Linux 2.6.35-15-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Aug 16 13:06:20 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha amd64 (20100803.1) ProcEnviron: PATH=(custom, user) LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-appmenu To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-gtk/+bug/618587/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1238346] Re: on bootup wrong keyboard layout is recognized
** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Status: New = Confirmed ** Changed in: hundredpapercuts Importance: Undecided = Low ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided = Critical ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Critical = Low ** Changed in: unity (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1238346 Title: on bootup wrong keyboard layout is recognized Status in One Hundred Papercuts: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: This is a regression. I have two keyboard layouts activated, the Dvorak and the English US. The Dvorak should be the default keyboard. That is the way I have it set up, and it shows up in the task bar on top as En1, which is the Dvorak. However, when I start to type, it starts in QUERTY. ?? To correct this, I go to the task bar (where it shows EN1, or Dvorak), re-select the Dvorak, and then everything is fine. ?? I have another minor problem which should probably go on another bug, but happened at the same time. CTL-ALT-T doesn't bring up the terminal any more. No matter what keyboard I'm using. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.1+13.10.20131004-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 10 21:20:39 2013 InstallationDate: Installed on 2013-08-12 (60 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130811) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1238346/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1197213] Re: Heads up display does not work in 13.10
** Changed in: hud (Ubuntu) Importance: Undecided = High ** Changed in: hud (Ubuntu) Status: Confirmed = Triaged ** Also affects: hud Importance: Undecided Status: New ** Changed in: hud Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1197213 Title: Heads up display does not work in 13.10 Status in Unity HUD: Confirmed Status in “hud” package in Ubuntu: Triaged Bug description: The Heads up display feature does not work in ubuntu 13.10. the interface invokes on pressing the alt key. But it does nothing when the first few letters or the entire text is typed. Please fix this bug as soon as possible Thanks and Have a nice day :) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20130702-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Uname: Linux 3.10.0-2-generic i686 ApportVersion: 2.10.2-0ubuntu3 Architecture: i386 Date: Wed Jul 3 06:46:22 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-05-21 (42 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130101) MarkForUpload: True ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_IN SHELL=/bin/bash SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1197213/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager
** Changed in: gnome-session (Ubuntu) Importance: Undecided = Medium ** Changed in: systemd (Ubuntu) Importance: Undecided = Medium ** Changed in: kde-workspace (Ubuntu) Importance: Undecided = Medium ** Changed in: systemd-shim (Ubuntu) Importance: Undecided = Medium ** Changed in: kde-workspace (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling poweroff, but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1221304] Re: Global app-menu is missing from Unity panel...
This bug is just a work-around for another one, while the second is being addressed. ** Changed in: indicator-appmenu (Ubuntu) Importance: Undecided = High ** Changed in: indicator-appmenu (Ubuntu) Status: Confirmed = Invalid ** Changed in: unity (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1221304 Title: Global app-menu is missing from Unity panel... Status in “indicator-appmenu” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: Upgraded to 13.10 and there's a strange issue with the global menu - the one in the panel - it isn't consistent for all applications. For example GIMP is missing it's menu at the top of the panel and instead has it below the panel. Screenshot included. wanted to know if it's supposed to be that way or if there's a fix, thanks... ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.32 Wed Jun 19 15:51:20 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-9ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Sep 5 11:56:46 2013 DistUpgraded: 2013-09-04 18:37:41,066 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:050e] InstallationDate: Installed on 2013-01-16 (232 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MachineType: HP-Pavilion GC674AA-ABA m8120n MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=73dd09de-3940-4451-a160-8a036cc025a3 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-09-04 (0 days ago) dmi.bios.date: 06/08/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.09 dmi.board.name: Basswood3G dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.05 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.09:bd06/08/2007:svnHP-Pavilion:pnGC674AA-ABAm8120n:pvr:rvnASUSTekComputerINC.:rnBasswood3G:rvr1.05:cvnHewlett-Packard:ct3:cvr: dmi.product.name: GC674AA-ABA m8120n dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Sep 5 10:26:27 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Keyboard KEYBOARD, id 8 inputImPS/2 Logitech Wheel Mouse MOUSE, id 9 xserver.errors: Failed to load module nouveau (module does not exist, 0) Failed to load module modesetting (module does not exist, 0) Failed to load module nouveau (module does not exist, 0) Failed to load module
[Dx-packages] [Bug 1271138] [NEW] Several icons stopped showing since updating to Trusty
Public bug reported: I had to enable the notification area because several icons disappeared. These include, dropbox, synaptic, nm-applet, and many others. ** Affects: indicator-applet (Ubuntu) Importance: Undecided Status: New ** Tags: trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1271138 Title: Several icons stopped showing since updating to Trusty Status in “indicator-applet” package in Ubuntu: New Bug description: I had to enable the notification area because several icons disappeared. These include, dropbox, synaptic, nm-applet, and many others. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1271138/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager
Hi Could you please check if this is still present in 14.04? -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling poweroff, but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager
( Specifically for KDE ) -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling poweroff, but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1208019] Re: Eclipse menus doesn't show up in Saucy
I have run a debugging session from the Eclipse side. When you click the global menu it is producing event that gets handed down to the main SWT loop, there Eclipse takes the event and gives it back to GTK calling gtk_main_do_event for precise targeting of the affected component. Without the global menu the event would popout back from GTK inside the Menu widget triggering something like menuIsAboutToShow callback. With global menu however the event is swallowed and never comes back. The Java code in Eclipse has no role here nor the super-thin SWT native code. It an apparent regression in the behavior of the GTK library. In other words it is Ubuntu global menu back not being compatible with standard GTK behavior. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in Unity GTK+ module: Confirmed Status in “unity-gtk-module” package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify /usr/share/applications/eclipse.desktop to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-gtk-module/+bug/1208019/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1061852] Re: Unity Application Lens slow to load
This has been a major problem for me in 13.10. I managed to solve it by turning off the record search activity option under provacy settings. It seems that the circling icon next to the magnifying glass is the process recording, or calling, previous searches. If i turn if off (dash -- Security and privacy -- Files and applications --- Turn off: 'Record file and application usage'), my applications come up really quickly in the dash. j -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1061852 Title: Unity Application Lens slow to load Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: WHAT HAPPENS -- Log into the system Launch the dash with the 'window' key Start typing 'chr'... I see my files appearing in the search results The application lens results appear ~10 - 15 seconds later WHAT IS DESIRABLE --- The application lens results appear immediately Most users would login into the system and launch a web browser Optimal unity experience demands that their browser or mail client shows up in the dash instantaneously Also this behaviour has worsened recently (after upgrade to 12.04) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.16.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,resize,commands,place,regex,move,grid,session,snap,vpswitch,imgpng,gnomecompat,mousepoll,put,animation,compiztoolbox,expo,wall,ezoom,workarounds,unitymtgrabhandles,fade,scale,unityshell] Date: Fri Oct 5 01:13:34 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1061852/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1271187] [NEW] Add a search fonction utility field
Public bug reported: Using the 0.19.3 dconf-editor from Trusty to set a better mouse settings for my needs, i would like to use a keyword inside the tree from a search field, instead to blindly open then closing the sub trees. So please, add a search fonction, for better usability. ** Affects: d-conf (Ubuntu) Importance: Undecided Status: New ** Tags: bot-stop-nagging trusty ** Tags added: trusty ** Tags added: bot-stop-nagging ** Summary changed: - Add a search utility fonction field + Add a search fonction utility field -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1271187 Title: Add a search fonction utility field Status in “d-conf” package in Ubuntu: New Bug description: Using the 0.19.3 dconf-editor from Trusty to set a better mouse settings for my needs, i would like to use a keyword inside the tree from a search field, instead to blindly open then closing the sub trees. So please, add a search fonction, for better usability. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1271187/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1228588] Re: unity makes confusion when trying to focus partitions' folders
** Tags added: trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228588 Title: unity makes confusion when trying to focus partitions' folders Status in “unity” package in Ubuntu: Confirmed Bug description: How to reproduce version 1:workspaces disabled Open gedit Click on a partition icon on the launcher You see nautilus windows appears, a white arrow appears alongside of Files icon and both the icon of the volume you clicked on and the File's one have a backlight. Focus gedit I see the white arrow is alongside of the Files icon, so if I want to focus the partition's folder I should click on it. I do it Expected result Unity focuses the partition's folder What happens instead Damn! It opens a new File window in my home folder, but if I click on the partition icon it works... ok, I can get used to it, even if it's a bit confusing... version 2:workspaces enabled Click on a partition icon on the launcher You see nautilus windows appears, a white arrow appears alongside of Files icon and both the icon of the volume you clicked on and the File's one have a backlight. Switch to another workspace I want to focus the partition's folder in the other workspace, as in the previous case I see the arrow alongside File's icon and I click on it Expected result Unity switches to the correct workspace and focuses the partition's folder What happens: It opens a new File's window in my home folder. Ok ok, I have to click on the partition's icon. I do it. Expected result #2 Unity switches to the correct workspace and focuses the partition's folder What happens #2 What!? The File icon wiggles and its edge becomes illuminated? Nothing else? Do I really have to manually switch to the correct workspace and then click on the correct icon? I can't realize a convenient way to focus the window on the other workspace without doing it manually (which is not comfortable) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130920-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Sep 21 13:58:02 2013 InstallationDate: Installed on 2013-06-20 (93 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: unity SystemImageInfo: Error: [Errno 2] File o directory non esistente: 'system-image-cli' UpgradeStatus: Upgraded to saucy on 2013-07-23 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1228588/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 793450] Re: Calendar doesn't show today's date until opened a second time today
confirming the behaviour that Marcus Sundman sees: The calendar day never updates, not when closing and re-opening, not when coming back from sleep, not at midnight. (Don't know about rebooting which I rarely do.) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/793450 Title: Calendar doesn't show today's date until opened a second time today Status in The Date and Time Indicator: Fix Released Status in Unity Foundations: Fix Committed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Ubuntu 11.04 indicator-datetime 0.3.1-0ubuntu1, Ubuntu 11.10 indicator-datetime 0.3.94-0ubuntu2, Ubuntu 12.04 Ubuntu 12.10 indicator-datetime 12.10.3daily13.03.26-0ubuntu1, Ubuntu 13.04 Ubuntu 13.10 1) Log in 2) Run a session for a day or two 3) Open the calendar applet by clicking the clock. Although the date in the text field is correct, the graphic calendar still shows the date at which you either originally logged in, or clicked the calendar before. 4) Hide it, and show it once more. The calendar now shows the correct date. The conflicting visual data can be very confusing if you only summon the calendar to find out what day it is. (I don't get much sunlight.) This is the sequel to bug 649800, which was supposedly fixed in Ubuntu 11.04. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/793450/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1228588] Re: unity makes confusion when trying to focus partitions' folders
Same behavior in Ubuntu 14.04 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228588 Title: unity makes confusion when trying to focus partitions' folders Status in “unity” package in Ubuntu: Confirmed Bug description: How to reproduce version 1:workspaces disabled Open gedit Click on a partition icon on the launcher You see nautilus windows appears, a white arrow appears alongside of Files icon and both the icon of the volume you clicked on and the File's one have a backlight. Focus gedit I see the white arrow is alongside of the Files icon, so if I want to focus the partition's folder I should click on it. I do it Expected result Unity focuses the partition's folder What happens instead Damn! It opens a new File window in my home folder, but if I click on the partition icon it works... ok, I can get used to it, even if it's a bit confusing... version 2:workspaces enabled Click on a partition icon on the launcher You see nautilus windows appears, a white arrow appears alongside of Files icon and both the icon of the volume you clicked on and the File's one have a backlight. Switch to another workspace I want to focus the partition's folder in the other workspace, as in the previous case I see the arrow alongside File's icon and I click on it Expected result Unity switches to the correct workspace and focuses the partition's folder What happens: It opens a new File's window in my home folder. Ok ok, I have to click on the partition's icon. I do it. Expected result #2 Unity switches to the correct workspace and focuses the partition's folder What happens #2 What!? The File icon wiggles and its edge becomes illuminated? Nothing else? Do I really have to manually switch to the correct workspace and then click on the correct icon? I can't realize a convenient way to focus the window on the other workspace without doing it manually (which is not comfortable) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130920-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Sep 21 13:58:02 2013 InstallationDate: Installed on 2013-06-20 (93 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: unity SystemImageInfo: Error: [Errno 2] File o directory non esistente: 'system-image-cli' UpgradeStatus: Upgraded to saucy on 2013-07-23 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1228588/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1228588] Re: unity makes confusion when trying to focus partitions' folders
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228588 Title: unity makes confusion when trying to focus partitions' folders Status in “unity” package in Ubuntu: Confirmed Bug description: How to reproduce version 1:workspaces disabled Open gedit Click on a partition icon on the launcher You see nautilus windows appears, a white arrow appears alongside of Files icon and both the icon of the volume you clicked on and the File's one have a backlight. Focus gedit I see the white arrow is alongside of the Files icon, so if I want to focus the partition's folder I should click on it. I do it Expected result Unity focuses the partition's folder What happens instead Damn! It opens a new File window in my home folder, but if I click on the partition icon it works... ok, I can get used to it, even if it's a bit confusing... version 2:workspaces enabled Click on a partition icon on the launcher You see nautilus windows appears, a white arrow appears alongside of Files icon and both the icon of the volume you clicked on and the File's one have a backlight. Switch to another workspace I want to focus the partition's folder in the other workspace, as in the previous case I see the arrow alongside File's icon and I click on it Expected result Unity switches to the correct workspace and focuses the partition's folder What happens: It opens a new File's window in my home folder. Ok ok, I have to click on the partition's icon. I do it. Expected result #2 Unity switches to the correct workspace and focuses the partition's folder What happens #2 What!? The File icon wiggles and its edge becomes illuminated? Nothing else? Do I really have to manually switch to the correct workspace and then click on the correct icon? I can't realize a convenient way to focus the window on the other workspace without doing it manually (which is not comfortable) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130920-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Sep 21 13:58:02 2013 InstallationDate: Installed on 2013-06-20 (93 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: unity SystemImageInfo: Error: [Errno 2] File o directory non esistente: 'system-image-cli' UpgradeStatus: Upgraded to saucy on 2013-07-23 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1228588/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1228360] Re: No clock in menu bar and can't edit Clock settings
It's not fixed, I'm afraid. My up-to-date Saucy 64bit, running on an XPS 13, had exactly the same issue. killall worked for me too. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228360 Title: No clock in menu bar and can't edit Clock settings Status in One Hundred Papercuts: Fix Released Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: The latest update broke the clock in several ways: * No clock shows up in the menu bar. * Open Time Date settings. You cannot edit anything in the Clock tab. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu38 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 20 15:51:55 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2011-07-12 (800 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110705.1) MarkForUpload: True SourcePackage: gnome-control-center SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to saucy on 2011-12-23 (637 days ago) usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130913-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1228360/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1228588] Re: unity makes confusion when trying to focus partitions' folders
*** This bug is a duplicate of bug 1170647 *** https://bugs.launchpad.net/bugs/1170647 This bug seems to be a duplicate of #1170647 ** This bug has been marked a duplicate of bug 1170647 Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1228588 Title: unity makes confusion when trying to focus partitions' folders Status in “unity” package in Ubuntu: Confirmed Bug description: How to reproduce version 1:workspaces disabled Open gedit Click on a partition icon on the launcher You see nautilus windows appears, a white arrow appears alongside of Files icon and both the icon of the volume you clicked on and the File's one have a backlight. Focus gedit I see the white arrow is alongside of the Files icon, so if I want to focus the partition's folder I should click on it. I do it Expected result Unity focuses the partition's folder What happens instead Damn! It opens a new File window in my home folder, but if I click on the partition icon it works... ok, I can get used to it, even if it's a bit confusing... version 2:workspaces enabled Click on a partition icon on the launcher You see nautilus windows appears, a white arrow appears alongside of Files icon and both the icon of the volume you clicked on and the File's one have a backlight. Switch to another workspace I want to focus the partition's folder in the other workspace, as in the previous case I see the arrow alongside File's icon and I click on it Expected result Unity switches to the correct workspace and focuses the partition's folder What happens: It opens a new File's window in my home folder. Ok ok, I have to click on the partition's icon. I do it. Expected result #2 Unity switches to the correct workspace and focuses the partition's folder What happens #2 What!? The File icon wiggles and its edge becomes illuminated? Nothing else? Do I really have to manually switch to the correct workspace and then click on the correct icon? I can't realize a convenient way to focus the window on the other workspace without doing it manually (which is not comfortable) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130920-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Sep 21 13:58:02 2013 InstallationDate: Installed on 2013-06-20 (93 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: unity SystemImageInfo: Error: [Errno 2] File o directory non esistente: 'system-image-cli' UpgradeStatus: Upgraded to saucy on 2013-07-23 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1228588/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1249266] Re: Restart and Shutdown via Desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1249266 Title: Restart and Shutdown via Desktop Status in “unity” package in Ubuntu: Confirmed Bug description: By trying to restart or shutdown my Ubuntu 13.10 via the desktop shurtcut(s) nothing happens. The restart and shutdown button seem to be functionless. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/hwC1D1', '/dev/snd/hwC1D2', '/dev/snd/hwC1D3', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D9p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 8 10:53:54 2013 HibernationDevice: RESUME=UUID=3a3b4c31-4148-4827-847c-c8b0b7d96a98 InstallationDate: Installed on 2013-08-22 (77 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: Dell Inc. Precision T3600 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-18 (20 days ago) dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1249266/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1268211] Re: Black screen after logging in, after installing Nvidia-CUDA
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1268211 Title: Black screen after logging in, after installing Nvidia-CUDA Status in “unity” package in Ubuntu: Confirmed Bug description: After installing Nvidia-CUDA* packages, Unity breaks. There's only black screen after logging in, even when I remove the Nvidia-CUDA packages. please advise. sudo dpkg-reconfigure xorg doesn't help at all either. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.88 Wed Mar 27 14:26:46 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Jan 11 13:58:28 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.88, 3.11.0-15-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:054e] Subsystem: Dell GeForce GT 630M [1028:054e] InstallationDate: Installed on 2013-11-23 (49 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. XPS L521X MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=8e997c12-0ee0-422b-a7e4-a7cb0a74f38f ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0C5Y96 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A14 dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/22/2013:svnDellInc.:pnXPSL521X:pvrA14:rvnDellInc.:rn0C5Y96:rvrA00:cvnDellInc.:ct8:cvrA14: dmi.product.name: XPS L521X dmi.product.version: A14 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sat Jan 11 13:50:26 2014 xserver.configfile: default xserver.errors: Failed to initialize GLX extension (Compatible NVIDIA X driver not found) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4333 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1268211/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations
I can confirm this bug is present also in Ubuntu 14.04 64 bit ** Tags added: amd64 trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1170647 Title: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations Status in “bamf” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sometimes left clicking the nautilus launcher icon doesn't bring up a minimized nautilus window. Instead of restoring the window a new instance of nautilus is showing up. Steps to reproduce: 1. Open a nautilus window by clicking on the launcher icon. 2. Navigate to a symlinked directory whose target is located on a different harddrive (for example: a symlink to a folder on a sd-card). 3. Minimize the nautilus window. 4. Try to bring up that window again by clicking the launcher icon. What happens: 1. A new instance (window) of nautilus is opened. 2. There's no obvious way to access the first window again. The only way is ALT+TAB. What schould happen: If a nautilus window is already open and minimized clicking the launcher icon should bring up that window. This was the behavior of nautilus windows in Ubuntu 12.10 (quantal). Ubuntu 13.04 Raring Ringtail (development branch) nautilus 3.6.3-0ubuntu16 unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1170647/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations
I have 3 other partitions apart from Ubuntu 14.04 one, one of which is set in fstab to be automatically mounted at startup (and not by gvfsd). I've noticed the behavior mentioned in this bug applies for the other partitions, but not for this one. Maybe this info could be useful. Here is the relative fstab line: UUID=4031F06913658C89 /mnt/DATI auto nosuid,nodev,nofail,x-gvfs-show 0 0 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1170647 Title: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations Status in “bamf” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sometimes left clicking the nautilus launcher icon doesn't bring up a minimized nautilus window. Instead of restoring the window a new instance of nautilus is showing up. Steps to reproduce: 1. Open a nautilus window by clicking on the launcher icon. 2. Navigate to a symlinked directory whose target is located on a different harddrive (for example: a symlink to a folder on a sd-card). 3. Minimize the nautilus window. 4. Try to bring up that window again by clicking the launcher icon. What happens: 1. A new instance (window) of nautilus is opened. 2. There's no obvious way to access the first window again. The only way is ALT+TAB. What schould happen: If a nautilus window is already open and minimized clicking the launcher icon should bring up that window. This was the behavior of nautilus windows in Ubuntu 12.10 (quantal). Ubuntu 13.04 Raring Ringtail (development branch) nautilus 3.6.3-0ubuntu16 unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1170647/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 932189] Re: Minimized windows are empty frames on restarting Unity
This seems fixed in current trunk ** Changed in: compiz Status: Confirmed = Fix Released ** Changed in: unity Status: Confirmed = Fix Released ** Changed in: compiz (Ubuntu) Status: Confirmed = Fix Released ** Changed in: unity (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/932189 Title: Minimized windows are empty frames on restarting Unity Status in Compiz: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: bzr1972 1. start nautilus 2. minimize it 3. restart unity from terminl with 'unity --replace' or restart it from alt-f2. 4. now click on nautilus icon in the launcher. What happens: see the screenshot. (tested it on both intel and nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/932189/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 691817] Re: Framing around window decorations on windows and panel should be identical.
** Changed in: unity-2d Status: Triaged = Won't Fix ** Changed in: unity (Ubuntu) Status: Triaged = In Progress ** Changed in: unity Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity Status: Triaged = In Progress ** Changed in: unity-2d (Ubuntu) Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity Milestone: None = 7.2.1 ** Branch linked: lp:~3v1n0/unity/unity-decorations -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/691817 Title: Framing around window decorations on windows and panel should be identical. Status in Unity: In Progress Status in Unity 2D: Won't Fix Status in “unity” package in Ubuntu: In Progress Status in “unity-2d” package in Ubuntu: Triaged Bug description: AS per the screen shot. The AppMenu in Unity does not display the indent around the window controls the same as a standard window. Sorry to report something so petty. But I read on Mark Shuttleworth's blog that he wants us to report anything and everything to make Natty the most beautiful version of Ubuntu ever. Avoiding any flies in the icecream. Edit: Title to reflect mark's comments bellow. It might be worth updating the bug summary to say they should be identical, rather than that the panel should get the framing, as I don't think the design is final for Natty. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/691817/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager
Hi, I can confirm the bug in Kubuntu 13.10 and 14.04, both full updated. This one is getting old, no solution yet ?? Thank you. Date: Tue, 21 Jan 2014 11:57:43 + From: rohan16g...@gmail.com To: axe...@hotmail.com Subject: [Bug 1201180] Re: Pressing power button turns off the PC ignoring thepresence of another session manager Hi Could you please check if this is still present in 14.04? -- You received this bug notification because you are subscribed to a duplicate bug report (1124149). https://bugs.launchpad.net/bugs/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+subscriptions -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling poweroff, but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager
Hi, I can confirm the bug in Kubuntu 13.10 and 14.04, both full updated. This one is getting old, no solution yet ?? Thank you. Date: Tue, 21 Jan 2014 11:57:43 + From: rohan16g...@gmail.com To: axe...@hotmail.com Subject: [Bug 1201180] Re: Pressing power button turns off the PC ignoring thepresence of another session manager Hi Could you please check if this is still present in 14.04? -- You received this bug notification because you are subscribed to a duplicate bug report (1124149). https://bugs.launchpad.net/bugs/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+subscriptions -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling poweroff, but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager
Hi, I can confirm the bug in Kubuntu 13.10 and 14.04, both full updated. This one is getting old, no solution yet ?? Thank you. Date: Tue, 21 Jan 2014 11:58:05 + From: rohan16g...@gmail.com To: axe...@hotmail.com Subject: [Bug 1201180] Re: Pressing power button turns off the PC ignoring thepresence of another session manager ( Specifically for KDE ) -- You received this bug notification because you are subscribed to a duplicate bug report (1124149). https://bugs.launchpad.net/bugs/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+subscriptions -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling poweroff, but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1245136] Re: Super+Space and Shift+Super+Space hotkeys for keyboard layout switching do not work in Saucy and Unity session
Yesterday I've installed fresh Ubuntu 13.10 downloaded from official site a few days ago. On first boot Super+Space was working but after installing all updates and reboot it this not work anymore. 13.10 has been released about 3 months ago and this bug is still there. How it can be possible? It is very disturbing issue for me. Please make your best to resolve it as soon as you can. On Sat, Dec 28, 2013 at 2:18 PM, Mateusz Stachowski 1245...@bugs.launchpad.net wrote: Confirm the default shortcuts do nothing in daily images of Trusty. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1245136 Title: Super+Space and Shift+Super+Space hotkeys for keyboard layout switching do not work in Saucy and Unity session Status in “unity” package in Ubuntu: Incomplete Bug description: On clean Ubuntu 13.10 install with enabled proposed updates Super+Space and Shift+Super+Space are default options for keyboard layout change. But they do not work in Unity session. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Oct 27 12:39:30 2013 InstallationDate: Installed on 2013-10-20 (6 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136/+subscriptions -- With best regards, Taras. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1245136 Title: Super+Space and Shift+Super+Space hotkeys for keyboard layout switching do not work in Saucy and Unity session Status in “unity” package in Ubuntu: Incomplete Bug description: On clean Ubuntu 13.10 install with enabled proposed updates Super+Space and Shift+Super+Space are default options for keyboard layout change. But they do not work in Unity session. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Oct 27 12:39:30 2013 InstallationDate: Installed on 2013-10-20 (6 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1245136] Re: Super+Space and Shift+Super+Space hotkeys for keyboard layout switching do not work in Saucy and Unity session
Yesterday I've installed fresh Ubuntu 13.10 downloaded from official site a few days ago. On first boot Super+Space was working but after installing all updates and reboot it this not work anymore. 13.10 has been released about 3 months ago and this bug is still there. How it can be possible? It is very disturbing issue for me. Please make your best to resolve it as soon as you can. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1245136 Title: Super+Space and Shift+Super+Space hotkeys for keyboard layout switching do not work in Saucy and Unity session Status in “unity” package in Ubuntu: Incomplete Bug description: On clean Ubuntu 13.10 install with enabled proposed updates Super+Space and Shift+Super+Space are default options for keyboard layout change. But they do not work in Unity session. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Oct 27 12:39:30 2013 InstallationDate: Installed on 2013-10-20 (6 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
I experience this issue on a MacBook Air when closing the lid. In this case, the network does not come up. When I use pm-suspend to put it to sleep, I get a working network connection after wakeup. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1262022] Re: incorrect multi-arch related meta information.
Also, the same thing exists with unity-gtk-module. Do we need a separate bug report for that? -- You received this bug notification because you are a member of DX Packages, which is subscribed to overlay-scrollbar in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1262022 Title: incorrect multi-arch related meta information. Status in “overlay-scrollbar” package in Ubuntu: Confirmed Bug description: I'm on a 64-bit system trying to install overlay-scrollbar-gtk2:i386 which depends on the overlay-scrollbar:i386 package. overlay- scrollbar:i386 doesn't have an install candidate because it's a multi-arch package. This should (or so I've been told) be reflected in the meta information of the overlay-scrollbar package but isn't, which is why the former package fails to install. As a more competent person than I put it: The overlay-scrollbar package does not come in i386 or amd64 flavors; it comes as an all flavor, which installs on all archs. It appears to be missing the Multi-Arch: allowed header so it won't satisfy an i386 package depending on it. You should file a bug report asking that the missing header be added. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: overlay-scrollbar 0.2.16+r359+13.10.20130826-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Dec 18 02:14:35 2013 InstallationDate: Installed on 2013-12-14 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: overlay-scrollbar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1262022/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
I can't participate directly in this bug anymore because I've done a reinstall. Having said that, the following configuration now *works* for me. Ubuntu-Gnome 13.10 install (from scratch) Gnome-next ppa Gnome-staging ppa TLP from https://launchpad.net/~linrunner/+archive/tlp TLP properly manages my power settings, and gnome-shell suspends via its menus, via the system hotkeys and resume properly brings up the network. Looks like me like it might be a unity bug or part of the bits that unity depends on, but gnome-shell doesn't. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1268167] Re: No Autohide Launcher Bar Mouse Reveal on Secondary Monitor
I can confirm the same behaviour. The super key method works fine. My launcher is set to reveal when the mouse goes to the top left corner but it does not behave that way on the external monitor configured to the right of the laptop monitor. The behaviour appears to be top left of the entire display area rather than per monitor: switching the external monitor to be left of the laptop monitor allows the launcher to reveal as expected on the external monitor but not on the laptop monitor. WM_CLASS for the launcher is not found as shown by xprop WM_CLASS and clicking on the launcher bar; presuming unity package. System: Lenovo Z580 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz Ubuntu: 12.04.4 LTS Kernel: Linux 3.8.0-35-generic #50~precise1-Ubuntu SMP Wed Dec 4 17:25:51 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Graphics: 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1268167 Title: No Autohide Launcher Bar Mouse Reveal on Secondary Monitor Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: Since several updates performed on 1/8/2014, I am no longer able to reveal the launcher bar on my secondary (right) display with the mouse auto-reveal function. Under display settings, both monitors are set to display a launcher bar. Auto reveal works fine with the mouse on the primary (left) monitor. The sticky edge works fine with the secondary (right) monitor, but no auto reveal for the launcher bar. I can bring up the secondary (right) monitor launcher bar with the super key and alt+f1. So far I've reverted to Nvidia 3.04 drivers from 3.19 by purging from terminal and re-installing to no avail, and now back to 3.19 and it's still not working. Ubuntu 12.04.4 LTS 32-bit AMD Athlon 64x2 Dual Core Processor 6000+ Nvidia GT630 PCIe 2GB RAM Any outputs you'd like from me, please let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1268167/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1243974] Re: [regression] Recent documents list broken in some applications
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-gtk-module (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1243974 Title: [regression] Recent documents list broken in some applications Status in Unity GTK+ module: Fix Committed Status in “unity-gtk-module” package in Ubuntu: Confirmed Bug description: Both Inkscape Gitg only open the first item in the Recently Opened menu regardless of what is selected. I brought up https://bugs.launchpad.net/indicator-appmenu/+bug/752674 to Ted Gould and he pointed me to this new module which has replaced the old one. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-gtk-module/+bug/1243974/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1244225] Re: Display is unrefreshed/corrupted when opening/closing/switching windows and tabs
[Expired for unity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1244225 Title: Display is unrefreshed/corrupted when opening/closing/switching windows and tabs Status in Compiz: Expired Status in “unity” package in Ubuntu: Expired Bug description: When I switch between windows, or switch between tabs in the same window, or switch desktops, part or all of the affected windows often fail to repaint (or repaint and then revert to stale content). Unfocusing/refocusing the affected window usually forces it to repaint again (but may then leave another window stale). It doesn't seem toolkit-specific (happens with xchat, firefox, chrome, skype, gnome-terminal, ...). Attached is a screenshot showing an example of corruption after switching between two tabs in xchat. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.32 Wed Jun 19 15:51:20 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity: Error: [Errno 21] Is a directory: '/tmp/unity' .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,compiztoolbox,vpswitch,move,gnomecompat,grid,place,regex,imgpng,resize,annotate,mousepoll,wobbly,session,animation,fade,animationaddon,cube,rotate,workarounds,unitymtgrabhandles,cubeaddon,trailfocus,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Oct 24 15:15:48 2013 DistUpgraded: 2013-10-18 10:50:28,943 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. nvidia-319, 319.32, 3.8.0-31-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 420] [10de:0de2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:2302] InstallationDate: Installed on 2011-05-11 (896 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) JockeyStatus: kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use) MachineType: Dell Inc. XPS 8300 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=0b19268c-a493-49b7-81d6-7249daf74712 ro quiet splash SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-10-18 (6 days ago) dmi.bios.date: 02/15/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/15/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Oct 18 10:51:55 2013 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to:
[Dx-packages] [Bug 1244225] Re: Display is unrefreshed/corrupted when opening/closing/switching windows and tabs
[Expired for Compiz because there has been no activity for 60 days.] ** Changed in: compiz Status: Incomplete = Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1244225 Title: Display is unrefreshed/corrupted when opening/closing/switching windows and tabs Status in Compiz: Expired Status in “unity” package in Ubuntu: Expired Bug description: When I switch between windows, or switch between tabs in the same window, or switch desktops, part or all of the affected windows often fail to repaint (or repaint and then revert to stale content). Unfocusing/refocusing the affected window usually forces it to repaint again (but may then leave another window stale). It doesn't seem toolkit-specific (happens with xchat, firefox, chrome, skype, gnome-terminal, ...). Attached is a screenshot showing an example of corruption after switching between two tabs in xchat. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.32 Wed Jun 19 15:51:20 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity: Error: [Errno 21] Is a directory: '/tmp/unity' .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,compiztoolbox,vpswitch,move,gnomecompat,grid,place,regex,imgpng,resize,annotate,mousepoll,wobbly,session,animation,fade,animationaddon,cube,rotate,workarounds,unitymtgrabhandles,cubeaddon,trailfocus,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Oct 24 15:15:48 2013 DistUpgraded: 2013-10-18 10:50:28,943 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-319, 319.32, 3.11.0-12-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. nvidia-319, 319.32, 3.8.0-31-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 420] [10de:0de2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:2302] InstallationDate: Installed on 2011-05-11 (896 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) JockeyStatus: kmod:nvidia_319_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_319 - nvidia_319 (Proprietary, Enabled, Not in use) MachineType: Dell Inc. XPS 8300 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=0b19268c-a493-49b7-81d6-7249daf74712 ro quiet splash SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-10-18 (6 days ago) dmi.bios.date: 02/15/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/15/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Oct 18 10:51:55 2013 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to:
[Dx-packages] [Bug 1253456] [NEW] Suspend takes 20 seconds
You have been subscribed to a public bug: My ThinkPad X220 with Ubuntu 13.10 (upgraded from previous versions) takes 20 seconds or more to suspend. This wasn't the case with 13.04. During those 20 seconds I can reactivate the screen (which turns off properly) and then login and use the laptop (until it suspends after some time). If I login before suspend, I don't have to login on resume. The issue is present with all of these ways to suspend: - closing the lid - using the Unity menu - Suspend - sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m Calling sudo pm-suspend on the other hand always works immediately. I can't use this as a workaround, because it doesn't ask for the password on resume. For logs, see this bugreport: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121) pm-utils version is 1.4.1-12ubuntu1 I don't know if this is designed like this on purpose or a (related?) bug: The login screen I get after resume is quite different from the one I get on normal startup (see other bug report for details on that). ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: Incomplete -- Suspend takes 20 seconds https://bugs.launchpad.net/bugs/1253456 You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1253456] Re: Suspend takes 20 seconds
I don't know if this is designed like this on purpose or a (related?) bug: The login screen I get after resume is quite different from the one I get on normal startup Yes, that's the screensaver, while the initial one is lightdm. As pm-suspend works, this is not a bug in pm-utils but somewhere in the higher levels. Can you please enable system D-BUS debugging as on https://wiki.ubuntu.com/DebuggingDBus and create/attach a system D-BUS debug log what happens when you run sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 [...] or just use the unity menu? ** Package changed: pm-utils (Ubuntu) = systemd-shim (Ubuntu) ** Changed in: systemd-shim (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1253456 Title: Suspend takes 20 seconds Status in “systemd-shim” package in Ubuntu: Incomplete Bug description: My ThinkPad X220 with Ubuntu 13.10 (upgraded from previous versions) takes 20 seconds or more to suspend. This wasn't the case with 13.04. During those 20 seconds I can reactivate the screen (which turns off properly) and then login and use the laptop (until it suspends after some time). If I login before suspend, I don't have to login on resume. The issue is present with all of these ways to suspend: - closing the lid - using the Unity menu - Suspend - sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m Calling sudo pm-suspend on the other hand always works immediately. I can't use this as a workaround, because it doesn't ask for the password on resume. For logs, see this bugreport: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121) pm-utils version is 1.4.1-12ubuntu1 I don't know if this is designed like this on purpose or a (related?) bug: The login screen I get after resume is quite different from the one I get on normal startup (see other bug report for details on that). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1253456/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
that 30 lines were not enough. here are 300 ** Attachment added: nm2.log https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/3954113/+files/nm2.log -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
The last 30 lines of the network manager log as requested. ** Attachment added: nm2.log https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/3954102/+files/nm2.log -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
When doing sudo pm-suspend, the log does *not* contain the lines [nm-sleep-monitor-systemd.c:150] signal_cb(): Received PrepareForSleep signal: 1 [nm-manager.c:3511] sleeping_cb(): Received sleeping signal -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
Christian, that still looks incomplete: the log ends after the suspend, but there is nothing at all after resume? If you do pm-suspend then the PrepareForSleep signal isn't sent, as that's a logind thing. Christian, I didn't get a system D-BUS monitor log from you yet. If that really is the whole NM log, then for you the PrepareForSleep False signal seems to be missing; please follow https://wiki.ubuntu.com/DebuggingDBus to create a system bus debug log during a suspend cycle. Thanks! -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
