Bug 196576 - knemo crash since KDE 3.5.3 update
Summary: knemo crash since KDE 3.5.3 update
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: knemo   
(Show other bugs)
Version: 5
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Hugo Cisneiros
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-25 05:02 UTC by Stefan Hoelldampf
Modified: 2014-06-24 03:37 UTC (History)
2 users (show)

Fixed In Version: 0.4.2-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-06-26 13:27:07 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
KDE backtrace (5.11 KB, text/plain)
2006-06-25 05:02 UTC, Stefan Hoelldampf 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Stefan Hoelldampf 2006-06-25 05:02:42 UTC 
Description of problem:
knemo crashes when clicking the systray icon since the KDE 3.5.3 update. See the
attachment for the KDE backtrace.

Version-Release number of selected component (if applicable):
knemo-0.4.1-2.fc5

How reproducible:
Click on the knemo systray icon

Steps to Reproduce:
1. Configure knemo
2. Click on the knemo systray icon
3.
  
Actual results:
knemo crashes

Expected results:
Normal behavior

Additional info:
I only have a Wireless LAN network device (madwifi driver) at the moment,
perhaps it might be related to this combination.
Comment 1 Stefan Hoelldampf 2006-06-25 05:02:42 UTC 
Created attachment 131497 [details]
KDE backtrace
Comment 2 Stefan Hoelldampf 2006-06-26 00:53:14 UTC 
I rebuilt the SRPM with the latest version 0.4.2 on my up-to-date FC5, the
problem seems to be gone.
I cannot check anymore whether it was related to the new version 0.4.2 or the
rebuild on KDE 3.5.3.
Comment 3 Hugo Cisneiros 2006-06-26 13:27:07 UTC 
Hi Stefan, thanks for your report. There was a bug in 0.4.1 upstream release 
that caused this behavior. The 0.4.2-1 package will be available in the next 
few hours on Fedora Extras repository.
Note You need to log in before you can comment on or make changes to this bug.