[00:05] is there some way to work around the maintainer-script-needs-depends-on-adduser lintian error, if the packages its pointing at all depend on a common package, which has adduser as a Depends? [00:05] or should adduser be moved to each package in question instead of defining globally, to shut lintian up? [00:09] adam_g: there's a way to shut lintian up, but I would argue it's simpler to just comply [00:22] adam_g: I would in general argue that direct use should imply direct dependency === dendro-afk is now known as dendrobates [02:19] is there something more that bug #941874 needs to make sure it's on the radar as a critical regression that needs fixed before precise is finalized? like a milestone target? [02:19] Launchpad bug 941874 in multipath-tools (Ubuntu) "(fakeraid) root device not activated during boot" [Critical,In progress] https://launchpad.net/bugs/941874 [02:21] psusi: Sure, I'll milestone it. :P [02:21] psusi: You could just fix it instead! ;) [02:22] I have, just waiting for a sponsor to merge [02:22] Ah, so I see. [02:23] I'll have a look at it in a bit, then. [02:23] psusi: Are you around for a bit tonight, in case I have questions? [02:23] infinity, sure [02:24] psusi: Alright. I'll poke it later tonight. If you decide to go have a life instead, I'll either sponsor or leave feedback on the bug, as appropriate. [02:24] hehe... never can tell with a new baby [02:25] ;) [02:25] Congrats. [02:25] ty === jalcine_ is now known as jalcine === jalcine_ is now known as jalcine [03:44] Hi, I was bored and decided to try fixing one of the bugs on the tracker. I decided on a seemingly simple one, the text size in notify bubbles being wrong [03:45] I have a stupid question though... there's debug statements in the code, how would I normally activate them? do I have to go and tell g++ to compile with DEBUG defined, or is there a better way? [04:40] bitplane-: If you're talking about the code having something like DEBUG("foo") in it, find the declaration of DEBUG and see what it does. [04:41] bitplane-: Odds are that it keys off a magic environment variable being set, or the program being run with --debug. [05:01] i'm running a machine on 12.04 and the last few kernel updates have failed to find my network driver. i'm wondering what I should do wrt to reporting that. [05:01] #ubuntu-kernel [09:29] slangasek: can you or possibly somebody else from foundations look into/fix bug #941867? i would but i'm not going to have time in the next few weeks (starting a new job on monday) [09:29] Launchpad bug 941867 in insserv (Ubuntu) "after upgrade to 1.14.0-2.1ubuntu0.1 0 dpkg --configure ror" [Undecided,Confirmed] https://launchpad.net/bugs/941867 === _salem is now known as salem_ === salem_ is now known as _salem [13:20] Hi al! [13:20] all* === yofel_ is now known as yofel [13:43] hi all, I am using 12.04 I am getting random crashes to a terminal like screen were I have to hard reboot the laptop. this never happened in any of the prior ubuntu releases. Is there a known issue at the moment? === Quintasan_ is now known as Quintasan === albrigha is now known as Guest33734 [14:50] georgelappies: hard to say, I'm not seeing this problem [14:51] georgelappies: if X is crashing it should ask you to upload the report to LP [15:06] kklimonda: it does look like X, i tried ATI proprietary drivers as well but the crash still happens... [15:24] kklimonda: where could the log files be that would indicate the source of this bug? can I somehow enable logging?> [15:28] georgelappies: if it crashed you should get a log in /var/crash [15:31] kklimonda: if it is not in /var/crash does it mean that maybe the kernel crashed and not X? [15:31] georgelappies: ah yes, that's also possible (I think I misread your question) [15:34] kklimonda: is their log files the kernel writes to on a crash? [15:34] georgelappies: I'd try to ask people on #ubuntu-x in that case during week, they have more experience debugging such issues [15:35] georgelappies: you can check /var/log/syslog and /var/log/syslog.1 [15:36] if computer hasn't completely locked up there is a chance that something ended up there [16:06] kklimonda: thanks, will do ;) === allquixotic_ is now known as allquixotic [18:42] broder: yeah... sorry, I had foreseen that as a possible issue when reviewing your patch but had assumed nobody would have a *partially* fixed system in this way === kasper is now known as eights === vibhav is now known as Guest16852 [20:31] hallo! [20:31] I've a trouble. I can't share files from linux to windows, files are in a folder of an NTFS partition mounted on boot time. What i see is that i can't change folder and than in it contained files. Can someone help me? === dendrobates is now known as dendro-afk [23:28] Someone could reproduce the bug? https://bugs.launchpad.net/ubuntu/+source/procps/+bug/965341 [23:28] Launchpad bug 965341 in procps (Ubuntu) "watch command line utility crashes with segfault when processing binary output" [Undecided,New] [23:29] How are launchpad bugs triggered? There are days since i reported the bug and stills undecided state. [23:35] juliohm: It relies on someone triaging it - there are lots of bugs, so it's a matter of time available and luck, it depends on the package as well and if someone tries it [23:35] juliohm: They are not automagically handled, except for some simple cases. They need to be triaged in order to progress. More info on #ubuntu-bugs channel. [23:41] Understand, just wondering because that was my first report to launchpad. I was thinking the community was more active in the sense that the bug is easily reproducible. In other track systems i've reporting bugs, the state is decided pretty fast. [23:43] juliohm: Until someone looks at it, they don't realise it's so easy to reproduce! [23:44] penguin42, oh, i was thinking people is notified in their mail box with some kind of summary of what the bug is about. :-) [23:45] Anyways, thank you for take the look. ;-) [23:46] juliohm: Some people will be, but they just get zillions of notifications; so they pick off stuff which is affecting lots of people or causing major panics and occasionally get around to looking at the rest [23:49] I can imagine a lot of notifications, one more reason why i have to make a post about how to contribute in launchpad. Do you have some nice blog post about contributing with Ubuntu on Launchpad? [23:50] juliohm: possibly https://help.ubuntu.com/community/ReportingBugs although it doesn't say much about what happens next [23:51] penguin42, that one i already know [23:51] But i'm talking about the launchpad features, the daily activities of a Ubuntu-bug-reporter [23:54] juliohm: there is a #launchpad that may help somewhat - but that's the mehcanics of the system more, #ubuntu-bugs is perhaps a better place to ask about that, and see the info on bugsquad and bugcontrol [23:55] any libc standards lawyers about - juliohm's bug seems to be isprint segfaulting when passed invalid input - I just don't know whether it's correct for it to do that [23:55] ok, thanks penguin42 , i'll ask in the appropriate channel. ;-) [23:56] penguin42, the bug with watch is not just a print in the binary file, because watch is interactive, it should hang until a Ctrl+c [23:56] the manpage for isprint and friends says 'These functions check whether c, which must have the value of an unsigned char or EOF, ....' - is it reasonable for it to seg if the value isn't an unsigned char or EOF? [23:56] for me, segfault is always a bug [23:57] juliohm: The question is whether the bug is in watch or the C library [23:57] independently of the program. [23:57] oh [23:57] I don't know. [23:59] the behaviour of isprint is undefined if it is passed something other than a value representable as an unsigned char or EOF; undefined behaviour includes the potential to segfault [23:59] (C99 7.4 para 1)