|
Bugzilla – Full Text Bug Listing |
| Summary: | App-specific icons get "lost" while changing KDE styles | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Reinhard Gimbel <opensuse> |
| Component: | KDE | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | alex.loes, forgotten_--EoyBps8f, miguelduarte, opensuse |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Screenshot with OK-state (i.e. firefox icon available)
Screenshot with NOK-state (i.e. firefox icon replaced by "placeholder") |
||
|
Description
Reinhard Gimbel
2005-08-27 11:12:09 UTC
Created attachment 47855 [details]
Screenshot with OK-state (i.e. firefox icon available)
Created attachment 47856 [details]
Screenshot with NOK-state (i.e. firefox icon replaced by "placeholder")
I can confirm the behavior. While browsing for a different problem I found a work-around/solution(?) for the "missing icons"-issue. It is related to file /opt/kde3/share/icons/default.kde/index.theme More details are mentioned in thread http://www.linux-club.de/viewtopic.php?t=39850&highlight=icons The work-around/solution described in the thread mentioned above works for me. I don't know if that work-around/solution helps to find the real cause. BTW: The "missing icons"-issue is somwhow related to the "missing add new tab button"-issue as mentioned in https://bugzilla.novell.com/show_bug.cgi?id=113534 The missing "add new tab" re-appeared after applying the work-around/solution described above ... If I am correct, this is similar to my experience losing non-KDE icons after an upgrade in SuSE Pro 9.3. I think it was something from KDE supplementary that broke it. It was the latest kdelibs build that broke it for 9.3 I think, at least reverting that one "solves" the issue. do you agree that this can be closed as duplicate to bug 114951 ? *** This bug has been marked as a duplicate of 115139 *** Questions are if those bugs (114951, 115139) are duplicates of this bug or vice versa ... ;-) Have anyone tested if the work-around mentioned above (comment #4) leads into finding the root cause for the trouble ? *** Bug 116108 has been marked as a duplicate of this bug. *** *** Bug 114381 has been marked as a duplicate of this bug. *** |