/srv/irclogs.ubuntu.com/2008/08/31/#ubuntu-bugs.txt

Ampelbeinhi! could some member of bug-control please set bug #261598 to wishlist? thanks.00:17
ubottuLaunchpad bug 261598 in ubuntu "[needs-packaging] seahorse-plugins" [Undecided,Confirmed] https://launchpad.net/bugs/26159800:17
hggdhAmpelbein, done01:58
=== jjesse_ is now known as jjesse
=== LucidFox is now known as LucidFox_WoW
anakronHI all07:08
anakronwich is the repository for 5-a-day applet in intrepid???07:08
anakroncause i can found it in wiki07:08
anakronsomeone can say repositories of 5-a-day applet for intrepid or hardy?07:15
=== mcas_away is now known as mcas
=== Igorots is now known as Igorot
mcashello10:44
mcasi need some help with bug26314110:44
mcasi need some help with bug 26314110:45
ubottuLaunchpad bug 263141 in firefox-3.0 "Ctrl+C and Ctrl+V does not work with Caps Lock active" [Undecided,New] https://launchpad.net/bugs/26314110:45
mcasi think this is the correct behaviour10:45
mcasso how should i handle this bug10:45
thekornmcas, hi, I agree, it is the correct behaviour10:47
mcasshould i comment this and mark it as won't fix?10:47
thekornIMO it is invalid10:47
mcasah ok10:48
mcasthanks10:48
thekornI would close it as invalid and explain that the keys are ctrl+c and ctrl+v10:48
thekornand not ctrl+shift+v10:48
mcasok i'll do so10:49
thekornsuper10:49
mcasdone10:53
=== mcas is now known as mcas_away
=== asac_ is now known as asac
=== mcas_away is now known as mcas
=== warp10_ is now known as warp10
=== mcas is now known as mcas_away
=== Initial_2 is now known as Initial_M
=== bcurtiswx1 is now known as bcurtiswx
nullackWould someone please confirm bug 262027 for me, thanks22:48
ubottuLaunchpad bug 262027 in synaptic "Synaptic Erroneously Reports Success on Fail" [Undecided,New] https://launchpad.net/bugs/26202722:48
james_wnullack: I think that the package probably didn't fail installation22:53
nullackjames_w It did, and it resulted in X falling back to bulletproof X mode :)22:53
james_wnullack: I realise it failed, but it looks like it didn't fail22:54
james_wsorry, cryptic22:54
james_wit had a problem, but didn't report this with a non-zero exit code of the maintainer script22:54
james_wso dpkg/apt had no idea that it had a problem22:54
nullackjames_w: If a user upgrades tselliots driver packages and it fails, and it says it fails, synaptic shoould not say the upgrade was "successful". So should I redirect the bug to tseliot on the driver?22:54
james_wthe action is probably run as "something-that-might-fail || true"22:55
nullackGiven hes not sending a fail code?22:55
james_wso that it doesn't fail the installation22:55
james_wI think it is a bug in the nvidia package, yes, would you reassign and modify the bug appropriately please?22:55
nullackYes I will, thanks mate22:55
james_wthank you22:56
nullackJust out of interest do I assume right that devs have a coding standard about errors? Just to be sure this is being consistently done and isnt in other packages as well?22:56
james_wsometimes this is done intentionally22:56
james_we.g. I know it is also done in flashplugin-nonfree22:57
james_wI don't agree with it there, but it is often a definite choice to do this22:57
nullackYeah I can see isolated reasons why it would need to be done sometimes22:58
tseliotmaybe we can report the problem to dkms22:58
andre____to use bug-buddy instead of apport, i have to create /apps/bug-buddy/run_on_crash and set it to true in gconf?22:59
nullackHi tseliot, is the problem with your package or dkms?22:59
tseliotnullack: both. I have fixed this bug: https://bugs.launchpad.net/bugs/26181623:00
ubottuLaunchpad bug 261816 in linux-restricted-modules-envy-2.6.24 "nvidia: Multiple versions in DKMS" [Medium,In progress]23:00
nullacktseliot : thank you I will edit my bug then23:01
tseliotbut there's still something left in the /var/lob/dkms/nvidia directory23:01
nullacktseliot : I have another matter I am in the process of raising a bug for, do you have time for a quick discuss?23:01
tseliottherefore there might still be directories which should have been removed23:01
tseliotnullack: sure23:01
nullacktselliot: Thanks. I did a fresh install of yesterdays ubuquity ISO23:02
nullacktselliot: After the glx install of 177.70 I got sent to bulletproof X23:02
nullacktselliot: I eventualy resolved it by getting rid of everything in xorg.conf except for the nvidia driver device section23:03
nullacktselliot: The default conf has items that dont need to be there like loading glx which is done anyway23:03
tseliotnullack: knowing what was there before would help me diagnose the problem23:03
nullacktselliot: X was failing because the server layout had a keyboard entry23:04
tseliotnullack: did it have a serverlayout section too?23:04
nullacktselliot: yes23:04
nullacktselliot: It was all debian default, then the glx install added other stuff23:05
tseliotnullack: and was there an entry about the keyboard in the serverlayout section?23:05
nullacktselliot: Another user said he installed 177.70 from a fresh install too, and he got booted to bulletproof x on logout, but after reboot was ok23:05
nullacktselliot: Yes, keyboard in server layout but no keyboard device as HAL configured it23:06
tseliotnullack: that's a different problem. Doing a sudo rmmod nvidia && sudo modprobe nvidia would have solved the problem23:06
nullacktselliot: Right, has to be removed and added back with latest I understand23:06
tseliotyes, or simply reboot23:07
nullacktselliot: Anyway, it seems to me that the install is adding stuff to the xorg.conf that isnt needed and HAL is setting it all up anyway23:07
tseliotadding glx won't cause any problem, however you might want to file a bug report with the original xorg.conf about the problems with input devices23:08
nullacktselliot: I will do that thanks. Im a big fan of your work and Im grateful that you always quickly get out new nvidia drivers once they are released. Top stuff :)23:09
tseliot;)23:09
sectechhowdie23:29
sectechFor hardy,  has any of the kernel developers addressed the issue of the "suspend to ram" kernel panic being fixed for hardy?23:29
sectechone too many hardy's23:30
james_whi sectech23:30
sectechI know they wanted to move forward to 2.6.27... problem is that the people running hardy now that don't follow bugs are kinda screwed up right now23:31
james_wis there a bug for it?23:31
sectechjames_w,  the closest that I can see is 25125223:31
james_w#ubuntu-kernel is probably a better place for these questions, they will be more knowledgeable.23:31
sectechjames_w,  true...  they would be... but probably were asked the question 1000 times already23:32
sectech2.6.27 fixes the problem...  but the hardy users arn't getting that kernel as far as I know23:33
james_wI doubt they will23:34
e-jatuse intrepid main repo ... then u will get the 2.6.27-223:34
james_wif you know it fixes it you can "bisect" to find the fix, and then that can be applied in hardy.23:34
sectechjames_w,  I guess my issue is that _I_ know how to get around it... but what about the other hardy users...23:35
james_wthat's the right instinct, and if you could point towards the fix I'm sure the developers would apply it to the hardy kernel.23:35
sectechjames_w,  imagine they would... I am still trying to find out how wide spread the bug is... I have been off for a few weeks and I just noticed this now23:37
sectechit was affecting my laptop for the last couple days,  this is the first day I could look into it23:37
sectechthere might be a fix out there.23:37
nullackCan I please get a second opinion on bug 262788 - The user has now attached required logs and Im thinking about making the package APCI rather than the Linux kernel?23:46
ubottuLaunchpad bug 262788 in linux "linux 2.6.27 kernel won't boot on amd64 hp laptop" [Undecided,New] https://launchpad.net/bugs/26278823:46
james_wis there such a package?23:48
sectechjames_w,  I was getting in a panic for nothing... I had the proposed repository enabled by accident23:50
james_wyou have the problem with -proposed, but not with -updates?23:50
james_wah, there is an acpi package, I'm not sure it should be moved there though, I would still suspect the kernel.23:52
sectechjames_w,  With proposed packages arn't out of testing yet...23:52
sectechif an end user enabled that repository, they do so at there own risk23:52
sectechin my opinonj23:52
sectecherr opinion23:52
nullackjames_w: thanks Ill leave the package with the kernel and I guess the kernel devs can drill down from there23:53
sectechI tried to keep this laptop as "end user" friendly as possible... my desktop is used for testing... I guess I must have hit that by mistake23:53
james_wsectech: they are there for testing, if you find a regression in a package in -proposed please file a bug and state that it is a regression in -proposed package, otherwise it will be moved to -updates and more people will be exposed to it23:53
sectechjames_w,  I am looking at that part now...23:54
james_wthanks23:55
sectechthat would be very bad if that hits -updates23:55
sectechjames_w,  I actually have a guy on #ubuntu-kernel (not part of the devel or any other team) trying to tell me that a kernel panic isn't important.23:56
sectechlol23:56

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