Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#27956 - gnash-gtk errors fill partition in /var/log/slim.log

Attached to Project: Arch Linux
Opened by Matthew Nubbe (mnubbe) - Monday, 16 January 2012, 06:31 GMT
Last edited by Jan Alexander Steffens (heftig) - Wednesday, 18 January 2012, 09:33 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Slim seems to log gnash-gtk stacktraces without end. Not 100% sure which is the cause, but this continues until the disk is full.

Additional info:
* package version(s): slim: 1.3.2-6, gnash-gtk 0.8.9-7
* config and/or log files etc.: section of the log file attached

Steps to reproduce:

chromium starts up automatically to view a flash item (youtube video) that was in a previous session
gnash-gtk seems to be spinning
/var/log/slim.log expands with messages related to gnash-gtk
(eventually) other things get hosed by disk full-related errors

I recently pacman -Syu'd (today) and see this. I believe gnash-gtk is new but slim is definitely not. I think both had updates.
   slim.log.sample (196.6 KiB)
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Wednesday, 18 January 2012, 09:33 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.9.8-8
Comment by Jan Alexander Steffens (heftig) - Tuesday, 17 January 2012, 05:24 GMT
How much data per hour are we talking here?
Comment by Matthew Nubbe (mnubbe) - Wednesday, 18 January 2012, 03:20 GMT
On the order of GB/hr I think, but I am not sure. The files reached 42GB. Lowest it could have been would be 1GB/day assuming I remembered the uptime at reboot correctly. Want me to run a test on this for more exact numbers?
Comment by Jan Alexander Steffens (heftig) - Wednesday, 18 January 2012, 08:44 GMT
I can see two problems here:

1) gnash is too noisy
2) slim doesn't redirect stderr of the user session to something like ~/.xsession-errors

Since slim is discontinued, 2) will not be fixed and will have to be done in .xinitrc or similar. That leaves 1).

gnash 0.8.9 enabled some very verbose stack debugging. I'll disable it.

Loading...