=== OutOfControl is now known as benonsoftware
=== JoseeAntonioR is now known as jose
=== FourDollars_ is now known as FourDollars
[11:23] <brainwash> can anyone please re-open bug 1290575 ?
[11:23] <ubot2> Launchpad bug 1290575 in LightDM GTK+ Greeter "lightdm-gtk-greeter does not exit cleanly when logging in" [High,Confirmed] https://launchpad.net/bugs/1290575
[11:24] <brainwash> the bug is not fully fixed
[11:26] <brainwash> the status has been already set back to "confirmed", but "fix released" seems to override it
[12:16] <rbasak> brainwash: done. Note that there are two bug tasks there - one for the upstream project; one for the package in Ubuntu. Bug status applies independently to each task.
=== back is now known as Guest81905
=== Guest81905 is now known as bakc
=== om26er_ is now known as om26er
[20:12] <jobin> Hey all! I am trying to help with triaging bugs at launchpad with the nautilus package and have come across some bugs which are related to 13.04 release which is now past its EOL. What is the procedure to deal with such bugs? I would like to know since I am a newbie at triaging and hence please forgive my naivety.
[20:16] <jobin> One of the bugs here FYR: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1235457
[20:16] <ubot2> Launchpad bug 1235457 in nautilus (Ubuntu) "error open nautilus on terminal" [Undecided,New]
[20:23] <hggdh> jobin: in general, we should check if the issue is still present on a supported version
[20:24] <hggdh> jobin: and please do not worry, we are happy to have you helping :-)
[20:24] <jobin> but then the bug reported should be modified or a new bug filed with the updated release?
[20:24] <jobin> if the bug is present
[20:25] <hggdh> if the bug is still present, you just adjust the description to state it is still there on version <x.y>; it would be nice to check on bugzilla.gnome.org if it was reported there are well, and then (if so) link the upstream report to the LP bug
[20:26] <jobin> and thanks, it feels nice when people help out on IRC :)
[20:26] <jobin> and if the bug is not present?
[20:27] <hggdh> then... (just a sec, let me get the URL)
[20:27] <jobin> and which bugs are reported to bugzilla.gnome.org btw if they have already been reported on LP?
[20:28] <hggdh> jobin: you can use https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_EOL
[20:28] <hggdh> in fact, the page has a series of common cases
[20:29] <jobin> thanks a lot, have a lot to read before i proceed :-|
[20:29] <hggdh> don't worry, we all started without knowing what to do ;-)
[20:31] <brainwash> I wasn't aware of the standard responses page, well, it had to exist :D
[20:34] <hggdh> there is a wealth of information in the wiki about triaging. https://wiki.ubuntu.com/BugSquad/KnowledgeBase is also a good reference
[20:35] <jobin> love your humility hggdh :)
[20:40] <jobin> I confirmed that this bug: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1235457 still exists on version 14.04, so modified the bug report, can you please check if what I have done is correct or it needs further modification?
[20:40] <ubot2> Launchpad bug 1235457 in nautilus (Ubuntu) "nautilus exits when opened using sudo user and properties of a file/folder is opened" [Undecided,New]
[20:43] <hggdh> jobin: let me also check -- I am unsure if the messages you include are correct
[20:43] <brainwash> but isn't the usage of sudo for graphical apps considered wrong?
[20:46] <hggdh> brainwash: it is not adequate, but should not fail this way
[20:48] <hggdh> ah, I can repeat -- I also get a coredump
[20:48] <brainwash> and if launched with gksudo or pkexec?
[20:51] <hggdh> then it eventually fails as well. the difference is that gksudo will change the home to root's
[20:51] <hggdh> but navigating to a different user id (I went to my personal home dir) and select properties also crashes nautilus
[20:52] <hggdh> jobin: I get more messages when it fails
[20:52] <jobin> what is to be done in such cases?
[20:53] <hggdh> jobin: you can copy http://pastebin.com/6qXqQ5t4 as a comment to the bug -- these are the errors I see with sudo and gksudo
[20:55] <hggdh> I will stop for a while, my migraine returned...
[20:57] <jobin> the samba errors in your core-dump seems to be because samba is installed, so I am not sure whether to include them, should I?
[20:58] <brainwash> I cannot trigger this crash
[20:58] <brainwash> 14.04
[20:59] <jobin> nautilus version?
[20:59] <hggdh> I am not sure. I would have to follow the stacktrace, and I am not in any condition to do that now
[20:59] <hggdh> for the record, I am 14.04 up-to-date
[20:59] <jobin> same here
[21:00] <brainwash> me too
[21:02] <hggdh> interesting. really have to look at the stacktrace
[21:02] <brainwash> the crash does not trigger apport?
[21:08] <hggdh> it triggers woopsie, which sends the error to errors.ubuntu.com (access restricted)
[21:09] <hggdh> but I am not in condition to look at it now