[Bug 1292398] Re: Second screen position isn't saved from one session to another

2019-05-10 Thread Chris Rainey
@macbreeze you might want to open a bug for the xfce4-session package or the xubuntu meta package as this one is targeting the gnome-shell package. LightDM has settings in /etc/lightdm for overriding which monitor is used for the login widget and xrandr tool may help in the session after login. --

[Bug 1292398] Re: Second screen position isn't saved from one session to another

2019-04-22 Thread Chris Rainey
@vanvugt: not sure if #136 is directed at my comment in #135, but the _only_ way to produce the problem is to logout or reboot which naturally involves the display manager. Again, the problem goes away, for my case, simply by using a different display manager, as stated in #131. The problem is cle

Re: [Bug 1292398] Re: Second screen position isn't saved from one session to another

2019-04-18 Thread Chris Rainey
Our setup: 1. Older GPU(Integrated Intel® HD Graphics 2000) 2. Always using some sort of display multiplexer(splitter) on VGA out to dual TV’s, previously, now only single local monitor on VGA and 4K Tx(wireless) on HDMI out to a projector, currently. Thoughts: 1. Could the splitter or wireless

Re: [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

2019-03-20 Thread Chris Rainey
I find that primary(left-clicking) up to 15 or 20+ times _eventually_ spawns the pkexec-gui box. On Wed, Mar 20, 2019 at 9:26 AM Bjoern H. <1727...@bugs.launchpad.net> wrote: > I have this issue both in 18.10 and 19.04. Using arrows and space does > not work, the only workaround I've found is "s

[Bug 1820423] Re: monitors.xml is not parsed or applied correctly during login after reboot or shutdown

2019-03-20 Thread Chris Rainey
** Description changed: - WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome- - screensaver + numlockx(optionally) + WORKAROUND + + Replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver + + numlockx(optionally) + TL;DR + + Correct positioning and workin

[Bug 1820423] Re: monitors.xml is not parsed or applied correctly during login after reboot or shutdown

2019-03-19 Thread Chris Rainey
** Summary changed: - monitors.xml is not parsed or applied correctly after reboot or shutdown + monitors.xml is not parsed or applied correctly during login after reboot or shutdown ** Description changed: WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome- screensaver

[Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown

2019-03-18 Thread Chris Rainey
** Bug watch added: gitlab.gnome.org/GNOME/gdm/issues #474 https://gitlab.gnome.org/GNOME/gdm/issues/474 ** Also affects: gdm via https://gitlab.gnome.org/GNOME/gdm/issues/474 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ub

[Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown

2019-03-18 Thread Chris Rainey
** Description changed: WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome- screensaver + numlockx(optionally) TL;DR After a clean install of Ubuntu 18.10, connecting a FHD(1920x1080) LED monitor to the VGA port of a DELL Optiplex 390 desktop tower, connecting

[Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown

2019-03-18 Thread Chris Rainey
@seb128 I have edited the bug description to provide more information on how the issue is triggered. The bug occurs during the handoff of gdm3 ---> gnome-shell(mutter?) _after_ login. The issue is repeatedly and consistently triggered until GDM(gdm3) is replaced by LightDM(slick- greeter) and then

[Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown

2019-03-18 Thread Chris Rainey
** Description changed: WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome- screensaver + numlockx(optionally) - ERROR(syslog) = "Failed to get current display configuration state: - GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name - "org.gnome.Mutter.DisplayC

[Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown

2019-03-17 Thread Chris Rainey
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1820423 Title: monitors.xml is not parsed or applied c

[Bug 1760849] Re: Login screen appears on only one monitor and it's not the one I want

2019-03-16 Thread Chris Rainey
WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome- screensaver + numlockx(optionally) Greeter will auto-appear on whichever screen your mouse is on or moves to, dynamically. See: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423 -- You received this bug notificat

[Bug 1820423] Re: monitors.xml is not parsed or applied correctly after reboot or shutdown

2019-03-16 Thread Chris Rainey
** Description changed: WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome- - screensaver + screensaver + numlockx(optionally) ERROR(syslog) = "Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.M

[Bug 1292398] Re: Second screen position isn't saved from one session to another

2019-03-16 Thread Chris Rainey
WORKAROUND FOR UBUNTU 18.10(clean install): Replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver + numlockx(optionally) See: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, wh

[Bug 1820423] [NEW] monitors.xml is not parsed or applied correctly after reboot or shutdown

2019-03-16 Thread Chris Rainey
Public bug reported: WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome- screensaver ERROR(syslog) = "Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist" gnome-shell[30

[Bug 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .

2019-02-01 Thread Chris Rainey
[SOLVED] Just needed to: $ sudo apt install gstreamer1.0-plugins-bad I'm not sure why this isn't included in the restricted-extras or libdvd-pkg depends? ** Summary changed: - DVD playback error: unable to play . . . DVD source is required . . . + [SOLVED] DVD playback error: unable to pl

Re: [Bug 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .

2018-12-20 Thread Chris Rainey
$ dpkg -l | grep dvdcss ii libdvdcss-dev:amd64 1.4.2-1~local amd64library for accessing encrypted DVDs - development files ii libdvdcss2:amd64 1.4.2-1~local amd64library for accessing encry

Re: [Bug 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .

2018-12-19 Thread Chris Rainey
@Daniel: sorry . . . forgot to mention that ubuntu-restricted-extras(which depends on *-addons) _is_ installed. I also ensured that all other dependencies are installed according to: https://help.ubuntu.com/stable/ubuntu-help/video-dvd-restricted.html.en This definitely feels like a regression..

[Bug 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .

2018-12-19 Thread Chris Rainey
** Also affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1809044 Title: DVD playback error: unable to play . . . DV

[Bug 1711538] Re: Tap-to-click does not work on the GDM login screen

2018-12-17 Thread Chris Rainey
Upstream bug-watch(Launchpad does not track GitLab, so here it is): https://gitlab.gnome.org/GNOME/gnome-control-center/issues/124 -- 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/1711538

[Bug 1808638] Re: Tap-to-Click at login screen for principle of least astonishment (POLA)

2018-12-15 Thread Chris Rainey
Migrated upstream to: https://gitlab.gnome.org/GNOME/gsettings-desktop- schemas/issues/4 ** Changed in: gdm Importance: Medium => Undecided ** Changed in: gdm Status: Expired => New ** Changed in: gdm Remote watch: GNOME Bug Tracker #785855 => None -- You received this bug notifica

[Bug 1808638] Re: Tap-to-Click at login screen for principle of least astonishment (POLA)

2018-12-15 Thread Chris Rainey
As Launchpad has _not_ been updated to track GNOME bugs which have been migrated to GitLab, I'm posting an upstream bug which can also be tracked for this issue: https://gitlab.gnome.org/GNOME/gdm/issues/325 ** Bug watch added: GNOME Bug Tracker #785855 https://bugzilla.gnome.org/show_bug.cgi

[Bug 1808638] [NEW] Tap-to-Click at login screen for principle of least astonishment (POLA)

2018-12-15 Thread Chris Rainey
Public bug reported: I've observed many end-users who are confused by the lack of ability to "Tap-to-Click" on their touchpads at the login screen after boot(and screen-lock?). Most---if not all, of these users are migrating from MS Windows or another system which does prevent this technique. In

[Bug 1802507] [NEW] "Launch Calculator" keyboard setting does not work

2018-11-09 Thread Chris Rainey
Public bug reported: Keyboard setting for "Launch Calculator" does _not_ work for snap installed "gnome-calculator". WORKAROUND: $sudo apt install gnome-calculator && sudo snap remove gnome-calculator ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 P

[Bug 1780308] Re: calculator does not start using special-key on keyboard

2018-07-05 Thread Chris Rainey
Thanks @mottenkiller. I've marked my bug, https://bugs.launchpad.net/ubuntu/+source/gnome- settings-daemon/+bug/1773589, as a duplicate of yours since you actually uncovered the mechanics of the problem. ** Package changed: apache2 (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received thi

[Bug 1773589] Re: gnome-calculator not launching with any custom shortcut(Super+3)

2018-07-05 Thread Chris Rainey
*** This bug is a duplicate of bug 1780308 *** https://bugs.launchpad.net/bugs/1780308 ** This bug has been marked a duplicate of bug 1780308 calculator does not start using special-key on keyboard -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, whic

[Bug 1773589] [NEW] gnome-calculator not launching with any custom shortcut(Super+3)

2018-05-26 Thread Chris Rainey
Public bug reported: Creating a custom keyboard shortcut for launching gnome-calculator is possible in the gnome-control-center keyboard panel, but no shortcut works when tested. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubun

[Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2018-02-05 Thread Chris Rainey
Never mind, found it: https://bugs.launchpad.net/launchpad/+bug/1747469 Sorry for the SPAM! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/1714518 Title: GTK+3 doesn't show FUSE/

[Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2018-02-05 Thread Chris Rainey
OK so I'm _really_ glad to see the work on this bug progressing and, as such, I've been attempting to "add myself" to this bug's "affected user" list. However, I have _not_ been able to do so for the past 2-weeks with the error message: "timeout, please try again later". Does anybody know how

[Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2018-01-26 Thread Chris Rainey
@colin-colino Awesome! Thanks for your work on this. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/1714518 Title: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) ne

[Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2018-01-26 Thread Chris Rainey
In case any Ubuntu/GNOME Dev's are confused about the urgency of this and they don't work in a LAN/WAN-based environment: 1. Switching business users from MS Windows to Ubuntu Linux carries an expectation that they can still access LAN/WAN resources from the 'file chooser' dialogs(i.e. Chrome brow

Re: [Bug 1700813] Re: Metacity-3.24 crashes Xorg while installing Microsoft Office 2013 using winehq-stable

2018-01-20 Thread Chris Rainey
I never got back to testing this as the need went away. On Sat, Jan 20, 2018 at 9:55 AM dino99 <1700...@bugs.launchpad.net> wrote: > That version is now dead > > http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml > > Is that i

[Bug 1700813] [NEW] Metacity-3.24 crashes Xorg while installing Microsoft Office 2013 using winehq-stable

2017-06-27 Thread Chris Rainey
Public bug reported: Metacity crashes back to TTY's, as I use startx + .xinitrc, when reaching 82% of the initial MS Office 2013 installer with the following commands & syslog entries: $ WINEPREFIX=~/.wine/Office2013 WINEARCH=win32 wine setup32.exe /var/log/syslog: ... Jun 23 13:52:21 CKR-1 ker

Re: [Bug 1686257] Re: gdm3 fails to start when default session-name=ubuntu

2017-05-16 Thread Chris Rainey
Works-for-me after dist-upgrade using Ubuntu Gnome 17.04 64-bit and Intel® HD Graphics 520 (Skylake GT2). On Tue, May 16, 2017 at 10:46 AM Johon Doee <1686...@bugs.launchpad.net> wrote: > The update to gdm3 - 3.24.1-0ubuntu0.1 is just crap. > > It's not possible anymore to switch users. It just s

[Bug 1686257] Re: gdm3 fails to start when default session-name=ubuntu

2017-05-11 Thread Chris Rainey
@jbicha: yeah ... I just tried to reproduce in a gnome-boxes clean install of ubuntu-16.04.2-x86_64 to no avail. gnome-session-wayland is _not_ required. Workaround: install ubuntu-gnome-default-settings was all that was needed to complete a boot cycle. Sorry for hijacking this bug! -- You r