[00:38] <ceed^> darkxst, Same problem with Adwaita and the other themes I have installed. Can't resize either, but can't remember if I used to be able to.
[00:40] <darkxst> does it only happen with a particular app? or all?
[00:42] <ceed^> let me check....
[00:45] <ceed^> Seems like it may only be Evolution. The text isn't wrapped.
[00:46] <darkxst> ceed^, file a bug against evo (in ubuntu) then, that is just copied from utopic
[00:46] <ceed^> k, will do. thanks!
[03:37] <Malyndra_Crow> Hey guys, I've got an irritating little bug that's really getting on my nerves. When I right click on the desktop for setting and change background, i change my background, then close settings, then after that, right click on desktop no longer works. This happens every single time.
[03:38] <Malyndra_Crow> Oh, using trusty tahr
[04:06] <Malyndra_Crow> sparq: I've got an irritating little bug in Trusty that's really getting on my nerves. When I right click on the desktop for settings and change my background, then close settings, after that, right click on desktop no longer works. This happens every single time.
[10:02] <darkxst> ricotz, fyi bug 1342923, popped up with 1.0.2
[10:06] <darkxst> ricotz, I've not seen it locally though, could it be a glib api mismatch
[10:07] <ricotz> darkxst, i see, you shouldn't do the retrace with ppa:ricotz/testing
[10:14] <darkxst> ricotz, those traces are automated ;(
[10:14] <darkxst> ricotz, if you had ddebs on your ppa they would work ;)
[10:15] <darkxst> (I have a slightly patched instance of the main retracer bot running, with support for ppa's
[10:23] <ricotz> darkxst, ok, but if the reporter doesnt use my ppa while should be the common case, as for this one, the retrace should do so too
[10:24] <ricotz> i doubt i would get ddebs support granted ;)
[10:31] <darkxst> ricotz, it should only trigger from crashes reported for gnome3 ppa's packages, but its hard to know about the deps
[10:32] <darkxst> before actually retracing
[10:32] <ricotz> darkxst, Dependencies.txt is pretty clear about that
[10:33] <darkxst> ricotz, there are a lot of packages in there though
[10:33] <darkxst> and it will only break if a certain package ends up in the trace
[10:36] <darkxst> so I either block the retracer for all packages with foreign ppa's in there
[10:36] <darkxst> or let it run and hope it works
[10:46] <darkxst> ricotz, and fwiw, your ppa in not in that trace, I suppose you saw it one of the dupes?
[10:52] <ricotz> if the stacktrace refers to "/build/buildd/glib2.0-2.41.2~git20140710.60fe7b46/" is looks pretty much like a package to my ppa
[10:52] <ricotz> https://bugs.launchpad.net/ubuntu-gnome/+bug/1342923/comments/3
[10:55] <darkxst> ricotz, but that is not in Dependencies.txt
[10:55] <ricotz> exactly that is what i am talking about here!
[10:55] <ricotz> the retracer uses my ppa, but the reporter not
[10:55] <darkxst> so how is the bot supposed to kno
[10:56] <darkxst> ricotz, the retracer fires because of the tracker bug
[10:56] <ricotz> Dependencies.txt is coming from the reporter
[10:56] <darkxst> s/bug/crash/
[10:57] <darkxst> ricotz, do your packages have debug symbols?
[10:57] <darkxst> like non-stripped ones?
[10:58] <ricotz> no, but i guess you have *-dbg installed on your machine
[10:58] <darkxst> ricotz, that was not my crash report, just saw a bunch of them file in after 1.0.2
[10:59] <ricotz> i looked at the bug you linked me to
[10:59] <darkxst> I don't think the retracer will pick up -dbg packages for ppa's unless they are listed in dependencies.txt
[10:59] <darkxst> it runs in a chroot after all
[11:00] <ricotz> i assume those "core" dbg packages might be picked up by default
[11:00] <ricotz> since the ddebs are empty for those, right?
[11:00] <darkxst> ricotz, not from PPA's
[11:00] <darkxst> uess ddebs are empty where there is a -dbh
[11:00] <darkxst> -dbg
[11:01] <darkxst> the upstream retracer has no support for PPA's
[11:01] <darkxst> mine scans for [origin: LP-PPA- tags] in dependencies.txt and add them to the sources.list
[11:01] <ricotz> darkxst, i can't follow you here, it is clear the glib package from my ppa is included in this chroot
[11:02] <darkxst> ricotz, I pretty sure it is not
[11:04] <ricotz> no idea where this is coming from then
[11:04] <ricotz> anyhow the trace is pretty useless in this case
[11:04] <darkxst> I see no [origin: LP-PPA-ricotz-testing] in Dependencies.txt, which is the only way retracer could get the -dbg packages
[11:04] <ricotz> if something went wrong inside of glib the retracer needs to have the same version
[11:05] <ricotz> darkxst, you see the snapshot reference in the stacktrace, i am just refering to that!
[11:06] <darkxst> ricotz, yes I see that, but the retracer does not!
[11:07] <darkxst> (well not the bit the fires off the chroot, with what ppa's to include)
[11:20] <darkxst> ricotz, though all that might explain the large number of failures that we see with the retracer
[11:24] <ricotz> darkxst, you are really sure the chroot itself doesnt include it already?
[11:25] <darkxst> ricotz, imagine an "apport-retrace -g" but with a custom apt/sources.list
[11:25] <ricotz> i am not speaking of the apt-sources, i mean the actually installed packages in there
[11:26] <darkxst> ricotz, it runs in a clean chroot everytime, and there are zero ppa's installed on the server
[11:26] <ricotz> mount it and look with "dpkg -l"
[11:28] <darkxst> ricotz, I can guarantee there are no ppa's in the base chroot, in fact, it may still be saucy
[11:28] <ricotz> ok
[11:28] <darkxst> its kinda  chroot in a chroot since its on a centos server
[11:29] <darkxst> but the actual retracer chroot, has only PPA's listed in Dependencies.txt
[11:30] <ricotz> alright, that is pretty weird then
[11:31] <darkxst> very!
[11:33] <ricotz> next time you might see "2.41.2~git20140714.79e63d4e"
[11:34] <darkxst> could well be a bug in the generation of dependencies.txt, but even then it should not show up unless that particular symbol is not stripped
[23:43] <balleyne> My network interfaces just disappeared on me in NetworkManager (I think that's what it is). Can't see wired or wireless connections anymore, though I can see them from iwconfig and connect via the commandline (iwconfig + dhclient). Help?