=== txwikinger2 is now known as txwikinger === wylde_ is now known as wylde === wgrant_ is now known as wgrant [02:01] 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] multiarch* [02:05] it's ignoring the "/etc/dpkg/dpkg.d/multiarch", or it's looking somewhere else? anyone knows why? [02:12] !multiarch [07:25] anyone having problems with no images in liferea - xubuntu === Jikan is now known as Jikai === ninjak_ is now known as ninjak === Jikai is now known as Jikan === Jikan is now known as Jikai === Jikai is now known as Jikan === Jikan is now known as Jikai === Jikai is now known as Jikan === Jikan is now known as Jikai === Jikai is now known as Jikan === Jikan is now known as Jikai [12:59] 'morning all [13:44] good day === stkrzysiak_ is now known as stkrzysiak === stkrzysiak_ is now known as stkrzysiak [16:39] hi! I'm having problems http://paste.ubuntu.com/1086461/ [16:39] how to solve this? http://paste.ubuntu.com/1086461/ [16:42] more info http://paste.ubuntu.com/1086468/ [16:58] MechanisM: Did you try yet sudo apt-get -f install ...to make it continue on where possible? [16:58] yes [17:02] 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/ [17:03] yes I understand [17:09] 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/ (eg: there might be /etc/init/udev.conf which is the upstart [17:09] job but then maybe also /etc/init.d/udev which is the old sysvinit job ) [17:10] MechanisM: Then after stopping the upstart jobs and starting the old sysvinit jobs, to run sudo apt-get -f install once more [17:13]

thanks [17:20] MechanisM: Please let us know if this works :) === bkerensa_ is now known as bkerensa === stkrzysiak_ is now known as stkrzysiak === Logan__ is now known as Logan_ [19:31] update-manager in my vm with 12.10 is broken: http://pastebin.com/vG5jJew0. How can I fix it? [19:43] marco: bug 1023536 , not workaround yet but I'll take a look (seeing it here too) [19:43] Launchpad bug 1023536 in update-manager (Ubuntu) "update-manager crashed with ImportError in __main__: No module named UpdateManager.UpdateManager" [Undecided,Confirmed] https://launchpad.net/bugs/1023536 [19:48] 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] 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] trism: is "sudo apt-get update" enough to replace it temporarily? [19:51] 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] trism: Thanks! [19:55] trism: great news: "apt-get upgrade" updated update-manager. Problem fixed here [20:00] marco: I see, thanks for the heads up, seems this was quickly fixed in bug 1023474 [20:00] Launchpad bug 1023474 in update-manager (Ubuntu) "dh_python3 mangles shebangs to use Python" [Undecided,Fix released] https://launchpad.net/bugs/1023474 === IdleOne is now known as Guest87635 === Guest87635 is now known as IdleOne [23:06] So, update-manager core went and broke something. [23:07] * IdleOne is now on Windows 7 :( [23:20] IdleOne: Can't boot to single user? [23:21] 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] when I try to boot to failsafe it loops back to the login manager [23:23] 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] black screen after login that is [23:24] IdleOne: how about guest session ? [23:25] FernandoMiguel, I didn't try. [23:25] if it works, your session got corrupt [23:25] clean the session/plasma settings [23:25] should work [23:25] getting ready for dinner now. I'll have to try that after. How do I clean those settings? [23:26] I believe I saw an error about not being able to boot plasma-desktop but it went away too quick [23:26] maybe I clicked ok too quick. [23:28] there was someone earlier today who reported a similar error as I saw with his VM [23:28] in here* [23:28] IdleOne: not sure on KDE [23:28] on gnome usually compiz and unity stuff in .local [23:29] ok, I'll see if I can find it. [23:29] dinner time. ping me if you think/figure more out :)