[00:07] d1ndra, there is pretty much no c++ in GNOME [00:07] lots of c, vala, javascript (for gnome-shell) and a few python apps [00:09] I know C too, but I've heard that developing with C take in a lot of effort and one has to focus on a lot of details. Would it be a good idea to enhance my knowledge of Python and work on something using it? [06:36] darkxst: adwaita (default) [06:37] knittl, I have heard reports but not been able to reproduce myself [06:38] hm. I will make a screenshot later today [06:38] knittl, are they just transparent? [06:39] darkxst: yeah, the dark themed windows (for instance gnome-terminal) get a transparent title bar (still with title and buttons, but transparent background) [06:40] yeh seen screenshots of that, but I am hopeless at theming, so can't fix unless I can reproduce [06:40] my guess is some invalid css properties [06:41] knittl, maybe its using the old adwaita, rather than the one that is now built-in to gtk package (for 3.14) [06:41] could be a possibility [06:41] how can I verify? [06:44] I'm not entirely sure, you could just try removing the old gnome-themes package if its still installed? [06:44] iirc it was a dependency of ubuntu-gnome-desktop [06:45] knittl, let it remove that if needed [06:45] alright. will try in the afternoon [06:47] knittl, ok let me know how it goes, I will be updating ubuntu-gnome-desktop for 3.14 in a week or 2 (on vivid) but can backport that to utopic ppa also [06:47] sure. thanks :) [06:48] knittl, it's also worth running apt-show-versions | grep -v uptodate, to see if you've all the packages from the right archives [06:49] will do (but I think everything is up to date) [06:56] (also it _might_ be a driver bug) [06:57] nvidia? how?? [06:59] I mean, if badly-drawn shadows can be a driver bug, why not badly-drawn titlebars? [07:02] mgedmin, sure it could be, but I have not seen any bugs with nvidia blob [07:03] knittl, do you use the blob or noveau? [07:04] mgedmin: proprietary nvidia [07:05] nouveau doesn't work on my system (forces hard reboots) [07:06] ok, that's interesting: my gnome-shell just crashed [07:07] the hard reboots don't have anything to do with gnome-shell [07:07] segfault in shell_app_compare [07:11] ho ho ho UnicodeEncodeError in apport-retrace while printing the stack trace [07:15] mgedmin, apport-retrace is pretty fragile [07:16] and if the crash is from js code, you really need shell in a live gdb session so you can gjs_dumpstack() [07:27] one day gdb might grow support to retrace those things (I think someone at mozilla is working on it), but right now its not that way unfortunaley [07:28] my disk hasn't got enough free space for all the debug symbols :/ [07:31] most are pretty small except for bloody webkit [08:04] interesting message in /home/mg/.cache/upstart/gnome-session-GNOME.log during gnome-shell startup [08:04] (gnome-shell:30338): Gjs-WARNING **: JS ERROR: Exception in callback for signal: startup-complete: Error: Requiring GSystem, version none: Typelib file for namespace 'GSystem' (any version) not found [08:04] missing dependency on some gir package? [08:06] gir1.2-gsystem-1.0? [08:10] yeah, installing that and alt-f2 r gets rid of the error [08:11] I'll file a bug so this doesn't get lost [08:15] https://bugs.launchpad.net/ubuntu-gnome/+bug/1388736 [08:15] Ubuntu bug 1388736 in Ubuntu GNOME "missing dependency on gir1.2-gsystem-1.0" [Undecided,New] [08:46] mgedmin, or fix it and I will upload for you ;) [08:49] this month is a flurry of sorts, hopefully we will have all of core 3.14 in before alpha1 [08:52] mgedmin, and I only have time to work on the real problems, that other team members can't do [08:53] do you keep the packaging bits in a repository somewhere? I could send a git patch... [08:54] <[vbm]> hi there, my 14.04 upgrade broke Gnome Do. I am running ubuntu with openbox + tint2 + docky and I can invoke Do with ctrl+alt+space but when I type something nothing appears. I googled it but couldn't find anything helpful. can anybody help? [09:28] oh, gir1.2-gsystem-1.0 is not available on debian [09:28] and here I was all prepared to report a debian bug === prth is now known as prth|away [11:03] welp, why is libvte in ubuntu so ancient (0.28.2)? upstream is up to version 0.38 already [11:03] and I want a bugfix from 0.35.1 (https://github.com/GNOME/vte/commit/a118544044e064ea1d3f36e959d961845ec9c317) [11:08] never mind I'm an idio [11:20] <[vbm]> hi there, my 14.04 upgrade broke Gnome Do. I am running ubuntu with openbox + tint2 + docky and I can invoke Do with ctrl+alt+space but when I type something nothing appears. I googled it but couldn't find anything helpful. can anybody help? [11:21] [vbm], wouldn't know where to start :( [11:25] <[vbm]> mgedmin, thanks anyway. I upgraded my X40 a couple of days ago and now I can't use do's shortcuts. It's a bit annoying as a I normally use it for everything that isn't on the dock. [11:26] I can imagine [11:26] is it gnome-do failing to find something? or an input problem of some sort? [11:26] have you tried google? [11:29] <[vbm]> gnome-do appears as blank. whatever I type appears in the box, but the usual autocomplete and with the 2nd box showing run does not appear [11:29] any errors in, uh, ~/.cache/upstart/*.log? [11:30] <[vbm]> google hasn't been particularly helpful. most links are about how great gnome-do is and how to install it :) checking *.log now [11:33] <[vbm]> can't find upstart under .cache [11:35] then maybe ~/.xsession-errors [11:39] <[vbm]> a couple of badwindow messages and a few "Cairo.Surface is leaking, programmer is missing a call to Dispose" but I'm not sure invoking do creates nay more entries on the log [11:40] [vbm], I suggest asking for advice on #gnome-do [11:43] <[vbm]> thanks. will do. i didn't see that channel before. thanks. [11:51] hi all [11:52] Heavensbus, hi [11:55] lindol: hi [16:47] darkxst: hi [16:47] I'm at my machine again [16:48] removing gnome-themes-standard will also remove gdm*, gnome-shell*, and mutter* (to name a few)