/srv/irclogs.ubuntu.com/2015/02/04/#ubuntu+1.txt

=== zerick_ is now known as zerick
lordievaderGood morning.06:15
lotuspsychjelordievader: morning mate06:15
kernelpanic_Hello! I just downloaded vivid-desktop-amd64.iso and want to install it without installing a bootloader. So I'd like to start "ubiquity --no-bootloader". My problem is that in plain install mode, ubiquity is started without "--no-bootloader" and with mir and unity8 running in live mode, I don't know how to start ubiquity at all.10:52
kernelpanic_I tried live mode, then ALT+F1 and start "ubiquity --no-bootloader" from text mode, but it just returns and nothing happens at all10:53
=== snadg3 is now known as snadge
kernelpanic_can someone please tell me how to start a simple terminal in the current daily build?11:42
=== kbroulik_ is now known as kbroulik-lunch
lordievaderkernelpanic_: In Ubuntu? ctrl + alt + k? Else open a tty point it to :0 and start a terminal emulator from there.12:38
lordievaderOr use that terminal ofcourse.12:38
BluesKajHiyas all13:00
=== kbroulik-lunch is now known as kbroulik
=== rymate12- is now known as rymate1234
=== Malsasa_ is now known as Malsasa
=== Malsasa_ is now known as Malsasa
=== SuperLag_ is now known as SuperLag
sternshello, just updated my vivid install and now, I'm presented with an X login screen, which looks good, after logging in I just get a blank screen.  I'm on the Ubuntu Gnome distro.  I found this error in the syslog:17:17
sternshttp://pastebin.com/8EnkxJBd17:18
sternsI am testing to see if the latest systemd update is causing my system not to function properly.  I would like to rollback to 218-6ubuntu1, but it's not in my apt-cache19:07
sternsany recommendations?19:07
trismsterns: https://launchpad.net/ubuntu/+source/systemd/218-6ubuntu1 if you click your arch under Builds it will take you to a page with all the debs19:09
trismsterns: although they might be in /var/cache/apt/archives already19:09
sternstrism: apt-cache showpakg systemd would show me that if they were there correct?19:10
sterns*showpkg19:10
trismsterns: no, they will not show up because they are not in the package lists anymore19:10
sternsah, ok19:11
trismsterns: you would have to look in the directory and install manually with dpkg -i19:11
sternsnow, when I did do showpkg earlier, it showed a bunch of reverse dependencies.  Am I going to create a trainwreck?19:11
trismsterns: and you would need to get all of them at once or it might cause some issues (and it might anyway)19:12
trismsterns: you might, or it might be fine, I would: ls /var/cache/apt/archives/*218-6ubuntu1*.deb; to see which ones you would need to get at once19:13
sternstrism: did you see my earlier posts about the nature of my problem?  I am shooting in the dark with this systemd idea.19:13
trismsterns: no I did not19:14
sternsi did a apt-get dist-upgrade earlier this morning.  After I login to X (username/pass), I get a blank screen.19:15
sternsI see this in my syslog: http://pastebin.com/8EnkxJBd19:15
sternsthis is the apt history.log: http://pastebin.com/fy3SfCrt19:16
sternsalso, when I login to tty1, I see "failed to start user service.  Unknown init user@1000.service19:17
sternsbut tty session works fine19:17
trismsterns: I see bug 1416943 for gnome-shell which is very recent19:18
ubottubug 1416943 in gnome-shell (Ubuntu) "/usr/bin/gnome-shell:5:_cogl_set_error:allocate_from_gl_foreign:_cogl_texture_2d_gl_allocate:cogl_texture_allocate:cogl_texture_2d_new_from_data" [High,Confirmed] https://launchpad.net/bugs/141694319:18
sternsI tried utilizing two prior kernels using grub with no benefit19:18
trismsterns: it links to an errors log that I can't view though so hard to tell19:18
trismsterns: it looks more like a bug with the latest gnome-shell uploads instead of a systemd issue19:19
sternsgnome-shell has it's own package right?19:20
sternsI didn't see that package being updated in the history19:21
trismsterns: the gnome-shell package was from a while ago, but some of the libs used by gnome-shell might have been updated19:21
sternstrism: do you know how I could go about confirming that this bug is the one I'm encountering?19:27
trismsterns: looking at the dups I'm not so sure it is anymore, they all manage to log in but crash later on19:28
sternstrism: this is also the Ubuntu-Gnome distro19:30
trismsterns: did you get a crash file in /var/crash for gnome-shell?19:30
sternsVivid19:30
sternsI'll check19:30
sternsyes, it's there, it's 50MB _usr_bin_gnome-shell.1000.crash19:32
trismsterns: you could try going into another session if you can and: ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash; and see if it dups on anything19:33
sternsk, sec19:33
sternswell, I'm accessing the log from a working system and ubuntu-bug reports that it's unreportable because it pertains to a program that is not installed.19:37
sternsI assume that means it's not installed on my working system, which is true.19:38
sternsshould I try it again after booting the Vivid OS?19:39
sternsI'm checking out: https://wiki.ubuntu.com/DebuggingProgramCrash19:42
elfytry apport-cli -c /var/crash/_usr_bin_gnome-shell.1000.crash19:45
elfyoh - really should tab people's nicks lol19:46
sternstrism: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/141820920:37
ubottuLaunchpad bug 1418209 in gnome-shell (Ubuntu) "gnome-shell crashed with SIGKILL" [Undecided,New]20:37
trismsterns: strange, have to wait for the retracing to learn much from it20:39
sternsI am prepared to do the retrace myself, I was just looking at that20:40
sternswould that be valuable, or just wait for the automated system?20:41
trismsterns: it may help match it to another bug if you don't want to wait, it's really up to you20:49

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