Well that was really painful to find. After hours of bisecting and
building kernel manually I've found it: Kernel (and Ubuntu Devs) enabled
Intel IOMMU by default:
* https://github.com/torvalds/linux/commit/792fb43ce2c9
* https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951440
Ubuntu Devs we
6.6.0 -> Works
6.6.12 -> Works
6.6.15 -> Works
6.6.17 -> Works
6.6.18 -> Works
6.6.19 -> Broken
6.6.25 -> Broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060709
Title:
Kernel 6.8 and Gigabyte
@romwriter: This works out fine for me:
```
$ lspci | grep SATA
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family
6-port SATA Controller 1 [AHCI mode] (rev 05)
04:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2
4-port SATA 6 Gb/s RAID Control
Further tests showed, that it seems to be related to the Marvell
88SE9230 SATA chip my board is using. Connecting the disk to the second
SATA chip available on the board, the OS boots up properly. Sadly this
isn't an option for operating the system because those ports are
normally used for my stora
Further testing with mainline kernel:
5.19.17 -> Works
6.2.0 -> Works
6.5.13 -> Works, but already seeing a LOT of strange ata log messages in dmesg.
See attached dmesg log.
** Attachment added: "dmesg-6.5.0-060500-generic.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060709/+at
Seeing similar issues on my Gigabyte Z87X-UD5H with a Samsung 840 SSD.
Booting worked fine for years with same hardware. Upgrading to 24.04 and
Kernel 6.8.0 ends in broken boot state. My current workaround is to boot
the old 5.15 kernel. Using 6.8.6 mainline didn't work for me.
** Attachment added
Can confirm that this has been fixed with 5.15.0.122 on Ubuntu 22.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076576
Title:
5.15.0-118: NFS causes suspend to fail
To manage notifications abo
I can confirm hat this fixes the mentioned issue. Thanks for your quick
responds!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763414
Title:
ruby 1.9.3.484-2ubuntu1.8 throws gem warning
To manage
Hi Christian,
no this didn't happen with 1.9.3.484-2ubuntu1.7:
(Forgive me the ugly installation method, i had to get those packages
from our snapshotted mirror)
root@mbaur-gem-test:~# dpkg -i ruby_1.9.3.4_all.deb
ruby1.9.1_1.9.3.484-2ubuntu1.7_amd64.deb
libruby1.9.1_1.9.3.484-2ubuntu1.7_amd64
Public bug reported:
After upgrading the ruby1.9.1 package to 1.9.3.484-2ubuntu1.8 gem throws
the following warning:
root@mbaur-gems-test:/# gem list
YAML safe loading is not available. Please upgrade psych to a version that
supports safe loading (>= 2.0).
*** LOCAL GEMS ***
root@mbaur-gems-t
Any change this gets fixed soon?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634613
Title:
mysqltuner looks for old 'password' field, not 'authentication_string'
To manage notifications about th
Seriously? This bug was reported 2013-10-30 and a proper fixes was
suggested on 2014-05-29. How the fuck is it possible that this bug still
exists?!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/124624
I'm running php5-apcu (4.0.7-1build1~ubuntu14.04.1) since the 13.03.2013
without any problems. It fixed the issues i had with 4.0.2-2build1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374892
Title:
Same here on Ubuntu 14.04 on Firefox 38.08. Works on Chromium
41.0.2272.76, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413665
Title:
Bad Request - Bad bot, go away! Request aborted.
To
Which kernel has a fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308674
Title:
[Lenovo ThinkPad X220] kernel 3.13 i915 brightness settings broken
when going from docked -> undocked
To manag
I'm so sorry, i didn't get to it and now traveling the world for a year
without my docking station. Hope someone else finds the time to bisect
this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I think this might be fixed with Ubuntu 14.04. At least the
"/etc/xdg/autostart/clipit-startup.desktop" now contains
"OnlyShowIn=GNOME;XFCE;LXDE;Unity;" as mention by yannubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Will do, but i guess not before the weekend. Tonight i've did some easy
debugging by just installing some old version (3.14-3.16) of the mainline
kernel. It showed, that the actual bug (not being able to adjust the brightness
level after undocking) is fixed in those versions as well, but there i
Awesome, it works perfectly with 3.17. Since 14.10 will have 3.16 as
kernel, when will it be available for Ubuntu?
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/13
Public bug reported:
When undocking my Thinkpad T30s from my dockingstation, the brightness
is set to the lowest level and can't be changed.
Workaround:
- Dock/Undock again. After the second undocking the brightness level can be
changed. Rule of thumb: Every uneven undocking won't work.
- Reboot
I can also confirm this for a Lenovo ThinkPad T430s with Lenovo ThinkPad
Mini Dock Plus Series 3.
OS: Ubuntu 14.04.1
Kernel: Linux ThinkPad 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member
Public bug reported:
Bug: SSH public key isn't created in vagrant cloud images
Reproduction:
- Download:
http://cloud-images.ubuntu.com/vagrant/raring/current/raring-server-cloudimg-amd64-vagrant-disk1.box
- Start with vagrant or manual with VirtualBox
- Look into /etc/ssh
Environment:
- Ubuntu
22 matches
Mail list logo
