Had another crash today, and went through the crash process, but in the
crash box that appears you hit the submit button, it just stops, so I
used the command ubuntu-bug colord which seemed to work, as I managed to
enter the crash in launchpad, but I am now getting crashes of different
things e
On 9 May 2012 08:09, scoundrel50a wrote:
> On 05/05/12 16:46, Alan Pope wrote:
>>
>> On 05/05/12 01:46, scoundrel50a wrote:
>>>
>>> > Ok, did that, and as soon as the laptop started a crash report box
>>> > appeared, blueman applet, so I went through the process again, and
>>> > nothing happene
On 05/05/12 16:46, Alan Pope wrote:
On 05/05/12 01:46, scoundrel50a wrote:
> Ok, did that, and as soon as the laptop started a crash report box
> appeared, blueman applet, so I went through the process again, and
> nothing happened, how do you know if the crash report gets to you,
> how do y
On 5 May 2012 16:46, Alan Pope wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 05/05/12 01:46, scoundrel50a wrote:
>> Ok, did that, and as soon as the laptop started a crash report box
>> appeared, blueman applet, so I went through the process again, and
>> nothing happened, how do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/05/12 01:46, scoundrel50a wrote:
> Ok, did that, and as soon as the laptop started a crash report box
> appeared, blueman applet, so I went through the process again, and
> nothing happened, how do you know if the crash report gets to you,
> ho
On 05/05/12 09:46, scoundrel50a wrote:
.
> then I try the terminal and use ubuntu-bug whatever and it says it
> cant find the crash report.
ubuntu-bug shouldn't be looking for crash reports. It should
just file a new bug.
oh, ok, now I have learnt something, what is the difference be
A bug can be a flaw in an otherwise functional program, like a typo or an
unclickable button. A crash is when the program ceases to respond to user
interaction, usually seen as it just closing.
An example of a crash on say, android, is when you get a "force close"
message.
On May 5, 2012 9:47 AM,
On 04/05/12 23:59, Alan Pope wrote:
On 04/05/12 12:18, scoundrel50a wrote:
> Since I had to do the reinstall, I keep getting crash reports, a
> lot more than what I was getting when it was running beta 1.I
> click on the crash report logo, it brings up the box, which shows
> what has cra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/05/12 12:18, scoundrel50a wrote:
> Since I had to do the reinstall, I keep getting crash reports, a
> lot more than what I was getting when it was running beta 1.I
> click on the crash report logo, it brings up the box, which shows
> what has
On 4 May 2012 22:32, Tony Pursell wrote:
>
>
> On 4 May 2012 21:17, Colin Law wrote:
>
>> On 4 May 2012 20:18, scoundrel50a wrote:
>> > Since I had to do the reinstall, I keep getting crash reports, a lot
>> more
>> > than what I was getting when it was running beta 1.I click on the
>> cras
On 4 May 2012 21:17, Colin Law wrote:
> On 4 May 2012 20:18, scoundrel50a wrote:
> > Since I had to do the reinstall, I keep getting crash reports, a lot more
> > than what I was getting when it was running beta 1.I click on the
> crash
> > report logo, it brings up the box, which shows what
On 4 May 2012 20:18, scoundrel50a wrote:
> Since I had to do the reinstall, I keep getting crash reports, a lot more
> than what I was getting when it was running beta 1.I click on the crash
> report logo, it brings up the box, which shows what has crashed and where it
> says submit, I click a
Since I had to do the reinstall, I keep getting crash reports, a lot
more than what I was getting when it was running beta 1.I click on
the crash report logo, it brings up the box, which shows what has
crashed and where it says submit, I click and nothing happens, so I cant
submit the crash
13 matches
Mail list logo
