Please note that for virtio/virt-manager, setting this envionment
variable in ~/.profile may be a workaround.
export GSK_RENDERER=gl
this at least fixes Files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This affects qemu/kvm too. On vanilla 22.04 host, gtk4 apps (e.g. Files)
from 24.04 do not render properly (with 3D/openGL enabled)
via virt-manager
mesa in the 24.04 guest is 24.0.5-1
Fedora 40 guest with all updates has the same problem (open files apps and view
files in list view, for
the issues in Comment #10 appear to be closed, and they are not mentioned
anyway on
https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043
so it is confusing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For me the fix included the new version of pipewire (now released in
24.04) AND adding my user to the video group
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061687
Title:
Snapshot doesn't work
I confirm the findings of @corradoventu : fixing this requires both
pipewire1.0.5-1 AND adding my user to group video.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060390
Title:
Snapshot No
*** This bug is a duplicate of bug 2061687 ***
https://bugs.launchpad.net/bugs/2061687
** This bug has been marked a duplicate of bug 2061687
Snapshot doesn't work until camera is unplugged and plugged back in
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Package changed: ubuntu => pipewire (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065288
Title:
gnome 46 camera app requires systemctl --user restart pipewire
To manage notifications
Public bug reported:
In ubuntu 24.40 the camera app will not see my laptop camera until I do
this:
systemctl --user restart pipewire
this is required in every log in.
The camera problem also affects other usage, such as using the laptop camera in
google meet via firefox.
It is probably a
@sbeattie I tested the package you built for 22.04 and it fixes the
problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060354
Title:
Segfaults and assertion failures in Xorg's
@sbeattie It's broken in mantic too. In xwayland, the window dies. in
xorg, the session crashes, badly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060354
Title:
Segfaults and assertion failures
Yeah, for me it crashed 100% of the time with no changes, and removing a
configuration file (which among other things removed my non-default
preference for grayscale antialias) completely stopped the crashing.
This is in a kvm/qemu VM. So from my perspective, and from a few others
users, it looks
for what it's worth, JetBrains bug reports find that the problem is
triggered by requesting grayscale anti-aliasing.
https://youtrack.jetbrains.com/issue/IDEA-350864/Idea.sh-abort-X-window
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971434
Title:
Public bug reported:
Ubuntu now defaults to systemd oom handling.
Is there a way to warn an upgrade user who has earlyoom installed that the two
are in conflict (assuming that they are).
** Affects: earlyoom (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
I see this in the xorg session in the flatpak firefox save downloads
dialog, for instance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971112
Title:
File picker gets bigger more and more each
see also https://bugzilla.redhat.com/show_bug.cgi?id=2072070 for lengthy
discussion.
** Bug watch added: Red Hat Bugzilla #2072070
https://bugzilla.redhat.com/show_bug.cgi?id=2072070
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, out of habit I installed the snap. The .deb works fine, so I am
using that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967437
Title:
does not detect battery discharge 22.04 beta thinkpad
Ubuntu 22.04.
I still have this problem
intel-media-va-driver 22.3.0
tigerlake laptop
$ apt-cache show intel-media-va-driver
Package: intel-media-va-driver
Architecture: amd64
Version: 22.3.0+dfsg1-1
tim@ochre:~$ vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open
Public bug reported:
On Tigerlake Thinkpad X1, ubuntu 22.04 beta
powerstat -d 0
reports
Device is not discharging, cannon measure power usage.
this worked previously, including with the snap installed on Fedora 35
kernel is 5.15.0-23-generic
** Affects: powerstat (Ubuntu)
Importance:
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952107
Title:
Google Contacts API Deprecated
To manage
(... Ubuntu 21.10)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952107
Title:
Google Contacts API Deprecated
To manage notifications about this bug go to:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952107
Title:
I have this laptop. Bug happens on S3 suspend, much better on modern
standby (once it took two minutes or so for the touchpad to resume,
every other time it has worked).
Modern suspend does not use much battery. Mine slept for 8:20h last night and
the battery percentage declined from 96% to 94%.
It doesn't corrupt boots. It's inconvenient.
On Wed, 1 Sept 2021, 15:31 martin, <1396...@bugs.launchpad.net> wrote:
> This sounds like a massive, GIGANTIC bug which is corrupting people's
> boot setups. It's a wonder that it hasn't been fixed after SEVEN YEARS.
>
> --
> You received this bug
No data available from (1) or (2) and the problem has not reoccurred.
I have commented line 23 of crashdb.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927767
Title:
All apps crashed in my
Public bug reported:
The reboot failed with many services that could not stop. I think there
may have been a crash in the network stack.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-16-generic 5.11.0-16.17
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
The flathub version is fixed too.
Please see upstream bug report
https://github.com/pdfarranger/pdfarranger/issues/478
which is closed as fixed in new release.
** Bug watch added: github.com/pdfarranger/pdfarranger/issues #478
https://github.com/pdfarranger/pdfarranger/issues/478
--
You
Update. I had zram-tools installed as well. Or at least, I have it after the
upgrade to 21.04
I removed it and zram-config, and reinstalled zram-config, and it works fine.
However, this still doesn't make much sense: if they were both installed
previously, why did it stop working?
I stepped
Public bug reported:
Under 20.10, my machine of 64GB had 8 zram devices of 2GB each.
After the 21.04 upgrade, zram was still configured, but now with one 1 device
of 256MB.
dpkg-reconfigure did not fix this
purge and reinstall did not fix this.
$ cat /proc/swaps
Filename
e
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions
>
--
Tim Richardson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
//bugs.launchpad.net/bugs/1816497
>
> Title:
> [snap] vaapi chromium no video hardware decoding
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
>
--
Tim Richardson
--
You received t
tifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions
>
--
Tim Richardson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396379
T
I just installed Ubuntu 20.10 on a machine that was running Pop!os 20.04
and 20.10 (a fairly new AMD Ryzen desktop system, different to the
machine I had the problem on earlier, which was a laptop). Not 24 hours
later, this problem again. I thought there was something wrong with Team
app ('bloody
My sound control panel reports three speech-dispatcher entries in Volume
Levels. I don't know why.
My session is about two days old and I haven't had any instance of
distortion, so the workaround referred to in my previous comment, a
config change, may be a good idea for package maintainers to
If you want to test this, force YouTube to serve H264, which your card
supports judging by the vainfo results. A 4k 60fps YouTube video won't
be in a codec your hardware can handle, I guess. There are 'h264ify'
extensions for Chromium.
--
You received this bug notification because you are a
I will try this workaround/config change:
https://github.com/brailcom/speechd/issues/198#issuecomment-619605269
** Bug watch added: github.com/brailcom/speechd/issues #198
https://github.com/brailcom/speechd/issues/198
--
You received this bug notification because you are a member of Ubuntu
This bug started affecting me in the past week although I've been on
20.04 since launch. I have removed the packages including orca.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736222
Title:
device is an IdeaPad 5 14 (14ARE05) with a Ryzen 5 4600
Now on kernel 5.8
observation is that the touchpad sometimes doesn't work. So far,
shutdown and remove AC then restart fixes it every time. This was true
on 5.7 too.
Something goes wrong with hardware initialisation?
--
You received this
@olepet I have 14ARE05 too, same symptoms. It seems the hardware is different,
we need a new bug.
I see no elan modules loaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881319
Title:
I tested this today, and with HDMI connection, I no longer have the
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872159
Title:
booting with splash hangs when external monitors are
*** This bug is a duplicate of bug 1872159 ***
https://bugs.launchpad.net/bugs/1872159
** This bug is no longer a duplicate of bug 1874194
Ubuntu 20.04 HDMI connected, no boot
** This bug has been marked a duplicate of bug 1872159
booting with splash hangs when external monitors are
*** This bug is a duplicate of bug 1872159 ***
https://bugs.launchpad.net/bugs/1872159
** This bug has been marked a duplicate of bug 1872159
booting with splash hangs when external monitors are connected (pure intel
8th gen laptop)
--
You received this bug notification because you are
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
You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1396379
>
> Title:
> installer uses first EFI system partition found even when directed
> otherwise
>
> To manage notifications about this bug go to:
>
>
@vasyl: thanks, good comment. It pays to RTFM, apparently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765363
Title:
prime-select intel is not powering off the nvidia card
To manage
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
PS there is no text at all, the process gets as far as the spinning icon
and stops. I don't see the fsck check start.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872159
Title:
booting with
Hi Sebastien,
my most recent attachment #11 is from a failed boot.
When it gets stuck, I get no keyboard response from Esc, ctrl-C. I don't think
it is possible to log in to virtual terminals at this point in the boot, but if
I try, I can get to a blank screen, which after a few seconds jumps
I have been trying to work out how to log a failed session with plymouth debug
messages. I finally succeeded, it is attached.
Note that at the end of log file, it goes into suspend. That was me trying to
power off the machine, and not holding the button long enough. It actually
suspends and
I have been investigating other bug reports. I can't find anything that
helps my very much, but I did note references to timing. It is very
puzzling why I don't have problems when booting from the installation to
an external drive. That drive is actually a USB stick (ext4 formatted).
My internal
I installed 20.04 beta on a usb drive on the same machine, and reinstalled
packages to resemble my main install as closely as possible. The bug does not
occur when booting from the usb drive.
The most significant difference I can think of is that the main install is on
an lvm partition
** Attachment added: "boot messages with plymouth debugging messages"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5352286/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- booting with splash hangs when external monitors are connected (pure intel
laptop)
+ booting with splash hangs when external monitors are connected (pure intel
8th gen laptop)
** Description changed:
+ I think this is a problem with the splash boot loader. This problem
** Summary changed:
- booting with splash hangs when external monitors are connected
+ booting with splash hangs when external monitors are connected (pure intel
laptop)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "journalctl -b-1 > journal.txt"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5351782/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "journalctl -b0 > journal.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872159/+attachment/5351769/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What happens if you edit
/etc/default/grub
to remove splash as a setting (that is, boot without plymouth).
I was having similar problems to you, also with log message saying job was on
hold. I did not wait beyond 3 minutes. In my case, this only happens if an
external monitor is connected at
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872159
Title:
booting with splash hangs when external monitors are
boot.log could not be attached by the report tool, I added it manualy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872159
Title:
booting with splash hangs when external monitors are connected
Public bug reported:
I think this is a problem with the splash boot loader.
I have installed 20.04 to this laptop. Clean install, not an upgrade.
When booting from the install, the greeter screen is never reached if external
monitors are connected at startup.
I get the spinning ubuntu logo,
@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
not 'a fix', the intel maintainer's 5.4 patch has been applied by the
ubuntu devs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856653
Title:
CVE-2019-0154 caused major power problem, pls
Confirming that a fix has been backported to 20.04, currently in the
proposed kernel. I'm testing it, the power usage is great.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856653
Title:
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
Also, please note the upstream bug discussion also includes patches for 5.4
It seems that 5.4 is destined for 20.04. So far 5.4 upstream is still using the
first release of this patch, which means 5.4 has the i915 RC6 bug. 5.4 is a LTS
kernel bug so it strange to me, but please, I hope you can
Yes, that little patch applies cleanly to every 5.3 hwe build I've done (about
five I'd say)
To be clear:
diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c
b/drivers/gpu/drm/i915/gt/intel_lrc.c
index 82b7ace62d97..b18f281d5d12 100644
--- a/drivers/gpu/drm/i915/gt/intel_lrc.c
+++
PS I've been running on hwe 5.3 from Ubuntu's kernel git repository for
a few weeks, with the patch linked above, and it is stable on my
Thinkpad T480.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: nvidia-prime (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765888
Title:
Please revert to debian-alternatives based prime-select
If the power-saving patch is backported,will this be updated? I'm on own
patched kernel so I won't notice.
It's an awful problem, by the way, it harms battery life on any laptop with
intel graphics from 2016 or later.
--
You received this bug notification because you are a member of Ubuntu
logs not applicable
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- CVE-2019-0154 caused major power problem, pls backport maintainers fix
+ CVE-2019-0154 caused major power problem, pls backport maintainer's fix
** Summary changed:
- CVE-2019-0154
** Description changed:
https://gitlab.freedesktop.org/drm/intel/issues/614
the fix released as CVE-2019-0154 increases idle power consumption on intel
i915 6th gen and later.
- That's because the GPU does not enter RC6 any more.
+ That's because the GPU does not enter RC6 any more.
-
Public bug reported:
https://gitlab.freedesktop.org/drm/intel/issues/614
the fix released as CVE-2019-0154 increases idle power consumption on intel
i915 6th gen and later.
That's because the GPU does not enter RC6 any more.
For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3
You are correct. Thanks. I was so puzzled by this.
I am using KDE. Possibly the network manager interface is different. This is
what I did.
Imported the openvpn config file into networkmanger. It makes a connection, it
times out, and no amount of debugging gives any more hint.
I edit the
With my T480 and the 5.0 ubuntu kernel, and the 5.3 in the proposed PPA, two
finger scrolling does not work unless I specify psmouse.synaptics_intertouch=0
or =1
either value fixes it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to 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
--
A very similar thing just happened to me, with the 435 drivers via ppa.
Reverting to 430 solved it. Ubuntu 19.04, P50. USB mouse works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826597
Title:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714881
Title:
no gdm3 greeter with nvidia quadro and
>>> import dateutil.parser
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/dateutil/parser.py", line 40, in
from six import text_type, binary_type, integer_types
ModuleNotFoundError: No module named 'six'
--
You received this bug notification
I had the module python3-six installed but after I reinstalled it,
software-properties-gtk started working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830914
Title:
I have this problem in one Ubuntu 18.04
journalctl -e
Sep 06 17:54:28 ubuntu dbus-daemon[723]: [system] Activating service
name='com.ubuntu.SoftwareProperties' requested by ':1.106' (uid=1000 pid=6185
comm="/usr/bin/python3 /usr/bin/software-properties-gtk " label="unconfined")
(using
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 Ubuntu
> 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 Ubuntu
"gdm3 compile without wayland", I meant
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
nvidia-drm.modeset=1 results in no monitors detected by Xorg
To manage notifications about this
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
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
nvidia-drm.modeset=1 results in no
I will post your findings to the nvidia developers forum.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
nvidia-drm.modeset=1 results in no monitors detected by Xorg
To manage
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
This works. Thanks. What does gdm3 do that requires this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
gdm3, hybrid nvidia with modeset=1, no external monitors detected
To manage
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
kde neon: (ubuntu 18.04.2 with HWE stack)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt+KEY incorrectly behaves like Ctrl+Alt+KEY
To manage notifications about this bug go to:
Thanks Olivier, I changed my mount point (under /media) and it's
working fine now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820543
Title:
[snap] libreoffice can not see mounted volume under
Yep. I didn't find that, I filed a new Ubuntu kernel bug which I will now
close.
On Tue, 19 Mar. 2019, 16:05 Kai-Heng Feng,
wrote:
> LP: #1812099?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1820796
>
> Title:
>
already fixed (see https://lists.ubuntu.com/archives/cosmic-
changes/2019-March/012430.html)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820796
Title:
natacpi bug in 4.18.0-16-generic, fixed
The external monitor problem is probably a well-known gdm3 bug: gdm3
with nvidia modeset=1 stops the nvidia driver from detecting external
monitors (possibly it invokes some wayland features when it shouldn't).
It is not a problem with nvidia-prime or with the kernel. You can fix it
by using
1 - 100 of 364 matches
Mail list logo
