I should add that I didn't start an upgrade, then cancel it, like the
original bug reporter. I ran update-manager, and it was working away
when apport came up. These recent reports might be a lot of reasons
it's not the same bug, but this is where apport wanted to put it; same
errors and stack tr
I see that in duplicate bug 915413, apt-daemon crashed just before
update-manager. There's no evidence of that in the one time this
happened to me. For whatever that's worth...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Apport did not save the crash report from my system, seeing the bug as a
dupe. But since the original report is older, and information was asked
for, here is the crash report from my system.
** Attachment added: "_usr_bin_update-manager.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/u
Well, I haven't been able to reproduce the crash at all. Including
manually killing g-s-d while update-manager was running (although it
just restarted itself, so that wasn't quite what I was going for.) I
don't know if g-s-d's absence was a cause, at all, or another symptom of
something wrong in
More minor points -
The upgrade that was happening seemed to complete fine. No packages
were in a half-installed or unconfigured state, and every available
update was completed. (And as I said, the update-manager UI didn't go
away.)
It looks like gnome-settings daemon was missing, possibly cras
Apport just sent me here, from an apparent crash, although the update-
manager window is still present and functional, after the apport window
came up.
I can only offer pretty minor details.
The upgrade was just a day's worth of updates in Precise. It included a
new kernel, with update-manager i
I had this crash occur in precise as well. Note that #915413 was marked
as a duplicate of this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/628104
Title:
Doing and update and canceling it
To
@Brian: When the crach occured the system claimed it was already
reported and opened this bug.
I now manually uploaded it as Bug #915413
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/628104
Title:
@Nest - Did you receive an apport crash? If so it would be useful if
you were to report it and open a new bug. Thanks in advance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/628104
Title:
Doing
Just encountered this bug in Precise!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/628104
Title:
Doing and update and canceling it
To manage notifications about this bug go to:
https://bugs.launch
I've marked this bug as fix released, as it's clearly been fixed at some
point.
** Changed in: update-manager (Ubuntu)
Status: Confirmed => Invalid
** Changed in: update-manager (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privileg
12 matches
Mail list logo
