[Expired for apport (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apport (Ubuntu)
Status: Incomplete = Expired
--
apport ValueError('need more than 1 value to unpack',)
https://bugs.launchpad.net/bugs/485238
You received this bug notification because you are a
X3 [2009-11-25 10:35 -]:
Pehaps the Karmic documentation on this should be revised and the root
of why this has happened on a minimal install spits out that error when
like you say it should have outputed that -c is invalid to start with.
Where did you see the -c being documented? I'm
Ah, I gracefully ignored that, since -c does not even work any more:
$ ubuntu-bug -c /tmp/linux-image.apport
Usage: /usr/bin/ubuntu-bug pid|symptom name|package name|program
path|.crash file
Which Ubuntu release are you trying this on? In the initial description
you said 9.10 (karmic), but -c
Well if I said Karmic then it was karmic, like I said the documentation
does point to that.
On another note could you be a gentleman and ping someone to get some
ball rolling on other bug report since it will either be addressed
properly with the introduction of a decently working kernel on the
###Also, the error you got shows that it was actually reading the
.apport file and stumbled over an invalidly formatted line. If there
###were problems with recognizing the command line arguments, it would
have looked completely different.
Well in this case some bug does exist in the minimal
Actually no the switch is ubuntu-bug -c /tmp/linux-image.apport if the
-c is redundant then the documentation is wrong. If you use -c which is
for path then IT will bug out and this is how the documentations says
you should do it and thats where it craps out...
I remember saying I used the -c at
I tried this:
$ ubuntu-bug /tmp/linux-image.apport
works fine for me. So this doesn't reproduce the apport crash.
As for the actual bug in Linux, I'm afraid that's not my area of
expertise. :-(
--
apport ValueError('need more than 1 value to unpack',)
https://bugs.launchpad.net/bugs/485238
like I said the bug only occurrs when your trying to later upload the
apport generated file and the error is a s documented.
the file is here http://launchpadlibrarian.net/35849216/linux-
image.apport
Pertaining to another bug no one has even touched or commeneted and is far more
serious then
the bug does not exist when doing apport-cli -f -p linux the bug occurrs
when you do ubuntu-bug -c path
--
apport ValueError('need more than 1 value to unpack',)
https://bugs.launchpad.net/bugs/485238
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I still cannot reproduce this, this works fine for me. Please attach the
generated .apport file which reproduces the crash. Thanks!
--
apport ValueError('need more than 1 value to unpack',)
https://bugs.launchpad.net/bugs/485238
You received this bug notification because you are a member of
Can you please tell me which package you were trying to file the bug
against? Can you please attach the .crash file which caused the problem?
** Changed in: apport (Ubuntu)
Status: New = Incomplete
--
apport ValueError('need more than 1 value to unpack',)
the package was the linux-kernel and there was no crash report I was
gathering info to report another issue and apport failed to work as
expected.
I donthave anymore information relevant to this except what I posted
already which is irrelevant since this bug is independent of the other,
at least
I just tried apport-cli -f -p linux and it did not crash. Can you
replicate the crash? Please copypaste the entire output.
--
apport ValueError('need more than 1 value to unpack',)
https://bugs.launchpad.net/bugs/485238
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
Binary package hint: apport
- I collected a
+ I collected a report via cli like apport-cli -f -p package kept it for
+ later sending as ubuntu-bug -c path
+
+ this is being done in Karmic Koala 9.10 with shipping kernel and
+ backports kernel doesnt make a differnce.
14 matches
Mail list logo
