[00:03] azeem, you missed the right order [00:03] dang [00:03] but probably you could guess one answer :-P [00:05] really, I'm reading the gdb manual to find out why the backtrace always says that the library doesn't have any debug symbol. [00:08] giaco: just in case u can use LD_PRELOAD=/usr/lib/debug/usr/lib/libGL.so.1.5.070200 gdb myappname [00:08] no, you can't [00:08] why? [00:09] was working all the time just fine [00:09] :) [00:09] no, it just contains debug symbols [00:09] ah [00:09] i see [00:09] that's what I've just learned: it segfaults immediately if I preload it [00:12] isn't there a way to confirm that gdb loads the symbols automatically? The backtrace says that /usr/lib/libGL.so.1 is used, but no symbols inside [00:13] giaco: that's really not on-topic for this channel; but are you sure that /usr/lib/GL.so.1 on your system is the one from libgl1-mesa-swx11? [00:16] slangasek, that's what this page says http://packages.ubuntu.com/intrepid/i386/libgl1-mesa-swx11/filelist [00:16] I've just installed it, I could reinstall it if it's necessary [00:16] that's the wrong place to look; the question is not "does libgl1-mesa-swx11 contain such a file", the question is "is that the package which provides that file on your system" [00:17] that question is answered by dpkg -S /usr/lib/libGL.so.1 - and now this is definitely off-topic [00:17] it's off topic, ok, btw libgl1-mesa-swx11: /usr/lib/libGL.so.1 and the debug is not working [00:49] kees: so it seems that pie breaks at least one test case in openldap 2.4.15 [00:49] slangasek: ^^ [00:49] slangasek: debian doesn [00:50] slangasek: debian doesn't enable pie in openldap right? [00:50] there's nothing in the Debian packaging to enable PIE, no [00:50] slangasek: great - thanks. [00:50] kees: how can I debug this? [00:52] mathiaz: ew, is it only with the new version? [00:52] mathiaz: I've actually never debugged a PIE problem, but I'd basically treat it like any other corruption problem -- what's die, where, what variables are involved, and how does it compare to the non-PIE version [00:53] kees: yes - 2.4.14 built sucessfully in jaunty [00:54] kees: 2.4.15 does not [00:54] kees: it always fails in the same test case. [00:54] kees: ok - I'll try to replicate the setup - a least I've got a test case to work from [00:57] /c/c [01:28] I pretty much got suspend to ram working pretty flawlessly. anyone have any ideas why suspending to disk can still be an epic failure? I'll try anything, any ideas? === asac_ is now known as asac === LaserJock_ is now known as LaserJock === asac_ is now known as asac [03:37] I finally got suspend to disk working too. but upon second resume, although everything appeared fine, my networking is dead. the first time it was fine. the second time, dead and sudo /etc/init.d/networking restart|stop|start didn't do a thing about it :/ [03:37] can someone help me troubleshoot that? [03:40] vbgunz: Help is in #ubuntu for dapper/gutsy/hardy/intrepid and #ubuntu+1 for Jaunty [03:42] ScottK: ok. thought this was a big issue here. I have about 90% suspend issues solved. 100% if not for the failed network on second resume. cool. === Knives is now known as Guest38101 [07:50] Good morning [07:52] pitti: moin [07:53] pitti: re apport-collect, in https://bugs.launchpad.net/ubuntu/+source/cups/+bug/336512 the reporter used apport-collect to collect additional information, but it looks like only the stuff reported by attach_hardware(report) got attached and not attach_printing(report), which is sadly the crucial bit. Any idea why? [07:53] Launchpad bug 336512 in cups "HP Deskjet F4180 not detected as printer on Jaunty" [Undecided,Incomplete] [07:56] sbeattie: but it does [07:56] sbeattie: there's Papersize and a (failed) lpstat [07:57] pitti: hrm, but where's the cups error log? [07:57] sbeattie: problem for error_log is that a normal user doesn't have permission to access it [07:58] Oh. mu. [07:58] PpdFiles is missing, too, though [07:58] sbeattie: looks like the hook crashed halfway through [07:58] sbeattie: let me try that here locally [07:59] pitti: was wondering if the failed lpstat was causing something like that. [07:59] no, shouldn't [08:00] but wait.. [08:00] nicknames = command_output(['fgrep', '-H', '*NickName'] + glob.glob('/etc/cups/ppd/*.ppd')) [08:00] sbeattie: ^ if the glob is empty, then this will hang forever [08:00] >>> apport.hookutils.attach_printing(r) [08:00] -> indeed that never returns [08:01] * pitti fixes [08:01] sbeattie: ah, and it also tries to attach "error-log", not "error_log" [08:04] cool, thanks for digging into it. [08:04] sbeattie: btw, attaching error_log will do fine for crashes (which are processed as root), but not for bug reports [08:05] arguably those log files should be root:adm, not root:lp [08:07] is there anything sensitive that gets reported in error_log? [08:08] well, file names, dates, etc. [08:37] tseliot, after all that, seems 180.11 DOES support the 216-core gtx260..... however, intrepid's kernel doesn't support the audio or networking on my board ;) [08:37] so seems i'll be updating my desktop to jaunty earlier than planned :| [08:37] directhex: problem solved then, well kind of ;) [08:38] tseliot, good thing i had a spare tg3 card === azeem_ is now known as azeem === seb128_ is now known as seb128 [09:29] StevenK: Hi. Do you maintain seed for mobile-meta? [09:30] slytherin: I do. [09:31] StevenK: just wanted to bring bug 337881 to your attention. :-) [09:31] Launchpad bug 337881 in mobile-meta "Please remove libpt-1.10.10-plugins-* from ubuntu-netbook-remix dependencies" [Undecided,New] https://launchpad.net/bugs/337881 [09:35] slytherin: Commented on, thanks! [09:36] Where are the removal reasons again? [09:36] StevenK: Could you please check why mesa-swx11-source was removed in intrepid? [09:37] StevenK: it's needed to build vnc4 it seems [09:37] Build-Depends: ... mesa-swx11-source (>> 6.4.1) [09:38] lool: The removal reasons have all been pulled into LP [09:39] Ah right [09:39] lool: But dropping a binary is up to the source package that provided it [09:43] StevenK: Right, I see it was dropped in mesa now; thanks [09:55] how can I download the linux-image souce? [09:55] the LPIA jaunty port has a mistake [09:55] strangely it lacks of the ext4 module [09:55] it has to be recompiled/patched [09:56] I'm fairly sure there's a bug report about that [09:56] apt-get --only-source source linux [09:56] I did them [09:57] I've targeted it for jaunty so that it doesn't get forgotten (bug 331848) [09:57] Launchpad bug 331848 in linux "Cannot mount ext4 on linux-image-lpia" [Medium,Triaged] https://launchpad.net/bugs/331848 [09:57] perfect [09:57] anyway apt-get --only-source source linux doesn't work with jaunty [09:57] it doesn't fetch the sources [09:57] just something like a meta package [09:57] only few bytes [09:58] correct [09:59] linux-meta [09:59] where's the source of those packages? [09:59] are you sure you used the --only-source option? [09:59] I've tried a lot of combinations, it just downloads the linux.meta [10:00] hmm, indeed that doesn't work, odd [10:00] oh. tee hee. the source package "linux" contains images; the source package "linux-meta" contains the "linux" package [10:00] yeah, but --only-source is meant to avoid that problem [10:00] http://archive.ubuntu.com/ubuntu/pool/main/l/linux/ anyway [10:00] apt-get source linux-image-2.6.28-8-generic ;) [10:01] sigh, there has GOT to be a better way to enumerate model= parameters for snd-hda-intel than looking at the source [10:01] generic will work for LPIA? [10:01] Cimi: same source package, don't worry about it [10:01] hmm, apt-get source seems a bit broken here [10:01] I mean when I will run the dpkg-buildpackage it will generate the lpia deb with custom kernel config? [10:02] if you're building on an lpia system, yes [10:02] but I want the lpia config with the lpia patches [10:02] just with ext4 support [10:02] mvo: why does 'apt-get source linux-source-2.6.28' print out some strange misformatted messages and then get me the linux-meta source? [10:02] Cimi: yes [10:02] I don't want a generic, i385 compiled for lpia [10:02] ok [10:02] *i386 [10:03] 'apt-get source linux-image-2.6.28-8-generic' doesn't work at the moment anyway [10:03] Cimi: just download the source from http://archive.ubuntu.com/ubuntu/pool/main/l/linux/ directly [10:03] cjwatson, I'm using apt-get source linux-image-2.6.28-8-generic [10:03] it works here [10:03] Cimi: you want the linux_2.6.28.orig.tar.gz, linux_2.6.28-8.27.diff.gz, and linux_2.6.28-8.27.dsc files [10:04] ok [10:06] cjwatson, I would like to attach a patch on the bugreport, which is the correct way to get debian diffs? I mean, i just need to use diff on the uncompressed folder or something different? [10:07] Cimi: is a patch actually going to speed things up? it would take a kernel developer about ten seconds to fix [10:07] (so I nudged them) [10:07] it's one second patch [10:07] so don't bother :) [10:07] ok ;) [10:08] Cimi: for submitting patches to the kernel in general though, https://wiki.ubuntu.com/KernelGitGuide [10:08] but since this bugreport is opened from days and no one did anything... [10:08] Cimi: so you could do that [10:10] cjwatson: looks like a bug, give me a sec, I have a closer look (it seems to prefer the binary "linux" that is build from linux-meta over the srcpkg "linux" [10:10] mvo: well, that's just the behaviour that --only-source changes; but linux-source-2.6.28 should be unambiguous [10:10] (I'm not asking for the --only-source default to change, that seems like a bikeshed) [10:11] Cimi: smb_tp said he'd fix it [10:12] cjwatson, so I just need to wait for an updated package? [10:12] that's usual when a developer says he'll fix something, yes :) [10:13] cjwatson, please ask him when it will be released: I have a big partition I would like to use, and I need to know if it worth a compile on my netbook [10:15] Cimi: you can ask him yourself, he's here [10:15] oh :) [10:15] smb_tp, ^^ [10:16] I am on it to enable the ext4 module [10:16] yeah [10:16] do you know when the package will hit the repository? [10:17] not exactly, I'll have to check with someone else, but I could provide you with intermediate kernels. [10:18] that would be wonderful, compilation on an atom is somewhat painful :) [10:18] _R("RTL8168d/8111d", RTL_GIGA_MAC_VER_25, 0xff7e1880) // PCI-E [10:18] damn. jaunty supports this, but not intrepid [10:18] I know :) Will update the bug when I got something up [10:19] smb_tp, something like a link on a deb? :-) [10:19] yep [10:19] amazing, thank you [10:20] intrepid has RTL_GIGA_MAC up to VER_20, new motherboard has VER_25 [10:20] cjwatson: it seems like the prolem is that it goes over the Source file sequentially and stops on the first (bin|src) name it finds. so if the bin linux name is found first it gives this confusing result [10:22] mvo, cjwatson https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/330103 [10:22] Launchpad bug 330103 in linux-meta "[jaunty] apt-get source linux-image`-uname -r` does not download sources" [Undecided,New] [10:28] thanks Cimi [10:38] pitti: with regards to bug 305790, any idea why lucene2 was never moved to main? [10:38] Launchpad bug 305790 in suitesparse "MIR - move to main for openoffice.org 3 build-depends" [Undecided,Fix released] https://launchpad.net/bugs/305790 [10:47] guys what package should I file this too Bug 338159 [10:47] Launchpad bug 338159 in ubuntu "Jaunty: libavcodec52 and libavutils49 conflict with the unstripped versions" [Undecided,New] https://launchpad.net/bugs/338159 [10:49] davmor2, you know that's intentional, right? [10:50] almost certainly but you can't overwrite the one with the other [10:57] davmor2: what do you mean by overwrite? [10:58] not clear to me. the conflicts is intentional, it forces apt to replace onewith the other (but never both together) as needed [10:59] right. Even I am not clear what the issue is. [11:02] slytherin: I understand this. How ever only synaptic is able to replace the packages. Add/remove and apt-get can't and don't give a sensible explanation as to why it failed === thegodfather is now known as fabbione [11:03] slytherin, directhex: It is this that I'm having issues with rather than the conflict in packages [11:04] davmor2: Both synaptic and add/remove use apt-get as backend. So I don't see why it should fail in apt-get and add/remove while it works in synaptic. [11:04] davmor2, you've neglected to paste the actual messages from apt/synaptic/whatever, which makes it harder to diagnose [11:04] davmor2: may be there is something wrong on your system. [11:05] slytherin: it's a vanilla install and it has been confirmed by others [11:07] directhex: it just says it can't be installed in add/remove syaptic says nothing it just removes the non-unstripped versions [11:12] superm1: around? [11:16] hm @ current gdm theme in jaunty. not unique & brown enough! [11:17] directhex: and I remember some problem with the right click menu not visible enough. [11:55] Keybuk: http://launchpadlibrarian.net/20975050/ifupdown_0.6.8ubuntu13_0.6.8ubuntu14.diff.gz [11:56] Keybuk: did you look at the debdiff before uploading? [11:56] asac: webm always goes mad [11:57] oh [11:57] that debdiff isn't even webm mostly [11:57] Keybuk: well. you trashed the complete _darcs directory ;) [11:57] it's just that _darcs isn't included in the .tar.gz now [11:57] Keybuk: can you do something like that: https://edge.launchpad.net/ubuntu/+source/ifupdown/0.6.8ubuntu12 [11:57] and this is a bad thing because? === pgraner-afk is now known as pgraner [11:57] Keybuk: unreadable debdiff ... [11:58] Keybuk: i dont care. its just that the feature to not up interfaces if they are managed=true by NM seemed not to work [11:58] and i tried to find the reason ;) [11:58] I guess dpkg doesn't include the _darcs directories anymore? [11:58] I would have just done dpkg-buildpackage -S [11:59] Keybuk: yes. you need to trick it [11:59] thats why i had this issue in ubuntu11 [11:59] yeah, can't be arsed with that [11:59] if a package needs to be tricked to dpkg-buildpackage, it's a bug in the package [11:59] Keybuk: its -I"" [11:59] or something [11:59] putting revision control in the package is a bug anyway [11:59] Keybuk: well. tell that debian ;) [11:59] Keybuk: i agree, but do having this diff in ubuntu makes future merges hard [12:00] we can fix that next time we merge [12:02] Keybuk: are you building on intrepid by any chance? [12:02] asac: hmm, the _darcs directory has come back again? [12:02] Keybuk: even after filtering out _darcs from the diff its still really huge ;) [12:02] cjwatson: yes [12:02] Keybuk: see bug 317761 [12:02] Launchpad bug 317761 in dpkg "dpkg-source sets -i -I by default" [Undecided,Fix released] https://launchpad.net/bugs/317761 [12:03] I'm just uploading an SRU for that now [12:03] ahh [12:03] interesting [12:03] Keybuk: not sure. i will check now if the ifupdown feature is really broken ... if not i will not care [12:03] I thought that was deliberate :p [12:03] if it is, i will let you knwo ;) [12:03] nah, causes real problems [12:03] heh [12:04] I should just upgrade dpkg to jaunty I guess [12:04] particularly for people who are intentionally trying to put binary gunk in source packages for one reason or another [12:04] you can test my SRU once it's approved :) [12:04] ok, deal [12:07] Keybuk: could it be that we dont run ifup -a at boot time anymore now? [12:07] but ifup IFACE for each individual one? [12:10] we do run ifup -a at boot [12:10] Keybuk: hmm ok. i will check why the managed=true NM case was broken on my last boot then [12:10] e.g. it was upped [12:11] thanks [12:38] just once [12:38] for one release [12:38] or even just one day [12:38] I'd like the brightness setting and keys to work properly on my Dell [12:38] :-) [12:39] i've never owned a dell where they DON'T work! [12:39] it seems computers just hate you, Keybuk [12:40] wfm? [12:40] but still - i'd *love* my next track button to work again! [12:40] * Hobbsee has never been able to track that one down [12:41] directhex: if I don't touch my laptop, the backlight basically turns off [12:41] then if I do anything ... nothing happens [12:41] it doesn't go brighter again [12:41] if I use the brightness keys, there are over a hundred presses required to get it back to full brightness [12:41] and you can't just hold the key down either :p [12:42] Keybuk: so the reason seems to be that the udev rules now trigger ifup UDEVDEVICE [12:42] asac: they have since ~dapper [12:42] really? [12:42] pretty sure it was dapper, yeah [12:42] Keybuk: then the order seems to have changed ... or the udev rules are now triggered on startup while they were not in intrepid? [12:42] nope, always been triggered on startup ;) [12:43] Keybuk: well. i 100% sure that ifup IFACE was not run on startup ... only ifup -a in intrepid ;) [12:43] Keybuk: any idea why? maybe the rules were broken? [12:45] anyway. now that i know whats up i will fix that somehow. [12:45] if they didn't run, that was a bug in intrepid [12:45] pitti: damn, you're ahead of me on http://qa.ubuntu.com/reports/bug-fixing/jaunty-fixes-report.html [12:45] it might have been caused by that whole /var/run/network/initialized madness [12:45] * cjwatson considers strategies for catching up [12:46] ... ethical ones [12:46] Keybuk: you mean ifstate? [12:46] asac: no, siretart did a whole bunch of changes in intrepid to try and fix a wpa_supplicant bug [12:46] but broke just about everything else in the process [12:46] he may have broken udev ifup too [12:46] we reverted them all in jaunty [12:46] oh... that might be possible [12:46] cjwatson: *psssst* secret tip: fix more? cjwatson: I have 5 more in the pipe right now :) [12:47] anyway, i will fix that somehow, but come back to you in case i am still on top of changelog for next merge round ;) [12:47] pitti: bah :) [12:47] I'm working on it :) [12:47] pitti: so i talked to wellark. he said he would prefer if we wait till next week with mbpi [12:47] go, cjwatson, go! [12:47] pitti: he wants to bake a real release over the weekend [12:47] pitti: did you already push the upload out? [12:47] asac: hm, MBPI? [12:47] oh, that [12:48] * pitti knows that as Meyer-Briggs Personality Index [12:48] ;) [12:48] (or something like that) [12:48] cjwatson, hmm, didnt flash-kernel get moved to main during the arm enablement ? [12:48] asac: can't talk longer, must fix more bugz!! [12:48] * mneptok is an ENFP [12:48] pitti: sure. just wanted to let you know that we should wait with the upload/SRU [12:49] * pitti is ISTJ [12:49] asac: (just kidding); thanks for the heads-up [12:49] * Hobbsee twitches at pitti [12:49] ogra: I had thought so but apparently not [12:49] cjwatson, ah, that might explain bug 336770 then *g* [12:49] Launchpad bug 336770 in debian-installer "Problems Installing Jaunty On NSLU2" [Undecided,Confirmed] https://launchpad.net/bugs/336770 [12:49] ogra: no bugs ever reported on flash-kernel so there can't have been an MIR either [12:49] asac: your nick always makes me think of notes Spanish-speaking developers write themselves to remind them to lock the house on the way out. ;) [12:49] yes, I'll reassign [12:49] right, i'll write one later today [12:50] Hobbsee: http://en.wikipedia.org/wiki/Myers-Briggs_Type_Indicator [12:50] mneptok: heh. how does that come? [12:50] pitti: i'm aware. it was discussed in lecture today, along with a whole lot of other management type things. it's interesting, but...wow... [12:50] casa [12:50] mneptok: ;) [12:50] make food [12:51] watch movie [12:51] asac [12:51] mneptok: actually when my nick is not avail, i use asacasa :) [12:51] * directhex is chaotic neutral [12:52] directhex: Chaotic Good FTW [12:52] mneptok, i'm a mono packager, i don't think i'm allowed good alignments [12:52] directhex: http://www.wilddamntexan.com/kids/demotivators/chaotic_good.jpg [12:53] * Keybuk always gets a different result every time he takes one of those tests [12:59] mneptok: isn't that just "good" in 4th ed? [13:00] Keybuk: i still have my First Edition rules. you kids ... [13:02] seb128: hey, any idea what change in Jaunty's gnome broke the way LTSP makes USB keys and other local medias to work ? [13:02] no [13:02] seb128: basically mounting something in /media no longer appears on the desktop [13:02] I've not clue about ltsp [13:03] seb128, gvfs used to pick up all mounts that show up in /media, does it still do that ? [13:03] seb128: LTSP mounts local devices in /media// so something like /media/stgraber/usbdisk-sdc [13:03] ogra: dunno, we got no bug about it not doing that and there is no reason to think that it changed [13:04] well, ltsp is the only thing acutally relying on it [13:04] you guys write a testcase which work on an ubuntu desktop and I will have a look [13:04] I don't plan to a ltsp install for that [13:04] indeed [13:04] hum? on media mounts? [13:04] and thats not needed [13:04] usb keys are mounted there [13:04] I've fstab partitions mounted there [13:04] on gvfs picking it up from the directory change [13:04] wfm [13:04] without hal being involved [13:05] ntfs and usb key are listed [13:05] or dbus ... [13:05] ok [13:16] is nvidia graphics driver 180 in intrepid considered "silent"? it's not present in hardware drivers and many users are wondering why [13:16] savvas, it's a backport. you need to explicitly install the modaliases [13:17] nvidia-180-modaliases package [13:17] possibly also run jockey-gtk -u [13:18] ah... thanks for the tip directhex :) [13:51] for those that were hitting the 2.6 problems with it, a fixed bzr-builddeb has just been synced, sorry for the delay [13:52] cjwatson: got that SRU yet? [13:54] Keybuk: it's uploaded and waiting for ubuntu-sru to review, I believe [13:54] Keybuk: you could pull the patch from the bug and build it [13:55] what's the bug#? [13:55] 12:02 Keybuk: see bug 317761 [13:55] Launchpad bug 317761 in dpkg "dpkg-source sets -i -I by default" [Undecided,Fix released] https://launchpad.net/bugs/317761 [14:02] doko: have you some time to look at python-4suite? Building for python2.5 works but with python2.6 setup.py only eats memory and I've no idea how to debug this. A build log is at http://launchpadlibrarian.net/23448421/buildlog_ubuntu-jaunty-amd64.python-4suite_1.0.2-7ubuntu1_FAILEDTOBUILD.txt.gz [14:03] geser: there's a bug report about it, not compatible with 2.6. we should repackage this as python2.5-4suite [14:04] doko: It is problematic though since it has rdepends. [14:05] ScottK: yes, however what do you want to do? [14:05] I want you to fix it? [14:05] Dunno. I'm afraid the transition to 2.6 isn't quite as smooth as I'd hoped. [14:06] jelmer: Are you interested in doing the packaging changes for samaba4 for Python2.6? I'd rather not be touched-it-last for samba4. [14:07] it's not a trivial one === BrunoX1ambert is now known as BrunoXLambert [14:09] ScottK, shouldn't it just be a binNMU (or whatever the equivalent of that is in Ubuntu)? [14:10] jelmer: We don't have binNMU, it's all sourceful uploads. It does look like rules needs a spot of work due to site-packages/dist-packages in 2.6. [14:12] jelmer, ubuntu doesn't have a maintainer per package per se, so there's no "non-maintainer" to upload. however, generally the last guy in changelog gets consulted about the package as a guy who "cares" about it, and i think ScottK would rather someone convenient with an @samba.org address did it instead of him ;) [14:17] Keybuk: hi, are you around? [14:17] always [14:17] Keybuk: sweet, could you have a look at Bug 71418 [14:17] Launchpad bug 71418 in sysvinit "/etc/init.d/(halt|reboot) disables WoL" [Low,Confirmed] https://launchpad.net/bugs/71418 [14:18] Hi, when proposing a debdiff to a package not currently using a patch system and not currently having any patches outside debian/ dir, is it correct to just patch the package in the traditional directly-in-.diff.gz way? [14:18] is there new information on it? [14:18] Keybuk: yes, i mean my latest comments :-) [14:19] maxb: yes [14:20] maxb: don't add patch systems to packages that don't have them, generally === Amaranth_ is now known as Amaranth [14:39] cjwatson: we had the "cdrom in fstab" discussion a number of times already; however, do you think it would be reasonable to at least use /dev/cdrom instead of hardcoded /dev/scd0?? [14:39] cjwatson: aside from the fact that the number might change, scd0 is already deprecated again AFAIUI (it's srN now) [14:40] right [14:41] Keybuk: ? [14:41] pitti: the installer doesn't hardcode /dev/scd0, actually [14:42] Keybuk: oh, that probably wasn't for me :-) [14:42] kirkland: tab open, please wait ;) [14:42] pitti: it uses the device that /cdrom gets mounted on [14:42] pitti: which I think comes out of 'list-devices cd' [14:42] cjwatson: right, I expect it detects it, but for the purpose of writing it into fstab I still consider it hardcoding [14:42] I could try to check whether there's a symlink pointing there [14:42] scd0 is a symlink itself [14:42] cjwatson: maybe easier: if /dev/cdrom exists, put that in, otherwise use the current device name? [14:43] scd0 isn't relevant [14:43] there's a /dev/cdrom and /dev/dvd, i wonder if there are blu-ray names. remind me to check [14:43] pitti: no, we should check that it matches the device actually in use, in case of multiple drives [14:43] cjwatson: be thankful it's even there before ;) [14:43] cjwatson: okay [14:43] the scsi cd maintainer was pushing pretty hard to just drop it and only have /dev/sr0 [14:43] * pitti wishes we could just drop it entirely for desktop installs [14:43] directhex: there are not [14:44] I've "/dev/scd0 /media/cdrom udf,iso9660 user,noauto,exec 0 0" in my fstab which breaks eject of unmounted CDs [14:44] Keybuk, aw. but how else can i feel special about owning a blu-ray drive? :o [14:44] for seb128's problem: eject apparently doesn't resolve symlinks in mount points === ilowe_ is now known as ilowe [14:45] $ eject /media/cdrom0 [14:45] eject: tried to use `/media/cdrom0' as device name but it is no block device [14:45] eject: unable to find or open device for: `/media/cdrom0' [14:46] so the bug is with eject, shirley? [14:46] well, that's clearly just a bug in eject as well ;) [14:46] absolutely [14:46] if it can't found the mount point name, and it's looking at a symlink, it should at least call readlink() [14:46] it just reminded me that we still put it into fstab in the first place, and with hardcoded device names [14:47] yeah, the fstab entry is ugly [14:47] I also find it odd that it's /dev/scd0 and /media/cdrom0 [14:47] shouldn't it /media/scd0 ? [14:47] (or just /dev/cdrom and /media/cdrom) [14:49] hum [14:49] bug #264071 [14:49] Launchpad bug 264071 in eject "eject -X reports "error while finding CD-ROM name"." [Undecided,Fix released] https://launchpad.net/bugs/264071 [14:49] pitti: you fixed that symlink bug in intrepid apparently [14:49] seb128: that's what I seemed to remember, but apparently not then [14:50] someone sync'd eject [14:50] * Merge to Debian unstable. Remaining Ubuntu changes: [14:50] - Fix eject -T for Macs (ioctl() can return EIO if tray is open). Thanks [14:50] to Andy Matteson for the patch. (LP #91873, Debian #504478) [14:50] - Resolve symbolic links when reading CD-ROM names, to fix "eject -X" [14:50] and possibly other modes. Thanks to Adam Buchbinder for the patch. [14:50] (LP #264071, Debian ##504480, submitted upstream via email) [14:50] it might also have been to resolve symlinks for device names [14:50]