[00:27] <xclaesse[m]> Hi, I'm testing Ubuntu 22.04, one issue I have is my wired networkd device does not appear. Wifi works fine. Is that a known issue? Any workaround possible?
[00:29] <sarnold> xclaesse[m]: this channel is more for development; #ubuntu-next will have more folks familiar with common support needs
[00:29] <sarnold> xclaesse[m]: some kernel modules are commonly stuffed into an 'extra' package
[00:30] <sarnold> xclaesse[m]: it might be worth blindly installing that package, reboot, and see if things get happy
[00:30] <sarnold> apt-cache search linux module extra    might help figure out hte name, I don't know it off-hand
[00:31] <xclaesse[m]> It is installed: linux-modules-extra-5.15.0-23-generic
[00:32] <xclaesse[m]> Thanks for pointing to the other chan, I'll repost :)
[00:35] <sarnold> dang, I hoped for an easy win :)
[05:53] <jibel> Good morning
[05:53] <oSoMoN> good morning desktoppers
[05:55] <duflu> Hi jibel and oSoMoN
[05:56] <oSoMoN> hey duflu
[06:07] <jibel> duflu, is bug 1967901 the only report you saw with qxl ?
[06:07] <jibel> if so it's surprising because on my machine qxl is the default
[06:09] <duflu> jibel, I linked to two other QXL bugs in yours, but they sound different
[06:17] <duflu> jibel, best I can tell the QXL Xorg driver found the qxl kernel driver, loaded, found it was incompatible and then unloaded
[06:47] <didrocks> good morning
[06:48] <jibel> salut didrocks
[06:53] <didrocks> salut jibel
[07:15] <tjaalton> checking for qxl_drm.h... no
[07:16] <tjaalton> I think that's why qxl fails
[07:20] <tjaalton> it is detected on debian
[07:20] <tjaalton>         KMS:                      no
[07:20] <tjaalton> so yeah, I'll pull a patch from fedora to fix that..
[07:24] <seb128> goood morning desktopers
[07:24] <seb128> hey tjaalton, how are you?
[07:24] <tjaalton> hi, fine thanks
[07:25] <seb128> tjaalton, do you plan to land the libx11 update before release? or if not should we try to cherrypick some fixes?
[07:25] <tjaalton> seb128: that was the goal yes
[07:25] <tjaalton> there was some regression in 1.7.4 that got quickly fixed and released as 1.7.5
[07:26] <tjaalton> haven't seen any reports on debian since uploading it on sunday, so I guess we're good
[07:26] <seb128> time for a sync then? ;)
[07:26] <tjaalton> yup
[07:27] <tjaalton> 1.7.3 actually fixed some firefox crashers, but there were some regressions that I was waiting for those to get fixed before attempting to bring it in
[07:28] <tjaalton> synced
[07:28] <seb128> let's hope 1.7.5 is in shape then
[07:28] <seb128> thanks :)
[07:28] <tjaalton> uploaded a new xkeyboard-config yesterday
[07:28] <tjaalton> to sid
[07:28] <tjaalton> let's wait for a few days for that
[07:29] <tjaalton> and uploaded some updates for intel opencl stack to experimental, will sync those once they're ready
[07:29] <tjaalton> those are purely universe stuff
[07:32] <tjaalton> also asked the new wacom maintainer to bump the epoch so we could sync the driver, but he's going by the book and requires to open a thread on debian-devel about ...
[07:32] <tjaalton> +it
[07:32] <seb128> :-/
[07:33] <tjaalton> maybe I'll just fakesync it for jammy
[07:34] <seb128> tjaalton, and the mesa/webkit/wayland issue, I did bisect and commented on https://gitlab.freedesktop.org/mesa/mesa/-/issues/6236 , do you have anyone you can try to nag about it?
[07:34] <tjaalton> I noticed
[07:35] <tjaalton> not sure where to poked, though I did add a comment to the original MR
[07:35] <tjaalton> *poke
[07:35] <didrocks> salut seb128, tjaalton
[07:35] <tjaalton> yo
[07:36] <seb128> thx
[07:36] <seb128> didrocks, lut, en forme ?
[07:36] <didrocks> ça va, debug de stacktrace de bon matin, et toi ?
[07:36] <seb128> ça va :)
[08:09] <oSoMoN> salut didrocks, jibel, seb128
[08:27] <seb128> oSoMoN, salut, en forme ?
[08:28] <oSoMoN> seb128, ça va, et toi?
[08:29] <seb128> oSoMoN, ça va !
[08:58] <KGB-2> xdg-desktop-portal-gnome Sebastien Bacher 304097 * commented merge request !2 * https://deb.li/71eE
[09:24] <oSoMoN> Trevinho, I identified the mutter commit that caused the dnd regression in the firefox snap (bug #1964541), I could use some help to figure out exactly why this is causing the regression, and if it's a bug in mutter or something that needs patching in firefox
[09:52] <oSoMoN> Trevinho, note that in the corresponding merge request, I see a comment (https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2122#note_1325253) that makes me think the problem might be with mutter: « I agree this is a less trigger-happy variant than that, at the expense of false negatives. »
[09:53] <jamesh> Wimpy: I was looking into the auto-connect problems for your Ubuntu Mate snap theme here: https://github.com/snapcore/snapd-desktop-integration/issues/10 -- from the look of it, the snap needs a store assertion to enable auto-connection/greedy plugs
[09:53] <Wimpy> jamesh: o/
[09:54] <Wimpy> jamesh: Is "greedy plugs" what I should be requesting?
[09:54] <jamesh> Wimpy: the usual process for this is  to request the assertion on the forum. You could use https://forum.snapcraft.io/t/auto-connect-and-greedy-plug-behaviour-for-for-gtk-common-themes-and-gtk-theme-traditionalhumanized-snaps/19113?u=jamesh as a template for what to request.
[09:55] <jamesh> Wimpy: we still don't really have solid policy or automatic review for theme snaps, but you seem like a trustworthy fellow
[09:55] <jamesh> :-)
[09:55] <Wimpy> jamesh: Thank for the info. I'll get on that.
[09:55] <Wimpy> fossfreedom: See above. You'll need to do the same for your theme snaps.
[09:57] <fossfreedom> Umm... OK. Feel like a bit of copy paste discourse posting
[09:58] <jamesh> Wimpy: we don't do any manual plug connection when installing the theme snaps, since (a) that bypasses the store's policy, and (b) wouldn't help when you install new app snaps.
[09:59] <jamesh> once the store assertion is available, it should all just work automatically
[10:06] <cnihelton> Hi, everyone!
[10:09] <oSoMoN> hey cnihelton
[10:16] <Wimpy> jamesh: Any changes required to snapcraft.yaml to support this?
[10:16] <ack> hi, any hints on how I could debug this issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967727 ? It's pretty annoying as it randomly happens while working
[10:17] <jamesh> Wimpy: If your theme snap works when you manually connect it to app snaps, then you shouldn't require any more changes
[10:19] <Wimpy> jamesh: OK, manual connection works.
[10:19] <Wimpy> Anything need requesting for the icon snaps?
[10:20] <jamesh> You'd need a similar snap declaration for the icon snaps
[10:20] <Wimpy> Thanks.
[10:20] <Trevinho> oSoMoN: interesting... Let me see
[10:21] <jamesh> I don't have a specific example of what to request, but it should be fairly obvious from the GTK theme version
[10:23] <Trevinho> oSoMoN: specifically is the 2nd or 1st commit of the MR?
[10:24] <Wimpy> jamesh: Thank for your help. I'm writing the post now...
[10:24] <oSoMoN> Trevinho, https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2122/diffs?commit_id=26676a829e74859488154cd8c45de1d0b629f3ca
[10:25] <oSoMoN> Trevinho, specifically, the changes to src/core/events.c
[10:25] <oSoMoN> (I locally distro-patched mutter to revert these changes (the second hunk), and the issue was gone)
[10:26] <jamesh> Wimpy: awesome! It'll be great to have this ready on the LTS.
[10:27] <Trevinho> oSoMoN: I see, do we have a tinier reproducer than Firefox? As it would be nice to figure out what the app is doing too
[10:28] <oSoMoN> Trevinho, not much smaller, but I observed that dragging selected text in the gedit snap also doesn't work
[10:29] <Trevinho> Oh indeed helps though
[10:29] <oSoMoN> gotta reboot to test downgrading a package, back in a moment
[10:29] <fossfreedom> jamesh: I am a little confused... I am looking at the gtk-common-themes snapcraft.yaml on gnome gitlab and I can't see the allow-auto-connection bits ... I want to make sure I have added that correctly for our two snaps I.e. https://github.com/UbuntuBudgie/gtk-theme-pocillo-snap/blob/main/snap/snapcraft.yaml
[10:30] <Trevinho> oSoMoN: will try in a bit, my biggest problem was to get the snaps working in my dev environment
[10:30] <jamesh> fossfreedom: it's not part of the snapcraft.yaml. You're essentially requesting a special permission from the store, similar to if you wanted your snap to auto-connect to cameras or microphones
[10:31] <jamesh> fossfreedom: in this case, it is permission to have your snap's content shared with snaps asking for gtk-3-themes, icon-themes, etc.
[10:31] <fossfreedom> Ah. OK reverting. And will kind of copy paste your discourse post. Thx.
[10:33] <Wimpy> jamesh: Here's my request. I think it is correct.
[10:33] <Wimpy> https://forum.snapcraft.io/t/auto-connect-and-greedy-plug-behaviour-for-gtk-theme-yaru-mate-and-icon-theme-yaru-mate/29443
[10:33] <Wimpy> fossfreedom: Some bioler plate for you :-) ^
[10:34] <fossfreedom> Cheers :)
[10:34] <jamesh> fossfreedom: in short, there a policy file describing how plugs/slots can be connected, which can be seen by running "snap debug base-declaration"
[10:35] <jamesh> fossfreedom: the store can deliver per-snap overrides for that policy as part of a snap-declaration assertion
[10:37] <Trevinho> oSoMoN: will try to play more with it in a bit, my biggest problem was to get the snaps working in my dev environment
[10:55] <bittin> good afternoon
[11:03] <oSoMoN> good afternoon bittin
[12:08] <jbicha> good morning
[12:54] <bdrung> hi, i'll try to fix https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/comments/68 and figured out that there is a discrepancy between the org.gnome.desktop.input-sources sources setting and the gnome keyboard applet. can someone assist there?
[13:31] <KGB-2> gnome-control-center ubuntu/master a759b86 Sebastien Bacher debian/patches/ubuntu/Allow-tweaking-some-settings-for-Ubuntu-Dock.patch * Use the correct gettext function in the ubuntu panel for context strings * https://deb.li/31ngI
[13:32] <oSoMoN> good morning jbicha
[14:03] <Trevinho> oSoMoN: while i noticed that gedit dnd is indeed broken it seems to be broken also on unconfined gedit under wayland, isn't it?
[14:05] <oSoMoN> let me check
[14:06] <oSoMoN> Trevinho, not here. dnd of text selection works for /usr/bin/gedit, it doesn't for /snap/bin/gedit
[14:09] <Trevinho> oSoMoN: ok it was consistent for me, but yeah, indeed that line is the gulty one... let me see if I can get the root cause
[14:11] <oSoMoN> cool, thanks for your help on this!
[14:12] <Trevinho> the only thing is that when the app is not confined... if I disable that check. then I get an "hanging dialog"
[14:14] <oSoMoN> right, my "patch" is probably not the right solution, merely a way to point out where the problem originated
[14:14] <Trevinho> sure sure
[14:27] <Trevinho> oSoMoN: lovely... normal gedit running in gdb is not affected, while running outside gdb is....
[14:27] <oSoMoN> that's clearly a timing issue
[14:37] <Trevinho> oSoMoN: yeah, so it seems
[14:43] <Trevinho> oSoMoN: something like this  seems enough, but still would like to get closer to the root cause... as also drag events should keep the window "alive"...
[14:43] <Trevinho> https://www.irccloud.com/pastebin/4mj5YCu4/mutter.diff
[14:46] <Trevinho> oSoMoN: I've the same issue also on unconfined apps in my jhbuild environment though.. just as simple as dnd on nautilus folders...
[14:49] <seb128> Trevinho, hey, do you need sponsoring for the portal update? I don't think you replied to my msg earlier?
[14:50] <Trevinho> seb128: I saw your comment on the MR, but no questions, was it? :D
[14:50] <Trevinho> seb128: however, yeah please if you can handle that?
[14:50] <Trevinho> given I couldn't upload it would need some external intervention anywahs
[14:50] <Trevinho> anyways*
[14:51] <Trevinho> speaking of it, who should I ping to get those components under the desktop umbrella?
[14:51] <seb128> bdrung, unsure if someone replied but maybe GunnarHj would know about bug #1875062 and input-sources
[14:52] <seb128> Trevinho, it's a DMB thing which I'm on now so I will figure that out, I also mentioned that in the query earlier when I asked about sponsoring :p
[14:52] <bdrung> seb128, thanks. I haven't got a reply get.
[14:57] <jbicha> seb128: could you look into getting the upload permission packagesets before the jammy release? as a test case, gnome-screenshot should switch to the ubuntu-budgie packageset
[14:57] <seb128> jbicha, do you have any guidance on how the refresh is done? like how did you figure out where screenshot would go?
[14:59] <jbicha> I never directly managed the packagesets when I did a term years ago on the DMB but you can try https://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase#Packagesets
[14:59] <KGB-2> xdg-desktop-portal-gnome pipeline Sebastien Bacher 366211 * running (extract-source: running; piuparts: created; blhc: created; autopkgtest: created; lintian: created; reprotest: created; test-crossbuild-arm64: created; test-build-all: created; test-build-any: created; build source: created; build i386: created; build: created)
[14:59] <jbicha> seeded-in-ubuntu gnome-screenshot    says only Ubuntu Budgie ships it now
[15:00] <seb128> jbicha, but it's in universe so does it need to be in a set?
[15:00] <seb128> or is anything on a flavor added to the corresponding set?
[15:01] <seb128> I should start by reading that page before asking more questions right?
[15:01] <jbicha> yes, because David is not a MOTU yet :)
[15:01] <seb128> he should :p
[15:01] <jbicha> fossfreedom: ^
[15:04] <KGB-2> xdg-desktop-portal-gnome signed tags 062ef55 Sebastien Bacher ubuntu/42.0.1-1ubuntu2 * xdg-desktop-portal-gnome Debian release 42.0.1-1ubuntu2 * https://deb.li/XzO2
[15:05] <KGB-2> xdg-desktop-portal-gnome ubuntu/master 2ad7fc6 Sebastien Bacher debian/changelog * upload to Ubuntu * https://deb.li/iknmC
[15:05] <KGB-0> xdg-desktop-portal-gnome pipeline Sebastien Bacher 366213 * pending (blhc: created; autopkgtest: created; lintian: created; reprotest: created; test-crossbuild-arm64: created; test-build-all: created; test-build-any: created; build source: created; build i386: created; extract-source: pending; piuparts: created; build: created)
[15:05] <KGB-0> xdg-desktop-portal-gnome pipeline Sebastien Bacher 366213 * running (extract-source: running; blhc: created; autopkgtest: created; lintian: created; reprotest: created; test-crossbuild-arm64: created; test-build-all: created; test-build-any: created; build source: created; build i386: created; piuparts: created; build: created)
[15:05] <seb128> Trevinho, ^
[15:05] <GunnarHj> bdrung: I saw your comments and your ongoing investigation sounds really interesting to me. Sounds like we will soon be able to address the root cause of that long standing issue.
[15:06] <Trevinho> seb128: lovely, thanks!
[15:06] <GunnarHj> bdrung: As regards your question, I'm not sure I'm qualified to help, but bug #1956916 comes to mind.
[15:06] <seb128> GunnarHj, hey, the ubiquity changes got merged and uploaded :-) also I fixed the gcc translation issue
[15:07] <GunnarHj> seb128: Great, you have earned a gold star. :)
[15:07] <Trevinho> oSoMoN: AH! I think I found where we're stopping the drag to happen...
[15:10] <GunnarHj> bdrung: What I mean is that there are issues where gnome-shell and XKB don't play well together. May or may not be relevant.
[15:37] <bdrung> GunnarHj, if this problem is related to wayland, I can test if it can be reproduced on X11.
[15:39] <GunnarHj> bdrung: Yes, knowing that might be useful.
[15:40] <GunnarHj> bdrung: Btw, let's continue our conversation on the bug report.
[15:41] <bdrung> the login screen of the ubuntu live image does not provide a way to change to X11. do i need to install some package for it?
[15:42] <bdrung> GunnarHj, i would prefer to continue the conversation here and only put stuff in the ticket that is relevant (to avoid clutter the ticket with noise)
[15:53] <Trevinho> oSoMoN: ok this seems likely the proper solution.. .even though the serial isn't changing on drags, so could be avoided at times... but still. More to come in a GNOME Issue
[15:53] <Trevinho> https://www.irccloud.com/pastebin/qdw2DfCJ/foo.diff
[15:54] <oSoMoN> great!
[15:54] <Trevinho> would probably nice to understand who is calling back meta_display_pong_for_serial on the snap implementation to `meta_display_pong_for_serial` but...
[15:55] <Trevinho> oSoMoN: give a check if that works there too please :)
[15:55] <oSoMoN> Trevinho, will do in a moment
[15:56] <Trevinho> upstream would probably need more cleanups (like wrapping stuff up more, but that's the point imho)
[15:58] <GunnarHj> bdrung: Ok, that works too. :)
[16:00] <bdrung> GunnarHj, something really fishy is going on. i tried the live system without my gsetting patch. now "gsettings get org.gnome.desktop.input-sources sources" returns "[('xkb', 'us'), ('xkb', 'au'), ('xkb', 'cm'), ('xkb', 'gb')]".
[16:05] <oSoMoN> Trevinho, I applied your patch instead of mine and rebuilt mutter packages here, installed locally and this appears to fix the bug as intended, at least dragging tabs in the firefox snap works. Good job!
[16:05] <oSoMoN> ship it!
[16:06] <Trevinho> ehe, well upstream work will be slower :)
[16:10] <GunnarHj> bdrung: Yeah, that's odd, but please note that the bug isn't really about the live session, but about the behavior in the installer. You wouldn't see all those input sources at first login if you completed the installation, so investigating details in the live session may be a dead end.
[16:23] <bdrung> GunnarHj, i have to revise my last comment in the bug report. "gsettings set org.gnome.desktop.input-sources sources" is called once. but the result is still the same: the gnome keyboard applet in the live session does not show the new entries.
[16:23] <bdrung> btw, is "gsettings set org.gnome.desktop.input-sources sources" the correct way to change the keyboard layout?
[16:32] <GunnarHj> bdrung: That's equivalent to manipulating the list of input sources in Settings. But I think it changes the effective input source only if the command means that the previously effective input source is removed through the command.
[16:34] <GunnarHj> bdrung: So, yes, you shouldn't expect that only *adding* an entry changes the effective layout.
[16:54] <bdrung> GunnarHj, it is probably not required for the installer to change the layout. the layout should just be added to the list and gnome should notice the keyboard layout change done via setxkbmap
[16:57] <GunnarHj> bdrung: But using setxkbmap is not sufficient to make GNOME recognize the layout.
[16:57] <bdrung> GunnarHj, what needs to be done to make GNOME recognise the layout?
[16:58] <bdrung> "gsettings set org.gnome.desktop.input-sources sources" followed by setxkbmap?
[16:58] <GunnarHj> bdrung: Consider this example, assuming this list to start with:
[16:58] <GunnarHj> $ gsettings get org.gnome.desktop.input-sources sources
[16:58] <GunnarHj> [('xkb', 'de'), ('xkb', 'se'), ('xkb', 'us')]
[16:58] <GunnarHj> And the effective layout, i.e. the layout shown in the input source indicator, is "de". Then if I do:
[16:58] <GunnarHj> $ gsettings set org.gnome.desktop.input-sources sources "[('xkb', 'se'), ('xkb', 'us')]"
[16:58] <GunnarHj> the effective layout is instantly changed to Swedish. But the reason for that is that I effectively removed the German layout.
[17:01] <GunnarHj> bdrung: Now a stupid question: Is ubiquity really working in a GNOME DE environment?
[17:03] <bdrung> I am using the jammy-desktop-amd64.iso for testing - this is a GNOME live system. is there a command to shows the session details?
[17:05] <GunnarHj> bdrung: The live session is indeed GNOME, but I'm talking about the installer itself. Assume that you click "Install Ubuntu" at the welcome screen and never enter a live session. Which kind of environment are you in then?
[17:05] <bdrung> GunnarHj, how about a video call? then I can show it to you hands on.
[17:05] <bdrung> GunnarHj, all my tests are done in the GNOME session by clicking "Try Ubuntu".
[17:08] <GunnarHj> bdrung: And I'm not confident that the live session is representative for the environment used for the installation phase. But I'm not sure; I'm not really familiar with the ubiquity code.
[17:09] <GunnarHj> bdrung: Sure, a video call may help.
[17:14] <KGB-2> gnome-nettool upstream/latest fb75227 Jeremy Bicha * pushed 273 commits (first 5 follow) * https://deb.li/iWwMl
[17:14] <KGB-2> gnome-nettool upstream/latest 38eb075 Daniel Korostil po/uk.po * Update Ukrainian translation * https://deb.li/iM4I
[17:14] <KGB-2> gnome-nettool upstream/latest dce0cc3 Yuri Chornoivan help/uk/uk.po * Update Ukrainian translation * https://deb.li/3QDzA
[17:14] <KGB-2> gnome-nettool upstream/latest 314526f AsciiWolf pixmaps/icons/scalable/apps/gnome-nettool.svg * Fix scalable icon * https://deb.li/3VIs0
[17:15] <KGB-2> gnome-nettool upstream/latest d54dd27 Germán Poo-Caamaño pixmaps/icons/scalable/apps/gnome-nettool.svg * Merge branch 'icon-fix' into 'master' * https://deb.li/DJjz
[17:15] <KGB-2> gnome-nettool upstream/latest 730fada Jwtiyar Nariman po/ LINGUAS ckb.po * Add Central Kurdish translation * https://deb.li/3Ruvs
[17:15] <KGB-2> gnome-nettool pristine-tar 7fa463e Jeremy Bicha gnome-nettool_42.0.orig.tar.xz.delta gnome-nettool_42.0.orig.tar.xz.id * pristine-tar data for gnome-nettool_42.0.orig.tar.xz * https://deb.li/T8Rv
[17:15] <bdrung> GunnarHj, I sent you a PM for the video call.
[17:31] <Trevinho> oSoMoN: so... apparently, it would needed to bump gtk in the firefox snap... or well, fix the issue in gtk for 20.04... quite annoying, so for now I suppose we'll bring that patch in the distro only
[17:33] <oSoMoN> Trevinho, ack, I saw your comment
[17:33] <oSoMoN> we'll need a fix in time for 22.04, as the issue is very visible with the firefox snap
[17:34] <Trevinho> yeah, I'll defintely include something in mutter, but meanwhile please get the platform snap ready for that too
[17:34] <oSoMoN> so a mutter distro-patch for 22.04 sounds like the easiest and quickest solution for now, and then backport that gtk fix to 20.04 and have it included in the gnome platform snap
[17:34] <Trevinho> yeah, fair enough
[17:36] <Trevinho> also I had a local libgdk version that was older than that... due why i was affected in my jhbuild... Which was lucky :)
[18:14] <seb128> Trevinho, oSoMoN, the platform snaps builds gtk from source and doesn't use the focal deb
[18:15] <oSoMoN> ah, that makes it easier to cherry-pick a patch, that's good news
[18:15] <seb128> yes, it's easy to get one in stable before release I think
[20:04] <KGB-2> libadwaita signed tags bb19d92 Jeremy Bicha ubuntu/1.1.0-1ubuntu2 * libadwaita-1 Debian release 1.1.0-1ubuntu2 * https://deb.li/3Z7ZM
[20:04] <KGB-2> libadwaita pipeline Jeremy Bicha 366301 * running (extract-source: running; piuparts: created; blhc: created; autopkgtest: created; lintian: created; reprotest: created; test-crossbuild-arm64: created; test-build-all: created; test-build-any: created; build source: created; build i386: created; build: created)
[20:20] <KGB-0> libadwaita pipeline Jeremy Bicha 366301 * [15 minutes and 14 seconds] failed (piuparts: success; reprotest: failed; autopkgtest: success; test-build-any: success; test-build-all: success; lintian: failed; test-crossbuild-arm64: failed; blhc: success; build i386: success; build: success; build source: success; extract-source: success)


