[00:08] X won't start with Alpha 5 livecd. Same has been true since beginning of Karmic cycle. Any ideas? [00:08] I tried with safe graphics mode - still no X. [00:11] What graphics hardware do you have? [00:12] onboard nvidia card [00:13] I could be more specific but the machine in question is checking the hard drive currently. [00:14] anything useful in Xorg logs? [00:14] I can't check until fsck is done with it's work, but I will check them. [00:15] OK. The last working driver would also be a useful information. [00:16] hello everyone. i'm not sure what package this is a bug in---whatever part of the Display preferences dialog rewrites the Virtual line in xorg.conf, seemed to max out at 2048 by 2048, and so i couldn't get a proper dual-head setup with these 2 widescreens totaling 2726x768. i had to manually edit xorg.conf for it to work. [00:16] It has worked fine, just not with the Livecd. [00:17] Worked fine in jaunty or worked fine in older karmic? [00:17] Hi. I've got an hp mini 110, and i can get the broadcom bcm4312 network chipset working with the alpha5 live disk, but it's a no go once it's actually installed. any ideas? trying to modprobe the b43 driver causes a hard machine lock, with not so much as a whipser in my kernel/sys logs [00:17] dto: the applet that lets you change the screen does this [00:18] also, the fwcutter util which showed up in the live disk isn't there under restricted drivers once it's actually installd. [00:18] lokad: right but it doesn't work. it would always set the main laptop screen to 1024x768 [00:18] so the screen was scaled and blurry. [00:19] i tried both with that applet, and with the extra Multiple Screens applet, and the mulitple screens one said "user requested larger screensize than max screensize" which clued me into editing xorg.conf manually [00:19] after that, the applet works correctly [00:19] so i conclude the part that was writing Virtual 2048 2048 into the xorg.conf, is wrong [00:19] All i know is that 2048x2048 is the maximum resolution the embedded intel cards support whit acceleration [00:19] and some radeons [00:20] or rather, the largest single texture size, which constrains the desktop because the root window has to span the entire desktop [00:20] this is a laptop with a radeon and works fine with a wider virtual screen than that. so where do i report this? [00:20] when I play a flash video, sound stops working on my system. Is this a known bug? I see a bug report back in hardy on it... [00:21] ahh, found a bunch of similar bugs in jaunty...I should be able to find a fix, just don't know if it needs reporting against kk [00:21] dto, did you have compiz working on it before at the largest resolution? [00:21] cwillu_at_work: i never tried. i don't like compiz, i had trouble with it only allowing me 2 desktops === eltoozero_ is now known as eltoozero [00:22] hi DBO [00:22] dto, I'd expect it to be working fine under metacity in that case [00:22] ah, I see [00:23] in what file should i set vga=794 now that menu.lst is gone? [00:23] judgen, /etc/defaults/grub [00:23] dto, That max size almost certainly comes from the max texture size, and by extension, compiz-on-by-default [00:24] sounds sensible [00:24] cwillu_at_work: i dont have such files. [00:24] cwillu_at_work: so is this a bug? [00:24] cwillu_at_work: what happens if i add it to /boot/grub/grub.cfg [00:24] judgen, /etc/default/grub [00:24] you can only use 2048x2048 with compiz [00:25] here is my setup. http://imagebin.ca/view/jzTDyy.html [00:25] although it pains me a little that you didn't check that when /etc/defaults/ didn't work :p [00:25] *i* consider compiz-on-by-default a bug ;-) [00:25] cwillu_at_work: i dont have a file with the name grub in /etc/default/ [00:25] dto, I think you could file a bug against the resolution switcher, it's a tricky problem though [00:26] dto, mainly as an interface problem: how should the user be told that it'll only partially work? [00:26] Hello anyone, i'm having some problems with a bug, what happens is; when i remove the power cable from my laptop, the computer goes to sleep after some seconds. Im running karmic alpha5 with latest upgrades on a hp dv1667 [00:27] judgen, assuming that something in grub2 hasn't changed in the last couple weeks, I think you have a broken install [00:27] cwillu_at_work: they could just pop up a message saying that the underlying device might not support the resolution. [00:27] dto, but that's not true [00:27] oh [00:27] the underlying device supports it, but not accelerated [00:27] ah. [00:27] cwillu_at_work: ok [00:27] exit [00:27] the trick is how to do it in a _good_ way :) [00:27] well i have compositing on. does that require acceleration? [00:28] dto, yes and no [00:28] metacity compositing doesn't right now afaik, although they're going that direction (of using accelerated compositing) [00:28] can somebody give me a push in the right direction to resolve it? [00:29] compiz and most other fancy displays require hardware acceleration, and therefore need to have a max texture size large enough to accommodate the root window. This isn't a fundamental problem, but it's would be alot of work to hack around it [00:29] i just think it should not have 2048x2048 as the hardcoded max that it will update the virtual line to [00:30] dto, it's not hardcoded though, that's the max size supported by your card [00:30] cwillu_at_work: i am using grub 1.5 afaik. [00:30] cwillu_at_work: no it's not. i'm running at 2726x768 [00:30] dto, ... [00:30] dto, it's the max texture size supported by your card [00:31] i'm not asking that they change the method it uses to calculate it, i just think it should allow override [00:31] judgen: grub 0.97 you mean? [00:32] lokad: maybe... the one that came with jaunty... [00:32] i.e. if it knows the user has selected a monitor layout larger than 2048x2048 in some dimension, it could tell the user that acceleration will not work [00:32] judgen, and you don't have /boot/grub/menu.lst? [00:32] dto: i think it's some kind of auto guessing logic to keep your graphics accelerated [00:32] dto, yes, we've been through this already :) [00:32] dto, file the bug [00:32] ok :) [00:32] thanks [00:32] what do you think of my toshiba combo? [00:33] cwillu_at_work: nope, i have a grub.cfg that has the list in it though [00:33] dtchen: hey [00:33] judgen, stuff's changed out from under me there then, sorry :p [00:33] dtchen: someone told me to talk to you about pulseaudio. i'm running on the dev ppa and i have some issues [00:34] dtchen: do you have a minute to speak? [00:34] cwillu_at_work: now i got grub2... so shall i just add the 794 tag to it then? [00:34] shoot. [00:34] judgen, grub2 should definitely have /etc/default/grub [00:34] i think he still has grub-legacy from jaunty [00:35] cwillu_at_work: i got the default file now after installing grub2 [00:35] dtchen: zoom h4 not recognized. /var/log/messages shows http://pastebin.ca/1561642 [00:35] ok [00:35] but i dont know where to add the line for 1023x768 so usplash will run at that resolution. [00:35] 1024* [00:35] dtchen: m-audio fast track pro, works fine for playback, but can't choose between A/B outputs, also can't see recording input. [00:35] judgen, GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" [00:36] cwillu_at_work: aaah ok [00:36] thanks [00:36] dtchen: i'm going to test it with a delta 1010 but i can barely get ubuntu running on that machine [00:37] dto: first: echo autospawn = no|tee -a ~/.pulse/client.conf [00:37] dto: second: killall pulseaudio && pulseaudio -vvv [00:37] dto: third: need the debug output from -vvvv when you insert the device [00:38] dto: if you haven't filed a bug already, please do so, and attach the debug output [00:38] is 791 or 794 1024x768? [00:38] no idea, sorry [00:38] dtchen: which page/project do i file the bug under? [00:38] dto: just use "ubuntu-bug pulseaudio" [00:39] dtchen: thank you! [00:39] dtchen: ok i will pastebin the stuff in a moment [00:42] dtchen: can i comment out that autospawn line now? [00:43] dto: if the debug output is attached to the bug report already, sure [00:44] i'm working on an update for the version just uploaded to Karmic proper [00:44] it should land in the PPA RSN [00:47] Darnit, grub tells me that vga=791 is deprecated... what now? [00:48] dtchen: ubuntu-bug pulseaudio says, this is not a genuine ubuntu package. prolly cause i'm on the ppa [00:49] dtchen: i piped the two reports to a file. one for the m-audio, one for the zoom [00:49] dtchen: do you have a url i can use for reporting this bug? [00:50] dto: just report it as standard, then please make sure you update to the newer PA in the PPA once it builds [00:50] it should affect the pulseaudio source package [00:50] i.e., [00:50] Uploading pulseaudio_0.9.16-0ubuntu2~ubuntuaudiodev1_source.changes: done. [00:50] Successfully uploaded packages. [00:51] that's what you'll want to test [00:52] no ideas? [00:56] what'd i miss [00:56] my connection died [00:56] so i should tell you i'm using your ppa? [00:56] i mean, tell them [00:57] it should appear in the bug report once you rerun -vvvv [00:57] but i have been using the ppa already since the other day [00:57] to clarify: it should appear in the debug output of pulseaudio -vvvv once you attach it to the bug report [00:57] ok [00:58] wait, i only used 3 v's [00:58] should i re-run? [00:58] yes [00:58] ok [00:59] bbl [01:02] Hello anyone, i'm having some problems with a bug, what happens is; when i remove the power cable from my laptop, the computer goes to sleep after some seconds. Im running karmic alpha5 with latest upgrades on a hp dv1667, please someone help? === eltoozero_ is now known as eltoozero [01:09] yay! bugs reported. [01:16] hello people! [01:23] hi folks. is there any way to get the livecd to not start up x? i'm trying to live boot karmic alpha 5 on a machine w/ati hd4670 and the display is completely corrupted. i don't want to install karmic yet though, thus livecd === eltoozero_ is now known as eltoozero [01:26] hey guys, i wanna upgrade to alpha 5, if I install it from a usb, will I be able to keep all my settings and things like Music, Pictures, Documents? [01:32] hi, does suspend to ram work with ubuntu 9.10 and fglrx? [01:35] barry_: you can get the alternate cd image [01:36] barry_: but I don't really see the point [01:36] you want to try karmic but you don't want to run X? what's the point? [01:46] what's happening to the second artwork drop? [01:48] literal: the problem is that x does not work with my card. i want to try bryce's ppa but i can't get far enough in the boot process to pull that in. the altcd has no live boot and i'm not quite ready to install ubuntu on this machine yet [01:54] can someone recall the command to re-establish access to my NTFS partition ..error HalDevice invalid mount option.. I just did a kubuntu clean install [01:57] Hmm... update wants to remove gnome-games and gnome-games-common. Is this okay? [01:57] s/common/data/ [01:58] last I checked, those packages aren't required to boot the system, or get an x session going :p [01:58] a dist-upgrade removed Empathy today. what gives? [01:59] mneptok, you installed updates after some package was updated, but before empathy was updated to match it [01:59] happens all the time [02:00] I just installed Karmic and have a few issues if anyone can help...they are related to unreachable drives, lots of ? icons in folders and kwin crashes [02:00] less often immediately before alpha and beta releases of course [02:00] cwillu: sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade <--- perfectly fine procedure [02:00] So, I installed Karmic and the partitioner wouldn't be launched by the installer, so I just installed on a single 8gb partition on this netbook. I also selected to encrypt home partition[folder]. I now want to put /home on the second partition on my netbook[32gb], how would one go about this? [02:00] mneptok, that has nothing to do with what I said though [02:00] updated as in the actual package, not updated as in apt-get update [02:01] cwillu: yes, hence my question "what gives?" when will Empathy be updated against Python 2.6 updates (or whatever) [02:01] mneptok, might already be updated [02:01] unless you're updating immediately before an alpha is released (i.e., during the soft-freeze), it's quite normal for some packages to be uninstallable [02:01] cwillu: nope [02:02] so wait 24 hours and try again [02:02] cwillu: i know how this all works :) [02:02] do you now :p [02:02] you really should be checking the updates by hand if you can't afford to have something break [02:02] well, having been a Senior Ubuntu Support Analyst for Canonical for 3 years, i tend to have learned a thing or 2. [02:03] so that was a rhetorical 'what gives'? [02:03] cwillu: it was directed at whoever is maintaining the Empathy package. [02:04] sorry, it sounded like the usual "something broke in my unreleased operating system", I assumed the worst. My bad ;p [02:04] * cwillu goes and answers questions about pulseaudio and flash in #ubuntu for ten minutes as his penance [02:05] cwillu: not good enough. i want you to answer the next person that asks about iTunes, their iPhone/iPod, and Windows games. that's pure Hell. :) === scimitar is now known as Scimitar^ [02:06] mneptok: where can i get itunes for karmic? [02:06] * cwillu sighs [02:06] * mneptok bends over [02:06] barry_, dual boot, or use a virtual machine [02:06] mneptok: :) [02:06] qemu works fine, virtualbox works better [02:06] cwillu: sorry, i'm just yankin' mneptok's chain [02:06] you'll need to use sun's virtualbox (rather than the one in our repository) however if you want usb support to work properly [02:06] barry_, I'm obliging :p [02:07] :) [02:07] can anyone answer a few questions for me [02:07] firm maybe :p [02:07] cwillu: why can't i install "Super Maggot Deathmatch Arena 3D" for Amiga on Ubuntu?!?!? this OS SUUUUUUUUUUUUCKS!!!!111!!!!!1!one!! [02:07] mneptok, we have an amiga simulator, no? [02:07] I just installed Karmic and have a few issues if anyone can help...they are related to unreachable drives, lots of ? icons in folders and kwin crashes [02:07] Scimitar^: on partitions formatted as ..... [02:08] Scimitar^, install or upgrade? and was it an existing partition? and what filesystem did you use? [02:08] ntfs partitions [02:08] Scimitar^, wubi? [02:08] * cwillu curses wubi [02:08] Scimitar^: as karmic is unreleased, and even released versions of Ubuntu have to tiptoe around NTFS, breakage in that regard is not at all surprising. [02:09] and avoid wubi at all costs if your data has any value to you [02:09] Scimitar^: if you *need* working NTFS support, best to install Jaunty [02:09] Scimitar^: otherwise, be patient and a future update may well resolve the issues you see [02:09] cwillu: i have not succeeded in getting any version of wubi to work on my spanking new vista box [02:09] Scimitar^, the ? icons are also in ntfs drives? [02:09] they show up in dolphin on the left but tell me that utf8 is not a valid option [02:09] no they are in dev [02:10] that's normal [02:10] iirc [02:10] So, I installed Karmic and the partitioner wouldn't be launched by the installer, so I just installed on a single 8gb partition on this netbook. I also selected to encrypt home partition[folder] (and automatically decrypt on login). I now want to put /home on the second SSD on my netbook[32gb], how would one go about this? [02:10] Scimitar^: edit fstab and use ISO to address those partitions [02:10] h00k: edit fstab [02:10] I tried to edit fstab but it won't save [02:10] mneptok: is that where decryption...whatever its looking for is handled? [02:11] this is fun. i like yelling into canyons and hearing my echo. :) [02:11] mneptok: thats what I figured, alright. [02:11] Scimitar^, sudoedit /etc/fstab [02:11] * cwillu echoes [02:11] h00k: login. use rsync to get the data over to the other drive. then edit fstab and tell it /home is over there/ [02:11] mneptok: I did have access to ntfs on a previous karmic alpha5 32 bit install, but decided to finally take the 64bit plunge ...everything is really quite good so far except for the UUID error for the ntfs partition [02:12] h00k, re: encryption, you'll need to learn how to set up encryption in the first place, although it generally isn't too hard [02:12] hi guys [02:12] BluesKaj: just switched to AMD64 myself for this new laptop. what Flash option do you find the best? [02:12] h00k, otherwise, everything is the same at that point [02:12] just did apt-get install apache2 and i cant do /etc/init.d/httpd start [02:12] how do i start it heh [02:12] cwillu: yeah, I can move /home otherwise, no problem, the encryption part is what I wondered about. [02:12] mneptok: dunno yet , I havent tried youtube [02:13] h00k, luks is straightforward to do from the command line [02:13] mneptok, BluesKaj, the 64bit flash alpha (is it beta or released yet?) has been working okay for me [02:13] cwillu how do I save after the edit? [02:13] Scimitar^, which editor are you in? [02:13] cwillu sudoedit [02:14] cwillu, mneptok: thanks [02:14] vi/vim = ZZ, nano is ctrl-w (I think, but it says at the bottom) [02:14] nostahl, it's not httpd [02:14] nostahl, apache21 [02:14] vim is also escape : wq [02:14] args [02:14] /etc/init.d/apache2 [02:14] ah just figured that out as you typed it hehe [02:15] nostahl, apache2ctk has some additional args [02:15] ctl ratehr [02:15] agrh [02:15] * cwillu gives up on typing for today [02:16] Scimitar^, don't pm people without asking in channel first... I don't even see them half the time until an hour later [02:16] sorry that was a mistake [02:17] Scimitar^, luksformat -t ext4 /dev/path/to/partition [02:17] I think [02:17] hey, is 2.6.31 stable? [02:18] actually, use cryptsetup [02:18] it was released [02:18] i see that [02:18] i guess thats my answer then [02:18] still trying to get the editor to save fstab.orig [02:18] * cwillu cheers, now he can use 2.6.32 and maybe get his suspend working :p [02:18] i wonder if it will play with my nvidia drivers [02:18] Scimitar^, still haven't told us which editor you're using :p [02:18] gandhi, 2.6.31 works fine with our nvidia packages [02:19] I typed sudoedit /etc/fstab.orig [02:19] Scimitar^, do you see "write out" at the bottom of the screen anywhere? [02:19] ok lol now I feel dumb [02:19] don't, it's got my vote for the most gratuitous change in terminology :p [02:20] second only to "uncut text" [02:20] I did that told it to overwrite and then reopened fstab.orig and nothing is changed [02:20] Scimitar^, fstab should be what changed [02:22] nope no change there either...any way to do a root edit in kate? [02:22] not sure what the kde equivilent of gksudo is, but gksudo kate /path/to/file should work [02:22] I will try that [02:24] ne1 knows how to get the asus light sensor to work on karmic? thx [02:24] cool that accepted the changes [02:24] now if I did it right when I reboot I will have a drive mounted manually [02:27] mneptok: data is backed up on a thumbdrive ^.^ [02:28] Could not create LUKS device /dev/sdb at /usr/sbin/luksformat line 58, line 17. [02:31] I format this drive EXT4 and then use luksformat? [02:36] How do i get frambuffer modes to work with an nvidia card? [02:37] h00k, backwarsd [02:37] h00k, you cryptsetup the partition, open the partition, and then create the filesystem on the /dev/mapper/ device that gets made [02:38] h00k, man cryptsetup -> the luks extension section [02:39] luksFormat and luksOpen being the relevant ones (note that they're case sensitive... whoever made it "luksCommandName" instead of "luke commandname" should be shot) :p [02:39] ok mneptok , got the media plugins working ok on chromium..been using it for 7 or 8 wks now and I'm kinda liking it. [02:42] ne1 knows how to get asus light sensor to work on karmic? thx [02:42] !lol [02:42] Please don't use "LOL" and "OMG" and so forth on a regular basis. This is IRC, not IM, and using those lines on their own is not required, and it is rather annoying to the rest of the people in the channel; thanks. [02:43] hmm... what was the leetspeek thingy? [02:43] !1337 [02:43] 1337 i5 nigh-inc0mpr3h3n5ib13 70 u5 n00bs, 4nd n0b0dy c4r35 if UR 4 1337 h4x0r. Giv3 i7 4 r357. [02:43] ah, thanks :) [02:43] :D [02:43] neonflx, best bet is to google for the model of the laptop + ubuntu (or similar) [02:43] odds are that somebody somewhere has figured it out [02:44] cwillu: what is looks like is: cryptsetup create home /dev/sdb [02:44] first [02:44] i'm just hoping for support for adjusting the backlight on the inspiron 12 in karmic [02:44] h00k, you probably want to use luks instead [02:44] as it is, i *can* adjust the backlight, as long as i do it before the OS finishes booting [02:44] cwillu: luks failed, apparently this cryptsetup ran and I didn't see any errors [02:45] what error did luks fail with? [02:45] cwillu: Could not create LUKS device /dev/sdb at /usr/sbin/luksformat line 58, line 17. [02:46] cwillu: thanks for the patience [02:46] cryptsetup luksFormat /dev/sdb should do the trick (although I'd suggest using a partition instead of the entire disk) [02:46] is that the command you ran? [02:46] negative, but thats what I'll do now [02:46] Command failed: Can not access device [02:46] ta-da! [02:46] :/ [02:46] (ran as root) [02:47] no, its not mounted [02:47] :) [02:47] ne1 knows how to get asus light sensor to work on karmic? thx [02:47] wow, someone isn't paying attention at all [02:48] cwillu: althouth 'sudo cryptsetup create home /dev/sdb' worked. [02:48] neonflx, the best way to get on everyone's ignore list is to repeat the question after you've received an answer, without giving any indication that you've tried what was suggested [02:49] h00k, you know, I think it might actually _have_ to be a partition, rather than the whole drive [02:49] cwillu: so, create...a partition on this entire drive (ext4)? [02:49] h00k, use gparted to make a single partition on that drive, the full size of the disk, and without a fs assigned to it [02:49] type=none [02:49] ohok. [02:50] and then try crypsetup luksFormat /dev/sdb1 [02:50] iirc, a raw encrypted disk can have difficulties if you mistype the password [02:51] and luks allows you to change the passphrase without reencrypting the entire disk [02:51] cwillu: horray: Command failed: Can not access device [02:51] oh, I know [02:51] cryptsetup remove [02:51] you have an active mapping, from the other cryptsetup [02:51] i installed ubuntu-restricted-extras but still can't play dvds. [02:51] so cryptsetup remove home [02:52] and then reformat, again? [02:52] well, crypsetup luksFormat /dev/sdb1 [02:52] yeah..can not access [02:52] h00k, what does "cryptsetup status home" say? [02:53] maybe I just wait until the next karmic alpha is released and try to reinstall then ^.^ [02:53] h00k, I've got two machines using this :p [02:53] should be working [02:53] cwillu: /dev/mapper/home is inactive. [02:53] cwillu: this is my second, yeah. [02:54] [02:54] cwillu: yeah, cannot access device :( I am disappoint [02:54] Karmic Alpha 5? [02:54] h00k, dmsetup ls? [02:54] Karmic Alpha 5? [02:54] yes [02:54] THIS IS KARMIC ALPHA 5! [02:54] [02:54] mneptok, I take back anything I ever said to you that was apologetic :p [02:55] cwillu: cryptswap1(252, 0) luksformat1(252, 1) [02:55] cwillu: i think you just set a new world record for longest time befors that sentiment [02:55] ;) [02:55] i updated to the karmic kernel under jaunty, how do i enable karmic repos? [02:56] changed the apt source lines to karmic, but they are greyed out in the update manager [02:56] gandhi, that's not a good way to upgrade to karmic [02:56] use update-manager -c -d [02:56] +gksu [02:56] the alternative can be made to work, but you get to keep the pieces when (_when_) it breaks [02:56] cwillu: I believe it has encrypted my swap, also [02:58] ugh [02:58] gotta go [02:58] yay for the boss calling at 8pm [02:58] thanks for the help, cwillu. Peace. [02:59] holy fuck, 192 packages to update at once [02:59] pushed real hard today. [02:59] thanks cwillu [03:01] I'm going to try today's daily iso and see if that helps. [03:01] http://cdimage.ubuntu.com/daily-live/current/karmic-desktop-i386.iso === Lars_G is now known as Lars_G_zombie [03:55] grr, stupid udev... still refuses to give my sound card an output. [03:58] My styles are all messed up. [03:58] Half of 'em don't work. [03:58] When I go into the main menu with Human, half of the selected item has an orange background as expected but the other half isn't highlighted at all. [04:08] Any suggestions? [04:20] https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/427680 anything I left out from the bug report? I try to be helpful and not file a useless report. [04:20] Ubuntu bug 427680 in knetworkmanager "knetworkmanager crashes after resume" [Undecided,New] === chx is now known as chx_afk [04:37] So I've got to reinstall Ubuntu, thinking to jump to Karmic. Non-mission critical, everyday use. How's the beta looking? [04:37] chx_afk: run `apport-collect 427680` [04:38] chx_afk: that'll attach all the information the developers think is important === chx_afk is now known as chx [05:16] Amaranth: hi [05:16] chx: hey, did you run that apport command? [05:16] Amaranth: Package knetworkmanager not installed and no hook available, ignoring [05:16] Amaranth: No additional information collected. [05:17] chx: err, you ran it on the machine you have the bug on, right? [05:17] yes [05:17] chx: and you have knetworkmanager installed? [05:17] yes but the package is called network-manager-kde [05:18] chx: that package doesn't exist [05:18] erm sorry [05:18] plasma-widget-networkmanagement [05:18] i checked jaunty [05:18] that's the problem, you filed the bug on the wrong package in launchpad [05:19] chx: run that command again [05:19] Amaranth: sorry! running [05:20] chx: it's no problem, we'll get it all fixed up so the developers have a good chance of fixing it [05:20] its working [05:20] chx: btw, in the future the best way to file a bug is to run `ubuntu-bug plasma-widget-networkmanagement` [05:20] oh [05:21] sure [05:21] of course replacing the plasma bit with the package you want to file a bug against [05:21] i will try to be useful here, if i a atest os [05:21] that way it automatically adds the files the developers will want and you just have to describe the problem [05:21] *if i run a test os [05:23] btw Karmic is fantastic [05:23] thanks [05:23] it really feels a good release already [05:23] chx: btw, did apport tell you about the crash? [05:23] the occassional app crashing does not bother me too much [05:23] Hey, I'm noticing that Palimpsest is complaining about a bad disk, but the disk in question passes dell's DST short, WDs short and long test, etc. etc. Any idea what gives? [05:23] Amaranth: hm, no? [05:24] Amaranth: when it crashes next time i will look for me [05:24] *motr [05:24] *more (sigh) [05:24] chx: can you check the contents of /var/crash and see if there is a file in there that looks like it would be for the network applet? [05:24] tntc: known issue [05:25] Amaranth: absolutely there is! i should up then that, right? [05:25] tntc: iirc it considers _any_ errors a bad disk instead of errors over the threshold [05:25] chx: not quite, hang on a second [05:26] chx: apport-bug /var/crash/_bin_bash.1000.crash [05:26] of course change the path [05:26] chx: then tell me the bug number you end up with since it'll file a new bug report [05:26]