@ecanepa: it does seem like 6.15.0-061500-generic behaves better (the
rc4 kernel had issues w/ snapd taking 100% cpu so didn't stay on it very
long -- i've been on 6.15.0 for about a week without seeing the
bluetooth-hid issue yet)
--
You received this bug notification because you are a member of
fwiw happens in chrome as well as firefox. seems to work somewhat
better under google meet than under zoom but not sure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2109368
Title:
Sharing screen t
right before rebooting (ie was still on the same 6.14.0-13 kernel
version), tested this a few more times and the mouse was immediately
recognized upon connection. not sure what cleaned it up or triggered it
in the first place.
am now running with 6.15.0-061500rc4-generic and seeing the same
immed
Public bug reported:
When I connect my bluetooth mouse, the bluetooth indicator shows a
connection immediately, but the mouse is not responsive for another
10-15 seconds, at which point journalctl shows the following (it doesn't
show anything when the bluetooth connection is established):
```
May
Public bug reported:
Joining a zoom meeting through the web browser (firefox on wayland) and
sharing screen appears to work. After a short time, however, the shared
content silently becomes a black box and other people on the call can no
longer see the screen. Nothing appears in journalctl outpu
Public bug reported:
upon updating to plucky, gnome-shell crashes in wayland very often -- it
appears a mouse move trigggers it in both the login shell and a user
session (although in user session it seems to be ok unless moving the
mouse while the overview is open?). Running in X11 appears to no
can confirm things appear to be working again in wayland (both gdm and
user session) after unsetting MUTTER_DEBUG_KMS_THREAD_TYPE per linked
upstream bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2
i do have files in /var/crash: _usr_bin_gnome-shell.1000.crash for the
gdm shell and _usr_bin_gnome-shell.123.crash for the user shell, what's
the best way to add them here? ubuntu-bug /var/crash/... doesn't appear
to do anything?
--
You received this bug notification because you are a member of
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2104183/+attachment/5867286/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3977
https://gitlab.gnome.org/GNOME/mutter/-/issues/3977
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3977
Importance: Unknown
Status: Unknown
--
You received this bug notification beca
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2104183/+attachment/5867284/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104183
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/2104183/+attachment/5867280/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2104183/+attachment/5867281/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/2104183/+attachment/5867282/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104183
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/2104183/+attachment/5867288/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104183
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/2104183/+attachment/5867287/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104183
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/2104183/+attachment/5867285/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/2104183/+attachment/5867283/+files/monitors.xml.txt
** Description changed:
upon updating to plucky, gnome-shell crashes in wayland very often -- it
appears a mouse move trigggers it in both the lo
apport information
** Tags added: apport-collected
** Description changed:
upon updating to plucky, gnome-shell crashes in wayland very often -- it
appears a mouse move trigggers it in both the login shell and a user
session (although in user session it seems to be ok unless moving the
m
see also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2087687 --
but haven't actually gotten anywhere there either
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2042043
Title:
system boot fr
@juergh, anything in those logs of interest? any further way suggested
to grab logs for the case when the system locks up (I assume they can't
persist anywhere since the disk is still encrypted?)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
bluez 5.78 appears to resolve this for me (at least symptom wise,
haven't checked the first attempt logs since didn't notice any bad
behavior). is the fix cherry picked in
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084337 the same
thing? haven't tried downgrading to that package version
also the more I look at it the more the lock seems associated with the
speed in which I type the password rather than the waiting time I
mentioned earlier. but maybe both contribute?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
/var/log/kern.log trimmed from start of boot
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2087687/+attachment/5839541/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Yes, bios is up to date. Things used to work, and regressed toward the
end of october last year, probably after 23.10 release, but not
immediately after upgrading to mantic ( see original untriaged bug here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042043 )
Will reboot later today an
@juergh thanks, I do generally have a USB hub plugged in, but have the
issue whether it is plugged in or not. Attaching a USB keyboard still
does not unfreeze the ability to type the password.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
@mruffell (or anyone else): are there other steps (kernel boot args
maybe?) you'd recommend to try to get more info?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2087687
Title:
system boot freeze
After pressing escape, I see an "enter your password to unlock nvme
crypt:" type prompt at the top of the screen. If I start typing each
key I press puts a space character / moves the cursor one character to
the right. If I type fast enough (ie, at a reasonable speed), the
cursor stops moving and
Public bug reported:
Filed this about a year ago as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042043 but never
got triaged. Still seeing this on up to date oracular system. Advice
in #ubuntu was to file a new bug
At the luks/crypt password entry screen, I am only able to type about
still seeing this in oracular, any advice on how to debug / fix ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2042043
Title:
system boot freeze while typing crypt password
To manage notifications
Public bug reported:
Since upgrading to 24.10, my bluetooth headphones often fail to connect
until I remove them and re-pair. More specifically, they connect for a
second or two and then immediately disconnect. Seems to happen more
when I switch them to connect to a different device and come bac
this might be a dup of
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2081384 //
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084337 apologies
if so
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
it does appear that `mplayer tv:// -tv driver=v4l2:device=/dev/video2`
doesn't have this problem, while the gst-launch command above does, so
adding gst plugins package that includes the v4l2 src
** Also affects: gst-plugins-good1.0 (Ubuntu)
Importance: Undecided
Status: New
--
You rec
can reproduce this without opencv using:
gst-launch-1.0 v4l2src device="/dev/video2" ! videoconvert ! ximagesink
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: opencv (Ubuntu)
--
You received this bug notification because you are a member of U
Public bug reported:
since upgrading to noble, sometimes the following bit of code works
instantaneously, and sometimes it takes ~5 seconds to report:
** (gst-plugin-scanner:692358): CRITICAL **: 10:55:31.508:
_dma_fmt_to_dma_drm_fmts: assertion 'fmt != GST_VIDEO_FORMAT_UNKNOWN'
failed
code:
>>
yes you circled the right ones! sorry for not having a better example
but was trying to quickly reproduce without leaking internal info that
most of my long command line history entries have
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
not a great example but the white dots in this picture blink in an out
with the cursor blink. yes, fractional scaling is enabled @ 175%
** Attachment added: "PXL_20240424_153154820.MP.jpg"
https://bugs.launchpad.net/ubuntu/+source/gnome-console/+bug/2063270/+attachment/5770070/+files/PXL_2024
Public bug reported:
in noble, gnome-console fonts show slight corruption and artifacts,
especially between consecutive lines. gnome-terminal doesn't appear to
have the same.
trying to take screenshots "cleans up" the artifacts
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-con
Public bug reported:
Running snapshot, I get a UI error message "could not play camera
stream", a black window, and the following log messages:
2024-04-12T16:32:17.738325Z INFO snapshot::application::imp: Snapshot
(org.gnome.Snapshot)
2024-04-12T16:32:17.738340Z INFO snapshot::application:
Public bug reported:
Occasionally after unlocking a locked gnome session, the image on my
external monitor is "frozen" -- it displays the unlocked desktop as of
the lock/unlock time, but does not update (no mouse cursor etc).
Started noticing this post-jammy release.
Unplugging and replugging the
any plans to address this in jammy? haven't had any movement on the
upstream bug so I assume reverting that one commit is probably the best
option?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/195862
is there a way for users to re-enable wayland / override the
DISABLE_WAYLAND=1 setting recently set in the snap?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964541
Title:
Cannot use Drag and Drop
https://public-inbox.org/git/YYFEE%2F2g3SiM04zx@hades.panopticon/ --
seems this is working as desired and I should remove ff=only from my
config
** Changed in: git (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Public bug reported:
I have pull.rebase=true and pull.ff=only set up in my global git config:
```
[pull]
ff = only
rebase = true
```
however in jammy, when I git pull with a local commit, I get the following
error:
```
fatal: Not possible to fast-forward, aborting.
```
doing a
also fwiw, confirmed that starting from tag Ubuntu-5.15.0-25.25 (commit
f4a9abe17854fc753c84a0ba4ac275e715a008f3), reverting commit
6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0 applies cleanly and fixes the
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
found some other reports that claim i915.fastboot=0 is a workaround, and
can confirm it does work around the issue on jammy's current 5.15
kernel.
https://www.reddit.com/r/pop_os/comments/scqr4n/dell_xps_15_9575_screen_flickering_upon_boot/
https://bugs.archlinux.org/task/72134
https://gitlab.free
** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #5534
https://gitlab.freedesktop.org/drm/intel/-/issues/5534
** Also affects: linux via
https://gitlab.freedesktop.org/drm/intel/-/issues/5534
Importance: Unknown
Status: Unknown
--
You received this bug notification b
If I didn't get my good/bad confused on the reverse bisection, this
appears to be the commit that fixes it:
5ac860cc52540df8bca27e0bb25b6744df67e8f0 is the first bad commit
commit 5ac860cc52540df8bca27e0bb25b6744df67e8f0
Author: Ville Syrjälä
Date: Thu Mar 3 21:12:06 2022 +0200
drm/i915: F
seeing the same behavior with the -non-free version too, does it need a
separate rebuild?
** Also affects: intel-media-driver-non-free (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
appears to be fixed in drm-tip 2022-03-29 packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958620
Title:
[Dell XPS 15 9575] Flickering white/black screen once KMS comes up
To manage notifica
Yeah I was confused that the built kernel versions were in the v5.13-rc
range, but according to `git tag --contains
6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0` (and the list of tags in
https://github.com/torvalds/linux/commit/6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0)
v5.14-rc1 is the first tag that h
after bisection:
6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0 is the first bad commit
commit 6d7a793aabf31d7ba2b16fc13a94ccf0b90e4be0
Author: José Roberto de Souza
Date: Fri May 14 16:22:45 2021 -0700
drm/i915/display: Allow fastsets when DP_SDP_VSC infoframe do not match
with PSR enabled
Public bug reported:
After upgrade to jammy, noticed that the gnome session locks the screen
when I unplug an external screen.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generi
Was the Precision 5530 2-in-1 version of this machine ever certified?
don't know if it would have the exact same issue but its the same
chipset.
In the meantime I'm attempting to bisect the mainline kernel to find the
commit that broke this.
--
You received this bug notification because you are
based on previous comment no longer testing with i915.enable_psr=0, but
here's what i've narrowed it down to:
v5.13.19: works
v5.14.0rc2: black screen
looks like the v5.14.0rc1 build failed so can't test that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
v5.14: black screen
v5.13: black screen with i915.enable_psr=0, works without
went back and tried the initial 5.13.0-35 as well, and it also does the
black screen with i915.enable_psr=0
will try to find the first mainline 5.13 that doesn't work today (or if they
all work).
--
You received thi
both of those exhibit the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965968
Title:
post jammy update, black/flickering screen on boot
To manage notifications about this bug go to:
https://
i915.enable_psr=0 did not fix the black screen issue, but did appear to
remove the flickering purple streaks, fwiw.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965968
Title:
post jammy update, bl
kernel parameter intel_idle.max_cstate=4 does not help.
Things do work properly if I boot with the external display plugged in
to begin with.
It does appear that blindly typing the encrypted disk password still
"works" and gdm does end up starting behind the black screen, but the
display does not
Public bug reported:
After initial jammy upgrade things were working fine, but after a recent
update the machine boots to a blank screen. There are occasional
purplish flickers that seem to correspond with keypresses, but even
blindly typing the encrypted disk password doesn't appear to advance t
One more piece of information in a wayland session: If I fully fold the
device into tablet mode, then I can rotate back and forth successfully,
it only gets stuck if I go back into laptop mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I had pipewire-media-session libpipewire-0.3-common installed fine after
an upgrade from impish->jammy, but still had to remove the
libgstpipewire so, and reinstall the package to get gstreamer to
recognize the pipewiresrc element
--
You received this bug notification because you are a member of
The bug does not appear to occur under Xorg sessions:
- Ubuntu on Xorg: rotated back and forth numerous times successfully
- Ubuntu: rotated back and forth once successfully and then got stuck in
portrait mode
- Gnome on Xorg: rotated back and forth numerous times successfully
- Gnome: rotate
I do occasionally get crashes when attempting to rearrange tabs as well.
The crashes happen both in .deb & snap versions of firefox though?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964541
Title:
Public bug reported:
While upgrading from impish->jammy, the screen went black and nothing
could wake it up. Hard reset brought up a half-upgraded system that gdm
couldn't start on, booting to text console and finishing upgrade via apt
(combination of `--fix-broken install` and `full-upgrade`) br
seems like pulse was fighting with pipewire; not sure what I did to
clean it up but appears to be working better now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965647
Title:
pulseaudio gets stuc
Public bug reported:
In jammy I can get mutter's auto-rotate to switch to portrait mode
("right-up") by rotating the device (this only worked in impish if I
installed the autorotate gnome-shell extension).
However, putting it back into "normal" orientation doesn't put the
screen back in landscape
Public bug reported:
after updating to jammy, pulseaudio appears to get stuck after opening
firefox.
I can play an audio file using mplayer fine, then I open firefox (either snap
or deb version), then it fails to play the same audio file and prints out
"Audio device got stuck!"
killing pulseaud
Public bug reported:
After upgrading from impish to jammy, seeing the following behavior in
firefox when trying to reorder tabs by clicking and dragging them:
1) in the .deb firefox, firefox will crash most of the time, but
sometimes reorder successfully
2) in the snap firefox, firefox will not
*** This bug is a duplicate of bug 1945100 ***
https://bugs.launchpad.net/bugs/1945100
Public bug reported:
Watching Widevine content (eg netflix, hbomax, etc) on the .deb package
of firefox in impish has recently stopped working. Get a "The
WidevineCdm plugin has crashed" message at the top
Public bug reported:
since upgrading to firefox 90, all newly opened firefox windows are very
small and need to be manually resized to a usable size.
prior to firefox 90, new windows would be the same size as the last
opened window.
running on gnome on wayland with fractional scaling enabled, if
ok that makes sense, I think opening links from slack (electron/x11) was
likely the culprit that "poisoned" the running firefox instance
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921931
Title:
Thanks Olivier. That bug report looks related but seems more like it
never works, vs/ works for a little while and then stops working? But
adding the MOZ_DBUS_REMOTE flag that it mentions seems to fix the issue
when running with MOZ_ENABLE_WAYLAND in limited testing so far.
--
You received this
Yes, commenting out the MOZ_ENABLE_WAYLAND line appears to fix the
issue. With MOZ_ENABLE_WAYLAND=1, initial link requests work, but after
a short while start getting the firefox is running but not responding
dialog. Without it, link requests work even after a while.
** Changed in: firefox (Ubun
Public bug reported:
Since the latest package release enabling wayland, I often get the
"Firefox is already running, but is not responding. To use Firefox, you
must first close the existing Firefox process, restart your device, or
use a different profile." message when trying to open links from ot
Public bug reported:
Upgrading from groovy to hirsuite, base-passwd asks if the `irc` user's
home directory should be moved from `/var/run/ircd` to `/run/ircd`.
Having no IRC server installed makes this very confusing, but appears
harmless (https://askubuntu.com/questions/876975/user-irc-inside-of
seems to have fixed itself somehow.
** Changed in: geary (Ubuntu)
Status: New => Invalid
** Changed in: webkit2gtk (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Public bug reported:
Recently in groovy, using the mouse scroll wheel while hovering over a
message in geary stopped scrolling the message. hovering over the
header or the scrollbar still works. possibly related to webkit2gtk
update?
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: geary 3.
Public bug reported:
Per https://wiki.archlinux.org/index.php/PipeWire#WebRTC_screen_sharing,
it appears that chrome/chromium need pipewire 0.2 userspace libraries
installed for pipewire based screen sharing to work. (Verified that it
doesn't appear to work with manually compiled, pipewire enable
Public bug reported:
In a wayland session with fractional scaling (175% on laptop screen),
seeing weird visual artifacts around windows when moving them around,
see attached video for an example. Also see similar artifacts near
terminal prompt, gtk file chooser when mousing over items, and maybe
acpidump on latest (1.13.0) firmware.
** Attachment added: "1.13.0.acpidump"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+attachment/5415405/+files/1.13.0.acpidump
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
1.2.0 firmware acpidump attached
** Attachment added: "1.2.0.acpidump"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+attachment/5415318/+files/1.2.0.acpidump
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues #126
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/126
** Also affects: gnome-online-accounts via
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/126
Importance: Unknown
Status:
Public bug reported:
Trying to add a google account that redirects to another site for sign
in results in a window with the following error:
{"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
an invalid header value that can't be parsed."}]}
ProblemType: Bug
DistroRelease: Ub
Public bug reported:
Per https://github.com/FedoraQt/adwaita-qt/issues/128, the Adwaita-Dark
QT theme doesn't work great with virtualbox. Including the patch from
https://github.com/FedoraQt/adwaita-
qt/commit/d1e76197e5db24b6d1d286c6e73439d4b1a0500a appears to fix it.
ProblemType: Bug
DistroRel
fwiw, here's gdb backtrace when seeing this bug:
(gdb) bt
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x77d74483 in g_cond_wait ()
at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x77d50b0f in g_once_init_enter ()
at /lib/x86_64-linux-gnu/libglib-2.0.
Interesting that I didn't see this in eoan, but did once upgrading to
focal. appears the "Highlight current line" option default changed to
true maybe?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
Public bug reported:
In focal, with a dark theme (adwaita-dark), the current line highlight
in almost the same color as the text, making it very hard to read. see
screenshot.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gedit 3.36.0-3
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.
Looks like already reported, linked to existing bug
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2239
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2239
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2239
Importance: Unknown
verified fixed with proposed kernel on dell xps15 2-in-1.
Device: Mesa Intel(R) HD Graphics 630 (KBL GT2) (0x591b)
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
The new lock screen in gnome 3.36 looks strange, as if the blurred
background image is being scaled down to the top left corner of the
screen. background image being used is 1920x1440 pixel jpeg, display
size is 3840x2160, with fractional scaling enabled and set to 175% on
wa
appears to be fixed in focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845387
Title:
boot splash shows green underline under logo
To manage notifications about this bug go to:
https://bugs.lau
** Changed in: linux (Ubuntu)
Status: Fix Committed => 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/1844962
Title:
apparent memory usage regression - not getting freed?
To mana
confirmed fixed in 5.3.0-24.26
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844962
Title:
apparent memory usage regression
3.34.1+git20191107-1ubuntu1~19.10.1 appears to fix the issue here.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848119
added to the 5.3-stable tree:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-
queue.git/tree/queue-5.3/drm-amdgpu-user-pages-array-memory-leak-
fix.patch
can this get into the next ubuntu kernel as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs
Have seen it both with the internal laptop keyboard as well as an
external USB keyboard
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848086
Title:
Keyboard shortcuts to launch apps sometimes launc
Initial testing does make it look like an Xorg session behaves better in
this regard than a wayland session (using vanilla gnome sessions in
both, fwiw)
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You re
fwiw, with a 5.3 kernel on eoan and a system-sleep script that does
`btmgmt power off` pre sleep, and `btmgmt power on` post sleep, I
haven't been seeing the lock up issue.
just an occasional instant wake from suspend with the system usable
after that, and able to successfully suspend with another
** Tags added: patch-accepted-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844962
Title:
apparent memory usage regression - not getting freed?
To manage notifications about this bug go t
1 - 100 of 676 matches
Mail list logo