[00:33] <shtylman> Riddell: one can never be to sure...
[00:33] <shtylman> *too
[01:02] <freeflying> apachelogger: it dosen't now, but utf8 would be nicer
[01:02] <apachelogger> freeflying: see what riddell wrote, it uses what the system uses, which is utf8 by default
[01:03] <apachelogger> I have yet to see a kubuntu instalaltion where that is not the case, and eitherway not anything that can be controlled by konsole but must be done at a much lower level than KDE
[01:06] <ejat> is there a karmic backport for choqok ? for 0.9.4 ?
[01:09] <ejat> http://paste.ubuntu.com/364238/ <-- any idea why this happend?
[01:28] <jjesse> interesting on my lucid fully updated vm plasma-desktop doesn't start up, anyone else having problems like that?
[01:38] <ryanakca> Thanks JontheEchidna
[01:38] <JontheEchidna> no prob
[01:40] <Lex79> JontheEchidna: my kmail crashes when I delete all your email...please stop to do bug stuff in launchpad :P
[01:41] <Lex79> hihih
[01:41] <JontheEchidna> :P
[01:48] <jjesse> ran an update on my lucid vm, now getting apport notifications upon login for zz-plasma-remove-network-manager.py, update notifier, printer-applet, and apport-kde
[01:48] <nixternal> yeah, me too...just zz-plasma and printer-applet now
[01:48] <jjesse> are these known  ?
[01:48] <jjesse> as in should i report the bugs?
[01:51] <JontheEchidna> nah, just skew due to the new python0kde4, should resolve itself in a while
[01:51] <jjesse> is that causing plasma-desktop not to start as well?  or is that another issue?
[01:51] <JontheEchidna> that'd be a separate issue
[01:52] <jjesse> acutally i think plasma-desktop is running, just no plasmoids or anything
[02:02] <jjesse> hrmm remvoed my config folder and my desktop started up correctly
[02:11] <ejat> guys .. any idea about this -> http://paste.ubuntu.com/364238/
[02:12] <jjesse> with the change to yahoo as the default search engine will the default search engine in konqueror swtich to yahoo as well?
[02:41] <JontheEchidna> Riddell: packagekit seems to fail. This patch seems to get it to build, but I didn't check the list-missing: http://pastebin.com/f13c66405
[02:44] <dhillon-v10> hi all, can anyone explain why konqueror wouldn't type a specific single character '(' in the youtube search box, is it supposed to be a security measure or is it just a simple bug, I suppose its the latter
[02:53] <shtylman> dhillon-v10: sounds like a bug? ... I can't imagine its on purpose...
[03:09] <dhillon-v10> shtylman: I figured as much, there's really no reason to block '(' on a social website
[09:21] <agateau> Riddell: I need ninja help!
[09:21] <agateau> I packaged my Colibri notification system: https://launchpad.net/~agateau/+archive/ppa/+packages
[09:21] <agateau> but there is a tricky part:
[09:22] <agateau> it needs to install a d-bus service file in /usr/share/dbus-1/services
[09:22] <agateau> and this file is also installed by notification-daemon and notify-osd
[09:22] <agateau> notify-osd diverts the file, but it seems the diversion system does not support more than one diversion
[09:24] <ejat> Riddell: can the choqok be backport to karmic ?
[09:27] <shadeslayer_> ejat: i already did it :)
[09:27] <ejat> shadeslayer_: in ya ppa?
[09:27] <shadeslayer_> ejat: check out my PPA at ~rohangarg
[09:27] <ejat> shadeslayer_: thanks ..
[09:28] <shadeslayer_> ejat: no problem,ive also backported rekonq and kopete-facebook
[09:28] <ejat> shadeslayer_: c00l ..
[09:28] <shadeslayer_> ejat: :)
[09:30] <ejat> shadeslayer_: i mean 0.9.4+git20091230-1
[10:11] <apachelogger> agateau: thou shalt not use cdbs :P
[10:11] <agateau> apachelogger: oh, why?
[10:11] <agateau> isn't it used in all kde packages?
[10:11] <apachelogger> dh 7 is superior and the latest hype :)
[10:11]  * agateau is not up to the latest hype :/
[10:12] <Riddell> you can use cdbs if you like!
[10:12] <agateau> ah... a ninja fight!
[10:12] <agateau> let's see who wins
[10:12]  * agateau grabs popcorn
[10:14] <Riddell> I mean dh 7 is more in with the kids but there's a very good argument for saying "I have no desire to learn yet another .deb build system"
[10:14] <Riddell> anyway, dpkg-diverts are fiddly and almost always prone to breaking
[10:15] <agateau> That's why I called for help :)
[10:15] <agateau> I could do a conflicts/replaces, but this would mean removing notify-osd, which will remove ubuntu-desktop if installed
[10:15] <agateau> not sure whether it's a good idea
[10:16] <Riddell> not ideal
[10:18] <apachelogger> it should be migrated to update-alternatives
[10:19] <agateau> apachelogger: but this means I need to convince notify-osd and notification-daemon packagers to do it as well, right?
[10:21] <apachelogger> yes
[10:21] <apachelogger> though there should not be much convincing necessary
[10:21] <agateau> ok
[10:22] <apachelogger> dpkg-divert is like using a chain saw to cut off your current cyborg arm to then attach a new one
[10:22] <agateau> Sounds fun!
[10:22] <apachelogger> while update-alternatives is like asking the nice cyborg mechanic from around the corner the remove the current and attach the new one
[10:23] <apachelogger> of course the latter is much less likely to break + can be influenced by the user without having to uninstall packages that divert the same file
[10:23] <agateau> ok
[10:24] <apachelogger> Riddell: btw, technically that argument of yours is one against cdbs, because dh 7 is nothing but dh 6 with macros, so learning cdbs is the undesired learning of yet another system :P
[10:25] <Riddell> for new packagers yes
[10:26] <apachelogger> agateau: the short description should not end with a periodds ==> +Description: Alternative to KDE4 Plasma notifications.
[10:26] <agateau> ok
[10:27] <agateau> fixing it right now
[10:27] <apachelogger> kthx
[10:40] <Riddell> agateau: I confirm that multiple dpkg-diverts don't seem like a good idea
[10:40] <agateau> Riddell: I know, I tried it :)
[10:40] <Riddell> hopefully kenvandine can be convinced to convert to alternates
[10:41] <agateau> I hope so
[10:41] <agateau> will probably talk to him during Portland sprint
[10:42] <Riddell> ah yes, remind me to go to america tomorrow night
[10:43] <agateau> Riddell: :)
[11:06] <apachelogger> :D :D
[11:06] <apachelogger> I am getting to the point where I think that the Kubuntu logo is just no good for anything -.-
[11:07] <apachelogger> terrible shape to do anything subtle
[11:37] <Riddell> apachelogger: ccheney is going firefox now
[11:47] <apachelogger> jussi01: if still valid bug 310969 should go upstream please
[11:59]  * Riddell wanders out to dentist
[12:03] <ejat> Riddell: ok
[12:05] <ejat> can someone help me on this http://paste.ubuntu.com/364238/
[12:11] <Quintasan|Szel> o/
[12:12] <Quintasan|Szel> anyone here got HTC Touch?
[12:13]  * Quintasan|Szel is wondering which phone to pick
[12:15] <apachelogger> Quintasan|Szel: nexus one :P
[12:15]  * shadeslayer hands Quintasan|Szel a Nokia 1100
[12:15] <shadeslayer> :o
[12:15] <Quintasan|Szel> lol
[12:15] <apachelogger> a phone, not a thing that looks like a phone but does not do calls :P
[12:16] <apachelogger> Quintasan|Szel: if you want one now I would go for the motorola milestone
[12:16] <shadeslayer> Quintasan|Szel: anything but the Blackberry storm :)
[12:16] <apachelogger> otherwise HTC is bringing some nice android devices in 2010
[12:16]  * shadeslayer wants a Droid :)
[12:16] <apachelogger> also I suspect nokia will be rolling some sweet Qt device at some point
[12:16] <apachelogger> shadeslayer: no, a nexus one you want
[12:16] <shadeslayer> apachelogger: i nuked my Kubuntu install btw :)
[12:17] <apachelogger> sweet :D
[12:17] <Quintasan|Szel> apachelogger: hah, I'm limited by my carrier, my dad got some mobile plan which allows him to buy few mobiles on lower price, I have HTC Touch, Nokia E66 (or $omething with doubles) and few other nokas
[12:17] <apachelogger> ejat: looks like someone posted a ugly emoticon that broke something
[12:17] <shadeslayer> yeah i was foolish enough to trust ubiquity with re partitioning my HD,not that it didnt do its job.. did it too well
[12:18] <shadeslayer> ejat: get my memo?
[12:18] <apachelogger> ejat: better check your twitter timeline online, maybe you can isolte the bad guy
[12:18] <Quintasan|Szel> I wanted N900 at first bu I lol'd at price - 2,5k polish zloty
[12:18] <apachelogger> that is like 3 bucks in real money?  I find it quite funny that canonical sells engineering to google and at the same time google fails to nail a stay-search-provider-deal :P
[12:23] <shadeslayer> lol
[12:23] <shadeslayer> apachelogger: so you heard about the recent yahoo spate
[12:24] <apachelogger> well
[12:24] <apachelogger> that raises one particular quesiton for us... should we switch too?
[12:24] <apachelogger> maybe jr gets a raise then :D
[12:24] <shadeslayer> hehe... well thats up to the community
[12:25] <shadeslayer> since we are more of a commmunity distro rather than something canonical influences
[12:25] <apachelogger> I dont think the user will particularly care about what search tingy is used
[12:25] <shadeslayer> yeah... the conclusion at identi.ca was that it doesnt really matter
[12:25] <apachelogger> also we were already using the google custom search anyway
[12:26] <apachelogger> at the same time we can sell the switch to yahoo with privacy concerns of google collecting too much data of our users ;)
[12:26] <shadeslayer> lol
[12:27] <apachelogger> we should get a deal with bing though
[12:27] <shadeslayer> hehe...
[12:27] <apachelogger> I have contacts you know :P
[12:28] <shadeslayer> apachelogger: contract with bing showing linux users how to swtich to windows
[12:28] <apachelogger> also one of my current professors is the original father of bing maps :P
[12:28] <apachelogger> shadeslayer: well, that is an ever growing market, and if we think our product is superior to windows then pro-switching-to-windows-ads might even be a good thing
[12:29] <apachelogger> since users might try switching and fail and realize how good linux is and all
[12:29] <apachelogger> be all the more happy with it
[12:29] <shadeslayer> thats well thought out :)
[12:30] <apachelogger> though if your product is inferior a contract with bing might not work out well for us :P
[12:30] <shadeslayer> hehe...
[12:31] <apachelogger> then again we get loads of money and can buy an isle in the caribbean
[12:32] <apachelogger> name it Isle of Kubuntu and make it a tourist paradise
[12:33] <shadeslayer> apachelogger: btw did you hear about launchpad deleting the source files for ppa uploads?
[12:33] <apachelogger> no
[12:33] <apachelogger> to a certain degree that sounds like a sensible thing... at some point each datacenter runs out of ca pacity :P
[12:33] <shadeslayer> apachelogger: yeah genii told me about it :)
[12:34] <shadeslayer> apachelogger: yeah they ran out of space :P
[12:34] <apachelogger> shadeslayer: did you file a backport request for kopete-facebook yet?
[12:34] <apachelogger> !backports
[12:34] <shadeslayer> apachelogger: http://blog.launchpad.net/general/action-back-up-old-sources-from-ppas
[12:34] <shadeslayer> apachelogger: not till now...
[12:35] <shadeslayer> i need to get the new install updgraded fully right now
[12:36] <apachelogger> you dont need an install to request a backport if your ppa upload for karmic is a non-change upload of the lucid version
[12:36] <apachelogger> which it hopefully is
[12:36] <shadeslayer> yeah its not a changed version
[12:36] <shadeslayer> i just took the lucid changelog and added : new upstream release and removed patches
[12:38] <apachelogger> well then you can write a request and link to the PPA buildlog and state that you did not have to change anything to build the lucid version on karmic and that it runs just fine on karmic etc.\
[12:38] <shadeslayer> ok sure
[12:39] <shadeslayer> apachelogger: btw if i want to download my changelogs again,how do i go about that?
[12:39] <shadeslayer> since i lost everything in the install
[12:42] <apachelogger> shadeslayer: download the dsc and extract it with dpkg-source -x
[12:42] <shadeslayer> ah ok
[12:44] <shadeslayer> apachelogger: i need all the other files too? the source and stuff?
[12:45] <apachelogger> well, technically you can extract the changelog from the diff.gz
[12:45] <apachelogger> but you probably need the source anyway?
[12:47] <shadeslayer> hmm..
[12:47] <shadeslayer> ok ill figure this out :)
[12:48] <Quintasan> I CANT BELIVE THIS
[12:48] <Quintasan> FFFFUUUUUU-
[12:48] <shadeslayer> ?
[12:49] <Quintasan> This num lock thingy makes us look pathetic
[12:49] <apachelogger> this what?
[12:49] <Quintasan> when you get to KDM, do you have to turn on numlock manually?
[12:49] <apachelogger> yes
[12:50] <Quintasan> :3
[12:50] <apachelogger> that however IMHO is due to BIOS crappyness
[12:50] <Quintasan> lol no
[12:50] <Quintasan> let me show you something
[12:50] <apachelogger> why in the name of all gods would each operating system on themself have to ensure that numlock is on?
[12:51] <Quintasan> dunno but the trick is here
[12:51] <apachelogger> also I'd like to mention that on some laptop/netbook keyboards numlock on by default can trigger issues in combination with the function key
[12:51] <Quintasan> funny thing is that
[12:52] <Quintasan> by default boot -> kdm -> no numlock -> login -> no numlock
[12:52] <Quintasan> when you change the kdm you get: boot -> kdm -> numlock on -> login -> no numlock
[12:52] <apachelogger> change the kdm?
[12:52] <Quintasan> when you enable num lock in KDE System settings in Keyboard options you get
[12:53] <shadeslayer> Quintasan: um i think you can change the setting in KDE
[12:53] <Quintasan> boot -> kdm -> numlock on -> login (numlock gets turned off) -> during startup numlock gets turned on once again
[12:53] <Quintasan> shadeslayer: it doesn't work in KDM
[12:54] <Quintasan> shadeslayer: try enabling it and you will see numlock still won't turn on when you are on login screen
[12:54] <apachelogger> Quintasan: so the problem is really that numlock gets turned off after login?
[12:54] <Quintasan> apachelogger: by default it's not enabled in kdm and KDE
[12:54] <Quintasan> :/
[12:54] <apachelogger> by default it's not enabled in your bios!
[12:54] <Quintasan> in kde you go to system settings and enable it there
[12:55] <Quintasan> wanna bet?
[12:55] <Quintasan> anyways I got a fix to KDM numlock
[12:55] <apachelogger> srsly I feel like only half the story got told
[12:55] <apachelogger> well
[12:55] <apachelogger> Quintasan: where is the fix?
[12:56] <Quintasan>  /etc/kde4/kdm/kdmrc
[12:56] <Quintasan> you need to add NumLock=On there
[12:56] <Quintasan> and it will work
[12:57] <shadeslayer> apachelogger: what were the two fields i need to add to my bashrc?
[12:57] <apachelogger> Quintasan: and break keyboards of some laptop and netbook models
[12:57] <Quintasan> how come?
[12:57] <apachelogger> shadeslayer: see bottom of man debuild
[12:57] <apachelogger> Quintasan: because hardware vendors are stupid as hell
[12:58] <Quintasan> +1 on this
[12:59] <Quintasan> anyways this issue is minor but fcking annoying
[12:59] <Quintasan> it deserves some attention form us or we need to talk to KDE
[12:59] <apachelogger> well, before doing anything it is essential that we find out why it is not turned on by X to begin with
[12:59] <apachelogger> Quintasan: that has nothing to do with KDE
[12:59] <apachelogger> that is all X
[12:59] <apachelogger> X X and X alone
[12:59] <apachelogger> not the porn X but the X11 X :P
[13:00] <Quintasan> apachelogger: but shouldn't KDM respect KDE setting and vice-versa?
[13:00] <Quintasan> like when I set to turn on numlock on KDE start KDM should do it as well!
[13:00] <apachelogger> is that so?
[13:00] <apachelogger> what if user1 sets it to on and user2 sets it to off
[13:00] <Quintasan> it's stupid to have to configure the same option in TWO places
[13:02] <Quintasan> and the best thing is that in KDM it is hidden so deep that you have to modify the config file in /etc to enable
[13:02] <Quintasan> it
[13:02] <apachelogger> ossi likes to hide things I think :P
[13:03] <Quintasan> I would just turn it on by defualt and if anyone actually turns it off they can do this manually
[13:03] <Quintasan> 99 % of users have it on so who really cares?
[13:04] <a|wen> Quintasan: not on laptops
[13:04] <Quintasan> laptops don't count as computers :P
[13:04] <apachelogger> Quintasan: did you even listen?
[13:05] <apachelogger> numlock on can cause issues on some models
[13:05] <Quintasan> so wtf we are supposed to do?
[13:05] <apachelogger> and I think most laptop/netbook models since num will switch on a virtual numpad
[13:05] <apachelogger> e.g. my dell inspiron 6k4 for example got a numpad spread across 7-9:m--
[13:06] <apachelogger> now if num was on for that particular keyboard I would not be able to use that beast anymore
[13:06] <a|wen> same deal here on a IBM T60
[13:06] <Quintasan> hmm we have numlockx in repos
[13:07] <Quintasan> I wonder if it will help
[13:07] <apachelogger> no
[13:07] <apachelogger> it also just turns numlock on without regard to the keyboard
[13:08] <Quintasan> :/
[13:08] <apachelogger> IIRC there is not even a sensible way for X to recognize most keyboard models because they do not have any identifying values or anything
[13:08] <apachelogger> even if they had
[13:08] <apachelogger> what if you have a laptop with external keybard attached
[13:08] <Quintasan> I wonder how Windows deals with it
[13:09] <apachelogger> go ask bing!   Use -b to force.
[13:20] <shadeslayer> when i try to build for karmic....
[13:20] <shadeslayer> (just brushing up my basics once again :) )
[13:20] <shadeslayer> so should i force it?
[13:22] <a|wen> would be nice to figure out exactly what turns it off, X or KDM
[13:22]  * shadeslayer opens a USB full off windows viruses
[13:22] <shadeslayer> anyone want the binaries?
[13:23] <shadeslayer> a|wen: probably kdm
[13:23] <shadeslayer> a|wen: since its the kdmrc were editing
[13:24] <a|wen> kdm is set to leave it be on default ... so either there is an error in kdm defaults or something else turns it off (changing kdm to turn it on can fix both of those cases)
[13:25] <shadeslayer> a|wen: good at packaging?
[13:26] <a|wen> shadeslayer: have been motly out of the loop for a few months; but believe I can remember most of it still
[13:26] <a|wen> :)
[13:27] <shadeslayer> a|wen: ok well can you tell me whats the problem with : http://launchpadlibrarian.net/38489013/buildlog_ubuntu-lucid-i386.kopete-facebook_0.1.5-0ubuntu1%2Blucid1~ppa3_FAILEDTOBUILD.txt.gz
[13:28] <Riddell> ouch my mouth
[13:28] <shadeslayer> a|wen: same problem with 64 bit build
[13:29] <a|wen> shadeslayer: building on karmic or lucid?
[13:29] <shadeslayer> a|wen: im on karmic,building it for lucid
[13:29]  * a|wen pushes some cold and soft ice towards Riddell
[13:31] <shadeslayer> a|wen: so whats your diagnosis?
[13:31] <a|wen> shadeslayer: looks like libqt4-dev no longer depends on pkg-config; so build depend on pkg-config directly
[13:32] <shadeslayer> a|wen: oh..
[13:32] <shadeslayer> thats a recent development
[13:32] <a|wen> shadeslayer: it does on karmic but not on current lucid
[13:33] <shadeslayer> ah.. so i need to add in the change log for lucid but not karmic
[13:34] <a|wen> hmm, no mention in the changelog why we dropped that depends; might be an error that it was dropped
[13:35] <shadeslayer> hmm
[13:35] <shadeslayer> well ok ive added it to my change log
[13:36] <a|wen> shadeslayer: add it for now to make it work ... maybe it should be fixed in libqt4-dev instead though
[13:37] <Quintasan> I belive virt-manager should be written in Qt, not crappy GTK
[13:37] <shadeslayer> a|wen: so should i add a bug report?
[13:39] <shadeslayer> oh noes... got to upload again
[13:39] <a|wen> Riddell: do you know if pkg-config was removed from depends of libqt4-dev on purpose? no mention of it in the changelog (so probably done when merging)
[13:39] <shadeslayer> uploaded the same veriosn
[13:41] <shadeslayer> i need more eyes to keep track of things
[13:44] <shadeslayer> a|wen: btw what about : New version specified (0.1.5-0ubuntu1~karmic~ppa2) is less than
[13:44] <shadeslayer> the current version number (0.1.5-0ubuntu1+lucid1~ppa3)!  Use -b to force.
[13:45] <shadeslayer> a|wen: im backporting the same package to karmic
[13:45] <a|wen> shadeslayer: when backporting/PPA-building/et.al you will want it to be smaller; so that warning is only positive
[13:55] <Riddell> a|wen: a load of depends were removed from qt-dev to keep us in line with debian
[13:55] <Riddell> Tm_T: hmm?
[13:56] <Riddell> tseliot: did jockey get sorted?
[13:56] <a|wen> okay, thx ... as long as it is intended i'm happy (and just adds them to others build-depends when needed)
[13:56] <Tm_T> Riddell: ctcp spammers are not running around currently
[13:56] <tseliot> Riddell: yes but I would like to test it a bit more before I upload it
[13:56] <tseliot> Riddell: it builds fine though
[13:57] <tseliot> :-)
[14:00] <ghostcube> ehlo peoples
[14:00] <ghostcube> rc2 working fine so far
[14:07] <Quintasan> hurr durr
[14:08] <Quintasan> can't get networking on my debian to work :/
[14:12] <shadeslayer> a|wen: yeah sorry for that... power outage
[14:13] <a|wen> shadeslayer: conclusion was: just add pkg-config as build-depend
[14:14] <shadeslayer> ok
[14:14] <shadeslayer> a|wen: yeah i think we got till that point and then you asked Riddell about it
[14:15] <a|wen> shadeslayer: got a reply as well; was intentional
[14:15] <shadeslayer> a|wen: and about the forcing of karmic version?
[14:15] <shadeslayer> should i use -b
[14:15] <a|wen>  when backporting/PPA-building/et.al you will want it to be smaller; so that warning is only positive
[14:16] <shadeslayer> a|wen: ok
[14:37] <shadeslayer> a|wen: apart from New upstream release,i dont require anything else in the backport right?
[14:39] <a|wen> shadeslayer: you are taking the one in lucid and building it for karmic, right? normally you would just write no-change backport in the changelog
[14:40] <shadeslayer> a|wen: oh ok
[14:40] <shadeslayer> a|wen: yeah im doing that... so just the new version at the top
[14:41] <a|wen> shadeslayer: you take the lucid version and append ~karmic1 to it (and if you build it in your ppa for now, you will most likely want to append ~karmic1~ppa1 to it)
[14:42] <shadeslayer> a|wen: ah ok :)
[14:42] <shadeslayer> so the versio is : kopete-facebook-0.1.5-0ubuntu1~karmic1~ppa1
[14:44] <shadeslayer> a|wen: ^^
[14:44] <a|wen> shadeslayer: jup
[14:45] <shadeslayer> ok thanks :)
[14:46] <shadeslayer> a|wen: oh wait i have to remove pkg-config from control so i should mention that right
[14:47] <a|wen> shadeslayer: no need to remove it
[14:47] <shadeslayer> a|wen: ok
[14:48] <a|wen> shadeslayer: but current kopete-facebook in lucid does that build on lucid?
[14:48] <shadeslayer> a|wen: yeah
[14:48] <shadeslayer> it did
[14:49] <a|wen> have you tried building it now?
[14:49] <shadeslayer> a|wen: building what?
[14:52] <a|wen> hmm, if it builds i wonder why you got an error earlier ... nevermind; no need to remove pkg-config from build-deps if it is there when backporting
[14:53] <shadeslayer> ok
[14:53] <a|wen> you should just add a new changelog entry and nothing more if you can get away with it
[14:53] <shadeslayer> :D
[14:56] <shadeslayer> a|wen: apparently the build failed http://launchpadlibrarian.net/38490980/buildlog_ubuntu-karmic-amd64.kopete-facebook_0.1.5-0ubuntu1~karmic1~ppa1_FAILEDTOBUILD.txt.gz
[14:57] <a|wen> shadeslayer: looks like you have removed pkg-config from build-deps before uploading
[14:58] <shadeslayer> a|wen: eek!
[14:59] <shadeslayer> a|wen: btw if i want to upload the just the new .dsc etc without uploading the source and changing the version,how do i do that?
[15:00] <a|wen> shadeslayer: you can't; but using "debuild -S -sd" it will only upload the dsc + diff.gz and not the .orig.tar.gz
[15:00] <shadeslayer> a|wen: hm.. ok
[15:00] <a|wen> shadeslayer: the diff.gz contains your changes; so that one is needed
[15:02] <shadeslayer> ok
[15:14] <shadeslayer> a|wen: Rejected:
[15:14] <shadeslayer> The source kopete-facebook - 0.1.5-0ubuntu1~karmic1~ppa1 is already accepted in ubuntu/karmic and you cannot upload the same version within the same distribution. You have to modify the source version and re-upload.
[15:14] <shadeslayer> a|wen: which is weird since i already deleted the packages
[15:15] <Riddell> shadeslayer: it doesn't get deleted straigh away
[15:16] <Riddell> just upload with ~ppa2
[15:18] <shadeslayer> Riddell: well im going link it to ubuntu backports....
[15:19] <shadeslayer> so will they check for the previous entries too?
[15:20] <a|wen> shadeslayer: when it is backported for real, the "~ppaX" part will be removed
[15:21] <shadeslayer> oh ok
[15:25] <shadeslayer> and while uploading how do i get rid of : gpg: WARNING: This key is not certified with a trusted signature!
[15:34] <shadeslayer> apachelogger: https://bugs.launchpad.net/karmic-backports/+bug/513825
[15:34] <shadeslayer> a|wen Riddell ^^
[16:09] <freeflying> Riddell: are we going to drop the patch to force use dejavu font?
[16:09] <freeflying> Riddell: this patch is really stupid
[16:11] <Tm_T> freeflying: what where?
[16:13] <freeflying> Tm_T: dejavu is a font which only contains latin characters, it will not let use pickup corresponding font according to his locale
[16:13] <freeflying> Tm_T: I only can say the author of this patch dosen't know what is font mean
[16:13] <Riddell> freeflying: can do, which package is that in?
[16:13] <Tm_T> freeflying: this forces that font be used by default, or it cannot overridden at all?
[16:14] <freeflying> Riddell: kdebase? or kdelibs, can't remeber clearly
[16:14] <freeflying> Tm_T: can be overwriten is another story, we're going to bring more user friendly experience
[16:15] <Tm_T> freeflying: sure, I just heard about this first time
[16:15] <freeflying> Tm_T: I have raised this up in last release cycle :)
[16:16] <Tm_T> aye, I havent been active enough ):
[16:19] <Riddell> freeflying: removed in bzr
[16:19] <freeflying> Riddell: thx dude
[17:02] <ulysses> KDE SC meant "KDE Software Compilation", am I right? Not "KDE Software Collection", as it"s written at http://www.kubuntu.org/news/kde-sc-4.3.5
[17:03]  * shadeslayer wonders who edits these pages
[17:04] <shadeslayer> Riddell: ping
[17:04]  * ulysses edits only kde.hu and ubuntu.hu
[17:05]  * shadeslayer realises he needs to work on rekonq docs
[17:07] <Riddell> you are indeed right
[17:08] <Riddell> fixed, thanks ulysses
[17:08] <ulysses> you're welcome
[17:10] <nixternal> Riddell:
[17:10] <ulysses> o.O
[17:10] <nixternal> 11:10:50 [notice(ChanServ!ChanServ@services.)] You are not authorized to perform this operation.
[17:11] <nixternal> I tried to op up to stop it
[17:15] <shadeslayer_> 0_o
[17:25] <shadeslayer_> Riddell: btw if i apply for kubuntu membership as of now,what are my chances of getting one?
[17:26] <shadeslayer_> i dont wanna get my hopes high by applying and get rejected after applying :)
[17:26] <Riddell> shadeslayer_: what are your contributions?
[17:27] <shadeslayer_> Riddell: does the IRC count?
[17:27] <shadeslayer_> Riddell: i mean support on the irc
[17:28] <Riddell> yeah, if there's people who can back it up
[17:29] <shadeslayer_> Riddell: ok well then 1 year of IRC support,im starting as a packager and i maintain the docs for a small browser rekonq...
[17:29] <shadeslayer_> and ive filed loads of bug reports on bug.kde.org....
[17:30] <shadeslayer_> Riddell: ill probably apply next month,so some more packages i guess
[17:31] <Riddell> a year of IRC support is lovely, just find people to back it up with testimonials on your wiki page
[17:31] <Riddell> upstream stuff like rekonq and bugs to b.k.o don't count I'm afraid
[17:31] <Riddell> go go packaging
[17:31] <maco> isnt packaging more for kubuntu-dev than km?
[17:32] <Riddell> any sustained and significant contribution, packaging is one of those
[17:32] <Riddell> so both
[17:33] <shadeslayer_> Riddell: hmm... well i guess short term packaging adventures dont count then LO
[17:33] <shadeslayer_> :P
[17:35] <Riddell> it shows you're intending to branch out, so it's all good
[17:36] <shadeslayer_> Riddell: hmm,and _suppose_ i become a member,will it be necessary to contribute regurlarly or can i be silent for 2 months and then work like crazy for a month
[17:37] <Riddell> that's ok, but if you are not going to do significant contributions in the near future you should step down gracefully and deactivate your membership
[17:38] <shadeslayer_> hmm
[17:38] <shadeslayer_> Riddell: and the people who will write the testimonials... they should be...
[17:39] <Riddell> anyone who can vouch for your contributions.  it helps if that includes people I know of course
[17:39] <shadeslayer_> hmm... ok
[17:39] <shadeslayer_> Riddell: thanks for all that info :)
[17:39] <Tm_T> don't look at me
[17:39]  * Tm_T hides
[17:39] <shadeslayer_> Tm_T: im not :)
[17:40]  * shadeslayer_ closes his eyes
[17:49] <Tm_T> shadeslayer_: actually, keep up the good work (:
[17:49] <Tm_T> now I can hide
[17:51] <shadeslayer_> hehe :)
[17:51] <shadeslayer_> can anyone get into identi.ca ?
[17:53] <shadeslayer_> Riddell: will promotion of kubuntu via my college magazine count?
[17:53] <shadeslayer_> :P
[17:54] <shadeslayer_> i have to write 7 articles... 5 of them probably on kubuntu,ubuntu,canonica and identi.ca :P
[18:00] <Riddell> shadeslayer_: sure
[18:01] <shadeslayer_> hehe
[18:05] <ulysses> Bug 442000 was reopened, but there isn't enough information again, can I close it?
[18:07] <Riddell> ubottu: well he gave the information requested
[18:07] <Riddell> ulysses:
[18:09] <ulysses> Riddell: Do you think?
[18:09] <Riddell> jon asked "Is it still a problem for you?" he said that it is
[18:10] <ulysses> Oh, I missed *still*
[18:10] <shadeslayer_> alsways.... =)
[18:11] <ulysses> English isn't his/her native language:)
[18:12] <nixternal> that person needs to remove ~/.kde/share/config/dolphinrc - I had that problem a long time ago, and iirc that fixed it
[18:14] <ulysses> nixternal: I'll post a comment
[18:15] <nixternal> don't like sitting up there looking like I am different from everyone else
[18:15] <Tm_T> but you are!
[18:20]  * shadeslayer_ puts a hat on top of nixternal
[18:23] <nixternal> brr it's cold out
[18:26]  * shadeslayer_ stuggles with git
[18:44] <binarylooks> ubiquity crashes in the latest current kubuntu daily-live. Known?
[18:45] <binarylooks> TypeError: QLabel.setText(QString: argument 1 has unexpected type 'NoneType'
[18:45] <binarylooks> in kde_ui.py line 205
[18:48] <Riddell> shtylman: ^^ ?
[18:50] <binarylooks> I'll try filing a bug
[18:50] <maco> no seele? what?
[18:57] <binarylooks> ok, was already reported: bug 511947
[19:05] <neversfelde> why is kopete's context menu in tray different from the others? Did we do that, or is it from upstream.
[19:09] <marcosRz> serious Riddell if you think OO.org from Kubuntu is decent please tell
[19:10] <Riddell> grumpy grumpy
[19:10] <Riddell> neversfelde: if it looks all plasma-ified that's the dbusmenu stuff
[19:10] <shadeslayer_> wow..he doesnt want to give up does he
[19:11] <neversfelde> Riddell: so it is our patch? If so, it does not work very good with two screens.
[19:11] <Riddell> neversfelde: yes, it's being by agateau in consultation with upstream
[19:11] <shadeslayer_> neversfelde: oh yeah wanted to talk to you
[19:11] <neversfelde> ok, I will tell him about these problems, when he returns
[19:12] <Riddell> neversfelde: I'm sure he's appreciate that
[19:12] <shadeslayer_> neversfelde: https://launchpad.net/~neversfelde/+archive/experimental << what version of packages do you have?
[19:12] <neversfelde> shadeslayer_: I do not understand, what version?
[19:13] <neversfelde> there is only choqok in there afaik
[19:13] <shadeslayer_> neversfelde: i mean are they the current git version or just 0.9.4?
[19:13] <shadeslayer_> (i dont know when 0.9.4 was released)
[19:13] <neversfelde> shadeslayer_: +git20100123
[19:13] <neversfelde> 23rd of January
[19:14] <shadeslayer_> neversfelde: and when was 0.9.4 released any ideas?
[19:14] <neversfelde> shadeslayer_: hum, last year in December I think
[19:14] <shadeslayer_> neversfelde: ok well... no point in updating my ppa now then :)
[19:14] <neversfelde> oh no, it was October
[19:14] <shadeslayer_> oh... thats a long time back...
[19:15] <neversfelde> but there are some recent changes and I think we#ll can expect a new alpha or beta soon
[19:15] <shadeslayer_> neversfelde: ah well.. someone was asking for git packages,was thinking whether to upload or not
[19:16] <neversfelde> shadeslayer_: well, there are actual git packages in my ppa, no changes after they were uploaded
[19:16] <neversfelde> so no need for newer ones?
[19:16] <shadeslayer_> yeah..
[19:16] <shadeslayer_> neversfelde: there were minor changes... disabling of the public timeline etc
[19:17] <neversfelde> shadeslayer_: that feature should be available with the packages from my ppa
[19:18] <shadeslayer_> neversfelde: oh cool then... i wont go through the trouble of updating my repo then :P
[19:21] <Tm_T> sillyness
[19:26] <shadeslayer_> Tm_T: yeps
[19:29]  * shadeslayer_ wonders who knows how to write docs
[19:29] <Riddell> that nixternal chap is quite the man
[19:30] <shadeslayer_> nixternal:ping
[19:30] <jjesse_> i do as well
[19:30] <shadeslayer_> oh cool
[19:30] <shadeslayer_> jjesse: whats the command to check for XML errors?
[19:30] <jjesse> particular question?
[19:30] <jjesse> do you have the docs checked out?
[19:30]  * shadeslayer_ is writing the docbook after 2 months
[19:31] <shadeslayer_> jjesse: yeah i worked on it initially and have the git version
[19:31] <shadeslayer_> (worst part comes after editing the docbook... pushing the new one back :P )
[19:32] <jjesse> from the scripts folder there is a validatae.sh script that will work
[19:32] <shadeslayer_> jjesse: um no scripts folder....
[19:32] <shadeslayer_> i remember there used to be something like xmlchecker
[19:32] <jjesse> are you talking kde-docs or kbuuntu-docs?
[19:33] <shadeslayer_> jjesse: kde docs
[19:33] <jjesse> ah
[19:33] <jjesse> that's a bit different
[19:33] <shadeslayer_> jjesse: yeah i know...
[19:33] <jjesse> ok hold on phone call
[19:34] <jjesse> lets move this to #kde-docs
[19:34] <shadeslayer_> jjesse: actually i found it :)
[19:34] <shadeslayer_> its index.docbook:238: element xref: validity error : IDREF attribute linkend references an unknown ID "lmb-mmb"
[19:34] <shadeslayer_> eeks...
[19:35] <shadeslayer_> its checkXML btw
[19:35] <jjesse> oh sorry
[19:35]  * jjesse is a bit busy working
[19:36] <nixternal> shadeslayer_: what's up?
[19:36] <Riddell> shtylman: maco's patience finally find out what the problem was that the guy we just kicked had, openoffice in KDE mode doesn't show most of the labels in its statusbar
[19:37] <shadeslayer_> wth
[19:37] <maco> he claims there are more bugs, but he refuses to file them
[19:37] <maco> because he doesnt have time to do
[19:37] <shadeslayer_> kwin just vanished as soon as my laptop fan came on :P
[19:37] <maco> he could've filed 10 bugs in the time he was in #kubuntu though
[19:37] <shadeslayer_> nixternal: wanted to know how to check docbooks via checkXML
[19:38] <nixternal> http://www.englishbreakfastnetwork.org/sanitizer/just-in-time.php  <- shadeslayer_ you can use this as well...it does more than CheckXML
[19:38] <nixternal> meinproc also will tell you when test building
[19:39] <nixternal> xmllint --noout --noent --postvalid index.docbook
[19:39] <nixternal> that is another one as well
 I just had right know more 3 bugs
 ...
 letters dissapearing
 i am not a bug tracker
