[Bug 264104] Re: ipw2200 driver no longer works with wpa2 network

Here's mine: /sys/module/ipw2200/parameters/antenna:0 /sys/module/ipw2200/parameters/associate:0 /sys/module/ipw2200/parameters/auto_create:1 /sys/module/ipw2200/parameters/bt_coexist:0 /sys/module/ipw2200/parameters/burst_duration_CCK:0 /sys/module/ipw2200/parameters/burst_duration_OFDM:0 /sys/mo

[Bug 264104] Re: ipw2200 driver no longer works with wpa2 network

Not sure what you need from modinfo, but does this help? version:1.2.2kmprq vermagic: 2.6.27-11-generic SMP mod_unload modversions 586 I don't think I had intrepid-backports, but I was probably using intrepid-updates... Thanks :) -- ipw2200 driver no longer works with wpa2 networ

[Bug 264104] Re: ipw2200 driver no longer works with wpa2 network

Well, while my computer is pretty hot (It's a fanless Fujitsu-Siemens P7120), I don't it's related. sti...@chrysler:~$ cat /proc/acpi/thermal_zone/TZ00/temperature temperature: 40 C As I wrote earlier, I only have this problem when using Network Manager with kernel 2.6.28 and later. U

[Bug 264104] Re: ipw2200 driver no longer works with wpa2 network

Hmm. I've upgraded to karmic tonight (using dist-upgrade, did not do a fresh install). That actually just made it worse. Now it's not usable with network-manager even with my good, old 2.6.27-11-kernel. Or the new 2.6.31-5. Wicd still works fine with any kernel I've tried, so I can still use my com

[Bug 264104] Re: ipw2200 driver no longer works with wpa2 network

I'm also seeing this after the upgrade to Jaunty, it seems. It works perfectly with 2.6.27-11-generic, but fails with 2.6.28-13-generic (I have also tried 2.6.30 from http://kernel.ubuntu.com/~kernel-ppa) As an additional datapoint, it works when I replaced Network-Manager with Wicd. I really pref

[Bug 56271] Won't resume from 2.6.17, worked with Dapper

Public bug reported: I upgraded my laptop to edgy this weekend, and everythings work fine, except for resume. I don't really know what information is needed. After Dapper came out, there was an update (don't remember the version) that made resume fail with the 2.6.15 kernel as well, but it was lat

[Bug 56271] Re: Won't resume from 2.6.17, worked with Dapper

Fujitsu-Siemens P7120. Do you need dmesg, perhaps? -- Won't resume from 2.6.17, worked with Dapper https://launchpad.net/bugs/56271 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 56271] Re: Won't resume from 2.6.17, worked with Dapper

Here it is. After blacklisting sdhci and mmc_core, it seems to be a bit better. I actually had a sucessful resume (except for wireless network being unavailable). But usually the screen never lights up, and the few times it does light up, I never get more than the cursor. And again, with 2.6.15-26

[Bug 56271] Re: Won't resume from 2.6.17, worked with Dapper

Not the same bug, since my problem is suspend-to-RAM... Btw. just tested with 2.6.18-rc4 as well, and it works 100% perfect... But I can't get self-compiled 2.6.17 to work neither (nor any earlier kernel), so it must be a patch you used on 2.6.15 that you haven't applied to 2.6.17... -- Won't re

[Bug 57501] After resume, thinks my wireless network is wired

Public bug reported: With kernels 2.6.17-6 and self compiled 2.6.18-rc4 after resume sometimes (but not always) network-manager thinks that my ipw2200 is wired. And then it obviously can't connect... Never have this problem with the dapper kernel (2.6.15-26). ** Affects: network-manager (Ubuntu)

[Bug 57501] Re: After resume, thinks my wireless network is wired

Forgot to write that wireless works after resume _every_ time when just having wireless-essid and wireless-key in interfaces. So while the bug does not happen with 2.6.15-26, I don't think it's a kernel problem... -- After resume, thinks my wireless network is wired https://launchpad.net/bugs/575

[Bug 59222] Computer isn't discoverable

Public bug reported: Hi, I'm not really sure when this started (not using bluetooth very often). It might have been with Dapper, or it might have been with edgy. Anyway, with updated edgy, hciconfig shows: [EMAIL PROTECTED]:~$ hciconfig hci0: Type: USB BD Address: 00:60:57:33:5B:A6 AC

[Bug 56271] Re: Won't resume from 2.6.17, worked with Dapper

Still the same with 2.6.17.7-generic... The computer wakes up, but the screen is black except for the mouse, which is movable, but sometimes it (the mouse) locks up for maybe ten seconds, and then I can move it for some seconds before it locks up again. Still, Dapper kernel works perfect, as well

[Bug 56271] Re: Won't resume from 2.6.17, worked with Dapper

Seems like 2.6.17-8-generic works fine :) Been testing all day, and seems good :) Thanks! -- Won't resume from 2.6.17, worked with Dapper https://launchpad.net/bugs/56271 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 56271] Re: Won't resume from 2.6.17, worked with Dapper

