Bug 158481 - seamonkey does not come with proper icon (KDE)
Summary: seamonkey does not come with proper icon (KDE)
Status: RESOLVED DUPLICATE of bug 158556
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: X11 Applications (show other bugs)
Version: Beta 8
Hardware: i386 SuSE Linux 10.1
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-16 00:54 UTC by Gerald Pfeifer
Modified: 2006-03-16 10:15 UTC (History)
0 users

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
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 Gerald Pfeifer 2006-03-16 00:54:25 UTC 
I added seamonkey to my KDE panel, only to find that it does not come with
a proper icon, but displays the default gear-wheel icon in the taskbar.

Similarly, under "Add Application to Panel" - "Internet" - "Web Browser" the
other browsers on my system (Epiphany, Firefox, Konqueror) all come with icons
in the menu, just SeaMonkey does not have one.
Comment 1 Gerald Pfeifer 2006-03-16 00:56:46 UTC 
This may, or may not, be related, but when starting seamonkey on a shell,
I get the following:

/home/gpl/.gtk_qt_engine_rc:28: Unable to locate image file in pixmap_path: "32x32/filesystems/folder_home.png"
/home/gpl/.gtk_qt_engine_rc:29: Unable to locate image file in pixmap_path: "32x32/filesystems/folder_home.png"
/home/gpl/.gtk_qt_engine_rc:30: Unable to locate image file in pixmap_path: "16x16/filesystems/folder_home.png"
/home/gpl/.gtk_qt_engine_rc:31: Unable to locate image file in pixmap_path: "16x16/filesystems/folder_home.png"
/home/gpl/.gtk_qt_engine_rc:32: Unable to locate image file in pixmap_path: "16x16/filesystems/folder_home.png"
Comment 2 Stephan Binner 2006-03-16 10:15:42 UTC 
The initial report is dupe of 158556

Comment #1 is likely unrelated and reported in 157455

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