Bug 819509 - gnome-system-log fails to run
gnome-system-log fails to run
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: gnome-system-log (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-07 09:01 EDT by Przemek Klosowski
Modified: 2012-05-18 21:56 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-05-18 21:56:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Przemek Klosowski 2012-05-07 09:01:28 EDT
Description of problem:
gnome-system-log fails to display anything, disappears without a trace.


Version-Release number of selected component (if applicable):
gnome-system-log-3.4.1-2.fc17.x86_64


How reproducible: every time


Steps to Reproduce:
1. run gnome-system-log from menus or command line
2. see nothing

  
Actual results:
When ran from Applications/System Tools/Log File Viewer menu, it shows 'Starting Log File Viewer' icon in the bottom bar for about 10 seconds, and disappears, without opening any windows. 

When run from the root shell prompt, it prints the message:

(logview:13781): gnome-system-log-CRITICAL **: Unable to parse arguments: Cannot open display: 

It is not a $DISPLAY problem because e.g. gnome-system-monitor command works fine (opens the monitor window, etc).
 

Expected results:
I believe that a window should appear displaying the system logs 


Additional info:
Comment 1 antonio montagnani 2012-05-07 09:29:26 EDT
if you open a terminal and you become root by su, then issue gnome-system-monitor, it works
Comment 2 Przemek Klosowski 2012-05-07 14:01:09 EDT
(In reply to comment #1)
> if you open a terminal and you become root by su, then issue
> gnome-system-monitor, it works

Yes, that's what I reported: gnome-system-monitor works but gnome-system-log (which is what this bug report is about) doesn't:

[root@przemek przemek]# gnome-system-log
  (logview:4748): gnome-system-log-CRITICAL **: Unable to parse arguments: Cannot 
  open display: 
  <immediately returns to shell prompt...>
[root@przemek przemek]# gnome-system-monitor 
  <shows correct monitor window and works, in general>
[root@przemek przemek]#
Comment 3 Matthias Clasen 2012-05-07 14:16:28 EDT
what kind of desktop environment is this running in ?
do you get a password prompt when running gnome-system-log as regular user ?
do you have /usr/share/polkit-1/actions/org.gnome.logview.policy ?
does "pkexec sh" bring up a password dialog ?
Comment 4 antonio montagnani 2012-05-07 14:58:00 EDT
it had to be read as gnome-system-log

Running Gnome
Yes I get passwd prompt
Yes I have /usr/share/polkit-1/actions/org.gnome.logview.policy
Yes pkexec sh brings up a password dialog

Same on fresh installation and upgraded installation
Comment 5 antonio montagnani 2012-05-07 15:04:30 EDT
it had to be read as gnome-system-log

Running Gnome
Yes I get passwd prompt
Yes I have /usr/share/polkit-1/actions/org.gnome.logview.policy
Yes pkexec sh brings up a password dialog

Same on fresh installation and upgraded installation
Comment 6 Przemek Klosowski 2012-05-07 17:03:42 EDT
(In reply to comment #3)
> what kind of desktop environment is this running in ?
Gnome

> do you get a password prompt when running gnome-system-log as regular user ?
Yes, and after authentication it actually runs!!!!!!!!!!!!!!!!
still, doesn't work off the menu or from the root shell.

> do you have /usr/share/polkit-1/actions/org.gnome.logview.policy ?
Yes, it is owned by gnome-system-log-3.4.1-2.fc17.x86_64 and rpm --verify confirms it's unchanged (only /usr/bin/logview is changed due to prelinking)

> does "pkexec sh" bring up a password dialog ?
Yes, and when I give the user password, it runs the root shell for me.
Comment 7 Matthias Clasen 2012-05-18 21:56:51 EDT
This was tracked down to a problem with the way gnome-shell launches applications:
http://git.gnome.org/browse/gnome-shell/commit/?id=02e4726ba62659b4cdeca5274d76ba8f14edb768

Will be fixed in the next gnome-shell release.

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