Re: f17 x86_64 :: yumex broken

2012-06-24 Thread TASAKA Mamoru
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

Re: On a side note (Was: f17 x86_64 :: yumex broken)

2012-06-24 Thread Ed Greshko
On 06/24/2012 06:37 PM, Frank Murphy wrote: > On 24/06/12 11:08, Ed Greshko wrote: > . >> >> Your message caused me to investigate and I found that setting >> mail.strict_threading >> to "false" from the default "true" will also use the "Subject" when making >> threading >> decisions. >> >> Thank

Re: On a side note (Was: f17 x86_64 :: yumex broken)

2012-06-24 Thread Frank Murphy
On 24/06/12 11:08, Ed Greshko wrote: . Your message caused me to investigate and I found that setting mail.strict_threading to "false" from the default "true" will also use the "Subject" when making threading decisions. Thanks. How to? bring forgetful these modern days. -- Regards, F

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Adrian Sevcenco
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

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Adrian Sevcenco
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 befor

Re: On a side note (Was: f17 x86_64 :: yumex broken)

2012-06-24 Thread Ed Greshko
On 06/24/2012 05:51 PM, Ed Greshko wrote: > It seems that others have been following "strange" procedures these days and > breaking > threading. It messes things up. But, I'll survive. :-) Good news for me. Your message caused me to investigate and I found that setting mail.strict_th

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Ed Greshko
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.

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Adrian Sevcenco
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

Re: On a side note (Was: f17 x86_64 :: yumex broken)

2012-06-24 Thread Ed Greshko
On 06/24/2012 05:47 PM, Daniel wrote: > On 06/24/2012 02:22 AM, Ed Greshko wrote: > >> 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. > > I'm sorry to have induced this concern. I su

Re: On a side note (Was: f17 x86_64 :: yumex broken)

2012-06-24 Thread Daniel
On 06/24/2012 02:22 AM, Ed Greshko wrote: 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. I'm sorry to have induced this concern. I subscribe to the digest, but happened to look-in on

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Michael Schwendt
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 --roo

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Ed Greshko
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

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Daniel
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. -- users mailing list users@lists.fedoraproject.org To uns

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Ed Greshko
On 06/24/2012 04:44 PM, Adrian Sevcenco wrote: > then somewhere there is something wrong .. > > adrian@t420 : ~ $ rpm -qa | grep yumex > yumex-3.0.5-2.fc17.noarch > > adrian@t420 : ~ $ yumex > > ** (process:29224): WARNING **: Trying to register gtype 'GMountMountFlags' > as enum > when in fact it

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Adrian Sevcenco
On 06/24/12 11:33, Ed Greshko wrote: On 06/24/2012 04:30 PM, Adrian Sevcenco wrote: there is no supposition .. i started from root terminal and that's all.. and i am very sure that the error has nothing to do with the starting method .. OK But, when started as a normal user it works just

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Ed Greshko
On 06/24/2012 04:33 PM, Ed Greshko wrote: > On 06/24/2012 04:30 PM, Adrian Sevcenco wrote: >> there is no supposition .. i started from root terminal and that's all.. and >> i am >> very sure that the error has nothing to do with the starting method .. > OK > > But, when started as a normal us

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Ed Greshko
On 06/24/2012 04:30 PM, Adrian Sevcenco wrote: > there is no supposition .. i started from root terminal and that's all.. and > i am > very sure that the error has nothing to do with the starting method .. OK But, when started as a normal user it works just fine here. yumex-3.0.5-2.fc17.noa

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Adrian Sevcenco
On 06/24/12 11:18, Ed Greshko wrote: On 06/24/2012 03:24 PM, 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 Why are you doing this? You are already "root". Aren't you supposed to start "yumex" as a regular

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Adrian Sevcenco
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

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Ed Greshko
On 06/24/2012 03:24 PM, 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 Why are you doing this? You are already "root". Aren't you supposed to start "yumex" as a regular user and then simply enter the p

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Adrian Sevcenco
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

Re: f17 x86_64 :: yumex broken

2012-06-24 Thread Michael Schwendt
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/y

f17 x86_64 :: yumex broken

2012-06-24 Thread Adrian Sevcenco
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