Bryce: I suppose it's plausible the slow keys feature was the reason,
although I as I said in the original report, this was related to playing
with upstart/sysvinit. I'm pretty certain I didn't visit the slow keys
dialog box, but at this point, three Ubuntu releases later, I can't
really confirm or
I just tried it again, this time I got a different problem:
The system has reached a state where there are no jobs running. A shell
will be spawned so that... etc.
It had got the network connection up, but that was pretty much it. Oh
well, reinstalled sysvinit.
I'm planning on doing a clean inst
Public bug reported:
I run Edgy. Everything is up to date. I wanted to give upstart a try,
but ran into problems. I'm not sure if this bug is in upstart or if
upstart just triggered a bug in somewhere else.
Startup seemed to go OK, I got the GDM login screen and could log in.
However, once the Gn
--
Philips GoGear SA1330 audio player not recognized (patch included)
https://launchpad.net/bugs/58077
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
--
Philips GoGear SA1330 audio player not recognized (patch included)
https://launchpad.net/bugs/58077
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Public bug reported:
Attaching a patch for /usr/share/hal/fdi/information/10freedesktop/10
-usb-music-players.fdi , lspci and lsusb output. This will result in
support for Philips GoGear SA1330.
** Affects: hal (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
Philips GoGear S
--
Philips GoGear SA1330 audio player not recognized (patch included)
https://launchpad.net/bugs/58077
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
