[Bug 725198] Re: quodlibet crashed with ImportError in /usr/lib/pymodules/python2.7/quodlibet/widgets.py: cannot import name EditingPlugins
*** This bug is a duplicate of bug 708711 *** https://bugs.launchpad.net/bugs/708711 This particular crash has already been reported and is a duplicate of bug #708711, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide Then please mark #708711 as public, give me access to the bug, or remove the duplicate status: Sorry, you don't have permission to access this page. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/725198 Title: quodlibet crashed with ImportError in /usr/lib/pymodules/python2.7/quodlibet/widgets.py: cannot import name EditingPlugins -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 564629] Re: rt2860 cardbus can't connect: Association request to the driver failed
Sadly, I no longer am able to test this. The harddisk of the notebook died a few weeks ago, and given its age, it's very unlikely I will spend money on a new disk for this machine. -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 410401] Re: [r300 KMS] modesetting not accepted by monitor
This is no longer an issue. Upstream bug is still open because with KMS the driver performs load-detect on already enabled outputs, causing occasional screen flicker -- [r300 KMS] modesetting not accepted by monitor https://bugs.launchpad.net/bugs/410401 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 311890] Re: imon driver does not work, irw crashes lircd
@herrmidnquer: actually, several Soundgraph remotes (including the -PAD models) register themselves as two separate modules (see minor:0 and minor:1 in my log above). One is the normal remote function, and the other is the pad - a mouse-like input device with movement keys and buttons, controlled from the same remote. -- imon driver does not work, irw crashes lircd https://bugs.launchpad.net/bugs/311890 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 606709] [NEW] can't play audio CD
Public bug reported: Binary package hint: kdemultimedia I must say I'm more than a bit disheartened to see bugs like #121177 marked invalid, as I stumbled across this bug today for the first time, with a fully up-to-date 10.04 install. I don't care whether the reason is Amarok doesn't play audio CDs, or Amarok doesn't support kioslaves, or KSCD can play discs just fine, the original bug is still there. When I insert an audio CD, I get a helpful autorun dialog, which gives me the following options: - rip CD iwth k3b - copy CD with k3b - open disc with Dolphin - play disc with Amarok No matter which of my 2 disc drives I use, Amarok keeps reporting 0 tracks (when I press eject, it does open the correct tray). And when I choose open disc with Dolphin, it shows no tracks and reports failed to read in the statusbar. Only k3b handles the disc well, but that's useless to me because I don't want to rip. I want to play. Some reports mention the ability to change the device path to the cdrom drive in Amarok's settings, but: - that option does not appear to exist in this version (2.3.0) - the whole point of using a DE is the ability to be blissfully unaware of device files Of course, the CD plays just fine with vlc. ** Affects: kdemultimedia (Ubuntu) Importance: Undecided Status: New -- can't play audio CD https://bugs.launchpad.net/bugs/606709 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 564629] Re: rt2860 cardbus can't connect: Association request to the driver failed
PJO wrote: Solution here: http://wombatdiet.net/2010/05/09/ubuntu-10-04-on-asus-1000-eee-pc/ You must have missed the part where I said my issue is not fixed with v2.3.0 from the Ralink website. It's only the third line of my report. ** Tags removed: needs-kernel-logs -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] Re: rt2860 cardbus can't connect: Association request to the driver failed
apport information ** Tags added: apport-collected ** Description changed: This might very well be a duplicate of #496093, but I'm reporting a new bug because: - I'm using the pcmcia module, which no other reporter seems to have - my issue is not fixed with v2.3.0 from the Ralink website - I'm already using a WPA2-only access point (or I don't know how to configure OpenWRT correctly) - I have not run any Linux before on this notebook, so I can't tell whether it is a regression lspci info: 05:00.0 Network controller: RaLink RT2800 802.11n PCI Subsystem: SiteCom Europe BV Device 0015 Flags: bus master, slow devsel, latency 64, IRQ 9 Memory at 1c00 (32-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Kernel driver in use: rt2860 Kernel modules: rt2860sta 05:00.0 0280: 1814:0601 Subsystem: 182d:0015 lad...@pixie:~$ modinfo rt2860sta filename: /lib/modules/2.6.32-21-generic/kernel/drivers/net/wireless/rt2860sta.ko version:2.3.0.0 license:GPL srcversion: 73F7AA771D91BB10E13F38D But I'm still getting this in syslog: Apr 16 13:28:08 pixie wpa_supplicant[1659]: Trying to associate with 00:1d:7e:c6:9c:24 (SSID='WRT-AS24' freq=2412 MHz) Apr 16 13:28:08 pixie kernel: [ 723.024400] ===rt_ioctl_giwscan. 7(7) BSS returned, data-length = 1023 Apr 16 13:28:08 pixie kernel: [ 723.024972] ==rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Apr 16 13:28:08 pixie wpa_supplicant[1659]: Association request to the driver failed Apr 16 13:28:08 pixie wpa_supplicant[1659]: Associated with 00:1d:7e:c6:9c:24 Apr 16 13:28:08 pixie wpa_supplicant[1659]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Apr 16 13:28:08 pixie wpa_supplicant[1659]: last message repeated 3 times Whereas with the original driver (1.1.8? from kernel 2.6.32-21) I got: Apr 16 12:36:14 pixie wpa_supplicant[741]: Trying to associate with 00:1d:7e:c6: 9c:24 (SSID='WRT-AS24' freq=2412 MHz) Apr 16 12:36:14 pixie wpa_supplicant[741]: Association request to the driver failed Apr 16 12:36:14 pixie wpa_supplicant[741]: Associated with 00:1d:7e:c6:9c:24 Apr 16 12:36:17 pixie wpa_supplicant[741]: WPA: Key negotiation completed with 0 0:1d:7e:c6:9c:24 [PTK=CCMP GTK=CCMP] Apr 16 12:36:17 pixie wpa_supplicant[741]: CTRL-EVENT-CONNECTED - Connection to 00:1d:7e:c6:9c:24 completed (auth) [id=0 id_str=wlan-loos] Apr 16 12:40:47 pixie wpa_supplicant[741]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Apr 16 12:40:53 pixie wpa_supplicant[741]: Failed to initiate AP scan. Apr 16 12:41:08 pixie wpa_supplicant[741]: Trying to associate with 00:1d:7e:c6:9c:24 (SSID='WRT-AS24' freq=2412 MHz) Apr 16 12:41:08 pixie wpa_supplicant[741]: Association request to the driver failed This all worked correctly in Windows (which I no longer have), and my game console connects to the access point without trouble. I don't have other access points to try right now. + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. + AplayDevices: aplay: device_list:223: no soundcards found... + Architecture: i386 + ArecordDevices: arecord: device_list:223: no soundcards found... + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1: + CRDA: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 10.04 + Lsusb: Error: [Errno 2] No such file or directory + MachineType: FUJITSU SIEMENS LIFEBOOK B Series + Package: linux (not installed) + PccardctlIdent: + Socket 0: +no product info available + Socket 1: +no product info available + PccardctlStatus: + Socket 0: +no card + Socket 1: +3.3V 32-bit PC Card + ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=/dev/mapper/hostname-root ro quiet splash + ProcEnviron: + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 + Regression: No + RelatedPackageVersions: linux-firmware 1.34 + Reproducible: Yes + RfKill: + + StagingDrivers: rt2860sta + Tags: lucid ubuntu-une networking needs-upstream-testing staging + Title: [STAGING] + Uname: Linux 2.6.32-21-generic i686 + UserGroups: sudo + dmi.bios.date: 06/17/2002 + dmi.bios.vendor: Phoenix/FUJITSU + dmi.bios.version: Version 1.24 + dmi.board.name: FJNB150 + dmi.board.vendor: FUJITSU + dmi.chassis.type: 10 + dmi.chassis.vendor: FUJITSU SIEMENS + dmi.modalias: dmi:bvnPhoenix/FUJITSU:bvrVersion1.24:bd06/17/2002:svnFUJITSUSIEMENS:pnLIFEBOOKBSeries:pvr:rvnFUJITSU:rnFJNB150:rvr:cvnFUJITSUSIEMENS:ct10:cvr: + dmi.product.name: LIFEBOOK B Series + dmi.sys.vendor: FUJITSU SIEMENS ** Attachment added: AlsaDevices.txt
[Bug 564629] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/46553017/BootDmesg.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/46553021/Card0.Amixer.values.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] Card0.Amixer.info.txt
apport information ** Attachment added: Card0.Amixer.info.txt http://launchpadlibrarian.net/46553019/Card0.Amixer.info.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] Card0.Codecs.codec97.0.ac97.0.0.regs.txt
apport information ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt http://launchpadlibrarian.net/46553124/Card0.Codecs.codec97.0.ac97.0.0.regs.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] Card0.Codecs.codec97.0.ac97.0.0.txt
apport information ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt http://launchpadlibrarian.net/46553032/Card0.Codecs.codec97.0.ac97.0.0.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] Lspci.txt
apport information ** Attachment added: Lspci.txt http://launchpadlibrarian.net/46553137/Lspci.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/46553138/PciMultimedia.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/46553135/CurrentDmesg.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] IwConfig.txt
apport information ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/46553136/IwConfig.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/46553142/ProcCpuinfo.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/46553144/ProcInterrupts.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] ProcModules.txt
apport information ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/46553145/ProcModules.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] UdevDb.txt
apport information ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/46553147/UdevDb.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] UdevLog.txt
apport information ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/46553156/UdevLog.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/46553270/WifiSyslog.txt -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] Re: rt2860 cardbus can't connect: Association request to the driver failed
with 2.6.34-rc4, the symptoms are exactly the same: on boot, the association appears to succeed, and on the router I can see that an IP address is being allocated to 00:0c:f6:37:be:29, which is the macaddress of wlan0. But this IP address, although distributed by the server, is never allocated on the client. I can see in daemon.log: Apr 30 12:41:51 pixie wpa_supplicant[607]: Trying to associate with 00:1d:7e:c6:9c:24 (SSID='WRT-AS24' freq=2412 MHz) Apr 30 12:41:51 pixie wpa_supplicant[607]: Association request to the driver failed And syslog shows messages like: Apr 30 12:43:36 pixie kernel: [ 670.015997] ===rt_ioctl_giwscan. 5(5) BSS returned, data-length = 677 Apr 30 12:43:36 pixie kernel: [ 670.016588] ==rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Apr 30 12:43:41 pixie kernel: [ 675.341534] ===rt_ioctl_giwscan. 6(6) BSS returned, data-length = 853 Apr 30 12:43:41 pixie kernel: [ 675.342073] ==rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) lad...@pixie:~$ uname -a Linux pixie 2.6.34-020634rc4-generic #020634rc4 SMP Mon Apr 19 09:38:39 UTC 2010 i686 GNU/Linux lad...@pixie:~$ iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 00:1D:7E:C6:9C:24 Protocol:802.11g ESSID:WRT-AS24 Mode:Managed Channel:1 -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] Re: rt2860 cardbus can't connect: Association request to the driver failed
** Tags removed: needs-upstream-testing -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 564629] [NEW] rt2860 cardbus can't connect: Association request to the driver failed
Public bug reported: This might very well be a duplicate of #496093, but I'm reporting a new bug because: - I'm using the pcmcia module, which no other reporter seems to have - my issue is not fixed with v2.3.0 from the Ralink website - I'm already using a WPA2-only access point (or I don't know how to configure OpenWRT correctly) - I have not run any Linux before on this notebook, so I can't tell whether it is a regression lspci info: 05:00.0 Network controller: RaLink RT2800 802.11n PCI Subsystem: SiteCom Europe BV Device 0015 Flags: bus master, slow devsel, latency 64, IRQ 9 Memory at 1c00 (32-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Kernel driver in use: rt2860 Kernel modules: rt2860sta 05:00.0 0280: 1814:0601 Subsystem: 182d:0015 lad...@pixie:~$ modinfo rt2860sta filename: /lib/modules/2.6.32-21-generic/kernel/drivers/net/wireless/rt2860sta.ko version:2.3.0.0 license:GPL srcversion: 73F7AA771D91BB10E13F38D But I'm still getting this in syslog: Apr 16 13:28:08 pixie wpa_supplicant[1659]: Trying to associate with 00:1d:7e:c6:9c:24 (SSID='WRT-AS24' freq=2412 MHz) Apr 16 13:28:08 pixie kernel: [ 723.024400] ===rt_ioctl_giwscan. 7(7) BSS returned, data-length = 1023 Apr 16 13:28:08 pixie kernel: [ 723.024972] ==rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1) Apr 16 13:28:08 pixie wpa_supplicant[1659]: Association request to the driver failed Apr 16 13:28:08 pixie wpa_supplicant[1659]: Associated with 00:1d:7e:c6:9c:24 Apr 16 13:28:08 pixie wpa_supplicant[1659]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Apr 16 13:28:08 pixie wpa_supplicant[1659]: last message repeated 3 times Whereas with the original driver (1.1.8? from kernel 2.6.32-21) I got: Apr 16 12:36:14 pixie wpa_supplicant[741]: Trying to associate with 00:1d:7e:c6: 9c:24 (SSID='WRT-AS24' freq=2412 MHz) Apr 16 12:36:14 pixie wpa_supplicant[741]: Association request to the driver failed Apr 16 12:36:14 pixie wpa_supplicant[741]: Associated with 00:1d:7e:c6:9c:24 Apr 16 12:36:17 pixie wpa_supplicant[741]: WPA: Key negotiation completed with 0 0:1d:7e:c6:9c:24 [PTK=CCMP GTK=CCMP] Apr 16 12:36:17 pixie wpa_supplicant[741]: CTRL-EVENT-CONNECTED - Connection to 00:1d:7e:c6:9c:24 completed (auth) [id=0 id_str=wlan-loos] Apr 16 12:40:47 pixie wpa_supplicant[741]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Apr 16 12:40:53 pixie wpa_supplicant[741]: Failed to initiate AP scan. Apr 16 12:41:08 pixie wpa_supplicant[741]: Trying to associate with 00:1d:7e:c6:9c:24 (SSID='WRT-AS24' freq=2412 MHz) Apr 16 12:41:08 pixie wpa_supplicant[741]: Association request to the driver failed This all worked correctly in Windows (which I no longer have), and my game console connects to the access point without trouble. I don't have other access points to try right now. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- rt2860 cardbus can't connect: Association request to the driver failed https://bugs.launchpad.net/bugs/564629 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 410401] Re: [r300 KMS] modesetting not accepted by monitor
Just a quick update: the original problem (wrong signal clocks) has been fixed upstream and the bug no longer appears with a 2.6.33 kernel (haven't tried a .32 kernel recently). There is only a minor issue remaining with load detection, which causes the monitors to blink when probing outputs (occurs when starting g-s-d or totem for example). -- [r300 KMS] modesetting not accepted by monitor https://bugs.launchpad.net/bugs/410401 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 489998] [NEW] default tmpfs configuration uses 250% of available memory
Public bug reported: Binary package hint: sysvinit here is an excerpt from $df -h on my current karmic system: udev 3.0G 328K 3.0G 1% /dev none 3.0G 0 3.0G 0% /dev/shm tmpfs 2.4G 366M 2.0G 16% /tmp none 3.0G 212K 3.0G 1% /var/run none 3.0G 0 3.0G 0% /var/lock none 3.0G 0 3.0G 0% /lib/init/rw This setup allows any local user to allocate 15G of system memory (to be exact, 5x 50% in a default install - /tmp is mounted via a line in fstab), potentially bringing the system to a complete halt. Please set sane filesystem limits, or allow a local administrator to change these limits. Debian does this through the /etc/defaults/tmpfs file, but that file has no effect on Ubuntu. I have not been able to find which package is responsible for mounting these various tmpfs mounts; /dev is mounted by initramfs-tools, but there seems to be no init script that governs the creation of the other tmpfs mounts. ** Affects: sysvinit (Ubuntu) Importance: Undecided Status: New -- default tmpfs configuration uses 250% of available memory https://bugs.launchpad.net/bugs/489998 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 403291] Re: Unable to change the default session for GDM
Martin Pitt wrote: [...] Right now, you can't have both xubuntu-default-settings and mythbuntu- default-settings installed at the same time. I'm afraid I'm just pointing out the elephant in the room here, but my point wasn't about the *-default-settings packages: as it stands now for karmic, it's not possible to install mythbuntu-desktop and xubuntu-desktop alongside each other. I'm fine with whatever your solution will be. Am I to understand that this will not be fixed in karmic? In that case I'll just put the -default-settings packages on hold for the next few months, to prevent aptitude from trying to fix this by removing a -desktop package. -- Unable to change the default session for GDM https://bugs.launchpad.net/bugs/403291 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 403291] Re: Unable to change the default session for GDM
Please take care that both of you add
Provides: ubuntu-derivative-default-settings
Conflicts: ubuntu-derivative-default-settings
to avoid settings fighting each other and file-conflicting over
default.session.
I'm sorry, I don't think that is an acceptable workaround. Take a look
at what happens on a system with both mythbuntu-desktop and xubuntu-
desktop installed:
sa...@satyr:~$ sudo aptitude -f install
[...]
The following packages are BROKEN:
xubuntu-desktop
[...]
The following packages will be REMOVED:
xubuntu-default-settings{p}
[...]
xubuntu-desktop: Depends: xubuntu-default-settings but it is not installable
The following actions will resolve these dependencies:
Remove the following packages:
xubuntu-desktop
[...]
sa...@satyr:~$ sudo aptitude -f install xubuntu-default-settings+M
[...]
The following packages are BROKEN:
mythbuntu-desktop
The following packages will be REMOVED:
mythbuntu-default-settings{a}
The following packages will be upgraded:
xubuntu-default-settings
[...]
mythbuntu-desktop: Depends: mythbuntu-default-settings but it is not
installable
The following actions will resolve these dependencies:
Remove the following packages:
mythbuntu-desktop
sa...@satyr:~$ aptitude why xubuntu-default-settings
iB xubuntu-desktop Depends xubuntu-default-settings
sa...@satyr:~$ aptitude why mythbuntu-default-settings
i mythbuntu-desktop Depends mythbuntu-default-settings
I think, if you're going to take this route, that the Depends of both packages
need to weaken their Depend into a Recommends. That will probably bring a host
of other problems with it, but it is safer than breaking installations, imho.
--
Unable to change the default session for GDM
https://bugs.launchpad.net/bugs/403291
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 403291] Re: Unable to change the default session for GDM
Oh, I saw too late that this bug hasn't been updated in over a month. If you want me to open a new bugreport instead, please let me know. Regards, Arno -- Unable to change the default session for GDM https://bugs.launchpad.net/bugs/403291 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 410401] Re: [r300 KMS] modesetting not accepted by monitor
** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New I think you meant xserver-xorg-video-radeon, right? -- [r300 KMS] modesetting not accepted by monitor https://bugs.launchpad.net/bugs/410401 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 401146] [NEW] ubuntu-standard should recommend xfsprogs
Public bug reported: current ubuntu-standard (1.154) recommends reiserfsprogs, but does not do the same for xfsprogs. Given that Xfs and Reiserfs are equal in terms of goal and function, I don't see a reason why they should be treated differently. Could xfsprogs be added to the Recommends-list of -standard? ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- ubuntu-standard should recommend xfsprogs https://bugs.launchpad.net/bugs/401146 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 186193] Re: soundgraph imon LCD not recognized
If the original request concerns the same iMon LCD display that I have, there is no way to power down the display when the PC goes to sleep or even poweroff. This is because my display is tied to an IR receiver that is able to power on the machine via a button on the remote, thus the device is powered even when the PC is switched off. However, there is a solution that will result in a blank LCD screen, which is as good as it gets. Edit /etc/LCDd.conf and search for the line(s) GoodBye=, and change them to contain only spaces. My display is 2 lines of 16 characters, so my LCDd.conf contains: GoodBye= GoodBye= -- soundgraph imon LCD not recognized https://bugs.launchpad.net/bugs/186193 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 186193] Re: soundgraph imon LCD not recognized
Ouch, launchpad ate my whitespace. There should be sixteen spaces between the quotes. -- soundgraph imon LCD not recognized https://bugs.launchpad.net/bugs/186193 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 311890] Re: imon driver does not work, irw crashes lircd
Several Soundgraph iMon models are only supported since lirc 0.8.4, which is included in 9.04 (Jaunty). You could try using intrepid- backports, but I'm not sure if the kernel modules are backported as well. I'm currently using a pre-release of lirc 0.8.5, but my device gets recognized correctly: r...@satyr:/etc/init.d# dmesg | grep -i imon [ 30.264999] Driver for Soundgraph iMON MultiMedia IR/Display, v0.5 [ 30.265028] imon_probe: found iMON device [ 30.265086] imon_probe: Registered iMON driver(minor:0) [ 30.265123] imon_probe: iMON device on usb9:3 initialized [ 30.265131] imon_probe: found iMON device [ 30.265158] imon_probe: Registered iMON driver(minor:1) [ 30.265179] imon_probe: iMON device on usb9:3 initialized [ 30.265192] usbcore: registered new interface driver lirc_imon I also had to use a small patch to the init script to fix stability issues in lirc (it would sometimes stop responding after a while). I'll attach it, but it should not be necessary and I haven't yet figured out why it solves my problems. ** Attachment added: patch to remove output socket from slave lircd http://launchpadlibrarian.net/25995143/init.d-lirc.diff -- imon driver does not work, irw crashes lircd https://bugs.launchpad.net/bugs/311890 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 213053] Re: Totem is 'uninterruptible'
I ran into this same (well, appears to be same) bug with a Debian kernel (2.6.26). See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515009 Like this bug, I have been unable to reproduce it or even stumble upon it a second time. ** Bug watch added: Debian Bug tracker #515009 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515009 -- Totem is 'uninterruptible' https://bugs.launchpad.net/bugs/213053 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 355341] [NEW] initramfs: missing reiserfs module
Public bug reported: Binary package hint: initramfs-tools After dist-upgrading to Jaunty (from Intrepid), I was unpleasantly surprised by the kernel boot giving me a Busybox prompt in initramfs: it failed to mount the root filesystem. Performing a 'cat /proc/filesystems' revealed no presence of reiserfs module, and 'modprobe reiserfs' gave me an error code of 1. What's even more annoying, is that all installed kernels had their initramfs re-generated, so none of the options would boot. I'm currently downloading a rescue disc, after which I'll investigate more. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- initramfs: missing reiserfs module https://bugs.launchpad.net/bugs/355341 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 355341] Re: initramfs: missing reiserfs module
probably just a fluke. I have another two or three systems that will need dist-upgrading soon, will reopen if it happens again ** Changed in: initramfs-tools (Ubuntu) Status: New = Invalid -- initramfs: missing reiserfs module https://bugs.launchpad.net/bugs/355341 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 355341] Re: initramfs: missing reiserfs module
As it turns out, the initramfs of both kernels (2.6.27 and 2.6.28) did not contain any modules. I'm not sure what happened or what went wrong, but somehow the dist-upgrade process seems to have missed the entire rebuild after modules installation event. After booting into my system, a simple $ update-initramfs -c -k `uname -r` was enough to create a fully-working system again. a...@master:~$ zcat /boot/initrd.img-2.6.27-11-generic | cpio -t | grep lib/mod 19733 blocks lib/modules lib/modules/2.6.27-11-generic a...@master:~$ zcat /boot/initrd.img-2.6.28-11-generic | cpio -t | grep lib/mod 44596 blocks lib/modules lib/modules/2.6.28-11-generic lib/modules/2.6.28-11-generic/kernel [... snip all modules ...] -- initramfs: missing reiserfs module https://bugs.launchpad.net/bugs/355341 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 243958] Re: Multiple return values from dbus_method return multiple times the first value
Already fixed upstream -- Multiple return values from dbus_method return multiple times the first value https://bugs.launchpad.net/bugs/243958 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 57789] Re: Crossfading option causes skipping
Testing 2.0 would mean to try Jaunty, and I have no machines on Jaunty yet So I moved one of my machines over to jaunty (well, only kubuntu-desktop really) and guess what: there is no crossfade option in Amarok2! So it appears to be fixed, isn't it? Or am I doing something terribly wrong here? In Amarok 2.0.1, build date Feb 27, I can find in the Configure Amarok menu, the following options: Fadeout and Resume playback on start. Is the fadeout option supposed to enable crossfading as well? -- Crossfading option causes skipping https://bugs.launchpad.net/bugs/57789 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to amarok in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 57789] Re: Crossfading option causes skipping
You mean you can't reproduce it yourself? Besides, this bug is present Hardy as well, and since that is an LTS release it should have long been confirmed, even if it is fixed in 2.0. Testing 2.0 would mean to try Jaunty, and I have no machines on Jaunty yet. Will report back when I have. But considering the fact that this bug has existed since at least 2006 and FAFAIK was never reported upstream, I have zero confidence that it is fixed in 2.0 (there is one possibility, though: if the error is triggered by the Xine engine, it might have been fixed by Phonon). -- Crossfading option causes skipping https://bugs.launchpad.net/bugs/57789 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 57789] Re: Crossfading option causes skipping
Amarok upstream here. Welcome! Glad to know I was wrong about that. It was reported upstream as you can see in the bugwatch at the top of this page. The link at the top refers to a bug report that is older than this one. To be exact, the upstream report was closed a month before this bug report was opened. Now I can appreciate some lag between an upstream release and inclusion in Ubuntu, but #110814 was fixed in 1.3-SVN by commit 451292 in August 2005. Since everyone here experiences this bug in 1.4, either this is a regression, or it was never really fixed, or it was fixed only on the 1.3 branch. Either way, I have not found a newer upstream bug report that deals with this issue. It should indeed be fixed in Amarok 2. Let's hope so. Will a fix be backported to Hardy (Amarok 1.4)? -- Crossfading option causes skipping https://bugs.launchpad.net/bugs/57789 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check
@cevatcethun : are you sure you are running 8.10 (intrepid)? In comment 257, you said that you're running 8.04, which shouldn't be affected by this bug. So maybe you're seeing the effects of another bug? The alsa-utils fix works for me as well. Thanks to all involved! -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically due to internal alsa-plugins pulse check https://bugs.launchpad.net/bugs/274995 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 295136] Re: amixer timeout when muting sound card
*** This bug is a duplicate of bug 274995 *** https://bugs.launchpad.net/bugs/274995 Good catch! I hadn't thought about testing ipv6 resolution. It does explain why amixer tries to resolve localhost even though an IPv4 entry for it exists in /etc/hosts. Perfect. I guess the missing search statement prevent dns lookup because the software didn't have an FQDN, only localhost. -- amixer timeout when muting sound card https://bugs.launchpad.net/bugs/295136 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
I have to agree with Robb here. I have been bitten by this bug (#274995), but I don't have Intel HDA onboard sound - I have a Terratec EWS88 (module snd_ice1712). So if #126140 only applies to Intel onboard sound, it is most certainly not a duplicate of this bug. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 295136] Re: amixer timeout when muting sound card
Yes, I agree that the problem seems to be related to pulseaudio (it is the only part of the sound system that includes networking), but I really like pulse and don't want to uninstall it. Aside from that, I'm really not sure what the application is doing. In the strace above, you can see that amixer is talking on port 53, which is DNS, and is trying to resolve localhost. I have found that I had an incorrect entry in /etc/hosts (it mentioned localhost.localdomain while amixer was trying to resolve localhost.loos.site), which I thought would explain it. However, I have since corrected my /etc/hosts and the problem didn't go away. There are a few things I'd still like to try, and I'll probably get to it this weekend: - removing/commenting out everything in /usr/share/alsa/pulse.conf - which should prevent pulseaudio from being loaded - removing the mdns references in /etc/nsswitch.conf - which I think is causing the slowdown - removing the search-domain entry in /etc/resolv.conf - to see if it is the search entry that causes the spurious dns requests -- amixer timeout when muting sound card https://bugs.launchpad.net/bugs/295136 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 295136] Re: amixer timeout when muting sound card
It seems I can't help myself :) Here are the results: - commenting out everything in /usr/share/alsa/pulse.conf: amixer responds fast - removing the mdns references in /etc/nsswitch.conf no change. However, removing dns does work. So the bug is likely in libnss_dns, which is part of glibc itself. - removing the search entry in /etc/resolv.conf amixer responds fast So it seems that the bug is that with a search-domain present in /etc/resolv.conf, the nameserver is always contacted, even when the correct information can be found in /etc/hosts. Removing the search statement is my workaround of choice, I don't think it will have any impact on home users. However, my guess is that /etc/resolv.conf is auto-generated by dhclient. Can anyone confirm that? -- amixer timeout when muting sound card https://bugs.launchpad.net/bugs/295136 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
can anyone confirm whether they have a search ... statement in /etc/resolv.conf, and whether removing that statement fixes the delays? It's not really a workaround, because that file will be regenerated if you use dhcp, but it does add an additional point of information. -- MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up https://bugs.launchpad.net/bugs/274995 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 231950] Re: playbin2 pipeline fails to start
It appears to be fixed in 8.10. Repeating the above command results in noise from the speakers and this terminal output: [EMAIL PROTECTED]:~$ gst-launch-0.10 playbin2 uri=file:///usr/share/sounds/alsa/Noise.wav Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstAudioSinkClock Got EOS from element playbin20. Execution ended after 1528350575 ns. Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... FREEING pipeline ... Also note, that playbin2 is not an official gstreamer element. If I understood correctly, it is kind of in beta status. It's slated to replace the old playbin element once it is matured, at which time it will be renamed to playbin. -- playbin2 pipeline fails to start https://bugs.launchpad.net/bugs/231950 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 295136] [NEW] amixer timeout when muting sound card
Public bug reported: After dist-upgrading to intrepid, Ubuntu appears to hang when shutting down. I have traced this down to the ALSA shutdown script taking more than a minute (!) to save sound card state. More specifically: [EMAIL PROTECTED]:~$ time amixer -c0 -q set Mic 0% mute real0m8.061s user0m0.003s sys 0m0.012s This is reproducable only in single-user mode. When I run the amixer command when logged in into X (I can even run the command from a console, as long as X is running), the same command takes only a few milliseconds as it should. I will attach an strace log from above call. Of interest is the following line: 4.013297 ioctl(5, FIONREAD, [37]) = 0 which occurs twice in the script. It seems to be expecting data from a network socket, but I can't figure out why. On a side note: why is amixer doing dns resolution, or any network activity for that matter? ** Affects: alsa-utils (Ubuntu) Importance: Undecided Status: New -- amixer timeout when muting sound card https://bugs.launchpad.net/bugs/295136 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 295136] Re: amixer timeout when muting sound card
** Attachment added: strace -r log of amixer run http://launchpadlibrarian.net/19456415/amixer.log.gz -- amixer timeout when muting sound card https://bugs.launchpad.net/bugs/295136 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 295136] Re: amixer timeout when muting sound card
** Attachment added: output of sudo lshw http://launchpadlibrarian.net/19456456/amix-hw.log.gz -- amixer timeout when muting sound card https://bugs.launchpad.net/bugs/295136 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 295136] Re: amixer timeout when muting sound card
I just found out the official live cd (ubuntu-8.10-desktop-amd64.iso) exhibits the same behaviour on a laptop I am currently testing on; as this is a bog-standard Sony Vaio laptop (Centrino platform, core2duo), I'm afraid this might be a much more widespread problem than just my system. Maybe a more alarming bug description might be warranted, along the lines of Ubuntu freezes during shutdown process... -- amixer timeout when muting sound card https://bugs.launchpad.net/bugs/295136 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 295136] Re: amixer timeout when muting sound card
** Attachment added: lshw output of Vaio laptop http://launchpadlibrarian.net/19474256/vaio-hw.log.gz -- amixer timeout when muting sound card https://bugs.launchpad.net/bugs/295136 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 274995] Re: MASTER storing ALSA mixer element values during shutdown hangs nondeterministically if non-loopback network interfaces are still up
see #295136. The problem is actually in the amixer executable, which
gets invoked about 15 times during shutdown. The problem is reproducable
(for me) by running amixer in single-user mode. strace log can be found
in the mentioned report.
For reference, see the following note in the news section on
http://0pointer.de/lennart/projects/nss-mdns/:
Please note that due to security reasons from this release on the minimal mDNS
stack included in nss-mdns (dubbed legacy) is no longer built by default.
Thus, nss-mdns will not work unless Avahi is running! That makes Avahi
essentially a hard dependency of nss-mdns.
And see the following lines in the strace log:
0.69 open(/lib/libnss_mdns4_minimal.so.2, O_RDONLY) = 5
0.69 connect(5, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr(192.168.1.1)}, 28) = 0
4.013297 ioctl(5, FIONREAD, [37]) = 0
That still does not answer the question why the ** amixer needs to do
dns resolution in the first place...
--
MASTER storing ALSA mixer element values during shutdown hangs
nondeterministically if non-loopback network interfaces are still up
https://bugs.launchpad.net/bugs/274995
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 278202] [NEW] xorg-driver-fglrx: broken package
Public bug reported: I'm not sure this should be filed against fglrx-installer, but I'm going to anyway, because this is where people will search first. This concerns the latest intrepid release, that has been invalidated on purpose because there simply is no fglrx version that works with the X version shipped in Intrepid. As noted in the package history: fglrx-installer (2:8.532-0ubuntu5) intrepid; urgency=low * control: xorg-driver-fglrx Provides: xserver-xorg-video-2. The driver doesn't work with the current xserver, so no reason to pretend that it would. This prevents breaking upgrades from hardy where the driver would be updated and on reboot X would fail. Now, the problem is the following: apt is not being helpful. Take a look at the following console output: [EMAIL PROTECTED]:~# apt-get -Vy dist-upgrade [...] The following packages have been kept back: xorg-driver-fglrx (8.532-0ubuntu2 = 8.532-0ubuntu5) 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. [EMAIL PROTECTED]:~# apt-get install xorg-driver-fglrx [...] The following packages have unmet dependencies: xorg-driver-fglrx: Depends: xserver-xorg-core but it is not going to be installed E: Broken packages [EMAIL PROTECTED]:~# dpkg -l xserver-xorg-core [...] ii xserver-xorg-c 2:1.5.1-1ubunt Xorg X server - core server [EMAIL PROTECTED]:~# wget http://nl.archive.ubuntu.com/ubuntu/pool/multiverse/f/fglrx-installer/xorg-driver-fglrx_8.532-0ubuntu5_amd64.deb [...] [EMAIL PROTECTED]:~# dpkg -i xorg-driver-fglrx_8.532-0ubuntu5_amd64.deb dpkg: regarding xorg-driver-fglrx_8.532-0ubuntu5_amd64.deb containing xorg-driver-fglrx: xserver-xorg-core conflicts with xserver-xorg-video-2 xorg-driver-fglrx provides xserver-xorg-video-2 and is to be installed. dpkg: error processing xorg-driver-fglrx_8.532-0ubuntu5_amd64.deb (--install): conflicting packages - not installing xorg-driver-fglrx Errors were encountered while processing: xorg-driver-fglrx_8.532-0ubuntu5_amd64.deb apt is informing the user only indirectly that installing the fglrx driver will uninstall xserver-xorg-core. It should mention the conflict explicitly, like dpkg does. Note that even dpkg does not tell the entire situation, it fails to mention that fglrx depends on xserver-xorg-core. I understand that the current method achieves the desired goal, but it leaves the user hanging and wondering why it doesn't install. Can the package description be changed to inform users that the broken package is intentional? Or maybe, can apt be changed to explicitly tell the user that a package will be removed, instead of only not going to be installed? ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New -- xorg-driver-fglrx: broken package https://bugs.launchpad.net/bugs/278202 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 269656] Re: AN IRRELEVANT LICENSE IS PRESENTED TO YOU FREE-OF-CHARGE ON STARTUP
In light of the recent comments, I'm starting to see the additional problems with having firefox as-is in main, especially with the web services enabled by default. Indeed, like Chip pointed out, Firefox with web services cannot be freely used without taking note of its use restrictions. I do accept Marks premise that web services are fundamentally of a different nature than applications, and therefore can not be treated the same. But the bottom line remains the same: with anti-phishing enabled by default, Ubuntu is shipping a piece of software in main that has use restrictions in a default install (quoting from the draft Web Services Agreement: [...] which are [...] made available subject to the terms below). That's tough to reconcile with Ubuntu's promise of using only open/free software. On the one hand, requiring the user to take positive action in order to *disable* a web service he does not agree to is the wrong approach, but on the other hand, the users most likely to fall prone to phishing are the ones that will probably never go to the preferences dialog to enable the feature. Finally, there is one other point I feel I should comment on: [...] there is no GPL for Services but we expect one to emerge over the next few years, and this work by Mozilla is an important first step. The GPL is not a use license: you can use the software without even being aware of the license. Like others have said, there is a GPL for services (Affero GPL) but at its core it's still a distribution license, not a use license, since it obliges the implementor of a service to convey the source of the service to its users. I do not agree that Mozilla is working on a GPL for services because what we're having is still an end-user license. In fact, it's not even Mozilla's. The agreement governs a web service provided (hosted) by Google. -- AN IRRELEVANT LICENSE IS PRESENTED TO YOU FREE-OF-CHARGE ON STARTUP https://bugs.launchpad.net/bugs/269656 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 269656] Re: AN IRRELEVANT LICENSE IS PRESENTED TO YOU FREE-OF-CHARGE ON STARTUP
I am impressed with the solution that has sprung forward, even if it is only a mockup. I already commented on them, we'll have to wait how the final version pans out. I'm wondering how much Canonical had a hand in that mockup. I guess we'll never know :). Either way, it looks like the Mozilla/Canonical collaboration is a succesful one. And I'd like to think that we (the community) did have a hand in the end result. I'd like to thank you, Mark (and other Ubuntu and Mozilla officials as well) for still attending this bug in spite of the low signal-to-noise ratio. With regards to the question by lord_alan about shipping Firefox with web services switched off by default: as a system admin you can do this yourself via /etc/firefox-3.0/pref/firefox.js: pref(browser.safebrowsing.enabled, false); pref(browser.safebrowsing.malware.enabled, false); Considering how things are now with the services agreement, I don't think it will be necessary to ship with them turned off. -- AN IRRELEVANT LICENSE IS PRESENTED TO YOU FREE-OF-CHARGE ON STARTUP https://bugs.launchpad.net/bugs/269656 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 255582] Re: gnome-settings-daemon crashed with signal 5 in xkl_process_error()
can this possibly be a duplicate of #254671 ? The backtrace listed above is incomplete, but it seems to be following the same codepath as the aforementioned bug. The only difference I can see is that this bug is not triggered automatically on login, is that correct? -- gnome-settings-daemon crashed with signal 5 in xkl_process_error() https://bugs.launchpad.net/bugs/255582 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 255889] Re: jockey-gtk crashed with DBusException in call_blocking()
I have found this happens with both jockey-gtk and jockey-kde on my system (up to date as of an hour ago). -- jockey-gtk crashed with DBusException in call_blocking() https://bugs.launchpad.net/bugs/255889 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 57789] Re: Crossfading option causes skipping
Has this ever been reported upstream? The closest I could come to an upstream report is http://bugs.kde.org/show_bug.cgi?id=110814 but that has been resolved (presumably it only fixed the issues with the crossfade length). I'm using the dynamic playlists quite a lot, and have crossfading set to 4000ms. Amarok reliably skips every other song (plays one, skips one, etc). I can confirm that turning off crossfading makes the skipping go away, but skipping occurs in either dynamic or static playlists. Maybe another point of interest: my library is moderately sized (3000 songs), and I'm using mysql as database backend. This is on Intrepid, current as of a few hours ago. Amarok 1.4.10, build 14-8-2008. -- Crossfading option causes skipping https://bugs.launchpad.net/bugs/57789 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to amarok in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices
jnygaard wrote: No hurry... I had to do real work myself, so I simply put in a new PCI- based USB host adapter, and voila, disks work at full speed... Just for clarification: are you saying that with a new card plugged in, the old ports suddenly started playing nice to each other, or did you move all (some) of your devices over to the new controller? And FWIW, I don't think the problem is well understood yet; I'm not even sure everything can be traced down to one bug. So far we have: - several chipsets affected, all ohci-based - problems only seem to appear when a slow and a fast device are connected to the same usb controller - some affected machines have problems with usb-1.1 devices (Al, me) - they get error -62 in the logs - some affected machines have problems with usb-2.0 devices (Martin, Mika) - they get error -71 in the logs - some machines exhibit spurious usb reset signals instead/as well And several workarounds: - unloading the ehci module allows all devices to work reliably (but slow) - rearranging the devices (adding a hub, using a different port) can give better results J.O., would you be able to confirm if your devices still work if you attach some of them to the new ports, and others to the old (I guess on-board) ports? -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 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 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices
According to some of the duplicates, this error appears with certain uhci chipsets as well, however the error in those cases seems to be error -110. Also, I forgot to mention the workaround of disabling autosuspend. That also seems to work for only a few people (haven't tried it myself). -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 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 243958] [NEW] Multiple return values from dbus_method return multiple times the first value
Public bug reported: Binary package hint: libdbus-ruby Please take a look at upstream bug report https://trac.luon.net/ruby- dbus/ticket/23. I filed it just minutes ago, after I got bitten by it. The fix is relatively low-risk but has only received preliminary testing by myself. Any chance the proposed patch might find its way into the Ubuntu repositories before it is picked up by upstream? I know the preferred mode of operation is to wait for upstream to release a new version, but the project seems dormant at best. ** Affects: libdbus-ruby (Ubuntu) Importance: Undecided Status: New -- Multiple return values from dbus_method return multiple times the first value https://bugs.launchpad.net/bugs/243958 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 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices
I can confirm the workaround posted above, to connect the usb-1 devices via an external hub instead of directly on the root hub. Oddly enough, the usb hub I am using is usb-1 only; I would have expected the workaround to work only when using an usb-2 hub. -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 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 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices
USB events since boot sequence: [26] both ohci and ehci drivers loaded [27] ehci recognizes and activates LaCie external disk [28] ohci fails to activate mouse [160] plug-out-and-in logitech mouse; no recourse [570] rmmod ehci-hcd [571] ohci activates external disk on full speed [613] plug-out-and-in mouse; mouse activated [EMAIL PROTECTED]:~# lsusb Bus 002 Device 001: ID : Bus 001 Device 007: ID 046d:c00b Logitech, Inc. MouseMan Wheel Bus 001 Device 006: ID 059f:100d LaCie, Ltd Bus 001 Device 001: ID : ** Attachment added: output of dmesg | grep -i usb http://launchpadlibrarian.net/15621160/dmesg-usb.log -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 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 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices
I thought I'd chime in as well. This bug is old, seeing as how Bug #54273 is essentially the same bug. However, I have not been hit hard by this bug until today, under: [EMAIL PROTECTED]:~# uname -a Linux neminis 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 GNU/Linux My symptoms are a bit strange, though: I have no problems with my usb-2.0 external harddisk, but instead, Ubuntu fails to recognize my (usb-1.1) mouse until I unload the ehci module. Also, after various plug-in-and-out attempts I had my mouse activated, but pressing ctrl+alt+f7 to return to X caused an USB reset on all hubs, and killed my mouse again. By now, I'm guessing it's a timing-related issue, seeing as how a VT switch always causes a 2-second hang on my machine (I'm using the radeon driver, not fglrx). I'm not familiar with the usb protocol specs, but is it possible that the ehci driver sometimes fails to respond in a timely fashion? I'm attaching my lspci output. Needless to say, I have not changed any hardware since the last kernel upgrade. I did before have issues with my mouse not activating after a reboot, but that was always fixed by a plug-out-and-in sequence. Until the last update, that is. ** Attachment added: output of lspci -vv http://launchpadlibrarian.net/15621014/lspci-vv.log -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 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 231950] [NEW] playbin2 pipeline fails to start
Public bug reported: I'm trying to teach QuodLibet to support gapless playback, but I can't because the playbin2 element doesn't appear to work correctly in Hardy (the default playbin works as advertised, but doesn't support gapless): [EMAIL PROTECTED]:~$ gst-launch-0.10 playbin2 uri=file:///usr/share/sounds/alsa/Noise.wav Setting pipeline to PAUSED ... ERROR: Pipeline doesn't want to pause. Setting pipeline to NULL ... FREEING pipeline ... [EMAIL PROTECTED]:~$ gst-launch-0.10 --version gst-launch-0.10 version 0.10.18 GStreamer 0.10.18 https://launchpad.net/distros/ubuntu/+source/gstreamer0.10 I have compiled version 0.10.19 manually, and that works. I'm not sure that's because of a bugfix in 0.10.19, or due to different compile-time options (configured with ./configure --prefix=$HOME). This is probably very low impact (maybe even wish-list material), because I know of no audio players that already use the playbin2 pipeline instead of the old playbin. But it would be nice to get working nonetheless... ** Affects: gst-plugins-base0.10 (Ubuntu) Importance: Undecided Status: New -- playbin2 pipeline fails to start https://bugs.launchpad.net/bugs/231950 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 219888] Re: gnome-language-selector crashed with IOError in getSystemDefaultLanguage()
*** This bug is a duplicate of bug 210180 *** https://bugs.launchpad.net/bugs/210180 It would be nice if I would be allowed to view bug #210180. I understand the user has probably marked the bug as private, but I can't confirm or refute the duplicate status of this bug when I can't view it, can I? -- gnome-language-selector crashed with IOError in getSystemDefaultLanguage() https://bugs.launchpad.net/bugs/219888 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 183776] Re: gnome session fails to start after upgrading from 7.10 to 8.04
This appears to be similar to what I have seen so far on every PC that I
have upgraded from gutsy to hardy: after a dist-upgrade, GNOME only
appears to work in fail-safe mode. When I select GNOME in non-failsafe
mode, the login screen (kdm) disappears but the background stays the
blue background of kdm, and nothing happens. Viewing top in one of the
terminals reveals a 99% idle CPU; it's as if GNOME has become a large
black hole, and remains that way until I press ctrl-alt-backspace.
I run KDE as well on most of my boxes, and that works. Without problems.
Starting gnome-settings-daemon from a terminal gives the same hangs, a
lot of ALSA messages and a number of xrdb messages:
xrdb: *Label.background on line 220 overrides entry on line 150
xrdb: *Text.background on line 226 overrides entry on line 191
xrdb: *Label.foreground on line 232 overrides entry on line 151
xrdb: *Text.foreground on line 238 overrides entry on line 192
/usr/share/themes/Crux/gtk-2.0/gtkrc:37: Invalid symbolic color 'fg_color'
/usr/share/themes/Crux/gtk-2.0/gtkrc:37: error: invalid identifier `fg_color',
expected valid identifier
The strace log explains the hangs, but I don't understand why:
connect(23, {sa_family=AF_INET, sin_port=htons(16001),
sin_addr=inet_addr(127.0.0.1)}, 16) = -1 ETIMEDOUT (Connection timed out)
timeout on a localhost connection? What's supposed to be listening on
port 16001? There is no firewall active (all policies are ACCEPT).
According to some messages on the net, should this be esd?
[EMAIL PROTECTED]:~$ dpkg -S /usr/bin/esd
pulseaudio-esound-compat: /usr/bin/esd
[EMAIL PROTECTED]:~$ sudo netstat -ntlp | grep 16001
[no output]
I'll try to re-login to GNOME and search for port 16001 then.
(btw: the hangs also occur in KDE when I start certain gtk-based apps,
most notably firefox and gvim)
** Attachment added: strace log of gnome-settings-daemon (gzipped)
http://launchpadlibrarian.net/13586310/gnome-settings-daemon.log.gz
--
gnome session fails to start after upgrading from 7.10 to 8.04
https://bugs.launchpad.net/bugs/183776
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 183776] Re: gnome session fails to start after upgrading from 7.10 to 8.04
it appears the bug is due to pulseaudio being wrongly configured; even after manually starting pulseaudio (/usr/bin/esd is a wrapper for PA), there is no daemon listening on port 16001. However, I have found that GNOME does start after a timeout (appeared to be more than 30 seconds though?), if you happen to wait long enough. But that can also be due to two other factors: - I did a apt-get --reinstall install ubuntu-desktop before diving into this problem (which I believe pulled in some missing pulseaudio packages) - I manually started /usr/bin/esd from VT1 (but I'm assuming that's also done by the GNOME login script) PA is not running when I start a KDE session; manually starting PA gives the ALSA messages that I also mentioned in the previous post. Full PA output log attached. [EMAIL PROTECTED]:~$ LC_MESSAGES=C pulseaudio [...] ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM hw:0 E: alsa-util.c: Error opening PCM device hw:0: No such file or directory E: module.c: Failed to load module module-alsa-sink (argument: device_id=0 sink_name=alsa_output.pci_1106_3059_sound_card_0_alsa_playback_0): initialization failed. [...] ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM hw:1 E: alsa-util.c: Error opening PCM device hw:1: No such file or directory E: module.c: Failed to load module module-alsa-source (argument: device_id=1 source_name=alsa_input.usb_device_c45_60af_noserial_if1_sound_card_0_alsa_capture_0): initialization failed. ** Attachment added: pulseaudio output log http://launchpadlibrarian.net/13586594/pulseaudio.out -- gnome session fails to start after upgrading from 7.10 to 8.04 https://bugs.launchpad.net/bugs/183776 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 183776] Re: gnome session fails to start after upgrading from 7.10 to 8.04
(apologies for spamming this bug) ALSA does not work under KDE either; in KDE System Settings, the sound system is configured to use OSS. If I switch to ALSA, I get no error messages but I get no sound either... [EMAIL PROTECTED]:~$ lspci -vv 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60) Subsystem: Micro-Star International Co., Ltd. Unknown device b014 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Interrupt: pin C routed to IRQ 19 Region 0: I/O ports at d000 [size=256] Capabilities: access denied I think the problem (for me) now revolves around this issue: E: alsa-util.c: Error opening PCM device hw:0: No such file or directory -- gnome session fails to start after upgrading from 7.10 to 8.04 https://bugs.launchpad.net/bugs/183776 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 183776] Re: gnome session fails to start after upgrading from 7.10 to 8.04
Fixed for me: [EMAIL PROTECTED]:~$ alsamixer alsamixer: function snd_ctl_open failed for default: No such device [EMAIL PROTECTED]:~$ asoundconf list Names of available sound cards: V8237 camera [EMAIL PROTECTED]:~$ asoundconf set-default-card V8237 And after this, both alsamixer and pulseaudio start correctly. I can even select ESD in KDE System Settings, and it works. Both firefox and gvim start without slowdown, I'm confident that GNOME will now also start without problems. If not, I will report back. -- gnome session fails to start after upgrading from 7.10 to 8.04 https://bugs.launchpad.net/bugs/183776 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 183776] Re: gnome session fails to start after upgrading from 7.10 to 8.04
Sadly, it is not completely fixed. It seems that gnome-session does not start pulseaudio by itself when a user logs in. I have to login to a terminal and manually start pulseaudio before I can login to GNOME (yes, I can also wait for about 60 seconds, but I still won't have sound in GNOME then). However, my knowledge ends here. I have no clue how to debug the gnome- session startup scripts. All I know is that, when I want to log in to GNOME, I have to login to a terminal first and start PA manually. GNOME audio settings: all devices use PulseAudio, and software mixer (ESD) is checked. -- gnome session fails to start after upgrading from 7.10 to 8.04 https://bugs.launchpad.net/bugs/183776 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 219888] [NEW] gnome-language-selector crashed with IOError in getSystemDefaultLanguage()
Public bug reported: Binary package hint: language-selector Running a just-upgraded version of Hardy beta on i386. The first time I started the language-selector applet, it advised me that certain languages were incompletely installed, and I let it install the language support files for KDE for me (not sure if it installed the -en or the -nl packages). It advised me to reboot, which I did not do directly. Starting the language selector again caused a crash, which I did not report because I remembered I still had to reboot. But, after reboot, the language-selector still crashes... [EMAIL PROTECTED]:~$ locale LANG=nl_NL.UTF-8 LANGUAGE=nl_NL:nl LC_CTYPE=nl_NL.UTF-8 LC_NUMERIC=nl_NL.UTF-8 LC_TIME=nl_NL.UTF-8 LC_COLLATE=nl_NL.UTF-8 LC_MONETARY=nl_NL.UTF-8 LC_MESSAGES=nl_NL.UTF-8 LC_PAPER=nl_NL.UTF-8 LC_NAME=nl_NL.UTF-8 LC_ADDRESS=nl_NL.UTF-8 LC_TELEPHONE=nl_NL.UTF-8 LC_MEASUREMENT=nl_NL.UTF-8 LC_IDENTIFICATION=nl_NL.UTF-8 LC_ALL= I am aware of bug #88357, but it mentions an ImportError. I believe my crash was caused by an IOError instead, but I can't seem to view the apport crash details from this page (or can I?) ProblemType: Crash Architecture: i386 Date: Sun Apr 20 16:16:26 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/gnome-language-selector InterpreterPath: /usr/bin/python2.5 Package: language-selector 0.3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/gnome-language-selector ProcEnviron: LANGUAGE=nl_NL:nl PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=nl_NL.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/gnome-language-selector'] SourcePackage: language-selector Title: gnome-language-selector crashed with IOError in getSystemDefaultLanguage() Uname: Linux 2.6.24-16-generic i686 UserGroups: adm admin audio cdrom dialout dip fax floppy lpadmin plugdev scanner tape video ** Affects: language-selector (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash need-duplicate-check -- gnome-language-selector crashed with IOError in getSystemDefaultLanguage() https://bugs.launchpad.net/bugs/219888 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 219888] Re: gnome-language-selector crashed with IOError in getSystemDefaultLanguage()
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/13587482/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/13587483/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/13587484/ProcStatus.txt ** Attachment added: Traceback.txt http://launchpadlibrarian.net/13587485/Traceback.txt ** Visibility changed to: Public -- gnome-language-selector crashed with IOError in getSystemDefaultLanguage() https://bugs.launchpad.net/bugs/219888 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 219888] Re: gnome-language-selector crashed with IOError in getSystemDefaultLanguage()
The .desktop file (/usr/share/applications/language-selector.desktop) contains the following line: Exec=/usr/bin/gnome-language-selector Shoudn't this be started with gksu? Exec=gksu /usr/bin/gnome-language-selector -- gnome-language-selector crashed with IOError in getSystemDefaultLanguage() https://bugs.launchpad.net/bugs/219888 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 195055] Re: Hardy Alpha 5 fails to start on Asus F3Jp with ATI X1700
It's not just fglrx. I get the same white screen when using the ati driver. I can still log in using KDE as my window manager, but I can only get to Gnome when I use the failsafe mode, but it's dog-slow (read 2 seconds to focus a window) I believe this is caused by a bug in the compiz start script, but I'm not sure yet. I'll try to get some more info and post what I can find. -- Hardy Alpha 5 fails to start on Asus F3Jp with ATI X1700 https://bugs.launchpad.net/bugs/195055 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 195055] Re: Hardy Alpha 5 fails to start on Asus F3Jp with ATI X1700
Forgot my hardware: it's an ATI Technologies Inc RV516 [Radeon X1300/X1550 Series], and my system is up-to-date as of a few hours ago (let's say March 23rd, 19h00 GMT). I'm on 64bit, and using the fglrx driver seems to freeze my entire system (at least the video card part). So I can't test the other driver on this system. Btw I also found a report #194430 which says the problem went away when reinstalling. But I'm not going to go with that solution just yet. -- Hardy Alpha 5 fails to start on Asus F3Jp with ATI X1700 https://bugs.launchpad.net/bugs/195055 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 195055] Re: Hardy Alpha 5 fails to start on Asus F3Jp with ATI X1700
the .xsession-errors file when running Gnome (white screen situation). Some errors appear serious: /usr/bin/compiz.real (core) - Warn: Unable to parse XML metadata from file ccp.xml /usr/bin/gtk-window-decorator: Screen 0 on display :0.0 already has a decoration manager; try using the --replace option to replace the current decoration manager. And some appear less important: /etc/X11/Xsession.d/25enable-compiz: 3: [[: not found ERROR: trackerd already running on your session dbus - exiting... /usr/bin/compiz.real (core) - Error: Couldn't load plugin 'keybinding' ** (nautilus:17879): WARNING **: Unable to add monitor: Not supported I tried to get a session-errors file from the failsafe mode as well, but it seems there is none. Is that correct? ** Attachment added: .xsession-errors file when running Gnome (white screen situation) http://launchpadlibrarian.net/12829821/xsession-errors -- Hardy Alpha 5 fails to start on Asus F3Jp with ATI X1700 https://bugs.launchpad.net/bugs/195055 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 195055] Re: Hardy Alpha 5 fails to start on Asus F3Jp with ATI X1700
gzip'ed because of its size. I fail to notice anything of interest here. (oh, and concerning the previous xsession-errors: I have put a set -x line in the /usr/bin/compiz start script) ** Attachment added: Xorg.log file when running Gnome (white screen situation) http://launchpadlibrarian.net/12830241/Xorg.0.log.gz -- Hardy Alpha 5 fails to start on Asus F3Jp with ATI X1700 https://bugs.launchpad.net/bugs/195055 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 184805] misplaced TODO.gz in ubuntu hal package
Public bug reported: Binary package hint: hal This is actually so very minor that I can't believe I'm actually reporting it; there just aren't any more interesting things to report :) A file /usr/share/doc/TODO.gz is installed by the package, while the corresponding directory hal/ remains empty. [EMAIL PROTECTED]:~$ dpkg -S /usr/share/doc/TODO.gz hal: /usr/share/doc/TODO.gz [EMAIL PROTECTED]:~$ find /usr/share/doc/hal /usr/share/doc/hal [EMAIL PROTECTED]:~$ dpkg -s hal Package: hal Status: install ok installed [...] Version: 0.5.9.1-6ubuntu5 ** Affects: hal (Ubuntu) Importance: Undecided Status: New -- misplaced TODO.gz in ubuntu hal package https://bugs.launchpad.net/bugs/184805 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 183969] Re: xserver-xorg-core update breaks java wxwidgets apps
contrary to what Björn Streicher wrote earlier, I have the following in xorg.conf: Option Composite enable Option AccelMethod EXA Driver ati and VLC still crashes with a BadAlloc error (serial 476 error_code 11 request_code 146 minor_code 5) [EMAIL PROTECTED]:~$ dpkg -s xserver-xorg-core Package: xserver-xorg-core [...] Architecture: i386 Version: 2:1.3.0.0.dfsg-12ubuntu8.1 -- xserver-xorg-core update breaks java wxwidgets apps https://bugs.launchpad.net/bugs/183969 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 85554] Feisty usplash breaks X on Geforce5700
Public bug reported: Performed a dist-upgrade from Edgy-Feisty this morning. The upgrade went well, but after reboot, the screen would remain blank where usually GDM would appear. Ctrl-Alt-F[1-6] did not work, however the system was not frozen since num-lock still toggled and Ctrl-Alt-Delete worked. Booting in recovery mode worked, and I could also do a succesful startx as root. After trying some X configuration options I removed 'splash' from the kernel command-line, and this resolved the problem. I seems like usplash is somehow not releasing its console. I don't think it's limited to my video card (though I have no way of testing other cards). $ uname -a Linux master 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux $ dpkg -la usplash ii usplash0.4-41 Userspace bootsplash utility $ grep Driver /etc/X11/xorg.conf [...] Driver nv Note: I found multiple bugs similar to this one, but none seemed to target Feisty specifically (everything worked in Edgy). I'm sorry if this is a duplicate ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Feisty usplash breaks X on Geforce5700 https://launchpad.net/bugs/85554 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85554] Re: Feisty usplash breaks X on Geforce5700
Additional note: in 80x24 textmode, the monitor's OSD reports: 700x400, 61.5K, 70 (I assume resolution, Hrefresh, Vrefresh) When booting with Usplash, the mode changes to 1024x1024, 64K, 60 This mode is the same when X started succesfully (as it has now) When Usplash completes, the modeline reverts to the above 700x400 line and stays completely black. Also, when I press ctrl-alt-del, the X mouse cursor briefly appears before the Usplash shutdown theme takes over. -- Feisty usplash breaks X on Geforce5700 https://launchpad.net/bugs/85554 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
