[Desktop-packages] [Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working
Sorry to hear of the problem. I followed the procedure mentioned in my initial post to create my launchers. I "solved" the problem by recreating my whole user profile. But the problem came back in limited forms. But not as bad. I am now largely free of issues and I put that down to software updates. If yours is a new build, you might try running all the updates. See also: https://askubuntu.com/questions/1261625/how-to-make-desktop-icons- display-on-startup-of-ubuntu-20-04-focal-fossa/1261626#1261626 which may help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1878392 Title: Ubuntu 20.04 Focal Fossa desktop launchers not working Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Bug description: Using the procedure here = https://linuxconfig.org/how-to-create-desktop-shortcut-launcher-on-ubuntu-20-04-focal-fossa-linux AND OTHERWISE I have successfully created launchable desktop app shortcuts. But they stop working: (1) no launch; (2) no right click context to make launchable; and (3) no app icon. They can even remain in ~/Desktop but disappear from the desktop view. A logout kills them. Creating another new launcher is successful and peculiarly triggers the temporary reactivation of all the others. But euphoria soon dies as they all revert to inertia later. My work around at present is to install PCManFM 1.3.1. Navigating to ~/Desktop on PCManFM, my Nautilus created launchers are all visible, launchable and have the usual colourful app icon features. But they remain inert in Nautilus. My Gnome version is: 3.36.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1878392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working
Hi Seb, I'm really sorry but that user is gone. Unless another user develops the same issue, I feel it may be appropriate to put this down as an aberration in Ubuntu but close the bug entry. (I do not know how to do that). Thanks again for your help. It is much appreciated. Tom -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1878392 Title: Ubuntu 20.04 Focal Fossa desktop launchers not working Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Using the procedure here = https://linuxconfig.org/how-to-create-desktop-shortcut-launcher-on-ubuntu-20-04-focal-fossa-linux AND OTHERWISE I have successfully created launchable desktop app shortcuts. But they stop working: (1) no launch; (2) no right click context to make launchable; and (3) no app icon. They can even remain in ~/Desktop but disappear from the desktop view. A logout kills them. Creating another new launcher is successful and peculiarly triggers the temporary reactivation of all the others. But euphoria soon dies as they all revert to inertia later. My work around at present is to install PCManFM 1.3.1. Navigating to ~/Desktop on PCManFM, my Nautilus created launchers are all visible, launchable and have the usual colourful app icon features. But they remain inert in Nautilus. My Gnome version is: 3.36.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1878392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working
Thank you Seb Once I realised that mine was the only user account on my home desktop PC with this problem, I tried deleting all hidden config files that included the words "Nautilus" or "Gnome". This did not help so I created another sudoer and removed my home folder. I then recreated my home folder using cp /etc/skel. As explained in my earlier post, this action has removed the problem. I now feel that this issue is unlikely to be replicable by others. However in case it useful I followed your suggestion and put "journalctl -b 0" into a terminal and below is the result. I have only copies part of the output. I'm afraid I do not understand any of this myself. -- Logs begin at Wed 2020-04-29 19:21:25 BST, end at Mon 2020-05-18 16:42:40 BS> May 17 13:04:20 susan kernel: microcode: microcode updated early to revision 0x> May 17 13:04:20 susan kernel: Linux version 5.4.0-29-generic (buildd@lgw01-amd6> May 17 13:04:20 susan kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-g> May 17 13:04:20 susan kernel: KERNEL supported cpus: May 17 13:04:20 susan kernel: Intel GenuineIntel May 17 13:04:20 susan kernel: AMD AuthenticAMD May 17 13:04:20 susan kernel: Hygon HygonGenuine May 17 13:04:20 susan kernel: Centaur CentaurHauls May 17 13:04:20 susan kernel: zhaoxin Shanghai May 17 13:04:20 susan kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 flo> May 17 13:04:20 susan kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE reg> May 17 13:04:20 susan kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX reg> May 17 13:04:20 susan kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]:> May 17 13:04:20 susan kernel: x86/fpu: Enabled xstate features 0x7, context siz> May 17 13:04:20 susan kernel: BIOS-provided physical RAM map: May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x-0x0005> May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x00058000-0x0005> May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x00059000-0x0009> May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x0009e000-0x0009> May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x0010-0x8b85> May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x8b852000-0x8b85> May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x8b859000-0x8c30> lines 1-23...skipping... -- Logs begin at Wed 2020-04-29 19:21:25 BST, end at Mon 2020-05-18 16:42:40 BST. -- May 17 13:04:20 susan kernel: microcode: microcode updated early to revision 0x27, date = 2019-02-26 May 17 13:04:20 susan kernel: Linux version 5.4.0-29-generic (buildd@lgw01-amd64-035) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 (Ubuntu 5.4.0-29.33-generic 5.4.30) May 17 13:04:20 susan kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=c977975b-e6da-444a-b063-5200452dc91f ro quiet splash vt.handoff=7 May 17 13:04:20 susan kernel: KERNEL supported cpus: May 17 13:04:20 susan kernel: Intel GenuineIntel May 17 13:04:20 susan kernel: AMD AuthenticAMD May 17 13:04:20 susan kernel: Hygon HygonGenuine May 17 13:04:20 susan kernel: Centaur CentaurHauls May 17 13:04:20 susan kernel: zhaoxin Shanghai May 17 13:04:20 susan kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' May 17 13:04:20 susan kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' May 17 13:04:20 susan kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' May 17 13:04:20 susan kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 May 17 13:04:20 susan kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. May 17 13:04:20 susan kernel: BIOS-provided physical RAM map: May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x-0x00057fff] usable May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x00058000-0x00058fff] reserved May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x00059000-0x0009dfff] usable May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x0009e000-0x0009] reserved May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x0010-0x8b851fff] usable May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x8b852000-0x8b858fff] ACPI NVS May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x8b859000-0x8c302fff] usable May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x8c303000-0x8c7fafff] reserved May 17 13:04:20 susan kernel: BIOS-e820: [mem 0x8c7fb000-0xaa02bfff] usable May 17 13:04:20 susan kernel: BIOS-e820: [mem 0xaa02c000-0xaa433fff] reserved May 17 13:04:20 susan kernel: BIOS-e820: [mem 0xaa434000-0xaa49bfff] usable May 17 13:04:20 susan kernel: BIOS-e820: [mem 0xaa49c000-0xaa5defff] ACPI NVS May 17 13:04:20 susan kernel: BIOS-e820: [mem 0xaa5df000-0xad
[Desktop-packages] [Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working
The behaviour of Nautilus desktop remains baffling. But I have resolved the problem on my PC by recreating my user profile and home user folder. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1878392 Title: Ubuntu 20.04 Focal Fossa desktop launchers not working Status in nautilus package in Ubuntu: Incomplete Bug description: Using the procedure here = https://linuxconfig.org/how-to-create-desktop-shortcut-launcher-on-ubuntu-20-04-focal-fossa-linux AND OTHERWISE I have successfully created launchable desktop app shortcuts. But they stop working: (1) no launch; (2) no right click context to make launchable; and (3) no app icon. They can even remain in ~/Desktop but disappear from the desktop view. A logout kills them. Creating another new launcher is successful and peculiarly triggers the temporary reactivation of all the others. But euphoria soon dies as they all revert to inertia later. My work around at present is to install PCManFM 1.3.1. Navigating to ~/Desktop on PCManFM, my Nautilus created launchers are all visible, launchable and have the usual colourful app icon features. But they remain inert in Nautilus. My Gnome version is: 3.36.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1878392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working
Sorry, I'm afraid I'n not very familiar with this. The steps I followed where in the link I gave: https://linuxconfig.org/how-to-create-desktop-shortcut-launcher-on- ubuntu-20-04-focal-fossa-linux There is now a YouTube showing the problem: https://youtu.be/irZME1Tt-EA Is there anything else I can do/should do to better explain how to replicate? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1878392 Title: Ubuntu 20.04 Focal Fossa desktop launchers not working Status in nautilus package in Ubuntu: Incomplete Bug description: Using the procedure here = https://linuxconfig.org/how-to-create-desktop-shortcut-launcher-on-ubuntu-20-04-focal-fossa-linux AND OTHERWISE I have successfully created launchable desktop app shortcuts. But they stop working: (1) no launch; (2) no right click context to make launchable; and (3) no app icon. They can even remain in ~/Desktop but disappear from the desktop view. A logout kills them. Creating another new launcher is successful and peculiarly triggers the temporary reactivation of all the others. But euphoria soon dies as they all revert to inertia later. My work around at present is to install PCManFM 1.3.1. Navigating to ~/Desktop on PCManFM, my Nautilus created launchers are all visible, launchable and have the usual colourful app icon features. But they remain inert in Nautilus. My Gnome version is: 3.36.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1878392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878392] [NEW] Ubuntu 20.04 Focal Fossa desktop launchers not working
Public bug reported: Using the procedure here = https://linuxconfig.org/how-to-create-desktop-shortcut-launcher-on-ubuntu-20-04-focal-fossa-linux AND OTHERWISE I have successfully created launchable desktop app shortcuts. But they stop working: (1) no launch; (2) no right click context to make launchable; and (3) no app icon. They can even remain in ~/Desktop but disappear from the desktop view. A logout kills them. Creating another new launcher is successful and peculiarly triggers the temporary reactivation of all the others. But euphoria soon dies as they all revert to inertia later. My work around at present is to install PCManFM 1.3.1. Navigating to ~/Desktop on PCManFM, my Nautilus created launchers are all visible, launchable and have the usual colourful app icon features. But they remain inert in Nautilus. My Gnome version is: 3.36.1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1878392 Title: Ubuntu 20.04 Focal Fossa desktop launchers not working Status in nautilus package in Ubuntu: New Bug description: Using the procedure here = https://linuxconfig.org/how-to-create-desktop-shortcut-launcher-on-ubuntu-20-04-focal-fossa-linux AND OTHERWISE I have successfully created launchable desktop app shortcuts. But they stop working: (1) no launch; (2) no right click context to make launchable; and (3) no app icon. They can even remain in ~/Desktop but disappear from the desktop view. A logout kills them. Creating another new launcher is successful and peculiarly triggers the temporary reactivation of all the others. But euphoria soon dies as they all revert to inertia later. My work around at present is to install PCManFM 1.3.1. Navigating to ~/Desktop on PCManFM, my Nautilus created launchers are all visible, launchable and have the usual colourful app icon features. But they remain inert in Nautilus. My Gnome version is: 3.36.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1878392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
My Asus ZenBook UX370UAF worked straight out of the box with Ubuntu 18.04. Since upgrading to Focal Fossa 20.04 it does not show. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783817] Re: Nautilus doesnt know what its doing, showing unneccesary progress bars
I find it most irritating when renaming a file. I just tested and the renaming file window and offer to cancel is on screen for 25 seconds. I also do not like the new design which provides a small pop up window to do a quick rename of a file. The filename is often bigger than the pop up window so I have to scroll to find my insertion point. It could be this overhead that is causing the bug which did not happen before 18.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1783817 Title: Nautilus doesnt know what its doing, showing unneccesary progress bars Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 GNOME nautilus 3.26.3 -When renaming a file it creates a warning "Pending operations on files, press cancel to cancel" but it appears AFTER the renaming process has finished (which is dealt with in a blink of an eye) -When moving even a small file (1Kb for example) it shows progress bar which is stuck at around 33% and dissapears after Nautilus finally realizes that the file is already moved Nautilus shouldnt display theese, especially the warning after renaming a file, and teh progress should only appear when dealing with large files The solution seems to be installing and enabling/running zeitgeist and also chown`ing its directory in .local/share recursively to the user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1783817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Not on first login but on switch user after entering correct password I get purple screen and mouse. Sometimes after a long delay I can get back to the login screen. I can usually force it back to the login screen by hitting a few random cycles of ctl+alt + F1, ctl+alt F2 and ctl+alt + F3. At this point, if I click on the the user that failed it shows a message about authorization problem (but the password was correct). At login of this user it then allows access. I know on subsequent logins it is going to fail as soon as I see the purple screen. If I see initial black, I know it is going to work OK. I noticed this issue on an initial clean build on erased disks. Concerned about my hardware, I rebuilt again from clean and the problem is the same. I do not have a graphics card. I have: Intel® Core™ i7-4790 CPU @ 3.60GHz × 8. Ram = 24g. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Confirmed Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: Won't Fix Bug description: WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1030615] Re: Braser hangs at end of burn
#578910 #904662 #549184 #661625 A Google of "The disc could not be ejected though it needs to be removed for the current operation to continue" reveals this bug has been around for a long time. I have been affected now for years by it. To avoid it I have tried using K3B instead but I get problems reusing K3B after close because it does not close properly I have to use system monitor to kill off all the K... activities. The best burner on Ubuntu for me has been Imgburn running under Wine. But it would be really nice if Brasero could be fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1030615 Title: Braser hangs at end of burn Status in “brasero” package in Ubuntu: Confirmed Bug description: After burning the disk (CD or DVD), Brasero tried to eject the disk - and fails with this message: Please eject the disc from "HL-DT-ST DVD-RAM GH22LP21" manually. The disc could not be ejected though it needs to be removed for the current operation to continue. Ejecting the disk does not cancel the message. After ejecting the disk and clicking cancel this message appears: Image successfully burned to DVD (or CD) (progress bar) Success Clicking close appears to close the application. However it still appears as a running process, which prevents it being launched again (either with right click against a file or from Main menu -> Sound and Video - Brasero Disk Burner until the running instance has been ended or killed. Other information Release: 12.04 Package version: 3.4.1-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: brasero 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 Date: Sun Jul 29 13:55:53 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1030615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
