[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:

[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"

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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.

[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

[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

[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