[Dx-packages] [Bug 1331361] [NEW] Don't recommend unity-control-center-signon | gnome-control-center-signon - GNOME Flashback (gnome-panel) session uses indicator-applet-complete, which recommends ind
Public bug reported: Please suggest unity-control-center-signon | gnome-control-center-signon instead of recommending - GNOME Flashback (gnome-panel) environment uses indicator-applet-complete, which recommends indicator-session. Currently GNOME Classic (flashback) users get unity-control-center installed on their systems because indicator-session recommends unity- control-center-signon | gnome-control-center-signon ** Affects: indicator-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1331361 Title: Don't recommend unity-control-center-signon | gnome-control-center- signon - GNOME Flashback (gnome-panel) session uses indicator-applet- complete, which recommends indicator-session Status in “indicator-session” package in Ubuntu: New Bug description: Please suggest unity-control-center-signon | gnome-control-center- signon instead of recommending - GNOME Flashback (gnome-panel) environment uses indicator-applet-complete, which recommends indicator-session. Currently GNOME Classic (flashback) users get unity-control-center installed on their systems because indicator-session recommends unity-control-center-signon | gnome-control-center-signon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1331361/+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 1331361] Re: Don't recommend unity-control-center-signon | gnome-control-center-signon - GNOME Flashback (gnome-panel) session uses indicator-applet-complete, which recommends indic
** Description changed: Please suggest unity-control-center-signon | gnome-control-center-signon instead of recommending - GNOME Flashback (gnome-panel) environment uses indicator-applet-complete, which recommends indicator-session. - Currently GNOME Classic (flashback) users get unity-control-center - installed on their systems because indicator-session recommends unity- - control-center-signon | gnome-control-center-signon + Currently GNOME Classic (flashback) users get signon-ui and lots of very + big QT5 libraries (like libqt5webkit5) installed on their systems + because indicator-session recommends unity-control-center-signon | + gnome-control-center-signon -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1331361 Title: Don't recommend unity-control-center-signon | gnome-control-center- signon - GNOME Flashback (gnome-panel) session uses indicator-applet- complete, which recommends indicator-session Status in “indicator-session” package in Ubuntu: New Bug description: Please suggest unity-control-center-signon | gnome-control-center- signon instead of recommending - GNOME Flashback (gnome-panel) environment uses indicator-applet-complete, which recommends indicator-session. Currently GNOME Classic (flashback) users get signon-ui and lots of very big QT5 libraries (like libqt5webkit5) installed on their systems because indicator-session recommends unity-control-center-signon | gnome-control-center-signon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1331361/+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 1325110] Re: Audacity HEAD shows almost no shortcuts in menus using Unity
Is this an Audacity or an Ubuntu bug? -- 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/1325110 Title: Audacity HEAD shows almost no shortcuts in menus using Unity Status in “unity” package in Ubuntu: Confirmed Bug description: Observed in Audacity r13166 in Ubuntu 14.04 using Unity with Ambience or Radiance theme. Only the shortcuts for Edit Undo and Redo are visible in the menus. I do not experience inactive menus mentioned in https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1312625 . Initialising audacity.cfg does not help. The shortcuts appear in the menus when using Gnome flashback ( http://www.omgubuntu.co.uk/2014/04/ubuntu-14-04-classic-gnome- flashback-session ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1325110/+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 1325110] Re: Audacity HEAD shows almost no shortcuts in menus using Unity
Is this an Audacity or an Ubuntu bug? -- 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/1325110 Title: Audacity HEAD shows almost no shortcuts in menus using Unity Status in “unity” package in Ubuntu: Confirmed Bug description: Observed in Audacity r13166 in Ubuntu 14.04 using Unity with Ambience or Radiance theme. Only the shortcuts for Edit Undo and Redo are visible in the menus. I do not experience inactive menus mentioned in https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1312625 . Initialising audacity.cfg does not help. The shortcuts appear in the menus when using Gnome flashback ( http://www.omgubuntu.co.uk/2014/04/ubuntu-14-04-classic-gnome- flashback-session ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1325110/+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 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering
** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Status: Confirmed = Triaged -- 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/1316265 Title: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: A maximized application's title bar does not merge into the menu bar once a user has performed Super + W (window slide). Note that if one does not do Super+E, then the bars to merge together. However, once Super+E has been performed, this bug persists for the lifetime of the windowed application. If the application is restarted after doing Super+E, then the bug is gone. Thus, it seems like Super+E introduces this bug for the lifetime of the windowed application. Expected behavior: Maximized window's title bar is merged into menu bar. Observed: Does not occur after Super+W is performed. Try this out using Terminal. ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon May 5 14:48:01 2014 InstallationDate: Installed on 2013-09-08 (239 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1316265/+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 1215644] Re: Messaging menu does not change icon when a new message appears
It works on Utopic #87, closing. ** Changed in: unity8 (Ubuntu) Status: Confirmed = Fix Released ** Changed in: unity8 (Ubuntu Saucy) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1215644 Title: Messaging menu does not change icon when a new message appears Status in The Messaging Menu: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “indicator-messages” source package in Saucy: Fix Released Status in “unity8” source package in Saucy: Fix Released Bug description: I just pulled indicator-messages from trunk (bzr360) and installed it on the phone and rebooted. Now when a new message appears, I get the OSD notification and when I open the messaging menu there is indeed a pending sms there but The color of the messaging menu did not change. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1215644/+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 1315369] Re: Log in not available after lock screen with multi-monitor
I tried the drm-intel-nightly kernel (from 18 June) and still experience the same problems as originally reported. I followed the steps in comment #31 to attach logs - those logs attached. The failure with these logs was slightly different though - behaviour was that I could see the login prompt, but no keyboard input was recognised - i.e., the same thing that I saw in comment #32. So sometimes failure is that I can't get to a screen with the login prompt and sometimes the failure is that the login prompt is there but I can't actually log in because keyboard input not recognised/processed. ** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1315369/+attachment/4134142/+files/syslog -- 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/1315369 Title: Log in not available after lock screen with multi-monitor Status in Unity: Invalid Status in “linux” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Confirmed Status in “unity” source package in Trusty: Confirmed Bug description: After the screen locks I am unable to log back in because the screen with the login prompt is black, and the screen on my laptop just shows the Ubuntu logo. Furthermore, if I then unplug the external monitor (in an attempt to force the log in option to be displayed on the laptop) the laptop screen then goes black and I can't do anything at all. I can't reproduce this if I select lock screen from the UI, but it happens reliably if it locks due to inactivity. Other info: - I am running a fresh install of 14.04 - I have it set to lock after 5 min of inactivity, and require login after lock - I have an external monitor, configured to be on the left side of the laptop screen --- ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jane 2184 F pulseaudio /dev/snd/controlC0: jane 2184 F pulseaudio 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 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=61f52096-031e-4e3d-b1ae-e504b3b3edec InstallationDate: Installed on 2014-05-01 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) MachineType: Dell Inc. Dell System XPS L321X Package: unity 7.2.0+14.04.20140416-0ubuntu1 PackageArchitecture: i386 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 Tags: trusty trusty Uname: Linux 3.13.0-24-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 085X6F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd04/09/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1315369/+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 1315369] Re: Log in not available after lock screen with multi-monitor
** Attachment added: dmesg.0 https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1315369/+attachment/4134144/+files/dmesg.0 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1315369 Title: Log in not available after lock screen with multi-monitor Status in Unity: Invalid Status in “linux” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Status in “linux” source package in Trusty: Confirmed Status in “unity” source package in Trusty: Confirmed Bug description: After the screen locks I am unable to log back in because the screen with the login prompt is black, and the screen on my laptop just shows the Ubuntu logo. Furthermore, if I then unplug the external monitor (in an attempt to force the log in option to be displayed on the laptop) the laptop screen then goes black and I can't do anything at all. I can't reproduce this if I select lock screen from the UI, but it happens reliably if it locks due to inactivity. Other info: - I am running a fresh install of 14.04 - I have it set to lock after 5 min of inactivity, and require login after lock - I have an external monitor, configured to be on the left side of the laptop screen --- ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jane 2184 F pulseaudio /dev/snd/controlC0: jane 2184 F pulseaudio 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 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=61f52096-031e-4e3d-b1ae-e504b3b3edec InstallationDate: Installed on 2014-05-01 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) MachineType: Dell Inc. Dell System XPS L321X Package: unity 7.2.0+14.04.20140416-0ubuntu1 PackageArchitecture: i386 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 Tags: trusty trusty Uname: Linux 3.13.0-24-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 085X6F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd04/09/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1315369/+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 1331460] [NEW] vlc sound-menu entry broken 14.04
Public bug reported: I can observe some weird behaviour (see also http://askubuntu.com/questions/481713/vlc-sound-menu-integration-broken-14-04 ) where the sound-menu entry is insensitive to anything, only when vlc is running; when closing vlc one can use the entry to open it again, but as soon as it is running the entry becomes insensitive (which means, that the back/forward/play buttons do not work) again; Moreover the multimedia-keys do not work for vlc. All other players spotify, gmusicbrowser, gnome-mplayer work flawlessly... I'm Running ubuntu 14.04 and vlc 2.1.4 ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New -- 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/1331460 Title: vlc sound-menu entry broken 14.04 Status in “indicator-sound” package in Ubuntu: New Bug description: I can observe some weird behaviour (see also http://askubuntu.com/questions/481713/vlc-sound-menu-integration-broken-14-04 ) where the sound-menu entry is insensitive to anything, only when vlc is running; when closing vlc one can use the entry to open it again, but as soon as it is running the entry becomes insensitive (which means, that the back/forward/play buttons do not work) again; Moreover the multimedia-keys do not work for vlc. All other players spotify, gmusicbrowser, gnome-mplayer work flawlessly... I'm Running ubuntu 14.04 and vlc 2.1.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1331460/+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 1331460] Re: vlc sound-menu entry broken 14.04
Thanks for reporting this bug. The sound menu shows vlc as inactive because vlc reports that it cannot raise its main window: $ gdbus call --session --dest org.mpris.MediaPlayer2.vlc --object-path /org/mpris/MediaPlayer2 --method org.freedesktop.DBus.Properties.Get 'org.mpris.MediaPlayer2' 'CanRaise' (false,) Also, the sound menu doesn't handle multimedia keys. That's up to the application. ** Package changed: indicator-sound (Ubuntu) = vlc (Ubuntu) -- 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/1331460 Title: vlc sound-menu entry broken 14.04 Status in “vlc” package in Ubuntu: New Bug description: I can observe some weird behaviour (see also http://askubuntu.com/questions/481713/vlc-sound-menu-integration-broken-14-04 ) where the sound-menu entry is insensitive to anything, only when vlc is running; when closing vlc one can use the entry to open it again, but as soon as it is running the entry becomes insensitive (which means, that the back/forward/play buttons do not work) again; Moreover the multimedia-keys do not work for vlc. All other players spotify, gmusicbrowser, gnome-mplayer work flawlessly... I'm Running ubuntu 14.04 and vlc 2.1.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1331460/+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 727904] Re: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken
** Changed in: compiz/0.9.11 Milestone: 0.9.11.1 = 0.9.11.2 -- 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/727904 Title: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken Status in Ayatana Design: Fix Committed Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in Unity: Invalid Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: To reproduce: Open two Chrome windows and two Firefox windows. Drag a .html file over the Chrome icon in the Launcher. A spread of the two Chrome windows should appear. Then continue the same drag, and drag the file over the Firefox icon in the Launcher. Nothing happens, the Chrome spread is still displayed. Desired behaviour; After a spread appears as a result of the user dragging a file over a application icon in the Launcher, if the user then drags the file over a different application icon (where the application is also a valid drop receptacle for the file type) the spread should switch to the newly selected application. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/727904/+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 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application
** Changed in: compiz/0.9.11 Milestone: 0.9.11.1 = 0.9.11.2 -- 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/607796 Title: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application Status in Ayatana Design: Fix Committed Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in One Hundred Papercuts: Fix Released Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as buggybutclosed for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/607796/+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 some windows have a keyboard/mouse grab
** Description changed: + [Impact] + + Some windows will grab the keyboard/mouse and when the lockscreen kicks + in, this window will still have the grab and thusly, ou can enter your + password in the lockscreen. + + [Test case] + + 1. Open a window that will hold the grab, such as the ssh password dialog. + 2. Wait for the lock screen to activate. + 3. Enter your password to unlock the screen. + + [Regression potential] + + This particular fix doesn't fix all cases, but does fix it for some. + That said, no new regressions are expected. + + Original 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). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state 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) -- 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 some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, ou can enter your password in the lockscreen. [Test case] 1. Open a window that will hold the grab, such as the ssh password dialog. 2. Wait for the lock screen to activate. 3. Enter your password to unlock the screen. [Regression potential] This particular fix doesn't fix all cases, but does fix it for some. That said, no new regressions are expected. Original 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). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state 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/compiz/+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 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
** Description changed: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, ou can enter your password in the lockscreen. [Test case] 1. Open a window that will hold the grab, such as the ssh password dialog. 2. Wait for the lock screen to activate. 3. Enter your password to unlock the screen. [Regression potential] This particular fix doesn't fix all cases, but does fix it for some. That said, no new regressions are expected. + + * Debdiff is found at + https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files + /compiz-trusty-sru.debdiff * Original 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). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state 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) -- 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 some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, ou can enter your password in the lockscreen. [Test case] 1. Open a window that will hold the grab, such as the ssh password dialog. 2. Wait for the lock screen to activate. 3. Enter your password to unlock the screen. [Regression potential] This particular fix doesn't fix all cases, but does fix it for some. That said, no new regressions are expected. * Debdiff is found at https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files /compiz-trusty-sru.debdiff * Original 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). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state 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/compiz/+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 1331545] [NEW] gitk instances create separate icons in Unity bar
Public bug reported: Distinct instances of gitk create distinct icons in Unity bar, instead of one icon with 2 or 3 white triangles on the left. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,mousepoll,regex,vpswitch,snap,gnomecompat,place,wall,move,resize,imgpng,animation,expo,session,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CurrentDesktop: Unity Date: Wed Jun 18 19:15:08 2014 InstallationDate: Installed on 2011-10-23 (969 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-25 (24 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: 2 gitk icons in Unity bar https://bugs.launchpad.net/bugs/1331545/+attachment/4134261/+files/desktop_screenshot.png -- 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/1331545 Title: gitk instances create separate icons in Unity bar Status in “unity” package in Ubuntu: New Bug description: Distinct instances of gitk create distinct icons in Unity bar, instead of one icon with 2 or 3 white triangles on the left. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,mousepoll,regex,vpswitch,snap,gnomecompat,place,wall,move,resize,imgpng,animation,expo,session,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CurrentDesktop: Unity Date: Wed Jun 18 19:15:08 2014 InstallationDate: Installed on 2011-10-23 (969 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-25 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1331545/+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 1331545] Re: gitk instances create separate icons in Unity bar
Just a note: gitk is a wish (tcl/tk gui) application. ** Changed in: unity (Ubuntu) Status: New = Triaged ** Changed in: unity (Ubuntu) Importance: Undecided = Medium -- 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/1331545 Title: gitk instances create separate icons in Unity bar Status in “unity” package in Ubuntu: Triaged Bug description: Distinct instances of gitk create distinct icons in Unity bar, instead of one icon with 2 or 3 white triangles on the left. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,mousepoll,regex,vpswitch,snap,gnomecompat,place,wall,move,resize,imgpng,animation,expo,session,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CurrentDesktop: Unity Date: Wed Jun 18 19:15:08 2014 InstallationDate: Installed on 2011-10-23 (969 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-25 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1331545/+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 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** Branch linked: lp:~bregma/unity/lp-1324114 -- 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/1324114 Title: Unity kills running compiz, even if it belongs to a different Unity session Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity” source package in Trusty: New Bug description: Hi! I'm trying to get a setup with two different Unity desktop sessions running at the same time. One for the local desktop, one for a remote desktop. This almost works, except that when starting the second Unity session, the compiz process that belongs to the first one is killed because of this code in /usr/bin/unity: # kill a previous compiz if was there (this is a hack as compiz can # sometimes get stuck and not exit on --replace) subprocess.call ([pkill, -9, compiz]) Commenting this line makes both desktop sessions work fine. This kill is far too harsh. If you want to kill compiz, you should make sure that you are killing it in the same DISPLAY as the session that you are about to start, and not just every possible compiz process that is running. Please consider either removing the kill or making it apply only to processes in the same DISPLAY. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1324114/+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 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** Changed in: unity Assignee: (unassigned) = Stephen M. Webb (bregma) ** Changed in: unity/7.2 Assignee: (unassigned) = Stephen M. Webb (bregma) ** Changed in: unity/7.2 Milestone: None = 7.2.2 -- 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/1324114 Title: Unity kills running compiz, even if it belongs to a different Unity session Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity” source package in Trusty: New Bug description: Hi! I'm trying to get a setup with two different Unity desktop sessions running at the same time. One for the local desktop, one for a remote desktop. This almost works, except that when starting the second Unity session, the compiz process that belongs to the first one is killed because of this code in /usr/bin/unity: # kill a previous compiz if was there (this is a hack as compiz can # sometimes get stuck and not exit on --replace) subprocess.call ([pkill, -9, compiz]) Commenting this line makes both desktop sessions work fine. This kill is far too harsh. If you want to kill compiz, you should make sure that you are killing it in the same DISPLAY as the session that you are about to start, and not just every possible compiz process that is running. Please consider either removing the kill or making it apply only to processes in the same DISPLAY. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1324114/+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 1331923] Re: unity-2d-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 936560 *** https://bugs.launchpad.net/bugs/936560 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #936560, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1331923/+attachment/4134665/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1331923/+attachment/4134667/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1331923/+attachment/4134668/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1331923/+attachment/4134669/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1331923/+attachment/4134670/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1331923/+attachment/4134671/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1331923/+attachment/4134672/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 936560 unity-2d-shell crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/1331923 Title: unity-2d-shell crashed with SIGSEGV Status in “unity-2d” package in Ubuntu: New Bug description: Not sure what caused this crash, but it happens intermittently and can only be fixed by 'killall unity-2d-panel', which I type into an available terminal window if possible. Otherwise, the panel is totally unresponsive. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-2d-shell 5.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-63.95-generic 3.2.57 Uname: Linux 3.2.0-63-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CrashCounter: 1 Date: Thu Jun 19 15:33:28 2014 ExecutablePath: /usr/bin/unity-2d-shell InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True ProcCmdline: unity-2d-shell ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f1169989082:testb $0x4,(%rbx) PC (0x7f1169989082) ok source $0x4 ok destination (%rbx) (0x2fa003d) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity-2d StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 ?? () from /usr/lib/x86_64-linux-gnu/libQtDeclarative.so.4 ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 Title: unity-2d-shell crashed with SIGSEGV 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-2d/+bug/1331923/+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
