I cannot clean my Trashbin
by Antonio M
Once again, I deleted files from my home folder, and when I open Trash
and I want to clean I can't do anything....Trashbin clean button is
grayed!!! but what is funny (that it is not true, I am a little bit
annoyed...) that .Trash folder is empty!!!!!
I will not file any bug. (I am tired of back and forward bugs)
--
Antonio Montagnani
Skype : antoniomontag
16 years, 2 months
Only other in login menu
by Antonio M
I filed this bug against recent gdm:
Bug 432919: Only Other in login menu
--
Antonio Montagnani
Skype : antoniomontag
16 years, 2 months
selinux now causing trouble with seamonkey
by Antonio Olivares
Dear all,
In addition to the bug filed
https://bugzilla.redhat.com/show_bug.cgi?id=432198
selinux now is causing trouble with seamonkey.
I deleted the ~/.mozilla/ directory and started from
scratch. So the argument about the plugins will not
work now :)
Am I the only one seeing this?
I feel kind of bad about complaining that selinux is
doing this, but it did not happen before and now it
does, both with firefox and with seamonkey.
Here's the message
Summary:
SELinux is preventing seamonkey-bin from making the
program stack executable.
Detailed Description:
The seamonkey-bin application attempted to make its
stack executable. This is a
potential security problem. This should never ever be
necessary. Stack memory is
not executable on most OSes these days and this will
not change. Executable
stack memory is one of the biggest security problems.
An execstack error might
in fact be most likely raised by malicious code.
Applications are sometimes
coded incorrectly and request this permission. The
SELinux Memory Protection
Tests
(http://people.redhat.com/drepper/selinux-mem.html)
web page explains how
to remove this requirement. If seamonkey-bin does not
work and you need it to
work, you can configure SELinux temporarily to allow
this access until the
application is fixed. Please file a bug report
(http://bugzilla.redhat.com/bugzilla/enter_bug.cgi)
against this package.
Allowing Access:
Sometimes a library is accidentally marked with the
execstack flag, if you find
a library with this flag you can clear it with the
execstack -c LIBRARY_PATH.
Then retry your application. If the app continues to
not work, you can turn the
flag back on with execstack -s LIBRARY_PATH.
Otherwise, if you trust
seamonkey-bin to run correctly, you can change the
context of the executable to
unconfined_execmem_exec_t. "chcon -t
unconfined_execmem_exec_t
'/usr/lib/seamonkey-1.1.8/seamonkey-bin'" You must
also change the default file
context files on the system in order to preserve them
even on a full relabel.
"semanage fcontext -a -t unconfined_execmem_exec_t
'/usr/lib/seamonkey-1.1.8/seamonkey-bin'"
The following command will allow this access:
chcon -t unconfined_execmem_exec_t
'/usr/lib/seamonkey-1.1.8/seamonkey-bin'
Additional Information:
Source Context
unconfined_u:unconfined_r:unconfined_t:SystemLow-
SystemHigh
Target Context
unconfined_u:unconfined_r:unconfined_t:SystemLow-
SystemHigh
Target Objects None [ process ]
Source firefox
Source Path
/usr/lib/firefox-3.0b3pre/firefox
Port <Unknown>
Host localhost
Source RPM Packages seamonkey-1.1.8-3.fc9
Target RPM Packages
Policy RPM
selinux-policy-3.2.7-1.fc9
Selinux Enabled True
Policy Type targeted
MLS Enabled True
Enforcing Mode Enforcing
Plugin Name allow_execstack
Host Name localhost
Platform Linux localhost
2.6.24.1-28.fc9 #1 SMP Sun Feb 10
17:27:37 EST 2008 i686
athlon
Alert Count 33
First Seen Fri 01 Feb 2008 05:08:54
PM CST
Last Seen Mon 11 Feb 2008 06:39:47
PM CST
Local ID
c4806f30-a6dc-43b0-8901-5531075795f7
Line Numbers
Raw Audit Messages
host=localhost type=AVC msg=audit(1202776787.936:31):
avc: denied { execstack } for pid=3481
comm="seamonkey-bin"
scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
tclass=process
host=localhost type=SYSCALL
msg=audit(1202776787.936:31): arch=40000003
syscall=125 success=no exit=-13 a0=bff2d000 a1=1000
a2=1000007 a3=fffff000 items=0 ppid=1 pid=3481
auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500
egid=500 sgid=500 fsgid=500 tty=(none)
comm="seamonkey-bin"
exe="/usr/lib/seamonkey-1.1.8/seamonkey-bin"
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
key=(null)
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
16 years, 2 months
ISO 216 vs U.S. paper Another "Mars Climate Orbiter" in the horizon
by "Jóhann B. Guðmundsson"
Asking tester to look into default printer settings
on a clean installed system both KDE and Gnome...
And report the findings back to the list so we/me
can gather the results and start filing RFE or bugs
based on the results so we get consistency in default printer settings in
applications.
Did a little research and notice this..
Note this is a clean system install running FC-8 updated with
updates-testing.
I've done no printer configuration what so ever.
Gedit is set to A4 <--- ISO 216
Gthumb is set to A4 <--- ISO 216
Gimp is set to Letter <--- U.S. paper
Firefox is set to Letter <--- U.S. paper
Thunderbird is set to Letter <--- U.S. paper
Open office defaults to Letter <--- U.S. paper
How to test...
When using or switched to locale for these country's The United States,
Canada, and in possible Mexico ( some parts of Mexico still uses US.Letter )
the printers default settings in the application should show US.Letter
or just Letter.
Any other country than the 2 ( possible 3 ) default printer settings
should show A4.
Turn off CUPS ( service cups stop )
Application that support printing and relie on cups don't need checking
Change the locale on the system.
Verify the locale from terminal has change/taken effect( locale )
Verify the printing option in the locale ( locale -ck LC_PAPER )
For Letter
height=279
width=216
For A4
height=297
width=210
Check if application that support printing have change accordingly..
Any application in which default printer settings does not change
accordingly gets flagged.
Report the applications you tested what locale was set and which ones
did not change the default paper size accordingly.
Best regards.
Johann B.
16 years, 2 months
F9Alpha Firefox Bookmarks (KDE4)
by Gerry Tool
Bookmarks behave unexpectedly in F9Alpha Firefox
{Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b3pre) Gecko/2008012200
Fedora/3.0b3pre-0.beta2.12.nightly20080121.fc9 Minefield/3.0b3pre}
I deleted the bookmarks.html file in my .mozilla/firefox/xxxxx.default
directory. I then tried to link to my standard bookmarks.html file on
a data partition. ln didn't complain, but when I did an ls in my
.mozilla/firefox/xxxxx.default directory, there was no link shown.
This has always worked before.
I then copied the file to that directory, reopened firefox, and the
bookmarks were still not present.IS this a bug, or a new feature of
Firefox 3?
Thanks.
Gerry
16 years, 2 months
Rawhide NFS load broken
by Chuck Forsberg WA7KGX
I downloaded the current Rawhide x86_64 tree and wrote
diskboot.img to a USB. It fails to locate the specified
directory. The server sees no incoming NFS request.
I tried an older diskboot.img using the identical entries
and it was able to authenticate a mount request for
the directory but complained that the files didn't match
the boot.
This is with an A8N and AMD chip.
Alpha 1 from DVD did load and run on this machine.
FWIW I could get neither neither diskboot.img to boot
with an Intel DG33BU motherboard.
--
Chuck Forsberg caf(a)omen.com www.omen.com 503-614-0430
Developer of Industrial ZMODEM(Tm) for Embedded Applications
Omen Technology Inc "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231 FAX 629-0665
16 years, 2 months
rawhide slow like a snail because of kernel debugging?
by Michael Schwendt
It has begun some weeks ago in rawhide and is the same in F9 Alpha,
which I installed from jigdo CD images.
The entire system is slow whatever it does. Loadavg jumps up
quickly. When running a simple yum update, loadavg goes above 6. User
processes don't seem to get as much cpu power as would be possible.
Windows take seconds to open. The GNOME Desktop is not as responsive
as in F8 either. Opening dialogs, clicking buttons, there seems to be
a penalty on everything. It's unbearable. Testing rawhide or F9 is no
fun at all. Why is this? I remember that during Fedora Core test
releases various kernel debugging features are enabled. Is this the
reason also this time? Has it become much more cpu power hungry than
e.g. with FC7 and older?
16 years, 2 months
Latest NetworkManager test update dying in F8
by Peter Robinson
Hi All,
I downloaded the latest NetworkManager as part of my updates (which
include testing) last night with the glee of it supporting 3G cards.
Now when I power up this morning NM is broken.
A "service NetworkManager status" reports NetworkManager dead but pid
file exists, the applet doesn't appear.
>From the /var/log/messages I get the output below from a couple of
tries. There's some complaints about selinux but its in permissive
mode so wouldn't actually be blocking.
Also when I try and start nm-applet manually it fails with some errors
about utms (3G card not connected currently) but I suspect its because
NM itself can't startup. Output from that even further below.
Cheers,
Peter
Feb 14 08:21:27 localhost NetworkManager: <info> starting...
Feb 14 08:21:27 localhost NetworkManager: <info> Found radio
killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch
Feb 14 08:21:27 localhost NetworkManager: <info> eth0: Device is
fully-supported using driver 'b44'.
Feb 14 08:21:27 localhost NetworkManager: <info> Now managing wired
Ethernet (802.3) device 'eth0'.
Feb 14 08:21:27 localhost NetworkManager: <info> Bringing down device eth0
Feb 14 08:21:27 localhost kernel: b44: eth0: powering down PHY
Feb 14 08:21:27 localhost avahi-daemon[2223]: Interface eth0.IPv4 no
longer relevant for mDNS.
Feb 14 08:21:27 localhost avahi-daemon[2223]: Leaving mDNS multicast
group on interface eth0.IPv4 with address 172.16.4.11.
Feb 14 08:21:27 localhost dhclient: receive_packet failed on eth0:
Network is down
Feb 14 08:21:27 localhost avahi-daemon[2223]: Withdrawing address
record for fe80::21a:4bff:fe5c:ce on eth0.
Feb 14 08:21:27 localhost avahi-daemon[2223]: Withdrawing address
record for 172.16.4.11 on eth0.
Feb 14 08:21:29 localhost NetworkManager: <info> Bringing up device eth0
Feb 14 08:21:30 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 14 08:21:30 localhost avahi-daemon[2223]: Joining mDNS multicast
group on interface eth0.IPv4 with address 172.16.4.11.
Feb 14 08:21:30 localhost avahi-daemon[2223]: New relevant interface
eth0.IPv4 for mDNS.
Feb 14 08:21:30 localhost avahi-daemon[2223]: Registering new address
record for 172.16.4.11 on eth0.IPv4.
Feb 14 08:21:30 localhost NetworkManager: <info> Deactivating device eth0.
Feb 14 08:21:30 localhost avahi-daemon[2223]: Withdrawing address
record for 172.16.4.11 on eth0.
Feb 14 08:21:30 localhost avahi-daemon[2223]: Leaving mDNS multicast
group on interface eth0.IPv4 with address 172.16.4.11.
Feb 14 08:21:30 localhost avahi-daemon[2223]: Interface eth0.IPv4 no
longer relevant for mDNS.
Feb 14 08:21:30 localhost NetworkManager: <info> (eth0): exported as
/org/freedesktop/Hal/devices/net_00_1a_4b_5c_00_ce
Feb 14 08:21:30 localhost NetworkManager: <info> wlan0: Device is
fully-supported using driver 'iwl3945'.
Feb 14 08:21:30 localhost NetworkManager: <info> wlan0: driver
supports SSID scans (scan_capa 0x01).
Feb 14 08:21:30 localhost NetworkManager: <info> Now managing
wireless (802.11) device 'wlan0'.
Feb 14 08:21:30 localhost NetworkManager: <info> Bringing down device wlan0
Feb 14 08:21:30 localhost kernel: ACPI: PCI interrupt for device
0000:10:00.0 disabled
Feb 14 08:21:30 localhost avahi-daemon[2223]: Withdrawing address
record for fe80::21b:77ff:fe76:b2a6 on wlan0.
Feb 14 08:21:32 localhost NetworkManager: <info> Bringing up device wlan0
Feb 14 08:21:32 localhost kernel: ACPI: PCI Interrupt 0000:10:00.0[A]
-> GSI 17 (level, low) -> IRQ 17
Feb 14 08:21:32 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 14 08:21:32 localhost NetworkManager: <info> Deactivating device wlan0.
Feb 14 08:21:32 localhost NetworkManager: <info> (wlan0): exported as
/org/freedesktop/Hal/devices/net_00_1b_77_76_b2_a6
Feb 14 08:21:32 localhost NetworkManager: <info> Trying to start the
system settings daemon...
Feb 14 08:21:32 localhost kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link
becomes ready
Feb 14 08:21:32 localhost NetworkManager: <info> (eth0) supplicant
interface is now in state 2 (from 1).
Feb 14 08:21:32 localhost NetworkManager: <info> (wlan0) supplicant
interface is now in state 2 (from 1).
Feb 14 08:21:32 localhost kernel: printk: 203 messages suppressed.
Feb 14 08:21:32 localhost kernel: nm-system-setti[4648]: segfault at
0000000000000008 rip 00002aaaab80b36a rsp 00007ffff4282b40 error 4
Feb 14 08:21:32 localhost NetworkManager: file dbus-gproxy.c: line 659
(unassociate_proxies): assertion failed: (priv->associated)
Feb 14 08:21:33 localhost kernel: b44: eth0: Link is up at 100 Mbps,
half duplex.
Feb 14 08:21:33 localhost kernel: b44: eth0: Flow control is off for
TX and off for RX.
Feb 14 08:21:33 localhost kernel: ADDRCONF(NETDEV_CHANGE): eth0: link
becomes ready
Feb 14 08:21:33 localhost avahi-daemon[2223]: Registering new address
record for fe80::21b:77ff:fe76:b2a6 on wlan0.*.
Feb 14 08:21:34 localhost setroubleshoot: #012 SELinux is
preventing nm-system-setti(/usr/sbin/nm-system-settings)
(system_dbusd_t) "getattr" to <Unknown> (inotifyfs_t).#012
For complete SELinux messages. run sealert -l
c4a5c22d-eafd-47c0-afb3-e322f146a55a
Feb 14 08:21:34 localhost avahi-daemon[2223]: Registering new address
record for fe80::21a:4bff:fe5c:ce on eth0.*.
Feb 14 08:22:50 localhost NetworkManager: <info> starting...
Feb 14 08:22:50 localhost NetworkManager: <info> Found radio
killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch
Feb 14 08:22:50 localhost NetworkManager: <info> eth0: Device is
fully-supported using driver 'b44'.
Feb 14 08:22:50 localhost NetworkManager: <info> Now managing wired
Ethernet (802.3) device 'eth0'.
Feb 14 08:22:50 localhost NetworkManager: <info> Bringing down device eth0
Feb 14 08:22:50 localhost kernel: b44: eth0: powering down PHY
Feb 14 08:22:50 localhost avahi-daemon[2223]: Withdrawing address
record for fe80::21a:4bff:fe5c:ce on eth0.
Feb 14 08:22:50 localhost dhclient: receive_packet failed on eth0:
Network is down
Feb 14 08:22:52 localhost NetworkManager: <info> Bringing up device eth0
Feb 14 08:22:52 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 14 08:22:52 localhost NetworkManager: <info> Deactivating device eth0.
Feb 14 08:22:52 localhost NetworkManager: <info> (eth0): exported as
/org/freedesktop/Hal/devices/net_00_1a_4b_5c_00_ce
Feb 14 08:22:52 localhost NetworkManager: <info> wlan0: Device is
fully-supported using driver 'iwl3945'.
Feb 14 08:22:52 localhost NetworkManager: <info> wlan0: driver
supports SSID scans (scan_capa 0x01).
Feb 14 08:22:52 localhost NetworkManager: <info> Now managing
wireless (802.11) device 'wlan0'.
Feb 14 08:22:52 localhost NetworkManager: <info> Bringing down device wlan0
Feb 14 08:22:52 localhost avahi-daemon[2223]: Withdrawing address
record for fe80::21b:77ff:fe76:b2a6 on wlan0.
Feb 14 08:22:52 localhost kernel: ACPI: PCI interrupt for device
0000:10:00.0 disabled
Feb 14 08:22:54 localhost NetworkManager: <info> Bringing up device wlan0
Feb 14 08:22:54 localhost kernel: ACPI: PCI Interrupt 0000:10:00.0[A]
-> GSI 17 (level, low) -> IRQ 17
Feb 14 08:22:54 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 14 08:22:54 localhost NetworkManager: <info> Deactivating device wlan0.
Feb 14 08:22:54 localhost NetworkManager: <info> (wlan0): exported as
/org/freedesktop/Hal/devices/net_00_1b_77_76_b2_a6
Feb 14 08:22:54 localhost NetworkManager: <info> Trying to start the
system settings daemon...
Feb 14 08:22:54 localhost NetworkManager: <info> (eth0) supplicant
interface is now in state 2 (from 1).
Feb 14 08:22:54 localhost NetworkManager: <info> (wlan0) supplicant
interface is now in state 2 (from 1).
Feb 14 08:22:54 localhost kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link
becomes ready
Feb 14 08:22:54 localhost kernel: nm-system-setti[4714]: segfault at
0000000000000008 rip 00002aaaab80b36a rsp 00007fffc3585e40 error 4
Feb 14 08:22:54 localhost NetworkManager: <info> Trying to start the
system settings daemon...
Feb 14 08:22:54 localhost kernel: nm-system-setti[4716]: segfault at
0000000000000008 rip 00002aaaab80b36a rsp 00007fff9e4fadc0 error 4
Feb 14 08:22:54 localhost NetworkManager: <info> Trying to start the
system settings daemon...
Feb 14 08:22:54 localhost kernel: nm-system-setti[4718]: segfault at
0000000000000008 rip 00002aaaab80b36a rsp 00007fff10312bd0 error 4
Feb 14 08:22:54 localhost NetworkManager: <info> Trying to start the
system settings daemon...
Feb 14 08:22:54 localhost kernel: nm-system-setti[4720]: segfault at
0000000000000008 rip 00002aaaab80b36a rsp 00007fff76be84b0 error 4
Feb 14 08:22:54 localhost NetworkManager: <info> Trying to start the
system settings daemon...
Feb 14 08:22:54 localhost kernel: nm-system-setti[4722]: segfault at
0000000000000008 rip 00002aaaab80b36a rsp 00007fffa4e82740 error 4
Feb 14 08:22:54 localhost NetworkManager: <info> Trying to start the
system settings daemon...
Feb 14 08:22:54 localhost kernel: nm-system-setti[4724]: segfault at
0000000000000008 rip 00002aaaab80b36a rsp 00007fff96f2a7f0 error 4
Feb 14 08:22:54 localhost NetworkManager: <info> Trying to start the
system settings daemon...
Feb 14 08:22:54 localhost kernel: nm-system-setti[4726]: segfault at
0000000000000008 rip 00002aaaab80b36a rsp 00007fffce882140 error 4
Feb 14 08:22:54 localhost NetworkManager: <info> Trying to start the
system settings daemon...
Feb 14 08:22:54 localhost kernel: nm-system-setti[4728]: segfault at
0000000000000008 rip 00002aaaab80b36a rsp 00007fff2d40ecd0 error 4
Feb 14 08:22:54 localhost NetworkManager: <info> Trying to start the
system settings daemon...
Feb 14 08:22:54 localhost kernel: nm-system-setti[4730]: segfault at
0000000000000008 rip 00002aaaab80b36a rsp 00007fff2f34cc10 error 4
Feb 14 08:22:54 localhost NetworkManager: <info> Trying to start the
system settings daemon...
Feb 14 08:22:54 localhost kernel: nm-system-setti[4732]: segfault at
0000000000000008 rip 00002aaaab80b36a rsp 00007fff9cad93a0 error 4
Feb 14 08:22:54 localhost NetworkManager: <info> Trying to start the
system settings daemon...
Feb 14 08:22:55 localhost NetworkManager:last message repeated 53 times
Feb 14 08:22:55 localhost kernel: b44: eth0: Link is up at 100 Mbps,
half duplex.
Feb 14 08:22:55 localhost kernel: b44: eth0: Flow control is off for
TX and off for RX.
Feb 14 08:22:55 localhost kernel: ADDRCONF(NETDEV_CHANGE): eth0: link
becomes ready
Feb 14 08:22:55 localhost NetworkManager: <info> SWITCH: no current
connection, found better connection 'Auto Ethernet (eth0)'.
Feb 14 08:22:55 localhost NetworkManager: <info> Activating device eth0
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 1 of 5 (Device Prepare) scheduled...
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 1 of 5 (Device Prepare) started...
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 2 of 5 (Device Configure) scheduled...
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 1 of 5 (Device Prepare) complete.
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 2 of 5 (Device Configure) starting...
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 2 of 5 (Device Configure) successful.
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 3 of 5 (IP Configure Start) scheduled.
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 2 of 5 (Device Configure) complete.
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 3 of 5 (IP Configure Start) started...
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Beginning DHCP transaction.
Feb 14 08:22:55 localhost NetworkManager: <info> dhclient started with pid 4842
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 3 of 5 (IP Configure Start) complete.
Feb 14 08:22:55 localhost dhclient: Internet Systems Consortium DHCP
Client V3.0.6-Fedora
Feb 14 08:22:55 localhost dhclient: Copyright 2004-2007 Internet
Systems Consortium.
Feb 14 08:22:55 localhost dhclient: All rights reserved.
Feb 14 08:22:55 localhost dhclient: For info, please visit
http://www.isc.org/sw/dhcp/
Feb 14 08:22:55 localhost dhclient:
Feb 14 08:22:55 localhost dhclient: wmaster0: unknown hardware address type 801
Feb 14 08:22:55 localhost NetworkManager: <info> Trying to start the
system settings daemon...
Feb 14 08:22:55 localhost NetworkManager:last message repeated 3 times
Feb 14 08:22:55 localhost dhclient: wmaster0: unknown hardware address type 801
Feb 14 08:22:55 localhost NetworkManager: <info> DHCP: device eth0
state changed (null) -> preinit
Feb 14 08:22:55 localhost dhclient: Listening on LPF/eth0/00:1a:4b:5c:00:ce
Feb 14 08:22:55 localhost dhclient: Sending on LPF/eth0/00:1a:4b:5c:00:ce
Feb 14 08:22:55 localhost dhclient: Sending on Socket/fallback
Feb 14 08:22:55 localhost dhclient: DHCPDISCOVER on eth0 to
255.255.255.255 port 67 interval 5
Feb 14 08:22:55 localhost dhclient: DHCPOFFER from 172.16.1.9
Feb 14 08:22:55 localhost dhclient: DHCPREQUEST on eth0 to
255.255.255.255 port 67
Feb 14 08:22:55 localhost dhclient: DHCPACK from 172.16.1.9
Feb 14 08:22:55 localhost NetworkManager: <info> Trying to start the
system settings daemon...
Feb 14 08:22:55 localhost dhclient: bound to 172.16.4.11 -- renewal in
13079 seconds.
Feb 14 08:22:55 localhost NetworkManager: <info> DHCP: device eth0
state changed preinit -> bound
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 4 of 5 (IP Configure Get) scheduled...
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 4 of 5 (IP Configure Get) started...
Feb 14 08:22:55 localhost NetworkManager: <info> address 172.16.4.11
Feb 14 08:22:55 localhost NetworkManager: <info> netmask 255.255.248.0
Feb 14 08:22:55 localhost NetworkManager: <info> broadcast 172.16.255.255
Feb 14 08:22:55 localhost NetworkManager: <info> gateway 172.16.0.1
Feb 14 08:22:55 localhost NetworkManager: <info> nameserver '172.16.1.9'
Feb 14 08:22:55 localhost NetworkManager: <info> nameserver '213.130.62.249'
Feb 14 08:22:55 localhost NetworkManager: <info> nameserver '213.198.86.135'
Feb 14 08:22:55 localhost NetworkManager: <info> domain name
'int.online.ntt.eu'
Feb 14 08:22:55 localhost NetworkManager: <info> domain name 'eu.verio.net'
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 5 of 5 (IP Configure Commit) scheduled...
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 4 of 5 (IP Configure Get) complete.
Feb 14 08:22:55 localhost NetworkManager: <info> Activation (eth0)
Stage 5 of 5 (IP Configure Commit) started...
Feb 14 08:22:55 localhost avahi-daemon[2223]: Joining mDNS multicast
group on interface eth0.IPv4 with address 172.16.4.11.
Feb 14 08:22:55 localhost avahi-daemon[2223]: New relevant interface
eth0.IPv4 for mDNS.
Feb 14 08:22:55 localhost avahi-daemon[2223]: Registering new address
record for 172.16.4.11 on eth0.IPv4.
Feb 14 08:22:55 localhost avahi-daemon[2223]: Registering new address
record for fe80::21b:77ff:fe76:b2a6 on wlan0.*.
Feb 14 08:22:56 localhost NetworkManager: <info> Activation (eth0)
successful, device activated.
Feb 14 08:22:56 localhost NetworkManager: <info> Activation (eth0)
Stage 5 of 5 (IP Configure Commit) complete.
Feb 14 08:22:56 localhost NetworkManager: file dbus-gproxy.c: line 659
(unassociate_proxies): assertion failed: (priv->associated)
Feb 14 08:22:56 localhost gnome-keyring-daemon[2693]: couldn't read 4
bytes from client:
Feb 14 08:22:56 localhost gnome-keyring-daemon[2693]: couldn't read 4
bytes from client:
Feb 14 08:22:58 localhost avahi-daemon[2223]: Registering new address
record for fe80::21a:4bff:fe5c:ce on eth0.*.
Feb 14 08:22:58 localhost dnsmasq[2347]: reading /etc/resolv.conf
Feb 14 08:22:58 localhost dnsmasq[2347]: using nameserver 213.198.86.135#53
Feb 14 08:22:58 localhost dnsmasq[2347]: using nameserver 213.130.62.249#53
Feb 14 08:22:58 localhost dnsmasq[2347]: using nameserver 172.16.1.9#53
Feb 14 08:22:58 localhost setroubleshoot: #012 SELinux is
preventing nm-system-setti(/usr/sbin/nm-system-settings)
(system_dbusd_t) "getattr" to <Unknown> (inotifyfs_t).#012
For complete SELinux messages. run sealert -l
c4a5c22d-eafd-47c0-afb3-e322f146a55a
Feb 14 08:22:58 localhost setroubleshoot: #012 SELinux is
preventing the dhclient(/sbin/dhclient) from using potentially
mislabeled files (<Unknown>).#012 For complete SELinux
messages. run sealert -l df941369-6ce6-49df-ad44-18fcf4b0f607
Feb 14 08:22:58 localhost setroubleshoot: #012 SELinux is
preventing the dhclient(/sbin/dhclient) from using potentially
mislabeled files (/etc/services).#012 For complete SELinux
messages. run sealert -l 6f0ac0d2-bf99-48ad-a23f-d3fc4437b4db
[perobinson@euuklonw7300b1n ~]$ nm-applet
** (nm-applet:3587): WARNING **: Unknown setting 'umts'
** (nm-applet:3587): WARNING **: Required setting 'umts' not found.
** (nm-applet:3587): WARNING **: Invalid connection read from GConf at
/system/networking/connections/4.
** (nm-applet:3587): WARNING **: nm_object_get_property: Error getting
'WirelessEnabled' for /org/freedesktop/NetworkManager: The name
org.freedesktop.NetworkManager was not provided by any .service files
** (nm-applet:3587): WARNING **: nm_object_get_property: Error getting
'WirelessHardwareEnabled' for /org/freedesktop/NetworkManager: The
name org.freedesktop.NetworkManager was not provided by any .service
files
** (nm-applet:3587): WARNING **: nm_object_get_property: Error getting
'State' for /org/freedesktop/NetworkManager: The name
org.freedesktop.NetworkManager was not provided by any .service files
** (nm-applet:3587): WARNING **: Error in getting VPN connections: The
name org.freedesktop.NetworkManager was not provided by any .service
files
16 years, 2 months
Firefox doesn't start
by Adrin Jalali
Hi there, since I've updated my firefox I can not start it. It says :
Firefox is already running, but is not responding. To open a new window, you
must first close the existing Firefox process, or restart your system.
even when I start it with -safe-mode or -no-remote switches. and
#ps -A | grep firefox
gets no result.
I have these packages :
firefox-3.0-0.beta2.16.nightly20080206.fc9.i386
xulrunner-1.9-0.beta2.16.nightly20080206.fc9.i386
Best,
adrin.
16 years, 2 months
gnome-system-monitor causes X to use 100% CPU
by Michael Schwendt
$ rpm -qf $(which gnome-system-monitor)
gnome-system-monitor-2.21.5-1.fc9.i386
I load it as applet in order to watch processor, network and disk
usage.
When double-clicking it to open its window mode, the Xorg process
uses the CPU at 100%, not only in the graph but also in "top".
Can anyone confirm?
16 years, 2 months