I have checked again, and for me the problem is gone (likely due to some
update).
--
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/1974029
Title:
[nvidia] vram memory leak under
I have upgraded mutter to 44.1 from *-proposed repository. I have
restarted my system. "GNOME version" is 44.1 in "Settings" (before
restart it was 44.0). I have worked on the computer for a day after
restart and this memory usage buildup does not occur. Actually, I do
not see "mutter-x11-frames"
Still present in Ubuntu 23.04.
--
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/1974029
Title:
[nvidia] vram memory leak under Wayland
To manage notifications about this bug go to:
24B 24B ?
120 0 1 0 0 0 0B 24B 24B ?
100 0 0 0 0 1 0B 24B 24B ?
080 0 1 0 0 0 0B 24B 24B ?
Best,
Mateusz Łącki
On 3/13/23 02:30, Daniel van Vugt wrote:
> will
Present in 22.10 proper.
--
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/1974029
Title:
[nvidia] vram memory leak under Wayland
To manage notifications about this bug go to:
Still present in 22.10 beta.
--
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/1974029
Title:
[nvidia] vram memory leak under Wayland
To manage notifications about this bug go to:
Hi, this allows me to log in to "Ubuntu on Wayland".
--
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/1992285
Title:
[nvidia] wayland does not start - blank screen with underscore
Public bug reported:
Hi, in 22.10 beta there seem to be several problems with *desktop files
related to the gnome terminal. They cause misbehaviour of the Terminal
application with ubuntu dock.
There are two such files:
/usr/share/applications/org.gnome.Terminal.Preferences.desktop
There is a recent gnome-shell crash that is mine:
https://errors.ubuntu.com/oops/19cbbbc2-4876-11ed-9948-fa163e993415
Other than that nothing related (at least 3 days old)
> MUTTER_DEBUG_FORCE_KMS_MODE=simple
I have tried that and it did not change anything
> Ctrl + Alt + F1
> Ctrl + Alt
Additional information: under novueau the Wayland session starts
properly.
--
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/1992285
Title:
wayland does not start - blank screen with
Public bug reported:
After upgrade to kinetic I can't start Gnome Desktop under Wayland.
Until recent update to the gdm3,trying to start gdm3 with
"WaylandEnable=true" in /var/gdm3/custom.conf lead to blank screen with
non-blinking underscore sign in top left corner of the screen (with x11
gdm3
Today there has been a gdm3 update. There is progress with
"WaylandEnable=true" the gdm3 actually starts, but only "Ubuntu" session
can be logged in "Ubuntu on Wayland" ends on "blinking underscore". This
is still a regression as Wayland used to work on 22.04. Though most
likely this now goes to
and lspci.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1992150/+attachment/5622031/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
The log is from /var/log/syslog but it contains more information than usual as
I have turned on:
[debug]
# Uncomment the line below to turn on debugging
# More verbose logs
# Additionally lets the X server dump core if it crashes
Enable=true
in /etc/gdm3/custom.conf.
I attach both requested
Public bug reported:
After installing 22.10 beta, the gdm3 does not start properly. This
happens only if in /etc/gdm3/custom.conf :
[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false
(...)
The line with WaylandEnable is commented out or set explicitly
Clarification: "They also show up in alsamixer, where I can mute/unmute,
change volume..." but still just "dummy output" is in System settings
and no sound.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
Are there further things I can check? The list of audio devices is what
I have - exactly those 4 devices showed up in 22.04. They also show up
in alsamixer, where I can mute/unmute, change volume...
I usually used an USB sound card (the 1 [G1 ]: USB-Audio - Sound
BlasterX G1) listed in the above
This is the screenshot of the Bluetooth settings menu.
** Attachment added: "Screenshot from 2022-05-04 14-49-39.png"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1971577/+attachment/5586674/+files/Screenshot%20from%202022-05-04%2014-49-39.png
--
You received this bug
Public bug reported:
In "bluetooth" panel of the settings there are connected/presiously
connected devices. In case some one owns multiple devices of same model
it is impossible to distinguish them easily. In practice different
entries are distinguishable by the bluetooth device address.
There
Public bug reported:
The values shown as "memory used" are not really informative. Roughly
speaking
"used" memory (indicated in the tool) = "really used" memory (NOT
indicated in the tool) + "cache" (indicated in the tool) + "available"
(NOT indicated in the tool)
The tool shows the LHS "used
Public bug reported:
I have a 4K monitor. If I open Nautilus window when display is in 1920x1080
resolution, then change the resolution to 3840x2160 AND change "scaling" to
200% then the context menu appears cut.
Changing the resolution and leaving "scaling" at 100% does not trigger the bug.
Public bug reported:
When I click "compress.." from Nautilus, the menu that allows to change
compression format is obscured (screen attached)
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
ii gnome-sushi 41.0-3
Hi,thank you for your reply. Unfortunately there were no crashes in
/var/crash that were related nor there was a "whoopsie". I will try to
reproduce the crash, so far my initial attempts have failed.
Best,Mateusz
On Mon, 2021-05-03 at 13:32 +, Sebastien Bacher wrote:
> Thank you for taking
Public bug reported:
Mounted share (phone) went to sleep (lock screen activated), but the
share was still mounted. I logged in to the phone at almost the same
time when I clicked the mount in nautilus, which caused it to crash.
May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: **
May 3
24 matches
Mail list logo
