[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr
Can everyone clear their gnome-shell extensions and check this isn't the cause of the issue? If so, I think we need a better way of handling extension crashes. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1736011 Title: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1452084] Re: Segmentation fault whilst opening Rubbish Bin/ trash://
@ads2 we are still waiting to confirm they tested this on trash:// though :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1452084 Title: Segmentation fault whilst opening Rubbish Bin/ trash:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1550824] Re: Reproducable hard lock on ISO mount
Just confirmed, the ISO concerned mounts fine when it's on an ext4 file- system, so highly suspecting the issue it to with ZFS handling on the part of gnome-disk-utility) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1550824 Title: Reproducable hard lock on ISO mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1550824/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1550824] [NEW] Reproducable hard lock on ISO mount
Public bug reported: Release:15.10 (amd64) When opening an ISO I have recently downloaded, using the "Open With > Disk Image Mounter" feature of Ubuntu it causes a hard system lock. (Not even pressing REISUB works) This is not a freak one off occurrence, as the same thing will happen again when opening the same file. Sadly, nothing is logged either before the crash in the system log, so it's hard to find out what's specifically causing this. My hunch is either: 1) Something in the ISO that doesn't get handled properly (less likely) 2) The fact the file-system where the ISO is held is using ZFS (installed from the Ubuntu repos) and something in gnome-disk-utility doesn't handle this properly. (I find more likely as ZFS on Ubuntu is still fairly experimental) Anyone care to share some experience or hunches in how to go figure out what's causing this horrendous bug? I'm going to try and place the file on an ext4 partition and see what that does, but I don't really want to keep on risking hard-locking the system if I don't have to! Thanks! ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1550824 Title: Reproducable hard lock on ISO mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1550824/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1497592] [NEW] Jayatana causes java.awt.IllegalComponentStateException in NetBeans
Public bug reported: java.awt.IllegalComponentStateException: component must be showing on the screen to determine its location https://netbeans.org/bugzilla/show_bug.cgi?id=255249 Jayatana caused an exception in NetBeans. I'm reporting here because a stack trace is available for this Exception from two people and by default this is being sent to the NetBeans developers rather than the responsible Jayatana developer(s). I've personally had many problems with Jayatana, and I don't see why it's included with Ubuntu by default, when in it's current state, it's so clearly incompatible with so many existing Java programs! ** Affects: jayatana Importance: Unknown Status: Unknown ** Affects: jayatana (Ubuntu) Importance: Undecided Status: New ** Tags: java netbeans ** Bug watch added: netbeans.org/bugzilla/ #255249 http://netbeans.org/bugzilla/show_bug.cgi?id=255249 ** Also affects: jayatana via http://netbeans.org/bugzilla/show_bug.cgi?id=255249 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to jayatana in Ubuntu. https://bugs.launchpad.net/bugs/1497592 Title: Jayatana causes java.awt.IllegalComponentStateException in NetBeans To manage notifications about this bug go to: https://bugs.launchpad.net/jayatana/+bug/1497592/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1452084] Re: Segmentation fault whilst opening Rubbish Bin/ trash://
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 recreate this bug! https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+attachment/4404339/+files/bug1452084.tar.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1452084 Title: Segmentation fault whilst opening Rubbish Bin/ trash:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1452084] Re: Segmentation fault whilst opening Rubbish Bin/ trash://
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 jonathan13 Apr 8 05:04 ToggleRGB.c - ToggleRGB.ino lrwxrwxrwx 1 jonathan jonathan11 Apr 8 05:05 ToggleRGB.ino - ToggleRGB.c There is indeed a circular reference created here is there not as they're now referencing each other? These files weren't originally ever together at the same time until they were deleted, and then this problem occurred when they were moved into the trash together. I wasn't aware Nautilus would try to resolve the symlinks in some way, but surely crashing when this situation occurs is still undesirable behaviour? Many thanks for helping work out what was going wrong though :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1452084 Title: Segmentation fault whilst opening Rubbish Bin/ trash:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1452084] Re: Segmentation fault whilst opening Rubbish Bin/ trash://
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__IO_default_xsputn (f=0x7f7ff600, data=optimised out, n=38) at genops.c:463) with python-nautilus uninstalled and pruged out (I did not restart the system, but I ensured that nautilus was completely killed before I re- attempted the test) I'm guessing there's probably something in my trash:// that's triggering this right? Any particular file types I should look for? Interestingly opening `nautilus ~/.local/share/Trash/files` causes a sefault too! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1452084 Title: Segmentation fault whilst opening Rubbish Bin/ trash:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1452084] Re: Segmentation fault whilst opening Rubbish Bin/ trash://
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/+source/nautilus/+bug/1452084/+attachment/4393220/+files/valgrind-logs-nautilus.tar.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1452084 Title: Segmentation fault whilst opening Rubbish Bin/ trash:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1452084] Re: Segmentation fault whilst opening Rubbish Bin/ trash://
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 received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1452084 Title: Segmentation fault whilst opening Rubbish Bin/ trash:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1452084] [NEW] Segmentation fault whilst opening Rubbish Bin/ trash://
Public bug reported: Package version 1:3.14.2-0ubuntu9 from http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages Ubuntu 15.04 amd64 on an i5-4670K CPU Hi, I'm currently getting a consistent SIGSEGV from Nautilus when attempting to open the rubbish bin. This happens whether I click the bookmark on the left or instantaneously if I run `nautilus trash://`. The crash occurs before the icons have fully loaded, but a second after the rubbish bin is selected. I installed the debug symbols for nautilus and ran with gdb and got the following output: (gdb) run Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. (nautilus:21736): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed (nautilus:21736): GLib-GObject-WARNING **: invalid (NULL) pointer instance (nautilus:21736): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed [Thread 0x77f8ba00 (LWP 21736) exited] [Inferior 1 (process 21736) exited normally] (gdb) run Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. nautilus-wipe-Message: Initializing [New Thread 0x7fffe9017700 (LWP 22649)] [Thread 0x7fffe9017700 (LWP 22649) exited] [New Thread 0x7fffc1347700 (LWP 22680)] [New Thread 0x7fffe35f1700 (LWP 22651)] [New Thread 0x7fffe3fff700 (LWP 22650)] [New Thread 0x7fffe9818700 (LWP 22648)] Program received signal SIGSEGV, Segmentation fault. 0x7372332e in __GI__IO_default_xsputn (f=0x7f7ff5f0, data=0x50e080, n=6) at genops.c:447 447 genops.c: No such file or directory. I can provide more info if needed as I can easily reproduce the bug. I know a little about using gdb as well, but may need a bit of guidance as I'm no hardened C programmer. Thanks! ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1452084 Title: Segmentation fault whilst opening Rubbish Bin/ trash:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1452084] Re: Segmentation fault whilst opening Rubbish Bin/ trash://
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 Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1452084 Title: Segmentation fault whilst opening Rubbish Bin/ trash:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
