Precise upgrade and I got it simply seconds after logging in from a
fresh boot. Can we have the status changed to confirmed since so
multiple people are getting it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Quite similar to comment #12 except I upgraded to Ubuntu 12.04 Beta ?? on
2012-04-17 from Ubuntu 11.10.
Release 12.04 (precise) 32-bit
Kernel Linux 3.2.0-23-generic
GNOME 3.4.1
After login in, the error message was self generated (I did not open
nautilus).
--
You received this bug notification
Just happened to me on Ubuntu 12.04 LTS Beta 2 (nightly build), nautilus
3.4.0-0ubuntu2. It happened on a login to unity - I actually even didn't
opened nautilus - but got the crash detection and raise of this bug
report.
--
You received this bug notification because you are a member of Ubuntu
Just happened in Precise Beta 2 upon clicking on a .tex file
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/749409
Title:
nautilus crashed with SIGABRT in raise()
To manage notifications about this
I am on Precise and this happened when I wanted to open a DVD folder.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/749409
Title:
nautilus crashed with SIGABRT in raise()
To manage notifications
** Changed in: nautilus (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/749409
Title:
nautilus crashed with SIGABRT in raise()
To manage notifications
Javier, please don;t change status without explanation.
Did you manage to reproduce the bug? Which version were you using?
** Changed in: nautilus (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This issue just affected me in Ubuntu 12.04 LTS Alpha 2!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/749409
Title:
nautilus crashed with SIGABRT in raise()
To manage notifications about this bug
I am closing this report for now due to the last comment from the
original reporter. Thanks!
** Changed in: nautilus (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Is the issue reproducible with Nautilus 3.1.90 or newer?
There's no recent comments on this report indicating that, could you
please test and comment back?. Thanks again and we appreciate your help.
** Changed in:
You are welcome. I have tested it again and the issue is not reproducible
with a newer version of nautilus; no problem renaming any folder.Thanks for
making ubuntu be possible.
2011/9/8 Pedro Villavicencio pe...@ubuntu.com
Thank you for taking the time to report this bug and helping to make
For me it was renaming a file on an ftp server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/749409
Title:
nautilus crashed with SIGABRT in raise()
--
ubuntu-bugs mailing list
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/749409
Title:
nautilus crashed with SIGABRT in raise()
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
13 matches
Mail list logo
