/srv/irclogs.ubuntu.com/2012/07/11/#ubuntu+1.txt

=== txwikinger2 is now known as txwikinger
=== wylde_ is now known as wylde
=== wgrant_ is now known as wgrant
utu-sanLooks like dpkg is broken?  mukltiarch support for i386 is disabled but it keeps querrying i386 packages.  Is there any other config file?02:01
utu-sanmultiarch*02:02
utu-sanit's ignoring the "/etc/dpkg/dpkg.d/multiarch", or it's looking somewhere else? anyone knows why?02:05
utu-san!multiarch02:12
hobgoblinanyone having problems with no images in liferea - xubuntu07:25
=== 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
BluesKaj'morning all12:59
jokerdinogood day13:44
=== stkrzysiak_ is now known as stkrzysiak
=== stkrzysiak_ is now known as stkrzysiak
MechanisMhi! I'm having problems http://paste.ubuntu.com/1086461/16:39
MechanisMhow to solve this? http://paste.ubuntu.com/1086461/16:39
MechanisMmore info http://paste.ubuntu.com/1086468/16:42
genii-aroundMechanisM: Did you try yet sudo apt-get -f install    ...to make it continue on where possible?16:58
MechanisMyes16:58
genii-aroundMechanisM: 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:02
MechanisMyes I understand17:03
genii-aroundThe 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 upstart17:09
genii-around job but then maybe also /etc/init.d/udev  which is the old sysvinit job )17:09
genii-aroundMechanisM: Then after stopping the upstart jobs and starting the old sysvinit jobs, to run sudo apt-get -f install   once more17:10
MechanisM<genii-around> thanks17:13
genii-aroundMechanisM: Please let us know if this works :)17:20
=== bkerensa_ is now known as bkerensa
=== stkrzysiak_ is now known as stkrzysiak
=== Logan__ is now known as Logan_
marcoupdate-manager in my vm with 12.10 is broken: http://pastebin.com/vG5jJew0. How can I fix it?19:31
trismmarco: bug 1023536 , not workaround yet but I'll take a look (seeing it here too)19:43
ubottuLaunchpad bug 1023536 in update-manager (Ubuntu) "update-manager crashed with ImportError in __main__: No module named UpdateManager.UpdateManager" [Undecided,Confirmed] https://launchpad.net/bugs/102353619:43
trismmarco: I see the issue, UpdateManager python code is in the python3 path, but /usr/bin/update-manager is still using #! /usr/bin/python19:48
trismmarco: 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 fixed19:48
marcotrism: is "sudo apt-get update" enough to replace it temporarily?19:49
trismmarco: 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 packages19:51
marcotrism: Thanks!19:51
marcotrism: great news: "apt-get upgrade" updated update-manager. Problem fixed here19:55
trismmarco: I see, thanks for the heads up, seems this was quickly fixed in bug 102347420:00
ubottuLaunchpad bug 1023474 in update-manager (Ubuntu) "dh_python3 mangles shebangs to use Python" [Undecided,Fix released] https://launchpad.net/bugs/102347420:00
=== IdleOne is now known as Guest87635
=== Guest87635 is now known as IdleOne
IdleOneSo, update-manager core went and broke something.23:06
* IdleOne is now on Windows 7 :(23:07
genii-aroundIdleOne: Can't boot to single user?23:20
IdleOnenope, 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:21
IdleOnewhen I try to boot to failsafe it loops back to the login manager23:22
IdleOnethere 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:23
IdleOneblack screen after login that is23:24
FernandoMiguelIdleOne: how about guest session ?23:24
IdleOneFernandoMiguel, I didn't try.23:25
FernandoMiguelif it works, your session got corrupt23:25
FernandoMiguelclean the session/plasma settings23:25
FernandoMiguelshould work23:25
IdleOnegetting ready for dinner now. I'll have to try that after. How do I clean those settings?23:25
IdleOneI believe I saw an error  about not being able to boot plasma-desktop but it went away too quick23:26
IdleOnemaybe I clicked ok too quick.23:26
IdleOnethere was someone earlier today who reported a similar error as I saw with his VM23:28
IdleOnein here*23:28
FernandoMiguelIdleOne: not sure on KDE23:28
FernandoMiguelon gnome usually compiz and unity stuff in .local23:28
IdleOneok, I'll see if I can find it.23:29
IdleOnedinner time. ping me if you think/figure more out :)23:29

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!