[13:24] <melodie_> hi
[13:24] <penguin42> hey
[13:26] <melodie_> I just installed a Trusty almost up to date and after install I updated. From there : some applications would not display their "face" anymore, only the borders of the windows. I realized later after some research in the history of the update that the gtkpixbuf packages were the guilty.
[13:26] <penguin42> what makes you say it was gtkpixbug?
[13:26] <penguin42> f
[13:26] <melodie_> so I have rebooted to live, proceeded to get the packages from there with dpkg-repack, rebooted to the install, installed the three packages using dpkg and that's fixed.
[13:26] <melodie_> the error messages said it was gtkpixbuf
[13:27] <melodie_> now, I would like to know against which of the three packages should I check for bug reports?
[13:27] <melodie_> Here is the list:
[13:27] <melodie_> gir1.2-gdkpixbuf-2.0_2.30.7-0ubuntu1_amd64.deb
[13:27] <melodie_> libgdk-pixbuf2.0-0_2.30.7-0ubuntu1_amd64.deb
[13:27] <melodie_> libgdk-pixbuf2.0-common_2.30.7-0ubuntu1_all.deb
[13:28] <melodie_> these ones are the ones I recreated with dpkg-repack
[13:28] <penguin42> do they all come from the same source package?
[13:28] <melodie_> penguin42, I think so?
[13:28] <melodie_> let me check
[13:28] <penguin42> I think the bugs come back to the source package, so they'd all be against one
[13:30] <melodie_> penguin42, you are right, I got my answer, thanks!
[13:30] <melodie_> now I have to head to my other machine, where my account is setup :D
[13:30] <melodie_> terrible, you can fancy?
[13:31] <melodie_> update and oops! GUI vanished! /o\
[13:32] <melodie_> so the package is gdk-pixbuf
[13:32] <penguin42> melodie_: OK, so that's a really grim failure if there's a trusty update that's breaking it
[13:32] <melodie_> what does "grim" mean here?
[13:32] <penguin42> BAD
[13:32] <melodie_> yes
[13:32] <melodie_> terrible
[13:33] <melodie_> in the present install I have reinstalled the previous and blocked the version for the time being, now I'll check what I can find at the ubuntu packages place, see if there are already other bug reports
[13:34] <penguin42> melodie_: If you can't find the right one, then use ubuntu-bug to report the bug,  state clearly the version you had the problem with and paste the bug link here
[13:36] <melodie_> penguin42, don't worry, I'll find a way to proceed to the bug reports, I am now reading the former high confirmed bug
[13:37] <penguin42> URL?
[13:38] <melodie_> version for http://packages.ubuntu.com/trusty/libgdk-pixbuf2.0-0 is now "2.30.7-0ubuntu1.1", and to fix the bug I reinstalled versions " 2.30.7-0ubuntu1 "
[13:39] <melodie_> the former bug relates to a former major version, it's not related directly
[13:39] <melodie_> here: #619003
[13:40] <melodie_> now I head to my other machine, login to launchpad and will be back here and on the logs pages of ubuntu IRC to get back the info for the bug report.
[13:40] <melodie_> also I have the .xsession-errors.old from the former session with the errors
[13:40] <melodie_> well, with some of the errors
[13:41] <penguin42> 619003 is ancient
[13:41] <melodie_> http://paste.ubuntu.com/12295075/
[13:41] <penguin42> however...
[13:41] <melodie_> however?
[13:42] <penguin42> melodie_: can you do    file /usr/share/themes/bluebird/gtk-3.0/assets/entry.png
[13:43] <melodie_> yes, it's svg files not png
[13:43] <melodie_>  no
[13:43] <melodie_> wait
[13:44] <melodie_> [myriam@pegase:/usr/share/themes]$ file Bluebird/gtk-3.0/assets/entry.png
[13:44] <melodie_> Bluebird/gtk-3.0/assets/entry.png: PNG image data, 24 x 16, 8-bit colormap, non-interlaced
[13:44] <melodie_> this is "Bluebird" and not "bluebird" :D
[13:45] <penguin42> I was just looking at the other errors in your log about those, but I don't see wh it's upset at them
[13:45] <melodie_> penguin42, do you want me to bring any other information right here?
[13:46] <penguin42> melodie_: Not that I can think of
[13:46] <melodie_> just after update there were error messages related to gdkpixbuf loaders
[13:46] <penguin42> melodie_: If you reupgrade to the broken packages does it fail again?
[13:46] <melodie_> let me check the logs
[13:47] <melodie_> should I break this install again? I don't think so, that's not my machine and I have to hand it back in a pair of days
[13:47] <melodie_> I'll rather test in a virtual machine in my tower
[13:47] <penguin42> melodie_: Well if you've kept the old packages on there, you shouldn't need to use a livecd, you should just be able to do the packages from the command line
[13:48] <penguin42> melodie_: But if you can repeat the failure in a VM that would be great - but I'm not one of the gdk-pixbuf devs
[13:49] <melodie_> yes, I'd rather check in a virtualbox machine
[13:50] <melodie_> also I would like to find the post-install messages from apt-get but it seems not to exist? Or do I miss something?
[13:50]  * penguin42 isn't sure if they're logged anywhere
[13:50] <melodie_> also I can test in the live usb, it won't hurt it as it's in read only mode
[13:51] <melodie_> penguin42, in Archlinux, their pcmanfm.log logs everything, in one single file. as long as the owner of the machine does not remove it, he can retrace all his/her history from the very first day the system was installed : post-install messages included
[13:52] <penguin42> melodie_: There is /var/log/dpkg.log
[13:52] <melodie_> let me check
[13:52] <penguin42> melodie_: I'm not sure if it will contain what you're after though
[13:54] <melodie_> http://paste.ubuntu.com/12295187/ lines 296 to 302
[13:55] <melodie_> it just says "half installed"
[13:56] <melodie_> but this is not a clue, it says the same for the other packages udpated and installed too
[13:57] <melodie_> I'll reboot to the live now and test there. This way I can come back here with the history of our discussion which I will retrieve directly. I'll boot the tower too at same time. and in the live usb I'll do the upgrade and see how it reacts.
[13:57] <melodie_> brb
[13:57] <penguin42> oh, gets configure at line 600ish
[14:44] <melodie> hi
[14:44] <melodie> penguin42,
[14:44] <melodie> https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1492767
[14:46] <penguin42> melodie: What do you mean by 'custom version'
[14:46] <melodie> Ubuntu with Openbox
[14:47] <penguin42> melodie: and where are the openbox packages from?
[14:47] <melodie> https://launchpad.net/bento-dev
[14:47] <melodie> from the repos of course
[14:48] <penguin42> melodie: From the main repos or from that bento thing?
[14:48] <melodie> Bento does not have a repos
[14:48] <penguin42> ah
[14:48] <melodie> and it's not a thing :D
[14:49] <melodie> it's a well working version
[14:49] <penguin42> melodie: OK, it's just starting a bug report off with 'I installed a custom version and something broke' isn't going to get very far
[14:49] <melodie> if it's confirmed in other installs it will go further
[14:50] <melodie> ok, I removed "custom version"
[14:51] <penguin42> melodie: No, you must be honest - if it is a custom version then you've got to be honest and debug whether it's your custom version that's the problem
[14:51] <melodie> to do that, I'll need to check in an official version such as Lubuntu
[14:52] <penguin42> yep, but if you're going to do something non-standard then the onus is on you to figure out what's going on
[14:52] <melodie> so I may show my bug report to people using and working for the Lubuntu community and ask if they find the same as I do. i work regularly with them on improving things
[14:52] <penguin42> sure
[14:53] <penguin42> melodie: It's just it's a very different triage; a main package that breaks lots of users is obviously high/critical - if it's just breaking a few people with some odd setup then it's very different
[14:54] <melodie> penguin42, there is no special thing in Bento Openbox, just the files are in the /etc/skel and as it's Openbox it has some configuration files in text mode, and up to now, after dozens of ISOs done since 3 years, it's the first time I meet such an issue (and other issues I met were confirmed and fixed the same way with bug reports and cross findings in official editions)
[14:54] <melodie> you can have a look at my bugs page https://bugs.launchpad.net/~meets
[14:55] <penguin42> melodie: OK, so rather than saying custom install actually document in the bug the setup you're hitting
[14:55] <melodie> ok, how do I do that?
[14:55] <penguin42> I don't know anything about your setup, but obviously you've done it some how
[14:57] <melodie> the setup is very classical, lxappearance writes to the files .gtkrc-2.0 and .config/gtk-3.0/settings.ini
[14:57] <melodie> really nothing special about that
[14:57] <melodie> the elements of the theme come from the repos
[14:57] <melodie> one icon theme comes from a ppa, and brings no trouble at all
[14:57] <penguin42> you've got to report what you're doing or the bug is worse than useless
[14:58] <penguin42> you're hitting a bug in gdk-pixbuf with a theme from a ppa? Have you tried switching that off?
[14:58] <melodie> no
[14:58] <melodie> this is not a theme from a ppa
[14:58] <melodie> only the icons
[14:58] <melodie> the theme is clearlooks-phenix
[14:58] <melodie> and yes I have switched themes this is explained in the bug report
[14:58] <penguin42> but gdk-pixbuf wrangles images, so that could be those icons?
[14:59] <melodie> no the icons aren't involved
[14:59] <penguin42> how do you know?
[14:59] <melodie> it's something related to gtk3 themes
[14:59] <melodie> I know because I tried gtk2 themes
[14:59] <melodie> and in programs which can use it, the problem was gone
[14:59] <melodie> but with synaptic that uses GTK3 the problem was gone only when I move the gtk3 theme out of the way:
[15:00] <melodie> then synaptic looked ugly as a lost dog, but was working
[15:08] <melodie> penguin42, I have to go test in vbox now, I am leaving here, the live update didn't teach me anything because there was not enough space available
[15:09] <melodie> bbl
[15:09] <melodie> and thanks for your help!