I'm using KDE and I'm running F17 in virtualbox so I'm not sure where the problem lies.
Using the mouse wheel scrolls the virtual desktop even with the mouse inside an application window.
This is very annoying. I have looked at all the desktop settings, configurations, whatever I can find that deals with mouse, desktop switching or shortcuts and I have yet to find anything that effects this annoying behavior.
This started somewhere around the first beta release.
We currently don't have any explicit criterion that mandates that
keyboard layouts choose in the installer should work in the installed
As a maintainer of one of the packages involved there
(system-setup-keyboard) I see such bugs in basically every release,
during the development cycle.
We should pay more attention to such issues as a system that uses a
different keyboard layout as the one physically present can not only
be very annoying (we shouldn't release in that state) but
can be useless when you have special characters in your password(s).
(Can't easily decrypt / login).
As seen in https://lists.fedoraproject.org/pipermail/test/2011-March/097859.html
we do currently have a paragraph that mentions this but is IMO way to
So I propose something like: "The keyboard layout selected in the
installer must be in use after rebooting the installer (plymouth and
Dear GIMP lovers,
for the first time after update to Fedora 17, I've needed to do
some simple edits to a few photos.
Now I feel it is time to say goodbye to GIMP and start saving for
There is no point for me in reporting bugs - this is some
fundamental difference between my and the GIMP developers'
thinking ("it is not a bug, it is a feature").
The first thing was that GIMP had asked me if I want the photos
rotated according to EXIF. Hell yes, I can hardly remember any
single case where I wouldn't want this. - There was just a little
problem that I simply don't know which orientation is "standard".
So I was really not sure what to answer, will the photo get
rotated according to EXIF or will it be rotated from EXIF
orientation to the physical orientation of the JPEG data in the
file? And that's where I got the suspicion ...
I wouldn't mind that "resize" got renamed to "scale".
What do I mind is that "Save as" no longer works as before. I
still have the possibility to choose the file extension, however
trying to use "jpg" tells me that it won't save the file as JPEG
and that I have to "export" the file. That sounds very "logical"
when I've opened somefile.jpg and I just want to save it as
someothername.jpg not to overwrite original; I do not want to
"export" to any other format than what was the original.
Ok, so I went to "export", did all the "advanced" settings and
saved the file. Then the same for the rest of files I had
altered. Oh, the JPEG settings dialogue doesn't remember the
settings over the editing session as it always did? The only
possibility not to spent half an hour clicking the same twenty
times in a row is to save the settings as default. But I don't
want these exact settings to be the default ...
Cool, so I've spent half an hour "exporting" the files. So I'm
finished, let's close GIMP. Hey, but what's that dialogue asking
me to save unsaved changes of a file that I have just saved?
Every single file that just got saved is treated as unsaved just
because I was so bold not to use the one and only holy XCF format
for reprocessed JPEGs? Okay, just enough for me ...
Next time I'll rather spend my time studying ImageMagick usage to
script the task even for less than ten images, rather than doing
So, feel free to join me with the moment of silence for the good
old GIMP that is just getting buried.
QE BaseOs/Daemons Team
Red Hat Czech, Brno
tel. +420 532294274
(RH: +420 532294111 ext. 8262074)
:: "Never attribute to malice what can
:: easily be explained by stupidity."
I see in f17 that firewalld is the default and iptables and
ip6tables are not enabled by default.
So if I have an elaborate /etc/sysconfig/iptables file
that has grown over the years to do all sorts of complicated
stuff, how do I port it to firewalld?
Is firewalld nice enough to just go ahead and apply the
/etc/sysconfig/iptables file at startup should I happen
to create one?
==Testing of f17 TC2 in USB==
dd if=Fedora-17-TC2-x86_64-DVD.iso of=/dev/sdb bs=2M
# dd if=Fedora-17-TC2-x86_64-DVD.iso of=/dev/sdb bs=2M
1843+0 records in
1843+0 records out
3865051136 bytes (3.9 GB) copied, 726.369 s, 5.3 MB/s
*Bios boots - uses DVD install repo
: boots to grub only (Fails)
*l-i-t-d ver 9-1
: f17 gnome 3.4.1
:8 GB USB Disk-Utility GPT with /dev/sdb1 fat label=LIVE
*Builds 2 Partitions
# livecd-iso-to-disk --format --efi Fedora-17-TC2-x86_64-DVD.iso /dev/sdb1
Fragment count: 20
Press [Esc] to abort check.
T he media check is complete, the result is: PASS.
It is OK to use this media.
/Packages found, will copy source .iso to target
WARNING: THIS WILL DESTROY ANY DATA ON /dev/sdb!!!
Press Enter to continue or ctrl-c to abort
8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54
8 bytes were erased at offset 0x1debffe00 (gpt): 45 46 49 20 50 41 52 54
Waiting for devices to settle...
mkdosfs 3.0.12 (29 Oct 2011)
mkdosfs 3.0.12 (29 Oct 2011)
Copying live image to target device.
137777152 100% 5.56MB/s 0:00:23 (xfer#1, to-check=0/1)
sent 137794045 bytes received 31 bytes 5863577.70 bytes/sec
total size is 137777152 speedup is 1.00
3865051136 100% 3.65MB/s 0:16:50 (xfer#1, to-check=0/1)
sent 3865523034 bytes received 31 bytes 3821574.95 bytes/sec
total size is 3865051136 speedup is 1.00
Updating boot config file
Installing boot loader
Target device is now set up with a Live image!
*Install to HD works
:Boots to grub 2.00 then to Firstboot.
:Logs in successfully via gdm
*DVD install repo contains 33 files for Sugar-Desktop
Did an upgrade from F16 to current F17 tree + updates on my server and
all seemed well.
Except for dovecot..which after the upgrade, it seemed to error on my
client side (via imap) about namespace and inbox=yes and no namespace or
something along those lines.
Anyone else seen this? It seems downgrading back to the 2.0 version in
F16 get it back to working again.
"Best little town on Earth!"
Has anyone experienced Palimpsest discrepancies?
Palimsest in Fedora 16 reports a disk (MAXTOR STM3320620AS) as failing: "DISK HAS MANY BAD SECTORS" etc.
SMART: 197 Current pending Sector Count Value -4 sectors.
Palimsest in Fedora 17 beta reports the same disk (MAXTOR STM3320620AS) as "OK"
SMART: 197 Current pending Sector Count 0 sectors OK.
Obviously one is incorrect, which one?
Has F17 been tested to see whether it will install on a Pentium 4?
Recently I installed F15 because I could not get the F16 installer to boot.
I can get the F13, F14 and F15 installers to boot without media.
The F16 installer was a no go, both without media and with a minimal CD.
In both cases, I got crashes that required pushing the reset button.
I never got to tell them about the iso file.
"On Monday, I'm gonna have to tell my kindergarten class,
whom I teach not to run with scissors,
that my fiance ran me through with a broadsword." -- Lily
after updating to systemd-44-7.fc17 (and systemd-sysv-44-7.fc17),
rebooting hangs up. Pushing the reset button is needed :-(
I had to downgrade systemd to get rid from this bug.
No such problems with the previous version.
Anybody sees this too?
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
I upgraded from F-16 to F-17 Beta, then upgraded to find that I couldn't
delete my own files!!! after disabling Selinux and enabling it again
(i.e. relabeling) everything is o.k.Anybody experiencing it??
Fedora 17 Beta