[04:50] are patches to remove g_thread_init completely from packages upstreamable to actual upstreams yet or should we just keep this as a diff right now? [04:53] micahg: i thought you needed to add gthread-2.0 to the pkg-config list, not remove it [04:53] broder: well, that's one option, but it won't do anything anymore in precise AFAICT [04:54] micahg: but presumably it's needed on older glibs, right? [04:55] yeah, maybe I should just change it to link with gthread-2.0 now that I think about it, but I'm wondering why people are adding patches to remove the calls [04:57] if there's actually any multithreading, that seems like it could be dangerously wrong [04:58] broder: which part? [04:58] not calling g_thread_init [04:58] is it actually no longer needed? [04:59] ah, yeah [04:59] well, it seems to b: http://developer.gnome.org/glib/2.31/glib-Deprecated-Thread-APIs.html#g-thread-inite needed, but doesn't support custom implementations [05:03] yeah, dropping the calls just doesn't feel like a great idea if you need them to do any multithreaded stuff [05:16] rhythmbox in 12.04 seems to have forgotten about the music store. :-/ [05:16] achiang: well, it needs to be ported to gtk3 for that [05:17] oh. [05:17] is there a blueprint for that? [05:19] this page is... missing stuff? http://status.ubuntu.com/ubuntu-precise/ [05:25] achiang: could be it's already ported, but that's why we didn't have it in oneiric [05:25] micahg: poking around with apt-cache search doesn't show anything promising === AfC1 is now known as AfC === huats_ is now known as huats [22:12] Ah, well. At least now I know *where* those bad sectors on the hard drive are... [22:15] you haven't replaced that drive yet? [22:16] RAOF: You should replace it ASAP! [22:17] Yeah, yeah. [22:17] I'm happy to ride it into the ground; all the data's safely duplicated elsewhere. [22:17] * RAOF is more annoyed with his SSD that's no longer appearing as a drive to the BIOS. [22:19] Oh, that doesn't sound good either. [22:19] What SSD is it? [22:20] Again, Déja Dup to the rescue. [22:20] A vertex 3. [22:20] Oh no! I wanted to get on of those! [22:22] is that a bios bug? [22:22] Only if it's a bios bug that applies to an x200s, a UEFI dell, and a legacy dell. [22:24] * RAOF wonders if there's been unusual power fluctuations; *all* his hardware has decided to do strange things. [22:29] That might be an explanation. [22:48] "unusual power fluctuations" shouldn't influence a laptop all that much, I think [22:49] Yeah; everything's plugged into surge-protectors, and the battery should cushion low-voltage events. [22:49] as should the power supply really [22:50] that's 3 levels of protection, at least [22:54] although, beware of network connections... [22:55] Also plugged into a surge protector. [22:55] Well, except for the DSL :) [22:56] I have my DSL going through a surge protector actually ;) [22:56] (although it probably won't survive a direct lightning strike...) [22:59] I got somewhat wary about these things after a neighbour got hit by a lightning strike and I lost several pieces of electronic/computer equipment by that too... [23:02] I lost a cable modem, a monitor, a router and an USB disk that night... [23:02] Oh! I think this might explain my > 1 minute login time on this system. There are bad sectors in some files that might get touched at login… [23:02] Ooh, ow. [23:05] well, I could rescue the actual hard disk, but the USB part was fried; and similarly only the ethernet parts of the router were fried, but that made them useless for the purpose I bought them ;) [23:06] Heh. [23:07] RAOF: bad sectors on an SSD should be relocated normally? [23:07] by the SSD firmware? [23:07] Yes, but only on write IIUC. [23:08] right [23:08] And this is a rotating rust. [23:08] well, maybe even on read, duno [23:09] I think it's only on write; it can't make a sensible relocation on read, as it doesn't have sensible data. [23:09] depends, it could relocate if multiple reads are needed [23:10] or if a read needs error corrections [23:10] depending on how they implemented stuff ;) [23:11] but i doubt most SSD are that clever :-/