Version-Release number of selected component: driconf-0.9.1-20.fc20 Additional info: reporter: libreport-2.1.11 cmdline: /usr/bin/python /usr/bin/driconf --help dso_list: pygtk2-2.24.0-8.fc20.x86_64 executable: /usr/bin/driconf kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: #1 <module> in /usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py:40 #2 <module> in /usr/lib/python2.7/site-packages/driconf.py:26 #3 <module> in /usr/bin/driconf:26
Created attachment 850865 [details] File: backtrace
Created attachment 850866 [details] File: environ
What were you doing when this happened? Just running it? Does it happen everytime?
yes, I run xorg and mesa packages from rawhide and all the times i run driconf i get: driconf Traceback (most recent call last): File "/usr/bin/driconf", line 26, in <module> import driconf File "/usr/lib/python2.7/site-packages/driconf.py", line 26, in <module> import gtk File "/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 40, in <module> from gtk import _gtk ImportError: /lib64/libEGL.so.1: undefined symbol: wl_proxy_marshal_constructor
What does: rpm -V mesa-libEGL output?
rpm -V mesa-libEGL outputs nothing: [sheepdestroyer@localhost ~]$ rpm -V mesa-libEGL [sheepdestroyer@localhost ~]$ [sheepdestroyer@localhost ~]$ yum info mesa-libEGL Installed Packages Name : mesa-libEGL Arch : i686 Version : 10.0.2 Release : 1.20140110.fc21 Size : 167 k Repo : installed Name : mesa-libEGL Arch : x86_64 Version : 10.0.2 Release : 1.20140110.fc21 Size : 168 k Repo : installed From repo : updates
Wait, you are mixing rawhide packages into a f20 system? Likely this is due to something else in the graphics stack changed in rawhide, but not yet in f20, quite possibly wayland related.
driconf available in rawhide is Name : driconf Arch : noarch Version : 0.9.1 Release : 20.fc20 It appears that it's the same than base fedora 20's driconf and has not been recompiled against xserver 1.15/mesa 10 Beside compiling myself, using rawhide packages are the only way to get access to new xserver/mesa. Shouldn't rawhide's driconf be kept in sync?
(In reply to sheepdestroyer from comment #8) > driconf available in rawhide is > Name : driconf > Arch : noarch > Version : 0.9.1 > Release : 20.fc20 > > It appears that it's the same than base fedora 20's driconf and has not > been recompiled against xserver 1.15/mesa 10 It doesn't need to be. ;) There's been no upstream update and it's a python program, so it doesn't need to relink to new libraries. > Beside compiling myself, using rawhide packages are the only way to get > access to new xserver/mesa. Shouldn't rawhide's driconf be kept in sync? It's not out of sync. It works just fine here. I think you are running into a case of something you are pulling from rawhide not fully showing it's dependency tree, so it doesn't pull that in and you get this unknown symbol. If you can boot one of the rawhide daily images and duplicate this there I would be interested to hear it...
I did boot Fedora-Live-Desktop-x86_64-rawhide-20140118 and had no problem running driconf. sorry for the erroneous bug report, it's quite a bummer it would not run on my system.
Sorry. If I knew what lib/package was out of sync I would tell you. ;(
Hit this problem myself trying to use PlayOnLinux to launch a wine program. The tell is wl_proxy_marshal_constructor. A bit of googling shows that this is a Wayland related symbol. To get things running, I installed wayland and llvm, and updated libwayland-client, all from Rawhide.