Public bug reported:
When using Chromium (snap) on Wayland (gnome-session), if I keep two
windows open on different workspaces, sometimes the current tab becomes
unusable as it freezes or is super-slow.
This usually happens with specific pages open, like youtube, mattermost,
google drive.
If I use the builtin settings app to change output it doesn't creash,
but it also doesn't seem to be doing anything. Output output keeps going
through BT headset even if I switch to something else.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug
Hi, this is the link to the uploaded oops:
https://errors.ubuntu.com/oops/f9043ff6-1530-11eb-bd53-fa163ee63de6
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
When switching from the builtin output on laptop to HDMI output the
session crashes and restarts
dmesg shows the following error:
[21562.487136] gnome-shell[35176]: segfault at 94 ip 7ff455106daf
sp 7ffce9718ec0 error 6 in
I can confirm the issue with 3.36.3-0ubuntu0.20.04.1 too
--
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/1880739
Title:
Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1
To
after a reboot it's back to working
** Changed in: gnome-session (Ubuntu)
Status: New => Invalid
--
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/1878472
Title:
Public bug reported:
After latest gnome-related updates, nightlight is no longer working.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-session 3.36.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs
Public bug reported:
The volume icon and sound output slider doesn't show up in the top-right
menu in Focal Gnome.
Also, changing the volume with mouse wheel while on the menu doesn't
work anymore.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.35.91-1ubuntu2
Is the fig going to be backported to Eoan?
--
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/1847551
Title:
Mutter 3.34.1 broke Night Light, screen color profiles in Wayland
@Daniel, yes, even disabling all extensions I still have the issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1805257
Title:
gnome apps provided by snaps show default
Public bug reported:
On 18.10 with GNOME session and default Adwaita icon theme, desktop apps
installed via snap, like gnome-calculator, gnome-system-monitor, ... all
have the default executable icon (diamond with gears), instead of their
own icons.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
I just had a series of freezes, and managed to ssh and watch logs in the
meantime, the only messages that I that might be relevant are the
following (repeated many times):
May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap:
assertion 'SHELL_IS_EMBEDDED_WINDOW (window)'
Daniel, not sure if they're related, but it seems that when I get back
from the "slide" screen (even if not locked) I'm getting a lot of these
errors repeated in journalctl:
May 24 14:52:47 kashyyyk gnome-shell[6901]: Object Meta.Background
(0x562f8156e590), has been already deallocated -
I only see apparmor audit messages there
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1769981
Title:
Temporary screen freeze when coming back from screen standby
To manage
No, I've never seen any message in log that could seem related to the
issue.
Yes there are two cases here, although related. I experience these
freezes when coming out of screen standby, which sometime are longer and
end up with a session crash, but in many case they just freeze the UI
and send
The last crash is https://errors.ubuntu.com/oops/93aef40e-5deb-11e8
-945f-fa163e8d4bab
There are a few previous chrashes with the same syntomps:
https://errors.ubuntu.com/oops/c9e22fbe-58dc-11e8-9127-fa163ed44aae
https://errors.ubuntu.com/oops/385a60b4-334f-11e8-a211-fa163ef911dc
>From the list on that page I can see that a report was indeed uploaded
for that crash:
2018-05-22 20:052018-05-22 18:05 UTCCrash xwayland
Unfortunately if I click on the link, I get an error saying that I'm not
allowed to see crash reports. Is it ok for me to share the link to
@Daniel I followed the steps there (specifically, enabling crashes for X). I
just got a freeze with subsequent crash and got a new Xwayland .crash file.
Still, running ubuntu-bug on it it just exits with no error when I click to
submit, and it doesn't seem to be submitting the bug.
What steps
That link mentions how to create a crash file, but I do have one, I just
can't upload it via ubuntu-bug
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1769981
Title:
Temporary
Yes I have a Xwayland crash file in /var/crash with the same timestamp.
I tried running ubuntu-bug on it, but after I confirm the popup message,
it just exits without any error and it doesn't pop up a launchpad
window.
--
You received this bug notification because you are a member of Ubuntu
Thanks Daniel,
the core file I got from the crash (in my home dir) shows as
core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style,
from '/usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4
-listen 5 -d', real uid: 1000, effective uid: 1000, real gid: 1000,
effective
@Daniel, I just got a session crash because of this freeze and got an Xwayland
core file in my home.
Should I open a different bug? How do I attach the core through apport?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell
FTR this also happens on another PC, also with Intel card (different
model), also a fresh Bionic install
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1769981
Title:
Public bug reported:
When waking up the PC screen from standby, quite often the screen freezes for
10-20s.
I can't move the mouse or type anything. After a while, it unfreezes.
This is quite annoying because often the freeze is long enough to send the
screen to standby again for absence of
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
@Daniel
I see #1748450 is marked as fix released now, but I still see this behavior
(including Xwayland core dumps in my home) with latest bionic packages.
Should I open a new bug or unduplicate this one?
I just reproduced a crash, uploaded the crash files to
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759849 and
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1759850
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
I haven't seen any crash after latest updates, but I still have the
issue with screen freezing when coming out of the lock/blank screen.
Is there anything else I can do to track down the issue?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
When tailing /var/log/syslog, I see the following errors every time I
switch between windows with alt-tab.
Mar 28 12:24:51 kashyyyk gnome-shell[3164]: Object Shell.GenericContainer
(0x558047013e00), has been already finalized. Impossible to get any property
from it.
Mar 28
After leaving my PC alone for a few minutes I found it at the login
window and the session crashed.
Attached is the crash log
** Attachment added: "_usr_bin_Xwayland.1000.crash"
After leaving my PC alone for a few minutes I found it at the login
window and the session crashed.
Attached is the crash log. If it can be useful, I also have a 145Mb
Xwayland core dump from the same crash
** Attachment added: "_usr_bin_Xwayland.1000.crash"
Not when the system freezes for some time as described above. I'll see
if I get a crashdump when the session actually crashes
--
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/1756092
This seems to have gotten worse after latest updates. Now if I leave the
PC for a while and the screen blanks, when I get and wake up the screen,
I find the login screen (and the previous session has creashed).
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
** Attachment added: "journalctl.log.gz"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+attachment/5088004/+files/journalctl.log.gz
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Uploaded the dmesg and journalctl log as requested
--
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/1756092
Title:
Screen freeze for some time when unlocking
To manage notifications
** Attachment added: "kernel.log"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+attachment/5087994/+files/kernel.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
I attached the previous dmesg without apparmor errors (although I don't
see much useful in there)
** Attachment added: "kernel.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+attachment/5087121/+files/kernel.txt
--
You received this bug notification because you are a
Attached a dmesg right after the issue occurred
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+attachment/5086281/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in
Done. Is there any more info I can provide on the original machine?
--
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/1756092
Title:
Screen freeze for some time when unlocking
To
Yes, the latter attachments are from my laptop, which shows the same issue.
Note that the issue happens on resume from screen standby, not resume from
machine standby
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
When trying to unlock the machine, sometimes the screen freezes entirely
(including mouse and keyboard input) for a long time either right away or after
submitting the password.
The freeze lasts for 10-20s, and
Daniel,
I'll take a look at what that device is (I don't have access to that
computer today) but it's not a printer.
But as said, this behavior also happens on my laptop (also a fresh
bionic install). I've attached log from it right after the issue
occurred.
** Changed in: gdm3 (Ubuntu)
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1756092/+attachment/5083754/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1756092/+attachment/5083755/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1756092/+attachment/5083756/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
To clarify, this happens even if the password lock hasn't kicked in yet
but the display went into standby
--
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/1756092
Title:
Screen freeze
Public bug reported:
When trying to unlock the machine, sometimes the screen freezes entirely
(including mouse and keyboard input) for a long time either right away or after
submitting the password.
The freeze lasts for 10-20s, and sometimes the display goes into suspend.
I've seen this
@Daniel no, the whole system freezes, even if I ssh before the UI starts
(which requires exact timing), then the machine freezes.
--
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/1697450
@Daniel I can't really follow those steps exactly, as the machine hangs
as soon as either GDM or gnome-shell is started
--
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/1697450
Title:
I'm still seeing a similar issue with daily images of Bionic.
At boot, the machine hangs at splash screen.
If I boot without "splash quiet", I can see the last message is about starting
login session.
I'm not sure this is actually a duplicate of #1505409.
How can I help fixing this? It makes it
To test the issue, I booted in text mode (multi-user.target), logged in
and then started gnome-shell.
Nothing happens (the session doesn't start and the console seems hang).
Via ssh, I ran the killall, saved the .crash file and uploaded to the
following bug:
FTR this still happens with gnome-shell 3.26.1-0ubuntu4 and kernel
4.13.0-16-generic
--
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/1697450
Title:
Gnome Shell hangs at startup
To
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1697450/+attachment/4966437/+files/ProcEnviron.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop
apport information
** Tags added: apport-collected wayland-session
** Description changed:
I'm trying to install from the daily Artful desktop image (20170612).
After boot, the gnome session hangs at startup, while the "zoom"
animation is being shown.
I have an intel card:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1697450/+attachment/4966436/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1697450/+attachment/4966435/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Is there any way I could debug the issue with 4.13?
--
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/1697450
Title:
Gnome Shell hangs at startup
To manage notifications about this bug
If I run gnome-shell from the terminal with the latest (4.13.0-12.13)
kernel, the system freezes.
Running apport-collect while running the 4.8 kernel segfaults:
$ sudo apport-collect 1697450
Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect:
Connection refused
Invalid
** Tags added: gnome-17.10
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1697450
Title:
Gnome Shell hangs at startup
To manage notifications about this bug go to:
** Summary changed:
- Gnome Shell hangs at login, while the "zoom" animation is being shown
+ Gnome Shell hangs at startup
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1697450
As an additional info, running artful on the 4.8.0-59-generic kernel
from yakkety seem to work fine.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1697450
Title:
Gnome Shell
I can confirm this is a gnome-shell bug.
I tried booting with multi-user.target and manually starting gnome-
shell, it hangs right after showing the mouse pointer on the console
screen.
I also tried starting weston manually, which works fine.
** Also affects: gnome-shell (Ubuntu)
Importance:
Public bug reported:
On Artful, I disabled the ubuntu-dock extension using the gnome tweak tool.
The dock is still there.
I'm not sure if this is a duplicate of #1712698
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell-extension-ubuntu-dock 0.4
ProcVersionSignature: Ubuntu
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1697450
Title:
Installer freezes at session startup
To manage
Public bug reported:
The "SMART Data & Self-Tests" menu entry is always disabled on Yakkety
for internal hard drives.
See attached screenshot.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnome-disk-utility 3.22.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname:
Public bug reported:
On a fresh Ubuntu 16.10 (yakkety) install, resolution of mDNS hosts
doesn't work anymore (it used to in xenial)
I can resolve names with avahi-resolve but ssh,ping,etc. fail to
resolve.
After some digging I found out that what's causing it is the "resolve"
option in
I have the same problem on a Dell D830, Intel graphics, on Oneiric.
The brightness when returning from screensaver is at minimum
(xbrightness shows level 0), brightness keys work and so does
xbrightness -set 100.
Brightness control worked fine for me on Natty.
--
You received this bug
I have the same problem with the attached pdf on Jaunty:
$ apt-cache policy evince
evince:
Installed: 2.26.1-0ubuntu1
Candidate: 2.26.1-0ubuntu1
Version table:
*** 2.26.1-0ubuntu1 0
500 http://it.archive.ubuntu.com jaunty-updates/main Packages
100 /var/lib/dpkg/status
I have the same behaviuor on Ubuntu 8.10 x86_64.
Setting Multimedia player to a different one doesn't work.
Other settings, terminal emulator for instance, work as expected.
--
Preferred applications doesn't work
https://bugs.launchpad.net/bugs/301040
You received this bug notification because
69 matches
Mail list logo
