[14:45] <LantzR> Hiya. Looking for feedback on my comment #3 to Bug #1119832.
[14:45] <ubot2> Launchpad bug 1119832 in nautilus (Ubuntu) "After creating a blank txt file in ~/Templates there are 2 "Empty Document" options in context menu" [Undecided,Confirmed] https://launchpad.net/bugs/1119832
[14:47]  * penguin42 looks
[14:51] <penguin42> LantzR: I suspect it's probably best to comment on the upstream bug
[14:52] <chilicuil> penguin42: it's actually fixed, see last comment in https://bugzilla.gnome.org/show_bug.cgi?id=687139
[14:52] <ubot2> Gnome bug 687139 in File and Folder Operations "Context menu entry to create a new blank file" [Enhancement,Resolved: notabug]
[14:54] <penguin42> chilicuil: Yeh but not bubbled down into ubuntu yet from my reading; the reporter is pointing to the fix as I read it
[14:54] <LantzR> penguin42: Thx I will look. The process was from TC-NFM-001 in http://packages.qa.ubuntu.com/qatracker/testcases/1424/info
[14:56] <penguin42> LantzR: Hmm so is that just a bad test case; in the sense if you create the document as Empty Text Document.txt  will the menu name be more sensible?
[14:58] <LantzR> No the test case is fine.     Template of aName.txt gives two menu entries. "aName" and "aName" one creates "aName.txt" the other creates "aName"
[14:59] <penguin42> oh I see, yeh that is weird
[15:00] <LantzR> My point re test case is I'm a virgin. Not sure if my comment was clear _and_ in the right spot for the qa testing results.
[15:01] <LantzR> The "Testing Tracker" is ... strange.
[15:02] <chilicuil> LantzR: I think it's ok, you've done an excellent work pointing out to the fix from a problem you found, I'd say it would be best for ubuntu to cherry pick the bug and provide some default file so people wont need to add them to its Template folder
[15:03] <LantzR> But your point ... I could have also gone upstream to post the a comment knowing that that is where the fix should come from.
[15:04] <penguin42> LantzR: Yeh I think that's a clear comment; I would have probably mentioned the test number you were following, but I don't do the test case stuff personally
 Ok thanks for the feedback.
