[Dx-packages] [Bug 1304568] Re: Upgrade 12.04 LTS to 14.04LTS Beta 2 lost panel launch
I am not able to attach $HOME/.cache/upstart/gnome-session-Unity.log so attaching content of $HOME/.cache/upstart/gnome-session-Unity.log (gnome-terminal:2913): GLib-GIO-CRITICAL **: g_settings_get: the format string may not contain '' (key 'monospace-font-name' from schema 'org.gnome.desktop.interface'). This call will probably stop working with a future version of glib. /var/lib/dpkg/lock: ** (zeitgeist-datahub:2673): WARNING **: zeitgeist-datahub.vala:212: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required ** (zeitgeist-datahub:2673): WARNING **: zeitgeist-datahub.vala:212: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required ~ i ran apport-collect 1304568 but is showed a message You are not the reporter or subscriber of this problem report or the report is a duplicate or already closed please create a new report using apport-bug and apport-bug shows nothing -- 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/1304568 Title: Upgrade 12.04 LTS to 14.04LTS Beta 2 lost panel launch Status in “unity” package in Ubuntu: Incomplete Bug description: Have used 14.04LTS Beta 2 for about a week, it was an in place upgrade, all seemed well. However this morning starting the system I got the background but no panel and no launcher. Right click on the screen gave the settings menu and all settings could be accessed, but still no launcher or panel. I downloaded 14.04LTS Beta2 and made a USB stick, did a complete install, formatting / but not the other paritions. When restarted again no panel, no launcher but access to the settings menuis available. I used to be able to start terminal by using ctrl+alt+t, but that does not work anymore. ICannot access anything on the perfectly good screen. Shutting down by pressing the startup knob and then restarting provides the sam eproblem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1304568/+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 1247579] Re: unity-panel-service tons of logs
I just found I encounter this bug, following is the log I collects. /.cache/upstart$ pwd /home/diabloneo/.cache/upstart ~/.cache/upstart$ ll unity-panel-service.log -h -rw-r- 1 diabloneo diabloneo 53G Apr 13 16:29 unity-panel-service.log ~/.cache/upstart$ tail -n 20 unity-panel-service.log [08:26:37.656064 GLib-GObject-Critical] g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed [08:26:37.656084 GLib-GObject-Warning] invalid (NULL) pointer instance [08:26:37.656101 GLib-GObject-Critical] g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed [08:26:37.656121 GLib-GObject-Warning] invalid (NULL) pointer instance [08:26:37.656136 GLib-GObject-Critical] g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed [08:26:37.656153 GLib-GObject-Warning] invalid (NULL) pointer instance [08:26:37.656169 GLib-GObject-Critical] g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed [08:26:37.656187 GLib-GObject-Warning] invalid (NULL) pointer instance [08:26:37.656201 GLib-GObject-Critical] g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed [08:26:37.656226 GLib-GObject-Warning] invalid (NULL) pointer instance [08:26:37.656242 GLib-GObject-Critical] g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed [08:26:37.656262 GLib-GObject-Warning] invalid (NULL) pointer instance [08:26:37.656278 GLib-GObject-Critical] g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed [08:26:37.656296 GLib-GObject-Warning] invalid (NULL) pointer instance [08:26:37.656311 GLib-GObject-Critical] g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed [08:26:37.656328 GLib-GObject-Warning] invalid (NULL) pointer instance [08:26:37.656342 GLib-GObject-Critical] g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed [08:27:00.244143 Warning] Unable to support GtkImageType: 0 [08:28:00.244652 Warning] Unable to support GtkImageType: 0 [08:29:00.243693 Warning] Unable to support GtkImageType: 0 ~/.cache/upstart$ uname -a Linux diabloneo-ThinkPad-X230 3.11.0-19-generic #33-Ubuntu SMP Tue Mar 11 18:48:34 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux === Then I delete the file, and it's generated again and keep growing up. ~/.cache/upstart$ lsof | grep unity-panel-service.log init 3660 diabloneo 17w REG8,1 1190 4194308 /home/diabloneo/.cache/upstart/unity-panel-service.log ~/.cache/upstart$ ll total 16 -rw-r- 1 diabloneo diabloneo 1021 Apr 13 16:47 dbus.log -rw-r- 1 diabloneo diabloneo 4537 Apr 13 16:40 gnome-session.log -rw-r- 1 diabloneo diabloneo 1260 Apr 13 16:48 unity-panel-service.log ~/.cache/upstart$ ll total 16 -rw-r- 1 diabloneo diabloneo 2108 Apr 13 16:49 dbus.log -rw-r- 1 diabloneo diabloneo 4537 Apr 13 16:40 gnome-session.log -rw-r- 1 diabloneo diabloneo 3000 Apr 13 16:49 unity-panel-service.log -- 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/1247579 Title: unity-panel-service tons of logs Status in “unity” package in Ubuntu: Expired Bug description: Since this morning, unity-panel-service generate lot of logs in .cache/upstart. I have 10Go of log every 30minutes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1247579/+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 1299080] Re: [UIFe] New style force-quit window dialog
I have already seen the new dialogs in action several times (slow machine) - I wonder why wasn't this bug closed already. ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released ** Changed in: unity Status: In Progress = Fix Committed -- 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/1299080 Title: [UIFe] New style force-quit window dialog Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: In order to fix the regression lp:1299061 we want to introduce a new styled dialog (as designed lp:698031) inside unity (it used to be in compiz gtk-window-decorator before). Unfortunately this introduces two new strings: - This window is not responding - Do you want to force the application to exit, or wait for it to respond? Result: http://people.ubuntu.com/~3v1n0/shots/force-quit-dialog- new.png Translators ML: https://lists.ubuntu.com/archives/ubuntu-translators/2014-March/006439.html Docs ML: in moderation queue... To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299080/+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 1305412] Re: After locking screen sometimes must login twice
Same here. Issue resolved after 3.6.1-0ubuntu13 upgrade. Thanks. -- 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/1305412 Title: After locking screen sometimes must login twice Status in Unity: New Status in “unity” package in Ubuntu: Incomplete Bug description: Using Ubuntu 14.04 final beta. Intermittently, when I lock the screen then unlock after a period of time the screen locks again by itself and I must unlock one more time. To date I haven't found a pattern for when this happens other than it seems to occur when the computer has been locked for several minutes. The computer has not been suspended. Steps: 1. Lock screen 2. Leave locked for several minutes 3. Login to unlock Screen refreshes to the desktop. Then all of a sudden the screen locks itself and I must re-enter my password and unlock the screen yet again. After that the system is stable and I can continue to work. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305412/+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 1303468] Re: [Regression] Unity Gestures: 4 Finger Tap directly after login results in empty dash
** Changed in: unity Status: In Progress = 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/1303468 Title: [Regression] Unity Gestures: 4 Finger Tap directly after login results in empty dash Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: The problem: If the dash has not been opened before using the Super-Key or launcher icon, the 4 finger tap results in showing an empty dash that does not have the home scope selected. The fix: Show the home scope if the dash is opened the first time after login using the 4 finger tap. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Apr 6 22:00:48 2014 InstallationDate: Installed on 2014-04-04 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303468/+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 1307118] [NEW] Unity freezes on resuming from suspend
Public bug reported: After suspending laptop (by closing the laptop screen) and then resuming, the screen is black and doesn't seem to take any keyboard or mouse input. As a result, the only way to fix the situation is to hard reboot the system. Steps to reproduce: 1. Suspend laptop 2. Wait for at least 10-15 minutes 3. Try resuming What happens: Black screen with the mouse cursor visible. However the whole screen is frozen. No keyboard or mouse input is accepted. As a result, I cannot switch to any vt to reboot or restart the lightdm process What should happen: Unity lockscreen is shown where one can enter the password and return to the user session gnome-screensaver: 3.6.1-0ubuntu13 amd64 [Installed] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 13 13:56:56 2014 DistUpgraded: 2014-02-27 11:46:48,360 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2013-09-18 (207 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130802) MachineType: LENOVO 20217 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=63532c2e-8584-466e-8215-2d6770489a00 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-27 (45 days ago) dmi.bios.date: 06/04/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN32WW(V2.02) dmi.board.asset.tag: YB00228460 dmi.board.name: 20217 dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: YB00228460 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN32WW(V2.02):bd06/04/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rn20217:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 13 13:51:07 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0) NOUVEAU(G0): Error initialising acceleration. Falling back to NoAccel xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 489 vendor LGD xserver.version: 2:1.15.0-1ubuntu7 ** Affects: unity Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu ** Description changed: After suspending laptop (by closing the laptop screen) and then resuming, the screen is black and doesn't seem to take any keyboard or mouse input. As a result, the only way to fix the situation is to hard reboot the system. Steps to reproduce: 1. Suspend laptop 2. Wait for at least 10-15 minutes 3. Try resuming What happens: Black screen with the mouse cursor visible. However the whole screen is frozen. No keyboard or mouse input is accepted. As a result, I cannot switch to any vt to reboot or restart the lightdm process What should happen: Unity lockscreen is shown where one can enter the password and return to the user session + gnome-screensaver: 3.6.1-0ubuntu13 amd64 [Installed] + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux
[Dx-packages] [Bug 1307118] Re: Unity freezes on resuming from suspend
FYI, I did look at https://bugs.launchpad.net/unity/+bug/1301125, however in that bug the unity freeze occurs only after the system is locked after idle time. In my case, the unity freeze after manually suspending and then resuming from freeze after 10-15 minutes. -- 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/1307118 Title: Unity freezes on resuming from suspend Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: After suspending laptop (by closing the laptop screen) and then resuming, the screen is black and doesn't seem to take any keyboard or mouse input. As a result, the only way to fix the situation is to hard reboot the system. Steps to reproduce: 1. Suspend laptop 2. Wait for at least 10-15 minutes 3. Try resuming What happens: Black screen with the mouse cursor visible. However the whole screen is frozen. No keyboard or mouse input is accepted. As a result, I cannot switch to any vt to reboot or restart the lightdm process What should happen: Unity lockscreen is shown where one can enter the password and return to the user session gnome-screensaver: 3.6.1-0ubuntu13 amd64 [Installed] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 13 13:56:56 2014 DistUpgraded: 2014-02-27 11:46:48,360 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2013-09-18 (207 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130802) MachineType: LENOVO 20217 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=63532c2e-8584-466e-8215-2d6770489a00 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-27 (45 days ago) dmi.bios.date: 06/04/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN32WW(V2.02) dmi.board.asset.tag: YB00228460 dmi.board.name: 20217 dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: YB00228460 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN32WW(V2.02):bd06/04/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rn20217:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 13 13:51:07 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0) NOUVEAU(G0): Error initialising acceleration. Falling back to NoAccel xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 489 vendor LGD xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1307118/+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 1303468] Re: [Regression] Unity Gestures: 4 Finger Tap directly after login results in empty dash
** Changed in: unity Status: Fix Released = Fix Committed ** Changed in: unity Milestone: None = 7.2.1 -- 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/1303468 Title: [Regression] Unity Gestures: 4 Finger Tap directly after login results in empty dash Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: The problem: If the dash has not been opened before using the Super-Key or launcher icon, the 4 finger tap results in showing an empty dash that does not have the home scope selected. The fix: Show the home scope if the dash is opened the first time after login using the 4 finger tap. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Apr 6 22:00:48 2014 InstallationDate: Installed on 2014-04-04 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303468/+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 1307128] [NEW] Dash Search Keeps Launching Tomboy Instances When Tomboy Source is ON
Public bug reported: When Tomboy search source is ENABLED in Unity Dash, a simple search is enough to trigger launching of new Tomboy instances. Once the source is DISABLED, no search triggers this bug. How to reproduce: Enable the Tomboy source, open Dash and start typing something what might trigger Tomboy. Say, typing Tomboy or just Tom and so on, and deleting it and typing again, is enough to keep firing new instances. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 Uname: Linux 3.14.0-031400rc8-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: GNOME Date: Sun Apr 13 14:34:16 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-19 (297 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=lt_LT.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-10 (3 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug third-party-packages 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/1307128 Title: Dash Search Keeps Launching Tomboy Instances When Tomboy Source is ON Status in “unity” package in Ubuntu: Confirmed Bug description: When Tomboy search source is ENABLED in Unity Dash, a simple search is enough to trigger launching of new Tomboy instances. Once the source is DISABLED, no search triggers this bug. How to reproduce: Enable the Tomboy source, open Dash and start typing something what might trigger Tomboy. Say, typing Tomboy or just Tom and so on, and deleting it and typing again, is enough to keep firing new instances. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 Uname: Linux 3.14.0-031400rc8-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: GNOME Date: Sun Apr 13 14:34:16 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-19 (297 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=lt_LT.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-10 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307128/+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 1303141] Re: [Regression] Unity Gestures: Launcher doesn't slide in
** Changed in: unity Status: Fix Released = Fix Committed -- 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/1303141 Title: [Regression] Unity Gestures: Launcher doesn't slide in Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: I just tried Ubuntu 12.04.4 from a USB stick to compare it to 14.04. On 12.04 the launcher does slide in beautifully and in sync with the fingers when swiping with 4 fingers from left to right on a touchpad. The problem: On 14.04 the launcher suddenly appears, giving no hint on whether the gesture acually works or how far the launcher is slided in. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Apr 5 21:32:52 2014 InstallationDate: Installed on 2014-04-04 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303141/+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 1307128] Re: Dash Search Keeps Launching Tomboy Instances When Tomboy Source is ON
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/1307128 Title: Dash Search Keeps Launching Tomboy Instances When Tomboy Source is ON Status in “unity” package in Ubuntu: Confirmed Bug description: When Tomboy search source is ENABLED in Unity Dash, a simple search is enough to trigger launching of new Tomboy instances. Once the source is DISABLED, no search triggers this bug. How to reproduce: Enable the Tomboy source, open Dash and start typing something what might trigger Tomboy. Say, typing Tomboy or just Tom and so on, and deleting it and typing again, is enough to keep firing new instances. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 Uname: Linux 3.14.0-031400rc8-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: GNOME Date: Sun Apr 13 14:34:16 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-19 (297 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=lt_LT.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-10 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307128/+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 1307132] [NEW] force-quit dialog is not being rendered properly
Public bug reported: Recently I had some applications freeze and had to be quit forcefully. At that time, I saw the new force-quit dialog, however it is not being rendered properly. You can see a screenshot of it at https://imgur.com/jnGt0IY. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 13 14:58:08 2014 DistUpgraded: 2014-02-27 11:46:48,360 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2013-09-18 (207 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130802) MachineType: LENOVO 20217 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=63532c2e-8584-466e-8215-2d6770489a00 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-27 (45 days ago) dmi.bios.date: 06/04/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN32WW(V2.02) dmi.board.asset.tag: YB00228460 dmi.board.name: 20217 dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: YB00228460 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN32WW(V2.02):bd06/04/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rn20217:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 13 13:51:07 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0) NOUVEAU(G0): Error initialising acceleration. Falling back to NoAccel xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 489 vendor LGD xserver.version: 2:1.15.0-1ubuntu7 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1307132 Title: force-quit dialog is not being rendered properly Status in “unity” package in Ubuntu: New Bug description: Recently I had some applications freeze and had to be quit forcefully. At that time, I saw the new force-quit dialog, however it is not being rendered properly. You can see a screenshot of it at https://imgur.com/jnGt0IY. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 13 14:58:08 2014 DistUpgraded: 2014-02-27 11:46:48,360 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1)
[Dx-packages] [Bug 1305412] Re: After locking screen sometimes must login twice
*** This bug is a duplicate of bug 1292451 *** https://bugs.launchpad.net/bugs/1292451 ** This bug has been marked a duplicate of bug 1292451 screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked -- 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/1305412 Title: After locking screen sometimes must login twice Status in Unity: New Status in “unity” package in Ubuntu: Incomplete Bug description: Using Ubuntu 14.04 final beta. Intermittently, when I lock the screen then unlock after a period of time the screen locks again by itself and I must unlock one more time. To date I haven't found a pattern for when this happens other than it seems to occur when the computer has been locked for several minutes. The computer has not been suspended. Steps: 1. Lock screen 2. Leave locked for several minutes 3. Login to unlock Screen refreshes to the desktop. Then all of a sudden the screen locks itself and I must re-enter my password and unlock the screen yet again. After that the system is stable and I can continue to work. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305412/+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 1299706] Re: distortions in Unity after lock screen
** Changed in: unity (Ubuntu) Status: New = Incomplete -- 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/1299706 Title: distortions in Unity after lock screen Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Hi, I locked my Ubuntu, then I unlocked it, opened DASH, then it lock again without my will as I describe in bug report #1299705 . The problem is, Unity is not rendered good in MacbookAir with sandy bridge, because if I do this: Lock screen - unlock - open DASH - then it locks without my will . in MacbookAir it do NOT show me it is locked, all I can see it something that left from DASH with black background, without left panel but WITH top panel. I think this can be a security issue because in this point I cannot know I am on lockscreen or not and so typing password can be dangerous. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.3-0ubuntu1 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] CurrentDesktop: Unity Date: Sun Mar 30 10:36:01 2014 InstallationDate: Installed on 2014-03-29 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140317) ProcEnviron: LANGUAGE=cs PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=cs_CZ.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299706/+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 1305586] Re: Lock screen is unusable when a client has a keyboard/mouse grab
This happens just with the ssh password dialog. With other grabs the lock fails to start. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Lock screen is unusable when a client has a keyboard/mouse grab + Lock screen is unusable when a ssh dialog has a keyboard/mouse grab ** Changed in: unity Status: New = Triaged ** 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/1305586 Title: Lock screen is unusable when a ssh dialog has a keyboard/mouse grab Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305586/+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 1199571] Re: compiz crashed with SIGSEGV in af_latin_hints_compute_edges()
I looked at my coredump on trusty (it crashed for me twice already!) with gdb and I see evidence that this crash might be due to multithreading issues. The reason is that when inspecting memory at %rdx (edge) and I see that a pointer at %rdx+0x48 (edge-first) doesn't match with a pointer in %rcx (edge-first taken at the start of the loop). Besides, freetype code can never produce %rax == 0 at the crash location, this would only happen if af_latin_hints_compute_edges is called concurrently on the same hints structure, which causes pointers to change for segments that are processed in another thread. Best of luck, ThreadStackTrace.txt shows exactly that, two threads are in af_latin_hints_compute_edges with same parameters! Now the real question is which application or library is actually violating thread-safety here... -- 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/1199571 Title: compiz crashed with SIGSEGV in af_latin_hints_compute_edges() Status in “unity” package in Ubuntu: Triaged Bug description: Fresh dist-upgrade; brought up the dash, typed term; single clicked on the terminal app and _bang_. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 17:47:10 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-06 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax) PC (0x7ff3b4ed7a10) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1199571/+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 1199571] Re: compiz crashed with SIGSEGV in af_latin_hints_compute_edges()
I looked at the implementation of cairo-ft-font.c and it seems that there are huge multi-threading violations in cairo. The reason is that FreeType API documentation clearly states: In multi-threaded applications, make sure that the same FT_Library object or any of its children doesn't get accessed in parallel. Cairo initializes FT_Library for its font map and there's a lock for that, however it's only used for font map manipulations, the actual FT_ library calls are completely unprotected with that lock, although they should be! What adds to the injury is that cairo-ft-font.c even has this comment on one of its functions: You must be careful when using this function in a library or in a threaded application, because freetype's design makes it unsafe to call freetype functions simultaneously from multiple threads, (even if using distinct FT_Face objects) Too bad they don't follow their own advice, and no wonder compiz is crashing like that. Can somebody contact upstream about this issue and make them aware of it? -- 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/1199571 Title: compiz crashed with SIGSEGV in af_latin_hints_compute_edges() Status in “unity” package in Ubuntu: Triaged Bug description: Fresh dist-upgrade; brought up the dash, typed term; single clicked on the terminal app and _bang_. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 17:47:10 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-06 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax) PC (0x7ff3b4ed7a10) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1199571/+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 1305586] Re: Lock screen is unusable when a client has a keyboard/mouse grab
When I reported this bug I'd just had it with a prompt for an account password from e-d-s. Andrea Azzarone 1305...@bugs.launchpad.net wrote: This happens just with the ssh password dialog. With other grabs the lock fails to start. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Lock screen is unusable when a client has a keyboard/mouse grab + Lock screen is unusable when a ssh dialog has a keyboard/mouse grab ** Changed in: unity Status: New = Triaged ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1305586 Title: Lock screen is unusable when a ssh dialog has a keyboard/mouse grab To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305586/+subscriptions -- 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/1305586 Title: Lock screen is unusable when a ssh dialog has a keyboard/mouse grab Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305586/+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 1199571] Re: compiz crashed with SIGSEGV in af_latin_hints_compute_edges()
** Also affects: cairo Importance: Undecided Status: New -- 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/1199571 Title: compiz crashed with SIGSEGV in af_latin_hints_compute_edges() Status in “cairo” package in Ubuntu: New Status in “unity” package in Ubuntu: Triaged Bug description: Fresh dist-upgrade; brought up the dash, typed term; single clicked on the terminal app and _bang_. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 17:47:10 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-06 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax) PC (0x7ff3b4ed7a10) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1199571/+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 1199571] Re: compiz crashed with SIGSEGV in af_latin_hints_compute_edges()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cairo (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/1199571 Title: compiz crashed with SIGSEGV in af_latin_hints_compute_edges() Status in “cairo” package in Ubuntu: New Status in “unity” package in Ubuntu: Triaged Bug description: Fresh dist-upgrade; brought up the dash, typed term; single clicked on the terminal app and _bang_. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 17:47:10 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-06 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax) PC (0x7ff3b4ed7a10) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1199571/+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 1199571] Re: compiz crashed with SIGSEGV in af_latin_hints_compute_edges()
** Project changed: cairo = cairo (Ubuntu) -- 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/1199571 Title: compiz crashed with SIGSEGV in af_latin_hints_compute_edges() Status in “cairo” package in Ubuntu: New Status in “unity” package in Ubuntu: Triaged Bug description: Fresh dist-upgrade; brought up the dash, typed term; single clicked on the terminal app and _bang_. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 17:47:10 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-06 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax) PC (0x7ff3b4ed7a10) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1199571/+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 1305586] Re: Lock screen is unusable when a client has a keyboard/mouse grab
Eds? On Apr 13, 2014 4:50 PM, Iain Lane i...@orangesquash.org.uk wrote: When I reported this bug I'd just had it with a prompt for an account password from e-d-s. Andrea Azzarone 1305...@bugs.launchpad.net wrote: This happens just with the ssh password dialog. With other grabs the lock fails to start. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Lock screen is unusable when a client has a keyboard/mouse grab + Lock screen is unusable when a ssh dialog has a keyboard/mouse grab ** Changed in: unity Status: New = Triaged ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1305586 Title: Lock screen is unusable when a ssh dialog has a keyboard/mouse grab To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305586/+subscriptions -- You received this bug notification because you are subscribed to Unity. https://bugs.launchpad.net/bugs/1305586 Title: Lock screen is unusable when a ssh dialog has a keyboard/mouse grab Status in Unity: Triaged Status in unity package in Ubuntu: Confirmed Bug description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305586/+subscriptions -- 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/1305586 Title: Lock screen is unusable when a ssh dialog has a keyboard/mouse grab Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305586/+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 1305586] Re: Lock screen is unusable when a client has a keyboard/mouse grab
On Sun, Apr 13, 2014 at 05:07:18PM -, Andrea Azzarone wrote: Eds? evolution-data-server. My point was that it isn't specific to prompts from the SSH agent. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- 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/1305586 Title: Lock screen is unusable when a ssh dialog has a keyboard/mouse grab Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305586/+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 1306970] Re: Screensaver leaks password key-presses through to applications
I rebooted on Saturday morning (so had a fresh Unity session) and I got it today too, my Unity is 7.2.0+14.04.20140411-0ubuntu1. I'm afraid I can't remember how I locked it this time either, however this time I did notice that alt+tab would bring up the unity application switcher menu on top of the lock screen. I also managed to change my keyboard layout to US somehow. (In other news, I forgot to subscribe myself to this bug report. Fixing that.) -- 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/1306970 Title: Screensaver leaks password key-presses through to applications Status in “unity” package in Ubuntu: Confirmed Bug description: On more than one occasion I have been unable to focus on the password field. I typed my password in but it didn't appear. Eventually I managed to get focus on the password field, and unlocked. When I did, I found the active window had a copy of my password and some other keys I mashed only during the lock screen. Just had a friend confirm this happened to them. We shouldn't allow keypresses to leak through from the lock screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 12 16:24:59 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-01-02 (830 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120102) SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2013-12-09 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1306970/+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 1307198] [NEW] Bluetooth shuts down contact with mouse
Public bug reported: My Dell Vostro 3555 purchased in Sept 2011 is equipped with Bluetooth. I used a bluetooth mouse from then on and never lost contact between computer and mouse, not even when changing the battery in the mouse. Since installing 1404LTS Beta 2 the connection is shut down when the computer is shut down and sometimes when the computer goes into hibernation. This results in having to manually goto the Bluetooth GUI and the mouse and force the connection. The Bluetooth GUI has three on/off buttons, bluetooth , visibility on Ubuntu-0 and mouse. The mouse button is off wenever I start the system. This did not happen in any Ubuntu version of Linux I have had on this computer, other than in 14.04LTS. This is a nuisance, and prevents me from demonstrating how good Ubuntu Linux really is. Having to sit in a demo and manually pressing a button on the mouse until the on/off button turns on immediately turns off any interest a newbie might have. A quick fix would be appreciated. At this point I have no idea od what corroborating info I need to provide, but will send anything asked for. ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- 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/1307198 Title: Bluetooth shuts down contact with mouse Status in “unity” package in Ubuntu: New Bug description: My Dell Vostro 3555 purchased in Sept 2011 is equipped with Bluetooth. I used a bluetooth mouse from then on and never lost contact between computer and mouse, not even when changing the battery in the mouse. Since installing 1404LTS Beta 2 the connection is shut down when the computer is shut down and sometimes when the computer goes into hibernation. This results in having to manually goto the Bluetooth GUI and the mouse and force the connection. The Bluetooth GUI has three on/off buttons, bluetooth , visibility on Ubuntu-0 and mouse. The mouse button is off wenever I start the system. This did not happen in any Ubuntu version of Linux I have had on this computer, other than in 14.04LTS. This is a nuisance, and prevents me from demonstrating how good Ubuntu Linux really is. Having to sit in a demo and manually pressing a button on the mouse until the on/off button turns on immediately turns off any interest a newbie might have. A quick fix would be appreciated. At this point I have no idea od what corroborating info I need to provide, but will send anything asked for. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307198/+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 964333] Re: rhythmbox controls at unity does not work
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect bug # and any other logs that are relevant for this particular issue. ** Changed in: rhythmbox (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/964333 Title: rhythmbox controls at unity does not work Status in Sound Menu: Invalid Status in “indicator-sound” package in Ubuntu: Invalid Status in “rhythmbox” package in Ubuntu: Incomplete Bug description: I use Dell XPS 1640, running Ubuntu 12. Rhythmbox controls at unity (top notification bar under the sound section) do not work. None of them works (play, previous, next...), also when i click on the name, while it should show the main window, it does nothing. It was fine before i did Ubuntu updates this week, i wonder if that caused the problem or something else. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.95-0ubuntu1 Architecture: i386 Date: Sun Mar 25 12:50:13 2012 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/964333/+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 1282884] Re: compiz crashed with SIGSEGV in __dynamic_cast()
im having issues with my compiz. im somewhat new to ubuntu and am on 14.04. I was on 13.10 and upgraded after having issues where my ccsm wouldnt open and its a consistant crash. I cant figure out why it wont open and is 100% crash all the time. i even went to the point where i reinstalled every app that i thought was involved and it did nothing to help. I just want to be able to run ccsm and enjoy a more interactive interface, as well as learn about ubuntu and continue on. Would appreciate it you could help fix this and help me understand how to fix this if the problem continues. thank you. -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1282884 Title: compiz crashed with SIGSEGV in __dynamic_cast() Status in Nux: Fix Released Status in “nux” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: $ apt-cache policy compiz compiz: Installed: 1:0.9.11+14.04.20140218-0ubuntu1 Candidate: 1:0.9.11+14.04.20140218-0ubuntu1 Version table: *** 1:0.9.11+14.04.20140218-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy unity unity: Installed: 7.1.2+14.04.20140220-0ubuntu1 Candidate: 7.1.2+14.04.20140220-0ubuntu1 Version table: *** 7.1.2+14.04.20140220-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status $ dmesg [ 3920.925590] compiz[2391]: segfault at 8038 ip 7f863004e31c sp 7fff232998d0 error 4 in libstdc++.so.6.0.19[7f862fff1000+e6000] ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 21 13:20:30 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2012-09-30 (508 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.1) ProcCmdline: compiz Signal: 11 SourcePackage: unity StacktraceTop: __dynamic_cast () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 nux_base_window_accessible_check_active () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in __dynamic_cast() UpgradeStatus: Upgraded to trusty on 2013-11-10 (102 days ago) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1282884/+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 1307132] Re: force-quit dialog is not being rendered properly
Indeed there's a regression on shadows, but since it seems you're using a custom theme, isn't that doing something wrong for force-quit dialog background (see https://wiki.ubuntu.com/Unity/Theming#Windows_Force_Quit_dialog)? -- 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/1307132 Title: force-quit dialog is not being rendered properly Status in “unity” package in Ubuntu: New Bug description: Recently I had some applications freeze and had to be quit forcefully. At that time, I saw the new force-quit dialog, however it is not being rendered properly. You can see a screenshot of it at https://imgur.com/jnGt0IY. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 13 14:58:08 2014 DistUpgraded: 2014-02-27 11:46:48,360 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2013-09-18 (207 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130802) MachineType: LENOVO 20217 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=63532c2e-8584-466e-8215-2d6770489a00 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-27 (45 days ago) dmi.bios.date: 06/04/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN32WW(V2.02) dmi.board.asset.tag: YB00228460 dmi.board.name: 20217 dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: YB00228460 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN32WW(V2.02):bd06/04/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rn20217:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 13 13:51:07 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0) NOUVEAU(G0): Error initialising acceleration. Falling back to NoAccel xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 489 vendor LGD xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307132/+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 1307118] Re: Unity freezes on resuming from suspend
If you can't Ctrl+Alt+F1 to move to tty1, then it's not an unity bug. But it seems a resume issue instead. -- 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/1307118 Title: Unity freezes on resuming from suspend Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: After suspending laptop (by closing the laptop screen) and then resuming, the screen is black and doesn't seem to take any keyboard or mouse input. As a result, the only way to fix the situation is to hard reboot the system. Steps to reproduce: 1. Suspend laptop 2. Wait for at least 10-15 minutes 3. Try resuming What happens: Black screen with the mouse cursor visible. However the whole screen is frozen. No keyboard or mouse input is accepted. As a result, I cannot switch to any vt to reboot or restart the lightdm process What should happen: Unity lockscreen is shown where one can enter the password and return to the user session gnome-screensaver: 3.6.1-0ubuntu13 amd64 [Installed] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 13 13:56:56 2014 DistUpgraded: 2014-02-27 11:46:48,360 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2013-09-18 (207 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130802) MachineType: LENOVO 20217 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=63532c2e-8584-466e-8215-2d6770489a00 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-27 (45 days ago) dmi.bios.date: 06/04/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN32WW(V2.02) dmi.board.asset.tag: YB00228460 dmi.board.name: 20217 dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: YB00228460 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN32WW(V2.02):bd06/04/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rn20217:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 13 13:51:07 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0) NOUVEAU(G0): Error initialising acceleration. Falling back to NoAccel xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 489 vendor LGD xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1307118/+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 1306970] Re: Screensaver leaks password key-presses through to applications
** Also affects: unity Importance: Undecided Status: New ** Tags added: lockscreen -- 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/1306970 Title: Screensaver leaks password key-presses through to applications Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: On more than one occasion I have been unable to focus on the password field. I typed my password in but it didn't appear. Eventually I managed to get focus on the password field, and unlocked. When I did, I found the active window had a copy of my password and some other keys I mashed only during the lock screen. Just had a friend confirm this happened to them. We shouldn't allow keypresses to leak through from the lock screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 12 16:24:59 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-01-02 (830 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120102) SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2013-12-09 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1306970/+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 1306968] Re: After unlocking the desktop, it locks itself again.
** Tags added: lockscreen ** Also affects: unity Importance: Undecided Status: New -- 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/1306968 Title: After unlocking the desktop, it locks itself again. Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: After idling for some time my desktop locks. When I return and enter the password, it unlocks and I briefly see my desktop and open applications before it locks itself again. After entering the password (again), it seems to work fine. Expected behavior: The desktop shouldn't lock immediately after unlocking. Reproduce: 1. Let the screen lock on its own. Using CTRL-ALT-L seems to only require unlocking once. 2. Try to unlock the desktop using your password. It will relock (for me). I have a feeling it might have something to do with the monitor going to sleep, which might explain why CTRL-ALT-L seems to work (the monitor never sleeps.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Apr 11 14:38:30 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:304a] InstallationDate: Installed on 2014-04-02 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic root=UUID=e01ba637-d590-489e-ba5a-d0a4f1ed4cae ro quiet splash nomdmonddf nomdmonisw SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A74MX-S/A74MX-K dmi.board.vendor: FOXCONN dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd03/05/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnFOXCONN:rnA74MX-S/A74MX-K:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Apr 9 08:51:09 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Keyboard KEYBOARD, id 8 inputLogitech USB Keyboard KEYBOARD, id 9 inputLogitech Unifying Device. Wireless PID:1025 MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1306968/+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 1305127] Re: Skype systray icon disappear
** Also affects: skype (Ubuntu) Importance: Undecided Status: New ** Also affects: unity Importance: Undecided Status: New ** No longer affects: skype (Ubuntu) ** Changed in: unity Status: New = Triaged ** Changed in: unity Milestone: None = 7.2.1 -- 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/1305127 Title: Skype systray icon disappear Status in Unity: Triaged Status in “unity” package in Ubuntu: New Bug description: I did a Ubuntu 14.04 beta 2 fresh install on one of my notebooks. After that I install Skype from partner repository. The Skype icon in systray shows at start, but disappear after login into my Skype account. Any questions about this just ask. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1305127/+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 1303462] Re: [Regression] Window titlebars placed behind panel
** Changed in: unity Status: Triaged = Invalid -- 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/1303462 Title: [Regression] Window titlebars placed behind panel Status in Compiz: Triaged Status in Unity: Invalid Status in “unity” package in Ubuntu: Triaged Bug description: Windows with a height of (Display Height - Panel Height) get placed at y=0 (behind the top panel) which means window titlebars are not reachable without alt-moving the window. I assume this happens with windows that want to resize themselves if their height exceeds the display resolution. Reproducable on my 1366x768 screen with LibreOffice and a Qt 5 desktop application I'm working on. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Apr 6 21:45:41 2014 InstallationDate: Installed on 2014-04-04 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1303462/+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 1307198] Re: Bluetooth shuts down contact with mouse
** Changed in: unity (Ubuntu) Status: New = Invalid ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1307198 Title: Bluetooth shuts down contact with mouse Status in “bluez” package in Ubuntu: New Status in “unity” package in Ubuntu: Invalid Bug description: My Dell Vostro 3555 purchased in Sept 2011 is equipped with Bluetooth. I used a bluetooth mouse from then on and never lost contact between computer and mouse, not even when changing the battery in the mouse. Since installing 1404LTS Beta 2 the connection is shut down when the computer is shut down and sometimes when the computer goes into hibernation. This results in having to manually goto the Bluetooth GUI and the mouse and force the connection. The Bluetooth GUI has three on/off buttons, bluetooth , visibility on Ubuntu-0 and mouse. The mouse button is off wenever I start the system. This did not happen in any Ubuntu version of Linux I have had on this computer, other than in 14.04LTS. This is a nuisance, and prevents me from demonstrating how good Ubuntu Linux really is. Having to sit in a demo and manually pressing a button on the mouse until the on/off button turns on immediately turns off any interest a newbie might have. A quick fix would be appreciated. At this point I have no idea od what corroborating info I need to provide, but will send anything asked for. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1307198/+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 1303066] Re: Maximize button looks blurry with display scale of 0.825
Well, unfortunately we can't do much... That's what happen when you resize the svg file, and so probably the only solution would be for you to provide a svg file with smaller native resolution. ** Changed in: unity (Ubuntu) Status: New = Opinion -- 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/1303066 Title: Maximize button looks blurry with display scale of 0.825 Status in “unity” package in Ubuntu: Opinion Bug description: Since my laptop only has a display resolution of 1366x768 I like to gain more space by scaling down using the new capabilities in display settings. The problem: Maximize button looks blurry with display scale of 0.825 (screenshot attatched) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Apr 5 16:50:29 2014 InstallationDate: Installed on 2014-04-04 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404) 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/1303066/+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 1302835] Re: unity hud shows through screensaver
** Changed in: unity (Ubuntu) Status: New = 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/1302835 Title: unity hud shows through screensaver Status in “unity” package in Ubuntu: Fix Released Bug description: I'm seeing a bug that sounds somewhat similar to the old bug 771391. On trusty sometimes the Unity HUD shows through the screensaver. I will attach a photo of the issue. --- .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2014-03-16 (19 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140315) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD5H Package: unity 7.2.0+14.04.20140403-0ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-21-generic.efi.signed root=UUID=19efb927-173d-42b5-bb48-163ee5cb72d8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Tags: trusty trusty trusty ubuntu compiz-0.9 Uname: Linux 3.13.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87X-UD5H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/02/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87X-UD5H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Apr 3 00:58:55 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputLogitech Unifying Device. Wireless PID:101b MOUSE, id 9 inputLogitech Unifying Device. Wireless PID:2008 KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22746 vendor GSM xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302835/+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 1302663] Re: Unity's Scale UI function problematic on some devices.
FYI, from a tty you can fix the problem by running: gsettings reset com.ubuntu.user-interface scale-factor ** Also affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New = Invalid ** Also affects: unity-control-center Importance: Undecided Status: New -- 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/1302663 Title: Unity's Scale UI function problematic on some devices. Status in Unity Control Center: New Status in “unity” package in Ubuntu: Invalid Status in “unity-control-center” package in Ubuntu: New Bug description: I'm running a fully updated (as of 4/1/2014) install of Ubuntu 14.04 64 bit. This is on a Toshiba ultrabook with a mobile i5 processor and a 13.3 screen @ 1366x768. Earlier I was messing with the scale UI mode of the system settings display field. I set my UI scale to be maxed out at 4. Once done, windows were so large it was impossible to see. I couldn't even see any options within system settings besides two. Scrolling of course helped a bit but it was largely cumbersome. Once I went into the displays section to turn UI scaling back down to 1, I realized the function was far out of reach on my screen. I tried to hold down ALT and click to drag the window up beyond the top edge, but Unity crashed. In fact, every single time I hit the ALT key and clicked to drag, Unity crashed. Once Unity crashes 2 or 3 times, it doesn't come back without a hard power down and full startup. On the flip side, I plugged in an external monitor with a resolution of 1440x900. Once done, suddenly ALT worked and I had no crashes. I was able to drag the displays window up until I could see the UI scaling feature and turn it back down to 1. There's a few issues here that I feel need to be addressed, since there's little doubt that people will tinker with these functions. After all, these features are baked directly in to the interface as available parameters, but as notated above, settings (such as 4) render the system into a non-usable (and non-fixable without accessive tinkering) state. Is there a way higher UI scaling modes can be altered for easier scrolling or maneuvering of windows to reset it back if need be? Perhaps a work around could even be a reset to defaults button at the top bar? After all, with a UI scaling of 4, I could see the top of the window - just very little else. If I could have reset to default that would have alleviated any headaches. Thanks for all of your hard work! It's appreciated. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Apr 4 11:10:27 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0009] InstallationDate: Installed on 2014-04-01 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140330) MachineType: TOSHIBA PORTEGE Z835 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic root=UUID=5d7f7158-1b5b-4946-9916-b8a0c2f59525 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd02/08/2012:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-013021:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z835 dmi.product.version: PT224U-013021 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
[Dx-packages] [Bug 1306970] Re: Screensaver leaks password key-presses through to applications
This bug might be related to bug 1306417 which was supposedly fixed the other day (unity package version 7.2.0+14.04.20140411-0ubuntu1). -- 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/1306970 Title: Screensaver leaks password key-presses through to applications Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: On more than one occasion I have been unable to focus on the password field. I typed my password in but it didn't appear. Eventually I managed to get focus on the password field, and unlocked. When I did, I found the active window had a copy of my password and some other keys I mashed only during the lock screen. Just had a friend confirm this happened to them. We shouldn't allow keypresses to leak through from the lock screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 12 16:24:59 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-01-02 (830 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120102) SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2013-12-09 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1306970/+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 1289689] [NEW] Launcher icons don't work when option is set to only show launcher on one monitor.
You have been subscribed to a public bug: In Ubuntu 14.04 beta when the launcher is set to only show on one monitor if you open an application from the menu it opens, but if you close it and try to open it again nothing happens when you click the icon. The way it behaves it's like you're clicking an empty space, the right click menu still works and if you show the launcher on both monitors it also works. ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- Launcher icons don't work when option is set to only show launcher on one monitor. https://bugs.launchpad.net/bugs/1289689 You received this bug notification because you are a member of DX Packages, which is subscribed to unity 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 1289689] Re: Launcher icons don't work when option is set to only show launcher on one monitor.
*** This bug is a duplicate of bug 1303325 *** https://bugs.launchpad.net/bugs/1303325 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/1289689 Title: Launcher icons don't work when option is set to only show launcher on one monitor. Status in “unity” package in Ubuntu: New Bug description: In Ubuntu 14.04 beta when the launcher is set to only show on one monitor if you open an application from the menu it opens, but if you close it and try to open it again nothing happens when you click the icon. The way it behaves it's like you're clicking an empty space, the right click menu still works and if you show the launcher on both monitors it also works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1289689/+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 1289689] Re: Launcher icons don't work when option is set to only show launcher on one monitor.
*** This bug is a duplicate of bug 1303325 *** https://bugs.launchpad.net/bugs/1303325 Have found some duplicates of the same issue, changing from affects Unity to affects Unity (Ubuntu) so that it matches the others. ** Project changed: unity = unity (Ubuntu) ** This bug has been marked a duplicate of bug 1303325 clicking on its launcher icon doesn't open it (occured after closing app before) -- 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/1289689 Title: Launcher icons don't work when option is set to only show launcher on one monitor. Status in “unity” package in Ubuntu: New Bug description: In Ubuntu 14.04 beta when the launcher is set to only show on one monitor if you open an application from the menu it opens, but if you close it and try to open it again nothing happens when you click the icon. The way it behaves it's like you're clicking an empty space, the right click menu still works and if you show the launcher on both monitors it also works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1289689/+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 1298656] Re: hud-service crashed with g-assert-if-reached in GMenu call from qtgmenu::QtGMenuModel::CreateChild()
** Branch linked: lp:~unity-api-team/hud/lp-1298656 ** Branch unlinked: lp:~marcustomlinson/hud/lp-1298656 -- 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/1298656 Title: hud-service crashed with g-assert-if-reached in GMenu call from qtgmenu::QtGMenuModel::CreateChild() Status in “hud” package in Ubuntu: In Progress Bug description: Don't think I did anything special. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140326-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Thu Mar 27 22:37:06 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2013-09-29 (179 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64+mac (20130925.1) ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service Signal: 6 SourcePackage: hud StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () ?? () Title: hud-service crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2014-03-15 (12 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo upstart.hud.log: (hud-service:1836): GLib-CRITICAL **: g_sequence_get: assertion '!is_end (iter)' failed (hud-service:1836): GLib-GIO-CRITICAL **: g_dbus_menu_model_get_item_links: assertion 'item' failed ** GLib-GIO:ERROR:/build/buildd/glib2.0-2.39.92/./gio/gmenumodel.c:398:g_menu_model_real_get_item_link: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1298656/+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
