By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2615 - TCL/TK applications fail to start
Summary: TCL/TK applications fail to start
Status: RESOLVED DUPLICATE of bug 1375
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.1.x [Trinity]
Hardware: All Linux
: P5 critical
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2016-03-19 10:15 CDT by ThoMaus
Modified: 2016-03-19 11:04 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Error messages from "wish"/"ding" when started in "konsole" (438 bytes, text/plain)
2016-03-19 10:15 CDT, ThoMaus 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ThoMaus 2016-03-19 10:15:07 CDT 
Created attachment 2639 [details]
Error messages from "wish"/"ding" when started in "konsole"

TCL/TK applications based on "wish", e.g. "ding" fail to start -- see attachment.
The applications start without any problems under various other desktops on this OpenSuSE Tumbleweed installation. Trintity is at 14.0.3.


I consider this a critical bug, as whole classes of applications fail to start in a manner quite confusing and unresolvable for end-users: If started from the menu (kicker/kickoff) no error feedback whatever is available! 

A detailed discussion of the same behavior under KDE4 is found here:
https://bugzilla.redhat.com/show_bug.cgi?id=1043686

I suspect a common root cause, so the remediation for KDE4 should give some indication, what the actual problem is.

This bug seems related to bug 1375.
Comment 1 Slávek Banko 2016-03-19 11:04:36 CDT 
Yes, the problem here from time to time appears again and again. This is still a problem filled in bug 1375. Therefore, I close this bug report as a duplicate.

*** This bug has been marked as a duplicate of bug 1375 ***