[Konsole-devel] [Bug 159631] New: konsole-kde4 goes black and eats my cursor when it tries to play a beep sound

[Ralph Janke]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=159631         
           Summary: konsole-kde4 goes black and eats my cursor when it tries
                    to play a beep sound
           Product: konsole
           Version: unspecified
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: konsole-devel kde org
        ReportedBy: txwikinger ubuntu com


Version:            (using KDE 4.0.2)
Installed from:    Ubuntu Packages
OS:                Linux

This is a forwarded report from Kubuntu (https://bugs.launchpad.net/ubuntu/+source/kdebase-kde4/+bug/186172)

I start up konsole-kde4 and all is well - everything works as expected.
However, after writing a command or two, sometimes the window goes completely black and my mouse-cursor disappears.
 It doesn't seem like the sudden change of window-content is connected to commands I type (like cd and ls - nothing strange).
I can still move the window around and resize the window. The mouse-cursor still works correctly everywhere except when moving it over that window.
I have turned off the scrollbar, tab-bar and menubar in the options, and run konsole-kde4 as full screen (it covers the entire virtual desktop). I use Fvwm.

Steps to reproduce:
 1. Start FVWM2 or some other non-KDE windowmanager, preferably not Xfce or Gnome, since I think they start their own sound-systems
 2. Start the konsole-application belonging to kde4 (/usr/lib/kde4/bin/konsole)
 3. type "cd", space, tab
 4. Now, konsole wishes to play a "beep", but it seems like it needs to start the sound-system, and this takes some time. The result is that the konsole becomes completely unresponsive for a while.
 5. In my case, the entire konsole-window also went black, since I switched to another desktop and back, and konsole was busy with other things than redrawing the window.

After the step-by-step howto, there should be enough information to reproduce this and, IMO, not to be marked as incomplete. Anyways, here is the output when I reproduced the problem on another computer, this time using Xterm under Gnome:
~$ /usr/lib/kde4/bin/konsole
 ~$ konsole(10833) KToolInvocation::klauncher: klauncher not running... launching kdeinit
 kdeinit4: preparing to launch /usr/lib/kde4/lib/kde4/libexec/klauncher
 kdeinit4: Launched KLauncher, pid = 10908 result = 0
 kdeinit4: opened connection to :0.0
 kdeinit4: preparing to launch /usr/lib/kde4/bin/kded4
 kdeinit4: Launched KDED, pid = 10909 result = 0
 kdeinit4: Got EXT_EXEC '/usr/lib/kde4/bin/kbuildsycoca4' from launcher.
 kdeinit4: preparing to launch /usr/lib/kde4/bin/kbuildsycoca4
 kbuildsycoca4 running...
 kdeinit4: PID 10916 terminated.
 kdeinit4: Got EXEC_NEW 'kconf_update' from launcher.
 kdeinit4: preparing to launch /usr/lib/kde4/lib/kde4/libexec/kconf_update
 kdeinit4: PID 10917 terminated.
 kdeinit4: PID 10909 terminated.
 kdeinit4: Got EXT_EXEC '/usr/lib/kde4/bin/knotify4' from launcher.
 kdeinit4: preparing to launch /usr/lib/kde4/bin/knotify4
 kdeinit4: PID 10918 terminated.
 konsole(10833): Couldn't start knotify from knotify4.desktop: "KDEInit could not launch '/usr/lib/kde4/bin/knotify4'."
knotify(10919) Phonon::KdePlatformPlugin::createBackend: using backend: "Xine"
 konsole(10833) Konsole::SessionManager::setDefaultProfile: setting default session type to "Shell.profile"
~$
---
All i did in Konsole was to type in "cd d", press Tab and then notice that it takes a long time to respond. During the time it takes for konsole to respond again, it's completely unresponsive. I have two directories that starts with "d".