Still no network: Nautilus kann nicht mit network:/// umgehen
(Nautilus cannot deal with network:///) Should that be a new bug?
dpkg -l | grep nautilus
ii libnautilus-burn4 2.21.6-0ubuntu1
Nautilus Burn Library - runtime version
ii
Yes I think it should be. I also experience this bug.
On Sat, Feb 2, 2008 at 4:10 AM, barbex [EMAIL PROTECTED] wrote:
Still no network: Nautilus kann nicht mit network:/// umgehen
(Nautilus cannot deal with network:///) Should that be a new bug?
dpkg -l | grep nautilus
ii libnautilus-burn4
I don't know if it helps but I attached the output from gdb after
following the instruction from hyperair (2008-01-24).
** Attachment added: gdb.out
http://launchpadlibrarian.net/11685890/gdb.out
--
[Hardy] Nautilus segfaults, cannot be upgraded
https://bugs.launchpad.net/bugs/185650
You
Latest update fixed the problem for me but killed the network
dpkg -l | grep nautilus
ii libnautilus-burn4 2.21.6-0ubuntu1
Nautilus Burn Library - runtime version
ii libnautilus-extension11:2.21.90-0ubuntu1
The problem's fixed for me. Network's fine for me too.
On Fri, Feb 1, 2008 at 6:19 AM, barbex [EMAIL PROTECTED] wrote:
Latest update fixed the problem for me but killed the network
dpkg -l | grep nautilus
ii libnautilus-burn4 2.21.6-0ubuntu1
Nautilus
workaround is to remove nautilus-share, it needs some work for the new
ABI.
--
[Hardy] Nautilus segfaults, cannot be upgraded
https://bugs.launchpad.net/bugs/185650
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for eel2 in ubuntu.
--
Did you upgrade nautilus or not? The bug report is not clear. Could you
get a crash stacktrace?
** Changed in: nautilus (Ubuntu)
Status: New = Incomplete
--
[Hardy] Nautilus segfaults, cannot be upgraded
https://bugs.launchpad.net/bugs/185650
You received this bug notification because
I cannot upgrade nautilus because when i use sudo apt-get upgrade it
says that all the packages are kept back and does nothing. When I use
sudo apt-get dist-upgrade I get the output as shown above. I just
aborted because it tries to remove nautilus as well as ubuntu-desktop,
among other nautilus
Stack trace:
#0 0xb71d7b03 in strchr () from /lib/tls/i686/cmov/libc.so.6
#1 0xb6036abd in ?? ()
from /usr/lib/nautilus/extensions-1.0/libnautilus-open-terminal.so
#2 0x in ?? ()
--
[Hardy] Nautilus segfaults, cannot be upgraded
https://bugs.launchpad.net/bugs/185650
You received
one bug task is enough and that's not a libeel issue
** Changed in: eel2 (Ubuntu)
Status: New = Invalid
--
[Hardy] Nautilus segfaults, cannot be upgraded
https://bugs.launchpad.net/bugs/185650
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
I'll add a confirm on this , I first removed python-nautilus which was
blocking libeel2 then upgraded , nautilus segfaults
[EMAIL PROTECTED]:~$ nautilus
** (nautilus:8434): CRITICAL **: nautilus_file_new_from_filename: assertion
`filename[0] != '\0'' failed
Segmentation fault (core dumped)
Okay I removed nautilus-open-terminal and tried again. This time yields
more interesting results. Nautilus doesn't segfault. However, it keeps
opening (shows the desktop and my home directory for a brief moment),
and crashing, and repeating the process until I send SIGKILL to it.
This is what gdb
Ah python-nautilus was the problem! I just removed it, and with python-
nautilus, timevault. Then dist-upgraded the packages. Now it doesn't
segfault.
Then I've installed nautilus-open-terminal, and found that it's broken.
Damn. No menu item for opening a terminal.
--
[Hardy] Nautilus
I have reason to believe that Nautilus forks before encountering the
symbol lookup error. pidof nautilus reports a changing PID, and if the
timing is right, 2 PIDs.
--
[Hardy] Nautilus segfaults, cannot be upgraded
https://bugs.launchpad.net/bugs/185650
You received this bug notification because
could people having issue list the nautilus packages and versions they
are using and get a crach stacktrace to copy to the bug?
--
[Hardy] Nautilus segfaults, cannot be upgraded
https://bugs.launchpad.net/bugs/185650
You received this bug notification because you are a member of Ubuntu
Desktop
dist-upgraded again no help here it still segfaults with the same error
. NOTE! I am amd64 here .
--
[Hardy] Nautilus segfaults, cannot be upgraded
https://bugs.launchpad.net/bugs/185650
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact
[EMAIL PROTECTED]:~$ dpkg -l | grep nautilus
ii libnautilus-burn4 2.21.5-0ubuntu1
Nautilus Burn Library - runtime version
ii libnautilus-extension1 1:2.21.6-0ubuntu2
libraries for nautilus
[EMAIL PROTECTED]:~$ dpkg -l | grep nautilus
ii libnautilus-burn4 2.21.5-0ubuntu1
Nautilus Burn Library - runtime version
ii libnautilus-extension1 1:2.21.6-0ubuntu2
libraries for
The stacktrace is not one
--
[Hardy] Nautilus segfaults, cannot be upgraded
https://bugs.launchpad.net/bugs/185650
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for eel2 in ubuntu.
--
desktop-bugs mailing list
where do I find the right one ?
--
[Hardy] Nautilus segfaults, cannot be upgraded
https://bugs.launchpad.net/bugs/185650
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for eel2 in ubuntu.
--
desktop-bugs mailing list
Run gdb nautilus in a terminal. You will get a gdb prompt. Type run.
Then press enter every time it prompts you whether to continue or not.
Eventually it will crash. Then you will have a prompt again. Type bt.
The output is your stack trace.
--
[Hardy] Nautilus segfaults, cannot be upgraded
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fe0c75696f0 (LWP 21777)]
0x004b3b08 in ?? ()
(gdb) bt
#0 0x004b3b08 in ?? ()
#1 0x00431a3d in ?? ()
#2 0x00431b5f in ?? ()
#3 0x7fe0c373b948 in g_type_create_instance () from
instuctions to have apport report a new bug about your crash that can be
dealt with by the automatic retracer.
If you are using Ubuntu with the Gnome desktop environment - launch nautilus
and navigate to your /var/crash directory and double click on the crash report
you wish to submit.
If you
I cant launch nautilus, it segfaults . If I launch thunar and double
click on the crash report it does not send it , instead it opens the
report in text editor. besides the crash report is from before updating
, after update no crash report is generated because it never gets that
far it segfaults
Just running apport-cli in a terminal without any arguments should
offer to send the pending crash reports. Or you can issue apport-cli -c
/path/to/crash/file to send a particular one.
--
[Hardy] Nautilus segfaults, cannot be upgraded
https://bugs.launchpad.net/bugs/185650
You received this bug
25 matches
Mail list logo
