Possible duplicates with bug #1607919
Possible duplicates with bug #1607919
Viestialustana vianhallintajärjestelmät
nautilus crashed with SIGSEGV in nautilus_list_model_get_all_iters_for_file() when trying to open a password-protected 7z archive
== Steps to reproduce ==
1. Create a password protected 7z archive: `echo hello >hello.txt; 7z a hello.7z hello.txt -ppassword`
2. Left-click the archive in Nautilus
== What happens ==
Nautilus shows an empty window, and together with gnome-shell they eat up the CPU until you close the Nautilus window. Alternatively, a crash report prompt appears.
== What I expect to happen ==
Preferably to prompt for a password and then open the archive contents. At the very least to not eat all the CPU, and inform the user that Nautilus is incapable of handling this file format.
== Other info ==
I don’t have Dropbox installed unlike in bug #1734891.
Upstream issue: https://gitlab.gnome.org/GNOME/nautilus/issues/51
Red Hat issue: https://bugzilla.redhat.com/show_bug.cgi?id=1499401
Haven’t seen this since upgrading to 18.04, so it appears to be fixed
Haven’t seen this since upgrading to 18.04, and can’t reproduce it following the instructions anymore either, so it appears to be fixed.
This is currently still present in Bionic’s Shotwell 0.28.1-0ubuntu1
This is currently still present in Bionic’s Shotwell 0.28.1-0ubuntu1.
gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
Had been AFK for a couple of hours with the display turned off, came back and turned it on when this occurred.
I’ve redirected Gnome Shell related log entries away from my syslog so I’m attaching the separate log here.
mp3cut makes output file executable
== Steps to reproduce ==
$ wget -q ’https://upload.wikimedia.org/wikipedia/commons/a/a5/Uncle_Josh_and_the_Insurance_Company_-_Cal_Stewart.mp3’ && mp3cut -o test.mp3 Uncle_Josh_and_the_Insurance_Company_-_Cal_Stewart.mp3 &>/dev/null && ls -l test.mp3
== Expected result ==
-rw-r–r– 1 jani jani 2433848 maali 26 15:45 test.mp3
== Actual result ==
-rwxr–r– 1 jani jani 2433848 maali 26 15:45 test.mp3
Looks like you can still enter ’Print’ in dconf-editor for a custom action
Looks like you can still enter ’Print’ in dconf-editor for a custom action (/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/customN/binding), so at least there’s that.
PrintScreen is now bound to Gnome Settings Daemon, which is used to take screenshots instead of gnome-screenshot
It seems that PrintScreen is now bound to Gnome Settings Daemon, which is used to take screenshots instead of gnome-screenshot. Keyboard settings (in Gnome settings) still has a screenshot shortcuts section in the keyboard shortcut settings, but those too now only trigger Gnome Settings Daemon’s screenshot feature, not gnome-screenshot.
What’s worse, disabling those shortcuts does not allow for remapping PrintScreen back to gnome-screenshot using a custom shortcut, as pressing PrintScreen in the shortcut selector window still just triggers the GSD ’blink’ instead of registering PrintScreen as the new shortcut key for the custom command. Only the screenshot section’s pre-defined actions allow for PrintScreen to be grabbed. (At least that’s what it does here.)
When the screenshot shortcuts are disabled, nothing is apparently saved anywhere despite the blink effect. The ”Save a screenshot to Pictures” shortcut has to be defined for the screenshots to actually get saved, and then they will be unconditionally saved to $XDG_PICTURES_DIR: https://bugzilla.gnome.org/show_bug.cgi?id=699642
Flood of ”peer a.b.c.d:port is not from a LAN” in syslog
After upgrading from Xenial to Bionic, my syslog is being spammed by minissdpd. From today’s syslog going back three hours:
15.05 jani@saegusa:~$ grep ”is not from a LAN” /var/log/syslog | tail
Mar 23 15:03:30 saegusa minissdpd[1990]: peer 192.168.1.4:39280 is not from a LAN
Mar 23 15:03:33 saegusa minissdpd[1990]: message repeated 3 times: [ peer 192.168.1.4:39280 is not from a LAN]
Mar 23 15:03:36 saegusa minissdpd[1990]: peer 192.168.1.10:13206 is not from a LAN
Mar 23 15:03:36 saegusa minissdpd[1990]: peer 192.168.1.10:13206 is not from a LAN
Mar 23 15:03:51 saegusa minissdpd[1990]: peer 192.168.1.1:32769 is not from a LAN
Mar 23 15:04:21 saegusa minissdpd[1990]: message repeated 39 times: [ peer 192.168.1.1:32769 is not from a LAN]
Mar 23 15:04:29 saegusa minissdpd[1990]: peer 192.168.1.10:13206 is not from a LAN
Mar 23 15:04:29 saegusa minissdpd[1990]: peer 192.168.1.10:13206 is not from a LAN
Mar 23 15:04:50 saegusa minissdpd[1990]: peer 192.168.1.1:32769 is not from a LAN
Mar 23 15:04:51 saegusa minissdpd[1990]: message repeated 19 times: [ peer 192.168.1.1:32769 is not from a LAN]
15.05 jani@saegusa:~$ grep -c ”is not from a LAN” /var/log/syslog
1623
192.168.1.0 is my LAN.
According to the upstream report [1], specifying an interface should get rid of the ”not from a LAN” messages, and I can confirm that adding ”-i eth1” to the value of MiniSSDPd_OTHER_OPTIONS in /etc/default/minissdpd does just that. I don’t know how good a solution adding a fixed interface is though, I’d imagine switching to (e.g.) a wifi interface on a system with multiple interfaces would cause the message flood to reappear.
*[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890584
Possible upstream issues
Possible upstream issues: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842015 -> https://dev.gnupg.org/T2818 (-> https://dev.gnupg.org/T2843#)