[Bug 1962314] Re: grub 2 custom.cfg colors not all used in Advanced options
** Description changed:
1) Ubuntu MATE 21.10
2) grub 2.04-1ubuntu47
3) I use text-mode for Grub, so made the following changes in
/etc/default/grub:
GRUB_TIMEOUT_STYLE=timeout
GRUB_TERMINAL=console
I then created a /boot/grub/custom.cfg with the following entries:
color_normal="light-gray/blue"
color_highlight="white/blue"
menu_color_normal="light-gray/blue"
menu_color_highlight="yellow/magenta"
I expect these colors to be used on both the initial menu showing the OS
version, Advanced options, and two Memory test options; and also on the
Advanced options submenu showing the list of available kernels.
4) What I'm seeing is that these colors are accurately reflected on the
initial text menu. However, if I select Advanced Options to show the
list of kernels, then the first three color specs are shown properly.
But the last one, for the highlighted menu entry is not respected.
Instead, the color_highlight combination of white/blue is used instead.
Perhaps menu_color_highlight is not used on submenus, but I cannot find
anything that states this restriction.
+
+ After some searching, I found a suggestion to manually update the
+ /boot/grub/grub.cfg file to add the menu_color options to the Advanced
+ options submenu, like so:
+
+ submenu 'Advanced options for Ubuntu' $menuentry_id_option
'gnulinux-advanced-43548515-6ad7-4cdb-b295-f880ef847d12' {
+ menu_color_normal="light-gray/blue"
+ menu_color_highlight="yellow/magenta"
+
+ menuentry 'Ubuntu, with Linux 5.13.0-30-generic' ...
+
+ This does indeed produce the desired result, in that the highlighted
+ menu item now has the desired colors. But of course these changes will
+ be lost the next time a new kernel is installed.
+
+ Since the submenu inherits color_normal and color_hightlight from the
+ top level menu, would be great if the menu_color_normal and
+ menu_color_highlight were also inherited. I don't believe the submenu
+ can be modified via custom.cfg, since custom.cfg is simply sourced from
+ grub.cfg at the very end, after all the menu and submenu entries have
+ been created.
** Description changed:
1) Ubuntu MATE 21.10
2) grub 2.04-1ubuntu47
3) I use text-mode for Grub, so made the following changes in
/etc/default/grub:
GRUB_TIMEOUT_STYLE=timeout
GRUB_TERMINAL=console
I then created a /boot/grub/custom.cfg with the following entries:
color_normal="light-gray/blue"
color_highlight="white/blue"
menu_color_normal="light-gray/blue"
menu_color_highlight="yellow/magenta"
I expect these colors to be used on both the initial menu showing the OS
version, Advanced options, and two Memory test options; and also on the
Advanced options submenu showing the list of available kernels.
4) What I'm seeing is that these colors are accurately reflected on the
initial text menu. However, if I select Advanced Options to show the
list of kernels, then the first three color specs are shown properly.
But the last one, for the highlighted menu entry is not respected.
Instead, the color_highlight combination of white/blue is used instead.
- Perhaps menu_color_highlight is not used on submenus, but I cannot find
- anything that states this restriction.
-
After some searching, I found a suggestion to manually update the
/boot/grub/grub.cfg file to add the menu_color options to the Advanced
options submenu, like so:
- submenu 'Advanced options for Ubuntu' $menuentry_id_option
'gnulinux-advanced-43548515-6ad7-4cdb-b295-f880ef847d12' {
- menu_color_normal="light-gray/blue"
- menu_color_highlight="yellow/magenta"
+ submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-
+ advanced-43548515-6ad7-4cdb-b295-f880ef847d12' {
- menuentry 'Ubuntu, with Linux 5.13.0-30-generic' ...
+ menu_color_normal="light-gray/blue"
+ menu_color_highlight="yellow/magenta"
+
+ menuentry 'Ubuntu, with Linux 5.13.0-30-generic' ...
This does indeed produce the desired result, in that the highlighted
menu item now has the desired colors. But of course these changes will
be lost the next time a new kernel is installed.
Since the submenu inherits color_normal and color_hightlight from the
top level menu, would be great if the menu_color_normal and
menu_color_highlight were also inherited. I don't believe the submenu
can be modified via custom.cfg, since custom.cfg is simply sourced from
grub.cfg at the very end, after all the menu and submenu entries have
been created.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962314
Title:
grub 2 custom.cfg colors not all used in Advanced options
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1962314/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
[Bug 1962314] Re: grub 2 custom.cfg colors not all used in Advanced options
** Description changed: 1) Ubuntu MATE 21.10 2) grub 2.04-1ubuntu47 3) I use text-mode for Grub, so made the following changes in /etc/default/grub: GRUB_TIMEOUT_STYLE=timeout GRUB_TERMINAL=console I then created a /boot/grub/custom.cfg with the following entries: color_normal="light-gray/blue" color_highlight="white/blue" menu_color_normal="light-gray/blue" menu_color_highlight="yellow/magenta" I expect these colors to be used on both the initial menu showing the OS version, Advanced options, and two Memory test options; and also on the - Advanced options showing the list of available kernels. + Advanced options submenu showing the list of available kernels. 4) What I'm seeing is that these colors are accurately reflected on the initial text menu. However, if I select Advanced Options to show the list of kernels, then the first three color specs are shown properly. But the last one, for the highlighted menu entry is not respected. Instead, the color_highlight combination of white/blue is used instead. + + Perhaps menu_color_highlight is not used on submenus, but I cannot find + anything that states this restriction. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962314 Title: grub 2 custom.cfg colors not all used in Advanced options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1962314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962314] Re: grub 2 custom.cfg colors not all used in Advanced options
** Description changed: 1) Ubuntu MATE 21.10 2) grub 2.04-1ubuntu47 - 3) I created a /boot/grub/custom.cfg with the following entries: + 3) I use text-mode for Grub, so made the following changes in /etc/default/grub: + + GRUB_TIMEOUT_STYLE=timeout + GRUB_TERMINAL=console + + I then created a /boot/grub/custom.cfg with the following entries: color_normal="light-gray/blue" color_highlight="white/blue" menu_color_normal="light-gray/blue" menu_color_highlight="yellow/magenta" I expect these colors to be used on both the initial menu showing the OS version, Advanced options, and two Memory test options; and also on the Advanced options showing the list of available kernels. 4) What I'm seeing is that these colors are accurately reflected on the initial text menu. However, if I select Advanced Options to show the list of kernels, then the first three color specs are shown properly. But the last one, for the highlighted menu entry is not respected. - Instead, the default combination of white/blue is used instead. + Instead, the color_highlight combination of white/blue is used instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962314 Title: grub 2 custom.cfg colors not all used in Advanced options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1962314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962314] [NEW] grub 2 custom.cfg colors not all used in Advanced options
Public bug reported: 1) Ubuntu MATE 21.10 2) grub 2.04-1ubuntu47 3) I created a /boot/grub/custom.cfg with the following entries: color_normal="light-gray/blue" color_highlight="white/blue" menu_color_normal="light-gray/blue" menu_color_highlight="yellow/magenta" I expect these colors to be used on both the initial menu showing the OS version, Advanced options, and two Memory test options; and also on the Advanced options showing the list of available kernels. 4) What I'm seeing is that these colors are accurately reflected on the initial text menu. However, if I select Advanced Options to show the list of kernels, then the first three color specs are shown properly. But the last one, for the highlighted menu entry is not respected. Instead, the default combination of white/blue is used instead. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: color grub2 mate menu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962314 Title: grub 2 custom.cfg colors not all used in Advanced options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1962314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.
Norbert, thank you for the quick response. I'm very impressed with apport automatically updating this bug report with requested info! I will try the FlatPak version when I have some time, since the next LTS release isn't until April 2022. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959473 Title: Evolution: Migrate to People API to retain programmatic access to Google Contacts. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1959473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959473] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1959473/+attachment/5558143/+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/1959473 Title: Evolution: Migrate to People API to retain programmatic access to Google Contacts. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1959473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959473] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1959473/+attachment/5558142/+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/1959473 Title: Evolution: Migrate to People API to retain programmatic access to Google Contacts. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1959473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.
apport information ** Tags added: apport-collected third-party-packages ** Description changed: I'm running Ubuntu MATE 20.04; I stick with LTS for this system. I use Evolution for email and calendar. Tonight I got this message: = Failed to connect address book “guy.rouill...@gmail.com : Contacts” Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. == I went to report this on the GNOME bug tracker and found this existing issue: https://gitlab.gnome.org/GNOME/evolution/-/issues/1655 That issue was closed with this comment: == "Andre Klapper Issue found on latest Evolution in Debian 11 (3.38.3-1) That version is ancient and not maintained anymore by GNOME developers. Feel free to file a bug report in your distribution's issue tracker." The version in MATE is even older: 3.36.5-0ubuntu1 - So apparently Evolution in MATE is currently not functional. We need to - update to a later release. I will update to the newer LTS of MATE when - it is released. + So apparently Evolution in MATE is currently not functional. We need to update to a later release. I will update to the newer LTS of MATE when it is released. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: MATE + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2018-10-05 (1212 days ago) + InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + Package: evolution-data-server + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 + Tags: third-party-packages focal + Uname: Linux 5.4.0-92-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1959473/+attachment/5558141/+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/1959473 Title: Evolution: Migrate to People API to retain programmatic access to Google Contacts. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1959473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799319] Re: Upgrade to 18.10 fails: Please install all available updates
I had forgotten I had submitted this bug report, and just encountered this same issue when I upgraded from 21.04 to 21.10. I reported my problem with this latest upgrade on the Ubuntu Mate Community forum. At least I'm consistent: the post there reads almost exactly like my bug report here. :) See details here: https://ubuntu-mate.community/t/prompt-to-upgrade-21-04-to-21-10-does- nothing/24672 This is a little disheartening that the same issue continues 2 1/2 years later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799319 Title: Upgrade to 18.10 fails: Please install all available updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1799319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1483975] Re: update-initramfs complains about missing /sbin/fsck.btrfs
I'm still seeing this message in Ubuntu Mate 20.04 on December 22,2020: "W: /sbin/fsck.btrfs doesn't exist, can't install to initramfs" Has the released fix just not been incorporated into the distros after 18 months? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1483975 Title: update-initramfs complains about missing /sbin/fsck.btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/1483975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901725] Re: check-new-release-gtk tells i386 users Ubuntu 20.04.1 is available
Just wanted to add that this affected me also. I've been aware for many months that support for 32-bit Ubuntu has been dropped. So, I was surprised when I started up this system I use only for backups to see the following message on the console: New release '20.04.1 LTS' available. Run 'do-release-upgrade' to upgrade to it. = Running do-release-upgrade produces: = Sorry, no more upgrades for this system There will not be any further Ubundo-release-upgradetu releases for this system's 'i386' architecture. Updates for Ubuntu 18.04 will continue until April 2023. = Seems odd to get a message telling me to perform an upgrade, then when doing that, to be told no upgrade is available. Why not just display the second message initially and save me the trip through do-release- upgrade? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901725 Title: check-new-release-gtk tells i386 users Ubuntu 20.04.1 is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1901725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799319] Re: Upgrade to 18.10 fails: Please install all available updates
Brian, thanks for the responses. Please see my last action: root@ubuntu64:~# apt-get purge lldb This allowed do-release-upgrade to finally proceed. gnome-shell and gnome-shell-common were wild gooses. The key ingredient seems to be this: root@ubuntu64:~# apt-get upgrade The following packages have been kept back: lldb Once I purged lldb, the release upgrade was clear to go. So, the hiccup seems to be held-back packages. I don't know enough about the inner workings of the upgrade process to understand how held-back packages figure into it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799319 Title: Upgrade to 18.10 fails: Please install all available updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1799319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799319] Re: Upgrade to 18.10 fails: Please install all available updates
I just encountered this exact same scenario running Ubuntu Mate 19.04. Software Updater believes all updates have been applied. I get the pop- up saying 19.10 is available, I click the Upgrade button, and the dialog disappears and nothing happens. Again, I drop to a command prompt: root@ubuntu64:~# do-release-upgrade Checking for a new Ubuntu release Please install all available updates for your release before upgrading. root@ubuntu64:~# apt-get upgrade (following update) The following packages were automatically installed and are no longer required: liblldb-8 llvm-8 llvm-8-dev llvm-8-runtime Use 'apt autoremove' to remove them. The following packages have been kept back: lldb The following packages will be upgraded: gnome-shell gnome-shell-common root@ubuntu64:~# do-release-upgrade Checking for a new Ubuntu release Please install all available updates for your release before upgrading. root@ubuntu64:~# apt-get purge lldb Removing lldb (1:7.0-43ubuntu1) ... And now do-release-upgrade is proceeding. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799319 Title: Upgrade to 18.10 fails: Please install all available updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1799319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589210] Re: snap remove "core" on classic not allowed
Commenting on this old post I found via search because Uli.Heller's suggestion worked for me to remove the snap core18 from Ubuntu 19.04. The core18 snap was mounted thusly: /dev/loop1355808 55808 0 100% /snap/core18/1066 First I disabled it: snap disable core18 Then I unmounted it: umount /dev/loop13 and then I could remove the snap: snap remove core18 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589210 Title: snap remove "core" on classic not allowed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1589210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799319] Re: Upgrade to 18.10 fails: Please install all available updates
Brian, thanks for the reply. I didn't get notified so I missed your reply. I used my workaround to eventually update the VM, so I can no longer test the failed upgrade. I'll try to remember if this happens again. Here is the output of the command you requested: guyr@ubuntu64:~$ apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:19.04.16.6 Candidate: 1:19.04.16.6 Version table: *** 1:19.04.16.6 500 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 100 /var/lib/dpkg/status 1:19.04.16 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu disco/main i386 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799319 Title: Upgrade to 18.10 fails: Please install all available updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1799319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574841] Re: The panel encountered a problem while loading "TrashAppletFactory::TrashApplet".
Still getting this error on 19.04 Mate. I don't use the applet often, and I'm tried of seeing this popup, so I'm going to simply delete it. I can test if anyone is interested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574841 Title: The panel encountered a problem while loading "TrashAppletFactory::TrashApplet". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1574841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799319] Re: Upgrade to 18.10 fails: Please install all available updates
** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799319 Title: Upgrade to 18.10 fails: Please install all available updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1799319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799319] Re: Upgrade to 18.10 fails: Please install all available updates
I was wondering how I could possible recreate this scenario. Coincidentally, I received your update on the same day I learned that 19.04 was available. So, I started up the VirtualBox VM containing Ubuntu Mate 18.10. I got a pop up telling me that 19.04, and asking if I would like to upgrade. I hadn't started this VM in over a week, so I ran Software Updater to check for updates. Some were available, so I installed them first. Once finished, I closed Software Updater, then clicked the Upgrade button on the original popup. The popup disappeared and nothing happened! So, I'm back in this same situation as I was when I first reported this issue. I tried rebooting so the updates applied by Software Updater were running. The same thing is happening. I run Software Updater; it reports no updates are available, but a new version is available. When I click the upgrade button, Software Updater disappears and nothing happens. I'm going to shut down the VM and back it up, so I can repeat this scenario. Please let me know what steps you'd like me to take. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799319 Title: Upgrade to 18.10 fails: Please install all available updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1799319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
I couldn't resist a challenge :), so I installed GCC version 5. In the process of trying to compile a bisected kernel, my file system somehow got corrupted. I have no idea who the culprit is, as this laptop is very old. So, it could be a hardware issue, who knows. But this exercise has convinced me that these Toshiba laptops are just too outdated for modern Linux versions. I've reformatted my filesystems, and I'm falling back to 16.04 Mate. I'll stay there as long as the laptop lasts. Thanks all for attempting to help. As Kenny Rogers would say, you gotta know when to fold 'em. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Ok, I started with v4.5 and v4.6. I successfully did a couple iterations, after adding the follownig CFLAGS to Makefile to get past compiler errors: -fno-pie -fno-stack-protector But I then ran into this error when trying to compile both 4.9.0 and 4.8.0: kernel/built-in.o: In function `update_wall_time': /data/ubuntu_mainline_kernel/linux/kernel/time/timekeeping.c:2073: undefined reference to `ilog2_NaN' This appears to be a problem with GCC 7: https://lore.kernel.org/lkml/20170225081810.GA1364@x4/ This is taking too much time, and I don't use this laptop enough to justify the time expenditure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Ugh, tab key did a submit! Launchpad needs some work. So, in summary: - with "acpi=off noapic", all kernels can reboot but hang during shutdown - without "acpi=off noapic", <= 4.5.7 can reboot and shutdown, but later kernels hang during both reboot and shutdown. Since I can't run the ancient kernels forever, I'm adding "acpi=off noapic" and will just live with the hang during shutdown. Fortunately, the filesystem appears to close before hang, so I don't have filesystem corruptions when I start up the next time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
I tried with 4.5.7, nothing changes with WiFi on or off However, back to the original problem, while playing with WiFi, I discovered that 4.5.7 was now freezing during shutdown (reboot okay). So, I then tried removing "acpi=off noapic" again, and 4.5.7 was now able to reboot and shutdown. But as before, any later kernel now hangs during both reboot and shutdown. So, in summary: - with "acpi=off noapic", all kernels can reboot but hang during shutdown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Hey! I'm typing this from the laptop over WiFi. I powered on the laptop with the WiFi off, but then turned it on before booting up 18.04. I got connected, then did a reboot. That went without any issues, and I got back into Ubuntu 18.04. After getting back into Ubuntu, I started up this browser session; Ubuntu remembered my WiFi configuration from the previous boot. So, no issues rebooting with WiFi turned on (or off). Sorry, I no longer have 16.04, so I can't comment on that. My active kernel is 4.15.0-39-generic. You say your laptop freezes on the Toshiba splash screen? Or did you mean the Ubuntu splash screen? Either way, mine is not freezing, either during power up or reboot. I doubt the WiFi being on will alter my hangs on power down, though I'll try that now. Hmm, I still have 4.5.7, I'll try rebooting with that to see if it changes anything. That was a 16.04 kernel. Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Ugh, partial retraction. The above solution works for reboot, but not for shutdown. I managed to get one shutdown session to show me the console, and the final statement was something like "poweroff reached", and then it just sits there forever. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
I tried the bisect procedure, but failed to build a kernel. First, the provided link won't work: git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git This repo only contains major releases. To get minor releases, this link is necessary: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git In the step "make localmodconfig", I accepted all the default config values, because I'm assuming that is what produces the published kernels. When I attempted to build the kernel, I got the following: guyr@tosh:/data/ubuntu_mainline_kernel/linux-minor$ make -j2 deb-pkg arch/x86/Makefile:133: stack-protector enabled but compiler support broken Makefile:666: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler CHK include/config/kernel.release UPD include/config/kernel.release make clean TAR linux-4.5.0.tar.gz make KBUILD_SRC= arch/x86/Makefile:133: stack-protector enabled but compiler support broken Makefile:666: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler SYSTBL arch/x86/entry/syscalls/../../include/generated/asm/syscalls_32.h HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/bin2c SYSHDR arch/x86/entry/syscalls/../../include/generated/asm/unistd_32_ia32.h SYSHDR arch/x86/entry/syscalls/../../include/generated/asm/unistd_64_x32.h SYSTBL arch/x86/entry/syscalls/../../include/generated/asm/syscalls_64.h HYPERCALLS arch/x86/entry/syscalls/../../include/generated/asm/xen-hypercalls.h SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_32.h CHK include/config/kernel.release WRAParch/x86/include/generated/asm/clkdev.h WRAParch/x86/include/generated/asm/cputime.h WRAParch/x86/include/generated/asm/dma-contiguous.h WRAParch/x86/include/generated/asm/early_ioremap.h WRAParch/x86/include/generated/asm/mcs_spinlock.h WRAParch/x86/include/generated/asm/mm-arch-hooks.h CHK include/generated/uapi/linux/version.h UPD include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h UPD include/generated/utsrelease.h CC scripts/mod/empty.o cc1: error: code model kernel does not support PIC mode SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_64.h scripts/Makefile.build:258: recipe for target 'scripts/mod/empty.o' failed make[4]: *** [scripts/mod/empty.o] Error 1 scripts/Makefile.build:407: recipe for target 'scripts/mod' failed make[3]: *** [scripts/mod] Error 2 Makefile:551: recipe for target 'scripts' failed make[2]: *** [scripts] Error 2 make[2]: *** Waiting for unfinished jobs SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_x32.h scripts/package/Makefile:91: recipe for target 'deb-pkg' failed make[1]: *** [deb-pkg] Error 2 Makefile:1238: recipe for target 'deb-pkg' failed make: *** [deb-pkg] Error 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
I found a related post here: https://www.linuxliteos.com/forums/suggestions-and-feedback/possible- kernel-problems-with-ubuntu-18-04-and-latest- kernel/15/?PHPSESSID=sgfuljc5afl0kgfg1lsj4oltg1 My Toshiba laptop does not have any power settings in the BIOS, so I tried adding "acpi=off noapic" to the kernel boot parameters in grub 2. That fixed the problem. I'll proceed with the bisect, but I'm guessing it will come down to this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Following the lead of #12 (sorry, I originally said #10, but could not edit to correct), I confirm those findings. http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5.7-yakkety/ works http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ hangs I purposely skipped the v4.6 release candidates since changes may have been redone or removed throughout the RC process; a change that might be suspect in RC1 may not even be present in subsequent RCs. I tried comparing syslog after rebooting both of these, but they too different to provide anything useful. I'll attempt to follow the bisect instructions to identify the problem commit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Got some testing results: 4.19.0 latest currently listed stable release hangs 4.4.0.163 latest version listed for 16.04 works I'll try a couple later kernels tomorrow - might as well follow the lead in #10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Just upgraded an old Toshiba Satellite A215-S7422 with AMD Turion X2 from 16.04 to 18.04. Was working fine under 16.04. Now I'm encountering this same issue. I don't use this laptop very much, so I can run tests on it. I'm running the Ubuntu Mate flavor. The current kernel it is running is 4.15.0-38-generic. Would it make any sense for me to try 4.5.7-yakkety, since I'm already well past that? I had fully updated the laptop with 16.04 prior to upgrading, so I know the latest kernel version from Ubuntu Mate 16.04 as of yesterday Nov 12 2018 works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799009] Re: Failed upgrade from Ubuntu 18.04 to 18.10
Awal, thanks, that worked! I opened a bug against the Ubuntu Mate upgrade process: https://bugs.launchpad.net/ubuntu-mate/+bug/1799319 I'll amend that to include these comments. Apparently the issue must be with Software Updater; it says my system is up to date, but running the two apt instruction manually updated about 12 packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799009 Title: Failed upgrade from Ubuntu 18.04 to 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1799009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799009] Re: Failed upgrade from Ubuntu 18.04 to 18.10
@Brian, will do, thanks. I'll post in the ubuntu-mate section, since I'm using that and the issue may be specific to Mate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799009 Title: Failed upgrade from Ubuntu 18.04 to 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1799009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799009] Re: Failed upgrade from Ubuntu 18.04 to 18.10
[UPDATE] I have dual boot on this computer, and also have Ubuntu Mate 18.04 running as a bootable OS. I just tried to upgrade that installation, and it fails in exactly the same way. I only recently installed that instance, so it's a very simple installation at this point (unlike the VM which I've used for several years and installed numerous packages, including PPA.) So there appears to be a general problem in this upgrade path. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799009 Title: Failed upgrade from Ubuntu 18.04 to 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1799009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799009] Re: Failed upgrade from Ubuntu 18.04 to 18.10
I just tried to upgrade an x64 VM from 18.04 Mate to 18.10 tonight, and it failed. Using the Software Updater from the menu, it tells me "The software on this computer is up to date. However, Ubuntu 18.10 is now available (you have 18.04)." When I click the Upgrade... button, the dialog disappears and nothing happens. If I run do-release-upgrade from a terminal, it tells me "root@ubuntu64:~# do-release-upgrade Checking for a new Ubuntu release Please install all available updates for your release before upgrading." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799009 Title: Failed upgrade from Ubuntu 18.04 to 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1799009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574841] Re: The panel encountered a problem while loading "TrashAppletFactory::TrashApplet".
I recently upgraded to 18.04 Mate AMD64, and I'm now getting this error. I wasn't getting this on 17.10. Please let me know what information you'd like me to provide. ** Changed in: mate-applets (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/1574841 Title: The panel encountered a problem while loading "TrashAppletFactory::TrashApplet". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-applets/+bug/1574841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
