Upgrade: gnome-shell-common:amd64 (42.9-0ubuntu2.1, 42.9-0ubuntu2.2)
Remove: gnome-shell:amd64 (42.9-0ubuntu2.1),
This shows only gnome-shell-common being installed and gnome-shell being
removed. What does `apt policy` show for these two packages?
--
You received this bug notification because
The log looks like Wayland sessions are starting up just fine. I wonder
if this might be another simpledrm issue (even though simpledrm card0 is
clearly already removed before GNOME starts on Intel card1)... Please
try adding kernel parameter:
initcall_blacklist=simpledrm_platform_driver_init
*
It sounds like you're referring to OBEX used to transfer files between
devices. But also since you're using Unity 7, I don't know what other
legacy components might be getting in the way here.
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu
Is anything in your report a regression, i.e., a new issue that was not
there a few days ago?
What is this large text setting and where is it used? In the web pages
themselves or in Chromium's interface elements such as tab bar,
configurations menu etc.?
What is this 'top bar named New Tab - chro
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Chromium opens, but still loads within 15 seconds after opening.
+ Chromium opens, but cursor remains in "loading" state within 15 seconds after
opening.
--
You received this bug notificatio
And why would we delay the login screen waiting for Chromium to be
mounted? Surely that should only delay your ability to launch Chromium.
** Package changed: mysql-8.0 (Ubuntu) => chromium (Ubuntu)
** No longer affects: apt (Ubuntu)
--
You received this bug notification because you are a membe
Thanks. Something killed the shell when it started in Wayland mode:
Aug 19 07:41:34 Sam-acer-notebook gnome-session[1773]:
gnome-session-binary[1773]: WARNING: Application 'org.gnome.Shell.desktop'
killed by signal 9
Aug 19 07:41:34 Sam-acer-notebook gnome-session-binary[1773]: WARNING:
Applica
Public bug reported:
These GTK 4.15.5 tests fail:
--->
gtk:gdk / memorytexture
ERROR0.33s killed by signal 5 SIGTRAP
gtk:gdk / dmabufformats
ERROR0.21s killed by
Did you try adding a dependency on `mesa-vulkan-drivers`?
It includes a software-only vulkan implementation which should help in testing
these code paths.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launc
** Description changed:
These GTK 4.15.5 tests fail:
--->
gtk:gdk / memorytexture
ERROR0.33s killed by signal 5 SIGTRAP
gtk:gdk / dmabufformats
ERROR0.21
Okay, let's just talk only about the large text text then.
Wayland
-
Ubuntu -> Settings -> accessibility -> seeing -> large text. Chromium's
v127.0.6533.119. The interface does not change at all. But it must change.
** Attachment added: "Screenshot from 2024-08-19 12-25-16.png"
No. I'll try too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2077313
Title:
GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
Status in gtk4 package in Ubuntu:
In Pr
There is no extensions folder in the specified directory, so I don't think
there aren't any installed.
As I said the thing happens when too many things are open (many tabs and a VM
running).
I am just arguing that killing the whole GUI environment seems wrong to me..
--
You received this bug no
You added some patch to version 127.0.6533.119 that makes it open
normally on wayland session. What did you do? Because this behavior is
preserved in the flatpak of the same version.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromiu
this is what a wayland session looks like
** Attachment added: "wayland.webm"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+attachment/5806974/+files/wayland.webm
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
> open normally on wayland session
What exactly do you mean with open normally? As far as I know, it opened
normally before too. The only abnormal thing was the spinning cursor.
Do you mean the spinning cursor went away in 127.0.6533.119?
The substantial difference in that version is that Chromi
For the top bar, there is a 'use system title bar and borders'. That
works if you turn it off, doesn't it?
--
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/2077272
Title:
Diffe
** Summary changed:
- Difference in behavior in wayland and xorg sessions
+ Gnome's large text accessibility setting not reflect in Chromium in Wayland
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medi
Adding mesa-vulkan-drivers to build-depends makes the memorytexture and
scaling tests fail with segmentation fault, although it solves
dmabufformats test failure.
https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+build/28880496/+files/buildlog_ubuntu-
oracular-armhf.gtk4_4.15.5+ds-2_BUILD
I suspect I am affected by this as well, after updating from FF 115 ESR
to FF 128 ESR in F-40 with XFCE.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2047262
Title:
Firefox stopped
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/b
** Also affects: k3b (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: k3b (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to snapd-glib in Ubuntu.
https://bugs.launchpad.net/bugs/2076984
Title:
Plasma 6
After adding that to `/etc/environment` , the gear icon appeared and the
desktop defaulted to Wayland along-with an option for x11.
Do, you need the latest copy of journalctl or anything else ?
```
> echo $XDG_SESSION_TYPE
> wayland
```
--
You received this bug notification because you are a me
Trying this: gsettings set org.gnome.shell.extensions.dash-to-dock
show-mounts-network false
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/2077245
Title:
faced the same bug. Fixed by selecting `NVIDIA (Performance Mode)`
profile in NVIDIA X-server settings
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1870736
Title:
[nvid
Public bug reported:
Hello,
I came across this error after installing flashback, logging out from ubuntu
and logging in to flashback.
I wasn't expecting this bug, since I was using the flashback session.
Regards!
ProblemType: Crash
DistroRelease: Ubuntu 24.10
Package: gnome-shell 47~beta-1ubun
StacktraceTop:
__GI_getenv (name=name@entry=0x7a71cdbf5e5a "EXPAT_ENTROPY_DEBUG") at
./stdlib/getenv.c:31
getDebugLevel.constprop.0 (variableName=variableName@entry=0x7a71cdbf5e5a
"EXPAT_ENTROPY_DEBUG", defaultDebugLevel=0) at ../../src/lib/xmlparse.c:8525
ENTROPY_DEBUG (label=0x7a71cdbf5e6e "
** Attachment added: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/2077331/+attachment/5807020/+files/Stacktrace.txt
--
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/2077331
Ti
** Attachment added: "StacktraceSource.txt"
https://bugs.launchpad.net/bugs/2077331/+attachment/5807021/+files/StacktraceSource.txt
--
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
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/2077331/+attachment/5807022/+files/ThreadStacktrace.txt
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/2077331/+attachment/5807009/+files/CoreDump.gz
** Changed in: gnome-shell (Ubuntu)
Im
Answering my own question:
> Is anything in your report a regression, i.e., a new issue that was
not there a few days ago?
This is a regression of Chromium in native Wayland, it does not occur in
older releases.
Chromium on Xwayland is fine as tested with --ozone-platform-hint=x11.
** Tags adde
Public bug reported:
Screen flickering randomly when using my pc. its not too frequent but it
happens sometimes when i switch between apps and it continues behaving
like that for like 30 secs then stops
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignatur
Reversion committed: https://git.launchpad.net/~chromium-team/chromium-
browser/+git/snap-from-
source/commit/?id=66a95be63c03ae2b8c0c5a5d5ee612ded8b51dbd
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a memb
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libreoffice (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/b
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: thunderbird (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/b
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
--
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/2077232
Title:
Security update 42.9-0ubuntu2.2 uninstalls
Public bug reported:
Under Ubuntu 22.04.4 on Wayland, since upgrade to kernel 6.8, when moving
mouse, on a dark background, white bars are created...
See attachment.
Remembering a previous bug, I added "i915.enable_psr=0" to grub, and the
problem disappears...
Under Xorg, no problem.
Sorry for m
Public bug reported:
I was turning off the PC, and thus, I was closing the apps. After
clicking on the "x" close button on Google Chrome, the system froze for
a few seconds (neither the mouse was moving), then went back to the
login page.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg
Finally "i915.enable_psr=0" doesn't solve the problem... :-(
--
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/2077349
Title:
little display problems since kernel 6.8
Status in xorg packag
I checked that the build flags for systemd on s390x and ppc64el in
noble-proposed look correct:
https://launchpadlibrarian.net/743007715/buildlog_ubuntu-noble-ppc64el.systemd_255.4-1ubuntu8.4_BUILDING.txt.gz
https://launchpadlibrarian.net/743006792/buildlog_ubuntu-noble-s390x.systemd_255.4-1ubuntu
** Changed in: mutter
Status: New => Fix Released
--
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/2040977
Title:
Mouse cursor stutters if nothing else is animating on screen
Sta
Daniel, the gtk revert from gtk #6620 that you linked to was included in
gtk4 4.15.5
** Changed in: gtk4 (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.laun
Specifically https://gitlab.gnome.org/GNOME/gtk/-/commit/3d802177be
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2076652
Title:
Mouse cursor is oversized in GTK4 apps
Status in GTK+:
Hi Frank Heimes,
Comment #67:
> A new upload of the s390-tools package always also requires an upload of the
> s390-tools-signed package with the same version as well.
> I've attached the debdiff for it here...
Thanks for that.
The upload contains removals of d/{changelog,control}.orig which ar
For those whom it may help:
On Mint 22, xfce:
$ xreader
EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
Segmentation fault (core dumped)
However,
$ WEBKIT_DISABLE_COMPOSITING_MODE=1 xreader # Starts normally
To make WE
Apparently, this is still waiting on actions to comment #5.
If that is not the case (or once it is no longer the case), please clarify in a
comment.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmbim in Ubuntu.
https://bugs.launchpa
> What does `apt policy` show for these two packages?
See the bug description.
I found this StackExchange question:
https://askubuntu.com/questions/1477377/gnome-shell-broken-after-the-latest-update
which reports a similar error, but for an older upgrade a year ago.
--
You received this bug no
I still have the same issues as the original bug mentioned here. When
troubleshooting I do have different results though than the users here.
I can get all the tests to come back good, they all work like they're
supposed to, but running adsysctl update -m still nets me with the same
results.
I can
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2024377
Title:
Adsys can't fetch GPOs
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Jammy:
Fix Rel
In the past two years, the WPE renderer has itself also been removed.
This bug is surely not relevant to anybody in 2024. You're hitting some
other bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpa
I am working on certifying Dell platform with the modem requires the
SRU, after that the modem service will do needs-pacakging to be in
Ubuntu archive, then proceed the SRU and verify the full function.
--
You received this bug notification because you are a member of Desktop
Packages, which is s
** Tags added: fixed-in-gtk-4.15.5 fixed-upstream
** Changed in: gtk4 (Ubuntu)
Milestone: None => ubuntu-24.10
** Changed in: gtk4 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubu
Great that you have a workaround now. We do need to report this to the
upstream developers though. Please open a new issue at:
https://gitlab.gnome.org/GNOME/mutter/-/issues
Mention that gnome-shell is being killed by signal 9 and the workaround
MUTTER_DEBUG_KMS_THREAD_TYPE=user is working.
**
** Tags added: kmsthread
--
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/2076318
Title:
[Asus Zenbook S 13] Heavy cursor stutter
Status in Mutter:
Fix Released
Status in mutter packa
** Tags added: kmsthread
--
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/2074254
Title:
Screen freezes when using EGL Stream (Nvidia-470)
Status in Mutter:
Fix Released
Status in mut
** Tags added: kmsthread
--
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/2074253
Title:
i915 cursor position does not move if nvidia-470 is also present
Status in Mutter:
Fix Release
I think I might have misinterpreted that table. gnome-shell was only
using 156348416 bytes (156MB) of RAM. Other processes like 'java',
'kdevelop', 'VirtualBoxVM' and lots of Firefox tabs seem to be the
reason the machine ran out of memory.
So overall it sounds like gnome-shell probably just crash
*** This bug is a duplicate of bug 2043956 ***
https://bugs.launchpad.net/bugs/2043956
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 2043956, so it is being marked as such. Please look
** Summary changed:
- gnome-shell crashed with SIGSEGV in __GI_getenv("EXPAT_ENTROPY_DEBUG") from
getDebugLevel() from ENTROPY_DEBUG() from generate_hash_secret_salt() from
startParsing()
+ gnome-shell crashed with SIGSEGV in __GI_getenv("EXPAT_ENTROPY_DEBUG") from
getDebugLevel() from ENTROPY_
Ok, sorry for overlooking.
Here's what it should look like:
$ apt policy gnome-shell
gnome-shell:
Installed: (none)
Candidate: 42.9-0ubuntu2.2
Version table:
42.9-0ubuntu2.2 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://security.u
It seems that everything fell into place, the scale is preserved, the title bar
is present again. Indeed, the "use system title bar and borders" option works.
But it is confusing.
Because in the flatpak version, the deb version of Google Chrome, as well as
Chromium downloaded from AUR (I did thi
https://issues.chromium.org/issues/360909063
I created a bug report
** Bug watch added: issues.chromium.org/issues #360909063
https://issues.chromium.org/issues/360909063
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-brows
>spinning cursor went away
Yes, Wayland via Ozone fixes the issue for wayland session.
--
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/2070889
Title:
Chromium opens, but curso
Public bug reported:
Installed the Community version of the Intellij IDEA Community Edition
2024.2.0.1 on a Ubunbtu 24.04 build. I tried snap , download from
JetBrain site it will run for a few seconds initially and then freeze.
Let me know if this is not the right place to report this issue with
Ok,Reported upstream.
https://gitlab.gnome.org/GNOME/mutter/-/issues/3628
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3628
https://gitlab.gnome.org/GNOME/mutter/-/issues/3628
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
** Changed in: mutter (Ubuntu)
Importance: Undecided => Medium
** Changed in: mutter (Ubuntu)
Status: New => Triaged
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3628
Importance: Unknown
Thanks. The logs say that GNOME is functioning just fine. This might be
related to the fact that it's using Intel Arrandale graphics which I
haven't tried in a long time.
Please try adding this to /etc/environment:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
and reboot. If that doesn't solve it then pl
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-6472
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/2073054
Title:
[SRU] libreoffice 24.2.5 for noble
Status in
This is the second time in recent memory that gnome-shell-common has
caused upgrades grief. In this case, I don't think requiring equal
versions is sensible:
Package: gnome-shell
...
gnome-shell-common (= ${source:Version}),
The main ABIs of gnome-shell-common are /usr/share/glib-2.0/schemas
Public bug reported:
[Impact]
* LibreOffice 24.2.5 is in its fifth bugfix release of the 24.2 line:
https://wiki.documentfoundation.org/ReleasePlan/24.2#24.2.5_release
* This source packages matches the proposed SRU for noble handled at
https://bugs.launchpad.net/ubuntu/+source/libre
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
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 2062951, so it is being marked as such. Please look
As a workaround, please try adding this to /etc/environment:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
and reboot.
** Tags added: i915 psr regression-update
** Package changed: xorg (Ubuntu) => linux-hwe-6.8 (Ubuntu)
** Changed in: linux-hwe-6.8 (Ubuntu)
Importance: Undecided => Medium
** Summa
Based on the description I think this is most likely to be bug 2037055.
But to be sure, please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash for crash files and if f
** Changed in: gnome-shell (Ubuntu)
Importance: Critical => High
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
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/bu
Packaging changes are staged at
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/log/?h=wip/jammy-24.2
** Patch added: "libreoffice_24.2.5-0ubuntu0.24.04.1_bpo22.04.1.diff"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2077391/+attachment/5807279/+files/libreoffic
** Attachment added: "prevjournal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2077254/+attachment/5807278/+files/prevjournal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.l
I didn't find any related crash files.
There are plenty of error reports there, those regarding the gnome-shell are:
https://errors.ubuntu.com/oops/4f78c16e-1189-11ee-a2f6-fa163e993415
https://errors.ubuntu.com/oops/0a9dd314-6a71-11ed-b53a-fa163ef35206
https://errors.ubuntu.com/oops/33d15182-3035-1
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2077254/+attachment/5807277/+files/journal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad
Sorry I just remembered the Nvidia 550 driver will be hidden from the
GUI on most systems.
This should get you most of the way:
sudo apt purge nvidia-driver-535
sudo apt install nvidia-driver-550 linux-modules-nvidia-550-generic
libnvidia-egl-wayland1
--
You received this bug notification
Removed tag 'regression-update' because this sounds like it's correlated
with the unusual state of this machine, and could in fact happen in any
gnome-shell update.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** Tags removed: regression-update
--
You received this bug n
80 matches
Mail list logo
