[Bug 2042973] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only
Hello, the extensions were already disabled, anyway I can't reproduce the symptoms anymore on a fresh installed system with the same extensions configuration. Will update if the issue comes back somehow. -- 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/2042973 Title: Desktop becomes unusable after changing window from fullscreen games on Wayland Only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042973/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2044190] [NEW] Lockscreen shows black background in user login section
Public bug reported: Unlike my laptop, my desktop, has issues with the lockscreen background, which disappears and goes black after trying to unlock the lockscreen only after the login section (after you click or type something in the screen to put the password) Didn't happen on Ubuntu 23.04 or 22.04 LTS Happens even on a fresh 23.10 install. Wayland session. Tried MUTTER_DEBUG_KMS_THREAD_TYPE=user but did not make any effect. After some tests, it looks like it happens only when a double monitor is used. The second monitor is not affected. Changing the primary monitor for the dock didn't make any effect The monitor having the issue: Gigabyte M27Q 2560x1440 170hz, using Displayport with FreeSync enabled Second monitor, not having the issue: Zowie XL2411Z 1080p with DVI input. There are no other symptoms or useful logs somewhere. The session works fine overall. Disabling the gnome extensions didn't make any effect. Picture attached. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 22:22:19 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-11-19 (2 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "Schermata del 2023-11-21 22-31-05.png" https://bugs.launchpad.net/bugs/2044190/+attachment/5721953/+files/Schermata%20del%202023-11-21%2022-31-05.png -- 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/2044190 Title: Lockscreen shows black background in user login section To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2044190/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923845] Re: Please compress packages with zstd by default
** Changed in: libsolv (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1923845 Title: Please compress packages with zstd by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1923845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
I don't think if that is the same issue, but I tried setting the automatic screen sleep to 1 minute and not always but most of the times I can't login back to the system since it does not wake up. The system is still functional, having nomachine installing and configured trying to login from another computer, I get a successfull connection with no video, since then, the system takes like 4/5 minutes to show a black screen with a cursor first, then the lockscreen and everything works again Ryzen 5 5600 and an AMD RX 7800 XT -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2042973] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only
Trying the following things - Resetting settings to default using dconf reset -f / - Deleting .config .cache .local folder No success But creating a new user profile temporarily solved the problem. In case I saved the old profile. If the issue comes back maybe I can be more specific Cant think of anything else -- 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/2042973 Title: Desktop becomes unusable after changing window from fullscreen games on Wayland Only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042973/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2042874] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only
Trying the following things - Resetting settings to default using dconf reset -f / - Deleting .config .cache .local folder No success But creating a new user profile temporarily solved the problem. In case I saved the old profile. If the issue comes back maybe I can be more specific Cant think of anything else -- 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/2042874 Title: Desktop becomes unusable after changing window from fullscreen games on Wayland Only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042874/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2042973] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only
Hello, tried the workarounds and the proposed packages The issue persists. -- 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/2042973 Title: Desktop becomes unusable after changing window from fullscreen games on Wayland Only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042973/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2042973] [NEW] Desktop becomes unusable after changing window from fullscreen games on Wayland Only
Public bug reported: Description: Ubuntu 23.10 Release: 23.10 gnome-shell 45.0-1ubuntu2 Steps to reproduce: 1)Open certain games (Like An Anime Game Launcher, or Shadow Warrior 2 from steam, both using DXVK) 2)Wait for them to fully load 3)Press the Super button in order to go back to the desktop What should happen: A list of windows, the gnome desktop overview, is shown What happened: All the screen section from above the gnome taskbar became grey like the activity overview accent color and nothing else can be done, the desktop functionality is broken - Since I upgraded from 23.04 to 23.10 the desktop becomes unusable (video attached) 80% of the times when I switch from certain fullscreen games to the desktop using the super button. The gray color of the activity overview is shown above the shell taskbar on both screens and nothing else can be done. - The issue does not happen on an X11 session. - The notifications still work correctly, as clicking the gnome shell bar or even locking and unlocking the screen. - Right clicking and closing apps work. However, only the buttons from the shell itself only - Everything involving actively changing windows does not. - No matter the screen configuration the issue still persist. Tried to upgrade mesa drivers, switching from 2 screens to 1, no luck. No workaround is discovered. Session can be terminated from the taskbar, as it works correctly. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 19:47:42 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-12 (87 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-13 (25 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "Video showing the issue" https://bugs.launchpad.net/bugs/2042973/+attachment/5717019/+files/senza%20titolo.mp4 -- 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/2042973 Title: Desktop becomes unusable after changing window from fullscreen games on Wayland Only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042973/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2042874] Re: Desktop becomes unusable after changing window from fullscreen games on Wayland Only
Good morning, at the moment of writing I have created the apport when I had the mesa PPA installed as an attempt to find if the issue was related to the graphics drivers so that's why the PPA is shown. It is already uninstalled now, as I said still happens, do you need other logs? -- 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/2042874 Title: Desktop becomes unusable after changing window from fullscreen games on Wayland Only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042874/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2042874] [NEW] Desktop becomes unusable after changing window from fullscreen games on Wayland Only
Public bug reported: Description:Ubuntu 23.10 Release:23.10 gnome-shell 45.0-1ubuntu2 Steps to reproduce: 1)Open certain games (Like An Anime Game Launcher, or Shadow Warrior 2 from steam, both using DXVK) 2)Wait for them to fully load 3)Press the Super button in order to go back to the desktop What should happen: A list of windows, the gnome desktop overview, is shown What happened: All the screen section from above the gnome taskbar became grey like the activity overview accent color and nothing else can be done, the desktop functionality is broken - Since I upgraded from 23.04 to 23.10 the desktop becomes unusable (video attached) 80% of the times when I switch from certain fullscreen games to the desktop using the super button. The gray color of the activity overview is shown above the shell taskbar on both screens and nothing else can be done. - The issue does not happen on an X11 session. - The notifications still work correctly, as clicking the gnome shell bar or even locking and unlocking the screen. - Right clicking and closing apps work. However, only the buttons from the shell itself only - Everything involving actively changing windows does not. - No matter the screen configuration the issue still persist. Tried to upgrade mesa drivers, switching from 2 screens to 1, no luck. No workaround is discovered. Session can be terminated from the taskbar, as it works correctly. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 Uname: Linux 6.5.10-x64v4-xanmod1 x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 6 21:43:01 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-12 (86 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-13 (24 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic third-party-packages wayland-session ** Attachment added: "senza titolo.mp4" https://bugs.launchpad.net/bugs/2042874/+attachment/5716578/+files/senza%20titolo.mp4 -- 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/2042874 Title: Desktop becomes unusable after changing window from fullscreen games on Wayland Only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042874/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2018158] [NEW] [Multi Monitor] Built-in screen gets enabled changing the entire layout after resuming from the lockscreen
Public bug reported: Hello, first of all I am not entirely sure where to report this To explain the issue briefly, I have an ASUS TUF F15 laptop and two external monitors connected each to the HDMI and USB-C port with the laptop lid opened but the built-in screen disabled, what happens on the resume from the lock screen (after a couple of minutes, when all the screens go off), the layout gets messed up because the built in screen gets re-enabled automatically, the HDMI screen remains correctly on, but the USB-C screen gets disabled. I may have a clue on why this happens, I have an NVIDIA optimus setup where the Intel iGPU runs the USB-C monitor and the built-in monitor, the HDMI gets managed from the dedicated NVIDIA card so nothing changes here, and somwhow the builtin screen gets disabled then enabled when resuming the system, resulting in GNOME switching to it automatically as you have plugged in a new screen No matter how many times you force the screen disabling it, it will happen again. The workaround is to just to keep closed the laptop lid, of course, but since you can't power it on without the power button is a bit difficult. So I'd just like to keep it open. Another workaround I found is to unload the asus_nb_wmi and asus_wmi kernel modules as I thought they could be the issue, since they manage this specific platform, but as I said before I am not sure what to expect here, is it the intended behavior from GNOME? I mean, it's like someone plugs in some screens then the output gets enabled automatically but that's not the case of course, but the asus_wmi module may do some weird things. What you expected to happen: Resuming from the lock screen with all the screen layout in place What happened instead: Built-in screen enables itself, USB-C monitor gets disabled, HDMI monitor remains the same, the entire screen layout gets changed Workaround: Keeping the laptop lid closed or disabling asus_wmi and asus_nb_wmi kernel modules System affected: Ubuntu: 23.04 Lunar Lobster, tried also Ubuntu 22.04 and a custom flavor (PopOS 22.04) Don't mind the custom kernel, I tried different releases, including: Kernel: 6.2.0-20-generic Custom 6.2.13 and 6.3.0 kernels gnome-shell version: GNOME Shell 44.0 Info: inxi -F System: Host: haru-nb Kernel: 6.3.0-x64v4-xanmod1 arch: x86_64 bits: 64 Desktop: GNOME v: 44.0 Distro: Ubuntu 23.04 (Lunar Lobster) Machine: Type: Laptop System: ASUSTeK product: ASUS TUF Dash F15 FX516PM_FX516PM v: 1.0 serial: Mobo: ASUSTeK model: FX516PM v: 1.0 serial: UEFI: American Megatrends LLC. v: FX516PM.329 date: 02/01/2023 Battery: ID-1: BAT0 charge: 64.0 Wh (98.9%) condition: 64.7/76.0 Wh (85.1%) volts: 15.8 min: 15.8 CPU: Info: quad core model: 11th Gen Intel Core i7-11370H bits: 64 type: MT MCP cache: L2: 5 MiB Speed (MHz): avg: 3001 min/max: 400/4800 cores: 1: 2068 2: 2607 3: 1718 4: 2707 5: 4300 6: 4284 7: 4312 8: 2018 Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] driver: nvidia v: 530.41.03 Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.8 driver: X: loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa dri: iris gpu: i915,nvidia,nvidia-nvswitch resolution: 1: 2560x1440 2: 1920x1080~60Hz 3: N/A API: OpenGL v: 4.6 Mesa 23.0.2 renderer: Mesa Intel Xe Graphics (TGL GT2) Audio: Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: snd_hda_intel Device-2: NVIDIA GA106 High Definition Audio driver: snd_hda_intel Device-3: Thesycon System & Consulting GmbH DX3 Pro type: USB driver: snd-usb-audio Device-4: Logitech Blue Snowball type: USB driver: hid-generic,snd-usb-audio,usbhid Sound API: ALSA v: k6.3.0-x64v4-xanmod1 running: yes Sound Server-1: PipeWire v: 0.3.65 running: yes Network: Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi IF: wlo1 state: up mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eno2 state: down mac: Device-3: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 IF: enx00e04c6928d4 state: down mac: IF-ID-1: virbr0 state: down mac: Bluetooth: Device-1: Intel AX201 Bluetooth type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: bt-v: 3.0 RAID: Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd Drives: Local Storage: total: 8.65 TiB used: 3.51 TiB (40.6%) ID-1: /dev/nvme0n1 vendor: Crucial model: CT4000P3SSD8 size: 3.64 TiB ID-2: /dev/nvme1n1 vendor: SK Hynix model: HFM512GD3JX013N size: 476.94 GiB ID-3: /dev/sda type: USB vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB ID-4: /dev/sdb type: USB vendor: Toshiba model: External USB 3.0 size: 931.51 GiB Partition: ID-1: / size: 198.66 GiB used: 133.69 GiB (67.3%) fs: ext4 dev: /dev/nvme1n1p5 ID-2: /boot/efi size: 298.8 MiB used: 91.1 MiB (30.5%) fs: vfat dev:
[Bug 1999167] [NEW] Backport two patches from the GTK 4.6 maintenance branch
Public bug reported: This is a request to update the libgtk-4-1 package to include two important patches merged upstream into the gtk-4-6 stable branch: * https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4714 * https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5288 See https://gitlab.gnome.org/GNOME/gtk/-/issues/2638#note_1612970 Thanks! ** Affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Tags: patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1999167 Title: Backport two patches from the GTK 4.6 maintenance branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1999167/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971044] Re: The bookmark function doesn't work and doesn't work the session registration
*** This bug is a duplicate of bug 1969896 *** https://bugs.launchpad.net/bugs/1969896 ** This bug has been marked a duplicate of bug 1969896 Evince Document Viewer(42.0) does not remember last page in 22.04 -- 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/1971044 Title: The bookmark function doesn't work and doesn't work the session registration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1971044/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971044] Re: The bookmark function doesn't work and doesn't work the session registration
** Summary changed: - The bookmark function doesn't work and doesn't work the session registration + The bookmark function doesn't work and doesn't work the session registration -- 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/1971044 Title: The bookmark function doesn't work and doesn't work the session registration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1971044/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971044] [NEW] The bookmark function doesn't work and doesn't work the session registration
Public bug reported: The bookmark function doesn't work (the keys "plus" and "minus" are grey in color and are unclickable) and when i close and reopen the application it doesn't re-enter on the page of the closed session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-28.29-generic 5.15.35 Uname: Linux 5.15.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 30 15:23:27 2022 InstallationDate: Installed on 2021-12-30 (121 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- 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/1971044 Title: The bookmark function doesn't work and doesn't work the session registration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1971044/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Fixed also in systemd v250.4 and v249.11 -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1928161] Re: Wacom Tablet Map Buttons blank on Wayland
I find the same behavior shown in the screenshot. Steps to reproduce the bug: 1. Connect my wacom tablet (by bluetooth). 2. Open "Settings"-"Wacom Tablet". 3. Select "Tablet". 4. Click on "Map Buttons..." button. The behavior I expected. Something that would allow me to configure the behavior of the buttons on the tablet The behavior I encounter every time I repeat the previous steps. A screen as in the attached screenshot appears, where is it not clear how I can configure anything. Clicking on the tablet button does not have any visible effect, pressing "Esc" does not allow to exit the screen. The only way I found to exit from this situation is to switch off the tablet: I could not find how to get out by pressing any key or clicking anywhere. In this situation I cannot execute the suggested apport-collect command because I cannot do anything useful until I switch off the tablet. Would it still be useful if I execute it whwn the screen of the screenshot is not active? My tablet is different from the one mentioned in the bug (Wacom Intuos BT S) but the behavior is the same. Should I open a new bug? I can add that I find the same behavior under Wayland and under X, however the consequences of the bug are worse in Wayland because in X I can configure the buttons using a script based on xsetwacom. Is there any additional information I can add to help debug the issue? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1928161 Title: Wacom Tablet Map Buttons blank on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1928161/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38
Hello tested package: gnome-shell version: 3.38.4-1ubuntu3~21.04.1 Machine: Lenovo ThinkPad T430 root@TP-T430:~# uname -r 5.11.0-18-generic root@TP-T430:~# apt-cache policy gnome-shell| grep Install Installato: 3.38.4-1ubuntu3~21.04.1 steps undertaken to test: 1. Log into GNOME. 2. Press Super+A 3. Click on 'Files' and wait till it has launched. 4. Press the Super key. Expected: Can interact with the application window. Result: I can interact with the system as expected. This release fixed the bug for me. Thanks! -- 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/1922353 Title: Overview sometimes fails to appear or disappear in gnome-shell 3.38 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922353/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1921598] [NEW] opened windows extend behind dock after screen unlock
Public bug reported: Hi all, after last gnome-shell-extension-ubuntu-dock update (69ubuntu1), after screen unlock, all opened and maximize windows extend behind the dock. Restoring window size and then maximized again solve the problem. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell-extension-ubuntu-dock 69ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 27 22:47:36 2021 InstallationDate: Installed on 2021-03-23 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute uec-images wayland-session ** Attachment added: "after_screen_unlock.png" https://bugs.launchpad.net/bugs/1921598/+attachment/5481494/+files/after_screen_unlock.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1921598 Title: opened windows extend behind dock after screen unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1921598/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1919960] [NEW] windows showed over applications grid when show-app-button clicked
Public bug reported: Hi all, clicking on show-apps-button in the dock shows applications grid behind opened windows. Using the shortcut Super+A, applications grid is displayed correctly hiding windows. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 18 07:03:29 2021 InstallationDate: Installed on 2021-03-17 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session ** Attachment added: "show-apps.png" https://bugs.launchpad.net/bugs/1919960/+attachment/5477751/+files/show-apps.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1919960 Title: windows showed over applications grid when show-app-button clicked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1919960/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
Hi Mauricio, unfortunately I've upgraded to Focal Fossa since then and the bug is not present in this version of Ubuntu. -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1891771] Re: gdm3 crashes after upgrade from bionic to focal but lightdm and sddm work fine
Hello Daniel, here you can find the link: https://errors.ubuntu.com/user/a0bccc0d41c89b42afbe332929a7f00566720fe2fcfc8f4ca657778404328e77f704f6088efe855865488a2f9635243b26b54e543fe6e58c26f7de6c73d1df8c Thanks, Luca On Mon, Aug 17, 2020 at 5:55 AM Daniel van Vugt <1891...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It sounds like some part of the system has crashed. To > help us find the cause of the crash please follow these steps: > > 1. Look in /var/crash for crash files and if found run: > ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. > > 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us. > > 3. If step 2 also failed then apply the workaround from bug 994921, > reboot, reproduce the crash, and retry step 1. > > Please take care to avoid attaching .crash files to bugs as we are > unable to process them as file attachments. It would also be a security > risk for yourself. > > > ** Changed in: gdm3 (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1891771 > > Title: > gdm3 crashes after upgrade from bionic to focal but lightdm and sddm > work fine > > Status in gdm3 package in Ubuntu: > Incomplete > > Bug description: > Hi all, > > after upgrading from bionic to focal I switched from lightdm to gdm3 > to use Gnome Desktop. > > Gdm3 crashes systematically when enabled as default display-manager > with a blank display with the following message: > > Oh no! Something has gone wrong. > A problem has occurred and the system can't recover. Please contact a > system administrator. > > In /etc/gdm3/custom.conf I've tried the following settings: > > WaylandEnable=false -> crash > WaylandEnable=true-> crash > > I've enabled Debug but I cannot find any correlation with the error > message. > > Gdm version 3.34.1-1ubuntu1. > > Switching to another display manager like lightdm or sddm solves the > problem. > I've a Dell Inspiron with Intel U620 graphic card. > The problems happens with the laptop display alone but also with > external monitor connected via HDMI. > > Thanks in advance for your help. > > Regards > Luca > dpkg > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gdm3 3.34.1-1ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.6 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sat Aug 15 23:06:37 2020 > InstallationDate: Installed on 2016-12-14 (1340 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > SourcePackage: gdm3 > UpgradeStatus: Upgraded to focal on 2020-08-11 (4 days ago) > mtime.conffile..etc.gdm3.custom.conf: 2020-08-15T00:22:27.116452 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1891771/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1891771 Title: gdm3 crashes after upgrade from bionic to focal but lightdm and sddm work fine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1891771/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1891771] [NEW] gdm3 crashes after upgrade from bionic to focal but lightdm and sddm work fine
Public bug reported: Hi all, after upgrading from bionic to focal I switched from lightdm to gdm3 to use Gnome Desktop. Gdm3 crashes systematically when enabled as default display-manager with a blank display with the following message: Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please contact a system administrator. In /etc/gdm3/custom.conf I've tried the following settings: WaylandEnable=false -> crash WaylandEnable=true-> crash I've enabled Debug but I cannot find any correlation with the error message. Gdm version 3.34.1-1ubuntu1. Switching to another display manager like lightdm or sddm solves the problem. I've a Dell Inspiron with Intel U620 graphic card. The problems happens with the laptop display alone but also with external monitor connected via HDMI. Thanks in advance for your help. Regards Luca dpkg ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 23:06:37 2020 InstallationDate: Installed on 2016-12-14 (1340 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-08-11 (4 days ago) mtime.conffile..etc.gdm3.custom.conf: 2020-08-15T00:22:27.116452 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1891771 Title: gdm3 crashes after upgrade from bionic to focal but lightdm and sddm work fine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1891771/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
Marcello, your workaround does indeed work because Xu and Lu flavours use a window manager other than Mutter in Gnome. I myself had to revert back to Unity. -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
I am on Ubuntu FF 20.04 using office 2010 via wine-stable 5.0, my system is fully updated. The issue still persists when I am copying and pasting any text within word 2010, with an interesting twist. Copying and pasting works most of the times, but when I copy a portion of text within Word 2010 using ctrl+C then delete it and try paste it, it always fails. As if by deleting the text I just copied from the page I would also delete its copy in the clipboard. When I am in Unity (yeah, I still love and use Unity, even on 20.04) everything works as intended: you copy a portion of the text and can always paste it, no matter what you do to the original text. Hope this helps, this bug is so very annoying. -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)
Happens to me as well on FF 20.04 using Word 2010, both on X11 and Wayland. If I switch back to Unity the bug is gone -- 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/1852183 Title: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1878469] Re: Corrupt background and some corrupt icons
Thank you Daniel: what I should do to solve the issue? On Thu, May 14, 2020 at 10:41 AM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > ** Summary changed: > > - Ubuntu 20.04 causing green vertical stripes on my desktop > + Corrupt background and some corrupt icons > > ** Summary changed: > > - Corrupt background and some corrupt icons > + Corrupt background and some corrupt icons [Intel Coffee Lake] > > ** Also affects: mutter (Ubuntu) >Importance: Undecided >Status: New > > ** Also affects: gnome-shell (Ubuntu) >Importance: Undecided >Status: New > > ** No longer affects: xorg-server (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1878469 > > Title: > Corrupt background and some corrupt icons [Intel Coffee Lake] > > Status in gnome-shell package in Ubuntu: > New > Status in mutter package in Ubuntu: > New > > Bug description: > As soon as I upgraded to Ubuntu 20.04, two green pixel stripes appeared > on my desktop. > They do not interfere with windows when opened, whether they are > browsers, files or other items, and they do not seem to have an impact on > the general behavior of the PC. > > Still, something tells me that they are not supposed to be there. > > I have a dual boot, Windows and Ubuntu, and two drivers: > > VGA compatbile controller: Intel UHD Graphics 630 (mobile) > 3D controller: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] > > Any support would be welcome. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-31.35-lowlatency 5.4.34 > Uname: Linux 5.4.0-31-lowlatency x86_64 > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed May 13 18:55:14 2020 > DistUpgraded: 2020-05-13 13:02:22,581 DEBUG icon theme changed, > re-reading > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 > [VGA controller]) > Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] > InstallationDate: Installed on 2018-12-23 (506 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. > Fingerprint Reader >Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications >Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Dell Inc. XPS 15 9570 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-lowlatency > root=UUID=d49b534b-1745-4089-80d9-cb11f85d2570 ro acpi=force > nvidia.NVreg_EnableBacklightHandler=1 > SourcePackage: xorg > UpgradeStatus: Upgraded to focal on 2020-05-13 (0 days ago) > dmi.bios.date: 12/25/2019 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.15.0 > dmi.board.name: 0D0T05 > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: XPS > dmi.product.name: XPS 15 9570 > dmi.product.sku: 087C > dmi.sys.vendor: Dell Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878469/+subscriptions > -- 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/1878469 Title: Corrupt background and some corrupt icons [Intel Coffee Lake] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878547] [NEW] quit 2 windows not localized
Public bug reported: If I have more than 1 application windows open, the 'quit 2 windows' command is not localized (not in italian at least). See attachemnt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 09:01:14 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-08 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1878547 Title: quit 2 windows not localized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878547/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878547] Re: quit 2 windows not localized
strings not localized ** Attachment added: "attachement" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878547/+attachment/5371340/+files/Schermata%20del%202020-05-14%2009-01-01.png -- 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/1878547 Title: quit 2 windows not localized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878547/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872822] [NEW] opening utilities folder has strange behavior
Public bug reported: Dear All, in a fresh install of Ubuntu 20.04 beta: luca@blpcfl1:~$ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 luca@blpcfl1:~$ apt-cache policy gnome-shell gnome-shell: Installato: 3.36.1-4ubuntu1 Candidato: 3.36.1-4ubuntu1 Tabella versione: *** 3.36.1-4ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status What Expected: After opening and closing utilities folder (showed as X-GNOME-Utilities.directory) in the Application list, the Applications list is showed as before. What happen: After opening and closing utilities folder in the Applications list, the Applications list disappeared (or tiny) (picture 3 in the attached png) and pages dots are incremented by n. The frequently applications are tiny (picture 4) and returning to all Applications page, pages dots are incremented by n (picture 5). Best regards, Luca ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 22:32:09 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-05 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "bug-gnome-shell-utilities.png" https://bugs.launchpad.net/bugs/1872822/+attachment/5354147/+files/bug-gnome-shell-utilities.png -- 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/1872822 Title: opening utilities folder has strange behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827428] Re: Mouse cursor left frozen copy of itself
This also occurs in Fedora 32 and Xfce 4.14 for me. -- 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/1827428 Title: Mouse cursor left frozen copy of itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 956120] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a()
I got this issue today on Ubuntu 18.04.3. -- 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/956120 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/956120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833098] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from _st_theme_node_ensure_background() from st_theme_node_pain
*** This bug is a duplicate of bug 1788429 *** https://bugs.launchpad.net/bugs/1788429 It happened to me on 18.04, randomly during normal office working session. -- 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/1833098 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from _st_theme_node_ensure_background() from st_theme_node_paint_equal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833098/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718135] Re: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers()
I have experienced this bug in a clean 18.04.3 install. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1718135 Title: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers() To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1718135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
I can't. If I click it I get "You do not have permission to nominate this bug." since I'm not a maintainer of this package. -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
Hi Daniel, thanks for your prompt reply. Good to see that this problem is fixed in future versions of Ubuntu. Indeed it would be nice to see it in 18.04, I'm not a member of the project therefore I can't do "Nominate for series" but I hope someone does nominate it as the issue seems relatively small and improves performance/avoid a crash. -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838152] [NEW] gnome-shell freezes on notification arrival (fixed upstream)
Public bug reported: Sometimes certain notifications make the desktop unresponsive for a few seconds and then gnome-shell crashes and all extensions are reloaded. I have found an upstream bug with a patch, but it's probably not in the Ubuntu's package. I thought of creating an issue in case it is something not known. https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 https://gitlab.gnome.org/GNOME/gnome- shell/commit/86a00b6872375a266449beee1ea6d5e94f1ebbcb In my case it happens only with the notifications of gsconnect and maybe android studio. I have reproduced the problem in gsconnect in case it helps. https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/549 the error is: lug 27 19:55:56 ghv gnome-shell[4071]: Object Meta.Background (0x55ce6b4cf300), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Ubuntu 18.04 gnome-shell Version: 3.28.4-0ubuntu18.04.1 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: crash gnome-shell notifications -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1602900] Re: libzmq3 crashes when 'getifaddrs()' is unavailable
Fixed since Bionic ** Changed in: zeromq3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1602900 Title: libzmq3 crashes when 'getifaddrs()' is unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ipython/+bug/1602900/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1834762] Re: Screen locks after timeout with hidraw input
** Description changed: As the title says, when using the hidraw as input method, used by game controllers in games in Steam big picture mode especially, is not being detected by the gnome desktop, and so if you are playing a game using hidraw only, the screen timeout will come out, and the session will be blocked Steps to reproduce: - Open a game - Play a game with a controller using hidraw as input, such as the RPCS3 emulator - - The gnome-screenshot timeout will kick in and lock the session even when actively playing, as long no mouse or keyboard is used + - The gnome-screensaver timeout will kick in and lock the session even when actively playing, as long no mouse or keyboard is used What should happen - Hidraw should be detected in the same way a mouse or keyboard does I have NOT tested with a game using native evdev My config is: Steam + steam-devices packages installed, the steam devices has some rules for hidraw to be correctly working with my controller. I own a PS4 controller connected via bluetooth, but the same should happen on USB as well I used the RPCS3 emulator, which so far supports only hidraw as input method. ** Description changed: As the title says, when using the hidraw as input method, used by game controllers in games in Steam big picture mode especially, is not being detected by the gnome desktop, and so if you are playing a game using hidraw only, the screen timeout will come out, and the session will be blocked Steps to reproduce: - Open a game - Play a game with a controller using hidraw as input, such as the RPCS3 emulator - The gnome-screensaver timeout will kick in and lock the session even when actively playing, as long no mouse or keyboard is used What should happen - Hidraw should be detected in the same way a mouse or keyboard does I have NOT tested with a game using native evdev My config is: - Steam + steam-devices packages installed, the steam devices has some rules for hidraw to be correctly working with my controller. + Steam + steam-devices packages installed, the steam-devices package has some udev rules for hidraw to be correctly working with this controller. I own a PS4 controller connected via bluetooth, but the same should happen on USB as well I used the RPCS3 emulator, which so far supports only hidraw as input method. ** Description changed: - As the title says, when using the hidraw as input method, used by game + As the title says, when using hidraw as input method, used by game controllers in games in Steam big picture mode especially, is not being detected by the gnome desktop, and so if you are playing a game using - hidraw only, the screen timeout will come out, and the session will be - blocked + hidraw only, the blank screen and/or lock timeout will come out, and the + session will be blocked or the screen will become blank Steps to reproduce: - Open a game - Play a game with a controller using hidraw as input, such as the RPCS3 emulator - The gnome-screensaver timeout will kick in and lock the session even when actively playing, as long no mouse or keyboard is used What should happen - Hidraw should be detected in the same way a mouse or keyboard does I have NOT tested with a game using native evdev My config is: Steam + steam-devices packages installed, the steam-devices package has some udev rules for hidraw to be correctly working with this controller. I own a PS4 controller connected via bluetooth, but the same should happen on USB as well I used the RPCS3 emulator, which so far supports only hidraw as input method. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1834762 Title: Screen locks after timeout with hidraw input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1834762/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1834762] [NEW] Screen locks after timeout with hidraw input
Public bug reported: As the title says, when using the hidraw as input method, used by game controllers in games in Steam big picture mode especially, is not being detected by the gnome desktop, and so if you are playing a game using hidraw only, the screen timeout will come out, and the session will be blocked Steps to reproduce: - Open a game - Play a game with a controller using hidraw as input, such as the RPCS3 emulator - The gnome-screensaver timeout will kick in and lock the session even when actively playing, as long no mouse or keyboard is used What should happen - Hidraw should be detected in the same way a mouse or keyboard does I have NOT tested with a game using native evdev My config is: Steam + steam-devices packages installed, the steam devices has some rules for hidraw to be correctly working with my controller. I own a PS4 controller connected via bluetooth, but the same should happen on USB as well I used the RPCS3 emulator, which so far supports only hidraw as input method. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Description changed: As the title says, when using the hidraw as input method, used by game - controllers in games like Steam especially, is not being detected by the - gnome desktop, and so if you are playing a game using hidraw with the - controller, the screen timeout will come out, and the session will be + controllers in games in Steam big picture mode especially, is not being + detected by the gnome desktop, and so if you are playing a game using + hidraw only, the screen timeout will come out, and the session will be blocked Steps to reproduce: - Open a game - Play a game with a controller using hidraw as input, such as the RPCS3 emulator - The gnome-screenshot timeout will kick in and lock the session even when actively playing, as long no mouse or keyboard is used What should happen - Hidraw should be detected in the same way a mouse or keyboard does I have NOT tested with a game using native evdev My config is: Steam + steam-devices packages installed, the steam devices has some rules for hidraw to be correctly working with my controller. I own a PS4 controller connected via bluetooth, but the same should happen on USB as well I used the RPCS3 emulator, which so far supports only hidraw as input method. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1834762 Title: Screen locks after timeout with hidraw input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1834762/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Hi, in debian testing this does not happen, neither in debian unstable or other distros with the same gnome-shell package version I confirm it's a regression from 18.10 to 19.04 In 18.10 it works fine -- 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/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823544] Re: Unreasonable NVIDIA GPU VRAM usage on gnome-shell
Yes but the amount of time I kept in the first test was not the same, I just do not have enough time to test In the first one my PC was up for almost a day unlike the second scenario where the uptime was just 1h and a couple of minutes -- 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/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823544] Re: Unreasonable NVIDIA GPU VRAM usage on gnome-shell
Ok, fine I uninstalled any non-official GNOME extension and in cold start I'm getting after 1.2h of uptime 200MB more than the normal, I am not 100% sure but I think this still persist Cold start: +-+ | NVIDIA-SMI 418.56 Driver Version: 418.56 CUDA Version: 10.1 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GTX 106... Off | :1C:00.0 On | N/A | | 51% 30CP028W / 120W |225MiB / 3011MiB | 0% Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| |0 1501 G /usr/lib/xorg/Xorg18MiB | |0 1559 G /usr/bin/gnome-shell 49MiB | |0 2017 G /usr/lib/xorg/Xorg44MiB | |0 2154 G /usr/bin/gnome-shell 109MiB | +-+ 1.2h of uptime Mon Apr 8 13:53:34 2019 +-+ | NVIDIA-SMI 418.56 Driver Version: 418.56 CUDA Version: 10.1 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GTX 106... Off | :1C:00.0 On | N/A | | 55% 33CP8 9W / 120W |447MiB / 3011MiB | 0% Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| |0 1501 G /usr/lib/xorg/Xorg18MiB | |0 1559 G /usr/bin/gnome-shell 49MiB | |0 2017 G /usr/lib/xorg/Xorg 124MiB | |0 2154 G /usr/bin/gnome-shell 204MiB | |0 7639 G ...quest-channel-token=920471993479850461346MiB | +-+ -- 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/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823544] Re: Unreasonable NVIDIA GPU VRAM usage on gnome-shell
apport information ** Tags added: apport-collected ** Description changed: GPU: NVIDIA GTX 1060 3GB Ubuntu: 19.04, Kernel Linux luky-pc 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux NVIDIA driver version: 418.56 Display settings: BenQ XL2411Z, 144Hz monitor, 1920x1080p I have noticed this strange behavior only on gnome-shell where the overall gnome-shell desktop VRAM usage was taking up to 1GB of GPU VRAM which does not happen on other desktops, or on Windows, happens after some hours of normal desktop usage Even the system RAM increases a lot during normal usage, but remains acceptable This behaviour can be observed by using "nvidia-smi" a tool from the NVIDIA proprietary driver gnome-shell VRAM usage on a cold start: 139MB, + 9 MB X.org VRAM usage on cold start: 48MB + 18MB Total: 214MB gnome-shell VRAM usage after some hours of normal usage: 445MB + 83 MB X.org VRAM usage after some hours of normal usage: 244MB + 18MB Total: 800MB On windows or other desktops the GPU VRAM usage remains the same + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu25 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 19.04 + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 3.32.0-1ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=it_IT.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 + Tags: disco + Uname: Linux 5.0.0-8-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1823544/+attachment/5254040/+files/Dependencies.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.net/bugs/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823544] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1823544/+attachment/5254042/+files/ProcCpuinfoMinimal.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.net/bugs/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823544] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1823544/+attachment/5254041/+files/GsettingsChanges.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.net/bugs/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823544] [NEW] Unreasonable NVIDIA GPU VRAM usage on gnome-shell
Public bug reported: GPU: NVIDIA GTX 1060 3GB Ubuntu: 19.04, Kernel Linux luky-pc 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux NVIDIA driver version: 418.56 Display settings: BenQ XL2411Z, 144Hz monitor, 1920x1080p I have noticed this strange behavior only on gnome-shell where the overall gnome-shell desktop VRAM usage was taking up to 1GB of GPU VRAM which does not happen on other desktops, or on Windows, happens after some hours of normal desktop usage Even the system RAM increases a lot during normal usage, but remains acceptable This behaviour can be observed by using "nvidia-smi" a tool from the NVIDIA proprietary driver gnome-shell VRAM usage on a cold start: 139MB, + 9 MB X.org VRAM usage on cold start: 48MB + 18MB Total: 214MB gnome-shell VRAM usage after some hours of normal usage: 445MB + 83 MB X.org VRAM usage after some hours of normal usage: 244MB + 18MB Total: 800MB On windows or other desktops the GPU VRAM usage remains the same ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "vram usage after some hours" https://bugs.launchpad.net/bugs/1823544/+attachment/5253737/+files/aftersomehours.png -- 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/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823544] Re: Unreasonable NVIDIA GPU VRAM usage on gnome-shell
vram usage on fresh start ** Attachment added: "freshstart.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+attachment/5253738/+files/freshstart.png -- 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/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Okay, it's fine anyway I tested 18.10 again as well with another distribution with roughly the same packages and I was not able to reproduce the issue I'll try Debian testing -- 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/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 I never had this issue until the 19.04 update, I always used the NVIDIA proprietary driver. In Ubuntu 18.10 is working fine, so I suppose is some sort of regression... I'm curious to try this on another distribution. -- 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/1576859 Title: [nvidia] Graphics corruption when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Hi Daniel, I've seen you marked my bug as this duplicate, but for me this doesn't happen on Ubuntu 18.10, only after the 19.04 upgrade -- 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/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Hi, I don't know if that's correct because in Ubuntu 18.10 I had no issue, I will provide more information once I'll get on my PC -- 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/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1811531] Re: remote execution vulnerability
** Description changed: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. + + [1] https://github.com/zeromq/libzmq/issues/3351 ** Bug watch added: Debian Bug tracker #919098 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919098 ** Also affects: zeromq3 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919098 Importance: Unknown Status: Unknown ** Bug watch added: bugzilla.opensuse.org/ #1121717 https://bugzilla.opensuse.org/show_bug.cgi?id=1121717 ** Also affects: zeromq (Suse) via https://bugzilla.opensuse.org/show_bug.cgi?id=1121717 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790010] Re: Cursor reverts to default size and theme after login, when hovering over certain parts of the UI
*** This bug is a duplicate of bug 1700085 *** https://bugs.launchpad.net/bugs/1700085 I believe it's incorrect to mark this bug as a duplicate of bug #1700085. In fact, in bug #1700085, the user puts a lot of effort to get hidpi scaling and, even if he succeds in that, he is not able to make the cursor scale as well. So, the cursor doesn't scale at all. Concerning this bug (which affects me literally in the same way), gnome is scaling everything automatically, no action is needed and everything looks beautiful out of the box. The only (small) problem is that, immediately after login, if you move the cursor over the top or the left bars, its size go back to the default and it becomes very small. So, while the cursor is on the desktop the size is scaled properly, as soon as you move on the bars, it goes back to the default size. As soon as you click on something that triggers the cursor to switch to the "wait circle" (for instance, Firefox or any other application), some magic happens and the cursor size is scaled properly even on the top and left bars. -- 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/1790010 Title: Cursor reverts to default size and theme after login, when hovering over certain parts of the UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1790010/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790010] Re: Cursor reverts to default size and theme after login, when hovering over certain parts of the UI
** This bug is no longer a duplicate of bug 1700085 Mouse cursor is tiny on HiDPI screens -- 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/1790010 Title: Cursor reverts to default size and theme after login, when hovering over certain parts of the UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1790010/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1801320] [NEW] new icons on desktop should appear on primary display
Public bug reported: Have ubuntu 18.04 with communitheme Ubuntu is running on laptop (on my left side) while I have my external monitor in front of me (so on right side of the laptop), and primary desktop is on external monitor. If I create a new file on desktop the icon is aligned on left side is considering both screens, it should be aligned on left side only considering primary display. ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1801320 Title: new icons on desktop should appear on primary display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1801320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)
Can be the same issue as https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1800465 Only happening with GDM in ubuntu 18.04 with updated nvidia drivers and ubuntu 18.10 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1769857 Title: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1793152] [NEW] No feedback when I format a voume from Nautilus
Public bug reported: Ubuntu 18.04.1 - Communitheme installed If I have to format a Volume (in my case an external usb 750GB hard drive with secure erasing flag on) I have no feedback about the process, the window simply disappear. Good to have some progressing feedback since could be a long process ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Sep 18 15:57:42 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'322' b'org.gnome.nautilus.window-state' b'geometry' b"'1026x550+2367+244'" InstallationDate: Installed on 2018-05-08 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: synology-cloud-station 4.2.6-4408 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1793152 Title: No feedback when I format a voume from Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1793152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754674] [NEW] nautilus crashes on unzip attempt
Public bug reported: 1) Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) nautilus: Installed: 1:3.26.2-0ubuntu3.1 Candidate: 1:3.26.2-0ubuntu3.1 Version table: *** 1:3.26.2-0ubuntu3.1 500 3) After a double click on a zip file, I expect to see archive manager opening that file 4) After a double click on a zip file, the nautilus window disappeared and no unzipped file is available Notes: - I can unzip the file from CLI without issues. The problem is also present with right-click and selecting 'Open With Archive Manager'. - I have updated to Bionic from Ubuntu 17.10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri Mar 9 15:24:24 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'166' b'org.gnome.nautilus.window-state' b'geometry' b"'898x651+26+23'" b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" InstallationDate: Installed on 2017-10-22 (137 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1754674 Title: nautilus crashes on unzip attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1623792] Re: possible sigbus
The fix was released in version 4.2.0 last year and is available in Ubuntu since Zesty. ** Changed in: zeromq3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1623792 Title: possible sigbus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1623792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718253] Re: dependency mismatch in libzmq3-dev and libzmq5-dev for Xenial
libzmq5-dev is a virtual package. libzmq5 is the correct dependency, and it is in Xenial: https://packages.ubuntu.com/xenial/libzmq5 ** Changed in: zeromq3 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1718253 Title: dependency mismatch in libzmq3-dev and libzmq5-dev for Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1718253/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1732204] Re: Totem could not get a screenshot of the video
Thanks for comment. I have already reported above as duplicate in https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/comments/9 > This isn't news, the reason is likely described here & due to the use of > gstreamer1.0-vaapi plugin > https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/comments/3 > (- videos not supported by the gst vaapi plugin will get screenshots -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1732204 Title: Totem could not get a screenshot of the video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1732204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721248] Re: Totem could not get a screenshot of the video
I have the same issue: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1732204 When I opened the bug, Launchpad didn't show me this one, so I made a new one. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1721248 Title: Totem could not get a screenshot of the video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1732204] Re: Totem could not get a screenshot of the video
I have fully upgraded the system and the problem persists. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1732204 Title: Totem could not get a screenshot of the video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1732204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1732204] [NEW] Totem could not get a screenshot of the video
Public bug reported: 1) Ubuntu 17.10 2) totem 3.26.0-0ubuntu1 3) I have selected 'Take screenshot' option and I expected to get a screenshot of the video in the pictures folder 4) I got an error message, a pop-up showing 'Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report.' and no screenshot available in 'Pictures' folder ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 15:46:44 2017 InstallationDate: Installed on 2017-10-22 (22 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1732204 Title: Totem could not get a screenshot of the video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1732204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1690336] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
Public bug reported: bug ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed May 10 18:56:29 2017 DuplicateSignature: package:gconf2-common:3.2.6-3ubuntu7 Setting up gconf2-common (3.2.6-3ubuntu7) ... dpkg: error processing package gconf2-common (--configure): subprocess installed post-installation script was killed by signal (Terminated) ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2017-05-10 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1690336 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1690336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1684100] Re: TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on 16.10
The workaround fixes it for me too. Other wifi adapters I have (one using rt73usb, the other rtl8812au) don't need it, so maybe the bug lies in athk9_htc. How did you find the workaround? (just curious, apart from this bug my google searches only gave me outdated or irrelevant information). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-nettool in Ubuntu. https://bugs.launchpad.net/bugs/1684100 Title: TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/1684100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1648538] [NEW] Custom keyboard shortcuts not work
Public bug reported: 1) Description: Ubuntu 16.04.1 LTS Release: 16.04 2) ubuntu-settings: Installed: 15.10.8 Candidate: 15.10.8 Version table: *** 15.10.8 500 500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status 3) I made some custom keyboard shortcuts under All Settings > Keyboard > Shortcuts In particular, I made these: CTRL+SHIFT+S - Custom screenshot - gnome-screenshot -f "$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png" CTRL+SHIFT+A - Custom screenshot area - gnome-screenshot -a -f "$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png" CTRL+SHIFT+W - Custom screenshot window - gnome-screenshot -w -f "$HOME/Pictures/Screenshots/$(date +%F_%H:%M:%S).png" I expected the shortcuts working when I press the right keys combination. 4) Custom keyboard shortcuts not work. The shortcuts worked only one time and after never worked. If I use the commands directly in a terminal window, the commands work fine. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-settings-daemon (Ubuntu) => ubuntu-settings (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1648538 Title: Custom keyboard shortcuts not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1648538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1598246] [NEW] package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: il sottoprocesso installato script di post-installation è stato terminato dal segnale (Ucciso)
Public bug reported: I faced it while starting the Unity Desktop environment ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shared-mime-info 1.5-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Jul 1 18:51:54 2016 ErrorMessage: il sottoprocesso installato script di post-installation è stato terminato dal segnale (Ucciso) InstallationDate: Installed on 2016-05-15 (47 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: il sottoprocesso installato script di post-installation è stato terminato dal segnale (Ucciso) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1598246 Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: il sottoprocesso installato script di post-installation è stato terminato dal segnale (Ucciso) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1598246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 245716] Re: file-roller puts temporary files in the home dir instead of /tmp
Very annoying... file-roller 3.20.2-1 on Arch Linux. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/245716 Title: file-roller puts temporary files in the home dir instead of /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/245716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1071759] Re: File-roller can't create new archives in mounted samba/ftp shares
I have the same problem. I guess that file-roller il looking at the wrong locations, as I pointed out here https://github.com/linuxmint/nemo/issues/1085 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1071759 Title: File-roller can't create new archives in mounted samba/ftp shares To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1071759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1445595] Re: Empty trash from Launcher results in Nautilus window opening
Still problem today. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1445595 Title: Empty trash from Launcher results in Nautilus window opening To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1445595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1489632] Re: gedit fails to display line with > 1000000 characters
I tested it and the display bug occurs at 466034 characters and more, and selecting the text doesn't work anymore with lower character counts. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1489632 Title: gedit fails to display line with > 100 characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1489632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1131321] Re: Emptying Rubbish bin open a nautilus view in addition of the confirmation dialog
I have the same bug on 2 different machine both with Ubuntu 15.04. Right click > Empty Bin > A Nautilus 'Home' window is open. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1131321 Title: Emptying Rubbish bin open a nautilus view in addition of the confirmation dialog To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1131321/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1400079] [NEW] Bluetooth not working on Asus X751LA
Public bug reported: This bug is associated with launchpad's question #257206. Since the question did not receive any useful answer, I thought to scale up the issue. In order to be 100% sure, since I made several tests for another problem I have with the touchpad, I reinstalled entirely the whole system, so now I'm running a fresh install of Ubuntu 14.04 on the mentioned notebook. The Notebook is equipped with a Qualcomm Atheros, the wifi is working fine - at least so it appears to me. The bluetooth app is not able to activate the bluetooth. I installed blueman, and through it I could switch on the bluetooth (at least it says it is on); however when I do a search. it cannot detect any remote device. Moreover, although I set the device as visible, it does not show up on other devices scanner. Hcitool seems to detect the local device: $ hcitool dev Devices: hci054:27:1E:51:63:DE However it does not detect remote devices: $ sudo hcitool scan Scanning ... $ (this was after I set my phone as discoverable). The kill list is clear: $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 3: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 4: hci0: Bluetooth Soft blocked: no Hard blocked: no $ lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 This is the version of blueman I installed, while hcitool came with the ubuntu install: $ apt-cache policy blueman blueman: Installed: 1.23-git201403102151-1ubuntu1 Candidate: 1.23-git201403102151-1ubuntu1 Version table: *** 1.23-git201403102151-1ubuntu1 0 500 http://rs.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 7 14:10:43 2014 InstallationDate: Installed on 2014-11-27 (10 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) KernLog: SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1400079 Title: Bluetooth not working on Asus X751LA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1400079/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1390628] Re: Mouse pointer invisible after upgrade to Ubuntu 14.10
Replacing gnome-setings-daemon with unity-settings-daemon seems to fix this too. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1390628 Title: Mouse pointer invisible after upgrade to Ubuntu 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1390628/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1390628] Re: Mouse pointer invisible after upgrade to Ubuntu 14.10
And also brings back function keys (brightness, volumen) that didn't work when using gnome-settiings-daemon. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1390628 Title: Mouse pointer invisible after upgrade to Ubuntu 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1390628/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1386186] Re: Screen locking issue - account with no password set
Captain analysis is correct, but this is a bug anyway. You cannot ask for a non-existent password. This is a problem in a multi-user system, where different policies may be applied to different users. For example, user A is password-protected while user B is not. Options above are enabled. With current behaviour, user B can't log in. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1386186 Title: Screen locking issue - account with no password set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1386186/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1386186] Re: Screen locking issue - account with no password set
This also affects Ubuntu 14.10 with a fresh install. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1386186 Title: Screen locking issue - account with no password set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1386186/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1040412] Re: Ubuntu reporting error while using bleachBit
** Package changed: bleachbit (Ubuntu) = gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1040412 Title: Ubuntu reporting error while using bleachBit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1040412/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247370] [NEW] Gedit launched from terminal : Gtk-CRITICAL **: gtk_window_set_default: assertion `gtk_widget_get_can_default (default_widget)' failed
Public bug reported: I launch gedit from terminal and it shows: (gedit:11995): Gtk-CRITICAL **: gtk_window_set_default: assertion `gtk_widget_get_can_default (default_widget)' failed if I open a file: (gedit:12698): Gtk-CRITICAL **: gtk_container_remove: assertion `gtk_widget_get_parent (widget) == GTK_WIDGET (container) || GTK_IS_ASSISTANT (container)' failed if I click file open ... on show of file picker: (gedit:12698): Gtk-CRITICAL **: gtk_tree_selection_get_selected: assertion `GTK_IS_TREE_SELECTION (selection)' failed After i do it at first time, no more error messages are spammed. If i close and i re-open, same story. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sat Nov 2 12:34:12 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1247370 Title: Gedit launched from terminal : Gtk-CRITICAL **: gtk_window_set_default: assertion `gtk_widget_get_can_default (default_widget)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1247370/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1244638] Re: Terminal in gedit is uneditable
Sorry, my mistake. The terminal bg color and text was same so i can't see anything. Terminal works, it is only that i can't see nothing :). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1244638 Title: Terminal in gedit is uneditable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1244638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1244638] [NEW] Terminal in gedit is uneditable
Public bug reported: Terminal doesn't work. I can't write anything in terminal windows embedded in gedit. I tried to change directory by using righ-click contextual menu but it doesn't work. I can't write any commands in embedded window terminal. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.5 Architecture: amd64 Date: Fri Oct 25 14:21:18 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug precise running-unity ** Changed in: gedit (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1244638 Title: Terminal in gedit is uneditable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1244638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1243646] [NEW] Crash of OpenJDK running Eclipse in gtk_widget_queue_draw
Public bug reported: Eclipse Kepler frequently crashes after upgrade to Ubuntu 13.10. Environment is KDE on Ubuntu. Seems to crash in different situations, but not deterministically reproducible. Sorry if I selected the wrong package, I'm just guessing. I have many dumps but all seem to refer to the same problematic frame: [libgtk-x11-2.0.so.0+0x262a43] gtk_widget_queue_draw+0x23. ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Attachment added: Dump of the crash. https://bugs.launchpad.net/bugs/1243646/+attachment/3888463/+files/hs_err_pid6044.log ** Package changed: openjdk-6 (Ubuntu) = gtk+2.0 (Ubuntu) ** Description changed: - Eclipse frequently crashes after upgrade to Ubuntu 13.10. Environment is KDE on Ubuntu. Seems to crash in different situations, but not deterministically reproducible. Crash might be due to a crash of OpenJDK in a native library. Sorry if I selected the wrong package, I'm just guessing. + Eclipse frequently crashes after upgrade to Ubuntu 13.10. Environment is KDE on Ubuntu. Seems to crash in different situations, but not deterministically reproducible. Crash might be due to a crash outside OpenJDK in a native library. Sorry if I selected the wrong package, I'm just guessing. I have many dumps but all seem to refer to the same problematic frame: [libgtk-x11-2.0.so.0+0x262a43] gtk_widget_queue_draw+0x23. ** Description changed: - Eclipse frequently crashes after upgrade to Ubuntu 13.10. Environment is KDE on Ubuntu. Seems to crash in different situations, but not deterministically reproducible. Crash might be due to a crash outside OpenJDK in a native library. Sorry if I selected the wrong package, I'm just guessing. + Eclipse frequently crashes after upgrade to Ubuntu 13.10. Environment is KDE on Ubuntu. Seems to crash in different situations, but not deterministically reproducible. Sorry if I selected the wrong package, I'm just guessing. I have many dumps but all seem to refer to the same problematic frame: [libgtk-x11-2.0.so.0+0x262a43] gtk_widget_queue_draw+0x23. ** Description changed: - Eclipse frequently crashes after upgrade to Ubuntu 13.10. Environment is KDE on Ubuntu. Seems to crash in different situations, but not deterministically reproducible. Sorry if I selected the wrong package, I'm just guessing. + Eclipse Kepler frequently crashes after upgrade to Ubuntu 13.10. Environment is KDE on Ubuntu. Seems to crash in different situations, but not deterministically reproducible. Sorry if I selected the wrong package, I'm just guessing. I have many dumps but all seem to refer to the same problematic frame: [libgtk-x11-2.0.so.0+0x262a43] gtk_widget_queue_draw+0x23. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1243646 Title: Crash of OpenJDK running Eclipse in gtk_widget_queue_draw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1243646/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 973295] Re: Enable grilo plugin
Good job Florian! ;-) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/973295 Title: Enable grilo plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/973295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 217892] Re: gdm with x11vnc not honoring KillInitClients
** Package changed: libvncserver (Ubuntu) = x11vnc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/217892 Title: gdm with x11vnc not honoring KillInitClients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/217892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1043336] Re: Swiss keyboard layout with Apple keyboard (period instead of comma)
For a temporary layout switch fix: echo 0 | sudo tee /sys/module/hid_apple/parameters/iso_layout for a definitive fix, insert into /etc/modprobe.d/hid_apple.conf: options hid_apple iso_layout=0 ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1043336 Title: Swiss keyboard layout with Apple keyboard (period instead of comma) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1043336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1048059] Re: Adding ACLs to /media/$user does not work
I have the same problem: ubuntu in sd card in live mode cant' mount the hard disk. Pleas fix this bug! Thanx!! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1048059 Title: Adding ACLs to /media/$user does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1048059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 986358] Re: No maximize button on Appearance settings Window after un-maximizing it
This bug should no loger exists: all windows in gnome-control-center cannot be maximized and they never appear as maximized. ** Changed in: gnome-control-center (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/986358 Title: No maximize button on Appearance settings Window after un-maximizing it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/986358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1003671] Re: [soundnua]: Internal sound card (HDA ATI SB) not showed in Sound Input
Here too, sorry for the lag, I'll add relevant info to other bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1003671 Title: [soundnua]: Internal sound card (HDA ATI SB) not showed in Sound Input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1003671/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1003671] Re: [soundnua]: Internal sound card (HDA ATI SB) not showed in Sound Input
David, yes it's the internal microphone/input (Realtek ALC889 on MSI 790GX-G65 motherboard). Pulseaudio seems unaffected to me, see attached out `pactl list`, and nothing changes plugging headphone jacks. ** Attachment added: On same system, running Sound setting inside GNOME Session (in Italian, sorry) https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1003671/+attachment/3161618/+files/audio-gnome-with-internal.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1003671 Title: [soundnua]: Internal sound card (HDA ATI SB) not showed in Sound Input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1003671/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1003671] [NEW] Internal sound card (HDA ATI SB) not showed in Sound Input
Public bug reported: As in summary, opening Sound settings and going to Input tab, there are no entries in Record sound from list related to internal sound card. The sound card is recognized by alsa and pulseaudio (info attached) and curiously it appears starting gnome-control-center within GNOME Shell session (i.e. starting the upstream Sound capplet). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 23 23:13:43 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120327.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hw-specific precise regression-release -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1003671 Title: Internal sound card (HDA ATI SB) not showed in Sound Input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1003671/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1003671] Re: Internal sound card (HDA ATI SB) not showed in Sound Input
** Attachment added: Sound settings screenshot, no internal sound card listed https://bugs.launchpad.net/bugs/1003671/+attachment/3160102/+files/no-internal-sound-card.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1003671 Title: Internal sound card (HDA ATI SB) not showed in Sound Input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1003671/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1003671] Re: Internal sound card (HDA ATI SB) not showed in Sound Input
** Attachment added: Output for `amixer` https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1003671/+attachment/3160104/+files/amixer.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1003671 Title: Internal sound card (HDA ATI SB) not showed in Sound Input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1003671/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1003671] Re: Internal sound card (HDA ATI SB) not showed in Sound Input
** Attachment added: Output for `pactl list` https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1003671/+attachment/3160105/+files/pactl-list.txt ** Tags added: hw-specific regression-release -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1003671 Title: Internal sound card (HDA ATI SB) not showed in Sound Input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1003671/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1003671] Re: Internal sound card (HDA ATI SB) not showed in Sound Input
** Tags added: soundnua -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1003671 Title: Internal sound card (HDA ATI SB) not showed in Sound Input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1003671/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1001490] [NEW] No beep for sticky, slow, and bounce keys features
Public bug reported: It seems there is no audio feedback (beep) to assist in typing with a11y features enabled. The audio file to play (bell named sound) is installed (both ubuntu and freedesktop sound themes). ## Steps to reproduce 1) Open System Settings Universal Access 2) Go to Typing tab 3) Turn ON Slow Keys switch 4) Activate Beep when a key is ... accepted 5) Focus test text entry and press (and hold) a key on keyboard ## Expected result The systems should beep when the key press is accepted and the letter appears on screen ## Current result No sound ## Additional info *Same issue for other beep related options in Styky, Slow and Bound keys. * It seems a Ubuntu only issue, 'cause the same feature in Fedora 17 works fine (and it seems there are no special differences between Fedora's and Ubuntu's a11y/sound related values for GSettings keys). * Release: 12.04 * Package version: 3.4.1-0ubuntu1.1 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.4.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sat May 19 01:08:18 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120327.1) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1001490 Title: No beep for sticky, slow, and bounce keys features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1001490/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1001490] Re: No beep for sticky, slow, and bounce keys features
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1001490 Title: No beep for sticky, slow, and bounce keys features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1001490/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1001490] Re: No beep for sticky, slow, and bounce keys features
** Tags added: a11y -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1001490 Title: No beep for sticky, slow, and bounce keys features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1001490/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 424499] Re: rhythmbox does not set IM status in empathy
@octavio: you're right! :) OT: does anybody get context plugin working in Precise? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/424499 Title: rhythmbox does not set IM status in empathy To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/424499/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