[19:39] <nixternal> haha
[19:39] <nixternal> I get messaged constantly from that user
[19:43] <shadeslayer_> lol
[19:53] <shadeslayer_> nixternal: thats a awesome site..
[19:54] <shadeslayer_> nixternal: the command isnt that awesome... gave me alot of errors while the site says the docbook is perfect :)
[19:55] <shadeslayer_> nixternal: oh and btw next time you have a job in the docs department,please do notify me via identi.ca or the IRC :)
[19:55] <nixternal> roger that
[19:56] <nixternal> yeah, we use xmllint with kubuntu-docs...haven't used it in quite some time on kde docs
[20:30] <Tm_T> nooo he quit...
[20:57] <neversfelde> there seems to be a release of basket-kde4 on 12th of February, when is our freeze?
[21:02] <Riddell> 18th
[21:05] <genii> Man. plasma-desktop crash, sudo apt-get install kdeplasma-addons-dbg plasma-widget-networkmanagement-dbg wants to install 355Mb of stuff.
[21:05] <genii> Hopefully there'll be some useful info after.
[21:07] <shadeslayer> genii: please do memoserv me the bug link :)
[21:08] <neversfelde> anyone already working on a KDE4 package for basket?
[21:08] <Lex79> no
[21:08] <genii> shadeslayer: Will do
[21:09] <shadeslayer> genii: thanks :)
[21:09] <shadeslayer> neversfelde: is it in the repos?
[21:10] <shadeslayer> neversfelde: if its in the repos i can update it...
[21:10] <shadeslayer> cant package from scratch :P
[21:10] <neversfelde> shadeslayer: well, there is no relases atm, I will have a look at it
[21:10] <shadeslayer> neversfelde: ok
[21:24] <Tm_T> claydoh: huh indeed
[21:25] <claydoh> Tm_T : ?? what did i do?
[21:25] <claydoh> Tm_T : ?? what did i do?
[21:25] <claydoh> oops
[21:25] <Tm_T> claydoh: nothing, your "ircname" or "realname" is set to "huh?"
[21:27] <claydoh> heh  I guess I did do that
[21:28] <Tm_T> yes you did (:
[21:29] <claydoh> in chatzilla, the option for "description"  must mean 'real name'
[21:29] <Tm_T> claydoh: aye
[21:30] <claydoh> well then chatzilla  is not so good then :) but there aren't many good portable/lite irc clients
[21:31] <Tm_T> claydoh: I just use irssi everywhere
[21:31] <Tm_T> well, almost
[21:31] <claydoh> I can't, usually
[21:32] <Tm_T> aye, there's no single solution I'm afraid
[21:33] <claydoh> tho I just managed to get an ssh connection to one of my home boxes, so I can , um, circumvent the evil hardware filter we have at work
[21:34] <Tm_T> hehe
[21:35] <claydoh> luckily they trust me enough, but there have been pr0n issues in some of our restaurants so they basically allow us about access to 5 websites
[21:36] <claydoh> so irssi is next on my list if new things to try out
[21:55] <maco> seele: #ubuntu-us-dc /topic now mentions the party
[22:02] <Tm_T> there is any way to see what's situation of package buildings in archives?
[22:09] <neversfelde> how todo I skip dh_auto_test for debehlper in debian/rules?
[22:09] <neversfelde> s/todo/do
[22:14] <seele> maco: cool.. i think it is going to be at fudruckers, so any DC people needing rides will have to ping me
[22:14] <maco> where is that?
[22:14] <maco> chinatown's the only fudruckers i know
[22:14] <maco> also, why arent you in our loco channel :(
[22:14] <maco> you dont like us! *pout*
[22:18] <maco> seele: ^
[22:23] <crimsun> I hope you don't mean the Fudd in Columbia...
[22:24] <crimsun> maco: are we proceeding with the concurrent Ubuntu Hour?
[22:24] <maco> um im going to the kde party...
[22:25] <maco> i was joking about kubuntu and ubuntu people being separatists
[22:25] <seele> the fudruckers in columbia
[22:25] <seele> since 80% of the people who come to the kde events are from the md loco and calug
[22:26] <seele> crimsun: yes.
[22:26] <crimsun> maco: hm?  I proposed this morning to combine the KDE party with an Ubuntu Hour.
[22:26] <maco> crimsun: you asked if it should be at the same time
[22:26] <maco> i thought you were saying "us gnome people are gonna go have fun without you kde people, so HRMPH!"
[22:26] <crimsun> maco: lolzwut?  I'm not a GNOME person.
[22:27] <maco> you were totally using gnome when i saw your computer today
[22:28] <crimsun> what does that have to do with Ubuntu Hour running concurrently with the KDE party?
[22:28] <maco> i didnt realise you meant in the same place
[22:28] <crimsun> and I always use GNOME in that sense; it's the fastest way to track regressions
[23:09]  * gkmngrgn nn