[04:45] <nixternal> argh, beta 2 doesn't work for me...anyone else have a problem with plasma not showing 2 boxes in the kicker, or a menu button? is there a way to fix this?
[04:45] <mluser> same problem here :(
[04:46] <nixternal> well this stinks
[04:46] <nixternal> I had the same problem with an svn checkout as well
[04:46] <mluser> most kde4 programs are segfaulting when I run them
[04:46] <nixternal> I think it worked in Xephyr though
[04:47] <mluser> I'm not sure the environment is being exported correctly
[04:47] <nixternal> I am in KDE 4 now with Konsole running this irssi session
[04:47] <mluser> whats the name of the kicker replacement?
[04:47] <stdin> I've seen a lot of people say it's not working
[04:47] <nixternal> plasma
[04:47] <nixternal> konqi crashes in kde 4 as well
[04:48] <mluser> konqueror runs for me.. as long as I dont click on certain parts of it :)
[04:48] <nixternal> konqueror(6474) kdemain: main() -> no argsSegmentation fault
[04:49] <stdin> seems to work for me
[04:49] <mluser> how are you starting it stdin?
[04:49] <mluser> kde4 not konqueror
[04:49] <mluser> from kdm or Xephyr?
[04:50] <stdin> mluser: konqueror, not the whole KDE4, I get the same problem with no bar at the bottom as everyone else
[04:50] <mluser> ok
[04:51] <nixternal> now how to people have the groovy kickers that I have been seeing in the screenshots?
[04:52] <stdin> maybe they are running the svn version, I know compiling the release source packages gives the same results as the debs
[04:53] <nixternal> ahhh..no the reason is because what we need is in the KDE 4 playground
[04:54] <stdin> ahh, yeah. that would make sense
[04:59] <mluser> Is there a way to disable strigi from comming up on startup?
[05:05] <bddebian> Any of you familiar with p2kmoto?
[05:06] <bddebian> Oh, jridell uploaded it
[05:24] <mluser> anyone have a good howto for pairing devices (specificaly a bluetooth headset) with gutsy?
[10:42] <blekos> hi, dont know if there is a developer here, but I think you should know that UUID causes quite a problems I've posted it as a bug
[10:43] <blekos> could you tell me how i can use nvidia restricted driver? I can't find the restricted manager (gui)
[10:44] <Jucato> if you're on gutsy, it should be in System Settings -> Advanced tab
[10:44] <blekos> i'm on gutsy, yes i saw it thnx
[10:45] <Jucato> as for the UUID thing, #ubuntu-devel or #ubuntu-kernel would probably be the best place for that. but the bug report is fine
[10:46] <blekos> ok
[11:42] <mhb> good morning fellow Kubuntu creators and fans
[11:43] <Jucato> moin mhb
[12:28] <superstoned> morning
[12:36] <Jucato> hm.. do we have a KDE 4 package for playground/plasma?
[12:41] <mhb> Jucato: I doubt it
[12:41] <Jucato> wishful thinking :)
[03:24] <Viper550> I think I already found a Gutsy bug
[03:26] <Viper550> When I started it, I got a huge resolution in VMWare Server (LARGER THAN MY SCREEN!)
[03:27] <Viper550> So, I obviously went to the Screen Resolution applet
[03:28] <Viper550> BUT, when I went to change it, you have to click that box to confirm it, but it went by VERY FAST
[03:30] <Viper550> you there?
[03:31] <stdin> it waits 15 seconds, just checked
[03:31] <stdin> sounds more like a vmware bug
[03:31] <Hobbsee> only vaguely.  very vaguely
[03:31] <Viper550> there any way to set resolution on the boot menu?
[03:32] <stdin> doesn't the liveCD give you that option?
[03:32] <Viper550> that's what I'm using
[03:32] <stdin> before you choose "Start or install Kubuntu"
[03:32] <stdin> it's f4 or something
[03:34] <Viper550> okay, I did that, looks like it's doing something but the screen is garbled
[03:34] <Viper550> STILL huge.
[03:37] <Viper550> going to try VirtualBox, see if anything happens differently
[03:38] <Viper550> and usplash is broken I see
[03:48] <Viper550> yeah, updated VirtualBox, it's booting now. also lol, no usplash
[04:09] <Hobbsee> do we have any people here interested in mentoring stuff?
[04:10] <Hobbsee> nixternal: how's kde4 for mentoring?
[04:15] <mhb> Hobbsee: I could do some mentoring, I guess.
[04:15] <mhb> Hobbsee: if you consider me experienced enough :o)
[04:15] <Hobbsee> mhb: i dont know what they're looking for, in particular.
[04:16] <Hobbsee> mhb: there's a thread on ubuntu-devel-discuss, about mentoring of italian students for implementing specs on ubuntu
[04:16] <Hobbsee> mhb: it would probably be smart to get some of these people involved in ubuntu
[04:17] <mhb> ah. Well, I can't really do much GTK/GNOME-related mentoring.
[04:17] <mhb> But if they are looking for KDE/Kubuntu mentors, I'd apply.
[04:19] <Hobbsee> they dont say - i suspectthey'll pick anything interesting looking
[04:20] <Hobbsee> and if you say "we've got kde/kubuntu people who are happy to mentor", then i suspect tehy'll pick kubuntu stuff.
[04:20] <mhb> Hobbsee: do you know whom should I contact?
[04:21] <Hobbsee> see u-d-d ML
[04:22] <Hobbsee> yay, closed 16 bugs.
[04:25] <Hobbsee> nixternal: you actually here now?
[04:38] <larsivi> anyone here heard of the WM not being able to pick up the X settings ?
[04:39] <larsivi> KDE believe that I have 1024x768, wheras it is 1200x800
[04:39] <larsivi> X knows this (xrandr shows that) and I can move the pointer and windows over the full screen
[04:39] <mhb> larsivi: could you please be more specific?
[04:40] <mhb> larsivi: "KDE believes" is hard to debug, please tell us which app believes that
[04:40] <larsivi> but if I maximize a window, it maximizes if screen is 1024x768
[04:40] <larsivi> mhb: all of KDE, including KDM
[04:41] <larsivi> I see the same with Xfce, btw and I experienced the same when upgrading X earlier this year independently from the ubuntu updates to test a new driver
[04:42] <mhb> so both KDE and XFCE have this error?
[04:42] <larsivi> yes
[04:43] <larsivi> did the xrandr interface (that the system settings use) change with the previous X release? I think I heard something about it ...
[04:43] <mhb> larsivi: it did change, yes. However, most people are not experiencing any issues like that.
[04:44] <larsivi> could it be due to me having widescreen laptops?
[04:44] <larsivi> such that default settings usually looks smart?
[04:44] <mhb> larsivi: I am having one and working fine with the latest X
[04:44] <mhb> so it could be a laptop-specific problem
[04:45] <larsivi> I installed gutsy on this one yesterday, the other is running feisty, but with a post-feisty X
[04:45] <larsivi> both laptops
[04:45] <larsivi> if I connect an external monitor, it seems that one gets correct settings
[04:49] <larsivi> I will create a bug report and upload a couple of screen shots
[05:01] <fdoving> larsivi: do you use xrandr to set the correct resolution, or does xorg find the correct one itself?
[05:02] <fdoving> xrandr did change not too long ago.
[05:02] <fdoving> i belive feisty does have xrandr 1.2.
[05:11] <fdoving> larsivi: do you have any devices connected,  that could report a maximum resoluiton of 1024x768? (xrandr will tell you)
[05:11] <Hobbsee> greetings, fdoving
[05:11] <fdoving> hi hobbsee :)
[05:12] <Jucato> live long and prosper!
[05:13] <Hobbsee> i havent accepted the shift yet
[05:13] <Hobbsee> and yes, i'ts 1am
[05:13] <Jucato> hehe :)
[05:16] <fdoving> larsivi: did you ask for suggestions in #xorg or #xorg-devel ?
[05:56] <fdoving> larsivi: did you report that bug?
[06:24] <larsivi> fdoving: sorry, needed to attend some family - will report the bug a bit later
[06:24] <larsivi> fdoving: xrandr on the command line reports the correct settings, and the screen has the correct resolution
[06:24] <larsivi> it
[06:24] <fdoving> ok.
[06:24] <larsivi> it's things placed by kde (kwin?) that are placed incorrectly
[06:25] <fdoving> does the same thing happen for xfce/gnome?
[06:25] <fdoving> or is it just kwin?
[06:27] <larsivi> fdoving: same thing happened with xfce, haven't tried gnome
[06:27] <fdoving> larsivi: ok, atleast we know it's not kde-specific then.
[06:28] <fdoving> larsivi: if you take a screenshot, will it include a black/blank field?
[06:29] <fdoving> larsivi: you're not using compiz or similar, right?
[06:30] <larsivi> fdoving: not unless it is on by default :)
[06:30] <fdoving> ok.
[06:30] <larsivi> fdoving: I have a screenshot of a "maximized" window, + 1 with kde settings and xrandr output
[06:31] <fdoving> url?
[06:37] <larsivi> fdoving: http://larsivi.net/files/detectingwrongscreensize.png
[06:38] <larsivi> fdoving: http://larsivi.net/files/xrandrandkdesettings.png
[06:38] <larsivi> will create the bug report later tonight, I think
[07:01] <fdoving> larsivi: did you do anything special to make the kicker extend to the full width or does it do that?
[07:02] <fdoving> larsivi: and what if you disconnect the TV?
[07:02] <fdoving> .. then restart x maybe.
[07:06] <larsivi> fdoving: I just moved kicker, and it fixed itself
[07:07] <fdoving> ok.
[07:07] <larsivi> but it starts in the wrong position
[07:08] <larsivi> on another laptop with a similar problem (feisty), I usually connect an external monitor and it behaves correctly
[07:08] <larsivi> if I restart without it, all previous positioning is forgotten
[07:08] <fdoving> if you kill kdesktop then restart it, does it fix the issue? 'dcop kdesktop MainApplication-Interface quit && kdesktop&'
[07:11] <larsivi> fdoving: no immediate effect, no
[07:11] <fdoving> k.
[07:11] <fdoving> what about kwin: 'kwin --replace'
[07:13] <larsivi> nope
[07:13] <fdoving> ok.
[07:27] <larsivi> fdoving: actually, the kwin --replace messed up quite a bit :)
[07:31] <larsivi> fdoving: do you have a guess on which component I should file this bug?
[07:36] <fdoving> larsivi: i'd say xorg.
[07:39] <fdoving> larsivi: including /var/log/Xorg.0.log and 'lspci -v' in the bugreport might help.
[07:41] <larsivi> fdoving: thanks (although it would have to mean xorg provides inconsistent info?)
[07:41] <fdoving> maybe, i don't know how those internals work.
[07:41] <fdoving> but since it happens both for kde and xfce, it's not a kde problem as far as i can understand.
[07:42] <larsivi> or it's a problem with both :)
[07:43] <fdoving> not likely, as xorg is the common piece.
[07:45] <fdoving> i need to run. back in a while.
[07:46] <_StefanS_> hey
[07:46] <_StefanS_> Tonio_: is there something new in the latest svn bluetooth?
[07:48] <_StefanS_> brb.
[08:04] <_StefanS_> Tonio_: back..
[08:22] <_StefanS_> Tonio_: seems like the accept code for the bt mouse is working now
[08:22] <_StefanS_> Tonio_: but still a segfault in the paired devices .
[08:53] <Tonio_> _StefanS__: latest svn fixes the issues for input devices
[08:54] <Tonio_> _StefanS__: I'd say it's the first version where everything works, so now I won't upload anything before testing widelly
[08:54] <Tonio_> paired segfaults for you ?
[08:54] <_StefanS__> Tonio_: good strategy :)
[08:55] <Tonio_> _StefanS__: argh the segfault is back
[08:55] <Tonio_> _StefanS__: didn't crash with previous version..........
[08:55] <Tonio_> _StefanS__: shoudl be possible to check the difference I guess
[08:55] <Tonio_> _StefanS__: interested in working on this ?
[08:55] <_StefanS__> Tonio_: well, it could be compared easily. can you do that?
[08:55] <_StefanS__> heh, ok
[08:55] <Tonio_> _StefanS__: well I can but I'm not sure to understand the code on that point.....
[08:56] <_StefanS__> i can do it later then
[08:56] <Tonio_> _StefanS__: well I suggest we both work on this on our own, I'll try to have a look on monday, I'm not available before
[08:57] <_StefanS__> ill just do it. no problem. got my new kid on my arm now, so ill do it later
[08:58] <Tonio_> _StefanS__: sure, there are priorities :)
[08:58] <Tonio_> _StefanS__: I just don't understand how they tet this
[08:58] <_StefanS__> he's staring at me like crazy :)
[08:58] <Tonio_> they fix something and they rebreak something the next upload..... strage
[08:58] <_StefanS__> well its easy.. they dony test.
[08:59] <Tonio_> lol that's possible
[08:59] <_StefanS__> just commiting all the time, and i ythink its a merge in libbluketooth that causes it'
[09:00] <Tonio_> _StefanS__: maybe yes
[09:00] <Tonio_> _StefanS__: well the point is that there is just that bug now, so I suggest to stop the svn sync and focus on that bug and that's it
[09:00] <_StefanS__> Tonio_: ive traced the segfault to it
[09:00] <_StefanS__> yes agreed.
[09:01] <Tonio_> :)
[09:01] <Tonio_> _StefanS__: stay with your child, I'll try first, and then if I'm too limited on that point you can waste your time on it
[09:02] <_StefanS__> just mail me. i will expect to start in an hour or something
[09:04] <Tonio_> _StefanS__: well I'm going out toonight, so I won't have found that before, better you start then........ :( sorry
[09:05] <_StefanS__> Tonio_: thats cool, no problem. Have a good time, I will be home taking care of kids and patching stuff :D
[09:05] <Tonio_> hehe :)
[09:05] <Tonio_> well time to go for me, have fun :)
[09:13] <jjesse> wow finally back home
[12:36] <MidMark> hi, just two mistakes in the beta2 backport news:
[12:36] <MidMark> 1) Install kdebase-workspace (this has changed since beta 1) -> package not present
[12:37] <stdin> yes it is :)
[12:37] <MidMark> ops sorry
[12:37] <MidMark> my fault
[12:37] <stdin> it took a while to get out, but it should be there now
[12:38] <MidMark> probably yesterday wasn't present?
[12:39] <MidMark> mmm
[12:39] <stdin> no it was still getting built then
[12:39] <MidMark> trying to install it, adept says there are some brackage
[12:39] <MidMark> breakage
[12:40] <stdin> make sure you're installing version 3.93.0-0ubuntu2~feisty3