Bug 1401246

Summary: Update Failure: python2-pyxdg-0.25-10.fc25.noarch
Product: [Fedora] Fedora Reporter: Geo <Geonote3>
Component: pyxdgAssignee: Tom "spot" Callaway <tcallawa>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: Geonote3, jpmahowald, sindrepb, tcallawa
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-21 13:27:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Geo 2016-12-03 23:31:15 UTC
Description of problem: Recommended update (python2-pyxdg-0.25-10.fc25.noarch) will not install via Yum/DNF.


Version-Release number of selected component (if applicable):


How reproducible:
Every day for the past week.

Steps to Reproduce:
1.Tried 12 times, including after rebooting and on different days.
2.Searched for info on forum and bugzilla
3.Attempted to install source by method of download/open with Yum.

Actual results:

This error message appears every time: "Error(s) in building transactionupdate : python2-pyxdg-0.25-10.fc25.noarch"

Expected results:


Additional info:

Comment 1 Geo 2016-12-03 23:35:11 UTC
I am having trouble saving any changes made in Alacarte. "OK" option remains grey on every attempt to add new item or edit. Attempts to run Alacarte as SU via CLI result in the following error messages:

** (alacarte:7318): WARNING **: Could not open X display
/usr/lib/python2.7/site-packages/Alacarte/MainWindow.py:22: PyGIWarning: GMenu was imported without specifying a version first. Use gi.require_version('GMenu', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, GdkPixbuf, Gdk, GMenu

(alacarte:7318): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed

(alacarte:7318): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
[root@localhost socrates]#

Comment 2 Geo 2016-12-03 23:36:45 UTC
My installed OS is Fedora 25 Design Suite with Gnome Desktop.

Comment 3 Geo 2016-12-04 06:28:15 UTC
The update python2-pyxdg-0.25-10.fc25.noarch was successfully installed through Yum/DNF by first uninstalling the earlier version that came with f25 Design Suite, then installing the updated version recommended by the repository. 

The update of pyxdg, however, has not had any noticeable affect on the above noted problem in Alacarte menus. I determined that the Alacarte problem exists in all three versions of the desktop environment: Gnome, Gnome-Classic and Gnome X-org.

Comment 4 Tom "spot" Callaway 2016-12-07 17:20:37 UTC
I don't think this is a pyxdg issue. Let's tease this apart a bit.

1) If you're using Fedora 25 with GNOME, you're using wayland. Wayland does not permit graphical applications to run as root (you can't launch them via su or sudo). See: https://bugzilla.redhat.com/show_bug.cgi?id=1274451 for discussion and ways to open up permissions (they also cause potential security risks).

2) Running it as a non-root user works fine for me. I get these warnings (but they are all non-fatal):

/usr/lib/python2.7/site-packages/Alacarte/MainWindow.py:22: PyGIWarning: GMenu was imported without specifying a version first. Use gi.require_version('GMenu', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, GdkPixbuf, Gdk, GMenu

(alacarte:1311): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed

(alacarte:1311): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed

When I add a new item, I put in "test" and then "/bin/bash" in the command field. When I finish typing a valid path to a binary, the OK button becomes active. Are you putting in a full path to an existing binary in the command field?

Comment 5 Tom "spot" Callaway 2017-03-21 13:27:04 UTC
Not enough info here to troubleshoot. Closing. Please feel free to reopen if you can reproduce.