https://qa.mandrakesoft.com/show_bug.cgi?id=1610
------- Additional Comments From [EMAIL PROTECTED] 2003-02-14 04:16 -------
After upgrading to today's versions:
kdebase-3.1-29mdk
kdebase-devel-3.1-29mdk
kdebase-servicemenu-1.0-4mdk
kdelibs-3.1-23mdk
kdelibs-common-3.1-23mdk
kernel-enterprise-2.4.21.0.pre4.6mdk-1-1mdk
The same behavior is observed.
-C.S.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date:
description:
Launching a "Konsole" (/usr/bin/konsole) from the kicker panel in kde now freezes the
kicker panel, and it's child panels, until the konsole terminal session terminates.
When
the konsole session ends, a KDE Panel error dialog box (Title = "Sorry - KDE Panel")
is
displayed with the text: "KDEInit could not launch '/usr/bin/konsole'" with only the
option
button "OK". The konsole session functions (seemingly) perfectly, and it seems that
all
other KDE actions also work normally, except those that are bound to/docked with the
kicker panel. These applications do not respond to normal input until the konsole
session exits.
In my case, I have a child panel with the knews news ticker running, and i. It
freezes,
and accepts no input while a konsole launched from the kicker panel is active.
Similarly, the xmms-kde dock application stops scrolling the current track name, and
the
"OSD" option no longer displays the new track name when the track changes, all while
xmms itself continues to play normally.
Launching Konsole from the KDE Menu -> Run Command dialog box also fails to
function properly. In this case, the Konsole never fully loads, though the
panel/applets
do not freeze. (Terminating the konsole produces the same error dialog noted above.)
Launching a Konsole from another konsole (started from KDE menu -> Terminals ->
Konsole) produces results similar to launching from the KDE Menu -> Run Command
dialog, with the addition that the following output is produced: (Konsole configured
with
"Green Tint with Transparant MC" Schema)
---Begin---
[chas@visitoth chas]$ konsole
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
kdeui (KRootPixmap): WARNING: [virtual bool KSharedPixmap::x11Event(XEvent*)]
illegal selection notify event.
kdeui (KRootPixmap): WARNING: [krootpixmap.cpp:200] loading of desktop
background failed.
undecodable token: \001b(hex)[36l
kdeui (KRootPixmap): WARNING: [virtual bool KSharedPixmap::x11Event(XEvent*)]
illegal selection notify event.
kdeui (KRootPixmap): WARNING: [krootpixmap.cpp:200] loading of desktop
background failed.
kdeui (KRootPixmap): WARNING: [virtual bool KSharedPixmap::x11Event(XEvent*)]
illegal selection notify event.
kdeui (KRootPixmap): WARNING: [krootpixmap.cpp:200] loading of desktop
background failed.
---End---
Reconfiguring Konsole to use the "Konsole Default" Schema yields the same results,
except that the following output is obtained from launching from another terminal:
---Begin---
[chas@visitoth chas]$ konsole
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
konsole: cannot chown /dev/pts/2.
Reason: Operation not permitted
konsole_grantpty: determined a strange device name `/dev/ptmx'.
konsole: chownpty failed for device /dev/pts/2::/dev/pts/2.
: This means the session can be eavesdroped.
: Make sure konsole_grantpty is installed in
: /usr/bin/ and setuid root.
undecodable token: \001b(hex)[36l
---End---
*Or*
---Begin---
[chas@visitoth chas]$ konsole
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
undecodable token: \001b(hex)[36l
---End---
This problem *Only* affects the system when Konsole is launched from the panel.
Launching a konsole from the KDE menu does not exhibit the same problem.
