[Bug 2006055] Re: Gnome stuck after going to "activities"

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 2012287] Re: GNOME Characters search provider for GNOME Shell 44 crashes

** Also affects: gjs (Ubuntu Lunar) Importance: Medium Status: Confirmed ** Also affects: gnome-characters (Ubuntu Lunar) Importance: High Status: Triaged ** Also affects: gjs (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: gnome-characters

[Bug 435928] Re: Password works in virtual terminal but not in Gnome screensaver

This bug affects me, and I'm running 20.04. It started a couple of months ago. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/435928 Title: Password works in virtual terminal but not in Gnome

[Bug 353356] Re: Gnome screensaver lock always reports "incorrect password"

I have this same issue, started a couple months ago. Everything worked previously. The fixes mentioned above did not help, other than the "switch user and exit X" tip. Must have a regression somewhere because the most recent comment above is 12 years old (I'm running 20.04). -- You received

[Bug 2015610] [NEW] Input source indicator not shown

Public bug reported: In my 23.04 development installation I installed the ubuntu-unity- desktop package and then logged in to Unity. One observation is that the input source indicator is not shown in the top bar, even if that feature is enabled in Text Entry. Please see the attached screenshot.

[Bug 2012879] Re: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_finished() from g_

This bug was fixed in the package accountsservice - 22.08.8-1ubuntu6 --- accountsservice (22.08.8-1ubuntu6) lunar; urgency=medium * debian/patches/git_users_requests.patch: - included more fixes from upstream !128, resolves an invalid read which is leading to crashes

[Bug 2015465] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2015465/+attachment/5661988/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2015465/+attachment/5661564/+files/CoreDump.gz ** Changed in: gnome-control-center

[Bug 2015465] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/2015465/+attachment/5661987/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.

[Bug 2015465] Stacktrace.txt

** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2015465/+attachment/5661986/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.

[Bug 2015465] gnome-control-center crashed with SIGSEGV in g_closure_invoke()

StacktraceTop: undefined_value.lto_priv () from /srv/vms/apport-sandbox-dir/Ubuntu 23.04/amd64/report-sandbox/usr/lib/x86_64-linux-gnu/libgtk-4.so.1.1000.1 cc_display_config_manager_get_night_light_supported (self=) at ../panels/display/cc-display-config-manager.c:72 dialog_update_state

[Bug 2015568] Re: [lunar] Settings are not applied

I see the icon size to be wrong: in my extension DashBar with Ubuntu's panel height, the Proton bridge is 22 px height, much bigger than Indicator's one that is supposed to be set at 22 px too in my setup. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs,

[Bug 2015568] [NEW] [lunar] Settings are not applied

Public bug reported: Hi Marco, When I change the extension's settings, I do not see any change (icon size, opacity, position, ...). Lunar Ubuntu session, ext version 53-1 ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Description

[Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()

** Changed in: mozjs Status: New => Invalid -- 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/1974293 Title: gnome-shell crashed on logout with SIGSEGV in

[Bug 1974293]

Your comment in the linked issue identifies the problem: > Basically I'm wondering if it's safe that JS::GCVector::~GCVector happens after JS_DestroyContext. It's not safe. The vector (and anything else containing a JS::Heap) must be destroyed before the JS context is destroyed. -- You

[Bug 2015555] Re: launched steam - thats when I saw the error

*** This bug is a duplicate of bug 2012287 *** https://bugs.launchpad.net/bugs/2012287 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 #2012287, so is being marked as such.

[Bug 2012287] Re: GNOME Characters search provider for GNOME Shell 44 crashes

I'm getting this error every time I'm launching Steam (deb version). -- 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/2012287 Title: GNOME Characters search provider for GNOME Shell 44

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

** Information type changed from Public to Public Security -- 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/1968040 Title: Blanked screen doesn't wake up after locking

[Bug 2015540] Re: Loop PCIe Bus Error: severity=Corrected,

** Attachment added: "n100.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015540/+attachment/5661905/+files/n100.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 2015540] [NEW] Loop PCIe Bus Error: severity=Corrected,

Public bug reported: at login hi have this loop: Apr 07 11:48:54 corrado-n4-ll-beta kernel: pcieport :00:1d.0: AER: Multiple Corrected error received: :01:00.0 Apr 07 11:48:54 corrado-n4-ll-beta kernel: r8169 :01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer,

[Bug 2015538] [NEW] [MIR] dbus-broker

Public bug reported: [Availability] The package dbus-broker is already in Ubuntu universe. The package dbus-broker build for the architectures it is designed to work on. It currently builds and works for architetcures: amd64, arm64, armhf, i386, ppc64el, riscv64, s390x Link to package

[Bug 2015534] Re: totem crashed with SIGSEGV in gtk_tree_model_get_valist()

** Tags removed: need-amd64-retrace -- 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/2015534 Title: totem crashed with SIGSEGV in gtk_tree_model_get_valist() To manage notifications

[Bug 2015534] [NEW] totem crashed with SIGSEGV in gtk_tree_model_get_valist()

Public bug reported: crash without knowing the exact problem ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: totem 43.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: