apport-gtk crashed with KeyError in __getitem__()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: apport
Not sure.
ProblemType: Crash
ApportLog:
apport (pid 6769) Sat Oct 31 05:05:15 2009: called for pid 6768, signal 6
apport (pid 6769) Sat Oct 31 05:05:15 2009: executable: /usr/sbin/cupsd (command line "/usr/sbin/cupsd")
apport (pid 6769) Sat Oct 31 05:05:15 2009: Ignoring SIGABRT
Architecture: amd64
CrashReports:
600:0:
600:0:
Date: Sat Oct 31 06:58:34 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.6
NonfreeKernelMo
Package: apport-gtk 1.9.3-0ubuntu4
PackageArchitec
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: apport
Title: apport-gtk crashed with KeyError in __getitem__()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:
Mark Avera (averamj) wrote : | #1 |
Apport retracing service (apport) wrote : This bug is a duplicate | #2 |
tags: | removed: need-duplicate-check |
visibility: | private → public |
jiml27 (jiml9) wrote : Re: [Bug 466489] Re: apport-gtk crashed with KeyError in __getitem__() | #3 |
stop sending me these. This is not the bug I reported.
On 11/05/2009 04:52 PM, Apport retracing service wrote:
> *** This bug is a duplicate of bug 424965 ***
> https:/
>
> Thank you for taking the time to report this crash and helping to make
> Ubuntu better. This particular crash has already been reported and is a
> duplicate of bug #424965, so is being marked as such. Please look at
> the other bug report to see if there is any missing information that you
> can provide, or to see if there is a workaround for the bug.
> Additionally, any further discussion regarding the bug should occur in
> the other report. Please continue to report any other bugs you may
> find.
>
> ** Tags removed: need-duplicate-
>
> ** Attachment removed: "Dependencies.txt"
> http://
>
> ** Attachment removed: "ProcMaps.txt"
> http://
>
> ** Attachment removed: "ProcStatus.txt"
> http://
>
> ** This bug has been marked a duplicate of bug 424965
> apport-gtk crashed with KeyError in __getitem__()
>
> ** Visibility changed to: Public
>
>
Frogman66 (jeff-froning-deactivatedaccount) wrote : | #4 |
Sorry, But I am not sending them. They are coming from launchpad. I
have gotten about 20 of them.
jiml27 wrote:
> *** This bug is a duplicate of bug 424965 ***
> https:/
>
> stop sending me these. This is not the bug I reported.
>
> On 11/05/2009 04:52 PM, Apport retracing service wrote:
>
>> *** This bug is a duplicate of bug 424965 ***
>> https:/
>>
>> Thank you for taking the time to report this crash and helping to make
>> Ubuntu better. This particular crash has already been reported and is a
>> duplicate of bug #424965, so is being marked as such. Please look at
>> the other bug report to see if there is any missing information that you
>> can provide, or to see if there is a workaround for the bug.
>> Additionally, any further discussion regarding the bug should occur in
>> the other report. Please continue to report any other bugs you may
>> find.
>>
>> ** Tags removed: need-duplicate-
>>
>> ** Attachment removed: "Dependencies.txt"
>> http://
>>
>> ** Attachment removed: "ProcMaps.txt"
>> http://
>>
>> ** Attachment removed: "ProcStatus.txt"
>> http://
>>
>> ** This bug has been marked a duplicate of bug 424965
>> apport-gtk crashed with KeyError in __getitem__()
>>
>> ** Visibility changed to: Public
>>
>>
>>
>
>
jimmy roussel (jamesroussel) wrote : Re: [Bug 466489] Re: apport-gtk crashed with KeyError in __getitem__() | #5 |
I am getting them also about 20 of them, why?
On Fri, Nov 6, 2009 at 4:03 PM, Frogman66 <email address hidden>wrote:
> *** This bug is a duplicate of bug 424965 ***
> https:/
>
> Sorry, But I am not sending them. They are coming from launchpad. I
> have gotten about 20 of them.
>
> jiml27 wrote:
> > *** This bug is a duplicate of bug 424965 ***
> > https:/
> >
> > stop sending me these. This is not the bug I reported.
> >
> > On 11/05/2009 04:52 PM, Apport retracing service wrote:
> >
> >> *** This bug is a duplicate of bug 424965 ***
> >> https:/
> >>
> >> Thank you for taking the time to report this crash and helping to make
> >> Ubuntu better. This particular crash has already been reported and is a
> >> duplicate of bug #424965, so is being marked as such. Please look at
> >> the other bug report to see if there is any missing information that you
> >> can provide, or to see if there is a workaround for the bug.
> >> Additionally, any further discussion regarding the bug should occur in
> >> the other report. Please continue to report any other bugs you may
> >> find.
> >>
> >> ** Tags removed: need-duplicate-
> >>
> >> ** Attachment removed: "Dependencies.txt"
> >> http://
> >>
> >> ** Attachment removed: "ProcMaps.txt"
> >> http://
> >>
> >> ** Attachment removed: "ProcStatus.txt"
> >> http://
> >>
> >> ** This bug has been marked a duplicate of bug 424965
> >> apport-gtk crashed with KeyError in __getitem__()
> >>
> >> ** Visibility changed to: Public
> >>
> >>
> >>
> >
> >
>
> --
> apport-gtk crashed with KeyError in __getitem__()
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (via bug 424965).
>
> Status in “apport” package in Ubuntu: New
>
> Bug description:
> Binary package hint: apport
>
> Not sure.
>
> ProblemType: Crash
> ApportLog:
> apport (pid 6769) Sat Oct 31 05:05:15 2009: called for pid 6768, signal 6
> apport (pid 6769) Sat Oct 31 05:05:15 2009: executable: /usr/sbin/cupsd
> (command line "/usr/sbin/cupsd")
> apport (pid 6769) Sat Oct 31 05:05:15 2009: Ignoring SIGABRT
> Architecture: amd64
> CrashReports:
> 600:0:0:
> 06:58:13.000000000 -0500:/
> 600:0:0:
> 06:58:40.000000000 -0500:/
> Date: Sat Oct 31 06:58:34 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/share/
> InterpreterPath: /usr/bin/python2.6
> NonfreeKernelMo
> Package: apport-gtk 1.9.3-0ubuntu4
> PackageArchitec
> ProcCmdline: /usr/bin/python /usr/share/
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSign
> PythonArgs: ['/usr/
> Sou...
Sebastian (svillarreal11) wrote : Re: [Bug 466489] Re: apport-gtk crashed with KeyError in __getitem__() | #6 |
If anyone should stop sending messages is you. I am saturated with messages
like yours further more I no longer have nothing to do with Ubuntu 9.10...
If you don't mind conplain to the people who run that Linux site.
Regards,
Sebastian
----- Original Message -----
From: "jiml27" <email address hidden>
To: <email address hidden>
Sent: Friday, November 06, 2009 3:39 PM
Subject: Re: [Bug 466489] Re: apport-gtk crashed with KeyError in
__getitem__()
*** This bug is a duplicate of bug 424965 ***
https:/
stop sending me these. This is not the bug I reported.
On 11/05/2009 04:52 PM, Apport retracing service wrote:
> *** This bug is a duplicate of bug 424965 ***
> https:/
>
> Thank you for taking the time to report this crash and helping to make
> Ubuntu better. This particular crash has already been reported and is a
> duplicate of bug #424965, so is being marked as such. Please look at
> the other bug report to see if there is any missing information that you
> can provide, or to see if there is a workaround for the bug.
> Additionally, any further discussion regarding the bug should occur in
> the other report. Please continue to report any other bugs you may
> find.
>
> ** Tags removed: need-duplicate-
>
> ** Attachment removed: "Dependencies.txt"
> http://
>
> ** Attachment removed: "ProcMaps.txt"
> http://
>
> ** Attachment removed: "ProcStatus.txt"
> http://
>
> ** This bug has been marked a duplicate of bug 424965
> apport-gtk crashed with KeyError in __getitem__()
>
> ** Visibility changed to: Public
>
>
--
apport-gtk crashed with KeyError in __getitem__()
https:/
You received this bug notification because you are a direct subscriber
of a duplicate bug (via bug 424965).
Status in “apport” package in Ubuntu: New
Bug description:
Binary package hint: apport
Not sure.
ProblemType: Crash
ApportLog:
apport (pid 6769) Sat Oct 31 05:05:15 2009: called for pid 6768, signal 6
apport (pid 6769) Sat Oct 31 05:05:15 2009: executable: /usr/sbin/cupsd
(command line "/usr/sbin/cupsd")
apport (pid 6769) Sat Oct 31 05:05:15 2009: Ignoring SIGABRT
Architecture: amd64
CrashReports:
600:0:
06:58:13.000000000 -0500:/
600:0:
06:58:40.000000000 -0500:/
Date: Sat Oct 31 06:58:34 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.6
NonfreeKernelMo
Package: apport-gtk 1.9.3-0ubuntu4
PackageArchitec
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: apport
Title: apport-gtk crashed with KeyError in __getitem__()
...
Sebastian (svillarreal11) wrote : | #7 |
LISTEN UP...COMPLAIN TO THOSE CHUMPS AT LAUNCH PAD, DON'T BE COMING DOWN ON
ME.
HELL, MAN I GET 30-40 OF THESE MESSAGES AND I DON'T EVEN RUN LINUX OR UBUNTU
9.10
----- Original Message -----
From: "Frogman66" <email address hidden>
To: <email address hidden>
Sent: Friday, November 06, 2009 4:03 PM
Subject: Re: [Bug 466489] Re: apport-gtk crashed with KeyError in
__getitem__()
*** This bug is a duplicate of bug 424965 ***
https:/
Sorry, But I am not sending them. They are coming from launchpad. I
have gotten about 20 of them.
jiml27 wrote:
> *** This bug is a duplicate of bug 424965 ***
> https:/
>
> stop sending me these. This is not the bug I reported.
>
> On 11/05/2009 04:52 PM, Apport retracing service wrote:
>
>> *** This bug is a duplicate of bug 424965 ***
>> https:/
>>
>> Thank you for taking the time to report this crash and helping to make
>> Ubuntu better. This particular crash has already been reported and is a
>> duplicate of bug #424965, so is being marked as such. Please look at
>> the other bug report to see if there is any missing information that you
>> can provide, or to see if there is a workaround for the bug.
>> Additionally, any further discussion regarding the bug should occur in
>> the other report. Please continue to report any other bugs you may
>> find.
>>
>> ** Tags removed: need-duplicate-
>>
>> ** Attachment removed: "Dependencies.txt"
>> http://
>>
>> ** Attachment removed: "ProcMaps.txt"
>> http://
>>
>> ** Attachment removed: "ProcStatus.txt"
>> http://
>>
>> ** This bug has been marked a duplicate of bug 424965
>> apport-gtk crashed with KeyError in __getitem__()
>>
>> ** Visibility changed to: Public
>>
>>
>>
>
>
--
apport-gtk crashed with KeyError in __getitem__()
https:/
You received this bug notification because you are a direct subscriber
of a duplicate bug (via bug 424965).
Status in “apport” package in Ubuntu: New
Bug description:
Binary package hint: apport
Not sure.
ProblemType: Crash
ApportLog:
apport (pid 6769) Sat Oct 31 05:05:15 2009: called for pid 6768, signal 6
apport (pid 6769) Sat Oct 31 05:05:15 2009: executable: /usr/sbin/cupsd
(command line "/usr/sbin/cupsd")
apport (pid 6769) Sat Oct 31 05:05:15 2009: Ignoring SIGABRT
Architecture: amd64
CrashReports:
600:0:
06:58:13.000000000 -0500:/
600:0:
06:58:40.000000000 -0500:/
Date: Sat Oct 31 06:58:34 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.6
NonfreeKernelMo
Package: apport-gtk 1.9.3-0ubuntu4
PackageArchitec
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHE...
Sebastian (svillarreal11) wrote : | #8 |
FILE A COMPLAINT WITH "LAUNCH PAD" THEY ARE THE ONES SENDING THIS SH**!!! I
DO NOT HAVE LINUX ON MY RIG.
GOOD LUCK
----- Original Message -----
From: "jimmy roussel" <email address hidden>
To: <email address hidden>
Sent: Friday, November 06, 2009 4:51 PM
Subject: Re: [Bug 466489] Re: apport-gtk crashed with KeyError in
__getitem__()
*** This bug is a duplicate of bug 424965 ***
https:/
I am getting them also about 20 of them, why?
On Fri, Nov 6, 2009 at 4:03 PM, Frogman66
<email address hidden>wrote:
> *** This bug is a duplicate of bug 424965 ***
> https:/
>
> Sorry, But I am not sending them. They are coming from launchpad. I
> have gotten about 20 of them.
>
> jiml27 wrote:
> > *** This bug is a duplicate of bug 424965 ***
> > https:/
> >
> > stop sending me these. This is not the bug I reported.
> >
> > On 11/05/2009 04:52 PM, Apport retracing service wrote:
> >
> >> *** This bug is a duplicate of bug 424965 ***
> >> https:/
> >>
> >> Thank you for taking the time to report this crash and helping to make
> >> Ubuntu better. This particular crash has already been reported and is
> >> a
> >> duplicate of bug #424965, so is being marked as such. Please look at
> >> the other bug report to see if there is any missing information that
> >> you
> >> can provide, or to see if there is a workaround for the bug.
> >> Additionally, any further discussion regarding the bug should occur in
> >> the other report. Please continue to report any other bugs you may
> >> find.
> >>
> >> ** Tags removed: need-duplicate-
> >>
> >> ** Attachment removed: "Dependencies.txt"
> >> http://
> >>
> >> ** Attachment removed: "ProcMaps.txt"
> >> http://
> >>
> >> ** Attachment removed: "ProcStatus.txt"
> >> http://
> >>
> >> ** This bug has been marked a duplicate of bug 424965
> >> apport-gtk crashed with KeyError in __getitem__()
> >>
> >> ** Visibility changed to: Public
> >>
> >>
> >>
> >
> >
>
> --
> apport-gtk crashed with KeyError in __getitem__()
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (via bug 424965).
>
> Status in “apport” package in Ubuntu: New
>
> Bug description:
> Binary package hint: apport
>
> Not sure.
>
> ProblemType: Crash
> ApportLog:
> apport (pid 6769) Sat Oct 31 05:05:15 2009: called for pid 6768, signal 6
> apport (pid 6769) Sat Oct 31 05:05:15 2009: executable: /usr/sbin/cupsd
> (command line "/usr/sbin/cupsd")
> apport (pid 6769) Sat Oct 31 05:05:15 2009: Ignoring SIGABRT
> Architecture: amd64
> CrashReports:
> 600:0:0:
> 06:58:13.000000000 -0500:/
> 600:0:0:
> 06:58:40.000000000 -0500:/
> Date: Sat Oct 31 06:58:34 2009
>...
Steve Langasek (vorlon) wrote : | #9 |
On Sat, Nov 07, 2009 at 12:48:12AM -0000, Sebastian wrote:
> *** This bug is a duplicate of bug 424965 ***
> https:/
> FILE A COMPLAINT WITH "LAUNCH PAD" THEY ARE THE ONES SENDING THIS SH**!!! I
> DO NOT HAVE LINUX ON MY RIG.
Launchpad does not send unsolicited email. If you are receiving notices
about this bug, it is either because you are subscribed to the bug directly
(because you subscribed yourself or because another Launchpad user
subscribed you), or because someone else who is subscribed to this bug is
forwarding those messages to you.
In the latter case, you should review the mail you're receiving for
information about who's forwarding them to you, since that's not Launchpad's
doing.
In the former case, every mail sent by Launchpad includes information at the
bottom about how to unsubscribe from a given bug.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://
<email address hidden> <email address hidden>
cogefip (cogefip) wrote : | #10 |
Ce n'est pas moi,
Cette nuit, 1 heure 48 Paris, ma machine était arrêté.
Desolé
This is not me
That night, 1 hour 48 Paris, my machine was stopped.
Sorry
Sebastian a écrit :
> *** This bug is a duplicate of bug 424965 ***
> https:/
>
> FILE A COMPLAINT WITH "LAUNCH PAD" THEY ARE THE ONES SENDING THIS SH**!!! I
> DO NOT HAVE LINUX ON MY RIG.
> GOOD LUCK
> ----- Original Message -----
> From: "jimmy roussel" <email address hidden>
> To: <email address hidden>
> Sent: Friday, November 06, 2009 4:51 PM
> Subject: Re: [Bug 466489] Re: apport-gtk crashed with KeyError in
> __getitem__()
>
>
> *** This bug is a duplicate of bug 424965 ***
> https:/
>
> I am getting them also about 20 of them, why?
>
> On Fri, Nov 6, 2009 at 4:03 PM, Frogman66
> <email address hidden>wrote:
>
>
>> *** This bug is a duplicate of bug 424965 ***
>> https:/
>>
>> Sorry, But I am not sending them. They are coming from launchpad. I
>> have gotten about 20 of them.
>>
>> jiml27 wrote:
>>
>>> *** This bug is a duplicate of bug 424965 ***
>>> https:/
>>>
>>> stop sending me these. This is not the bug I reported.
>>>
>>> On 11/05/2009 04:52 PM, Apport retracing service wrote:
>>>
>>>
>>>> *** This bug is a duplicate of bug 424965 ***
>>>> https:/
>>>>
>>>> Thank you for taking the time to report this crash and helping to make
>>>> Ubuntu better. This particular crash has already been reported and is
>>>> a
>>>> duplicate of bug #424965, so is being marked as such. Please look at
>>>> the other bug report to see if there is any missing information that
>>>> you
>>>> can provide, or to see if there is a workaround for the bug.
>>>> Additionally, any further discussion regarding the bug should occur in
>>>> the other report. Please continue to report any other bugs you may
>>>> find.
>>>>
>>>> ** Tags removed: need-duplicate-
>>>>
>>>> ** Attachment removed: "Dependencies.txt"
>>>> http://
>>>>
>>>> ** Attachment removed: "ProcMaps.txt"
>>>> http://
>>>>
>>>> ** Attachment removed: "ProcStatus.txt"
>>>> http://
>>>>
>>>> ** This bug has been marked a duplicate of bug 424965
>>>> apport-gtk crashed with KeyError in __getitem__()
>>>>
>>>> ** Visibility changed to: Public
>>>>
>>>>
>>>>
>>>>
>>>
>> --
>> apport-gtk crashed with KeyError in __getitem__()
>> https:/
>> You received this bug notification because you are a direct subscriber
>> of a duplicate bug (via bug 424965).
>>
>> Status in “apport” package in Ubuntu: New
>>
>> Bug description:
>> Binary package hint: apport
>>
>> Not sure.
>>
>> ProblemType: Crash
>> ApportLog:
>> apport (pid 6769) Sat Oct 31 05:05:15 2009: called for pid 6768, signal 6
>> apport (pid 6769) Sat Oct 31 05:05:15 2009: executable: /usr/sbin/cupsd
>> (command line "/usr/sbin/cupsd")
>> apport (pid 6769) Sat Oct 31 05:05:15 200...
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #424965, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.