[00:05] <adam_g> 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] <adam_g> or should adduser be moved to each package in question instead of defining globally, to shut lintian up?
[00:09] <slangasek> adam_g: there's a way to shut lintian up, but I would argue it's simpler to just comply
[00:22] <cjwatson> adam_g: I would in general argue that direct use should imply direct dependency
[02:19] <psusi> 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:21] <infinity> psusi: Sure, I'll milestone it. :P
[02:21] <infinity> psusi: You could just fix it instead! ;)
[02:22] <psusi> I have, just waiting for a sponsor to merge
[02:22] <infinity> Ah, so I see.
[02:23] <infinity> I'll have a look at it in a bit, then.
[02:23] <infinity> psusi: Are you around for a bit tonight, in case I have questions?
[02:23] <psusi> infinity, sure
[02:24] <infinity> 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] <psusi> hehe... never can tell with a new baby
[02:25] <infinity> ;)
[02:25] <infinity> Congrats.
[02:25] <psusi> ty
[03:44] <bitplane-> 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] <bitplane-> 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] <infinity> 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] <infinity> bitplane-: Odds are that it keys off a magic environment variable being set, or the program being run with --debug.
[05:01] <pkh> 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] <pkh> #ubuntu-kernel
[09:29] <broder> 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)
[13:20] <PaoloRotolo> Hi al!
[13:20] <PaoloRotolo> all*
[13:43] <georgelappies> 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?
[14:50] <kklimonda> georgelappies: hard to say, I'm not seeing this problem
[14:51] <kklimonda> georgelappies: if X is crashing it should ask you to upload the report to LP
[15:06] <georgelappies> kklimonda: it does look like X, i tried ATI proprietary drivers as well but the crash still happens...
[15:24] <georgelappies> kklimonda: where could the log files be that would indicate the source of this bug? can I somehow enable logging?>
[15:28] <kklimonda> georgelappies: if it crashed you should get a log in /var/crash
[15:31] <georgelappies> kklimonda: if it is not in /var/crash does it mean that maybe the kernel crashed and not X?
[15:31] <kklimonda> georgelappies: ah yes, that's also possible (I think I misread your question)
[15:34] <georgelappies> kklimonda: is their log files the kernel writes to on a crash?
[15:34] <kklimonda> georgelappies: I'd try to ask people on #ubuntu-x in that case during week, they have more experience debugging such issues
[15:35] <kklimonda> georgelappies: you can check /var/log/syslog and /var/log/syslog.1
[15:36] <kklimonda> if computer hasn't completely locked up there is a chance that something ended up there
[16:06] <georgelappies> kklimonda: thanks, will do ;)
[18:42] <slangasek> 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
[20:31] <Spartan29> hallo!
[20:31] <Spartan29>  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?
[23:28] <juliohm> Someone could reproduce the bug? https://bugs.launchpad.net/ubuntu/+source/procps/+bug/965341
[23:29] <juliohm> How are launchpad bugs triggered? There are days since i reported the bug and stills undecided state.
[23:35] <penguin42> 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] <astraljava> 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] <juliohm> 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] <penguin42> juliohm: Until someone looks at it, they don't realise it's so easy to reproduce!
[23:44] <juliohm> 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] <juliohm> Anyways, thank you for take the look. ;-)
[23:46] <penguin42> 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] <juliohm> 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] <penguin42> juliohm: possibly https://help.ubuntu.com/community/ReportingBugs   although it doesn't say much about what happens next
[23:51] <juliohm> penguin42, that one i already know
[23:51] <juliohm> But i'm talking about the launchpad features, the daily activities of a Ubuntu-bug-reporter
[23:54] <penguin42> 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] <penguin42> 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] <juliohm> ok, thanks penguin42 , i'll ask in the appropriate channel. ;-)
[23:56] <juliohm> 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] <penguin42> 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] <juliohm> for me, segfault is always a bug
[23:57] <penguin42> juliohm: The question is whether the bug is in watch or the C library
[23:57] <juliohm> independently of the program.
[23:57] <juliohm> oh
[23:57] <juliohm> I don't know.
[23:59] <cjwatson> 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] <cjwatson> (C99 7.4 para 1)