/srv/irclogs.ubuntu.com/2012/06/12/#ubuntu-desktop.txt

cyphermoxrobert_ancell: hey01:30
RAOFARGH STUPID DAMN SSDs.02:04
lifelessRAOF: ?02:05
RAOFThe ssd in my laptop has decided that it's *too good* to talk to the bios. Therefore, the bios sees it not.02:05
lifelesshah02:05
lifeless'too good'? Is that hyperbole, or an actual error symptom ?02:06
RAOFHyperbole ;)02:06
RAOFIt no longer appears in the BIOS' list of devices; presumably it's not responding to SATA commands.02:06
RAOFThis is why déjà dup is set to daily backups.02:08
brycehRAOF, last week I had a problem where the SSD wouldn't come up, because the freakin' liveusb stick installed the boot loader on the usb stick.  wtf.02:23
RAOFThat's a bit sub-optimal02:24
brycehRAOF, so the ssd only booted when the usb stick was installed.  fun!02:24
brycehof course, easy to fix once I figured out what was going on, but eesh.02:24
brycehcommon problem with liveusb's with persistent storage enabled, apparently.02:24
thomiDoes anyone know what "failed to set drm interface version" means? It's an error that I'm getting from X on three separate boxes with different graphics cards when trying to live-boot the precise daily CD image.03:03
TheMusoGiven all the things I've heard about SSDs, I can't help but wonder if the tech is still a little immature.03:03
RAOFthomi: "failed to set drm interface version" generally means one of two things: the drm modules aren't ready, or you don't have the requisite permissions.03:05
RAOFWoot! Thank you deja-dup; now I have the actual code I want to palm off to robert_ancell :)03:06
thomihmmm, I'm guessing it's the former, rather than the latter, since this is the live CD03:06
thomiRAOF: any idea how I'd check that?03:06
RAOFWhere are you seeing that?03:06
robert_ancellRAOF, lost then found again?03:06
RAOFrobert_ancell: On an SSD that's died, then extracted from yesterday's backup.03:07
thomiRAOF: in the X log, instead of booting into the desktop I get the "system running in low graphics mode" dialog.03:07
RAOFthomi: You could pastebin the Xorg.0.log; you could also try logging in to a VT and checking that the drm module's up and running - that'd be one of i915, radeon, or nouveau.03:08
brycehTheMuso, I've a bunch of systems on SSD's now, and anecdotally would say they're definitely no worse than HDDs generally03:09
thomiRAOF: the 'radeon' module is indeed listed in 'lsmod'03:09
brycehTheMuso, remember with HDD's there's a class of mechanical problems you can run into, which just aren't going to happen on SSD's.03:09
cyphermoxrobert_ancell: fyi; seb told me you were working on g-s-d 3.5; might want to merge with what's currently in lp:~ubuntu-desktop/gnome-settings-daemon/ubuntu if you have a local branch, I did an upload earlier.03:10
RAOFthomi: If you start lightdm now, does it work?03:10
TheMusobryceh: Yeah I know, same for both I guess, I've just heard of some pretty bad SSD failings, which surprises me for drives with no moving parts.03:10
thomiRAOF: I don't get an error, but I can't seem to switch to VT7, I just get a black screen. However, there's a chance that's the KVM I'm fighting with03:12
* thomi checks logs03:12
RAOFI think the vertex series is particularly bad; I heard similar bad things about vertex 2 drives, but (at the time I bought it) people were saying that the vertex 3 had resolved that.03:12
brycehTheMuso, maybe so.  I always research my drive purchases on newegg and have yet to have an SSD failure (out of about a dozen I own currently).03:17
brycehTheMuso, of course having said that I'm sure tomorrow I'll have the SSD in my most critical system go down...03:18
micahgbryceh: how old is your oldest drive?03:18
thomiRAOF: OK, I finally beat the KVM into submission. Yes, if I start lightdm manually it works perfectly03:19
RAOFthomi: In that case it sounds like a race between X startup and drm.03:19
RAOFthomi: Are you only seeing this on radeon cards?03:19
thomiRAOF: nope, I have *exactly* the same issue on three separate machines running radeon, nvidia, and intel chipsets03:20
RAOFThat's very odd.03:20
thomiRAOF: possibly something to do with it being a PXE boot?03:21
thomiI dunno how that would change anything though, but I guess having an NFS FS might make some race conditions rear their heads03:22
RAOFI guess it *could* be? But intel and nouveau are usually better at actually waiting for their devices to come up before bailing in that way.03:22
thomiRAOF: I am able to tweak the OS before it boots, so if there's a hack you can think of to make sure things happen in the right order I'm happy to try it out03:24
brycehmicahg, hardy timeframe.03:25
RAOFthomi: Loading the drm modules into the initramfs should rule out a race.03:25
micahgbryceh: a 4 yr old SSD?03:25
brycehmicahg, hmm that doesn't sound right03:27
thomihmmm03:27
RAOFthomi: An easy way to get the drm modules into the initramfs is to install cryptsetup, then rebuild the initramfs.03:28
thomiRAOF: sp is the kernel module always called 'drm', or does that change between drivers?03:33
RAOFthomi: There's drm.ko, drm_kms_helper.ko, and a hardware-specific driver - i915.ko, radeon.ko, nouveau.ko.03:38
brycehmicahg, I'm a year off; it was right after berlin, which looks like it was the Jaunty sprint in Feb 200903:38
micahgbryceh: still, a 3yr SSD seems amazing03:39
thomiRAOF: thanks03:39
brycehmicahg, yeah I got in early on ssd's.  That particular drive has been hand-me-downed through a few systems.  I've lost track of where it exists now but think it's in a netbook I gave to a relative.03:42
thomiRAOF: possibly a stupid question: Would it matter if I loaded a graphics driver in the initramfs that wasn't needed for the hardware? For example, I had the 'radeon' module in there and the machine had an intel card?04:06
thomi...reason being: I have one OS image that serves several different machines04:06
RAOFNo; the modules will only autoload if the hardware they support is present, and (generally) will fail to load if you try to manually modprobe them on a system without hardware they can drive.04:07
RAOFAnd won't *harm* anything even if they do load.04:08
thomiok, cool04:09
pittiGood morning04:14
cyphermoxhey pitti04:40
cyphermoxI'm planning on starting on the drivers stuff "tomorrow", basically in a few hours04:40
cyphermoxI'll poke your brain about the plans then :)04:41
pitticyphermox: nice!04:47
pittilooking forward to the new GUI04:47
rickspencer3good morning all05:41
pittihey rickspencer305:43
rickspencer3hiya pitti05:43
rickspencer3pitti,  how is your new upstream QA work going?05:43
pittirickspencer3: some slow progress; still working on desktop backlog05:44
pittirickspencer3: but I submitted my first kernel patch last week and did not get flamed (didn't get applied yet, though)05:44
rickspencer3pitti, backlog of desktop work, or backlog of desktop QA?05:44
pittirickspencer3: and I'm making some nice progress on the udisks2 test suite; it already helped to discover one bug in udisks2 itself, and one in util-linux, which is quite nice (and unexpected)05:45
rickspencer3congrats!05:45
pittirickspencer3: desktop work; some python3 porting and the like05:45
pittibut that's fine05:45
rickspencer3well, looks like daily quality is still marching along, except KDE seems to be in some difficulties05:46
pittiyeah, today quantal is much better than yesterday05:46
BigWhaleGood Morning.05:51
didrocksgood morning06:03
rickspencer3'morning didrocks06:10
didrocksbonjour rickspencer3, ça va ?06:10
rickspencer3ça va bien06:11
rickspencer3expeté, je n'ai pas café06:12
rickspencer3je dois sortir pour café biento ....06:12
rickspencer3je dorm ....06:12
rickspencer3zzzzzzz06:12
rickspencer3didrocks, et tois? ça va?06:13
didrocksrickspencer3: ça va bien! pas encore pris de café non plus, mais je vais me faire un petit thé bientôt06:14
rickspencer3tu as la vie sànte06:16
didrocksje sais pas si le thé est plus zen que le café, mais je préfère son goût06:17
=== tkamppeter_ is now known as tkamppeter
=== rickspencer3_ is now known as rickspencer3
seb128hey08:06
didrockssalut seb128, ça va?08:06
seb128lut didrocks, ouais, et toi ?08:06
didrocksça va bien :)08:07
Sweetsharkbonjours mes amis!08:07
seb128Sweetshark, guten tag!08:07
Sweetshark;)08:08
Sweetsharkseb128: I could need a helping hand with forcing gcc to 4.6 on quantal. I have "build-conflicts: gcc (>= 4:4.7~) [!kfreebsd-i386 !kfreebsd-amd64], g++ (>= 4:4.7~) [!kfreebsd-i386 !kfreebsd-amd64]" but dpkg complains that g++ 4.7 whats gcc 4.7. yeah, right. but it shouldnt fiddle with g++ 4.7 anyway ...08:12
Sweetsharkseb128: https://launchpadlibrarian.net/107401324/buildlog_ubuntu-quantal-amd64.libreoffice_1%3A3.6.0~beta1-0ubuntu4_FAILEDTOBUILD.txt.gz08:12
seb128Sweetshark, do you need to remove 4.7? can't you just build-depends on 4.6 and tweak CC= and equivalents?08:12
Sweetsharkseb128: maybe -- Im unsure, if the old build system respects CC in every corner ...08:16
seb128Sweetshark, the issue there is that build-essential depends on 4.708:16
seb128Sweetshark, I'm not sure you can remove build-essential from the buildds08:16
Sweetsharkseb128: right08:17
Sweetsharkwell, the old bs should work on that too ...08:19
seb128Sweetshark, ?08:19
seb128bs?08:19
Sweetsharkseb128: old build system (or old bull****) ;)08:20
seb128heh, I see ;-)08:21
glatzorhello mvo08:28
glatzormvo I added some patches to lp:~aptdaemon-developers/aptdaemon/ubuntu-precise to reduce the shame on errors.ubuntu.com :)08:29
pittipopey: hey Alan, how are you?08:32
pittipopey: do you guys plan to port unity away from libgdu to libudisks2 soon? udisks1 and libgdu are both obsolete08:33
seb128pitti, I doubt anyone is working on that yet, I'm not even sure they knew about that transition, can you open a bug?08:35
pittisure08:35
pittishould be fairly easy08:36
BigWhaleseb128, I chatted with DktrKranz yesterday. He'll update keybinder and get it ready for Wheezy in the next couple of days.08:36
popeypitti: I was not aware of that08:38
popeythanks!08:38
pittipopey, seb128: I filed bug 1012000 about it08:38
ubot2Launchpad bug 1012000 in unity "Port to libudisks2" [Undecided,New] https://launchpad.net/bugs/101200008:38
seb128pitti, thanks08:39
pittipopey: please let me know if there is any trouble; I know udisks rather well, so can help if there are any questions08:39
pittijust got bug 1011997, which reminded me about this :)08:39
ubot2Launchpad bug 1011997 in compiz "compiz crashed with SIGABRT in g_assertion_message()" [Undecided,New] https://launchpad.net/bugs/101199708:39
pittiI can reliably crash compiz by running udisks' test suite08:40
popeydelightful!08:40
seb128pitti, you probably want to talk to the unity hackers rather than the packagers, I will ping andyrock, I think he's the closer of a maintainer for that code08:40
pittiright; I pinged popey because I thought he would know best whom to assign/forward it to08:41
pittiseb128: merci08:41
seb128pitti, andyrock said he would work on it ... btw is the sigabrt a unity issue or a libgdu one?08:43
pittiI don't have the full stack trace yet, but I figure it's calling gdu_pool_get_by_device_file() with a NULL argument or so08:44
pittiit seems the code/logic for getting teh actual assertion message isn't working, meh08:44
pittithat even has a test in glib08:44
* pitti puts that on his todo08:44
seb128pitti, https://launchpadlibrarian.net/107405806/Stacktrace.txt08:44
seb128stacktrace from the retracer08:44
seb128interesting stuff are optimized out...08:45
seb128get_device_for_device_file (device_file=0x375a880 "/dev/sdb")08:45
mvoglatzor: awsome, let me sponsor that08:45
seb128though08:45
pittiget_device_for_device_file (device_file=0x375a880 "/dev/sdb") seems complete, though08:46
pittiso, presumably in libgdu08:46
* pitti reassigns08:46
mvoglatzor: I'm currently working on your python-apt MP for the auth stuff too08:47
pittiseb128: updated the bug, FYI08:47
seb128pitti, danke08:47
pittiseb128: I got your ping about bug 1010141, btw; on my todo list08:48
ubot2Launchpad bug 1010141 in gvfs "gvfs-gdu-volume-monitor automounts loop devices, preventing them from being unmounted" [Low,Triaged] https://launchpad.net/bugs/101014108:48
seb128pitti, danke08:48
seb128pitti, I got pinged by kees about it, I've the feeling the google guys are bothered about it ;-)08:48
chrisccoulsongood morning everyone09:03
didrocksseb128: oh, meeting report reminder!09:07
didrockshey chrisccoulson ;)09:07
seb128chrisccoulson, hey, how are you?09:07
seb128didrocks, thanks09:07
chrisccoulsonhi didrocks seb12809:09
chrisccoulsoni'm good thanks, how are you?09:10
chrisccoulsoni'd be better if i didn't have to drop everything to fix a bug i can't even reproduce though ;)09:10
jibelSweetshark, ping09:11
Sweetsharkjibel: pong09:11
jibelSweetshark, hey, I have setup an environment in the lab that builds LO periodically09:12
jibelit's currently setup to build from the pre-release PPA on Quantal09:13
jibelSweetshark, the results are here https://jenkins.qa.ubuntu.com/job/quantal-pkg-libreoffice/09:13
Sweetsharklemme guess, you want a 3.6 beta building against gcc 4.6 on quantal?09:13
jibelSweetshark, it's using 4.7 currently09:14
jibeland fails on i386 as expected09:14
jibelSweetshark, amd64 builds but make check fail09:14
jibelhttps://jenkins.qa.ubuntu.com/job/quantal-pkg-libreoffice/ARCH=amd64,label=albali/26/09:14
jibelSweetshark, is there any log I should collect from the build env when check fail ?09:14
Sweetsharknot as it is now, but with next upload (for quantal), ./debian/rules should set "ulimit -c unlimited" if you have gdb installed and that should give us a helpful stacktrace from the crashers ...09:17
seb128chrisccoulson, I'm good thanks09:18
Sweetsharks/stacktrace/stacktraces/09:18
Sweetsharkjibel: however, I am trying to force gcc=4.6 on quantal for now -- I dont see these issues on gcc-4.6.09:19
Sweetsharkjibel: so, it might be interesting to see if those are indeed introduced by gcc 4.709:19
Sweetsharksee https://launchpad.net/~libreoffice/+archive/libreoffice-prereleases/+sourcepub/2504240/+listing-archive-extra for the current build of beta on quantal (hopefully against 4.6)09:21
jibelSweetshark, ok, I updated the source and it's building.09:27
Sweetsharkjibel: as for archiving artifacts from that: while the logs should be a lot more helpful already with the new version and gdb around (because they then have stacktraces), it might actually be interesting to get the core dumps in the long run.09:43
Sweetsharkjibel: they should be generated by the build system then and might be rather helpful in debugging the issues ...09:44
=== rickspencer3_ is now known as rickspencer3
seb128Laney, hey10:56
Laneyhiya!10:56
seb128Laney, librhythmbox-core5_2.97-0ubuntu1_i386.deb contains librhythmbox-core.so.610:56
seb128Laney, can you fix?10:56
Laneyargs10:56
Laneyyes10:56
Laneyi'll merge it from debian, was going to do that anyway10:57
seb128Laney, sorry for not spotting that when sponsoring, I just trusted the update and uploaded, I noticed today because it's in Debian NEW and I looked what binary changed10:57
seb128Laney, thanks10:57
* Laney configures sbuild to run lintian11:02
=== MacSlow is now known as MacSlow|lunch
valentin_muhi guys, i have problems with google earth package - i see corrupted chars everywhere, have no menu "File"12:27
valentin_mu i tryed both deb from google and deb made by googleearth-package - they both have problems12:27
=== MacSlow|lunch is now known as MacSlow
=== slomo_ is now known as slomo
=== Ursinha` is now known as Ursinha
=== Ursinha is now known as Guest63012
cyphermoxseb128: mvo: re https://wiki.ubuntu.com/SoftwareAndUpdatesSettings . I'd like to start implementing the Drivers tab; but if it's all supposed to be stuff in our control center, seems like pretty high effort to reimplement the whole software-properties thing in g-c-c before being "able to" add drivers.13:55
cyphermoxOTOH, if the plan is to have this in software-properties for now, I guess it's much simpler13:56
seb128cyphermox, can we embed python in g-c-c? I think we can't right?14:08
seb128cyphermox, well I was not at the session at UDS, did we sign to make it a proper panel?14:08
seb128pitti, ^ do you remember what was stupid us to make panels in i.e python?14:09
pittiseb128: we didn't use the shell for a long time, so it didn't matter :)14:10
cyphermoxseb128: I have no idea on python in g-c-c14:10
cyphermoxseb128: ok, so from what I see in the blueprint perhaps I'm jumping ahead a little bit14:11
pittirodrigo_ looked into this, and AFAIR it was by and large "won't do"14:11
seb128pitti, well I think the "embed python" was discussed for u1 or similar in oneiric14:11
cyphermoxthere's no question of g-c-c in there, just software-properties14:11
seb128cyphermox, I would say "implement the design in software-properties" to start, we can do the "port to a g-c-c panel" later one, I think we do that most of the code will be able to be reused14:11
cyphermoxyes, most likely14:12
seb128pitti, do you remember if there was a technical limitation that blocked i.e python panels?14:12
pittiseb128: I don't know the details, I'm afraid (I never did)14:12
seb128pitti, I guess the loader code would need to be updated, it's loaded .so atm14:13
seb128pitti, ok, thanks14:13
seb128cyphermox, so, yeah, forget about g-c-c in a first time14:13
cyphermoxg-c-what?14:13
dobeygcc. not needed for python :)14:14
seb128cyphermox, exactly ;-)14:15
cyphermoxgah, glade dies on me14:16
jbichahmm, gnome-documents recommends unoconv which needs python-uno which pulls in libreoffice-core & -common14:20
cyphermoxcute.14:23
=== Guest63012 is now known as Ursinha
=== Ursinha is now known as Guest90889
=== Guest90889 is now known as Ursula
cyphermoxseb128: pitti: well, it's started; I'll get on looking at how I can display the information, but I'm keeping all in lp:~mathieu-tl/software-properties/additional-drivers15:04
seb128cyphermox, great15:04
cyphermoxUI is already there15:04
seb128cyphermox, you got glade to behave? ;-)15:05
cyphermoxyeah15:05
cyphermoxit was crashing because of the overlay scrollbars, somewhere in cairo15:05
cyphermoxthanks for reminding me, I should file a bug about this ;)15:06
seb128you should yes!15:06
seb128didrocks, chrisccoulson, Sweetshark, cyphermox, mlankhorst, Ursula, Laney, tkamppeter, mterry, kenvandine: 10 minutes before meeting if anyone has a topic to discuss15:22
didrocksseems there is nothing planned on the wiki yet :)15:22
chrisccoulsonhmmm, i really should add something to the wiki ;)15:23
chrisccoulsoncan i assign someone bug 1010466? thanks! :-)15:24
ubot2Launchpad bug 1010466 in firefox "dropdown boxes on sites stop working" [Undecided,Incomplete] https://launchpad.net/bugs/101046615:24
didrockschrisccoulson: you would feel jalous if we steal it from you :)15:25
chrisccoulsonheh, no, i wouldn't mind ;)15:25
kenvandineseb128, no agenda items from me15:25
* kenvandine is trying to get info for a partner update, but getting ignored15:25
chrisccoulsonheh15:26
seb128chrisccoulson, did you manage to reproduce?15:28
seb128chrisccoulson, I guess reassign to micahg if he can reproduce it?15:28
chrisccoulsonseb128, not yet. and none of the reporters have responded yet. i've tried using unity 2d all day, just in case ;)15:28
seb128micahg, could you have a look to https://launchpad.net/bugs/1010466 if you are able to trigger the issue? we are not...15:28
ubot2Launchpad bug 1010466 in firefox "dropdown boxes on sites stop working" [Undecided,Incomplete]15:28
chrisccoulsonyeah, that makes sense15:28
micahgseb128: I could only reproduce in thunderbird, and even then, I don't think it was every time16:08
seb128micahg, can you try to see if you can get it again? it might be useful to have somebody around who can reproduce to get us debug infos at least16:13
micahgseb128: sure16:17
chrisccoulsonthe timestamps in X events are in units of milliseconds, aren't they?16:39
chrisccoulsonactually, may be one for #ubuntu-x16:39
brycehchrisccoulson, yep16:41
chrisccoulsonbryceh, ah, thanks :)16:41
chrisccoulson(sorry, just asked on #ubuntu-x as well) ;)16:41
=== rickspencer3 is now known as rickspencer3_
=== rickspencer3_ is now known as rickspencer3
didrockssee you tomorrow guys! :)17:00
seb128pitti, are you still around?17:11
bigonpitti: I've seen you name in the consolekit changelog, so maybe you will have more clue than me21:39
bigonare you around :)?21:39
jasoncwarner_robert_ancell RAOF TheMuso just a reminder about the meeting, wiki and agenda items: https://wiki.ubuntu.com/DesktopTeam/Meeting/2012-06-1222:16
jasoncwarner_and bryceh ^^22:17
* bryceh waves22:18
chrisccoulsonhowdy people from the other hemisphere22:50
TheMusochrisccoulson: Hey there.22:51
chrisccoulsonhi TheMuso, how are you?22:51
TheMusochrisccoulson: Nice catch re unity and C++ ABIs.22:51
TheMusochrisccoulson: Not too bad thanks, yourself?22:51
chrisccoulsonTheMuso, yeah, that was a fun one. and i've spent all day today tracking down another nice bug :)22:51
chrisccoulsonother than that, i'm not too bad thanks22:52
* TheMuso feels much more justified in not liking C++ to the point where he feels he'd rather not learn more than he absolutely has to.22:52
TheMusoAll this stuff that pops up with C++ ABIs and gcc issues every minor release puts me right off the language.22:53
* micahg likes C++ much more than the PHP he used to work with22:53
chrisccoulsonTheMuso, oh, C++ isn't too bad. it's the STL that sucks ;)22:54
TheMusoIts not hard to be better than php. :)22:54
TheMusoYeah but thats rather heavily used afaik.22:55
jasoncwarner_TheMuso robert_ancell RAOF bryceh doesn't look like any agenda items...so no meeting. please update the wiki when you get a chance.22:55
* micahg thought the purpose of the STL was to not have to reinvent the wheel22:55
chrisccoulsonthe purpose of the STL is to make yourself suicidal :)22:56
TheMusojasoncwarner_: Done thank,22:56
TheMusothanks22:56
brycehjasoncwarner_, thanks22:57

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!