/srv/irclogs.ubuntu.com/2014/04/04/#ubuntu-desktop.txt

jdstrandman, I just rebooted after accumulating a bunch of updates, and 3D performance is really poor with my intel graphics00:55
jdstrandeg, just opening the dash is really bad00:55
jdstrandinteresting, .xsession-errors says: libGL error: failed to open drm device: Permission denied00:56
jdstrandlibGL error: failed to load driver: i96500:56
jdstrandI'm guessing that would explain it00:56
sarnoldpermission denied? o_O00:56
* jdstrand guesses it is the mesa update00:59
mdeslaurjdstrand: you're supposed to do what everyone else does and blame apparmor first :)00:59
jdstrandhehe01:00
jdstrandI don't confine compiz or X01:00
jdstrandI probably should :P01:00
mdeslaurthen you fall back to blaming upstart :)01:00
jdstrand:)01:00
jpdshttp://i.qkme.me/3trz9o.jpg01:01
mdeslaurhehe01:01
jdstrandhehehe01:01
jdstrandnice01:01
jdstrandperfect picture01:01
sarnold:D01:02
=== thumper-gym is now known as thumper
jdstrandfyi, bug #130227001:15
ubot2Launchpad bug 1302270 in xorg (Ubuntu) "Poor performance with recent update with i965: libGL error: failed to open drm device: Permission denied" [Undecided,New] https://launchpad.net/bugs/130227001:15
Sarvattjdstrand: your xorg.0.log is fine and from a recent boot but the xorg.0.log.old is using modesetting instead of intel and X was started again really late, guess you rebooted before filing it? all the dmesg info that might have helped was lost, might be worth attaching /var/log/kern.log that has the historical info02:36
Sarvatttjaalton: ping re: ^, arrandale and might be the mesa 10.1 bug you were talking about02:45
jdstrandSarvatt: I did not reboot before filing. I logged in, noticed it, made a comment here, did ubuntu-bug and am still running it02:52
* jdstrand is testing a bunch of stuff and can't really downgrade/etc atm02:52
jdstrandI don't know about the modesetting... I don't recall messing with anything like that in ages and ages02:53
jdstrandmaybe I did at some point...02:53
Sarvattjdstrand: using kde? i think it might be https://bugs.freedesktop.org/show_bug.cgi?id=7572302:54
ubot2Freedesktop bug 75723 in Drivers/DRI/i965 "(regression since Linux 3.14?) brw_get_graphics_reset_status: Assertion `brw->hw_ctx != ((void *)0)' failed" [Major,New]02:54
jdstrandSarvatt: unity702:54
Sarvattah02:54
jdstrandI hadn't rebooted in several days at least, but had been upgrading all along02:55
jdstrandso I can't really pin point it02:55
jdstrandis any of this interesting:02:55
jdstrand[    1.716252] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver02:55
jdstrand[    1.815666] fbcon: inteldrmfb (fb0) is primary device02:55
jdstrand[    2.335498] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device02:55
jdstrand[    2.342002] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 002:55
jdstrandI have 965, but I can't remember if ^ is normal02:56
Sarvattyeah thats normal02:56
jdstrandI figured I'd downgrade mesa when I had a chance02:56
Sarvattyour https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1302270/+attachment/4064372/+files/XorgLogOld.txt looks bad but the current one looks fine..02:57
ubot2Launchpad bug 1302270 in xorg (Ubuntu) "Poor performance with recent update with i965: libGL error: failed to open drm device: Permission denied" [Undecided,New]02:57
jdstrandthat's weird02:57
jdstrandI'm still in the affected session02:59
dufluSarvatt: Same issue with being stuck in software rendering for me today :( Permissions are broken for both DRM and my software config too (I can't change servers any more)03:06
RAOFduflu:03:14
RAOFduflu: Fallout from the systemd upload?03:14
stgrabertoday's changes to systemd shouldn't cause anything like that, though the upgrade may restart logind which if it can't read its state properly could cause this... in theory switching VTs may do the trick, otherwise logging out and back in should (or just reboot if you're in a hurry).03:17
dufluRAOF: I spy more (older duplicates). It's not specific to Intel graphics. But whatever sets the seat permissions isn't working (randomly)03:18
jdstrandSarvatt: fyi, https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1302270/comments/403:18
ubot2Launchpad bug 1302270 in xorg (Ubuntu) "[regression] Poor performance with recent update with i965: libGL error: failed to open drm device: Permission denied" [High,Confirmed]03:18
dufluAlso affects nouveau and my ability to change apt configs03:18
jdstrandseems duflu came upon it03:18
* duflu goes to link up the dupes03:18
jdstrandif I add myself to the video group, it works-- so yeah, something changed with the perms03:18
dufluMaybe I won't link the dupes. But it seems to be a common problem with getting permissions (nouveau too)03:21
dufluRAOF: Yeah looking at the updates I got today, only systemd starts out as suspicious03:24
RAOFsystemd or cgroupmgr would be my high-suspicion targets.03:25
dufluOh and libudev-dev03:25
dufluudev even03:25
dufluOh, udev comes from source "systemd"03:27
RAOFIndeed it does.03:27
dufluYes! I reverted all the systemd packages from today's update and it's fixed03:30
stgraberquick heads up, the last systemd change indeed causing this for machines without cgmanager due to extra error processing code which wasn't needed and caused an assert...04:18
stgraberjdstrand is testing fixed packages, if those work, I'll push in the archive very soon04:18
stgraberpeople affected may need to manually start logind after the update (not entirely clear if it'll do that on its own if it crashed before...)04:19
hikikohello06:52
hikikoLaney, hi :) could you get a look at this branch: https://code.launchpad.net/~hikiko/unity-control-center/unity-control-center.clamp-ui-scale/+merge/21401906:55
hikikoit clamps the ui scale to a value at which the slider will remain visible06:56
dholbachhiya06:57
dholbachare things funny for anyone else on 14.04 today?06:57
dholbachI seem to have no audio interface, just a "dummy interface"06:57
dholbachand every now and then compiz is using 200% cpu06:57
sarnolddholbach: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/130226406:58
ubot2Launchpad bug 1302264 in systemd (Ubuntu) "systemd-logind assert failure: error.c:319: Assertion failed in nih_error_get: context_stack != NULL" [Critical,Fix released]06:58
hikikodholbach, I dist-upgraded a while ago and the only "strange" thing I ve noticed was some dpkg errors07:04
dholbachhikiko, I didn't see any - which ones did you see?07:06
hikikodholbach, these: http://pastebin.ubuntu.com/7202139/07:07
dholbachhikiko, looks like it's bug 130230007:08
ubot2Launchpad bug 1302300 in isc-dhcp (Ubuntu) "package isc-dhcp-client 4.2.4-7ubuntu9 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2" [Undecided,Fix released] https://launchpad.net/bugs/130230007:08
dholbachhikiko, is the situation fixed on your end already? if not, you might want to try another dist-upgrade; or run sudo dpkg --configure -a07:09
hikikono, -f didnt solve it so I guess I have to configure dpkg07:09
hikikodholbach, with dpkg --configure -a, and apt-get -f install it's not fixed so I suppose it's a bug07:12
dholbachhikiko, did you try   sudo apt-get update; sudo apt-get dist-upgrade   as well?07:13
hikikoyes07:14
dholbachmvo, ^07:14
hikikoPreparing to unpack .../isc-dhcp-client_4.2.4-7ubuntu10_amd64.deb ...07:14
hikiko/var/lib/dpkg/tmp.ci/preinst: 17: /var/lib/dpkg/tmp.ci/preinst: Syntax error: "fi" unexpected (expecting "then")07:14
hikikothere's a syntax error in the installation script07:14
dholbachmvo, do you have an idea how to recover from an issue like that if the usual tricks (dist-upgrade, dpkg --configure -a, etc.) don't work?07:14
sarnoldhikiko: you need to find a mirror that has ubuntu1107:15
dholbachahhhh ok, that makes perfect sense - thanks sarnold07:16
hikikoI changed my repositories to use ubuntu .de :)07:16
hikikolet's see if it goes away07:17
dholbachmvo, unping :)07:17
dholbachmvo, can we make "apt-get changelog <...>" act on source package names as well? :)07:22
sarnold+1 :)07:24
mvodholbach: let me look into that07:25
hikikohello07:25
sarnoldhikiko: success I hope? :)07:25
dholbachhikiko, better?07:25
hikikonoooo07:26
sarnold:(07:26
hikikowell07:26
hikikodpkg07:26
hikikodecided to remove isc-dhcp-common :D07:26
hikikoso...07:26
hikikoI cant run dhclient eth007:26
hikikoand I have no clue how to install the dhclient :p could you help me?07:27
sarnoldhikiko: check /var/cache/apt/archives/ to find an old package..07:27
hikiko:D07:27
hikikowell07:27
hikikothe archived package07:28
hikikohas the syntax error07:28
hikikoso it cant be installed07:28
sarnoldyou may have e.g. ubuntu7 or something?07:28
hikikono I ll download one07:28
hikikobut wont there be any dependency issues?07:29
hikikommm what if I download the daily build and change my sources.list to use the cd-rom to install the latest package?07:30
sarnoldooof that sounds like a lot of work :)07:30
hikikoyes :/07:30
hikikois there any easiest way to do it?07:30
sarnoldhikiko: I'd use ip or ifconfig to set an ip at random, use ip or route to add a route to your gateway, then use apt-get install isc-dhcp-whatever=specific.version.number07:32
hikikoyes!! static ip !!07:32
sarnoldhikiko: bed tie for me, good luck :)07:32
hikikothanks a lot sarnold07:33
hikikohave a good night07:33
sarnoldthanks :)07:33
czajkowskimorning07:36
hikiko just for the record I have internet with my static ip but the isc-dhcp-common cannot be installed...07:51
seb128good morning desktopers08:01
seb128hey hikiko08:01
seb128hikiko, what's the issue/error when you try to install it?08:01
hikikoline 17 in a script08:02
hikikojust a sec08:02
hikikoto switch desktop08:02
hikikoand paste it08:02
pittihey seb12808:02
seb128pitti, hey, how are you? how is IoM?08:02
pittiseb128: small, green, cold, and wet :)08:03
hikikoback :)08:03
seb128haha08:03
seb128pitti, how cold?08:03
hikikosorry there's a new error now: http://pastebin.ubuntu.com/7202265/08:03
pittiseb128: about 8 to 10 degrees..08:03
seb128brrr08:03
seb128hikiko, do you use an outdated mirror?08:04
Laneygreetings08:04
Laneyhappy friday, how did that happen so soon?08:04
seb128hikiko, current version is ubuntu11, it should fix the shell script error you had earlier08:05
seb128Laney, happy friday!08:05
hikikowhich mirror do you use in your sources.list?08:05
hikikoI used .de08:05
seb128no mirror, archive.ubuntu.com08:06
hikikook I will change it then08:06
Laneyhikiko: the idea seems reasonable08:10
CrazyLemonguys i dont know what was in todays update.. but 14.04 is barely usable for me untill i kill deja-dup-monitor .. compiz is also CPU hungry08:10
LaneyNot sure if it's arbitrary to use the current window size though08:10
hikikoLaney, seb12808:11
LaneyMaybe it could instead say 'a 640x480' (or whatever) window must fit on the screen08:11
hikikohello08:11
Laneyhey!08:11
Laneyalso can you have the same issue with the gtk values or not?08:11
hikikoI have a branch for review08:11
hikikoLaney, seb128 there was a problem with the mpt's design for u-c-c: that when a toplevel win is larger than the screen size, the window manager places it to a predefined position and ignores the program's requests08:12
hikikoso I ve done a new branch where we just clamp the values08:12
hikikohttps://code.launchpad.net/~hikiko/unity-control-center/unity-control-center.clamp-ui-scale08:12
Laneyyeah that's what I'm looking at08:12
hikikothis branch has another "issue" but bregma said it's acceptable08:13
hikikothe issue is that08:13
hikikothe window size depends on 2 parameters08:13
hikiko1- an integer scale factor08:13
hikiko2- the size of the widgets it contains that depend on their font size and number of characters etc and it's not predictable08:14
LaneyIt's why a dialog would be better, but I get that we are where we are08:15
hikikoso, since in order to clamp the slider we take the window size into account08:15
hikikofor different scale factors in gsettings08:15
hikikothe user might see the slider clamped to a different value08:15
hikikoeg: for scale factor 1, clamp=1.88 for scale factor 1.5 clamp = 1.7508:16
seb128what do you call "clamp"? you limit the max value to what would put the dialog offscreen?08:16
hikikoyes08:16
hikikonot the dialog, the u-c-c window08:16
hikikothere's no dialog08:16
seb128that's what I called dialog, sorry08:16
seb128but limiting the values range seems fine to me08:17
hikikoso, the window never exceeds the screen boundaries08:17
seb128before we landed the slider I was already suggesting to limit to 208:17
hikikobut the user might see different clamp values08:18
seb128because in practice nobody is going to want to go over 208:18
hikikowell now it's limited to 1.75-1.88 in normal screens08:18
hikikobecause in 2 it goes offline08:18
hikiko:s/offline/offscreen :p08:18
hikikosorry08:18
hikiko:)08:18
seb128that approach seems reasonable to me08:19
hikikogreat :)08:19
hikikoI just wanted to make sure08:19
hikikothat there's no problem!08:19
seb128it's a bit hackish, but that should do08:19
seb128Laney, what do you think?08:19
LaneyI was suggesting to use some reference size instead of the size of the current window08:20
Laneybut the idea is fine08:20
seb128that would work for me as well08:20
seb128seems even easier08:20
hikikowhat do you mean by reference size?08:20
seb128don't get the geometry, just a fixed value08:20
Laneylike "you can't make a 600px window go oversize"08:21
Laneyor whatever constant08:21
hikikothat's what I am doing08:21
hikikoaaa08:21
hikikono08:21
hikikowell08:21
hikikoI might not explain it well08:21
seb128you do08:22
hikikoinstead of limiting the win size to <fixed pixels>08:22
hikikoI limit it to <screen's pixels>08:22
hikikoin both cases there will be an unpredictable maximum value08:22
LaneyBut you perform your calculation based on the height of the window08:22
Laneyright?08:23
hikikono08:23
hikikowhat I do08:23
hikikois that:08:23
Laney+ gtk_window_get_size (win, &win_width, &win_height);08:23
hikikoI check that the window height08:23
hikikodoesnt exceed08:23
hikikothe screen height08:23
hikikobecause height <= width08:23
hikikoand I want the window08:23
knome(not necessarily, what about pivot setups?)08:23
hikikoto be all visible08:24
hikikoI used to choose08:24
hikikoMIN (width, height)08:24
hikikobut that was resulting08:24
knomehikiko, can you please not use enter as punctuation? it makes the text really hard to read08:24
hikikook sorry08:25
LaneyWe understand what you're doing, my suggestion is to instead say "int win_height = 600;"08:26
LaneyBut I don't think it's a big deal08:26
hikikoI see :)08:26
hikikosorry08:26
hikikoI thought you mean08:27
hikikowin_height < 60008:27
LaneyIt means you use a fixed size and say "A window of height 600px must always fit on the screen" instead of "This panel window must always fit on the screen" which you do at the minute08:27
hikikoLaney, I'll fix this right now! I just misunderstood it!08:27
hikikoyou are right :)08:28
seb128that seems a bit less "random"08:28
LaneyWell, see if it works - it'll make the code simpler08:28
hikikoyes, it's a very good idea :)08:28
Laneyseb128: can you test something for me? bdmurray said it didn't work for him but it seems to here...08:28
seb128Laney, I was just about to ask you to test something for me as well :p08:29
seb128let's trade testing!08:29
Laneywoo!08:29
seb128Laney, https://launchpad.net/~ci-train-ppa-service/+archive/landing-017/+packages08:29
seb128Laney, the url-dispatcher workaround from ted08:29
Laneyok, first try to reproduce this please https://bugs.launchpad.net/ubuntu/+source/whoopsie-preferences/+bug/126109608:29
ubot2Launchpad bug 1261096 in whoopsie-preferences (Ubuntu) "whoopsie-preferences respawns whoopsie in an infinite loop" [High,Confirmed]08:29
Laneyit's "start a-l-m → diagnostics, watch top for whoopsie-preferences/init spinning"08:29
Laneywhile I put my possible fix into a branch08:30
seb128Laney, ok, init/dbus toping08:33
seb128dbus-monitor says08:33
seb128      string "ARG0=/com/ubuntu/Upstart/jobs/startpar_2dbridge/whoopsie_2d_2dstopped"08:34
hikikoLaney, there's a define: #define MINIMUM_HEIGHT 530 because according to gnome wiki: In order to fit on Netbooks screens all panels should be 675x530px08:34
hikikomaybe I should just use this08:34
Laneyseb128: lp:~laney/whoopsie-preferences/g-spawn-sync08:36
Laneyman that guy loves doing things in upstart jobs08:38
seb128lol08:38
LaneyI'd have expected some defensive measures in the code too08:38
LaneyWith this you can still get it created with the wrong permissions, they'll just get fixed up later08:39
seb128do you want to block the landing on that?08:41
Laneylemme see what happens now08:41
seb128Laney, I don't understand your patch08:43
Laneyhttps://developer.gnome.org/glib/stable/glib-Spawning-Processes.html#g-spawn-sync08:44
LaneyI guessed that the call was going wrong because those flags weren't set08:44
* seb128 kicks google08:45
seb128Laney, first result gave me http://www.gtk.org/api/2.6/glib/glib-Spawning-Processes.html#g-spawn-sync08:45
seb128which doesn't have that note08:45
seb128also the note doesn't explain what happens when you don't use those flags08:46
seb128it feels weird it's looping on the command08:46
Laneymaybe we know a guy who knows08:46
seb128desrt, !08:46
seb128;-)08:46
seb128Laney, that branch doesn't fix it08:51
Laneyhmm ok, I didn't manage to get it again with that08:51
hikikoLaney, fixed and it works very well in my monitor :)08:52
Laneyhikiko: great08:52
seb128CrazyLemon, your deja-dup issue might be https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/130241608:52
ubot2Launchpad bug 1302416 in deja-dup (Ubuntu) "deja-dup monitor was taking 6GB of memory" [Undecided,New]08:53
CrazyLemonseb128 it might.. but there was a wide number of issues which are now gone - thankfully. I changed the server from si.archive.ubuntu.com to archive.ubuntu.com and that one had all the latest bugfixed which solved every issue.08:54
seb128good08:54
CrazyLemonis there any way i can close the bug report on LP? i opened a u-c-c bug repored and i can find the 'close' button08:55
CrazyLemoncant*08:55
seb128change the status to invalid08:56
seb128the yellow round icon next to "new" in the status column08:56
CrazyLemoni found it..thanks :)08:57
seb128Laney, things go crazy when whoopsie-preferences exit09:00
Laneyyeah I got it to happen again in the end09:01
seb128it's easy to trigger, just kill whoopsie-preference while the panel is open09:01
Laneyurl-dispatcher seems okay09:03
seb128great09:03
LaneyI didn't manage to get wrong permissions yet anyway09:03
seb128I still need to restart my session09:03
seb128to see if that fix my permissions09:04
Laneyit did for me09:06
seb128Laney, the whoopsie issue is that whoopsie_preferences_on_set_report_crashes() keeps being called in loop09:08
seb128    g_signal_connect (interface, "handle-set-report-crashes",09:08
seb128                      G_CALLBACK (whoopsie_preferences_on_set_report_crashes),09:08
seb128                      NULL);09:08
seb128hum, no09:10
dholbachhiya09:11
dholbachI don't know what just happened, but my keyboard settings changed to english on their own09:12
dholbachdo we have a bug report for that somewhere? anything I can do to debug?09:12
ochosimaybe the ibus bug?09:12
seb128dholbach, hey, we don't know either ;-)09:12
ochosithere's one we see in xubuntu where it always falls back to en_US09:12
seb128Laney, ok, I'm going to let you debug the whoopsie thing, it's weird, it seems like whoopsie-preference keeps respawning, I guess a bug in a-l-m's code09:13
seb128dholbach, did you use another session than Unity?09:13
dholbachseb128, in the settings dialog it says that I'm still on German09:13
dholbachseb128, not recently09:13
seb128I hate keyboards09:13
attente:(09:14
=== psivaa_ is now known as psivaa
ochosidholbach: https://bugs.launchpad.net/ubuntu/trusty/+source/ibus/+bug/128463509:14
ubot2Launchpad bug 1284635 in ibus (Ubuntu Trusty) "Keyboard layout changes after login" [High,Triaged]09:14
knomepossibly unrelated, but who knows09:14
seb128attente, not saying that because of you!09:15
seb128knome, ochosi: you guys are for sure nagging about that issue :p09:15
seb128dholbach, bug #1292412 as well09:15
ubot2Launchpad bug 1292412 in unity-settings-daemon (Ubuntu) "Keyboard layout is always English(!)" [Medium,Confirmed] https://launchpad.net/bugs/129241209:15
seb128dholbach, can you change back using the indicator?09:15
ochosiseb128: in all fairness, it's the first time *i* mentioned it09:15
dholbachochosi, knome: I didn't use another session and it was German up until a few minutes ago - it just changed09:15
seb128dholbach, is that a one time thing?09:15
dholbachseb128, yes, first time09:15
seb128ochosi, yeah, that's true, I included you in the xubuntu group who keeps mentioning it ;-)09:16
dholbachseb128, hum, let me see if I can re-enable the indicator somehow09:16
seb128dholbach, is unity-settings-daemon running?09:16
ochosiseb128: and i only mentioned it cause it seemed ibus related and also fell back to en_US. so i think that's not too bad ;)09:16
dholbachseb128, yes09:16
seb128dholbach, since when?09:16
seb128e.g did it segfault or something?09:16
desrtseb128: hi :)09:17
seb128desrt, hey09:17
desrtwhat am i supposed to know? :)09:17
dholbachseb128, no crash file09:17
Laneymany things, but not the thing that we thought was the thing09:17
Laneywhich turns out not to be the thing09:17
Laneyso the thing is still an unknown thing09:17
seb128desrt, what happens if you use g_spawn_sync () with  standard_output and standard_error being NULL without using  G_SPAWN_STDOUT_TO_DEV_NULL and G_SPAWN_STDERR_TO_DEV_NULL09:18
Laneybut the thing is still an interesting thing, but no longer the thing09:18
desrtthey go to the stdout/err of the parent process09:18
knomeseb128, hey, it's our best bet... :)09:18
seb128dholbach, since when is the process running (ps should tell you)09:18
seb128desrt, well anyway, that's probably not our issue, there is a command that seems to be ran in loop, Laney spotted that error and though it could be creating the bug, but that's not it09:19
dholbachseb128, which ps flag do I have to use for that_09:20
dholbach?09:20
seb128dholbach, ps ux | grep unity-settings-daemon09:20
dholbachseb128, since I rebooted the machine09:20
seb128k09:21
dholbach09:3409:21
seb128but the issue started after that?09:21
seb128attente, do we have a gsettings key or something supposed to contain the current config?09:21
dholbachseb128, yes, just 5m before I pinged you guys in here09:22
seb128dholbach, do you remember what you did just before it happened?09:22
seb128brb, need to restart my sesison09:23
attenteseb128: like under /org/gnome/desktop/input-sources?09:23
attentedholbach: are you using an ibus input method?09:24
dholbachattente, no09:25
attentedholbach: if you add a different keyboard layout and switch to that, does it still persist as en_US?09:26
dholbachattente, http://paste.ubuntu.com/7202445/09:26
dholbachok, let me trz09:26
dholbachtry09:26
dholbachattente, no, doesn't seem to have an effect09:27
attentedholbach: it just happened randomly during the session or at start up?09:27
seb128seems like a similar description to bug #129241209:28
ubot2Launchpad bug 1292412 in unity-settings-daemon (Ubuntu) "Keyboard layout is always English(!)" [Medium,Confirmed] https://launchpad.net/bugs/129241209:28
seb128attente, it happened during the session09:29
seb128attente, the "current" key should be 0 not 1 right?09:29
seb128in his dconf's pastbin09:29
dholbachattente, during the session09:29
seb128what changes that index?09:29
attenteseb128: yeah, but what flipped it09:29
dholbachdoes any log help?09:30
attenteunity-settings-daemon, indicator-keyboard09:30
seb128attente, that's a good question... is that source handled by u-s-d only, or is ibus touching it?09:30
dholbachI think I had indicator-keyboard disabled for a long time09:30
seb128dholbach, those are in .cache/upstart09:30
attentei don't think ibus is touching it09:30
dholbachcan't remember having seen it in months09:30
seb128it's not supposed to show if there is only one layout (I think)09:31
attenteit shows if there is one, but doesn't if there are none09:31
dholbachunable to create file '/home/daniel/.cache/dconf/user':09:31
seb128dholbach, can you pastebin the full logs?09:32
dholbachattente, seb128: no indicator-keyboard log09:33
dholbachhttp://paste.ubuntu.com/7202465/09:34
seb128shrug09:35
dholbach .cache/dconf was owned by root.root09:35
seb128wth?09:35
dholbachI have never touched it09:35
dholbachI'm quite certain of that09:35
seb128what was the timestamp?09:35
dholbachDec 2309:36
seb128well, dconf should use XDG_RUNTIME_DIR09:36
seb128dholbach, echo $XDG_RUNTIME_DIR09:36
dholbachI installed the machine on Dec 2209:36
dholbach /run/user/100009:36
seb128dholbach, .cache/dconf is not supposed to be used09:37
dholbachok, I just changed the permissions anyway09:38
seb128well, that's an issue but probably doesn't explain why the keymap changed during the session09:38
dholbachif you want I can restart the session again and see if that helps09:38
seb128attente, was there any debug info you wanted while in the session?09:38
seb128dholbach, can you share your dbus.log and gnome-session-Unity.log?09:39
dholbachsure09:40
dholbachseb128, dbus> http://paste.ubuntu.com/7202496/09:41
dholbachholy cow09:43
attentedholbach: sorry, what did you mean by you had indicator-keyboard disabled? like the process isn't running?09:43
dholbach94M gnome-session-Unity.log09:43
seb128dholbach, hum, don't bother about sharing that09:43
seb128dholbach, maybe clean .cache/upstart, and restart your session and let's see where we stand ;-)09:44
seb128your dconf seems unhappy though09:44
dholbachattente, /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk is running09:44
dholbachseb128, http://people.canonical.com/~dholbach/tmp/gnome-session-Unity.log.xz09:46
seb128dholbach, crazyness ;-)09:46
seb128dholbach, next clean the logs and restart session and let's see how are things09:46
dholbachseb128, you mean remove the logs?09:47
seb128dholbach, yeah, jusr mv .cache/upstart/* somewhere09:47
seb128so you are sure to have only logs about the new login09:47
seb128to avoid confusion09:47
dholbachochosi, knome: uploading xubuntu-artwork - just a small note: it's "LP: #123456", not "LP #123456@09:48
ubot2Launchpad bug 123456 in xine-lib (Ubuntu) "podcast crashes amarok" [Undecided,Fix released] https://launchpad.net/bugs/12345609:48
dholbachseb128, gotcha09:48
ochosidholbach: thanks a bunch! where's that @? just to know where to avoid typos the next time09:49
dholbachochosi, debian/changelog09:50
* knome bows09:50
ochosidholbach: weird, didn't see it here: http://bazaar.launchpad.net/~xubuntu-art/xubuntu-artwork/trusty/revision/26309:50
ochosiit says "Add new wallpaper for Trusty (LP #1298711)"09:50
ubot2Launchpad bug 1298711 in xubuntu-artwork (Ubuntu) "[UIFe] New Xubuntu wallpaper" [Undecided,Fix committed] https://launchpad.net/bugs/129871109:50
ochosior are the brackets what you shouldn't be there?09:51
dholbachochosi, the :09:52
ochosidholbach: weird, i also don't see a ":" there. are we using different char-encoding?09:53
knomeochosi, you *should* have the :09:54
dholbachseb128, .dbus and .gvfs and .config/enchant also belonged to root09:55
dholbachI changed them as well and will now move the logs and restart09:55
seb128dholbach, what did you do to your box?09:55
seb128dholbach, k09:55
dholbachseb128, as I said: fresh install before Christmas, almost no changes09:55
ochosidholbach: oh ok, sry, now i get it. will keep that in mind"09:55
dholbachI even still have the default wallpaper09:56
seb128dholbach, you must have run a graphical app under sudo that screwed up with your directories09:56
dholbachI guess09:56
dholbachbrb09:56
dholbachno dice :(09:58
seb128still buggy?09:58
dholbachthis is going to be a very long day :(09:58
dholbachyes09:59
seb128can you share your new logs?09:59
dholbachsure09:59
dholbachseb128, people.canonical.com/~dholbach/tmp/upstart.tar.xz10:00
seb128dholbach, so what is buggy? still the keyboard?10:01
dholbachseb128, yes, still English and I can't change it10:02
dholbachI added a new keyboard layout, switched back, etc10:02
seb128dholbach, is unity-settings-daemon running?10:05
seb128dholbach, $ lsof -p $(pidof unity-settings-daemon)| grep libkeyboard10:06
dholbachseb128,10:08
dholbachunity-set 2074 daniel  mem       REG                8,5    57152  791889 /usr/lib/unity-settings-daemon-1.0/libkeyboard.so10:08
seb128dholbach, can you unity-settings-daemon --replace --debug10:09
seb128then try to change keymaps using the keybinding your configured/which is listed in the keyboard settings10:09
seb128than copy the log?10:09
dholbachseb128, super+space10:11
dholbachseb128, that made it switch back10:11
dholbachmaybe I hit it accidentally?10:11
seb128well, that doesn't explain why the indicator is not working10:11
dholbachstill I should have been able to switch back, right?10:11
seb128picking a layout should work10:12
seb128does it work now?10:12
attenteis the indicator changing the dconf setting?10:12
dholbachseb128, I changed the layout in the settings page10:12
dholbachseb128, I don't have a keyboard indicator - I think I must have clicked "don't show indicator" somehwere10:12
seb128dholbach, that was not working earlier?10:12
dholbachhow can I get it to show again?10:12
dholbachseb128, changes in the settings page didn't do anything10:12
seb128it's at the bottom of the settings dialog10:12
dholbachit was just super+space which fixed it10:13
dholbachahhh, there it is10:13
seb128hum, it's confusing10:13
seb128is the setting page working now if you change10:13
seb128does it get buggy again if you use ctrl-space?10:13
seb128super-space rather10:13
dholbachseb128, ok: super-space works, indicator works too, changes in the settings page don't work10:13
dholbachdoes that clear it up?10:14
dholbachattente, ^10:14
dholbachthanks a lot for the help10:14
seb128dholbach, I'm unsure the settings are supposed to change the active one, they change the order10:15
seb128dholbach, so you basically hit super-space by error and didn't know the keybinding/had the indicator hidden so you didn't have a way to go back10:15
tjaaltonok to add this to u-s-d? https://github.com/GNOME/gnome-settings-daemon/commit/3a8beaaf380a483ce33363031d8d276c371d7af110:15
dholbachseb128, yes, that's the case10:16
seb128tjaalton, https://launchpadlibrarian.net/171554356/unity-settings-daemon_14.04.0%2B14.04.20140310-0ubuntu2_14.04.0%2B14.04.20140402-0ubuntu1.diff.gz ?10:16
tjaaltonseb128: ooh10:16
seb128dholbach, ok, sorry it took us so many step to understand the issue10:16
tjaaltonshould've checked10:16
dholbachseb128, no worries - I could have thought of using super+space myself ;-)10:17
seb128dholbach, the fact that you are hidding the indicator also didn't make it obvious to change back10:18
seb128or to show the actual layout10:18
seb128attente, NOTABUG in the end ;-)10:19
seb128attente, have a good w.e btw!10:19
seb128tjaalton, ;-)10:19
tjaaltonmakes ara happy :)10:19
seb128great!10:20
dholbachattente, seb128: thanks!10:20
seb128dholbach, yw!10:20
tjaaltonhmm, something else is missing though, micmute on my thinkpad doesn't seem to work10:21
tjaaltoncgmanager takes 100% cpu after dist-upgrade10:24
Laneyget a bt of what it's doing and file a bug10:24
Laneythat's a stgraber thing10:25
tjaaltonhmm no it didn't dist-upgrade, wth10:25
tjaaltonok I'll try again after this is done10:25
tjaaltonmaybe micmute will work too :P10:25
seb128Laney, https://code.launchpad.net/~hikiko/unity-control-center/unity-control-center.clamp-ui-scale/+merge/214019 looks fine to me, wdyt?10:26
Laneyseb128: looks ok indeed10:27
seb128ok, great, let me test build/run it and then put it in a silo10:27
tjaaltonseb128: yep micmute works after all.. phew10:29
seb128tjaalton, great!10:29
seb128bah, I'm again having a non working ssh agent10:30
seb128xnox, stgraber: is there any chance somebody look at those upstart script issues?10:30
seb128often ssh-agent is taking over gnome-keyring-daemon's agent and I end up with a non working config10:30
xnoxseb128: correct. we don't have jobs for seahorse...10:33
xnoxseb128: i think we should add gpg, ssh, secret-service upstart jobs such that gnome-keyring would take over, on top, again.10:34
seb128xnox, the issue is not seahorse, it's gnome-keyring (that's the agent for ssh/gpg)10:37
xnoxseb128: right, and gnome-keyring ships 4 xdg/autostart files, which race with upstart's ssh-agent job. And gnome-keyring, ideally should provide 4 upstart jobs. Or drop in an override to disable ssh-agent.10:38
xnoxseb128: you can try $ echo manual > ~/.config/upstart/ssh-agent.override10:39
xnoxseb128: and can you tell me if that fixes everything for you?10:39
seb128https://launchpad.net/ubuntu/+source/openssh/1:6.6p1-1 had changes to help there10:39
seb128  * Don't start ssh-agent from the Upstart user session job if something10:39
seb128    like Xsession has already done so (based on work by Bruno Vasselle;10:39
seb128    LP: #1244736).10:39
ubot2Launchpad bug 1244736 in gnome-session (Ubuntu) "upstart configuration for user launches an extra ssh-agent" [Undecided,Confirmed] https://launchpad.net/bugs/124473610:39
seb128xnox, ok, let me try that10:39
seb128xnox, thanks10:40
xnoxyeah, that helps preventing duplicate ssh-agents, it doesn't help that we want gnome-keyring to be our SSH agent on the desktop and take that role over the top of `ssh-agent' =)))10:41
seb128xnox, do we do anything to uninstall indicator-sync on upgrades?11:04
seb128(I still have it installed)11:04
xnoxseb128: well, we will need to sru something in the indicator-sync for stable releases to e.g. become a dummy empty package.11:05
xnoxseb128: or maybe we can make something conflict and replace it?11:05
seb128not sure11:06
seb128we should at least teach update-manager/the dist upgrader to uninstall it on upgrade11:07
seb128there is a list of deprecated packages/things to clean iirc11:07
=== MacSlow is now known as MacSlow|lunch
seb128Laney, do you have an opinion on https://code.launchpad.net/~seb128/unity-control-center/depends-on-indicators/+merge/212137 ?11:54
Laneyseb128: I agree with you both, so feel free to do it12:01
seb128Laney, thanks, I'm going to push that through today, it starts becoming a frequently reported issue on e.u.c12:01
=== alan_g is now known as alan_g|lunch
=== davidcalle_ is now known as davidcalle
=== MacSlow|lunch is now known as MacSlow
=== alan_g|lunch is now known as alan_g
pesarihey, do you think that the trusty kernel will be backported to precise ~soon?12:57
xnoxpesari: only just after trusty release.13:02
xnoxpesari: by end of ~monthish.13:02
pesariokay sounds good, thanks13:02
xnoxpesari: in practice it will only be ready and supported with 12.04.5 approximatelly targeted for august.13:02
pesariok13:03
xnoxcause X and related packages would need updates as well, but 12.04.5 desktop images will default to trusty hwe stack.13:03
xnox(hwe = hardware enablement)13:03
brainwashtedg: hey, we are testing a patch to start indicator-services via upstart in xubuntu. it works fine, but we need to hide the autostart launchers, so that they don't show up in our autostart managing app. is the right approach to remove XFCE from OnlyShowIn= or add it NotShowIn= ?13:14
brainwashI've edited the .desktop files accordingly and the indicators still launch properly for me13:15
tedgbrainwash, Remove from OnlyShowIn13:15
brainwashwhat about indicator-bluetooth and -power? they don't have this line13:17
xnoxbrainwash: tedg: the right aproach is to ship override in the /usr/share/upstart/xdg no?13:17
xnoxbrainwash: tedg: cause that xdg dir is added in sessions that are managed by upstart, which xubuntu is.13:17
tedgxnox, Read backlog from yesterday :-)13:17
xnoxtedg: oh, i'm so out of date, always =)13:17
tedgxnox, Yes, this is about their configuration app, not starting them :-)13:18
brainwashexactly :)13:18
xnoxtedg: bah, meh. I'm wrong as always =)13:18
tedgbrainwash, Hmm, does your configuration app use the OnlyShowIn attribute?13:18
brainwashwe don't want to confuse the user with showing unfunctional autostart launchers in our config app13:18
tedgbrainwash, Guessing it's ignoring that? Because if it's "OnlyShowIn" for Unity it really shouldn't show up.13:18
brainwashright, but -sound and -application do contain XFCE13:19
tedgYes, those should go. But I'm worried it won't be a complete solution if the app doesn't look at OnlyShowIn.13:19
brainwash-power and -bluetooth don't even have OnlyShowIn13:19
tedgOh, that's right, their updates are still stuck in CI Train.13:20
brainwashit does consider OnlyShowIn13:20
brainwash-session and -datetime are already hidden13:20
tedgseb128, Can we land all the startup fix branches?13:20
seb128tedg, I doubt it so close from release13:20
xnoxtedg: prepare SRUs13:20
seb128tedg, we seem to already have issues with the ones we landed13:20
tedgseb128, We kinda need them to fix this issue on XFCE13:20
brainwashwe are still testing the patch to launch them via upstart13:21
tedgseb128, And we're fixing those, but we need them to be consistent to have a good fix.13:21
seb128tedg, they were complaining about -sound yesterday which has the branch landed13:21
tedgseb128, Yes, and they're testing the fix for that, but it breaks other indicators because they're not consistent.13:22
seb128shrug, what a mess13:22
brainwashlong story =S13:22
seb128we should have stayed on the old autostart13:22
tedgNo, we should have landed the startup fixes in Feb when they were done and just moved on :-)13:23
seb128so we have even more bugs today13:23
seb128I hate those changes, they are bringing complexity and bugs without benefits13:23
seb128which is why I've tried to stay away from them13:24
seb128I'm not going to block others to land them, but I'm not really wanting to step into that13:24
tedgThey're removing code that is maintained in libindicator which is poorly done to Upstart, which has a better process management.13:24
seb128except that upstart is not managing all sessions13:24
seb128so we end up keeping the old way13:24
seb128and adding the new one13:24
seb128not to mention that we now get stuff like indicators not stopped on the greeter13:25
seb128which let cgroups/logged users actives where they shouldn't13:25
LaneyPretty sure you don't want to mess with OnlyShowIn13:25
LaneyThose desktop files have NoDisplay=true so whatever UI ought not to be showing them13:25
tedgI'm all for dropping the old way. It's just there for compatibility with folks like GNOME2.13:25
tedgseb128, Those bugs would have happened regardless, because I'm betting in that case dbus is sticking around too. Because if it died, the indicators would die.13:26
seb128could be13:27
seb128anyway it feels like close from release to land those13:27
seb128if you get Laney/release team about it those I can put a landing for you though13:27
seb128I just decline responsability for bugs that are coming from those changes13:28
tedgI feel like we need consistency or we're just going to find rough edges if they don't work the same.13:28
LaneyWhat's the problem if they're started by both in reality?13:28
LaneyThe second one just bails out13:28
brainwashwe'll investigate and see if we can simply hide the launchers based on NoDisplay=true13:28
tedgLaney, The issue right now is that not all the indicators have the NoDisplay entry in the upstart directory.13:29
tedgThere's no real consistency13:30
LaneyI mean for trusty, for umbongo we can do the good thing when there's 6 months to fix stuff13:31
LaneyThe only problem I have on my !upstart session is that application doesn't work13:31
knomethe problem is that trusty is the LTS, umbongo isn't13:31
Laneybecause of the no watchers thing13:31
Laneythat's not the problem13:31
Laneyif there was a big issue then it would be13:31
Laneybut there isn't13:31
LaneyThat's a reason to not do risky things less than a week before the final freeze13:32
tedgFor trusty we have some indicators doing the NoShowIn in /etc/xdg and some have Hidden in /usr/share/upstart/xdg13:32
knomei vote for consistency, whatever the way it was13:33
knomewe will adapt to that.13:33
tedgWe do have the watchers thing as well, not sure how the folks are handling that now.13:33
LaneyThe hidden thing is right, but I don't get what the actual problem is with leaving it inconsistent13:34
LaneyWe discovered straight away that one desktop isn't ready for the change13:34
Laney(that came because OnlyShowIn there was updated to include XFCE)13:35
Laney(the other ones just have Unity which is fine with it)13:35
tedgThe branches have been in queue since the middle of Feb. Saying "too late" seems like a bad answer.13:39
dobeyLaney, seb128: do you guys usually build system-settings with srcddir == builddir or something?13:44
seb128I usually bzr bd it and work in the builddir13:44
seb128Laney, btw, do you receive/filter the "request review" emails? or do those end up in your spambox?13:49
Laneyfor what?13:49
seb128spam->launchpad ;-)13:49
seb128Laney, u-c-c, I was wondering if you saw e.g https://code.launchpad.net/~seb128/unity-control-center/crp-gcc-unity/+merge/21401813:49
Laneyyeah but Robert had already done it13:50
seb128right, I sent it yesterday morning though and it was a trivial one13:50
seb128I was wondering if you queue/flush or if you didn't see it13:50
seb128I would usually be fine waiting some days, but we are getting close from freeze ;-)13:50
LaneyI did queue it but then didn't get back to it that day13:50
Laneysoz13:51
seb128k, fair enough13:51
seb128tedg, speaking about indicator upstart jobs, do you have any idea about https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1302123 ?14:02
ubot2Launchpad bug 1302123 in indicator-application (Ubuntu) "Won't respawn when restarting unity-panel-service" [High,Confirmed]14:02
tedgseb128, Yup, fixed in the branch.14:04
seb128tedg, "the" branch?14:04
tedgseb128, It's also the reason nm-applet doesn't show on the greeter14:04
tedgseb128, The startup-cleanup branch for indicator-application14:04
seb128tedg, no, I landed that branch a month ago14:05
seb128tedg, http://bazaar.launchpad.net/~indicator-applet-developers/indicator-application/trunk.14.04/revision/24614:05
tedgseb128, yeah, the problem there was that I hadn't pushed the last changes to it :-(14:05
seb128tedg, sorry, more recently, https://launchpad.net/ubuntu/+source/indicator-application/12.10.1+14.04.20140324-0ubuntu114:05
seb128tedg, there is still no mp with those fix that I can see?14:05
seb128tedg, https://code.launchpad.net/indicator-application/+activereviews14:06
tedghttps://code.launchpad.net/~ted/indicator-application/startup-cleanup/+merge/21272614:06
tedgI forgot to change it's status :-(14:06
seb128thanks14:07
* seb128 test build that14:07
tedgseb128, It looks like bug 1296715 has LO setting those actions to disabled. We're rendering it correctly.14:16
ubot2Launchpad bug 1296715 in libreoffice (Ubuntu) "Menu items are greyed out in Libreoffice menu." [Undecided,New] https://launchpad.net/bugs/129671514:16
seb128tedg, thanks for investigating14:16
tedgSweetsha1k, ^14:16
seb128Sweetsha1k, ^ one for you14:16
tedgOh, one thing to note that screwed me up, It's not the "add" menu but the "insert" menu. Guessing a reverse translation.14:17
tedgStarted with "Oh, my, the whole add menu is missing!"14:18
Sweetsha1kseb128, ricotz: libreoffice 4.2.3.3 tagged upstream, tarballs build, source package build, binaries building locally right now ...14:18
Sweetsha1ktedg: meh14:18
=== Sweetsha1k is now known as Sweetshark
Sweetsharklucky me. That bug by tedg was for that Sweetsha1k guy, not for me.14:19
seb128Sweetshark, sponsoring time!14:19
seb128lol14:20
Sweetsharkseb128: is the accessodf thing sponsored btw? see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=74363414:21
ubot2Debian bug 743634 in libreoffice-accessodf "libreoffice-accessodf: MessageBox API changed in LO 4.2 :/" [Important,Open]14:21
seb128Sweetshark, no, that's what happens when you use IRC pings rather than bugs/ubuntu-sponsors :p14:22
seb128Sweetshark, let me do it now14:22
Sweetsharkseb128: thx14:22
seb128Sweetshark, done14:23
seb128Sweetshark, bah, got rejected, the version is older than the one in trusty-proposed14:29
Sweetsharkseb128: urgh, seeing that now - will fix that.14:31
seb128thanks14:32
=== alan_g is now known as alan_g|tea
=== alan_g|tea is now known as alan_g
=== Ursinha-afk is now known as Ursinha
l3ondarkxst around ?14:47
=== alan_g is now known as alan_g|tea
=== alan_g|tea is now known as alan_g
seb128l3on, he's in .au, it's like middle of the night there14:58
l3onthanks seb128 :)14:58
seb128yw14:58
Sweetsharkseb128: next try http://people.canonical.com/~bjoern/trusty/accessodf_0.1-4ubuntu1_source.changes and http://people.canonical.com/~bjoern/trusty/accessodf_0.1-4ubuntu1.diff14:59
ricotzSweetshark, nice, did you push the source-package somewhere already?15:02
Sweetsharkricotz: not yet, will do if the build finishes ...15:03
Sweetshark... and whatever15:03
Sweetsharkricotz: pushing it now.15:04
Sweetsharks/and/ah/15:04
ricotzSweetshark, alrighty ;)15:04
=== Ursinha is now known as Ursinha-afk
seb128Sweetshark, https://launchpad.net/ubuntu/trusty/+source/accessodf/0.1-4ubuntu115:09
=== Ursinha-afk is now known as Ursinha
Sweetsharkseb128: \o/15:15
seb128mvo, do you think you could have a look to https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1301776? Not sure if that's a compiz or update-manager issue (I mentioned it to Trevinho some time ago in the cycle)15:21
ubot2Launchpad bug 1301776 in update-manager (Ubuntu) "Update manager is really small and not resizeable" [High,Confirmed]15:21
mvoseb128: looking15:34
seb128mvo, danke15:34
=== bschaefer_ is now known as bschaefer
mvoseb128: hm, looking at the code it might be on purpose, is design cool with the window being resizable?15:41
seb128mvo, I don't know, that's a question for mpt ;-)15:41
seb128mvo, if it's on purpose, can we make it a bit less small maybe? https://launchpadlibrarian.net/171657786/update-manager-is-small.png is a bit ridiculous ;-)15:42
Sweetsharkricotz: packages are at https://launchpad.net/~bjoern-michaelsen/+archive/libreoffice-staging15:42
mvoseb128: aha, I think I get it - with details its supposed to be resizable, when no details are there it seems to be its not supposed to be resizable15:43
seb128mvo, I'm never going to understand designers I think, why don't they let users resign their windows if they want? ;-)15:44
ricotzSweetshark, thx!15:44
=== gatox is now known as gatox_lunch
seb128bregma, andyrock: what's the status of the lockscreen/power manager? any chance it lands this week still?15:46
seb128bregma, you should probably put a landing back for the force quit dialog thing as well15:46
bregmaseb128, I'll be doing that Unity landing in a bit15:48
bregmaseb128, I've already pinged andyrock on the lockscreen status, I'm waiting for his reply15:48
seb128bregma, ok, thanks15:49
Laneyseb128: http://people.canonical.com/~laney/package-junkyard/ could you try this one please15:49
seb128mvo, well, even if we let resize the default shouldn't be that small15:50
andyrockbregma, can land tomorrow if I work tomorrow15:51
seb128Laney, seems to fix it15:52
andyrockseb128, ^^^15:52
Laneyseb128: *phew*15:52
seb128andyrock, are you supposed to work tomorrow? ;-)15:52
andyrockit's saturday15:52
andyrockI can try15:52
seb128andyrock, right, sorry about that, but it's getting close from release freeze :/15:52
andyrockseb128, yeah and it's a complicated piece of software15:53
andyrock:D15:53
seb128Laney, well done ;-)15:53
Laneywell, i don't understand why it's broken15:53
seb128andyrock, I warned you guys that it was late to land a feature like the lockscreen, when you did it...15:53
Laneybut we love a good workaround15:53
mvoseb128: yeah, so this looks like this is a issue with compiz :/ I can resize just fine with metacity running15:53
mvoseb128: and the code set the correct gtk_window_set_resize(True/False) at the right spots AFAICT15:54
seb128mvo, well, different behaviour doesn't mean bug15:54
seb128k15:54
seb128so one for Trevinho then15:54
mvoseb128: how do you mean?15:54
seb128mvo, I mean that some wm let you resize things that they shouldn't, e.g the "it works with $otherwm" doesn't always mean it's compiz which is buggy (even if it's often the case ;-)15:56
mvoseb128: fair enough :) in this case it seems u-m is setting the hints at the correct times but for some reason they are not picked up15:57
seb128Laney, what is looping (I didn't look at the code)? Do we end up with something owning the bus name and a codepath trying it loop to claim it and failing or..?15:57
seb128mvo, http://irclogs.ubuntu.com/2014/03/11/%23ubuntu-desktop.html#t18:5415:58
seb128mvo, that was the previous discussion with Trevinho ... I'm going to add compiz to the bug/assign to him15:59
mvoseb128: thanks, gtg to get dinner now15:59
* mvo waves15:59
seb128mvo, do you still think we should change the default geometry to bit less small though?15:59
seb128mvo, enjoy, and have a good w.e!15:59
mvoseb128: yes, that is a good idea15:59
Laneyseb128: AFAICT when whoopsie-preferences went away it emitted PropertiesChanged which triggered the handler inside alm which then got into a loop with the checkbox toggled handler16:01
LaneyBut it's all done with gdbus-codegen so quite hard to get at16:01
LaneyI think that sometimes it was seeing the wrong result for some reason16:02
seb128looks like something for desrt ;-)16:03
LaneyI think the backend managed to get the opposite idea of the checkbox state to the ui16:03
Laneywhich triggered a loop toggling the setting on and off16:03
Laneyfrom the property callback to the toggled callback on the togglebutton16:04
seb128k16:04
seb128isn't that a bug that whoopsie-preferences is emitting that PropertiesChanged?16:05
seb128the "out of sync" seems also a bug on the alm side16:05
seb128that code is not great :/16:05
seb128well, at least we have a working workaround16:05
LaneyIt does it all through gdbus so dunno16:05
LaneyNever emits that signal explicitly16:05
LaneyBut it could be using that wrong16:05
Laneyanyway ;-)16:05
seb128Laney, you didn't manage to do your shifted piloting day it seems ;-)16:21
Laneyyeah, my bad16:21
LaneyI'll shift it one more time(!)16:22
seb128well, monday is likely to have more in the queue ;-)16:22
Laneyif it's the first thing on monday then I can't get stuck doing something else before it16:22
Laneybah16:22
seb128(assuming some contributor are going to use the w.e to get work up for review)16:22
Laneystupid gcal permissions16:22
seb128ok, on that note I'm away for a bit16:23
seb128no exercice today, I feel tired, but still going to walk around for a bit and see some outside16:23
Laneyget on your bike!16:23
seb128be back in a bit to clean up emails backlog and stuff and then calling it a week16:24
seb128Laney, that's an idea ;-)16:24
seb128k, bbiab16:24
seb128have a good w.e for those who are taking off before I'm back!16:24
Laneyhf, you too!16:24
* Laney gets a webkit ready to upload for building over the weekend16:25
=== gatox_lunch is now known as gatox
Laneywill block it in proposed, that's if it actually does build ¬_¬16:25
andyrockseb128, do you know if when the screen is locked but not is on16:30
andyrockorg.gnome.screensaver GetActive16:30
andyrockshould be True or False16:30
andyrock?16:30
=== alan_g is now known as alan_g|EOD
seb128andyrock, no idea about that sorry17:33
=== tkamppeter__ is now known as tkamppeter
xclaessedoes mediascanner has another purpose in life than taking 100% CPU ?21:41
brainwasheating memory maybe?21:42
darkxstl3on, am now21:54
l3ondarkxst, bug 130207721:54
ubot2Launchpad bug 1302077 in nautilus (Ubuntu) "Hardcoded css style checks on GTK Theme instead of XGD_CURRENT_DESKTOP" [Undecided,New] https://launchpad.net/bugs/130207721:54
l3onbut I have to go right now21:55
l3onthis tricks are odd ...21:56
l3on*these21:56
l3oneven the patch ubuntu_show_titlebar.patch (always in nautilus) should be dropped. It's just a workaround because unity+compiz does not handle csd_windows correctly. You should instead fix compiz (or unity)22:00
darkxstl3on, nautilus uses a non-standard headerbar/csd implemention22:01
darkxstand Ubuntu doesnt want CSD's22:01
darkxstbut Ubuntu GNOME does22:01
l3onso, you have a problem :P22:02
darkxstand the checks were based on theme, since they mess up things with high contrast and adwaita22:04
l3onso darkxst, you're in gnome-shell and you're using Ambiance. what happen to nautilus?22:06
l3onor, you're in Unity and you're using Adwaita. what happen to nautilus?22:06
darkxstfirst case will display without CSD's22:07
darkxstsecond will be with CSD's22:07
darkxstthings will be a bit saner next cycle with gtk 3.1222:08
l3onok with next cycle. but right now your patch does not work properly in Unity if users used onther theme with .header-bar { border-radius: some.px }22:11
l3onam I wrong ?22:14
darkxstl3on, overrides are only applied to ubuntu themes22:17
l3onyep, I'm wrong. Anyway you're overring also un gnome-shell if I use Ambiance. This is wrong22:20
bigonhey, so let's ask here too22:21
bigonI'm thinking about pkging nautilus-sendto 3.8 in debian (the version that removes all the plugins) now that empathy has drop its own nst plugins22:22
bigonis it a problem for you?22:22
darkxstl3on, Ambiance is very broken in gnome-shell anyway22:23
l3onsomeone's working on https://code.launchpad.net/~l3on/ubuntu-themes/gnome-shell-fixes22:23

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