[Bug 1714908] Re: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 00007f54021c9836 sp 00007fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000]
Workaround: apt install xubuntu-desktop (choose lightdm over gdm) ** Description changed: Attempting to use multiple monitors from the graphical interface results in nothing happening: (gnome-control-center:8910): display-cc-panel-WARNING **: Error applying configuration: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig Attempting to set up the same from xrandr causes segmentation faults in libmutter: $ sudo dmesg --console-on $ xrandr --output eDP-1 --off --output DP-1-2 --mode 1920x1080 --rotate left --pos 2160x0 --output DP-1-1 --pos 0x0 --mode 1920x1080 --rotate left --output DP-1-3 --pos 1080x0 --mode 1920x1080 --rotate left --verbose --scale 1x1 screen 0: 3240x1920 858x508 mm 95.92dpi crtc 0:1920x1080 60.00 +1080+0 "DP-1-3" crtc 1:1920x1080 60.00 +2160+0 "DP-1-2" crtc 2:1920x1080 60.00 +0+0 "DP-1-1" - sraffa@sraffa-Latitude-E7270:~⟫ [Sep 4 11:07] gnome-shell[3603]: segfault at 8 ip 7f79e651bda0 sp 7ffd48c3d1b8 error 4 in libmutter-1.so.0.0.0[7f79e64c2000+13f000] + [Sep 4 11:07] gnome-shell[3603]: segfault at 8 ip 7f79e651bda0 sp 7ffd48c3d1b8 error 4 in libmutter-1.so.0.0.0[7f79e64c2000+13f000] It should be noted that all monitors are working as expected during boot (e.g. while typing my HDD unlock password) + + Regrettably the segfault information changes every time and apport + doesn't seem able to capture reports for it. + + xfce sessions from lightdm start regularly and can use external monitors + regularly. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libmutter-1-0 3.25.91+20170902~ce515c5-1ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 11:02:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (20 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1714908 Title: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 7f54021c9836 sp 7fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714908] Re: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 00007f54021c9836 sp 00007fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000]
Of course, the Ubuntu repos removed the previous version of the relevant packages so I can't roll back the package upgrade to see if that helps anything. ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908/+attachment/4944025/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1714908 Title: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 7f54021c9836 sp 7fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714908] [NEW] Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 00007f54021c9836 sp 00007fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000]
Public bug reported: Attempting to use multiple monitors from the graphical interface results in nothing happening: (gnome-control-center:8910): display-cc-panel-WARNING **: Error applying configuration: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig Attempting to set up the same from xrandr causes segmentation faults in libmutter: $ sudo dmesg --console-on $ xrandr --output eDP-1 --off --output DP-1-2 --mode 1920x1080 --rotate left --pos 2160x0 --output DP-1-1 --pos 0x0 --mode 1920x1080 --rotate left --output DP-1-3 --pos 1080x0 --mode 1920x1080 --rotate left --verbose --scale 1x1 screen 0: 3240x1920 858x508 mm 95.92dpi crtc 0:1920x1080 60.00 +1080+0 "DP-1-3" crtc 1:1920x1080 60.00 +2160+0 "DP-1-2" crtc 2:1920x1080 60.00 +0+0 "DP-1-1" sraffa@sraffa-Latitude-E7270:~⟫ [Sep 4 11:07] gnome-shell[3603]: segfault at 8 ip 7f79e651bda0 sp 7ffd48c3d1b8 error 4 in libmutter-1.so.0.0.0[7f79e64c2000+13f000] It should be noted that all monitors are working as expected during boot (e.g. while typing my HDD unlock password) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libmutter-1-0 3.25.91+20170902~ce515c5-1ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 11:02:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (20 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Description changed: Attempting to use multiple monitors from the graphical interface results in nothing happening: (gnome-control-center:8910): display-cc-panel-WARNING **: Error applying configuration: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig Attempting to set up the same from xrandr causes segmentation faults in libmutter: $ sudo dmesg --console-on $ xrandr --output eDP-1 --off --output DP-1-2 --mode 1920x1080 --rotate left --pos 2160x0 --output DP-1-1 --pos 0x0 --mode 1920x1080 --rotate left --output DP-1-3 --pos 1080x0 --mode 1920x1080 --rotate left --verbose --scale 1x1 screen 0: 3240x1920 858x508 mm 95.92dpi crtc 0:1920x1080 60.00 +1080+0 "DP-1-3" crtc 1:1920x1080 60.00 +2160+0 "DP-1-2" crtc 2:1920x1080 60.00 +0+0 "DP-1-1" sraffa@sraffa-Latitude-E7270:~⟫ [Sep 4 11:07] gnome-shell[3603]: segfault at 8 ip 7f79e651bda0 sp 7ffd48c3d1b8 error 4 in libmutter-1.so.0.0.0[7f79e64c2000+13f000] + It should be noted that all monitors are working as expected during boot + (e.g. while typing my HDD unlock password) + ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libmutter-1-0 3.25.91+20170902~ce515c5-1ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 11:02:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (20 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1714908 Title: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 7f54021c9836 sp 7fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714908] Re: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 00007f54021c9836 sp 00007fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000]
Re-attaching redacted journal messages. My username wasn't fully scrubbed out. ** Attachment added: "JournalMessages.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908/+attachment/4944030/+files/JournalMessages.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1714908 Title: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 7f54021c9836 sp 7fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1712548] Re: Gnome 3 lock screen does not respect org.gnome.desktop.lockdown disable-user-switching
** Description changed: - The "log in as other user" option on the lock screen has been known to - cause Gnome 3 to stop responding on my hardware. - - I am open to assuming that this is a problem with my hardware, but - disabling org.gnome.desktop.lockdown disable-user-switching should - remove this option from the lock screen. It does not. - - This means anyone in the physical vicinity of my laptop may cause loss - of work with a single click. This is almost a security vulnerability. + Disabling org.gnome.desktop.lockdown disable-user-switching should + remove the "log in as other option" link from the lock screen. It does + not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.25.90.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 23 13:35:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Disabling org.gnome.desktop.lockdown disable-user-switching should - remove the "log in as other option" link from the lock screen. It does + remove the "log in as other user" link from the lock screen. It does not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.25.90.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 23 13:35:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1712548 Title: Gnome 3 lock screen does not respect org.gnome.desktop.lockdown disable-user-switching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1712548/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1712548] Re: Gnome 3 lock screen does not respect org.gnome.desktop.lockdown disable-user-switching
** Description changed: - The "log in as other user" option on the lock screen occasionally causes - Gnome 3 to stop responding. (The only time it hasn't was right after I - filed this bug, naturally.) + The "log in as other user" option on the lock screen has been known to + cause Gnome 3 to stop responding on my hardware. I am open to assuming that this is a problem with my hardware, but disabling org.gnome.desktop.lockdown disable-user-switching should remove this option from the lock screen. It does not. - This means anyone in the physical vicinity of my laptop can cause loss + This means anyone in the physical vicinity of my laptop may cause loss of work with a single click. This is almost a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.25.90.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 23 13:35:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1712548 Title: Gnome 3 lock screen does not respect org.gnome.desktop.lockdown disable-user-switching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1712548/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1712548] [NEW] Gnome 3 lock screen does not respect org.gnome.desktop.lockdown disable-user-switching
Public bug reported: The "log in as other user" option on the lock screen has been known to cause Gnome 3 to stop responding on my hardware. I am open to assuming that this is a problem with my hardware, but disabling org.gnome.desktop.lockdown disable-user-switching should remove this option from the lock screen. It does not. This means anyone in the physical vicinity of my laptop may cause loss of work with a single click. This is almost a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.25.90.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 23 13:35:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Description changed: - The "log in as other user" option on the lock screen causes Gnome 3 to - stop responding. + The "log in as other user" option on the lock screen occasionally causes + Gnome 3 to stop responding. (The only time it hasn't was right after I + filed this bug, naturally.) I am open to assuming that this is a problem with my hardware, but disabling org.gnome.desktop.lockdown disable-user-switching should remove this option from the lock screen. It does not. This means anyone in the physical vicinity of my laptop can cause loss of work with a single click. This is almost a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.25.90.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 23 13:35:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-08-14 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1712548 Title: Gnome 3 lock screen does not respect org.gnome.desktop.lockdown disable-user-switching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1712548/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1291365] Re: gnome screensaver locks again shortly after unlocking
As a result of this bug (the screensaver is not meant to trigger as the user is trying to actively use the system), it might happen that the screensaver fails to acquire focus properly as it fades in. As a result you can type in characters, but the keystrokes are sent in underneath windows... such as an IRC client. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1291365 Title: gnome screensaver locks again shortly after unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1291365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292965] Re: Unlocking screensaver needs two redundant steps
*** This bug is a duplicate of bug 1291365 *** https://bugs.launchpad.net/bugs/1291365 ** This bug is no longer a duplicate of bug 1292620 Session unlocking after screen blank results in screen blanking and a locked sessions ** This bug has been marked a duplicate of bug 1291365 gnome screensaver locks again shortly after unlocking -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292965 Title: Unlocking screensaver needs two redundant steps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292965/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292620] Re: Session unlocking after screen blank results in screen blanking and a locked sessions
*** This bug is a duplicate of bug 1291365 *** https://bugs.launchpad.net/bugs/1291365 ** This bug has been marked a duplicate of bug 1291365 gnome screensaver locks again shortly after unlocking -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292620 Title: Session unlocking after screen blank results in screen blanking and a locked sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292620] [NEW] Session unlocking after screen blank results in screen blanking and a locked sessions
Public bug reported: What happens: 1. I lock my session 2. Time passes; screen goes blank 3. I type in my password 4. I get my session back for 2 seconds 5. Screen blanks (given enough seconds, the monitor says no HDMI input) 6. I move the mouse, the screen comes back 7. I get another password prompt (same as the one in step 3) 8. I unlock the session correctly 9. I resume work. What should happen instead are steps 1-3,8-9. Questions from https://wiki.ubuntu.com/DebuggingScreenLocking that are still relevant: What desktop environment does this problem occur in? Unity 3D Do you use visual effects? Unity 3D's defaults. Is this a laptop or a desktop machine? Laptop How many monitors do you use? 2, of which only 1 is active. If it is a laptop, do you use an external screen? Yes. Only the external screen is ON. The lid is closed at all times. Do you have the hamster-applet application installed? No. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 17:30:13 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2012-03-15 (728 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-01-22 (50 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: gconftool-2 --dump /apps/gnome-screensaver /apps/gnome-power-manager /desktop/gnome/session /desktop/gnome/lockdown screen-locking-debug.xml https://bugs.launchpad.net/bugs/1292620/+attachment/4024173/+files/screen-locking-debug.xml -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292620 Title: Session unlocking after screen blank results in screen blanking and a locked sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 631009] Re: Using volume control keys on my USB keyboard stops left click to be registered until I unplug the keyboard.
This bug made its way into 10.10 final. (Marked from incomplete to new per comment #3) ** Changed in: gnome-applets (Ubuntu) Status: Incomplete = New -- Using volume control keys on my USB keyboard stops left click to be registered until I unplug the keyboard. https://bugs.launchpad.net/bugs/631009 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 631009] Re: Using volume control keys on my USB keyboard stops left click to be registered until I unplug the keyboard.
Sure. Here it is. (Nothing is added to it by pressing media control keys.) ** Attachment added: .xsession-errors https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/631009/+attachment/1579217/+files/.xsession-errors -- Using volume control keys on my USB keyboard stops left click to be registered until I unplug the keyboard. https://bugs.launchpad.net/bugs/631009 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 631009] [NEW] Using volume control keys on my USB keyboard stops left click to be registered until I plug off the keyboard.
Public bug reported: Binary package hint: gnome-applets The external keyboard I use for my laptop is a Microsoft® Digital Media Keyboard 3000. After I use the volume control I can no longer left click on anything and the panel no longer responds to keyboard or mouse events. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-applets 2.30.0-3ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3 Uname: Linux 2.6.35-19-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sun Sep 5 19:09:03 2010 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-applets ** Affects: gnome-applets (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- Using volume control keys on my USB keyboard stops left click to be registered until I plug off the keyboard. https://bugs.launchpad.net/bugs/631009 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 631009] Re: Using volume control keys on my USB keyboard stops left click to be registered until I plug off the keyboard.
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/631009/+attachment/1547005/+files/Dependencies.txt -- Using volume control keys on my USB keyboard stops left click to be registered until I plug off the keyboard. https://bugs.launchpad.net/bugs/631009 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
