[Bug 1977497] Re: Ubuntu 22.04 does not boot on legacy system. Works only when used with Rufus
** Description changed: What I did: Booting from Ubuntu 22.04, created with startup disk creator program of Ubuntu 16.04. What happened: - The grub menu is shown. I selected "try or install Ubuntu". I can see a blinking cursor on the top left of the screen. The rest of the screen is blank. The cursor just keeps blinking. Nothing else happens. + The grub menu is shown. I selected "try or install Ubuntu". I can see a blinking cursor on the top left of the screen. The rest of the screen is blank. The cursor just keeps blinking. Nothing else happens. Alternatives I tried: - I tried starting Ubuntu 22.04 in safe graphics mode, but that didn't work either. It was stuck at the blinking cursor. I tried writing the Ubuntu ISO using Etcher, but Etcher recommended using Rufus. On Windows 8.1, I ran Rufus and wrote the Ubuntu 22.04 ISO onto the pen drive using Rufus. I also selected the MBR option instead of GPT, and selected the additional options of writing some extra partition that's necessary for legacy computer support. + I tried starting Ubuntu 22.04 in safe graphics mode, but that didn't work either. It was stuck at the blinking cursor. On Windows 8.1, I ran Rufus and wrote the Ubuntu 22.04 ISO onto the pen drive using Rufus. I also selected the MBR option instead of GPT, and selected the additional options of writing some extra partition that's necessary for legacy computer support. - Result of the alternative method with Rufus: + Result of the alternative method with Rufus: This time, after selecting "try or install Ubuntu", after around 30 or 40 seconds of cursor blinking, Ubuntu's orange icon was shown and Ubuntu was loaded. The installation of Ubuntu worked fine. What needs to be fixed: - Please don't make us depend on a third party like Rufus. Not everyone is financially well off to keep buying new computers so often. Please provide built-in support for legacy systems within the Ubuntu 22.04 installer and all future Ubuntu versions for at least ten more years. + Please don't make us depend on a third party like Rufus. Not everyone is financially well off to keep buying new computers so often. Please provide built-in support for legacy systems within the Ubuntu 22.04 installer and all future Ubuntu versions for at least ten more years. System details: Hardware model: Gigabyte Technology Co., Ltd. GA-880GM-USB3 - Processor: AMD® Fx(tm)-4100 quad-core processor × 4 - RAM: 6GiB + Processor: AMD® Fx(tm)-4100 quad-core processor × 4 + RAM: 6GiB Graphics: AMD® Rs880 (built into the motherboard) OS: Ubuntu 22.04 LTS, 64-bit, gnome 42.0. Windowing system: Wayland - Some more info: - Even the current Windows 10 ISO does not boot unless the option for selecting legacy support is enabled in Rufus. I dearly hope the Linux, Mac and Windows communities come up with a better, more robust bootloader that "just-works". Sometimes, people like may want to install Ubuntu first and then install Windows for dual boot. But Windows has this sad monopoly of using the first partition. + Some more info: + Even the current Windows 10 ISO does not boot unless the option for selecting legacy support is enabled in Rufus. I tried writing the Windows ISO using Etcher in Ubuntu 16.04, but Etcher recommended using Rufus. I dearly hope the Linux, Mac and Windows communities come up with a better, more robust bootloader that "just-works". Sometimes, people like may want to install Ubuntu first and then install Windows for dual boot. But Windows has this sad monopoly of using the first partition. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-common 2.06-2ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 3 14:46:37 2022 InstallationDate: Installed on 2022-06-01 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: - LANGUAGE=en_IN:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_IN - SHELL=/bin/bash + LANGUAGE=en_IN:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_IN + SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) + + ps: Thanks for all the nice upgrades in Ubuntu 22.04. I like using it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977497 Title: Ubuntu 22.04 does not boot on legacy system. Works only when used with Rufus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1977497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977497] [NEW] Ubuntu 22.04 does not boot on legacy system. Works only when used with Rufus
Public bug reported: What I did: Booting from Ubuntu 22.04, created with startup disk creator program of Ubuntu 16.04. What happened: The grub menu is shown. I selected "try or install Ubuntu". I can see a blinking cursor on the top left of the screen. The rest of the screen is blank. The cursor just keeps blinking. Nothing else happens. Alternatives I tried: I tried starting Ubuntu 22.04 in safe graphics mode, but that didn't work either. It was stuck at the blinking cursor. I tried writing the Ubuntu ISO using Etcher, but Etcher recommended using Rufus. On Windows 8.1, I ran Rufus and wrote the Ubuntu 22.04 ISO onto the pen drive using Rufus. I also selected the MBR option instead of GPT, and selected the additional options of writing some extra partition that's necessary for legacy computer support. Result of the alternative method with Rufus: This time, after selecting "try or install Ubuntu", after around 30 or 40 seconds of cursor blinking, Ubuntu's orange icon was shown and Ubuntu was loaded. The installation of Ubuntu worked fine. What needs to be fixed: Please don't make us depend on a third party like Rufus. Not everyone is financially well off to keep buying new computers so often. Please provide built-in support for legacy systems within the Ubuntu 22.04 installer and all future Ubuntu versions for at least ten more years. System details: Hardware model: Gigabyte Technology Co., Ltd. GA-880GM-USB3 Processor: AMD® Fx(tm)-4100 quad-core processor × 4 RAM: 6GiB Graphics: AMD® Rs880 (built into the motherboard) OS: Ubuntu 22.04 LTS, 64-bit, gnome 42.0. Windowing system: Wayland Some more info: Even the current Windows 10 ISO does not boot unless the option for selecting legacy support is enabled in Rufus. I dearly hope the Linux, Mac and Windows communities come up with a better, more robust bootloader that "just-works". Sometimes, people like may want to install Ubuntu first and then install Windows for dual boot. But Windows has this sad monopoly of using the first partition. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: grub-common 2.06-2ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 3 14:46:37 2022 InstallationDate: Installed on 2022-06-01 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977497 Title: Ubuntu 22.04 does not boot on legacy system. Works only when used with Rufus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1977497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942245] Re: Option to change login screen color missing
Thank you Paul. I've mentioned it in Discourse https://discourse.ubuntu.com/t/changing-the-grub-splash-and-gdm-lock- screen-color/7516/15?u=navnav -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942245 Title: Option to change login screen color missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1942245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958719] Re: Copy paste does not work from and to Desktop
Even pasting with Ctrl+v to the Desktop does not work. From any folder on Nautilus to Desktop and Desktop to any folder on Nautilus. Both don't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958719 Title: Copy paste does not work from and to Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1958719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958719] [NEW] Copy paste does not work from and to Desktop
Public bug reported: A similar problem is reported here by someone: https://askubuntu.com/questions/1241475/cut-paste-or-copy-paste-not- working-on-ubuntu-20-04-on-using-right-click-context Everything was working fine when I had installed Ubuntu. This problem began either ever since I did an update or perhaps after I installed (don't know which) program. The problem: If I copy a file/folder directly from the Desktop, then open Nautilus and try to paste the file/folder into any other folder, the Paste option is shown as disabled, in the right click menu. Image attached. Same way, if I copy a file/folder from Nautilus and try pasting it directly onto the Desktop, the Paste option is shown as disabled in the right click menu. However, when I open the Desktop folder in Nautilus, I can copy or paste any files or folders to any other file or folder that's open in Nautilus. I'm sure this is not a file or folder permission issue. I'm able to copy and move the files/folders without sudo when I use the terminal. If I try to copy a file from Nautilus and right click on any folder on the Desktop, the "paste into folder" option is not available either. Guys, Ubuntu has such really annoying bugs related to the Desktop. Please fix them ASAP. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 22 20:17:40 2022 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'205' b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-10-24 (89 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN 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 ** Attachment added: "paste not available" https://bugs.launchpad.net/bugs/1958719/+attachment/5556386/+files/pasteDisabled.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958719 Title: Copy paste does not work from and to Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1958719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942246] [NEW] Option to change WiFi options not available after first typing it
Public bug reported: This is for Ubuntu 20.04 LTS. When I use the GUI to connect to WiFi (hidden network where the SSID is not broadcast or when the WiFi allows only devices with recognized MAC addresses to connect), I enter the name of the WiFi and the password and click ok to connect. It tries to connect and then says it could not connect. Now I want to try a different password, but the password field is un-editable. The GUI only allows me to try connecting to WiFi again. It doesn't allow changing the details for that particular WiFi connection. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942246 Title: Option to change WiFi options not available after first typing it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1942246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942245] [NEW] Option to change login screen color missing
Public bug reported: This is for Ubuntu 20.04 LTS. Not everyone likes the pink/purple colors of Ubuntu. We'd prefer to change it to grey/blue shades. But those options do not appear to be available now, as mentioned here: https://askubuntu.com/questions/1227070/how-do-i-change-login-screen- theme-or-background-in-ubuntu-20-04 Apart from login screen, there are a lot of other settings which need to be provided via the default GUI settings in Ubuntu, instead of expecting us to open up the /etc/default/grub file or installing gnome-tweaks. Some of these are: 1. The Ubuntu login screen color. 2. Grub timeout countdown and grub menu options order. 3. Ubuntu splash screen switched off during startup and shutdown. 4. Ubuntu firewall (ufw) being pre-installed and active. 5. GUI close button, maximise and minimize buttons being on the left side instead of right. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942245 Title: Option to change login screen color missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1942245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 449225] Re: Airplane mode doesn't persist through shutdown/startup
I'm facing this issue on an HP Omen laptop 15ek0018tx. Ubuntu 20.04 LTS 64 bit. Even if I switch off airplane mode, it turns on when I restart. On switching off airplane mode, Bluetooth annoyingly becomes active. Please fix this to be able to permanently switch off airplane mode and Bluetooth (and any other such settings). https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781049 Many other people are facing this too. https://www.google.com/search?q=airplane+mode+turns+on+automatically+ubuntu=airplane+mode+turns+on+automatically+ubuntu=chrome..69i57j69i60.10167j0j4=chrome=UTF-8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/449225 Title: Airplane mode doesn't persist through shutdown/startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kairmode/+bug/449225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942242] [NEW] keyboard repeat rate setting and mouse scroll setting missing in Ubuntu 20.04 LTS
Public bug reported: Normally, system settings GUI should have a setting, which is not available in Ubuntu 20.04 LTS. These are: 1. The option to change the keyboard's repeat rate on key press. 2. The option to set the number of lines to scroll on using the mouse wheel and to set the mouse pointer speed of movement. Please make these available via the GUI settings. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942242 Title: keyboard repeat rate setting and mouse scroll setting missing in Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1942242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928586] Re: Desktop icons disappearing
No. It's not bug 1812883. I've actually described in detail what happens. The desktop icons aren't flashing. They disappear and stay invisible until I reactivate USB tethering. Let me describe the steps again: Step 1. Desktop icons are visible. Step 2. I connect my phone to the PC. Desktop icons are still visible. At this point, there's a dialog box on the phone's screen, asking "Allow access to phones data?". Options for me are to click "Allow" or "Deny". Step 3. Whether I click Allow or Deny, the Desktop icons disappear. Step 4. I activate USB tethering, and the Desktop icons appear. Step 5. I deactivate USB tethering, and the Desktop icons are still visible. The phone is again asking the Allow/Deny question. Step 6. Goto Step 3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928586 Title: Desktop icons disappearing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1928586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928586] [NEW] Desktop icons disappearing
Public bug reported: This is in Ubuntu 20.10 Groovy Gorilla. The bug: When connecting to USB tethering and allowing access to the phone's filesystem, Ubuntu's Desktop icons disappear. Steps to reproduce: Connect a phone to the computer via USB tethering (am a bit uneasy about mentioning which model phone it is). Switch on USB tethering and then switch off USB tethering in the phone's Mobile hotspot and tethering options. The phones screen will popup a dialog box asking "Allow access to phone data?" (which is a way to give the computer access to the phone's filesystem). You can click either "Allow" or "Deny". When either "Allow" or "Deny" is selected, the Desktop icons on Ubuntu disappear. When USB tethering is switched back on, the Desktop icons reappear. I've attached a video of the phenomenon. The video starts with USB tethering being switched on, which is why you can see the desktop icons. Then when USB tethering is switched off and "Allow" is clicked on the phone, the icons disappear and then they reappear when USB tethering is switched on again. This bug is probably related to bugs #1928206 and #1928213, which indicate that there are some inconsistencies with how the Nautilus Desktop works with respect to a Nautilus window. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Video of the problem" https://bugs.launchpad.net/bugs/1928586/+attachment/5497965/+files/disappearingIcons.mp4 ** Description changed: This is in Ubuntu 20.10 Groovy Gorilla. The bug: When connecting to USB tethering and allowing access to the phone's filesystem, Ubuntu's Desktop icons disappear. - Steps to reproduce: - Connect a phone to the computer via USB tethering (am a bit uneasy about mentioning which model phone it is). Switch on USB tethering and then switch off USB tethering in the phone's Mobile hotspot and tethering options. The phones screen will popup a dialog box asking "Allow access to phone data?" (which is a way to give the computer access to the phone's filesystem. You can click either "Allow" or "Deny". When either "Allow" or "Deny" is selected, you can access the phone's files via Nautilus, but the Desktop icons on Ubuntu disappear. When USB tethering is switched back on, the Desktop icons reappear. + Steps to reproduce: + Connect a phone to the computer via USB tethering (am a bit uneasy about mentioning which model phone it is). Switch on USB tethering and then switch off USB tethering in the phone's Mobile hotspot and tethering options. The phones screen will popup a dialog box asking "Allow access to phone data?" (which is a way to give the computer access to the phone's filesystem). You can click either "Allow" or "Deny". When either "Allow" or "Deny" is selected, the Desktop icons on Ubuntu disappear. When USB tethering is switched back on, the Desktop icons reappear. I've attached a video of the phenomenon. The video starts with USB tethering being switched on, which is why you can see the desktop icons. Then when USB tethering is switched off, the icons disappear and then they reappear when USB tethering is switched on again. This bug is probably related to bugs #1928206 and #1928213, which indicate that there are some inconsistencies with how the Nautilus Desktop works with respect to a Nautilus window. ** Description changed: This is in Ubuntu 20.10 Groovy Gorilla. The bug: When connecting to USB tethering and allowing access to the phone's filesystem, Ubuntu's Desktop icons disappear. Steps to reproduce: Connect a phone to the computer via USB tethering (am a bit uneasy about mentioning which model phone it is). Switch on USB tethering and then switch off USB tethering in the phone's Mobile hotspot and tethering options. The phones screen will popup a dialog box asking "Allow access to phone data?" (which is a way to give the computer access to the phone's filesystem). You can click either "Allow" or "Deny". When either "Allow" or "Deny" is selected, the Desktop icons on Ubuntu disappear. When USB tethering is switched back on, the Desktop icons reappear. I've attached a video of the phenomenon. The video starts with USB tethering being switched on, which is why you can see the desktop icons. - Then when USB tethering is switched off, the icons disappear and then - they reappear when USB tethering is switched on again. + Then when USB tethering is switched off and "Allow" is clicked on the + phone, the icons disappear and then they reappear when USB tethering is + switched on again. This bug is probably related to bugs #1928206 and #1928213, which indicate that there are some inconsistencies with how the Nautilus Desktop works with respect to a Nautilus window. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928586 Title: Desktop icons
[Bug 1867092] Re: Failed to set MokListRT: Invalid Parameter
@Dimitri: Just noticed that Impish is part of a daily build. I live in a 3rd world country, and use the internet from my mobile phone. There's a daily limit of 1GB and the download speed is around 1MBps to 5MBps. Impish is 2.6GB. If you've made any patches that support legacy motherboards and helps avoid the errors during installation and boot, please let me know when those patches are applied to the LTS version. I've been wanting to install the LTS version, but as I remember, I had faced installation issues, which is why I downloaded Groovy Gorilla...where I faced installation issues again, but somehow managed to get through. I need to use a torrent to download Ubuntu over a span of multiple days. Kinda hoping y'all keep the ISO size small. I've also been informing Steam, Snap and the Android SDK teams that these massive download sizes are quite crippling for people in 3rd world countries :-) Waiting to hear about the LTS patch that I could test for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867092 Title: Failed to set MokListRT: Invalid Parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867092] Re: Failed to set MokListRT: Invalid Parameter
@Steve: I had mentioned installer issues in Comment 12 for bug 1905491 (https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1905491/comments/12). Entered my computer's BIOS and checked...there was no option for secure boot or MokManager. Very confident that the old BIOS does not support these. The following partitions were what got automatically created: DeviceType. /dev/sda1 BIOS boot. /dev/sda2 EFI System. /dev/sda3 Linux filesystem. @Dimitri: It'll be many days before I can download and try a live USB boot of Impish. Although I'm not sure if live boot will show the error I've mentioned in comment #28. The error of comment #30 I could perhaps reproduce, by creating a dual boot with Groovy Gorilla. It'll take a while before I can start with this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867092 Title: Failed to set MokListRT: Invalid Parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926932] Re: Error message too short to understand what is wrong
@Daniel. I ran the command in command #4. That's a lot of sensitive info, in my opinion, to post on a public forum. Besides, this bug is about the display of an error message, and does not require all that info. For any future bug reports that do require such information, it'd help to either have a private mode of submitting info, which allows only a limited number of legit people to view the details, or to request the user for specific portions of the journalctl output, explaining why that info is required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926932 Title: Error message too short to understand what is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926932] Re: Error message too short to understand what is wrong
Also, I've marked bug 1928208 (https://bugs.launchpad.net/ubuntu/+bug/1928208) as a duplicate of this bug. 1928208 has a better image description of how the problem could be solved, by displaying the message higher up. Perhaps what could also be included, is the functionality of taking to the user to a screen where they can see more details about the message if they click the message. I noticed that clicking a circle near the date displayed, opens up a box that shows recent messages. Perhaps this existing functionality could be developed further (image attached) to be made more useful in terms of displaying more details. ** Attachment added: "messageDetailsDisplay.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926932/+attachment/5497391/+files/messageDetailsDisplay.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926932 Title: Error message too short to understand what is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928208] Re: Notification messages block the screen
*** This bug is a duplicate of bug 1926932 *** https://bugs.launchpad.net/bugs/1926932 ** This bug has been marked a duplicate of bug 1926932 Error message too short to understand what is wrong -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928208 Title: Notification messages block the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926932] Re: Error message too short to understand what is wrong
@Daniel: I'm not reporting a bug about the error displayed in the image I attached. I'm saying that the message bubble was too small to display the error, and even if I clicked the message bubble, it didn't expand to display the full error message. Moreover, the bubble appeared over some folders, and temporarily blocked my view of the files/folders in Nautilus. @Chris. I ran appport-collect for this bug just now. When I received your message about running apport-collect, I didn't have a clue about how it'd work and what the point of it was. So I didn't run it until now. I've been through the https://wiki.ubuntu.com/ReportingBugs page innumerable times, and I assure you, it's extremely frustrating to read through all that text and not be able to figure out why y'all wrote all that, when all I wanted to do was to just search if the bug is already reported, and then just file a bug report. I could volunteer to improve the UX of that wiki page. But Perhaps what's more important, is to not require users to read through all of that, and maybe have a web page that would take them through a step-by-step process of what they want to achieve. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926932 Title: Error message too short to understand what is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926932] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1926932/+attachment/5497363/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926932 Title: Error message too short to understand what is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926932] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1926932/+attachment/5497364/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926932 Title: Error message too short to understand what is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926932] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1926932/+attachment/5497366/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926932 Title: Error message too short to understand what is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926932] Re: Error message too short to understand what is wrong
apport information ** Tags added: apport-collected ** Description changed: This is on Ubuntu 20.10 (Groovy Gorilla). I placed a text file on my desktop, and on clicking it, I was shown the error "Execution of /home/myUsername/Desktop/.goutputstream-WU... Command not found". Even on clicking the error message that popped up, it didn't expand to show more details. So basically, the bug I'm reporting is about error messages being too short/obscure to be useful for users to figure out what the problem actually is. Image attached. The black spot in the middle was added by me to obscure the username. - (on a a side note, I was clicking a plain text document which had the - checkbox for "allow executing file as a program" ticked). Clicking any - other textfile didn't show this error. + (on a a side note, I was clicking a plain text document which had the checkbox for "allow executing file as a program" ticked). Clicking any other textfile didn't show this error. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.6 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2021-05-02 (12 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + Package: gnome-shell 3.38.1-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 + RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 + Tags: groovy + Uname: Linux 5.8.0-50-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1926932/+attachment/5497361/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926932 Title: Error message too short to understand what is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926932] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1926932/+attachment/5497362/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926932 Title: Error message too short to understand what is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928206] Re: File extension included in renaming selection
Thank you Sebastien. Nice to know the bug was already reported two years ago. Didn't know y'all filed bug reports in GitLab too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928206 Title: File extension included in renaming selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1928206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867092] Re: Failed to set MokListRT: Invalid Parameter
@Steve: Ok, the /sys/firmware/efi folder exists, so I guess there might be EFI support somewhere, but I'm quite confident the BIOS options have nothing regarding MokManager or UEFI. After creating a bootable USB (Groovy Gorilla), it wouldn't boot. I don't remember the error message, but there was some solution on the internet which I followed to (I think), convert the USB filesystem to GPT or something, and only then it worked. Toward the end of the Ubuntu installation, I encountered this error: "Executing grub-install /dev/sda failed. This is a fatal error" (Image attached). ** Attachment added: "installIssue.png" https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1867092/+attachment/5496656/+files/installIssue.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867092 Title: Failed to set MokListRT: Invalid Parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928213] [NEW] Open with other application not working for multi file select and not showing cascading menu for single file select
Public bug reported: This is in Ubuntu 20.10 Groovy Gorilla. Problem 1: As shown in the attached image, on selecting multiple files and right clicking to "Open with other application", the option for opening the files is not enabled. Problem 2: When right clicking a single file, the "Open with other application" is visible, but does not show a cascading dropdown menu like it used to in Ubuntu 16.04. The cascading menu would help avoid some unnecessary extra clicks. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "openWithOtherApplicationNotWorkingToOpenWithGimp.png" https://bugs.launchpad.net/bugs/1928213/+attachment/5496647/+files/openWithOtherApplicationNotWorkingToOpenWithGimp.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928213 Title: Open with other application not working for multi file select and not showing cascading menu for single file select To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928208] [NEW] Notification messages block the screen
Public bug reported: This is in Ubuntu 20.10 Groovy Gorilla. There are many notification messages (as shown in the attachment) that pop up and interfere by blocking the view and hindering the ability of the user to proceed normally. I can only assume this is a bug where the positioning of the message went wrong. As shown in the attachment, the yellow arrow points to the message popup. The green arrow shows that the time could be displayed more to the right. The red arrow shows where such notification messages could be displayed so that they don't interfere. Other such messages are when opening a folder, a popup says "Files. Home is ready". Or if an application opens in the background "Software updater is ready". Please reposition these messages higher. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "InterferingMessage.png" https://bugs.launchpad.net/bugs/1928208/+attachment/5496645/+files/InterferingMessage.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928208 Title: Notification messages block the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928206] [NEW] File rename selection and single click do not work uniformly across the Files application
Public bug reported: This is on Ubuntu 20.10 Groovy Gorilla. Problem1: If I open Files (the Nautilus equivalent) and select a file and press F2 or right click and select "rename", I'm given the option of renaming the file. If the filename is someFile.txt, the "someFile" portion is highlighted automatically, so when I start renaming it, the ".txt" portion remains unaffected. This is the normal and expected behaviour. However, when I do the same thing directly on the Desktop for any file on the Desktop, the entire "someName.txt" gets highlighted, and the full name isn't even shown at first glance. The attachments show details. Problem2: In Files preferences > Behaviour > Open Action, if I select "Single click to open items", it works fine everywhere except for files on the Desktop, where I have to double click a file to open it. So the bug here is that there seems to be some inconsistency in the behaviour of files on the Desktop vs. the files that are opened in the Files window. If any of the Desktop files are opened in Files, it works fine. The problem happens only when performing these actions directly on files that are on the Desktop. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "renamingAndSingleClick.png" https://bugs.launchpad.net/bugs/1928206/+attachment/5496644/+files/renamingAndSingleClick.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928206 Title: File rename selection and single click do not work uniformly across the Files application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926932] [NEW] Error message too short to understand what is wrong
Public bug reported: This is on Ubuntu 20.10 (Groovy Gorilla). I placed a text file on my desktop, and on clicking it, I was shown the error "Execution of /home/myUsername/Desktop/.goutputstream-WU... Command not found". Even on clicking the error message that popped up, it didn't expand to show more details. So basically, the bug I'm reporting is about error messages being too short/obscure to be useful for users to figure out what the problem actually is. Image attached. The black spot in the middle was added by me to obscure the username. (on a a side note, I was clicking a plain text document which had the checkbox for "allow executing file as a program" ticked). Clicking any other textfile didn't show this error. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "error message" https://bugs.launchpad.net/bugs/1926932/+attachment/5494346/+files/textEditorError.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926932 Title: Error message too short to understand what is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1926932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905491] Re: Recent (Nov 2020) ISO copied to USB Drive cannot load
Ubuntu version: 20.10 Groovy Gorilla. PC motherboard: Gigabyte 880GM-USB3 (rev3.1). The problem: Using Ubuntu's startup disk creator, I created an image of Groovy Gorilla's ISO onto a pen drive (formatted with NTFS). I booted from the pen drive and am shown an error: "cannot find grub_platform". Then I'm presented with a blank screen with a blinking cursor at the top left corner of the screen. It remains stuck at that. Someone else who experienced this: https://askubuntu.com/questions/1288476/can-not-install-from-usb-with-error-cannot-find-grub-platform/1335403. Solution: As pdecat mentioned, converting GPT to MBR helps. Why this needs fixing: Not everyone uses a modern PC with UEFI support. Just as in this bug (https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1867092/comments/28), all sub-versions of Ubuntu 20 and above, need to be patched to have some kind of legacy support. Not all users would have sufficient tech knowledge to search and find this solution. ** Changed in: usb-creator (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905491 Title: Recent (Nov 2020) ISO copied to USB Drive cannot load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1905491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867092] Re: Failed to set MokListRT: Invalid Parameter
I faced this, but not on a Mac. I have an ordinary Desktop PC with a Gigabyte 880GM-USB3 (rev3.1) motherboard. This old motherboard does not have secure boot or MokManager or UEFI etc. It has a legacy BIOS. I installed Ubuntu 20.10 (Groovy Gorilla) yesterday. Each time I start the PC, I'm shown the following message for around 10 seconds and only then it proceeds to grub: Failed to set MokListRT: Invalid Parameter Could not create MokListRT: Invalid Parameter Importing MOK states has failed: import_mok_state() failed: Invalid Parameter Continuing boot since secure mode is disabled System BootOrder not found. Initializing defaults. Creating boot entry "Boot0002" with label "ubuntu" for file "\EFI\ubuntu\shimx64.efi" Failed to set MokListRT: Invalid Parameter Could not create MokListRT: Invalid Parameter Import MOK states has failed: import_mok_state() failed: Invalid Parameter Continuing boot since secure mode is disabled. I've attached an image of the error screen. The annoying thing about this bug is that each time I start my PC, this message is shown for 10 seconds. Please fix this. Many people still use old computers that don't have MokManager etc. Please take that into account. ** Attachment added: "Failed to set MokListRT: Invalid Parameter" https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1867092/+attachment/5494299/+files/startupError -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867092 Title: Failed to set MokListRT: Invalid Parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 451148] Re: Repaint Bugs in all gnome-applications
The bug seems to appear only, when using 2 monitors. Even after 2 complete reinstalls. I'm using a macbook pro with the newest nvidia drivers. After heavy usage all applications suffer from this, but in the most cases it only affects gnome apps. Can be reproduced everytime when I need to scroll. ** Summary changed: - Repaint Bugs on Gedit, Nautilus, software-center etc. + Repaint Bugs in all gnome-applications -- Repaint Bugs in all gnome-applications https://bugs.launchpad.net/bugs/451148 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 467069] Re: Printing everything zoomed in on Samsung ML-2010
Forget it, I fixed it by downloading the original PPD file. I guess I'd corrupted the old one. Thanks anyway. -- Printing everything zoomed in on Samsung ML-2010 https://bugs.launchpad.net/bugs/467069 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 467069] Re: Printing everything zoomed in on Samsung ML-2010
** Attachment added: troubleshoot.txt http://launchpadlibrarian.net/34794959/troubleshoot.txt -- Printing everything zoomed in on Samsung ML-2010 https://bugs.launchpad.net/bugs/467069 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 467069] [NEW] Printing everything zoomed in on Samsung ML-2010
Public bug reported: Everything I try to print comes out zoomed in to roughly 150% width- wise, like it should be split into two side-by-side pages. The length is fine. I checked all the printing options and it's all set to default values, nothing is set to zoom or booklet print or anything like that. I also tried changing the drivers to no avail. Even tried installing the Samsung linux drivers but that didn't help anything either. Running Ubuntu 9.10 64-bit since the Beta with printing issues on and off over the last few releases. Playing around with the drivers usually fixes it but I'm stuck this time. Any help would be hugely appreciated- I'm a student and I have tons of notes to print everyday. Troubleshooting report attached. Thanks. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: ml-2010 printing zoom -- Printing everything zoomed in on Samsung ML-2010 https://bugs.launchpad.net/bugs/467069 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 451148] Re: Repaint Bugs on Gedit, Nautilus, software-center etc.
** Attachment added: screenshot1.png http://launchpadlibrarian.net/33649211/screenshot1.png ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/33649212/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/33649213/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/33649214/ProcStatus.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/33649215/XsessionErrors.txt -- Repaint Bugs on Gedit, Nautilus, software-center etc. https://bugs.launchpad.net/bugs/451148 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 451148] [NEW] Repaint Bugs on Gedit, Nautilus, software-center etc.
Public bug reported: Binary package hint: gedit $ lsb_release -rd Description:Ubuntu karmic (development branch) Release:9.10 I have noticed this everytime in gedit, when i have to scroll and several times in nautilus and the software center. ProblemType: Bug Architecture: amd64 Date: Wed Oct 14 12:11:08 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/gedit NonfreeKernelModules: nvidia Package: gedit 2.28.0-0ubuntu1 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-13.43-generic SourcePackage: gedit Uname: Linux 2.6.31-13-generic x86_64 ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Repaint Bugs on Gedit, Nautilus, software-center etc. https://bugs.launchpad.net/bugs/451148 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 182996] Re: [hardy] kernel 2.6.24-3-generic #1 SMP -- ide cdrom hdc: status error: error=0x00 { }
I too am experiencing this in Hardy with 2.6.24 when I was not in Gutsy
merely an hour ago. My optical drive (a Plextor PX-740A, connected as
master to my only IDE controller as /dev/hda) is empty to start with,
refuses to open once in Ubuntu (but works fine elsewhere), and I receive
a large amount of output. All HDDs are connected through SATA and
continue to work properly. This particular Plextor uses a Philips
chipset if I recall correctly, if that matters at all...
$ uname -a
Linux seeker 2.6.24-4-386 #1 Mon Jan 14 16:49:51 UTC 2008 i686 GNU/Linux
From dmesg (extra verbose, just in-case it helps):
[ 28.768452] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[ 28.768454] ide: Assuming 33MHz system bus speed for PIO modes; override
with idebus=xx
[ 28.768783] NFORCE-MCP55: IDE controller (0x10de:0x036e rev 0xa1) at PCI
slot :00:04.0
[ 28.768798] NFORCE-MCP55: not 100% native mode: will probe irqs later
[ 28.768801] NFORCE-MCP55: :00:04.0 (rev a1) UDMA133 controller
[ 28.768805] ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA,
hdb:DMA
[ 28.768809] NFORCE-MCP55: IDE port disabled
[ 28.768812] Probing IDE interface ide0...
[ 28.782775] SCSI subsystem initialized
[ 28.806646] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI)
Driver
[ 28.822517] libata version 3.00 loaded.
[ 28.986818] Floppy drive(s): fd0 is 1.44M
[ 29.003938] FDC 0 is a post-1991 82077
[ 30.204248] hda: PLEXTOR DVDR PX-740A, ATAPI CD/DVD-ROM drive
[ 30.204266] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[ 30.204714] hda: UDMA/33 mode selected
[ 30.205099] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[ 30.205298] hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
[ 30.205301] hda: task_in_intr: error=0x04 { AbortedCommand }
[ 30.205302] ide: failed opcode was: 0xa1
...
[ 31.528645] scsi0 : sata_nv
[ 31.528934] scsi1 : sata_nv
[ 31.529066] ata1: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xdc00 irq 16
[ 31.529068] ata2: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xdc08 irq 16
[ 31.995930] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 32.046691] ata1.00: ATA-7: ST3320620AS, 3.AAK, max UDMA/133
[ 32.046693] ata1.00: 625142448 sectors, multi 1: LBA48 NCQ (depth 0/32)
[ 32.113330] ata1.00: configured for UDMA/133
[ 32.579846] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 32.630990] ata2.00: ATA-7: ST3160812AS, 3.AAH, max UDMA/133
[ 32.630992] ata2.00: 312581808 sectors, multi 1: LBA48 NCQ (depth 0/32)
[ 32.697624] ata2.00: configured for UDMA/133
[ 32.697681] scsi 0:0:0:0: Direct-Access ATA ST3320620AS 3.AA
PQ: 0 ANSI: 5
[ 32.697881] scsi 1:0:0:0: Direct-Access ATA ST3160812AS 3.AA
PQ: 0 ANSI: 5
[ 32.697917] ACPI: PCI Interrupt :00:05.1[B] - Link [APSJ] - GSI 22
(level, low) - IRQ 17
[ 32.697944] PCI: Setting latency timer of device :00:05.1 to 64
[ 32.698089] scsi2 : sata_nv
[ 32.698176] scsi3 : sata_nv
[ 32.698303] ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xc800 irq 17
[ 32.698305] ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xc808 irq 17
[ 33.163766] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 33.217388] ata3.00: ATA-7: ST3160812AS, 3.AAH, max UDMA/133
[ 33.217389] ata3.00: 312581808 sectors, multi 1: LBA48 NCQ (depth 0/32)
[ 33.284020] ata3.00: configured for UDMA/133
[ 33.595697] ata4: SATA link down (SStatus 0 SControl 300)
[ 33.605932] scsi 2:0:0:0: Direct-Access ATA ST3160812AS 3.AA
PQ: 0 ANSI: 5
[ 33.605964] ACPI: PCI Interrupt :00:05.2[C] - Link [ASA2] - GSI 21
(level, low) - IRQ 18
[ 33.605985] PCI: Setting latency timer of device :00:05.2 to 64
[ 33.606158] scsi4 : sata_nv
[ 33.606253] scsi5 : sata_nv
[ 33.606370] ata5: SATA max UDMA/133 cmd 0xc400 ctl 0xc000 bmdma 0xb400 irq 18
[ 33.606372] ata6: SATA max UDMA/133 cmd 0xbc00 ctl 0xb800 bmdma 0xb408 irq 18
[ 33.915652] ata5: SATA link down (SStatus 0 SControl 300)
[ 34.235608] ata6: SATA link down (SStatus 0 SControl 300)
[ 34.246150] ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
[ 34.246157] ACPI: PCI Interrupt :01:0b.0[A] - Link [APC4] - GSI 19
(level, low) - IRQ 20
[ 34.295879] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[20]
MMIO=[fdeff000-fdeff7ff] Max Packet=[2048] IR/IT contexts=[4/8]
[ 34.300872] Driver 'sd' needs updating - please use bus_type methods
[ 34.301094] sd 0:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB)
[ 34.301101] sd 0:0:0:0: [sda] Write Protect is off
[ 34.301103] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 34.301112] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[ 34.301137] sd 0:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB)
[ 34.301142] sd 0:0:0:0: [sda] Write Protect is off
[ 34.301144] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 34.301151] sd 0:0:0:0: [sda] Write
[Bug 121955] Re: wpa supplicant bug, causes random crashes to su processes
** Attachment added: lspci-vvn.log http://launchpadlibrarian.net/8218626/lspci-vvn.log -- wpa supplicant bug, causes random crashes to su processes https://bugs.launchpad.net/bugs/121955 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121955] Re: wpa supplicant bug, causes random crashes to su processes
Hi Thank you for the quick reply and I'm sorry for my slow response (nazi email filter). Unfortunately the system hasn't crashed today so I can't include a dmseg log of a crash. But I can include all the other information you requested. I hope this helps. I'll try to get a matching set of logs as soon as I can. Thank you for looking at this for me. ** Attachment added: lscpi-vv.log http://launchpadlibrarian.net/8218624/lscpi-vv.log -- wpa supplicant bug, causes random crashes to su processes https://bugs.launchpad.net/bugs/121955 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121955] Re: wpa supplicant bug, causes random crashes to su processes
** Attachment added: lspci-vvn.log http://launchpadlibrarian.net/8218629/lspci-vvn.log -- wpa supplicant bug, causes random crashes to su processes https://bugs.launchpad.net/bugs/121955 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121955] Re: wpa supplicant bug, causes random crashes to su processes
** Attachment added: proc_version.log http://launchpadlibrarian.net/8218631/proc_version.log -- wpa supplicant bug, causes random crashes to su processes https://bugs.launchpad.net/bugs/121955 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121955] Re: wpa supplicant bug, causes random crashes to su processes
** Attachment added: uname-a.log http://launchpadlibrarian.net/8218635/uname-a.log -- wpa supplicant bug, causes random crashes to su processes https://bugs.launchpad.net/bugs/121955 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121955] wpa supplicant bug, causes random crashes to su processes
Public bug reported: Hello Could I first say that I'm still rather new to Linux, I appologise if I report this bug incorrectly, I'm willing to listen to any comments. I upgraded my girlfriends computer from Edgy to Fiesty and its been having having random crashes, there doesn't appear to be any sequence to trigger it off (it can happen sometimes 5 time in 1 hour, or maybe just once a day). The whole system doesn't freeze, instead only certain processes appear frozen (mainly X and GUI programs). For example once the crash happens I can't open a new terminal window in X (existing terminals and open programs worked with limited effect) and the internet cuts out. I have to press CTRL+ALT+F1 to get a new command line. Once logged on I can do anything except execute super user processes (like trying to restart gdm). The system is such that I'm forced to resort to SysRq to restart my computer safely. I've tried to SysRq kill all process/send SIGTERM to all processes except init/send SIGKILL to all processes except init/call oom_kill/make nice realtime processes. None seem to recover the system to full operation :( I've included a tracedump for you to see, I suspect wpasupplicant is causing a problem (or possibly ndiswrapper and wpasupplicant) Our computer is a P3 (coppermine) 800MHz, 256Mb ram, fiesty, D-link DWL-G520+ Wireless PCI Adapter (not the best stats, but I'm afraid we're not that well off). Also this might be important: when I upgraded from edgy I couldn't get ndiswrapper from the repository to work, so I downloaded it from the ndiswrapper website and installed it from source (version 1.47 currently). I've also run memtest and no errors found and checked hard drive for errors and no bad clusters. I hope you can help me, otherwise we might have to buy windows XP for this computer, its not a nice thought :( ** Affects: Ubuntu Importance: Undecided Status: New -- wpa supplicant bug, causes random crashes to su processes https://bugs.launchpad.net/bugs/121955 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121955] Re: wpa supplicant bug, causes random crashes to su processes
I've attached the kernel log, the crash I believe happened at around 7:09am while I was on the net, but I only noticed the system was partially froozen (and net cut out) at 7:13am I hope this helps ** Attachment added: kernel log http://launchpadlibrarian.net/8175625/kern.log -- wpa supplicant bug, causes random crashes to su processes https://bugs.launchpad.net/bugs/121955 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121955] Re: wpa supplicant bug, causes random crashes to su processes
Oh forgot to mention, the kernel log has a trace dump I did with SysRq -- wpa supplicant bug, causes random crashes to su processes https://bugs.launchpad.net/bugs/121955 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
