[Bug 892906] Re: SD Card reader not working
Having tried the latest daily mainline kernel debs as of 2012-01-07, I can confirm this problem is still present on my system. My system is one of the Twinhead H12Y ones that requires the reserve=0xFFB0,0x10 I am running 64-bit. These are the relevant lines from lspci 03:06.0 FireWire (IEEE 1394) [0c00]: O2 Micro, Inc. Firewire (IEEE 1394) [1217:00f7] (rev 02) 03:06.2 SD Host controller [0805]: O2 Micro, Inc. Integrated MMC/SD Controller [1217:7120] (rev 01) 03:06.3 Mass storage controller [0180]: O2 Micro, Inc. Integrated MS/xD Controller [1217:7130] (rev 01) These are the relevant lines from load of sdhci-pci, note that I have an Unknown controller version. [ 434.613448] sdhci-pci :03:06.2: SDHCI controller found [1217:7120] (rev 1) [ 434.613476] sdhci-pci :03:06.2: PCI INT A - GSI 19 (level, low) - IRQ 19 [ 434.613512] mmc0: Unknown controller version (16). You may experience problems. [ 434.613532] mmc0: no vmmc regulator found [ 434.613582] Registered led device: mmc0:: [ 434.613646] mmc0: SDHCI controller on PCI [:03:06.2] using PIO No combination of debug_quirk, etc. I have tried has been able to get past the mmc0: Timeout waiting for hardware interrupt, though I have not been exhaustive. The lack of documentation makes it a little hard to be sure what any of the parameters are for without reading the entire sdhci tree, but none of the obviously named quirks helped. A thought though, is there perhaps a way to interact with this card that does not require interrupts for the transfer? At least as a workaround until this is fixed? ** Tags removed: kernel-unable-to-test-upstream needs-upstream-testing ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/892906 Title: SD Card reader not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/892906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 680135] Re: natty Intel Corporation Mobile 945GM/GMS, 943/940GML bad performance
A configuration option from an old guide to getting effects to work seems to help on my 945, that being Option Tiling False -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/680135 Title: natty Intel Corporation Mobile 945GM/GMS, 943/940GML bad performance -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348353] Re: Pulseaudio fails with Alsa a52 (ac3) plugin (Ubuntu 10.04 Lucid)
In trying to build from source, I had to patch debian/rules to pass --enable-avcodec=yes to configure before it would notice that I'd installed libavcodec-dev, I may have happened to do something else at the same time, but I doubt it. At the very least its something to look into to get it to build on the build system -- Pulseaudio fails with Alsa a52 (ac3) plugin (Ubuntu 10.04 Lucid) https://bugs.launchpad.net/bugs/348353 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 348353] Re: Pulseaudio fails with Alsa a52 (ac3) plugin (Ubuntu 10.04 Lucid)
Strike that, I didn't catch that it was running configure twice, I'm not sure just why, I was just using debian/rules binary, maybe there's something strange about how its built, I apologize, I should have checked more before commenting...wish there was an edit feature -- Pulseaudio fails with Alsa a52 (ac3) plugin (Ubuntu 10.04 Lucid) https://bugs.launchpad.net/bugs/348353 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 279197] [NEW] NetworkManager does not work with aircard 881U
Public bug reported: Binary package hint: network-manager Note that this is in the latest version of intrepid, latest packages as of 10/6/2008 Network Manager notices my 881U when I plug it in, and pops up its helpful wizard. I click through, selecting ATT (have tried the other ATT options too) and all seems well until I go to connect, at which point it simply instantly fails. Here is the relevant sections from /var/log/daemon.log: Oct 6 10:29:51 tymestl-eee-1000 NetworkManager: info Activation (ttyUSB0) starting connection 'ATT' Oct 6 10:29:51 tymestl-eee-1000 NetworkManager: info (ttyUSB0): device state change: 3 - 4 Oct 6 10:29:51 tymestl-eee-1000 NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Oct 6 10:29:51 tymestl-eee-1000 NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Oct 6 10:29:51 tymestl-eee-1000 NetworkManager: debug [1223314191.888144] nm_serial_device_open(): (ttyUSB0) opening device... Oct 6 10:29:51 tymestl-eee-1000 NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info (ttyUSB0): powering up... Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info Registered on Home network Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info Associated with network: +COPS: 0,0,ATT,2 Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: WARN set_apn_done(): Setting APN failed Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info (ttyUSB0): device state change: 4 - 9 Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: debug [1223314192.114943] nm_serial_device_close(): Closing device 'ttyUSB0' Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info Marking connection 'ATT' invalid. Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info Activation (ttyUSB0) failed. Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info (ttyUSB0): device state change: 9 - 3 Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info (ttyUSB0): deactivating device. Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx = 0' failed Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx = 0' failed For what its worth, it also doesn't use the correct USB port -- 0 and 2 are both usable for the 881U but 2 is the preferred one as then 0 can be used to query status while 2 is active for modem/ppp (1 is a proprietary status protocol) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: network-manager + + Note that this is in the latest version of intrepid, latest packages as + of 10/6/2008 Network Manager notices my 881U when I plug it in, and pops up its helpful wizard. I click through, selecting ATT (have tried the other ATT options too) and all seems well until I go to connect, at which point it simply instantly fails. Here is the relevant sections from /var/log/daemon.log: Oct 6 10:29:51 tymestl-eee-1000 NetworkManager: info Activation (ttyUSB0) starting connection 'ATT' Oct 6 10:29:51 tymestl-eee-1000 NetworkManager: info (ttyUSB0): device state change: 3 - 4 Oct 6 10:29:51 tymestl-eee-1000 NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Oct 6 10:29:51 tymestl-eee-1000 NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Oct 6 10:29:51 tymestl-eee-1000 NetworkManager: debug [1223314191.888144] nm_serial_device_open(): (ttyUSB0) opening device... Oct 6 10:29:51 tymestl-eee-1000 NetworkManager: info Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info (ttyUSB0): powering up... Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info Registered on Home network Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info Associated with network: +COPS: 0,0,ATT,2 Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: WARN set_apn_done(): Setting APN failed Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info (ttyUSB0): device state change: 4 - 9 Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: debug [1223314192.114943] nm_serial_device_close(): Closing device 'ttyUSB0' Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info Marking connection 'ATT' invalid. Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info Activation (ttyUSB0) failed. Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info (ttyUSB0): device state change: 9 - 3 Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: info (ttyUSB0): deactivating device. Oct 6 10:29:52 tymestl-eee-1000 NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx = 0' failed Oct 6 10:29:52 tymestl-eee-1000 NetworkManager:
[Bug 118723] KMilo/Volume Hotkeys regression
Public bug reported: Binary package hint: kmilo On Gutsy with the latest KMilo packages, the volume control is failing to work properly. This is due to it attempting to use the old setAbsoluteVolume on channel 0 instead of the new setMasterVolume (and the equivalent absoluteVolume/masterVolume 'get's) I've attached a patch which fixes kmilo here (I'm sure the format isn't right, but at least its a starting point). I hope to see this fixed soon, its a minor issue but important. ** Affects: kdeutils (Ubuntu) Importance: Undecided Status: Unconfirmed -- KMilo/Volume Hotkeys regression https://bugs.launchpad.net/bugs/118723 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 118723] Re: KMilo/Volume Hotkeys regression
I think I stripped out everything unimportant in it, this is the patch that fixes kmilo (at least for the generic case, which mine is) ** Attachment added: kmilofix.patch http://launchpadlibrarian.net/7962747/kmilofix.patch -- KMilo/Volume Hotkeys regression https://bugs.launchpad.net/bugs/118723 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 115014] Re: Kde System Settings Crashes (Backtrace attached)
*** This bug is a duplicate of bug 114286 *** https://bugs.launchpad.net/bugs/114286 This bug is caused by kdebase-data not installing a file it should due to config protection. The specific file is /etc/xdg/menus/kde- applications-merged/kde-essential.menu It is easy to fix by puge/reinstalling kdebase-data or installing with the proper --force option to dpkg -- Kde System Settings Crashes (Backtrace attached) https://bugs.launchpad.net/bugs/115014 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 115277] Re: Darter backlight buttons do not work
The bios version 305 (well actually a previous version but 305 is latest as of this posting) from www.asus.com (for the Z35Fm) resolves this issue as well, without the need for a new DSDT, and is quite likely a more suitable choice here. Obviously getting the bios loaded can be a hassle, but actually if you can repartition and make a small FAT partition, the bios has a built-in updater utility that can find the file (no boot needed, just go into the bios!) -- Darter backlight buttons do not work https://bugs.launchpad.net/bugs/115277 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 115277] Darter backlight buttons do not work
Public bug reported: This bug is (as usual) due to an invalid DSDT, in this case it calls some functions that do not exist, ending in _Q0E or _Q0F instead of the proper functions. I will attach a fixed DSDT (both source and compiled) to be used in /etc/initramfs-tools/DSDT.aml This is for the Darter Ultra only (and probably *some* asus z35fm models too) ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Darter backlight buttons do not work https://bugs.launchpad.net/bugs/115277 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 115277] Re: Darter backlight buttons do not work
** Attachment added: dsdt.dsl http://librarian.launchpad.net/7687487/dsdt.dsl -- Darter backlight buttons do not work https://bugs.launchpad.net/bugs/115277 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 115277] Re: Darter backlight buttons do not work
** Attachment added: dsdt.aml http://librarian.launchpad.net/7687488/dsdt.aml -- Darter backlight buttons do not work https://bugs.launchpad.net/bugs/115277 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 75616] Re: support suspend2 kernels in initramfs
The relevant code isn't there in the scripts as far as I can tell, did it get moved elsewhere (hardcoded into initramfs-tools perhaps?) For now I've dropped in these scripts -- support suspend2 kernels in initramfs https://bugs.launchpad.net/bugs/75616 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 56583] Re: [Bug 56583] Re: Gnome-session-manager crashes when some dbus apps run
Sorry, I meant to mention that. I use edgy, and one good example that triggers it is compiz, another being cgwd, I know they are both unsupported applications (at least the versions I run), but either way they should not be able to trigger a crash in gnome-session-manager. The best way I know of to trigger the crash is to stop and start one or both of them a few times. The crash is not 100% reliable, but will eventually happen. Because gnome-session-manager is the sm, it won't let any other apps start, so you won't see it crashed until you look in the process list and see that it spawned a bug-buddy, or see that you can't start any more X apps. On Thu, 17 Aug 2006 07:46:54 - Sebastien Bacher [EMAIL PROTECTED] wrote: Thanks for your bug. What version of Ubuntu do you use? Do you have a dbus application example triggering that crash? ** Changed in: gnome-session (Ubuntu) Assignee: (unassigned) = Ubuntu Desktop Bugs Status: Unconfirmed = Needs Info -- Gnome-session-manager crashes when some dbus apps run https://launchpad.net/bugs/56583 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56583] Gnome-session-manager crashes when some dbus apps run
Public bug reported: Binary package hint: gnome-session It appears its a pointer bug of some kind, bt follows. The bug might actually be in libdbus-glib, I'm not sure. The stuff above signal handler called is where it tried to launch bug-buddy, but failed, since bug-buddy asked about a session manager, and locked (like all apps do until you remove its /tmp/.ICE-unix/$PID) (gdb) bt #0 0xe410 in __kernel_vsyscall () #1 0xb787 in __waitpid_nocancel () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb7f0e558 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0 #3 signal handler called #4 0xb7856b53 in dbus_g_method_return_error () from /usr/lib/libdbus-glib-1.so.2 #5 0xb77fdd28 in g_slist_find_custom () from /usr/lib/libglib-2.0.so.0 #6 0xb785ad0c in dbus_g_proxy_set_interface () from /usr/lib/libdbus-glib-1.so.2 #7 0xb72197f8 in dbus_connection_dispatch () from /usr/lib/libdbus-1.so.2 #8 0xb7852a15 in dbus_server_setup_with_g_main () from /usr/lib/libdbus-glib-1.so.2 #9 0xb77e70c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #10 0xb77e9e62 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #11 0xb77ea20c in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #12 0xb7c9c052 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #13 0x08053c57 in ?? () #14 0x080a5c48 in ?? () #15 0x080a92b8 in ?? () #16 0x in ?? () (gdb) ** Affects: gnome-session (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Gnome-session-manager crashes when some dbus apps run https://launchpad.net/bugs/56583 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 55710] cvs [checkout aborted]: could not get working directory: Permission denied
Public bug reported: Binary package hint: cvs I've just updated to edgy, and suddenly my cvs repo (exported by pserver through inetd) is failing to allow checkouts. I've checked all permissions, etc., to no avail. ** Affects: cvs (Ubuntu) Importance: Untriaged Status: Unconfirmed -- cvs [checkout aborted]: could not get working directory: Permission denied https://launchpad.net/bugs/55710 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 55710] Re: cvs [checkout aborted]: could not get working directory: Permission denied
This bug seems to only show up using pserver, it doesn't happen on ext, but I do have to support pserver, so switching away from it isn't a good solution -- cvs [checkout aborted]: could not get working directory: Permission denied https://launchpad.net/bugs/55710 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
