Thanks! Sounds like this change in mutter 42.7:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2734
So a workaround might be to add MUTTER_DEBUG_SEND_KMS_MODIFIERS=1 to
/etc/environment
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug
Indeed your machine has no integrated GPU so the 'prime-select' command
can do nothing on your machine.
If you want to change Nvidia profiles then please open the Nvidia
Settings app instead.
** Package changed: ubuntu => nvidia-prime (Ubuntu)
** Changed in: nvidia-prime (Ubuntu)
Status:
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
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/2026886
XMir is no longer supported.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1263365
Title:
Losing the
Might be a Wayland bug after all:
jul 17 06:49:40 X1-carbon gnome-shell[3140]: XWAYLAND: mode -1x-1 is not
available
... is the recurring error message (between lots of "thunderbird[3569]:
Couldn't map window 0x7f4cbe67ab20 as subsurface because its parent is
not mapped." and other processes
I think "This was a regression introduced by Intel in 42.9!" should be
removed from the changelog. It's not something I wrote in the patch or
in the merge proposal.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
I think:
> This was a regression introduced by Intel in 42.9!
should be removed from the changelog. It's not something I wrote in the
patch or in the merge proposal.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
I don't think it's appropriate my name is mentioned as the creator of
the update itself:
https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu3
Although I am the author of the individual patches, I do not endorse
some of the wording used in the changelog, or the fact that we're now
retesting
Tested with laptop 202211-30793 which only has 1920x1200 for internal
display. Install stock 22.04 iso image and update gnome-control-center
1:41.7-0ubuntu0.22.04.7 from jammy-proposed. Connected DUT with external
monitor which had resolution 1920x1080. Open gnome-control-center,
switch to Display
Tested with laptop 202211-30793 which only has 1920x1200 for internal
display. Install stock 23.04 iso image and update gnome-control-center
1:44.0-1ubuntu6 from lunar-proposed. Connected DUT with external monitor
which had resolution 1920x1080. Open gnome-control-center, switch to
Display panel
Public bug reported:
many sys-links and cannot update
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: python3-speechd (not installed)
ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-46-generic x86_64
Architecture: amd64
CasperMD5CheckResult: pass
Tried using apport-collect to provide more information but, as both
Firefox and Chromium don't currently work when Xwayland is active, I
decided to add the output of dmidecode, in the hope of providing
something useful.
** Attachment added: "dmidecode-i915-wayland.txt"
Public bug reported:
Firefox and emacs not working with i915 driver and XWayland combination.
System can be used OK if take login-time option to use X rather than
Wayland.
System is a Dell (Desktop) Inspiron 530s
** Affects: libreoffice (Ubuntu)
Importance: Undecided
Status: New
The --reinstall did the trick here. Without, it said, it was there, blabla,
nothing happening.
I guess the --reinstall drew in the necessary dependencies in order to not just
being happy.
Thanks for the comment; it feels good to know that I wasn't fantasizing
stuff.
--
You received this bug
In lunar / 23.04, there is no linux-objects-nvidia-535-6.2.0-25-generic
package, but the linux-image-6.2.0-25-generic package has been available
for some time. Package upgrades therefore insist on switching to nvidia-
dkms, no matter what I try to do. So I'm still on 6.2.0-24.
Is this just
This happened to me in recent days. I did routine updates to ubuntu
22.04 and the next time I went to boot the system chromium was not
working. the icon was still on the launcher bar, but it would just spin
loading for 15 or so seconds and do nothing. I started "chromium-
browser" from a terminal
Public bug reported:
It takes around 3 to 4 seconds to launch even post start-up launching.
Other snaps are snappy !
No logs indicate any errors or warnings.
** Affects: libreoffice (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are
** Description changed:
[Impact]
* LibreOffice 7.5.5 is in its fifth bugfix release of the 7.5 line:
https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.5_release
- * Version 7.5.4 is currently released in lunar. For a list of fixed bugs
compared to 7.5.4 see the list of
The only fix found is--
shutdown > unplug the charger > remove the batt > reset the CMOS mem by
holding the powerbotton for around 10 to 15 sec > replug batt > boot to
ubuntu > plug charger.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Tried a live session using Ventoy and Mantic Minotaur daily build 2 days
back. It was having kernel 6.3. The volume issue didn't go away. Thought
using the latest build with a new kernel would help.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Same issue with Vivobook x505za, the report while battery is charging.
$ upower -i /org/freedesktop/UPower/devices/battery_BAT0
native-path: BAT0
vendor: ASUSTeK
model:ASUS Battery
power supply: yes
updated: Sunday 16 July
23 matches
Mail list logo
