| Summary: | kwifimanager crashes - problem reporting on "bugs.kde.org" | ||
|---|---|---|---|
| Product: | [Unmaintained] kwireless | Reporter: | David Hart <dchart> |
| Component: | general | Assignee: | Stefan Winter <swinter> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | thomas.bettler |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | RedHat Enterprise Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
David Hart
2004-05-09 18:12:03 UTC
Presents itself a little differently to me: Kwifimanager starts, but only as long as the WLAN card is absent from the system. It crashes with SIGFPE as soon as either a) the card is being plugged in while kwifimanager is running, or b) when it is started with the card plugged in. I'm not getting the "Alarm clock" message, but there's at least one report by another Gentoo user who has encountered the exact same error as the original reporter of this bug, here: http://forums.gentoo.org/viewtopic.php?t=174144. My environment: Gentoo Linux (gcc-3.3.3, glibc-2.3.3_pre20040420-r0, kernel 2.6.6-mm4) Wireless tools version 27-pre22 Kwifimanager from KDE 3.2.2 Please provide the backtrace from the KDE Crash handler. I am really curious where exactly that SIGFPE occurs... Concerning the alarm clock: I couldn´t reproduce this, since it doesn´t occur on any of my boxes, so it´s hard to find the cause. But maybe at least the SIGFPE can be resolved quickly. I upgraded to FC2 and kwm is no longer included. On Sat, 2004-05-22 at 04:00, mail@stefan-winter.de wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=81204 > > > > > ------- Additional Comments From mail stefan-winter de 2004-05-22 10:00 ------- > Please provide the backtrace from the KDE Crash handler. I am really curious where exactly that SIGFPE occurs... > Concerning the alarm clock: I couldn Same problem here on Gentoo, w 2.6.6. kdenetwork 3.2.3 Starting kwifimanager from shell gives Alarm Clock. If ndiswrapper module is removed it will start fine, but with the ndiswrapper module in place the app crashes consistently. jup, same here. 2.6.5-gentoo-sources orinoco / thinkpad r32 kde 3.2.3 Finally, the source for the "Alarm Clock" problem seems to be found. The
problem lies in the way Gentoo installs its kernel sources. It produces an
oddity that leads to a version mismatch in the wireless extensions.
Unfortunately, it shows up only when compiling KDE (and thus KWiFiManager is
the only program on which it has an impact). A user with some knowledge of
doing decent debugger work found this glitch (thank you very much, Markus
Moll!).
/usr/include/linux contains its own set of kernel headers, which unfortunately
don´t necessarily matches the set of header files
in /usr/src/linux/include/linux, which it should.
The temporary workaround for this problem is as follows:
Make /usr/include/linux a symlink pointing to /usr/src/linux/include/linux and
re-emerge kdenetwork.
("ln -s /usr/src/linux/include/linux /usr/include/linux") after deleting /
renaming /usr/include/linux.
I will probably open a bug report on Gentoo´s bugzilla to make this
distribution behave like that per default. After they have updated their
packages, the workaround should become obsolete.
The original reporter of this bug said he is using Fedora, but is the only one who ever reported this problem under FC. He should check whether he has/had the same problem.
If this workaround works for Gentoo (I sure do hope so), please attach a comment. I will then close the bug.
Greetings,
Stefan Winter
Thanks a lot for all your work! It's running fine now on Gentoo with kernel 2.6.x ... we got it. Greetings tom *** Bug has been marked as fixed ***. |