Bug 4879 - 2_b1: xconsole using 98.8% cpu
Summary: 2_b1: xconsole using 98.8% cpu
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-11 18:07 CET by Bit Twister
Modified: 2013-09-08 06:36 CEST (History)
0 users

See Also:
Source RPM: xconsole-1.0.4-1.mga1.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2012-03-11 18:07:13 CET 
Description of problem:

xconsole using 98.8% cpu in a single cpu system and 100% in a 4 cpu system in a runlevel 3 setup.

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. Clean install + all updates applied and xconsole installed.
2. cd /etc/systemd/system/
3. ln -sf /lib/systemd/system/multi-user.target default.target 
4. chmod 644 /var/log/messages
5. reboot
6. log in as a user
7. click up a terminal
8. xconsole -title "xconsole -file /var/log/messages" \
   -geom 1022x50+50+935 -file /var/log/messages &
9. top
Comment 1 Bit Twister 2012-03-11 20:37:40 CET 
Step 
6.5 startx
Comment 2 Marja Van Waes 2012-05-26 13:09:39 CEST 
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 3 Bit Twister 2012-05-26 15:51:53 CEST 
(In reply to comment #2)
> 
> Please report whether this bug is still valid for Mageia 2.

still valid.

Keywords: NEEDINFO => (none)

Comment 4 Bit Twister 2012-11-16 17:30:05 CET 
(In reply to comment #2)
Thought I would beat the rush. :)

Still valid in 3 alpha3
xconsole -title "xconsole -file /var/log/security.log" \
   -geom 1022x50+50+935 -file /var/log/security.log &
Comment 5 Bit Twister 2013-09-08 06:36:30 CEST 
Closing this bug since most logging is in journalctl.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.