Re: [Bug 207072] Re: nautilus does not display samba shares for machines inside an ADS network.

2008-10-08 Thread Tim Richardson
On Wed, 2008-10-08 at 19:58 +, Sebastien Bacher wrote: changing GNOME to use gnomevfs rather than gvfs would basically means downgrading some hundred applications and the GNOME desktop to its gutsy version, you can as well use gutsy if that's to do that change Or use the about to be

[Bug 125308] Re: [gutsy] esd makes diverse gnome apps freeze

2008-10-12 Thread Tim Richardson
I have the same problem with Debian Lenny. I am using pulseaudio. The problem occurs when I have system sounds turned on. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499081 -- [gutsy] esd makes diverse gnome apps freeze https://bugs.launchpad.net/bugs/125308 You received this bug

[Bug 125308] Re: [gutsy] esd makes diverse gnome apps freeze

2008-10-12 Thread Tim Richardson
See my upstream report http://pulseaudio.org/ticket/381 -- [gutsy] esd makes diverse gnome apps freeze https://bugs.launchpad.net/bugs/125308 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list

[Bug 213404] Re: high CPU usage when creating a new message

2008-07-14 Thread Tim Richardson
I forwarded it Bug 543022 – Exchange plugin unusable if Global Catalog server setting is blank http://bugzilla.gnome.org/show_activity.cgi?id=543022 It is definitely a bug, and it seems easy to fix since there is a very simple user workaround. -- high CPU usage when creating a new message

[Bug 213404] Re: high CPU usage when creating a new message

2008-07-14 Thread Tim Richardson
I have forwarded it. This is one of the easiest bugs to reproduce that I have ever filed, and it has one of the easiest workarounds, so this should be low-hanging fruit. I hope the Ubuntu team can backport a fix quickly once upstream fixes it. ** Changed in: evolution-exchange (Ubuntu)

[Bug 213404] Re: high CPU usage when creating a new message

2008-07-14 Thread Tim Richardson
And just to be clear, you can add me to the list of users who sees this bug. -- high CPU usage when creating a new message https://bugs.launchpad.net/bugs/213404 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing

[Bug 249321] [NEW] (Hardy) nautilus can not browse Windows small business server

2008-07-16 Thread Tim Richardson
Public bug reported: Binary package hint: nautilus I have hardy with proposed updates, etc. I still can not browse a Windows file server. It's a Windows Small Business Server. This is what i do: (1) Places - Connect to Server Choose windows server, enter the IP address of the server. Leave

[Bug 249321] Re: (Hardy) nautilus can not browse Windows small business server

2008-07-17 Thread Tim Richardson
I have gvfs 0.2.5-0ubuntu1 (hardy-proposed) -- (Hardy) nautilus can not browse Windows small business server https://bugs.launchpad.net/bugs/249321 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs

[Bug 207072] Re: nautilus does not display samba shares for machines inside an ADS network.

2008-07-17 Thread Tim Richardson
A workaround while waiting for this to be patched is to use via a terminal smbtree -U=trichardson%PASSWORD -k The % sign is just that: a % sign put your domain password in place of PASSWORD This let's me see the shares. -- nautilus does not display samba shares for machines inside an ADS

[Bug 249321] Re: (Hardy) nautilus can not browse Windows small business server

2008-07-17 Thread Tim Richardson
*** This bug is a duplicate of bug 207072 *** https://bugs.launchpad.net/bugs/207072 ** This bug has been marked a duplicate of bug 207072 nautilus does not display samba shares for machines inside an ADS network. -- (Hardy) nautilus can not browse Windows small business server

[Bug 50115] Re: Weather applet doesn't update after I connect to a network

2008-07-20 Thread Tim Richardson
I confirm this as well, in hardy. Perhaps that online check doesn't wait long enough for a wireless connection to be established. -- Weather applet doesn't update after I connect to a network https://bugs.launchpad.net/bugs/50115 You received this bug notification because you are a member of

[Bug 236666] Re: Switch user confuses virtual console usage 8.04

