[Bug 1860851] Re: blueman-applet crashed with UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8e in position 4: invalid start byte
This error was annoying. Something triggered it and the logs were not clear on what. I'm was file corruption somewhere. I had some old files in /home/myusername/.cache/blueman* I removed those and logged out and in. No more crash but it may not last. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860851 Title: blueman-applet crashed with UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8e in position 4: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1860851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
FYI a kernel bisection may be outside the skill set of your average user and chances are much lower without detailed instructions. Please don't shoot the messenger. I too have a Asrock motherboard but a ASRock Z370M-ITX/ac. I had a lot off trouble getting my I219-V NICs to behave on Ubuntu. I started on 18.04 and eventually went to 19.10 with the Intel e1000e 3.6.0-NAPI driver and a bunch of commands to get good performance. File transfers were severely impacted but it is immediately obvious in iperf3 when the card is not performing properly. Tweaking several of these options added several hundred Mbps to transfers giving a consistent 60MB/s over SMB but I'm still getting half the throughput of my Windows 10 workstation when talking to the same Ubuntu server. Given my Ubuntu client storage is 5X faster the cause is unknown. I'm curious if anyone has figured out if the firmware version on the I219-V NIC is updateable and how. It's odd the same chip users different drivers and shows different firmware revisions. $ ethtool -i enp2s0 driver: igb version: 5.6.0-k firmware-version: 0. 4-1 $ ethtool -i eno1 driver: e1000e version: 3.6.0-NAPI firmware-version: 0.2-4 It's really odd to be using two different drivers for the same NIC: sudo lspci -v | grep -i ether 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V DeviceName: Onboard - Ethernet Subsystem: ASRock Incorporation Ethernet Connection (2) I219-V 02:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) I have this in my rc.local now: ethtool -A eno1 autoneg off tx off rx off 2> /dev/null || : ethtool -K eno1 gso off tso off 2> /dev/null || : ethtool -A enp2s0 autoneg off tx off rx off 2> /dev/null || : ethtool --set-eee eno1 eee off 2> /dev/null || : ethtool --set-eee enp2s0 eee off 2> /dev/null || : 1st line turns off flow control, 2nd turns off offloading specifically gso and tso, the last ones turn off a energy efficient Ethernet option. Post tweaks I consistently get 935-958Mbit/s in perf3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
FYI in terms of sustainable options I was able to find a very hard to find .deb with the latest driver as a DKMS module. It works fine for me on Ubuntu 19.10. I really wish this was in a repository which was part of universe but I'm never figured out how to do things like that. # dpkg -l | grep e1000e ii e1000e-dkms 3.6.0 all Intel e1000e Ethernet adapter driver (DKMS version) Details here: https://github.com/koljah-de/e1000e-dkms-debian The latest V3.6.0 driver I use: https://github.com/koljah-de/e1000e- dkms-debian/releases/tag/3.6.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873514] Re: Ubuntu uses insecure FreeRDP version
I suspect freerdp2 was derailed in politics much like the stalls and eventual removal of a package for guacamole-server. What is currently deployed in Ubuntu focal is a alpha development snapshot of freerdp2 2.0.0 which is buggy to the point of being unusable for Apache guacamole and has significant security holes. There are 14 CVEs currently listed as fixed in freerdp 2.1.0. The advisories, which are a recent additional reflective of the maturity of the product, can be found here: https://github.com/FreeRDP/FreeRDP/security/advisories It's hard to get an exact number on security issues between that development snapshot and the stable release but freerdp went through a lot of development before the recent stable releases appeared. Hundreds to thousands of issues fixed and some of them will have had security impact. An alpha development snapshot may been needed temporarily in an LTS release but it should be replaced with something stable once it is available. I have no interest in the politics and have not managed to navigate the bureaucracy needed to contribute packages to Debian and Ubuntu. I am trying to see if I can leverage the freerdp2 daily builds to build a stable package for freerdp 2.1.1 which is the current stable release. I'm also trying to see if I can take the 0.9.9 Debian package of Apache Guacamole and rebuild it around 1.1.0 and eventually 1.2.0 as that release is what will be stable on 20.04. If someone can help grease inclusion of the resulting packages that would be appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1873514 Title: Ubuntu uses insecure FreeRDP version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1873514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873514] Re: Ubuntu uses insecure FreeRDP version
FYI a Debian developer has started on freerdp 2.1.0, nothing is released as of yet. I took a look at all the symbols in that package and was taking the wrong approach so I didn't use my attempt. The freerdp-daily repository guys have also kindly packaged 2.1.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1873514 Title: Ubuntu uses insecure FreeRDP version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1873514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873514] Re: Ubuntu uses insecure FreeRDP version
Thanks much appreciated. I've got a development build from the freerdp- daily PPA but it's pretty clear that the symbols still need appropriate mapping. The Debian build has some it for the 2.1.0 build they started. It's clearly some kind of backwards compatibility logic but I'm unclear on intent. I'm still trying to figure out if the new freerdp2-2.1.1 package really should have libswscale support. That is desirable to the guacamole package but it is unclear if that package will need the support in freerdp2. I suspect it would be easy to add with a libswscale-dev build require to freerdp2's packaging and it should pick it up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1873514 Title: Ubuntu uses insecure FreeRDP version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1873514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873514] Re: Ubuntu uses insecure FreeRDP version
Thanks. I deliberately wasn't going to use cairo instead of libswscale as I read it may cause performance issues for image scaling. I didn't test it so some testing is needed to see if it matters or is even used with guacamole. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1873514 Title: Ubuntu uses insecure FreeRDP version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1873514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
I just started having this issue on Ubuntu 19.10 w/ 5.3.0-46-generic. What a mess... My system is an Asrock Z370M-ITXax with an Intel i3-8100. sudo cat /sys/class/drm/card0/error GPU HANG: ecode 9:0:0x, hang on rcs0 Kernel: 5.3.0-46-generic x86_64 As if all my Intel NIC problems weren't bad enough. What happened to Intel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
For what it is worth I just downgraded my kernel to 5.3.0-45.37 and I haven't had a hang since: https://launchpad.net/ubuntu/+source/linux/5.3.0-45.37 Not clear at all from the change log as to what brought this on in 5.3.0-46.38: https://launchpad.net/ubuntu/+source/linux/5.3.0-46.38 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
I wanted the security patches in 5.3.0-46.38 so I tried updating to the kernel from proposed i.e. 5.3.0-47.39. Sadly hangs returned within a couple minutes of trying to use the kernel. # cat /sys/class/drm/card0/error | head -2 GPU HANG: ecode 9:0:0x, hang on rcs0 Kernel: 5.3.0-47-generic x86_64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
The test kernel 5.3.0-48.41+lp1861395v1 seems to be a major improvement! On 5.3.0-45.37 pauses still happened rarely i.e. a single 2 second pause every 15 hrs and I hadn't noticed them until I was watching the logs for them. 5.3.0-46 and later were pausing several times a minute and the system was unusable. This test kernel 5.3.0-48.41+lp1861395v1 has yet to pause at all. I will keep testing it but I suspect we have a winner here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
I thought 5.3.0-48.41+lp1861395v1 fixed it for me. I haven't logged a hang for a very long time. Now out of the blue my audio stopped working altogether. I tried rebooting into 5.3.0-51.44 and I still don't have audio but I'm not hanging with that either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Just an FYI for those trying to figure out what the heck is going on. The fix related to this thread wasn't in 5.3.0-51.44. >From the changelog, which is hard to find, the fix was committed in >5.3.0-52.46 which is currently in eoan-proposed: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 (LP: #1872001) - drm/i915/execlists: Preempt-to-busy - drm/i915/gt: Detect if we miss WaIdleLiteRestore - drm/i915/execlists: Always force a context reload when rewinding RING_TAIL It is not recommended to run proposed kernels for production systems but it is possible to add them to systems which would otherwise be broken (like mine right now) using this repository: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed I had hoped since that also contained a bunch of audio fixes it might have fixed my inability to play sound but I haven't solved that one yet. I still have yet to see a hang on 5.3.0-52.46 either but again video playback with sound and heavy office document work seemed to trigger hangs for me so with no sound I could just be avoiding 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
The lack of kernel stability here is really getting frustrating With recent kernels audio playback over HDMI has stopped working for me altogether. I'm getting zero traction resolving it. I get audio playback when I plug in a headset but short cables are preventing use of that. Longer ones ordered but with pandemic ETA in weeks. I was able to get audio over Bluetooth working as a temporary work around but that was so unstable that it crashed my computer so badly I could not reboot. With the new 5.3.0-52.46 kernel I've seen both multiple crashes of blueman and kernel stack traces with kernels failing to the point of being unable to reboot once. No i915 hangs though ugh... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Here is the syslog content just before the hard crash on proposed 5.3.0-52 from which I could not reboot and finally had to hit my reset button. Please note this syslog extract contains a long string of UTF8 characters I had never seen before in a syslog just before the crash where I had to hit the reset button. I did not remove those. For lack of a better option, I'm still running it and BT audio has worked so far today.. ** Attachment added: "5.3.0-52 hard crash syslog excerpt." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+attachment/5365206/+files/syslog_hard_crash_bluetooth.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
To be clear 5.3.0-51 did NOT include the backported patches. Proposed 5.3.0-52.46 had some and 5.3.0-52.46+lp1861395v1 had more. Out of curiosity could the people who are still having hangs on the 5.3.0-52.46 proposed or 5.3.0-52.46+lp1861395v1 kernel have different generations of CPUs? I've got a Coffee Lake CPU and the patches seemed to do a better job of fixing issues for me. Perhaps we really have two different issues here. @pcworld we saw similar behaviour. What is your CPU model? Here is mine: # grep "model name" /proc/cpuinfo CPU model name : Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Hmm so patches were effective for: i5-8250U Kaby Lake R i.e. Gen 8 i9-9880H and i3-8100 both Coffee Lake Gen 9 It's hard enough debugging this directly on hardware. Doing it in a VM isn't going to be helpful. Which CPU models are still failing with 5.3.0-52.46 or 5.3.0-52.46+lp1861395v1? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
For me initially I saw it when working with large office documents and when attempting to do certain 1080p A/V playback. When it really got bad I couldn't use a browser as it was happening all the time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
I got about another 4 hrs before I had a 2nd hard crash with 5.3.0-52. I once again could not shutdown or reboot and was forced to hit my reset button. What a mess Basically BT audio works until the connection stops. Pausing an audio stream encourages the BT audio to unpair. The Audio sink still shows connected in Linux even though my DVD player shows it has unpaired. After that happens does it doesn't do that cleanly and causes a kernel panic when you attempt to reconnect the audio. Afterwards you cannot cleanup the broken audio sink or power off Bluetooth. Any kind of authentication seems to freeze the session. Things are very broken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
After it was pretty clear a stable kernel wasn't coming any time soon for 19.10 I gave up and took a dangerous leap. The only way I was going to get a 5.4 kernel was to move to 20.04. It was dangerous and I had to get there through a do-release-upgrade -d. Highly not recommended if you don't know what you are doing. I basically backed everything up and planned on things failing. I did it from the command line from multiple root shells launched ahead of time using screen in case X died. I had Virtualbox 6.1.6 installed before I went through my upgrade. It was not a clean upgrade as something as part of the upgrade process forced the uninstall of Virtualbox 6.1.6. I suspect it was because some of the dependencies of Virtualbox 6.1.6 only existed in Universe on focal Virtualbox 6.1.6 was uninstalled as part of the upgrade to 20.04. The upgrade actually blew up but I knew enough to recover. That blew a lot of things out of the water and was not listed on the upgrade screen or I would not have proceeded. I shutdown virtualbox and let it be temporarily uninstalled. Then I did a apt-get dist-upgrade and once that completed I tried to install Virtualbox 6.1.6 again but failed due to missing dependencies. I regretted doing an apt-get autoremove --purge just before hand. I had to manually download and install libqt5opengl5:amd64 for focal and then an apt-get install -f was able to fix python and in turn Virtualbox 6.1.6. Then once Virtualbox installed things worked again. After all the hell on 19.10 suddenly all my problems are gone. My NIC drivers still work thanks to the updated Intel e1000e 3.8.4 release DKMS package which Intel engineering kindly provided. That badly needs to be native to Ubuntu 20.04 as the kernel driver at least back on 5.3.0 didn't work for me. I have seen no i915 hangs with the kernel 5.4.0-28-generic. I haven't seen any flaky Bluetooth behavior that led to kernel panics but to be fair I didn't need to use Bluetooth audio sink on 20.04 as my HDMI audio pass-through works properly again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
I also had the issue on the 5.3.0-45 kernel but it happened once for 2 seconds every two days. It wasn't even noticeable unless you really looked for it. The 5.3 kernel series seems to be a total write off at this point. While it likely isn't allowed as a solution it might be less effort to back port the focal 5.4.0-28-generic kernel to eoan. I've been on that for several days. Since I upgraded to focal, I've seen no BT kernel panics, no issues with HDMI passthrough audio not working, no i915 hangs or any of the other issues I was seeing on the 5.3.0-x kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736743] Re: environment block not implemented on btrfs
This same issue bit me using 18.04. I think this should really be reclassified as an installer bug. Ubuntu has known for many releases that a single btrfs root partition does not work properly. The installer should warn people when they use a single partition that is btrfs that grub cannot write to it and you may want a separate ext4 /boot partition to avoid problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736743 Title: environment block not implemented on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/736743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1216187] [NEW] unity blocks saucy upgrade
Public bug reported: Upgrade failed from latest raring to saucy development. Success was expected. Fortunately it was done in a sandbox so no damage occured. "Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade: The package 'unity' is marked for removal but it is in the removal blacklist." ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.12 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Fri Aug 23 22:49:54 2013 InstallationDate: Installed on 2010-05-23 (1188 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/tcsh SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to raring on 2013-08-24 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1216187 Title: unity blocks saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1216187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460794] Re: boot fails if /dev/cgroup fstab entry is present
This shouldn't have been marked invalid. It has caused me and apparently others grief. It wouldn't be hard to have the upgrade tool check for uncommented cgroup lines, given they blow up an upgrade. I'm glad my experience and work around helped someone else who ran into the same things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460794 Title: boot fails if /dev/cgroup fstab entry is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1460794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460790] Re: 14.10 to 15.04 upgraded system with separate /usr fails to boot
Please note attempting to mitigate this by switching back to upstart failed as well. Doing so did make it so the system would boot past mounting /usr however for no obvious reason the system stopped automatically mounting the /var partition. With no network services running, the system would stop the boot process on a screen and complain /var hadn't mounted and prompt me to press m to enter emergency mode. Once I did that and logged in, /var was in fact not mounted and a mount -av would immediately mount it and then exiting emergency mode would cause a normal boot to complete. This should be a blocking issue for 16.04 as it will cause a lot of grief to end users when servers fail during upgrades. If I didn't have an IPMI remote console device I would have been really stuck. To be clear the only fix that worked was connecting using an IPMI remote console device, booting my server from a rescue iso, taring up each of my partitions with tar cpf and dumping them on a disk outside my raid array. I then wiped all the partitions off my main raid array and switched to a configurations where I had 1 primary boot, 1 primary swap and a root and home partition in a LVM physical volume. I then formated boot ext2, root btrfs and home xfs and extracted all the tars. I then follow a process similar to the one below to reinstall grub: https://help.ubuntu.com/community/Grub2/Installing#via_ChRoot At the end of the process, inside the chroot, I also did an: update-initramfs -u The result was a working system but was way way more effort than should have been required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460790 Title: 14.10 to 15.04 upgraded system with separate /usr fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1460790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460794] Re: systemd will not work with a separate /usr partition
Please note attempting to mitigate this by switching back to upstart failed as well. Doing so did make it so the system would boot past mounting /usr however for no obvious reason the system stopped automatically mounting the /var partition. With no network services running, the system would stop the boot process on a screen and complain /var hadn't mounted and prompt me to press m to enter emergency mode. Once I did that and logged in, /var was in fact not mounted and a mount -av would immediately mount it and then exiting emergency mode would cause a normal boot to complete. This should be a blocking issue for 16.04 as it will cause a lot of grief to end users when servers fail during upgrades. If I didn't have an IPMI remote console device I would have been really stuck. To be clear the only fix that worked was connecting using an IPMI remote console device, booting my server from a rescue iso, taring up each of my partitions with tar cpf and dumping them on a disk outside my raid array. I then wiped all the partitions off my main raid array and switched to a configurations where I had 1 primary boot, 1 primary swap and a root and home partition in a LVM physical volume. I then formated boot ext2, root btrfs and home xfs and extracted all the tars. I then follow a process similar to the one below to reinstall grub: https://help.ubuntu.com/community/Grub2/Installing#via_ChRoot At the end of the process, inside the chroot, I also did an: update-initramfs -u The result was a working system but was way way more effort than should have been required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460794 Title: systemd will not work with a separate /usr partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1460794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461340] [NEW] 2012 squirrelmail release incompatible with php 5.6.
Public bug reported: The version of squirrelmail in universe is ancient i.e. from 2012. Ubuntu 15.04 now ships with php 5.6 which has verify_peer on my default. That is a good idea if you can actually configure it. This version of squirrelmail does not support configuring your TLS connections and expects verify_peer to be off. This means no matter what you do all your SMTPS and IMAPS connections will always fail because the certificate verification will always fail. Most likely due to not having CA certificate(s) configured for the verification. To be clear this version of squirrelmail does not support CA certificate configuration. Upstream this is fixed in the Stable version snapshots. Please upgrade this package to the latest Stable version snapshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: squirrelmail 2:1.4.23~svn20120406-2 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 Date: Tue Jun 2 20:51:09 2015 InstallationDate: Installed on 2010-05-23 (1836 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/tcsh SourcePackage: squirrelmail UpgradeStatus: Upgraded to vivid on 2015-06-01 (1 days ago) ** Affects: squirrelmail (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461340 Title: 2012 squirrelmail release incompatible with php 5.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squirrelmail/+bug/1461340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461340] Re: 2012 squirrelmail release incompatible with php 5.6.
Please note I had to upgrade to the 1.5.2 series in order to get a working system on Ubuntu 15.04. I have packaged this and put an upgraded package in my PPA: ppa:rhardy/webconsrp The new package works for me. I went for a fresh config file on the new version but that is optional. The package is based on the original package for vivid but was upgraded to handle the new release. I have never figured out how to actually get that "published" so it shows in Universe. If the original maintainer knows how feel free to either take the packages or the patches there in which I had to port so they applied to the 1.5.2 series. There were also packaging changes to handle the new css and templates directories which are new in 1.5.2. The package still recommends squirrelmail-viewashtml but will actually remove that when it is installed. The squirrelmail 1.5.2 seems to have that built in now. I'll find where that recommend is coming from at some later point... Please note you must have a working certificate verification chain for the package to work. To get this I had to ensure /etc/ssl/certs had the full certificate chain and then ran a c_rehash in that directory. Ultimately openssl must be able to cleanly connect for the rest to work. I found this helpful for debugging: openssl s_client -CApath /etc/ssl/certs -connect : If you have it configured properly you should see "Verify return code: 0 (ok)" near the end of the output, if not add certificates and c_rehash until you do. To make the php and squirrelmail use that working certificate validation chain I did two things: 1. I configured openssl.capath in /etc/php5/apache2/php.ini 2. I created a /etc/squirrelmail/config_local.php. See config_local.example.php for hints. I used capath instead of cafile. You may be able to get away with only one of those but I did both and it works for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1461340 Title: 2012 squirrelmail release incompatible with php 5.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squirrelmail/+bug/1461340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1460790] Re: 14.10 to 15.04 upgraded system with separate /usr fails to boot
*** This bug is a duplicate of bug 1460794 *** https://bugs.launchpad.net/bugs/1460794 On 2015-06-10 09:00, Martin Pitt wrote: > *** This bug is a duplicate of bug 1460794 *** > https://bugs.launchpad.net/bugs/1460794 > > ** This bug has been marked a duplicate of bug 1460794 > systemd does not boot with a separate /usr partition > This most assured is NOT a duplicate of bug 1460794. That bug is not even for the same package! I was told by people in the #ubuntu-server chat room on Freenode to file these two bugs. I think it was sarnold but I no longer have the logs... Regards, Rob -- -"Happiness is understanding."------ Robert Hardy, B.Eng Computer Systems C.I.O. Webcon Inc. rhardy webcon caGPG Key available (613) 276-7327 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460790 Title: 14.10 to 15.04 upgraded system with separate /usr fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1460790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1460794] Re: systemd will not work with a separate /usr partition
On 2015-06-10 08:59, Martin Pitt wrote: > The "/usr appears to be on its own filesystem ..." is just a warning. > Booting with separate /usr is supported, as long as it's a local > partition and not a remote one (the latter could work, but really nobody > tests this). I just did a 15.04 installation with separate /usr, and it > works fine. > > Could there be something wrong with your /etc/fstab perhaps? Maybe some > UUID mismatch or so? In the emergency shell, can you please do > >journalctl -b > /root/journal.txt >blkid > /root/blkid.txt > > and attach /etc/fstab, /root/blkid.txt, and /root/journal.txt here? > Thanks! > > ** Summary changed: > > - systemd will not work with a separate /usr partition > + systemd does not boot with a separate /usr partition > > ** Changed in: systemd (Ubuntu) > Status: New => Incomplete > I've been working with Linux for 20 years, I really doubt there was anything wrong with my fstab. The system configuration had been working perfectly since it was installed using Ubuntu 10.04 several years ago. The upgrade from 14.04 to 14.10 worked fine. It was the 14.10 to 15.05 upgrade that blew up. It was not just a warning. The system and emergency mode were both unusable until I switched back to upstart. Even after the switch to upstart the 15.04 system would only boot only with manual intervention on the console during every boot as /var stopped being automatically mounted. The system sat there with an error not booting until I manually did a mount -av from emergency mode and then continued the boot process. This happened on each and every boot. In my honest opinion to test this properly you would have to test a system which had been upgraded from 14.04 with a similar layout with separate ext4 partitions. You might get away with starting at 14.10... This was a total system failure on a production server over ten days ago. I couldn't just leave it failed state for two weeks. The journalctl and blkid commands would only show the current system state after all was rebuilt, where everything is working fine. Do you still want them? As I indicated previously in my comments I was forced to wipe all my partitions from a rescue disk and switch to a boot, root, home partition layout abandoning my previous system layout. I then restored from backups. I was able to restore my old /etc/fstab from a backup. Before the upgrade it was as follows: # /etc/fstab: static file system information. # # Use 'blkid -o value -s UUID' to print the universally unique identifier # for a device; this may be used with UUID= as a more robust way to name # devices that works even if disks are added and removed. See fstab(5). # # proc/proc procnodev,noexec,nosuid 0 0 # / was on /dev/sda1 during installation UUID=676235cd-93b1-426e-8336-fa0078d96145 / ext4errors=remount-ro 0 1 /dev/mapper/Guru2VG1-home /home xfs defaults0 2 /dev/mapper/Guru2VG1-tmp /tmpext4 defaults0 2 /dev/mapper/Guru2VG1-usr /usrext4 defaults0 2 /dev/mapper/Guru2VG1-var /varext4 defaults0 2 cgroup /dev/cgroup cgroup defaults0 0 # swap was on /dev/sda2 during installation UUID=217f140d-f4ad-45a3-9486-9e3af1734f0d none swapsw 0 0 UUID=3a482248-399d-4fbd-aa1d-e013343b44e5 /mnt/backups xfsdefaults 0 0 UUID=99649f74-7be3-427a-9eef-65a1b2922196 /mnt/tmp xfs defaults 0 0 All a journalctl -b would gather now would be the boot log data 9 days after this was all fixed. The log only goes back 3 days. The blkid would capture uuids for the new partitions. Do you still want those? Perhaps other logs would be more helpful? I do have nightly backups. Regards, Robert Hardy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460794 Title: systemd does not boot with a separate /usr partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1460794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460794] Re: systemd does not boot with a separate /usr partition
I dug into this more on the server that failed to upgrade properly to see if the server would work properly after switching back to systemd. Please recall this was after a backup and restore with a much simpler partitioning scheme. It still would not boot. I ended up finding this line in my fstab: cgroup/dev/cgroup cgroup defaults 0 0 This was not a line I added. I believe it may be a remenant from an old release which the upgrader did not comment out. The server began its life with Ubuntu 10.04. Once I commented that cgroup line out the system booted with systemd in place. Since I doubt this will ever get to a complete state please close the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460794 Title: systemd does not boot with a separate /usr partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1460794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1460794] Re: systemd does not boot with a separate /usr partition
I am not convinced that the cgroup issue was the only issue here, but since this is a single physical I can't easily go back in time to test further. Either way the changed summary is backwards. Once repartitioning was completed systemd fails to boot if the /dev/cgroup fstab entry IS present. The one obvious thing we have is a case where do-release-upgrade should have removed the /dev/cgroup fstab entry and did not. A better summary might be something like: + boot fails with systemd when /dev/cgroup fstab entry is present On Thu, July 2, 2015 2:44 am, Martin Pitt wrote: >> cgroup /dev/cgroup cgroup defaults 0 0 > > Erk -- that's what broke the boot after all? Indeed, this was in comment > 4 already, but I missed that. So the journal should have a > complaint/timeout on that, as /dev/cgroup is a thing of the distant past > (google still has a few hits). Thanks for finding! > > > I'm going to poke around in 10.04's and 12.04's packages to see which > one would possibly have added that fstab line. > > ** Summary changed: > > > - systemd does not boot with a separate /usr partition > + boot fails on missing /dev/cgroup fstab entry > > > ** Changed in: systemd (Ubuntu) > Status: Incomplete => Confirmed > > > -- > You received this bug notification because you are subscribed to the bug > report. https://bugs.launchpad.net/bugs/1460794 > > > Title: > boot fails on missing /dev/cgroup fstab entry > > Status in systemd package in Ubuntu: > Confirmed > > > Bug description: > I recently upgraded a server from 14.10 to 15.04. The upgrade claim to > have worked but the system could not boot afterwards. > > Basically when you attempt to reboot you end up at an emergency > maintenance prompt early in the boot process. After a lot of digging one > of the messages in the logs gives: systemd[1]: /usr appears to be on its > own filesystem and is not already mounted. This is not a supported setup. > Some things will probably break (sometimes even silently) in mysterious > ways. Consult > http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken > > > Basically systemd cannot deal with /usr being on a separate partition. > That needs to be fixed or systemd should not be used for upgrades with > a separate /usr partition. > > This is related to bug 1460790 but asking for systemd to actually be > fixed. Please see bug 1460790 if you are looking for a work around on this > issue. > > ProblemType: Bug > DistroRelease: Ubuntu 15.04 > Package: systemd 219-7ubuntu5 > ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 > Uname: Linux 3.19.0-18-generic x86_64 > ApportVersion: 2.17.2-0ubuntu1.1 > Architecture: amd64 > Date: Mon Jun 1 15:29:32 2015 > InstallationDate: Installed on 2010-05-23 (1835 days ago) > InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 > (20100427) > MachineType: Supermicro X8STi > ProcEnviron: > TERM=xterm > PATH=(custom, no user) > XDG_RUNTIME_DIR= > LANG=en_CA.UTF-8 > SHELL=/bin/tcsh > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic > root=UUID=676235cd-93b1-426e-8336-fa0078d96145 ro quiet acpi=off > pci=noacpi SourcePackage: systemd > UpgradeStatus: Upgraded to vivid on 2015-06-01 (0 days ago) > dmi.bios.date: 09/17/10 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 2.0 > dmi.board.asset.tag: To Be Filled By O.E.M. > dmi.board.name: X8STi > dmi.board.vendor: Supermicro > dmi.board.version: 1234567890 > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: Supermicro > dmi.chassis.version: 1234567890 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd09/17/10:svnSupermicro:pnX8STi:pvr > 1234567890:rvnSupermicro:rnX8STi:rvr1234567890:cvnSupermicro:ct3:cvr12345 > 67890: > dmi.product.name: X8STi > dmi.product.version: 1234567890 > dmi.sys.vendor: Supermicro > > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1460794/+subscripti > ons > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460794 Title: boot fails on missing /dev/cgroup fstab entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1460794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460790] [NEW] 14.10 to 15.04 upgraded system with separate /usr fails to boot
Public bug reported: One of my servers has a separate partition for /usr partition. I recently tried to upgrade my server from 14.04 to 14.10 and then 15.04. The first upgrade went well. The 2nd from 14.10 to 15.04 "succeeded" with no obvious issues until you reboot. Unfortunately what actually happened was a total fail. The result was a system which simply cannot boot. Basically when you attempt to reboot you end up at an emergency maintenance prompt early in the boot process. After a lot of digging one of the messages in the logs gives: systemd[1]: /usr appears to be on its own filesystem and is not already mounted. This is not a supported setup. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken This leaves users with two options: 1. Connect to IPMI. Boot with a rescue CD and repartition and move software around so you no longer have a separate /usr. This is incredibly PAINFUL! 2. Switch back to upstart see: https://wiki.ubuntu.com/SystemdForUpstartUsers#Permanent_switch_back_to_upstart In my opinion do-release-upgrade should do one of: 1. Check if /usr is on a separate partition before starting the actual upgrade. Display a big warning to user before proceeding. 2. Check if /usr is on a separate partition and automatically switch to upstart if it is. I will file a separate bug in an attempt to get systemd fixed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-release-upgrader-core 1:15.04.14 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CrashDB: ubuntu Date: Mon Jun 1 14:55:57 2015 InstallationDate: Installed on 2010-05-23 (1835 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/tcsh SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to vivid on 2015-06-01 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460790 Title: 14.10 to 15.04 upgraded system with separate /usr fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1460790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460794] [NEW] systemd will not work with a separate /usr partition
Public bug reported: I recently upgraded a server from 14.10 to 15.04. The upgrade claim to have worked but the system could not boot afterwards. Basically when you attempt to reboot you end up at an emergency maintenance prompt early in the boot process. After a lot of digging one of the messages in the logs gives: systemd[1]: /usr appears to be on its own filesystem and is not already mounted. This is not a supported setup. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken Basically systemd cannot deal with /usr being on a separate partition. That needs to be fixed or systemd should not be used for upgrades with a separate /usr partition. This is related to bug 1460790 but asking for systemd to actually be fixed. Please see bug 1460790 if you are looking for a work around on this issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 Date: Mon Jun 1 15:29:32 2015 InstallationDate: Installed on 2010-05-23 (1835 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MachineType: Supermicro X8STi ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/tcsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=676235cd-93b1-426e-8336-fa0078d96145 ro quiet acpi=off pci=noacpi SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-06-01 (0 days ago) dmi.bios.date: 09/17/10 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: X8STi dmi.board.vendor: Supermicro dmi.board.version: 1234567890 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Supermicro dmi.chassis.version: 1234567890 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd09/17/10:svnSupermicro:pnX8STi:pvr1234567890:rvnSupermicro:rnX8STi:rvr1234567890:cvnSupermicro:ct3:cvr1234567890: dmi.product.name: X8STi dmi.product.version: 1234567890 dmi.sys.vendor: Supermicro ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460794 Title: systemd will not work with a separate /usr partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1460794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1216187] Re: unity blocks saucy upgrade
I started from a server install of 10.04 on which I added Xubuntu. Unity must have gotten picked up along the upgrade path. Rob --- Original message --- > From: Brian Murray > To: rha...@webcon.ca > Sent: 2013-08-27, 16:41 > > I believe this is because you've installed unity on a Xubuntu system, > and then during the upgrade process unity is selected for removal but it > is on the blacklist so the upgrade fails. > > ** Changed in: ubuntu-release-upgrader (Ubuntu) >Importance: Undecided => Low > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1216187 Title: unity blocks saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1216187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529402] [NEW] 15.04 Upgrade crash results in powered off server
Public bug reported: I attempted to upgrade a small home server that serves my parents from 15.04 to 15.10 to remain supported. The first attempt at this resulted in a crash and power off in roughly the last 20% of the upgrade. The system is a desktop but it does have a good AVR capable UPS protecting it.. Thanks to btrfs I was able to recover and was able to revert my root to the snapshot before the upgrade and restore the system. I then attempted to cleanup the mess by removing the @badroot. I found I could not delete it as btrfs kept insisting an empty directory had files in it. Running brtfsck --repair from a rescue disk saw nothing wrong with the file system. Some btrfs developers told me this is already fixed in 4.3. It was unclear if that was the kernel, btrfs tools or both. I was eventually forced to wipe and reformat my root and restore a full tar ball backup I had. That worked and got me up and running on a root file system free of corruption. I then tried a do-release-upgrade again, the results of which are this bug report. I was doing the upgrade over ssh from remote. The upgrade was running fine until it got to around 85%. The text at the end of the attached file 20151223ThorFail.txt is the last that appeared on the console. Shortly after that appeared the system went unreachable and the next day when I arrived to debug I again found the system powered down with a corrupt and un-bootable root. My parents had not touched it. From a rescue USB I moved the borked root file system to @_failed_upgrade and reverted to the pre-upgrade snapshot. Please note I still have the borked root file system as a snapshot and the system in the pre-upgrade state. There should be something useful in that failed snapshot but I'm not seeing it. What was logged on the console did not really help me figure why the upgrade was failing. Would someone please give me some pointers on how I can debug this further? I really don't want to fully reinstall the server from scratch... ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-release-upgrader-core 1:15.04.14.3 ProcVersionSignature: Ubuntu 3.19.0-42.48-generic 3.19.8-ckt10 Uname: Linux 3.19.0-42-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CrashDB: ubuntu Date: Sat Dec 26 14:40:53 2015 InstallationDate: Installed on 2012-12-22 (1099 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to vivid on 2015-12-23 (3 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade vivid ** Attachment added: "Key text captured from remote during failed upgrade." https://bugs.launchpad.net/bugs/1529402/+attachment/4540602/+files/20151223ThorFail.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529402 Title: 15.04 Upgrade crash results in powered off server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1529402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529402] Re: 15.04 Upgrade crash results in powered off server
Please note the automatic captured data was on the server pre-upgrade 15.04. I did not think ubuntu-bug would run on the corrupted snapshot if I chrooted so I didn't try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529402 Title: 15.04 Upgrade crash results in powered off server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1529402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529402] Re: 15.04 Upgrade crash results in powered off server
No one has any suggestions? This server 15.04 and is either already end of life or going end of life this month. I would really like to keep it supported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529402 Title: 15.04 Upgrade crash results in powered off server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1529402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 594827] Re: broken bmc-watchdog init script/logrotate config
I've rebuilt a deb suitable for inclusion in Universe which fixes this bug. If anyone copied here has an idea how to actually make that happen, please let me know. My freeipmi_0.7.15-2ubuntu4.dsc based packages are currently in my ppa:rhardy/webconsrp here: https://launchpad.net/~rhardy/+archive/webconsrp/+packages You can read the change log for the details, but in summary here are the fixes: 1. Fix configuration file naming in a way which minimal carnage will ensue. i.e. Use freeipmi-bmc-watchdog everywhere. Depending on how people hacked things to make the old deb work. This will either pick up their existing configuration options or turn the watchdog off with the default config. 2. Adapt Jamie Jamison's upstart script and package, replacing the broken init.d based script. 3. Correct the logrotate script to use copytruncate. Watchdogs really shouldn't be interrupted for simple logrotation. This also fixes the error with the logrotate script trying to do a condrestart when the init.d script didn't support this. 4. Make sure the watchdog doesn't run by default until it is configured (this wasn't handled by Jamie's upstart script.) 5. Quilt all the patches so others can follow what I did. Note the upstart script avoids the bmc-watchdog bugs related to quietly dying at start up by using "bmc-watchdog --clear" in two places. These are fixed in freeipmi 1.0.2 but my backporting the fixes caused more issues so my most recent 0.7.15-2ubuntu4 package uses the --clear work around instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/594827 Title: broken bmc-watchdog init script/logrotate config -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692691] Re: update-grub thinks my kernel is a xen one
This regression also affects lucid and is blocking use of kernels in lucid updates such as linux-image-2.6.38-10-virtual. Natty's fixed grub rebuilds fine without changes under lucid without issue. Please fast track the fix in updates for lucid as well. I've put the rebuild in my PPA for now. FYI it won't be tested in production until Launchpad.net catches up. Currently a 2 hr delay... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692691 Title: update-grub thinks my kernel is a xen one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/692691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523311] Re: pbzip2 should be able to replace bzip2
My PPA has a build of pbzip2-1.15-0ubuntu1 with a few of the addons which bzip2 has. ex. bzdiff as pbzdiff etc. If pbzip2 is an alternative it probably should be in /bin not /usr/bin. My package made that change too. Still missing are: bzip2recover, bzexe and bzcat. But at least it is a start. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/523311 Title: pbzip2 should be able to replace bzip2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pbzip2/+bug/523311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768360] Re: double welcome banner in ubuntu server
I started seeing this too around April 18th @ 11:08 on all my 10.04 Ubuntu servers. I eventually found a static copy of my motd, which was never getting updated in /etc/motd.tail. I have no idea what put that there, but given it happened on all my servers it must have been a package update and yet looking at the dates in /var/lib/dpkg/info none of the packages which touch /etc/update- motd.d/* have changed recently. Some of the servers only I have access to, so this is very odd... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768360 Title: double welcome banner in ubuntu server -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607838] Re: 3w-sas driver
Note: for dkms to work reliably you must do this: echo 3w-sas >> /etc/initramfs-tools/modules I'm not sure what happened but starting with 2.6.32-25-server dkms now refuses to install the 3w-sas.ko module anywhere except /lib/modules/2.6.32-*-server/updates/dkms/3w-sas.ko, despite my dkms.conf explicitedly telling it to put the module in /lib/modules/2.6.32-*server/kernel/drivers/scsi/3w-sas.ko. If it doesn't put it in the latter update-initramfs ignores it and that system fails to boot the next reboot into a new initramfs... VERY annoying when your recovery disks don't have the raid driver... If you update /etc /initramfs-tools/modules as above it see the file in /lib/modules/2.6.32-*-server/update/dkms/. This issue is a huge pain in the behind. I really which Ubuntu would include the stable 3w-sas driver in it's kernels. I would be happy to upgrade to Maverick and its kernels to get built in support, but for some inexplicable reason the driver is not built standard there either. -- 3w-sas driver https://bugs.launchpad.net/bugs/607838 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607838] Re: 3w-sas driver
The simplest way of dealing with this right now, and it is far from painless, is to grab the 3w-sas-2.6.32.tgz src driver from 3ware/lsi and use dkms to manage it. It took me a while to find this. The rough process for Lucid goes: apt-get install dkms mkdir -p /tmp/foo; cd /tmp/foo; tar xzvpf 3w-sas-2.6.32; mv drivers/* /usr/src/3w-sas-2.6.32/ Then put the attached dkms.conf in /usr/src/3w-sas-2.6.32/dkms.conf N.B. Obviously if you are building for something other than 2.6.32-24-server you update the -k arguments below appropriately. You then add the source with: dkms add -m 3w-sas -v 2.6.32 You can then build it with: dkms build -m 3w-sas -v 2.6.32 -k 2.6.32-24-server Check the build status with: dkms status Install it with: dkms install -m 3w-sas -v 2.6.32 -k 2.6.32-24-server -- 3w-sas driver https://bugs.launchpad.net/bugs/607838 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607838] Re: 3w-sas driver
Here is the dkms.conf referenced in my previous comment. ** Attachment added: "dkms.conf" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/607838/+attachment/1501492/+files/dkms.conf -- 3w-sas driver https://bugs.launchpad.net/bugs/607838 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 594827] [NEW] broken bmc-watchdog init script/logrotate config
Public bug reported: Description:Ubuntu 10.04 LTS Release:10.04 freeipmi-bmc-watchdog: Installed: 0.7.15-2 Candidate: 0.7.15-2 Version table: *** 0.7.15-2 0 500 http://ca.archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status The init scripts provided with the package above are not LSB compliant and fail to properly startup/shutdown the daemon in various ways. During testing, in some cases the old script completely refused to start the daemon even after a cold boot. The old script was not PID aware and was not using PIDFILEs. In some cases, the daemon would be shutdown but not properly, causing eventual unexpected hard resets etc... The logrotate configuration has an invalid path for the restart script and even then executes it with an unsupported condrestart. Please find attached a rewritten init script based on Ubuntu 10.04 /etc/init.d/skeleton and hopefully LSB best practices. All code paths in this init work properly for me and it has none of the cludges in the old init script. Please also find attached a diff for the logwatch config. Both files are in a tar because it seems attaching two files to this bug report isn't an option. ** Affects: freeipmi (Ubuntu) Importance: Undecided Status: New ** Affects: freeipmi (Debian) Importance: Undecided Status: New ** Tags: bmc-watchdog freeipmi initscript logrotate -- broken bmc-watchdog init script/logrotate config https://bugs.launchpad.net/bugs/594827 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 594827] Re: broken bmc-watchdog init script/logrotate config
** Patch added: "tgz with new init script and logrotate patch" http://launchpadlibrarian.net/50396383/freeipmi-bmc-watchdog_logrotate_init_fixes.tar.gz -- broken bmc-watchdog init script/logrotate config https://bugs.launchpad.net/bugs/594827 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 594827] Re: broken bmc-watchdog init script/logrotate config
** Also affects: freeipmi (Debian) Importance: Undecided Status: New -- broken bmc-watchdog init script/logrotate config https://bugs.launchpad.net/bugs/594827 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763648] Re: [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04
This is truly sad when a vendor that built it's business on having good drivers has fallen so far to deprecate a perfectly good workstation/server grade video card in my server because they won't release updates. I really need this fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763648 Title: [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1763648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
