Eddie G.O'Connor Jr-I wrote:
While I don't consider myself on the level of most of the people here,
I also am not stupid enough to think my "blanket statement" will be
wonderfully and miraculously accepted by all.
The issue wasn't whether a blanket statement would be accepted by all.
The iss
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
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
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
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
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
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
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
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
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
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
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
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
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
On Sat, 23 Jun 2012 16:45:25 -0400, Tom Horsley wrote:
> When I genned my fedora 17 system, I installed ntp,
> enabled the ntpd.service and disabled the chronyd.service.
>
> Yet today, I just noticed in the logs that chronyd
> is running and ntpd is not running (and, no doubt, other
> systems on
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
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
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
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.
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
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
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
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
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
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
I've never looked at or modified any files in /etc/pam.d
till I happened to notice some *.rpmnew files in there.
Now I see a bunch of files that are symlinks to
other files with -ac on the end, but also have
versions that are *.rpmnew.
rpm queries show that the pam rpm owns the
files without the
On Sat, 2012-06-23 at 19:05 +0100, John Horne wrote:
> Hello,
>
> I have installed F17 onto my home PC today, and somewhere along the way
> changed I seem to have changed the KDE panel background. It is now
> somewhat transparent, which means that when the display background
> changes (I have it s
On Sun, 2012-06-24 at 12:17 +0100, John Horne wrote:
> On Sat, 2012-06-23 at 19:05 +0100, John Horne wrote:
> > Hello,
> >
> > I have installed F17 onto my home PC today, and somewhere along the way
> > changed I seem to have changed the KDE panel background. It is now
> > somewhat transparent, wh
what is this in dmesg?
why is "--log-prefix" here loggd instead the --log-prefix from whatever rule it
was?
--log-prefixIN=eth1 OUT= MAC=00:50:8d:b5:cc:de:00:01:5c:24:68:01:08:00
SRC=120.89.73.74 DST=84.113.45.179 LEN=60
TOS=0x00 PREC=0x00 TTL=51 ID=58168 DF PROTO=TCP SPT=39903 DPT=19 WINDOW=584
On Sun, 24 Jun 2012 07:14:03 -0400, Tom Horsley wrote:
> I've never looked at or modified any files in /etc/pam.d
> till I happened to notice some *.rpmnew files in there.
>
> Now I see a bunch of files that are symlinks to
> other files with -ac on the end, but also have
> versions that are *.rp
On Sun, 24 Jun 2012 14:03:08 +0200, Reindl Harald wrote:
> what is this in dmesg?
> why is "--log-prefix" here loggd instead the --log-prefix from whatever rule
> it was?
>
> --log-prefixIN=eth1 OUT= MAC=00:50:8d:b5:cc:de:00:01:5c:24:68:01:08:00
> SRC=120.89.73.74 DST=84.113.45.179 LEN=60
> TOS
On Sun, 24 Jun 2012 14:11:01 +0200
Michael Schwendt wrote:
> The -ac files from authconfig are those which to use by symlinking them.
So the correct response to this nonsense is "do nothing" :-).
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
h
Hi,
I just ran a yum update on F16 which included the 3.4.2-1.fc16.x86_64
kernel.
All the CIFS mounts failed, error 22 (Invalid Argument). In 'messages'
I found a series of msgs like this:
Jun 24 05:34:36 mel kernel: [ 3989.465216] CIFS: Unknown mount option
"UID=500"
Removing UID=500 from an
Am 24.06.2012 14:15, schrieb Michael Schwendt:
> On Sun, 24 Jun 2012 14:03:08 +0200, Reindl Harald wrote:
>
>> what is this in dmesg?
>> why is "--log-prefix" here loggd instead the --log-prefix from whatever rule
>> it was?
>>
>> --log-prefixIN=eth1 OUT= MAC=00:50:8d:b5:cc:de:00:01:5c:24:68:01
On 06/23/2012 02:54 PM, Adrian Sevcenco wrote:
> Hi! I just installed f17 on my thinkpad t420 and clean up my home directory
> of all configurations .. i have disable selinux and chown -R all my files ...
> the problem is that at start of kde i have a crash of Plasma Desktop Shell
> followed at
I recently used preupgrade from f15 to f16. The installation (x86_64)
was new at f12. The upgrade was largely troublefree but booting has
gone from grub to grub2 - and it did not carry over elevator=deadline to
specify the kernel scheduler, or the timeout value.
Now, if I try to run system-c
On Sun, 24 Jun 2012 15:25:54 +0100, John Pilkington wrote:
> I recently used preupgrade from f15 to f16. The installation (x86_64)
> was new at f12. The upgrade was largely troublefree but booting has
> gone from grub to grub2 - and it did not carry over elevator=deadline to
> specify the ker
Well then I stand corrected! I once again apologize, and will keep mt
"pop-ins" as minimal and brief as possible! Thank you for clearing this
up for me! LoL!
EGO II
On 06/24/2012 03:02 AM, Daniel wrote:
Eddie G.O'Connor Jr-I wrote:
While I don't consider myself on the level of most of the
Greetings,
Apologies, but I'm arriving late to this discussion.
I've just gone through a re-install (F15->F16) and now an upgrade
(F16->F17).
I've encountered the same problem that has been lenghthily discussed. I
also see that it impacts the upgrade of gtk2, cairo, and several other
packa
Hi,
After running a yum update on F16 which included the 3.4.2-1.fc16.x86_64
kernel, and rebooting to that kernel, all the CIFS mounts failed with
error 22 (Invalid Argument).
In '/var/log/messages I found a series of entries like this:
Jun 24 05:34:36 mel kernel: [ 3989.465216] CIFS: Unknow
On Fri, Jun 22, 2012 at 10:11 PM, Ed Greshko wrote:
> On 06/23/2012 12:19 PM, Richard Vickery wrote:
> > This is awesome Ed: Did it work like this before as well, and I was
> just ignorant
> > of it? Now all the commands are readable, which for me is better as it
> seemed as if
> > they were som
On Sun, 24 Jun 2012 11:55:28 -0400 (EDT), Max Pyziur wrote:
>
> Greetings,
>
> Apologies, but I'm arriving late to this discussion.
>
> I've just gone through a re-install (F15->F16) and now an upgrade
> (F16->F17).
>
> I've encountered the same problem that has been lenghthily discussed. I
On Sat, Jun 23, 2012 at 6:12 AM, Eddie G.O'Connor Jr-I wrote:
>
> On 06/22/2012 08:47 PM, Tim wrote:
>
>> On Fri, 2012-06-22 at 14:28 +0200, suvayu ali wrote:
>>
>>> I don't know the details but if this makes all Flash sites start
>>> working reliably on Linux, I would be willing to put up with w
On 06/25/2012 12:55 AM, Richard Vickery wrote:
> Bottom and top posting rules between posting here and the Developers list may
> get
> confusing
I'm sure you can handle it Does the Developer's list have rules about
trimming
unnecessary cruft? :-) :-)
--
Never be afraid to laugh at yourse
On Fri, Jun 22, 2012 at 7:47 AM, Fernando Cassia wrote:
> Suddenly after a reboot I find between 50-60% of my CPU used. I load
> process manager and find tracker-store and tracker-extract being the main
> culprits, with spikes of 90% of cpu usage.
>
> This is a dual-core AMD Opteron server with 2
On Sun, Jun 24, 2012 at 1:27 PM, Ed Greshko wrote:
> On 06/25/2012 12:55 AM, Richard Vickery wrote:
> > Bottom and top posting rules between posting here and the Developers
> list may get
> > confusing
>
> I'm sure you can handle it Does the Developer's list have rules about
> trimming
> unn
I can't make gnome-rdp work not can I get remmina to work either. Please
give me some information concerning this problem.
I work on computers remotely and so this is a major concern for me.
Thanking you in advance for all your help.
--
All things are workable but don't all things work. Prov.3:5
On 06/25/2012 08:58 AM, Lawrence Graves wrote:
> I can't make gnome-rdp work not can I get remmina to work either. Please give
> me
> some information concerning this problem.
> I work on computers remotely and so this is a major concern for me. Thanking
> you in
> advance for all your help.
F1
On 06/24/2012 07:09 PM, Ed Greshko wrote:
On 06/25/2012 08:58 AM, Lawrence Graves wrote:
I can't make gnome-rdp work not can I get remmina to work either. Please give me
some information concerning this problem.
I work on computers remotely and so this is a major concern for me. Thanking
you i
I made some adjustments with the firewall and I am still receiving the
message/ ERROR: gettaddrinfo: name or server unknown
--
All things are workable but don't all things work. Prov.3:5 & 6
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https:/
On 06/25/2012 09:16 AM, Lawrence Graves wrote:
> I am using tigervnc-server and what adjustments have to be made to the
> firewall?
By default the vncservers start listening on port 5901 for display :1.
So, you need to open port 5901 on the server side to accept connections.
--
Never be afrai
On 06/24/2012 07:26 PM, Ed Greshko wrote:
On 06/25/2012 09:16 AM, Lawrence Graves wrote:
I am using tigervnc-server and what adjustments have to be made to the firewall?
By default the vncservers start listening on port 5901 for display :1.
So, you need to open port 5901 on the server side to
On 06/25/2012 09:50 AM, Lawrence Graves wrote:
> I gave you the wrong information about the server. I am using RDP and all the
> ports
> of open.
I don't use xrdp. However, I believe it listens on port 3389.
You can test to make sure your server is running simply by doing something like
this.
fc16 with latest updates.
Pinging my gateway:
$ ping 192.168.42.129
ping: icmp open socket: Operation not permitted
Now as root:
# ping 192.168.42.129
PING 192.168.42.129 (192.168.42.129) 56(84) bytes of data.
64 bytes from 192.168.42.129: icmp_req=1 ttl=64 time=3.53 ms
64 bytes from 192.168.42
On 06/25/2012 01:21 PM, JD wrote:
> fc16 with latest updates.
>
> Pinging my gateway:
> $ ping 192.168.42.129
> ping: icmp open socket: Operation not permitted
>
> Now as root:
>
> # ping 192.168.42.129
> PING 192.168.42.129 (192.168.42.129) 56(84) bytes of data.
> 64 bytes from 192.168.42.129: icm
On 06/25/2012 12:21 AM, JD wrote:
fc16 with latest updates.
Pinging my gateway:
$ ping 192.168.42.129
ping: icmp open socket: Operation not permitted
Now as root:
# ping 192.168.42.129
PING 192.168.42.129 (192.168.42.129) 56(84) bytes of data.
64 bytes from 192.168.42.129: icmp_req=1 ttl=64 ti
On 06/25/2012 02:22 PM, Ed Greshko wrote:
> I forget what black on a red background means.
OK Now I rememberor at least relearned.
Looking at LS_COLORS it is the ca=30;41 which gives black letters on red
background.
Which equates to "capability".
Sodo you have something like this
On 06/25/2012 02:42 PM, Ed Greshko wrote:
> OK Now I rememberor at least relearned.
>
> Looking at LS_COLORS it is the ca=30;41 which gives black letters on red
> background.
> Which equates to "capability".
>
> Sodo you have something like this?
>
> egreshko@f17 tmp]$ lsattr /bin/p
On 06/25/2012 12:22 AM, Ed Greshko wrote:
On 06/25/2012 01:21 PM, JD wrote:
fc16 with latest updates.
Pinging my gateway:
$ ping 192.168.42.129
ping: icmp open socket: Operation not permitted
Now as root:
# ping 192.168.42.129
PING 192.168.42.129 (192.168.42.129) 56(84) bytes of data.
64 byte
On 06/25/2012 12:24 AM, Larry wrote:
On
06/25/2012 12:21 AM, JD wrote:
fc16 with latest updates.
Pinging my gateway:
$ ping 192.168.42.129
ping: icmp open socket: Operation not permitted
On 06/25/2012 02:54 PM, JD wrote:
> On 06/25/2012 12:22 AM, Ed Greshko wrote:
>> On 06/25/2012 01:21 PM, JD wrote:
>>> fc16 with latest updates.
>>>
>>> Pinging my gateway:
>>> $ ping 192.168.42.129
>>> ping: icmp open socket: Operation not permitted
>>>
>>> Now as root:
>>>
>>> # ping 192.168.42.1
On 06/25/2012 02:47 PM, Ed Greshko wrote:
> Actually.strike all that. Or at least most of it. Need to
> rethink...
OK *NOW* I do have it
The "correct" command is "getcap"
root@f17 tmp]# getcap /bin/ping
/bin/ping = cap_net_raw+ep
If nothing is returned from getcap then
62 matches
Mail list logo
