having running F17-x86_64 fully updated. I run gnome-shell and
Sometimes, if loading a CD or DVD, the desktop is locked until nautilus
has checked the media (no mouse movements, a.s.o).
Anybody sees this too? How to get rid of this effects?
I had this effect already in earlier Fedora versions, but I don't
remember how I could solve this issue.
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
I just installed wireshark on my F16 laptop. At least I think I did.
The only issue is it looks like it installed everything /except/ the
binary. Has anyone else seen this?
Linux marius.homelinux 3.4.2-1.fc16.x86_64 GNU/Linux
After installation everything I see is the top edge of the screen, rest
is just black. No matter if I install from livecd/dvd or try upgrading
from Fedora 16 through dvd installer. Same if I try to boot with 3
instead of rhgb and quiet options (runlevel 3 if I remember correctly).
Fedora 16 was running fine, without any problems.
Hardware: Phenom II X6 1090T, AMD HD 6870, 8GB RAM, HDD WD 1TB
Thanks in advice.
I have a laptop with Fedora 16-x86_64bit installed. One day last week I
noticed that I was not required to enter a password to log in from the
graphical screen. For example, when I click on my username from the GUI the
system logs me in immediately without requiring or prompting me to enter my
password. This is true with all users and when using both Gnome and KDE
desktops. I have searched everywhere I can think of and can't seem to find
a post describing this issue. I have verified that auto-login has not been
configured in either Gnome or KDE. I have also made sure the "Enable
Password-less Logins" is not enabled in the System
Settings/Logins/Convenience tab. Strangely enough, if the screen saver
kicks in I have to enter a password to unlock it and if I switch to a
textual session (Ctrl+Alt-F3 for example) I have to enter both username and
password to login.
Does anyone have an idea how to re-enable the need to provide a password
from the GUI or where I should begin to look for the problem?
I have a problem with assembling working environment with all packages
required to encode/decode/convert MPEG-4 and H.264 media files in Fedora
I'd like to convert some video files to mpeg-4 format easily but I'm
unable to do it. I'm unable to find any comprehensive info about
packages that need to be installed in Fedora 17 in order to work with
aforementioned files. So I ended up mixing some advice form several
blogs etc. I can watch mp4 videos but not create them from other media
My questions are:
1) What packages are to be installed to fully support MPGE-4 as
destination media format?
2) Is there a package with WinFF, the GUI form ffmpeg
(http://winff.org/html_new/) in Fedora 17? Yumming doesn't seem to
provide and faint trail of such a packaged.
3) How can I find extensive info about Fedora packages where I can read
detail about them and search for appropriate one by myself (something
like http://www.debian.org/distrib/packages because
https://admin.fedoraproject.org/pkgdb/ doesn't work for me, I hardly can
find anything useful there.)
Thanks in advance for any help,
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.129: icmp_req=2 ttl=64 time=2.65 ms
64 bytes from 192.168.42.129: icmp_req=3 ttl=64 time=2.83 ms
When was this change put in place?
I have created a USB installer for the FC16 DVD ISO image via the
livecd-iso-to-disk tool, as detailed on the Fedora wiki. I also included
the appropriate "repo=hd:<device>:/path/file" boot parameter to the kernel
command-line, as the wiki states that for all releases prior to FC17 this
must be added.
My USB installer boots the kernel and initrd and starts to run anaconda,
but soon complains that it is "Unable to download the kickstart file."
which had been specified in the kernel command-line as "hd:sdb1:/ks1.cfg".
I've tried changing this (just for the sake of argument) to sda1, sdb2
etc, but sdb1 *is* indeed the device with the kickstart file (ks1.cfg).
Indeed even in the kernel boot output the device can be seen:
[ 5.794336] usb 2-1.2: New USB device found, idVendor=0951, idProduct=1642
[ 5.794344] usb 2-1.2: New USB device strings: Mfr=1, Product=2,
[ 5.794351] usb 2-1.2: Product: DT 101 G2
[ 5.794356] usb 2-1.2: Manufacturer: KINGSTON
[ 5.794360] usb 2-1.2: SerialNumber: 001CC0EC34BBAC41B64402BA
[ 9.881948] scsi 4:0:0:0: Direct-Access
[ 9.891143] sd 4:0:0:0: Attached scsi generic sg1 type 0
[ 9.891886] sd 4:0:0:0: [sdb] 15204352 512-byte logical blocks: (7.78
[ 9.894032] sd 4:0:0:0: [sdb] Write Protect is off
[ 9.896133] sd 4:0:0:0: [sdb] Write cache: disabled, read cache:
[ 9.902880] sdb: sdb1 sdb2
[ 9.926528] sd 4:0:0:0: [sdb] Attached SCSI removable disk
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: Unknown mount
Removing UID=500 from an fstab entry allowed me to mount that Win7
share, but all files/dirs in that share are now root:root. I also
tried UID=user_name, but got the same invalid arg error.
Rebooting to the prev kernel (3.3.8-1.fc16.x86_64), fstab entries with
UID=500 again mounted w/o error and shares again show the approp owner.
Is this a bug in the newer kernel?
Thanks for any help you can offer,
P.S. My apologies if this is a duplicate message - I sent the original
about 4 hours ago, but haven't yet received a copy from the list. I
looked for an online archive to check, but failed to find anything
more recent than 2010.
Apologies, but I'm arriving late to this discussion.
I've just gone through a re-install (F15->F16) and now an upgrade
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
Is this situation still awaiting a resolution?
Hi, has anyone else seen this? Since installing F17 (probably the
first clean fedora install I've done since single digits), I get a
flickering mouse pointer when the system is busy. This might be
related to the fact the mouse pointer hides instantly (no pause) when
stopped over certain window areas (list items seem most common).
Asking partly because I'm not sure what component to report this as a