[02:53] <dougg3> I reported a crashing bug in caja on bugs.launchpad.net, and it got marked as a duplicate by apport retracing service. But the bug it's a duplicate of is private...how can I provide more info about the bug and check on its fix status if the original report is private?
[03:02] <dougg3> FWIW, my report is here: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1645944
[04:02] <australopithecus> Hello so I installed ubuntu 16.1 I have a gefore 1070 installed graphics driver 370, and a 6600k intel cpu, my computer is unable to adjust brightness
[04:03] <australopithecus> which is a huge deal breaker for me because I have a laptop
[04:03] <australopithecus> I am unable to find a fix online for this issue I was wondering if one of you would be able to help me
[04:03] <australopithecus> my screen feels like it is frying my eyes
[04:22] <ali1234> dougg3: bug reports are automatically marked private if they contain backtraces because they can reveal private information
[04:24] <ali1234> if it is still private at this point then nobody is working on it, if they were the first thing they'd do is remove the core file and mark it public
[04:40] <dougg3> ali1234: thanks, that makes sense -- is there anything I can do on my end to try to help with the bug then? my particular report contained a description on how to reproduce it, and I feel there's a good chance the original private report may not have been as useful...
[04:40] <ali1234> dougg3: you can remove the core dump and mark it public
[04:41] <ali1234> and maybe unmark it as a duplicate, and write a better title
[04:41] <dougg3> I already marked my bug as public and apport already stripped the core dump
[04:42] <dougg3> I have no idea what the private report's title even is though. :-/
[04:42] <ali1234> next thing to do is probably to forward the bug to upstream developers
[04:42] <dougg3> like create a github issue on the caja github?
[04:43] <ali1234> it was fixed in nautilus?
[04:43] <dougg3> yeah, I helped them track it down in nautilus last year. then I switched to MATE this year after someone made me aware of it, and I'm dealing with the bug again. heh
[04:44] <ali1234> go here and ask them to port over the fix: https://github.com/mate-desktop/caja/issues
[04:44] <dougg3> that's what I was thinking. thanks! is there a way I can prod the ubuntu people to pull the fix back into 16.04 after that? or will it just happen automagically?
[04:45] <ali1234> you can link your launchpad bug report to the upstream bug, and then mark it "fix available" when upstream fixes it
[04:45] <ali1234> but it probably won't speed up getting the fix into ubuntu any
[04:46] <dougg3> ah, got it. well, thanks for the info ali1234. that was very helpful information!
[04:46] <dougg3> I guess I'll just start with the upstream folks and see what happens from there.
[06:55] <zzp> z
[07:57] <baap> crosoft office on ubuntu how to do that
[12:49] <matej_> hi all
[12:51] <matej_> who have raspberyy pi 2
[12:51] <matej_> exit
[13:41] <kly> miaaa
[15:10] <timo_> Someone who uses German Keyboard Layout here/QWERTZ
[16:55] <mate|35298> hi
[18:28] <TwoNotes> I need to get libcursesw.so.6 on my 16.4 RPi3.  apt does not list it.  Is there a way to get it?
[21:19] <slim> why the flag button doesn't work in ubuntu mate like shortcut for search bar
[22:57] <DarkPsydeLord> becaue ctrl + space is usual combo for search bar