How do I close bugs in launchpad? -- Won't resume from 2.6.17, worked with Dapper https://launchpad.net/bugs/56271 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 56271] Re: Won't resume from 2.6.17, worked with Dapper

Uhh, I said that to fast... I guess this is to late for edgy, but for the record... It seems that after the first suspend it always resumes, but after the second suspend it almost never resumes properly. The display lights up (but stays black), and I can move the mouse (but I have the working "glo

[Bug 87951] Re: Compact flash (with PCMCIA adaptor) does not mount

I have the exact same error on two very different computers. It doesn't seem like pcmcia cards with ata works at all. I have tried several different cards with the same result in both computers. -- Compact flash (with PCMCIA adaptor) does not mount https://launchpad.net/bugs/87951 -- ubuntu-bug

[Bug 88741] Re: mergedfb doesn't work with xserver-xorg-core 2:1.2.0-3ubuntu1 (or newer)

If you'll need Xorg.0.log from a working mergedfb session, I'll attach that as well. But to avoid confusion I'll wait for you to request it. -- mergedfb doesn't work with xserver-xorg-core 2:1.2.0-3ubuntu1 (or newer) https://launchpad.net/bugs/88741 -- ubuntu-bugs mailing list ubuntu-bugs@lists

[Bug 88741] mergedfb doesn't work with xserver-xorg-core 2:1.2.0-3ubuntu1 (or newer)

Public bug reported: Binary package hint: xserver-xorg-core After update to xserver-xorg-core 2:1.2.0-3ubuntu1 two days ago, mergedfb won't work anymore, I just get clone mode on my two monitors. Xinerama still works fine. I'll attach Xorg.0.log and xorg.conf in a moment. After downgrading to 1.

[Bug 88741] Re: mergedfb doesn't work with xserver-xorg-core 2:1.2.0-3ubuntu1 (or newer)

** Attachment added: "Xorg.0.log from failing x-session with xserver-xorg-core 2:1.2.0-3ubuntu1" http://librarian.launchpad.net/6579607/Xorg.0.log -- mergedfb doesn't work with xserver-xorg-core 2:1.2.0-3ubuntu1 (or newer) https://launchpad.net/bugs/88741 -- ubuntu-bugs mailing list ubuntu

[Bug 88741] Re: mergedfb doesn't work with xserver-xorg-core 2:1.2.0-3ubuntu1 (or newer)

** Attachment added: "xorg.conf with mergedfb" http://librarian.launchpad.net/6579602/xorg.conf -- mergedfb doesn't work with xserver-xorg-core 2:1.2.0-3ubuntu1 (or newer) https://launchpad.net/bugs/88741 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mail

[Bug 88741] Re: mergedfb doesn't work with xserver-xorg-core 2:1.2.0-3ubuntu1 (or newer)

Indeed, fixed now :) Must have been something with xserver-xorg-video- ati, maybe? -- mergedfb doesn't work with xserver-xorg-core 2:1.2.0-3ubuntu1 (or newer) https://launchpad.net/bugs/88741 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubun

[Bug 87951] Re: Compact flash (with PCMCIA adaptor) does not mount

Still works fine for me with the latest kernel... :) -- Compact flash (with PCMCIA adaptor) does not mount https://launchpad.net/bugs/87951 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 87951] Re: Compact flash (with PCMCIA adaptor) does not mount

Indeed, fixed now :) -- Compact flash (with PCMCIA adaptor) does not mount https://launchpad.net/bugs/87951 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 30871] Re: will not open terminal in current folder

Nope, works for me, at least :):) -- will not open terminal in current folder https://launchpad.net/bugs/30871 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 54779] Re: Keyring password

Would be awesome to get libpam-keyring included in edgy... Would save a lot of unneeded and (IMHO) stupid password-typing. It's just very weird to have to enter the password three times (in my case) when you login. -- Keyring password https://launchpad.net/bugs/54779 -- ubuntu-bugs mailing list

[Bug 264104] Re: ipw2200 driver no longer works with wpa2 network

Sorry for the very late reply. Changing the module's roaming option didn't change anything - I'm still resorted to using wicd (with no 3g support...) -Stian -- ipw2200 driver no longer works with wpa2 network https://bugs.launchpad.net/bugs/264104 You received this bug notification because you a

[Bug 884658] Re: Won't start because of missing directory for lock-file

Well, this is still a problem in oneiric, that is still supposed to be supported. Or isn't that valid for Universe, maybe? Anyway, it's utterly useless now, and should either be updater or removed from the archive. Regards, Stian -- You received this bug notification because you are a member of

[Bug 884658] [NEW] Won't start because of missing directory for lock-file

Public bug reported: Hi! After my upgrade to oneiric today, I find that p910nd won't start, and I get this message in the syslog: Nov 1 10:09:22 dodge p9100d[780]: /var/lock/subsys/p9100d: No such file or directory If I manually create the directory it starts alright... Regards, Stian ** Aff

[Bug 884658] Re: Won't start because of missing directory for lock-file

(But since /run/lock is mounted on tmpfs, I obviously need to recreate it after every boot) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884658 Title: Won't start because of missing directory for l

