[08:41] damn, everything becomes slow during weekends === bilalakhtar_ is now known as bilalakhtar === bilalakhtar_ is now known as bilalakhtar [15:00] could someone take a look on bug 533432? [15:00] Launchpad bug 533432 in kdegraphics (Ubuntu) "kolourpaint4 breaks GNOME widget style (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/533432 [15:01] !weekend | ari-tczew [15:01] ari-tczew: It's a weekend. Often on weekends the paid developers and a lot of the community may not be around to answer your question. Please be patient, wait longer than you normally would or try again during the working week. [15:11] devildante: hmm , you do know that you are over-using that factoid, right? usually the factoid is used when someone keeps repeatedly asking the same question on a weekend. and not just for asking a question ;) [15:11] vish: meh, sorry :p [15:12] vish: I just don't want someone to wait without knowing that all the important guys are here :p [15:12] devildante: ari-tczew is not someone new , so he knows ;) [15:12] vish: oh, sorry for that [15:13] sorry, ari-tczew ;) [15:13] np.. :) [15:17] devildante: no problem. anyway, I should wait for seb128 or pedro or robertancell [15:47] ari-tczew: looks like gnome-settings-daemon crashes, do you have a stacktrace? [15:48] kklimonda: I can prepare [15:55] kklimonda: apport doesn't see this crash. can I prepare backtrace insteaD? [15:58] ari-tczew: sure - only install gnome-settings-daemon-dbgsym first [15:59] ari-tczew: but apport should catch it - do you have it enabled? [15:59] and I can't reproduce it in vm.. heh.. [16:00] kklimonda: I'm not sure - how can I check it? [16:00] ari-tczew: check if you have enabled=1 in /etc/default/apport [17:08] kklimonda: I have already enabled=1 [18:03] kklimonda: around? [18:09] how can I grab backtrace from gnome-settings-daemon? [18:12] ari-tczew: kill it and then restart inside debugger, set logging (set logging on) and run it (run) - after it crashes dump a backtrace (bt) and full backtrace (bt full) - you will get a file named gdb.txt in the current directory. pieces in () are gdb commands. [18:23] vish, https://code.launchpad.net/~and471/ubuntu-mono/fix-605092/+merge/34023 :) [18:26] and471: whoops! i already included the icon in my local branch! [18:26] vish, hehe oh well [18:26] and471: what happened to shotwell btw? [18:26] vish, sizes for 32 and 48? [18:27] vish, they shipped with the icons that I was able to finish [18:27] vish, not all are done yet, so I need to write that on the bug report [18:27] vish, bug me tomorrow [18:27] ah.. [18:29] hey glatzor [18:31] hello and471 [18:31] how are you? [18:31] glatzor, not bad, and yourself? [18:31] and471, tired :) [18:32] glatzor, can I ask a question about aptdaemon, or should I leave it till tomorrow :) [18:32] ? [18:32] and471, no problem. I am a part time programmer :) [18:32] hehe [18:32] glatzor, which property I need to monitor/signal I need to connect to when I use client.update_cache() [18:33] so that I can tell [18:33] when the repository it is downloading from changes [18:33] (so changes from ppa x, to ppa y etc.) [18:34] progress-download-changed [18:34] and471, sorry the client documentation is really bad [18:34] and471, but I am working on it :) [18:34] glatzor, no problem :) [18:35] glatzor, is that in a new version of aptdaemon? [18:35] unknown signal name: progress-download-changed [18:35] and471, puh. it should be in 0.3 [18:36] glatzor, how do I tell which version I have? [18:36] and471, the NEWS files holds all the API changes. it was introduced in 0.32 [18:37] glatzor, ah ok, I see that I have an update for aptdaemon, give me a sec [18:40] - Add a progress-download-changed signal to AptTransaction which is emitted [18:40] when a download progress information changed, see above. [18:40] glatzor, yup ^ [18:43] and471, you don't need to unlock the package cache for aptdaemon to work [18:44] glatzor, you mean apt_pkg.PkgSystemUnLock() [18:44] ? [18:44] and471, because any application which is running as non-root cannot acquire or release the lock at all [18:44] right [18:44] you need root privileges. [18:44] glatzor, that was something that I just copied over from UpdateManager [18:44] glatzor, I didn't write it - i swear! [18:44] :) [18:44] and471, no problem. [18:47] * and471 loves how he doesn't need to put in his password for updating now! [18:47] glatzor, ok, so the signal works now [18:47] glatzor, gotta go now, see ya tomorrow [18:48] see you! [18:48] thanks! [18:51] kklimonda: No stack. [18:51] but I have file in /var/crash and error message from ~/.xsession-errors [18:59] kklimonda: gnome-settings-daemon crashed with SIGSEGV in g_main_context_dispatch() [19:02] ari-tczew: it should be catched by apport - do you have "|/usr/share/apport/apport %p %s %c" in /proc/sys/kernel/core_pattern ? [19:03] ari-tczew: if you have a file in /var/crash then it's great [19:03] ari-tczew: is it from this crash? can you compare timestamps? if so can you upload it to LP using apport-cli /var/crash/filename.crash ? [19:04] kklimonda: exactly: |/usr/share/apport/apport %p %s %c [19:04] kklimonda: I clicked twice on this file and then apport has created new bug. [19:04] kklimonda: bug 626379 [19:04] ari-tczew: Bug 626379 on http://launchpad.net/bugs/626379 is private [19:06] ari-tczew: I'll look into it once apport retraces runs [19:07] kklimonda: http://launchpadlibrarian.net/54595255/Stacktrace.txt [19:08] ari-tczew: without retrace it's hardly useful - I see in which file did it occur (and it's indeed related to clipboard) but that's it :) [19:10] kklimonda: exactly, like in my test case! [19:10] kklimonda: I subscribed you to apport's bug. [19:10] kklimonda: my first bug is bug 533432 [19:10] Launchpad bug 533432 in kdegraphics (Ubuntu) "kolourpaint4 breaks GNOME widget style (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/533432 === JanC_ is now known as JanC