The new version is in Ubuntu now
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1452084
Title:
Segmentation
As far as I understand, Fix Committed is the wrong status for the Ubuntu
task since the fix is not committed into Ubuntu.
I'm waiting for someone to rebuild the Files Nightly Flatpak (the last
build was 2018-03-18 08:53:15 +) since I don't really want to build
master by hand.
** Also affects:
The upstream commit is
https://gitlab.gnome.org/GNOME/nautilus/commit/0d24b6a1
Could you confirm if the fix is working?
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
(well, supposedly fixed by a commit, will test in the Files Nightly
Flatpak soon to see if I can reproduce the bug post-commit)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1452084
T
This is fixed upstream (I'm assuming this means it'll get into GNOME
3.30 and Ubuntu 18.10)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1452084
Title:
Segmentation fault whilst op
Upstream: 'Having nautilus-dropbox installed is a shortcut to
reproducing the crash. Otherwise, you can trigger it by copying/moving
the two files together somewhere.'
They've reopened the bug.
( I wouldn't be commenting this if bug 1745210 were fixed ;) )
--
You received this bug notification
As per the upstream bug:
The bug doesn't exist in the Files 3.24.1 Flatpak.
Also I got a newer stacktrace here: https://paste.ubuntu.com/p/R8bvFbbw77/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launch
@ads2 we are still waiting to confirm they tested this on trash://
though :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1452084
Title:
Segmentation fault whilst opening Rubbi
Upstream says their latest stable and master works fine (see previous
link), so this is an Ubuntu-specific bug
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1452084
Title:
Segmentat
* bug 1745210
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1452084
Title:
Segmentation fault whilst opening Rubbish Bin/ trash://
Status in nautilus package in Ubuntu:
Confirmed
(Btw I can confirm this bug is reproducible in Ubuntu 17.10)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1452084
Title:
Segmentation fault whilst opening Rubbish Bin/ trash://
St
I've reported the bug here:
https://gitlab.gnome.org/GNOME/nautilus/issues/289
Proper tracking is blocked by bug 1603679
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to na
Thanks, the issue is an upstream one, it would be nice if somebody could
send the bug to the developers of the software by following the
instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscr
Just discovered Nautilus will crash wherever these two files are placed
together! Attached .tar.gz with a folder that upon opening should crash
Nautilus. Hopefully the symlinks will be preserved in the archive!
** Attachment added: "A folder that when extracted and opened in Nautilus,
should recr
Result! XD There were indeed some (now broken after being moved to
trash) symlinks in there! Moving two of them out of the trash stopped
the crash! The symlinks that caused the SIGSEGV, were also relative-
based ones, I've posted the result of ls -la below.
lrwxrwxrwx 1 jonathan jonathan1
not sure, do you have symlinks in there? maybe a looping one?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1452084
Title:
Segmentation fault whilst opening Rubbish Bin/ trash://
S
Can confirm gvfs-ls trash:/// works fine producing the output of all the
files in the trash:// location.
I have another account on the system with plenty of files in that
trash:// works perfectly fine for. Guest mode trash:// also works
perfectly fine.
The program still crashes with SIGSEGV (__GI
weird, it seems that it keeps getting change events ... does "gvfs-ls
trash:///" works? does it work if you uninstall python-nautilus? do you
get the same issue in a guest session?
** Changed in: nautilus (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you
Please also find attached the backtrace obtained from GDB using the
instructions at https://wiki.ubuntu.com/Backtrace
** Attachment added: "GDB Backtrace of Nautilus"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+attachment/4393231/+files/gdb-nautilus.tar.gz
--
You receive
Please find attached the Valgrind log of `_SLICE=always-malloc G_DEBUG
=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-
callers=40 --log-file=valgrind.log $(which nautilus) trash://`
** Attachment added: "valgrind-logs-nautilus.tar.gz"
https://bugs.launchpad.net/ubuntu/+sourc
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 y
Just ran again with the source directory for libio enabled in gdb and the line
that's going wrong is as follows:
463 f->_IO_write_ptr = __mempcpy (f->_IO_write_ptr, s, count);
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
22 matches
Mail list logo
