[07:45] <mar77i> morning. I haven't dug into this, but boot spends quite some time looking for btrfs filesystems... can I disable that somehow? - tbh tho, I'm not even sure it's the last output's why I'm waiting (loading the kernel take 5 full seconds, even from a mechanical hd).
[07:45] <mar77i> *doesn't take
[09:11] <Fuzzles> have they changed all the icons in 13.04 or is it just the dash icon?
[09:19] <pecc> !raring | pecc
[13:19] <rohdef> is there a page with 13.04 know issues and what changes are there etc.? Seems that it has become impossible to google those any more :( usually the wiki for the next ubuntu was quite easy to find
[13:29] <BluesKaj> Hey all
[13:53] <eliasp_web> hi
[13:54] <smartboyhw> Hello
[13:55] <eliasp_web> I can't install debug symbols for KDE applications via DrKonqi… is this known to be broken? the dialog always just tells me "No debug packages could be found for the files listed below. Do you want to continue anyway?"
[13:56] <eliasp_web> haven't looked up manually yet, whether the actual debug packages are available… doing this now
[13:56] <eliasp_web> ran into this with at least smb4k and muon updater
[13:58] <eliasp_web> looks like there are none at all for smb4k…
[13:58] <eliasp_web> should I request them via Launchpad?
[15:34] <user82> !info wine
[15:36] <Bauer1> anyone experienced problems trying to install the special flash version for Steam on 13.04?
[15:37] <Bauer1> after opening the adobe-flashplugin in the software center, I get a message "Available from the "raring-partner" source" but clicking 'Use This Source' is not helping, it stays on the same way
[15:55] <bjsnider> adobe-flashplugin hasn't been uploaded to partner for raring yet: http://archive.canonical.com/ubuntu/pool/partner/a/adobe-flashplugin/
[15:59] <genii-around> Just wondering if anyone besides me had issues with 3.8.0-10 to 3.8.0-11 jump. No video, had to boot to recovery and install the headers and reinstall nvidia
[15:59] <Bauer1> hmmm, bjsnider  any workaround you could recommend in the meanwhile?
[16:02] <Bauer1> could I use one of the recent .deb packages perhaps?
[16:04] <bjsnider> the quantal package will work
[16:04] <bjsnider> i don't know about any special steam version though
[16:05] <bjsnider> i'm assuming you were talking about adobe-flashplugin since the message you got was about partner
[16:43] <user82> hello. wine currently has broken dependencies because the i368 version of wine1.4 is missing in the repos. what can i do? wait?
[22:06] <bazhang> !torrents
[23:19] <Bauer1> there might be a bug in 13.04 with the way terminal is handling deleted directories  on NTFS partitions - when I am inside dir a (in terminal) and I delete it from the GUI file browser - I cant do cd .. to get out of the deleted directory, I have to do cd full/path/to/dir/above/a to get out
[23:19] <Bauer1> as I said, not sure this bug is unique to 13.04 only
[23:19] <Bauer1> dont have another distro here to test
[23:22] <jtaylor> I think thats normal
[23:24] <jtaylor> you get somewhat weird behavior on non ntfs too
[23:24] <jtaylor> difference is probably in how the reference counting is done between regular unix fs and ntfs
[23:36] <bekks> linux isnt unix... :P
[23:38] <bekks> Bauer1: Your issue is based on the following: the directory entry of the current directory is deleted, so there is no chance to determine the parent of it. This behaviour is always the same, regardless of the filesystem.
[23:38] <jtaylor> no
[23:38] <bekks> And yes, thats no bug, thats an expected behaviour since decades.
[23:38] <jtaylor> most native linux filesystems will keep a reference to the directory, so the parent is still valid
[23:39] <jtaylor> ntfs apparently does not
[23:39] <bekks> You are entirely wrong. Show a pastebin proving what you just said.
[23:39] <jtaylor> whats the point
[23:40] <jtaylor> try it yourself in ext4 if you like
[23:40] <jtaylor> but its still not recommended to start applications from this semi invalid directory
[23:40] <jtaylor> many will crash as getcwd calls return null
[23:41] <bekks> jtaylor: I did it too often. I do know I am right.
[23:42] <alankila> the cd .. is emulated by shells as a general rule
[23:42] <alankila> to prove this, make a symlink like foo/bar -> foo/x/y/z and go to cd foo/bar. You are physically in z, but if you cd .. you are back at foo
[23:42] <bekks> And it is based on the current directory entry, which is invalid, so cd .. will not work.
[23:42] <jtaylor> yes thats great
[23:42] <jtaylor> I prefer bind mounts over symlinks
[23:43] <jtaylor> they don't have that problem
[23:46] <jtaylor> bekks: its not really invalid you can even go in it from another shell if you like
[23:46] <jtaylor> its only removed when the last reference is gone
[23:47] <jtaylor> same as with file which you can still read and copy even after deletion as long as something still has it open
[23:48] <bekks> Just try it and pastebin your proof.
[23:48] <jtaylor> it involves two shells, how would I pastebin that?
[23:48] <jtaylor> ok I can
[23:49] <bekks> Deleting the current directory in one shell, and issueing cd .. in the same shalle does involve one shell only.
[23:49] <bekks> *shell
[23:50] <bekks> An even in one shell, you can use pushd and popd.
[23:51] <jtaylor> http://paste.ubuntu.com/5597476/ happy?
[23:51] <jtaylor> ow got the wrong pid
[23:55] <jtaylor> its of course possible that this is just bash magic, as the entry for .. is not present anymore
[23:55] <jtaylor> if so I wonder why it wouldn'T work on ntfs