[Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
I upgraded from 16.04 to 18.04 (from kernel 4.4.0-193-generic to 4.15.0-122-generic) and I had this exact issue. Same HP Microserver Gen 8 as the others, probably there's something in their motherboard that makes SATA disks discovery particularly slow, and the kernel (or initrd scripts harness?) doesn't _really_ wait for /dev to populate properly. Doesn't seem fixed in next kernels, or at least not in what is available on 18.04 - I installed the HWE kernel (5.4.0-52-generic) and I have the problem just the same; the only thing that fixed it was the "sleep" workaround before "/bin/btrfs device scan". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752961 Title: With kernel 4.13 btrfs scans for devices before all devices have been discovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872800] Re: Problem with default monospace font
Related to https://bugs.launchpad.net/ubuntu/+source/kubuntu- settings/+bug/1872492; that 56-kubuntu-noto.conf that is installed stealthily by kubuntu-settings-desktop overrides way too much system- wide stuff, and should just NOT be included. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872800 Title: Problem with default monospace font To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1872800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872492] Re: Setting in /etc/fonts/conf.avail/56-kubuntu-noto.conf causes Arimo font to be rendered weirdly in Firefox
This is still a problem; the aforementioned file ruins fonts rendering in Firefox in many common sites (Twitter, Gitlab, many Google sites). The easiest fix for me was to remove the /etc/fonts/conf.d/56-kubuntu- noto.conf symlink completely, and add it to dpkg excludes, putting ``` # Ignore defective kubuntu fontconfig directives path-exclude=/etc/fonts/conf.d/56-kubuntu-noto.conf ``` in a file under /etc/dpkg/dpkg.cfg.d. Please fix this ASAP, it greatly degrades the browsing experience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872492 Title: Setting in /etc/fonts/conf.avail/56-kubuntu-noto.conf causes Arimo font to be rendered weirdly in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1872492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872492] Re: Setting in /etc/fonts/conf.avail/56-kubuntu-noto.conf causes Arimo font to be rendered weirdly in Firefox
But more in general, I think that kubuntu-settings shipping system-wide font hinting overrides to fonts used by a ton of applications/sites deeply wrong. IDK what you wanted to accomplish here, but that's not the way nor the right package. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1872492 Title: Setting in /etc/fonts/conf.avail/56-kubuntu-noto.conf causes Arimo font to be rendered weirdly in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1872492/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 213215] Re: Please include original cdrecord (cdrtools) package in Ubuntu
Woa, now the ridicolousness of this debate is getting critical, I've seen five-year-old children way more reasonable than the two opposing parties involved in this debate. If this wasn't keeping millions of systems with broken software it would be at least mildly entertaining; seeing how this is going, probably our best hope is that optical media just phase out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/213215 Title: Please include original cdrecord (cdrtools) package in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/213215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569755] Re: Get rid of nspluginwrapper for flashplugin on AMD64
I too think that this should be solved. nspluginwrapper is *way* buggier than almost any 64 bit alpha plugin that Adobe released in the last years. It's been quite a while since Debian and Mint moved to the native plugin, why isn't Ubuntu doing the same? This seriously affects the usability of the system on the Internet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569755 Title: Get rid of nspluginwrapper for flashplugin on AMD64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/569755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909887] Re: compiz crashed with SIGSEGV (Xubuntu 11.10)
The debug symbol packages installed come all from the offical dbgsym repository and are as updated as it is, if they don't match the installed versions it's not my fault, and I wouldn't know how to remedy. Also, I don't think that any of those libraries are involved in some way in the crash, since: - none of them is directly correlated with compiz, and the gdb instance called by the crash plugin for compiz, - none of them were mentioned in the debug crash logo created by the compiz crash handler plugin; - after I installed the debug symbols, the gdb instance called by the crash handler plugin never complained in its log about version mismatching. Also, the problem seems way deeper than just missing symbols, since the faulty location corresponds either to /dev/zero or to a deleted file in /tmp, so I doubt that any installed symbol could provide meaningful results for that. Anyway, I got tired of the instability of 11.10 (which gave me several other problems), so I replaced that installation with Debian Stable; it runs without problems with compiz 0.8.4 and the nVidia drivers 195.36.1 (and I got Gnome 2.30 back, wohoho!). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909887 Title: compiz crashed with SIGSEGV (Xubuntu 11.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/909887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909887] Re: compiz crashed with SIGSEGV (Xubuntu 11.10)
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909887 Title: compiz crashed with SIGSEGV (Xubuntu 11.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/909887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909887] Re: compiz crashed with SIGSEGV (Xubuntu 11.10)
Again on the stack trace: I installed the -dbg/-dbgsym packets of every
library about which the Compiz crash plugin log complained ("no symbol
found"), but it didn't add any detail to the stack trace.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/909887
Title:
compiz crashed with SIGSEGV (Xubuntu 11.10)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/909887/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909887] Re: compiz crashed with SIGSEGV (Xubuntu 11.10)
Further examination of the process map shows that the fault address (0x406fcee8) belongs to a portion of memory associated with the file "/tmp/glNSpQ5n (deleted)". I am inclined to think that this file belongs to the proprietary nVidia drivers: I heard several times that they need /tmp to be executable otherwise they won't work correctly, so probably they place part of their stuff there to be loaded by executables. Maybe I'll try again to use older drivers and check if I get some result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909887 Title: compiz crashed with SIGSEGV (Xubuntu 11.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/909887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 909887] Re: compiz crashed with SIGSEGV (Xubuntu 11.10)
Tested older nVidia drivers (version 173-updates), crash again. This time the memory region of the crash (almost the same) is associated with /dev/zero, go figure... One thing I forgot to mention: on this very machine I run without problems Linux Mint 11 with compiz enabled; thinking that maybe there was a regression in the Oneiric compiz packages, I also tried to downgrade them to the Natty versions, but without success. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/909887 Title: compiz crashed with SIGSEGV (Xubuntu 11.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/909887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 963736] Re: thunderbird freezes at random : must be killed and reload
*** This bug is a duplicate of bug 1142213 *** https://bugs.launchpad.net/bugs/1142213 ** This bug has been marked a duplicate of bug 1142213 emacs23/24 GUI does not start when run in Kubuntu 13.04 with oxygen-gtk theme enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963736 Title: thunderbird freezes at random : must be killed and reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/963736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 213215] Re: Please include original cdrecord (cdrtools) package in Ubuntu
Schily, what's wrong with adding those words, even if they are redundant? If your interpretation of the matter is correct (and I believe it is, although IANAL) you are just making extra-explicit what is already permitted by of your license and the GPL, so you aren't granting any extra permission over what can be done with your code - from your point of view nothing changes. On the other hand, people who think that the situation is currently into a "grey zone" will be relieved by the explicit permission, and we'll put to an end to the whole cdrkit nonsense. Everybody wins. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/213215 Title: Please include original cdrecord (cdrtools) package in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/213215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961791] Re: 2.54.3+21.10.1ubuntu0.1 broke Plasma Desktop when Fish is the default shell
Other trivial workaround: keep snapd to 2.44.3 (at least on 20.04), possibly forever. There's a serious QA problem here, in a week I got three updates, each of which progressively broke stuff worse than the previous one: - first warnings every time I opened a shell - then broken XDG env, which made applications crash in the strangest ways but only when started from the shell - then even more broken XDG env that literally _broke the user session after login_. I don't think a bug can get worse than this, as it makes the machine (progressively more) impossible to use _for tasks unrelated to those for which you need this package_, and, with the exception of the first problem, without any hint about the fact that it's snapd fault — in the last case I only suspected that (and downgraded) because I was bit by the first issue, I had to debug the second one, and it dawned on me that they could have fucked up the fix for a third time after managing to open a shell inside the broken session through strange expedients and checking the environment. I get that the Linux desktop environment initialization is a shitshow, but after breaking this for the first time the response should have been immediate rollback and _thorough_ testing instead rushing fixes, at least on the LTS channel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961791 Title: 2.54.3+21.10.1ubuntu0.1 broke Plasma Desktop when Fish is the default shell To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1961791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
