[Bug 990129] Re: Suspend/Resume hangs and fails - Ubuntu 12.04LTS

It's definetely a kernel bug, fixed for some with normal updates, I had to install the 3.4 kernel from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.laun

[Bug 990129] Re: Suspend/Resume hangs and fails - Ubuntu 12.04LTS

Sorry for the run around. I tried the Oneiric version of pm-utils and standby still didn't work. Not, that I have any experience in this, but since I don't have gnome- power-manager and was using a version of pm-utils that used to work, I would say this is a kernel bug. -- You received this bug

[Bug 990129] Re: Suspend/Resume hangs and fails - Ubuntu 12.04LTS

Hi all, I'm a on Xubuntu 12.04. Hardware profile: 00:00.0 Host bridge: Advanced Micro Devices [AMD] nee ATI RS690 Host Bridge 00:01.0 PCI bridge: Advanced Micro Devices [AMD] nee ATI RS690 PCI to PCI Bridge (Internal gfx) 00:05.0 PCI bridge: Advanced Micro Devices [AMD] nee ATI RS690 PCI to PCI

[Bug 74278] Re: [feisty regression] ipw2200 broken after suspend, need to boot into WINDOWS to get it working again

*** This bug is a duplicate of bug 42387 *** Link to said patch? When will it be applied? -- [feisty regression] ipw2200 broken after suspend, need to boot into WINDOWS to get it working again https://launchpad.net/bugs/74278 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://li

[Bug 73517] Re: yelp broken on Feisty: CRITICAL **: AT_SPI_REGISTRY was not started at session startup.

Err, woops. Sorry for remarking, didn't mean to click that. -- yelp broken on Feisty: CRITICAL **: AT_SPI_REGISTRY was not started at session startup. https://launchpad.net/bugs/73517 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 74278] Re: [feisty regression] ipw2200 broken after suspend, need to boot into WINDOWS to get it working again

I did try that. I get a "permission denied" even as root. On 12/5/06, Nicolò Chieffo <[EMAIL PROTECTED]> wrote: > > if it does not work, 2 might mean hardware kill So I have no > solution. > > -- > [feisty regression] ipw2200 broken after suspend, need to boot into > WINDOWS to get it working

[Bug 74278] Re: [feisty regression] ipw2200 broken after suspend, need to boot into WINDOWS to get it working again

[EMAIL PROTECTED]:~$ cat /sys/class/net/eth1/device/rf_kill 2 -- [feisty regression] ipw2200 broken after suspend, need to boot into WINDOWS to get it working again https://launchpad.net/bugs/74278 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listi

[Bug 74278] Re: [feisty regression] ipw2200 broken after suspend, need to boot into WINDOWS to get it working again

Notice in my bad dmesg this: [ 398.16] atkbd.c: Unknown key pressed (translated set 2, code 0xb4 on isa0060/serio0). [ 398.16] atkbd.c: Use 'setkeycodes e034 ' to make it known. That's normal; it's my wireless killswitch button (the pressable LED) which turns the radio on and off. But

[Bug 74278] Re: [feisty regression] ipw2200 broken after suspend, need to boot into WINDOWS to get it working again

** Attachment added: ""bad" dmesg indicating problem" http://librarian.launchpad.net/5240387/aftersusp.txt -- [feisty regression] ipw2200 broken after suspend, need to boot into WINDOWS to get it working again https://launchpad.net/bugs/74278 -- ubuntu-bugs mailing list ubuntu-bugs@lists.u

[Bug 74278] Re: [feisty regression] ipw2200 broken after suspend, need to boot into WINDOWS to get it working again

"Good" dmesg after a Windows boot ** Attachment added: "good dmesg" http://librarian.launchpad.net/5240381/good.txt -- [feisty regression] ipw2200 broken after suspend, need to boot into WINDOWS to get it working again https://launchpad.net/bugs/74278 -- ubuntu-bugs mailing list ubuntu-bug

[Bug 74278] [feisty regression] ipw2200 broken after suspend, need to boot into WINDOWS to get it working again

Public bug reported: Binary package hint: linux-image-2.6.19-7-386 As the summary says. This was not an issue with kernel 2.6.17. I _literally_ have to boot into Windows XP, and then restart, to get my wireless working again; rebooting Ubuntu does nothing; it says the killswitch is on and it cann

[Bug 73517] yelp broken on Feisty: CRITICAL **: AT_SPI_REGISTRY was not started at session startup.

Public bug reported: Binary package hint: yelp [EMAIL PROTECTED]:~$ yelp ** (yelp:6028): CRITICAL **: AT_SPI_REGISTRY was not started at session startup. ** (yelp:6028): WARNING **: IOR not set. ** ERROR **: Could not locate registry aborting... Aborted yelp opens for a few seconds then dies

[Bug 71872] Re: gdmsetup not starting on feisty fawn

`Export` shows that DISPLAY is normally set as DISPLAY=:0.0 -- I'm wondering if this is incorrect? Does anyone know what exactly DISPLAY does, and in what script where this variable is set? -- gdmsetup not starting on feisty fawn https://launchpad.net/bugs/71872 -- ubuntu-bugs mailing list ubun

[Bug 71872] Re: gdmsetup not starting on feisty fawn

Workaround: [EMAIL PROTECTED]:~$ sudo -i [EMAIL PROTECTED]:~# DISPLAY=:0 gdmsetup -- gdmsetup not starting on feisty fawn https://launchpad.net/bugs/71872 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 71872] Re: gdmsetup not starting on feisty fawn

With gdm.conf set with debug, this is what I get when I do sudo gdmsetup ... Nov 27 08:41:57 paul-laptop gdm[4208]: gdm_socket_handler: Accepting new connection fd 10 Nov 27 08:41:57 paul-laptop gdm[4208]: Handling user message: 'VERSION' Nov 27 08:41:57 paul-laptop gdm[4208]: Handling user messa

