Bug 81503
Summary: | konqueror crashes on a double click | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Michal Jaegermann <michal> |
Component: | kdebase | Assignee: | Than Ngo <than> |
Status: | CLOSED RAWHIDE | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | phoebe | CC: | wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-02-10 19:11:03 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 79578 |
Description
Michal Jaegermann
2003-01-09 23:04:45 UTC
I can't reproduce this. How big is that text file that caused the crash? Does it occur with any text file? Any other type of file? If it occurs only with one text file, please send that to me directly via e-mail so I can test it too. All right! When /usr/bin/desktop-create-kmenu runs into troubles (one possible reason is shown in bug #81512 but there are likely multiple other failure modes) then /var/lib/menu/kde is absent. Then clicking in a konqueror window on an icon for a file which has a name with a suffix (say 'my.log') without a predefined action is causing an immediate SIGSEGV with a backtrace as described. A file content is totally immaterial. As an aside, I always thought that 'file' utility determines file types on Linux/Unix because "extensions" are really worthless for anything serious. For an extra fun even if /var/lib/menu/kde is already there but /usr/bin/desktop-create-kmenu failed then, before bailing out, it will clobber an old /var/lib/menu/kde anyway; but this kind of fragility in KDE is hardly of any surprise. it's fixed in 3.1-5 or newer. |