Thanks for the bug report. When the monitor is plugged into HDMI, please
run:
sudo apt install drm-info
drm_info > drminfo.txt
grep . /sys/class/drm/*/status > connections.txt
and attach the resulting text files here.
It might also be worth testing this in /etc/environment:
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
--
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/2027631
Title:
no signal to external monitor from HDMI port
To manage
Indeed it sounds like a bug that you have to click on a profile after
waking up. If you have to select a profile then it means either:
* There are two different users logged in; or
* Your gnome-shell session crashed during sleep/waking.
So we should check for crashes. Please:
1. Look in
You have been subscribed to a public bug:
On fresh installation of Ubuntu 22.04.2 LTS with and without latest updates
there's no HDMI signal to external monitor. No display , no picture, no
detection at all.
The hardware is functional under Windows the HDMI port is working.
What I've managed
Also strange - your screenshots show corruption which should only be
relevant to mutter and the graphics drivers (kernel / mesa). I cannot
imagine how gnome-shell is related. More like gnome-shell is triggering
a bug in mutter, mesa, the kernel, or Chrome.
On the slight chance this is related to
** Summary changed:
- google chrome hardware acceleration broken on 42.9-0ubuntu2
+ [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2
** Tags added: amdgpu regression-update
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
I think all of those questions are off-topic for this bug so should not
be discussed here. That said...
1. No that's not relevant. It's required to put a picture on the screen.
2. I don't know.
3. Please
That sounds like an important regression, but since this bug is closed
we will need you to open a new one by running:
ubuntu-bug mutter
and add the tag 'regression-update'. Please also attach output from
'drm_info' to the new bug.
--
You received this bug notification because you are a
Following the upstream bug...
Do you have a ~/.config/gtk-4.0/Compose file? If so, please attach it
** Package changed: meta-gnome3 (Ubuntu) => gnome-shell (Ubuntu)
** Also affects: gtk4 (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added:
You have been subscribed to a public bug:
ENV: Ubuntu 22.04.2 LTS on X11, GNOME Shell 42.9
symptom :
gnome-extensions-app crash everytime right at start.
message:
```
/usr/bin/gnome-extensions-app
**
Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table:
assertion failed:
I can reproduced the gnome-control-center crash on Lunar. The crash only
happened when two monitor can't find match resolution. My laptop's
internal display only has one resolution 1920x1200, external monitor's
highest resolution is 1920x1080. When switching to mirror mode in gnome-
Public bug reported:
Ubuntu 22.04.2 LTS
gdm version: 42.0-1ubuntu7.22.04.3
Hi all, minor bug but it is annoying for my ADHD ass.
If I power on my PC, let it boot to ubuntu, and then immediately start
typing my password, it accepts the password without me needing to click
on my profile name at
Please don't subscribe ubuntu-sru to bugs. You can subscribe ubuntu-
sponsors (as was already done here) if you need someone to upload your
work to a stable Ubuntu release.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
This bug was fixed in the package gnome-control-center - 1:44.3-1ubuntu2
---
gnome-control-center (1:44.3-1ubuntu2) mantic; urgency=medium
* Add patch to fix mirror mode crash when resolution of
the 2 monitors don't match (LP: #2026228)
-- Dirk Su Wed, 12 Jul 2023 13:29:55
I have uploaded your patch to Mantic.
When I tested this on Lunar, I was unable to reproduce the crash. I had
set my second monitor to a different screen resolution than the first
but gnome-control-center made the 2 monitors have the same resolution
when I enabled Mirror Mode. Are you able to
** Description changed:
[Impact]
gnome-control-center crashed when switching to mirror mode and monitors don't
have matched resolution
[Test case]
+ Mirror mode is only an option if there are only 2 monitors connected even if
one monitor is disabled. A laptop's internal screen counts
I am closing the Kinetic task. Ubuntu 22.10 "Kinetic" will be End of
Life on July 20 and there is not enough time under normal Stable Release
Update procedures for this fix to land in kinetic-updates before July
20.
** Also affects: gnome-control-center (Ubuntu Jammy)
Importance: Undecided
** Information type changed from Private Security to Public
--
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/2026729
Title:
package evince-common 42.3-0ubuntu3 failed to
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
Sure,I get it.
The work around of using Xorg does not resolve the issue on this setup,
Wayland and Xorg both suffer different problems. Just wanted to call
that out!
Simple open questions:
1. The
Hello Fabio, or anyone else affected,
Accepted mutter into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Daniel, or anyone else affected,
Accepted mutter into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Accepting into Jammy. I can see that the code changes appear already
present in lunar-proposed. Please could you confirm the status of the
fix in lunar-updates please, so we can avoid introducing a regression
when users upgrade?
On test plans, I see both this bug and the other one will be
I was a bit premature with my last comment. If I restart chrome after
re-enabling hardware acceleration, rendering breaks again. So the
overall behavior looks like:
- Start at v42.0 of gnome-shell and gnome-shell-common
- Upgrade to v42.9 of gnome-shell and gnome-shell-common
- Note strange
Thank you for responding so quickly :-)
Danial van Vugt wrote:
> When reporting bugs in the future please use apport by using 'ubuntu-bug' and
> the name of the package affected.
Can do :-)
> Or if you prefer to collect info manually, please run these commands
while the problem is happening
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+attachment/5685720/+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.
** Attachment added: "lscpu.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+attachment/5685719/+files/lscpu.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+attachment/5685718/+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.
** Attachment added: "packages.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+attachment/5685717/+files/packages.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I installed mutter 44.3-0ubuntu1 on Ubuntu 23.04 and verified that these
sessions still work well:
- GNOME
- GNOME Classic
- Ubuntu
- Ubuntu on Xorg
** Tags removed: verification-needed verification-needed-lunar
** Tags added: verification-done verification-done-lunar
--
You received this bug
Yesterday i upgraded mutter:amd64 (42.5-0ubuntu1 to 42.9-0ubuntu1) and
suddenly experienced the problem described in this thread. (black screen
and logs like in #2)
After some investigation and finally finding this bug here adding
MUTTER_DEBUG_USE_KMS_MODIFIERS=0
to
/etc/environment
fixed it for
This bug was fixed in the package gjs - 1.76.2-1~ubuntu23.04.1
---
gjs (1.76.2-1~ubuntu23.04.1) lunar; urgency=medium
* No-change backport to lunar (LP: #2023571)
gjs (1.76.2-1) experimental; urgency=medium
* New upstream release (LP: #2023571)
* Drop all patches: applied in
The verification of the Stable Release Update for gjs 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
the event that you encounter a
Tested version 44.3-0ubuntu1 of libmutter-12-0 on ubuntu budgie.
Test case I substituted settings for budgie-control-center. No
regressions noted.
Checked general window management - max, min, tiling as well as side-by-side
tiling. No regressions. No reported /var/crash type stuff.
Checked
This should fix most cases of the log flood:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3115
** Tags added: logspam
--
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/1967707
Thanks for the bug report. It appears the kernel '5.15.0-1034-intel-
iotg' is too old for the integrated GPU of 'i7-1260P'.
Did you install that kernel manually? Or perhaps install some IOT image
instead of Ubuntu Desktop? I would have expected a fresh install of
Ubuntu Desktop 22.04.2 to come
Was it only downgrading gnome-shell that helped or were you actually
downgrading the mutter packages too?
--
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/2026886
Title:
google
Or if you prefer to collect info manually, please run these commands
while the problem is happening:
lspci -k > lspci.txt
lscpu > lscpu.txt
journalctl -b0 > journal.txt
dpkg -l > packages.txt
and attach the resulting text files here.
--
You received this bug notification because you
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 2026886
When reporting bugs in the future please use apport by using 'ubuntu-
Thanks, I can see you switched to Xorg so the log in comment #5 is no
longer relevant to this bug. Not all freezes have the same cause. What I
can see in that log is the Nvidia driver refusing to support eGPUs at
boot time:
Jul 11 13:19:52 semiauto /usr/libexec/gdm-x-session[1638]: (WW)
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
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/2026727
Title:
Clicking on a notification no longer raises
40 matches
Mail list logo
