RPMFusion - what is going on?
by Valent Turkovic
Does anybody have some info on when is RPMFusion repo scheduled to be
officially released to Fedora users?
I have read only announcements couple months ago on few blogs and
since then complete radio silence. What is going on with that project,
does anybody know?
Valent.
--
http://kernelreloaded.blog385.com/
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241, Skype: valent.turkovic
16 years, 3 months
GNOME_ClockApplet doesn't always load
by wayne
I finally decided to upgrade from my old reliable Redhat 9 to Fedora 8.
For the most part it works great. I am having problems with
GNOME_ClockApplet
and GNOME_WorkspaceSwitcherApplet, where they do not always appear on
the panel
when I log in. Here are the pop-up errors I get:
=============
The panel encountered a problem while loading "OAFIID:GNOME_ClockApplet".
The panel encountered a problem while loading
"OAFIID:GNOME_WorkspaceSwitcherApplet".
=============
Sometimes they appear on the Gnome panel and sometimes they do not.
Here is the
output of .xsession-errors:
=============
SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/16377,unix/unix:/tmp/.ICE-unix/16377
** (gnome-session:16377): WARNING **: Host name lookup failure on localhost.
11
** (nm-applet:16481): WARNING **: <WARN>
applet_dbus_manager_start_service(): Could not acquire the
NetworkManagerUserSettings service as it is already taken. Return: 3
(nm-applet:16481): GLib-CRITICAL **: g_hash_table_destroy: assertion
`hash_table != NULL' failed
(nm-applet:16481): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(nm-applet:16481): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
Key
/apps/panel/objects/0t1109568543ut155660u500p14986r508150898k3221215820/launcher_location
is not set, cannot load launcher
** (gnome-panel:16460): WARNING **: panel-applet-frame.c:1293: failed to
load applet OAFIID:GNOME_WorkspaceSwitcherApplet:
Failed to resolve, or extend
'!prefs_key=/apps/panel/applets/applet_6/prefs;background=none:;orient=up;size=medium;locked_down=false
** (gnome-panel:16460): WARNING **: panel-applet-frame.c:1293: failed to
load applet OAFIID:GNOME_ClockApplet:
Failed to resolve, or extend
'!prefs_key=/apps/panel/applets/applet_1/prefs;background=none:;orient=up;size=medium;locked_down=false
Unable to connect to yum-updatesd. Please ensure that the yum-updatesd
package is installed and that the service is running.
could not attach to desktop process
Unable to connect to yum-updatesd. Please ensure that the yum-updatesd
package is installed and that the service is running.
=============
Does anyone out there know what the cause of this is and what the fix is?
Thanks,
-- Wayne.
16 years, 3 months
OT: security of make as authorized_keys command
by Dave Burns
I should probably ask this on an ssh oriented list, but I thought I'd
try my luck here first.
I want to do some remote commands securely. I put a key in my
.ssh/authorized_keys file like so:
command="/usr/bin/make $SSH_ORIGINAL_COMMAND" ssh-rsa AAAAB3NzaC1[etc.etc.]
so I can invoke make targets like so:
ssh username@host target
Assuming the bad guys never get my key, I am fine, even though it is
passwordless.
What if a bad guy does get my key? Then I see three possible problems:
1) somehow use make's -F switch in ssh command to change Makefiles?
2) stack overflow of make or ssh?
3) Somehow put extra command after make target using ';' or something?
And obviously the bad guy can invoke any of the targets in my
makefile, but I've made them pretty innocuous.
So, should I seriously worry about any of these potential problems?
Any other holes I haven't thought of?
The motivation for all this is some cron jobs I want to run, obviously
calls for a passwordless ssh key, but I want to put some limits on it.
Thanks,
Dave
16 years, 3 months
4L-gui problem
by Gene Heskett
Greetings;
Just now burning the respin dvd's and found that since I'd converted this FC6
install to all libata drive access, that Lacie's 4L-gui cannot now find the
drive. I had no trouble reconfiguring k3b to use /dev/sdc.
The /etc/lightscribe.rc file doesn't contain any drive pointers so I'm a bit
puzzled as to how to proceed. It did work the one time I tried it on my F8
lappy.
Running 4L-cli, it reports that the device does not exist, and /dev/dvd is a
link to /dev/scd0, both are visible in the/dev tree, and I can mount -t
iso9660 /dev/dvd /media/dvd just fine.
Has anyone else encountered this and arrived at a fix?
Thanks.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
You want to know why I kept getting promoted? Because my mouth knows more
than my brain.
-- W.G.
16 years, 3 months
32- versus 64-bit fedora on an AMD 64 mobile athlon?
by Robert P. J. Day
moving on, i have a roomful of gateway MX7120 laptops (with AMD
64-bit mobile athlon CPU) that i use for linux training and, until
now, i've just wimped out and installed the 32-bit version of fedora
on them for my clients, and that works just fine.
but i figure, why waste all that 64-bit computing power, so is there
any compelling reason to *not* upgrade them all to fedora x86_64 for
those courses? that is, are there any real show-stoppers when it
comes to fedora x86_64 that would make that version unusable?
thanks.
rday
p.s. i'm guessing that, since these things have a broadcom chipset,
wireless is still going to be an issue as it is with fedora i386 but,
in my classrooms, these systems are always hardwired so that's not a
problem for me. at least, not yet.
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
16 years, 3 months
FC6
by Patrick Dupre
Hello,
I did try to upgrade a FC4 to FC6 but anaconda failed. I am uisng the
Rescude CD and then the fedora6.iso The DVD has been checked. I can
eventually access to the fc6.rpm files but anaconda fails. At one poin the
/tmp/cdrom is mounted on /mnt/source but then the DVD is dismounted.
anaconda complains on
///mnt/source/Fedora/RPMS/firefox-1.5.7-7.fc6.i386.rpm, I guess that it is
just because it is the first file to update.
What is wrong ?
Regards
16 years, 3 months
[Fedora] Seeing input on Securing the Linux system from intrusions and attacks.
by Dan Thurman
I have finally got my F8 setup and running so now I am reviewing the
security issues that needs to be taken into account.
I have looked into trying many things to protect and harden my systems,
but I thought I'd ask members what they are doing/using to defend their
systems against attacks and unwanted intrusions? Would it be neat
if there was an automatic non-human defender to do it for you while you
sleep? Dream on.
I would like to focus on securing Fedora. I have tried snort w/Base etc.,
Tripwire, Fam, nmap, Iptable techniques, and so on.
Does anyone have any advice, links to great sites focused on security
and how to secure your linux box against intrusions and attacks?
Thanks!
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.17.9/1198 - Release Date: 12/26/2007 5:26 PM
16 years, 3 months
amarok-backtraces to amarok-backtraces@lists.sf.net
by John Summerfield
amorak seems a little fragile, but has this cool feature such that it
reports them to amarok-backtraces(a)lists.sf.net
Unfortunately, amarok-backtraces(a)lists.sf.net declines them when I send
them, and I don't understand why. Here is the message I get:
<amarok-backtraces(a)lists.sf.net>: host mail.sourceforge.net[66.35.250.206]
said: 550-Verification failed for <xxxxxx(a)js.id.au> 550-Called:
58.6.192.22 550-Sent: RCPT TO:<xxxxxx(a)js.id.au> 550-Response: 554
<xxxxxx(a)js.id.au>: Relay access denied 550 Sender verify failed (in
reply
to RCPT TO command)
I've carefully obfuscated my email address, but the rest is as in my
bounce message.
I don't understand how it's trying to verify the sender address, but the
sender address is correct and able to receive email - hence the need to
obfuscate it.
Do others have this problem, and if so what are you doing? Binning the
crashes?
--
Cheers
John
-- spambait
1aaaaaaa(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
16 years, 3 months
Broadcom BCM94311MCG mini-pci
by potat0
This is regarding a thread in the devel list:
http://fcp.surfsite.org/modules/newbb/viewtopic.php?viewmode=flat&order=A... [1]
I hope you guys are reading this.
I have managed to get mine working, but via a somewhat difficult route.
I have used kmod-ndiswrapper and a driver I used (64 bit) successfully for some time.
Whilst mucking around I noticed that after a rmmod ndiswrapper the logs showed a requirement for firmware, so I followed the link & instructions in the link (I needed to be using the ndiswrapper wireless to do this) :
http://linuxwireless.org/en/users/Drivers/b43#devicefirmware [2]
I used the firmware on that site, and populated /lib/firmware/b43 with the required firmware stuff.
I then did rmmod ndiswrapper, modprobe b43 and about 20s later Network Manager re-established a connection using the b43-pci-bridge but the LED on the laptop wasn't on, but who cares.
Yippee I though, not more ndiswrapper.
However on next boot no wireless, even though all the logs seemed to show everything as OK.
What I now do is use ndiswrapper to get the card into a warm state, and then rmmod ndiswrapper, modprobe b43 in rc.local
I do this because the b43 driver runs my card better then ndiswrapper!
It seems like I just need better firmware, however the b43-fwcutter doesn't recognise the checksum on the bcmwl5.sys I used for ndiswrapper.
Where can I submit my bcmwl5.sys to be included as a recognised file by b43-fwcutter.
Regards,
Steve
Links:
------
[1] http://fcp.surfsite.org/modules/newbb/viewtopic.php?viewmode=flat&ord...
[2] http://linuxwireless.org/en/users/Drivers/b43#devicefirmware
--
This is an email sent via The Fedora Community Portal https://fcp.surfsite.org
https://fcp.surfsite.org/modules/newbb/viewtopic.php?post_id=230543&topic...
If you think, this is spam, please report this to webmaster(a)fcp.surfsite.org and/or blame fcp.surfsite.org(a)stephen-milner.me.uk.
16 years, 3 months
BlueTooth Issues
by Donald Reader
Hi all
I seem to be having Issues getting my New Xmas gift to pair properly. I
am running FC6
on a pentium4 box. here is the packages I have installed on:
bluez-utils-cups-3.7-2
bluez-libs-devel-3.7-1
bluez-hcidump-1.32-1
bluez-bluefw-1.0-6
bluez-utils-3.7-2
bluez-libs-3.7-1
pybluez-0.9.1-3.fc6
bluez-gnome-0.6-1.fc6
openpbx-bluetooth-1.2-3.rc2.svn2282.fc6
kdebluetooth-1.0-0.19.beta3
gnome-bluetooth-0.7.0-12.fc6
gnome-bluetooth-devel-0.7.0-12.fc6
gnome-bluetooth-libs-0.7.0-12.fc6
nautilus-sendto-bluetooth-0.7-5.fc6
Now I don't know if I am missing a package or if some may be outdated
and need updating. Especially the kdebluetooth package. I have read
pages for days on the web trying to to get a handle on what to do as
this is the very first time I every worked with bluetooth
on starting bluetooth service the log reads
Dec 30 09:49:50 Dads hcid[5878]: Bluetooth HCI daemon
Dec 30 09:49:50 Dads hcid[5878]: Register path:/org/bluez fallback:1
Dec 30 09:49:50 Dads hcid[5878]: HCI dev 0 registered
Dec 30 09:49:50 Dads hcid[5878]: Register path:/org/bluez/hci0
fallback:0
Dec 30 09:49:50 Dads hcid[5878]: HCI dev 0 already up
Dec 30 09:49:50 Dads hcid[5878]: Device hci0 has been added
Dec 30 09:49:50 Dads hcid[5878]: Starting security manager 0
Dec 30 09:49:50 Dads hcid[5878]: Device hci0 has been activated
Dec 30 09:49:50 Dads hcid[5878]: Default passkey agent
(:1.8, /org/kde/kbluetooth_1234) registered
Dec 30 09:49:51 Dads sdpd[5884]: Bluetooth SDP daemon
using hciconfig -a here is the output
hci0: Type: USB
BD Address: 00:02:76:0C:D6:03 ACL MTU: 1017:8 SCO MTU: 64:0
UP RUNNING PSCAN ISCAN
RX bytes:601 acl:0 sco:0 events:43 errors:0
TX bytes:700 acl:0 sco:0 commands:43 errors:0
Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'usbHeadset'
Class: 0x120104
Service Classes: Networking, Object Transfer
Device Class: Computer, Desktop workstation
HCI Ver: 2.0 (0x3) HCI Rev: 0x4116 LMP Ver: 2.0 (0x3) LMP
Subver: 0x430e
Manufacturer: Broadcom Corporation (15)
Now using the hcitool I scan, inq, and cc with these results
[root@Dads ~]# hcitool scan
Scanning ...
00:E0:98:49:2A:92 MATTHEW
00:1C:EF:0A:F3:01 NS-BTHDST
[root@Dads ~]# hcitool inq 00:1C:EF:0A:F3:01
Inquiring ...
00:E0:98:49:2A:92 clock offset: 0x2fe5 class: 0x300104
00:1C:EF:0A:F3:01 clock offset: 0x0efe class: 0x240404
# hcitool info 00:1C:EF:0A:F3:01
Requesting information ...
BD Address: 00:1C:EF:0A:F3:01
LMP Version: 2.0 (0x3) LMP Subversion: 0xbf1
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xff 0xff 0x8f 0x78 0x18 0x18 0x00 0x80
<3-slot packets> <5-slot packets> <encryption> <slot
offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link> <HV2
packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <paging
scheme>
<power control> <transparent SCO> <broadcast encrypt>
<enhanced iscan> <interlaced iscan> <interlaced pscan>
<inquiry with RSSI> <AFH cap. slave> <AFH class. slave>
<AFH cap. master> <AFH class. master> <extended
features>
# hcitool cc 00:1C:EF:0A:F3:01
# hcitool lq 00:1C:EF:0A:F3:01
Not connected.
then I try this
# rfcomm -i hci0 connect 0 00:1C:EF:0A:F3:01
Can't connect RFCOMM socket: Connection refused
log entries after the rfcomm command are
Dec 30 09:58:07 Dads hcid[5878]: link_key_request
(sba=00:02:76:0C:D6:03, dba=00:1C:EF:0A:F3:01)
Dec 30 09:58:07 Dads hcid[5878]: pin_code_request
(sba=00:02:76:0C:D6:03, dba=00:1C:EF:0A:F3:01)
Dec 30 09:58:07 Dads hcid[5878]: Passkey agent replied with an error:
org.freedesktop.DBus.Error.UnknownMethod, Method "Request" with
signature "ss" on interface "org.bluez.PasskeyAgent" doesn't exist
Config files
hcid.conf
#
# HCI daemon configuration file.
#
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# Default PIN code for incoming connections
passkey "0000";
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h-%d";
# Local device class
class 0x120104;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
iscan enable; pscan enable;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
}
rfcomm.conf
#
# RFCOMM configuration file.
#
rfcomm0 {
# # Automatically bind the device at startup
bind no;
#
# # Bluetooth address of the device
device 00:1C:EF:0A:F3:01;
#
# # RFCOMM channel for the connection
channel 1;
#
# # Description of the connection
# comment "Example Bluetooth device";
}
Please help me shed some light on this. Through the whole command
process I am never asked to input the
pin that the headset wants which I believe is a bug. Also with
kdebluetooth I am unable to Configure services or add devices. when I go
to setup my device I get a crash. the backtrace info is as follows
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208932656 (LWP 6026)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0x0670d7ff in QString::latin1 ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#7 0x0670ef42 in QString::ascii ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#8 0x0011e316 in KBluetooth::DBusSignal::newMessage ()
from /usr/lib/libkbluetooth.so.0
#9 0x0011e5a0 in KBluetooth::DBusSignal::sendString ()
from /usr/lib/libkbluetooth.so.0
#10 0x0011e5fc in KBluetooth::DBusSignal::sendString ()
from /usr/lib/libkbluetooth.so.0
#11 0x00120e9b in KBluetooth::InputDevice::connect ()
from /usr/lib/libkbluetooth.so.0
#12 0x08051f0d in QWidget::setUpdatesEnabled ()
#13 0x08052106 in QWidget::setUpdatesEnabled ()
#14 0x080533f4 in QWidget::setUpdatesEnabled ()
#15 0x063f116a in QObject::activate_signal ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x063f1b5d in QObject::activate_signal ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#17 0x0678695c in QButton::clicked ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#18 0x06495afd in QButton::mouseReleaseEvent ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x0642d7f5 in QWidget::event ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x06387cab in QApplication::internalNotify ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#21 0x06389307 in QApplication::notify ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#22 0x05cf2921 in KApplication::notify () from /usr/lib/libkdecore.so.4
#23 0x0631efa6 in QETWidget::translateMouseEvent ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#24 0x0631daa6 in QApplication::x11ProcessEvent ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#25 0x0632f90b in QEventLoop::processEvents ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#26 0x063a1250 in QEventLoop::enterLoop ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#27 0x063a1116 in QEventLoop::exec ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#28 0x063877bf in QApplication::exec ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#29 0x08050d26 in QWidget::setUpdatesEnabled ()
#30 0x009e6dec in __libc_start_main () from /lib/libc.so.6
#31 0x0804d201 in QWidget::setUpdatesEnabled ()
Thanks for any help with this matter
Don
16 years, 3 months
