/srv/irclogs.ubuntu.com/2009/04/09/#ubuntu-bugs.txt

bdmurrayjgoguen: doesn't everything lose data when you hd is full?00:04
bdmurrayjgoguen: okay, I read the report ;-)00:04
jgoguenbdmurray: not everything gets data corruption when the HDD is full though, and the interactive things should allow you to save elsewhere00:05
jgoguenbdmurray: admittedly, thunderbird isn't interactive that way :) and I don't know what else it could do for POP3...00:05
bdmurrayit'd be good to test it in Jaunty00:06
jgoguenbdmurray: ok...do you think High is right then?  When I get a chance, I'll create a Thunderbird profile on a nearly-full partition and see if I can reproduce00:07
bdmurrayjgoguen: yes, at least high00:07
jgoguenCritical if it still exists?00:08
bdmurrayjgoguen: perhaps00:08
jgoguenbdmurray: ok...I'm going to an exam in a bit, I'll come ask about it once I get a chance to test and see just what happens00:09
bdmurrayjgoguen: oh, if its not fixed upstream its unlikely to be fixed in Jaunty ;-)00:11
* jgoguen looks again00:11
jgoguenheh :)00:11
jgoguenwonder if it's been fixed in Thunderbird 3 since Jan 11...I've seen at least one other bug, either there or in GNOME, that's fixed but not marked fixed00:13
bdmurrayYeah, it would be good to know for sure00:14
jgoguenis there a PPA for Thunderbird 3 builds?  it's failing for me right now, apparently GCC doesn't follow the C++ standard for temporary object destruction...00:14
jgoguenas of gcc-4.300:14
bdmurrayThe mozillateam does not have one00:16
jgoguenok...I have to run now, either late tonight when I get home or sometime tomorrow I'll install gcc 4.2 and compile Thunderbird 3 and test00:17
bdmurrayDoes anybody hear the logout sound? bug 25376300:49
ubottuLaunchpad bug 253763 in pulseaudio "Schedule pulseaudio to terminate last at logout. Logout sound doesn't... sound" [Undecided,Confirmed] https://launchpad.net/bugs/25376300:49
dtcheni thought a decision was made to not play any logout sound00:50
dtchenIIRC, part of the TearDown spec?00:50
bdmurrayI don't see anything in that spec00:55
=== stooj is now known as StooJ
dtchenbdmurray: i don't know offhand if the logout sound is *supposed* to be played. perhaps one of keybuk, pitti, or mdz would know.05:19
=== lacqui_ is now known as lacqui
YoBoYgood morning06:49
=== scott_ev is now known as OfficialGreeter
=== OfficialGreeter is now known as scott_ev
davmor2Guys is there anywhere special to report translation bug to or is it just on the normal ubuntu bug tracker09:09
YoBoYdavmor2: better to go to the translation page of the package to make your proposition of correction and send a mail to the maintener of the translation09:14
davmor2YoBoY: thanks09:15
efraserHello guys09:43
efraserI've got a bug when using dual head DVI on a dell docking station with a Dell Lattitude E4300, but I'm not sure what to file the bug against.09:44
efraserOr to search against.09:44
efraserBasically xrandr is messing up when it configures the monitors when you login.09:46
efrasernm, I've found the guides on reporting bugs.09:56
YoBoYefraser: hi, you can beggin your jorney by reading this page https://wiki.ubuntu.com/X/Debugging09:56
efrasercheers, that's what I'm doing :)09:56
james_wit's bug day today people! https://wiki.ubuntu.com/UbuntuBugDay/2009040910:07
james_wfeel free to ask about anything you are unsure about how to deal with10:07
james_wthe idea today is to do two things, remove the "patch" flag from attachments that aren't patches so the flag becomes more useful10:08
james_wand to move the patches that are there closer to being integrated in to the package, so that we can fix bugs or add features.10:09
efraserhttps://bugs.launchpad.net/ubuntu/+source/xorg/+bug/35831510:34
ubottuUbuntu bug 358315 in xorg "[jaunty] intel xrandr dual head auto config only configures part of one screen on Dell Lattitude E4300" [Undecided,New]10:34
efraserYeah, thats me.10:35
efraserI'm not troubled by the bug really, but it has been there since I started using Jaunty, so I figure I should report it before jaunty goes live.10:35
miki4242hi all, should a debdiff always include a new changelog entry describing the fix?10:36
=== asac_ is now known as asac
miki4242example in Bugs/Patches on wiki doesn't have one10:40
TheHobbithi10:41
TheHobbitI'm working on bug 321688. The bug could be better solved by upgrading the package to the new upstream release, should I?10:42
ubottuLaunchpad bug 321688 in liblocale-maketext-lexicon-perl "Broken argument parsing in Lexicon::import()." [Undecided,New] https://launchpad.net/bugs/32168810:42
TheHobbithmmm I need some clarification on policy.... The bug I'm hugging now is solved upstream in a new release. Moreover, jaunty already has the new release solving the bug, thus the problem only stays for intrepid...11:24
TheHobbitwhat is the right thing to do? bring the new release in intrepid or patch the old one?11:25
james_wmiki4242: a debdiff should generally, yes11:25
miki4242thanks11:26
james_wmiki4242: it's not usually crucial, but having it makes proper attribution easier11:26
miki4242ok.11:28
james_wTheHobbit: hi, I don't see the reference in the upstream changelog, which version fixes it?11:29
miki4242after lunch i'll work on espeak/portaudio bugs which are quite a problem for accessible ubuntu. any help greatly appreciated.11:30
TheHobbitjames_w: I did not download all the releases, but 0.77 has it cleaned... The fact that is not in the changelog does not surprise me...11:31
james_wwhy's that?11:31
TheHobbitis such a blunder, I wouldn't like to have it remembered each time someone opens the changelog:D11:31
james_wok, I see it now11:32
james_wso, as this is fixed in Jaunty it should be marked "Fix Released"11:33
TheHobbitok, but what for intrepid?11:33
james_wbut we know this affects Intrepid, so we should decide whether it is appropriate to fix there11:33
james_wwe need to weigh up the impact of the problem, against the potential for regression11:34
TheHobbitok, I just found it11:34
TheHobbitis solved in release 0.67 of the upstream package11:34
james_wcool, thanks11:34
TheHobbitthat is just the release after the one that is in intrepid11:35
TheHobbitI do not think that upgrading to 0.67 should pose any regression problems... just a sec11:35
james_wthere seems to be little potential for regression, except that something may be relying on the fact that it only accepts odd numbers of arguments11:35
james_wwe can check what packages depend on that one using "apt-cache rdepends"11:36
james_wso there are a few11:36
TheHobbityes, so there are... I'm looking for changes in the 0.67 wrt 0.6611:41
TheHobbithu?11:43
TheHobbitin the 0.66 version on cpan there is no bug!!!!11:44
TheHobbiteither the developper put on cpan two 0.66 versions, or the matainer had a problem somewhere11:45
james_wI can't see it in the Intrepid version either11:48
TheHobbitmee too, I'm sorry, I was wrong11:49
TheHobbit:(11:49
james_wit was fixed in ubuntu with the upload of 0.62-111:49
TheHobbityes, i saw11:50
TheHobbiti'm correctin my blunder11:50
james_wdapper, gutsy and hardy are then affected, but nothing after11:50
TheHobbitthus? should be 'confirmed'?11:51
james_wnope, still "Fix Released"11:51
james_wthe status tracks the development release11:51
james_wwe can add a bug task for earlier releases if we want to fix it there11:52
TheHobbithmmm11:52
TheHobbitif someone ask for it...11:53
TheHobbitI'm closing it on the hugday page too11:56
TheHobbitwell, a closed bug before lunch, and after I'll tag another;)11:58
TheHobbitat least being unemployed will produce something11:58
TheHobbitsee you later11:58
=== yofel_ is now known as yofel
=== Brownout_ is now known as Brownout
TheHobbithi13:55
TheHobbitI'm looking into bug 176862, proble is: the patch attached is a diff against the whole tree, almost a debdiff, for a old release of the package14:07
ubottuLaunchpad bug 176862 in gworldclock "unsorted country list" [Undecided,Confirmed] https://launchpad.net/bugs/17686214:07
TheHobbitmoreover the package has no patches for now, so I should choose a patch handler (I'm only familiar with dpatch,,,,)14:08
james_wTheHobbit: that patch appears to be a debdiff to me14:10
TheHobbityes, but against an old release14:10
james_wwhen there is no patch system already then we typically do not add one for packages which originate from Debian14:10
james_wah14:10
TheHobbitmoreover, I thought that patches should be in the debian/patches, not idden in the diff.gz14:11
TheHobbit+h14:11
james_wthat's what I was saying14:12
TheHobbitI have some doubt about the patch, by the way....14:12
james_wif there is no patch system already then we don't generally add one, as that can cause issues with merging from Debian14:12
TheHobbitit solves the proiblem yes14:12
james_wso in this case it would be ok14:12
TheHobbitbut only for english speaking people:D14:12
james_walso, it's only a tiny bit old, so it should be easy to update it to apply to the new version14:13
james_wheh :-)14:13
TheHobbityes it is easy, just modify the files :)14:13
TheHobbitdebian has a related bug, #16733914:14
TheHobbitwhich asks for displaying the country codes too14:14
TheHobbitanyhow, I can adapt the patch and upload a debdiff against current release14:15
TheHobbitshould I?14:15
james_wthat would be great14:15
james_walso, if you could forward it to Debian it would be even better14:15
james_wit appears the author is also the Debian maintainer, so it's two birds with one stone doing that14:15
TheHobbitwhat? the debdiff or the bug report? or both?14:15
james_wboth please14:16
TheHobbithmmm I'll be back for direction about how to do it...14:16
james_wplus, adding the note about the sponsors to the Ubuntu bug so that the reporter might know about that next time would be triple good14:16
TheHobbitwho's the sponsor?14:16
hggdhwhat should be done on patches that change Makefile.am?14:17
james_wTheHobbit: the sponsors team14:17
james_wah, I thought that was on the Bugs/Patches page14:18
james_whggdh: they are tricky. It sometimes depends on the package14:18
james_whggdh: generally though a sponsor should be able to do the necessary things with it, as it is often easier for them to do it themselves than review a patch that includes autotools changes.14:19
TheHobbityou mean subscribing the ubuntu-(main|universe)-sponsors to the bug james_w ?14:19
hggdhjames_w, yes... I would really not need to run autotools in the build14:19
james_whggdh: mentioning that "Makefile.am" is changed along with the patch would be good though14:19
james_whggdh: plus, check debian/rules, some packages already run it there14:19
hggdhjames_w, thanks14:20
james_wTheHobbit: yeah, but also add a comment explaining that that is what you are doing, and that if they attach a patch they should do the same thing14:20
TheHobbitI'll do it...14:20
james_wthank you14:20
TheHobbitis universe by the way in this case14:21
TheHobbitI'll be back14:21
=== thunderstruck is now known as gnomefreak
TheHobbithu..... being an ubuntu patch, should I change debian/control too?14:28
savvasTheHobbit: update-maintainer usually does the trick :)14:29
TheHobbitsavvas: thanks...14:29
savvasnp14:30
TheHobbitsorry, but I'm new to this game:D14:30
=== thunderstruck is now known as gnomefreak
TheHobbithmmm something does not work as expected...14:47
TheHobbitmust dwell a litle bit deeper14:47
TheHobbitapparently the patch is not enough.... :s14:55
* TheHobbit kicks himself in the ass.... stupid stupid stupid:D15:09
bddebianBoo15:11
BUGabundofoo15:12
TheHobbitok, now I have the right debdiff... I'm going to do the amministrative work, only I would like to know how to notify debian (And upstream being the same...)15:14
TheHobbitby the way....15:22
TheHobbithaving posted a debdiff, should I set the status to fix-released or something? Or should it stay 'confirmed'?15:22
james_wconfirmed is fine15:23
james_whaving the sponsors subscribed is the important bit15:23
TheHobbitthat's done15:23
james_wand not closing the bug, so "Fix Released" would actually be bad15:23
james_wcool :-)15:23
TheHobbitnow about notifying upstream...?15:24
james_wand https://wiki.ubuntu.com/Debian/Bugs should help with forwarding to Debian15:24
TheHobbitreading it....15:26
TheHobbitjust a question.... when it is said that the debdiff generated by submittodebian can be edited, is to remove specific ubuntu things? Like the update-mainatiner thing?15:42
james_wexactly15:51
bdmurrayjames_w: How's it going?15:57
james_whey bdmurray15:58
james_wpretty good, how are you?15:58
bdmurraygood, I was looking at bug 176862 which TheHobbit was working and part of the changelog has been modified is that alright?15:58
ubottuLaunchpad bug 176862 in gworldclock "unsorted country list" [Undecided,Confirmed] https://launchpad.net/bugs/17686215:59
TheHobbitbdmurray: modified by me you mean?15:59
bdmurrayTheHobbit: yeah the removed obsolete variables from changelog bit16:00
TheHobbithu....16:00
TheHobbitthat was the Local variable part16:00
TheHobbitI could add them again...16:00
TheHobbit:)16:01
bdmurrayTheHobbit: right, I'm not sure modifying the changelog is the right thing to do and wanted to check w/ someone else16:01
bdmurrayI mean its not worth carrying a diff from Debian for16:01
TheHobbitI was asking myself the same thing...16:02
TheHobbitbdmurray: I'll wait to notify upstream then....16:03
TheHobbitthese variables are mode setting for some text editor or other I think16:04
bdmurrayjames_w: ?16:07
james_wyeah, harmless, but discouraged16:07
james_wif there's no effect on the package then it's not worth diverging from Debian16:07
TheHobbitthus I'm back to generate a debdiff then..16:07
TheHobbitok, learning is made through doing the wrong thing and starting over16:08
TheHobbitas my grandmother was fond to say16:08
james_windeed :-)16:08
exosystCan anyone verify some odd behaviour after the last intrepid update?16:09
bdmurrayjames_w: once he's got that done what do we need to do to get it in?16:09
james_wat the moment it would need motu-release approval16:10
thekornwoohoo, happy hugday everybody ;)16:31
TheHobbitok, now the debdiff is minimal........16:31
TheHobbitshould I notify upstream?16:31
TheHobbitjames_w: ?16:34
TheHobbitmust go...16:38
bdmurrayTheHobbit: Thanks for helping out!16:38
TheHobbitbdmurray: no problem:)16:39
TheHobbit'till next week I've time16:39
bdmurrayjames_w: I've a question about the patch tagging guidelines17:00
james_wshoot17:00
bdmurraySo in a dpatch patch it says:17:01
bdmurray## All lines beginning with `## DP:' are a description of the patch.17:01
bdmurraySo is ## DP: Ubuntu: url appropriate?17:01
james_wI think so, yes17:03
bdmurrayjames_w: okay, I wasn't sure if it was redundant.  Is there somebody else to checkw with I'd like to update the wiki page too17:09
james_wbdmurray: I'm not sure that there is17:14
james_wI think the DP: lines are there to mark the description so that tools could parse them out17:14
james_wI don't see why the links shouldn't be part of the description, their valuable information17:15
bdmurrayMy question was whether or not is should be ## DP: Ubuntu: url vs ## Ubuntu: url17:15
james_wyeah17:21
bdmurrayCan anybody recreate bug 346474?  I can't on Jaunty17:21
ubottuLaunchpad bug 346474 in imagemagick "ImageMagick interprets PGM header incorrectly" [Undecided,New] https://launchpad.net/bugs/34647417:21
Picibdmurray: I cannot either.17:23
bdmurrayokay the source code looks a bit different too17:23
=== fader_ is now known as fader|lunch
=== Ampelbein is now known as Ampelbein_
=== Ampelbein_ is now known as Ampelbein
=== fader|lunch is now known as fader_
HammerHead66can anyone help me with the BugDay/Tools this is my first time and I'm vary new to Linux18:36
HammerHead66I get this error when installing it E: Couldn't find package ubuntu-qa-tools18:37
bdmurrayHammerHead66: what release are you on?18:38
HammerHead668.04 64bit Gnome18:39
bdmurrayAnd where did you find the bugday tools?18:39
HammerHead66https://wiki.ubuntu.com/UbuntuBugDay/Tools       ran it in terminal   "sudo apt-get install ubuntu-qa-tools"18:40
bdmurrayah, okay ubuntu-qa-tools is only available in Jaunty18:40
HammerHead66lol ok that's why it won't work.18:41
HammerHead66so those tools are only for jaunty do they have any tolls for 8.04?18:42
HammerHead66*tools18:42
bdmurraythe tools will work in Hardy its just a bit harder to set them up18:43
=== savvas is now known as Euaki
=== Euaki is now known as savvas
HammerHead66bdmurray: I'll try if your willing to help me18:51
bdmurrayHammerHead66: You don't really *need* the tools to particpate your time might be better spent participating rather than setting up tools.18:54
HammerHead66ok18:54
efefppoHas the google calendar bug in evoluition been fixed?19:40
bdmurrayCan anybody recreate bug 342332?19:51
ubottuLaunchpad bug 342332 in vlc "vlc crashes with SIGABRT at startup or when "Show Playlist" is clicked" [Undecided,New] https://launchpad.net/bugs/34233219:51
bdmurrayI'm having a hard time of it19:51
imachinehelllo!20:17
imachinehttp://paste.ubuntu.com/147849/ <-nvidia 71 fails to build @ 8.1020:17
imachineany ideas?20:17
HammerHead66imachine: see im20:44
imachineHammerHead66, that was a bunch of bloat I couldn't see through sorry20:45
imachineirssi doesn't autocreate chat windows for me20:45
imachineHammerHead66, also, I don't think it has to do with any of that. it looks upstream.20:46
imachinefirst it couldn't find semaphore.h (looked in asm/), I symlinked it from linux/20:46
imachinethen it just failed20:46
imachinehttp://paste.ubuntu.com/147849/20:46
imachinelike this20:46
HammerHead66 imachine:    ERROR: Kernel configuration is invalid."; this is the error you are getting so it has to do with drivers... at lest that's what I think. But I may be wrong20:54
imachineHammerHead66, you get that with every driver build through DKMS, at least with the other ones that work noprobs.20:58
imachineit's a standard error one can somewhat ignore.20:58
HammerHead66I don't have it on mine20:59
imachinenvidia setup just seems to be overly cautious.20:59
imachineexplain20:59
imachinewhat version of nvidia do you run?20:59
HammerHead66did you try what I im you?20:59
imachinesend it again please20:59
imachineit went out all rubbish since irssi doesn't auto-open im windows here for me.21:00
imachineI've opened a query now21:00
imachineright21:00
imachine:-)21:00
imachinedude what you wrote is for ati21:01
imachinewhat the hel21:01
HammerHead66did it work?21:01
imachineit's for another card.21:01
HammerHead66it will work for all cards21:02
* imachine fails21:02
imachineriiight;21:02
imachineanyone else?21:02
HammerHead66if you don't try it your just showing how much you don't want to  try something that someone is giving you that will work I hope you get it all worked out21:04
imachinecheers21:06
IntuitiveNippleimachine: just looked at your original pastebin report. Where did the dkms package come from?21:09
imachineIntuitiveNipple, apt22:11
imachineIntuitiveNipple, it's standard package from apt.22:11
imachine8,1022:11
imachineIntuitiveNipple, I did dpkg-reconfigure nvidia-71-kernel-source or whatever it's called22:15
imachineand during dkms module build, it failed.22:15
imachineI think it's upstream, since it fails to build with nvidia-installer with .run file from NVIDIA.com22:16
imachineI can provide that debug as well22:16
imachinebut not now since that pc is off and people sleep in the same room it's in22:16
IntuitiveNippleimachine: There are plenty of reports about that issue from a Google search. It seems the problem is the kernel changed the definition of some functions and Nvidia didn't update some driver packages22:16
imachineyes, very likely22:17
imachinelike I said, it's upstream 99$22:17
imachine99%22:17
imachinetho, it's a bug nonetheless and should be reported, so that it at least gets marked as upstream/won't fix22:17
imachine:-)22:17
imachineI'll browse laucnhpad later for it; the bigger problem is that nvidia 96 which should work is broken.22:17
imachineit displays RGB not as RGB but as GBR22:18
imachine;p22:18
IntuitiveNippleThis may help: http://www.nvnews.net/vbulletin/showthread.php?t=12097122:20
IntuitiveNipplewhat video chip-set is that?22:20
imachinegf3 ti22:21
IntuitiveNipple96.x.x displays as GBR?22:22
imachineyes22:23
imachineon DVI22:23
imachineworks fine on VGA22:23
imachineit's a known issue22:24
imachinehttp://www.nvnews.net/vbulletin/showthread.php?t=10649622:24
imachinethat's what I have22:25
imachineseems it's not just GF322:25
imachineI'd gladly use 71x22:25
imachinebut they fail to build :)22:25
IntuitiveNippleWhat's connected to the DVI?22:25
imachinea monitor22:31
imachine20" dell22:31
imachineworks fine on window$22:32
imachineworks fine with nv on linux22:32
IntuitiveNippleI was wondering if the nvidia xorg.conf EDID over-rides might help so you can set the parameters manually22:32
imachinewhat might help me is turning off VGA22:33
IntuitiveNippleftp://download.nvidia.com/XFree86/Linux-x86/96.43.11/README/appendix-d.html22:34
imachinebecause I think it's the fact that the card falsly keeps both outputs on, and therefore corruption comes up22:34
IntuitiveNippleThere's an IgnoreDisplayDevices option that may help22:34
IntuitiveNipplealso possibly ExactModeTimingsDVI if you over-ride EDID22:35
imachineits not EDID, I think22:35
imachinethere's no errors in xorg.0.log22:35
imachineit used to work on older drivers22:35
imachineand if I killed and restarted X a few times, it worked fine22:36
imachineso I'm guessing it's some nasty nvidia issue that makes it pick up both outputs at once.22:36
IntuitiveNippleFrom what I've read though, the driver is not using the provided EDID info correctly, so over-riding it could help22:36
imachineand it should not.22:36
imachineI'll check it out later tomorrow, thanks22:36
imachineit's tomorrow in 20 minutes over here anyway22:36
imachineand I guess I should be off22:36
imachineso lates! and thanks for the hints.22:36
imachineI'll report back later22:37
IntuitiveNipplethe other one is ModeValidation22:37
desavelhi all22:44
BUGabundodesavel: ehy22:44
desavelwhat is Ubuntu?22:44
desavelhm.........I feel myself lonely22:46
BUGabundohumm22:48
=== lifeless_ is now known as lifeless
bdmurrayWooo, found a fixed bug23:16
BUGabundoeheh23:18

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