Chris, is this the type of log you need for the bug? By the way,
sudonautilus is simply a script that contains sudo nautilus. My
apologies in advance if this is not what you need, as I don't usually
participate past describing bugs I have experienced. :-)
** Attachment added: valgrind.log
Sorry, forgot:
~$ sudo -s
r...@phoenix:~# nautilus
Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0e 0x00 0x00 0x00 0x00 0x3a
0x00 0x00 0x00 0x00 0x00 0x00
** (nautilus:6789): WARNING **: No marshaller for signature of signal
'UploadFinished'
** (nautilus:6789): WARNING **: No marshaller for
~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --log-file=valgrind.log gksudo nautilus
Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0e 0x00 0x00 0x00 0x00 0x3a
0x00 0x00 0x00 0x00 0x00 0x00
** (nautilus:6728): WARNING **: No
It is.. Try look at this bug
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/422041.. It's the
bug I reported but I don't know how to do the valgrind thing.. I tried
but it doesn't seem to work...
--
karmic nautilus fails to run as root
https://bugs.launchpad.net/bugs/420841
You received
I've got the same problem (I mistakenly reported a duplicate #424714)
I'm guessing it won't shine much light on the situation, but here's what I got:
berke...@be-just:~$ sudo nautilus
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Sense key: 0x70 0x00 0x02 0x00
Will this backtrace suffice?
What measures you would recommend on debugging gksudo nautilus not
working?
** Attachment added: gdb-nautilus-txt
http://launchpadlibrarian.net/31257111/gdb-nautilus-txt
--
karmic nautilus fails to run as root
https://bugs.launchpad.net/bugs/420841
You received
This certainly does seem to be related to brasero. If I downgrade to the
Jaunty versions of both brasero and libbrasero-media0 that seems to
solve the nautilus as root problem (both from cli and using the gui
'nautilus-gksu').
I must say however that it's not even a decent work-around because you
Chris, was there something wrong with my backtrace in comment #3?
--
karmic nautilus fails to run as root
https://bugs.launchpad.net/bugs/420841
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in ubuntu.
--
desktop-bugs
Yes, it's of a completely separate crash.
--
karmic nautilus fails to run as root
https://bugs.launchpad.net/bugs/420841
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in ubuntu.
--
desktop-bugs mailing list
I am also having the same problem with Karmic, but the workaround mentioned is
not working. Here is the output for sudo su then nautilus.
k...@karl-desktop:~$ sudo su
To run a command as administrator (user root), use sudo command.
See man sudo_root for details.
r...@karl-desktop:/home/karl#
@ Chris:
From Bug #420093:
http://launchpadlibrarian.net/30961326/valgrind.log
valgrind log obtained by running:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --log-file=valgrind.log gksu nautilus
Although, it might just be getting
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
Andrew - thanks, but that only shows a problem in gksu. It doesn't show
any issue in nautilus unfortunately.
--
karmic nautilus fails to run as root
https://bugs.launchpad.net/bugs/420841
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Typing sudo su and then nautilus worked only once. Now I get this
output:
nel...@nechus:~$ sudo su
r...@nechus:/home/nelson# nautilus
(nautilus:10239): Unique-DBus-WARNING **: Error while sending message:
Did not receive a reply. Possible causes include: the remote application
did not send a
Same issue here. The suggested commands are not working.
--
karmic nautilus fails to run as root
https://bugs.launchpad.net/bugs/420841
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs mailing list
This seems to have something to do with libnautilus-brasero-extension.
Possibly related:
Bug #420093
Bug #419565
Bug #419092
--
karmic nautilus fails to run as root
https://bugs.launchpad.net/bugs/420841
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Changed in: nautilus (Ubuntu)
Importance: Undecided = Medium
--
karmic nautilus fails to run as root
https://bugs.launchpad.net/bugs/420841
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/30954891/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/30954892/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/30954893/Disassembly.txt
** Attachment
** Package changed: nautilus (Ubuntu) = brasero (Ubuntu)
--
karmic nautilus fails to run as root
https://bugs.launchpad.net/bugs/420841
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in ubuntu.
--
desktop-bugs mailing list
** Changed in: brasero (Ubuntu)
Status: New = Confirmed
--
karmic nautilus fails to run as root
https://bugs.launchpad.net/bugs/420841
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in ubuntu.
--
desktop-bugs mailing
I get this message when I try to open Nautilus with root privileges in
Karmic:
nel...@nechus:~$ sudo nautilus
** Message: Initializing gksu extension...
** (nautilus:4275): WARNING **: No marshaller for signature of signal
'UploadFinished'
** (nautilus:4275): WARNING **: No marshaller for
I restarted my system and ran 'gksudo nautilus'. It ran fine once, but after
closing it and trying again, I also get a segfault. Backtrace attached
Also, note that the sudo su, nautilus method also produces a craah.
** Attachment added: gdb-nautilus.txt
22 matches
Mail list logo
