On 06/24/2012 04:57 PM, Daniel wrote:
> As I understand it, this is a known bug, and whether it appears is a function of
> whether one did a clean install or effected an upgrade.
>
> And (as I understand it) it can be repaired either by downgrading yumex or by
> altering one's path.

Well.... In the bugzilla I see...

how does your path look like ?

echo $PATH

If you have /bin before /usr/bin in your path you will get this issue

And my $PATH is...

/usr/lib/qt-3.3/bin:/usr/lib/ccache:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/egreshko/.local/bin:/home/egreshko/bin

So, I *do* have /bin before /usr/bin and I don't have the issue.

This was a fresh install of F17.... So, maybe that only holds for upgrades when /bin
was not a link as it is now.

However, to verify....

explicitly calling /bin/yumex does fail.


On a side note.... I notice that your replies don't have a "References" header.
Hope this isn't a new "feature" of TB 13. It is breaking treads on TB 12.





--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On Sun, 24 Jun 2012 11:14:17 +0300, Adrian Sevcenco wrote:

> On 06/24/12 10:57, Michael Schwendt wrote:
> > On Sun, 24 Jun 2012 10:24:38 +0300, Adrian Sevcenco wrote:
> >
> >> Hi! It seems that yumex in broken in f17..
> >> i try to start it and i have this :
> >>
> >> [root@t420 bin]# yumex --root
> >
> >> GError: Failed to open file '/bin/yumex.glade': No such file or directory
> >>
> >> i put a symlink from /usr/share/yumex/yumex.glade in /bin and in the
> >
> >> i have did :
> >> ln -s /usr/share/pixmaps/yumex /gfx
> >>
> >> but still the same error .. is this going to be fixed or yumex is dead
> >> in f17?
> >
> >
> > ???
> >
> > You are not supposed to mess with your installation by adding lots
> > of strange symlinks. Why don't you examine the package _as is_ and
> > simply report any problem?
>
> then just read the first part of mail ...

I've seen your other replies, too, so just some comments on this one:

Reading the first part of the mail doesn't change a thing. You've run into
an error condition, and you should have stopped right there, tried a
downgrade, and should have reported the problem in bugzilla (or searched
bugzilla for existing tickets about it). Searching for a Test Update
would have also been an idea and mentioning that you've found none.

> the fact that /bin/yumex.glade is not found ...

An obvious error, but why spend time on trying to make it worse with
symlinks? If at all, you could have tried to find out _why_ it searches
for the .glade file in /bin which would be a very strange location for
that file.

> is it something particular to my system?

That's a completely different question compared with your first message:

| but still the same error .. is this going to be fixed
| or yumex is dead in f17?

The tone of that message clearly indicates that you believed it to be a
bug in yumex, and you showed lack of patience, since asking whether yumex
would be "dead in f17" sounds much as if the problem has bugged you for
more than the last few minutes before your mail.

Asking whether anyone can reproduce the problem is not a bad idea.
However, imagine another user answered that he couldn't reproduce the
problem. What does that tell about your system? Not much, except that
you've got a system where yumex fails. Why does it fail? Only you could
conclude whether that is because you've damaged your system, e.g. with
symlinks. Or because yumex find an environment/installation where it
doesn't work because of a bug in the software. Then somebody would need
to investigate, too.

All too often, somebody confirms a bug on a mailing-list, but nobody
takes the time to report it.

--
Fedora release 17 (Beefy Miracle) - Linux 3.4.3-1.fc17.x86_64
loadavg: 0.93 0.31 0.22
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 06/24/12 11:56, Ed Greshko wrote:

Strange....

I did an "strace -e trace=file -o trace yumex"

And the reference to yumex.glade was....

[egreshko@f17 ~]$ grep glade trace
open("/usr/share/yumex/yumex.glade", O_RDONLY|O_LARGEFILE) = 3

I suppose there could be a difference between i686 and x86_64......

yeap :
adrian@t420 : ~ $ grep glade trace
open("/bin/yumex.glade", O_RDONLY) = -1 ENOENT (No such file or
directory)


thank for the hint .. at this moment i am so frustrated by f17 that i
missed good old means of investigation..
from the bug report it seems that are more than one path problem with
this.. well, i will wait for the fix


Thanks for looking into it!
Adrian

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 06/24/2012 05:54 PM, Adrian Sevcenco wrote:
> yeap :
> adrian@t420 : ~ $ grep glade trace
> open("/bin/yumex.glade", O_RDONLY) = -1 ENOENT (No such file or directory)
>
> thank for the hint .. at this moment i am so frustrated by f17 that i missed
> good old means of investigation..
> from the bug report it seems that are more than one path problem with this.. well,
> i will wait for the fix
>
> Thanks for looking into it!

Welcome....

But, I think Daniel has the answer. Try calling it as /usr/bin/yumex .....

Is yours a fresh f17 install or upgrade?

--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 06/24/12 12:22, Michael Schwendt wrote:

The tone of that message clearly indicates that you believed it to be a
bug in yumex, and you showed lack of patience, since asking whether yumex
would be "dead in f17" sounds much as if the problem has bugged you for
more than the last few minutes before your mail.
yeah, sorry about my overall tone! the thing is that kde is also
non-functional (bug reports sent automatically) for me and on one hand i
congratulate myself for not re-installing my desktops and OTOH i feel
sorry for installing f17 on my laptop..
So, i apologize for my tone and i will try to show more patience and to
follow proper procedures in order to not make too much noise..


Thanks,
Adrian

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 06/24/12 12:56, Ed Greshko wrote:

On 06/24/2012 05:54 PM, Adrian Sevcenco wrote:

yeap :
adrian@t420 : ~ $ grep glade trace
open("/bin/yumex.glade", O_RDONLY) = -1 ENOENT (No such file or directory)

