Re: [Bug 221499] Re: RTL8111/8168B does not work in Hardy
2008/7/28 Stefan Bader <[EMAIL PROTECTED]>: > Something to try: pci=nomsi as a boot option > > This might be a case where the card/bus claim to be able to use msi but > fail to do in reality. > Eventually an help from a dev! (sorry Kjell, but I don't think your playing with launchpad helped in solving this soon) So I was correct in observing strangeness with that "PCI-MSI-edge" and that suspicious IRQ in my logs. Unless ubuntu 7.10 and 8.10 ship with "pci=nomsi" by default, and I don't think so, there's a regression somewhere, maybe not in the r8169 module code. Is there any way we, users, can help with dealing of this regression? -- RTL8111/8168B does not work in Hardy https://bugs.launchpad.net/bugs/221499 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 225175] Re: S-ATA Hard drives swapped
No reactions from grub maintaner(s) or the the installer team? Are the right people already notified of this bug? -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 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 221499] Re: RTL8111/8168B does not work in Hardy
> Using pci=nomsi is not a real solution. Agreeed. Following are output of the commands you pointed. -- RTL8111/8168B does not work in Hardy https://bugs.launchpad.net/bugs/221499 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 221499] Re: RTL8111/8168B does not work in Hardy
** Attachment added: "lspci -t" http://launchpadlibrarian.net/16378383/lspci-t -- RTL8111/8168B does not work in Hardy https://bugs.launchpad.net/bugs/221499 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 221499] Re: RTL8111/8168B does not work in Hardy
** Attachment added: "sudo dmidecode" http://launchpadlibrarian.net/16378379/dmidecode -- RTL8111/8168B does not work in Hardy https://bugs.launchpad.net/bugs/221499 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 221499] Re: RTL8111/8168B does not work in Hardy
** Attachment added: "sudo lspci -vvnn" http://launchpadlibrarian.net/16378388/lspci-vvnn -- RTL8111/8168B does not work in Hardy https://bugs.launchpad.net/bugs/221499 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
Re: [Bug 221499] Re: RTL8111/8168B does not work in Hardy
2008/7/29 Stefan Bader <[EMAIL PROTECTED]>: > Thank you Francesco. Just to be bullet proof, your network works with the > nomsi option but not without. works with pci=nomsi, don't works without > The problem seems to be either the device (or some versions of that) or the > board which indicate with their capabilities to support this, have some flaws. IMHO, this is a regression since: - Ubuntu 7.10 works (kernel 2.6.22); - Gentoo 2008.1 works (kernel 2.6.24); - Ubuntu 8.10 alpha 3 works (kernel 2.6.26). Don't know the component which could be broken as I dunno who is responsible of detecting MSI capable cards. -- RTL8111/8168B does not work in Hardy https://bugs.launchpad.net/bugs/221499 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 336125] Re: Broken audio playback with Intel 82801G (Realtek ALC883) on 9.04
** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed -- Broken audio playback with Intel 82801G (Realtek ALC883) on 9.04 https://bugs.launchpad.net/bugs/336125 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 336125] Re: Broken audio playback with Intel 82801G (Realtek ALC883) on 9.04
** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- Broken audio playback with Intel 82801G (Realtek ALC883) on 9.04 https://bugs.launchpad.net/bugs/336125 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 336125] Re: Broken audio playback with Intel 82801G (Realtek ALC883) on 9.04
I don't know what happened but today my audio card emitted first sounds using 2.6.28-11.15 kernel. What I did in this days is: - playing with mixer while using 2.6.27-9 (that has always worked, as I stated); - updating the packages; - launching the existing ubuntu installation within a virtualbox environment using createrawvmdk directive. I launched alsa-info.sh script again and here is the result: http://www.alsa- project.org/db/?f=19debdecbb1e8e788b2d574abdeaa66ce14a7c52 I've attached the diff with the previous report. Many things are changed: yeah, it seems after all it was mixer related. However, I'm almost sure before commenting this bug report there were no channels muted (I tried alsamixer -c 0 and alsamixer -Dhw:0 without seeing anything strange). I have some suspect something really changed with updates. Dunno if the problem reported by the bug author is the same, however I advice him to do a clean install (my one was an upgrade). For security, I've marked the bug invalid/incomplete. I'm happy now. Bye ** Attachment added: "diff -u alsa-info.before alsa-info.later" http://launchpadlibrarian.net/26684695/alsa-info_diff_before_later -- Broken audio playback with Intel 82801G (Realtek ALC883) on 9.04 https://bugs.launchpad.net/bugs/336125 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 336125] Re: Broken audio playback with Intel 82801G (Realtek ALC883) on 9.04
The following in the diff file makes me thinking something is changed within ubuntu packages: one control is disappeared from the sound card! Anyway, all is ok now. Maybe it has been fixed somewhere. @@ -523,7 +523,7 @@ List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC883 Analog [ALC883 Analog] - Subdevices: 0/1 + Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 1: ALC883 Digital [ALC883 Digital] Subdevices: 1/1 @@ -547,8 +547,8 @@ Card hw:0 'Intel'/'HDA Intel at 0xf050 irq 22' Mixer name : 'Realtek ALC883' Components : 'HDA:10ec0883,10250090,0012 HDA:14f12bfa,1025007f,0009' - Controls : 23 - Simple ctrls : 14 + Controls : 22 + Simple ctrls : 13 Simple mixer control 'Master',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono -- Broken audio playback with Intel 82801G (Realtek ALC883) on 9.04 https://bugs.launchpad.net/bugs/336125 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 336125] Re: Broken audio playback with Intel 82801G on 9.04
As a workaround, download and install the following packages from ubuntu 8.10: http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-image-2.6.27-9-generic_2.6.27-9.19_i386.deb http://security.ubuntu.com/ubuntu/pool/restricted/l/linux-restricted-modules/linux-restricted-modules-2.6.27-9-generic_2.6.27-9.13_i386.deb http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-headers-2.6.27-9_2.6.27-9.19_all.deb http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-headers-2.6.27-9-generic_2.6.27-9.19_i386.deb Is there interest in this bug? Thanks ** Summary changed: - Broken audio playback with Intel 82801G on 9.04 + Broken audio playback with Intel 82801G (Realtek ALC883) on 9.04 -- Broken audio playback with Intel 82801G (Realtek ALC883) on 9.04 https://bugs.launchpad.net/bugs/336125 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 336125] Re: Broken audio playback with Intel 82801G on 9.04
Confirmed. Audio is completely broken. My system is a notebook Acer Aspire 5684WLMi. Here is the alsa-info.sh output: http://www.alsa- project.org/db/?f=776a3369f719f46219fc044ccab3b6f4ec9bd070 Attached is my dmesg. Please ask for other debug info. ** Attachment added: "dmesg-Acer_Aspire_5684WLMi" http://launchpadlibrarian.net/25926203/dmesg-Acer_Aspire_5684WLMi ** Also affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- Broken audio playback with Intel 82801G on 9.04 https://bugs.launchpad.net/bugs/336125 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 336125] Re: Broken audio playback with Intel 82801G on 9.04
To be more precise: Audio PLAYBACK is completely broken: no way to produce a sound in my system. Not that I have tested capture, tough. Mixer settings seems all ok, but you can verify this on the alsa-info.sh output. IMPORTANT: this is almost for sure kernel related as the old kernel 2.6.27-9.5 from ubuntu 8.10 DOES work and can be considered the last working kernel. I remember the regression started with kernel 2.6.27-11.* : I din't consider that much at the time, as the 2.6.27-11 kernel were just an optional upgrade. Anyway, it's even a ubuntu 8.10 regression for 2.6.27-11 kernel user, so some users may decide to nominate this bug even for that release. -- Broken audio playback with Intel 82801G on 9.04 https://bugs.launchpad.net/bugs/336125 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 336125] Re: Broken audio playback with Intel 82801G on 9.04
> IMPORTANT: this is almost for sure kernel related as the old kernel 2.6.27-9.5 from ubuntu 8.10 DOES work Sorry: 2.6.27-9.19, NOT 2.6.27-9.5. -- Broken audio playback with Intel 82801G on 9.04 https://bugs.launchpad.net/bugs/336125 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 221499] Re: RTL8111/8168B does not work in Hardy
Confirmed. I may have further information: first, the card works perfectly with Ubuntu 7.10. The card binds to strange IRQs in 8.04 (where it's completely unfunctional). This is from /proc/interrupts in 8.04: ... 220: 0 0 PCI-MSI-edge eth0 ... IRQ 220??? Isn't this STRANGE? Even logs from Kjell Braden shows the same bad IRQ. And something is strange even with that PCI-MSI-edge. Now, let see /proc/interrups from 7.10. Here the card works perfectly: ... 23: 0659 IO-APIC-fasteoi eth0 ... This seems more SANE to me. I'll attach /proc/interrupts output. ** Attachment added: "/proc/interrupts from livecd ubuntu 8.04.01, eth0 NOT working" http://launchpadlibrarian.net/16242150/interrupts-8.04.01 -- RTL8111/8168B does not work in Hardy https://bugs.launchpad.net/bugs/221499 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 221499] Re: RTL8111/8168B does not work in Hardy
** Attachment added: "/proc/interrupts from livecd ubuntu 7.10, eth0 works" http://launchpadlibrarian.net/16242159/interrupts-7.10 -- RTL8111/8168B does not work in Hardy https://bugs.launchpad.net/bugs/221499 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 221499] Re: RTL8111/8168B does not work in Hardy
Changed from Fix Released to Confirmed. Backporting 2.6.26 is not an option for an LTS release! ** Changed in: linux (Ubuntu) Status: Fix Released => Confirmed -- RTL8111/8168B does not work in Hardy https://bugs.launchpad.net/bugs/221499 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 225175] Re: S-ATA Hard drives swapped
** Changed in: udev (Ubuntu) Sourcepackagename: None => udev Status: New => Confirmed -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 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 225175] Re: S-ATA Hard drives swapped
Confirmed. And I would say it's a serious bug for newbies, as simply the booloader is default installed in the wrong hard disk, not the first in the order that bios follows. What's strange (to me) is that: - grub from bios (on start-up): sees the hard drives in the correct order; - grub from live cd 8.04.01: sees the hard drives in the WRONG order. I would say here that, not being in real-mode, grub from live cd is not using bios calls to detect hard drives but relays on an higher level linux syscalls/driver interface. Really dunno. Distributions that work (detect sata drives in the correct order): - Ubuntu 7.10; - Gentoo 2008 (2.6.24 kernel). Next I'll attach dmesg, /proc/interrupts, lspci output from ubuntu 8.04.01 and 7.10. -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 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 225175] Re: S-ATA Hard drives swapped
** Attachment added: "Dmesg livecd 8.04.01 (wrong hds order)" http://launchpadlibrarian.net/16242683/dmesg-8.04.01 -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 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 225175] Re: S-ATA Hard drives swapped
** Attachment added: "/proc/interrupts livecd 8.04.01 (wrong hds order)" http://launchpadlibrarian.net/16242687/interrupts-8.04.01 -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 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 225175] Re: S-ATA Hard drives swapped
** Attachment added: "lspci livecd 8.04.01 (wrong hds order)" http://launchpadlibrarian.net/16242694/lspci-8.04.01 -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 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 225175] Re: S-ATA Hard drives swapped
** Attachment added: "Dmesg livecd 7.10 (correct hds order)" http://launchpadlibrarian.net/16242703/dmesg-7.10 -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 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 225175] Re: S-ATA Hard drives swapped
** Attachment added: "/proc/interrupts livecd 7.10 (correct hds order)" http://launchpadlibrarian.net/16242706/interrupts-7.10 -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 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 225175] Re: S-ATA Hard drives swapped
** Attachment added: "lspci livecd 7.10 (correct hds order)" http://launchpadlibrarian.net/16242714/lspci-7.10 -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 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 225175] Re: S-ATA Hard drives swapped
Let me know if you want further debug info (hdparm, udev...). I don't know how to query udev for more details, so you'll have to instruct me. Thanks -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 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 225175] Re: S-ATA Hard drives swapped
Sorry, maybe it wasn't clear: I reassigned this bug to udev because even the name mangling of udev is swapped. /dev/sda --> /dev/sdb /dev/sdb --> /dev/sda So certainly, this bug is not pertinent to grub only, but refer to the way udev and grub detect their ordering (so may be system wide or similar on the 2 progs). May be even a kernel bug, but please note that Gentoo 2008 (comes with 2.6.24) works perfectly, like ubuntu 7.10. Please instruct me on how to collect more information from udev and grub to spot where they are assuming the wrong ordering and I'll report here. Thanks -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 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
Re: [Bug 225175] Re: S-ATA Hard drives swapped
2008/7/23 Scott James Remnant <[EMAIL PROTECTED]>: > As I said in my comment, If you further commented, your comment got lost somewhere. > This is why you'll find nowhere in Ubuntu that refers to the drives by > these names, instead fstab will be written in the form UUID=... which do > not change. > Alright, I know UUID mechanism. > the fact that the names change is perfectly > normal and expected behaviour. > Are you saying that something changed in udev and now it's expected to see modified ordering in hds (and maybe for ATA controllers in general)? I'm sorry, but just because as little as possible apps should rely on the static name mangling of the devices, and for very specific needs, this should be as close as possible to what bios detects (or want to detect). Let's do an example: grub from booted linux MAY (really dunno) relies on udev to do its job. So, grub could ask to udev: Grub: "Udev, please give me de device of the first hd on a ATA/SATA/SCSI controller, so I may expose it as hd0 to the user and install the bootloader here" Udev: "Ok, It's /dev/sda" If udev itself change this ordering, this will simply breaks application expecting to find an ordering as close as possible to the bios one. IMHO, the behaviour should be reverted to the previous (working) one. -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 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 221499] Re: RTL8111/8168B does not work in Hardy
Agreed with Mark, as this is clearly a regression. Ubuntu 7.10 worked and Gentoo 2008 (has kernel 2.6.24) works. -- RTL8111/8168B does not work in Hardy https://bugs.launchpad.net/bugs/221499 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 225175] Re: S-ATA Hard drives swapped
At least explain when and where this behaviour in ordering changed within udev and why shouldn't be a bug. Or, are you telling me that at the SAME TIME, udev changed its behavior in ordering and grub guys introduced a new bug that inadvertentlybroke the ordering? Tryed running grub (would be more correct to say the grub shell frontend, that's the component run when you are running linux) with --device-map option. This force grub to produce this device.map file: (fd0)/dev/fd0 (hd0)/dev/sda <-- This ISN'T the hd bios want to boot (hd1)/dev/sdb That is the wrong ordering, as said before. I'm sorry, but it's simpler to me to think that the grub shell frontend is just assuming the default LANANA device ordering to map devices, looking for the hd that hopefully will be booted by bios. So, for example, hd0 in grub is just the first /dev/hdX in alphabetical order (excluding cd-roms) if you use the old linux ATA driver, or /dev/sdX in alphabetical order (excluding cd-roms and usb mass storages) if you are using LIBATA or SCSI. In this case, you MAY think that changing the device ordering in udev is not a bug, but you would be inadvertently breaking other applications. Let's hope to hear a word from Grub devs soon. In the mean time, please, stay tuned. -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 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 221499] Re: RTL8111/8168B does not work in Hardy
Kjell, you pointed out how to nominated bugs using the SRU procedure and ironically you were the one to nominate this one for Hardy :) Let's hope for a fix...just to repeat it for the umpteenth time: this is *regression* . Gutsy worked flawlessly, as gentoo 2008.0, with a close kernel (slightly modified 2.6.24), works as well. -- RTL8111/8168B does not work in Hardy https://bugs.launchpad.net/bugs/221499 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
Re: [Bug 225175] Re: S-ATA Hard drives swapped
2008/7/24 Scott James Remnant <[EMAIL PROTECTED]>: > Nothing has changed in udev Maybe not in udev, but something has to be changed. Ubuntu 7.10: *always* correct bios ordering; Gentoo 2008.0 (kernel 2.6.24, udev 115): *always* correct bios ordering; Ubuntu 8.04.01: *always* SWAPPED ordering; Where *always* is "in all my attempts". I'm not saying it's not a lecit change, but please identify when this behavior changed. > > The relationship with grub is only a perceived one. > > In fact, grub has no matching or intelligence between sdX drives and its > own designators. This is the reason it uses its own in the first place. > Grub's device ordering depends entirely on the BIOS view of the drives, > in particular this means grub does not see any drive not seen by the > BIOS. > Let's make this important distinction: 1) Grub as a mbr: let's call it grub-mbr; 2) Grub as a shell frontend: let's call it /sbin/grub. grub-mbr obviously use bios, and after an install of ubuntu 8.04, the detected ordering of grub at boot is always "correct" (the bios one). /sbin/grub on livecd 8.04 gets different ordering, clearly not the bios one. So, I'm assuming that /sbin/grub is NOT using bios for its probes. It may use the current device files, but it's just my guess. We should ask this to grub maintainers (if they are listening...). You pointed: > Grub has its own issues as well; a favourite bug report is that grub > changes *its* device ordering when adding or removing drives, for no > readily apparent reason. (On my own machine, a new SATA drive on port 3 > became hd0 shuffling up those on ports 0-2) > > ... > > Switching grub to UUIDs solves both sets of problems. > 1) To make this working, grub-mbr must itself use UUIDs, not only /sbin/grub. In this way, even in grub.com/menu.lst you'll have root directives with UUIDs, for example "root (f0f68b8c-cf26-4c76-8a21-6a5c02c028dd)" instead of "root (hd0,0)". If this is not already implemented, it will require major changes to grub. 2) Not fully true. Switching to UUIDs won't solve the problem of finding the drive bios will boot (read where to install grub-mbr). I know, this problem is unsolvable in all the cases: people may want to boot from a SCSI drive even if they have an ATA drive, and grub can't say which is the preferred drive. However, we have to offer a "sensible default": relying on bios ordering and choosing the first hard disk is, IMHO, a good one in case of not so complicated configurations. Distros worked this way from the beginning, and nobody ever complained. If, for some reason, /sbin/grub is unable to detect bios ordering, this is a major problem and will breaks many configurations with >= 2 hard disks. > The only mapping between sdX and hdN names is /boot/grub/device.map > which is attempted to be kept in sync, but can fail between reboots. device.map is used only by /sbin/grub when you are using the switch --device-map. Changes on this file won't reflect to grub-mbr unless you re-install it from /sbin/grub using the command "setup (hdX)". So, simply keeping it synced correctly won't solve the problem either. -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 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 221499] Re: RTL8111/8168B does not work in Hardy
After all, this may be a motherboard bios configuration issue. I own a Asrock ALiveDual-eSATA2 [1] : with the last bios update (version 1.40, changelog "Modify code for PCI function." [2]), it seems the issue disappeared with ubuntu 8.10. This won't explain why the device worked with different distributions and kernel versions, but I hope it can help someone. [1] http://www.asrock.com/mb/overview.asp?Model=ALiveDual-eSATA2&s=n [2] http://www.asrock.com/mb/download.asp?Model=ALiveDual-eSATA2 -- RTL8111/8168B does not work in Hardy https://bugs.launchpad.net/bugs/221499 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
Re: [Bug 221499] Re: RTL8111/8168B does not work in Hardy
2008/12/18 sfikas : > I also own the Asrock ALiveDual-eSATA2 and i haven't problems with > kubuntu 8.10, but i had with kubuntu 8.04 > Nice to hear: I had problems with ubuntu 8.04 me too. I should test it with the newer bios, to see if this fixed the problem or something changed in ubuntu between 8.04 -> 8.10. Will do it later. -- RTL8111/8168B does not work in Hardy https://bugs.launchpad.net/bugs/221499 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
Re: [Bug 221499] Re: RTL8111/8168B does not work in Hardy
2008/12/18 Francesco Pretto : > I had problems with ubuntu 8.04 me too. I should test it > with the newer bios, to see if this fixed the problem or something > changed in ubuntu between 8.04 -> 8.10. Will do it later. > Nope, the newer bios didn't fixed the ethernet in ubuntu 8.04.1 livecd: my supposition was wrong! At least, I can confirm this bug is fixed for Asrock ALiveDual-eSATA2 users with ubuntu 8.10. -- RTL8111/8168B does not work in Hardy https://bugs.launchpad.net/bugs/221499 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 159941] Re: fglrx driver does not work in RT kernel
Confirmed.
WARNING: The following workaround doesn't respect ATI and linux
developers copyright. Don't redistribute the produced module.
Unfortunately, it seems the problem is in the -rt sources where some
symbols are marked GPL only (aren't they in the vanilla sources?).
In these files (change according the installed version of fglrx):
/usr/src/fglrx-8.543/firegl_public.c
/usr/src/fglrx-8.543/drm_compat.h
Look respectively for these lines:
#define MODULE_LICENSE(x)
MODULE_LICENSE("Proprietary. blah blah etc");
and change them respectively to
#define MODULE_LICENSE("GPL")
MODULE_LICENSE("GPL");
Run from the shell:
# sudo /etc/init.d/dkms_autoinstaller start
Reboot and you're done.
--
fglrx driver does not work in RT kernel
https://bugs.launchpad.net/bugs/159941
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 67810] Re: bad hard disk noise on shutdown
The definitive patches [1] [2] have been merged in mainstream 2.6.22rc1. I opened the bug #114683 to request changes in upstart shutdown(8). [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=9666f4009c22f6520ac3fb8a19c9e32ab973e828 [2] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=920a4b1038e442700a1cfac77ea7e20bd615a2c3 -- bad hard disk noise on shutdown https://bugs.launchpad.net/bugs/67810 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67810] Re: bad hard disk noise on shutdown
Someone can confirm me that the patch that add "stop_on_shutdown" is still in the latest ubuntu 2.6.20 kernel? Thanks -- bad hard disk noise on shutdown https://bugs.launchpad.net/bugs/67810 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67810] Re: bad hard disk noise on shutdown
> please try this immediately and report back? Which version of the kernel this patch apply? -- bad hard disk noise on shutdown https://bugs.launchpad.net/bugs/67810 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67810] Re: bad hard disk noise on shutdown
> Early reports indicate that this patch likely does NOT solve the problem. The fact is that this is not a bug/regression of the kernel. It's a lack of feature. The early original patch here, http://www.nabble.com/(fwd)--PATCH--sd:-implement-stop_on_shutdown-t3049703.html , that was already merged, need mandatory changes in userspace, so changes to upstart shutdown(8) or workaround as described in some posts here. The definitive patches here: http://article.gmane.org/gmane.linux.scsi/30489 http://article.gmane.org/gmane.linux.ide/17392 are probably too much invasive to be merged in a stable, distro customized kernel, but don't need changes in userspace (beacuse they use a kernel-space workaround, already scheduled for removal). So, from a distro perspective, there are few options: 1) Keep original early patch and modify upstart shutdown(8) now (i was waiting for the definitive patches to be merged in 2.6.22-rc before submitting a bug to upstart...); 2) Merge the definitive patches; 3) || die >From a user perspective, simply use the early patch (that should be already merged in ubuntu 2.6.20 kernel, right?) plus the workarounds described here by Martin Koßler and More. -- bad hard disk noise on shutdown https://bugs.launchpad.net/bugs/67810 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67810] Re: bad hard disk noise on shutdown
Oddly, no one except few people are complaining about this bug in the RIGHT places, linux kernel bugzilla and lkml. What do you need? A f***ing workaround that is good for 2 persons in the planet or a REAL solution??? Send additional details on http://bugzilla.kernel.org/show_bug.cgi?id=7674 or just leave a message at linux-kernel@vger.kernel.org (subscription is not needed and you can follow it from http://groups.google.com/group/linux.kernel/topics) asking for kernel bug #7674. -- bad hard disk noise on shutdown https://launchpad.net/bugs/67810 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67810] Re: bad hard disk noise on shutdown
Is it possible to produce a version of the above patch that apply to kernel 2.6.17 of ubuntu 6.10? However, i leaved a post on lmkl, http://groups.google.com/group/linux.kernel/browse_frm/thread/a08eb3f2887ae852/fa787ed42c1e3097?lnk=gst&q=weird&rnum=9 , regarding this problem. Please, if you are interested in seeing this bug resolved asap, put some contributions to it, as it seems very difficult to gain attention on this issue and, in my opinion, it's yet to be determined if this is a regression of a lack of feature. For example, can someone affirm that this bug wasn't present in ubuntu dapper drake using libata drivers? -- bad hard disk noise on shutdown https://launchpad.net/bugs/67810 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67810] Re: bad hard disk noise on shutdown
Fixed in mainstream http://article.gmane.org/gmane.linux.scsi/30489 .
Lot of infrastructure here, probably 2.6.22 stuff? Please note that the
FULL fix will need shutdown(8) modifies, as described here
http://article.gmane.org/gmane.linux.ide/17392 .
In the same message is described a meantime workaround, that consist of
a temporary setting (already scheduled for removal) in the libata
module. Here the extract:
> This patch implements module parameter libata.spindown_compat which,
> when set to one (default value), prevents libata from spinning down
> disks on shutdown thus avoiding double spinning down. Note that
> libata spins down disks for suspend to mem and disk, so with
> libata.spindown_compat set to one, disks should be properly spun down
> in all cases without modifying shutdown(8).
>
> shutdown(8) should be fixed eventually tho. Some drive do spin up on
> SYNCHRONZE_CACHE even when their cache is clean. Those disks
> currently spin up briefly when sd tries to shutdown the device and
> then the machine powers off immediately, which can't be good for the
> head. We can't skip SYNCHRONIZE_CACHE during shudown as it can be
> dangerous data integrity-wise.
>
> So, this spindown_compat parameter is already scheduled for removal by
> the end of the next year and here's what shutdown(8) should do.
>
> 1. Check whether /sys/modules/libata/parameters/spindown_compat
> exists. If it does, write 0 to it.
>
> For each libata harddisk {
>
>2. Check whether /sys/class/scsi_disk/h:c:i:l/manage_start_stop
> exists. If so, write 1 to it and continue; otherwise, fall
> through to #3.
>
>3. Synchronize cache and spin down as before.
>
> }
If i can ask, is there a mainstream for shutdown(8) or it vary between
distros?
--
bad hard disk noise on shutdown
https://launchpad.net/bugs/67810
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67810] Re: bad hard disk noise on shutdown
I was promised that a fix will eventually arrive. It would take longer because a code refactory of the libata layer was in program. -- bad hard disk noise on shutdown https://launchpad.net/bugs/67810 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545795] Re: apparmor driver blocks access to hostdev and pcidev devices
I'm using libvirt-bin 0.7.5-5ubuntu25 and the bug is still there. Is the fix lost somewhere? My /var/log/libvirt/qemu/storage.log have these lines: usb_create: no bus specified, using "usb.0" for "usb-host" husb: open device 6.2 /dev/bus/usb/006/002: Permission denied husb: open device 6.2 /dev/bus/usb/006/002: Permission denied husb: open device 6.2 /dev/bus/usb/006/002: Permission denied husb: open device 6.2 /dev/bus/usb/006/002: Permission denied husb: open device 6.2 /dev/bus/usb/006/002: Permission denied ... -- apparmor driver blocks access to hostdev and pcidev devices https://bugs.launchpad.net/bugs/545795 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 545795] Re: apparmor driver blocks access to hostdev and pcidev devices
Just to confirm something is still not working for me: $ sudo apt-cache showpkg libvirt-bin Package: libvirt-bin Versions: 0.7.5-5ubuntu25 Adding the generic (and unsafe) line: /dev/bus/usb/*/[0-9]* rw, to /etc/apparmor.d/abstractions/libvirt-qemu and reloading profiles works for me so it seems the mechanism to dynamically add host devices to the apparmor profile has been bounced as well or not working anymore. -- apparmor driver blocks access to hostdev and pcidev devices https://bugs.launchpad.net/bugs/545795 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 547091] Re: 10.04 beta 1 mountall fails to mount iSCSI volume at boot
Who is responsibile to honour _netdev option? In my /etc/fstab I have the line: /dev/sda /storageext4defaults,auto,_netdev 0 0 (yes, for ease administration, I created a partition in the whole iscsi "disk", that is a logical volume in the iscsitarget) Still I get many: mount: special device /dev/sda does not exist mountall: mount /storage [xxx] terminated with status 32 as the reporter. At last the fs is mounted **anyway**, so mountall is repeating mount attempts, but boot is soiled with many warnings, with a last: mountall: Disconnected from plymouth in front of the first tty. Not clear if this is the expected behavior or the boot is supposed to be more silent. -- 10.04 beta 1 mountall fails to mount iSCSI volume at boot https://bugs.launchpad.net/bugs/547091 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 545795] Re: apparmor driver blocks access to hostdev and pcidev devices
I used virt-manager: storage 0175b337-5faf-42ba-d6a7-bb60ec8da4ad 1572864 1572864 1 hvm destroy restart restart /usr/bin/kvm libvirt-0175b337-5faf-42ba-d6a7-bb60ec8da4ad libvirt-0175b337-5faf-42ba-d6a7-bb60ec8da4ad -- apparmor driver blocks access to hostdev and pcidev devices https://bugs.launchpad.net/bugs/545795 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 516018] Re: cups 400 Bad Request for fully qualified host name
** Bug watch added: Debian Bug tracker #525910 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525910 ** Also affects: cups (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525910 Importance: Unknown Status: Unknown -- cups 400 Bad Request for fully qualified host name https://bugs.launchpad.net/bugs/516018 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 516018] Re: cups 400 Bad Request for fully qualified host name
** Bug watch added: Red Hat Bugzilla #498884 https://bugzilla.redhat.com/show_bug.cgi?id=498884 ** Also affects: cups (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=498884 Importance: Unknown Status: Unknown -- cups 400 Bad Request for fully qualified host name https://bugs.launchpad.net/bugs/516018 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 516018] Re: cups 400 Bad Request for fully qualified host name
The solution seems to be add "ServerAlias *" to /etc/cups/cupsd.conf, but it's not added automatically installing cups 1.4.3-1 in ubuntu server 10.04 while it's there in ubuntu desktop 9.10. -- cups 400 Bad Request for fully qualified host name https://bugs.launchpad.net/bugs/516018 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 457144] Re: Add pulseaudio support to sun-java6-jdk
Hello. Sorry, I forgot to subscribe to this bug so I lost your update. Tried your hint and no joy. I usually test this problem with browser and this java web radio: http://rob.kohina.net/javastream Close browser -> open browser -> open java web radio -> open any youtube video -> NO sound on youtube. Close browser -> open browser -> open any youtube video -> open java web radio -> NO sound on java web radio. -- Add pulseaudio support to sun-java6-jdk https://bugs.launchpad.net/bugs/457144 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 545795] Re: apparmor driver blocks access to hostdev and pcidev devices
Yes, that worked! :) -- apparmor driver blocks access to hostdev and pcidev devices https://bugs.launchpad.net/bugs/545795 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 494141] Re: CUPS starts after SAMBA; printers are not available
** Also affects: samba (Ubuntu) Importance: Undecided Status: New -- CUPS starts after SAMBA; printers are not available https://bugs.launchpad.net/bugs/494141 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 494141] Re: CUPS starts after SAMBA; printers are not available
2 problems here: - cups is still an old sysvinit script; - samba is an upstart job but doesn't have any dependencies on cups. Moreover I think it's the samba upstart job that should assert "start after cups", and not cups to worry about starting before samba. So for sure this actually a deficiency in the samba upstart job. Not clear to me if it can be solved before cups becomes an upstart job too. If you want a temporary workaround, put a: sleep 10 just after "pre start script" in /etc/init/smbd.conf. Actually, I needed to put the same waiting time in /etc/init/nmbd.conf otherwise the master domain browser was nonfunctional, so it seems there are some dependencies nmbd <-> smbd (don't know the correct verse) unsatisfied. -- CUPS starts after SAMBA; printers are not available https://bugs.launchpad.net/bugs/494141 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 494141] Re: CUPS starts after SAMBA; printers are not available
Just to be clear, what is exactly the cups bug (other than not being an upstart job yet)? I don't know if upstart already have stanzas like "start before/after" (because it's clear that samba is not really dependent on cups, but if present cups should be started before samba), but it seems more easy to me for samba to say something like "start after cups" than cups keeping an updated list of services it should start before. -- CUPS starts after SAMBA; printers are not available https://bugs.launchpad.net/bugs/494141 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 494141] Re: CUPS starts after SAMBA; printers are not available
Or maybe is a problem in cups not promptly giving a dynamic list of printers available runtime? Sorry, but there were no explanation and I was curious about this. :) -- CUPS starts after SAMBA; printers are not available https://bugs.launchpad.net/bugs/494141 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 568877] Re: ERROR: 'Bad interface name' issuing ufw on valid, but non "ethx", interface names
** Also affects: ufw (Ubuntu) Importance: Undecided Status: New -- ERROR: 'Bad interface name' issuing ufw on valid, but non "ethx", interface names https://bugs.launchpad.net/bugs/568877 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 238143] Re: bug status "triaged" is ambiguous
Actually the real problem with the term "triaged" is that is hard to find in online vocabularies, and the problem is more serious for non english speaking people. I think "diagnosed" would be more appropriate. It would mean: - The bug is confirmed; - It's clear where the bug is; - It's clear how to fix it; - It will be fixed, soon or later. -- bug status "triaged" is ambiguous https://bugs.launchpad.net/bugs/238143 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 544733] Re: Adobe Flash player no longer works; I get "Install Missing Plugin" notice
*** This bug is a duplicate of bug 532542 *** https://bugs.launchpad.net/bugs/532542 ** Also affects: ubufox (Ubuntu) Importance: Undecided Status: New -- Adobe Flash player no longer works; I get "Install Missing Plugin" notice https://bugs.launchpad.net/bugs/544733 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 532542] Re: [lucid] flashplugin-installer doesn't work with Firefox 3.6
** Also affects: ubufox (Ubuntu) Importance: Undecided Status: New -- [lucid] flashplugin-installer doesn't work with Firefox 3.6 https://bugs.launchpad.net/bugs/532542 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
Re: [Bug 457144] Re: Add pulseaudio support to sun-java6-jdk
2010/5/8 manolo : > Francesco, thanks for the advice. > Wasn't my advice, but Antti's one. Anyway, it seems sun official jvm isn't going to be supported long (it's have been removed from lucid main repositories), so it's better to begin reporting bugs with openjdk where hopefully integration with pulseaudio works better. -- Add pulseaudio support to sun-java6-jdk https://bugs.launchpad.net/bugs/457144 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 350936] Re: Should shut down domains on system shutdown
2010/5/5 Soren Hansen : > > It's important to remember that libvirt intentionally does not kill VM's > on termination. This enables us to upgrade libvirt without interruping > running VM's, so we want to only conditionally shut down VM's. Correct. > What I've > done on one of my Hardy boxes is to check $0 to see if the init script > was invoked as K??libvirt-bin. If so, I assume we're being shut down and > then I go and shut down the virtual machines. If invoked any other way, > it just stops libvirt, not the VM's. To achieve something similar with > upstart jobs, there's an environment variable that tells us why libvirt- > bin is being stopped. This will reveal whether it's being shut down as a > result of shutdown being called or whatnot. > But the problem is that the PIDs of the vm are not part of the libvirt-bin upstart job. Try to look my *ugly* workaround[1] : /etc/init.d/sendsings is just parallelizing killing any process not in upstart pool of tracked ones. So, when upstart shutdown libvirt-bin, almost for sure libvirt-bin won't find any active guests because they have been killed before by /etc/init.d/sendsing (killing those vm processes seems very quick). While this is good for libvirt-bin independence from kvm guests processes, this make fine grain control of guests shutdown harder, and one may wonder if it's not kvm itelsef that should send ACPI shutdown signal to guests, and not libvirt. I have another suspect: upstart may failing here. Doesn't libvirt-bin forks here to create kvm guests? Shouldn't "expect daemon" upstart stanza track daemons that fork more than once? If so, shouldn't libvirt- bin upstart job track these guests processes too? I have to ask in upstart mailing list. [1] https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/350936/comments/8 -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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 538660] Re: "Advanced" tab in "Remote Desktop Preferences" disappeared
Not clear: why decide to remove graphical support for options that are actually necessary to secure vnc access? Actually, if I hadn't found a guide to help me recover those options in gconf, I would have a unsecure setup. And this would be a security issue. Still, the interface with an "advanced" tab seems perfect to me from an usability/easy to use point of view: it's "advanced", if you don't know just don't use. Considering this issue and removing of XDMCP support from gdm preferences (and who knows when and if it will come back), remote desktop in ubuntu is getting worse and worse with any new release. -- "Advanced" tab in "Remote Desktop Preferences" disappeared https://bugs.launchpad.net/bugs/538660 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 538660] Re: "Advanced" tab in "Remote Desktop Preferences" disappeared
Thanks, will do. -- "Advanced" tab in "Remote Desktop Preferences" disappeared https://bugs.launchpad.net/bugs/538660 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 538660] [NEW] "Advanced" tab in "Remote Desktop Preferences" disappeared
Public bug reported: Binary package hint: vino The "Advanced" tab in "System -> Preferences -> Remote Desktop" preferences gui is disappeared since ubuntu 9.04. I never reported this because it seemed just a gui glitch, to be resolved quickly, not related at all with functionalities provided by vino. In fact, advanced features are still working by enabling them in gconf with gconf-editor , under "/desktop/gnome/remote_access". Now I'd like to know what the maintainer of the package think about the issue because I can't believe he hasn't noticed this in 3 ubuntu releases, seeing that the bug is still present in ubuntu 10.04 alpha3. Moreover, options in "Advanced" tab were fundamental to force secure vnc access in ssh tunnles by providing the option "Only allow local connections". "Proofs" of the existence of the advanced tab in ubuntu 8.10 http://www.techotopia.com/images/1/12/Ubuntu_advanced_remote_desktop_preferences2.jpg http://www.ubuntugeek.com/images/rem/3.png ** Affects: vino (Ubuntu) Importance: Undecided Status: New ** Tags: advanced desktop preferences remote -- "Advanced" tab in "Remote Desktop Preferences" disappeared https://bugs.launchpad.net/bugs/538660 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 350936] Re: Should shut down domains on system shutdown
I'm not sure it can be done hacking upstart job. When libvirt was a sysvinit script in ubuntu 9.10, I used this [1] script adding it in "stop" function. In Lucid, if I add the same script to /etc/init /libvirt-bin.conf with the stanza: pre-stop exec shut-guests.sh 2>&1 > /var/log/shut-guests.log This works if I manually invoke a stop of libvirt-bin in a running system with: $ sudo stop libvirt-bin but **doesn't** work when issuing a reboot or halt. It seems there's an aggressive killing of all kvm processes **before** the pre-stop stanza is execute, and libvirt doesn't find any running guests when the shut- guests.sh is executed. it's not clear to me why and If this is an exptected behavior. For sure, kvm processes are detached from libvirt process branch. [1] http://www.linux-kvm.com/content/stop-script-running-vms-using-virsh -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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 350936] Re: Should shut down domains on system shutdown
Workaround:
Add the lines:
/usr/local/bin/shut-guests.sh 2>&1 >> /var/log/shut-guests.log
/sbin/initctl emit guests-shutted
just after "do_stop() {" in /etc/init.d/sendsings
*and* changing the line:
stop on (runlevel [!2345])
on file /etc/init/libvirt-bin.conf to:
stop on guests-shutted
Ugly but works, until libvirt/kvm/distributions crews will care more
about data integrity in vm guests during shutdown (sigh).
--
Should shut down domains on system shutdown
https://bugs.launchpad.net/bugs/350936
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
Re: [Bug 494141] Re: CUPS starts after SAMBA; printers are not available
2010/5/20 PryGuy : > I'm all sorry, this was a mistake. I'm really surprised an ordinary user > can change it. Sorry again. > (OT) Hehehe, actually Launchpad works better than others BTS because gives more freedom to users. If you did a mistake, don't worry but be more careful next time :) -- CUPS starts after SAMBA; printers are not available https://bugs.launchpad.net/bugs/494141 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 209198] Re: Cannot play my music when watching playing java games
*** This bug is a duplicate of bug 228487 *** https://bugs.launchpad.net/bugs/228487 ** Also affects: sun-java6 (Ubuntu) Importance: Undecided Status: New -- Cannot play my music when watching playing java games https://bugs.launchpad.net/bugs/209198 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 457144] Re: Add pulseaudio support to sun-java6-jdk
** Changed in: sun-java6 (Ubuntu) Status: New => Confirmed -- Add pulseaudio support to sun-java6-jdk https://bugs.launchpad.net/bugs/457144 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 404313] Re: Java applets block pulse audio
*** This bug is a duplicate of bug 457144 *** https://bugs.launchpad.net/bugs/457144 Marked as duplicate of #457144 and nominated that one for Karmik and Lucid, let's see if we get more attention. ** This bug has been marked a duplicate of bug 457144 Add pulseaudio support to sun-java6-jdk -- Java applets block pulse audio https://bugs.launchpad.net/bugs/404313 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 209198] Re: Cannot play my music when watching playing java games
*** This bug is a duplicate of bug 457144 *** https://bugs.launchpad.net/bugs/457144 ** This bug is no longer a duplicate of bug 228487 can only have one audio output program working at a time ** This bug has been marked a duplicate of bug 457144 Add pulseaudio support to sun-java6-jdk -- Cannot play my music when watching playing java games https://bugs.launchpad.net/bugs/209198 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
Re: [Bug 159941] [NEW] fglrx driver does not work in RT kernel
2009/10/8 Luke Yelavich : > Could you please provide the exact error message you get when attempting > to load the fglrx module? You can most probably get this output from the > dmesg command. If you can attach it to this bug, it would go a long way > in helping work out the problem. > Hmm... I advice to read the bug report from the begin: it's not a matter of loading the kernel. Much simply, the module can't be compiled within DKMS infrastructure using a -rt kernel because of GPL symbols violation. Nothing get compiled -> nothing to load -> nothing can fail :) . I've posted an (illegal) workaround [1]. Wondering why there's no legal problem compiling fglrx module using standard kernel/headers. [1] https://bugs.launchpad.net/ubuntu/+source/linux- rt/+bug/159941/comments/6 -- fglrx driver does not work in RT kernel https://bugs.launchpad.net/bugs/159941 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
Re: [Bug 159941] Re: fglrx driver does not work in RT kernel
2009/10/11 Alessio Igor Bogani : > Hi, > > We can't do nothing with this bug (in sense that we can't help when people > choose to use self compiled driver). > > But. it's how DKMS infrastructure *works*! When you install a standard nvidia or flgrx driver, the module must be built (very little compiling, because everyone knows that nvidia/flgrx drivers are bundled with a big binary blob) for each kernel you install, generic ubuntu kernels too; to avoid this, DKMS was created [1] so it performs the build phase for you without user intervention. I don't want to be too much critic but this bug report is VERY clear: the matter is just to understand why some symbols are GPL only in the -rt kernel headers/source that aren't in the generic. Please, don't misunderstand it a third time. [1] http://linux.dell.com/projects.shtml#dkms -- fglrx driver does not work in RT kernel https://bugs.launchpad.net/bugs/159941 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
Re: [Bug 159941] Re: fglrx driver does not work in RT kernel
In the weekend I can try :) Thanks Alessio! -- fglrx driver does not work in RT kernel https://bugs.launchpad.net/bugs/159941 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 1772365] Re: gnome-shell + chrome doing nothing consumes high CPU all the time
I think what reported by Lorens may be totally unrelated to the use of Chrome. The use of VirtualBox, latest version 5.2.18, with a Ubuntu 18.04 64bit guest with 3D acceleration **enabled** and maximum VRAM configured (128MB) is completely unusable because of extremely high memory usage of gnome-shell, independently of the application launched: you can launch nothing or launch firefox, for example, and the session will become unusable pretty soon. It may be worth some more investigation of VirtualBox+3D acceleration use case. My host is actually Windows 10 64bit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772365 Title: gnome-shell + chrome doing nothing consumes high CPU all the time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576746] [NEW] Can't launch do-release-upgrade as root (No new release found)
Public bug reported: Trying to update to Ubuntu 15.04 to Ubuntu 15.10 update-manager GUI silently fails or I constantly receive "No new release found" from command-line acting as root user. In /etc/update-manager/release-upgrades I correctly have "Prompt=normal" Attempted programs used: 1) update-manger (GUI, non-root) 2) update-manager -d (CLI/GUI, non-root) 3) sudo update-manager -d (CLI) 3) sudo do-release-manager -d (CLI) GUI launched as non-root prompts for a new release (update- manager1.png), but as soon as prompted to log to root (update- manager2.png) it fails silently. GUI launched as root *doesn't* prompt for new release. WORKAROUND: Only working mean to upgrade is by command line with non-root "do-release-manager", which correctly reports the available release. TROUBLESHOOTING: Debugging do-release-upgrade[1][2][3] led me to the following discovery: in MetaRelease.py[4] root succeeds in "opening" the non-existing file "/var/lib/update-manager/meta-release-development", leading to timeout exception while trying to download the remote file[6] checking for changes at line 330. Instead non-root fails trying to access meta-release-development and fallabacks to a file in the home directory[7]. Downloading at line 330 succeeds and the main script can continue. meta-release-development[5] in my system wasn't present. This is probably a LTS system switched to non-LTS at some point. Everything else seems to be working. STEPS TO REPRODUCE: - In a 15.04 system, delete system meta-release-development[5], if present; - Try to upgrade as a root user (GUI or CLI). PROPOSED SOLUTION: Better handle non existing meta-release-development[5] file as root in MetaRelease.py[4]. VERSIONS INFO: Description:Ubuntu 15.04 Release:15.04 ubuntu-release-upgrader-core: Installed: 1:15.04.14.3 Candidate: 1:15.04.14.3 [1] /usr/bin/do-release-upgrade [2]debug-do-release-upgrade-root.png [3] debug-do-release-upgrade-nonroot.png [4] /usr/lib/python3/dist-packages/UpdateManager/Core/MetaRelease.py [5] /var/lib/update-manager/meta-release-development [6] http://changelogs.ubuntu.com/meta-release-development [7] ~/.cache/update-manager-core/meta-release ** Affects: ubuntu-release-upgrader (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/1576746 Title: Can't launch do-release-upgrade as root (No new release found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1576746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576746] Re: Can't launch do-release-upgrade as root (No new release found)
** Attachment added: "update-manger1.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1576746/+attachment/4651440/+files/update-manger1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576746 Title: Can't launch do-release-upgrade as root (No new release found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1576746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576746] Re: Can't launch do-release-upgrade as root (No new release found)
** Attachment added: "debug-do-release-upgrade-nonroot.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1576746/+attachment/4651448/+files/debug-do-release-upgrade-nonroot.png ** Description changed: Trying to update to Ubuntu 15.04 to Ubuntu 15.10 update-manager GUI silently fails or I constantly receive "No new release found" from command-line acting as root user. In /etc/update-manager/release-upgrades I correctly have "Prompt=normal" Attempted programs used: 1) update-manger (GUI, non-root) 2) update-manager -d (CLI/GUI, non-root) 3) sudo update-manager -d (CLI) 3) sudo do-release-manager -d (CLI) GUI launched as non-root prompts for a new release (update- manager1.png), but as soon as prompted to log to root (update- manager2.png) it fails silently. GUI launched as root *doesn't* prompt for new release. WORKAROUND: Only working mean to upgrade is by command line with non-root "do-release-manager", which correctly reports the available release. TROUBLESHOOTING: - Debugging do-release-upgrade[1][2][3] led me to the following discovery: in MetaRelease.py[4] root succeeds in "opening" the non-existing file "/var/lib/update-manager/meta-release", leading to timeout exception while trying to download the remote file[6] checking for changes at line 330. Instead non-root fails trying to access meta-release and fallabacks to a file in the home directory[7]. Downloading at line 330 succeeds and the main script can continue. + Debugging do-release-upgrade[1][2][3] led me to the following discovery: in MetaRelease.py[4] root succeeds in "opening" the non-existing file "/var/lib/update-manager/meta-release-development", leading to timeout exception while trying to download the remote file[6] checking for changes at line 330. Instead non-root fails trying to access meta-release-development and fallabacks to a file in the home directory[7]. Downloading at line 330 succeeds and the main script can continue. - meta-release[5] in my system wasn't present. This is probably a LTS - system switched to non-LTS at some point. Everything else seems to be - working. + meta-release-development[5] in my system wasn't present. This is + probably a LTS system switched to non-LTS at some point. Everything else + seems to be working. STEPS TO REPRODUCE: - - In a 15.04 system, delete system meta-release[5], if present; + - In a 15.04 system, delete system meta-release-development[5], if present; - Try to upgrade as a root user (GUI or CLI). PROPOSED SOLUTION: - Better handle non existing meta-release[5] file as root in MetaRelease.py[4]. + Better handle non existing meta-release-development[5] file as root in MetaRelease.py[4]. VERSIONS INFO: Description: Ubuntu 15.04 Release: 15.04 ubuntu-release-upgrader-core: - Installed: 1:15.04.14.3 - Candidate: 1:15.04.14.3 - + Installed: 1:15.04.14.3 + Candidate: 1:15.04.14.3 [1] /usr/bin/do-release-upgrade [2]debug-do-release-upgrade-root.png [3] debug-do-release-upgrade-nonroot.png [4] /usr/lib/python3/dist-packages/UpdateManager/Core/MetaRelease.py - [5] /var/lib/update-manager/meta-release + [5] /var/lib/update-manager/meta-release-development [6] http://changelogs.ubuntu.com/meta-release-development [7] ~/.cache/update-manager-core/meta-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576746 Title: Can't launch do-release-upgrade as root (No new release found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1576746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576746] Re: Can't launch do-release-upgrade as root (No new release found)
** Attachment added: "update-manger2.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1576746/+attachment/4651441/+files/update-manger2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576746 Title: Can't launch do-release-upgrade as root (No new release found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1576746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576746] Re: Can't launch do-release-upgrade as root (No new release found)
Correction in the original description: fixed reference to system wide meta-release-development, *not* meta-release. "meta-release-development" is not present on my system, only "meta- release-lts". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576746 Title: Can't launch do-release-upgrade as root (No new release found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1576746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576746] Re: Can't launch do-release-upgrade as root (No new release found)
** Attachment added: "debug-do-release-upgrade-root.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1576746/+attachment/4651442/+files/debug-do-release-upgrade-root.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576746 Title: Can't launch do-release-upgrade as root (No new release found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1576746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576746] Re: Can't launch do-release-upgrade as root (No new release found)
Also affecting Ubuntu 15.10 trying to upgrade to 16.04 LTS ubuntu-release-upgrader-core: Installed: 1:15.10.14.4 Candidate: 1:15.10.14.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576746 Title: Can't launch do-release-upgrade as root (No new release found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1576746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 494141] Re: CUPS starts after SAMBA; printers are not available (convert cups to upstart)
2010/9/17 Martin Pitt : > cups (1.4.4-5) unstable; urgency=low > > [ Martin Pitt ] > * ubuntu-upstart.dpatch: Drop the dependency "on starting smbd", it causes > samba to hang on package upgrades or manual restarts. There doesn't seem > to be a good way to express this dependency right now. (LP: #639768) Is Scott (maintainer of upstart) aware of this? -- CUPS starts after SAMBA; printers are not available (convert cups to upstart) https://bugs.launchpad.net/bugs/494141 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 802538] Re: /etc/udev/rules.d/70-persistent-net.rules not automatically generated
This is a case where satysfying a wish cause problems to others. In my opinion the rule should be this: at every boot there's a check on every 70-persistent-net.rules entry: if (MAC(entry) is kvm/qemu/wmware type && the entry was referred to a card card in the PCI bus (read: not used often for hotpluggable devices) && MAC(entry) doens't exist anymore) delete(entry); Just disabling persistent net generator is, in my opinion, against the purpose of udev and it's causing troubles to users that liked the behavior of seeing the 70-persistent-net.rule to be autogenerated on delete. But I think udev is powerful enough that we can find a solution that satisfy "everybody". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802538 Title: /etc/udev/rules.d/70-persistent-net.rules not automatically generated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/802538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350936] Re: Should shut down domains on system shutdown
Is this fixed in ubuntu 10.04.3? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/350936 Title: Should shut down domains on system shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/350936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 350936] Re: Should shut down domains on system shutdown
Don't think so. It's part of the independence of libvirt from the the actual virtualization technology (KVM, ...) to permit updates without shutdown of guests. 2010/11/4 Valentijn Sessink : > Hmm. If libvirt shuts down the virtual machines it monitors, then these > virtual machines will also be shut down when updating libvirt. > -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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
Re: [Bug 350936] Re: Should shut down domains on system shutdown
2010/6/24 ossjunkie : > why does libvirt-bin still stop before the libvirt-shutdown-guests job has > finished the script? Because kvm guests processes aren't tracked by the upstart job and they are killed immediately by /etc/init.d/sendsings. This approach have pros (independence of libvirt from guests) and cons (this problem) so there's no easy fix. In my previous post [1] there's an ugly but safe workaround. If you want a definitive solution try to bug libvirt devs by pointing this exact problem (/etc/init.d/sendsings killing guests before libvirt-bin upstart job finishes). [1] https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/350936/comments/8 -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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
Re: [Bug 350936] Re: Should shut down domains on system shutdown
2010/6/24 Soren Hansen : >> why does libvirt-bin still stop before the libvirt-shutdown-guests job >> has finished the script? > > Good question. Upstart shouldn't be killing it, but something else > might. I can't imagine what, though. > I'm not sure Upstart isn't supposed to kill them. Let's suppose upstart is able to track all pids forked for livbvirt-bin job start (and it doesn't do so, even if the "expect daemon" stanza is used: this may be an upstart bug): there would be a pid for libvirt-bin and many pids for kvm guests. Suppose you want to kill the libvirt-bin job: how can you tell upstart to kill just libvirt-bin and not kvm guests? I don't think upstart jobs are so flexible. -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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 577825] Re: Either battery status icon not being shown, or the icon showing "Laptop battery is charged".
Seems a kernel problem: $ cat /proc/acpi/battery/BAT1/info present: yes design capacity: 4400 mAh last full capacity: 4400 mAh battery technology: rechargeable design voltage: 11100 mV design capacity warning: 300 mAh design capacity low: 132 mAh capacity granularity 1: 32 mAh capacity granularity 2: 32 mAh model number:BAT1 serial number: 11 battery type:11 OEM info:11 $ cat /proc/acpi/battery/BAT1/state present: yes capacity state: ok charging state: charged present rate:unknown remaining capacity: unknown present voltage: 1 mV ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- Either battery status icon not being shown, or the icon showing "Laptop battery is charged". https://bugs.launchpad.net/bugs/577825 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 577825] Re: Either battery status icon not being shown, or the icon showing "Laptop battery is charged".
Previous states are taken while the laptop is disconnected from power supply. -- Either battery status icon not being shown, or the icon showing "Laptop battery is charged". https://bugs.launchpad.net/bugs/577825 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 577825] Re: Either battery status icon not being shown, or the icon showing "Laptop battery is charged".
Good job DisDis! I removed the "needs-upstream-testing" tag as told in the automated message. ** Tags removed: needs-upstream-testing -- Either battery status icon not being shown, or the icon showing "Laptop battery is charged". https://bugs.launchpad.net/bugs/577825 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
Re: [Bug 350936] Re: Should shut down domains on system shutdown
Clap! :) 2010/9/29 Andy : > It is a dismal situation when at this point there is still no official simple > way from Canonical to > gracefully shutdown KVM VMs if the host has to go down for any reason such as > a UPS issued shutdown command. > -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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
Re: [Bug 350936] Re: Should shut down domains on system shutdown
I have seen the commit that implements this functionality and it's, as usual, a sysvinit script. Unfortunately, I think this is a use case where upstart can't do anything yet and the only solution (without moving back to a sysvinit script) is doing an ugly workaround in /etc/init.d/sendsigs. I've tried to subscribe Scott James Remnant (maintainer of upstart: thanks!): this is not a bug in upstart (maybe a feature lack) but I hope he have something to share with us about this problem. 2010/8/6 Sergey Svishchev <350...@bugs.launchpad.net>: > This is implemented in libvirt 0.8.2: > > https://bugzilla.redhat.com/show_bug.cgi?id=444273 > > ** Bug watch added: Red Hat Bugzilla #444273 > https://bugzilla.redhat.com/show_bug.cgi?id=444273 > > -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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
Re: [Bug 350936] Re: Should shut down domains on system shutdown
2010/9/17 John Morrissey : > The attached file updates libvirt-bin's upstart job to gracefully shut > down VMs when the system shuts down. You can alter the shutdown timeout > (SHUTDOWN_TIMEOUT, default: 300s) and list of virsh(1) URIs to use > (URIS, default: "qemu:///system") in /etc/default/libvirt-bin. > While I am beginning to hate upstart because of its deficiencies (#494141, #406397), I don't think adding a sysvinit script to fix an upstart job is the best workaround. Just handle pid omits in sendsigs as a special case for libvirt, as done for other problems. -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 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
