[08:13] <JonathanD> Morning.
[09:09] <rmg51> Morning
[12:05] <teddy-dbear> Morning peoples, dogs, turkeys and everything else
[12:11] <InHisName> good morning to you all
[13:08] <ChinnoDog> morning
[16:20] <Samuraialba> Good bacon to all!
[17:11] <InHisName> Hey Guys, I have software update running and it says:  "Installing Updates"  "Running post-installation trigger dpkg-exec"   Details --> 95% completed and has been stuck there for hours/days now.   What to do about this ?
[17:48] <Samuraialba> Not sure, man
[17:48] <Samuraialba> I have no clue
[17:48] <Samuraialba> This is unfortunately, a Windows Shop :(
[17:48] <Samuraialba> I'm running Ubuntu in aVM and I'll see if I can replicate
[17:49] <InHisName> I doubt it.   Something's gone wrong.  Just want to know what to do the make recovery least difficult.
[17:56] <ChinnoDog> InHisName: Can you expand the dialog to see a command prompt waiting for input?
[17:56] <ChinnoDog> I see those sometimes when I update a package that is complaining about a customization I did.
[17:56] <InHisName> The "Details" shows only a progress bar.  No command line to type input.
[17:57] <InHisName> Title is "Software Updater"
[17:57] <ChinnoDog> I would kill the process tree and then run apt to fix the database
[17:57] <ChinnoDog> and then you can try the update again
[17:57] <InHisName> Can it do a nice recovery from  a FIRM power down and then a restart ?
[17:58] <ChinnoDog> It isn't Windows. Fix your file system before you shut down. :-)
[17:58] <InHisName> True, its Ubuntu
[17:59] <InHisName> What to fix ?
[17:59] <ChinnoDog> The package database. The next time you run apt after killing the update it will tell you to run a command to repair the database
[17:59] <ChinnoDog> Then it will check your packages, run the triggers that were not run before, and help you add/remove packages so it isn't borked anymore.
[18:00] <InHisName> I would do this right after rebooting ?
[18:00] <ChinnoDog> You don't need to reboot
[18:00] <ChinnoDog> Do it now, without rebooting
[18:00] <InHisName> What commands to run ?
[18:01] <ChinnoDog> use killall to take down the process tree
[18:01] <InHisName> Do now ? with this panel still open?   There is NO "X" button and "cancel" is grey.
[18:01] <ChinnoDog> Then run apt. I don't know if you need a command to get it to tell you to fix stuff.
[18:01] <ChinnoDog> Do it from a command line
[18:02] <ChinnoDog> I need to eat lunch. bbiab
[18:03] <InHisName> Could not get a lock, Is another process using it ?
[18:04] <InHisName> Seems that this stuck panel is blocking usage of apt-get system.
[19:06] <ChinnoDog> so kill it
[19:25] <ChinnoDog> InHisName: did you fix it?
[21:43] <ChinnoDog> One of these days I need to learn to use busybox to recover after screwing up my fstab
[22:26] <waltman> Alternatively, you could stop screwing up your fstab. :)
[22:32] <ChinnoDog> That too. I should use mount options that actually exist.
[22:32] <jthan_> Seems to me that you just got burned, ChinnoDog
[22:33] <ChinnoDog> jthan--
[22:33] <jthan> PennBot is a lie.