[Bug 1072421] Re: Auto-login enabled at installation can't be disabled in Users Control Panel
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/1072421 Title: Auto-login enabled at installation can't be disabled in Users Control Panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1072421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1072421] Re: Auto-login enabled at installation can't be disabled in Users Control Panel
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Expired -- 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/1072421 Title: Auto-login enabled at installation can't be disabled in Users Control Panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1072421/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876839] Re: File-Roller continues as it has done for years to crash
This applies to ARJ format. RAR works, but has a problem after extraction 'show files' cant find directory. -- 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/1876839 Title: File-Roller continues as it has done for years to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1876839/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876837] Re: New lock screen gets stuck on the desktop after unlocking
** Summary changed: - Impossible to unlock if was blocked before unlock default keyring + New lock screen gets stuck on the desktop after unlocking ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2446 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2446 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2446 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Committed ** Tags added: fixed-in-3-36.2 fixed-upstream -- 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/1876837 Title: New lock screen gets stuck on the desktop after unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876835] Re: black screen before login on 5.4 kernel
Please try removing 'splash' from your kernel command line and tell us if that solves it. ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- 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/1876835 Title: black screen before login on 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1876835/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876837] Re: Impossible to unlock if was blocked before unlock default keyring
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- 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/1876837 Title: New lock screen gets stuck on the desktop after unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768603] Re: All review score averages are 5 Stars - 1 Star reviews show as 5 Star
https://github.com/shimmerproject/elementary-xfce/issues/117 ** Bug watch added: github.com/shimmerproject/elementary-xfce/issues #117 https://github.com/shimmerproject/elementary-xfce/issues/117 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1768603 Title: All review score averages are 5 Stars - 1 Star reviews show as 5 Star To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768603/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768603] Re: All review score averages are 5 Stars - 1 Star reviews show as 5 Star
** Changed in: gnome-software (Ubuntu) Status: Opinion => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1768603 Title: All review score averages are 5 Stars - 1 Star reviews show as 5 Star To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768603/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876802] Re: Gnome (on Xorg) crashes when disconnecting external monitor
** Tags added: 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/1876802 Title: Gnome (on Xorg) crashes when disconnecting external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876787] Re: Keyboard Shortcuts didn't working.
Please run this command (again): apport-collect 1876787 ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1876787 Title: Keyboard Shortcuts didn't working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876787/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876787] [NEW] Keyboard Shortcuts didn't working.
You have been subscribed to a public bug: Addded the "Super + 2", "Super + 3" and "Super + 4" commands to switch to the 2,3,and 4 Workspaces and it's not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic 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: Mon May 4 15:17:49 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [104d:908a] InstallationDate: Installed on 2020-04-24 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Sony Corporation VPCEG15FB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=f4a823e2-8306-4dcc-a6bc-c34ec67ae110 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2012 dmi.bios.vendor: INSYDE dmi.bios.version: R0240Z8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR0240Z8:bd01/06/2012:svnSonyCorporation:pnVPCEG15FB:pvrC902GW09:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCEG15FB dmi.product.sku: N/A dmi.product.version: C902GW09 dmi.sys.vendor: Sony Corporation 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 N/A 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 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Keyboard Shortcuts didn't working. https://bugs.launchpad.net/bugs/1876787 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876719] Re: The application folders are very buggy
*** This bug is a duplicate of bug 1870847 *** https://bugs.launchpad.net/bugs/1870847 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1870847, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1870847 App grid has too many page dots on right -- 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/1876719 Title: The application folders are very buggy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876719/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876719] Re: The application folders are very buggy
*** This bug is a duplicate of bug 1870847 *** https://bugs.launchpad.net/bugs/1870847 You seem to be describing multiple issues. Please open new bugs for those other issues. -- 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/1876719 Title: The application folders are very buggy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876719/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876722] Re: launcher fails to recognise applications referred in external media .desktop file
** Package changed: xorg (Ubuntu) => gnome-shell (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/1876722 Title: launcher fails to recognise applications referred in external media .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876722/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876706] Re: TILEd monitor not getting full res
mutter 3.36.2 fixes tiled monitor support for Wayland, but looking at that fix it also seems to share code with X11. So maybe that will help here too. Please wait till 3.36.2 is released as an update and then if the problem is still not fixed please open a new bug at: https://gitlab.gnome.org/GNOME/mutter/issues ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1876706 Title: TILEd monitor not getting full res To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1876706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
There is no fix right now. It will take time. Please come back in a few days/weeks. ** Summary changed: - [nvidia] Screen scaling 125% gives 200%, and sometimes extends off screen + [nvidia] Screen scaling 125% gives 200% -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876722] [NEW] launcher fails to recognise applications referred in external media .desktop file
You have been subscribed to a public bug: Ubuntu 20.04 fails to show shortcut icons in the launcher when .desktop file have applications pointing at external drive which is “always connected and mounted”. The screen capture below present you the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic 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: Mon May 4 18:20:54 2020 DistUpgraded: 2020-04-29 01:20:49,020 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:2211] InstallationDate: Installed on 2020-04-28 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Hewlett-Packard HP 250 G3 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=3c3bd88e-55df-4054-b631-c30ca6ffef19 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (5 days ago) dmi.bios.date: 06/13/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.47:bd06/13/2019:svnHewlett-Packard:pnHP250G3NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=CON B=HP S=PAV dmi.product.name: HP 250 G3 Notebook PC dmi.product.sku: J7V52PA#ACJ dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard 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 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ui ux -- launcher fails to recognise applications referred in external media .desktop file https://bugs.launchpad.net/bugs/1876722 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%, and sometimes extends off screen
I just upgrade these following packages an hour ago but the issue seem to be not fixed: linux-headers-5.4.0-26 linux-headers-5.4.0-26-generic linux-image-5.4.0-26-generic linux-modules-5.4.0-26-generic linux-modules-extra-5.4.0-26-generic linux-modules-nvidia-440-5.4.0-26-generic As you can see, we have linux-modules-nvidia-440 package in that list. -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200%, and sometimes extends off screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875285] Re: Ubuntu 20.04 Fractional scaling crops half the screen
Duplicate bug 1876530 shows it can happen on an Intel-only system too. ** Summary changed: - [nvidia] Ubuntu 20.04 Fractional scaling crops half the screen + Ubuntu 20.04 Fractional scaling crops half the screen ** This bug is no longer a duplicate of bug 1870736 [nvidia] Screen scaling 125% gives 200%, and sometimes extends off screen ** Changed in: mutter (Ubuntu) Status: Incomplete => Confirmed -- 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/1875285 Title: Ubuntu 20.04 Fractional scaling crops half the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876530] Re: Screen scales to grandma very unfriendly mode
*** This bug is a duplicate of bug 1875285 *** https://bugs.launchpad.net/bugs/1875285 Thanks. That shows the same issue as bug 1875285 I think. And I've now generalized bug 1870736 to cover it so we can use that. -- 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/1876530 Title: Screen scales to grandma very unfriendly mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1876530/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876530] Re: Screen scales to grandma very unfriendly mode
*** This bug is a duplicate of bug 1875285 *** https://bugs.launchpad.net/bugs/1875285 Now tracking in bug 1875285. ** This bug has been marked a duplicate of bug 1875285 Ubuntu 20.04 Fractional scaling crops half the screen -- 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/1876530 Title: Screen scales to grandma very unfriendly mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1876530/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876706] [NEW] TILEd monitor not getting full res
You have been subscribed to a public bug: I have an LG 34WK95U monitor which appears to be tiled using two diplay port interfaces connect over thunderbolt. I'm unable to get ubuntu to drive the monitor at it's full 5120x2160@60 resolution. Manually I can force it to 5120x2160@30, but by default Ubuntu gives me 3440x1440@60. I've been researching what the problem might be, my findings so far are collected in these two questions on askubuntu https://askubuntu.com/questions/1233284/tiled-monitor-support-lg-34wk95u https://askubuntu.com/questions/1230124/high-res-monitor-support-5120x2160-lg-34wk95 I've tried switching my laptop gpu from NVidia to the built-in Intel, but the problem persists. The monitor worked in Windows before I wiped the laptop to install Ubuntu. So I'm stuck with the conclusion that there is a bug somewhere at a lower layer preventing this from working since none of the things I've tested have worked. Ideally this should of course have worked out of the box as on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 4 12:33:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0906] Subsystem: Dell TU117GLM [Quadro T2000 Mobile / Max-Q] [1028:0906] InstallationDate: Installed on 2020-04-24 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 5540 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0FMYX6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd12/25/2019:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn0FMYX6:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5540 dmi.product.sku: 0906 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- TILEd monitor not getting full res https://bugs.launchpad.net/bugs/1876706 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876524] Re: Applications only maximize to use the overlapping area between monitors
Thanks. xrandr.txt seems to show no overlapping area in the current configuration. So if it only happens when you change the layout does the bug persist between reboots? And what if you delete the whole config (~/.config/monitors.xml) and recreate it? Does the problem go away? ** Summary changed: - Issue after repositioning display/monitor location usiing display settings + Applications only maximize to use the overlapping area between monitors ** Summary changed: - Applications only maximize to use the overlapping area between monitors + Issue after repositioning display/monitor location using display settings ** Tags added: nvidia ** Summary changed: - Issue after repositioning display/monitor location using display settings + [nvidia] Issue after repositioning display/monitor location using display settings -- 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/1876524 Title: [nvidia] Issue after repositioning display/monitor location using display settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1876524/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%, and sometimes extends off screen
** Summary changed: - [nvidia] Screen scaling 125% gives 200% + [nvidia] Screen scaling 125% gives 200%, and sometimes extends off screen -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200%, and sometimes extends off screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] Re: [nvidia] fractional monitor scaling fails due to overlapping monitors
Kind of. I think this bug should stay separate because it seems to have a clear cause: gnome-control-c[6913]: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors overlap that's not the same as bug 1873403 which happens even on single monitor systems. Although we should ideally fix the simpler case (bug 1873403) first, and then we might find that also fixes this bug. It's complicated and I am still confused. It will probably take a few weeks to sort out. This bug can stay open in the mean time. -- 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/1869042 Title: [nvidia] fractional monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870847] Re: App grid has too many page dots on right
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Confirmed ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Low -- 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/1870847 Title: App grid has too many page dots on right To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875285] Re: [nvidia] Ubuntu 20.04 Fractional scaling crops half the screen
*** This bug is a duplicate of bug 1870736 *** https://bugs.launchpad.net/bugs/1870736 Thanks. That (comment #7) looks closely related to bug 1870736. So I will mark this as a duplicate of that for now. If it turns out to be different after bug 1870736 is fixed then we can reopen this. ** This bug has been marked a duplicate of bug 1870736 [nvidia] Screen scaling 125% gives 200% -- 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/1875285 Title: [nvidia] Ubuntu 20.04 Fractional scaling crops half the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876839] [NEW] File-Roller continues as it has done for years to crash
Public bug reported: Ive been using FR for many years it gets totally out of sync when there are several thousand files. This has been reported as a bug by many others as well. Today I selected dropbox folder and tried running FR in bash but there were no error report, the messagebox showed compressing 13,500 files then crash after a minute. However if I use bash command: alistair@alsE590:~/Dropbox$ arj a -r myfiles.arj * arc is created properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: file-roller 3.36.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue May 5 13:32:28 2020 InstallationDate: Installed on 2020-01-23 (103 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file-roller (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 file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1876839 Title: File-Roller continues as it has done for years to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1876839/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868520] Re: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2
** Summary changed: - Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784) [DRM_FORMAT_XRGB2101010] + Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010]) -- 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/1868520 Title: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010]) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1868520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876594] Re: totem doesn't start on Wayland: Error 71 (Error de protocolo) dispatching to Wayland display
*** This bug is a duplicate of bug 1868520 *** https://bugs.launchpad.net/bugs/1868520 I just had to double-check that because it's a different format to what's in the other bug. The error here is: failed to import supplied dmabufs: Unsupported buffer format 808665665 and 808665665 (decimal) translates to ASCII "AB30" which is DRM_FORMAT_ABGR2101010. So yes it is another deep-colour issue similar to bug 1868520. Probably the same bug. -- 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/1876594 Title: totem doesn't start on Wayland: Error 71 (Error de protocolo) dispatching to Wayland display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1876594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870847] Re: App grid has too many page dots on right
I disabled the Ubuntu Dock extension using the Gnome Extensions app and tried to reproduce the bug, and the bug didn't happen anymore. When I installed the Dash to Dock extension by the Gnome Extensions site, and tried to reproduce the error, nothing wrong happened. I think that the bug is caused by the dock, and the version 68 of Dash to Dock fixed this bug. The Ubuntu dock is still in version 67. -- 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/1870847 Title: App grid has too many page dots on right To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876837] [NEW] Impossible to unlock if was blocked before unlock default keyring
Public bug reported: Steps: 1 - Enable automatic login and the option to turn off screen after X minutes, in gnome settings. 2 - Reboot 3 - DON'T type password when its asked for unlock default-keyring, just wait the time to auto lock screen (x minutes). 4 - move mouse or type keyboard. It will show login/lock screen. Then: Expected: After 4, if you type the correct password, the screen is supposed to be unlocked. What really happens: After the successfully login, the gnome-panel is showed, but the lock screen doesn't hide. See a screenshot (actually, a photo): https://photos.app.goo.gl/RiquTpkvM3hbZbDGA Description:Ubuntu 20.04 LTS Release:20.04 gdm3: Instalado: 3.34.1-1ubuntu1 Candidato: 3.34.1-1ubuntu1 Tabela de versão: *** 3.34.1-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 21:50:05 2020 InstallationDate: Installed on 2020-04-29 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2020-05-04T21:40:02.807077 ** Affects: gdm3 (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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1876837 Title: Impossible to unlock if was blocked before unlock default keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1876837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876835] [NEW] black screen before login on 5.4 kernel
Public bug reported: Black screen after grub menu, selected kernel 5.4.0-29-generic and can't login, have to shut down laptop by pressing power button, or Alt + SysRq + REISUB(O), and when those dont work a hard power off. I have installed linux-signed-oem-5.6 and ppa.launchpad.net/oibaf /graphics-drivers/ubuntu as a workaround the this problem ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 5 01:25:40 2020 InstallationDate: Installed on 2020-05-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2020-05-04T14:16:57.900775 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- 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/1876835 Title: black screen before login on 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1876835/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876281] Re: 20.4 - ssh/sftp - bookmark not working
Please open upstream issue here - https://gitlab.gnome.org/GNOME/gnome- panel/-/issues. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1876281 Title: 20.4 - ssh/sftp - bookmark not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1876281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876830] [NEW] Some Gnome applications do not find some fonts
Public bug reported: Not sure for which package to report this bug, as it shows up in multiple applications. Ubuntu 20.04 came with a newer GhostScript, which swapped the Nimbus-L series of fonts (e.g. Nimbus Mono L, format PostScript Type 1) for a Nimbus-PS series (e.g. Nimbus Mono PS, format ASCII Font Metrics, AFM). Ubuntu kindly placed these previous fonts in /usr/share/fonts/type1/gsfonts, albeit under cryptic file names. Nimbus Mono L used to be my standard monospaced font, so I'm very sure it worked in Ubuntu 19.10. Bug is, now some applications still see Nimbus-L fonts, others don't. Applications I found to not see them (not listed in preferences -> font selection): - gnome-terminal - gedit - geany Applications seeing them: - fc-list - gnome-font-view - Scribus Right after the upgrade, geany and gnome-terminal didn't show characters, but some unreadable replacement garbage (these tiny rectangles with some hex code inside). Both had Nimbus Mono L set as their font. Another bit of diagnosis: viewing a single font in Nautilus, placed e.g. in $HOME, shows such a Nimbus-L font fine, but in the window title bar it reads 'installed', installation button is greyed out. An excerpt of the list of installed fonts: $ fc-list | grep Nimbus | grep Mono /usr/share/fonts/opentype/urw-base35/NimbusMonoPS-Italic.otf: Nimbus Mono PS:style=Italic /usr/share/fonts/opentype/urw-base35/NimbusMonoPS-BoldItalic.otf: Nimbus Mono PS:style=Bold Italic /usr/share/fonts/type1/gsfonts/n022003l.pfb: Nimbus Mono L:style=Regular /usr/share/fonts/type1/urw-base35/NimbusMonoPS-Italic.t1: Nimbus Mono PS:style=Italic /usr/share/fonts/opentype/urw-base35/NimbusMonoPS-Bold.otf: Nimbus Mono PS:style=Bold /usr/share/fonts/type1/gsfonts/n022023l.pfb: Nimbus Mono L:style=Regular Oblique /usr/share/fonts/opentype/urw-base35/NimbusMonoPS-Regular.otf: Nimbus Mono PS:style=Regular /usr/share/fonts/type1/urw-base35/NimbusMonoPS-Regular.t1: Nimbus Mono PS:style=Regular /usr/share/fonts/type1/urw-base35/NimbusMonoPS-BoldItalic.t1: Nimbus Mono PS:style=Bold Italic /usr/share/fonts/type1/urw-base35/NimbusMonoPS-Bold.t1: Nimbus Mono PS:style=Bold /usr/share/fonts/type1/gsfonts/n022004l.pfb: Nimbus Mono L:style=Bold /usr/share/fonts/type1/gsfonts/n022024l.pfb: Nimbus Mono L:style=Bold Oblique ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software-common 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 5 00:22:40 2020 Dependencies: InstallationDate: Installed on 2016-05-04 (1461 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snapN/A PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-05-03 (0 days ago) ** Affects: gnome-software (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-software in Ubuntu. https://bugs.launchpad.net/bugs/1876830 Title: Some Gnome applications do not find some fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1876830/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876826] Re: Once enabled on multiple displays, the dock won't return to only "primary display"
*** This bug is a duplicate of bug 1866088 *** https://bugs.launchpad.net/bugs/1866088 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1866088, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1866088 Problems with the Dock setting of "Show on" in the Appearance tab -- 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/1876826 Title: Once enabled on multiple displays, the dock won't return to only "primary display" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1876826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875595] Re: SRU the current 3.36.2 stable update
** Changed in: nautilus (Ubuntu Focal) Importance: Undecided => Low -- 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/1875595 Title: SRU the current 3.36.2 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876826] [NEW] Once enabled on multiple displays, the dock won't return to only "primary display"
Public bug reported: Relatively fresh install of 20.04 here. I'm on an XPS 13 with "Intel Iris Plus Graphics (ICL GT2)" if that helps. I have it connected to an external Dell monitor. The two displays are joined. Fractional scaling is enabled: 200% on the laptop display, 100% on the external monitor. The external monitor is set to be the Primary Display. Under Ubuntu's Settings/Appearance config screen, I went down to the "Dock" settings. I tried out a few different placements of the dock, on both screens vs just the primary, tried changing the position, tried auto-hiding, etc just to get a feel for how these settings might look. Ultimately I decided that the defaults were the best, and wanted to return the dock to the left-hand side of the Primary Display only. While I could get the dock back into position on the left side of the screen, I could not get it to disappear from the secondary display. The "Show on" dropdown has no effect. Appearing within the "Show on" drop down are three choices: "All displays", "Built-in display", and "Dell Inc. 18"". No matter what I select in this dropdown, the dock will now only ever appear on All displays, all the time. I'd like to return to the default behavior, with the dock only appearing on the Primary Display. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 14:58:24 2020 InstallationDate: Installed on 2020-05-01 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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 focal ** Description changed: Relatively fresh install of 20.04 here. I'm on an XPS 13 with "Intel Iris Plus Graphics (ICL GT2)" if that helps. I have it connected to an external Dell monitor. The two displays are joined. Fractional scaling is enabled: 200% on the laptop display, 100% on the external monitor. The external monitor is set to be the Primary Display. Under Ubuntu's Settings/Appearance config screen, I went down to the "Dock" settings. I tried out a few different placements of the dock, on both screens vs just the primary, tried changing the position, tried auto-hiding, etc just to get a feel for how these settings might look. Ultimately I decided that the defaults were the best, and wanted to return the dock to the left-hand side of the Primary Display only. While I could get the dock back into position on the left side of the screen, I could not get it to disappear from the secondary display. The "Show on" dropdown has no effect. Appearing within the "Show on" drop down are three choices: "All displays", "Built-in display", and "Dell Inc. 18"". No matter what I select in this dropdown, the dock will now only ever appear on All displays, all the time. - I'd like to return get back to the default behavior, with the dock only - appearing on the Primary Display. + I'd like to return to the default behavior, with the dock only appearing + on the Primary Display. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 14:58:24 2020 InstallationDate: Installed on 2020-05-01 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1876826 Title: Once enabled on multiple displays, the dock won't return to only "primary display" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1876826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
Nevermind, the SRU to focal is already tracked by bug #1876256, and an upload is already sitting in the queue. ** Tags removed: rls-ff-incoming -- 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/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1862553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876821] [NEW] [needs-packaging] gtk+3.24: gtk+3.22 is discontinued
Public bug reported: Since there are no more updates released for gtk+3.22 it is important, that at least gtk+3.24 is added to ubuntu-18.04 APT. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1876821 Title: [needs-packaging] gtk+3.24: gtk+3.22 is discontinued To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1876821/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876594] Re: totem doesn't start on Wayland: Error 71 (Error de protocolo) dispatching to Wayland display
*** This bug is a duplicate of bug 1868520 *** https://bugs.launchpad.net/bugs/1868520 The log has the same error, marking it as duplicate ** This bug has been marked a duplicate of bug 1868520 Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784) [DRM_FORMAT_XRGB2101010] -- 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/1876594 Title: totem doesn't start on Wayland: Error 71 (Error de protocolo) dispatching to Wayland display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1876594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876802] Re: Gnome (on Xorg) crashes when disconnecting external monitor
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1876802 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1876802 Title: Gnome (on Xorg) crashes when disconnecting external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876768] Re: Terminal mouse went berserk after lost ssh connection
The same applies not just for the mouse mode, but a whole lot of other terminal modes (e.g. keypad modes, alternate charset, alternate scroll mode, bracketed paste mode, colors, attributes and many many more...). The problem cannot be fixed in the terminal: The terminal, by design, only sees a single continuous stream of instructions to execute. It has no idea where they come from, e.g. remote or local, ssh or not. It cannot figure out when is the time to override those instructions. A reasonable place to fix this would be the shell prompt (or a hardwired behavior of the shell, to reset these modes whenever it prints the prompt). You can customize your PS1 to include the escape sequence that switches off mouse mode, and whatever else you wish. (Don't forget to wrap these in \[ \] as per the PROMPTING section in bash's manual.) I agree that either upstream bash, or downstream distributions by configuring PS1 accordingly, should do their best to minimalize the risk of such situations, i.e. reset as many of the terminal modes as reasonable. I myself used to do it in my personal PS1 until I got bored of maintaining it and stopped caring, the problems are so rare that I just execute "reset" or close the terminal and open a new one :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1876768 Title: Terminal mouse went berserk after lost ssh connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1876768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876768] Re: Terminal mouse went berserk after lost ssh connection
pretty sure that's quite usual that the terminal get 'corrupted' in such cases, and you can get away with it by running 'reset' which resets the terminal emulation ** Package changed: xterm (Ubuntu) => gnome-shell (Ubuntu) ** Package changed: gnome-shell (Ubuntu) => gnome-terminal (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/1876768 Title: Terminal mouse went berserk after lost ssh connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1876768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876768] [NEW] Terminal mouse went berserk after lost ssh connection
You have been subscribed to a public bug: I'm not sure I assigned this issue to the correct package. The bug is either in bash, or in Ubuntu's application terminal, the one that provides a terminal window to run bash in, which I think is xterm but I'm not sure. Also this could be triggered by either an issue in ssh or in vim which is run on the remote server (see steps to reproduce below), BUT no matter whether or not there's actually a bug in either of them, the shell itself (or the terminal wrapper window) is almost certainly at fault for not being robust against that. So let's get to the issue. What reproduced it for me: 1. I opened a terminal in Ubuntu on my laptop 2. In that terminal, I connected to a remote server using ssh 3. Within ssh, on the remote server I ran vim 4. Several hours passed and I suspended my local laptop 5. I resumed from suspend and went back to the terminal At this point the connection with the remote server was obviously lost, so as soon as I typed something, I was outside of ssh and in my local shell. 6. I ran some commands locally in the terminal (obviously starting with "clear" to clean up the mess left from quitting ssh while vim was open on the remote server) 7. I clicked and dragged within the terminal to select some text EXPECTED: the mouse should behave normally as it usually does when you click and drag to select stuff in a terminal OBSERVED: the terminal went berserk and for every movement of the mouse while the mouse button was pressed, a bunch of gibberish characters appeared. Now, I understand that while I was connected to the remote server via ssh, and running vim on it, the mouse had a certain behavior, which implies that somehow information about the interaction of the mouse with the terminal is sent over to the server where vim reacts to it. And I understand that both vim on the server and ssh on the local machine exited abruptly when I suspended and resumed my computer, and/or because of the hours of inactivity. So, I understand that something about the way the terminal window, or bash itself, handles mouse input, ramained in some unexpected status. However, that that can happen is a bug. A ssh connection can be lost, and this possibility must be taken into account. The responsibility of this cannot by definition belong to vim or any other software on the remote machine, because if the connection is broken there's nothing the remote machine can do to prevent bad stuff from happening on the local machine. And I think the responsibility shouldn't fall on the ssh client either, because any program launched by the shell (such as in this case ssh) can die unexpectedly, or even behave malitiously, and once you exit from it, the shell itself (or the terminal window that hosts it) MUST restore its normal interaction with keyboard, mouse and whatever else. However, if ssh is exiting gracefully after detecting a break in the connection, then of course it should do its best to not leave its parent shell in a mess of a state (even if the shell has a responsibility to not be left in a mess of a state by a misbehaving ssh that doesn't do its job properly when exiting). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xterm 322-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon May 4 18:40:15 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2396 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-173-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xterm UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012
[Bug 1876802] [NEW] Gnome (on Xorg) crashes when disconnecting external monitor
Public bug reported: Working on a dell xps13 running Ubuntu 20.04, having a second display connected to my laptop. When disconnecting the 2nd display, first the application windows move the built-in laptop display, but after one or two seconds the screen went gray, telling me that an error has occured and that you need to log in again. I went through the journalctl, and noticed lots of messages as below: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Not sure if this is the actual cause though. After some googling I found bug report #1857660 in which it was suggested to uninstall a few gnome extensions. One of the mentioned extensions was indeed installed, but I removed (in the end) all of them, rebooted but still problem occurs. And is reproducable in a very simple way: - Reboot & Login (with 2nd monitor attached) - Open an app (not sure this is really needed to reproduce though) - Disconnect the 2nd display and wait a second. - Boom! Useful to mention that the problem does not occur on Wayland, even with the extensions installed (but with Wayland I can't share my full screen, which I need for Slack :-( ). ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/1876802/+attachment/5366447/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876802 Title: Gnome (on Xorg) crashes when disconnecting external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875285] Re: [nvidia] Ubuntu 20.04 Fractional scaling crops half the screen
This is how a screenshot looks like for reference. If this could be squeezed into the monitor frame size the bug would be resolved. ** Attachment added: "Screenshot from 2020-05-04 13-20-43.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285/+attachment/5366446/+files/Screenshot%20from%202020-05-04%2013-20-43.png -- 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/1875285 Title: [nvidia] Ubuntu 20.04 Fractional scaling crops half the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873402] Re: Can't connect to google account (The name :1.10 was not provided by any .service files)
Upgrading to 20.04 fixes this bug -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1873402 Title: Can't connect to google account (The name :1.10 was not provided by any .service files) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1873402/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875285] Re: [nvidia] Ubuntu 20.04 Fractional scaling crops half the screen
If I take a screenshot, it looks normal. But I took a photo so you can see how it's being cropped. Looks like fractional scaling gets the correct scale but doesn't manage to fit it to the screen size. Hope this photo helps. ** Attachment added: "20200504_132201.jpg" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285/+attachment/5366445/+files/20200504_132201.jpg -- 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/1875285 Title: [nvidia] Ubuntu 20.04 Fractional scaling crops half the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875326] Re: Can't double click items in icon view
Thanks for your help with this Sebastien. I suspected it was something like this but didn't know how to find it. If its an old, unmaintained feature then no need to pursue it. -- 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/1875326 Title: Can't double click items in icon view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
I think the fix should be SRUed to focal, indeed. ** Tags added: rls-ff-incoming -- 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/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1862553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876460] Re: No users appear in settings
you're welcome, it's still confusing that it was flagged as system user before ... did you have another shell set or something non standard? also there seems to be a bug that the status of system being true or false isn't revisited if the user change -- 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/1876460 Title: No users appear in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875285] Re: [nvidia] Ubuntu 20.04 Fractional scaling crops half the screen
This is how it looks like. Notice that it crops almost everything (after the time) at the top panel, the windows don't fit the screen real size and even the ubuntu dock is croped, I can't see "Show applications" at it's bottom. ** Attachment added: "bug.jpeg" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285/+attachment/5366371/+files/bug.jpeg -- 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/1875285 Title: [nvidia] Ubuntu 20.04 Fractional scaling crops half the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
@vangugt What's the status on when the fix will be released? We all see that you seem to have confirmed that the issue is no longer present with a new version, but none of us seem to have the version yet. -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876774] [NEW] Update makes system unusable if screen lock turns on
Public bug reported: When the update indication pops up, you click update, let the screen lock turn on. Then while the screen lock is turned on it gives you are still able to enter your password to continue with updates. If you do that, and try to unlock the screen, the lock screen is still visible along with the toolbar. At this point the system is basically unusable. Sometimes I've been able to log out or reboot the system, usually I have to do a hard reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.15 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 4 13:19:35 2020 InstallationDate: Installed on 2013-07-17 (2483 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.15 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2020-01-18 (106 days ago) ** Affects: gnome-software (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 gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876774 Title: Update makes system unusable if screen lock turns on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1876774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
Is this bug targetted for fixing in Ubuntu 20.04 LTS? -- 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/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1862553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875326] Re: Can't double click items in icon view
** Attachment added: "Nautilus with reset config" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875326/+attachment/5366215/+files/after-config.txt -- 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/1875326 Title: Can't double click items in icon view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875326] Re: Can't double click items in icon view
Hmm, doing the reset caused the computer to freeze, I had to switch to a tty and reboot. Ran the reset again in the background with just a terminal open and it succeeded. The problem has gone away. I've saved the config before and after (attached) but the suspicious item is org.gnome.nautilus.preferences use-experimental-views true ** Attachment added: "Nautilus config with the problem" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875326/+attachment/5366214/+files/before-config.txt -- 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/1875326 Title: Can't double click items in icon view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
To make life more interesting this seems to be also related somehow to the combined headphone/microphone combo jack issue I have, because it only appears when I use my headset, but only when the microphone is also recognized. Sometimes the microphone doesn't get picked up when I plug in the headset and then the music-restarting issues don't seem to appear either. During all this all I see in syslog are these lines that the reporter reported, nothing else of use. -- 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/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Hm. I think these may be a symptom of an underlying problem (or problems) that is causing really weird bugs related to all kinds of things. A few things that I noticed: - I tried mapping 'previous track' to Ctrl + Alt + Left Arrow and 'next track' to Ctrl + Alt + Right Arrow which just simply didn't work in Ubuntu 20.04 - I mapped Ctrl + Alt + Down Arrow to 'play/pause' which worked in Ubuntu 20.04 so far, but in Ubuntu 19.10 it sometimes just stopped working - Weirdly enough when you first try to map Ctrl + Alt + Down to a key it complains that it is already mapped to 'Move to workspace below' (which in the shortcut menu is shown to be bound by default to Super + Page Down), WTF - Now a few seconds after sounds stop (e.g. when pausing a song in Spotify or even after system sounds) I see these exact messages logged to syslog. At the same time if Spotify is open it resumes playing the paused song, if it is not open, I get a popup with a "prohibition" symbol in it (https://en.wikipedia.org/wiki/No_symbol). May I be damned but this all seems somehow related, although it looks like black magic from here. I'm not going to say that it all just worked perfectly under Unity, but all this actually did work mostly fine in Ubuntu 16.04. Well, 'previous track' and 'next track' didn't always work but hey, at least the music didn't restart itself. -- 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/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876460] Re: No users appear in settings
So, it's created with "false", and everything is back to normal... thank you Sebastien! -- 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/1876460 Title: No users appear in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876286] [NEW] Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
Rod, I experience, exact, same problem here using Evolution on Debian 9 with verizon.net server (aol.com). If it would be helpful, I can send similar wireshark recording of evolution communication with aol server. Using Thunderbird on same Debian 9 OS, I have no problem. Joe -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875326] Re: Can't double click items in icon view
I haven't knowingly changed anything recently but my original installation was 15.04 and I've upgraded progressively so may have set something in the past. I didn't have the problem with 18.04 though. I've tried with a different user and the problem doesn't appear to be present so it looks like it could be a setting for my user. Give me a clue where to look and I'm happy to try things out. I've tried eliminating the contents of .config/nautilus but no joy. -- 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/1875326 Title: Can't double click items in icon view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
Same issue for me with Nvidia GTX 1050 Ti. Settings in monitor.xml are not being applied. xrandr and nvidia-settings are able to change the monitor rotation, just gnome-settings messes it up. Just blaming the Nvidia driver for this without giving a reason seems unprofessional to me, especially because other programs like xrandr do not have any issue setting the proper monitor setup. To nail down the issue: screen/monitor positions can be set without problem in monitor.xml, but rotation settings are not applied or ignored. When trying to make the settings in gnome-settings it is like described above: As long as not monitor is rotated everything can be set up nicely, but as soon as the monitor is being rotated the screen is messed up in the way described above. -- 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/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876460] Re: No users appear in settings
hum, so /var/lib/AccountsService/users/kms has SystemAccount=true for some reason ... if you delete that file does it get re-created with the same value? -- 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/1876460 Title: No users appear in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876460] Re: No users appear in settings
=> grep kms /etc/passwd kms:x:1001:501:Krister Swenson,,,:/home/kms:/bin/bash => sudo more /var/lib/AccountsService/users/kms [User] Session= FormatsLocale=fr_FR.UTF-8 XSession=ubuntu-wayland Icon=/home/kms/.face SystemAccount=true [InputSource0] xkb=us+mac [InputSource1] xkb=fr -- 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/1876460 Title: No users appear in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876460] Re: No users appear in settings
** Attachment added: "accounts-daemon.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876460/+attachment/5366276/+files/accounts-daemon.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/1876460 Title: No users appear in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875765] Re: epiphany-browser opens 2 windows instead of 1
*** This bug is a duplicate of bug 1873964 *** https://bugs.launchpad.net/bugs/1873964 ** No longer affects: epiphany (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1875765 Title: epiphany-browser opens 2 windows instead of 1 To manage notifications about this bug go to: https://bugs.launchpad.net/epiphany-browser/+bug/1875765/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873964] Re: Browser when used from Ubuntu-Dock lanuches two browser instances.
** Changed in: epiphany-browser (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1873964 Title: Browser when used from Ubuntu-Dock lanuches two browser instances. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1873964/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876471] Re: Trash desktop icon is not translated
Not confirming on a french installed focal system, unsure what's the issue is from but it's probably from nautilus if the translation is missed in the top bar there ** Package changed: gnome-shell-extension-desktop-icons (Ubuntu) => nautilus (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1876471 Title: Trash desktop icon is not translated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1876471/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
I've been getting exactly the same issue as described here, always when I log in and find an "Authentication Required" dialog window in the top left of the screen. I've attached a screen shot, the details of my environment are below: OS: PopOS (Ubuntu 20.04 LTS x86_64) Kernel: 5.4.0-7626-generic DE: Gnome Window manager: Mutter I also have a Yubikey that I'm using in challenge-response mode and have the following line inserted in the following PAM modules: `auth sufficient pam_yubico.so mode=challenge-response chalresp_path=/var/yubico` ** Attachment added: "Screenshot of the authentication prompt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+attachment/5366258/+files/Screenshot%20from%202020-05-04%2015-45-51.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/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] Re: [nvidia] fractional monitor scaling fails due to overlapping monitors
Daniel, it sounds then like you are saying this is a duplicate of 1873403? -- 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/1869042 Title: [nvidia] fractional monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] Re: [nvidia] fractional monitor scaling fails due to overlapping monitors
(the issues here originally were that the screens go black and that I couldn't set the main monitor after changing scaling, for which I filed 1873266, as per your request) -- 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/1869042 Title: [nvidia] fractional monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876530] Re: Screen scales to grandma very unfriendly mode
Before the problem -- Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 308mm x 173mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) -- after the problem -- Screen 0: minimum 320 x 200, current 3072 x 1728, maximum 16384 x 16384 eDP-1 connected primary 3072x1728+0+0 (normal left inverted right x axis y axis) 308mm x 173mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) -- 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/1876530 Title: Screen scales to grandma very unfriendly mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1876530/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875326] Re: Can't double click items in icon view
Thanks, indeed it's due to the experimental-view. That settings seems old and unmaintained, it's not something we support or will fix so I'm closing the report but feel free to report it upstream in case they would like to work on it https://gitlab.gnome.org/GNOME/nautilus/-/issues ** Changed in: nautilus (Ubuntu) Status: New => Won't Fix -- 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/1875326 Title: Can't double click items in icon view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876719] [NEW] The application folders are very buggy
Public bug reported: The app folders have a glitch where when I click out, the number of app pages increases. The extra app pages are inaccessible. The animations for them are very jittery as well. There's no translucent background under the app folders (unexpanded), yet the background is there under Wayland I have to restart the gnome-shell so the extra pages go away, this bug is also identical in Wayland save for the folder backgrounds. I've also had items on the app pages begin to overlap with no trigger. https://imgur.com/L7GJ0kv https://imgur.com/k26cFem https://imgur.com/uhwJku2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 14:05:40 2020 DisplayManager: gdm3 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/1876719 Title: The application folders are very buggy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876719/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1442649] Re: nautilus trash doesn't include btrfs and zfs subvolumes
Is that still an issue in focal? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1442649 Title: nautilus trash doesn't include btrfs and zfs subvolumes To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1442649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876594] Re: totem doesn't start on Wayland: Error 71 (Error de protocolo) dispatching to Wayland display
WAYLAND_DEBUG=1 totem >& totem-wayland-log.txt asked in #3 ** Attachment added: "WAYLAND_DEBUG=1 totem >& totem-wayland-log.txt" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1876594/+attachment/5366162/+files/totem-wayland-log.txt -- 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/1876594 Title: totem doesn't start on Wayland: Error 71 (Error de protocolo) dispatching to Wayland display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1876594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875326] Re: Can't double click items in icon view
Configurations are not in .config but mostly in gsettings you can dump the current nautilus settings by $ gsettings list-recursively org.gnome.nautilus > config.txt reset the values $ gsettings reset-recursively org.gnome.nautilus Do you get the issue if you navigate e.g /usr/bin? -- 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/1875326 Title: Can't double click items in icon view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876716] [NEW] Error transferring track: "could not open resource for writing" when copying tracks to library
Public bug reported: I tried adding my old iTunes music folder into my (empty) Rhythmbox library having the option 'Copy files that are outside the music library' checked. After clicking 'Import 4974 listed tracks'. Expected behaviour: all files should've been copied to my Rhythmbox media folder. What happened instead: the copy process got interupted with the following error: Error transferring track: "could not open resource for writing" Only a few tracks where copied, I was able to press the button a few more times to copy a few more tracks, but then Rhythmbox crashed/closed and I had to restart it. I also tried it with just a few tracks. That worked, but the same error message came up when trying to copy tracks that were added to the library before. --- Description:Zorin OS 15.2 Release:15 rhythmbox: Installed: 3.4.2-4ubuntu1 Candidate: 3.4.2-4ubuntu1 Version table: *** 3.4.2-4ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2020-05-04 13-53-19.png" https://bugs.launchpad.net/bugs/1876716/+attachment/5366159/+files/Screenshot%20from%202020-05-04%2013-53-19.png -- 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/1876716 Title: Error transferring track: "could not open resource for writing" when copying tracks to library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1876716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1876524] Re: Issue after repositioning display/monitor location usiing display settings
As requested. FYI, the three monitors I have are connected to both the laptop/dock and a PC at the same time. I change the input source on each monitor to change between the laptop and PC. This may not be relevant, but I thought it would be worth mentioning. Steven. On 04/05/2020 10:27, Daniel van Vugt wrote: > Please also run: > > gsettings list-recursively org.gnome.shell > settings.txt > xrandr > xrandr.txt > lspci -k > lspcik.txt > journalctl -b0 > journal.txt > > and then attach the four resulting text files. > ** Attachment added: "xrandr.txt" https://bugs.launchpad.net/bugs/1876524/+attachment/5366139/+files/xrandr.txt ** Attachment added: "settings.txt" https://bugs.launchpad.net/bugs/1876524/+attachment/5366140/+files/settings.txt ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/bugs/1876524/+attachment/5366141/+files/lspcik.txt ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/1876524/+attachment/5366142/+files/journal.txt -- 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/1876524 Title: Issue after repositioning display/monitor location usiing display settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1876524/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876518] Re: Gtk.Clipboard set_text() not working
** Bug watch added: gitlab.gnome.org/GNOME/pygobject/-/issues #405 https://gitlab.gnome.org/GNOME/pygobject/-/issues/405 ** Also affects: pygobject via https://gitlab.gnome.org/GNOME/pygobject/-/issues/405 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1876518 Title: Gtk.Clipboard set_text() not working To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/1876518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876460] Re: No users appear in settings
Could you copy the /etc/passwd line for the user not listed? What's the content of /var/lib/AccountsService/users/ ? Accountsservice does some filtering on things like having a valid shell Could you also include the log of? $ /usr/lib/accountsservice/accounts-daemon --debug ** Changed in: gnome-control-center (Ubuntu) Status: Invalid => Incomplete -- 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/1876460 Title: No users appear in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876460] Re: No users appear in settings
The screenshot with shows no button when no user is listed sounds like a valid bug, it should allow to unlock/add the user as stated in the screen, could you report that upstream on https://gitlab.gnome.org/GNOME /gnome-control-center/issues ? -- 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/1876460 Title: No users appear in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871805] Re: --wait option not working as expected (3.28)
Thank you, I have just updated the description. Should I try to make the fix and upload a debdiff which includes all libraries upgrades? ** Description changed: + [Impact] + + Users are unable to launch an asynchronous gnome-terminal. In some + cases, a user/program/script might want to run a gnome-terminal with a + provided command and wait till the launched gnome-terminal exits. + + By default, gnome-terminal runs synchronously as it uses the gnome- + server to handle the requests. To solve that, gnome-terminal 3.27.1 + introduced the --wait option which solves this issue. The problem, is + that --wait flag does not work properly till version >= 3.36 which also + uses a new vte version (libvte-2.91-dev_0.60.1). Thus users cannot wait + for a gnome-terminal session process to finish. + + More information: https://gitlab.gnome.org/GNOME/gnome- + terminal/issues/16 + + [Test Case] + + To reproduce the bug let's assume that we want to open a gnome-terminal + with a provided command, for example a simple bash: + + 1- Open a terminal: + + gnome-terminal -- /bin/sh -c "/bin/bash" + + This will launch gnome-terminal with a bash but the parent process in + the first terminal finishes just after executing the command, even if + the gnome-terminal is opened. + + 2- Include the --wait option to make the command call asynchronous: + + gnome-terminal --wait -- /bin/sh -c "/bin/bash" + + - Now you can see int the first terminal that the processes didn't + finish, instead it is waiting for the launched gnome-terminal. + + To see the explained bug try to close the opened gnome-terminal using + the X icon windows or File-> Close Tab. => The parent process in + terminal 1 does not receive the child-exited signal, thus it keeps + waiting forever. + + However if we try to exit from the launched gnome-terminal by typing + "exit" on it, the parent process does receive the corresponding signal. + + [Regression Potential] + + As mentioned before, this bug was solved in gnome-terminal >= 3.36 + Many users use the GUI options in order to finish a process, so this bug prevents developers to take advantage of the --wait option in its programs. + + The version 3.36 is included in new Ubuntu versions but not in the + bionic one(Ubuntu 18.04). Many users and enterprises are still using + Ubuntu 18.04 as the new LTS has just been released a few days ago. + + [Other Info] + + Initial bug report: + Dear Maintainers, We have developed a program that it launches a new gnome-terminal with a ssh tunnel connection. Basically, the program forwards a local port to the destination address and opens a new terminal with a ssh connection to the local port: gnome-terminal -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2" The problem comes when we need to know when this gnome-terminal session has finished, in order to end the tunnel process. As you might know, the gnome-terminal command fires up gnome-terminal-server which it might be already running. Who handles the "ssh" connection is the gnome-terminal- server and not the gnome-terminal command, thus our program receives and exit code just after executing the previous command. In previous version there was the --disable-factory option, but unfortunately now is deprecated. Because of this type of problem it was added the --wait flag which was introduced in 3.27.1: gnome-terminal --wait -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2" - Nevertheless, there's a bug in this version. More information: - https://gitlab.gnome.org/GNOME/gnome-terminal/issues/16 + Nevertheless, there's a bug in this version. You can reproduced by launching a new gnome-terminal with the --wait flag from a gnome-terminal session and try to close it via a window operation. In that version --wait only works if with the exit command in the opened session. As mentioned in the linked URL this is solved in version >= 3.36 which also uses a new vte version (libvte-2.91-dev_0.60.1). I have seen that there are multiple issues referring the --disable-factory deprecated option, those could be closed as the new --wait option has the same behavior. Shall we update the libvte version used by gnome? The last libvte version has the proper child exit SIGNAL handler which solves the described issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.1-1ubuntu1 Architecture: amd64 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1871805 Title: --wait option not working as expected (3.28) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1871805/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876346] Re: Documents cannot be opened in desktop UI on storage device
*** This bug is a duplicate of bug 1872476 *** https://bugs.launchpad.net/bugs/1872476 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1872476, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1872476 Shared files are shown as folders -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1876346 Title: Documents cannot be opened in desktop UI on storage device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1876346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876657] Re: Sometimes Nautilus mounts USB media as read-only.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1876657 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1876657 Title: Sometimes Nautilus mounts USB media as read-only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1876657/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876281] Re: 20.4 - ssh/sftp - bookmark not working
** Package changed: nautilus (Ubuntu) => gnome-panel (Ubuntu) ** Changed in: gnome-panel (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1876281 Title: 20.4 - ssh/sftp - bookmark not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1876281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875106] Re: System irresponsive after 2-finger horizontal scroll over dock
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1875106 Title: System irresponsive after 2-finger horizontal scroll over dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1875106/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874197] Re: [nvidia] gnome-control-center crashed with SIGSEGV in _g_closure_invoke_va() from g_signal_emit_valist() from g_signal_emit() from gtk_css_node_reposition() from gtk_css_node_set_par
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #980 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/980 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/980 Importance: Unknown Status: Unknown -- 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/1874197 Title: [nvidia] gnome-control-center crashed with SIGSEGV in _g_closure_invoke_va() from g_signal_emit_valist() from g_signal_emit() from gtk_css_node_reposition() from gtk_css_node_set_parent() [when changing fractional scaling settings] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874197/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876512] Re: Desktop wallpaper and taskbar freezes once system comes back from sleep
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1876512 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1876512 Title: Desktop wallpaper and taskbar freezes once system comes back from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876221] Re: [nvidia] gnome-control-center crashed with SIGSEGV in g_object_unref() from _gtk_marshal_VOID__OBJECT_OBJECTv() from _g_closure_invoke_va() from g_signal_emit_valist() from g_signal_
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #980 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/980 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/980 Importance: Unknown Status: Unknown -- 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/1876221 Title: [nvidia] gnome-control-center crashed with SIGSEGV in g_object_unref() from _gtk_marshal_VOID__OBJECT_OBJECTv() from _g_closure_invoke_va() from g_signal_emit_valist() from g_signal_emit() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1876221/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876657] Re: Sometimes Noutilus mounts USB media as read-only.
** Package changed: ubuntu => nautilus (Ubuntu) ** Summary changed: - Sometimes Noutilus mounts USB media as read-only. + Sometimes Nautilus mounts USB media as read-only. ** Tags added: 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/1876657 Title: Sometimes Nautilus mounts USB media as read-only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1876657/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875326] Re: Can't double click items in icon view
> It seems that on clicking an item the focus is temporarily set to a different item further up the page before setting it to the selected item That's a weird issue, I can't confirm/reproduce it here though. Did you change any setting in the setting or file manager? Could you try if it also happens with a new user? -- 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/1875326 Title: Can't double click items in icon view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876696] [NEW] Install button still actionable when snap install in progress
Public bug reported: When installing a new snap from gnome-software, the "install" button remains clickable while installing is in progress. If you press the button once again, the store returns an error "Impossible to install «%snap_name%»: snap "%snap_name%" has "install-snap" change in progress". Test Case 1. Open GNOME Software 2. Select a snap and click on the install button 3. Click again on the same button Expected result: - When the button "Install" is clicked once, it should become inactive (change color and not be clickable anymore). - the label on the button should change showing something like "install in progress" - (Desired, not forcefully required) A progress bar should indicate that something is happening Observed result: Install button is always active and clickable. When the "install" button clicked , gnome-software returns the error "Impossible to install «%snap_name%»: snap "%snap_name%" has "install-snap" change in progress ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Description changed: When installing a new snap from gnome-software, the "install" button remains clickable while installing. If you press the button once again, - the store returns says install-snap change is in progress. + the store returns an error "Impossible to install «%snap_name%»: snap + "%snap_name%" has "install-snap" change in progress". Test Case 1. Open GNOME Software 2. Select a snap and click on the install button 3. Click again on the same button Expected result: - When the button "Install" is clicked once, it should become inactive (change color and not be clickable anymore). - the label on the button should change showing something like "install in progress" - (Desired, not forcefully required) A progress bar should indicate that something is happening Observed result: Install button is always active and clickable. When the "install" button clicked , gnome-software returns the error "Impossible to install «%snap_name%»: snap "%snap_name%" has "install-snap" change in progress ** Description changed: When installing a new snap from gnome-software, the "install" button - remains clickable while installing. If you press the button once again, - the store returns an error "Impossible to install «%snap_name%»: snap - "%snap_name%" has "install-snap" change in progress". + remains clickable while installing is in progress. If you press the + button once again, the store returns an error "Impossible to install + «%snap_name%»: snap "%snap_name%" has "install-snap" change in + progress". Test Case 1. Open GNOME Software 2. Select a snap and click on the install button 3. Click again on the same button Expected result: - When the button "Install" is clicked once, it should become inactive (change color and not be clickable anymore). - the label on the button should change showing something like "install in progress" - (Desired, not forcefully required) A progress bar should indicate that something is happening Observed result: Install button is always active and clickable. When the "install" button clicked , gnome-software returns the error "Impossible to install «%snap_name%»: snap "%snap_name%" has "install-snap" change in progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876696 Title: Install button still actionable when snap install in progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1876696/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876518] Re: Gtk.Clipboard set_text() not working
Thank you for your bug report. What desktop environment do you use? Could you report it upstream on https://gitlab.gnome.org/GNOME/pygobject/ ? ** Changed in: pygobject (Ubuntu) Importance: Undecided => Low ** Changed in: pygobject (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1876518 Title: Gtk.Clipboard set_text() not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1876518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876512] [NEW] Desktop wallpaper and taskbar freezes once system comes back from sleep
You have been subscribed to a public bug: Once the system comes back from sleep, the desktop wallpaper appears as frozen screen. Same with taskbar. Also, things become normal once I reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 3 00:51:44 2020 InstallationDate: Installed on 2019-07-29 (278 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to focal on 2020-04-25 (6 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug dist-upgrade focal -- Desktop wallpaper and taskbar freezes once system comes back from sleep https://bugs.launchpad.net/bugs/1876512 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876561] Re: Launching terminal or typing commands in it makes the desktop "refresh"
Thank you for your bug report. Do you edit any file in your ~/Desktop directory? It sounds similar to bug #1812883 ** Package changed: gnome-terminal (Ubuntu) => gnome-shell-extension- desktop-icons (Ubuntu) ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1876561 Title: Launching terminal or typing commands in it makes the desktop "refresh" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1876561/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876471] Re: Trash desktop icon is not translated
Thank you for your bug report, indeed it seems not translatable Could you report it upstream on https://gitlab.gnome.org/World/ShellExtensions/desktop-icons ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1876471 Title: Trash desktop icon is not translated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1876471/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876657] [NEW] Sometimes Noutilus mounts USB media as read-only.
You have been subscribed to a public bug: Ubuntu 18.04.4 This happens in my all 3 laptops with several USB memories. so it's not hardware specific. Sometimes(50% of times) Noutilus mounts USB memory as read-only. so I can't drag and drop files or delete files. But from terminal. I can fully access my USB memories. Rebooting all Nautilus process can solve this. so I guess problem is Noutilus. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Sometimes Noutilus mounts USB media as read-only. https://bugs.launchpad.net/bugs/1876657 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
