=== mythos_ is now known as mythos
[00:58] <TheLordOfTime> hggdh, got the latest message?
[00:58] <TheLordOfTime> on the mailing list
[00:58] <TheLordOfTime> bdmurray, same question ^
=== supercheetah is now known as Guest93700
=== emma is now known as em
=== brainwash_ is now known as brainwash
=== elopio_ is now known as elopio
[19:12] <hggdh> TheLordOfTime: from balloons? Yes, will answer as soon as possible. I think it is a good idea
[19:12] <TheLordOfTime> hggdh, yeah there's continued discussion on it, i put in my two cents, but i've lurked the QA team's area for a while now, since occasionally bug triage questions come out outside the scope of ISOtesting
[19:13] <TheLordOfTime> of course i put in my two-cents in #ubuntu-quality since GMail's not sending my emails today for some reason
[19:13] <TheLordOfTime> but meh
[20:44] <asd> hi i would like to assign a bug to a particular package but am not able to find which package the bug belongs too
[20:44] <asd> can someone please help
[20:44] <TheLordOfTime> asd, which bug
[20:45] <asd> TheLordOfTimes it is Bug #1242907
[20:45] <ubot2> Launchpad bug 1242907 in Ubuntu "The Shutdown button does not work" [Undecided,Confirmed] https://launchpad.net/bugs/1242907
[20:45] <asd> this bug also affects me
[20:47] <penguin42> fun - I'd file that against pm-utils or linux
[20:47] <penguin42> asd: So it stops working but doesn't actually turn the power off ?
[20:47] <TheLordOfTime> asd, ^
[20:48] <asd> for me the case is when i press the top right button and shutdown a window pops up with two huge buttons restart and shutdown
[20:48] <asd> clicking on wither does nothing
[20:49] <asd> and clicking on some where else in the screen dismisses the window
[20:49] <TheLordOfTime> asd, do me a favor and test this in the command line: `sudo shutdown -r now`  (tests restart)   or  `sudo shutdown -h now`  (tests full shutdown and halt)
[20:50] <TheLordOfTime> of course, assuming you aren't on your system right now :)
[20:50] <TheLordOfTime> but if you are just test
[20:50] <TheLordOfTime> (because if it's just those buttons not working that might be a more specific issue)
[20:50] <asd> TheLordOfTime: I have tested these two commands and they work from a user who is sudoers list
[20:51] <asimionov> asd: have you checked the logs? do you have something in the system log?
[20:52] <asd> asimionov: could you please direct me to where I can find the logs, sry but I am new to ubuntu
[20:53] <asimionov> do this: open a new console, type: tail -f /var/log/syslog
[20:53] <asimionov> asd: and type some ENTERs
[20:53] <asimionov> asd: then do you stuff and see what you get in the logs
[20:53] <asimionov> asd: *your
[20:55] <asd> asimionov: Oct 24 22:54:58 c490100005 gnome-session[1984]: WARNING: Unable to inhibit system: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted
[20:57] <asd> TheLordOfTime: it seems to be the buttons, i did what asimionov asked and in the logs i see ^
[20:57] <TheLordOfTime> wait, wasn't this a bug in 13.04?  And 12.10, too?
[20:57] <TheLordOfTime> i could've sworn i've seen this crop up in **every single release*
[20:59] <asd> I have not used 13.04 or 12.10, I was using 12.04 and i updated to 13.10 a few days back
[20:59] <TheLordOfTime> i was addressing everyone else, not just you
[20:59] <TheLordOfTime> i've seen questions about this issue since 12.10
[20:59] <TheLordOfTime> on Ask Ubuntu and stuff
[21:00] <asd> oh ok
[21:00] <penguin42> TheLordOfTime: So this is a permission/session permission thing where it's not allowing the shutdown?
[21:01] <TheLordOfTime> penguin42, dunno, i've only seen the people complaining on Ask Ubuntu about it, i haven't seen any bug resolutions for it
[21:01] <TheLordOfTime> i mean, i could go digging, but... meh
[21:01] <TheLordOfTime> penguin42, i'm also not a dev, and I personally have never had the bug
[21:01] <penguin42> TheLordOfTime: Yeh I'm sure I hit it a few releases ago but can't remember how it resolved
[21:01] <TheLordOfTime> (it works fine in my systems xD)
[21:02] <penguin42> asd: The problem you are hitting sounds different to the bug you linked to - that bug sounds like it starts shutting down just never actually manages to turn the power off
[21:02] <TheLordOfTime> ... be right back, I need to wage war against sbuild right now... (it's FTBFSing only on my system)
[21:02] <penguin42> asd: But there again it's not too clear from the wording of that bug if it is that he's seeing
[21:03] <asd> penguin42: okay i searched for my issue and found this bug, should i create a new one instead, thanks
[21:03] <penguin42> asd: Yes, create a new one - if the shutdown -h now works then I suggest  filing the bug against either unity or pm-utils
[21:03] <penguin42> asd: (unity assuming you're running unity that is)
[21:04] <asd> penguin42: how do i find if i am running unity, thanks
[21:04] <penguin42> asd: Is it the 'normal' Ubuntu gui - with the ubuntu symbol at the top left that when you click it pops up a search box and buttons down the left side?
[21:05] <brainwash> could be gnome-session, systemd/logind or policykit
[21:05] <penguin42> brainwash: Indeed, but very non-trivial to track down
[21:06] <penguin42> certainly I wouldn't know where to go from that point - feel free to suggest
[21:06] <asd> penguin42: yes that is what I have.
[21:07] <penguin42> asd: OK, Unless brainwash has some better ideas of package to pick then I'd file against   pm-utils  and see what happens
[21:07] <penguin42> asd: AS long as you pick something reasonable then the guys who own it might be able to point in a better direction
[21:07] <asd> penguin42: ok thanks I will do so
[21:07] <brainwash> pm-utils is kinda wrong
[21:07] <TheLordOfTime> ... and I'm back, apparently sbuild didn't take into account the PPA i told its schroots to add into it for the nginx builds...
[21:08] <penguin42> brainwash: Ok, make a better suggestion
[21:08]  * penguin42 has to disappear for a while
[21:08] <asd> brainwash: shall i choose unity then, thank you
[21:09] <brainwash> well, gnome-session is throwing the waring
[21:09] <brainwash> warning
[21:10] <asd> well the thing is that is same warning being thrown every few seconds
[21:10] <asd> i just realized this
[21:11] <brainwash> what does "dbus-send --print-reply --system --dest=org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanPowerOff" return?
[21:12] <brainwash> yes, no or challenge
[21:12] <asd> brainwash: dbus-send --print-reply --system --dest=org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanPowerOff
[21:12] <asd> returns method return sender=:1.3 -> dest=:1.77 reply_serial=2    string "challenge"
[21:13] <brainwash> that means that there is are other active user session running at the moment, right?
[21:13] <asd> yes i ran the command from a sudoer user
[21:13] <asd> from my user i see this method return sender=:1.3 -> dest=:1.78 reply_serial=2    string "challenge"
[21:14] <brainwash> mmh, how many sessions does "loginctl list-sessions" list?
[21:15] <asd> it says o sessions listed
[21:15] <asd> *0
[21:16] <brainwash> that is odd
[21:17] <asd> brainwash: the sudoer user I have logged in only from the terminal using su
[21:17] <asd> my user is the one currenty logged in physically
[21:17] <asd> dont know if that makes a difference
[21:18] <asd> again i am pretty new to ubuntu and linux in general so sry if it sounds silly :)
[21:18] <brainwash> using su?
[21:19] <brainwash> why that?
[21:19] <asd> yes from the terminal i say su <sudoerUserName>
[21:19] <TheLordOfTime> why would your user that you're logged in as not already be in sudoers?
[21:20] <asd> TheLordOfTime: that is the configuration from my office
[21:20] <asd> my user is not in the sudoers list
[21:21] <asd> i just know a user in the sudoers list that i am currently using to issue the shutdown command when i want to shutdown
[21:23] <brainwash> so did you run the mentioned commands as normal user (your user account)?
[21:25] <asd> yes the first one from my user account gives method return sender=:1.3 -> dest=:1.81 reply_serial=2    string "challenge"
[21:25] <asd> and the loginctl list gives 0 sessions also run from my user
[21:31] <brainwash> right, and that's a bit odd
[21:31] <brainwash> it should at least list your current session
[21:35] <brainwash> what does "cat /etc/pam.d/common-session | grep systemd" return?
[21:36] <asd> brainwash: it returns nothing
[21:36] <brainwash> oh
[21:36] <brainwash> mmmmmh
[21:36] <brainwash> it should return something
[21:38] <brainwash> I'm looking for an existing bug report
[21:38] <asd> it would maybe help to add that my user is linked to a kerberos account
[21:46] <brainwash> asd: so, the entry for systemd is missing in your pam conf file
[21:46] <asd> brainwash: yes it looks like that is the case
[21:47] <brainwash> it's "session optional        pam_systemd.so"
[21:48] <brainwash> there is pam-auth-update to manage the modules, well, but I'm not that familiar with pam
[21:48] <asd> brainwash: i have session optional with couple of other stuff
[21:49] <brainwash> add it below the the pam_unix.so line
[21:50] <asd> pam_unmask.so, pam_krb5.so minimum_uid=1000, pam_ldap.so and pam_ck_connector.so nox11 these are what i have
[21:51] <brainwash> so add "session optional        pam_systemd.so"
[21:52] <brainwash> the block on the bottom is called "Additional" block
[21:52] <brainwash> and the line belongs there
[21:53] <brainwash> It's the only hint we got so far, maybe it does solve your issue
[21:54] <brainwash> if no, you should file a bug report against gnome-session I guess and attach all the information we gathered
[21:55] <asd> ok will add and see what happens
[21:55] <asd> thank you for yout time
[21:55] <asd> *your
[21:57] <brainwash> hopefully the mystery gets solved now or soon :)
[22:00] <asd> brainwash: i have added the line i guess i will have to restart for the changes to take effect
[22:01] <brainwash> right, maybe a relog would be enough
[22:01] <brainwash> but a restart won't hurt
[22:03] <asd> ok doing a restart now
[22:13] <asd> brainwash: it worked
[22:13] <brainwash> great
[22:14] <asd> thank you, the results of the command now are, method return sender=:1.3 -> dest=:1.77 reply_serial=2    string "yes"
[22:15] <asd>    SESSION        UID USER             SEAT                     c2      20006 abduljabbar.gulam seat0             1 sessions listed.
[22:15] <brainwash> you should file a report, but against system and pam
[22:15] <asd> and i can do a restart and shutdown
[22:16] <asd> where can i do this report, thank you
[22:16] <brainwash> on launchpad
[22:17] <brainwash> to inform the devs about this issue, it might affect more people
[22:17] <brainwash> people who upgraded to 13.10
[22:18] <brainwash> https://bugs.launchpad.net/ubuntu/+source/systemd/+filebug
[22:18] <brainwash> afterwards you can also add pam to the list of affected packages
[22:21] <TheLordOfTime> brainwash, might be better for him to do `ubuntu-bug systemd` in the command line
[22:21] <TheLordOfTime> then apport grabs things about it
[22:21] <brainwash> right
[22:22] <brainwash> asd: use `ubuntu-bug systemd` in the command line
[22:23] <TheLordOfTime> without the ` characters
[22:23] <asd> TheLordOfTime and brainwash from command line i get a message saysing Package systemd does not exist
[22:23] <asd> a window pops up displaing this message
[22:23] <asd> displaying
[22:24] <TheLordOfTime> bleh
[22:24] <TheLordOfTime> hmm
[22:24] <TheLordOfTime> brainwash, systemd != in saucy
[22:26] <asd> from the link brainwash sent i find "libpam-systemd" shall i choose this
[22:26] <brainwash> yes
[22:27] <brainwash> systemd is the meta build package name I assume
[22:29] <asd> ok i did ubuntu-bug libpam-systemd
[22:30] <penguin42> brainwash: Nice bit of debug
[22:32] <asd> yes brainwash, thank you
[22:32] <brainwash> penguin42: thanks, sadly 13.10 isn't fully compatible with systemd/logind yet
[22:32] <brainwash> asd: you're welcome :)
[22:33] <brainwash> penguin42: and on top o that, not well tested regarding systemd/logind
[22:34] <penguin42> brainwash: But that is the default install isn't it?
[22:35] <brainwash> yes, logind is now the default, it replaced consolekit (deprecated)
[22:36] <brainwash> currently I'm trying to debug and understand bug 1184262
[22:36] <ubot2> Launchpad bug 1184262 in network-manager (Ubuntu) "[logind] stuck in PrepareForSleep, causing network and other services to not resume" [High,Confirmed] https://launchpad.net/bugs/1184262
[22:36] <penguin42> brainwash: OK, interesting - I hadn't noticed consolekit went away
[22:36] <TheLordOfTime> asd, what's the bug number on your bug that you filed (it should give you a link after its filed)
[22:37] <asd> TheLordOfTime it is Bug #1244463
[22:37] <ubot2> Launchpad bug 1244463 in systemd (Ubuntu) "session optional pam_systemd.so missing from /etc/pam.d common-session file" [Undecided,New] https://launchpad.net/bugs/1244463
[22:38] <penguin42> asd: Did you go straight from 12.04 to 13.10 ?
[22:39] <asd> penguin42: no i ran update-manager -d and it updated to 12.10, 13.04 and finally to 13.10
[22:39] <brainwash> o.o
[22:39] <asd> i did this however one after the other immediately without changing anything in betweem
[22:39] <asd> between
[22:39] <brainwash> clean install would have saved you some time
[22:41] <asd> well i did not want to lose my kerberos settings
[22:41] <asd> but it looks like a clean install would have been better :)
[22:42] <penguin42> asd: Hmm ok, that's interesting - could you add the detail about how you upgraded to your report please
[22:44] <asd> penguin42 yes sure
[22:50] <penguin42> brainwash: Really something somewhere should have done a lot of that session debug automagically rather than the thing just sulking
[22:51]  * penguin42 gulps at the loginctl kill-user  parameter
[22:53] <brainwash> I really dislike ubuntu's systemd abomination :/
[22:53] <penguin42> what have they done - picked just one part of it?
[22:54] <brainwash> the parts which are needed like logind, udev,..
[22:54] <brainwash> and we ship systemd-shim, a simple wrapper for dbus calls
[22:55] <penguin42> brainwash: In which direction do you dislike it, for going too far or not far enough?
[22:55] <brainwash> and the usual ubuntu custom patches :D
[22:55] <brainwash> going further would mean to replace upstart with systemd
[22:56] <penguin42> well you said you disliked it - but I wondered what your preferred route was
[22:57] <brainwash> the current one is the "right" one
[22:58] <brainwash> we had to replace consolekit
[23:49] <penguin42> brainwash: is this the same as bug 1243837 ?
[23:49] <ubot2> Launchpad bug 1243837 in xfce4 (Ubuntu) "Restart in the main menu does a logout instead" [Undecided,Confirmed] https://launchpad.net/bugs/1243837
[23:50] <TheLordOfTime> penguin42, i think this is a different bug, looks like the user here is hitting shutdown or restart but then nothing happens, at least by their description...
[23:51] <brainwash> it is related to bug 1184262
[23:51] <ubot2> Launchpad bug 1184262 in network-manager (Ubuntu) "[logind] stuck in PrepareForSleep, causing network and other services to not resume" [High,Confirmed] https://launchpad.net/bugs/1184262
[23:53] <penguin42> ok
[23:54] <brainwash> ^ this report is driving me mad anyway, people keep bumping it with "useless" comments or simply confirm the workaround over and over again
[23:54] <brainwash> still no real debugging information