Bug 1484754 - sealert -s / -S tracebacks when display is set to VNC server
Summary: sealert -s / -S tracebacks when display is set to VNC server
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: setroubleshoot
Version: 26
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Lautrbach
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-24 09:47 UTC by Milos Malik
Modified: 2018-05-29 11:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1574434 (view as bug list)
Environment:
Last Closed: 2018-05-29 11:33:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Milos Malik 2017-08-24 09:47:10 UTC
Description of problem:

Version-Release number of selected component (if applicable):
setroubleshoot-3.3.12-1.fc26.x86_64
setroubleshoot-plugins-3.3.7-1.fc26.noarch
setroubleshoot-server-3.3.12-1.fc26.x86_64
tigervnc-license-1.8.0-1.fc26.noarch
tigervnc-server-1.8.0-1.fc26.x86_64
tigervnc-server-minimal-1.8.0-1.fc26.x86_64

How reproducible:
* always

Steps to Reproduce:
# mkdir .vnc
# echo "P4ss${RANDOM}w0rD" > ~/.vnc/passwd
# chmod 600 .vnc/passwd 
# vncserver 

New 'removed:1 (root)' desktop is removed:1

Creating default startup script /root/.vnc/xstartup
Creating default config /root/.vnc/config
Starting applications specified in /root/.vnc/xstartup
Log file is /root/.vnc/removed:1.log

# export DISPLAY=removed:1
# LANG=de_DE sealert -s
Unable to init server: Could not connect: Connection refused
Unable to init server: Verbindung ist gescheitert:Connection refused
Opps, sealert hit an error!

Traceback (most recent call last):
  File "/usr/bin/sealert", line 659, in <module>
    run_as_dbus_service(username)
  File "/usr/bin/sealert", line 118, in run_as_dbus_service
    app = SEAlert(user, dbus_service.presentation_manager, watch_setroubleshootd=True)
  File "/usr/bin/sealert", line 351, in __init__
    self.browser = BrowserApplet(self.username, self.alert_client, domain=domain)
  File "/usr/lib/python3.6/site-packages/setroubleshoot/browser.py", line 179, in __init__
    size = Gdk.Screen().get_default().get_monitor_geometry(0)
AttributeError: 'NoneType' object has no attribute 'get_monitor_geometry'

# ps -efZ | grep setr
system_u:system_r:setroubleshootd_t:s0-s0:c0.c1023 setroub+ 1730 1  0 04:41 ? 00:00:00 /usr/bin/python3 -Es /usr/sbin/setroubleshootd -f
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 root 21740 919  0 05:35 pts/0 00:00:00 grep --color=auto setr
# ls -Z /run/setroubleshoot/
system_u:object_r:setroubleshoot_var_run_t:s0 setroubleshoot_server
# ls -lZ /run/setroubleshoot/
total 0
srw-rw-rw-. 1 setroubleshoot setroubleshoot system_u:object_r:setroubleshoot_var_run_t:s0 0 Aug 24 04:41 setroubleshoot_server
# LANG=de_DE sealert -S
Unable to init server: Could not connect: Connection refused
Unable to init server: Verbindung ist gescheitert:Connection refused
Opps, sealert hit an error!

Traceback (most recent call last):
  File "/usr/bin/sealert", line 668, in <module>
    run_app(username)
  File "/usr/bin/sealert", line 95, in run_app
    app = SEAlert(user)
  File "/usr/bin/sealert", line 351, in __init__
    self.browser = BrowserApplet(self.username, self.alert_client, domain=domain)
  File "/usr/lib/python3.6/site-packages/setroubleshoot/browser.py", line 179, in __init__
    size = Gdk.Screen().get_default().get_monitor_geometry(0)
AttributeError: 'NoneType' object has no attribute 'get_monitor_geometry'
# 

Actual results:
* tracebacks

Expected results:
* no tracebacks

Additional information:
* the same traceback appears when I run: vncserver -geometry 1024x768

Comment 1 Milos Malik 2017-08-24 09:56:46 UTC
The LANG setting is not important, the traceback appears even if default LANG setting is used.

sealert -s / -S works fine when executed inside an SSH terminal to the same machine (ssh -X ... used of course).

Comment 2 Fedora End Of Life 2018-05-03 08:09:22 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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.

Comment 3 Fedora End Of Life 2018-05-29 11:33:43 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.


Note You need to log in before you can comment on or make changes to this bug.