ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh instal
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
** Changed in: mutter (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1871475
Title:
[amdgpu] Black screen after screen lock
Status in
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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1852183
Title:
[X11] copy/paste
I'm not seeing any clue as to what might have happened in the journal,
unfortunately.
Just to confirm: this was a one-off issue, now firefox works well?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Public bug reported:
printing very faint
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: hplip 3.20.3+dfsg0-2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu25
Architecture: amd64
** Branch linked: lp:~ci-train-bot/libappindicator/libappindicator-
ubuntu-focal-4007
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sni-qt in Ubuntu.
https://bugs.launchpad.net/bugs/1600136
Title:
App indicator does not show icon
Could you rework the debdiff for bionic to use debian/patches and have a
shorter debian/changelog description? The changelog should be a summary
that the users will see for the update, the technical details can go to
the patch header itself
--
You received this bug notification because you are a
Thanks, I've uploaded to focal and will do bionic next. For futur
reference, changes shouldn't be applied inline but added as patches to
debian/patches. Please also include some description/bug reference when
doing that
As a reference that's how I updated the changeset before upload
Thank, I don't know but it's better to have details on what you did to
trigger the issue
** Changed in: xdg-desktop-portal-gtk (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
ok, I thought this was missing since it's been on the queue for a couple
of days now, but probably just unreviewed then
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1871662
** Changed in: pulseaudio (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819
Title:
[SRU] System can't detect
** Changed in: pulseaudio (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1871039
Title:
pulseaudio crashed with SIGABRT in raise()
Daniel responded on irc and said after several reboots with the new
apparmor, everything was fine on every boot (though his critical-chain
has var.lib.mount listed).
My attached systemd-analyze plot svg shows that apparmor.service is
indeed starting after var.lib.mount on the VM where the
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xdg-utils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
upload patch for bionic
** Patch added: "dual-jacks-bionic.patch"
https://bugs.launchpad.net/oem-priority/+bug/1869819/+attachment/5349710/+files/dual-jacks-bionic.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1509931.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Thanks for being diligent, but *feature* freeze exceptions are not
needed for bugfix releases.
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
I have personally subscribed to all gamemode bugs.
** Also affects: ubuntu-mate-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-mate-meta (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-mate-meta (Ubuntu)
Assignee: (unassigned) => Martin
Public bug reported:
The queue has a new bugfix release. The git changelog has these:
f84ad082557f9cd xserver 1.20.8
883727986930931 Fix old-style definition warning for xf86OSInputThreadInit()
0c012f968b4e02a Add xf86OSInputThreadInit to stub os-support as well
b25948597507808 xwayland: Delete
Also affecting Slack. Not possible to login to Slack app and I needed to
switch to Firefox for now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1776873
Title:
Whitelisted
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 Desktop
Packages, which is subscribed to
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 Desktop
Packages, which is subscribed to
Is there a relationship?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1871489
Title:
xdg-desktop-portal-gtk crashed with SIGSEGV
Status in xdg-desktop-portal-gtk
Sebastien, I updated the description of the report ...
Could it be because of this?
** Description changed:
- I don't know what happened.
+ I think it happened like this:
+ 1. I opened bijiben
+ 2. I clicked on a note that was already created
+ 3. In the note there was a web link
+ 4. I clicked
** Attachment added: "with separate menu bar"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1871644/+attachment/5349702/+files/firefox-csdbug-separate-menubar.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in
This is specific to the unification of the menu-bar into the title-bar
through client-side decorations. I am about to attach two more
screenshots that show the difference when the unification is disabled vs
the default.
** Attachment added: "with menubar in title bar"
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1871625
Title:
ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()
Status in
I'm seeing a similar artifact in top corners of firefox windows under
wayland, although it looks more transparent in my focal VM. But it's not
present under X11.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
** Bug watch added: Mozilla Bugzilla #1509931
I'm also seeing the pattern when logged-into X11 (note there is a
difference in the image because in Wayland I have the monitor set to
200% scaling while in X11 it is set to 100%, so the images have
different numbers of pixies for the bug)
** Attachment added: "top-right corner of a Firefox
Public bug reported:
Image to illustrate the problem is attached. All firefox windows on
Wayland have a weird black protrusion from the top-left and top-right
corners where yaru has curved the window corners, but something from
Firefox appears to not be being clipped by the theme. I need to
It seems that I am able to set the refresh rate to 120Hz and 144Hz.
Feel free to close this.
xserver-xorg-video-nouveau 1:1.0.16-1
Linux shahar-desktop 5.3.0-46-generic #38-Ubuntu SMP Fri Mar 27 17:37:05
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID:
** Changed in: glib2.0 (Ubuntu)
Assignee: (unassigned) => nassim (moujane)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1689344
Title:
print of __glib_assert_msg not returning
All that said, Daniel and Jean-Baptiste, I installed 20.04 in a vm and
tried to reproduce this and could not. The apparmor change was about
correctness of the unit so I performed the upload, but I also hoped that
it would address the issue you are seeing.
I'm not certain it will. On one boot,
*** 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.
P.B. I tried to verify your observation. Without luck. First I generated
a Windows-10 bootable USB drive and managed to install and run the "AMD
Driver Auto-detect tool". On Windows it was successful to set the
computer into standby and resume. Then I've done a warm-start of the
computer an booted
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
** Changed in: pulseaudio (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819
Title:
[SRU] System can't detect external
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1871414/+attachment/5349545/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Bug was also confirmed in Ubuntu's 5.4.0 kernel (original report)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1871414/+attachment/5349546/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Software details:
Distro: Kubuntu 20.04 Beta
Kernel: 5.4.0-21-generic
alsa-base version 1.0.25+dfsg-0ubuntu5
alsa-utils version 1.2.2-1ubuntu1
pulseaudio version 1:13.99.1-1ubuntu1
Hardware details:
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 1871563 ***
https://bugs.launchpad.net/bugs/1871563
** This bug has been marked a duplicate of bug 1871563
The window is frozen 3~10 seconds when swipe, pinch and zoom on the
google-map via touchscreen for a while.
--
You received this bug notification
Thanks for the report Tony. Can you confirm that it's only switching in
and out of fullscreen mode that's laggy, playback is otherwise smooth?
Could you please run the following command in a terminal to attach
additional information to the bug report:
apport-collect 1871618
** Changed in:
I was able to fully fix the issue of the microphone not working on my UX430UA
by doing this:
https://forums.linuxmint.com/viewtopic.php?p=1790578#p1790578
Original source linked in that forum post:
https://wiki.archlinux.org/index.php/ASUS_Zenbook_UX430/UX530#Headset_Microphone
--
You received
Public bug reported:
The switching of a playing youtube video to fullscreen mode and also
from fullscreen mode to normal mode lags.
Ubuntu version: 19:10
Chromium version: 80.0.3987.163 (Official Build) snap (64-bit)
Steps to reproduce
1. Launch Chromium and open Youtube.
2. Select/search for a
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1871573
Title:
HDMI port does not work on Ubuntu 20.04
Status in xorg package in Ubuntu:
*** 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.
You have been subscribed to a public bug:
Hi,
I know that you have certified version 18.04 and that 20.04 is not out yet.
So this is more heads up.
I am testing Ubuntu 20.04 on new Lenovo P1 2nd gen.
Currently HDMI does not work.
How do I know that problem is not in cable or monitor ?
If I
*** 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 Desktop
Packages,
** 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 Desktop
Packages, 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 Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1871580
Title:
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Desktop
Packages, 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 use
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
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
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"
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
Mistakenly posted under a duplicate, issue is still here on Ubuntu 18
with a Sennheiser headset. Issue is bound to pop up more now with
everyone remoting under lockdowns.
Device 00:16:94:32:A8:A7 (public)
Name: HD 4.40BT
Alias: HD 4.40BT
Class: 0x00240404
Icon: audio-card
Paired: yes
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,
** 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
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
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559
Device 00:16:94:32:A8:A7 (public)
Name: HD 4.40BT
Alias: HD 4.40BT
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
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
it'll be fixed in 20.0.5
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1867188
Title:
Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i
H.264
Status in mesa package
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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1871475
Title:
20.0.4 is in focal
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1855402
Title:
[TGL] mesa support
Status in intel:
** 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
I've had an HP Spectre 360 with HP dock for 5-6 years, and this has
always been a problem, and it still is. I traced it down one time to
the script that detects the available audio input devices, and sets the
default. The script is poorly written and is hard to follow. It
detects that there are
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an
@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
Public bug reported:
This concerns colord 1.4.4-2 in Ubuntu focal. (xiccd 0.3.0-1 may also be
relevant.)
I log into the Xfce desktop environment, and immediately see an
"Authenticate" window pop up:
Authentication is required to create a color managed device
Password for root:
@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...
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
Public bug reported:
Yaru version 20.04.4 needs some updates that require UI freeze
exception.
As suggested, I opened this ticket as container for speed up the review
- LP #1869141 [UIFe] Icon View Captions labels in Nautilus are hard to read
when selected
- LP #1870925 UI freeze exception to
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
> 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
> 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
> 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:
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
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
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 Desktop
Packages, which is subscribed to
** Changed in: gnome-session (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1871580
Title:
Session killed instead of suspended on
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349390/+files/Snap.Connections.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349395/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349391/+files/Snap.Info.chromium.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
@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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
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
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349394/+files/Snap.Info.gtk-common-themes.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349389/+files/Snap.ChromiumPrefs.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Info.core18.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349393/+files/Snap.Info.core18.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser 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
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/1871563/+attachment/5349392/+files/Snap.Info.core.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
101 - 200 of 282 matches
Mail list logo