2008-07-29 Thread Tim Richardson
Intel GM965 video (laptop) lsmod show intel_agp -- Switch user confuses virtual console usage 8.04 https://bugs.launchpad.net/bugs/23 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list

[Bug 236666] Re: Switch user confuses virtual console usage 8.04

2008-07-29 Thread Tim Richardson
Switch user is pretty screwed up, and I don't think it is a video card problem. I just tried it again to see if the problem I reported above is still reproducible, since I am getting all updates including proposed. I have a User Switch in my top menu bar now. Here is what happened: I login as

[Bug 252956] [NEW] switchuser: virtual terminal then back to GDM resumes wrong user

2008-07-29 Thread Tim Richardson
Public bug reported: Binary package hint: gdm Log on as user 1 Switch user to user 2 start a virtual terminal resume gdm via alt-F7 you are resumed into user 1, not user 2 version: 2.20.7-0ubuntu1.1 ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- switchuser:

Re: [Bug 252956] Re: switchuser: virtual terminal then back to GDM resumes wrong user

2008-07-29 Thread Tim Richardson
Ah, thanks for the education. It's not a bug, but a feature, and a good one. On Tue, 2008-07-29 at 14:59 +, Sebastien Bacher wrote: thank you for your bug report, that's not a bug though, vt are allocated to session, user1 gets vt7, user2 gets vt8, user3 gets vt9 ** Changed in: gdm

[Bug 239560] Re: tomboy applet error can not add to panel when second login

2008-08-08 Thread Tim Richardson
It is forwarded here: http://bugzilla.gnome.org/show_bug.cgi?id=547032 I don't know why you can't reproduce it. It is still happening in hardy. It also happens in Debian sid. The easiest way to reproduce it is to enable multiple logins for the same user, then switch user and login to a second

[Bug 249373] Re: gnome session does not restore the previous session

2008-12-29 Thread Tim Richardson
For a slightly different perspective on this bug, see http://np237.livejournal.com/22014.html However, it's true that the old behaviour was not great: openoffice didn't seem to react to session exits (logouts), for example. -- gnome session does not restore the previous session

[Bug 126333] Re: [GUTSY] Regression - Volume Control Bar doesn't slide when using keyboard shortcut

2007-12-16 Thread Tim Richardson
For me, on Debian unstable, the volume hotkeys do not change the volume as seen in the gnome volume preference panel. The volume hotkeys change linein, if linein is enabled in the volume preference. If linein is not enabled, then the volume hotkeys do nothing. The volume hotkeys worked until

[Bug 126333] Re: [GUTSY] Regression - Volume Control Bar doesn't slide when using keyboard shortcut

2007-12-16 Thread Tim Richardson
my problem with Debian was unrelated. -- [GUTSY] Regression - Volume Control Bar doesn't slide when using keyboard shortcut https://bugs.launchpad.net/bugs/126333 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs

[Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work

2017-08-15 Thread Tim Richardson
On the newer machine, the P50, I reinstalled 17.10 ubuntu yesterday, with pre-release packages enabled. It is using gdm3. It works, even with nvidia modeset=1 and external monitors. It is not obvious to me which updated packages have fixed this, since I also tried pre-release on the broken

[Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work

2017-08-16 Thread Tim Richardson
Sorry, that was premature. I had not enabled modeset=1 properly. After doing that a) in Optimus mode, only the laptop display works. The nvidia settings control panel opens, but it detects no screens. b) in discrete nvidia BIOS mode, gdm is stuck in a greeter loop when trying to start a Gmome or

[Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work

2017-08-10 Thread Tim Richardson
Update & simplication. This bug affects 17.10 & 17.04 with the current LTS support nvidia drivers. This bug affects both my laptops with nvidia hardware. External monitors are not necessary to reproduce. Reproduction is simple. 1. Activate the nvidia hardware using discrete mode. Therefore no

[Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work

2017-08-10 Thread Tim Richardson
And also note that modeset=1 is not designed to activate wayland. It is necessary to use the Prime Synchonization feature of the new nvidia drivers, which is actually a feature of X 1.19 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work

2017-08-11 Thread Tim Richardson
It is also broken on a ThinkPad W520, which is much older hardware (although still supported by current nvidia drivers). The Nvidia driver, gdm3, gnome (or gnome ubuntu) and modeset=1 is broken. Replace gdm3 with lightdm, and everything works. -- You received this bug notification because you

[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-07-27 Thread Tim Richardson
For what it's worth, nvidia Optimus requires the integrated display to be modeset=1, this is what you mean by "nomodeset would break laptops", I assume. Should we be reporting this upstream? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work

2017-07-27 Thread Tim Richardson
*** This bug is a duplicate of bug 1705369 *** https://bugs.launchpad.net/bugs/1705369 ** This bug has been marked a duplicate of bug 1705369 Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) -- You received this bug notification because you

[Bug 1697882] Re: GDM should not allow X11 sessions when NVIDIA's KMS is enabled

2017-07-26 Thread Tim Richardson
What's the bug report for hybrid systems? I can't get gdm working with modeset=1 (aiming to get PRIME sync working). Is good in lightdm. There are so many bug reports with similar symptoms. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed

Re: [Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work

2017-07-26 Thread Tim Richardson
1706474 > > Title: > gdm3 nvidia modeset=1 is broken, external screens don't work > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions > -- Tim Richardson ** Attachment added: "syslog"

[Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers

2017-07-25 Thread Tim Richardson
I have the same symptoms as this bug with 17.04 and the new 375.82 driver if I am use modesetting with gdm. With lightdm it works fine. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

Re: [Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work

2017-07-25 Thread Tim Richardson
bug > report. > https://bugs.launchpad.net/bugs/1706474 > > Title: > gdm3 nvidia modeset=1 is broken, external screens don't work > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions > -- Tim Ri

Re: [Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work

2017-07-30 Thread Tim Richardson
subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1706474 > > Title: > gdm3 nvidia modeset=1 is broken, external screens don't work > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions > --

[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-07-27 Thread Tim Richardson
Maybe https://bugzilla.gnome.org/show_bug.cgi?id=784470 ** Bug watch added: GNOME Bug Tracker #784470 https://bugzilla.gnome.org/show_bug.cgi?id=784470 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work

2017-07-25 Thread Tim Richardson
** Attachment added: "xrandr output" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+attachment/4921331/+files/xrandr.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu.

[Bug 1706474] [NEW] gdm3 nvidia modeset=1 is broken, external screens don't work

2017-07-25 Thread Tim Richardson
Public bug reported: ubuntu 17.04 with gnome desktop. The laptop is a Thinkpad p50 with a quadro M1000M. To get this bug I am using the hybrid graphics mode. This problem occurs with 375.82 and also with the new 384 driver. When using gdm3 and options nvidia_375_drm modeset=1 the greeter only

[Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work

2017-07-25 Thread Tim Richardson
** Attachment added: "nvidia-bug-report" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+attachment/4921327/+files/nvidia-bug-report.log.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu.

[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-07-27 Thread Tim Richardson
boots to black screen when using Nvidia drivers (on a > desktop with an Intel GPU) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions > -- Tim Richardson ** Bug watch added: GNOME Bug Tracker #78447

[Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes

2017-09-22 Thread Tim Richardson
#22 worked for me, after logout/login. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1620806 Title: gedit edit window is transparent when using Ambiance and Radiance themes To

Re: [Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)

2017-09-21 Thread Tim Richardson
> https://bugs.launchpad.net/bugs/1714881 > > Title: > no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not > optimus) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gdm/+bug/1714881/+subscriptions > -- Tim Richar

[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-09-12 Thread Tim Richardson
As of the latest updates to gdm3, I still can't boot with my laptop when it's in discrete mode (nvidia graphics only). Does not get to the greeter. syslog is full of countless repetitions of "Stopping NVIDIA persistence Daemon". CPU must be high because the fan comes on. I've reported this but

[Bug 1716857] [NEW] gdm3, hybrid nvidia with modeset=1, no external monitors detected

2017-09-13 Thread Tim Richardson
Public bug reported: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them

[Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)

2017-09-13 Thread Tim Richardson
** Summary changed: - no gdm3 greeter with nvidia quadro and modeset=1 + no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

Re: [Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work

2017-08-26 Thread Tim Richardson
o manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions > -- Tim Richardson -- 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/1706474

Re: [Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work

2017-08-28 Thread Tim Richardson
cation because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1706474 > > Title: > gdm3 nvidia modeset=1 is broken, external screens don't work > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/170647

[Bug 1714881] [NEW] no gdm3 greeter with nvidia quadro and modeset=1

2017-09-04 Thread Tim Richardson
Public bug reported: This is to track https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1 causes loop, does not launch greeter " I don't know if this is an nvidia bug or a gdm3 bug but it requires both to reproduce. [reply] [−] Description t...@tim-richardson.net

[Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1

2017-09-04 Thread Tim Richardson
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714881/+attachment/4943940/+files/Error_syslog -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work on a Thinkpad p50

2017-09-04 Thread Tim Richardson
Daniel, with the latest 17.10 the nvidia problems are now more specific and easier to reproduce. Neither of my Thinkpads gets to the login screen in discrete Nvidia mode iff modeset=1 is used. In hybrid graphics, the session starts, I suspect this is due to the intel driver being available.

Re: [Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work

2017-09-01 Thread Tim Richardson
repository. On 28 August 2017 at 21:08, Tim Richardson <t...@tim-richardson.net> wrote: > Thanks Doug, that bug report is exactly as the nvidia forum so you and I > are doing the same thing. > > On 28 August 2017 at 02:41, Doug McMahon <1706...@bugs.launchpad.net> > wro

Re: [Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)

2017-11-14 Thread Tim Richardson
nvidia (not > optimus) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gdm/+bug/1714881/+subscriptions > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu

[Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)

2017-11-28 Thread Tim Richardson
Ciro, you have reported "works for me" but you have not confirmed that you are actually trying to reproduce the bug. The problem occurs when using modeset=1. You do not mentioned that here or in your related answer on askubuntu If you are not using modeset=1, which is essential for people using

[Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)

2017-12-12 Thread Tim Richardson
The user I referred to in the last comment has proposed changes to /lib/systemd/system/gdm3.service to fix the problem. I have added his proposed changes to this report: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716857 -- You received this bug notification because you are a

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2017-12-12 Thread Tim Richardson
ubuntu user Hon Weng Chong has emailed me as he continues to investigate the problem. He believes he has proof that it is is GDM configuration issue and has provided the following fix Hey Tim, I figured out a hack solution to the GDM prime issue. If you replace

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2017-12-12 Thread Tim Richardson
Celebratory fireworks from me. It seems to work. For ubuntu the only difference is [Service] ExecStartPre=/usr/share/gdm/generate-config becomes [Service] ExecStartPre=/usr/bin/xinit /usr/share/gdm/generate-config I have a proper ubuntu gnome session running with gdm, an external monitor

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2017-12-16 Thread Tim Richardson
However with this change I'm seeing very long pauses on restart/shutdown, i haven't found any iclue why in the logs. -- 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/1716857 Title:

Re: [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2017-12-12 Thread Tim Richardson
/bugs.launchpad.net/bugs/1716857 > > Title: > gdm3, hybrid nvidia with modeset=1, no external monitors detected > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- You received t

[Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)

2017-12-10 Thread Tim Richardson
Another user has report this on the nvidia linux board. This user reproducts the problem exactly, and reports a workaround which narrows down the problem. I haven't yet verified this workaround. While this user has both intel and nvidia, he/she does not appear to be using a laptop. Hey guys, I

[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

2017-12-30 Thread Tim Richardson
gdm3 and nvidia binary drivers don't work together yet. Maybe 18.04 although there's not much evidence that anyone who knows how to fix this problem is working on it. This problem has emerged since the default Ubuntu session now uses gdm3 (as of 17.10) but standard gnome users on all recent

[Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2018-07-08 Thread Tim Richardson
uBlock fixes it for me and others ... But there should be some user control -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1600622 Title: Screen doesn't lock or go to sleep

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2018-04-19 Thread Tim Richardson
I re-confirm this. Stock 18.04 has no graphics in pure nvidia mode (on a Thinkpad W520 in discrete graphics). lightdm works. -- 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/1716857

Re: [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2018-12-12 Thread Tim Richardson
sleep when certain Chrome tabs are open > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Deskto

Re: [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2018-12-13 Thread Tim Richardson
.launchpad.net/bugs/1600622 > > Title: > Screen doesn't lock or go to sleep when certain Chrome tabs are open > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions > -- Tim Richardson -- You recei

[Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2019-01-08 Thread Tim Richardson
I switched to KDE to have a look at it, by installing KDE Neon from the PPAs. Otherwise the same environment. The slow suspend doesn't happen in plasma, it suspends in five seconds, while still suspending properly (including open VMWare virtual machines). So it's not simply Chrome, the bug needs

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2019-01-03 Thread Tim Richardson
sddm works too: I just put kde plasma on my ThinkPad P50 with ubuntu 18.10, it works well. -- 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/1716857 Title: gdm3, hybrid nvidia with

[Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)

2018-09-12 Thread Tim Richardson
In 18.10 (pre-release) this bug is no longer present. -- 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/1714881 Title: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2018-09-14 Thread Tim Richardson
The current 18.10 nvidia packages have this problem too. That is, out of the box, the nvidia driver defaults to KMS now (first time on any distro) but the nvidia driver does not detect external screens. Probably should be a new bug I guess. -- You received this bug notification because you are a

Re: [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2019-02-20 Thread Tim Richardson
/bugs/1716857 > > Title: > gdm3, hybrid nvidia with modeset=1, no external monitors detected > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- You received this bug notifi

Re: [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2019-02-20 Thread Tim Richardson
gdm3, hybrid nvidia with modeset=1, no external monitors detected > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- You received this bug notification because you are a member of Ubuntu Deskt

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2019-05-15 Thread Tim Richardson
This works. Thanks. What does gdm3 do that requires this? -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Tim Richardson
I will post your findings to the nvidia developers forum. -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Tim Richardson
Hi Daniel, thanks for not forgetting about this, unlike everyone else :) Have you communicated this observation to Nvidia at all? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu.

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Tim Richardson
User generix reports that when gdm3 is compiled without wayland support, this bug is not seen. -- 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/1716857 Title: nvidia-drm.modeset=1

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Tim Richardson
I posted here: https://devtalk.nvidia.com/default/topic/1055528/linux/nvidia-driver-in- modeset-1-requires-root-permissions-daniel-van-vugt-canonical-concludes- it-is-an-nvidia-bug/?offset=3#5351122 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

Re: [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-20 Thread Tim Richardson
> nvidia-drm.modeset=1 results in no monitors detected by Xorg > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- You received this bug notification because you are a member of Ubun

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-20 Thread Tim Richardson
What we know about this bug is that gdm3, nvidia and modeset=1 is broken under configurations which are not broken when sddm and lightdm are used. we know that gdm3 sessions with external monitors work with root permissions. we know that gdm3 compiled with wayland also works (according to the

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-20 Thread Tim Richardson
"gdm3 compile without wayland", I meant -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg To manage

Re: [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-20 Thread Tim Richardson
vidia-drm.modeset=1 results in no monitors detected by Xorg > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions > -- Tim Richardson -- You received this bug notification because you are a member of Ub

[Bug 1706474] Re: gdm3 nvidia modeset=1 is broken, external screens don't work on a Thinkpad p50

2019-06-20 Thread Tim Richardson
I should add that the "fix" I reported is only a narrow fix. The internal display works. But external displays don't work if you have nvidia drivers, gdm3 and if you are using modeset=1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2019-04-21 Thread Tim Richardson
Still present in 19.04, although as a workaround, the nvidia drivers have reverted to installing without modeset=1, so external monitors work, and Optimus users get dreadful tearing on their laptop's internal screen. With modeset=1 (which in my case was a setting preserved during the update to

[Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)

2019-09-09 Thread Tim Richardson
This bug is still present in 19.04 and 19.10 (pre-release), my comment above was premature. -- 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/1714881 Title: no gdm3 greeter with nvidia

[Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2019-09-29 Thread Tim Richardson
I haven't had this problem for several releases, so it is only triggered under some circumstances. I suspected the hangouts extension (which I no longer use) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu.

[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

2019-09-27 Thread Tim Richardson
19.10 beta and nvidia drivers 430 and 435 have the same problem. I have made the bug title correctly specific. ** Summary changed: - nvidia-drm.modeset=1 results in no monitors detected by Xorg + nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg --

[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

2019-09-27 Thread Tim Richardson
And PS: workaround continues to be: use lightdm, a five minute fix at worst. https://askubuntu.com/questions/139491/how-to-change-from-gdm-to-lightdm -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu.

[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

2019-11-02 Thread Tim Richardson
I just installed popOS 19.10 an an Optimus laptop, nvidia option. Out of the box you get gdm3 and tear-free prime-sync; it uses Jeremy Soller's solution (root rights granted in Xwrapper) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)

2019-10-17 Thread Tim Richardson
Nvidia release notes for Linux, Solaris, and FreeBSD driver 440.26 [beta release] [long-lived branch release] (2019-10-17) have a comment: "Fixed a bug that could cause a blank screen on some DisplayPort monitors when logging in to GNOME, if the nvidia-drm kernel module parameter modeset=1 is

[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works.

2020-03-05 Thread Tim Richardson
@Alberto, couldn't prime-select do this when going into hybrid or Optimus mode? Only users with nvidia hybrid graphics would go down this logic path, and they are only ones who need the fix (but only if they are using gdm3, sddm and lightdm continue to be unaffected by this) The set of users who

[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

2020-02-27 Thread Tim Richardson
This bug persists in 20.04 daily. The one-line Pop!OS solution (https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/comments/26) works, just logout and login. Pop!OS has used this for several releases now, just saying. ** Summary changed: - nvidia-drm.modeset=1, gdm3 and optimus

[Bug 1749779] Re: System freeze when going back and forth fullscreen mode with Firefox

2020-05-03 Thread Tim Richardson
For me in 20.04, bug is definitely still present. I have earlyoom active, and 32 gb a few seconds of "freeze" (which is not really a freeze) earlyoom activates and nukes a few things, including Firefox, which brings back interactive response. It also killed Chrome and Remmina, which was

[Bug 1844641] Re: Login screen not keyboard accessible after using NoMachine

2020-06-03 Thread Tim Richardson
I experience this in 20.04 as well: remote session with Workstation, after termination the greeter on this host does not respond to the mouse. The keyboard allows access to virtual terminals and ctrl-alt- delete reboots. Hopefully nomachine has an answer. -- You received this bug notification

[Bug 1952107] Re: Google Contacts API Deprecated

2022-01-19 Thread Tim Richardson
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated

[Bug 1952107] Re: Google Contacts API Deprecated

2022-01-19 Thread Tim Richardson
(... Ubuntu 21.10) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated To manage notifications about this bug go to:

[Bug 1952107] Re: Google Contacts API Deprecated

2022-01-19 Thread Tim Richardson
I used proposed-updates today to get the latest evolution, and contact sync works again. So 3.40.4-1ubuntu2 works. (amd64 arch) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu.

[Bug 1971434] Re: Display powersave only blanks, but does not turn off

2024-03-16 Thread Tim Richardson
I use the wayland session. I sort of have this bug. The screens do power off, but then the backlights resume. It is still a blank screen -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu.