Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1964392
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Yes it has changed again. Back to having an unusable stack trace:
https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058
So this bug is invalid. It's going to keep jumping between different
stack traces due to issues with errors.ubuntu.com.
** This bug is no longer a duplic
This is the crash that happens during jammy live sessions.
--
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/1964458
Title:
[jammy] gnome-shell crashes with SIGSEGV in js::gc::Cel
See also bug 1947130, bug 1962513.
--
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/1964458
Title:
[jammy] gnome-shell crashes with SIGSEGV in js::gc::Cell::storeBuffer
from js
Public bug reported:
gnome-shell crashes with SIGSEGV in:
#0 0x7fd9229e61b4 in js::gc::Cell::storeBuffer (this=,
this=)
at .././js/src/gc/Cell.h:357
#1 js::gc::PostWriteBarrierImpl (next=,
prev=, cellp=)
at .././js/src/gc/StoreBuffer.h:654
#2 js::gc::PostWriteBarrier (next=,
pre
The crash is indeed slightly different now that we've moved to mozjs91.
It's being tracked in bug 1964458.
We don't need to keep this one open for mozjs78.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of
Hello,
In fact, my installation is not quite standard, and apport is no longer
installed.
On the other hand, I have the problem changed a few minutes ago by
replacing the obsolete PPA of otto-kesselgulasch by that of ubuntuhandbook,
and by uninstalling, then reinstalling Gimp.
Another error messa
** Also affects: gjs (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- gnome-shell crashes with SIGSEGV in:
+ gnome-shell crashes on exit with SIGSEGV in:
#0 0x7fd9229e61b4 in js::gc::Cell::storeBuffer (this=,
this=)
- at .././js/src/gc/Cell.h:357
+
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (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.
https://bugs.launchpad.ne
'xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
LiveMediaBuild: Ubun
It appears the mozjs Heap is a bogus pointer from very early on.
Next steps:
1. See if the latest gjs update has changed the situation (waiting on
new live images).
2. Look into gjs to see if the problem starts in there or if the whole
gjs context from gnome-shell is invalid.
--
You received t
*** This bug is a duplicate of bug 1964458 ***
https://bugs.launchpad.net/bugs/1964458
** This bug has been marked a duplicate of bug 1964463
Ubuntu Jammy gnome-shell crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subsc
27; b'welcome-dialog-last-shown-version' b"'41.3'"
+ b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
+ b
*** 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 ?? ()
StacktraceTo
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gjs (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.
https://bugs.launchpad.net/bugs/1
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (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.
https://bugs.launchpad.ne
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mozjs91 (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.
https://bugs.launchpad.net/bu
*** This bug is a duplicate of bug 1964458 ***
https://bugs.launchpad.net/bugs/1964458
I failed to notice this is from:
gnome-shell --sm-disable --mode=ubiquity
and the crash address XXX1b4 confirms it, this is bug 1964458.
** This bug is no longer a duplicate of bug 1964463
Ubuntu Jam
*** This bug is a duplicate of bug 1964458 ***
https://bugs.launchpad.net/bugs/1964458
It looks like the crash address has shifted slightly in the latest mozjs
version but this is almost certainly bug 1964458.
Still waiting for the bots to try and retrace it.
** This bug has been marked a du
** Description changed:
- gnome-shell crashes on exit with SIGSEGV in:
+ 'gnome-shell --sm-disable --mode=ubiquity' crashes on exit with SIGSEGV
+ in:
#0 0x7fd9229e61b4 in js::gc::Cell::storeBuffer (this=,
this=)
at .././js/src/gc/Cell.h:357
#1 js::gc::PostWriteBarrierImpl (nex
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1964458
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
You're right. We need both codesearch lists.
I believe updating the distro packages is doable for Jammy but I am
willing to wait for 22.10 if you don't think it's a good idea now.
For our LTS users as long as they're using distro packages, it shouldn't
make a difference which way we go.
I think
I would start by reinstalling libgail-common, restart and see if that
brings the issue back. I also think you can install the pending
upgrades, it shouldn't make a difference here
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0
** Bug watch added: Debian Bug tracker #923345
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923345
** Also affects: evince (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923345
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: evince (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1794064
Title:
Clicking a hyperlink in a PDF fails to open it if the defa
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Jeremy Bicha (jbicha)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu
I will take a stab at this later today.
Yesterday while searching a bit I may have encountered the reason these
particular packages have a problem. I was doing a search and it may be
that the packages having the problem I am seeing are all qt5 users.
Could there be a problem between qt5 and the l
Public bug reported:
Using the GNOME 42 updates in proposed the login screen background is
black, that feels buggy, we should revert to the old style
** Affects: yaru-theme (Ubuntu)
Importance: High
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: New
** Package changed: gdm
*** This bug is a duplicate of bug 1962628 ***
https://bugs.launchpad.net/bugs/1962628
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 #1962628, so is being marked as such.
Public bug reported:
Hi,
Using GS 42 in Jammy, when I press the display switch key of my laptop
keyboard, I get the usual pop-up but the selected item is not applied.
I have to use gnome-control-center to configure my displays. (gcc is slow to
start these days?)
** Affects: gnome-shell (Ubuntu
** Changed in: packagekit (Ubuntu)
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/1962346
Title:
Ubuntu reboots instead of powering off if a softw
Public bug reported:
Hi,
In Jammy + GS 42, I get a very slow start for g-c-c.
In logs:
17:33:32 gnome-control-c: Error connecting to ModemManager: Erreur lors de
l’appel de StartServiceByName pour org.freedesktop.ModemManager1 : Failed to
activate service 'org.freedesktop.ModemManager1': timed
I see.
I did use 1.18.6-2 version for whatever reason, which has been deleted from
Jammy.
Reverting to the current *-1 version solves this.
Sorry.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubun
*** This bug is a duplicate of bug 1962628 ***
https://bugs.launchpad.net/bugs/1962628
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 #1962628, so is being marked as such.
How do I reinstall libgail-common? I used dpkg -i with
libgail-3-0_3.24.20-0ubuntu1_amd64.deb with no change in behavior. I
went back to
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.20-0ubuntu1/+build/19437463
but I don't see a libgail-common file there.
--
You received this bug notificati
I just thought to look in synaptic and I see it there. Should I install
from there, or is there a reason to do so in another manner?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/19
yes, installing from synaptic is fine. The package comes from gtk2
that's why it's not on the gtk3 buildpage
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1962807
Title:
segfault
IMHO we should still expose the new desktop file as NoDisplay, just to
be sure that applications that will target GNOME 42 will be able to open
settings.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bu
This bug was fixed in the package systemd - 249.10-0ubuntu2
---
systemd (249.10-0ubuntu2) jammy; urgency=medium
* Fix deadlock between pid1 and dbus-daemon (LP: #1871538)
File:
debian/patches/pid1-set-SYSTEMD_NSS_DYNAMIC_BYPASS-1-env-var-for-dbus-da.patch
https://git.launc
Installed libgail-common via synaptic as requested and restarted the
system. The results are not what I expected:
dhdurgee@z560:~/Downloads$ fcl
Gtk-Message: 12:46:26.155: Failed to load module "gail"
** (fcl:2132): WARNING **: 12:46:26.238:
(../atk-adaptor/bridge.c:1018):atk_bridge_adaptor_ini
the earlier experience of having the segfault not resolved after
removing it suggests that you might need to restart the session for the
change to be active, did you try to logout and log in again?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is sub
Already got picked up via process-removals. Generally no reason to file
removal bugs for cases like this.
** Changed in: gnome-desktop3 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome
I used synaptic to install the package and then did a restart of the
system after cleanly closing all running programs. That of course
required me to log back in when the system restarted. Is there more I
should do at this point?
--
You received this bug notification because you are a member of
Public bug reported:
[Impact]
Occasionally, when the screen has been locked for a medium length of
time, > 5 mins, when you press the spacebar, enter your password, the
primary display freezes and the lockscreen slider does not slide up. The
secondary screen is fine, and unlocks.
See screenshot
** Attachment added: "Primary screen stuck, secondary is unlocked"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+attachment/5567839/+files/IMG_20220311_122713.jpg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed t
Public bug reported:
Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
attempting to re-arrange tabs in Firefox fails. Click and drag the tab
and release, nothing changes. The next click to the tab is ignored.
syslog has the following:
Mar 11 13:06:47 desktop firefox[2192]: Attempti
** Also affects: gnome-shell (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags added: jammy
--
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/1964541
Title:
42be
Public bug reported:
[Impact]
If you move the mouse as the system fades into black for the
screensaver, the screensaver will be prevented as normal, but the user
will not be able to interact with the shell.
Mouse clicks are ignored, and most key presses are ignored too.
Workaround is to press s
** Also affects: gnome-shell (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags added: jammy
--
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/1964539
Title:
42be
Just to clarify, we will be adding the option to launch gnome-control-
center from the system menu? I keep finding myself trying to launch it
from there to check sound settings before meetings, but it is missing,
and have to launch from overview instead.
I think this is a feature that LTS users wi
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gnome-shell (Ubuntu)
** No longer affects: gnome-shell (Ubuntu Jammy)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
This is definitely a bug in mutter (gnome-shell). Other people reported
it to me in recent months per comment #3.
** Changed in: gnome-shell (Ubuntu)
Status: Invalid => Confirmed
** Information type changed from Private to Public
** Also affects: mutter (Ubuntu)
Importance: Undecided
Looks like it only fails in Xorg sessions. If you log into a Wayland
session then the icons appear.
** Also affects: gjs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gjs (Ubuntu)
Status: New => Confirmed
** Changed in: gjs (Ubuntu)
Importance: Undecided => High
Matthew, yes, the missing Settings link was basically an Ubuntu
packaging bug and is fixed with
https://launchpad.net/ubuntu/+source/gnome-shell/42~beta-1ubuntu2
I believe you would need to log out and log back in after installing
that update.
--
You received this bug notification because you ar
** Tags added: jammy
--
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/1964496
Title:
[GS 42] display switching key does not work
To manage notifications about this bug go to:
ht
Please try adding this to /etc/environment:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
and then reboot.
Also...
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a
Next time the problem happens please immediately run:
journalctl -b0 journal.txt
and attach the resulting text file here.
** Tags added: multimonitor
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://
apport information
** Tags added: apport-collected package-from-proposed third-party-
packages wayland-session
** Description changed:
[Impact]
Occasionally, when the screen has been locked for a medium length of
time, > 5 mins, when you press the spacebar, enter your password, the
pr
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1964539/+attachment/5567870/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1964539/+attachment/5567873/+files/ShellJournal.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.lau
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1964539/+attachment/5567872/+files/ProcEnviron.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.launc
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1964539/+attachment/5567871/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
http
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1964539/+attachment/5567874/+files/monitors.xml.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.lau
Hi Jeremy,
Sorry, I should have rebooted first. The settings link is there and it
works. Happy to say verified.
--
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/1964136
Title:
S
Public bug reported:
BraseroLibburn SCSI error condition on command 2Ah WRITE(10): See MMC specs:
Sense Key 5 "Illegal request", ASC 21 ASCQ 04.
BraseroLibburn called brasero_job_set_current_action
BraseroLibburn Libburn reported an error SCSI error on write(0,16): See MMC
specs: Sense Key 5 "I
apport information
** Tags added: apport-collected bionic
** Description changed:
BraseroLibburn SCSI error condition on command 2Ah WRITE(10): See MMC specs:
Sense Key 5 "Illegal request", ASC 21 ASCQ 04.
BraseroLibburn called brasero_job_set_current_action
BraseroLibburn Libburn repo
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1964554/+attachment/5567878/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in Ubuntu.
https://
See also bug 1181666, although that's probably a different issue if it
is still an issue at all.
--
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/1964545
Title:
42beta: moving mo
Please still follow the steps in comments #2 and #3. Although something
else stands out - that you're using the nouveau kernel driver. Nouveau
is prolific for kernel crashes, freezes, and other bugs. So ideally
please use the 'Additional Drivers' app to install a proprietary Nvidia
driver instead.
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-contro
Note to everyone else: A lot of machines don't have a display switching
key. It is sometimes Fn+F8 or Fn+F7.
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-she
You have been subscribed to a public bug:
Ubuntu 21.10 with wayland windowing system sits on completed file
transfers on and off usb and takes its time realising its finished and
closing the little transfer progress logo.
running an HP elitedesk 800 G1 SFF with 16gb ram, i5 4690 cpu and an HD
460
Flash drives are usually very slow devices. Next time a transfer has
trouble finishing please open a Terminal window and run:
sync
If the command returns immediately then this is a Nautilus bug. If the
command does not return until the file transfer finishes then this is
either a kernel bug or
Hi Daniel,
yes, in hybrid system, different BIOS have their own way to configure
it. We just need to make sure the memory point of efifb passed from BIOS
is correct one and it's correct in this case, the boot_vga is dGPU.
I'll risk this issue on upstream to discuss and share the upstream bug
here
Bug confirmed with Nvidia-510. External monitors connected to the
secondary (Nvidia) GPU never light up in Wayland sessions. Also my log
is full of:
clutter_frame_clock_notify_presented: code should not be reached
** Changed in: mutter (Ubuntu)
Status: Incomplete => Confirmed
** Change
** Changed in: mutter (Ubuntu)
Status: Triaged => 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/1959888
Title:
Wayland sessions can't use external monitors that
76 matches
Mail list logo
