It's the same with WSUSB100v2, the USB-ID is missing in the driver. In that
case, the ID is 1737:0078
I added the ID manually, just as in comment #2 and compiled the kernel on my
own and now the adapter is working just fine.
Would be great to have these IDs added in time for karmic.
--
Linksys
I can confirm this issue running Kubuntu Karmic with libpoppler 0.11.2.
Im running a 64bit machine. The example above and my own documents work
fine on a 32bit Jaunty installation (libpoppler 0.10.5-ubuntu2.2).
@Sebastian: Of course those examples open fine, there is nothing wrong
with them.
I can confirm this issue using latest KDE 4.2.2 packages on Jaunty.
Steps to reproduce:
1. Mount any removable storage device (no optical storage media)
2. Open Dolphin or another app and got to that storage device
3. Try to unmount the device using the devicenotifier applet
- Plasma freezes
Ok, seems that there is a fix available upstream. See
http://bugs.kde.org/show_bug.cgi?id=187242
** Bug watch added: KDE Bug Tracking System #187242
http://bugs.kde.org/show_bug.cgi?id=187242
--
unmounting disk via device notifier freezes desktop
https://bugs.launchpad.net/bugs/349595
You
I experience exactly the same behaviour using a notebook with a SiS network
card. The problem only occurs in our corporate network using the wired network.
Wireless works fine.
My syslog looks quite the same as above so I didn't reposte it. Rebooting,
reconfiguring the dhcp-packages and
While helping a friend on the same issue, I found a bug-report in the
madwifi-bugtracker that is dealing with exact the same issue:
http://madwifi.org/ticket/1679
This ticket includes a patched madwifi-version.
--
Wireless Not Working With Acer Aspire 5315 Laptop
After reinstalling my system from the Kubuntu 8.04 KDE4 Remix CD this
problem does not occure any more. So how did you guys come to Hardy?
Upgrade or fresh install?
--
[hardy] keytouch blocks logout
https://bugs.launchpad.net/bugs/186713
You received this bug notification because you are a
Hm, my workaround was using firefox ;)
I now found the time to play around with the problem a bit. After deleting
konquerorrc from ~/.kde4/share/config/ the adress bar works as it should again.
I also had a quick look at the config-file but didn't find anything strange
here.
Attached the
I can confirm this bug. It's exactly the same here, except I'm using
KDE. Keytouch 2.3.2-2 under hardy.
--
[hardy] keytouch blocks logout
https://bugs.launchpad.net/bugs/186713
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: Screenshot of konqueror-kde4 with adress bar
http://launchpadlibrarian.net/11817645/konq_adress_bar.png
--
[hardy] konqueror's adress bar screwed up
https://bugs.launchpad.net/bugs/190039
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Binary package hint: konqueror-kde4
My KDE4 konqueror shows the adress bar as a black rectengular, without
any possibility to interact with it. The adress bar is allways shown on
top, even with other windows on top focus. Additionaly, when closing
konqueror, the adress bar
I can confirm that. I use gutsy with latest updates too. I tried
scanning files on a usb drive first: Hangs at 35%. I then copied all
files to a local drive an the scan now hangs at 68%. amarokcollection
takes about 50% load on one core. After killing the process, collection
scanning resumes and
I get the same error when trying to add an additional nameserver under feisty
fawn.
The new nameserver entry is used in the current session, but is not present
after a reboot.
What is also strange about that: The apply-button is not greyed out after
restarting the networking. In all other
13 matches
Mail list logo
