https://salsa.debian.org/gnome-team/gnome-shell/-/commits/ubuntu/master
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Changed in: mutter (Ubuntu)
Status: Triaged => Fix Committed
--
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/1862081
Title:
Gnome resizes framebuffer when playing
Please wait until the problem happens again and then collect a fresh
system log:
journalctl -b0 > journal.txt
or if you had to reboot after it happened run:
journalctl -b-1 > prevboot.txt
and then attach the resulting file here. Please also follow the
instructions in comment #3.
**
Oh, actually this might be a mutter bug or even a kernel bug related to
this:
https://gitlab.gnome.org/GNOME/mutter/-/issues/182
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #182
https://gitlab.gnome.org/GNOME/mutter/-/issues/182
** Changed in: mutter (Ubuntu)
Status:
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Invalid
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided => Low
--
You received this bug
I think it is possible. Please try:
Settings >
Language and Region >
Manage Installed Languages >
Apply System-Wide (Use the same language choices for startup and the login
screen)
** Package changed: gdm (Ubuntu) => gnome-shell (Ubuntu)
** Package changed: gnome-shell (Ubuntu) => ubuntu
**
No disabling extensions is not enough because we have found that a
disabled buggy extension can still interfere with gnome-shell.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Tracking upstream in: https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/2541
** Summary changed:
- gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
+ gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from
_st_set_text_from_style()
** Bug watch added:
*** This bug is a duplicate of bug 1868440 ***
https://bugs.launchpad.net/bugs/1868440
** This bug has been marked a duplicate of bug 1868440
gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1868660 ***
https://bugs.launchpad.net/bugs/1868660
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1868660, so it is being marked as such. Please
** Tags removed: rls-ff-incoming
** Tags added: rls-ff-tracking
--
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/1869905
Title:
OnlyShowIn and NotShowIn not properly honored
To
** Tags removed: rls-ff-incoming
** Tags added: rls-ff-tracking
--
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/1862081
Title:
Gnome resizes framebuffer when playing fullscreen
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870975/+attachment/5349980/+files/journalctl.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
Yes, @juliank ! I am also suspecting gTile as the culprit for the
crashes. I haven't had enough time to make sure thought.
The bug I reported is: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1871063
Thank you for the link to the github issue!
--
You received this bug
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1871715
Title:
gnome-control-center crashed with SIGSEGV in
Might be related to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868440
--
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/1871063
Title:
gnome-shell crashed with
Oh, and I have no crash files in /var/crash/.
--
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/1871538
Title:
dbus timeout-ed during an upgrade, taking services down including
Hi, I had a similar crash this morning upgrading focal, after trying to
get unattended-upgrades to stop spinning on missing focal-security apt
list files. In this case, I don't use gnome-shell as my desktop
environment, but it still tore down my entire desktop environment and
caused gdm3 to
As you see in above image, additionally there is a sync issue between
g-c-c and snap-store about the permissions state.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
Same bug here, g-c-c 1:3.36.1-1ubuntu4. Image attached : control-center +
snap-store.
Really annoying if you don't use snap-store or gnome-software.
** Attachment added: "Capture d’écran de 2020-04-08 19-27-32.png"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
** Changed in: mutter (Ubuntu)
Status: Fix Committed => In Progress
--
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/1867757
Title:
Please pull Mutter cursor fixes for
No, I'm not using gTile. To Lock the screen and log in also works OK. My
gnome-shell crashes don't happen that often and I haven't found a way to
reproduce the crash.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
Ubuntu 18.04 using Wayland: The monitor connected to the AST2500 VGA has
no signal during and after login. "xrandr -q" shows both devices are
active. They are listed as XWAYLAND0 and XWAYLAND1. Ubuntu desktop's
"Display configuration" window shows both monitors are active. I can
move the
** Changed in: glib2.0 (Ubuntu)
Assignee: nassim (moujane) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344
Title:
print of __glib_assert_msg not
This bug was fixed in the package gnome-system-tools - 3.0.0-9ubuntu1
---
gnome-system-tools (3.0.0-9ubuntu1) focal; urgency=low
* Merge from Debian unstable (LP: #1871634). Remaining changes:
- debian/control: Recommend packagekit for Ubuntu patches
that allow installing
Public bug reported:
There are no translation files in the new version. The old version has
translation files.
In version for Ubuntu 18.04 no locale files. In Ubuntu 16.06 locale files
exists.
** Affects: empathy (Ubuntu)
Importance: Undecided
Status: New
--
You received this
Hey people, are you using gTile as well? This is what's causing the
crash for me (bug 1871684).
https://github.com/gTile/gTile/issues/124
** Bug watch added: github.com/gTile/gTile/issues #124
https://github.com/gTile/gTile/issues/124
--
You received this bug notification because you are a
** Package changed: nautilus (Ubuntu) => apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1871679
Title:
apt install libavcodec-extra asks for cdrom
To manage
Might be a duplicate of bug 1868440 aka
https://github.com/gTile/gTile/issues/124 - the bug goes away after
disabling gtile, however, gnome-shell automatic disablement of
extensions did not happen until after I logged out and back in again
(which also crashed).
Downgrading importance.
** Bug
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1871684/+attachment/5349824/+files/ThreadStacktrace.txt
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1871684/+attachment/5349799/+files/CoreDump.gz
** Tags removed: need-amd64-retrace
--
StacktraceTop:
st_theme_node_get_icon_style () from
/tmp/apport_sandbox_ua96zyca/usr/lib/gnome-shell/libst-1.0.so
st_texture_cache_load_gicon () from
/tmp/apport_sandbox_ua96zyca/usr/lib/gnome-shell/libst-1.0.so
st_icon_update () from
** Attachment added: "StacktraceSource.txt"
https://bugs.launchpad.net/bugs/1871684/+attachment/5349823/+files/StacktraceSource.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1871684/+attachment/5349822/+files/Stacktrace.txt
--
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/1871684
*** This bug is a security vulnerability ***
Public security bug reported:
Starting today, gnome-shell is crashing when you try to unlock the
screen. It then shows you your open windows (security?), and then it
restarts to the lock screen from where it will crash again if you move
mouse or press
The stack trace says it's crashing in st_theme_node_get_icon_style()
which is quite peculiar. Maybe it could be related to me running a GNOME
session, as opposed to an Ubuntu one?
I can log back in again only by switching to gdm tty, then waiting for
gdm to load, and logging back in there. Even
Public bug reported:
Whenever I talk in discord, the system log is spammed with the following
message and error:
discord1, Impossible to lookup icon for 'discord1_38-panel'
The error message that is logged:
JS ERROR: Exception in callback for signal: icon: Error: Argument 'filename'
(type
I fixed it by commenting out the first line of /etc/apt/sources.list*:
#deb cdrom:[Ubuntu 20.04 LTS _Focal Fossa_ - Beta amd64 (20200402)]/
focal main restricted
This fixes the apt bug and Netflix now also works in Firefox!
* As suggested in the Ubuntu Podcast Chatter Telegram channel.
--
You
Public bug reported:
Netflix does not work on Firefox on 20.04, even after enabling DRM. A
guide somewhere tells me I need libavcodec-extra, this reports:
```
$ sudo apt install libavcodec-extra
Reading package lists... Done
Building dependency tree
Reading state information... Done
The
Nevermind. I figured out that if I hover over the message text it is
hidden so I can see the file names.
** Changed in: nautilus (Ubuntu)
Status: New => Invalid
** Attachment removed: "Screenshot of issue"
** Changed in: mutter (Ubuntu)
Status: Incomplete => Confirmed
--
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/1871475
Title:
[amdgpu] Black screen after screen lock
To
Same applies for me. I assumed it was WPS office. But I noticed other
programs have it as well.
--
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
2020
GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level'
b"'standard'"
InstallationDate: Installed on 2020-04-08 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no us
** Changed in: gnome-system-tools (Ubuntu)
Assignee: Ross Gammon (rosco2) => (unassigned)
** Changed in: gnome-system-tools (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
Status: New => Confirmed
--
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:
While there is an accessibility menu on the login screen, there is no
way to set the keyboard layout at the login screen.
This is particularly annoying when an issue like bug 877371 occurs
or when multiple users with different layouts use the same device.
** Affects: gdm
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm (Ubuntu)
Status: New => Confirmed
--
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/877371
i got the same (though using azerty) on 20.04 today after an automatic
update
--
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/877371
Title:
keymap at login screen is set to qwerty
Public bug reported:
```
GNU Image Manipulation Program version 2.10.14
git-describe: GIMP_2_10_12-511-ga4f55d6c7e
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
Public bug reported:
The latest version of gnome-system-tools contains a patch to use yelp
instead of gnome-doc-utils which is not available in Ubuntu Focal.
** Affects: gnome-system-tools (Ubuntu)
Importance: Wishlist
Assignee: Ross Gammon (rosco2)
Status: In Progress
**
** Changed in: glib2.0 (Ubuntu)
Assignee: (unassigned) => nassim (moujane)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344
Title:
print of __glib_assert_msg not
*** This bug is a duplicate of bug 1857736 ***
https://bugs.launchpad.net/bugs/1857736
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1857736, so is being marked as such.
You have been subscribed to a public bug:
The latest version of gnome-system-tools contains a patch to use yelp
instead of gnome-doc-utils which is not available in Ubuntu Focal.
** Affects: gnome-system-tools (Ubuntu)
Importance: Wishlist
Assignee: Ross Gammon (rosco2)
The error messages “Import failed: Fatal: can't create directory
'/home/username/~/.gnupg': No such file or directory” and "Couldn't generate
PGP key" only come for me when trying to import or create a key from
LibreOffice Writer Version: 6.0.7.3, Build ID: 1:6.0.7-0ubuntu0.18.04.10
I am using
Public bug reported:
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OK, I get it.
I'm trying to investigate the crash, but I'm rather busy ATM.
You mentioned uninstalling all extensions would **disabling** them have
the same effect to trace the crash? (As you understand, it is much less
laborious than installing and uninstalling them)
Please, let me know if it
*** This bug is a duplicate of bug 1868440 ***
https://bugs.launchpad.net/bugs/1868440
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1868440, so is being marked as such.
*** This bug is a duplicate of bug 1871188 ***
https://bugs.launchpad.net/bugs/1871188
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1871188, so is being marked as such.
I did try logging out as well as restarting. After reboot I verified
the preferred-monitor setting was still set to the monitor I set it to
(which it is). But the Dock still persists on all three monitors.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Attachment added: "gsettings and Appearance settings"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1871358/+attachment/5349471/+files/ubuntu-dock-issue-2.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Uploaded in #1871580. Looking through gnome-shell issues, #1868440 looks
like it might also be the same thing.
--
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/1871580
Title:
Sorry I should have posted an additional comment yesterday. This is my
first Ubuntu bug posting.
I did try manually setting the preferred-monitor parameter:
gsettings set org.gnome.shell.extensions.dash-to-dock preferred-
monitor 1
Then I verified the setting was changed:
gsettings get
** Tags added: rls-ff-incoming
--
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/1869571
Title:
Vertical dual monitor setup with main monitor on bottom causes
overview to only
Same happening for me, with two rows of screens, three on top two in the bottom
row.
Primary is top left.
** Attachment added: "Screenshot_20200408_130437-search-bar-half-visible.png"
Overview of the affected layout
** Attachment added: "Screenshot_20200408_132041-layout.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571/+attachment/5349459/+files/Screenshot_20200408_132041-layout.png
--
You received this bug notification because you are a member of
could you use 'ubuntu-bug _usrcrash' to report the issue, adding the
dump to a comment like you did isn't really useful. If that's an
extension doing then it would be nice knowing which one but it's
probably not a gnome-session/shell issue at this point
--
You received this bug notification
*** This bug is a duplicate of bug 1869571 ***
https://bugs.launchpad.net/bugs/1869571
** Attachment added: "Screenshot_20200408_132041-layout.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871607/+attachment/5349457/+files/Screenshot_20200408_132041-layout.png
** This
*** This bug is a duplicate of bug 1869571 ***
https://bugs.launchpad.net/bugs/1869571
[13:14] cpaelzer, what screen resolution/scaling factor/video
card do you use?
That would be:
eDP-1 connected primary 1920x1080+0+840 (normal left inverted right x axis y
axis) 344mm x 193mm
DP-1
** Attachment added: "Screenshot_20200408_130437-search-bar-half-visible.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871607/+attachment/5349456/+files/Screenshot_20200408_130437-search-bar-half-visible.png
--
You received this bug notification because you are a member of
Deleting the old _usr_bin_gnome-shell.1000.crash and collecting a fresh
one.
However, a quick bit of experimentation appears to show that this crash
only occurs with extensions enabled - after globally disabling
extensions it appears to no longer occur. I haven't bisected extensions
individually,
Public bug reported:
Hi,
since the upgrade to Focal I wonder why the "activities" overview isn't
readable anymore.
It is the one you get to when you click "activities" in the top let or hit the
"meta" key.
In my case this preview is only half an icon high, so I have to assume
what things are
Lots of repetitions of:
```
ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: called for pid 7223, signal
11, core limit 0, dump mode 1
ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: executable:
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pid 7294) Wed Apr 8
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1412
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1412
** Changed in: nautilus (Ubuntu)
Assignee: (unassigned) => Cristiano Nunes (cfgnunes)
** Changed in: nautilus (Ubuntu)
Status: Triaged => Fix Committed
**
Thanks, that makes more sense, now why is apport not catching that one?
Could you look if there is something registered in /var/log/apport.log?
does it makes a difference if you
$ sudo service apport start force_start=1
then trigger the issue and see if apport picks the problem
--
You received
Session lock invoked manually (~11:00:00), lock screen displays, click
mouse to get unlock.
Screen freezes for ~10 seconds, then blanks briefly and shows login
screen.
Looks like gnome-shell crashing at about 11:00:26 - interesting lines:
Apr 08 11:00:26 kallisti gnome-shell[23758]:
I confirm that the problem also exists with "Ubuntu on Wayland". The
screen gets black after screen lock everytime.
--
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/1871475
Title:
Sure @seb128 - I'll let you know if it happens again (as I did a
cleaning-reboot now).
--
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/1871538
Title:
dbus timeout-ed during an
** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #372
https://gitlab.gnome.org/GNOME/gdm/-/issues/372
** Changed in: gdm
Status: New => Unknown
** Changed in: gdm
Remote watch: gitlab.gnome.org/GNOME/gdm/issues #195 =>
gitlab.gnome.org/GNOME/gdm/-/issues #372
--
You received
@Christian, dbus got reloaded a bunch of time during the upgrade according to
the log, that's expected, what isn't is that it stopped responding.
I haven't seen other reports from that so far so it's probably an uncommon
bug/issue hit there, I'm unsure how to debug it, especially after facts...
@Daniel, that doesn't look like this bug, from the journal
Apr 08 06:09:19 Keschdeichel systemd[1]: We couldn't coldplug
machine-qemu\x2d2\x2df\x2dnvidia.scope, proceedin
g anyway: Connection timed out
Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected
error response
Bug 1843982 is specifically about gnome-shell (and gdm) crashing when
accountsservice gets restarted, which is what you mentioned at the top
of this bug. So even if you are experiencing multiple bugs, I think
that's the one that matches the main bug report here.
--
You received this bug
Thank you for your bug report. Could you do
$ pacmd list-sources > dbg
and add the 'dbg' file to the bug?
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
--
You received this bug
This looks strongly like bug 1843982. If you disagree and still want a
more thorough analysis then please proceed to step 2 in comment #6.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
In that case please reproduce the problem and then immediately run:
journalctl -b0 > journal.txt
and send us the resulting file.
If you have to reboot before you are able to run journalctl then please
run:
journalctl -b-1 > prevjournal.txt
instead.
--
You received this bug notification
> could you add the journalctl log from that session, that might include
some hints
Sure attached here, you see in the initial report and the later comments
the time indexes to look out for.
Also FYI for the rtkit issue that you will see in there => bug 1871543
** Attachment added:
> Also do you have any gnome-shell/gdm crash collected in /var/crash?
No, just these:
$ ll /var/crash/*.crash
-rw-r- 1 paelzer whoopsie 3589735 Apr 6 08:34
/var/crash/_usr_bin_gnome-clocks.1000.crash
-rw-r- 1 paelzer whoopsie 53170176 Apr 8 10:36
> 1. Look in /var/crash for crash files and if found run:
>ubuntu-bug YOURFILE.crash
> Then tell us the ID of the newly-created bug.
Again, they all seem to be prior or follow on issues, but they already
have IDs in the error tracker.
/var/crash/_usr_bin_gnome-clocks.1000.uploaded
There appear to neither be any relevant crash files (there are a couple
which predate upgrading this system to focal), nor are there any reports
on errors.u.c for this whoopsie-id.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: gnome-session (Ubuntu)
Status: Invalid => Incomplete
--
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/1871580
Title:
Session killed instead of suspended
@Christian, could you add the journalctl log from that session, that
might include some hints. Also do you have any gnome-shell/gdm crash
collected in /var/crash?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Looks a little similar to https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/2596
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2596
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2596
** Also affects: gnome-shell via
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Hi Daniel,
none of the crashes that I had has the same signature as those that are
reported on the dup.
Furthermore as I outlined the crashes seem to be secondary issues after
soemthing breaks and recycles gnome-shell.
I'd ask for re-triage as that doesn't seem to be the same thing to me.
**
*** This bug is a duplicate of bug 1745345 ***
https://bugs.launchpad.net/bugs/1745345
Public bug reported:
Broken image 20200406
Test Case:
1. Install Ubuntu Desktop in Qemu
2. Reboot and login
Actual result:
User login and is back to GDM.
There is an xorg crash in the journal
*** This bug is a duplicate of bug 1745345 ***
https://bugs.launchpad.net/bugs/1745345
Yeah that's bug 1745345 which I'm told is a race and it seems more
likely to happen in VMs.
** This bug has been marked a duplicate of bug 1745345
Xorg assert failure: Xorg:
*** This bug is a duplicate of bug 1745345 ***
https://bugs.launchpad.net/bugs/1745345
/usr/lib/gdm3/gdm-x-session[3073]: Xorg:
../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion
`key->initialized' failed.
/usr/lib/gdm3/gdm-x-session[3073]: (EE)
Another crash just happened:
Apr 08 10:28:06 Keschdeichel systemd[1]: Reloading.
Apr 08 10:28:06 Keschdeichel systemd[1]: /lib/systemd/system/dbus.socket:5:
ListenStream= references a path below legacy directory /var/run/, updating
/var/run/dbus/system_bus_socket → /run>
Apr 08 10:28:17
Public bug reported:
Running focal (updated to 2020-04-08), ubuntu-on-wayland session.
Trigger: either lock the screen manually (top-right-corner menu -> Lock)
or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock).
Expected result: after unlock, previous session resumes.
1 - 100 of 125 matches
Mail list logo
