Bug 1394599

Created attachment 1220196 [details]
File: backtrace

Created attachment 1220197 [details]
File: cgroup

Created attachment 1220198 [details]
File: core_backtrace

Created attachment 1220201 [details]
File: dso_list

Created attachment 1220202 [details]
File: environ

Created attachment 1220204 [details]
File: exploitable

Created attachment 1220206 [details]
File: limits

Created attachment 1220209 [details]
File: maps

Created attachment 1220211 [details]
File: mountinfo

Created attachment 1220213 [details]
File: namespaces

Created attachment 1220215 [details]
File: open_fds

Created attachment 1220218 [details]
File: proc_pid_status

Created attachment 1220220 [details]
File: var_log_messages

*** Bug 1397633 has been marked as a duplicate of this bug. ***

I upgraded to F25 last week. vino was not working.

Today, I noticed in my logwatch the following lines:

--------------------- Kernel Begin ------------------------ 

 
 WARNING:  Segmentation Faults in these executables
    vino-server :  9 Time(s)
 
 WARNING:  General Protection Faults in these executables
    traps: vino-server :  1 Time(s)
 
 WARNING:  Trap int3 in these executables
    traps: gnome-shell :  1 Time(s)
    traps: gnome-terminal- :  1 Time(s)
 
 WARNING:  Kernel Errors Present
    ACPI Error: Method parse/ex ...:  12 Time(s)
    ACPI Error: [DSSP] Namespac ...:  12 Time(s)

Most recent logwatch lines:

    vino-server.service: Failed with result 'core-dump'.: 5 Time(s)
    vino-server.service: Failed with result 'start-limit-hit'.: 1 Time(s)
    vino-server.service: Main process exited, code=dumped, status=11/SEGV: 5 Time(s)
    vino-server.service: Service hold-off time over, scheduling restart.: 5 Time(s)
    vino-server.service: Start request repeated too quickly.: 1 Time(s)
    vino-server.service: Unit entered failed state.: 6 Time(s)
    vncserver@:1.service: Control process exited, code=exited status=217: 1 Time(s)
    vncserver@:1.service: Failed at step USER spawning /usr/bin/vncserver: No such process: 2 Time(s)
    vncserver@:1.service: Failed with result 'exit-code'.: 1 Time(s)
    vncserver@:1.service: Unit entered failed state.: 1 Time(s)

Here is another system - similar logwatch. This system has newer hardware than the previous Comment #16 (does not seem to try /usr/bin/vncserver)

   vino-server.service: Failed with result 'core-dump'.: 5 Time(s)
    vino-server.service: Failed with result 'start-limit-hit'.: 1 Time(s)
    vino-server.service: Main process exited, code=dumped, status=11/SEGV: 5 Time(s)
    vino-server.service: Service hold-off time over, scheduling restart.: 5 Time(s)
    vino-server.service: Start request repeated too quickly.: 1 Time(s)
    vino-server.service: Unit entered failed state.: 6 Time(s)
    vncserver@:0.service: Failed with result 'exit-code'.: 1 Time(s)
    vncserver@:0.service: Main process exited, code=exited, status=1/FAILURE: 1 Time(s)
    vncserver@:0.service: Unit entered failed state.: 1 Time(s)
    vncserver@:1.service: Failed with result 'exit-code'.: 1 Time(s)
    vncserver@:1.service: Main process exited, code=exited, status=1/FAILURE: 1 Time(s)
    vncserver@:1.service: Unit entered failed state.: 1 Time(s)
    x11vnc.service: Failed with result 'exit-code'.: 1 Time(s)
    x11vnc.service: Main process exited, code=exited, status=1/FAILURE: 1 Time(s)
    x11vnc.service: Unit entered failed state.: 1 Time(s)

