[00:00] ahahah :) === vorian is now known as MadMule === MadMule is now known as vorian === vorian is now known as evil[v] === evil[v] is now known as evilv === evilv is now known as vorian [01:46] who suggested disconnected imap? [01:46] to make kmail stop crashing? [01:50] Can someone take the new wiki theme for a test run please? It works fine here, but that doesn't necessarily mean it will work there :) http://wiki.ryanak.ca/kubuntu/ [01:54] ryanakca: The last modified text at the bottom is hard to read for me [01:55] Looks great otherwise [01:55] maco: I think approximately everyone who's used Kmail with imap. [01:55] (not me or JontheEchidna). [01:56] heh [01:56] :p [01:56] well im wondering if its normal that kmail decides to mark all the read messages as unread every danged time it syncs [01:56] * ScottK finds it normal for imap connections to do weird things. [01:57] * ScottK tries imap every now and then and then scurries back to nice, safe, comfortable pop3. [01:57] Tonio_ was one that suggested it. [02:00] maco: kmail4 + imap works pretty well [02:00] maco: but imap disconnected indeed works a lot better... [02:00] kmail4 + imap = crash on delete [02:00] kmail4+dimap = hey i already read that! stop marking it unread! [02:00] ryanakca: The actual content section is very small compared to the current wiki theme [02:04] Kubuntu logo seems to be in low res [02:10] nhandler: *nod* [02:10] JontheEchidna: Made it darker (same color as the date for articles on kubuntu.org), better? [02:11] ryanakca: much better [02:11] ryanakca: That is a lot better and easier to read imo [02:12] nhandler: Which? The smaller? Or the wider? [02:12] Or you talkin about the date? :) [02:12] s/talkin/talking/ [02:14] ryanakca: I was talking about the date [02:14] Ah, ok :) [02:15] I still think the content area should be bigger ;) [02:20] nhandler: *nod*, I'll ask seele how wide the max-width should be :) [02:21] :) [02:57] Tonio_: do your messages get marked as unread in kmail even after you've read them? [02:57] maco: nope... never happened [03:14] One thing about IMAP is that many issues are IMAP server implementation specifiy. [03:14] The IMAP specs are complex and vague enough that there's a lot of variations in how stuff works. [03:15] If I were to guess, the IMAP servers at your providers are running different IMAP servers and so you see different behavior. [04:23] wow, whoever worked KDEPIM into submission, great job! [04:23] I set it up for GMAIL and my funky folders, disconnected IMAP, and whoa it did everything fast [04:24] only downfall right now for Kontact, still doesn't have native Google Calendar support [04:25] Which would be handy in the project since we're now using Google Calendar. [04:25] seems I have to find out why KOrganizer keeps popping up an error about a file not existing anymore [04:26] I tried to setup a gcal sync and it didn't work like I wanted to [04:26] so I removed it and now korganizer keeps complaining that file isn't there, but there isn't even a calendar object using it anymore [04:26] oh man, these screen profiles have to go away on the server [04:30] ahh, so much better [08:19] * a|wen hugs apachelogger, vorian, Quintasan, JontheEchidna, Tonio_, Riddell, Lure, ScottK ... and goes for the new motu page + sponsors queue [08:25] * Quintasan hugs a|wen back [09:45] * Lure hugs a|wen back === siekaczx is now known as siekacz [12:46] hi [12:49] \o [13:44] Anyone up for Raptor Menu testing? [17:09] What should I install for debug ofplasma in KDE 4.2.1? [17:09] kdelibs-dbg is enough? [17:10] kdebase-workspace-dbg would be needed to [17:10] ok [17:10] and if it's a folderview-related crash you'd want kdebase-dbg [17:10] I don't know what it is [17:10] it crashes as soon as it starts [17:11] could be bug 338205 [17:11] Launchpad bug 338205 in kdebase-workspace "[jaunty] plasma crashes on start with SIGSEGV" [Medium,Fix committed] https://launchpad.net/bugs/338205 [17:11] Which I should probably fix soon [17:15] JontheEchidna: the error is Unrecognized character: / [17:16] And redirecting either stdout or stderr doesn't catch it [17:17] DaSkreech: does it work if you remove plasma rc files? [17:18] mhh, I cannot change fontsize of firefox with the ne qt-curve gtk style. Is this a known problem? [17:18] smarter: it works for slightly longer then crashes again same error [17:18] let me edit the new plasma-applets to be more dumb [17:18] strange [17:18] Yah [17:19] Oh it doesn't exist [17:30] a|wen: one question: is your kile 2.1 package still available somewhere? I can't find/get it [17:35] DaSkreech: That's not the error causing the crash, that happens all the time [17:36] hmm never noticed before [17:36] http://pastebin.com/m7c552eea [17:37] Yeah, that's the bug I mentioned earlier [17:38] It's Kubuntu specific ? [17:39] What happened? [17:39] I had plasma working fine and then this started [17:39] I didnt update or anything unless ubuntu intalled them silently [17:40] Nah, not Kubuntu specific [17:40] Did you change monitor resolution recently? [17:40] Yeah just noticed [17:40] Nope [17:40] Though [17:40] My fonts look nicer [17:41] this happened right after an X crash now that you mention it [17:41] I'll get to applying the patch in a bit, but I need to do some other things first [17:41] Then I'll need to find a sponsor for the upload [17:41] Sure let me play round in systemsettings [17:42] Apparently if you remove the Geometry related lines in plasmarc (not plasma-appletsrc) it won't crash [17:42] Though I haven't had this bug personally [17:50] ok [17:50] lets try that [17:51] oxygen-cursor-theme-extra is so neat! i suggest making it installed by default [17:52] how useful [17:53] Nope still crashes [17:59] JontheEchidna: Why would removing the rc files not autodetect the geometry? [18:10] Dunno [18:11] * JontheEchidna has time to incorporate the patch now, though [18:16] Tonio_: Thx for making the changes for qtcurve in -workspace [18:16] JontheEchidna: np :) I just did properly in kdebase, kds and also the seeds [18:17] JontheEchidna: everything should be in the repos toonight :) [18:17] Oh, so now my seed branch doesn't need merging [18:17] Great! [18:17] JontheEchidna: I also managed the transition, which you kds changes wouldn't (that's why I renamed and deleted the old file) [18:18] otherwise with startkde, the .gtk-kde4 wouldn't be updated :) [18:18] Good thinking [18:19] Anyways, I will have a kdebase-workspace crash-on-startup fix that will need sponsored in a bit [18:19] After I testbuild it in a ppa [18:20] JontheEchidna: I'll sponsor, just ping me :) [18:20] Ok, thanks in advance [18:20] yw :) [18:27] Riddell: the more we replace packages, the more I am concerned with the upgrade manager [18:27] Riddell: shouldn't we consider removing adept, knetworkmanager and gtk-qt-engines ? [18:27] adept concerns me especially, since people can miss the new kpackagekit and continue using adept [18:28] Lure: just saw your comments on k3b.... so you have a hang at the end of the burning process ? sounds bad :/ [18:29] * JontheEchidna takes the dog outside while kdebase-workspace builds in his ppa [18:36] Tonio_: yes, burn of Kubuntu ISO to DVD-RW. I had to kill -9, but image was burned OK (could boot from it) [18:36] Lure: that sounds pretty hard to fix.... maybe we should connect to trueg to get that done in time for beta [18:37] Tonio_: will test a bit more next week - this was just first try [18:38] Lure: oki ;) [18:38] Lure: thanks for the help on that point [18:38] Tonio_: it may be USB related (my new laptop does not have DVD at all) [18:49] [repeat] Could those who haven't take the new wiki theme for a test run please? It works fine here, but that doesn't necessarily mean it will work elsewheres. :) http://wiki.ryanak.ca/kubuntu/ [18:50] ryanakca: works here :) It's very nice [18:52] Quintasan: *nod*, thanks [18:54] ryanakca: let me crush it for you (;) [18:54] ryanakca: seems to work well with Arora(and Qt 4.5.0) [18:54] but I still hate fixed-width themes :p [18:58] smarter: ... it isn't fixed-width? [18:58] it is here [18:59] smarter: It has a max-width... but... dunno why it would be fixed-width for you and fluid here... try resizing the window? === sfs is now known as _StefanS2_ [19:00] ryanakca: oh, no you're right, when I say fixed width I mean max width [19:00] ah, :) [19:00] because, even if the background gradiant is nice, wasting 40% of my screen pixels to display it is really not worth it imho :p [19:00] indeed === _StefanS2_ is now known as _StefanS_ [19:05] Tonio_: For adept as long as we have update manager remove it in favor of kpackagekit, I think it doesn't hurt to have it still around. [19:06] ScottK: hum, that's just what I said, should update manager remove it ? :) [19:06] * ryanakca scratches his head and wonders about the usability / readability side... aka, 70 to 80 characters per line. [19:06] Tonio_: OK. I misread then. I thought you were talking about removal from the archive. [19:06] ScottK: I agree we shouldn't have conflicts/replacements to get it removed [19:07] Tonio_: IIRC Riddell spoke in favor of this the other day. I'd suggest file a bug against update-manager. [19:07] ScottK: but we have to ensure an upgrade will drop the elements we wanted droped from the default distro [19:07] Yes. IIRC Riddell said we did that with Guidanced Power Manager already. [19:07] So this is just more of the same. [19:08] ScottK: yep, and the same with gtk-qt-engines now :) [19:08] Yes. [19:08] and knetworkmanager of course... [19:08] Yep. [19:08] I really like qtcurve it really gives gtk apps a nice look [19:08] That one I think we should leave on the dvd though, just in case. [19:09] and doesn't have bugs in it like gtk-qt-shit.... [19:09] ScottK: imho having both the plasmoid and knetworkmanager talking to networkmanager at the same time can be pretty dangerous.... [19:10] ScottK: I suspect this can end in strange behavior since they don't use the same api to communicate with the backend... [19:10] Which is why I'd never cause KNetworkManager to be installed automatically. [19:10] ScottK: yeah but what for the people having it installed and started by kdeinit ? [19:10] ScottK: even droping the autostart desktop file isn't enough for them [19:11] Maybe have them conflict then? [19:11] and I would bet the people reporting the plasmoid to not work properly have knetworkmanager started... [19:11] ScottK: well I suspect they should conflict, I'm not surein fact... [19:11] There's lots of hardware out there and no way it all gets tested before release. [19:11] theorically they shouldnt conflict... [19:12] ScottK: conflict means people can't have both installed at the same time.... [19:12] I worry about some corner case and someone can't install Kubuntu because the applet doesn't work for them. [19:12] I would prefer the update manager to remove it, and people beeing able to install it without any conflict with the plasmoid if needed [19:12] Tonio_: Isn't that what you said you wanted? [19:12] ScottK: well those people should better use gnome nm-applet [19:12] OK [19:13] Tonio_: Yes, but we don't want to ship that on our install media. [19:13] ScottK: our current knm isn't reported to be fully working with 0.7 and is unmaintained [19:13] Works fine here. [19:13] ScottK: hum oki [19:13] well keep it on the dvd sounds sane waiting for karmik [19:14] but remove it during the update makes sense, imho [19:14] can be considered intrusive, but imho that's an "invitation" for our users to use new components [19:14] For stuff like getting your network working I think we should be conservative and not completely remove one thing in favor of another, but deprecate one and then remove it the following release. [19:14] so many people just didn't figure out the new powerdevil applet just because they had guidance installed [19:14] Providing our default config by default is reasonable. [19:15] Yes. [19:15] guidance missing, they would have search the reason and figure out the plasmoid I suspect [19:15] especially since the release announcement mentions it [19:15] We do need to figure out how to put the battery widget in the tray for laptops. [19:15] true, and only showing for laptops.... [19:16] Yes. [19:16] ScottK: I think this cannot be done before 4.3 right ? [19:16] I think if that's missing people think they have no power manager. [19:16] Dunno. [19:16] afaik systray plasmoid support will be fully working for 4.3 not with 4.2 [19:17] Yeah, they're hashing out a new system tray spec that will make it possible for plasmoids to become systray objects [19:17] but yeah, both powerdevil and networkmanager plasma-widgets should be in the tray, not in the bar, imho [19:17] but that won't be done until 4.3 at least :( [19:17] ScottK: ho something I'd like to see fixed is a cursor bug [19:17] But in the bar is better than nothing. [19:17] ScottK: I think it is a kde upstream bug nobody figured out... [19:18] ScottK: have you seen the cursor when droping an icon in dolphin, or a mail in kmail ? [19:18] it goes back to X default cursor, which is ugly [19:18] I haven't noticed. [19:18] We have a bug for that (tm) [19:18] JontheEchidna: which ? [19:19] hmm, where did it go... [19:19] * Tonio_ JontheEchidna Mr kubuntu bugs database... [19:19] :P [19:19] :) [19:19] bug 280113 [19:19] Launchpad bug 280113 in kdebase "Ugly mouse cursor when dragging and dropping plasma widget to desktop" [Unknown,Confirmed] https://launchpad.net/bugs/280113 [19:20] JontheEchidna: I think it's upstream btw [19:20] yeah, definitely [19:20] JontheEchidna: and being there since 4.0.... [19:20] yeah :( [19:20] it's basically a bug with the cursor theme not providing an icon for one of the gazillion possible X icon codes [19:21] KNetworkManager is just in the dvd seed now, so that's good. [19:21] s/icon/cursor [19:21] ScottK: yup :) [19:21] JontheEchidna: I can't understand how can this one still be there for more than a year.... :) [19:22] yell at ruphy :P [19:22] kindly of course [19:22] in the "I"ll buy you a beverage the next time we meet" tone of voice [19:22] ;-) [19:23] JontheEchidna: it's probably a typo error on the cursor icon to use in kdelibs somewhere.... [19:23] So I've been having some odd hangs that I think are due to IO saturation. So I have iotop running. [19:23] JontheEchidna: but that's not easy to find out [19:23] Of course having iotop running so far appears to stop the problem from happening. [19:23] JontheEchidna: here is my today's mission : find this out...... [19:24] Tonio_: Yeah, the X11 cursor naming scheme is insane... [19:24] JontheEchidna: unfortunatelly.... [19:24] oh noes! I'm missing cursor 12AD2432332FEC12 [19:24] JontheEchidna: but even if I regularly fail at simple patching tasks, I used to suceed in some more complicated than this.... [19:24] JontheEchidna: I'll try to find it.... [19:24] ^.^ [19:25] Is there a schedule for KDE 4.2.2 yet? [19:25] yep I think it is planned for the second week of april... [19:25] * JontheEchidna thinks he should fix this while he's patching kdebase-workspace: bug 259181 [19:25] Launchpad bug 259181 in kdebase "KDM background image not displayed correctly on wide screen display" [Unknown,Fix released] https://launchpad.net/bugs/259181 [19:25] now that upstream committed the fix I feel more easy about it [19:26] JontheEchidna: I don't experience that bug.... [19:26] I wonder if we can squeeze it in before release or not? [19:27] Tonio_: maybe they backported the fix to the 4.2 branch? [19:27] JontheEchidna: possible... I don't know [19:27] * JontheEchidna investigates [19:28] Nope, not backported [19:41] question: did an install of the altnerate cd of alpha6 and after logging in i get no desktop display on my VM [19:41] any help? [19:42] the "background" is still the same as the login background, however i can run applications from krunner (alt+f2) [19:42] jjesse: maybe you could run konsole from krunner then try running plasma? [19:42] JontheEchidna: just type plasma? [19:42] yeah [19:43] hrmm ok, son waking up not happy brb [19:48] JontheEchidna: http://pastebin.ubuntu.com/131245 [19:49] Do you get a crash window? [19:49] + is it possible to install kdebase-workspace-dbg in the vm and get a backtrace? [19:51] JontheEchidna: hum strange that it works for me then.... maybe I'm just lucky with being 1440x900 :) [19:52] sure could try [19:52] i did not get a crash windo [19:53] how can I add gwenview addons? [19:54] Gon: the plugins ? install kipi-plugins package.... [19:54] kipi-plugins break package tree [19:55] Se instalarán los siguientes paquetes extras: [19:55] kooka libkdcraw3 libkexiv2-3 libkipi-common libkipi0 libkscan1 libmpg123-0 mpg123 ocrad [19:55] Gon: how? [19:55] Los siguientes paquetes se ELIMINARÁN: [19:55] gwenview kdeplasma-addons libkexiv2-7 libkipi6 [19:55] oh, kde3 [19:55] no... I using 8.10 [19:55] Gon: you're using intrepid right ? [19:55] KDE 4.2.1 [19:56] I'm using Intrepid [19:56] :B [19:56] Gon: you should use digikam-experimental repository [19:56] Gon: it has KDE4 version of kipi-plugins [19:56] ok, [19:56] Gon: well known problem of intrepid, most jaunty complementary packages are missing.... [19:56] D: [19:56] Gon: also you can wait a little bit and get jaunty, or even get jaunty now.... it'll work a lot better anyway.. [19:56] Gon: https://edge.launchpad.net/~digikam-experimental/+archive/ppa [19:57] thanks, I will try this ... [19:57] Gon: but I agree with Tonio_, Jaunty is so near Beta that you may want to consider [19:57] Lure_: I'm conconered about how fucked up will be people computer after going from intrepid + 10 ppas to jaunty...... [19:57] concerned [19:58] Tonio_: should not be an issue if these packages are just backports with proper version numbers [19:58] Tonio_: but I agree it is hard to control [19:58] Lure_: fortunatelly, this situation where 50% of the packages are for kde3 and 50% for kde4 will not affect any release after jaunty [19:58] but intrepid got so many people in front of so many problems.... [19:59] I know jaunty will be a good release of kubuntu, but how many people did we lost in the process ? ;) [19:59] hard to say, but if I were a standard kubuntu user, I would have gone for sure... [19:59] we should have never officially released intrepid.... really [20:00] just publish isos with a hudge warning would have been a lot bettern and professionnal [20:00] s/bettern/better [20:01] Lure_: as a user I would prefer to read "better stay with kde3 for now and let us time to properly integrate it", than "you can go" and experience 30 bugs a day.... [20:01] really I'm not happy when I see the result.... [20:02] * ScottK thought Intrepid was a little rough, but we warned people OK. [20:02] thanks ;D I'm installing now... [20:02] ScottK: well... we warned, but afaics, not enough.... [20:02] Plus the digikam issue was caused by official backports [20:03] ScottK: not offically releasing would have been more clear imho :) [20:03] In the next beta release i going to upgrade to JJ [20:03] We ought to backport digikam then. [20:03] ScottK: so many people at work (not all geeks) got bored without even understanding it was not finished work... [20:03] ScottK: final release is this weekend, so we can backport that version next week [20:04] ScottK: that's not your fault or mine anyway, no one to blame :) [20:04] Excellent. [20:04] I just hope in the future, we would have the courage to take such a hard decision, and publically announce that for sanity, we are discarding a release, officially [20:04] * ScottK likes it better than Hardy with totally broken X integration. [20:04] * Lure_ needs to merge with debian tommorow [20:05] and we are just publishing isos so that "intrepid" users can test and help [20:05] ScottK: bah hardy works at least... [20:05] but yeah, xorg is better with intrepid (maybe the only better thing) [20:05] intrepid's not that bad, it works [20:05] aside from bluetooth and translations [20:05] JontheEchidna: I'm rude with intrepid, true that, but well.... just my opinion :) [20:06] I encounter limitations, not broken stuff [20:06] bluetooth and translations aside... [20:06] * apachelogger is wondering if topic is intrepid miscommunication all day long, ever day [20:06] apachelogger: yeah, I should stop with this, you're right.... [20:06] *nod* :P [20:06] \o apachelogger [20:07] apachelogger: I just have the feeling that most people consider "not that a big deal.... just little issue" [20:07] apachelogger: and if for any reason the same situation happens, we would do the same error :) [20:07] apachelogger: experience gaining is fine [20:07] there is a 90% chance that we will [20:07] or rather they [20:07] * Tonio_ stops now for real [20:07] Tonio_: fwiw, i didnt use intrepid even as a gnome user [20:08] maco: that's another story, but yeah, I agree too :) [20:08] if this happens again, we will most likely work on another project or have dropped out of floss [20:08] Actually most of the Intrepid problems I have are kernel related. [20:09] apachelogger: I can see ubuntu reputation going down for a moment especially because of this kind of errors... [20:09] ScottK: which is why i didnt use it. [20:09] talking about kernel ... for some reason the .28 is causing ubernice performance issues with 3d stuff here [20:09] the .27-rt one works fine [20:09] apachelogger: those are so simple to avoid.... 10 lines on a web page can avoid it.... so stupid.... [20:09] it's like when at work we are forced to release something not ready, because the client expects.... [20:09] we were not forced [20:09] we released it [20:10] it's so much better to place a phone call, be honnest and announce there is delay.... [20:10] because it was a good product [20:10] Tonio_: kdebase-workspace built in my PPA, so I pushed the revisions to bzr [20:10] translations and bluetooh aside [20:10] JontheEchidna: great, thanks :) [20:10] :) [20:10] apachelogger: let's end once and for all :) I promiss.... [20:10] * apachelogger hopes so :P [20:11] wow so what's this big discussion about? is jaunty realy that bad? [20:11] +1 === claydoh_ is now known as claydoh [20:11] by the way, anyone noticing that suspending in kubuntu sometimes works out fine and sometimes results in resuming at kdm instead of on the desktop where you suspended? [20:11] jjesse: intrepid [20:12] The worst thing in jaunty (for me) is the ext4 crashes @_@ [20:12] jjesse: btw your crash has a good chance at being fixed next kdebsae-workspace upload [20:12] so intrepid is the problem? [20:12] jjesse: unfortunately I think plasma restarts itself with the --nocrashhander flag after it has crashed, which is stupid and dumb [20:12] * ScottK notes ext4 and KDE or Gnome aren't a recpie for reliability. [20:12] that is [20:13] maco: not in jaunty anyway [20:14] might be X/driver related though ... i.e. X is going down and kdm restarts it leaving you at the login screen [20:15] right...thats what im thinking [20:15] I have been having X restarts when switching users lately [20:15] Tis annoying [20:15] weird though. before it only happend if i had Kwin compositing and UXA enabled [20:15] i have UXA disabled and compositing disabled, and it's still happening [20:15] (like, before, if i turned off compositing before suspend, it wouldn't crash) [20:18] JontheEchidna: with the dbg packaged installed tried plasma again pastebin.ubuntu.com/131264 [20:18] jjesse: unforunately the dbg packages only help with backtraces :( [20:18] ah ok [20:19] when will the new package be able to be installed? [20:19] the new kdebase-workspace? [20:19] Tonio_ is sponsoring it right now I think, then it may take an hour or two from there [20:20] JontheEchidna: let's go for upload :) [20:20] :) [20:25] Apport crash detection gets turned off for final releases, yeah? [20:25] JontheEchidna: uploaded [20:25] (I know it still does dpkg failure detection) [20:25] Tonio_: Great [20:27] JontheEchidna: yes, believe so [20:27] * JontheEchidna is just wondering how bad it will be if bug 317712 and bug 317271 don't get fixed before final release [20:28] Launchpad bug 317712 in kdebase "nepomukservicestub crashed with SIGSEGV in QThread::isRunning()" [Unknown,Confirmed] https://launchpad.net/bugs/317712 [20:28] Launchpad bug 317271 in redland "nepomukservicestub causes crash in Soprano::Redland backend" [High,Triaged] https://launchpad.net/bugs/317271 [20:28] each have like 50 dupes [20:28] but it only crashes a little-used background daemon so it shouldn't really have any negative affects [20:28] JontheEchidna: 317712 still affects you? [20:29] I dunno. I turned off apport ages ago :P [20:29] lol, maybe thats why I dont recive crash reports :D [20:29] but we're still getting tons of reports for 317271 [20:30] I think fsrunner should be instaled by default, the strigi + nepomuk doesnt work for me :/ [20:30] what's fsrunner? I think I saw that in my kde-look feed but I never investigated [20:31] JontheEchidna: It's an addon for KRunner that indexes the files from the directories you set up and you can access indexed files using krunner [20:32] cool, it's like nepomuk + strigi but without the redland fail [20:32] yup [20:32] or sesame-"I loves me some java" fail [20:32] Want to try it? [20:32] or virtuoso "my backend is KDE 4.3 material" fail [20:33] i havent seen a nepomuk crash on login in at least 3 weeks [20:33] maco: do you have apport turned on? :D [20:33] yes [20:33] I turned off apport back in Intrepid when it started superseeding the KDE crash handler [20:34] well, i didnt explicitly turnit off [20:34] JontheEchidna: it crashes here every 2nd login or so [20:34] though i havent seen any crashes in about 3 weeks, and i find that surprising [20:34] ...something must be wrong with apport. it hasn't reported any of my daily kernel panics [20:34] and kbluetooth4 crashes on resume :-( [20:35] I'm unable to send files to my mobile with kbluetooth so I'm not using it :< [20:35] but due to apport bug it gets marked invalid, so no bug opened [20:35] Lure_: Oh well, since it doesn't have any adverse affects (nepomuk already refuses to use the redland backend) as long as apport is turned off for final release it won't be too huge of an embarrasment [20:35] Lure_: I saved one of the apport bugs from invalidation [20:35] JontheEchidna: agreed [20:36] Lure_: do you think you could get a good backtrace for the resume bug? [20:36] it'd be nice if we could forward it [20:36] JontheEchidna: we do not have -dbg packages, right? [20:37] meh, you're right [20:37] I wonder if the dbgsym repo has ddebs [20:37] JontheEchidna: see bug 341358 [20:37] Launchpad bug 341358 in apport "crash report rejected due to wrong dependancy assumptions" [Undecided,New] https://launchpad.net/bugs/341358 [20:40] http://ddebs.ubuntu.com/pool/main/k/kdebluetooth/ [20:40] ^dbgsym packages [20:41] JontheEchidna: no amd64?! [20:41] damn [20:41] oh: http://ddebs.ubuntu.com/pool/main/k/kdebluetooth/kdebluetooth-dbgsym_0.3-0ubuntu0.2_amd64.ddeb [20:42] that might be it, just wrong version [20:42] hmm, that might be intrepid-updates [20:42] will try [21:15]