[09:05] <ubotu> New bug: #144011 in xserver-xorg-video-ati (main) "GUTSY. No video output firing up X." [Undecided,Incomplete]  https://launchpad.net/bugs/144011
[09:06] <ubotu> New bug: #145097 in xorg (main) "Live session directly go to black screen" [Undecided,New]  https://launchpad.net/bugs/145097
[11:10] <ubotu> New bug: #145128 in xorg (main) "LiveCD No intel video" [Undecided,New]  https://launchpad.net/bugs/145128
[02:11] <ubotu> New bug: #145186 in xorg (main) "mouse pointer disappears when using external display" [Undecided,New]  https://launchpad.net/bugs/145186
[02:40] <ubotu> New bug: #145198 in xserver-xorg-video-ati (main) "[gutsy] [9700]  analog output on DVI-I broken" [Undecided,New]  https://launchpad.net/bugs/145198
[04:02] <Q-FUNK> seb128: exactly how did you reach the conclusion that the broken gtkprint was caused by libcups?
[04:04] <seb128> Q-FUNK: what is the bug number? the backtrace calls are in libcups if I remember correctly
[04:05] <ubotu> New bug: #145211 in xorg (main) "OS won't shutdown after certain video usage; memory corruption?" [Undecided,New]  https://launchpad.net/bugs/145211
[04:06] <Q-FUNK> bug #135832
[04:06] <ubotu> Launchpad bug 135832 in cupsys "evince: libgtkprint support is broken" [Low,New]  https://launchpad.net/bugs/135832
[04:10] <seb128> #1  0xb71b5478 in connect () from /lib/tls/i686/cmov/libc.so.6
[04:10] <seb128> #2  0xb476513c in httpAddrConnect () from /usr/lib/libcups.so.2
[04:10] <seb128> #3  0xb47639e6 in httpReconnect () from /usr/lib/libcups.so.2
[04:10] <seb128> ^
[04:10] <seb128> that looks like it's hanging while connecting to cups
[04:10] <seb128> and it's a hang in libcups
[04:10] <seb128> maybe you have a firewall blocking it or something
[04:11] <Q-FUNK> definitely not
[04:11] <seb128> ok, so maybe the cupsys config is broken
[04:11] <seb128> or libcups has a bug
[04:11] <seb128> or you have a network issue
[04:11] <seb128> I'm not sure, and I don't know cups enough to figure
[04:11] <Q-FUNK> besides, gtkprint is the only thing that fails. gnomeprint, OOo, firefox, all work.
[04:12] <Q-FUNK> so that tells me that cupslib works fine, given how apps that directly access it and gnomeprint both work.
[04:12] <seb128> does it happen in other applications use gtkprint? yelp, epiphany, gtk-demo
[04:13] <Q-FUNK> I can try yelp.  just a sec.
[04:14] <Q-FUNK> yelp also buggers.
[04:14] <Q-FUNK> same symptoms
[04:15] <seb128> k, so it looks like gtkprint, libcups, cupsys issue
[04:15] <seb128> having a backtrace with dbgsym package for those would be useful
[04:16] <Q-FUNK> gtkprint, definitely.
[04:17] <seb128> how do you know?
[04:17] <seb128> the backtrace indicates it's hanging in a connect made by libgnomecups
[04:17] <seb128> libcups rather
[04:17] <Q-FUNK> and yet gnomeprint doesn't hang during connect.  it just works.
[04:18] <seb128> do you know it's internel?
[04:18] <seb128> does it uses the same libcups functions than gtkprint?
[04:18] <seb128> that's not because some part of libcups is not buggy that there is no bug
[04:21] <Q-FUNK> well, that's rich.
[04:47] <seb128> re
[04:48] <seb128> Q-FUNK: you know, trying to change bug setting over a maintainer is not the way to get it resolved
[04:48] <Q-FUNK> seb128:  neither is changing it without justification.
[04:49] <seb128> Q-FUNK: I told you my justification
[04:49] <seb128> the stacktrace indicates it's blocked on a libcups listen
[04:49] <Q-FUNK> "looks like a libcupsys bug. reassigning." that's not a justification.
[04:50] <seb128> Q-FUNK: I gave you details on this chan
[04:50] <seb128> looks at http://launchpadlibrarian.net/9211483/gdb-evince.txt
[04:50] <seb128> connect, httpAddrConnect, httpReconnect, httpConnectEncrypt
[04:51] <seb128> it's clearly hanging on a call from libcups
[04:51] <seb128> why do you think it's a GTK bug?
[04:51] <seb128> might be a httpConnectEncrypt() libcups bug, which is something libgnomeprint maybe doesn't use
[04:51] <Q-FUNK> you'd need to write that in the bug as a justification, for this to be usefull to pitti or anyone else. then they can decide for themselves if they agree with your assessment.  right now, the one-liner your wrote is useless as an explanation.
[04:52] <seb128> I explain it to you on this chan
[04:52] <Q-FUNK> that could be.
[04:52] <seb128> you could have asked that instead of just reassigning
[04:52] <Q-FUNK> I already asked.
[04:52] <Q-FUNK> you had already reassigned
[04:52] <seb128> from now I'll just ignore this bug since you don't want to work in the right way
[04:52] <Q-FUNK> you thus didn't get copy of the question.
[04:54] <Q-FUNK> seb128:  reassigning the bug with such a laconic justification helps nobody, so please work in the right way and provide details for that sort of action.
[04:54] <Q-FUNK> on the bug, where it belongs.
[04:55] <seb128> it was assigned to evince which was clearly wrong
[04:55] <seb128> I reassigned to libcups what is the most likely place according to the backtrace
[04:55] <seb128> what about letting the maintainer make calls?
[04:55] <seb128> bug tracker should not allow users to change settings over maintainers
[04:56] <seb128> anyway could you get a debug backtrace?
[04:56] <Q-FUNK> nothing more than what I already attached to the bug.
[04:57] <seb128> libcupsys2-dbgsym libc6-dbg libgtk2.0-0-dbgsym are installed?
[04:57] <seb128> http://launchpadlibrarian.net/9211483/gdb-evince.txt has no debug functions
[05:01] <ubotu> New bug: #145244 in xft (main) "[gutsy]  libXft library - undefined symbol FT_Library_SetLcdFilter" [Undecided,New]  https://launchpad.net/bugs/145244
[05:58] <bryce_> tepsipakki: on bug 136783, what do you think of forcing TV off in dexconf?  Is there a better way we can address this?
[05:58] <ubotu> Launchpad bug 136783 in xserver-xorg-video-intel "not using whole widescreen" [High,Triaged]  https://launchpad.net/bugs/136783
[06:28] <Q-FUNK> /querry bryce_ ah :)
[06:28] <Q-FUNK> ...
[06:28] <bryce_> hi Q-FUNK
[06:29] <Q-FUNK> bryce_: did the strace that Scott provide made any sense to oyu?
[06:35] <bryce_> bug#?
[06:37] <Q-FUNK> bug #140051
[06:37] <ubotu> Launchpad bug 140051 in xserver-xorg-video-amd "amd driver fails to autoconfigure" [Medium,Confirmed]  https://launchpad.net/bugs/140051
[06:41] <ubotu> New bug: #145276 in xorg (main) "xorg.conf multiple monitor failure" [Undecided,New]  https://launchpad.net/bugs/145276
[06:56] <ubotu> New bug: #145283 in kde-guidance (main) "[gutsy]  When Driver in xorg.conf is set to  "openchrome"  X fails to start. Changing it manually to "via" works." [Undecided,New]  https://launchpad.net/bugs/145283
[07:10] <bryce_> Q-FUNK: interesting
[07:13] <bryce_> Q-FUNK: it looks like its segfaulting while trying to load vgafb
[07:13] <bryce_> er, s/vgafb/vgahw/
[07:21] <bryce_> Q-FUNK, ok left my interpretation of the strace.  I have no idea what's going on, but hopefully that should give you some new stuff to test
[07:44] <tepsipakki> bryce_: well, that's one option.. but maybe first ask upstream?
[07:51] <bryce_> tepsipakki: who would be best to ask?
[07:54] <tormod> hi, I am building new ati drivers in PPA now, with the post-194 git commit.
[07:55] <bryce_> tepsipakki: also see discussion on #ubuntu-desktop about -ati's xrandr and multi-screening
[07:55] <bryce_> I sense that glatzor would favor sticking with -ati 6.6.3 since displayconfig-gtk does not support xrandr yet
[07:56] <tepsipakki> uh
[07:56] <tepsipakki> ok
[07:57] <tepsipakki> that's better than skip dualhead with intel&ati?
[07:57] <tepsipakki> in displayconfig-gtk
[07:57] <jcristau_> &nv
[07:58] <tepsipakki> right
[07:58] <tepsipakki> well, dunno
[08:00] <tormod> stick with 6.6.3? omg we have to reopen many a bug then. like my favorite 22985...
[08:00] <tepsipakki> i'll check the discussion soon
[08:02] <tormod> hmm #ubuntu-desktop is not logged
[08:43] <tepsipakki> hmm, the reason why xresprobe fails for so many is probably that laptop-detect fails
[08:45] <bryce_> that's what I'm wondering
[08:46] <tepsipakki> it's easy to check..
[08:46] <tepsipakki> ask the reporters to run that
[09:06] <tormod> laptop-detect fails? again?
[09:07] <tormod> last time it failed during casper, but would work in installed, which was quite confusing. (#40503)
[09:09] <tormod> and I remember initial resolution detection would also fail. bug # anyone?
[09:13] <bryce_> bug 127008
[09:13] <ubotu> Launchpad bug 127008 in xresprobe "Alternate install of Tribe-4 corrupts video display when installing packages (affected hardware includes Santa Rosa)" [High,In progress]  https://launchpad.net/bugs/127008
[09:20] <bryce_> tormod: btw, when you start a discussion with a user, and esp. after asking a question, could you set the state of the bug from New to Incomplete (or Confirmed)?
[09:20] <tormod> bryce_: ok, I do it sometimes :)
[09:21] <bryce_> tormod: this'll help the bug triagers a lot
[09:21] <tormod> sure. It's just that I then feel compelled to assign it to myself, which I sometimes don't want to.
[09:21] <bryce_> like bug 145097, can probably be set to incomplete
[09:21] <ubotu> Launchpad bug 145097 in xorg "Live session directly go to black screen" [Undecided,New]  https://launchpad.net/bugs/145097
[09:22] <tormod> in that bug I am not at all sure I am on the right track, would be nice if someone else takes a look.
[09:23] <bryce_> tormod, brian murray says the incomplete state should always be set when someone has at least taken a preliminary look, even if it's not clear what's going on
[09:23] <tormod> ok, will do that every time then.
[09:24] <bryce_> cool thanks
[09:24] <bryce_> yeah I looked at this one too, and it seemed odd
[09:24] <bryce_> I wonder if it really is the screensaver coming on
[09:24] <bryce_> it sounds very familiar; I think I ran into something similar once
[09:25] <bryce_> however there the issue was that the clock got reset, so the screensaver *thought* a lot of time had passed and came on
[09:25] <bryce_> doesn't sound like this is happening here
[09:28] <tormod> yes I saw that earlier when coming back from hibernation, but that's fixed (I think).
[09:29] <tormod> if he could change the screensaver and then restart X we would see. But at this point I am not sure he and I understand each other.
[09:31] <tormod> screensaver on/off is that logged somewhere? I guess not.
[09:34] <bryce_> I don't think it's logged, but it could be tested for using 'xset q'
[09:35] <bryce_> so something like xset q | grep -A 2 "Standby:" could be useful
[09:36] <bryce_> if those values are not 0, then it means a screensaver may be active
[09:36] <tormod> you mean the built-in xorg screensaver, ok
[09:38] <tormod> I built an ati driver with verbose dpms messages, I could get him to try that. However, the blanking doesn't call dpms functions I guess, only when it's time to shut off the screen.
[09:43] <tormod> btw the new ati packages (with more "mode" fixes) are done building in my ppa
[09:43] <bryce_> awesome
[09:49] <bryce_> Brice Goglin mentioned the multi-board multi-head bug on the xorg list (ATI + MGA)
[10:05] <bdmurray> Looking at an Xorg.0.log I saw "(--) Chipset ATI Radeon XPRESS 200M 5A62 (PCIE) found" is 5A62 the product part of the pci id?
[10:10] <bryce_> I think almost certainly
[10:10] <bryce_> I notice ATI Radeon XPRESS 200M 5955 (PCIE) has pciid 1002:5955, so expect 5A62 would be similarly so
[10:11] <bdmurray> I'm pretty sure too and was trying to figure out if lspci wasn't always necessary.
[10:12] <bdmurray> I understand that ideally we would like it but instead of bothering a reporter for the umpteenth time.
[10:19] <bryce_> it's extremely rare that the device name would include the pciid like in this case
[10:22] <bdmurray> That is the device name?
[10:24] <bdmurray> Okay, I see now.
[10:24] <tormod> there are probably so many versions of 200M they had to put in a unique ID
[10:25] <bdmurray> It seems ATI specific my laptops just says "Chipset 945GM found"
[10:45] <bryce_> bbiab
[10:46] <tormod> bryce_: I suggest making a Gutsy/Xrandr page and link to it from the release notes. Otherwise it will be too much with links and workarounds.
[11:31] <tormod> good night