[01:29] <darkxst> hey octoquad
[02:42] <ratchek> Hello!
[02:43] <ratchek> OK, this is my first time using IRC, so if i do anything wrong please correct me
[02:43] <ratchek> if i'm having problems with gnome-ubuntu where should i go?
[03:56] <darkxst> ratchek, what problems are you having?
[04:15] <ratchek> oh, didn't notice you're here
[04:15] <ratchek> hi
[04:17] <ratchek> so i've loaded ubuntu gnome on my new laptop (http://www.amazon.com/Dell-i3147-3750sLV-11-6-Inch-Convertible-Touchscreen/dp/B00KMRGF3M)
[04:17] <ratchek> and it keeps freezing during the booting sequence
[04:17] <ratchek> i tried reinstalling it
[04:17] <ratchek> then i tried reinstalling it in legacy boot mode
[04:18] <ratchek> and it keeps frezing
[04:18] <ratchek> when i entered ubuntu recovery mode
[04:19] <ratchek> it freezes at :
[04:19] <ratchek> [ 5.479187] system-devd[266] : starting version 204
[04:48] <ratchek> unfortunately, i have to leave. I won't be turning off the client, so if somebody could write what hours would be best to get help, i would come back then. Thanks in advance.
[06:07] <semicolon> Good morning
[06:11] <darkxst> ratchek, you are trying to install 14.04? might be best to try 14.10 since its a new laptop
[06:11] <darkxst> semicolon, morning
[06:12] <ratchek> 14.10 is the first one i tried
[06:13] <octoquad> morning semicolon
[06:14] <darkxst> ratchek, 14.10 has systemd 208 I think?
[06:14] <darkxst> ratchek, what gpu do you have?
[06:14] <ratchek> darkxst, sorry, but what is system 208?
[06:15] <darkxst> <ratchek> [ 5.479187] system-devd[266] : starting version 204
[06:15] <ratchek> darkxst, oh, yes I see what you're saying
[06:16] <ratchek> but after i tried and failed with 14.10 u started trying with 14.04
[06:16] <darkxst> ratchek, what gpu do you have?
[06:16] <ratchek> because i figured, sice it's lts, it should have better support
[06:16] <ratchek> ok, I'm kind of a newbie
[06:17] <darkxst> graphics card?
[06:17] <ratchek> so according to amazon, this particular laptop has Intel HD graphics
[06:17] <ratchek> that's all it says
[06:17] <ratchek> how can i find out?
[06:18] <darkxst> ratchek, look on dell site?
[06:18] <ratchek> ok, give me a sec
[06:20] <ratchek> all it says is Intel® HD Graphics
[06:21] <ratchek> this is a 400$ laptop
[06:21] <ratchek> is it possible for it to not have a dedicated gpu?
[06:21] <darkxst> intel gpu are integrated in the cpu
[06:22] <darkxst> ratchek, maybe try booting a daily image and see if that works (for live session) that has a newer kernel
[06:22] <ratchek> yeah so unfortunately, that is all i got out of the dell site
[06:22] <darkxst> http://cdimage.ubuntu.com/ubuntu-gnome/daily-live/
[06:24] <ratchek> darkxst, could you please explain what a daily-live image is?
[06:25] <ratchek> darkxst, ok, for some reason i was able to boot it off the live cd that i used for the originall install
[06:26] <ratchek> is there any diagnostic i could run in the terminal that would tell me what's wrong?
[06:27] <mgedmin> lspci -s 00:02.0 -nnn will tell you what kind of graphics it has
[06:29] <ratchek> darkxst, great, so i ran the command and got the following
[06:29] <ratchek> Intel Corporation ValleyView Gen7
[06:29] <ratchek> [8086:0f31]
[06:30] <darkxst> ratchek, hmm, so its actually quite old
[06:30] <ratchek> darkxst, is that a good thing or a bad thing?
[06:30] <darkxst> would be best to paste some logs, probably /var/log/gdm/\:0*.log
[06:31] <darkxst> ratchek, well it should definately work with 14.10 and probably 14.04
[06:35] <ratchek> darkxst, will the logs help even though i'm  using a live session to access the terminal?
[06:35] <darkxst> ratchek, no, probably not
[06:35] <ratchek> darkxst, isn't it wierd that the live session goes through and the normal install doesn't?
[06:35] <ratchek> darkxst, or does that happen
[06:38] <darkxst> ratchek, quite rare on a fresh install
[06:38] <ratchek> darkxst, any ideas what i could try next or where to look for a solution?
[06:41] <darkxst> ratchek, not without seeing logs of the failure
[06:41] <mgedmin> exactly how hard does it freeze on boot?
[06:41] <mgedmin> can you ctrl-alt-f1...f7?
[06:41] <mgedmin> can you alt-sysrq-s,u,b?
[06:42] <darkxst> reboot and get /var/log/gdm/\:0*.log and /var/log/syslog
[06:42] <ratchek> mgedmin, haven't tried, I'm kind of new to this. I'll try now.
[06:46] <ratchek> mgedmin, ok, so the ctrl-alt-f1...f7 didnt' work
[06:47] <ratchek> mgedmin, also my laptop doesn't have sysrq for some reason, so i tried with the prntscrn button which didn't work either
[06:48] <ratchek> darkxst, mgedmin, also funny thing when i was turning off the live sesion, it froze. Again none of the other methods worked
[06:49] <ratchek> darkxst, hmm, i'm new to irc, how do i indicate that the message is to both you and mgedmin?
[06:50] <darkxst> you just did!
[06:50] <darkxst> could be a kernel issue if you can't switch to a VT with ctl-alt-f1 etc
[06:51] <ratchek> darkxst, that sounds bad and complicated/impossible to fix...
[06:52] <darkxst> ratchek, 1. maybe try boot with 'nomodeset'
[06:52] <darkxst> 2. do try the daily-image maybe whatever bug you are hitting is fixed in newer kernel
[06:52] <ratchek> darkxst, ok, i just tried turning it on again and it somhow booted to the recovery menu
[06:53] <ratchek> darkxst, is there anyway i can now supply the logs of what was happening at startup?
[06:53] <darkxst> no, you need to get the logs after it freezes
[06:54] <ratchek> darkxst, too bad, thought i got lucky.
[06:54] <ratchek> darkxst, would you please explain what nomodest is?
[06:55] <octoquad> darkxst, any reason apport isn't submitting bug reports? Just had a crash with gnome-shell...
[06:55] <darkxst> ratchek, its a kernel option
[06:56] <darkxst> octoquad, 15.04? maybe they haven't enabled them yet?
[06:56] <ratchek> darkxst, mhm, but what does it do?
[06:56] <octoquad> weird
[06:56] <darkxst> switches from kernel mode setting which does fix some issues for people
[06:57] <darkxst> octoquad, you can run ubuntu-bug on the crash file in /var/crash
[06:57] <octoquad> darkxst, commented out a line in /etc/apport/crashdb.conf
[06:57] <octoquad> busy submitting
[06:57] <darkxst> or yes that also
[06:57] <octoquad> proabably got reset on an update
[06:58] <darkxst> crashes still go to errors.u.c regardless I think
[06:58] <octoquad> oh
[06:59] <darkxst> which is a good way to find high-impact crashes
[06:59] <octoquad> well this was bad, lost the shell completely and was unable to use gnome-shell --replace as connection was refused
[07:00] <octoquad> although the firefox was still working, just no window management
[07:00] <darkxst> octoquad, what I do, and it will nearly always work
[07:00] <octoquad> ah huh
[07:00] <darkxst> switch to VT and do a metacity --replace
[07:00] <octoquad> nice
[07:00] <octoquad> I'll remember that
[07:00] <darkxst> sometimes you need to kill gnome-shell first
[07:00] <darkxst> with -9
[07:01] <darkxst> then restart gnome-shell once you are back in your X session
[07:01] <octoquad> I just do sudo service gdm restart and everything is back to normal haha
[07:02] <ratchek> darkxst, i did it, it worked like a charm!
[07:02] <ratchek> darkxst, thank you very much
[07:02] <ratchek> darkxst, do i need to do that every time i reboot?
[07:05] <ratchek> darkxst, ok, i think i found the answer to my previous question
[07:05] <darkxst> octoquad, but that kills your session!
[07:07] <darkxst> ratchek, what did you do?
[07:08] <ratchek> darkxst, change the /etc/grub file  from "quiet splash" to "quiet splash nomodest"
[07:08] <ratchek> darkxst, and then update-grub
[07:08] <ratchek> darkxst, haven't rebooted yet, so if something's wrong, now would be the time to shout :)
[07:09] <darkxst> ratchek, ok, the will stick, no need to do it next time you reboot
[07:10] <ratchek> you guys are all awesome
[07:10] <darkxst> ricotz, hi
[07:10] <ratchek> darkxst, do you mind if i ask to off-topic  questions?
[07:10] <darkxst> ricotz, http://pastebin.com/K0bBWtte look right?
[07:10] <darkxst> ratchek, ok
[07:11] <darkxst> ricotz, cdbs really doesn't make it easy to override make check ;(
[07:14] <ratchek> darkxst, first of all, i'm a 2nd year computer science student and i just recently learned about opensource softwarre. I wanted to start contributing via github or something similar, but while i've learned c++ and java in school well enough to continue studying on my own, when i tried looking at the opensource projects their structure overwhelmed me. It is so different than anything i have learned. I don't know if i'll be learning
[07:14] <ratchek>  that in school but do you maybe know where i could ease into the opensource world, so i could get aquainted with the way things work and eventually be able to contribute?
[07:15] <darkxst> ratchek, GNOME is mostly C, Vala and Javascript not very much c++
[07:16] <darkxst> ratchek, probably best way is to start by trying to fix a few (simple) bugs
[07:17] <ratchek> darkxst, i would consider learning C but that's not my main point. I'm looking for somewhere to learn the structure of coding projects in general
[07:17] <darkxst> ratchek, there is no one structure
[07:17] <ricotz> darkxst, hi. yeah, cdbs can be weird, but this seems to be more hacky/verbose than needed
[07:18] <darkxst> most of the big projects have kind of each evolved into their own different standard
[07:18] <darkxst> ricotz, do you have a better idea? common-post-build-arch doesnt work because it runs in fakeroot
[07:18] <darkxst> and common-build-arch seems to get called multiple times
[07:18] <ratchek> darkxst, any small projects floating arround you know about?
[07:19] <darkxst> ratchek, I would say just pick any project that interests you. then find a bug that annoys you and fix it!
[07:20] <ratchek> darkxst, ok, thanks i'll keep trying.
[07:20] <ratchek> darkxst, also departing, where there any stumbles when it came to irc protocol that i made?
[07:20] <ratchek> darkxst, anything i should be aware of?
[07:21] <ricotz> darkxst, i see, did you take a look at existing packagings?
[07:21] <ricotz> e.g. unstable-desktop/libsoup2.4/debian/rules
[07:23] <darkxst> ricotz, I did do a code search for xvfb-run in debian, though its rarely used in cdbs it seems
[07:25] <darkxst> didnt see that one though
[07:29] <ratchek> darkst, thank you once again
[07:29] <ratchek> goodbye
[07:29] <darkxst> ricotz, though that seems way more verbose than mine
[07:29] <darkxst> does xvfb-run really spam $HOME?
[07:30] <darkxst> or would that be for tests that require $HOME
[07:32] <ricotz> darkxst, not xvfb-run itself but the tests if needed
[07:50] <darkxst> ricotz, ok, which I pretty sure isn't needed for gjs tests
[09:43] <darkxst> octoquad, feel like verifying bug 1391102?
[09:43] <darkxst> (see comment #6 for instructions)
[09:44] <darkxst> and given its a MRE you just need to make sure it works fine (there is no specific issues as such!)
[14:20] <LinDol> hi all
[14:34] <JockeTF> Hellopaca, LinDol!
[14:34] <LinDol> JockeTF, Thank you for your greeting :)
[14:36] <JockeTF> LinDol: You are very welcome. ;P
[14:41] <LinDol> ;)
[14:43] <LinDol> I will go to the bed, have a  good night. ;-)
[18:44] <octoquad> darkxst, sure, I'll test in a VM and a real machine I work on for a day to make sure there are no problems.
[20:47] <darkxst> octoquad, thanks
[20:57] <octoquad> so far no problems in VM
[21:02] <darkxst> ok, wouldnt expect any problems really, in fact it fixes a bunch of crashes
[21:07] <octoquad> Is this a mission: https://bugs.launchpad.net/bugs/1129409
[21:09] <octoquad> Would tracker be updated for this as well? https://bugs.launchpad.net/ubuntu-gnome/+bug/1409461
[21:11] <darkxst> not sure if that is fixed in tracker 1.0.6
[21:12] <darkxst> seems alberto is the only one that knows how to fix the fglrx bug
[21:12] <octoquad> I suppose I could just ask him to enable the proposed repo to try tracker 1.0.6?
[21:13] <octoquad> and ask them not to reply on that bug report that it doesn't work because it might be a seperate issue with tracker
[21:26] <darkxst> octoquad, well it wouldnt have been introduced in 1.0.5/1.0.6 so wouldnt affect the SRU
[21:29] <darkxst> and it maybe crashing on a particular file on the users system, '/usr/lib/tracker-miner-fs -v 3 -n' would show that