Here is logwatch fragment from a still newer hardware box:

    vino-server.service: Failed with result 'core-dump'.: 5 Time(s)
    vino-server.service: Failed with result 'start-limit-hit'.: 1 Time(s)
    vino-server.service: Main process exited, code=dumped, status=11/SEGV: 5 Time(s)
    vino-server.service: Service hold-off time over, scheduling restart.: 5 Time(s)
    vino-server.service: Start request repeated too quickly.: 1 Time(s)
    vino-server.service: Unit entered failed state.: 6 Time(s)
    xdg-permission-store.service: Failed with result 'exit-code'.: 1 Time(s)
    xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE: 1 Time(s)
    xdg-permission-store.service: Unit entered failed state.: 1 Time(s)
 
These lines on all systems seem to come from my most recent update:

   sudo dnf update

   sudo shutdown -r now

The problem is known, it doesn't need any further debugging, I believe.

(In reply to Kamil Páral from comment #19)
> The problem is known, it doesn't need any further debugging, I believe.

Knowing what the problem is - - and fixing the problem are two different things!

Yes. If you're willing to fix this, patches are definitely welcome. Be sure to provide them in the upstream bug report in that case, thanks.

*** Bug 1401992 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Automatic upgrade from Fedora 24 to 25

Faults logged before desktop has booted up.

reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/libexec/vino-server
crash_function: XQueryExtension
executable:     /usr/libexec/vino-server
global_pid:     3133
kernel:         4.9.9-200.fc25.x86_64
package:        vino-3.22.0-1.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         vino-server killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            0

Similar problem has been detected:

`CRASHES UPON BOOTUP.	


reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/libexec/vino-server
crash_function: XQueryExtension
executable:     /usr/libexec/vino-server
global_pid:     4346
kernel:         4.9.10-200.fc25.x86_64
package:        vino-3.22.0-1.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         vino-server killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            0

Similar problem has been detected:

program start on it's own and the crash appears in the reporter

reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/libexec/vino-server
crash_function: XQueryExtension
executable:     /usr/libexec/vino-server
global_pid:     6130
kernel:         4.9.10-200.fc25.x86_64
package:        vino-3.22.0-1.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         vino-server killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            0

Similar problem has been detected:

It popped up at login.

reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/libexec/vino-server
crash_function: _XSend
executable:     /usr/libexec/vino-server
global_pid:     1958
kernel:         4.9.13-200.fc25.x86_64
package:        vino-3.22.0-1.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         vino-server killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

The bottom line for me, afaict, is that vino-server auto-launches (i.e. with Screen Sharing "On") and runs fine under GNOME/Xorg, but crashes immediately when logging into a GNOME/Wayland session. Presumably this is what others are seeing on their installs as well? Willing to provide additional troubleshooting info (and possibly patches), if it helps.

It appears that some update within the last few months completely removed the screen sharing option from the gnome-control-center sharing sub-panel when running under Wayland. I suppose that's <em>one way</em> to eliminate the problem...

Vino-server runs fine under GNOME/Xorg, but segfaults and dumps core when I attempt to run /usr/libexec/vino-server from gnome-terminal in a GNOME/Wayland session. What are users supposed to do for remote desktop access to their GNOME/Wayland desktop? What's the recommended workaround? Tigervnc-server? X11vnc?

(In reply to Gabriel M. Elder from comment #28)

> What are users supposed to do for remote desktop
> access to their GNOME/Wayland desktop? What's the recommended workaround?

I have my screens, mice, keyboards on one Desktop..

If you need a more practical solution, pitch Wayland in the wastebasket and go back to X.

(In reply to Gabriel M. Elder from comment #28)
> What are users supposed to do for remote desktop
> access to their GNOME/Wayland desktop?

It's not possible at the moment. Use X11 session if you need that.

Process info: I'm going to keep this in common bugs, because the crash still occurs if you configured remote screen under X11 and then log in with Wayland. The removed option from UI helps to prevent people from triggering this easily, but does not completely avoid it.

I still see vino server crashed on a regular basis.
I'm running CentOS 7.3 and have all updates. I often
access VNC from the native screen sharing on Mac OS X.
A couple times a week I'll be connected from my Mac to my CentOS X
session and it will not only crash vino, but my session as well,
causing a logout; I must return to my CentOS system and log back in.

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.