We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Don't call it invalid just because no one's uploaded a full crash
report.
** Changed in: gnome-utils (Ubuntu)
Status: Invalid => Incomplete
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug notification because you are a me
The bug title mentions this is a segfault, so it should be possible to
obtain an apport crash file for this bug. Marking the bug as invalid is
reasonable in this case, as mentioned previously.
Please try to obtain a backtrace following the instructions at
http://wiki.ubuntu.com/DebuggingProgramCra
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic
I don't believe the crash is due to kernel version. I am running
2.6.27-11 and everything is fine, so as in other users too. It could be
useful to have a stack trace for that crash.
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug
** Changed in: gnome-utils (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug notification because you are a member of Ubu
Yes there is no crash report associated with the failure to start. I
just installed a fresh system on another machine and it's working fine
there. But still not working on my laptop. Something during the update
that updated the kernel caused the failure not necessarily the kernel
itself.
Please po
Yes there is no crash report associated with the failure to start. I
just installed a fresh system on another machine and it's working fine
there. But still not working on my laptop. Something during the update
that updated the kernel caused the failure not necessarily the kernel
itself.
Please po
Don't call it invalid just because no one's uploaded a full crash
report.
** Changed in: gnome-utils (Ubuntu)
Status: Invalid => Incomplete
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug notification because you are a me
The bug title mentions this is a segfault, so it should be possible to
obtain an apport crash file for this bug. Marking the bug as invalid is
reasonable in this case, as mentioned previously.
Please try to obtain a backtrace following the instructions at
http://wiki.ubuntu.com/DebuggingProgramCra
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic
I don't believe the crash is due to kernel version. I am running
2.6.27-11 and everything is fine, so as in other users too. It could be
useful to have a stack trace for that crash.
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug
** Changed in: gnome-utils (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug notification because you are a member of Ubu
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Don't call it invalid just because no one's uploaded a full crash
report.
** Changed in: gnome-utils (Ubuntu)
Status: Invalid => Incomplete
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug notification because you are a me
The bug title mentions this is a segfault, so it should be possible to
obtain an apport crash file for this bug. Marking the bug as invalid is
reasonable in this case, as mentioned previously.
Please try to obtain a backtrace following the instructions at
http://wiki.ubuntu.com/DebuggingProgramCra
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic
I don't believe the crash is due to kernel version. I am running
2.6.27-11 and everything is fine, so as in other users too. It could be
useful to have a stack trace for that crash.
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug
** Changed in: gnome-utils (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug notification because you are a member of Ubu
Yes there is no crash report associated with the failure to start. I
just installed a fresh system on another machine and it's working fine
there. But still not working on my laptop. Something during the update
that updated the kernel caused the failure not necessarily the kernel
itself.
Please po
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Yes there is no crash report associated with the failure to start. I
just installed a fresh system on another machine and it's working fine
there. But still not working on my laptop. Something during the update
that updated the kernel caused the failure not necessarily the kernel
itself.
Please po
Don't call it invalid just because no one's uploaded a full crash
report.
** Changed in: gnome-utils (Ubuntu)
Status: Invalid => Incomplete
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug notification because you are a me
The bug title mentions this is a segfault, so it should be possible to
obtain an apport crash file for this bug. Marking the bug as invalid is
reasonable in this case, as mentioned previously.
Please try to obtain a backtrace following the instructions at
http://wiki.ubuntu.com/DebuggingProgramCra
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic
I don't believe the crash is due to kernel version. I am running
2.6.27-11 and everything is fine, so as in other users too. It could be
useful to have a stack trace for that crash.
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug
** Changed in: gnome-utils (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug notification because you are a member of Ubu
Yes there is no crash report associated with the failure to start. I
just installed a fresh system on another machine and it's working fine
there. But still not working on my laptop. Something during the update
that updated the kernel caused the failure not necessarily the kernel
itself.
Please po
Don't call it invalid just because no one's uploaded a full crash
report.
** Changed in: gnome-utils (Ubuntu)
Status: Invalid => Incomplete
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug notification because you are a me
The bug title mentions this is a segfault, so it should be possible to
obtain an apport crash file for this bug. Marking the bug as invalid is
reasonable in this case, as mentioned previously.
Please try to obtain a backtrace following the instructions at
http://wiki.ubuntu.com/DebuggingProgramCra
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic
I don't believe the crash is due to kernel version. I am running
2.6.27-11 and everything is fine, so as in other users too. It could be
useful to have a stack trace for that crash.
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug
** Changed in: gnome-utils (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug notification because you are a member of Ubu
Yes there is no crash report associated with the failure to start. I
just installed a fresh system on another machine and it's working fine
there. But still not working on my laptop. Something during the update
that updated the kernel caused the failure not necessarily the kernel
itself.
Please po
Don't call it invalid just because no one's uploaded a full crash
report.
** Changed in: gnome-utils (Ubuntu)
Status: Invalid => Incomplete
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug notification because you are a me
The bug title mentions this is a segfault, so it should be possible to
obtain an apport crash file for this bug. Marking the bug as invalid is
reasonable in this case, as mentioned previously.
Please try to obtain a backtrace following the instructions at
http://wiki.ubuntu.com/DebuggingProgramCra
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic
I don't believe the crash is due to kernel version. I am running
2.6.27-11 and everything is fine, so as in other users too. It could be
useful to have a stack trace for that crash.
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug
** Changed in: gnome-utils (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
--
baobab segfault on start after upgrade to 2.6.27.11
https://bugs.launchpad.net/bugs/309894
You received this bug notification because you are a member of Ubu
42 matches
Mail list logo
