Forgot to state nothing in /var/crash/ directory
--
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/1964652
Title:
Settings program crashes intermittently. Will not shut
Public bug reported:
Settings program crashes intermittenly as I am trying to set/edit wifi
settings on a 'hidden network' System Settings (gnome-control-center)
stops responding. When I do 'sudo apt-get install --reinstall gnome-
control-center' I can get it to start again. Reason for attempting
Just found something at https://fossies.org/linux/gtk+/NEWS which
contains:
8699 658168 Gtk-Message: Failed to load module "gail"
So this might be a GTK bug that is fixed in GTK+ 3.24.32, 03-03-2022
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
I thought to do a web search and it appears that the failure to load
"gail" and the atk_bridge_adaptor_init runtime check failure have been
reported for a number of packages for a while.
It appears to be a harmless error in my case, but some of the other
reported cases appear to prevent packages
*** This bug is a duplicate of bug 1959937 ***
https://bugs.launchpad.net/bugs/1959937
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 #1959937, so is being marked as such.
I'm having the exact same issue in Pop!_OS 20.04 LTS
I fixed it once by doing:
sudo dpkg --force depends -P libglib2.0-0:i386
But then the next time I did an update the issue came back again. This
definitely seems like an upstream problem as it affects multiple Ubuntu
derived distros.
--
You
I just installed all of the queued updates with the exception of
virtualbox and the linux kernel. Everything appears to be working OK.
I had a thought occur to me, perhaps that console message "Gtk-Message:
11:09:45.426: Failed to load module "gail"
** (fcl:2049): WARNING **: 11:09:45.439:
*** This bug is a duplicate of bug 1964458 ***
https://bugs.launchpad.net/bugs/1964458
Thank you for your report!
However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some
*** This bug is a duplicate of bug 1964458 ***
https://bugs.launchpad.net/bugs/1964458
Stacktrace:
#0 0x7f04cd0f7f44 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7fff167a9950
StacktraceSource: #0 0x7f04cd0f7f44 in ?? ()
*** This bug is a duplicate of bug 1964458 ***
https://bugs.launchpad.net/bugs/1964458
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1964463/+attachment/5568001/+files/ThreadStacktrace.txt
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed =>
it has been fixed upstream now
** Changed in: totem (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1962679
Title:
take screenshot
Public bug reported:
At least according to gnome-control-center anyway.
Running the Ubuntu Desktop for Raspberry Pi image on a Pi 400 (or a Pi
4B), selecting Settings, then the "About" page shows that gnome-control-
center thinks the processor is "", the graphics are "unknown", and
apparently so
Fixed also in systemd v250.4 and v249.11
--
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 gdm
I'm closing this since there aren't any additional errors reported after
Ubuntu 14.04 LTS was released.
** Changed in: gnome-bluetooth (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I closed the gnome-bluetooth part of this bug since this was apparently
fixed in pulseaudio instead.
** Changed in: gnome-bluetooth (Ubuntu Xenial)
Status: New => Invalid
** Changed in: gnome-bluetooth (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification
Very similar to bug #1963756. As I mentioned there, the bug disappeared
when I had upgraded gnome-shell etc. from jammy-proposed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1964296
** Tags added: jiayi
--
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/1962523
Title:
[Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia
installed
To manage
** Tags added: jiayi
--
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/1963701
Title:
[NVIDIA][Wayland] graphic target not able to reach as the only monitor
connect to NV GPU only on
Hi,
the error message stems from the burner drive and was forwarded by libburn
to Brasero. Strangely the code ASC=21 , ASCQ=04 is not specified in in
the SCSI specs for optical drives (MMC).
In the overall error code list
https://www.t10.org/lists/asc-num.htm
it is listed for other device
19 matches
Mail list logo
