[showfoto] unable to resize images (jpeg)

I recently realized that showfoto crashes each time I try to resize a jpeg/jpg file (same for png).
I uninstalled reinstalled, but it seems it is linked to a library or a module but I don’t know which.

Any clues ?

I got this error message just before it crashes…

[21231:21231:0506/154420.190905:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180

I didn’t know we were using chromium (???).

You did not unveil where you found that error. It just falls out of the blue sky for people reading this.

And when you have a GUI program that breaks, then try to start it from a terminal, so that when it breaks, you get hopefully some error message or the like.

I followed the requests here: 436695 – [opensuse 15.2] unable to resize images (all types)

it seems that there is no more way to use showfoto with the “root” account… suddenly…

I am not quite sure what you are talking about the “root” account. What has root do to with this. You are having a problem about an end-user GUI program.

Not here – Leap 15.2 – Showfoto Version 7.1.0 – “root” Konsole session – resized a 20 M Pixel JPEG file to a 2.7 M Pixel JPEG file –

  • No crash …

But, I copied the files from my photographic library to ‘/root/Pictures/’ …
Also –


/root/Pictures # showfoto 
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
/root/Pictures # 
/root/Pictures # file _DQ_3348-001.jpg
_DQ_3348-001.jpg: JPEG image data, JFIF standard 1.01, aspect ratio, density 1x1, segment length 16, Exif Standard: [TIFF image data, little-endian, direntries=20], baseline, precision 8, 2007x1338, frames 3
 /root/Pictures # file _DQ_3348.JPG
_DQ_3348.JPG: JPEG image data, Exif standard: [TIFF image data, little-endian, direntries=16, description=                               , manufacturer=SIGMA, model=sd Quattro, orientation=upper-left, xresolution=286, yresolution=294, resolutionunit=2, software=SIGMA sd Quattro ver1.13.0.2487, datetime=2021:04:29 17:29:10], baseline, precision 8, 5424x3616, frames 3
 /root/Pictures # 

Which begs the question –

  • Just exactly, what did you do?

@soundlord:

Why on earth do you need to use the user “root” to edit photographs?

  • No normal human being would ever do that …
  • Editing digital photographs is basically the same as the work which used to be done in a Darkroom with chemicals and photographic equipment – nobody ever needed “system administrator rights
    ” to perform that work …

And, also, what was the OP’s perceived need to use showfoto as the root user?

Edit: @dcurtisfra Ah! you asked whilst I was typing.

I should have remembered earlier. But this thread https://forums.opensuse.org/showthread.php/546277-Knetwork-manager-non-root-user-can-t-access-network-selection-system-tray shows in post #6 that the OP runs everything as root. Not only that, but he is so convinced that that is normal behaviour, that he does not even mentions this when asking for help. Every time the helpers here have to find out by themselves why all things he shows are so strange (and often scary).

So, I am out here and I hope to remember next time to skip his threads before spoiling time on them.

soundlord,

please let me explain in some simple words why working as root is always a very bad idea.
In nearly all systems/permission setups (also on Windows), there exists a “Parent-Child” concept. When you start a media player like VLC, it becomes your child process and inherits your permissions. Without that, the media player wont be able to access your videos.
If you start Firefox as an (non-root) user, and the Javascript of the website says: Delete the harddrive!
The response would be: “Error - no permissions for that”
And now think about what is possible if you are root for daily purposes. :open_mouth:

And indeed, those kind of setup, (Default user = Admin user) was the main reason for so endless many successful windows attacks.

@soundlord:

The Linux Standard – which reflects the UNIX® Standard – defines the following relationship between a system’s users and, the system itself –

  • Users (human) are just that – human users …
  • The (Linux/UNIX®) system as such, permits (human) users to use the machine but, in general, users can only use the machine – they are not allowed to meddle with system activities and, possibly, break the system – that’s the reason why, there’s a special class of users who are the system administrators …
  • This is the strict separation of system and users which is a feature of systems based on UNIX® – Linux, MacOS, BSD, Android, etc., etc. …

Your pseudonym suggests that, the system you’re using is possibly being used for applications which process music –

  • Yes, in the past, some music applications required that, they be run as the user “root” – I seem to recall that, MIDI applications commonly needed to be run as the user “root” …

But, AFAICS, with current Linux audio processing applications, this need has disappeared.

  • And, if a music application needs strict timing constraints then, please consider using the “kernel-preempt” package – CONFIG_PREEMPT is supported …

Reference: <https://wiki.linuxaudio.org/wiki/system_configuration>

Greetings everyone… I know that “rooting” Linux is not a good idea, I know that’s risky… (relatively)
I just don’t like sudoing each command line and/or switch user/root to do administrative stuff.

My computer is not exposed to the “bad guys network side” and I have a redudant backup of the critical files I work on, included the system settings I use. All that stuff is automated.
I got also redundant copies on the clouds.

I will isolate the issue to users creating a test user and see if it works better.

The issue is isolated to user’s… there is no more way to use showfoto in “root” account.
It works using the “test user”…

I will uninstall showfoto definetly then and use Gimp untill they decide to prevent “root account” to use it :{

  • Despite Sunday …*

Then you need to understand Linux groups –

User Group Comments
adm adm Administrative special privileges
  • If
    , openSUSE or SUSE – the user group “wheel” – and, uncomment some lines in ‘/etc/sudoers’ – and, possibly, drop a file into ‘/etc/sudoers.d/’ –

## Uncomment to allow members of group wheel to execute any command
# %wheel ALL=(ALL) ALL

## Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL

## Read drop-in files from /etc/sudoers.d
## (the '#' here does not indicate a comment)
#includedir /etc/sudoers.d

Rather than removing the comments in ‘/etc/sudoers’ – the edits will be removed whenever the package “sudo” is either patched or updated – drop a «C source» ASCII text file into ‘/etc/sudoers.d/’ containing –


## Uncomment to allow members of group wheel to execute any command
%wheel ALL=(ALL) ALL

## Same thing without a password
%wheel ALL=(ALL) NOPASSWD: ALL

  • As the ‘/etc/sudoers’ file comments are telling the world – «the ‘#’ here does not indicate a comment
    » – the drop-in file in ‘/etc/sudoers.d/’ will be read … - The drop-in file shall have the same access permissions and ownership as ‘/etc/sudoers’ –

 # file /etc/sudoers
/etc/sudoers: C source, ASCII text
 # l /etc/sudoers
-r--r----- 1 root root 3391 20. Apr 16:14 /etc/sudoers
 # l -d /etc/sudoers.d
drwxr-x--- 2 root root 4096 20. Apr 16:14 /etc/sudoers.d/
 #