/srv/irclogs.ubuntu.com/2009/02/12/#ubuntu-desktop.txt

pittiGood morning07:18
didrocksmorning pitti07:49
=== tkamppeter__ is now known as tkamppeter
crevettehello08:17
didrocksHi seb128, crevette08:25
crevettesalut didrocks08:25
seb128lut crevette didrocks08:25
didrocksseb128: gtkmm2.4 is ready (https://bugs.edge.launchpad.net/ubuntu/+source/gtkmm2.4/+bug/328251)08:25
crevettesalut seb128 & andreasn08:25
ubottuUbuntu bug 328251 in gtkmm2.4 "Please, sponsor gtkmm2.4 2.15.3 for jaunty" [Undecided,Confirmed]08:25
andreasnhallo crevette08:25
seb128didrocks: good thanks08:25
crevettedidrocks is already on the run08:25
didrocksbut has gnome-python, it doesn't show up in dholbach page08:26
seb128ok08:26
crevetteseb128: you can "apt-get install nautilus-sendto-universe" now :) thanks for driving me08:26
didrocks(indeed, it show in "The following bugs have not been parsed")08:26
seb128I'm not sure we want to use bzr for this one08:26
didrocksseb128: really?08:26
seb128crevette: you're welcome08:27
seb128didrocks: well, gtkmm2.4 is often in sync with debian so I'm not sure how to manage that and keep the bzr uptodate, that seems extra work rather than win08:27
didrocksseb128: ok :)08:27
seb128didrocks: let me talk to mvo when he will be around08:27
mvohm?08:28
didrocksseb128: ok. So, I have only python-gnome-extras waiting for libgda08:28
seb128crevette: was that bug #327747?08:28
ubottuLaunchpad bug 327747 in nautilus-sendto "Please promote new package "nautilus-sendto-universe" to universe" [Undecided,Fix released] https://launchpad.net/bugs/32774708:28
didrocksand nothing else to do o/08:28
crevetteseb128: yes08:28
seb128mvo: didrocks is putting everything in bzr nowadays thanks to your guidance ;-)08:28
didrocks(pidgin has been taken by alessio)08:28
mvoheh :)08:28
seb128didrocks: ok08:28
crevetteseb128: oups I didn't read that last comment08:28
mvoI like that08:29
crevetteseb128: I hope this is a type08:29
crevettetypo08:29
seb128mvo: but gtkmm2.4 is often in sync with debian, not sure how to keep bzr uptodate in such case, that seems rather extra work08:29
seb128crevette: I think that's a bug triager closing the bug wrongly, let me reopen08:29
seb128crevette: the bug should not be on nautilus-sendto but on ubuntu08:29
crevetteah I didn't know08:29
mvoseb128: hm, good point. when its in sync with debian it will not have a vcs-bzr header, and when we de-sync it, we can do that from the bzr tree. but its a bit ugly to keep the tree around when its not up-tp-date08:30
mvoOTOH this way we will have full ubuntu changelogs08:30
mvo(something I sometimes miss)08:30
seb128what do you mean by full changelog?08:31
didrocksthat's right that the vcs-bzr header can be an issue :/08:31
seb128there is no ubuntu change, we are just sometime faster to package unstable versions08:31
crevetteneed to go08:31
crevettebye08:31
mvoseb128: hm, right08:33
seb128didrocks: can you drop the vcs-bzr line in control? we will just upload, using bzr is just extra work there, we will likely be using the debian again in next versions08:34
didrocksseb128: sure08:34
didrocksseb128: do you I put a debdiff?08:35
didrocks(so, I think I have to revert the debian/watch change)08:35
seb128didrocks: you can use your bzr, I will use if for sponsoring but just not push that to the ubuntu-desktop codepage08:35
seb128didrocks: the watch file is no issue08:36
seb128just let's not bother with bzr there08:36
didrocksok, thanks, it will be easier for me with push/pull :)08:36
didrocksok08:36
seb128vuntz: there?08:44
seb128vuntz: are you running gtk 2.15.n?08:44
didrocksseb128: done, rev 3 pushed08:49
asacmvo: see msg10:02
* huats notices that seb128 is on "clear gnome-keyring bugs" mode 10:06
huats:)10:06
seb128huats: yeah, you are welcome to do that too if you want ;-)10:06
huats:)10:06
seb128not on gnome-keyring though since it's mostly cleaned now10:07
huatsI am a bit on a rush at the moment for my day work10:07
huatsbut I wll try to help outĀµ...10:07
seb128no hurry you already did a lot recently10:07
didrocksseb128: if you have something that I can handle, it will be with pleasure :)10:18
seb128didrocks: http://download.gnome.org/sources/gnome-icon-theme/2.25/gnome-icon-theme-2.25.90.tar.gz10:18
seb128didrocks: http://download.gnome.org/sources/seahorse-plugins/2.25/seahorse-plugins-2.25.90.tar.gz10:19
didrocksseb128: ok, I take them :)10:19
seb128cool10:19
didrocksseb128: I checked withc check-symbols the ABI differences in gtkmm2.410:20
didrocksseb128: there is only added symbols, so, it's ok, but I wonder why all libraries still have the same name *.1.0.3010:21
didrocksand not bump a minor version like *.1.0.3110:21
seb128because upstream didn't upgrade the number correctly10:21
didrocks(without changing the SONAME as there is no ABI breakage)10:21
seb128that should not make a real difference though10:21
didrocksok, but theorically, this change has to be done, right?10:22
didrocksis it this? change the minor revision?10:22
seb128right10:22
didrocksit was just to confirm ^^ thanks10:22
mvoseb128: hi, how is compiz behaving today?10:58
seb128mvo: hello, not, I'm on my desktop right now which has a recent ati card and doesn't work on compiz10:59
seb128mvo: I will try again the laptop later and let you know11:00
mvoseb128: aha, no problem11:00
seb128mvo: you don't get the issue by running gnome-screenshot?11:00
mvoseb128: no :/11:00
seb128you have a tasklist and use the option to list only things on the current workspace?11:00
seb128it's weird it was doing it for evolution and gnome-screenshot for example11:01
seb128but not for gedit, xchat-gnome, etc11:01
seb128didrocks: ups, there was a bug in your gtkmm update11:01
seb128didrocks: SHVER in rules should be updated to 2.15.3 since there is new functions in this version11:02
mvoseb128: I tried it with evo and gnome-screenshot and the "workspace switcher" and the tasklist show them only on the current one11:02
seb128the workspace switcher and alt tab are not issue11:03
seb128that's the flat list of tasks which was11:03
seb128anyway will try a bit later and let you know11:03
mvoseb128: "window list" and "show windows from current workspaces=yes" - looks ok for me, when I switch its gone from the window list11:04
mvoseb128: let me check if I have the latest gnome panel applets11:05
seb128those didn't change recently11:05
asacmvo: did you figure how to enable NM system connections in upgrade tester?11:41
asacor do you need more info?11:41
mvoasac: not yet, sorry. need to get back to this11:49
seb128mvo: the synaptic quick search thing is not really smart11:50
mvoasac: how can I detect if its restarted? do I need some sort of monitoring process?11:50
mvoseb128: no?11:50
seb128I guess that's a known issue?11:50
seb128mvo: well it tends to list lot of things which don't match the filter, or it tries to be too smart and match in depends and descriptions too and score that quite high11:52
mvoseb128: what search did you do that was not good?11:53
seb128mvo: try typing gnome-applets in the entry11:53
seb128gnome-applets-data is listed first11:54
seb128gnome-applets is several screens after that11:54
seb128it lists11:54
seb128gnome-applets-data11:54
seb128capplets-data11:54
seb128bluez-gnome11:54
seb128etc etc etc11:54
seb128and then gnome-applets11:54
mvoseb128: yeah, I see the same here, I have a look, its xapian smartness, the amount of influcence I have is not that great into the scoring11:55
seb128mvo: usually have the exact name match first would be cool ;-)11:55
seb128having11:55
seb128or that's what I would expect when I type a binary name correctly11:55
seb128do you want a bug about that?11:56
mvoyep11:56
seb128it's a detail probably not worth the trouble11:57
seb128I was just pointing it in case you were interested ;-)11:57
didrocksseb128: you're right. I didn't checked what it is used for. New version pushed11:58
seb128didrocks: you need to update the changelog to 0ubuntu2 I did sponsor the previous revision a bit quickly, did test build, install, try gnome-system-monitor and upload11:59
didrocksoh crap12:00
seb128ie, you can't reupload using the same number12:00
didrocksok12:00
didrocksI didn't see you uploaded a new version12:00
didrockssorry for that12:01
didrockshow did you see that, for information?12:01
seb128didrocks: see what?12:01
seb128didrocks: I didn't upload a new version, I just sponsored your update12:02
didrocksthat I forgot to change this value, afterwards12:02
seb128I did bzr diff to see what you did exactly12:02
didrocksbecause once sponsored, I think you don't look at the rules file :)12:02
seb128as said I did sponsor too quickly, I just test built and uploaded12:03
seb128then I went "ups, maybe I should review the changes too"12:03
didrocksyes yes, but how did you see the mistake, once sponsored?12:03
didrocksok12:03
seb128that's what you get after sponsoring some good work ;-)12:03
seb128you just trust the updater ;-)12:03
didrockssorry for the mistake, I should have looked at the rules file :/12:03
didrocksnext time, I will grep for version, to be sure :)12:04
seb128that's just a small mistake, but since you told me they added functions but didn't change the soname I decided to check that you updates the shver12:04
seb128well, new function = shlibs update12:04
seb128it can be a .shlibs or in the rules12:04
didrocksok, I just looked for .shlibs :/12:05
vuntzseb128: gtk 2.15.n: yes, partly (didn't log out)12:05
didrocksseb128: so, rev 5 is pushed12:05
asacseb128: hmm yesterdays seahorse (ssh agent) has issues?12:05
asacslogin senica -lalex12:06
asacbuffer_get_ret: trying to get more bytes 4 than in buffer 012:06
asacbuffer_get_int: buffer error12:06
seb128vuntz: that's ok, I don't need testing out of ubuntu after all I think ;-)12:09
seb128asac: gnome bug #57106012:09
ubottuGnome bug 571060 in keyring files "gnome-keyring-daemon makes ssh fail with DSA keys" [Major,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=57106012:09
seb128vuntz: btw since you are there, did you ever looked at vertical gnome-panel freeze when there is over 8 tasks in the list?12:10
seb128vuntz: and to the gnome-panel not matching the screen after using xrandr?12:10
vuntzseb128: hrm, no12:10
vuntzdidn't know about the second issue12:10
seb128vuntz: try switching to a lower resolution using xrandr and back to your current one12:10
asacseb128: thanks. CCed me12:11
seb128vuntz: and let me know if it goes back to the correct value12:11
seb128asac: you use a dsa key right?12:11
vuntzseb128: why do you always ask me to test stuff that will break my config?12:11
* vuntz tries in xephyr12:11
seb128vuntz: that will not break, just restart gnome-panel12:12
asacseb128: i dont use it, but i have a key still yes.12:12
seb128asac: try moving it somewhere else?12:12
seb128didrocks: you did change the timestamp of the previous changelog entry, can you revert to the correct value? ;-)12:13
vuntzseb128: definitely works in xephyr12:13
vuntzseb128: can you try there?12:13
asacseb128: i think i have to relogin ... let me check12:14
asac(now getting wierd "cannot sign error")12:14
seb128asac: otherwise you can workaround by using ssh agent12:14
didrocksseb128: of course, I can do. For information, why is this really important for some automation tools)?12:14
didrocksor just for consistency?12:14
seb128just export SSH_AUTH_SOCK= to the ssh-agent socket and ssh-add12:14
seb128didrocks: for consistency, no reason to change things in the previous revision12:15
asacseb128: well so seems we have a dejavu ;)12:15
seb128didrocks: you usually try to not change things which have already been uploaded12:15
asaci removed my dsa stuff .... relogged in12:15
asacnow i get:12:15
asacAgent admitted failure to sign using the key.12:15
asacPermission denied (publickey).12:15
asacthats the error i had in intrepid for quite a while ;)12:15
didrocksseb128: some kind of "don't change the past", ok :)12:15
seb128asac: well to gnome bug #57142212:16
ubottuGnome bug 571422 in keyring files "ssh agent stopped working after 2.25.90 upgrade" [Normal,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=57142212:16
seb128asac: btw I opened gnome bug #571423 too for you12:16
ubottuGnome bug 571423 in ask dialog "grabbing the keyboard while a menu is open can lock the session" [Normal,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=57142312:16
seb128didrocks: right12:16
asacseb128: cool. could you reproduce outside of NM?12:17
seb128asac: I could, that's not trivial though (need to write some code to trigger that I guess) and I'm working on other things right now, will try later12:18
seb128vuntz: ups sorry, busy replying to other people, how do I use xephyr? I'm using this new gdm which has no gdmflexiserver --xnest on this box12:18
asacseb128: sorry "could" wasnt clear. i asked whether you reproduced it already. dont need to try for now12:18
seb128asac: no, I didn't try but I figured that letting upstream know about the issue can't hurt12:19
seb128if they don't do anything about it that will make no change12:19
seb128if they know what is wrong and fix it that's a win for everybody ;-)12:19
vuntzseb128: launch Xephyr :1 -ac -br -screen 1024x76812:20
vuntzseb128: and then DISPLAY=:1 gnome-session12:20
didrocksseb128: hopefully, commit 6 will be the right one :)12:21
seb128vuntz: no I don't get the issue in xephyr12:23
seb128didrocks: uploaded12:27
vuntzseb128: ah, interesting.12:29
vuntzseb128: intel driver?12:29
seb128vuntz: yes12:29
seb128well I got the issue during the sprint on my laptop which is intel12:29
seb128I'm on my desktop right now which is ati12:29
didrocksseb128: thanks seb :)12:30
seb128let me try in my session12:30
vuntzseb128: can you reproduce with ati?12:30
* vuntz is pretty sure it's one intel driver bug12:30
seb128I don't get it12:30
seb128ok, why would the driver create the issue?12:30
seb128some xevent not triggered?12:30
seb128compiz gets confused too on that box, it consider the screen limits to be where they were before the xrandr switch12:31
seb128bryce: ^ iz intel bog?12:31
vuntzseb128: http://bugzilla.gnome.org/show_bug.cgi?id=52340812:31
ubottuGnome bug 523408 in gdk "Xinerarama code needs to sanitize overlapping monitors" [Normal,New]12:31
vuntzseb128: my guess12:31
seb128vuntz: ok thanks12:31
vuntzmetacity works because we fixed it, iirc ;-)12:32
seb128mvo: fix compiz!12:33
mvoseb128: its not broken ;)12:33
seb128vuntz: but that bug would also make gnome-panel being wrongly fit for the screen on normal session not only after xrandr changes no?12:33
seb128vuntz: we had bugs were people have an output enable and it's broken all the time for them I think12:34
seb128vuntz: where the xrand bug is only after switching modes, or that trigger the vga by some way but calling xrand doesn't list the vga as being enabled12:34
seb128mvo: do you have intel video cards? ;-)12:34
mvoseb128: I can get hold of a machine with hintel12:35
seb128mvo: don't bother, I was just curious to know if you were getting the issue too there12:35
vuntzseb128: I don't know what's wrong. I just know that it's likely not a panel bug ;-)12:36
seb128vuntz: it seems weird to me that the bug is an xorg one since restarting gnome-panel makes it work correctly12:36
seb128vuntz: why would it behave correctly after a restart if xorg was reporting wrong informations?12:37
seb128that's not consistent, it seems that it rather doesn't detect that xrandr has been used and that it should refresh the screen infos or something12:37
seb128vuntz: other small thing, do you get the clock tooltip displayed on the other side of the screen when clicking on the clock applet to display the calendar?12:39
vuntzseb128: got a report of this. And then the guy told me it happened in evo too. So gtk+ bug :-)12:40
seb128ok what I was assuming, gnome-panel didn't change a lot this cycle12:40
vuntzseb128: if it doesn't work in compiz, is it really a panel bug? ;-)12:40
vuntzoh, it did have some change12:40
vuntznot for this kind of stuff12:40
seb128vuntz: compiz can be buggy too ;-)12:41
seb128vuntz: I'm just wondering what layer in xorg is wrong12:41
seb128because as said restart gnome-panel works12:41
seb128which means there is a way to get correct informations from xorg12:41
seb128so I'm wondering if there is some sort of update signal that should be sent and is not12:41
seb128or something around those lines12:42
seb128if I can get details I can try to ping bryce about the issue12:42
vuntzseb128: the panel gets a signal from gtk+, fwiw12:44
vuntzso if there's someone to blame it's between xorg and gtk+12:44
seb128ok12:44
seb128so either it doesn't get the signal12:45
seb128or the geometry query is not correct12:45
seb128I tend to lean toward a driver bug too if that's intel specific12:45
seb128vuntz: thanks for the informations there ;-)12:45
seb128vuntz: other quick question, do you know if something started looking at why the gnome-session dialog are not themed in the current 2.25 version?12:48
seb128vuntz: I might try to look at this afternoon if nobody else is on it yet12:48
vuntzseb128: didn't look at it, but I was wondering if this was because of g-s-d is launched12:49
vuntz"how g-s-d..."12:49
seb128well xsettings should apply dynamically12:49
seb128starting gnome-settings-daemon manually after the session doesn't workaround the issue12:50
seb128the settings apply to normal gtk applications but not to gnome-session12:50
vuntzseb128: right, but something changed12:51
vuntzand I'm not sure what it could be :-)12:51
* seb128 grrrrs a no gnome-session-remove in the rewrite12:53
seb128a-> at12:53
crevetteyeah I was unable to remove nautilus yesterday from the session to test something,12:57
vuntzit's quite easy to remove apps13:05
vuntzpkill $app; pkill $app; pkill $app; etc.13:05
mvowhile true; do pill $app; done ;) ?13:07
vuntzmvo: that's advanced shell usage. I'm not that clever13:07
mvolol13:07
pochubash: pill: command not found13:09
pochu:)13:09
* mvo can do shell, but he can not type!13:10
seb128vuntz: gnome-session respawn those automatically though13:11
seb128vuntz: ie nautilus13:11
seb128brb13:12
dholbachhello my desktop friends13:13
* pochu waves at dholbach :)13:14
dholbachcan somebody tell me how I can debug what's happening with my ssh connection13:14
dholbach?13:14
dholbachI have a hunch that something's wrong with seahorse or something13:14
dholbachssh -v  gives me "Agent admitted failure to sign using the key"13:15
emberhttp://bugzilla.gnome.org/show_bug.cgi?id=57142213:16
ubottuGnome bug 571422 in keyring files "ssh agent stopped working after 2.25.90 upgrade" [Normal,Unconfirmed]13:16
dholbachthanks a bunch ember13:16
dholbachstrangely enough it still works on my i38613:16
dholbachjust not on my amd6413:16
* ember hugs dholbach13:16
rickspencer3asac: ping13:17
asacrickspencer3: pong13:17
rickspencer3asac: msg?13:17
dholbachember: followed up on the bug13:18
dholbachmuchas gracias13:18
dholbachwhen I log into my amd64 from the i386, I can still ssh without problems13:18
dholbachmakes using bzr a bit of a pain13:18
* dholbach hugs seb12813:19
seb128dholbach: what?13:19
* seb128 hugs dholbach13:19
seb128dholbach: use ssh-add13:19
dholbachseb128: talking about gnome bug 57142213:19
ubottuGnome bug 571422 in keyring files "ssh agent stopped working after 2.25.90 upgrade" [Normal,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=57142213:19
seb128right13:19
dholbachother than that... how's the desktop world ticking along? all good?13:19
seb128set SSH_AUTH_SOCK= to the ssh-... directory13:20
seb128and use ssh-add13:20
seb128yes, we are mostly uptodate and not too buggy ;-)13:20
seb128and how is the community world?13:20
dholbachbusy, busy as always13:20
seb128the sponsoring queue seems reasonable again now13:20
dholbachtoday's loco docs day13:20
dholbachseb128: main yes, universe not yet :)13:21
dholbachbut a lot of people put some more effort into it, which is nice13:21
seb128I was pondering doing some work there or letting motu clean it13:21
dholbachif you see something interesting and have a little bit of time, consider doing it :)13:21
dholbachit makes me a happy man :)13:21
dholbachnot only you, but everybody else too13:21
* huats hugs seb128 and dholbach (advantage of having long arm)13:22
dholbachhiya huats13:22
dholbachhaha13:22
dholbacha lot of people put good efforts into merging important fixes from debian which is fantastic13:22
* dholbach is happy with the new people in MOTU land13:22
seb128dholbach: let's wait for tomorrow13:22
seb128then huats and didrocks can clean the universe sponsoring list ;-)13:23
* dholbach goes back to 5aday-automation :)13:23
dholbachhaha13:23
dholbachexactly13:23
huats;)13:23
dholbachthe French mafia13:23
huatswell13:23
didrocksseb128: :p13:23
huatsi am sure didrocks and I will be happy to help13:23
huats:)13:23
didrocksfor sure13:23
huats(but before there is the MC :))13:23
didrocks(and to have to wake up early, hey huats ;))13:24
dholbachyes, and as it's going to be 7:00 UTC and everybody will be grumpy, we'll grill you properly13:24
huatsbtw dholbach in the new process, do we need to prepare anything ?13:24
seb128;-)13:24
huatsI am sure you will dholbach13:24
didrocksgreat \o/13:24
seb128dholbach: do I need to be there?13:24
didrocksI love to be grilled ;)13:24
dholbachno, you guys sent in good applications, you're fine13:24
dholbachseb128: no13:24
seb128cool13:24
huatsusually I am the cooker :)13:24
seb128it's way too early ;-)13:24
huatsseb128:  lucky you :)13:25
didrocksseb128: lucky man, you can sleep during this time :)13:25
huatsseb128: if you want we can give you wake up call ;)13:25
dholbachseb128: so you prefer writing a bit more text on the application to getting up early for a meeting? :)))13:25
seb128vuntz: I found the commit which broke the gnome-session theming13:25
dholbachhiya vuntz!13:25
* seb128 hugs dholbach13:25
huatspochu: I sent you the check-symbol stuff13:26
dholbachI see... lots of stuff going on in Desktop land13:26
dholbachrickspencer3: you have a great community in here! :-)13:26
didrockshuats: you have to explain me again what you added, because I used the old one yesterday ;)13:26
huatsdidrocks: the idea, with my stuff13:26
rickspencer3dholbach: there is a great community here, yes13:26
huatsis that you can run it on your intrepid, even to test a jaunty stuff13:27
dholbachrock on my desktop friends and thanks again for the pointer for the broken seahorse13:27
rickspencer3but I think I don't think it's mine :) I think I joined a great community ;)13:27
didrockshuats: using pbuilder login (I was thinking about using this trick)13:27
vuntzseb128: oh, cool. Which one?13:27
didrocksdholbach: see you tomorrow :)13:27
dholbachdidrocks: yeah :)13:27
seb128vuntz: 5192 and 5193, ie the one which added the presence api13:28
pochuhuats: thanks! I'll look at it later :)13:29
huatsdidrocks: it is a possibility also13:29
seb128vuntz: not a small commit, trying to figure what is creating the issue there13:31
emberis anybody working on tracker? mvo or pochu perhaps?13:41
mvonot me13:41
pochuember: not me either, feel free to do the merge ;)13:41
emberhmm ok i will have a look13:42
emberbtw mvo thanks for gtsharp2 it was blocking tomboy13:42
mvoember: thank you work doing the update13:45
huatsseb128: I am testing the gnome-doc-utils update... the documentation created by it, is the one used by yelp right ?14:08
seb128huats: correct14:08
seb128hey hggdh14:08
huatsseb128: ok great14:09
huats:)14:09
seb128hggdh: there?14:21
hggdhseb128, yes14:27
hggdhhi14:27
seb128hggdh: so if you run seahorse, go to the password tab it's empty?14:28
seb128you don't have default or login lines?14:28
hggdhseb128, no, no keyring lines at all14:29
seb128and nothing typed in the filter there?14:29
hggdhnope14:29
seb128weird14:29
seb128so your bug is basically similar to bug #327481?14:29
ubottuLaunchpad bug 327481 in seahorse "seahorse does not display passwords from login.keyring" [Low,Incomplete] https://launchpad.net/bugs/32748114:29
hggdhlooking it up14:30
hggdhseb128, indeed. File/New/Password Keyring does not do anything14:30
hggdhso mine can be set as a dup of this one14:31
seb128ok, doing that14:31
seb128the new doing nothing is yet another issue14:31
seb128seahorse lists my keyrings and password correctly but new doesn't do anything there14:31
hggdhah14:31
seb128perhaps you could open the bug on bugzilla since you get the issue?14:32
hggdhyes, will do14:32
seb128it's working for me so I can't reply to the upstream questions if there is any there14:32
seb128thanks14:32
hggdhseb128, welcome14:32
mclasenfile/new/ssh is bizarre14:33
hggdh?14:34
mclasenthat help button is really misplaced14:34
hggdhoh14:35
hggdhperhaps a new bug on it would be good14:35
bryceseb128: re the panel bug, it'd be helpful to have a simple test case to demonstrate the issue.  Offhand it's not obvious to me at what level the breakage could be happening.15:35
seb128bryce: if you read the discussion it's not obvious to me either ;-)15:35
seb128bryce: but I don't get the issue in xephyr or using an ati driver15:35
bryceseb128: the patch by federico sounds like it is against Xinerama rather than Xrandr, and in reading it I'm not sure it would solve the problem.  Good to have for reference just in case though.15:35
seb128right I don't think that's the exact same issue15:36
seb128but gtk and gnome-panel don't change between those installations and the issue seems to be intel specific15:36
seb128so xorg behaves differently on intel in some way15:36
brycemm15:36
seb128compiz is buggy on intel too btw15:37
vuntzbryce: I think you should blame seb128. It's the easy way, really15:37
bryceintel is buggy too all by itself ;-)15:37
bryceanyway, if we have steps to reproduce, I can push it upstream as an -intel bug and see what happens15:38
brycethey're pretty responsive, including if it's an xserver bug rather than -intel15:38
brycemy worry is that it's going to be more of an xrandr protocol level issue... like some functionality not yet provided for setting/getting the primary display15:39
brycewhich would be tough to get a fix for15:39
brycebut if it is confirmed to work on -ati, then that suggests it's not a protocol issue15:39
seb128well at least we would know what the issue is15:39
bryceright15:39
seb128well, it works fine on ati and xephyr for me15:39
seb128and vuntz suggested from start that would be an intel bug15:40
brycedid you also reproduce without xephyr?15:40
seb128no, only on intel15:41
seb128ati and xephyr work fine15:41
bryceis there a bug id#?  And steps to reproduce written down?15:41
seb128let me look, I did got a lot of comment about that during the sprint15:43
seb128bug #325800 that you open is around those lines but slightly different15:43
ubottuLaunchpad bug 325800 in gnome-panel "On EeePC panel will not resize correctly after external monitor disconnected" [Undecided,New] https://launchpad.net/bugs/32580015:43
bryceyeah might be related but not the exact issue15:46
brycefwiw that is davidm's eeepc that he has promised to help do testing with15:46
seb128bryce: ok, no bug that I can found describing the issue, I will try to debug a bit and open one later15:53
rickspencer3bryce: https://bugs.edge.launchpad.net/xorg-server/+bug/32717515:53
ubottuUbuntu bug 327175 in xorg-server "Sometimes loses input devices on suspend/resume: Device has changed - disabling." [Unknown,Confirmed]15:53
bryceexcellent; subscribe me to it once it's open15:53
seb128ok15:54
seb128brb doing a new bootchart15:54
andreasnmpt, ping16:16
seb128vuntz: btw, http://bugzilla.gnome.org/show_bug.cgi?id=57076517:29
ubottuGnome bug 570765 in Calendar "gnome panel hangs after clicked on the clock applet" [Critical,Unconfirmed]17:29
seb128vuntz: you were asking for a stacktrace of clock applet hanging gnome-panel in 2.2517:30
vuntzseb128: added a comment17:34
seb128vuntz: thanks ;-)17:35
seb128vuntz: it does happen with 2.25.9017:35
vuntzah. Well. No luck. I blame eds17:36
seb128well, e-d-s is likely crashing17:38
seb128still the clock should not hang17:38
crevetteI did had this bug yesterday evening I guess17:42
=== asac_ is now known as asac
mvoseb128: let me know when you are close to your laptop again (no rush), I have a theory about the compiz bugs you mentioned the other day17:48
seb128mvo: ok, that will probably be in 15 minutes but I'll not be around it for long tonight since I go to sport soon after that, other that's for tomorrow17:49
seb128mvo: do you want me to try something?17:49
seb128ups17:49
mvoseb128: just a gconf dump of your plugin settings17:49
seb128ok17:49
mvo /apps/compiz/general/allscreens/options/active_plugins17:49
mvothat is all I need17:49
seb128that's probably the default set17:49
seb128or rather select normal in the appareance capplet17:50
mvoI think that the crucial bit, it seems like there is some reordering going on and that makde the default not the gconf default17:50
seb128I did that after the abi breakage issue17:50
mvoand to confirm I want to see yours :)17:50
seb128ok17:50
vuntzseb128: hope your question in the bug is not for me ;-)17:52
seb128vuntz: you or mbarnes whoever want to reply17:52
=== asac_ is now known as asac
seb128time for sport and dinner bbl17:57
=== spinus_ is now known as Spinus
=== Spinus is now known as Spinus_
mvomaxb: you had the compiz issues with gnomecompat too, right? is your system still in this state? if so, I would like to ask for debugging help :)18:47
maxbmvo: Hi, just saw bugmail. Is your info request still useful after I've manually ticked the gnomecompat plugin on?20:31
mvomaxb: I guess, please put it into the report that you did that :)20:33
mvomaxb: a vanialla one would be better, but I'm sure I find someone with one (or I can try to reproduce it with some livecd magic)20:33
mvomaxb: I have a theory about the problem at least20:33
maxbHmm.. I'm reading the debdiff now.... won't that solution fail if the user has played around in ccsm at all?20:34
maxbw.r.t. the addition of "gnome-terminal" as the terminal command line (in the debdiff) - somehow it was figuring that out anyway - my problem turned out to be that the gnomecompat plugin defaults the "terminal" keybinding to disabled20:37
maxbHmm... So gnome-keybinding-properties syncs the settings it makes into compiz's gconf area?20:56
=== Guest65438 is now known as mxab
=== mxab is now known as maxb

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!