[Dx-packages] [Bug 1523698] Re: indicator-session is leaking memory on ubuntu 15.10
** Changed in: indicator-session (Ubuntu) Status: Incomplete => Confirmed -- 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/1523698 Title: indicator-session is leaking memory on ubuntu 15.10 Status in indicator-session package in Ubuntu: Confirmed Bug description: The `indicator-session-service` is slowly leaking memory, after a while it has used up over 10 gigabytes of RAM and swap and the entire system freezes. I've reinstalled the entire OS, and even started using a new home folder, but it's still happening. indicator-session: Geïnstalleerd: 12.10.5+15.10.20150915-0ubuntu1 Kandidaat: 12.10.5+15.10.20150915-0ubuntu1 Versietabel: *** 12.10.5+15.10.20150915-0ubuntu1 0 500 http://be.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1523698/+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 1523698] Re: indicator-session is leaking memory on ubuntu 15.10
As a temporary workaround, I've been running this script in background which kills indicator-session-service when it hits 500M of rss: #!/bin/sh while sleep 1; do rss=$(ps -C indicator-session-service -o rss=) if [ -n "$rss" ] && [ "$rss" -gt 50 ]; then pkill -f indicator-session-service -u hyperair && \ echo "[$(date)] killed at $rss" fi done -- 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/1523698 Title: indicator-session is leaking memory on ubuntu 15.10 Status in indicator-session package in Ubuntu: Incomplete Bug description: The `indicator-session-service` is slowly leaking memory, after a while it has used up over 10 gigabytes of RAM and swap and the entire system freezes. I've reinstalled the entire OS, and even started using a new home folder, but it's still happening. indicator-session: Geïnstalleerd: 12.10.5+15.10.20150915-0ubuntu1 Kandidaat: 12.10.5+15.10.20150915-0ubuntu1 Versietabel: *** 12.10.5+15.10.20150915-0ubuntu1 0 500 http://be.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1523698/+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 1523698] Re: indicator-session is leaking memory on ubuntu 15.10
I ran it through valgrind by diverting indicator-session-service and
replacing it with the following script:
#!/bin/bash
exec valgrind \
--tool=massif \
--alloc-fn={g_slice_alloc,g_malloc,g_realloc} \
--massif-out-file=$HOME/massif-dump/indicator-session-service.out.%p \
/usr/lib/x86_64-linux-gnu/indicator-session/indicator-session-service.distrib \
"$@"
Running ms_print on the output files gave me some stack traces of the
highest number of unfreed allocations:
60.92% (1,262,577,672B) (heap allocation functions) malloc/new/new[],
--alloc-fns, etc.
->17.05% (353,258,600B) 0x568AC5C: g_variant_new_from_children (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4600.1)
| ->08.46% (175,306,320B) 0x568798A: g_variant_builder_end (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4600.1)
| | ->08.46% (175,306,120B) 0x4F05434: parse_value_from_blob (in
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4600.1)
| | | ->04.23% (87,682,360B) 0x4F05120: parse_value_from_blob (in
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4600.1)
| | | | ->04.23% (87,682,360B) 0x4F05400: parse_value_from_blob (in
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4600.1)
| | | | | ->04.23% (87,682,360B) 0x4F0501F: parse_value_from_blob (in
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4600.1)
| | | | | ->04.23% (87,682,360B) 0x4F05120: parse_value_from_blob (in
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4600.1)
| | | | | ->04.23% (87,682,360B) 0x4F051E8: parse_value_from_blob (in
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4600.1)
| | | | | ->04.23% (87,682,360B) 0x4F0747A: g_dbus_message_new_from_blob
(in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4600.1)
| | | | | ->04.23% (87,682,360B) 0x4F1168B: _g_dbus_worker_do_read_cb
(in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4600.1)
| | | | | ->04.23% (87,682,360B) 0x4EB45F1: g_task_return_now (in
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4600.1)
| | | | | ->04.22% (87,503,000B) 0x4EB4627: complete_in_idle_cb (in
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4600.1)
| | | | | | ->04.22% (87,503,000B) 0x564FEA8:
g_main_context_dispatch (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4600.1)
| | | | | | ->04.22% (87,503,000B) 0x565024E:
g_main_context_iterate.isra.29 (in
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4600.1)
| | | | | | ->04.22% (87,503,000B) 0x5650570: g_main_loop_run
(in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4600.1)
| | | | | | ->04.22% (87,503,000B) 0x4F0F4C4:
gdbus_shared_thread_func (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4600.1)
| | | | | | ->04.22% (87,503,000B) 0x5676963:
g_thread_proxy (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4600.1)
| | | | | | ->04.22% (87,503,000B) 0x69B96A8:
start_thread (pthread_create.c:333)
| | | | | | ->04.22% (87,503,000B) 0x5A1BEEB: clone
(clone.S:109)
I've attached the full dump from ms_print.
** Attachment added: "indicator-session-service.out.5268.ms_print"
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1523698/+attachment/4572208/+files/indicator-session-service.out.5268.ms_print
--
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/1523698
Title:
indicator-session is leaking memory on ubuntu 15.10
Status in indicator-session package in Ubuntu:
Incomplete
Bug description:
The `indicator-session-service` is slowly leaking memory, after a
while it has used up over 10 gigabytes of RAM and swap and the entire
system freezes.
I've reinstalled the entire OS, and even started using a new home
folder, but it's still happening.
indicator-session:
Geïnstalleerd: 12.10.5+15.10.20150915-0ubuntu1
Kandidaat: 12.10.5+15.10.20150915-0ubuntu1
Versietabel:
*** 12.10.5+15.10.20150915-0ubuntu1 0
500 http://be.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1523698/+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 1374249] Re: Scrolling works erratically when sound center balance is off-center
On Wed, Oct 01, 2014 at 02:55:25PM -, Lars Uebernickel wrote: Indeed, good catch. The sound menu always manipulated the left channel. I've attached a branch fixes most of the problem by making it handle channels in the same way that system settings does. Changing the volume to 0 still resets the balance to center, though (same as in system settings). I'm not sure it should reset the balance to center. Shouldn't it recall the last balance setting and try to preserve that? FWIW, the system settings also functions a little weirdly -- if you try to click and drag the volume control around in the system settings, it starts jumping around like it wants to reduce its volume instead of following your cursor. Scrolling seems to work as expected in the system settings though. -- Kind regards, Loong Jin -- 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/1374249 Title: Scrolling works erratically when sound center balance is off-center Status in “indicator-sound” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: Triaged Bug description: When the center balance is adjusted to the right, scrolling on the volume icon in the panel produces erratic results. The same thing happens when trying to adjust the volume in the sound menu. The volume buttons still function correctly though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1374249/+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 1374249] [NEW] Scrolling works erratically when sound center balance is off-center
Public bug reported: When the center balance is adjusted to the right, scrolling on the volume icon in the panel produces erratic results. The same thing happens when trying to adjust the volume in the sound menu. The volume buttons still function correctly though. ** 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/1374249 Title: Scrolling works erratically when sound center balance is off-center Status in “indicator-sound” package in Ubuntu: New Bug description: When the center balance is adjusted to the right, scrolling on the volume icon in the panel produces erratic results. The same thing happens when trying to adjust the volume in the sound menu. The volume buttons still function correctly though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1374249/+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 1374249] Re: Scrolling works erratically when sound center balance is off-center
Dragging the handle on the sound menu seems to indicate that it keeps trying to go down instead of following the mouse. Also, when it hits 0, the sound center balance is reset to 0 (right in the center). -- 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/1374249 Title: Scrolling works erratically when sound center balance is off-center Status in “indicator-sound” package in Ubuntu: New Bug description: When the center balance is adjusted to the right, scrolling on the volume icon in the panel produces erratic results. The same thing happens when trying to adjust the volume in the sound menu. The volume buttons still function correctly though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1374249/+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 1292451] Re: screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked
On Sun, Mar 30, 2014 at 07:33:58PM -, Jason Odoom wrote: This seems to be fixed now with latest updates on Trusty. Nope, still broken for me. -- Kind regards, Loong Jin -- 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/1292451 Title: screensaver re-locks itself after unlocking if the configured screen- off timer goes off while screen is locked Status in Unity: New Status in “gnome-screensaver” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Set screen-off timeout to 1 minute 2. Configure screen to lock immediately when screen goes off. 3. Lock screen manually (Ctrl+Alt+L) 4. Wait for 1 minute 5. Notice that screen doesn't turn off 6. Unlock screen 7. Wait a couple of seconds (~10 or so) 8. Notice that screen re-locks itself. 9. Repeat steps 6-7 and notice that the screen doesn't re-lock itself this time. There are two bugs described here: 1. Screen does not shut off if the screen is locked manually before the idle timer (see step 5). 2. Screen re-locks itself after unlocking if the idle timer goes off while the screen is locked (see step 7). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 18:19:26 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292451/+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 1298903] [NEW] ibus input method selection doesn't work in lock screen
Public bug reported: Earlier, I switched my ibus daemon to the Japanese/anthy input mode and locked my screen. I couldn't key in my password (consisting solely of ascii characters), as it appeared to be inputting everything in Japanese (the typical underlines were there, but everything was starred as it was a password input field). There didn't appear to be a way to switch it back to a standard qwerty input mode, so I was kind of stuck. Workaround: I managed to get back in by activating the switch user menu item and logging back in from there. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Fri Mar 28 17:56:06 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (24 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1298903 Title: ibus input method selection doesn't work in lock screen Status in “unity” package in Ubuntu: New Bug description: Earlier, I switched my ibus daemon to the Japanese/anthy input mode and locked my screen. I couldn't key in my password (consisting solely of ascii characters), as it appeared to be inputting everything in Japanese (the typical underlines were there, but everything was starred as it was a password input field). There didn't appear to be a way to switch it back to a standard qwerty input mode, so I was kind of stuck. Workaround: I managed to get back in by activating the switch user menu item and logging back in from there. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Fri Mar 28 17:56:06 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298903/+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 1288028] Re: [regression] Clicking on unity's panel does not raise a maximized window
This seems fixed in current trusty. ** 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/1288028 Title: [regression] Clicking on unity's panel does not raise a maximized window Status in “unity” package in Ubuntu: Fix Released Bug description: With one maximized window below an unmaximized window, clicking on the Unity panel (with the maximized window focused) does not raise the maximized window. This happens with both focus-follows-mouse and focus-follows-click, although the latter is harder to trigger with normal usage. Steps to reproduce (with focus follows mouse): 1. Open two windows. Maximize one (let's call this A), and leave one unmaximized (let's call this B). 2. Raise window B so that B is in front of A. 3. Move mouse over window A to focus it. 4. Move mouse up to the unity panel while keeping window A focused. 5. Click on an empty space in the panel. Observed behaviour: window A is not raised to the top, but it should. This used to work in Ubuntu 13.10, and 13.04, iirc. This bug also occurs with focus-follows-click: Steps to reproduce (with focus follows click): 1. Open two windows. Maximize one (let's call this A), and leave one unmaximized (let's call this B). 2. Raise window B so that B is in front of A. 3. Alt+RightClick on window B to bring up the window's context menu and enable the Always on top option. 4. Click on window A to focus it. Window B should remain in front of window A. 5. Alt+RightClick on window B to bring up the window's context menu, and disable the Always on top option. Window A should remain focused after this action. 6. Click on an empty space in the panel. Observed behaviour: Window A is not raised to the top, but it should. I'm not sure if this worked in previous releases. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140228-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Wed Mar 5 10:36:21 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1288028/+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 1292451] Re: screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked
I'm also adding unity to this bug as this only appeared after a gnome- screensaver upgrade that enabled the unity screenlock. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292451 Title: screensaver re-locks itself after unlocking if the configured screen- off timer goes off while screen is locked Status in “gnome-screensaver” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: Steps to reproduce: 1. Set screen-off timeout to 1 minute 2. Configure screen to lock immediately when screen goes off. 3. Lock screen manually (Ctrl+Alt+L) 4. Wait for 1 minute 5. Notice that screen doesn't turn off 6. Unlock screen 7. Wait a couple of seconds (~10 or so) 8. Notice that screen re-locks itself. 9. Repeat steps 6-7 and notice that the screen doesn't re-lock itself this time. There are two bugs described here: 1. Screen does not shut off if the screen is locked manually before the idle timer (see step 5). 2. Screen re-locks itself after unlocking if the idle timer goes off while the screen is locked (see step 7). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 18:19:26 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292451/+subscriptions -- Mailing list: https://launchpad.net/~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 1292451] [NEW] screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked
Public bug reported: Steps to reproduce: 1. Set screen-off timeout to 1 minute 2. Configure screen to lock immediately when screen goes off. 3. Lock screen manually (Ctrl+Alt+L) 4. Wait for 1 minute 5. Notice that screen doesn't turn off 6. Unlock screen 7. Wait a couple of seconds (~10 or so) 8. Notice that screen re-locks itself. 9. Repeat steps 6-7 and notice that the screen doesn't re-lock itself this time. There are two bugs described here: 1. Screen does not shut off if the screen is locked manually before the idle timer (see step 5). 2. Screen re-locks itself after unlocking if the idle timer goes off while the screen is locked (see step 7). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 18:19:26 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292451 Title: screensaver re-locks itself after unlocking if the configured screen- off timer goes off while screen is locked Status in “gnome-screensaver” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: Steps to reproduce: 1. Set screen-off timeout to 1 minute 2. Configure screen to lock immediately when screen goes off. 3. Lock screen manually (Ctrl+Alt+L) 4. Wait for 1 minute 5. Notice that screen doesn't turn off 6. Unlock screen 7. Wait a couple of seconds (~10 or so) 8. Notice that screen re-locks itself. 9. Repeat steps 6-7 and notice that the screen doesn't re-lock itself this time. There are two bugs described here: 1. Screen does not shut off if the screen is locked manually before the idle timer (see step 5). 2. Screen re-locks itself after unlocking if the idle timer goes off while the screen is locked (see step 7). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 18:19:26 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292451/+subscriptions -- Mailing list: https://launchpad.net/~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 1292451] Re: screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked
** Attachment added: Screenshot of BrightnessLock settings https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292451/+attachment/4023757/+files/Screenshot%20from%202014-03-14%2018%3A32%3A31.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292451 Title: screensaver re-locks itself after unlocking if the configured screen- off timer goes off while screen is locked Status in “gnome-screensaver” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: Steps to reproduce: 1. Set screen-off timeout to 1 minute 2. Configure screen to lock immediately when screen goes off. 3. Lock screen manually (Ctrl+Alt+L) 4. Wait for 1 minute 5. Notice that screen doesn't turn off 6. Unlock screen 7. Wait a couple of seconds (~10 or so) 8. Notice that screen re-locks itself. 9. Repeat steps 6-7 and notice that the screen doesn't re-lock itself this time. There are two bugs described here: 1. Screen does not shut off if the screen is locked manually before the idle timer (see step 5). 2. Screen re-locks itself after unlocking if the idle timer goes off while the screen is locked (see step 7). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 18:19:26 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292451/+subscriptions -- Mailing list: https://launchpad.net/~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 1292647] [NEW] Esc does not clear the password input field in the unity lock screen
Public bug reported: When hitting the escape key in the Unity lock screen password prompt, the password prompt is not cleared, whereas it used to be cleared in the old gnome-screensaver, as well as the lightdm login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140312-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Fri Mar 14 22:29:30 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (11 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lockscreen trusty ** 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/1292647 Title: Esc does not clear the password input field in the unity lock screen Status in “unity” package in Ubuntu: New Bug description: When hitting the escape key in the Unity lock screen password prompt, the password prompt is not cleared, whereas it used to be cleared in the old gnome-screensaver, as well as the lightdm login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140312-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Fri Mar 14 22:29:30 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292647/+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 1292343] [NEW] notify-osd positions its top notification overlapping the panel on displays not aligned with the top of the virtual screen
Public bug reported: My monitor layout is: 1. 1366x768+0+270 2. 1680x1050+1366+0 notify-osd renders the volume/brightness notification overlapping the panel on monitor 1. This doesn't happen when the top edge of monitor 1 touches the top of the virtual screen, i.e. 1366x768+0+0. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 12:08:56 2014 DesktopSession: 'ubuntu' GtkTheme: 'Ambiance' IconTheme: 'Humanity-Colors-Dark-Red' MachineType: LENOVO 2325F45 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.4-hyper1 root=UUID=274ad2d4-6566-4eb1-85d7-d22ef41b2170 ro acpi_osi=!Windows 2012 i915.i915_enable_rc6=7 i915.lvds_downclock=1 i915.i915_enable_fbc=1 i915.semaphores=1 rootflags=data=writeback splash resume=/dev/mapper/cryptostuff-swap crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0-1ubuntu1 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 xserver-xorg-video-ati 1:7.3.0-1ubuntu3 SourcePackage: notify-osd UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) dmi.bios.date: 04/30/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET94WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 2325F45 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: RH0005026 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET94WW(2.54):bd04/30/2013:svnLENOVO:pn2325F45:pvrThinkPadX230:rvnLENOVO:rn2325F45:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2325F45 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO ** Affects: notify-osd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292343 Title: notify-osd positions its top notification overlapping the panel on displays not aligned with the top of the virtual screen Status in “notify-osd” package in Ubuntu: New Bug description: My monitor layout is: 1. 1366x768+0+270 2. 1680x1050+1366+0 notify-osd renders the volume/brightness notification overlapping the panel on monitor 1. This doesn't happen when the top edge of monitor 1 touches the top of the virtual screen, i.e. 1366x768+0+0. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 12:08:56 2014 DesktopSession: 'ubuntu' GtkTheme: 'Ambiance' IconTheme: 'Humanity-Colors-Dark-Red' MachineType: LENOVO 2325F45 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.4-hyper1 root=UUID=274ad2d4-6566-4eb1-85d7-d22ef41b2170 ro acpi_osi=!Windows 2012 i915.i915_enable_rc6=7 i915.lvds_downclock=1 i915.i915_enable_fbc=1 i915.semaphores=1 rootflags=data=writeback splash resume=/dev/mapper/cryptostuff-swap crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0-1ubuntu1 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 xserver-xorg-video-ati 1:7.3.0-1ubuntu3 SourcePackage: notify-osd UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) dmi.bios.date: 04/30/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET94WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 2325F45 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: RH0005026 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET94WW(2.54):bd04/30/2013:svnLENOVO:pn2325F45:pvrThinkPadX230:rvnLENOVO:rn2325F45:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2325F45 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1292343/+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 1290644] [NEW] Clicking on top left corner does not trigger the 'x' button when a window is maximized on a screen that is not aligned to the top of the entire viewport
Public bug reported: When a screen configuration has a non-zero y-offset, clicking on the top left corner in that screen does not close the maximized window in that screen. Steps to reproduce: 1. Have a multihead setup with two screens of different height side by side, aligned by their bottom edges. 2. Maximize a window on the shorter screen 3. Move mouse to top left corner of the shorter screen 4. Notice that the window control buttons vanish, replaced by the window title at the exact corner. 5. Move your mouse inward a bit, and notice that the window controls reappear. Repeat steps 2-5 with the taller screen, and notice that at #4, the window controls are still present, and clicking on that corner results in the window closing. Expected behaviour: The shorter screen should follow the behaviour of the taller screen. Specific details of my multihead setup is as follows: LVDS1 connected primary 1366x768+0+270 (normal left inverted right x axis y axis) 277mm x 156mm HDMI2 connected 1680x1050+1366+0 (normal left inverted right x axis y axis) 434mm x 270mm ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140305-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Tue Mar 11 09:54:48 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (7 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1290644 Title: Clicking on top left corner does not trigger the 'x' button when a window is maximized on a screen that is not aligned to the top of the entire viewport Status in “unity” package in Ubuntu: New Bug description: When a screen configuration has a non-zero y-offset, clicking on the top left corner in that screen does not close the maximized window in that screen. Steps to reproduce: 1. Have a multihead setup with two screens of different height side by side, aligned by their bottom edges. 2. Maximize a window on the shorter screen 3. Move mouse to top left corner of the shorter screen 4. Notice that the window control buttons vanish, replaced by the window title at the exact corner. 5. Move your mouse inward a bit, and notice that the window controls reappear. Repeat steps 2-5 with the taller screen, and notice that at #4, the window controls are still present, and clicking on that corner results in the window closing. Expected behaviour: The shorter screen should follow the behaviour of the taller screen. Specific details of my multihead setup is as follows: LVDS1 connected primary 1366x768+0+270 (normal left inverted right x axis y axis) 277mm x 156mm HDMI2 connected 1680x1050+1366+0 (normal left inverted right x axis y axis) 434mm x 270mm ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140305-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Tue Mar 11 09:54:48 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1290644/+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 1288028] [NEW] [regression] Clicking on unity's panel does not raise a maximized window
Public bug reported: With one maximized window below an unmaximized window, clicking on the Unity panel (with the maximized window focused) does not raise the maximized window. This happens with both focus-follows-mouse and focus- follows-click, although the latter is harder to trigger with normal usage. Steps to reproduce (with focus follows mouse): 1. Open two windows. Maximize one (let's call this A), and leave one unmaximized (let's call this B). 2. Raise window B so that B is in front of A. 3. Move mouse over window A to focus it. 4. Move mouse up to the unity panel while keeping window A focused. 5. Click on an empty space in the panel. Observed behaviour: window A is not raised to the top, but it should. This used to work in Ubuntu 13.10, and 13.04, iirc. This bug also occurs with focus-follows-click: Steps to reproduce (with focus follows click): 1. Open two windows. Maximize one (let's call this A), and leave one unmaximized (let's call this B). 2. Raise window B so that B is in front of A. 3. Alt+RightClick on window B to bring up the window's context menu and enable the Always on top option. 4. Click on window A to focus it. Window B should remain in front of window A. 5. Alt+RightClick on window B to bring up the window's context menu, and disable the Always on top option. Window A should remain focused after this action. 6. Click on an empty space in the panel. Observed behaviour: Window A is not raised to the top, but it should. I'm not sure if this worked in previous releases. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140228-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Wed Mar 5 10:36:21 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (1 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug regression-release trusty ** Tags added: regression-release -- 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/1288028 Title: [regression] Clicking on unity's panel does not raise a maximized window Status in “unity” package in Ubuntu: New Bug description: With one maximized window below an unmaximized window, clicking on the Unity panel (with the maximized window focused) does not raise the maximized window. This happens with both focus-follows-mouse and focus-follows-click, although the latter is harder to trigger with normal usage. Steps to reproduce (with focus follows mouse): 1. Open two windows. Maximize one (let's call this A), and leave one unmaximized (let's call this B). 2. Raise window B so that B is in front of A. 3. Move mouse over window A to focus it. 4. Move mouse up to the unity panel while keeping window A focused. 5. Click on an empty space in the panel. Observed behaviour: window A is not raised to the top, but it should. This used to work in Ubuntu 13.10, and 13.04, iirc. This bug also occurs with focus-follows-click: Steps to reproduce (with focus follows click): 1. Open two windows. Maximize one (let's call this A), and leave one unmaximized (let's call this B). 2. Raise window B so that B is in front of A. 3. Alt+RightClick on window B to bring up the window's context menu and enable the Always on top option. 4. Click on window A to focus it. Window B should remain in front of window A. 5. Alt+RightClick on window B to bring up the window's context menu, and disable the Always on top option. Window A should remain focused after this action. 6. Click on an empty space in the panel. Observed behaviour: Window A is not raised to the top, but it should. I'm not sure if this worked in previous releases. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140228-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Wed Mar 5 10:36:21 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (1 days ago) To manage notifications about this bug go
[Dx-packages] [Bug 1287343] [NEW] Application menu hijacks Alt+F, E, V, S, T, H keybindings in gnome-terminal
Public bug reported: 1. Enable the menubar in gnome-terminal 2. Go to Edit-Keyboard Shortcuts and uncheck Enable menu access keys (such as Alt+F to open the File menu) 3. Type something in the shell, then go to the beginning of the line, and attempt to use Alt+F to navigate forward by word 4. Observe that the File menu triggers instead, even though it should have been disabled as per step 2. Repeat the above steps running gnome-terminal like: UBUNTU_MENUPROXY=0 gnome-terminal, and notice that the menu doesn't activate, and Alt+F gets successfully handled by the shell. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-gtk3-module 0.0.0+14.04.20140213.2-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 4 03:53:14 2014 SourcePackage: unity-gtk-module UpgradeStatus: Upgraded to trusty on 2014-03-03 (0 days ago) ** Affects: unity-gtk-module (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1287343 Title: Application menu hijacks Alt+F,E,V,S,T,H keybindings in gnome-terminal Status in “unity-gtk-module” package in Ubuntu: New Bug description: 1. Enable the menubar in gnome-terminal 2. Go to Edit-Keyboard Shortcuts and uncheck Enable menu access keys (such as Alt+F to open the File menu) 3. Type something in the shell, then go to the beginning of the line, and attempt to use Alt+F to navigate forward by word 4. Observe that the File menu triggers instead, even though it should have been disabled as per step 2. Repeat the above steps running gnome-terminal like: UBUNTU_MENUPROXY=0 gnome-terminal, and notice that the menu doesn't activate, and Alt+F gets successfully handled by the shell. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-gtk3-module 0.0.0+14.04.20140213.2-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 4 03:53:14 2014 SourcePackage: unity-gtk-module UpgradeStatus: Upgraded to trusty on 2014-03-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1287343/+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 1287322] Re: ctrl+super keybindings broken in trusty
** Also 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/1287322 Title: ctrl+super keybindings broken in trusty Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: affects unity status new Unity's handling of Ctrl+Super+X keybindings has regressed in trusty -- Control must be pressed before Super is pressed, or Unity hijacks the keybinding instead. For example: 1. Press and hold Control 2. Press and hold Super 3. Press 1 This activates the Ctrl+Super+1 keybinding, which for me is Zoom reset (from the ezoom plugin). However, if you reverse steps 1 and 2, so that Super is held down before Control, then the keybinding for Super+1 is activated instead, i.e. the first item in the launcher gets activated. This bug used to be present in older versions of Unity, but was fixed in Saucy, and reappeared in Trusty. -- Kind regards, Loong Jin To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1287322/+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 1241906] [NEW] indicator-session menu in guest session lists Switch User with Ctrl+Alt+L keybinding (which doesn't work)
Public bug reported: affects ubuntu/indicator-session status new When logged into the guest session, the Lock item in the indicator-session menu is replaced with Switch User, but the keybinding is still listed as Ctrl+Alt+L. However, hitting Ctrl+Alt+L does not do anything. I'd suggest dropping the keybinding from that menu item, at least when it reads Switch User in order to avoid confusion. -- Kind regards, Loong Jin ** 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/1241906 Title: indicator-session menu in guest session lists Switch User with Ctrl+Alt+L keybinding (which doesn't work) Status in “indicator-session” package in Ubuntu: New Bug description: affects ubuntu/indicator-session status new When logged into the guest session, the Lock item in the indicator-session menu is replaced with Switch User, but the keybinding is still listed as Ctrl+Alt+L. However, hitting Ctrl+Alt+L does not do anything. I'd suggest dropping the keybinding from that menu item, at least when it reads Switch User in order to avoid confusion. -- Kind regards, Loong Jin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1241906/+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 1240785] [NEW] unity-scopes-runner's description is not verbose enough, and contains a typo
Public bug reported: affects ubuntu/libunity status new The current description of unity-scopes-runner, as quoted, is hardly descriptive, and could use improvement: | Description-en: desktop runner for misceallenous scopes | The scope runner is a handy tool for wrapping on a desktop the various | scoped installed on the system. After reading this description, I still have no idea what unity-scopes-runner is supposed to do. Additionally, I think scoped is supposed to be scopes in the last line. -- Kind regards, Loong Jin ** Affects: libunity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1240785 Title: unity-scopes-runner's description is not verbose enough, and contains a typo Status in “libunity” package in Ubuntu: New Bug description: affects ubuntu/libunity status new The current description of unity-scopes-runner, as quoted, is hardly descriptive, and could use improvement: | Description-en: desktop runner for misceallenous scopes | The scope runner is a handy tool for wrapping on a desktop the various | scoped installed on the system. After reading this description, I still have no idea what unity-scopes-runner is supposed to do. Additionally, I think scoped is supposed to be scopes in the last line. -- Kind regards, Loong Jin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1240785/+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
