/srv/irclogs.ubuntu.com/2010/11/07/#ubuntu-bugs.txt

penguin42I wonder what the right thing to do with bug 671837 is01:39
ubot2Launchpad bug 671837 in xorg-server (Ubuntu) "Xorg crashes due to known bug in Xinerama code (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/67183701:39
penguin42it references an upstream mailing list (not a bug report though) and points to a patch01:40
penguin42hmm bed01:45
cjaemay I describe a problem and someone tell me how to best describe it for a bug report08:49
cjaeI have images of the issue as well08:50
=== yofel_ is now known as yofel
=== AbhiJit is now known as Guest27905
=== AbhiJit_ is now known as AbhiJit
nemoTrying to draw a little attention to my somewhat humerous yet rather damaging bug.15:12
nemobug #66149415:12
ubot2Launchpad bug 661494 in x11-apps (Ubuntu) "Request to limit xinit writes to .xsession-errors to some reasonable value, such as 10 megs (affects: 1) (heat: 157)" [Undecided,New] https://launchpad.net/bugs/66149415:12
nemowondering if I could get one of the good folk of this channel to look it over, maybe, dunno, say whether the idea has merit15:12
* penguin42 looks15:16
penguin42hehe, 373G that might be a record15:16
yofelindeed, at least I haven't yet seen another report with a file >100GiB yet15:17
penguin42nemo: So I've seen the same thing happen many times - I used to admin a ~100 person network with peoples ~ on NFS, and filling up /home due to .xsession-errors was a common screw up15:18
nemopenguin42: but. yeah. why on earth isn't this piped to head or a rolling log appender?15:19
nemoseems like a trivial fix15:19
nemopenguin42: if the log really overshot, say, 10 megs, it probably shouldn't be growing more anyway15:19
nemoit isn't like the information in it is critical15:19
nemoor 20 megs or 40. whatever15:20
nemo... or a percentage of the disc that $HOME is on...15:20
nemoor /home :)15:20
kklimonda_nemo: if it seems like a trivial fix and still it isn't fixed then it probably isn' trivial after all ;)15:21
nemokklimonda_: quite possibly, but then it should be easy to shoot down the trivial fix :)15:22
nemohm15:22
nemoI guess I could make some headway by, oh, trying head -c on my local system15:22
kklimonda_nemo: I do remember that at some point it was limited - after some time no new messages were logged. And it was terrible ;)15:22
nemokklimonda_: depends on what it was limited to15:22
nemoin a normal session, it'll never get more than a few megs15:22
nemobut if the limit is set high, then if it hits it, you're probably glad it did15:22
nemoas I would have been15:23
nemobut. ok. lemme test my trivial solution w/ a ceiling of, oh, 50 megs15:23
=== JoeSett is now known as JoeMaverickSett
nemokklimonda_: a rolling log app would avoid the halting errors prob of course, since it could just keep .xsession-errors and .xession-errors.1.gz etc w/ a few copies15:30
kklimonda_nemo: sure but X would have to support it15:30
nemowhy?15:30
nemothis is outside of X15:30
kklimonda_nemo: well, actually the application that does log it there15:30
nemounless you mean as a dependancy in ubuntu15:30
nemoexec >"$ERRFILE" 2>&115:30
nemovs15:30
nemoexec 2>&1 | head -c 5000000 > "$ERRFILE"15:31
nemoor15:31
nemoexec 2>&1 | rollinglogfile "$ERRFILE"15:31
yofelXsession is only run once right?15:31
kklimonda_$ rollinglogfile15:31
kklimonda_rollinglogfile: command not found15:31
kklimonda_:P15:31
nemokklimonda_: smartass15:31
nemokklimonda_: I'm sure they exist, and not just as generic logging mechanisms15:32
nemoworse to worse, could use one of those15:32
kklimonda_probably, someone should investigate :)15:32
nemowell. I'm trying head -c 50000000 right now :)15:32
nemoif *that* works it'd already be a lot less evil to users15:33
nemokklimonda_: hm. there's some truncation code in there now, but looks like it is just called on starting a new exec15:34
yofelwell, /etc/X11/Xsession has a DoS protection currently... but the way it's done it's pointless if it gets run just once (line 77ff in maverick)15:34
nemodoesn't limit the existing session15:34
nemoyofel: yeah. reading that15:34
nemoyofel: and is much more aggressive than me. limits to only 50000015:35
yofelright15:35
nemoso clearly 5 megs or 50 megs is a generous sanity15:35
nemolimit15:35
penguin42nemo: doing a log rotate type of thing might work15:37
nemohead -c 5000000 seems to be working fine too :)15:38
nemoI'll put it on all my systems15:38
nemobut15:38
nemoit'd be nice to not have to merge it15:38
nemooh well. just trying to get some visibility. and yes, 373 gigs is extreme15:39
nemowhat is alarming is how easily it happened15:39
nemoand the result basically shut down the system for that user15:40
penguin42nemo: Yeh it only takes one app to go nuts15:40
nemopenguin42: hell. someone could possibly do it w/ a web browser. plugins and such sometimes write to err15:40
nemoI could DOS an ubuntu user remotely15:40
nemoif I was clever15:40
nemoand I got them to hang out on my page long enough15:41
penguin42nemo: There are some related problems 1) It's difficult to tell what actually wrote into the log and 2) No one really takes care to clean apps up so they don't normally15:41
nemoI think webgl still does a bit of error spam in some situations, that would avoid even needing to load a plugin :)15:41
kklimonda_well, "a bit of error spam" isn't bad15:41
nemopenguin42: well. those are more usability. I'd just like to not have it kill my systems by accident ;)15:41
kklimonda_the Oracle Installer is an extreme case15:42
penguin42kklimonda_: I've seen lots of other things do similar15:42
kklimonda_penguin42: oh? that's the only app I've seen doing that :)15:42
kklimonda_some do spam a lot15:42
kklimonda_but not nearly enough15:42
kklimonda_for it to be a concern (enter fail) ;)15:43
nemowell15:43
nemolet me check what gets written in firefox on plugin / webgl activation15:43
nemoI bet I could whip up a page that is malicious15:43
nemow/o it using too much CPU15:43
yofelnemo: can you give me the *exact* syntax of exec you want to use? (the one with head)15:43
nemohell. noscript writes to stderr15:43
nemoyofel: can show you what I'm testing in my VM right now, sure15:44
kklimonda_nemo: but that would require you to have a malicious intent.15:44
nemokklimonda_: yes. but remote malicious intent15:44
nemojust as bad as local accidental :)15:44
nemoand insidious since oomkill won't pick it up and it'd persist15:44
nemoyofel: exec 2>&1 | head -c 50000000 >>"$ERRFILE"15:46
nemoyofel: the other truncation code will still work fine on restart.15:46
nemo.xession-errors still seemed to be written to normally15:47
nemoyofel: cleverer code might do a fraction of disc, but 50 megs isn't that much in this day and age.  anyone really short on space might want to use /dev/null anyway :-p15:48
yofelhm, right, this does work, but with head the limit should be like 50MiB, some apps do put a lot of messages in there, and they rarely fail at the beginning15:49
nemoyofel: that *is* 50 megs15:49
nemoadmittedly not 50MiB ;)15:49
yofelerr, right, too many zeroes :P15:49
nemobut. yeah 2 orders of magnitude more than the truncation15:49
yofelthe truncation code uses tail which is the right thing to use, but I agree that head with a sane limit would be ok to use. Won't protect against everything, but against most failures I guess15:51
nemoeasier than hooking up a rolling appender :-p15:52
nemocould do that as a "later"15:52
=== kyubutsu is now known as Guest18874
CarlFKhttp://dpaste.de/mGIK/  *** buffer overflow detected ***: tftp terminated======= Backtrace: =========/lib/libc.so.6(__fortify_fail+0x37)[0x7f29b446b527]...22:05
CarlFKwhats the shell command to post the bug report to lp?22:06
yofelCarlFK: run 'sudo service apport start force_start=1' - crash it again and file the crash report in /var/crash with ubuntu-bug (if it hopefully catches the crash)22:52
CarlFKgot it already. but thanks22:53
yofelnp, sorry for being late22:53
CarlFKwhile I got you, question bout https://wiki.ubuntu.com/DebuggingProgramCrash22:53
CarlFKecho "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse" | sudo tee -a /etc/apt/sources.list.d/ddebs.list22:53
CarlFKwhy not use  apt-add-repository "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse22:53
yofelbackwards compatibility I think. As far as I know hardy doesn't have add-apt-repository22:54
CarlFKk22:54
CarlFKand is there a way to do that in a preseed file that doesn't hardcode "natty"?22:55
CarlFKd-i apt-setup/local0/repository string http://ddebs.ubuntu.com natty main restricted universe multiverse22:55
yofelCarlFK: it uses '$(lsb_release -cs)' which will insert natty only if you run it on natty22:55
CarlFKpreseed file22:55
CarlFKreally an installer question than a -debug22:56
yofelI don't know about preseed files I fear22:56
CarlFKno prob22:57
yofelmaybe ask in #ubuntu-installer if it's d-i specific22:57
drizzleCan someone wishlist https://bugs.launchpad.net/ubuntu/+source/glade-3/+bug/672313 please23:03
ubot2Launchpad bug 672313 in glade-3 (Ubuntu) "Maximized window not remembered (affects: 1) (heat: 6)" [Undecided,Opinion]23:03
=== Guest18874 is now known as kyubutsu

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!