The problem only occurs if "Miniprogramme im Bildschirmschoner zulassen"
(Allow applets in screensaver (?)) is activated. I have installed the
analog clock and thought it might be a good idea to see it in
screensaver.
When the checkbox is active (applets allowed in screensaver), the
problem occurs
Public bug reported:
I am using a up-to-date kubuntu maverick meerkat.
Steps to reproduce:
- Lock the screen
- Watch screensaver start
- Move the mouse to get login dialog
- Hit or click Escape
Result: The login dialog disappears. The mouse pointer stays visible
forever. No action gives me back
Please close this bug. It doesn't occur in Jaunty anymore.
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
No ethernet after cold boot; works after warm boot
https://bugs.launchpad.net/bugs/160436
You received this bug notification because you are a member of Ubuntu
Bugs, whi
This did also occur in Intrepid.
However, this does *not* occur in Jaunty anymore. At least for my
system. If there aren't any objections, I would close this bug next
week.
--
No ethernet after cold boot; works after warm boot
https://bugs.launchpad.net/bugs/160436
You received this bug notifica
Yes, it still happens on KDE 3.5.10.
My krdc version is 4:3.5.10-0ubuntu1~hardy2.
--
[hardy] krdc crashes after upgrade to hardy
https://bugs.launchpad.net/bugs/231315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Public bug reported:
Binary package hint: krdc
After upgrade to hardy, krdc crashes when trying to connect to a windows
xp box running realvnc server 4.1.1/4.1.2. krdc worked fine with the
same vnc server with gutsy. I upgraded the realvnc server from 4.1.1 to
4.1.2 because of the openssl vulnera
Meanwhile I found out, that this applies *only* to the realtime kernel
2.6.22-14-rt. When I use kernel 2.6.22.14-generic, everything works.
--
No ethernet after cold boot; works after warm boot
https://bugs.launchpad.net/bugs/160436
You received this bug notification because you are a member of U
Public bug reported:
After the dist-upgrade from feisty to gutsy, ethernet does not work after a
cold boot. The NIC is a Broadcom NetXtreme BCM 5171 using the tg3 driver.
/etc/init.d/networking restart does not bring network up. Instead it issues a:
SIOCSIFADDR: no such device
error for eth0
Af
** Attachment added: "output of dmesg, lshw, lspci, ifconfig and syslog
before/after warm boot"
http://launchpadlibrarian.net/10290403/gutsy_no_eth0_after_cold_boot.tar.gz
--
No ethernet after cold boot; works after warm boot
https://bugs.launchpad.net/bugs/160436
You received this bug notif
