[01:13] <roothorick> alright so
[01:13] <roothorick> what's the now official way to hibernate
[01:13] <roothorick> *new
[01:43] <roothorick> does Trusty not support hibernation yet?
[01:43] <roothorick> pm-utils doesn't resume, uswsusp just hangs at start
[01:43] <roothorick> both have done that on two different systems now
[01:51] <roothorick> welp, I just found a system that does not have legacy boot
[01:51] <roothorick> a Toshiba laptop
[01:51] <roothorick> UEFI only
[01:59] <TJ-> roothorick: no CSM at all? what model?
[02:24] <roothorick> actually come to think of it
[02:24] <roothorick> it might just be a secure boot thing
[02:24] <roothorick> because the option is there but greyed out and set to "UEFI Only"
[02:24] <roothorick> Satellite L875D-S7342
[02:25] <roothorick> unfortunately not my machine, and the owner specifically requested Win8.1 with the OEM license intact
[02:40] <TJ-> roothorick: that would sound correct; no CSM in SB mode
[03:45] <utusan> dpkg ver 1.17.1 iin trusty as well as 1.16 in saucy is not cleaning up properly.  packages purged are still showing up in listing.
[03:46] <utusan> debian testing is now at 1.17.5, and this one is working properly
[05:07] <Darkangel> Is testing Ubuntu excitered as a Job? (Volunteer job)
[05:08] <holstein> excitered?
[05:09] <Darkangel> lol cant spell today
[05:09] <holstein> i thought maybe it was something lost in translation
[05:10] <Darkangel> na its english just cant spell it
[05:11] <TJ-> Testing can be boring if you're doing it for its own sake; if you're trying to do interesting things for their sake and just happen to be trying to use the latest development packages, that can be frustrating but fun when you find and then try to isolate bugs
[05:11] <holstein> is it "exciting"?
[05:12] <holstein> is testing exciting?.. is that the question?
[05:12] <Darkangel> I look for bugs and report them to Launchpad
[05:14] <Darkangel> lol i forget what it was but whats that bug when it freezes every thing up and ur 3 lights of CAPS, NUM LOCK AND SCROLL LOCK starts flashing
[05:15] <Darkangel> any 1 know what causes it?
[05:16] <TJ-> Darkangel: usually that can be a symptom of memory corruption
[05:16] <Darkangel> kk
[05:17] <TJ-> Darkangel: CPU's PC/IP (instruction pointer) reads an invalid code and goes off somewhere it shouldn't interpreting random data as instructions
[05:17] <Darkangel> can it be cause while installing something?
[05:20] <TJ-> Darkangel: can be caused by anything... buggy code, RAM modules going bad, or not properly seated, something interfering with the memory controller, etc.
[05:21] <Darkangel> ahh ok
[05:21] <Darkangel> thank u much
[07:32] <soee> hi, somaone has lately problems to strt lightdm ?
[08:13] <soee> were there some updates lately that have influance on lightdm ?
[10:59] <benonsoftware> Hi, I just upgraded to trusty, however when I boot into the default kernel it just displys a black screen.
[11:00] <benonsoftware> However, booting into 3.11.0-15-generic makes it boot normally.
[11:18] <k1l_> benonsoftware: kernel headers installed for the prop. video driver to built?
[11:22] <benonsoftware> k1l_: Sorry, I have no idea how to do that/check it.
[11:22] <BluesKaj> Hey folks
[11:23] <k1l_> benonsoftware: check if the linux-headers-... package is installed matching to the kernel linux-image-.. package
[11:23] <benonsoftware> Okay, will do
[11:29] <benonsoftware> k1l_: It appears I have it.
[12:00] <benonsoftware> Ah nevermind, I fixed it by changing to the nvidia drivers :)
[18:35] <Darkangel> lol holy crapper whats all the libboost files for? like what do they do? there in the "New in Repository" section
[18:38] <BluesKaj> Darkangel, "New in Repository" section?
[18:39] <Darkangel> its the option in Synaptic Package Manager
[18:41] <BluesKaj> in the repositories ? I don't use synaptic
[18:42] <BluesKaj> in /etc/apt/sources.list ?
[18:43] <Darkangel> na if u open Synaptic and then go to STATUS on the bottom right ull get a list above that and 1 of them will say "New in Repository"
[18:43] <Darkangel> bottom left i mean sorry just wook up not fully focused
[18:43] <UserError> Is python 2.7 still going to be installed by default and required for the trusty server install?
[18:44] <Darkangel> yes
[18:44] <Darkangel> ill have to check though on what version is running
[18:44] <Darkangel> there doin some fine upgrades for trusty
[18:44] <BluesKaj> look in the sources.list and put a # in front to disable the repository if you don't want it, then update
[18:45] <UserError> i hope 3.x is the only one installed
[18:45] <Darkangel> na i was just woundering on what it was for lol
[18:47] <Darkangel> Im running Python 2
[18:48] <Darkangel> oops
[18:48] <Darkangel> Im running Python 2.7.6 and some other 1 Python 3.3
[18:49] <UserError> ughhhh, 2.7 is never going to die
[18:49] <Darkangel> in trusty... but i thank the other 1 is for some other purpose
[18:52] <jtaylor> its a goal to remove it from the default install
[18:52] <jtaylor> desktop at least, don't know about server
[18:52] <jtaylor> it might have already happened?
[18:52] <UserError> nice
[18:54] <Darkangel> UserError: heres some info for ya with Trusty and Python https://wiki.ubuntu.com/Python
[18:54] <UserError> aw nice
[19:26] <UserError> So what i'm seeing is "we hope python3 will be the only one in Trusty"
[19:26] <UserError> :P
[19:26] <UserError> Can't even 2to3 like a boss
[19:33] <jtaylor> only in the default install
[19:33] <jtaylor> everything else is hopeless at this point
[19:34] <jtaylor> maybe in 16.06
[19:34] <jtaylor> 04
[19:37] <roothorick> hate to sound like a broken record b ut
[19:37] <roothorick> what hibernate mechanism, exactly, is 14.04 supposed to use by default? As far as I can see there isn't ANYTHING installed currently.
[19:45] <glitsj16> roothorick: should be pm-hibernate from the pm-utils package, and since 12.04 hibernate is off by default
[19:47] <roothorick> glitsj16: in 14.04 pm-utils isn't installed at all by default, and doesn't work
[19:48] <glitsj16> roothorick: you have the needed amount of swap in relation to RAM i assume?
[19:49] <roothorick> glitsj16: tried it on two different machines and the state of swap doesn't matter
[19:49] <roothorick> the resume= stuff isn't even on the kernel command line
[19:49] <roothorick> even if it was
[19:49] <roothorick> 14.04 automatically sets up cryptoswap which breaks that mechanism
[19:50] <roothorick> so I'm wondering if maybe we're supposed to use uswsusp now, but installing uswsusp renders the system unbootable
[19:52] <glitsj16> roothorick: could be, uswsusp supports encryption iirc
[19:53] <glitsj16> only relevant info i can find isn't conclusive though .. https://help.ubuntu.com/community/PowerManagement/Hibernate
[20:06] <Daekdroom> Is the Rhythmbox last.fm plugin working for anyone else?
[20:07] <Daekdroom> When I enabled it for Last.FM and leave the plug-in preferences, nothing happens and opening the preferences pop up again show me it's disabled.
[21:07] <TJ-> mamarley: ping
[21:16] <mamarley> TJ-: Switching sonar to active!  PONGPONGPONGPONG
[21:16] <TJ-> mamarley: :D
[21:16] <TJ-> mamarley: I'm busy delving into the source-code. I now know why it SEGFAULTS... but I need to identify the cause of that
[21:17] <TJ-> mamarley: Could you zip/tar.gz "/etc/init/*"    and "/var/log/apt/history.log"  and put them someplace I can pull them from? probably attaching them to bug #1269731 would be best
[21:18] <TJ-> mamarley: The crux of the issue is a pointer which is supposed to point to a data-structure that represents the jobs defined in /etc/init/*.conf files is NULL. So far it looks as if a faulty conf file syntax could be the reason
[21:19] <mamarley> That sounds logical.  Doing it right now.
[21:19] <mamarley> I still think it is an upstart bug though, because faulty input should never KP the system.
[21:20] <TJ-> I think it's a subtle change in eglibc and/or gcc, brought on by some significant re-ordering of the underlying assembly instructions generated.. I wouldn't be surprised if an upstart built without compiler optimsations works fine
[21:23] <mamarley> TJ-: OK, I attached the initscripts to the bug report. My APT history isn't helpful because I have my /var/log mounted on a tmpfs. (I know, very very bad mamarley)
[21:31] <TJ-> mamarley: hehehe yeah, I forgot you're trying to make it harder
[21:39] <TJ-> mamarley: I've updated the bug with my analysis - I'll look at your init scripts now
[21:47] <TJ-> mamarley: Just looking at modification times, three alsa jobs were modified on the 14th, and nvidia-peristenced.conf on the 9th. Could you move them out of "/etc/init/" temporarily and do "sudo telinit u" and see if the SEGFAULT still occurs?
[21:47] <mamarley> OK, just a sec...
[21:52] <mamarley> TJ-: When I remove those jobs, I can then run get_state.sh successfully from the desktop (I am testing using user jobs so I don't KP the system.)
[21:53] <jrr> using a recent ubuntu-gnome trusty image, the installer's live environment run nicely, and the installer seems to complete successfully, but the first boot stays at a black screen forever. where should I start poking?
[21:53] <jrr> (I can access the filesystem to see logs)
[21:53] <mamarley> (Before, running get_state.sh would cause either an X restart or a KP, depending on whether I did it for user or system jobs.)
[21:53] <holstein> jrr: where are you getting the iso?
[21:53] <genii> !nomodeset | jrr
[21:54] <jrr> http://cdimage.ubuntu.com/ubuntu-gnome/daily-live/current/
[21:54] <TJ-> mamarley: Can you add the jobs back one by one and retest after each one is added... we may be close to discovering the culprit
[21:54] <jrr> does the usb live image's nomodeset differ from that which is installed?
[21:56] <mamarley> TJ-: I added back all the ALSA jobs and that crashed it again.  I will now see which one is causing the problem.
[21:57] <TJ-> mamarley: You're a star :)
[21:59] <mamarley> TJ-: Thanks :) alsa-restore.conf makes it crash.  I will test the others too.
[21:59] <TJ-> with only one of them present at any time ... that would be great
[22:00] <mamarley> TJ-: Yeah, alsa-restore.conf crashed by itself.
[22:00] <TJ-> It may be they all contain the faulty syntax because they look, to me, to be almost identical
[22:01] <mamarley> TJ-: alsa-state.conf also crashes it.
[22:01] <mamarley> TJ-: All three of them crash it.
[22:02] <TJ-> OK... I'll report that
[22:04] <TJ-> mamarley: I think I've spotted the fault
[22:04] <mamarley> :) :) :)
[22:04] <TJ-> Can you move them out... then create a new empty alsa-restore.conf  and await my text for it?
[22:05] <mamarley> TJ-: OK.
[22:06] <mamarley> (With the empty file sitting there, it doesn't crash, by the way.)
[22:06] <TJ-> mamarley: http://paste.ubuntu.com/6764452/
[22:07] <mamarley> Should I add a final newline to that?
[22:07] <TJ-> yeah
[22:07] <mamarley> TJ-: It doesn't crash.
[22:08] <TJ-> Yay... I'm going to pastebin you the 2 other modified files
[22:09] <TJ-> mamarley: alsa-state.conf:  http://paste.ubuntu.com/6764479/
[22:10] <TJ-> mamarley: alsa-store.conf: http://paste.ubuntu.com/6764481/
[22:12] <TJ-> mamarley: I'm guessing it is OK now?
[22:13] <mamarley> Yep :)
[22:13] <TJ-> great teamwork :)
[22:14] <mamarley> :)
[22:14] <TJ-> I'm working up a patch for alsa-utils now
[22:30] <jrr> holstein: nomodeset gets me past the blank screen - I can now see all the text fly by, and then X starts at the wrong resolution. (nouveau)
[22:32] <jrr> googling suggests that nouveau requires nomodeset
[22:33] <jrr> er, the inverse - nouveau requires kernel mode setting
[22:34] <TJ-> jrr: resolution is read from the monitor's EDID  via DDC ... if that isn't being returned then issues will occur... first thing is to find out if the monitor is giving out valid modes: "xrandr -q" will help there
[22:35] <jrr> xrandr reports wrong (1280x1024 vs 1920x1080), but there are references to 1920 in Xorg log
[22:35] <jrr> "Supported established timings" vs "Supported standard timings"
[22:36] <jrr> also "DDC gathered Modelines" seems to carry the correct one
[22:40] <mamarley> TJ-: Shouldn't there also be a patch for upstart to prevent it from crashing when fed bad data?
[22:41] <TJ-> mamarley: I've suggested that... that's up to James though
[22:41] <TJ-> mamarley: (sloppy programming!) but don't say I said so
[22:46] <Fudge> is this ook to ignore, init: /etc/init/alsa-store.conf:10: Unknown stanza
[22:47] <Fudge> I am also getting  kernel panics when ever libc6 updates, have to chroot to fix
[22:56] <TJ-> Fudge: see bug #1269731
[23:06] <Fudge> TJ- thanks mate
[23:12] <Fudge> mamarley:  is bug 1269405  the problem with the suspected libc6?
[23:15] <Fudge> oh right, its the same
[23:18] <jrr> ooh look a kernel backtrace http://pastebin.com/33avdbMT
[23:18] <jrr> don't think I've seen one of those before
[23:26] <jrr> what's the appropriate way to file a bug for a kernel oops that I suspect is from nouveau?
[23:28] <jrr> 'linux' I guess =]