=== ara is now known as Guest22932 === chrisccoulson_ is now known as chrisccoulson === mck182 is now known as mck182|afk [19:05] tjaalton: the new radeon TearFree feature fixes my problem [19:31] furkan: guess it just hides the problem then [22:52] hello [22:52] there is a critical bug in ubuntu 15.04! [22:52] i am talking in #ubuntu-devel and in #xorg-devel [22:53] in two days there should be the release of 15.04 and its fully unusable on some machines! [22:53] how to reproduce: dd the most recent daily build into an usb pendrive, boot from it, open libreoffice -> there is an Xorg server crash [22:54] http://pastebin.com/9K0W1NwU [22:55] this report here looks same: https://bbs.archlinux.org/viewtopic.php?id=195666 [23:23] boax: Is there an Ubuntu bug filed? [23:24] RAOF: i was able to face that all down [23:24] http://pastebin.com/9K0W1NwU [23:24] is related to an gnome 3.14 bug [23:25] boax: You should have got a prompt to submit an error report to Launchpad? [23:25] RAOF: check the last message here: https://bbs.archlinux.org/viewtopic.php?id=194819 [23:25] the bug is somewhat strange. it come on few machines but on those machines it always come [23:25] and makes those machines somewhat unusable [23:26] Sure. [23:26] Have you filed a bug on launchpad? [23:26] Have you got a ‘submit error’ popup? [23:26] i cant beleive that i am the only one with that bug [23:26] or are there only that few people who test upcomming versions like 15.04? [23:26] Because if you submit the bug that way, it'll come attached with all sorts of useful debugging information. [23:27] the solution for the bug seem to be: backport some things from recent gnome versions that fix that error or bump the version of gnome to the recent one that dont cause this error [23:28] Neither of those is the solution to an X server crash. [23:28] At best, that's a workaround. [23:28] If you submit the bug report to Launchpad we'll get a full backtrace, with symbols, and it'll be much more likely that we can fix it. [23:31] RAOF: you are a dev that could help when reported the way you explain here? [23:31] Yes. [23:33] okay. to help you providing the information you need i have to start the system that crashes, let it crash and then when it ask me if it should send the crash report have to answer yes? [23:33] how can that be done on an machine that does not have an internet connection? [23:33] Hah. That's a little more difficult, but not too much. [23:34] i have an usb pendrive that can travel the data from the one to the other machine [23:34] When the machine crashes it should generate a /var/crash/_usr_bin_X_something_or_other.crash file. [23:35] okay. i get that for you :) [23:36] On a machine with an internet connection you can then run “ubuntu-bug that_crash_file”, and it'll do the reporting bits. [23:39] RAOF: okay. i have the file after making it 777 to be able to copy it to the usb pendrive as a normal user. its about 5mb. the machine i have internet on is not ubuntu. should i upload the file to you? [23:40] Ok; if you can put it somewhere I can download it. [23:41] uploading... have you already an idea on what part the bug could be? Xorg server? [23:44] If the X server's crashing it's an X bug. [23:44] (Almost certainly) [23:45] you got the file? Check your query ;) [23:46] Yup. [23:46] You've hit https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1443456 [23:46] Launchpad bug 1443456 in xorg-server (Ubuntu) "Xorg crashed with SIGABRT in fbBltOne()" [Medium,New] [23:50] i told tarpman that he was right with guessting that this could be the error :) [23:50] can i help somehow to debug that error? [23:50] i think its more then "Medium". Its critical or blocking [23:54] RAOF: can i do something else to help you debugging this error? [23:55] No, it seems pretty obvious what the immediate problem is; glamor shouldn't be passing in a NULL destination to fbCopy. [23:59] This doesn't look like something that should block the release, but should be fixed in an early update.