[00:00] Hi! How can you tell which version of QT you are currently running? [00:01] mattparry: apt-cache policy libqt4-core ? [00:03] crdlb - wow, thats what I like about linux - you learn something new everyday - thank you [00:07] mattparry: doesn't matter how long you use it for either..i started in 98 and i still learn new stuff almost every day. [00:18] ok how do I reconfigure x [00:19] whats the command in jaunty xorgconfig does not seem to be in a pkg [00:19] I lost my monitor and have to fall back to a older unit [00:20] ? [00:21] hello ? [00:22] unixdawg: sudo dpkg-reconfigure -phigh xserver-xorg [00:26] x comes up but I get a black background\ [00:27] unixdawg try xrandr also [00:28] unixdawg, got a new ati card? [00:29] "New" [00:31] its ati radeon xpress [00:32] unixdawg, well try adding Driver "radeonhd" under the device section [00:32] i've had xorg THINK it detects my graphics card correctly then give me a black screen [00:32] instead of picking the radeonhd driver [00:32] but come to find out it looks like the monitor only does 1024x768 and I cant get it to load in the proper res [00:33] meh. xorg is always trying to be clever and failing hard [00:33] i really dont know how to fix that piece of broken shit [00:43] well I just went and barrowed a moniter from my neighbor hoping it will come up in a min [00:43] I need to get in and backup my data [00:51] ok got it up witht he lcd [01:32] does anyone know if you have to install a separate package for the 'New' gnome artwork that is suppose to be in gnome 2.26? [01:53] ext4 is AMAZING! [01:53] yesh? [01:53] is the update-notifer not working for everyone or just me? [01:53] mphill_: intentional :/ [01:53] ok [01:54] Extents do make a difference [01:54] mphill_: now it will pop update-manager up in the background once a week [01:54] TheUnderTaker: so for those of us who haven't tried it, what is amazing about it ? [01:54] humm [01:54] are they going to switch to package kit or something? [01:54] there's a gconf setting to make it work the old way [01:55] faster fsck, faster file deletion times thanks to extents, less fragmentation [01:55] mphill_: not this cycle [01:55] afaik [01:55] although i dont trust it to my /home parition yet [01:55] crdlb, why did they do this? [01:55] TheUnderTaker: hmm, that's pretty smart :) [01:57] mphill_: because OS X does it :P [01:57] basically, they felt that users don't know what to do when they see the updates icon [01:57] windows does updates once a week too [01:58] no windows does updates once a month mostly called update tuesday [01:59] i found it: /apps/update-notifier/regular_auto_launch_interval [01:59] that's when they push them [01:59] which isn't what this is about; this is about when the computer does them / annoys the user about them [01:59] dood [02:00] well [02:00] thats the price i guess we pay for having a bunch of people jump ship to linux [02:00] :\ [02:00] it's design-by-committee at its worst [02:00] cya [02:01] i might install package-kit [02:01] its pretty nice [02:02] its not so bad as long as you have the ability to change it [02:15] hi guys, i just downloaded kubuntu alpha 6. [02:15] on both the computers i've tried it, so far a netbook and a desktop, plasma crashes immediately upon launch [02:15] it gives the following error [02:15] error message was: "org.freedesktop.DBus.Error.NoReply" [02:15] (when run manually from a terminal) [02:16] i essentially have no desktop. [02:16] this is a showstopping bug, even for an alpha release. [02:16] i googled the error message and got a launchpad bug that as of march 9, is labeled "fix committed." [02:16] however, i've downloaded all updates (had to plug in anethernet cable because network manager is now a plasma widget...) [02:17] no dice. [02:17] what's going on? how did an alpha get released that literally doesn't work? === lymeca is now known as ahnima [02:25] well after further googling i found a fix, luckily. if anyone else comes in and asks about the problem, tell them the fix is to run this [02:25] sudo rm /usr/share/kubuntu-default-settings/kde4-profile/default/share/config/plasma-appletsrc [02:31] I've been running Jaunty since ~Alpha 2. It is awesome. Love it. I had a couple complaints, but figured if I was patient, they would go away. All except 1 has. I can't get my bluetooth mouse to connect. bluetooth applet claims to connect, but the mouse stays in discovery mode. dmesg and /var/log/messages both look like they think the connection is happening.... [02:31] Any ideas what I could try [02:41] hi, has anyone noticed that apt-get update will resize your terminal window? It seems apt-get update sends escape codes to the terminal on summary, changes colors and such, but also resizes the terminal. [02:42] Can someone test this - make a terminal window much wider and then apt-get update? [02:43] victory747: I don't see that with gnome-terminal [02:44] your apt-get update has colors? [02:44] odd - why is it doing it for me? [02:44] yes [02:44] actually, it gives a big summary after I run apt-get update [02:44] of all the changes since the last time I ran it, I guess [02:44] I've only seen this in jaunty [02:44] are you sure that's not some kind of hook you added? === DBO2 is now known as DBO [02:44] I don't recall doing anything like that on purpose [02:45] hmmm, let me look into it - maybe i loaded in a package [02:47] ah, I think it's daptup [02:50] yep, that's it! [02:50] thanks for your help! [02:50] same happens here :) [02:50] you mean with daptup? [02:51] yes, it reverts the terminal to 80x24 [02:51] I wonder if that is intentional behavior [02:51] seems strange [02:51] I doubt it [02:51] maybe I'll file a bug against it then [02:54] although does anyone care about universe packages? [02:55] they do, just not to the same degree [02:56] it's just a shell script - I don't know where these codes are coming from [02:58] it uses tput [03:00] tput iniut [03:00] tput init [03:00] that is the offending line [03:01] it is? [03:01] yes [03:01] line 430 of /usr/bin/daptup [03:01] just type tput init in your terminal [03:01] I saw that, but it's not doing anything here :/ [03:01] ah [03:02] I hadn't made it wide enough [03:02] there must be a work-around [03:09] you can GET the width with tput cols [03:19] crdlb, why is the tput init there in the first place? Is it necessary? [03:19] I have no idea [03:19] I've never used it [03:20] are you still looking at this, or have you lost interest? [03:20] what is there to look at? :) [03:21] I want to fix it! [03:22] maybe I'll file a bug report against it [03:22] since I don't really understand it [03:22] ok, thanks for your help! [03:23] bug 251105 [03:23] Launchpad bug 251105 in vte "`tput init' works inconsistently in gnome-terminal, but not xterm, etc." [Low,Confirmed] https://launchpad.net/bugs/251105 [03:23] maybe? [03:23] hmm [03:24] tput init does not resize xterm [03:26] I don't think the init is needed [03:28] I'm going to write to the daptup author who is also the debian package maintainer [03:28] it appears to be for clearing any changes it made [03:30] tput sgr0 seems to do that [03:33] i don't think tput init is needed [03:38] i wrote to the author [03:38] thanks for your help [03:41] hey, reading that bug, it seems this is a problem with gnome-terminal [03:41] if I type "reset" in intrepid, it merely resets the terminal [03:41] if I type "reset" in jaunty, it resizes the terminal to 80 columns [03:47] ah! bug 330205 [03:47] Launchpad bug 330205 in gnome-terminal "terminal resizes when reset" [Low,Fix committed] https://launchpad.net/bugs/330205 [03:51] this is beyond me now, - back to work! [04:30] !find jcapimin.o [04:30] File jcapimin.o found in fp-units-base === Andre_Gondim is now known as Andre_Gondim-afk [05:06] Hi, Im running alpha 6 live CD - Plasma desktop not working - anyone else having this issue? [05:07] on kubuntu - btw [05:09] KMS is interesting, now that I built a kernel with it...... [05:09] ... but Plymouth doesn't work, for some reason. [05:18] pulseaudio messing up for anyone else? the new time scheduling mechanism or w/e...... at first tsched=0 fixed it for me, but no longer. my audio skips. and now i don't even know where to find the pulseaudio logs [06:06] why does vlc use alsa when pulseaudio is the default in jaunty? [06:07] i have to say.......this sound stuff is quite a mess :O [06:11] gnome-terminal: [06:11] Failed to contact the GConf daemon; exiting. [06:21] goddamnit, openoffice won't save to fat32. [06:21] Error saving the document " [06:21] Object not accessible. The object cannot be accessed due to insufficient user rights." [06:21] W------T---------F? [06:29] so is unclutter now active by default in jaunty? How do I turn this off? [06:31] unclutter? [06:32] Is the python package currently broken in jaunty? [06:32] Hobbsee: yes, the executable and packaged named 'unclutter'. It makes the mouse pointer disappear after a period of inactivity [06:34] sjanssen: oh. It's not by default, although it is in main [06:35] ah, I've figured it out [06:36] apparently the new version of unclutter adds a file in /etc/X11/Xsession.d that starts it automatically. This is a poor decision, IMO [06:37] well, if you've deliberately installed it, why shouldn't it automatically start? [06:37] it doesn't have any reverse dependancies, at all [06:37] I am getting this error when trying to upgrade python 2.6 http://rafb.net/p/G2oBpa98.html [06:37] or at least, according to my system. [06:37] hi, where should i file bugs against help.ubuntu.com? [06:37] Hobbsee: it is a notoriously broken program and I develop a window manager, I have it around for testing purposes [06:37] lanoxx: under the 'ubuntu-website' project on launchpad.net [06:38] sjanssen: ahhh. [06:38] Hobbsee, thx [06:38] it seems silly that installation should imply automatic use -- especially when there doesn't seem to be any way to disable without removing random files in /etc [06:39] removing the package again to stop using it doesn't work? [06:39] * Hobbsee is still unsure why it's in main at all [06:39] Hobbsee: sure, that works [06:39] Hobbsee: but isn't it silly for me to install and uninstall it every time I want to use it for just a few minutes? [06:40] it probalby is. OTOH, i'm not sure most people use it for short periods of time. [06:41] how strange. It should have dropped out of main, i'd expect [06:42] oh jeez [06:42] Hobbsee: IIRC it hasn't been maintained upstream for something like ten years [06:42] sjanssen: does it have the same bug where after the cursor comes back animated cursors are sized 1x1 pixel? [06:43] Hobbsee, should i file bugs about outdated pages there too? [06:43] lanoxx: yes, i think so [06:43] alright [06:43] compiz ezoom gets that if you zoom the cursor due to some bug in xfixes [06:44] sadly that python upgrade problem is blocking hundreds of other packages [06:50] why doesn't an ubuntu upgrade ever install new nvidia drivers? i always end up at a console after rebooting and have to install them myself [07:27] oh yeah, with accelerated ati driver, the notify-osd no longer lags so horribly. [07:29] I'm loving the new ATI drivers. I can watch videos without ridiculous flickering problems now <3 [07:29] I just wish they had some friggin' power savings. [07:29] I assume it was the -ati update that did that, anyway, since it didn't used to work and now does. [07:30] * DanaG happens to have R600. [07:30] oh yeah, you have tormodvolden's PPA enabled? [07:30] DanaG: nope. the jaunty repos got a snapshot of the new -ati drivers today [07:50] discovered data corruption issue with ext4 on Jaunty [07:51] anyone awake to check me? I submitted a reply to what I think is the relevant LK bug tracker report [07:51] http://bugzilla.kernel.org/show_bug.cgi?id=12821 [07:52] bugzilla.kernel.org bug 12821 in ext4 "filesystem corrupts on heavy I/O" [Normal,New] [07:54] python upgrade problems resolved by removing the offending packages, libboost-python-dev libboost-dbg pitivi [07:55] I ran into some corruption today when compiling a kernel.... all the compiled files had corrupt descriptors in some group. [07:55] Particularly aggravating was [07:55] Particularly aggravating was the [07:55] Particularly aggravating was the fact [07:55] ? [07:56] ... was the fact that, like I just did with my sentence... [07:56] .... it went back to the start after each SINGLE error fix. [07:56] 0->80%, back to 0->80.1% [07:56] well what was in dmesg? [07:57] oh, I don't remember now... lemme dig it up. [07:58] Oh, I remember.... [07:58] it was, some file referred to unused inode X in group Y, where X was a large (as expected) number. [07:59] or rather, referred to inode X in unused inodes table of Group Y. [08:39] does the version of Pidgin packaged with Jaunty apply any patches that modify its window close behavior? How do I go about figuring this out? [08:42] sjanssen: download the source package from jaunty repos and look at the patch files [08:47] i've been reading about ext4's delayed allocation and the zero-length file problem on reddit. might this be the reason why teh latest kernel update goes into panic when mountin my ext4 system? [08:50] http://www.reddit.com/r/programming/comments/846ih/ext4_delayed_allocation_and_the_zerolength_file/ [08:59] I'm using Ext4 [08:59] Haven't seen any panics [09:00] Lounge, no, a kernel panic would be a different issue [09:01] bug #317781 [09:01] Launchpad bug 317781 in linux "Ext4 data loss" [High,Confirmed] https://launchpad.net/bugs/317781 [09:01] more relevant than a reddit link :p [09:02] also, if it works with an older kernel, it's probably not the data [09:02] heh, bluez changelog. [09:02] (LP: #) [09:03] well i was just wondering about that if the latest kernel-image-2.6.28-9 panic and ext4 are related [09:07] anyone having issues with dual monitors and the login screen and logoff screens showing up dead center of the two monitors rather then just one [09:09] chipset? [09:10] * crdlb guesses nvidia [09:10] * cwillu doesn't presume :p [09:11] nvidia is the only one that doesn't always get Xinerama hints right nowadays :) [09:12] ya nvidia 9800gt [09:12] really? I don't think I've ever had a 'middle of the screen' issue except where an app didn't acknowledge the existence of xinerama (i.e., did the same thing on ati/intel) [09:12] MASQUERADE: lo ate my IP address [09:12] MASQUERADE: lo ate my IP address [09:12] MASQUERADE: lo ate my IP address [09:12] MASQUERADE: lo ate my IP address [09:12] unless [09:12] MASQUERADE: lo ate my IP address [09:13] um [09:13] .... what exactly does that mean? [09:13] beardbar-lap, did you plug in the second monitor after gdm started? [09:13] we only needed one [09:13] MMmm, IP address... sounds tasty. [09:13] im actually in ubuntu+1 i just noticed guys, im on kubuntu 8.10 running kde4.2 sorry [09:13] beardbar-lap, hold up :p [09:13] So tasty, it ate it multiple times. =þ [09:13] no, its been plugged in [09:13] the entire time. even during initial setup, this is a fresh install [09:13] beardbar-lap, nvidia's xinerama extension isn't enabled unless you had it configured at x start [09:13] yep, that's the usual problem with nvidia [09:14] hmm, dunno then [09:14] they haven't taken the changes in XRandR 1.2's version to make it truly dynamic [09:14] you had me at hold up, inspired my dreams of a fix and then left me on the side of road, a love lost :( hehe [09:15] beardbar-lap: xdpyinfo -ext XINERAMA| grep -i head [09:15] is alpha 6 release only a few days old? [09:16] crdlb: head #0: 3840X1200 @ 1920,0 head#1: 1920X1200 @ 0,0 [09:17] whoa [09:17] running 3 monitors 28inch samsung sync, and 2 24inch samsungsyncs [09:17] http://pastebin.com/f2beb2a3b [09:17] do you really have a 3840px wide monitor? :P [09:17] my xrandr [09:18] nvidia seems to be screwing it up [09:18] it's making head 0 the width of both of them, which would obviously screw up any apps trying to use that info [09:18] oh, 3 monitors? [09:18] ya 3 monitors, 2 on one card, 1 on another, both are 9800Gt nvidias [09:19] so I guess the other card is its own screen? [09:19] and that's the 28-incher? [09:19] exactly right [09:19] no its actually the 24, [09:19] I wonder if that's somehow confusing the nvidia driver [09:19] i wanted my 28 in the middle and the 24inces on the sides. [09:20] oh, I figured you'd have the two small ones on the same GPU [09:20] but I guess they're the same resolution anyway? [09:20] ya same reso [09:20] all 1920X1200 [09:20] can I have one? [09:21] Hi. Is anyone having trouble with the screensaver after updating today? On my system the windows freezes [09:21] anyway, my original description of the problem was correct [09:21] since the xinerama hints only apply to that one screen [09:21] the third monitor is out of the picture (unless it's somehow triggering a bug in the nvidia driver) [09:21] any suggestions on a course of action? [09:22] you could ask #nvidia [09:22] theres an actual channel hehe, checking it out, hey thanks crdlb, even when i was in the wrong room. [09:27] Okay, I no one has experienced this, I guess I should report it as a bug [09:35] anyone else think the removal of ctrl-alt-backspace was bad? [09:35] What is suggested replacement? [09:35] chronographer: you can reinstate it [09:36] chronographer: I am not a fan of disabling zap [09:36] yeah. is there a suggested replacement though? what happens when the game I run break and I can't get bac kto the desktop? [09:36] chronographer: there's a cli utility to re-enable it [09:36] chronographer, you can add it back in xorg.conf [09:36] chronographer: just re-enable it in xorg.conf [09:36] robin0800: no need to b0rk around with xorg.conf [09:36] magic sysrq can be a replacement [09:37] sudo apt-get install dontzap [09:37] chronographer: you can disable it in gutsy if you so wish, its not a new feature, just a new default feature [09:38] chronographer, you ever been on the other side of the phone call that starts "I was zooming in on a picture, and all of a sudden the whole screen went blank."? [09:38] crdlb: I've not seen how SysRq could be used from X11 [09:38] really? [09:38] lucent, you can put the keyboard into raw mode to force alt-f1 to work [09:38] oh... [09:38] sysrq+r for switching vts, or sysrq+k to kill X [09:38] the 'r' in 'reisub' [09:38] isn't Alt+SysRq trapped by X11 though? [09:38] no [09:38] sudo apt-get install dontzap <- sounds good [09:39] alt+SysRq here triggers the screen capture [09:39] heh [09:41] it should still work [09:41] or maybe you need shift or something [09:42] nope [09:42] I'd like to know what key combination you are pressing to do this [09:43] * crdlb just murdered his X for science [09:44] alt+sysrq+k [09:44] * cwillu gets crdlb a new one [09:44] where sysrq is printscreen [09:44] kill? okay, what about just switching term [09:44] r instead of k [09:44] http://en.wikipedia.org/wiki/Magic_SysRq_key - "Kill all processes on the current virtual console (Can be used to kill X and svgalib programs, see below) [09:45] This was originally designed to imitate a Secure Access Key k" [09:45] it means unraw [09:45] ah! [09:45] lucent: I get screenshot too [09:45] thanks for the info and labrattery [09:45] bug 276056 [09:45] Launchpad bug 276056 in xkeyboard-config "SysReq keyboard key acts as Print Screen (dup-of: 198748)" [Undecided,New] https://launchpad.net/bugs/276056 [09:45] Launchpad bug 198748 in gnome-control-center "sysrq and screenshot use the same keyboard shortcut" [Low,Incomplete] https://launchpad.net/bugs/198748 [09:45] * lucent lols [09:46] BUGabundo, k works though [09:46] r doesn't, but k does [09:46] ahh [09:46] sure [09:46] (k will kill the xserver though, don't do it on a whim) [09:46] but REISUB doesn't... yes [09:46] what if I don't need to kill X, and I just need to switch to a virtual console in a hurry? [09:46] eheheh [09:46] lucent, uh, switch to a virtual console then [09:46] if your server is in need of unrawing, I'd think it'd work? [09:46] lucent: ctrl alt Fx ? [09:46] ctrl-alt-f1 still works [09:46] cwillu: not every where [09:46] ctrl+alt+Fn doesn't work when X11 is borked [09:47] some intel and nvidia mess the TTYs [09:47] right, but that's no different from how it was before dontzap [09:47] point taken. [09:47] yep same thing [09:49] crdlb, sysrq doesn't work if I killall -STOP Xorg [09:49] sysrq-r rather. -k works fine [09:49] hmm, that sucks :/ [10:06] Hehe Linus hopes to to go stable next release... ;) [10:06] yea right [10:07] which Linus and what stable? [10:07] the famous one and the kernel one [10:08] oh .29 [10:08] yes maybe with a bit luck well see a stable .29 next week [10:08] you're waiting on .29 for some development? [10:09] no just for monitoring developement [10:09] not this again [10:09] currently im very interested in .30 [10:10] ikonia: me stfu? :) [10:10] do you follow lkml? [10:10] well, thats harsh [10:10] I want T.Tso's patch for dumb people applied [10:10] i follow the daily digest as far (bit) as i can and read lkml release notes [10:10] there's a tendancy for software authors to write really crappy code, and ext4 exposes the design flaws [10:11] it cripples ext4-as-root on Jaunty installs [10:11] lucent: what do you mena by that i installed on ext4 and using ext4 on all of my drives, still no data loss [10:11] CosmiChaos: mostly on power loss [10:11] i even tried copying files and hardresetting [10:11] ;) [10:11] which is a common event for desktops [10:12] yes i know, i have no losses for months with sometimes power losses [10:12] I've been bitten by ext4 related dataloss no fewer than a dozen times since Jaunty alpha 3 [10:13] there are some bizarre code paths that you have to hit to trigger the problems [10:13] I am just lucky to hit these code paths? [10:13] * lucent :( [10:13] O.O.o i converted all my storage 3 days ago ;) [10:14] seems like me is not using any of those related coded programms [10:14] and this is why I don't use new filesystems [10:14] till now im a lucky btch [10:14] at the moment I have an 1TB ext4 volume which is experiencing somewhat-reproducable data loss on a 50GB bittorrent download [10:15] if I leave Transmission running for longer than an hour or so, there's a scary message in dmesg and sync() no longer completes [10:16] http://bugzilla.kernel.org/show_bug.cgi?id=12821 [10:16] bugzilla.kernel.org bug 12821 in ext4 "filesystem corrupts on heavy I/O" [Normal,New] [10:16] lucent: as far as i can tell, my / root partition is on ext4 and has no dataloss under sometimes heavy power losses, and my storages are most of the time shut down because they are filed up completely with media [10:16] :) [10:17] took me lonk nights to get the fragmented NTFS to ext4 [10:17] I think you're just not pushing it hard enough yet [10:17] what can i do? [10:17] :D [10:18] any reproducablility, should i try downloading some torrents? [10:18] well, how many files are on the volume? [10:18] the 465GiB is ehm 550 files, full [10:18] also was this some ext2/3 volume that you mounted as ext4, or was it formatted as ext4? [10:18] the 372 is 1/3 full [10:19] no i installed alpha 5 on clean new partitions with ext4 [10:19] mine is "21,227 items, totalling 371.3 GB" [10:19] i removed NTFS completely and created new ext4 [10:19] and transfered all my data [10:20] yeah it's probably okay if it wrote out cleanly [10:20] i swaped them out, since i have 3 drives for storage [10:20] I don't have any problems yet *reading* data [10:21] * lucent just notices something [10:21] kernel option profile is one of the tasks i often do tough it writes alot to hdd [10:21] hope it's not confusing that my name Eric Shattow is similar looking to Eric Sandeen on the above bug report [10:22] CosmiChaos: there will be no mistaking it if the bug bites you, shit stops working and you can't cleanly shut down [10:22] lucent: but i will of course try out some torrents, did you say one 50gb torrent?? [10:23] I've hit a lot of different torrents that worked just fine [10:23] lucent: then ill pray to eris that only /root is affected [10:24]