[02:01] <utu-san> Looks like dpkg is broken?  mukltiarch support for i386 is disabled but it keeps querrying i386 packages.  Is there any other config file?
[02:02] <utu-san> multiarch*
[02:05] <utu-san> it's ignoring the "/etc/dpkg/dpkg.d/multiarch", or it's looking somewhere else? anyone knows why?
[02:12] <utu-san> !multiarch
[07:25] <hobgoblin> anyone having problems with no images in liferea - xubuntu
[12:59] <BluesKaj> 'morning all
[13:44] <jokerdino> good day
[16:39] <MechanisM> hi! I'm having problems http://paste.ubuntu.com/1086461/
[16:39] <MechanisM> how to solve this? http://paste.ubuntu.com/1086461/
[16:42] <MechanisM> more info http://paste.ubuntu.com/1086468/
[16:58] <genii-around> MechanisM: Did you try yet sudo apt-get -f install    ...to make it continue on where possible?
[16:58] <MechanisM> yes
[17:02] <genii-around> MechanisM: You can try manual install of those specific ones from the cache ( need to know their packagenames there though ) like  sudo dpkg -i /var/cache/apt/archives/<munin-node-deb-name-here>
[17:03] <MechanisM> yes I understand
[17:09] <genii-around> The issue seems to be coming from the post-install directive which restarts the things. I know udev has an upstart job yet it looks like the install is trying to do it the old way. I would suggest stop the upstart jobs( with sudo stop jobname ) and see if there is sysvinit script for same jobs in /etc/init.d  and then manually start those instead with sudo /etc/init.d/<jobname here>  (eg: there might be  /etc/init/udev.conf which is the upstart
[17:09] <genii-around>  job but then maybe also /etc/init.d/udev  which is the old sysvinit job )
[17:10] <genii-around> MechanisM: Then after stopping the upstart jobs and starting the old sysvinit jobs, to run sudo apt-get -f install   once more
 thanks
[17:20] <genii-around> MechanisM: Please let us know if this works :)
[19:31] <marco> update-manager in my vm with 12.10 is broken: http://pastebin.com/vG5jJew0. How can I fix it?
[19:43] <trism> marco: bug 1023536 , not workaround yet but I'll take a look (seeing it here too)
[19:48] <trism> marco: I see the issue, UpdateManager python code is in the python3 path, but /usr/bin/update-manager is still using #! /usr/bin/python
[19:48] <trism> marco: it runs changing it to /usr/bin/python3 but that may break other things, probably best to stick to apt-get on the command line until this is fixed
[19:49] <marco> trism: is "sudo apt-get update" enough to replace it temporarily?
[19:51] <trism> marco: sudo apt-get update; sudo apt-get upgrade; and sudo apt-get dist-upgrade; being careful with the last command to make sure it doesn't try to remove a bunch of packages
[19:51] <marco> trism: Thanks!
[19:55] <marco> trism: great news: "apt-get upgrade" updated update-manager. Problem fixed here
[20:00] <trism> marco: I see, thanks for the heads up, seems this was quickly fixed in bug 1023474
[23:06] <IdleOne> So, update-manager core went and broke something.
[23:07]  * IdleOne is now on Windows 7 :(
[23:20] <genii-around> IdleOne: Can't boot to single user?
[23:21] <IdleOne> nope, I'm unable to boot to my plasma desktop, goes to default. I get the login manager but then boots to a black screen.
[23:22] <IdleOne> when I try to boot to failsafe it loops back to the login manager
[23:23] <IdleOne> there was something about Line 8 in /update-manager-core/check-release-upgrade/ <--- not sure about the file name there. When I tried commenting out that line and rebooted the error went away but still a black screen on boot.
[23:24] <IdleOne> black screen after login that is
[23:24] <FernandoMiguel> IdleOne: how about guest session ?
[23:25] <IdleOne> FernandoMiguel, I didn't try.
[23:25] <FernandoMiguel> if it works, your session got corrupt
[23:25] <FernandoMiguel> clean the session/plasma settings
[23:25] <FernandoMiguel> should work
[23:25] <IdleOne> getting ready for dinner now. I'll have to try that after. How do I clean those settings?
[23:26] <IdleOne> I believe I saw an error  about not being able to boot plasma-desktop but it went away too quick
[23:26] <IdleOne> maybe I clicked ok too quick.
[23:28] <IdleOne> there was someone earlier today who reported a similar error as I saw with his VM
[23:28] <IdleOne> in here*
[23:28] <FernandoMiguel> IdleOne: not sure on KDE
[23:28] <FernandoMiguel> on gnome usually compiz and unity stuff in .local
[23:29] <IdleOne> ok, I'll see if I can find it.
[23:29] <IdleOne> dinner time. ping me if you think/figure more out :)