thank for the hint .. at this moment i am so frustrated by f17 that i missed
good old means of investigation..
from the bug report it seems that are more than one path problem with this.. well,
i will wait for the fix

Thanks for looking into it!


Welcome....

But, I think Daniel has the answer. Try calling it as /usr/bin/yumex .....

hmm, it seems that there is a difference ...
the problem is that i need to be root to call it like this or else :

adrian@t420 : ~ $ /usr/bin/yumex

** (process:30334): WARNING **: Trying to register gtype
'GMountMountFlags' as enum when in fact it is of type 'GFlags'


** (process:30334): WARNING **: Trying to register gtype
'GDriveStartFlags' as enum when in fact it is of type 'GFlags'


** (process:30334): WARNING **: Trying to register gtype
'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'
/usr/lib/python2.7/site-packages/guihelpers/__init__.py:256: GtkWarning:
gtk_scrolled_window_add(): cannot add non scrollable widget use
gtk_scrolled_window_add_with_viewport() instead

self.add_from_file(filename)
ERROR:dbus.proxies:Introspect error on
:1.1:/org/freedesktop/NetworkManager: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 3
matched rules; type="method_call", sender=":1.128" (uid=1000 pid=30334
comm="/usr/bin/python -tt /usr/bin/yumex ")
interface="org.freedesktop.DBus.Introspectable" member="Introspect"
error name="(unset)" requested_reply="0" destination=":1.1" (uid=0
pid=593 comm="/usr/sbin/NetworkManager --no-daemon ")
org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 5
matched rules; type="method_call", sender=":1.128" (uid=1000 pid=30334
comm="/usr/bin/python -tt /usr/bin/yumex ") interface="(unset)"
member="GetDevices" error name="(unset)" requested_reply="0"
destination=":1.1" (uid=0 pid=593 comm="/usr/sbin/NetworkManager
--no-daemon ")
ERROR:dbus.proxies:Introspect error on
:1.1:/org/freedesktop/NetworkManager: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 3
matched rules; type="method_call", sender=":1.128" (uid=1000 pid=30334
comm="/usr/bin/python -tt /usr/bin/yumex ")
interface="org.freedesktop.DBus.Introspectable" member="Introspect"
error name="(unset)" requested_reply="0" destination=":1.1" (uid=0
pid=593 comm="/usr/sbin/NetworkManager --no-daemon ")
org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 5
matched rules; type="method_call", sender=":1.128" (uid=1000 pid=30334
comm="/usr/bin/python -tt /usr/bin/yumex ") interface="(unset)"
member="GetDevices" error name="(unset)" requested_reply="0"
destination=":1.1" (uid=0 pid=593 comm="/usr/sbin/NetworkManager
--no-daemon ")

13:15:00 : INFO - Can't detect the network connection state
INFO:yumex.verbose:Can't detect the network connection state
ERROR:dbus.proxies:Introspect error on
:1.1:/org/freedesktop/NetworkManager: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 3
matched rules; type="method_call", sender=":1.128" (uid=1000 pid=30334
comm="/usr/bin/python -tt /usr/bin/yumex ")
interface="org.freedesktop.DBus.Introspectable" member="Introspect"
error name="(unset)" requested_reply="0" destination=":1.1" (uid=0
pid=593 comm="/usr/sbin/NetworkManager --no-daemon ")
org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 5
matched rules; type="method_call", sender=":1.128" (uid=1000 pid=30334
comm="/usr/bin/python -tt /usr/bin/yumex ") interface="(unset)"
member="GetDevices" error name="(unset)" requested_reply="0"
destination=":1.1" (uid=0 pid=593 comm="/usr/sbin/NetworkManager
--no-daemon ")

13:15:00 : INFO - Starting yum child process
INFO:yumex.verbose:Starting yum child process
13:15:00 : INFO - YUM: Error executing command as another user: Not
authorized
INFO:yumex.verbose:YUM: Error executing command as another user: Not
authorized

13:15:02 : ERROR - ERROR: Fatal Error : backend-not-running
ERROR:yumex.verbose:ERROR: Fatal Error : backend-not-running
13:15:02 : ERROR - ERROR: backend not running as expected (yumex will close)
ERROR:yumex.verbose:ERROR: backend not running as expected (yumex will
close)

13:15:02 : INFO - yum backend process is ended
INFO:yumex.verbose:yum backend process is ended
13:15:02 : INFO - yum backend process is ended
INFO:yumex.verbose:yum backend process is ended

but as root is ok .. so thank for info!!


Is yours a fresh f17 install or upgrade?

fresh install

Thanks!
Adrian

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Adrian Sevcenco wrote, at 06/24/2012 04:24 PM +9:00:

Hi! It seems that yumex in broken in f17..
i try to start it and i have this :

[root@t420 bin]# yumex --root

** (process:28197): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'

** (process:28197): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'

** (process:28197): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'
Traceback (most recent call last):

File "/bin/yumex", line 42, in <module>

app = YumexApplication(backend)

File "/usr/lib/python2.7/site-packages/yumexgui/__init__.py", line 203, in __init__
Controller.__init__(self, BUILDER_FILE , 'main', domain='yumex')

File "/usr/lib/python2.7/site-packages/guihelpers/__init__.py", line 278, in __init__
self.ui = UI(filename, rootname, domain)

File "/usr/lib/python2.7/site-packages/guihelpers/__init__.py", line 256, in __init__
self.add_from_file(filename)

GError: Failed to open file '/bin/yumex.glade': No such file or directory



Well, as Michael said, please report this issue against yumex on bugzilla.

Although I am not the maintainer of yumex, from this backtrace it can easily be found
where to fix on yumex. This is actually the side effect of F17 usrmove.

Regards,
Mamoru


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org