/srv/irclogs.ubuntu.com/2009/11/02/#ubuntu-devel.txt

amikropHello. Please package the latest gnome-screensaver into the main repos, because it now has the bug of not being able to stop when playing fullscreen movies.00:42
amikropA signal (I think --poke) does not work with the current version.00:42
amikropBut now there is a patch.00:42
MsMacois a bug filed?00:42
amikropI think.00:42
superm1yes, siretart was on that shortly before release00:42
superm1i'm not sure what happened of it though00:42
MsMacohi superm100:42
superm1hi MsMaco00:43
ajmitchsuperm1: it's in a PPA, I'm guessing he might look at getting it into -updates00:43
amikrophttps://bugs.launchpad.net/ubuntu/+source/vlc/+bug/42888400:43
superm1i sure hope so. it's certainly a very suboptimal experience right now00:43
ubottuUbuntu bug 428884 in gnome-screensaver "gnome-screensaver --poke functionality does no longer inhibit screen blanking" [Unknown,Confirmed]00:43
amikropI think this is the report. So, is the package ready to get available as an update?00:44
MsMacosuperm1: im going to be attempting to make a dkms-based package soon, going off that UDW session you did a while back. if i get stuck, do you mind if i poke you?00:44
superm1MsMaco, it would be better if you did said poking tomorrow, but yes feel free00:44
superm1things are actually significantly easier nowadays too00:45
superm1and will only be improving now that debian is working on dh_dkms :)00:45
mneptokamikrop: is the person that fixes that bug the "Screen Savior?"00:45
MsMacoah, i wont be attempting it today anyway. i have to migrate laptops so i can send this one for a replacement hinge. lid's almost detached :(00:45
ajmitchmneptok: puns like that should be shot00:46
superm1ah, then that would make it quite difficult to work with.00:46
wgrantAre the powerpc buildds still running Dapper?00:47
MsMacowill also make it difficult to test with since the hardware itd be enabling is on the to-be-fixed laptop :P gonna get bugabundo to test it for me ;)00:47
amikropmneptok: :P00:47
=== iWolf[Ubuntu] is now known as iWolf
amikropsuperm1: excuse me, but I didn't get what it is going to happen with this case00:49
amikropthe package is ready and it is going to be moved on official updates?00:49
superm1amikrop, i've not followed the details here, but once the proper fix has been developed, it will be put into -proposed00:49
ajmitchamikrop: no, from reading the bug, the package is mostly ready but needs some further work00:49
wgrants/will/may/00:49
bluefox_why is rhythmbox stupid?00:50
superm1people will need to verify that it works, and it will live there for about 2 weeks, and then go to updates if it fixes the problem properly without introducing regressions00:50
ajmitchwgrant: I think siretart plans to follow through with fixing it :)00:50
MsMacobluefox_: because applications lack brains?00:50
* bluefox_ saves a file into ~/Music/, rhythmbox sees the .part and then loses the file when the .part is lopped off and the file's called .mp300:50
amikropsuperm1: wow. would you suggest any workarounds until then?00:52
iWolfIs there any Community Council Members Here?00:53
MsMacoiWolf: pleia2 is signed on to freenode, but she's afk right now00:57
iWolfAnyone else00:57
wgrantiWolf: Why do you want a CC member?00:57
iWolfI need to ask a question00:58
iWolfCommunity Council Related00:58
iWolfCommunity*00:58
lifelessjust ask it00:58
lifelessif we can't help we'll point you at the list00:58
iWolfIts about Teams00:58
iWolfCheck this bug: https://bugs.launchpad.net/ubuntu/+bug/464710/01:04
ubottuUbuntu bug 464710 in ubuntu "LiveCD freeze" [Undecided,New]01:04
iWolfProblem with distro?01:04
jgoppertI'm trying to repackage libjsw on my ppa. My first go at this. Anyways it doesn't work for karmic due to a gtk 1.2 dependency. I've got a quick fix that will work but I can't figure out dpatch. I try to modify debian/rules not to run the makefile in the jscalibrator directory and somehow after i create the patch and apply all patches it still tries to call the makefile in this directory. I think it is possibly that someone unp01:13
MsMaco"someone unp..." cutoff01:14
jgoppertI think it is possibly that somehow unpatch is being called by build and that somehow allows make to run on an unpatched debian rules file?? help??01:14
ebroderjgoppert: You can't patch debian/rules using dpatch. Just edit it directly01:15
RAOFAnd you're right: unpatch will be a part of the clean target, which will be run first in the build process.01:15
jgoppertok thats kind of what i thought was going on, so i modify the original tarball? or how do i go about that01:16
jgoppertstupid question i know but i've tried that and have been very lost, do i do it in the patch to the original tarball? like the .gz.diff01:17
RAOFYou don't modify the original tarball, you modify the packaging directly, then the source package contains your changes in the diff.gz.  This is better suited to #ubuntu-motu, by the way.01:17
jgoppertok thanks for the help guys01:17
jgoppertthey are kind of dead over there a motu, so anyways i figured out what i was doing and got libjsw packaged, i noticed that when uploading to the ppa i just give it my .changes file, but since there is no original tarball on my ppa do i need to upload that as well, the tarball is also not in karmic yet01:29
ScottKjgoppert: #ubuntu-motu really is more appropriate than here.01:43
bluefox_okay I'm going to ask this before going forward.01:54
bluefox_Did someone hard-disable IP forwarding in the Ubuntu kernel?01:54
ionWorks in 2.6.31-14-generic-pae01:57
bluefox_nevermind I'm dumb01:59
* bluefox_ writes a firewall rule for IP masquerading.01:59
dtchennot that I can see. /etc/sysctl.conf unsets the /proc bits by default, but that's fairly straightforward to enable.02:00
bluefox_Yeah, I had forgotten that I have to do PAT for this to work.02:00
slangasekpitti: is there some straightforward way that apport could check for "package is already installed and configured" as the error message, and file the bug against dpkg or apt or something instead of the individual package which isn't at fault?02:47
lifelessslangasek: probably; we can haz bug plz?03:01
slangasekdone03:01
MsMacololspeak is an accepted dialect here?03:06
StevenKMsMaco: Sometimes.03:07
emgentccheney`: ola ola03:08
syn-ackI know its waaaaaaaaaay OT but you guy have GOT to see this: http://www.youtube.com/watch?v=pAoqOCQlb0E03:08
syn-ackI'm still laughing03:08
lifelessMsMaco: selectively :)03:16
=== Whoopie_ is now known as Whoopie
laptopnenolodso, umm03:39
laptopnenolodmountall has some weird bug where it hangs when ran on Xen03:39
eboyjrDoes Quickly have a dev website besides Launchpad?06:57
eboyjrhttps://wiki.ubuntu.com/Quickly is good, nvm06:58
=== jussi01 is now known as jussi01_
dholbachgood morning07:10
eboyjrdholbach, good night07:24
dholbachhi eboyjr07:25
eboyjrLol hiya.. It's night over here :P07:26
dholbach:)07:26
pittiGood morning07:51
omanig morning07:51
pittiMsMaco: no problem :)07:52
pittislangasek: yes, should be easy; found the bug07:54
pitti(... report)07:54
lifelessanyone spent any time looking into the wrong kernel/initramfs after upgrading to karmic?08:00
MsMacolifeless: dan's been looking08:01
MsMacoapparently users are prompted about keeping old config or using new one08:01
MsMacoand are choosing to keep the old config08:01
MsMacoand thus grub is not updated08:01
lifelessMsMaco: I wasn't prompted...08:01
slangasekpitti: ok - morning :)08:01
pittislangasek, mvo: for disabling apport again after that dist-upgrade, would I do the conffile change in preinst or postinst? I think "preinst", to avoid conffile questions, right?08:03
MsMacolifeless: nor was i. thats the confusing bit. no idea what determines who is prompted08:03
mvoI think preinst08:03
pittisince "no" is the default08:04
slangasekpitti: I don't think there's much difference, really - since the conffile shouldn't have changed between the previously installed version and the current one, there'd be no conffile prompt anyway08:04
slangasekpreinst lets you correctly handle the exceptional case where the user has removed apport and is reinstalling it08:04
pittislangasek: ah, true08:05
slangasekso preinst is a bit better :)08:05
slangaseklifeless, MsMaco: has anyone grabbed a copy of one of these "Don't install the maintainer's version" menu.lst files yet?08:05
pittichanging conffiles in maintainer scripts is new territory for me, so I better double-check08:05
lifelessslangasek: let me see if a backup was kept by update-grub08:06
slangasekupdate-grub keeps one backup08:06
lifelessMsMaco: whats the bug #08:07
=== dholbach_ is now known as dholbach
MsMacolifeless: there isnt a single bug. there's hundreds of bugs over the last 3 days that dtchen has triaged08:12
MsMacoof people with "no sound after upgrade" because they're using the wrong kernel08:13
MsMacoslangasek: no idea. dan may have08:13
MsMacoslangasek: he's asleep though08:13
lifelessMsMaco: there should be a single master bug or the failure to upgrade the menu.lst correctly08:14
MsMacoi guess...vast majority are being filed as audio bugs08:14
MsMacothere's also the caveat that some of these people, when told to use the right kernel...end up with no X08:14
MsMacoso they have to choose between 2.6.31-with-sound-but-no-X or 2.6.28-with-X-but-no-sound08:15
MsMaco(ive spent a lot of time on the forums the last few days)08:15
slangaseklifeless: well, they're each going to have to be looked at individually regardless, because many of these are likely to be "I changed menu.lst by hand, then update-grub did what I told it to" - there's no way to fix that other than using <blink> tags in the release notes, the menu.lst format is crap and this was a major reason for pushing grub208:16
slangasek(too bad we didn't get grub2 by default on upgrade, this cycle)08:16
lifelessslangasek: sure, they have to be looked at08:17
lifelessslangasek: so, is the bug, 'if any menu.lst changes were made, we fail to run update-grub' ?08:18
slangasekno, not atall08:18
lifelessslangasek: then I totally misunderstood what you said08:18
slangasekwe run update-grub, update-grub pops up a message informing the user that there's a conflict between their local changes and the changes the system wants to make, user clicks through "keep my changes" and ends up not getting entries for the new kernel08:19
MsMacowhereas it should be more of a merge?08:19
slangasekmerge is one of the options the user didn't choose08:19
lifelessslangasek: ok. That doesn't match what happened to me.08:19
slangaseklifeless: gonna need more info, then08:20
lifelessslangasek: I upgraded, rebooted, no sound. Ran 'sudo update-grub', which did not prompt me at all. Rebooted, had sound (though initially muted).08:20
slangaseklifeless: and the kernel package was in 'installed' state?08:20
lifelessI have the backup menu.lst.08:20
slangasekhit me08:20
MsMacooh. what dan saw in one comment looked more like "i upgraded, during upgrade i was prompted, i chose no, rebooted, and had no sound"08:20
lifelessslangasek: I can make no assertions about the kernel packages state at the time, i didn't think to check.08:20
slangaseklifeless: have you run update-manager or apt or dpkg since then?08:21
lifelessslangasek: I think so08:21
slangaseklifeless: ah; well, give me time stamps for the menu.lst files and full dpkg/apt logs as well, then :)08:21
lifelessslangasek: what bug do you want it on08:21
lifelessor should I make a new on?08:21
lifelessone?08:21
slangaseklifeless: feel free to open a new one on grub08:21
* lifeless pops through to the other machine08:22
slangasekthese other bugs apparently haven't been getting triaged over to the grub package yet, so I've only seen the barest trace of this issue08:22
MsMacoslangasek: look at pretty much any "alsa-driver" bug in the last week...08:22
MsMacodan sent one of 'em to you two in email08:23
MsMacohe pasted a link to another comment along the same lines in here earlier, but i dont have scrollback08:23
lifeless108576 could be a candidate08:24
slangasek*week*?  and no one thought to escalate it before the release?08:24
MsMacohe said he hit a couple of these weird "booting into the wrong kernel" ones back around beta but didnt notice the trend08:25
slangasekMsMaco: I have one thread in my mailbox about this starting Saturday, though lifeless isn't Cc:ed, so not sure if that's who you mean by "you two"08:25
MsMacolifeless = robbie?08:25
slangasekMsMaco: hah, no08:25
MsMacooh oops08:25
JanCaccording to crimsun some changes need a 2-5 min power down before they work because of crappy hardware, so that might also accidentally explain what lifeless saw...08:25
slangaseklifeless: 108576> unlikely to be the same bug, the ucf-based update-grub handling didn't exist back then08:25
slangaseklifeless: well.. might be the same as /your/ bug, but not the same as the other one I'm complaining about08:26
lifelessslangasek: kk08:26
lifelessslangasek: is apt/term.log useful?08:27
MsMacoi only heard about grub not updating when a week before release someone in #ubuntu+1 said current was -10 because his grub hadnt been updated since then08:27
slangaseklifeless: apt/term.log and dpkg.log both; I expect I'll need to cross-reference08:27
lifelessanything sensitive in term.log? its 050008:28
MsMacoshouldnt be...its just the spew from apt-get install type operations08:29
lifelessno passwords ?08:29
slangasekright, I'm not aware of anything sensitive; they routinely get copied to bug reports without setting the 'private' bit08:30
slangasekpasswords> God, I hope not08:30
slangasekthat would be Special08:30
lifelessok08:30
MsMacohaha08:30
lifelessslangasek: bug 47026508:31
ubottuLaunchpad bug 470265 in grub "intrepid to karmic upgrade failed to update menu.lst" [Undecided,New] https://launchpad.net/bugs/47026508:31
lifelessbug 47026508:31
lifelessbug, ubottu fail..08:31
lifelessbug, ubottu fail..08:31
lifelessbug 47026508:32
* lifeless shrugs08:32
lifelessslangasek: its there, ping me if you want more.08:32
slangasekintrepid to karmic, eh?08:32
slangaseklifeless: will do, thanks08:32
lifelessslangasek: jaunty.08:32
slangasekok :)08:32
* lifeless slaps himself08:32
slangaseklifeless: timestamps on menu.lst*?08:32
slangasek(need to know where to line it up with in the logs)08:32
lifelessslangasek: the backup appears to be open, copy data as opposed to 'cp -a' or 'mv'08:33
lifelessslangasek: the timestamp is unlikely to be useful, still - I've attached it08:33
slangasekright, ok; that limits its usefulness, but I should be able to get something out of it08:34
slangasekhuh, the diff is telling08:35
slangasekupdate-grub has only successfully run once since the new kernel was unpacked08:35
lifelessright08:35
lifelessI just don't know *why* :)08:35
slangaseklifeless: grep postinst_hook /etc/kernel-img.conf ?08:36
lifelesszip08:38
slangasekwe really ought to put those hooks in /etc/kernel/postinst.d instead of relying on the installer's setup to have infinite shelf life08:38
lifelessnada08:38
lifelessnothing08:38
slangaseklifeless: that's it, then.  On a normal system, you should see 'postinst_hook = update-grub'08:38
lifelessI haven't touched kernel-img.conf08:38
slangaseklifeless: when was this machine installed, and how?08:38
lifelessso the bug is 'somehow kernel-img.conf is missing postinst_hook'08:38
slangasekdid you ever have lilo on it instead of grub?08:39
lifelessno, its my new i7 desktop08:39
slangasekplease post your full kernel-img.conf to the bug08:39
lifelesswhich dates it08:39
pittislangasek, mvo: apport fix committed (see bug followup, and http://bazaar.launchpad.net/%7Eubuntu-core-dev/ubuntu/karmic/apport/ubuntu/revision/1570); quick eyeballing appreciated08:41
lifelessslangasek: done, with datestamp08:41
lifelessslangasek: which is either the jaunty cd datestamp, or when I installed the machine.08:41
slangaseklifeless: ack, thanks08:44
lifelessslangasek: I'm quite sure I installed jaunty fresh on it08:44
slangasekhmm, disturbing thought that all jaunty installs from liveCD might have this problem :/08:44
* slangasek will start poking at the livefs08:44
lifelessits certainly never had lilo on it08:44
slangasekright08:45
lifelessWas it a livecd install? I think so. dmraided though, so I may have manually partitioned08:45
lifelesstheres probably a log somewhere ;)08:45
lifelessindeed, installer logs are present if you want them08:46
slangaseklifeless: oh awesome, please attach those also :)08:46
slangasek(anyone wandering by this bug is going to be completely confused by the stack of attached files)08:46
lifeless21 april is the deb timestamp08:46
lifelessslangasek: are passwords in the installer logs?08:47
slangasekpitti: $1 check is superfluous but not wrong; bdmurray pointed out on the bug that release-upgrader 0.126.5 would also have this bug, so best to grep for 0.126.[56].  Otherwise, looks ok to e08:49
slangasekme08:50
slangaseklifeless: nope08:50
slangasek(man, what do you take us for :)08:50
pittislangasek: ah, thanks08:50
slangasekoh hey, I don't have to download a copy of the jaunty ISO to check this, do I08:51
slangasekthe bandwidth of me walking across the house and back is awesome08:52
pittislangasek: I just noticed that apport doesn't upgrade with being disabled (the upstart job failed, which causes postinst to fail); I'll file a bug and fix this first08:53
slangasekpitti: meep; methinks we should have a session on writing upstart jobs at UDS08:54
pittislangasek: oh, nevermind; it's the new lucid debhelper apparently08:56
slangasekoh, hmm08:57
pittiit adds an additional invoke-rc.d call08:57
slangasekmismerge?08:57
mdkeslangasek: pitti: I wonder if you have any ideas on the cause of bug 464037 - we have two duplicates (from Dell machines) and I can confirm it myself when installing gnome-user-guide-gu. I've read through the build log but can't figure it out, I wonder if it is something to do with pkgstriptranslations. Not urgent, but if you have any bright ideas...08:57
ubottuLaunchpad bug 464037 in gnome-user-docs "package gnome-user-guide-gu (not installed) failed to install/upgrade: trying to overwrite '/usr/share/omf/gnome-access-guide/gnome-access-guide-C.omf', which is also in package gnome-user-guide 0:2.28.0+git20090921ubuntu2" [Medium,Confirmed] https://launchpad.net/bugs/46403708:57
lifelessslangasek: I've written a good summary I hope08:57
slangasekpitti: oh, you merged it ;)08:57
pittislangasek: well, most of the upstart bits were committed to debian, so apparently there was an eror somewhere; will look into this after I'm done with this SRU08:58
lifelessMsMaco: this bug is the master, if you have other bugs where just upgrade-grub fixed the problem (no prompts being asked, just-worked), please feel free to close them as dups to this bug08:58
slangasekpitti: no, only *some* of the upstart bits were committed to Debian, then Keybuk extensively modified debhelper again after I'd negotiated that patch with joeyh08:58
lifelessslangasek: the concept of this being every or even  many livecd installs is scary-as08:59
slangasekso the chance of a mismerge is actually quite high08:59
pittislangasek: yeah, there were some bits which weren't accepted, I merged those08:59
pittiespecially the --only-upstart bits09:00
slangaseklifeless: indeed - but it gives us a nice way to clean up all the bug reports at once09:00
slangasekpitti: well, it's not that they weren't accepted, it's that they haven't been submitted... anyway, I guess you'll be able to sort it now that you're looking at it :)09:00
slangasek[281264.038921] SQUASHFS error: Major/Minor mismatch, older Squashfs 3.1 filesystems are unsupported09:00
slangasek<cough> right, how do I mount a jaunty squashfs :P09:01
MsMacolifeless: alrighty09:01
lifelessslangasek: someone claimed that the initramfs could be stale too, but I haven't seen data to corroorate that09:02
lifelesss/oo/obo09:03
slangasekthat'd be a separate bug, and should only ever happen when the kernel package has failed to finish installing09:03
MsMacoyeah i saw one person in #ubuntu where initramfs was wrong after an update-grub. the initramfs existed, so i just told them to edit it manually and it worked09:03
MsMacoer edit menu.lst manually09:03
MsMacoslangasek: inside a jaunty vm?09:05
slangasekMsMaco: no virtualization capabilities here09:05
slangasekif I had a jaunty vm, I wouldn't need to loopback mount the CD, I could just... boot the CD :)09:05
slangasek(which is what I'm going to end up doing as soon as I wrap this email)09:05
MsMacoi can look if you tell me what to look for09:06
wgrantcjwatson, slangasek: How important is v3 source package support before 2009-12-05?09:06
slangasekMsMaco: I want the contents of /etc/kernel-img.conf from inside the livefs09:07
slangasekMsMaco: specifically, I'm comparing it with http://launchpadlibrarian.net/34936461/kernel-img.conf09:07
MsMacook09:07
pittiwgrant: we'll start the syncs/merges from Debian in the next days, so if we need it at all, we need it soon, I guess09:08
slangasekwgrant, pitti: well, I wonder how quickly the new formats are going to be adopted - so far we just have buxy's one test package, right?09:10
slangasekand if we're autosyncing from testing, that's 10 days grace period09:10
wgrantRight. It's unclear exactly how quickly it will be adopted.09:10
pittislangasek: apport waiting in karmic/unapproved now09:10
pittiwgrant: right, that's the "if we need it at all" (for lucid) bit09:11
pittiI haven't seen such a package yet09:11
slangasekpitti: ok; may not get a chance to approve that 'til morning09:11
wgrantpitti: There is only one in the Debian archive at the moment.09:11
slangasekpitti: there's one test package in the archive; I know buxy is chomping at the bit to be able to start uploading them :-)09:11
pittiif it's only two or so, we can easily rebuild them on our side for lucid09:11
wgrantBut dak only gained support for it last week.09:11
\shmoins09:13
MsMacolifeless: wait where's that bug number?09:14
MsMaco470265?09:15
lifelessbug 47026509:15
ubottuLaunchpad bug 470265 in grub "[MASTER] intrepid to karmic upgrade failed to update menu.lst (update-grub missing from kernel-img.conf)" [High,New] https://launchpad.net/bugs/47026509:15
lifelessoh wow ubotto fail09:15
lifelessor hmm09:15
lifelessno slangasek trampled on my edit09:15
lifelessit should say jaunty09:15
slangasekheh09:15
slangasekthank AJAX :)09:15
lifelesshell no09:16
lifelessleast you didn't edit the description09:16
lifeless:)09:16
* slangasek grins09:16
\shoh that bugged me too...and I thought I messed my installation (intrepid -> jaunty -> kernel update fail)09:16
MsMacolifeless, slangasek: ok, livecd's /etc/kernel-img.conf attachd to bug09:17
MsMacolifeless: it says jaunty when i look in firefox in the vm09:17
slangasekMsMaco: thanks09:18
MsMaconp09:18
lifelessMsMaco: yes, cause I just fixed it ;)09:18
slangaseklifeless: was yours i386 or amd64?09:18
lifelessamd6409:18
slangasekok09:18
slangasek(probably doesn't matter, just wondering which livefs build logs to look at)09:19
slangaseksomebody want to check the kernel-img.conf in a *karmic* livefs?09:19
MsMacobooting i386 karmic...09:20
slangasekno mention of kernel-img.conf anywhere in the livefs build log for jaunty final, so not sure what actually generates the one that's there in the livefs - the kernel package, maybe09:21
slangasekwell, when ubiquity calls grub-installer it should unconditionally add its hooks to /etc/kernel-img.conf09:25
MsMacostill need the karmic live cd's /etc/kernel-img.conf?09:26
lifelessslangasek: what one in the live fs ?09:27
slangasekMsMaco: might be nice for reference09:27
lifelessMsMaco: yes, I'd say that that is a useful thing.09:27
MsMacook09:27
slangaseklifeless: the /etc/kernel-img.conf09:27
lifelessslangasek: not the file, the hook :)09:27
lifelesshttp://launchpadlibrarian.net/34939246/kernel-img.conf - no hook09:27
lifelessI wonder if it might be an ordering problem09:28
lifelessgrub-installer before /etc/kernel-img.conf exists09:28
lifelessif grub-installer is depending on dpkg hooks to run lazily at the right time09:29
buxyslangasek: everybody can upload new packages using new formats, I did logitee-tools, quilt itself and ftplib09:29
slangaseklifeless: not in the karmic version of grub-installer; checking jaunty now09:29
slangasekbuxy: quilt> bah :)09:29
slangasekbuxy: anyway, obviously everybody /can/ upload packages in the new format, I just have no feel for how many /will/ do so or how quickly09:31
buxyslangasek: that depends also whether I make dpkg-source produce new formats by default or not :)09:31
slangasekugh09:31
slangasekwell, that would neatly screw Ubuntu over until LP supports v3, then09:31
buxyit has been accepted as release goal, and there aren't that many packages failing to build with new formats, see http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=hertzog@debian.org;tag=3.0-quilt-by-default09:32
slangasekit's been accepted as a release goal to make it the /default/?09:33
slangasekthat's not mentioned on http://release.debian.org/squeeze/goals.txt or http://wiki.debian.org/ReleaseGoals/NewDebFormats09:34
buxy"Have all packages in the archive buildable using the new source package formats." => this is my prerequesite to enable dpkg-source to produce new format by default09:35
slangasekwell, yes, but that doesn't mention anything about actually /making/ it the default for squeeze...09:36
buxywell, the other half is my responsibily as dpkg (co-)maintainer, I can surely make that decision? and it's not like I haven't made it clear since quite some time09:37
lifelessbuxy: changing the default will affect every derivative distro09:39
slangasekobviously if we're having this conversation, it wasn't clear to me that you meant to make it the default for squeeze09:39
slangasekit is your decision; I'm informing you of one side effect of this decision09:39
buxybut it needs some fine-tuning still, I will probably solicit some input09:39
buxyslangasek: I'm still not sure we can make it for squeeze, it has taken much longer than what I hoped09:40
Whoopiejdong: thanks for ACKing bug 427217. What are the next steps?09:40
ubottuLaunchpad bug 427217 in openwsman "FTBFS in karmic" [High,In progress] https://launchpad.net/bugs/42721709:40
al-maisanEOCHAN09:55
buxyslangasek: is there a launchpad ticket requesting support of the new format in the ubuntu infrastructure?10:02
slangasekwgrant: ^^ ?10:02
wgrantBug #29310610:03
ubottuLaunchpad bug 293106 in soyuz "does not support debian v3 source formats" [Critical,In progress] https://launchpad.net/bugs/29310610:03
wgrantThe code is pretty much done.10:03
wgrantBut it is very very awkward timing.10:03
buxythanks, I subscribed to it, if you have questions just ask10:05
slangasekMsMaco: well, so far my sampling of recent alsa-driver bugs yields me only reports from people who /are/ running the karmic kernel10:07
slangasekhmm, a lot of checkbox bugs10:09
fatal^buxy: debian bug #485137 should be fixed in unstable (sometimes during the 2.27.x experimental era).... would be nice if you could confirm that (and tag the bug appropriately)...10:22
ubottuDebian bug 485137 in totem "totem: FTBFS when converted to new source format 3.0 (quilt): diff.gz contains cruft" [Minor,Open] http://bugs.debian.org/48513710:22
buxyfatal^: the recipe to reproduce is easy, why don't you do it yourself?10:24
MacSlowtseliot, yeah... let's hope that "special driver" is an OpenSource one10:24
* tseliot nods10:24
fatal^buxy: no time/interest/access_to_suitable_system at the moment. will probably forget it, so I thought it might be slightly better to poke you about it now.10:25
MacSlowtseliot, th GPU-core in the GMA500 isn't too bad... has geometry-, vertex- and fragment-shaders in hw10:25
buxyfatal^: it might be better to record that information in the BTS10:25
buxyI don't have time for such individual request, if I do anything like that it will be automated over all the bugs I submitted :)10:26
tseliotMacSlow: yes, it doesn't draw too much power and has hardware HD video decoding10:26
tseliotso it's good on the paper10:26
MacSlowtseliot, afaik the same GPU-core also drives the iPhone's screen10:27
tseliotpower-VR?10:27
MacSlowtseliot, yes10:27
tseliotlet's cross our fingers and wait then :-)10:28
SandGorgonis Ubuntu going to follow XDG desktop specifications (http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html) - for config file locations ?10:43
=== Shockrates is now known as Suckerats
=== Suckerats is now known as Linus
=== Linus is now known as LinusTorvalds
=== Shockrates_ is now known as avs2
=== MacSlow is now known as MacSlow|lunch
=== stefanlsd1 is now known as stefanlsd
pittiSandGorgon: we try, anyway; but of course there's still a lot of old upstream software which doesn't12:19
lucasgah. ruby1.8 needs a SRU. The version in unstable/testing fixes several major bugs, but nobody noticed :(12:42
sorenDo we have an expected ETA for when Lucid opens? Do we expect it to be this week?12:43
mvosoren: rumors in #ubuntu-release say soon, almost certainly this week12:51
sorenmvo: Cool. Thanks.12:56
=== fenris__ is now known as ejat
=== MacSlow|lunch is now known as MacSlow
pittisoren: still waiting for a debhelper fix to publish, then I think we're ready13:24
pittisoren: feel free to upload already (it'll land in the queue)13:24
=== mrpouit is now known as mr_pouit
=== bigjools is now known as bigjools-lunch
tseliotMacSlow: http://www.phoronix.com/scan.php?page=news_item&px=NzY2Mg13:43
sorenpitti: Great. Thanks!13:52
=== jamie is now known as Guest47125
=== bigjools-lunch is now known as bigjools
englaDktrKranz: thanks for your work on Kupfer. I think next version is going to default to install in DATADIR14:46
engla(install its python package there). I think it's smarter anyway, and as long as the binary is in the $PATH, there is no trouble to find the package14:46
DktrKranzyup :)14:46
englabut it is strange for a linux package to be installed all in one directory like that14:46
DktrKranzwell, it's one of the features provided by python packaging, in case someone ever wants to package some "kupfer" module, and make it available system-wide, we're safe14:49
dholbachhttps://wiki.ubuntu.com/UbuntuOpenWeek kicking off in 1 minute in #ubuntu-classroom14:59
=== mtrudel_ is now known as cyphermox
=== jcastro_ is now known as jcastro
=== funkyHat is now known as funnyHat
=== funnyHat is now known as funkyPants
=== dendro-afk is now known as dendrobates
=== funkyPants is now known as funkyHat
mantienaHi all15:11
mantienaI've noticed lots of identifical bugreports about jaunty->karmic upgrading problems when users have ttf-mscorefonts-installer (same bug occurs when also during installation ttf-mscorefonts-installer package, but not so often), maybe someone from Ubuntu developers can assign bug #464422 to the right person and increase importance ? Every day since karmic release about 10 identifical bugs are reported about this problem :(15:13
ubottuLaunchpad bug 464422 in baltix "fail to complete upgrade jaunty > karmic ttf-mscorefonts-installer" [Undecided,New] https://launchpad.net/bugs/46442215:13
mantienaThis problem appears because ttf-mscorefonts-installer always tries to download fonts from internet servers without asking if user wants to do this and returns an error if there are no access to the fonts download locations15:13
=== yofel_ is now known as yofel
=== marjomercado is now known as marjo
hdonhi all. does the libevent-dev package even work at *all*? it seems to contain errors :(15:59
* hdon wonders if it has been tested15:59
nxvljames_w`: ping16:15
nxvljames_w`: i'm trying to bzrize a package, but i can't find any documentation in https://wiki.ubuntu.com/DistributedDevelopment/Documentation/16:15
james_w`hi nxvl16:15
nxvljames_w`: i remember that with svn there was a way to do that from the dsc16:16
james_w`nxvl: a new package?16:16
james_w`oh16:16
james_w`bzr import-dsc16:16
nxvljames_w`: yup16:16
nxvljames_w`: awesome, will check the manpage for that, thank you16:16
james_w`bzr help import-dsc will get you started16:16
james_w`also file:///usr/share/doc/bzr-builddeb/user_manual16:16
* nxvl HUGS james_w` 16:17
kklimondajames_w`, will there be a way in future to work completely in VCS? Download upstream source though svn or git, merge with package branch and release ready source package?16:23
Laneywill need to run autogen.sh or similar16:24
kklimondaLaney, i know, i know16:24
james_w`kklimonda: yes16:24
LaneyI once tried to package f-spot based on the git tags, then decided it was too much work16:25
joaopintois /etc/rc.local expected to be called on Karmic boot ?16:31
=== james_w` is now known as james_w
=== mathiaz_ is now known as mathiaz
_lemsx1_the lsb-base package on Ubuntu introduces /etc/lsb-base-logging.sh which is supposed to be provided by sysadmins and other packages wanting to change the way init functions are called. this is inconvenient for others16:42
_lemsx1_there are 4 new bugs that should be merged with this one LP #32808916:43
ubottuLaunchpad bug 328089 in splashy "[Jaunty] splashy 0.3.13-3ubuntu1 fresh install conflicts with lsb-base" [High,In progress] https://launchpad.net/bugs/32808916:43
_lemsx1_now that karmic is out, i want to get this resolved some how...16:44
=== beuno is now known as beuno-lunch
=== asac_ is now known as asac
feisarI know this is officially not the right place to ask for support but the normal channels seem clueless. How do I add a new user with an encrypted home? --encrypt-home does not work in 9.10, it did in 9.0417:02
=== jsalisbury_ is now known as jsalisbury
bdmurraypitti: Do you know why apport-kerneloops reports are still coming in about karmic?17:14
pittibdmurray: unfortunatly kerneloops wasn't disabled before release; james_w wanted to look into this AFAIR17:14
bdmurraypitti: we are getting lots and lots of these17:15
james_wpitti, bdmurray: just uploading to -proposed now17:18
bdmurrayjames_w: is there a bug number so we can get it verified quickly?17:18
bdmurraysbeattie: ^17:18
pittijames_w: thank you!17:18
james_wbug 47113717:20
ubottuError: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/471137)17:20
zulso umm I know this has been asked before but is lucid open yet?17:52
ograzul, https://wiki.ubuntu.com/LucidReleaseSchedule17:53
ogragive it till end of the week17:53
zulogra: thanks17:54
=== beuno-lunch is now known as beuno
jdongpitti: potential verification-failed on bug 415766; ebroder's latest comment?18:13
ubottuLaunchpad bug 415766 in openafs "evince makes openafs to kernel oops" [Undecided,Fix committed] https://launchpad.net/bugs/41576618:13
ebroderjdong: I'll admit that I have no idea how that interacts with dkms, which you may care about more than module-assistant18:15
hoontekeis there a way to mirror an ubuntu via bittorrent?  I don't mean just offering bittorrent, I mean saving some mirror's bandwidth by utilizing bittorrent to download it my private mirror.18:21
=== akgraner_ is now known as akgraner
jdongebroder: yeah I have no idea either18:33
ebroderI guess I could go poke at that for a second18:33
MsMacoif it should be -1 not 0.1, jdong made me do it!18:33
MsMacos/-//18:33
ebroderNo, no - it should definitely 0.118:34
ebroderIt's a question of ubuntu0.1 or +ubuntu0.118:34
jdongMsMaco: no, it's the - vs +18:34
MsMacoah ok18:34
jdong+ is like the professional edition ;-)18:34
MsMaco:P18:34
ebroderAnyway, I'll poke as soon as I finish dealing with the fallout of bug #430224 for my build servers18:35
ubottuError: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/430224)18:35
jdongyay ubottu!18:35
ebroder*eyeroll* This is the "initctl in a chroot does the wrong thing" bug18:36
ScottKpitti: I was wondering if you could take a look at Bug #466028.  I think it may be a post-update regression (I don't recall seeing the error before).18:36
jdongheh has anyone gotten anything amusing to happen as a result of that?18:36
ubottuError: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/466028)18:36
ebroderjdong: I don't think anything amusing will happen; just annoying errors. Although I can certainly see it causing problems for Debathena's login chroots at some point down the line18:36
jdongebroder: yeah, I'd imagine18:37
ebroderjdong: I can't tell for sure, but it looks like dkms tracks modules outside the package manager. If that's true, the version number wouldn't matter if you're using dkms, but it still would if you use the module-assistant18:45
jdongebroder: now that you mention it, yeah, it'd purge the dkms modules and re-build them during postinst18:46
=== rmcbride_ is now known as rmcbride
jdongnot a big deal there18:46
ebroder(My perspective is biased, because Debathena is still distributing module-assistant-built modules for everybody)18:46
jdongnot biased at all; no reason why not to do a 1-character regression correction :)18:47
=== MacSlow is now known as MacSlow|break
lantizia_I'm very much sufficiently *ISSED off... whose bright idea was it to have GDM restart OVER AND OVER AND OVER if it fails to start X?19:45
lantizia_Jesus didn't this thing go under any testing?19:45
lantizia_Dependant on name server chosen, network-manager is screwed at name resolution too19:46
ebroderlantizia_: I don't know anything about your problem, but a word of advice from the other side: I have very little desire to help someone who starts their bug report by ranting about how incompetent I am19:47
lantizia_Then don't brand something as stable just because 6 months have passed19:47
jdongthat's a very helpful attitude19:48
lantizia_No it isn't... but I'm not using a very helpful OS either19:48
lantizia_I don't argue that I'm being a cock right now but it's irritated me greatly19:48
jdongwell sorry to hear that19:48
jdongbut it's unlikely this approach will yield any productive results19:48
lantizia_And #ubuntu is full of people who have silly questions like how to delete a file, or run a windows games... the odd's of having any real dialogue to work through issues is nill19:49
ScottKDoesn't make this a support channel19:56
MsMacoebroder++20:01
=== nxvl_ is now known as nxvl
=== ryu2 is now known as ryu
mdeslaurRiddell: I have some qt4-x11 packages for intrepid and jaunty in https://launchpad.net/~ubuntu-security-proposed/+archive/ppa/+packages20:38
mdeslaurRiddell: if you want to try them out20:38
Riddellmdeslaur: ok, I'll try them in a couple of hours20:41
mdeslaurRiddell: cool, thanks20:41
mdeslaurRiddell: it's webkit security updates, so anything that uses qt4-webkit20:41
mdeslaurRiddell: no rush20:41
=== MacSlow|break is now known as MacSlow
=== RAOF_ is now known as RAOF
davidroderickI ran out of disk space and so I started to apt-get remove stuff I found in /var/lib/dkpg/available.  This broke my system in subtle ways.  How should I have found a list of end packages?21:35
chrisccoulsonsiretart` - there?21:36
davidroderickI think that I might trash the os and move to gentoo21:37
siretartchrisccoulson: yes?21:49
chrisccoulsonsiretart - did you do any work on the screensaver/vlc issue?21:49
chrisccoulsoni was looking at the totem source earlier, and it contains the same hackery (simulating fake keypresses) as gnome-session for preventing the session from going idle21:50
siretartchrisccoulson: nope. I've just digged out the patch from the gnome bugzilla and prepared a ppa package21:50
RAOFdavidroderick: This isn't really the channel for that question, and it's not entirely obvious what you're trying to ask, but I think "deborphan" is the answer.21:50
siretartchrisccoulson: but I've read a bit about xlib. There is this API called XResetScreenSaver. Why can't we use just that API?21:51
chrisccoulsonsiretart - not sure about that21:52
siretartbtw, how do KDE applications prevent the screensaver from activating?21:53
chrisccoulsonsiretart - i'm not sure about that either. in gnome, applications must prevent the session from going idle somehow. once the session goes idle, gnome-screensaver will display the screensaver after a preset time21:54
siretartbtw, I found that API from this message: http://lists.freedesktop.org/archives/xdg/2009-May/010461.html while googling around..21:55
chrisccoulsonsiretart - interesting. i'll have to try and figure out what that does on the server-side21:56
chrisccoulsonbasically, we just need a way of resetting the IDLETIME counter21:56
chrisccoulsonwhich is reset automatically when you move the mouse / press keys etc21:57
siretarthm. the documentation XSetScreenSaver(3) fits perfectly to this description...21:58
Riddellsiretart: I believe they insert fake key events using libxtest22:02
chrisccoulsonRiddell - that's also what some gnome apps do as an alternative to using the inhibit interface22:06
* siretart reads the xlib specification, page 195, section 9.7. Controlling the Screen Saver.22:06
chrisccoulsonsiretart - remember though that gnome-screensaver disables the built-in X screensaver anyway22:10
chrisccoulsonjust to complicate things ;)22:11
chrisccoulsonit's all very confusing :-/22:11
siretartchrisccoulson: it does?! why the heck is this?22:12
siretartbtw, what *is* the 'built-in X screensaver' anyway?22:12
chrisccoulsonsiretart - the built in X screensaver is all controlled server-side. ie, it takes care of the timeout and screen blanking itself22:13
chrisccoulsonbut gnome-screensaver disables this and takes control of the screen itself22:14
chrisccoulsonand the screen blanking is handled by gnome-screensaver too22:14
siretarthm. I guess I need to do way more research here22:14
chrisccoulsonat least that's my understanding of it22:14
siretartchrisccoulson: you said that one cannot assume that the MIT-SCREEN-SAVER extension is always available. is that correct?22:15
siretartdo you know of examples when it is not available?22:15
chrisccoulsonthe built-in X screensaver probably doesn't allow a nice fade, and probably provides no way of drawing the unlock dialog too22:15
siretartbut it defines a documented and fine API for locking/unlocking/inhibiting the screen22:16
chrisccoulsonsiretart - i've no specific examples of when the extention might not be available, but i've had to debug several issues recently where people have made invalid assumptions about the presence of various X server features.22:16
siretartwouldn't it be great if g-s-s would just handle these xlib defined notifications just as one would expect it?22:16
ajmitchsiretart: wouldn't it be great if no software had bugs? :)22:17
chrisccoulsonand regardless of whether it is available or not, you must always make a call to XScreenSaverQuesryExtension to properly initialize some client-side parameters22:17
chrisccoulsonelse behaviour is unpredictable22:17
chrisccoulsonit would be great if software had no bugs:)22:17
chrisccoulsonbut then i'd have nothing to do...22:18
chrisccoulson;)22:18
siretartajmitch: sure, but we are not (yet) able to identify the defect exactly22:18
ajmitchI know, I was reading through that bug. It's a shame that screensavers are still a complicated field22:19
chrisccoulsonthey are too complicated. i knew nothing about gnome-screensaver until i had to debug a separate issue 3 weeks or so ago22:20
chrisccoulsoni had to spend several evenings trying to figure out how it worked ;)22:21
=== ryu2 is now known as ryu
siretartchrisccoulson: re: XScreenSaverQueryExtension - you're right, this is even documented in XScreenSaver(3)22:26
chrisccoulsonsiretart - this is also the case for any X extension request22:26
chrisccoulsoni think the call is needed for obtaining the major op code associated with the extension22:27
siretartchrisccoulson: ah, I think now I understand the issue. g-s-s has moved away from libxscreensaver (the MIT-SCREEN-SAVER) extension to directly query the IDLETIME sync counters in order to make the fading out effect interruptible22:45
siretartis this correct?22:45
chrisccoulsonsiretart - almost. it's actually gnome-session which queries the IDLETIME counter22:45
chrisccoulsongnome-screensaver just listens to the session idle status from gnome-session22:45
siretartokay, but I assume applications should still be able to use libxscreensaver to reset the IDLETIME counter and thus inhibit g-s-s22:47
siretartor even just plain libx1122:47
chrisccoulsonsiretart - the IDLETIME counter is accessible via the SYNC extension22:49
chrisccoulsonbut it is not writable by any clients22:49
chrisccoulsonthat seems to be the issue22:50
siretartchrisccoulson: perhaps XResetScreenSaver can be used to reset that counter?22:51
siretartor rather: make XResetScreenSaver(3) reset the counter?22:52
chrisccoulsonsiretart - i don't know. perhaps it does that indirectly already?22:52
siretartchrisccoulson: what library exposes the SYNC extension?22:54
siretartXext?22:54
chrisccoulsonsiretart - yes, i think that's the one22:55
siretartokay, that seems to be documented here: http://www.xfree86.org/current/synclib.pdf22:57
siretartchrisccoulson: do we have client programs to query the xsync counters, or do I have to hack something up myself?23:06
chrisccoulsonsiretart - gs-idle-monitor.c in gnome-session has some examples23:07
chrisccoulsonsiretart - that file also contains an example of how to reset the counter23:08
chrisccoulsonwhich is copied directly from totem too23:09
siretartI'm just reading that file right now23:09
bluefoxicy  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND23:09
bluefoxicy 4576 bluefox   20   0 1307m 117m  22m R  188  3.2   2696:39 pidgin23:09
bluefoxicyhtf can pidgin use 200% CPU23:09
bluefoxicyto idle23:09
jdonghahaha :)23:09
bluefoxicyit's been doing this a lot too23:10
chrisccoulsonbluefoxicy, empathy?23:10
* chrisccoulson runs23:10
bluefoxicyempathy is crap23:10
chrisccoulsonhmmm23:10
slangasekbluefoxicy: not helpful23:10
siretart        /* FIXME: is there a better way to reset the IDLETIME? */23:10
siretarthrmpf23:11
chrisccoulsonsiretart - that's the bit i referred to in the bug report23:11
bluefoxicyFIXME and XXX are awesome23:11
bluefoxicygrep at the source code for a while, find these, examine23:11
bluefoxicyhack the shit out of everything23:11
bluefoxicywash, rinse, repeat23:11
chrisccoulsonsiretart - it's really not very nice ;)23:11
bluefoxicy(FIXMEs occasionally become exploitable bugs)23:11
siretartchrisccoulson: hm. synclib.pdf mentions the API Status23:11
siretartXSyncSetCounter ( Display * dpy, XSyncCounter counter, XSyncValue value )23:11
siretartXSyncSetCounter sets counter to value. It returns False if dpy does not23:12
siretartsupport the SYNC extension; otherwise, it returns True.23:12
siretart<endofquote>23:12
slangasekchrisccoulson: did my xtrace help? :)23:12
chrisccoulsonsiretart - i tried patching gnome-screensaver to do that already23:12
chrisccoulsonbut Xorg doesn't let you change the value23:12
directhexhm23:12
chrisccoulsonsiretart - you just get a BadAccess error, and a crash;)23:13
chrisccoulsonslangasek - thanks - i've not had time to have a proper look at it yet23:13
directhexapparently debian now finally supports source format 3.0 - does ubuntu?23:13
dtchenslangasek: I'm beginning to think this grub issue is caused by users' errors. I haven't been able to reproduce the issue, but that doesn't mean very much...23:13
slangasekchrisccoulson: no worries23:13
chrisccoulsonbut i suspect it probably will help. i noticed something briefly at the end of the file when i glanced at it eariler, although that might end up being nothing23:13
slangasekdtchen: some of them will have been.  But each occurrence should be inspected individually before drawing a broad conclusion.23:14
slangasek(FSVO "each")23:14
slangasekdirecthex: no23:14
directhexslangasek, so don't upload any 3.0 stuff to debian i want to be syncable?23:15
slangasekdirecthex: for the nonce23:15
siretartchrisccoulson: have you seen http://antony.lesuisse.org/software/xorgsync/synctest.c?23:17
chrisccoulsonslangasek - it looked like the last XRRSetScreenSize call sets the screen size to 1280x800 when there is still an output allocated to a range outside of that new size23:17
siretartchrisccoulson: there various xsync API calls are demonstrated. the alarm ones fail for me, though23:18
chrisccoulsonfrom the randr documentation: "All active monitors must be configured to display asubset of the specified size, else a Match error results."23:18
chrisccoulsonmight be nothing though. i need to look in more depth23:18
slangasekchrisccoulson: feel free to use me as a sounding board, but I know nothing about the protocol, so can't give you much feedback :)23:20
slangasekchrisccoulson: I do think it's odd that it switches the size to 2640x800 and then immediately back down to 1280x80023:20
chrisccoulsonsiretart - i've not had a proper look at that source file, but SYNC does allows clients to set up and manipulate counters. unfortunately though, IDLETIME is a special counter which clients aren't permitted to modify directly23:20
chrisccoulsonslangasek - the larger size there would probably be normal if you have a second screen located to the right of your main screen23:21
siretarti see23:21
slangasekchrisccoulson: er, why is it normal for gnome-settings-daemon to not make up its mind on the first go? :)23:23
=== yofel_ is now known as yofel
chrisccoulsonslangasek - AFAICT, it should pick an existing configuration if the hardware that is attached matches that of a configuration that was stored previously23:24
chrisccoulsonif the hardware configuration is new, it auto-configures by appending new screens to the right-hand side of existing screens23:24
chrisccoulsonat least that's how i understand it ;)23:24
slangasekchrisccoulson: sure; my question is, why does it issue the command *twice* with two different resolutions, when I only hit the button once?23:25
slangasekit's not new hardware23:25
slangasek(it has no EDID, so maybe it doesn't know this is the case)23:25
chrisccoulsonii'm not too sure without looking at the data in more detail. i don't have 2 screens to test it out, and i don't have the benefit of playing with RANDR either23:25
* chrisccoulson curses proprietary drivers23:26
jdongdid keybuk ever make any headway on the mystery sreadahead-is-slow bugs23:35
jdonghttp://bradmisik.com/random/mike-desktop-karmic-20091102-1.png23:36
ionYes. He wrote ureadahead.23:36
jdongwas just helping someone with this craziness23:36
jdongpretty beefy system, sreadahead seems to just thrash23:37
ionIt’s available for testing from the ubuntu-boot PPA.23:37
jdong*nods*23:37
gphi guys pl help my server has run out of space (ec2 instance ) ......i created a new partition and mapped home folder to it but its now working23:42
azeemif it's now working - great!23:43
gp# /etc/fstab: static file system information.23:43
gp# <file system>                                 <mount point>   <type>  <options>       <dump>  <pass>23:43
gpproc                                            /proc           proc    defaults        0       023:43
gp/dev/sda3                                       None            swap    defaults        0       023:43
gp/dev/sda1                                       /               ext3    defaults        0       023:43
gp/dev/sda2                                      /home            ext3    nodev,nosuid    0       223:43
jpds!paste | gp23:43
gpnot working :-(23:43
ubottugp: For posting multi-line texts into the channel, please use http://paste.ubuntu.com (or !pastebinit for CLI) | For pasting !screenshots use http://tinyurl.com/imagebin Please give us the URLs for your posts!23:43
gpsorry23:43
gpis fstab is correct here23:44
gp?23:44
azeemgp: this is not a support channel, please ask in #ubuntu23:44
slangasekor possibly #ubuntu-server, in the case of ec223:44
brown`What should be permissions on /etc/cron.daily/apt be for Karmic?23:46
brown`On my my system, installed fresh from alternate CD, they are 644.23:47
wgrantbrown`: 755 here, installed from the final i386 alternate CD.23:48
gppl in the name of Gaint panda pl help me23:50
gpi copied to home folder to /mnt   and then renamed the home folder23:50
gpchanged "/dev/sda2 /mnt ext3 defaults 0 0"  to "/dev/sda2                                      /home            ext3    nodev,nosuid    0       2"23:50
gpbut fstab is not mounting it23:50
brown`wgrant: Thanks.  I installed from one of the betas and then upgraded to Karmic final.  Update manager is not checking for updates daily.  Is there an easy way to verify permissions and content for all installed packages?23:50
gpits national emergency pl help me23:53
brown`Second question:  My PC running 9.10 hibernates.  On reboot the root partition is identified as having problems, so the system mounts it read only.  Can applications already running write to files on the root partition.23:53
wgrantbrown`: You probably want to ask in #ubuntu.23:58
brown`wgrant: ok, will do, thanks.  Figured I'd ask here, since it's a kernel question.23:58

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