[Bug 735053] Re: rip crashed with TaskException in run(): (QueryError('query failed', ), 'exception QueryError at morituri/common/checksum.py:93: start(): query failed')

** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/735053 Title: rip crashed with TaskException in run(): (QueryError('query failed',), 'exception QueryError at moritur

[Bug 735053] Re: rip crashed with TaskException in run(): (QueryError('query failed', ), 'exception QueryError at morituri/common/checksum.py:93: start(): query failed')

Hi! Thanks for your reply. Attached is output from RIP_DEBUG=5. Hope this helps :) Regards, Stian ** Attachment added: "Log with RIP_DEBUG=5" https://bugs.launchpad.net/ubuntu/+source/morituri/+bug/735053/+attachment/1910682/+files/rip.log -- You received this bug notification because you

[Bug 735053] Re: rip crashed with TaskException in run(): (QueryError('query failed', ), 'exception QueryError at morituri/common/checksum.py:93: start(): query failed')

Hi! Attached is output from svn version with RIP_DEBUG=5. ** Attachment added: "Log from latest SVN with RIP_DEBUG=5" https://bugs.launchpad.net/ubuntu/+source/morituri/+bug/735053/+attachment/1911164/+files/rip.log -- You received this bug notification because you are a member of Ubuntu Bu

[Bug 735053] Re: rip crashed with TaskException in run(): (QueryError('query failed', ), 'exception QueryError at morituri/common/checksum.py:93: start(): query failed')

I had to compress this file because of size. This is output with GST_DEBUG=*:4 RIP_DEBUG=5. Thanks! Regards, Stian ** Attachment added: "Log from latest SVN with GST_DEBUG=*:4 RIP_DEBUG=5" https://bugs.launchpad.net/ubuntu/+source/morituri/+bug/735053/+attachment/1911225/+files/rip2.log.gz

[Bug 735053] Re: rip crashed with TaskException in run(): (QueryError('query failed', ), 'exception QueryError at morituri/common/checksum.py:93: start(): query failed')

Well, it seems I'm the only one using morituri on Ubuntu 11.04 64 bit. I just tested with 32 bit ubuntu, and it works ok there... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/735053 Title: rip cras

[Bug 735053] Re: rip crashed with TaskException in run(): (QueryError('query failed', ), 'exception QueryError at morituri/common/checksum.py:93: start(): query failed')

Yup, I can confirm that it's now fixed, with -bad reinstalled. Thank you very much for fixing this issue! My system is set to run in Norwegian, output below. Thanks again! Regards, Stian stianj@chevrolet:~$ set | grep LANG LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en LANG=C LC_M

[Bug 735053] Re: rip crashed with TaskException in run(): (QueryError('query failed', ), 'exception QueryError at morituri/common/checksum.py:93: start(): query failed')

Thanks! But this didn't seem to help. Or, it helped in a way, since I no longer get a stack trace, just an error message: rip: error: Could not create encoded file. I'll attach debug output with both GST_DEBUG=*:4 RIP_DEBUG=5 and RIP_DEBUG=5 in case it matters... Thanks. ** Attachment added: "Lo

[Bug 735053] Re: rip crashed with TaskException in run(): (QueryError('query failed', ), 'exception QueryError at morituri/common/checksum.py:93: start(): query failed')

** Attachment added: "Gzip-compressed log with GST_DEBUG=*:4 RIP_DEBUG=5" https://bugs.launchpad.net/ubuntu/+source/morituri/+bug/735053/+attachment/2141954/+files/rip2.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https:/

[Bug 735053] Re: rip crashed with TaskException in run(): (QueryError('query failed', ), 'exception QueryError at morituri/common/checksum.py:93: start(): query failed')

Well, you were correct about the assumption that my flacparse is in bad (see below). But your fix didn't seem to make any difference... I have double-checked that I'm running with latest SVN (and I see the changeset)... Regards, Stian stianj@chevrolet:~$ gst-inspect-0.10 flacparse Factory Detail

[Bug 735053] Re: rip crashed with TaskException in run(): (QueryError('query failed', ), 'exception QueryError at morituri/common/checksum.py:93: start(): query failed')

Hi! No need to excuse, I've used Linux for 11 years, and know how busy developers are :) I will attach three files, trial.txt with results from the "trial morituri". Lots of fun there, I guess... Then there is rip.log which is with RIP_DEBUG=5 and rip2.log.gz which is GST_DEBUG=*:4 RIP_DEBUG=5.

[Bug 735053] Re: rip crashed with TaskException in run(): (QueryError('query failed', ), 'exception QueryError at morituri/common/checksum.py:93: start(): query failed')

** Attachment added: "rip2.log.gz" https://bugs.launchpad.net/ubuntu/+source/morituri/+bug/735053/+attachment/2142827/+files/rip2.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/735053 Title:

[Bug 735053] Re: rip crashed with TaskException in run(): (QueryError('query failed', ), 'exception QueryError at morituri/common/checksum.py:93: start(): query failed')

** Attachment added: "trial.log" https://bugs.launchpad.net/ubuntu/+source/morituri/+bug/735053/+attachment/2142828/+files/trial.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/735053 Title: r