I was getting this like crazy with 2.6.35-28 and 2.6.35-26, about every
hour, nvidia 270.*
I switched back to 2.6.35-24 and nvidia 260.* and it stopped. I'm going
to try going back to nvidia 270.* when I get a chance, but this seemed
to fix it for me.
I no longer see this at all in dmesg:
NVRM:
While doing the workaround dance as stated above, I tried something and
seem to have it fixed!
gnome-pilot Settings Devices Edit Change BLUETOOTH to USB OK
Close
Now, when I sync, it just seems to work!
Note that I have a second Cradle1 under Devices, that is set to
Bluetooth (for another
I cleaned out my users .gnome* .gconf* etc and my screensaver/power-
saving started working again, however, if I go to screensaver
preferences and make a change, it stops working until the next
logout/login.
I can not be sure that the fresh .gnome* .gconf* made a difference, or if that
Sorry for lack of detail..
Karmic w/ gnome and metacity.
(upgrade from Jaunty, upgrade from Intrepid Install)
When I say stop working I mean that screensaver and powersave modes
no longer engage after any idle timeout.
Josef
On Mon, Dec 7, 2009 at 12:22 PM, Marc Deslauriers
In addition to my Karmic x64 install, I noticed this is also broken on Debian
Unstable i686 for me. So maybe it is upstream? Found this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538694
Odd that Debian unstable is on gnome 2.26 and Ubuntu 2.28. My mind is
blown.
** Bug watch added:
I updated to karmic 2 weeks ago. At first the screensaver/power
management didn't work at all. After the first week, screensaver
started working, but the power management (turning the monitor off)
never kicks in.
amd64 with nvidia 185 as well.
--
Screensaver does not turn on [Ubuntu/Xubuntu
Ori,
The Gigabeat has the ability to run in MTP or USB mode, at least with
the original firmware.
http://cdgenp01.csd.toshiba.com/content/support/downloads/gigabeat-F10204060_OwnersManual3_02_US_UE.pdf
(search for MTP)
I tried to reinstall the original firmware to no avail. I do wonder
what
Ori,
Sorry didn't see your note until today. I see now the XML speifies the
usb.*_id as int, so like you said, a hack, but that is fine while I wait
for upstream :) Just wanted to put up more detailed instructions for
people who just want it to work for now.
The rockbox firmware for the
I think a non-rockbox gigabeat has MTP capability, maybe someone else
can help. Or maybe it works for them, in as much as MTP can be
considered working.
--
usb-storage: waiting for device to settle before scanning
https://bugs.launchpad.net/bugs/355998
You received this bug notification because
Using a Toshiba Gigabeat MEGF-40 (tried several version of RockBox) I
had the same problem.
Edited /usr/share/hal/fdi/preprobe/10osvendor/20-libgphoto2.fdi as root
Searched for Gigabeat MEGF-40
A few lines before, It has:
match key=usb.vendor_id int=2352
match key=usb.product_id int=9
the
Same for me, but with nvidia. Compiz is running. Starting emerald
manually doesn't add decorations.
--
[Jaunty]No window borders any more
https://bugs.launchpad.net/bugs/341079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Opened synaptic and marked compiz and compizconfig-settings-manager
This also installed:
compiz-gnome
libprotobuf3.
libcompizconfig0
compizconfig-backend-gconf
python-compizconfig
Logged out and back in and compiz is working fine once again.
** Changed in: compiz (Ubuntu)
Status: New =
12 matches
Mail list logo
