[Bug 1863434] Re: 20.04 grub menu not visible
@Alexey: In my case on my '12 cMP that "GRUB_TERMINAL=console" as already set that way, so that wasn't "the solution" to a problem that has been affecting likely "EFI" boot computers for a year or more?? In my case I use my OpenSUSE installs to re-install grub2 . . . and that restores grub function, but they have slightly different commands than on the ubuntu side of things. But, possibly if you scroll up to #86 comment, I did just check in Launchpad and see that indeed grub 2.06 is there as tar.gz file . . . and he suggested that as the way to "fix" the problem, which indeed appears to be "shim" related. Another way I tried was to do a fresh install of a distro, that will also re-install grub, but then, if still in grub 2.04 in another install . . . likely will wipe grub menu again, etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
@iononsbalgiomai: This is interesting about the possibility that grub 2.06 might be the "solution" to the problem. Today I'm in LM 29.1 MATE (focal based) and synaptic shows only grub 2.04 as "available" . . . . I'll have to check my hirsute Lubuntu install in a day or so, but so far all "ubuntu" editions of grub have only selected themselves to boot up, no menu option list provided. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917528] Re: bcmwl-kernel-source fails to build on Linux 5.10
Yes, confirmed on my'12 cMP . . . after running an apt dist-upgrade, I was then able to use Add'l Driver app to install wifi drivers and wifi networks appeared in networkmanager applet?? Lubuntu hirsute edition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917528 Title: bcmwl-kernel-source fails to build on Linux 5.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1917528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
@GD: They do look like aspects of the same problem . . . a problem that is "unique" to ubuntu's handling of grub, which for most single boot users it "doesn't matter" . . . but for multi-boot users . . . it does. Just means to me that "ubuntu" flavors are being whittled down in number . . . . There are other options to choose from, options that let grub do what it needs to do, etc. : - ( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917528] Re: bcmwl-kernel-source fails to build on Linux 5.10
Thanks for the update . . . I'll be back in Lu 21 tomorrow and I'll check it . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917528 Title: bcmwl-kernel-source fails to build on Linux 5.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1917528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917528] Re: bcmwl-kernel-source fails to build on Linux 5.10
Yep, this is "a problem" for me running Hirsute Lubuntu on both my mac '09 MBP and just now tried to check it on my '12 cMP in Lu 21.04 and tried to "add the driver" via Add'l drivers and it would not install the driver . . . . It's less of a problem on the desktop unit, because it is plugged in, both appear to be using BCM4322 wifi units . . . but, this problem is a "show-stopper" for for laptop . . . must have wifi capability in that machine. Wifi was working fine as of this recent Wed night, logged into Lu 21.04 .. . connected to wifi, saw that there was a large "794 package upgrade" available, ran it through the wifi . . . but on reboot, wifi was "gone" . . . . Fortunately at that location I could use ethernet, but yesterday at my other part-time job, no such luck . . . no capacity for wifi. Today I messed around with it and found that as this post mentions "bcmwl-kernel-source" package is "not friendly" with the kernel??? Please advise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917528 Title: bcmwl-kernel-source fails to build on Linux 5.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1917528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
@YannUbuntu: I don't have time for fresh installs . . . but, as I've posted here a few times, if grub2 is updated in any of my ubuntu or ubuntu based, and likely in Debian . . . the grub menu and the 6 options menu are gone . . . and usually only ubuntu will boot. I have Lu 21.04, Linux Mint 20, and Debian Bullseye . . . the problem has been going on for at least a year now . . . definitely was happening in 20.04 and 20.10 iterations . . . I had a U-MATE 20 install for awhile that manifested this same issue, got corrupted and turned into Debian. I am too old to know for sure, but I don't think it was happening in 18xx Problem does not manifest with OpenSUSE options or Manjaro options running grub2 updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
@william: Well if it works, then that is elegance . . . ??? My menu does work because it is "run" by OpenSUSE . . . only the ubuntu flavors "disappear" my menu. My question was, does "disabling graphical terminal" in a Mac actually "fix" the problems that this thread is discussing??? By uncommenting that line, the grub menu will appear on booting?? Clearly my "TIMEOUT" matches your suggestion . . . that was in my Deb Bullseye distro this am. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
@William P: See, like in my case, in that file I have: [CODE] GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console [/CODE] So would anyone interested want to "disable graphical terminal" by uncommenting that line?? Really my personal issue is on the updating or installing of grub in ubuntu flavors that the grub menu on cold boot gets scrubbed and only one option in the ubuntu world will boot . . . no matter how I try to boot the system . . . only fixed by running os-prober in TW, or sometimes needing to chroot into TW to do the same action . . . it is "a pain" . . . only happens in ubuntu, possibly in Debian . . . not in OpenSUSE and not in Manjaro . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
@space_agent: Agreed, it is sad . . . and key point on the bug is that at the top line for "assigned" it shows "unassigned" . . . very interesting considering the large number of people who have posted on this bug report over . . . quite a long awhile. It does seem like some folks have figured out a "work around" . . . none of them seemed to apply to my investigation of their suggestions . . . I'm still waiting for the devs to be "assigned" to the situation . . . and get a real fix in the tubes on it. But, the great joy of linux is that there are "other options" to choose from . . . many of them. In the case of ubuntu it appears that the vision statement is "ubuntu first" . . . or only, they figure that most users only will use one OS, and so after an install it will only boot into ubuntu. But for multi-boot users such as myself that approach is problematic. Just last week I ran an apt on one of my ubuntu installs and once again upgrading grub in that process wiped my grub menu . . . so the problem still continues . . . . I had to once again boot the SuperGrub2 disk . . . find the "vmlinuz" for my Tumbleweed install and then run their "os-prober" to get my grub menu back . . . . I've been with ubuntu flavors for many years, but this problem has diminished my enthusiasm . . . because "they don't recognize it as a viable issue . . ." . . . to even "assign" it . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1863434] Re: 20.04 grub menu not visible
@Martin: O . . . the darkness . . . the darkness . . . . My question remains . . . will there be a time in which "ubuntu" gets this straightened out in their upstream "code" for grub . . . or biz as it has been for at least a year . . . the time of "darkness" . . . . Before this time of obscurity in grub2, grub2 actually functioned in the realm of ubuntu . . . then there was an eclipse which has remained and been supported as the "status quo" . . . seemingly not possible to adjust by the devs in charge of ubuntu's grub2 packages??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
Amazing that this bug has affected so many, considering that bug reports would be a small percentage of total number . . . and yet, it continues, essentially unaddressed . . . apparently a "non-issue." Or the expectation is it is "acceptable" that with every update to grub, the /etc/default/grub will have to be re-re-re-edited . . . to fix the bug??? The capacity of grub is to handle "multi-boot" without requiring edits . . . and the proof of that is my OpenSUSE and Manjaro updates provide a working grub menu . . . w/o any special handling from me. I'm assuming that my three ubuntu/debian based systems continue remove all other systems from grub, with each update, as they have over the last year, by now "Not a problem . . . ." ??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1863434] Re: 20.04 grub menu not visible
UlfZibis: Interesting to note that your issue also relates to EFI partition, which somewhere several months back I posted that that seemed to be a "commonality" to many of the posters in this bug report . . . . On Fri, Nov 13, 2020 at 4:41 AM UlfZibis <1863...@bugs.launchpad.net> wrote: > I had this problem combined with: > https://bugs.launchpad.net/bugs/1904076 > > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1863434] Re: 20.04 grub menu not visible
@UlfZibis: On Thu, Nov 12, 2020 at 4:55 PM UlfZibis <1863...@bugs.launchpad.net> wrote: > I have the same issue on Lenovo T540p and the latest BIOS update. It has > no dual graphics, only Intel. > Instead of the GRUB boot menu I only see a black screen with big "Lenovo" > logotype. After a while, Ubuntu is started automatically, as it is the > first entry in the boot menu. > However, the boot menu is functional with the up/down keys + Enter. > > Starting the PC from an external drive with Ubuntu life media or > MultiSystem USB drive, it's GRUB boot menu is visible as usual. > > -- > Thanks for the update, seems like the issues are continuing . . . my basic appraoch for the last few mnths is to use synaptic for upgrades in ubuntu flavors and NOT upgrade grub2 packages, whereas over in OpenSUSE and Manjaro grub2 upgrades are fine and that keeps my grub working and visible to boot other systems . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
@Ishrak: Thanks for the follow-up and the interest in the problem(s) with grub2 in ubtuntu flavorings. When I first signed on to this bug report I had this "grub menu is gone" problem, but that's because I was looking for it in an "EFI boot disk" wherein I would option key on boot to OSX boot manager, select the appropriate EFI disk, and then the grub menu would appear and I could select my chosen distro. When or before this bug hit, grub menu was removed from the EFI disk, and took awhile to find it with cold booting w/o keystroke . . . grub menu reappeared, but then the new problem became that with every ubuntu upgrade to grub2 packages, that new list and menu gets removed, gone totally and only one of the ubuntu choices will boot . . . until I get SG2 disk and boot to OpenSUSE and run their os-prober on the console, then grub menu is again fine until ubuntu decides to "upgrade" grub2 . . . again removing the menu listings and connections to grub, no "welcome to grub" . . . . \So I guess in that sense I still have the "grub menu is not appearing" problem. I was mostly in 20.10 and the problem is still happening, now I have Lu 20.10, LM 20.04, and new install of Deb 11 Testing, which also seemed to mess with grub yesterday . . . . I'll take a look at #48 and see if it makes any difference in my situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1863434] Re: 20.04 grub menu not visible
@Ishrak: I personally hope that you can get a handle on this problem . . . not sure if it goes "upstream" into Debian terrain, because I ran an install of Bullseye Testing yesterday, and at least it didn't wipe out grub listings as ubuntu has in recent months, but it re-ordered them, and had some issue with not being able to launch one of my 6 distros . . . . Again had to get over to TW and run their os-prober command to get it back into shape . . . . I "know" if I boot into Lubuntu and let apt update the various grub packages, likely again grub connections will be wiped and back to SG2 I will have to go . . . . F -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894242] Re: grub-install: error: failed to register EFI boot entry???
@Julian Klode: I've seen this "argument" before . . . which seems to display a lack of understanding of the capacity of grub2 to load and boot multiple systems . . . but does seem to display the "opinion" of ubuntu that continues to believe that only one system can be on grub at a time . . . which is in fact "correct" when ubuntu "grub" packages are run . . . grub is re-set to the last distro installed, more or less. My firmware was updated a year or so back to bring the machine up to OSX 10.14 . . . and there is another "grub" bug report in which numerous people with a range of machines are having similar problems with ubuntu's handling of grub . . . and the "head in sand" response to the problem. As I probably stated in the first post, after ubuntu removes all the other systems, if I use SG2 disk I can boot into OpenSUSE, run their "grub2-mkconfig" command, and voila, grub is again running at full capacity . . . . I'm not sure ow many bug reports I've filed on this problem, with similar response from ubuntu world . . . and the problem continues . . . unaddressed, marked "invalid," etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894242 Title: grub-install: error: failed to register EFI boot entry??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1894242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On Tue, Sep 29, 2020 at 4:10 PM Nicolas Bock <1891...@bugs.launchpad.net> wrote: > On Tue, Sep 29 2020, Brian Murray wrote: > > > On Tue, Sep 29, 2020 at 12:38:38PM -, Nicolas Bock wrote: > > Could you please run 'systemctl status whoopsie' and > > include the output of the command here? > > $ sudo systemctl status whoopsie > > I had a few minutes to boot my U-MATE 20.10 distro that is so slow to boot . . . . I checked "ls var/crash" and it showed three files there, when one of the last times I booted it up I trashed the whole directory, as was suggested to try to improve boot times . . . at first it seemed to but today wasn't very good as far as comparing ubuntu to my other options. I then ran the requested "whoopsie" command and got at least ten blocks of lines claiming to be "19 lines" spaced out with blackness between them . . . I copied one of the blocks, looks fairly similar to the previous posting?? [CODE] whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 11:26:52 PDT; 12min ago Main PID: 1902 (whoopsie) Tasks: 3 (limit: 19101) Memory: 7.9M CGroup: /system.slice/whoopsie.service └─1902 /usr/bin/whoopsie -f Sep 30 11:26:52 non1-MacPro systemd[1]: Started crash report submission daemon. Sep 30 11:26:52 non1-MacPro whoopsie[1902]: [11:26:52] Using lock path: /var/lock/whoopsie/lock Sep 30 11:26:53 non1-MacPro whoopsie[1902]: [11:26:53] The default IPv4 route is: /org/freedesktop/> Sep 30 11:26:53 non1-MacPro whoopsie[1902]: [11:26:53] Not a paid data plan: /org/freedesktop/Netwo> Sep 30 11:26:53 non1-MacPro whoopsie[1902]: [11:26:53] Found usable connection: /org/freedesktop/Ne> Sep 30 11:32:32 non1-MacPro whoopsie[1902]: [11:32:32] Parsing /var/crash/_usr_libexec_ayatana-indi> Sep 30 11:32:32 non1-MacPro whoopsie[1902]: [11:32:32] Uploading /var/crash/_usr_libexec_ayatana-in> Sep 30 11:32:33 non1-MacPro whoopsie[1902]: [11:32:33] Sent; server replied with: No error Sep 30 11:32:33 non1-MacPro whoopsie[1902]: [11:32:33] Response code: 200 Sep 30 11:32:33 non1-MacPro whoopsie[1902]: [11:32:33] Reported OOPS ID 4e2fc590-034b-11eb-bd50-fa1> ~ [CODE/] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
@Brian M: As you suggest that my or my problem reported likely by Dan van Vugt with my install of Ubuntu-MATE 20.10 had this similar problem of long strings of "Failed to start " items in the TTY and very long boot times . . . wasn't exactly "fixed" by trashing the /var/crash directory as he suggested there . . . . Then he said, "if that doesn't fix it you should do a fresh install" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1893952 I'll have to read through some of the suggestions here when I have more time to spend on it. As mentioned in my bug report, I also have a Lubuntu 20.10 and that doesn't have these issues with long boot times. In my U-MATE edition when the GUI log in window finally loads there is like a "clang-a-lang" error sound . . . unique to that one install out of maybe 6 linux installs I have on "bare metal" . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893952] Re: Repeated apport failures causing long boot delays
@Daniel: Thanks again for those commands . . . I didn't know if removing the whole crash directory was the way to remove those files . . . . So I ran that command, then I did the "apt update" . . . but then I ran "apt -f install" . . . and that showed a bunch of things to add and subtract . . . so I ran that through and then I did your "apt full- upgrade" . . . and then "sudo reboot" . . . and reboot took it's time. But on restart it was faster to the log in window . . . still got the "clang-a-lang" sound when it loaded, but logging in went "OK" . . . not the zippiest, but acceptable . . . and no universal error red dot symbol!!! So that is more or less OK . . . I probably won't need to re- install . . . I have enough linux distros that I don't need stone axe reliability, but I do prefer systems that "work" when clicking on stuff . . . not taking 60 seconds to reboot from console, etc. For now I think we have "solved" the complaint in this bug report . . . however, I have another bug report filed on U-MATE && Lubuntu 20.10 and that bug happened again while running through the "apt full-upgrade" commands suggested to fix the slow boot issues of this bug . . . and that is that ubuntu seems to be wiping the EFI grub data . . . leaving only itself on the grub listing . . . . It's a pain to have to use the SG2 disk to boot over into OpenSUSE to fix a problem that ubuntu seems to be causing . . . devs don't seem to be able to address that issue, which has been going on for months and effects a fair number of people . . . . If you have any experience in the grub area and can offer some suggestions that would be helpful . . . . I can't believe it happened yet again today in spite of my looking through the packages and not seeing "grub-" as it has been in the recent events with this problem . . . . Ubuntu does not seem to be playing well with others . . . for might be the last 9 -12 months?? https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1894242 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893952 Title: Repeated apport failures causing long boot delays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1893952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894242] Re: grub-install: error: failed to register EFI boot entry???
While working through some "broken packages" issues in my U-MATE 20.10 install I ran "apt full-upgrade" . . . didn't see anything about "grub" listed in the upgrades, but on reboot once again, the only system that will launch is . . . U-MATE . . . all the other 5 optional linux distros are again wiped from grub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894242 Title: grub-install: error: failed to register EFI boot entry??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1894242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893952] Re: very long boot/log in with log in window upper left corner?
OK . . . I deleted "immediately" the three or four crash logs that weren't locked, and on reboot it went faster and login window was in proper place . . . . But an "error" sound sounded when the log in window opened on the screen . . . and the "broken packages" symbol is still there. I'll have to try a few more times, because the problem seems to come and go, etc. Seems like cutting down on the crash logs maybe helped??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893952 Title: very long boot/log in with log in window upper left corner? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1893952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893952] Re: very long boot/log in with log in window upper left corner?
On reboot again it took a looo time to get to the tiny log in window . . . and the international red dot with line through it applet in toolbar upper right said, "unmet dependencies" . . . launched synaptic, seems like it wants to add the "2.31-Oubuntu" package back in?? and remove three others?? It says "4 broken packages" . . . . Anyway, I left things as they are there . . . . Maybe I'll try to "delete" the items that aren't locked in /var/crash/ . . . . Basically the slow boot issue is still continuing . . . to continue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893952 Title: very long boot/log in with log in window upper left corner? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1893952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893952] Re: very long boot/log in with log in window upper left corner?
@Daniel: Even though the previous time I booted in U-MATE seemed to go faster, this time again was very slow and again the log inwindow was squeezed into upper left corner. Thanks for providing the wget data . . . I ran that and it came up with some errors, so I'm pasting that here before I reboot. [CODE]$ sudo dpkg -i libc6_2.31-0ubuntu11_amd64.deb [sudo] password for nonspace1: dpkg: warning: downgrading libc6:amd64 from 2.31-2ubuntu1 to 2.31-0ubuntu11 (Reading database ... 345902 files and directories currently installed.) Preparing to unpack libc6_2.31-0ubuntu11_amd64.deb ... De-configuring libc6:i386 (2.31-2ubuntu1) ... Unpacking libc6:amd64 (2.31-0ubuntu11) over (2.31-2ubuntu1) ... dpkg: error processing package libc6:amd64 (--install): package libc6:amd64 2.31-0ubuntu11 cannot be configured because libc6:i386 is at a different version (2.31-2ubuntu1) dpkg: error processing package libc6:i386 (--install): package libc6:i386 2.31-2ubuntu1 cannot be configured because libc6:amd64 is at a different version (2.31-0ubuntu11) Errors were encountered while processing: libc6:amd64 libc6:i386 [/CODE] I also checked the /var/crash/ folder via the GUI and there were maybe 6 or 7 crash files in there, three of them were "locked" and properties said, "You are not the owner" . . . I right clicked on the other files and an error came up saying, "File can't be moved to trash" and then it had "cancel" "delete" or "something else (some other choice) . . . so I just closed the window and left the files as they were??? Is this something that has to be done in the console as root, or, clicking "delete" would "delete" the file "permanently" . . . bypassing "trash" and just going straight to linux "heck" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893952 Title: very long boot/log in with log in window upper left corner? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1893952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894242] [NEW] grub-install: error: failed to register EFI boot entry???
Public bug reported: Today both of my ubuntu 20.10 installs had "grub" packages to upgrade, Lubuntu & U-MATE . . . over the last year?? upgrading grub in ubuntu has managed to wipe the grub listings of the other systems I have installed, leaving only U-MATE to boot up. I've had to use SG2 disk to boot into OpenSUSE to repair the damages done by the ubuntu grub process . . . it keeps happening. Today I ran the Lu apt dist-upgrade and it had a few grub packages to upgrade . . . I ran them . . . I rebooted and, yep, grub list was again wiped . . . and into U-MATE we went. I ran apt over here and it showed the same grub packages . . . since the damage was already done I ran it. This time it actually showed errors with "grub-install" . . . . I may have other bug reports on this problem, but it seems like ubuntu's grub doesn't get "EFI"??? Devs haven't gotten this issue addressed as of this date?? I copied the data in the console: [CODE]Setting up grub-pc (2.04-1ubuntu30) ... Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.4.0-42-generic Found initrd image: /boot/initrd.img-5.4.0-42-generic Found linux image: /boot/vmlinuz-5.4.0-9-generic Found initrd image: /boot/initrd.img-5.4.0-9-generic Found Manjaro Linux (20.1) on /dev/sdb7 Found openSUSE Tumbleweed on /dev/sdb8 Found openSUSE Tumbleweed on /dev/sdb9 Found Mac OS X on /dev/sdc2 Found Ubuntu Groovy Gorilla (development branch) (20.10) on /dev/sdc7 done Setting up grub-efi-amd64-signed (1.151+2.04-1ubuntu30) ... Installing grub to /var/lib/grub/esp. Installing for x86_64-efi platform. Installation finished. No error reported. Installing grub to /var/lib/grub/esp. Installing for x86_64-efi platform. Installation finished. No error reported. Installing grub to /boot/efi. Installing for x86_64-efi platform. Installation finished. No error reported. Installing grub to /var/lib/grub/esp. Installing for x86_64-efi platform. Installation finished. No error reported. Setting up shim-signed (1.43+15+1552672080.a4a1fbe-0ubuntu2) ... Installing for x86_64-efi platform. grub-install: warning: Cannot set EFI variable Boot. grub-install: warning: efivarfs_set_variable: writing to fd 8 failed: Invalid ar gument. grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: Inval id argument. grub-install: error: failed to register the EFI boot entry: Invalid argument. dpkg: error processing package shim-signed (--configure): installed shim-signed package post-installation script subprocess returned erro r exit status 1 Processing triggers for libc-bin (2.31-2ubuntu1) ... Processing triggers for systemd (246.2-1ubuntu1) ... Processing triggers for man-db (2.9.3-2) ... Processing triggers for install-info (6.7.0.dfsg.2-5) ... install-info: warning: no info dir entry in `/usr/share/info/automake-history.in fo.gz' Errors were encountered while processing: shim-signed E: Sub-process /usr/bin/dpkg returned an error code (1) [/CODE] ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.11 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: MATE Date: Fri Sep 4 08:46:07 2020 InstallationDate: Installed on 2020-01-20 (228 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894242 Title: grub-install: error: failed to register EFI boot entry??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1894242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893952] Re: very long boot/log in with log in window upper left corner?
@Daniel: Well, I couldn't exactly reproduce the extremely slow boot to a distorted GUI log in window . . . it wasn't exactly "zippy" but maybe it took two minutes to get from restart to log in window, which was in the proper position. I ran the "journalctl" command and then the plan was to remove the "libc6 2.31-2ubuntu1" package . . . I tried to use GDebi to open you link to the regressed package, but GDebi said, "A newer package is already installed" . . . so then I tried to "apt rm libc6 2.31-2ubuntu1" . . . but it said, "Invalid operation rm" . . . . Then I searched synaptic with "libc6 2.31-2ubuntu1" and it found nothing??? I tried to get to root in the terminal and I guess I haven't been added as sudoer by U-MATE?? Kind of a pain . . . . So, for now I'm "stuck" on how to get that package regressed . . . do I have to use TTY? Does this package even exist? If so, how or why didn't synaptic "see" it as "installed" and/or give me choices to regress back to?? Looks like the journalctl file is showing the endless streams of "Failed to start process" . . . again?? Had this issue a couple days back and seemed to get it cleaned up in the TTY, now back? TTY2 seems to be "open for business" . . . . ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+bug/1893952/+attachment/5407464/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893952 Title: very long boot/log in with log in window upper left corner? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1893952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893952] Re: very long boot/log in with log in window upper left corner?
@Daniel: Thanks for the reply . . . it'll be a few hours before I can get back to U-MATE to test out your requests . . . . But, after I filed this bug I posted the issue on the U-MATE developmental sub-forum and I got one reply with a link to a recent post on LM forum expressing a similar issue. https://forums.linuxmint.com/viewtopic.php?f=46&t=329115&hilit=slow+boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893952 Title: very long boot/log in with log in window upper left corner? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1893952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893952] [NEW] very long boot/log in with log in window upper left corner?
Public bug reported: Been having problems with my installation of 20.10 U-MATE . . . reported here earlier to little fanfare . . . but the issues with very slow boot times, and then when finally arriving at GUI log in window, the log in "tray" is positioned upper left corner of the display and it's like a TTY, where it wants user name and then password. I think today it literally took 5 minutes to get logged into the GUI . . . . As reported previously I have an install of Lu 20.10 in the same drive . . . so far is not having the same problems that U-MATE is having . . . . ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: MATE Date: Wed Sep 2 07:28:33 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: broadcom-sta, 6.30.223.271, 5.4.0-42-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK110 [GeForce GTX 780] [10de:1004] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK110 [GeForce GTX 780] [3842:0781] InstallationDate: Installed on 2020-01-20 (226 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119) MachineType: Apple Inc. MacPro5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e795b2e6-5bef-4a6e-9217-539a6debda90 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: 138.0.0.0.0 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvr138.0.0.0.0:bd07/30/2018:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.family: MacPro dmi.product.name: MacPro5,1 dmi.product.sku: System SKU# dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.5-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893952 Title: very long boot/log in with log in window upper left corner? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1893952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892522] Re: apt dist-upgrade "crashes" two times
Just to update . . . running the update/upgrade after I posted before did seem to clear the TTY up, the "Failed" endlessly streaming seems to be gone . . . and I could log in to the TTY. Boot up seems a little faster, but when the log in window loads the "error" "clang" sound sounds . . . but there is no error "splotch" signaling a crash report . . . . and it still seems to be asking for the user name & password even though there is only one user. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892522 Title: apt dist-upgrade "crashes" two times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1892522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892522] Re: apt dist-upgrade "crashes" two times
[edit: After I posted this earlier data, I ran apt and it brought back 126 packages to upgrade and some to autoremove . . . . Also I tried to get into a TTY and it was filled with the "Failed" lines, I tried each of them--all showing the same data. I ran the upgrades and then autoremove showed at the end: BlockquoteProcessing triggers for desktop-file-utils (0.24-1ubuntu4) ... Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for gnome-menus (3.36.0-1ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.64.4-1) ... /usr/share/glib-2.0/schemas/org.ayatana.indicator.datetime.gschema.xml:4:1 Erro r on line 4 char 1: already specified. This entire file h as been ignored. Processing triggers for libc-bin (2.31-2ubuntu1) ... Processing triggers for man-db (2.9.3-2) ... Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu2) ... Rebuilding /usr/share/applications/bamf-2.index... About to restart to see if anything changes . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892522 Title: apt dist-upgrade "crashes" two times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1892522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892522] Re: apt dist-upgrade "crashes" two times
Problems continuing with my U-MATE install of 20.10 . . . very long boot times, and in the TTY there is a large "FAILED to start processes" . . . . This morning it took maybe 3 minutes to get to a log in window, but the "log in" window was upper left corner . . . it was like in the TTY where it was asking for user name, rather than already "knowing" and just wanting the password. I entered the password . . . then realizing that it wasn't going to accept my password as the user name . . . I hit the power button . . . the TTY with the large "FAILED" line after line showed up . . . before shutting down . . . . A thread on the U-MATE forum has been started w/o much in the way of insight . . . . https://ubuntu-mate.community/t/apt-dist-upgrade-crashes-gui-two- times/22561/9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892522 Title: apt dist-upgrade "crashes" two times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1892522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892522] Re: apt dist-upgrade "crashes" two times
Ran "configure" and then "fix broken install" . . . the ran thru apt dist-upgrade and it appeared "OK" . . . then I ran autoremove and autoclean and again ran apt dist-upgrade . . . it showed "52 packages" to upgrade . . . half way through again the GUI crashed into blackness. This time took a full minute before mouse came back . . . and back into GUI . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892522 Title: apt dist-upgrade "crashes" two times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1892522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892522] Re: apt dist-upgrade "crashes" two times
This time "dpkg --configure" made it through w/o crashing . . . but reported: "Errors were encountered while processing: libreoffice-math libreoffice-gtk3 libreoffice-writer libreoffice-draw libreoffice-gnome bcmwl-kernel-source libreoffice-base-core python3-uno libreoffice-calc" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892522 Title: apt dist-upgrade "crashes" two times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1892522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892522] Re: apt dist-upgrade "crashes" two times
Ran "configure" and then "fix broken install" . . . the ran thru apt dist-upgrade and it appeared "OK" . . . then I ran autoremove and autoclean and again ran apt dist-upgrade . . . it showed "52 packages" to upgrade . . . half way through again the GUI crashed into blackness. This time took a full minute before mouse came back . . . and back into GUI . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892522 Title: apt dist-upgrade "crashes" two times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1892522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892522] Re: apt dist-upgrade "crashes" two times
opened synaptic and it says: "E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. E: _cache->open() failed, please report." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892522 Title: apt dist-upgrade "crashes" two times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1892522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892522] Re: apt dist-upgrade "crashes" two times
This time "dpkg --configure" made it through w/o crashing . . . but reported: "Errors were encountered while processing: libreoffice-math libreoffice-gtk3 libreoffice-writer libreoffice-draw libreoffice-gnome bcmwl-kernel-source libreoffice-base-core python3-uno libreoffice-calc" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892522 Title: apt dist-upgrade "crashes" two times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1892522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892522] [NEW] apt dist-upgrade "crashes" two times
Public bug reported: Running a standard "apt dist-upgrade" in U-MATE 20.10 via GUI console & part way through suddenly the screen flashes black and a brief TTY-like dmesg data shows "[Failed] and a bunch of data before going black again . . . . Seems like the GUI was crashed . . . . After a minute the mouse cursor came back and then the log-in window. I logged in and saw the "error" applet up on the toolbar . . . saying "possibly unmet dependencies" . . . launched the console again and it said, "dpkg was interrupted, run 'sudo dpkg --configure -a'" . . . so I ran that, and a few errors on "libreoffice" showed up . . . it was running through the items again . . . and then the same crash of the GUI happened again . . . ??? Haven't seen anything quite like this in some 13 years of messing with linux . . . GUI crashes while running an apt update? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.9 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: MATE Date: Fri Aug 21 08:24:21 2020 InstallationDate: Installed on 2020-01-20 (214 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2020-03-18T12:04:25.397274 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892522 Title: apt dist-upgrade "crashes" two times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1892522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890211] Re: 5.8 kernel appears to break video in two groovy installs
@Kai-Heng Feng: When I posted that I was comparing my Tumbleweed kernel which is running 5.8 with the two ubuntu installs . . . that seemed to break when they bounced up to 5.8. The two ubuntu distros are now running something like 5.4 . . . because I unchecked the "pre-release packages" box . . . . Checking the "pre-release packages" box brought in the 5.8 kernel into the two ubuntu installs, but caused problems with video . . . . I assumed at the time that it was "the kernel" . . . . There are quite a few system reports posted in this thread, but I don't think any of them show the system when it was using the 5.8 kernel . . . because nothing could be seen . . . . Today I'm back in my Tumbleweed install, that system is running the 5.8 kernel . . . and it is working well . . . much faster than the 5.4 kernels that my ubuntu installs are . . . etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890211 Title: 5.8 kernel appears to break video in two groovy installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890211] Re: 5.8 kernel appears to break video in two groovy installs
Today my Tumbleweed distro upgraded to the 5.8.0.1-default kernel and on reboot video is working and I'm typing this post via the 5.8 kernel . . . . So either the ubuntu apt pre-release version of the kernel is higher up than this one, OR, there was some other package that caused the problems in the two ubuntu distros that I have installed. Both have been rolled back to "un-pre-release" and the grub listings have worked themselves out so that the 5.4 kernels are now default . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890211 Title: 5.8 kernel appears to break video in two groovy installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890211] [NEW] 5.8 kernel appears to break video in two groovy installs
Public bug reported: Ran apt to update/upgrade in both of my groovy distros, Lubuntu & U-MATE 20.10 . . . on reboot not only was my grub list broken in both cases but seemingly the update to the new 5.8.0-12 kernel shows splash logo, but "logs" to a black screen. Display power light is "on" but screen is black. I repeated this several times in both systems . . . having to boot using SG2 to another distro to repair grub . . . then after I did that I got to grub list and went to "advanced options" and rolled back to the prior 5.4.0-42 kernel . . . and GUI is operational. I believe in TW I am running 5.7 kernel and that system has video. I have an Nvidia card and I'm using "nouveau" as my driver. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu43 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: non-space2 1665 F pulseaudio /dev/snd/controlC0: non-space2 1665 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Mon Aug 3 15:45:08 2020 InstallationDate: Installed on 2019-06-17 (413 days ago) InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: lono wireless extensions. enp9s0no wireless extensions. enp10s0 no wireless extensions. MachineType: Apple Inc. MacPro5,1 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=17bcb813-d05e-4cc3-bcdf-16d283156780 ro quiet splash resume=UUID=f9ae531f-ec45-4a13-a75d-d3fd4cd80fe0 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.189 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2019-12-13 (234 days ago) dmi.bios.date: 07/30/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: 138.0.0.0.0 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvr138.0.0.0.0:bd07/30/2018:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.family: MacPro dmi.product.name: MacPro5,1 dmi.product.sku: System SKU# dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890211 Title: 5.8 kernel appears to break video in two groovy installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890211] Re: 5.8 kernel appears to break video in two groovy installs
Forgot to mention that when I'm booted in the 5.8 kernel with the black screen, when I hit the power button the splash for both U-MATE && Lubuntu return to the screen before then powering down. So we are moving from visible splash to black to visible splash to . . . powering down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890211 Title: 5.8 kernel appears to break video in two groovy installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
@Salvador Ortiz: I wasn't posting to get you to remove your post, just letting you know that so far "no action" has taken place here . . . in spite of a fair number of folks who have been affected by it. @Julian: I'm not sure what "inactionable" means, or why you would say "we don't want a menu" . . . when, for multi-booting we generally would want a menu? Compared to the usual 1 or 2 people on a bug this is quite a bit more . . . I found problems with "UEFI" as possibly involved . . . other people found work arounds . . . but a "bug" is a "bug" . . . and should be "actionable" or investigated until solution found?? If people are "complaining" then what is the basis of that complaint?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1863434] Re: 20.04 grub menu not visible
Salvador Ortiz: Just replying to the request for help . . . keep in mind that this is a "bug report" place, and probably not a place where help will be provided. This bug has been posted for many months and yet so far appears to be largely "unaddressed" . . .??? But for actual help you probably should go to a forum and post your issues there?? F On Wed, Jul 22, 2020 at 7:06 AM Salvador Ortiz <1863...@bugs.launchpad.net> wrote: > > > When it does boot into Grub it leaves me at a terminal login, as > expected, but this doesn't happen anymore regardless of how many times i > reboot or cycle power. I've cleared my BIOS settings, tried booting from > installation medium (video display was corrupted, making it difficult to > install in the first place). > > No options to recover the machine, access it's disk, etc. Please help! > > a short video illustrating the issue described above: > https://drive.google.com/file/d/1U2dYqGBRXP9cyVwuQEwJuVfEPWrLij5l/view > > > Thanks! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1863434 > > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1863434] Re: 20.04 grub menu not visible
On Thu, Jun 18, 2020 at 8:30 AM Dimitri John Ledkov < 1863...@bugs.launchpad.net> wrote: > Can someone please provide clear reproducer instructions? > > Ideally starting with a clean state (i.e. no installs / brand install) > with affected hardware details (model, firmware version numbers, SKU > numbers, etc) > > ** Changed in: grub2 (Ubuntu) >Status: Confirmed => Incomplete > > After initial boot there is a blank black screen where grub should be > visible. > Grub is functional but not visible. > > Gents: A lot of people have had issues with grub in the last 6 months or longer and they posted their data about in this bug report. It appears to relate to "EFI" and possibly how the installer is handling where grub is put when pointed to "efi/boot" . . .?? My case might be more "complicated" because I have 4 internal drives with 5 distros of linux and a few OSX installs. Don't have time for a fresh install right now, but traditionally when running an install I would select "advanced partitioner" and I would point grub to go to the EFI partition of the drive I was installing into . . . and all would go well, on reboot I would hold alt/option key in my '12 Mac Pro, that would fire OSX boot manager which would show available disks to boot from, and the linux options would show as "EFI Boot" and I would select that and that would load Grub. 6 or more months ago, that changed, with a fresh install the grub listing got messed up and finding the "EFI Boot" disk would bring a "grub rescue" screen, in several linux installs grub was "messed up" . . . fortunately I had SuperGrub2 and using that I was able to boot into a linux console and chroot into OpenSUSE where I could run os-prober . . . that after several attempts was enough to get grub "fixed" . . . now if I just "free boot" the computer with no keystrokes, grub shows up and I can pick my system. Possibly that is because I already had Grub installed, so I could run "grub-update" . . . ??? I don't know, but from my non-technical viewpoint it appears that something in the installer is not installing the /boot/EFI file??? for grub, something is going wrong there? Is my "best guess" as to the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
@et al: What's "interesting" is that considering the fairly substantial numbers of people having issues with grub . . . this bug still appears to be "unassigned" Seems like a problem interfering with function should get some faster attention??? other than folks figuring out their own work arounds??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
Adding my story here . . . in U-MATE running sources.list as "devel" and some of the list is ID-ing as "groovy" . . . it is showing as 20.10 . . . had some issues with the broadcom package not updating in apt, so on the U-MATE forum with wolfman and he had me look at my "Software & Updates" data, and while just looking at the items in "edit," and even though I changed nothing I got the same scenario as norbert in #3 post . . . where the "cache refresh" window opens, progress bar fills . . . but then window doesn't close--this time the crash report window opened. I believe this happened previously and I might have FQd in the GUI . . . . I sent the crash report and it auto-loaded the dup bug report #1832057 . . . which linked me here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829401 Title: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1863434] Re: 20.04 grub menu not visible
@swnw: Thanks for posting that link on "boot-repair" . . . I think I have an older version of it, but it didn't seem "easy" and it didn't always help out in my multi-boot situation. But, might be worth a try. Interesting that with a new install of ubuntu the problem reappeared, over the years if grub got messed up often times running a fresh install would "fix" grub . . . seemingly in this case, the opposite. On Mon, Apr 27, 2020 at 11:31 PM swnw <1863...@bugs.launchpad.net> wrote: > Looks like delete is impossible too? > > My problem is probably solved, I wrote "probably" because during the > procedure I can saw few errors which I can't explain, so we'll see. > > I use the first method from the "linuxconfig.org/ubuntu-boot-repair", im > my second PC I disconnected boot HD, then installed Boot-Repair, pressed > "Recomended repair" and restarted Ubuntu 20.04 and Grub menu appeared. So > far so good. > Then I made an experiment, I installed Ubuntu 20.04 with boot HD unplugged > on my old Hitachi 2.5' HD using fresh iso image downloaded fron Ubuntu > download section, prepared new USB bootable pendrive using BalenaEatcher, > started Ubuntu and again Grub menu wasn't visible. > So I installed Boot-Repair repaired procedure as above, saw a few errors > and I can see Grub menu again. Now everything works, so may my method could > be helpful. > > swnw > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1863434 > > Title: > 20.04 grub menu not visible > > Status in grub2 package in Ubuntu: > Confirmed > > Bug description: > T430 > Ubuntu MATE 20.04 > > New installation. > > After initial boot there is a blank black screen where grub should be > visible. > Grub is functional but not visible. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: grub-common 2.04-1ubuntu18 > ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 > Uname: Linux 5.4.0-14-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu16 > Architecture: amd64 > CurrentDesktop: MATE > Date: Sat Feb 15 09:19:13 2020 > InstallationDate: Installed on 2020-02-14 (0 days ago) > InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 > (20200214) > ProcEnviron: >LANGUAGE=en_US >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: grub2 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1863434] Re: 20.04 grub menu not visible
BTW . . . I had similar issues with getting my various linux distros to produce a TTY in nouveau, so I got advice to "go nvidia driver" . . . so I did that, but then, because I'm in rolling or devel for most of them, stuff started "breaking" with update/upgrades . . . because I don't think nvidia is "keeping pace" with the bleeding edge distros, or perhaps even leading edge . . . . My card is maybe 7400??? posted on the nvidia linux forum, guy got back to me, basically said, "Your card is very old news, so don't hold your breath" . . . so I didn't. Went back to nouveau in my ubuntu 20.04 installs, and some opensuse . . . but for tumbleweed I went with "default" by not accepting nouveau in the install . . . not sure which driver it is, but display is just as crispy . . . it's fine. But, this "grub not showing the menu" issue seems to be working it's way through all of the various distros . . . I did my chroot maneuver that worked last time, didn't seem to get it this time . . . but, now in my MacPro if I boot with no "alt/option" key held I get an OSX dmesg-like window that loads and then "welcome to grub" shows up, but, if I hold alt/option to an EFI disk boot . . . grub is all busted up . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1863434] Re: 20.04 grub menu not visible
Just from a fast scan of the posts it seems like the common factor might be the gpu?? Grub is having problems with the gpu?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
I'd like to add myself into the mix here . . . with a recent apt update/upgrade in both Lu 20.04 and U-MATE 20.04 . . . "grub" and a few other packages were run and subsequently the visible grub page that shows my 5 linux installs was wiped . . . leaving only the ubuntu systems as bootable in my '12 MacPro. I have a somewhat "complicated" set up with multi-booting OSX and linux in two out of three drives, but until this recent round of ubuntu updates I never had a GUI window open in the console saying, "grub doesn't know where to go, where should it go?" . . . and then having a "universal" effect on "grub" such that only ubuntu was showing from one EFI disk image. The first time I ran this I was in Lu 20.04 . . . and that busted up grub pretty good, had to get my SG2 disk out and after numerous reboots was able to find my way to an older OpenSUSE based grub window . . . and then I could boot the various other options . . . . But it was only after running the Lu upgrade that this problem happened. I posted to Lu-devel list serve . . . waiting for a reply on that one. To "fix" the problem I booted into Lu 20 and I chrooted over to the OpenSUSE filesystem Yast and used their os-prober . . . and rebooting a number of times I found that indeed "grub" was using the TW grub window and I was able to choose among a few of my systems. While I was doing that I rebooted into U-MATE 20.04 today and ran an apt update/upgrade and sure enough there again was "grub" and a few other "grub" packages . . . for scientific purposes I just ran it . . . and around 95% of the install, again the GUI window opened asking me, "Grub can't find itself, where do you want grub to go?" This time I checked all three of the options, and after finishing the upgrade I rebooted into OSX bootmanager and this time two out of three disks only booted U-MATE?? So the ubuntu "grub" seems to be commandeering the controls and setting grub to just boot . . . itself??? >From the console in U-MATE 20 I repeated my maneuver of chrooting into TW and running the os-prober . . . once again I have a "main grub" menu . . . visible to my aging eyes. . . . Seems like there is some kind of issue working around through the various OSs using EFI boot and grub . . . I believe I had a similar issue over in TW a few months back, which is what got me to the "chroot" solution . . . and possibly in Siduction as well . . . problem still seems to be happening . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864170] Re: dpkg ugrade error - files in qtermwidget5-data also in old qtermwidget-l10n
@Rik Mills: Yep, after I ran that and posted it, because previously when I ran "--fix-broken" it didn't fix it so I posted the data . . . I then right- clicked on the "!" applet and "launch package manager" and this time it showed the broken package as being able to "upgrade" . . . so I ran that . . . had some stuff to do, logged out. When I came back I couldn't log back in, went to TTY and ran the fresh upgrade and back into the GUI, seems like we're past this hiccough in the system. : - ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864170 Title: dpkg ugrade error - files in qtermwidget5-data also in old qtermwidget-l10n To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtermwidget/+bug/1864170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864170] Re: dpkg ugrade error - files in qtermwidget5-data also in old qtermwidget-l10n
Jut ran a basic apt update/dist-upgrade this AM in Lu 20.04 and it again errored out . . . . [CODE] Reading package lists... Done Building dependency tree Reading state information... Done 300 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libqtermwidget5-0 : Depends: qtermwidget5-data (= 0.14.1-3) but 0.14.1-0ubuntu3 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). [/CODE] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864170 Title: dpkg ugrade error - files in qtermwidget5-data also in old qtermwidget-l10n To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtermwidget/+bug/1864170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864170] Re: dpkg ugrade error - files in qtermwidget5-data also in old qtermwidget-l10n
Also ran into this problem this morning, kind of like "quicksand" in that it won't run "autoremove" and -f install also errors out . . . a conundrum within a conundrum . . . in Lu 20.04 . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864170 Title: dpkg ugrade error - files in qtermwidget5-data also in old qtermwidget-l10n To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtermwidget/+bug/1864170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798450] Re: [snap] File dialogs show snap's home directory instead of user's
Just adding that this issue has recently affected my work flow trying to upload a file to social media site in hopes of generating actual deniro . . . but could not get my own files to show up in what I was hoping would be my /home directory . . . but was instead a "snap" "virtual home" directory, so that it showed as "empty" . . . ?? very disruptive to routine uses . . . ??? I posted to wxl that if this was to prevent me from uploading his files to my social media then that "makes sense" . . . but to prevent me from simply uploading my own files n the system I'm booted and logged into . . . non-sensical . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798450 Title: [snap] File dialogs show snap's home directory instead of user's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1798450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1857815] Re: cups-browsed assert failure: corrupted double-linked list
On Wed, Jan 22, 2020 at 3:16 AM Till Kamppeter <1857...@bugs.launchpad.net> wrote: > Now I have tried with creating a fresh VM with the daily snapshot of > Focal and tried to reproduce the crash. Both with all normal, the host > providing some remote printers for which the cups-browsed in the VM > creates local queues and also with CUPS on the host stopped so that > cups-browsed does not create queues. No crash at all. > > > > T > I'll post to say that I did have this problem in Lu 20.04 and added myself to this bug, did a regular upgrade, problem seemed to go away, but then on another log in, returned. This morning after seeing this recent post logged into Lu and no "system problem" error window showing . . . i.e., no crash-ing. Perhaps this to will change?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857815 Title: cups-browsed assert failure: corrupted double-linked list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1857815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1825587] Re: non-existent temporary desktop file appears on desktop
I have since moved on to Lu 19.10 where this problem no longer is happening . . . it has other problems, but this desktop file problem is seemingly resolved in 19.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825587 Title: non-existent temporary desktop file appears on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/lxqt/+bug/1825587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
Just to add my $.02 . . . I also had this problem with perhaps 6/12 daily and then I zsyncd what I think is the 6/15 daily . . . finding the same "kernel panic" report as Dan found. A couple days later I downloaded a fresh 19.04 iso and ran the install . . . and that went well. Glad to hear that a fix has been engineered, right now I don't have the 19.10 iso installed to flash drive so I can't test out this proposed fix . . . may or may not get to that . . . . I might try to upgrade to 19.10 via the console . . . . But, this problem was "frustrating" in that, as Dan mentions, the "live" system appeared to be "fine" and the installer did not report "errors" and yet would not boot into the installed system, or tty to try stuff out . . . which possibly would have failed anyway?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1829805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825587] Re: non-existent temporary desktop file appears on desktop
Gents: Thanks for the comments . . . I did "sudo" . . . because "su" wasn't accepted ?? But I did "bulk" run the commands . . . . but the first one "E'd" out even with "sudo" . . . which I guess was w/o "sources" . . . . Haven't spent time to look at the repos I have in Lu 19.04 to know if "sources" is something to "check on" or "off" . . . . But, anyway, as of now, the "refresh" method does clear the desktop . . . it's not "life threatening" . . . might just wait for the upstream data to stream down to me . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825587 Title: non-existent temporary desktop file appears on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/lxqt/+bug/1825587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1825587]
@Walter: I'm sure you don't need me to confirm, but, just to confirm, your instructions to "reload" the desktop folder does work to clean up the desktop of this non-existent file . . . easy enough to do. As I posted on the bug, I did try to run Alf's series of commands . . . and w/o something from "sources" the whole series of commands "E'd" out . . . . So perhaps some further work has to be done "upstream"??? He seems to be the guy who is part of the team that has responded to this bug . . . in a sense "non-critical" . . . but on the aesthetic level . . . "critical" . . . . F > Until then, you cannot really do anything with the file since it doesn't > exist. The work around is in the description: > 1. Open pcmanfm-qt > 2. Go to the Desktop folder > 3. Refresh the folder (F5) > Now the errant file will not return, no matter whether or not you check > shortcuts on or off. It will return when you log in again, though. > > One other thing: the issue here is a timing issue, and it will be made > worse with less resources. That means that sometimes you might have the > issue and sometimes you might not. It's bizarre. Kudos to the upstream > developers for finding it so quickly. > > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825587 Title: non-existent temporary desktop file appears on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/lxqt/+bug/1825587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1825587] Re: non-existent temporary desktop file appears on desktop
@Alf: Well I guess I got my answer on this, simply running the list of commands essentially "errored out" "sudo apt source libfm-qt Reading package lists... Done E: You must put some 'source' URIs in your sources.list @-pc:~$ apt install debhelpers devscripts E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root? @-pc:~$ apt build-dep libfm-qt E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root? @-pc:~$ debuild Command 'debuild' not found, but can be installed with: sudo apt install devscripts @-pc:~$ apt install ./*deb ^C" I cancelled out of it at the "./*deb" line as all of the previous commands had failed So, apparently I do need to find some "sources" for this to work ??? And install some stuff?? F On Tue, Apr 23, 2019 at 1:15 PM Alf Gaida wrote: > otherwise a local build with the patch applied is cheap > > get the released sources, put the patch into the debian/patches dir and > into the series file > > apt source libfm-qt > apt install debhelpers devscripts > apt build-dep libfm-qt > debuild > apt install ./*deb > > login, logout, done ... > > -- > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825587 Title: non-existent temporary desktop file appears on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/lxqt/+bug/1825587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1825587] Re: non-existent temporary desktop file appears on desktop
@Alf: OK, thanks for the post on this . . . sorry to ask, but, are you saying to "get the released sources, Put the patch into debian patches . . ." AND THEN run the series of commands you provided?? OR, by running that series of "apt source libfm-qt . . . . to apt install ./*deb" . . . and logging out and in . . . that the released sources and patches will be "sourced" and "installed" . . . ??? Looking at the list of commands it does seem like that is the only sets that are needed??? F On Tue, Apr 23, 2019 at 1:15 PM Alf Gaida wrote: > otherwise a local build with the patch applied is cheap > > get the released sources, put the patch into the debian/patches dir and > into the series file > > apt source libfm-qt > apt install debhelpers devscripts > apt build-dep libfm-qt > debuild > apt install ./*deb > > login, logout, done ... > > -- > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825587 Title: non-existent temporary desktop file appears on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/lxqt/+bug/1825587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1825587]
Walter: Thanks for the clarifications and the reminder on how to "refresh the desktop" . . . . I will stay tuned, etc. F On Tue, Apr 23, 2019 at 10:51 AM Walter Lapchynski wrote: > Fritz, the reason you see quick fixes is because LXQt is actively being > developed, unlike LXDE, which hasn't been in a long, long time. There's > a reason why every new release of Lubuntu was essentially a maintenance > release. > > Anyways, it sounds like the consensus is that though this has a > relatively small impact, it's ugly and offensive enough that we should > do a SRU. That means that we should see it in Disco relatively soon. > Part of that process will involve some editing of this bug report. Then > when the fix is uploaded, it will go to "Fix Committed." Finally, when > the package with the fix is available in the repositories, it will go to > "Fix Released." At this point, running an update on libfm-qt and > pcmanfm-qt (since it's built based on libfm-qt) will resolve the issue. > > Until then, you cannot really do anything with the file since it doesn't > exist. The work around is in the description: > 1. Open pcmanfm-qt > 2. Go to the Desktop folder > 3. Refresh the folder (F5) > Now the errant file will not return, no matter whether or not you check > shortcuts on or off. It will return when you log in again, though. > > One other thing: the issue here is a timing issue, and it will be made > worse with less resources. That means that sometimes you might have the > issue and sometimes you might not. It's bizarre. Kudos to the upstream > developers for finding it so quickly. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1825587 > > Title: > non-existent temporary desktop file appears on desktop > > Status in LXQt: > Fix Released > Status in libfm-qt package in Ubuntu: > Triaged > > Bug description: > STEPS TO REPRODUCE >1. Boot to installed system >2. Note that desktop shortcuts for Home, Trash, Computer, and Network > are all displayed, along with a user-home.desktop with a 6 digit > alphanumeric string appended to it >3. Note that the file does not exist (e.g. with the file manager) >4. Right click on the desktop >5. Click on "Desktop Preferences" >6. Click on the "Advanced" tab >7. Uncheck "Home" >8. Click OK >9. Note that the desktop shortcut for Home and the extra non-existent > file disappears but nothing else changes > 10. Repeat steps above, but check "Home" again > 11. Note that all of the desktop shortcuts are displayed, but also a new > file, most likely computer.deskop, but with a 6 digit alphanumeric string > appended to it. > 12. Note that the file does not exist (e.g. with the file manager) > 13. Log out and back in again > 14. Note that now there's a user.desktop instead of a computer.desktop > > EXPECTED RESULTS >* non-existent files should not be displayed on the desktop >* if shortcuts files are temporarily renamed with the random string > appended, they should be recycled when finished > > ACTUAL RESULTS > The shortcuts display correctly, but the additional non-existent file > sometimes shows. There is an unambiguous way to reproduce (see below), but > it's not consistent: >* Lubuntu 19.04 live does not have the problem >* Lubuntu 19.04 install boots to the problem >* When pcmanfm-qt is restarted in Lubuntu, the errant file goes away, > but logging out and back in again returns the problem > > NOTES > Also occurs in Debian testing, though it doesn't initially have the > problem and only affects the Home shortcut. > > WORKAROUND >1. Open pcmanfm-qt >2. Go to the Desktop folder >3. Refresh the folder (F5) > Now the errant file will not return, no matter whether or not you check > shortcuts on or off. It will return when you log in again, though. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: pcmanfm-qt 0.14.1-0ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 > Uname: Linux 5.0.0-13-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: LXQt > Date: Fri Apr 19 15:18:20 2019 > InstallationDate: Installed on 2019-04-18 (0 days ago) > InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > SourcePackage: pcmanfm-qt > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/lxqt/+bug/1825587/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825587 Title: non-existent temporary desktop file appears on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/lxqt/+bug/1825587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/lis
Re: [Bug 1825587] Re: non-existent temporary desktop file appears on desktop
> We could work on ensuring it's in Disco, as we should be able to pull in > just the patch that fixes it, but it will require testing and a bunch of > paperwork. Since it has a relatively small impact, I'm a little > disinclined to go through all that, but we're discussing it. We'll > update the bug if we go this route. > > ** Package changed: pcmanfm-qt (Ubuntu) => libfm-qt (Ubuntu) > > > @Walter: No worries on it, I'm even amazed that there is a "fix committed" . . . coming from the olde PPC linux days, etc. But, it appears that I spoke too soon; yesterday I logged in and out of Lubuntu D a couple times and the "non-existent" file was just that . . . this morning, booted back into Lu and there it is in all its "existent" desktop glory . . . . It's not a show-stopper, so if it requires bureaucratic nightmare to "fix" it in Disco, don't do it . . . . I did run update/upgrade yesterday, and there were only a few packages to upgrade . . . it seemed like somehow **before** I ran the upgrade the "fix had been . . . in" . . . but, back on the planet . . . it remains. Can't remember if you mentioned it here . . . is this something that can be "trashed" . . . OR, better to just drag a window over it if I don't want to see it??? F -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825587 Title: non-existent temporary desktop file appears on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/lxqt/+bug/1825587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1825587] Re: non-existent temporary desktop file appears on desktop
On Sun, Apr 21, 2019 at 5:35 PM Bug Watch Updater < 1825...@bugs.launchpad.net> wrote: > ** Changed in: lxqt >Status: New => Fix Released > > Problem does seem to have been resolved, even before running an upgrade??? Thanks for the rapid response on this issue . . . minor annoyance . . . . F -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825587 Title: non-existent temporary desktop file appears on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/lxqt/+bug/1825587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814326] Re: [solved] home, root, and temp folders display errors
** Summary changed: - home, root, and temp folders display errors + [solved] home, root, and temp folders display errors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: [solved] home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814326] Re: home, root, and temp folders display errors
@Alf, et al: Yes. Is this marked in "status" as "fix released"?? Or name of bug is changed to show [solved]?? Or I do nothing and it returns back into empty cyber space in time? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1814326] Re: home, root, and temp folders display errors
@Alf: That does seem to have solved the glaring exclamation and "error" issues . . . . On Thu, Mar 14, 2019 at 3:23 PM Fritz Hudnut wrote: > > > On Thu, Mar 14, 2019 at 3:05 PM Alf Gaida wrote: > >> A possible solution - just delete the trash, network, user and computer >> icon and restart the machine (the desktop icons will be re-created) >> >> As long there is a broken desktop file present no update and no new >> version will help. >> >> >> @Alf: > > Amazingly simple to try . . . I'll try that later and see how it goes. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1814326] Re: home, root, and temp folders display errors
On Thu, Mar 14, 2019 at 3:05 PM Alf Gaida wrote: > A possible solution - just delete the trash, network, user and computer > icon and restart the machine (the desktop icons will be re-created) > > As long there is a broken desktop file present no update and no new > version will help. > > > @Alf: Amazingly simple to try . . . I'll try that later and see how it goes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1814326] Re: home, root, and temp folders display errors
@Alf: Alrighty, thanks for the post back . . . it isn't an insurmountable problem enough to warrant a fresh install . . . on what is a "developmental distro" . . . . It's now updated to LXQT "latest edition" . . . still a tad "irritating" to get an error window when trying to open the Home directory . . . . Just posting on the bug report, because it's a "problem" . . . and there was a post on the Lubuntu user's list-serve basically complaining about this "failure to open" error when clicking on desktop icons . . . . If a random update/upgrade "solves" the problem I'll post back on it . . . otherwise "we'll" just consider it a continuing "problem" . . . . On Thu, Mar 14, 2019 at 2:31 PM Alf Gaida wrote: > Download the latest disco daily and be done with - it makes no sense to > track this down. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1814326 > > Title: > home, root, and temp folders display errors > > Status in pcmanfm-qt package in Ubuntu: > New > > Bug description: > Folks: Not sure why this is "LxFIND" . . . for problem in Lubuntu > Next 18.10 && Lu 19.04 . . . after latest update/upgrade, the desktop > icons for Home, Root, and Temp folders have exclamation points over > them . . . previously in both 18.10 & now 19.04 . . . 2x clicking on > each of them brought an "error" window . . . now the Home folder shows > "Invalid desktop entry file: 'file:$HOME" when trying to open the > folder that way. Root shows the same error . . . Temp shows an > "execute file" window "This file 'Temp' seems to be a desktop entry. > What do you want to do with it?" options for open or execute . . . . > > Clicking on the PCmanFM-Qt file manager does open the Home folder > without error . . . . This isn't "earth shattering" of a problem, but > problem has persisted from 18.10 to 19.04 and the problem along with > some issue about properties showing 0 bytes in some folders was > reported on the Lubuntu Users list serve by another individual . . . > and I was the only person on the list to respond to this posters > findings . . . which, I did find . . . > > F > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814326] Re: home, root, and temp folders display errors
@Alf, et al: Another big upgrade/update via apt . . . the PCManFM-QT file manager issue (applet not launching the file manager window) problem seems to be repaired, along with the 100 windows phenom . . . . Checking on the version of LXQT now does show the latest version "0.14.1" . . . however, the remaining exclamation point remains over the "Home" desktop icon . . . and double clicking continues to bring the "Invalid desktop entry file: 'file:$HOME" error window. In the right-click menu and "properties" >"permissions" the "make file executable" is checked "on" . . . but now there is an "advanced options" toggle button (don't know if it was there before) . . . but the button is "greyed out" and does not respond to clicks . . . unchecking the "executable" box does not change the "greyness" of the advanced options button . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814326] Re: home, root, and temp folders display errors
Just for humor . . . now clicking on the toolbar PCMan-QT file manager applet . . . nothing happens; right-clicking it shows a drop down menu with some options, but it doesn't go away . . . and now, when I dragged the FireFox window . . . it shows something like one hundred Firefox windows Like instead of showing the window in its old place and then in the new place . . . it shows the "stop-action" frames of the movement . . . . Oh well, was hoping that this ws going to be the "go to" operating system . . . a little quirky still. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814326] Re: home, root, and temp folders display errors
@Alf, et al: Latest update on the exclamations . . . ran a fairly large apt update/upgrade this am, possibly including the kernel . . . and there is both good news and also "stalemate" as well . . . . In the packages listed there was one file named something like "lxqt-n|10"??? which I think was the name of the file that showed up in Muon Package the other day, but checking the version of LXQT after the upgrade it still shows it as "0.14.0" . . . we have not achieved One-ness . . . aka 0.14.1. After the reboot I right-clicked on the "root" and the "temp" icons, and in the drop down menu for those two items was now a "trust this executable" line option. . . which I then "checked" and instantly the exclamations were gone. Right-clicking "open with" and "featherpad" opens a file for them that lists some data . . . but double clicking does not open them . . . the "up" side is that there is no longer an error window opening for them . . . . However, on the Home directory icon, stalemate remains, the exclamation continues to fly . . . just to check it I opened permissions and the "make the file executable" was still checked . . . I unchecked it and logged out, then logged back in and checked it again . . . clicked "OK" and no change. Double clicking the icon does nothing except to open the error message as it has been doing . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814326] Re: home, root, and temp folders display errors
@Alf: Alrighty then, thanks for the follow-up and clarification . . . "traditionally" it seemed like packages that were available for various ubuntu flavors were often .deb files . . . . I did get to the lxqt.org downloads site earlier today and indeed the "0.14.1" packages were numerous and it didn't seem like a "one click" kind of install . . . so caution being the better part of valor, I didn't want to create a big mess out of it . . . likely I'll wait until apt can handle it, or muon/synaptic shows it as a complete DE . . . . Thanks for the conversation on it . . . I'll post back if and when it seems like the system has upgraded LXQT and/or if and when the flashing exclamation points go away . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814326] Re: home, root, and temp folders display errors
@Alf: OK . . . "foreign packages"?? Generally I don't have time for it, but does that mean if it doesn't show up in synaptic or muon then it's "foreign"?? Haven't had a chance to look at the "LXQT" web site to see if anything for "0.14.1" is available as a download there . . . but if it is there as a .deb file . . . is that what you mean by "foreign"??? Seems like what's on muon is "meta package version 29" . . . but doesn't seem like a complete "lxqt" package is available yet for Disco??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815148] Re: Bottom panel “flickers” when scrolling in FireFox?
Just ran the latest update/upgrade w/ new kernel and rebooted . . . flickering bottom panel problem remains . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815148 Title: Bottom panel “flickers” when scrolling in FireFox? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1815148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814326] Re: home, root, and temp folders display errors
@Alf: Thanks for the reply . . . alrighty then, so either the latest release will show up in the regular updates/upgrades via apt at some future time . . . or, look around and see if the 0.14.1 version is available to download and then use the olde "deb installer" ??? to install the downloaded package, whatever that is called?? There is no real rush on it, just that seeing those exclamation points as well as the "error" message flash when trying to open the desktop folders . . . is . . . un-smooth . . . very un-smooth. : - ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1814326] Re: home, root, and temp folders display errors
On Mon, Mar 4, 2019 at 9:30 AM Alf Gaida wrote: > @Fritz: with my upstream hat on: It would be nice to have the latest > LXQt release in Ubuntu. (Bonus points for packages that follow upstream > as far es possible) > > -- > > @Alf: Back in Lu 19 . . . LXQT version installed shows "0.14.0" . . . looking in synaptic shows two packages installed that are "0.14.1" . . . lxqt-admin && lxqt-admin|10 (closed the window so I can't remember exactly) . . . the rest of the packages are from 0.14.0 . . . . I ran a search for "lxqt 0.14.1" in synaptic and nothing showed up. Late update, I just found "muon package manager" . . . seems like a hotted up version of synaptic . . . ran "lxqt 0.14.1" and it brings "lxqt meta-package" for "version 29" shows as "not installed" . . . but, as mentioned it seems like the LXQT web site shows latest edition as the 0.14.1??? Saw your name mentioned in the meta package details, so this must be "official" . . . ??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814326] Re: home, root, and temp folders display errors
@Alf: OK, I think I get it, you are talking about LXQT 0.14.1??? As mentioned I am running Lubuntu 19.04, more or less I'm an end user . . . specializing in using the GUI as provided by the distro . . . . But in linux to me it's all "experimental" and if running the regular apt update/upgrade doesn't include installing the latest version of LXQT I am happy to play with it . . . . Would this show up in synaptic package manager or would this be a console install??? I'm away from that computer for the day . . . might not get to this until tomorrow-ish . . . is this a simple command effort like "sudo apt install lxqt"??? Or something where I'd have to indicate the version . . . "sudo apt install lxqt.0.14.1" ??? Any of those ideas??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814326] Re: home, root, and temp folders display errors
@Alf: I tried to follow the github "conversation" that you were engaged in, bit beyond my pay grade . . . but this morning I quickly checked the "home" folder via right click and in permissions the "make file executable" box was checked as "on" . . . ??? Don't know if that relates to the suggested "solution" . . . and not sure where you are standing, but to me, the "home" desktop file is part of my "user" data and should seemingly just "work"??? Don't know why I should have to mess with it to get it to "work"??? Why should I have to "activate" my desktop folders?? Other question, why is it that trying to open those desktop files results in "error" message?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1814326] Re: home, root, and temp folders display errors
@Alf: Thanks for the post on it, good to know that it is on purpose, but if it is a feature . . . what is it featuring? I have the latest upgrade on 19.04 . . . is there a newer version? 19.04 is "developmental" release . . . . On Sun, Mar 3, 2019 at 5:40 PM Alf Gaida wrote: > Solution: just update to the last release. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1814326 > > Title: > home, root, and temp folders display errors > > Status in pcmanfm-qt package in Ubuntu: > New > > Bug description: > Folks: Not sure why this is "LxFIND" . . . for problem in Lubuntu > Next 18.10 && Lu 19.04 . . . after latest update/upgrade, the desktop > icons for Home, Root, and Temp folders have exclamation points over > them . . . previously in both 18.10 & now 19.04 . . . 2x clicking on > each of them brought an "error" window . . . now the Home folder shows > "Invalid desktop entry file: 'file:$HOME" when trying to open the > folder that way. Root shows the same error . . . Temp shows an > "execute file" window "This file 'Temp' seems to be a desktop entry. > What do you want to do with it?" options for open or execute . . . . > > Clicking on the PCmanFM-Qt file manager does open the Home folder > without error . . . . This isn't "earth shattering" of a problem, but > problem has persisted from 18.10 to 19.04 and the problem along with > some issue about properties showing 0 bytes in some folders was > reported on the Lubuntu Users list serve by another individual . . . > and I was the only person on the list to respond to this posters > findings . . . which, I did find . . . > > F > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814326] Re: home, root, and temp folders display errors
Again ran the update/upgrade via apt . . . glaring exclamation points continue to glare. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814326] Re: home, root, and temp folders display errors
Ran another update/upgrade a couple days back . . . had some other issues with getting "authentication failed" error requiring jumping to a TTY to be able to log in to my user . . . . But, whatever that was about the reported issues in this bug continue to be present . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814326 Title: home, root, and temp folders display errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815148] Re: Bottom panel “flickers” when scrolling in FireFox?
Problem continued, even after I did a "panel reset" to the panel . . . . Tried to flip up an "apport-collect 1815148" to add the data, but apport "failed to find a browser" even though Firefox was launched . . . and I was logged in to LP . . . no report generated--"failed" to report . . . ??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815148 Title: Bottom panel “flickers” when scrolling in FireFox? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1815148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815148] Re: Bottom panel “flickers” when scrolling in FireFox?
Sorry . . . nope, problem still happening . . . as type this post the panel flickers . . . same as before . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815148 Title: Bottom panel “flickers” when scrolling in FireFox? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1815148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815148] Re: Bottom panel “flickers” when scrolling in FireFox?
Oops . . . seems like possibly after the problem showed in the Terminal for the latest upgrade . . . problem may have resolved??? I'll "monitor" the situation . . . didn't do the restart yet on the upgrade . . . possibly might return??? But, for now . . . not happening . . . after some weeks of it being there . . . this recent upgrade may have fixed it??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815148 Title: Bottom panel “flickers” when scrolling in FireFox? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1815148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815148] Re: Bottom panel “flickers” when scrolling in FireFox?
Noticed that the problem was happening while using the Terminal as well. As an update/upgrade was running the panel was flickering . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815148 Title: Bottom panel “flickers” when scrolling in FireFox? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1815148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815148] [NEW] Bottom panel “flickers” when scrolling in FireFox?
Public bug reported: Fairly fresh install of MATE 18.04 in MBP '09 . . . overall working well, but lately noticing that the bottom panel will “flicker” when scrolling down through some web page, or, also as a web page is loading . . . once the page has loaded the flickering stops . . . . Seemed like if more than one app is loaded and showing in the panel the problem is “less” . . . . It’s not a show stopper, but, somewhat irritating . . . visually distracting. I saw another thread entitled “Panel flickering” in 16.04, and I read through it, some of the posters were mentioning “window compositor” in MATE Tweaks . . . but I couldn’t exactly figure out what they wanted the OP to do with it . . . . Window Manager was originally set to "Marco (adaptive compositor) . . . which is possibly the default, I don’t think I changed it or set it to that . . . . I have another install of U-MATE 18.04 on a desktop computer, but the problem does not seem to affect that computer . . . I did change the WM on that install to Marco (Compton) . . . after that suggestion was made as a way to solve the problem on the laptop . . . . This issue was posted on the U-MATE forum and it brought the suggestion to try to change the WM to Marco (Compton) which helped the poster and one other individual . . . but doing that change did not solve the issue . . . where each key stroke makes the panel “shake” . . . or scrolling will "split" the panel horizontally . . . . I've done a few updates/upgrades to the system since the install--problem persists. ** Affects: mate-panel (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/1815148 Title: Bottom panel “flickers” when scrolling in FireFox? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1815148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814350] Re: "properties" in applications shows "file size 0 bytes"
@Walter: No worries on the "invalid" . . . this issue was "publicly reported" on the list serve by another individual and I was the only person to respond to it there . . . possibly I CCd you on it as well to which no reply was posted to the several posts that were sent there by the two of us. I assumed that the "applications" folder/directory in linux is "similar" to OSX, where the "Applications" folder contains . . . the applications . . . rather than what I'm now assuming would be an "alias" that might be used to open or launch said application . . . ??? In OSX >application folder, right-clicking on the Maps icon shows "9.7MB" of content . . . so it appears that in linux the "applications" directory in pcmanfm-qt does not contain "applications." My apologies for cross-posting two bugs within one bug . . . I'm sure that any devs coming across the bug will be able to figure it out, another bug report was filed for a problem likely posted on the list serve previously. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814350 Title: "properties" in applications shows "file size 0 bytes" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1814350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798176] Re: Lu Next 18.10 doesn't revive from suspend with keystroke or mouse click
Does seem like this issue has been resolved via apt update/upgrade . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798176 Title: Lu Next 18.10 doesn't revive from suspend with keystroke or mouse click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1798176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798175] Re: Lubuntu Next--toolbar opens in the middle of the screen and then jumps to top
apt-cache policy lxqt-panel Running that command brings: "~$ apt-cache policy lxqt-panel lxqt-panel: Installed: 0.13.0-0ubuntu5 Candidate: 0.13.0-0ubuntu5 Version table: *** 0.13.0-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 100 /var/lib/dpkg/status" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798175 Title: Lubuntu Next--toolbar opens in the middle of the screen and then jumps to top To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1798175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798175] Re: Lubuntu Next--toolbar opens in the middle of the screen and then jumps to top
Bug filed against ubiquity-slideshow in error ** Package changed: ubiquity-slideshow-ubuntu (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798175 Title: Lubuntu Next--toolbar opens in the middle of the screen and then jumps to top To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1798175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798176] Re: Lu Next 18.10 doesn't revive from suspend with keystroke or mouse click
Bug filed under ubiquity-slideshow in error. ** Package changed: ubiquity-slideshow-ubuntu (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798176 Title: Lu Next 18.10 doesn't revive from suspend with keystroke or mouse click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1798176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798176] Re: Lu Next 18.10 doesn't revive from suspend with keystroke or mouse click
Also, over here, right it was supposed to be at least an open "ubuntu" bug . . . lost in LP. Right after I filed this bug I ran an update/upgrade and that seems to have revived the key stroke revival from suspend. I'll monitor it a bit and if it has been resolved I'll try to take this bug down or report it as "solved" . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798176 Title: Lu Next 18.10 doesn't revive from suspend with keystroke or mouse click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1798176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798175] Re: Lubuntu Next--toolbar opens in the middle of the screen and then jumps to top
Right. It was supposed to be a "generic" "lubuntu 18.10" bug . . . this was an upgrade from 18.04 to 18.10 via console and this **panel** problem was a result of that system release upgrade process . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798175 Title: Lubuntu Next--toolbar opens in the middle of the screen and then jumps to top To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1798175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798176] [NEW] Lu Next 18.10 doesn't revive from suspend with keystroke or mouse click
Public bug reported: Recent upgrade from Lu Next 18.04 to 18.10 has seemed to break the "wake from suspend" via key stroke or mouse click . . . now the power button has to be used for each revival . . . . Also the splash window says "ubuntu 18.10" rather than "lubuntu next 18.10" or what have you. ** Affects: ubiquity-slideshow-ubuntu (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/1798176 Title: Lu Next 18.10 doesn't revive from suspend with keystroke or mouse click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1798176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798175] [NEW] Lubuntu Next--toolbar opens in the middle of the screen and then jumps to top
Public bug reported: When logging into Lubuntu Next 18.10 GUI, the toolbar panel is selected for "top" but it launches in the middle of the display and then jumps up to the top . . . . It's a distraction that didn't happen in Lu Next 18.04. ** Affects: ubiquity-slideshow-ubuntu (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/1798175 Title: Lubuntu Next--toolbar opens in the middle of the screen and then jumps to top To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1798175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768290] Re: Lubuntu Cosmic mistakenly opens LXDE Xsession by default
@Walter: OK, thanks for the effort on it . . . I did do some updates today, but haven't checked to see if that effected the choice of sessions . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768290 Title: Lubuntu Cosmic mistakenly opens LXDE Xsession by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1768290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1768290] Re: Lubuntu Cosmic mistakenly opens LXDE Xsession by default
" Also we may want to just clean up and minimize the sessions in general. + Why we have four is beyond me." @Walter: Once the "Lubuntu QT" session is selected upper left the problem is solved . . . as someone who multi-boots and/or traditionally had a couple DEs per install "more sessions" is not the problem; the problem is when the listed sessions either don't work, and/or throw an error requiring an extra step to get past, as in the case with what must be the regular "Lubuntu" session here. If there is an option for logging into a "regular Lubuntu" session from Lubuntu Next that might be "value added" . . . similar to how Lubuntu has included "OpenBox" DE alongside . . . . The main thing to change might be that the default session for Lu Next would be the "Lubuntu QT" session . . . also as in the past there might have been DE's or sessions included that "didn't work" . . . no need to erase them, just have the one that works be first up as "default." F -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768290 Title: Lubuntu Cosmic mistakenly opens LXDE Xsession by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1768290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1768294] Re: "eject" key doesn't open optical drive tray in Openbox
@walter: Thanks for the reply . . . haven't had to do an update/upgrade recently, checked a few days ago and apt said, "nothing to do at this time" . . . . Sometimes over in one of my "rolling" distros there can be a lot of "dependency" issues that crop up with updates, requiring actual thought . . . . I try to avoid that if possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768294 Title: "eject" key doesn't open optical drive tray in Openbox To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-next/+bug/1768294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1768294] Re: "eject" key doesn't open optical drive tray in Openbox
Success!!! I did use sudo, but using the "lxqt" option brought me to the "744 lines" and I used your shortcut to get me to line 192 and then scrolled down to the end right before "mouse" and I dropped your code in and . . . seems like I must have done "OK" because hitting the eject key . . . opens the tray!! I'm ready to be hired as a "programmer" . . . . : - )) Also, as you mentioned in Lu Next just typing "eject" does work . . . pretty sure it didn't over in reg Lu 18 . . . . One question . . . now that I've "modified" this file, will anything "strange" be in store whenever the next update/upgrade comes down the tubes? Or, will the system "see" that the change has been made and won't "care"? Or, will it have to be trashed . . .manually?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768294 Title: "eject" key doesn't open optical drive tray in Openbox To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-next/+bug/1768294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
