Buy a cheap Radeon card. This fight is not worth having.
On Mon, Jul 27, 2020 at 3:15 PM Adrian Nida <1875...@bugs.launchpad.net> wrote:
>
> Hi, Upgraded an old desktop from 19.10 to 20.04 and hit this graphics
> display issue. I also have the same graphics card:
>
> >From lspci:
> 03:00.0 VGA
I'd really like to test this (on 20.04), but there is no sign of it yet,
even as a developer option pre-release.
--
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/1879968
Title:
Adam - thanks for the clarification. I'm afraid for some of us ordinary
users the subtleties of 'fix released' but not released in ubuntu to the
outside world evaded me. Sorry.
I sincerely hope the fix works!
--
You received this bug notification because you are a member of Ubuntu
Desktop
It is not fixed in mutter 3.36.3 using libreoffice. I have checked and
o have 3.36.3 installed (and rebooted) and tested again. It failed
first time.
It seems to me that there is something very odd going on here. How was
the fix tested?
This is second time it has been 'fixed' but users have
Marcello - yes indeed.
For me it is worst with spreadsheets, where I copy a lot of data
regularly. For instance when keeping a record of regular measurements, I
copy the previous item's formulae each time. I only started to realise
that a lot of my sheets were corrupted in early April.
With
I am still really struggling to understand why this is not a major issue
amongst ubuntu users. If I use the default interface I get driven crazy
several times a day with mainly libreoffice various applications,
copying and pasting and getting the wrong data.
Can it be that there are either very
Marcello. I switched to Wayland. For a while now I have noticed
Libreoffice, wine applications, and some others being irritatingly slow,
and wondered why. It's Wayland! Switching back to the normal ubuntu
desktop has bought speed back, but brought the bug back with it.
I can't help wondering
I don't wan't to advertise but just to give an impression what virtual hardware
we are talking about:
https://contabo.com/?show=vps
Both VPS are the SSD models. The interesting thing is that the problems
started with Ubuntu 20.04. - I already used gnome on Ubuntu 18.04. Now I
installed
Thanks.
I think I have tried both before but just to be sure I changed both
settings and rebooted. Now the screen is not bluish with blue lines
anymore it is black and I can switch to shell. So that's more or less
like on VPS2 but without purple look.
After that I returned to
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
Daniel, sorry, but as far as I am concerned this is an ubuntu bug. That
ubuntu uses, as a fundamental component (not just an add-on), something
else is surely an ubuntu problem?
If my car breaks down I don't search for the supplier of a component, I
go to the car maker. I do not know if other
Can this get escalated in any way?
Surely such a basic operation as cut/copy and paste should be totally
reliable, as it has been on all the systems I have used since 1970. A
fundamental inability to do what a user requests is critical, in my
view.
I think I will have to ask people in the IT
I now realise a couple of my Calc spreadsheets have been corrupted
because of faulty copy and paste. The context menu is definitely the
worst offender, but now any regular copy and paste (eg weekly or monthly
readings of various things) have to be double-checked.
For me, this is a Major bug. To
Oh dear. Davide, you are right. I habitually use keyboard control keys
for cut, copy and paste, and had to try quite hard to get the problem.
Using the context menu (within one writer document) it fails for almost
every other try.
Using the main menu it rarely fails, but it did occasionally.
I tried to reproduce bug #1852183 with just one writer document, and
failed to do so after the mutter update. Maybe I didn't try hard enough,
but it didn't re-occur after many trials in one writer document.
However, I have now tested copying between two writer documents, and
reproduced the same
Ethany - is there something else I can do? I've installed the proposed
update, retested, and so far all seems well (as I said in #159).
It's difficult to test and report on a problem which doesn't happen
every time you do something. I never found a pattern to it, just when
it did start to
Just for info, I've never used the 'clipboard indicator extension', so
disabling it wasn't an option for me.
--
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/1852183
Title:
[X11]
Thanks Adam. I've made a note for then next time I need to try 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/1852183
Title:
[X11] copy/paste (clipboard) with LibreOffice is
I used 'developer options' to install all the proposed updates last
night. I could not find a way to just update the 4 mutter files - it
insisted on updating many files including the kernel.
So far, so good. I've done 30 or so cut/copy and paste with no errors
so far.
I wouldn't know how to
I would like to try upgrading mutter (proposed) and testing and using it
if possible but a mass of other stuff is also said to be required (By
synaptic), including kernel. Is that correct?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I have tested using the vanilla version (debs) of libreoffice and had
the same problem as in the ubuntu-specific build. (I also tested on
Windows 10 and did not have the problem).
I have failed to replicate the problem with geany on ubuntu.
--
You received this bug notification because you are
I have just started having this problem, having updated to 20.04. So
far I have only encountered it with libreoffice writer, about 30% of the
time I copy/cut and paste (whether by menu or keyboard shortcuts). I do
this a lot due to the nature of my writing.
This is the first time since I moved
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
idia card after switching from the
> digital video output to the on-card VGA output, but over a period of a
> couple of weeks or so, the video degraded again.
>
> The new card is a VisionTek Radeon 5450.
>
>
> On 4/28/20 1:42 PM, Tim Hockin wrote:
> > I just filed https://b
I just filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712
which feels like it might be similar?
--
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/1860483
Title:
Public bug reported:
On focal fossa Ubuntu software will not install .deb files (such as
Google Chrome installer) however gdebi has no problem with the same
files.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-software (not installed)
ProcVersionSignature: Ubuntu
Public bug reported:
On focal fossa Gimp refuses to open files on usb connected drives. It
fails 'Permission denied'. Other software such as Image Viewer and
Shotwell has no problem with the same files.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gimp (not installed)
** Tags added: champagne
--
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/1870758
Title:
[nvidia] Display scaling results in a blank screen (power save state)
To manage
@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
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
the splash screen, it crashed and the GIMP
Crash Debug dialog opened. If I can be of any help, please don't hesitate.
Tim Kissane
downbound.ri...@gmail.com
$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
$ apt-cache policy gimp
gimp:
Installed
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
I'm using autologin. But the login-window always comes up wen booting into
ubuntu.
The one where you can click your own user or login with a guest. (Page is all
purple)
When booting into the recovery option everything works perfectly and the
password prompt only comes up when i'm opening the
Public bug reported:
New upgrade failed with initial upgrade and i had to boot-repair to get to the
normal ubuntu login window.
The button Automatic Login in the settings does not work either...
Using Ubuntu 19.10
gdm3:
Installed: 3.34.1-1ubuntu1
Candidate: 3.34.1-1ubuntu1
Version table:
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
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.
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
--
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.
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
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
> 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
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
"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
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
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
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
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
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.
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
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1235
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1235
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1235
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Help me with the history, though... I started on this machine with
15.10, then 16.04, and now 18.04. Wasn't 16.04 _not_ Gnome but Unity
instead? This seems to be an issue with some left-over setting from
16.04 that's messing up 18.04. (unless it's something left over from
15.10)
There's so
I'm not sure I understand your questions...
If you're asking if I have the same problem when logging in with a
different user, then "yes" it also doesn't work when logging in with a
2nd account that's on my machine. That 2nd account existed before the
upgrade to 18.04.
Also, the keys to disable
I really have no idea what package to file this against because I don't
know where the disconnect lies nor how to determine that. Please let me
know what additional information is needed.
** Package changed: ubuntu => gnome-settings-daemon (Ubuntu)
--
You received this bug notification because
I'm on Ubuntu 19.04 as well and having issues with this.
I have an i7-8750h paired with a gtx 1050ti in a Dell G515.
I don't exactly what I did, but I can give a general idea:
I decided this morning that battery life was important to me, so I
tinkered around with TLP. After I did that
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
I had the same issue a few weeks ago, now however with 3.31.92 (on
Disco) I do get the configuration dropdown when selecting my HDMI Audio
device. It came up blank initially, but appears to have saved the
correct setting since.
--
You received this bug notification because you are a member of
Hi Peter,
Thanks for your bug report.
I was one of the original authors the system-monitor extension however
no longer actively involved in the project. gnome-shell extensions are
not supported by Canonical/Ubuntu (unless they are installed in the
default session) or GNOME. You would need to
/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
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 1725676 is about not being able to select a different keyboard
layout while this is about being able to select a different layout, but
it not actually working. It's unrelated.
bug 1652618 sounds similar, but the solution makes it seem to be
different. I went in and changed the settings to
apport information
** Tags added: apport-collected bionic
** Description changed:
I was using 16.04 with Dvorak and US-Qwerty keyboard layouts and was
able to utilize both on the login screen. My default layout was Dvorak
(defined in /etc/default/keyboard).
When I upgraded to 18.04
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1813304/+attachment/5233767/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1813304/+attachment/5233768/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
I was using 16.04 with Dvorak and US-Qwerty keyboard layouts and was
able to utilize both on the login screen. My default layout was Dvorak
(defined in /etc/default/keyboard).
When I upgraded to 18.04 the login became Dvorak only, but after some
searching I found the
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
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
Still present in 18.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/996552
Title:
file roller does not open files with odt ending
To manage notifications about this bug go
Bug still exists in 18.04
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/887331
Title:
file-roller cannot open filetypes with derived mimetypes (e.g. epub
and ods files)
To
.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
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
I uninstalled lightdm and lightdm-gtk-greeter to get the log. I
reinstalled lightdm and lightdm=gtk-greeter, restarted display-manager,
and I'm up and running again.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
** Attachment added: "boot with gdm3, fails to enumerate displays."
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/174/+attachment/5210975/+files/prev_boot.txt
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are
I'm already not running Wayland. When I was running Wayland, it started
up on the internal display using the Intel driver. When docked, I don't
use the internal display, so I disabled Wayland.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Incomplete => Confirmed
--
You
Adding nomodeset rebuilding initrd and rebooting does not fix it.
The Lenovo ThinkPad W540 has no option to disable the integrated video
card. The internal display is always run by the intel. I have it set to
use the nvidia on external displays because that allows supporting more
displays.
So
nvidia drivers build and install just fine. Starting gdm3 fails to
detect displays, but Xorg does start. Stopping gdm3 and running a bare
Xorg gets working displays. Restarting gdm3 and displays work.
Displays light up fine with lightdm-gtk-greeter and the single Xorg
instance.
If anyone has
After completely removing the nvidia drivers, rebooting, and
reinstalling the nvidia drivers, even the old kernel fails to boot. This
appears to be an nvidia driver issue that shows up because of the gdm3
setup where it runs two different Xorg instances. Under lightdm+gnome
the displays light up
** Summary changed:
- Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1
+ gdm3: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Probably the tracker patch needs to be updated, there seem to be a
couple of new modules using tracker that didnt exist when I wrote that
patch.
Upstream last I check only supports optional tracker at build time. Not
run-time detection like we did in distro patches in Ubuntu.
--
You received
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
** Bug watch added: Debian Bug tracker #908800
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908800
** Also affects: nautilus via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908800
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
thumbnailers are working fine for me, both tiff and jpg, perhaps there
is still a missing dependency, that is normally otherwise pulled in by
vanilla-gnome-desktop. I generally only test gnome3-staging on systems
with that meta package.
Can you file a separate bug for nautilus not starting
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
can you try reinstall tracker 2.1.3 and see if that file exists on your
filesystem? If it doesnt please run apport-collect which should
colllect your dpkg/apt logs.
see this page for manually getting backtraces
https://wiki.ubuntu.com/DebuggingProgramCrash
On 12/09/18 18:06, Harry wrote:
> I
Hi Harry,
Thank you for your bug report.
I am running nautilus 3.30 with tracker 2.1.3 on two system and they
are both working, so we will need some more info. Thumbnails are working
also
That default.rule file does exist in the tracker 2.1.3-1~cosmic1
package, is it not installed on
Public bug reported:
To go along with the rest of GNOME 3.30
Both tracker and tracker-miners 2.1.4 will be synced from Debian.
tracker is not installed by default on any Ubuntu Flavours, but does
provide an important part of the GNOME-Shell experience.
These releases bring lots of fixes and a
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
What did you upgrade from? I think the banner would be set in
/etc/gdm3/greeter.dconf-defaults these days
--
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/1774215
Title:
adding a
the gdm greeter/login screen and the lock screen are mostly independent.
The gdm greeter runs its own instance of gnome-shell running in a
special gdm mode.
The lock screen is drawn by the current gnome-shell session and thus
uses the current gnome-shell theme.
What gnome-shell theme are you
Public bug reported:
Install failed after upgrade from 16.04 to 17.10
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: totem-plugins 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
NonfreeKernelModules: nvidia_uvm
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
OP said that this also affects Xubuntu and Lubuntu so its not likely
only gnome-settings-daemon involved here, since neither of them use it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
/var/log/gdm is still used as a fallback in case journald is unavailable
or disabled. Unless upstream remove that I don't think we should remove
it from the packaging.
** Changed in: gdm3 (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of
gdm still runs under wayland by default. It is the "Ubuntu" login
session that defaults to Xorg.
--
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/1756061
Title:
'/var/log/gdm3/':
gdm logs to systemd journal these days.
You need to enable debugging in /etc/gdm3/custom.conf to get any useful logs
though
--
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/1756061
fossfreedom, your patch looks fine to me. It does seem more generally
useful however not sure who is using gnome-screensaver anymore? probably
just Unity as a fallback?
I was going to upload it to unblock you, but it has been dropped from
the ubuntu-desktop package set with the move to
Yes it probably makes sense to wait until after the LTS to drop those.
Will revisit early next cycle.
I have dropped the upstart patch on bzr branch for now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
Public bug reported:
I have had a look through the current gnome-session packaging and there
are a number of packages which I would like to drop.
22_support_autostart_delay.patch - This was broken while we were running
under upstart user sessions, not sure if it currently works with
systemd,
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
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:
/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
101 - 200 of 1780 matches
Mail list logo
