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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2027631
Title:
no signal to external monitor from HDMI port
Status in mutter
Thanks for the bug report. Please run:
sudo apt install drm-info
drm_info > drminfo.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a
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
I have exactly the same issue with only the tweeters outputting sound. I
am also using the 2023 model of the G14 (the model with the RTX4090). In
contrast, I use Kubuntu 23.04 as the OS and also installed pipewire (not
pulse audio) in the hopes it does solve my problem.
The command given in
Thanks for the bug report. Next time the screen goes black and after
rebooting, please run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535
(Ubuntu)
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
** Package changed: ubuntu => pulseaudio (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2027641
Title:
whole system has no sound
Status in pulseaudio package in Ubuntu:
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 Desktop
Packages, 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
The attached files show your GPU is detected and the driver is working.
What exactly is the problem you are facing?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
** Changed in: libadwaita-1 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libadwaita-1 in Ubuntu.
https://bugs.launchpad.net/bugs/2018163
Title:
Ctrl+click no longer allows
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:
Hello,
I have a report from an nVidia user that says that WebKitGTK 2.40.3
works fine but after upgrading to 2.41.6 it stops working (but only the
GTK3 builds).
This is all with Debian unstable on an X11 GNOME session:
- (2.40.3-2 => 2.41.6-1) for webkit2gtk-4.0. its MiniBrowser stops working.
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-
** Package changed: ubuntu => xorg (Ubuntu)
--
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/2027631
Title:
no signal to external monitor from HDMI port
Status in xorg package in Ubuntu:
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
There's a difference between "this package is required to allow people
to use our paid services" and "this package spams everyone who doesn't
pay for our paid services". This flies in the face of the whole ethos of
free software imo.
--
You received this bug notification because you are a member
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 Desktop
Packages, which is subscribed to
Public bug reported:
Hello; I hit Control+L to focus the URL bar, then typed:
http://www.debian.org/
This loads a Google search page for http.
I tried again with: https://www.debian.org/
This loaded a Google search page for https.
Typing just: www.debian.org
leads to the expected Debian
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
** Package changed: ubuntu => xorg (Ubuntu)
--
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/2027617
Title:
Can't change build-in display refresh rate
Status in xorg package in Ubuntu:
Thank you very much. Marking the SRU for Jammy as verified ...
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups
Generally the way to do this in Debian at least would be something like
1. move the removed dependencies/recommends to a ubuntu-desktop-legacy
metapackage/seed
2. recommend that so it is installed
3. one cycle later, drop the recommends (or move it to suggests to keep it
installed on upgrades*)
Now I get the following error if I run `apt full-upgrade`:
The following packages have unmet dependencies:
nvidia-dkms-535 : Depends: nvidia-kernel-common-535 (= 535.54.03-0ubuntu1) but
535.54.03-0ubuntu0.22.04.1 is installed
nvidia-driver-535 : Depends: libnvidia-extra-535 (=
Public bug reported:
Hi,
I am trying to setup CUDA on my system. Followed the instructions and
everything seemed to work. Tried nvcc command and it works. After a
reboot, tried to update packages with `apt update && apt full-upgrade`.
The following is the output before I proceeded:
The
It's completely normal for programs to use shared memory segments.
That's why they're there! :) rkhunter reports them because they're
persistent like the filesystem but not really visible, unlike the
filesystem. You have to know to look for them.
rkhunter is a tool for you to use as part of your
19:21:34 packagekitd: uid 1000 obtained auth for
org.freedesktop.packagekit.system-sources-refresh
19:21:34 packagekitd: uid 1000 obtained auth for
org.freedesktop.packagekit.system-sources-refresh
19:21:34 packagekitd: uid 1000 is trying to obtain
Public bug reported:
ubuntu 23.04
I just updated and did a reboot.
bt shows other devices, but I tried removing the one not connecting and it is
gone
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
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
can u tell me what to do clearly
--
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/2026762
Title:
gpu is not deceted
Status in xorg package in Ubuntu:
New
Bug description:
it is not
@vorlon I've installed the 2.4.1op1-1ubuntu4.5 packages from -proposed
and, after correcting the printer configuration with `sudo lpadmin -p
PRINTER -o print-color-mode-default=color` it seems to work well, i.e.
it doesn't revert to monochrome after printing any more. Thanks!
--
You received
** Package changed: ubuntu => xorg (Ubuntu)
--
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/2026762
Title:
gpu is not deceted
Status in xorg package in Ubuntu:
New
Bug description:
** Information type changed from Private Security to Public
--
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/2027552
Title:
package chromium-browser failed to install
Status
** Package changed: ubuntu => pulseaudio (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2027576
Title:
[Precision 5480, Intel Raptorlake-P HDMI, Digital Out, HDMI]
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Desktop
Packages, 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
I can confirm 42.9 did fix 42.8's crash issue. Thank you all.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/2024248
Title:
Update gnome-remote-desktop to 42.9
Status
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: vino (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1883744
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: "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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** 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 Desktop
Packages, 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 Desktop
Packages, 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 Desktop
Packages, 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 libadwaita-1 - 1.3.3-0ubuntu0.23.04.1
---
libadwaita-1 (1.3.3-0ubuntu0.23.04.1) lunar; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release (LP: #2023411):
- tab: Add a default handler to extra-drag-value
- Update Brazilian
This bug was fixed in the package libadwaita-1 - 1.3.3-0ubuntu0.23.04.1
---
libadwaita-1 (1.3.3-0ubuntu0.23.04.1) lunar; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release (LP: #2023411):
- tab: Add a default handler to extra-drag-value
- Update Brazilian
This bug was fixed in the package libadwaita-1 - 1.3.3-0ubuntu0.23.04.1
---
libadwaita-1 (1.3.3-0ubuntu0.23.04.1) lunar; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release (LP: #2023411):
- tab: Add a default handler to extra-drag-value
- Update Brazilian
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
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
I think it's OK to skip Kinetic if you don't want to proceed with it.
However, what are the implications of that severe regression for the QA
process for other releases? Are there QA gaps that could also affect a
release into Jammy, for example? Is it worth investigating the Kinetic
failure
> I never installed gnome; and surely not with snap.
That snap is just poorly named, it doesn't have only Gnome stuff, but
also other snaps' dependencies, including e.g. Chromium.
There is nothing surprising in the fact that it was refreshed though and
as such gives no insight into the
Once again, no, I didn't remove anything, neither manually nor
automatically.
I checked a bit closer, watching the logs of my 'daily routine' as mentioned
above, and today I saw this line in snap refresh:
gnome-3-38-2004 0+git.efb213a from Canonical✓ refreshed
What the heck is this?? I never
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
** Changed in: archlinux
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1838151
Title:
Poor quality audio with modern Bluetooth headsets in HSP/HFP.
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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967707
All autopkgtests for the newly accepted mesa (23.0.4-0ubuntu1~22.04.1) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
gtk4/blacklisted (s390x)
Please visit the excuses page listed below and investigate the failures,
proceeding
All autopkgtests for the newly accepted mesa (23.0.4-0ubuntu1~22.04.1) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
gtk4/blacklisted (s390x)
Please visit the excuses page listed below and investigate the failures,
proceeding
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2026886
Title:
google
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-
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
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)
Indeed the contents of the window (including the black rectangle) are
the responsibility of the primary GPU (AMD) by default. However that
window then gets composited (copied) to the screen and if that screen is
connected to Nvidia like by HDMI then Nvidia is used for that fullscreen
draw.
--
** 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/bugs/2026727
Title:
Clicking on a notification no longer raises
74 matches
Mail list logo