[Bug 71872] Re: gdmsetup not starting on feisty fawn

Confirmed here too. -- gdmsetup not starting on feisty fawn https://launchpad.net/bugs/71872 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 66025] Re: gnome-power-manager does not update often enough, only updates every 25% of battery charge

Okay, this is a hal issue, thanks much to Richard Hughes. Can the Ubuntu HAL maintainer apply this patch? http://lists.freedesktop.org/archives/hal/2006-October/006389.html ** Changed in: gnome-power-manager (Ubuntu) Sourcepackagename: gnome-power-manager => hal ** Changed in: hal (Ubuntu)

[Bug 66025] Re: gnome-power-manager does not update often enough, only updates every 25% of battery charge

Any ideas on what might be causing this? -- gnome-power-manager does not update often enough, only updates every 25% of battery charge https://launchpad.net/bugs/66025 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 66025] Re: gnome-power-manager does not update often enough, only updates every 25% of battery charge

Just to drive the point home ** Attachment added: "screenshot 2" http://librarian.launchpad.net/4903113/Screenshot-1.png -- gnome-power-manager does not update often enough, only updates every 25% of battery charge https://launchpad.net/bugs/66025 -- ubuntu-bugs mailing list ubuntu-bug

[Bug 66025] Re: gnome-power-manager does not update often enough, only updates every 25% of battery charge

Yes, but it isn't just the battery icon, its the information dialog too. I wasn't able to take a screenshot with the battery-icon popup, but here's the dialog box which is the same. Take a look. ** Attachment added: "screenshot" http://librarian.launchpad.net/4903047/Screenshot.png -- gnome-p

[Bug 66025] Re: gnome-power-manager does not update often enough, only updates every 25% of battery charge

Okay, this is not a HAL issue: [EMAIL PROTECTED]:~$ lshal -m Start monitoring devicelist: - acpi_BAT1 property battery.reporting.rate = 1804 (0x70c) acpi_BAT1 property battery.reporting.current = 4469 (0x1175) acpi_BAT1 property battery.reporting.ra

[Bug 56376] Re: [Dapper 6.06] Laptop - PCI cannot allocate resource for region 7 8 and 9

Same problem: Acer Travelmate 8104 WLMi. Edgy, linux-2.6.17 ** Changed in: linux-source-2.6.15 (Ubuntu) Sourcepackagename: linux-source-2.6.15 => linux-source-2.6.17 -- [Dapper 6.06] Laptop - PCI cannot allocate resource for region 7 8 and 9 https://launchpad.net/bugs/56376 -- ubuntu-bugs mail

[Bug 66025] Re: gnome-power-manager does not update often enough, only updates every 25% of battery charge

g-p-m lists tell me this is a HAL problem. ** Changed in: gnome-power-manager (Ubuntu) Sourcepackagename: gnome-power-manager => hal -- gnome-power-manager does not update often enough, only updates every 25% of battery charge https://launchpad.net/bugs/66025 -- ubuntu-bugs mailing list ubunt

[Bug 66025] gnome-power-manager does not update often enough, only updates every 25% of battery charge

Public bug reported: Binary package hint: gnome-power-manager As the summary says. It should definitely update more, at _least_ once every 5%. I understand polling is to be kept to a minimum to avoid unnecessary CPU usage but really, it'd be nice if when I look at my battery stats, they don't go

[Bug 65999] Re: After suspend, battery status report broken

After FURTHER investigation: this a gnome-power-manager problem. It simply isnt refreshing -- cat'ing /proc/acpi/battery/BAT1/state several times over a minute shows "remaining capacity" as decreasing but the g-p-m still shows 100% -- thus this isn't a kernel problem but a gnome one. -- After sus

[Bug 65999] Re: After suspend, battery status report broken

I apologize for the spam. g-p-m _finally_ updated itself -- now it says 75%. This simply appears to be a problem where it isn't updating itself nearly often enough, because really, it should poll at more than once every 25% of charge. So I will file a bug with that package, and leave this kernel

[Bug 65999] Re: After suspend, battery status report broken

Okay, after further examination, this is a problem even _without_ suspending, at least on my machine. On a clean boot, there are no ACPI errors, but It still always says 100% all the time on battery power, this was not a problem when I used Slackware. Attached is dmesg...any ideas? This is an Acer

[Bug 65999] After suspend, battery status report broken

Public bug reported: Binary package hint: acpi Upstream bug: http://bugzilla.kernel.org/show_bug.cgi?id=7185 I am using an Acer laptop with a custom DSDT and after resuming from suspend battery status is unable to be reported (gnome reports 100% all the time). Please, when a fix is available,

[Bug 61182] Re: Mozilla Firefox Bon Echo Beta 2 Doesn't show RSS Feed preview

Any ETA on the new firefox version? It's been a quite while. -- Mozilla Firefox Bon Echo Beta 2 Doesn't show RSS Feed preview https://launchpad.net/bugs/61182 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 64788] RSS feeds in firefox broken

Public bug reported: Binary package hint: firefox 1. Go to slashdot 2. click on the RSS icon in the url bar 3. Observe ugly webpage that doesnt do anything Why are we still at Beta 2 when RC2 has been released...? ** Affects: firefox (Ubuntu) Importance: Undecided Status: Unconfir

[Bug 63993] Default keyring remains locked when using evolution; makes storing passwords useless

Public bug reported: This is 6.10-beta. Okay, so I wanted Evolution to store my password for my gmail, so it asked me to create a keyring. I did, but now _what good is storing_ my password if the stupid thing pops up every boot, asking me for my keyring password (which is even longer and more cum