Yes I can see a corresponding .upload and .uploaded file.
Unique ID is: f8601c66-2247-11ef-8ba3-fa163ec8ca8c
--
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/2050865
Title:
GNOME Way
Thanks! Unfortunately the automated system isn't showing enough of the
stack trace to be helpful;
__pthread_kill_implementation (no_tid=0, signo=6, threadid=) at
./nptl/pthread_kill.c:44
__pthread_kill_internal (signo=6, threadid=) at
./nptl/pthread_kill.c:78
__GI___pthread_kill (threadid=, sign
It looks like arm64 is failing tests just because there are some
automated tests trying to use a real GPU (and sometimes failing to get
access to it). That's probably not something we should expect to work
all the time, but it's curious if it worked in the past.
--
You received this bug notificat
Looks like last time autopkgtest worked on arm64 it was because there
was no GPU for it to fail to open. And it would fall back to
"surfaceless" mode for testing. Now there is a GPU on the arm64 test
runner it's giving up when it can't use it.
--
You received this bug notification because you are
Public bug reported:
On Noble, using Gnome (not the Ubuntu desktop) + a few plugins, I had my
desktop completely unresponsive after logging in. The mouse cursor was
still moving, but the hot corner didn't work, nor did the various
keyboard shortcuts. Surprisingly, the Ctrl-Alt-Fn access to console
Public bug reported:
1)
when the cursor stay still things are better (not always) but things go bad
when you move it. It started with 22.04 I think
2)
gnome-shell:
Installed: 45.2-0ubuntu1.1
Candidate: 45.2-0ubuntu1.1
Version table:
*** 45.2-0ubuntu1.1 500
500 http://fr.archive.ub
** Attachment added: "Screenshot from 2024-06-05 09-40-15.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068116/+attachment/5786241/+files/Screenshot%20from%202024-06-05%2009-40-15.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whi
If you have a step-by-step, I'm happy to try and get the information you
need.
--
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/2050865
Title:
GNOME Wayland session crashes with
li
I also can't see anything relevant in the log that's failing. The first
thing to try is without custom extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again. Does the bug still occur?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You
The log mentions "No GPUs found" so it's probably using all the CPU in
order to emulate a GPU...
Please run:
lspci -k > lspci.txt
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
** Changed in: gnome-shell (Ubuntu)
Status: Ne
It sounds like we're only days away from 24.04 automated crash reports
starting to work correctly so I am inclined to wait for that.
--
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/2050
Public bug reported:
Mutter autgopkgtests are failing if a GPU exists but is not accessible.
Surprisingly this only just started becoming a problem recently:
2730s # libmutter-MESSAGE: Running Mutter Test (using mutter 42.9) as a Wayland
display server
2730s libmutter-Message: 13:24:23.050: Runn
Public bug reported:
My system lagging, become slow after installing ubuntu 22.04
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2.1
ProcVersionSignature: Ubuntu 5.15.0-107.117-generic 5.15.149
Uname: Linux 5.15.0-107-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_
Please explain in more detail what is "lagging" and run:
lspci -k > lspci.txt
journalctl -b0 > journal.txt
and attach the resulting text files here.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubunt
Does this mean it's safe to upgrade now (regarding this specific bug),
or does this have to propagate to more places... ?
--
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/2054761
Title:
It's still "phasing" which means you won't get the fix automatically
yet. Please wait...
--
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/2054761
Title:
Dist upgrades from Jammy to No
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3516
https://gitlab.gnome.org/GNOME/mutter/-/issues/3516
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3516
Importance: Unknown
Status: Unknown
** Summary changed:
- Mutter autgopkgtests are
Thank you for the analysis. I've triggered a retest against migration-
reference/0 then. That should reset the baseline and remove the flag.
--
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/b
** Changed in: mutter
Status: Unknown => New
--
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/2068119
Title:
Mutter autopkgtests are failing if a GPU exists but is not accessib
** Attachment added: "prevjournal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068116/+attachment/5786295/+files/prevjournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bug
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068116/+attachment/5786296/+files/journal.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.launch
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068116/+attachment/5786297/+files/lspci.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.launchpad.
This bug was fixed in the package gnome-shell-extension-appindicator -
58-1
---
gnome-shell-extension-appindicator (58-1) unstable; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release to fully support GNOME 46
* appIndicator: Try to introspect the application for
The verification of the Stable Release Update for gnome-shell-extension-
appindicator has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In th
The verification of the Stable Release Update for gnome-shell-extension-
appindicator has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In th
This bug was fixed in the package gnome-shell-extension-appindicator -
58-1
---
gnome-shell-extension-appindicator (58-1) unstable; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release to fully support GNOME 46
* appIndicator: Try to introspect the application for
This bug was fixed in the package gnome-shell-extension-appindicator -
58-1
---
gnome-shell-extension-appindicator (58-1) unstable; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release to fully support GNOME 46
* appIndicator: Try to introspect the application for
The verification of the Stable Release Update for gnome-shell-extension-
appindicator has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In th
** Attachment added: "tecla-azerty-light.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068243/+attachment/5786333/+files/tecla-azerty-light.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubunt
Public bug reported:
Impact
==
GNOME 45 switched their default keyboard layout viewer from libgnomekbd to
tecla. This change was made in gnome-control-center but Debian and Ubuntu
carried a patch to revert this for gnome-shell because gnome-shell wasn't
calling tecla correctly which made th
** Attachment added: "gkbd-azerty-dark.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068243/+attachment/5786334/+files/gkbd-azerty-dark.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
h
** Attachment added: "gkbd-azerty-light.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068243/+attachment/5786335/+files/gkbd-azerty-light.png
** Description changed:
Impact
==
GNOME 45 switched their default keyboard layout viewer from libgnomekbd to
tecla. This
The bug didn't occur after the reboot anyway so I'll keep my extensions.
I do feel like no extension should be able to lock up the shell to the point I
can't even reach the console.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnom
I also had a look at these regressions and noticed that they seem to be
happening on instances in bos03 which is PS6 and has newer hardware than
PS4.5. (We recently completed the transition to PS6.)
I opened a bug 2068053 about for this for my team to investigate it some
more.
--
You received th
@Daniel,
Do I need to file a new LP bug if I encounter the same issue on Noble?
https://gitlab.gnome.org/GNOME/mutter/-/issues/3515
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3515
https://gitlab.gnome.org/GNOME/mutter/-/issues/3515
--
You received this bug notification beca
Yeah absolutely file a new bug!
Even if it feels the same it's probably not the same bug in the source
code.
--
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/2016990
Title:
Irregular
I have the same problem on Ubuntu 24.04 with all updates. But there is a
workaround, as gnome-shell-portal-helper isn't strictly needed.
If you connect to a public wifi which then doesn't allow you to access
the internet, because you didn't accept terms of service and didn't log
in, you can do it
Public bug reported:
Ubuntu 24.04 LTS
gnome-shell-extension-ubuntu-tiling-assistant 46-1ubuntu1
gnome-shell 46.0-0ubuntu5.1
I am at a very stock X11 session with a i915 laptop. I move a firefox
window from my primary monitor to my secondary monitor and make it full
screen.
I am running, I guess,
** Description changed:
Ubuntu 24.04 LTS
gnome-shell-extension-ubuntu-tiling-assistant 46-1ubuntu1
gnome-shell 46.0-0ubuntu5.1
I am at a very stock X11 session with a i915 laptop. I move a firefox
window from my primary monitor to my secondary monitor and make it full
screen.
I
I think Mutter needs fixing here more than changing the hardware config
again to work around it. We can also expect more reliable test results
by using a virtual GPU in future.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
Also tracking upstream in:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7613
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7613
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7613
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/is
Looks like a temporary issue. Your current boot is using high CPU
because the graphics driver has been disabled by being in recovery mode
with the 'nomodeset' kernel parameter. The previous boot doesn't seem to
have had the same problem.
Please reboot and tap Escape after the BIOS logo appears. It
> I do feel like no extension should be able to lock up the shell to the
point I can't even reach the console.
In an ideal world, yes. But such a safe framework does not exist in
gnome-shell right now. Extensions are allowed to do anything, and thus
frequently break anything.
--
You received thi
** Tags added: noble
** Bug watch added: github.com/Leleat/Tiling-Assistant/issues #329
https://github.com/Leleat/Tiling-Assistant/issues/329
** Also affects: gnome-shell-extension-tiling-assistant via
https://github.com/Leleat/Tiling-Assistant/issues/329
Importance: Unknown
Statu
Hey Daniel, good night, thks for the help and the forum link. I solved the
problem with the following steps
1- create script file in this location
nano /usr/local/bin/fechar_anydesk.sh ("fechar" means close)
2- paste the following script
#!/bin/bash
window_id=$(xwininfo -root -tree
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2381
https://gitlab.gnome.org/GNOME/mutter/-/issues/2381
** Changed in: mutter
Status: New => Unknown
** Changed in: mutter
Remote watch: gitlab.gnome.org/GNOME/mutter/-/issues #3516 =>
gitlab.gnome.org/GNOME/mutter/-/issues
If committed in readiness for 42.9-0ubuntu9, but there's no need to
actually release that right now.
https://salsa.debian.org/gnome-
team/mutter/-/commit/9dc8a804dd75f72cecaf938551d8d16044c2b49b
** Changed in: mutter (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received thi
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: gnome-shell-extension-tiling-assistant (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
49 matches
Mail list logo
