[00:01] whats ugly about it :)? [00:01] it's called a theme [00:01] again he says that cause he has been programing in qt since 99 [00:01] qt is nice too, but eh [00:01] who said that? [00:02] I'd use Qt if I wanted to write a cross-platform desktop app, because I like pyqt4 [00:02] but if I was going to write for the linux desktop, I'd use GTK, because that's what I typically use. [00:02] oh and gtk doesnt ship on most recent distros i think the whole qt gtk thing died years ago looks like i was mistaken [00:03] gtk doesn't ship on recent distros!? [00:03] That makes so little sense. I'm fairly certain I'm staring at much GTK right now [00:03] it was a joke ;) [00:03] oh ok :) [00:04] most of the required files are installed for both qt and gtk now its really a mute point [00:04] * tdignan cranks it up to 11 [00:04] So guys, Linus uses Gtk [00:04] https://github.com/torvalds/subsurface [00:04] also, he hates C++ [00:04] and you should follow him blindly [00:04] so Qt is out, see ya [00:06] oh lord [00:06] this is so 99 [00:07] desktop apps are something like steam engines now :) [00:07] gotta use HTML5, obviously. [00:09] people are here good maybe you can help [00:10] i keep getting complete lockups with latest kernel [00:10] latest video drivers as well [00:10] screen does does not crash but i cant use kyb or mouse [00:10] no killing and no ssh [00:11] have to hard reset [00:12] sysrq magic works though, right [00:12] no [00:12] nothing!! [00:12] I'd confirm that it's indeed a kernel issue and not a hardware one [00:13] i have been having this issue for 6 months and kept hoping it will be fixed [00:13] thats what i need the help with [00:13] I used to have a computer that froze to deadlock, and it was caused by an overheating hdd [00:14] wouldnt that through a warning with hddtemp [00:14] it didn't [00:14] no no errors [00:14] if you use a livecd does this problem happen? [00:14] its baffiling my [00:14] some times yes tdignan [00:14] this is an ivy bridge build [00:15] i'd put my money on hardware [00:15] yes but what would lock it up and not allow a sysrq? [00:15] and no obvious errors [00:16] anything that undermines the system beneath the kernel, such as overheating hardware, or cosmic rays [00:16] boot into the bios next time it happens and check the temp of things [00:16] i have temps are normal [00:17] key the key to [00:17] sorry* [00:17] i keep Hardware Sensors Indicator running and every thing is normal [00:17] what if you switch your video driver to vesa [00:17] i had a system lock up from some bad options in an nvidia driver once [00:18] thats what i run in the livecd and it will lock up as well [00:18] there are tons of bugs with these same problems but no one has any ideas [00:18] i even removed my fbconsole to make sure that was not the issue [00:19] there have been bug reports for months with this issues and i cant seem to narrow anything down and no one else can either [00:20] well sorry to hear it man. good luck. I had systems before that locked up, throwing them away was satisfying. [00:21] this laptop has a couple very minor issues, one of which I can fix soon.. a loose headphone jack.. Other of which I'll just deal with.. a flaky left USB port. [00:21] I got what I paid for. [00:21] sure i waited 4 years for a new build and i have no more money i will just buy a mac :P [00:21] cheapest laptop in the store, but with Linux it's blazing fast and lean on memory. Even when I'm using eclipse. [00:22] figure out what's wrong with it and replace the offending hardware [00:22] hmm thats an idea where to start [00:22] nothing in any logs any where and no warnings or errors [00:23] open the box and look for bad capacitors, they will look round on top [00:23] perhaps be leaking acid or rusty [00:23] check the power supply [00:23] i dont have a side on my box and there are no bulging caps [00:23] take it to the geek squad [00:23] ;) [00:23] ahahaha [00:25] i like the bog report from 10-26-2012 where they asked the person to bisect from 3.2.0-23.36 to 3.5.0-17.28 and find the problem [00:25] bug' [00:57] yeah, that's a common response to bug reports [00:58] "where's the patch?" === bazhang_ is now known as bazhang [04:37] not a wholw lot of updates this week [04:38] whole === Logan__ is now known as Logan_ === Amaranthus is now known as Amaranth === Logan_ is now known as Guest38655 === Logan__ is now known as Logan_ === Logan__ is now known as Logan_ === Logan__ is now known as Logan_ === Logan_ is now known as Guest61656 === Logan__ is now known as Logan_ === Logan__ is now known as Logan_ === Logan_ is now known as Guest78089 === Logan__ is now known as Logan_ === Logan_ is now known as Guest88149 === Logan__ is now known as Logan_ [10:41] Hey all === yofel_ is now known as yofel === jackhill_ is now known as jackhill === jbicha_ is now known as jbicha === Ian_ is now known as Ian_Corne