[Bug 290313] Re: system-wide proxy does not apply to synaptic
Im facing the problem described above in Ubuntu 20.04 LTS. Should i open a new bug or just add here? Trying to report bug using apport-bug is showing this as a similar case. -- 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/290313 Title: system-wide proxy does not apply to synaptic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/290313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844808] Re: Can't delete file from desktop by clicking it and hitting delete key
** Also affects: gnome-shell-extension-desktop-icons (Baltix) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-desktop-icons (Baltix) Status: New => In Progress ** Changed in: gnome-shell-extension-desktop-icons (Baltix) Assignee: (unassigned) => Mantas Kriaučiūnas (mantas) ** Changed in: gnome-shell-extension-desktop-icons (Baltix) Milestone: None => baltix-18.04 -- 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/1844808 Title: Can't delete file from desktop by clicking it and hitting delete key To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1844808/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
I have a possible related problem with Ubuntu-mate 20.04. I adjusted my mouse pointer size (Dell Inspiron 7995 with Nvidia GTX 960M graphics) the screen went black mouse pointer frozen, 10 seconds later the login screen appears. If I log back in again the screen is black and I'm stuck in an endless loop. -- 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/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869650] Re: [nouveau] changing screen position, dash is gone, background is black.. and flashing white on any attempt to operate anything
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/1869650 Title: [nouveau] changing screen position, dash is gone, background is black.. and flashing white on any attempt to operate anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869650/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869650] Re: [nouveau] changing screen position, dash is gone, background is black.. and flashing white on any attempt to operate anything
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1869650 Title: [nouveau] changing screen position, dash is gone, background is black.. and flashing white on any attempt to operate anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869650/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
** Tags added: rls-gg-incoming -- 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/gnutls/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881372] Re: Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus.
*** This bug is a duplicate of bug 1881370 *** https://bugs.launchpad.net/bugs/1881370 ** This bug has been marked a duplicate of bug 1881370 Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus. -- 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/1881372 Title: Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1881372/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881371] Re: Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus.
*** This bug is a duplicate of bug 1881370 *** https://bugs.launchpad.net/bugs/1881370 ** This bug has been marked a duplicate of bug 1881370 Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus. -- 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/1881371 Title: Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881371/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881372] [NEW] Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus.
Public bug reported: When I attempted to drag the contents of the gcc subfolder in the gcc-10.1.0 source from a .xz file in archive manager and drop the results in the gcc subfolder of the extracted archive in nautilus, the cursor became stuck in the "drag and drop" mode without initiating the drag and drop. In this state, I was unable to click anything, and the enter button would be ignored, preventing me from entering any commands, forcing me to do a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: file-roller 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 29 22:01:26 2020 InstallationDate: Installed on 2020-05-07 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash 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/1881372 Title: Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1881372/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881371] [NEW] Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus.
Public bug reported: When I attempted to drag the contents of the gcc subfolder in the gcc-10.1.0 source from a .xz file in archive manager and drop the results in the gcc subfolder of the extracted archive in nautilus, the cursor became stuck in the "drag and drop" mode without initiating the drag and drop. In this state, I was unable to click anything, and the enter button would be ignored, preventing me from entering any commands, forcing me to do a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 29 21:59:38 2020 GsettingsChanges: InstallationDate: Installed on 2020-05-07 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1881371 Title: Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881371/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881370] [NEW] Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus.
Public bug reported: When I attempted to drag the contents of the gcc subfolder in the gcc-10.1.0 source from a .xz file in archive manager and drop the results in the gcc subfolder of the extracted archive in nautilus, the cursor became stuck in the "drag and drop" mode without initiating the drag and drop. In this state, I was unable to click anything, and the enter button would be ignored, preventing me from entering any commands, forcing me to do a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 29 21:53:18 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-05-07 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-05-25 19-01-22.png" https://bugs.launchpad.net/bugs/1881370/+attachment/5378620/+files/Screenshot%20from%202020-05-25%2019-01-22.png ** Attachment removed: "Screenshot from 2020-05-25 19-01-22.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881370/+attachment/5378620/+files/Screenshot%20from%202020-05-25%2019-01-22.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/1881370 Title: Mouse cursor fbecame stuck in the "drag and drop mode" when I grabbed files from archive manager and attempted to drag to nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881370/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1804568] Re: [HP Spectre x360 Convertible 13] click position is flipped to cursor position when in tent mode
For me removing iio sensor not helping ... My mouse cursor is still flipped like or your video. -- 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/1804568 Title: [HP Spectre x360 Convertible 13] click position is flipped to cursor position when in tent mode To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1804568/+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%
Same issue with GeForce 920M with nvidia drivers (ASUS TP-300LJ). -- 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 1881294] Re: Apparmor blocks evince GUI-Input-Dialogs
Hello Reinhard, please see the
/etc/apparmor.d/tunables/home.d/site.local file, it describes how to add
additional paths to the @{HOMEDIRS} variable, which should allow evince,
and all other profiles that use @{HOME}, to function in your
environment.
Thanks
** Changed in: evince (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1881294
Title:
Apparmor blocks evince GUI-Input-Dialogs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1881294/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881344] [NEW] JS WARNING: [/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/indicator.js 747]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2
Public bug reported: May 26 12:24:06 cerberus gnome-shell[3960]: JS WARNING: [/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/indicator.js 747]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2 May 26 12:24:06 cerberus gnome-shell[3960]: JS WARNING: [/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/indicator.js 786]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2 It seems the pomodoro extension package is either out of date or too new for the version of gnome-shell in Ubuntu 18.04. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- 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/1881344 Title: JS WARNING: [/usr/share/gnome- shell/extensions/pomod...@arun.codito.in/indicator.js 747]: Too many arguments to method Clutter.Actor.add_child: expected 1, got 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1881344/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852172] Re: Battery history and statistics graphs markings are unreadable on a dark theme
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-power-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1852172 Title: Battery history and statistics graphs markings are unreadable on a dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1852172/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881330] [NEW] gnome-terminal fails to start
Public bug reported: My system has something strange going on. I'm unable to start gnome- terminal. In journalctl, I see the following cryptic message: May 29 13:08:38 cerberus org.gnome.Shell.desktop[3960]: # Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Could not connect: Connection refused If I then try to start it from an existing terminal, I get: jlquinn@cerberus:~/work/lt-language-pairs$ gnome-terminal # Error constructing proxy for :1.89:/org/gnome/Terminal/Factory0: Could not connect: Connection refused # Failed to use specified server: Could not connect: Connection refused # Falling back to default server. # Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Could not connect: Connection refused This is a somewhat important issue because it will force me to reboot my machine (or at least GUI) due to the inability to create new terminals. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-102.103-generic 4.15.18 Uname: Linux 4.15.0-102-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 29 13:03:43 2020 InstallationDate: Installed on 2016-05-30 (1459 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to bionic on 2018-09-17 (620 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1881330 Title: gnome-terminal fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1881330/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880337] Re: Screen lock won't work
https://github.com/home-sweet-gnome/dash-to-panel/issues/1026 ** Bug watch added: github.com/home-sweet-gnome/dash-to-panel/issues #1026 https://github.com/home-sweet-gnome/dash-to-panel/issues/1026 -- 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/1880337 Title: Screen lock won't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
Will be fixed in 3.36.3: https://gitlab.gnome.org/GNOME/mutter/-/issues/1242#note_823253 -- 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/1880596 Title: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880596/+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%
RTX 2060 also. Any status updates? -- 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 1881298] Re: Incorrect disk information is displayed after creating a new partition
** Description changed: After creating a new partition, GNOME Disks did not indicate whether or not the partition creation had succeeded. Instead, it indicated that several partitions had been destroyed, when this was not correct. I will describe the steps that lead to the issue: - 1. A disk was divided into several ext4 and NTFS partitions. + 1. A disk had been divided into several ext4 and NTFS partitions. 2. I shrank the last partition (NTFS) using Windows. 3. I rebooted into Ubuntu and GNOME Disks correctly displayed the empty space at the end of the disk. 4. I instructed GNOME Disks to create a new ext4 logical partition using the dialog opened by the + symbol. 5. The dialog disappeared without any indication of whether the operation had succeeded or not. At the same time, the disk graphic was updated (see screenshot in attachment). It said that the disk had only one partition (/) and the rest of the disk was free space. This implied that the operation had failed and all the other partitions had been destroyed. 6. I tried closing and opening Disks, but it continued to indicate that most of the disk had been wiped. 7. I looked at the relevant filesystems in GNOME Files (Nautilus) and GNOME System Monitor. The information there suggested that the existing partitions were intact and the new partition had been successfully created. 8. I rebooted Ubuntu and opened Disks again. It correctly displayed the new disk layout (see screenshot in attachment in comment below). I have not attempted to reproduce the issue as I cannot afford to risk damaging a hard disk in daily use. This behaviour is highly undesirable. Users who are informed that their hard disk has been wiped suffer greatly increased stress and in their panic may take irreversible actions in an attempt to remedy the situation. I am using GNOME 3.28.2 as supplied with Ubuntu 18.04.4 LTS. The Disks utility itself does not seem to have a version number. I originally reported the issue upstream at GNOME (https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/171) and they asked me to report the issue at Ubuntu instead. ** Description changed: After creating a new partition, GNOME Disks did not indicate whether or not the partition creation had succeeded. Instead, it indicated that several partitions had been destroyed, when this was not correct. I will describe the steps that lead to the issue: - 1. A disk had been divided into several ext4 and NTFS partitions. + 1. A disk divided into several ext4 and NTFS partitions existed. 2. I shrank the last partition (NTFS) using Windows. 3. I rebooted into Ubuntu and GNOME Disks correctly displayed the empty space at the end of the disk. 4. I instructed GNOME Disks to create a new ext4 logical partition using the dialog opened by the + symbol. 5. The dialog disappeared without any indication of whether the operation had succeeded or not. At the same time, the disk graphic was updated (see screenshot in attachment). It said that the disk had only one partition (/) and the rest of the disk was free space. This implied that the operation had failed and all the other partitions had been destroyed. 6. I tried closing and opening Disks, but it continued to indicate that most of the disk had been wiped. 7. I looked at the relevant filesystems in GNOME Files (Nautilus) and GNOME System Monitor. The information there suggested that the existing partitions were intact and the new partition had been successfully created. 8. I rebooted Ubuntu and opened Disks again. It correctly displayed the new disk layout (see screenshot in attachment in comment below). I have not attempted to reproduce the issue as I cannot afford to risk damaging a hard disk in daily use. This behaviour is highly undesirable. Users who are informed that their hard disk has been wiped suffer greatly increased stress and in their panic may take irreversible actions in an attempt to remedy the situation. I am using GNOME 3.28.2 as supplied with Ubuntu 18.04.4 LTS. The Disks utility itself does not seem to have a version number. I originally reported the issue upstream at GNOME (https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/171) and they asked me to report the issue at Ubuntu instead. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1881298 Title: Incorrect disk information is displayed after creating a new partition To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1881298/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874630] Re: not start without sudo
I checked this. Ubuntu-software is installed and in use. So I added this ticket to the wrong package. The problem seems caused by the fact, that launchpad tells me that ubuntu-software do not exist. > ubuntu-software/eoan-updates,eoan-updates,now 3.30.6-2ubuntu10.19.10.1 all > [installiert] > Utility for browsing, installing, and removing software -- 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/1874630 Title: not start without sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1874630/+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%
Same here with a RTX 2070 Super. -- 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 1881298] Re: Incorrect disk information is displayed after creating a new partition
The attachment shows the disk layout after the partition was created and I rebooted. This is what GNOME Disks should have displayed when the partition-creation operation succeeded. ** Attachment added: "Correctly Displayed Disk Layout" https://bugs.launchpad.net/gnome-disk-utility/+bug/1881298/+attachment/5378411/+files/Correctly%20Displayed%20Disk.png ** Description changed: After creating a new partition, GNOME Disks did not indicate whether or not the partition creation had succeeded. Instead, it indicated that several partitions had been destroyed, when this was not correct. I will describe the steps that lead to the issue: - A disk was divided into several ext4 and NTFS partitions. - I shrank the last partition (NTFS) using Windows. - I rebooted into Ubuntu and GNOME Disks correctly displayed the empty space at the end of the disk. - I instructed GNOME Disks to create a new ext4 logical partition using the dialog opened by the + symbol. - The dialog disappeared without any indication of whether the operation had succeeded or not. At the same time, the disk graphic was updated (see screenshot in attachment). It said that the disk had only one partition (/) and the rest of the disk was free space. This implied that the operation had failed and all the other partitions had been destroyed. - I tried closing and opening Disks, but it continued to indicate that most of the disk had been wiped. - I looked at the relevant filesystems in GNOME Files (Nautilus) and GNOME System Monitor. The information there suggested that the existing partitions were intact and the new partition had been successfully created. - I rebooted Ubuntu and opened Disks again. It correctly displayed the new disk layout (see screenshot in attachment in comment below). + 1. A disk was divided into several ext4 and NTFS partitions. + 2. I shrank the last partition (NTFS) using Windows. + 3. I rebooted into Ubuntu and GNOME Disks correctly displayed the empty space at the end of the disk. + 4. I instructed GNOME Disks to create a new ext4 logical partition using the dialog opened by the + symbol. + 5. The dialog disappeared without any indication of whether the operation had succeeded or not. At the same time, the disk graphic was updated (see screenshot in attachment). It said that the disk had only one partition (/) and the rest of the disk was free space. This implied that the operation had failed and all the other partitions had been destroyed. + 6. I tried closing and opening Disks, but it continued to indicate that most of the disk had been wiped. + 7. I looked at the relevant filesystems in GNOME Files (Nautilus) and GNOME System Monitor. The information there suggested that the existing partitions were intact and the new partition had been successfully created. + 8. I rebooted Ubuntu and opened Disks again. It correctly displayed the new disk layout (see screenshot in attachment in comment below). - I have not attempted to reproduce the issue as I cannot afford to risk damaging a hard disk in daily use. - This behaviour is highly undesirable. Users who are informed that their hard disk has been wiped suffer greatly increased stress and in their panic may take irreversible actions in an attempt to remedy the situation. + I have not attempted to reproduce the issue as I cannot afford to risk + damaging a hard disk in daily use. + + This behaviour is highly undesirable. Users who are informed that their + hard disk has been wiped suffer greatly increased stress and in their + panic may take irreversible actions in an attempt to remedy the + situation. I am using GNOME 3.28.2 as supplied with Ubuntu 18.04.4 LTS. The Disks utility itself does not seem to have a version number. I originally reported the issue upstream at GNOME (https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/171) and they asked me to report the issue at Ubuntu instead. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1881298 Title: Incorrect disk information is displayed after creating a new partition To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1881298/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881298] [NEW] Incorrect disk information is displayed after creating a new partition
Public bug reported: After creating a new partition, GNOME Disks did not indicate whether or not the partition creation had succeeded. Instead, it indicated that several partitions had been destroyed, when this was not correct. I will describe the steps that lead to the issue: 1. A disk divided into several ext4 and NTFS partitions existed. 2. I shrank the last partition (NTFS) using Windows. 3. I rebooted into Ubuntu and GNOME Disks correctly displayed the empty space at the end of the disk. 4. I instructed GNOME Disks to create a new ext4 logical partition using the dialog opened by the + symbol. 5. The dialog disappeared without any indication of whether the operation had succeeded or not. At the same time, the disk graphic was updated (see screenshot in attachment). It said that the disk had only one partition (/) and the rest of the disk was free space. This implied that the operation had failed and all the other partitions had been destroyed. 6. I tried closing and opening Disks, but it continued to indicate that most of the disk had been wiped. 7. I looked at the relevant filesystems in GNOME Files (Nautilus) and GNOME System Monitor. The information there suggested that the existing partitions were intact and the new partition had been successfully created. 8. I rebooted Ubuntu and opened Disks again. It correctly displayed the new disk layout (see screenshot in attachment in comment below). I have not attempted to reproduce the issue as I cannot afford to risk damaging a hard disk in daily use. This behaviour is highly undesirable. Users who are informed that their hard disk has been wiped suffer greatly increased stress and in their panic may take irreversible actions in an attempt to remedy the situation. I am using GNOME 3.28.2 as supplied with Ubuntu 18.04.4 LTS. The Disks utility itself does not seem to have a version number. I originally reported the issue upstream at GNOME (https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/171) and they asked me to report the issue at Ubuntu instead. ** Affects: gnome-disk-utility Importance: Unknown Status: Unknown ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Attachment added: "What GNOME Disks Showed After Partition Creation" https://bugs.launchpad.net/bugs/1881298/+attachment/5378410/+files/What%20Disks%20Showed%20After%20Partition%20Creation.png ** Description changed: After creating a new partition, GNOME Disks did not indicate whether or not the partition creation had succeeded. Instead, it indicated that several partitions had been destroyed, when this was not correct. I will describe the steps that lead to the issue: A disk was divided into several ext4 and NTFS partitions. I shrank the last partition (NTFS) using Windows. I rebooted into Ubuntu and GNOME Disks correctly displayed the empty space at the end of the disk. I instructed GNOME Disks to create a new ext4 logical partition using the dialog opened by the + symbol. - The dialog disappeared without any indication of whether the operation had succeeded or not. At the same time, the disk graphic was updated (see screenshot above). It said that the disk had only one partition (/) and the rest of the disk was free space. This implied that the operation had failed and all the other partitions had been destroyed. + The dialog disappeared without any indication of whether the operation had succeeded or not. At the same time, the disk graphic was updated (see screenshot in attachment). It said that the disk had only one partition (/) and the rest of the disk was free space. This implied that the operation had failed and all the other partitions had been destroyed. I tried closing and opening Disks, but it continued to indicate that most of the disk had been wiped. I looked at the relevant filesystems in GNOME Files (Nautilus) and GNOME System Monitor. The information there suggested that the existing partitions were intact and the new partition had been successfully created. - I rebooted Ubuntu and opened Disks again. It correctly displayed the new disk layout: + I rebooted Ubuntu and opened Disks again. It correctly displayed the new disk layout (see screenshot in attachment in comment below). I have not attempted to reproduce the issue as I cannot afford to risk damaging a hard disk in daily use. This behaviour is highly undesirable. Users who are informed that their hard disk has been wiped suffer greatly increased stress and in their panic may take irreversible actions in an attempt to remedy the situation. - I am using GNOME 3.28.2 as supplied with Ubuntu 18.04.4 LTS. The Disks utility itself does not seem to have a version number. + + I am using GNOME 3.28.2 as supplied with Ubuntu 18.04.4 LTS. The Disks + utility itself does not seem to have a version number. + + I originally reported the issue upstream at GNOME + (https://gitlab.gnome.org/GNOME/g
[Bug 1880337] Re: Screen lock won't work
I find other extensions with same bug: Panel-OSD Unite -- 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/1880337 Title: Screen lock won't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881294] [NEW] Apparmor blocks evince GUI-Input-Dialogs
Public bug reported: Network Users (LDAP + NFS4 home) cannot interact with evince GUI-input- elements. * page navigation per number not possible * select pages to print not possible * save open PDF with different name not possible Local user on the same machine behaves as expected. apparmor messages in /var/log/syslog May 29 14:37:07 r002pc51 kernel: [15848.736916] audit: type=1400 audit(1590755827.768:827): apparmor="DENIED" operation="file_lock" profile="/usr/bin/evince" name="/home/teachers/ttfinr/.cache/event- sound-cache.tdb.2176809057334199ab75052753e0683a.x86_64-pc-linux-gnu" pid=34988 comm="evince" requested_mask="k" denied_mask="k" fsuid=4515 ouid=4515 May 29 14:37:07 r002pc51 kernel: [15848.739259] audit: type=1400 audit(1590755827.772:828): apparmor="DENIED" operation="link" profile="/usr/bin/evince" name="/home/teachers/ttfinr/.local/share/gvfs- metadata/.open04eaJ8" pid=34988 comm="pool-evince" requested_mask="l" denied_mask="l" fsuid=4515 ouid=4515 target="/home/teachers/ttfinr/.local/share/gvfs-metadata/home" May 29 14:37:07 r002pc51 kernel: [15848.739974] audit: type=1400 audit(1590755827.772:829): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/run/user/4515/gvfs- metadata/.openumWxE7" pid=34988 comm="pool-evince" requested_mask="r" denied_mask="r" fsuid=4515 ouid=4515 May 29 14:37:07 r002pc51 kernel: [15848.740088] audit: type=1400 audit(1590755827.772:830): apparmor="DENIED" operation="unlink" profile="/usr/bin/evince" name="/run/user/4515/gvfs- metadata/.openumWxE7" pid=34988 comm="pool-evince" requested_mask="d" denied_mask="d" fsuid=4515 ouid=4515 ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor envince -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1881294 Title: Apparmor blocks evince GUI-Input-Dialogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1881294/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880337] Re: Screen lock won't work
In my case I was able to narrow down the problem to the gTile extension. (I've never had Dash-to-panel installed.) Now all I have to do is find a way to live without gTile :) Thanks for the tip! -- 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/1880337 Title: Screen lock won't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874630] Re: not start without sudo
Yes, software-center is what was used when Unity was the default desktop environment. Moving to gnome-software (also known as ubuntu-software) which is the default for Ubuntu 19.10. ** Tags added: eoan ** Package changed: software-center (Ubuntu) => gnome-software (Ubuntu) ** Changed in: gnome-software (Ubuntu) Status: Incomplete => New -- 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/1874630 Title: not start without sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1874630/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874630] [NEW] not start without sudo
You have been subscribed to a public bug: To be able installing anything I have to run Ubuntu-software with sudo from terminal. sudo chown -Rh $USER:$USER ~/ not worked. Also interesting: If I do not start with sudo. I'm able to login to Ubutu-one but not to snap. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: eoan -- not start without sudo https://bugs.launchpad.net/bugs/1874630 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881284] [NEW] Pause the music after suspend
Public bug reported: Hi, I don't know how to describe it. What I basically need is pause the media/music automatically after I come back from suspend. Let's suppose we're suspending the laptop while playing the media (Spotify, youtube) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 29 18:09:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-04 (24 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 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/1881284 Title: Pause the music after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881284/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881273] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1881273/+attachment/5378368/+files/ProcEnviron.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/1881273 Title: Redo folder copy: incorrect recursion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881273/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881273] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1881273/+attachment/5378366/+files/GsettingsChanges.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/1881273 Title: Redo folder copy: incorrect recursion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881273/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881273] Re: Redo folder copy: incorrect recursion
apport information ** Tags added: apport-collected eoan ** Description changed: I did the following: - I copied folder `/somewhere/my-folder` to the same parent folder `/somewhere`, yielding `/somewhere/my-folder (copy)`. - I pressed ctrl+Z to undo this action (and confirmed), correctly causing `/somewhere/my-folder (copy)` to disappear. - I pressed shift+ctrl+Z to redo this action. This resulted not only in the reappearance of `/somewhere/my-folder (copy)` with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` was copied several times. I got: `/somewhere/my-folder (copy)/has/a/child.txt` (correct) `/somewhere/my-folder/has (copy)/a/child.txt` (wrong) `/somewhere/my-folder/has/a (copy)/child.txt` (wrong) `/somewhere/my-folder/has/a/child (copy).txt` (wrong) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.9 + Architecture: amd64 + CurrentDesktop: Unity:Unity7:ubuntu + DistroRelease: Ubuntu 19.10 + NonfreeKernelModules: nvidia wl + Package: nautilus 1:3.34.1-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18 + Tags: eoan + Uname: Linux 5.3.0-55-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2020-05-14 (14 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + usr_lib_nautilus: ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1881273/+attachment/5378365/+files/Dependencies.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/1881273 Title: Redo folder copy: incorrect recursion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881273/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881273] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1881273/+attachment/5378367/+files/ProcCpuinfoMinimal.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/1881273 Title: Redo folder copy: incorrect recursion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881273/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881273] Re: Redo folder copy: incorrect recursion
Thank you for reporting this bug and make ubuntu better! Please when filing bugs on ubuntu use ubuntu-bug packagename in the future so relevant system info gets pulled into your bug and developers can debug a better way. You can still pull the info in your existing bug with: apport-collect 1881273 in this stage, thank you! -- 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/1881273 Title: Redo folder copy: incorrect recursion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881273/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881273] [NEW] Redo folder copy: incorrect recursion
Public bug reported: I did the following: - I copied folder `/somewhere/my-folder` to the same parent folder `/somewhere`, yielding `/somewhere/my-folder (copy)`. - I pressed ctrl+Z to undo this action (and confirmed), correctly causing `/somewhere/my-folder (copy)` to disappear. - I pressed shift+ctrl+Z to redo this action. This resulted not only in the reappearance of `/somewhere/my-folder (copy)` with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` was copied several times. I got: `/somewhere/my-folder (copy)/has/a/child.txt` (correct) `/somewhere/my-folder/has (copy)/a/child.txt` (wrong) `/somewhere/my-folder/has/a (copy)/child.txt` (wrong) `/somewhere/my-folder/has/a/child (copy).txt` (wrong) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Description changed: I did the following: - I copied folder `/somewhere/my-folder` to the same parent folder `/somewhere`, yielding `/somewhere/my-folder (copy)`. - - I pressed ctrl+Z to undo this action (and confirmed), correctly causing `/somewhere/my-folder (copy)` + - I pressed ctrl+Z to undo this action (and confirmed), correctly causing `/somewhere/my-folder (copy)` to disappear. - I pressed shift+ctrl+Z to redo this action. This resulted not only in the reappearance of `/somewhere/my-folder (copy)` with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` was copied several times: I also got: `/somewhere/my-folder (copy)/has/a/child.txt` (correct) `/somewhere/my-folder/has (copy)/a/child.txt` (wrong) `/somewhere/my-folder/has/a (copy)/child.txt` (wrong) `/somewhere/my-folder/has/a/child (copy).txt` (wrong) ** Description changed: I did the following: - I copied folder `/somewhere/my-folder` to the same parent folder `/somewhere`, yielding `/somewhere/my-folder (copy)`. - I pressed ctrl+Z to undo this action (and confirmed), correctly causing `/somewhere/my-folder (copy)` to disappear. - I pressed shift+ctrl+Z to redo this action. - This resulted not only in the reappearance of `/somewhere/my-folder (copy)` with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` was copied several times: I also got: + This resulted not only in the reappearance of `/somewhere/my-folder (copy)` with the correct contents, but the file `/somewhere/my-folder/has/a/child.txt` was copied several times. I got: `/somewhere/my-folder (copy)/has/a/child.txt` (correct) `/somewhere/my-folder/has (copy)/a/child.txt` (wrong) `/somewhere/my-folder/has/a (copy)/child.txt` (wrong) `/somewhere/my-folder/has/a/child (copy).txt` (wrong) -- 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/1881273 Title: Redo folder copy: incorrect recursion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881273/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen
** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/-/issues/828 Importance: Unknown Status: Unknown ** No longer affects: mutter (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Triaged ** Changed in: xorg-server (Ubuntu) Importance: Undecided => Medium ** Tags added: fixed-in-1.20.9 fixed-upstream -- 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/1870512 Title: forced software cursor with PageFlip enabled triggers artifacts on screen To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1870512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881115] Re: desktop - no shift-delete, non localized menu
templates submenu is also missing on desktop...available in nautilus- window (i have created some templates to get the menu in nautilus- window) -- 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/1881115 Title: desktop - no shift-delete, non localized menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881115/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen
Fix in Xorg: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/447#note_515426 -- 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/1870512 Title: forced software cursor with PageFlip enabled triggers artifacts on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880337] Re: Screen lock won't work
That is bug 184. -- 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/1880337 Title: Screen lock won't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880337] Re: Screen lock won't work
Hi again, in my case, Dash-to-panel is the guilty, installed by synaptic... removing it and installing from Gnome.org solve the problem. -- 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/1880337 Title: Screen lock won't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880337] Re: Screen lock won't work
That's a good point. A few people are finding buggy extensions (especially dash-to-dock) are causing a crash on screen lock, which causes a blink and the lock to fail. That's mostly covered by bug 184. So yes, please do make sure you remove all your extensions as part of the testing process. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => 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/1880337 Title: Screen lock won't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880337] Re: Screen lock won't work
That's a good point. A few people are finding buggy extensions (especially dash-to-panel) are causing a crash on screen lock, which causes a blink and the lock to fail. That's mostly covered by bug 184. So yes, please do make sure you remove all your extensions as part of the testing process. -- 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/1880337 Title: Screen lock won't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880337] Re: Screen lock won't work
Good news, i find the issue, the problem are the gnome extensions, back up your .local/share/gnome-shell/ data and erase all your extensions, restart the shell and try to lock screen (it works for me). After, install one by one extensions and, for each, try lock screen since find the buggie extension. -- 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/1880337 Title: Screen lock won't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
