[Bug 355998] Re: usb-storage: waiting for device to settle before scanning
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 gigabeat doesn't have an MTP mode, so I can't help with that request. I think my wife's e200 Sansa can switch modes, I'll grab it tomorrow and try it. -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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 355998] Re: usb-storage: waiting for device to settle before scanning
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 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 355998] Re: usb-storage: waiting for device to settle before scanning
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: the command "lsusb" showed: Bus 001 Device 011: ID 0930:0009 Toshiba Corp. Gigabeat F/X (HDD audio player) I changed the 2352 to 0930 Saved. Plugged in my toshiba and it popped up on the desktop. Thanks so much for the help, I look forward to the package in an update! -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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 355998] Re: usb-storage: waiting for device to settle before scanning
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 lsusb would say if you changed the "mode" in the original firmware. If lsusb doesn't change for the modes, rockbox should update its usb id to match the original firmware. -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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 341079] Re: [Jaunty]No window borders any more
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 341079] Re: [Jaunty]No window borders any more
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 => Invalid -- [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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 397892] Re: Screensaver does not turn on [Ubuntu / Xubuntu Karmic]
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 coincided with a change in the package. I am also not 100% sure that mucking with the screensaver preferences breaks it, but others should give it a try. -- Screensaver does not turn on [Ubuntu / Xubuntu Karmic] https://bugs.launchpad.net/bugs/397892 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 397892] Re: Screensaver does not turn on [Ubuntu / Xubuntu Karmic]
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 wrote: > Josef, > > what desktop environment are you using? (Gnome, XFCE, etc.) > what change do you make in the preferences panel that makes it stop working? > When you say "stop working", do you mean gnome-screensaver doesn't come up > after the idle timeout, or does it not work at all? > > -- > Screensaver does not turn on [Ubuntu / Xubuntu Karmic] > https://bugs.launchpad.net/bugs/397892 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Xubuntu: New > Status in “gnome-screensaver” package in Ubuntu: Triaged > > Bug description: > Binary package hint: gnome-screensaver > > RELEASE: Karmic Koala > CD/DVD VARIANT: 64bit Xubuntu installed fresh using ext4 and grub2 > ISO BUILD: > SYMPTOMS: Using Applications -> Settings -> Screensaver to set the > screensaver preferences has no effect. The screensaver is set to start in 10 > minutes. Unfortunately, it never activates. > > Run in terminal gives me: > char...@wecan:~$ gnome-screensaver-preferences > ** (gnome-screensaver-preferences:6402): DEBUG: Found best visual for GL: 0x21 > > There are no entries in ~/.xsession-errors log and no entries in any system > log that I can find looking in /var/log. > > gnome-screensaver: > Installed: 2.27.0-0ubuntu3 > Candidate: 2.27.0-0ubuntu3 > Version table: > *** 2.27.0-0ubuntu3 0 > 500 http://us.archive.ubuntu.com karmic/main Packages > 100 /var/lib/dpkg/status > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/xubuntu-desktop/+bug/397892/+subscribe > -- Screensaver does not turn on [Ubuntu / Xubuntu Karmic] https://bugs.launchpad.net/bugs/397892 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 373507] Re: Gnome-Pilot Bluetooth HotSync Functions ONLY Once without "device" re-mapping
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 phone), that I did not change. I seem to be able to Sync over and over again with the "Cradle" device set to USB. Perhaps having one set to USB and the other to BLUETOOTH sets something to working. Running a fairly up to date Karmic x64 system here. gnome-pilot 2.0.17-0ubuntu2 gnome-pilot-conduits 2.0.15-1.2 -- Gnome-Pilot Bluetooth HotSync Functions ONLY Once without "device" re-mapping https://bugs.launchpad.net/bugs/373507 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 397892] Re: Screensaver does not turn on [Ubuntu/Xubuntu Karmic]
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 Karmic] https://bugs.launchpad.net/bugs/397892 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 397892] Re: Screensaver does not turn on [Ubuntu/Xubuntu Karmic]
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: Debian Bug tracker #538694 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538694 -- Screensaver does not turn on [Ubuntu/Xubuntu Karmic] https://bugs.launchpad.net/bugs/397892 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 733374] Re: X freeze, nvidia-current, Ubuntu 10.10 Maverick
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: os_schedule: Attempted to yield the CPU while in atomic or interrupt context -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/733374 Title: X freeze, nvidia-current, Ubuntu 10.10 Maverick -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