[17:38] <GermainZ> Can someone please try syndaemon -d -i 2s -t? It should disable mouse taps (left/right clicks) and scrolling while typing, but it doesn't have any effect. The bugtracker (https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/366014) shows it as fixed, but I'd like to make sure I'm not doing something wrong before reopening.
[17:38] <ubot2> Ubuntu bug 366014 in xserver-xorg-input-synaptics (Ubuntu) "Syndaemon -t option not working" [Medium,Fix released]
[18:07] <GermainZ> Never mind, it actually works for taps on the pad, but not for hard buttons (which isn't an issue).
[19:33] <jarlath> Can someone guide me on how to trace the root-cause of this issue I'm having? :http://askubuntu.com/questions/243630/shut-down-takes-me-to-greeter-now-removing-wifi-dongle-fixes#comment307626_243630
[19:33] <jarlath> title may be misleading
[19:53] <penguin42> hmm fun
[19:53] <penguin42> jarlath: There seem to be a bunch of people in bug 838792 that discussion references; but there again you say it doesn't happen without networking, which seems different from them
[19:53] <ubot2> Launchpad bug 838792 in gnome-session (Ubuntu) ""Restart" logs out, even when there are no other people logged in" [High,Confirmed] https://launchpad.net/bugs/838792
[19:55] <jarlath> yes penguin42, I'm stumped :) The networking exception isn't consistent in further testing so I'm not sure about it.
[19:59] <penguin42> oh, hmm
[19:59] <penguin42> jarlath: when it returns you to the login manager does it let you log back in ?
[20:00] <jarlath> penguin42: yes, it does.
[20:00] <penguin42> if you tap the power button instead of selecting shutdown does it shutdown?
[20:01] <penguin42> (I mean just tap it rather than holding it down - and that depends on the machine, some actually would switch off, most tell the OS)
[20:01] <jarlath> penguin42: that's a good question :) I'll try now and report back. It'll at least log me off so I'll be disconnected for a few minutes. Resist any temptation to hide when I come back :)
[20:01] <penguin42> me? Hide?
[20:02] <jarlath> :D
[20:02] <jarlath> here we go...
[20:04]  * penguin42 looks hidden
[20:04] <jarlath> Anybody seen penguin42?
[20:05] <jarlath> ...Damn. He tricked me.
[20:05]  * penguin42 hides behind ubot2
[20:05]  * jarlath thought he saw something move...
[20:05] <penguin42> anyway, erm so what happened?
[20:05] <jarlath> Okay.
[20:05] <jarlath> That took me as far as the greeter I'm afraid. Although the dialog box for the power button looks different to the one from the menu.
[20:06] <penguin42> hmph
[20:06] <penguin42> does a sudo shutdown -h now   shut it down   from a terminal in the desktop?
[20:06] <jarlath> Yes. sudo halt -p or sudo reboot work from a terminal window or a tty.
[20:07] <penguin42> I can't honestly remember what the difference is relative to those
[20:09] <penguin42> jarlath: So with the networking stuff I would have guessed it was some form of driver that didn't want to shut down properly; but if shutdown -h now is working then it sounds like the kernel will do it, it's just something not getting that far
[20:10] <jarlath> Good observation, that makes sense to me.
[20:10] <penguin42> I wonder if /var/log/upstart should see some stuff when a shutdown happens
[20:13] <jarlath> Hmmm... I see a mediatomb.log file in there. I uninstalled it the same day I installed it, but the date on the log is from only a few days ago.
[20:13] <jarlath> the mediatomb application that is.
[20:14] <jarlath> Whatever it is, it doesn't require a user to be logged in. I can just boot up to the greeter and try to log out and the problem will happen (unless I'm *really* quick). So whatever it is, it must be loading around the time the greeter appears.
[20:15]  * penguin42 isn't sure of the path of things that go from pressing the shutdown until it actually gets to doing the same as shutdown command; it's I guess going to have to go through policykit to make sure you have the perms to do it
[20:15] <jarlath> policykit. Right.
[20:16] <jarlath> Is there a gui for that?
[20:16] <penguin42> well there's the GUI where you give stuff permissions, but I don't think much more than that
[20:16] <jarlath> God, if I asked that back in 2001 I'd have been banned from the room. How things have changed.
[20:16] <penguin42> haha yeh
[20:16] <jarlath> okay, thanks. At least I can look into policykit.
[20:17] <penguin42> ok
[20:17] <jarlath> Yeah, I really appreciate that. Hope you have a great weekend.
[20:17] <penguin42> I can't see anything in the advanced bit of user settings that would indicate you could remove it
[20:18] <njin> hallo, can someone look at bug 1118626 ?
[20:18] <ubot2> Launchpad bug 1118626 in Ubuntu "binutils: Split out libiberty-dev to multiarch paths" [Undecided,New] https://launchpad.net/bugs/1118626
[20:18] <jarlath> Hmmm
[20:19] <penguin42> jarlath: What version of ubuntu are you on?
[20:19] <jarlath> 12.04
[20:19] <penguin42> ok, let me just boot my 12.04 vm
[20:19] <jarlath> thanks
[20:21] <penguin42> jarlath: Hmm it has a lot less stuff in the GUI than the last time I looked at that...
[20:23] <jarlath> the policykit tool?
[20:23] <penguin42> jarlath: Well long ago there used to be an advanced bit of the user settings on system settings, but it's not there any more
[20:23] <jarlath> oh, okay.
[20:24] <jarlath> I'll bet it shuts down fine fine for you.
[20:24] <penguin42> nod
[20:25] <jarlath> hmm
[20:26] <penguin42> ah 12.04 has a lot less in /var/log/upstart
[20:27] <jarlath> Yeah, it's pretty eh... tidy
[20:30] <penguin42> hmm I wonder
[20:32] <penguin42> I'm going to pastebin the output of dbus-monitor --system > log    (run as root) it shows upstart being told you want to stop - again not quite sure how it gets to it
[20:32] <penguin42> hmm actually that's syslog being told to stop
[20:35] <penguin42> jarlath: http://paste.ubuntu.com/1630691/
[20:35] <jarlath> Thanks
[20:36] <jarlath> penguin42: so can I use the same command to diagnose my shutdown process or lack thereof?
[20:36] <penguin42> jarlath: well that was my guess of something to look at
[20:37] <penguin42> jarlath: You see how it's for the upstart jobs going through a series of pre-stop/stopping/stop for a load of things and then eventually Killed
[20:37] <penguin42> jarlath: It would be interesting to know if yours did the same
[20:38] <jarlath> I'll try now.
[20:38] <jarlath> Wish me luck.
[20:42] <jarlath> The system isn't very stable. I haven't actually stuck around long enough to try this before penguin42
[20:42] <penguin42> hmm, in what other ways is it unstable (I wish you said that before!)
[20:43] <jarlath> Windows won't close or resize (nautilus, firefox) and some page elements don't register events.
[20:43] <penguin42> huh, I'd fix that type of problem first
[20:44] <jarlath> Unity is fine. But when I hit the close button on the window decoration, said window seems to get stuck. I can't right-click on the desktop either when that happens.
[20:44] <jarlath> In System Settings, none of the icons respond to clicking.
[20:45] <penguin42> that sounds like you have much bigger problems then
[20:45] <jarlath> Yeah, I can't move the firefox window either. Only this text-box (thankfully!) is working. A re-install might be called for.
[20:46] <penguin42> yeh
[20:46] <penguin42> jarlath: There's a big difference between having one odd problem and a machine full of odd problems!
[20:47] <jarlath> Yeah, like I say. This has never happened during a first boot. I only noticed it now because I stuck around long enough after a failed shutdown.
[20:49] <jarlath> fsck would pick up on a bad disk sector right?
[20:49] <penguin42> no
[20:49] <jarlath> oh...
[20:49] <penguin42> jarlath: I'd use smartctl -a to check for a bad disk
[20:50] <penguin42> I think you can get some of them from the disk utility as well
[20:50] <jarlath> okay, I'll do that right now. Disk Utility requires the drive to be unmounted so I can't use it for /
[20:50] <penguin42> no
[20:51] <jarlath> Okay, the UI is totally unresponsive in Disk Utility too so I'll need to reboot.
[20:51] <penguin42> ok, use smartctl -a   to see if the disk is happy
[20:52] <jarlath> okay
[20:52] <jarlath> terminal works :)
[20:53] <jarlath> Wierd, I can use TAB and arrow keys to navigate the gui elements as normal. It's the mouse cursor that's the problem.
[20:55] <jarlath> penguin42: http://paste.ubuntu.com/1630752/
[20:55] <jarlath> I'm not sure what that all means, but it looks like there were issues.
[20:55] <jarlath> Oh, sorry for the full dump but no mouse....
[20:56] <jarlath> Line 51 is the start
[20:56] <penguin42> jarlath: My reading is that it's got hot at some point, and I'm not sure but I read that as it's still very hit
[20:57] <jarlath> Hmm, I did have the side of the case off for some time (months) so the cooling system couldn't have been working as well as it should.
[20:58] <penguin42> jarlath: There are some other errors in the logs - failed commands, there's a failed read (that's bad) but there are a load of other failed things like set capcaities - I've never seen things like those fail
[20:59] <jarlath> penguin42: thanks for that. Looks like a new harddrive - or at least a backup is in order.
[20:59] <penguin42> jarlath: Check your cabling as well; are there any errors in dmesg?
[21:01] <jarlath> Cabling seems secure, although the PSU I got has so much extra leads that it's like an overstuffed sock-drawer in there.
[21:01] <jarlath> Here's dmesg, there are errors: http://paste.ubuntu.com/1630774/
[21:03] <penguin42> no hard drive errors though
[21:03] <jarlath> Oh, no you're right.
[21:04] <jarlath> It seems the desktop issue I'm having now is purely the mouse arrow. I have full funcionality with keyboard shortcuts.
[21:05] <penguin42> heh ok
[21:05] <penguin42> jarlath: OK, then did you get the dbus-monitor output?
[21:06] <jarlath> And I've just un-stuck a mouse button and all is well 8/
[21:06] <jarlath> The dbus output didn't amount to much but here it is:
[21:07] <jarlath> http://paste.ubuntu.com/1630792/
[21:08] <penguin42> and that's the output of dbus-monitor --system  run as root  during a shutdown?
[21:09] <jarlath> run as my user, which was logged out during the process. Should I run as root from a tty? I don't think shutdown takes you past the greeter when someone else is logged in though.
[21:09] <penguin42> jarlath: No
[21:10] <penguin42> jarlath: Do a sudo -s  in a terminal inside your gui, then inside that do the dbus-monitor --system > logfile   and then try to shutdown
[21:10] <jarlath> So from the gnome-terminal on my desktop?
[21:10] <penguin42> yep
[21:10] <jarlath> ok
[21:12] <jarlath> penguin42: It looks identical
[21:13] <penguin42> pastebinit ?
[21:13] <jarlath> http://paste.ubuntu.com/1630814/
[21:13] <penguin42> huh ok
[21:14] <penguin42> well, I guess that means it ain't getting far at all
[21:14] <jarlath> No, just as far as the greeter. It doesn't seem to even attempt to shutdown properly.
[21:15] <penguin42> I've run out of ideas really
[21:15] <jarlath> penguin42: thank you so much. I can't believe you did all that.
[21:16] <penguin42> hey well I'm just sitting here avoiding solving a harder problem :-)
[21:17] <jarlath> Haha :)
[21:17] <jarlath> Do you work for Canonical?
[21:17] <penguin42> no
[21:18] <jarlath> If the problem is non-technical maybe I can help :)
[21:18] <jarlath> I'm a wedding singer lol (seriously!)
[21:18] <penguin42> haha no, it's rather technical
[21:18]  * penguin42 is a programmer in my day job as well
[21:19] <jarlath> okay. I did software eng. for my degree and graduated in 2003 but the band was doing well so I did that for ten years instead. So I'm mega rusty.
[21:21] <penguin42> hehe
[21:28] <jarlath> Goodnight penguin42. Hope your Sunday is better than your Saturday.
[21:28] <jarlath> And thanks again.
[21:29] <penguin42> hey it's been a good day