Bug 183896 - Plasma is crashing when set FileWatcher to watch /var/log/systemlog
Summary: Plasma is crashing when set FileWatcher to watch /var/log/systemlog
Status: RESOLVED DUPLICATE of bug 168278
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-10 10:56 UTC by Simon Gebauer
Modified: 2009-02-10 11:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Gebauer 2009-02-10 10:56:03 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

  Loaded plugins
Standart-plasmaoids + three Folder Views + of course FileWatcher

  Backtraces
No backtrace information available

 How to Reproduce
My System crashes everytime I add FileWatcher to set it to watch /var/log/systemlog

 Expected Behaviour
Well - it shouldn't crash.


Bug appeared on Ubuntu 8.10 with KDE 4.2 from the ppa-repositories.
Comment 1 Anne-Marie Mahfouf 2009-02-10 11:16:33 UTC
Cannot reproduce on trunk, it does not crash on trunk but says 'Cannot watch non-text file /var/log/syslog' which is the expected behaviour.

Does it work OK for normal text files? (files that you have permission to read and are readable)

Can you try running it through gdb? either the whole plasma or appletviewer fileWatcher maybe to get a backtrace (provided you have debug symbols of course)
Comment 2 Simon Gebauer 2009-02-10 11:46:56 UTC
/var/log/syslog is a plain textfile on my system. As i read on other bugzilla-installations this is a known bug. But as I didn't read it here yet, but on https://bugzilla.redhat.com/show_bug.cgi?id=474042 , I decided to post it here as well. 

... I just found a bugreport here. https://bugs.kde.org/show_bug.cgi?id=168278

Marking as duplicate of bug # 168278 and waiting for qt 4.4.4

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