Fedora17 Alpha RC4

[tox]

As per the Fedora 17 schedule [1], Fedora 17 Alpha Release Candidate 4
(RC4) is now available for testing. Content information, including
changes, can be found at https://fedorahosted.org/rel-eng/ticket/5083 .
Please see the following pages for download links (including delta ISOs)
and testing instructions. Normally dl.fedoraproject.org should provide
the fastest download, but download-ib01.fedoraproject.org is available
as a mirror (with an approximately 1 hour lag) in case of trouble. To
use it, just replace "dl" with "download-ib01" in the download URL.

Installation:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test

Base:

https://fedoraproject.org/wiki/Test_Results:Current_Base_Test

Desktop:

https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test

Ideally, all Alpha priority test cases for Installation [2], Base [3],
and Desktop [4] should pass in order to meet the Alpha Release Criteria
[5]. Help is available on #fedora-qa on irc.freenode.net [6], or on the
test list [7].

Create Fedora 17 Alpha release candidate (RC) - live and traditional
https://fedorahosted.org/rel-eng/ticket/5083

F17 Alpha Blocker tracker bug:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=752648

F17 Alpha Nice-To-Have tracker bug:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=752653

[1] http://rbergero.fedorapeople.org/schedules/f-17/f-17-quality-tasks.html
[2] https://fedoraproject.org/wiki/QA:Installation_validation_testing
[3] https://fedoraproject.org/wiki/QA:Base_validation_testing
[4] https://fedoraproject.org/wiki/QA:Desktop_validation_testing
[5] https://fedoraproject.org/wiki/Fedora_17_Alpha_Release_Criteria
[6] irc://irc.freenode.net/fedora-qa
[7] https://admin.fedoraproject.org/mailman/listinfo/test RC4 DvD's (http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.RC4/Fedora/)

RC4 LiveCD's (http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.RC4/Live/)

---------- Post added at 01:03 PM ---------- Previous post was at 09:12 AM ----------

still getting Garbled Graphix, Plymouth no workies either. the result was, it actually booted but at the end all it was, was Garbled Graphics. ( i do get DRM Nouveau ) errors. how can i get the Logs of those errors even though i cannot log into the Desktop of Gnome?

i did trey another way of booting with 3 it got as far as loading the plymouth Bar on the bottom of the screen and stalled and wouldnt finish loading

[bob]

Greg, booting the X86_64 and posting from the Live CD right now. Very nice, actually. Gotta check it out, perhaps test the 3D options, but doubt I'll install it at this point. Well, 3D's a bust with my graphics card and Nouveau. Otherwise things are pretty decent.

[tox]

Greg, booting the X86_64 and posting from the Live CD right now. Very nice, actually. Gotta check it out, perhaps test the 3D options, but doubt I'll install it at this point. Well, 3D's a bust with my graphics card and Nouveau. Otherwise things are pretty decent.
only other thing i could try an boot with Vesa ? and dont use Nouveau but would that work?

[bob]

Well, since the Big Thing with F17's supposed to be universal support, I'd sure file a bugzilla and let them work it out.

[tox]

Well, since the Big Thing with F17's supposed to be universal support, I'd sure file a bugzilla and let them work it out.

i'll do that or use ABRT :p but again its still rather early days and for all i know by the time F17 beta arrives my issues maybe solved

[sonoran]

Installation went smooth as silk here. The Live version even let me yum install gparted (where does it install to??), create a single new partition for F17, then run Install to hard disk, all without a hitch.

Not even any complaints from Anaconda when I installed bootloader to first sector of boot partition, in this case /, instead of to mbr. Then created a chainloader entry in legacy grub's menu.lst and Fedora 17 booted on the first try.

the Big Thing with F17's supposed to be universal support

I'd say it's a Beefy Miracle! :D
*****************************************
I'd forgotten about the "you can check in but you can never leave" feature of gnome-hell. They seriously expect me to tweak something before I get anything but a useless "Suspend" on the logout power switch icon? They can take that presumption and their Beefy Miracle and stick them both where the sun don't shine.

F17 works, but that ain't saying much. I have better uses for that disk space... like leaving it empty.

[glennzo]

Working well here too. Live RC4. Booted fine. Everything looks good so far. Using RC4 Live to post this reply.

[tox]

Working well here too. Live RC4. Booted fine. Everything looks good so far. Using RC4 Live to post this reply.

so far i cannot get into a GUI of the Gnome Desktop. i havent tried KDE yet. i will tomorrow. but yeah i shall wait till the Beta perhaps and see if it works then. but what X-server GIT version is RC4 using?. it booted but without the proper plymouth. i just got the white/blue bar. least it got that far, recent ones i have downloaded didnt do that

[glennzo]

Dunno about the xserver GIT version. I didn't check. Now I've booted back to F16 and am thinking about installing Live to hard disk.

[sonoran]

what X-server GIT version is RC4 using?
The xorg server in the original TC4 is 1.11.99.901-6.20124.fc17. Nouveau works.

Using openbox, which seems to have been further downgraded by removing the ability to shade windows by double-clicking in the titlebar. You can get a titlebar icon to do it, but that's not nearly as convenient. Maybe installation of a better theme will change that.

[smr54]

I usually set that in rc.xml

Fedora's openbox has given me trouble in the past--usually, especially during alpha, I wind up just downloading the git version. I wonder if this regression is the Fedora packaging or openbox itself?

[sonoran]

My mistake - the window shade functionality can still be set in ObConf under the mouse tab. :doh:

[tox]

The xorg server in the original TC4 is 1.11.99.901-6.20124.fc17. Nouveau works.

Using openbox, which seems to have been further downgraded by removing the ability to shade windows by double-clicking in the titlebar. You can get a titlebar icon to do it, but that's not nearly as convenient. Maybe installation of a better theme will change that.

thanks dude, i'll ownload a current Nightly and see if tht works for me

[Dutchy]

I was trying to install the Vbox Guest Additions but of course that failed because of a too new X version,
when I suddenly noticed that I wasn't in fallback mode but the actual normal mode.
So the new software renderer seems to be doing its work.

[tox]

t the F17 Alpha Go/No-Go meeting today, the Fedora 17 Alpha release
(RC4) was declared GOLD, and ready for shipment on February 28, 2012.

GOLD is the color of mustard, and, as you know, mustard indicates
progress. A huge thank you to everyone who made this on-time(!!!) Alpha
release possible. My (occasionally inaccurate) research tells me that
the last time we shipped an Alpha according to schedule was Fedora 10.
That is some excellent progress, in my humble opinion :)
Fedora 17 Alpha is hereby declared GOLD(en mustard color)! http://lists.fedoraproject.org/pipermail/devel/2012-February/163082.html

[creataphysics]

If i'm fully updated from RC2 does that mean I'm basically on RC4?

Or do I need to download RC4 to be fully updated?

[tox]

If i'm fully updated from RC2 does that mean I'm basically on RC4?

Or do I need to download RC4 to be fully updated?

your fully updated to RC4

[LightDot]

No need to download again unless you wish to test the installer, etc. Just keep the system fully updated from now on and you'll move to alpha, beta, rc, all up to the final release of Fedora 17.

You might be even further than RC4 / alpha right now, depending on how quickly updates are getting released.

[creataphysics]

Alright, good to know.

Also what's up with gnome shell? When it was first announced that gnome shell would work on older cards I immetiately downloaded and installed and I was able to get the full experience.

Now on newer released I notice that in /usr/share/gnome-session/hardware compatibility my graphics card is blacklisted. So when I comment out that line I get the gnome shell login screen, and I'm able to load the full experience, but any window I open has white borders and the content of whatever I'm trying to load is not visible. Is this a bug I should report or what?

[tox]

Alright, good to know.

Also what's up with gnome shell? When it was first announced that gnome shell would work on older cards I immetiately downloaded and installed and I was able to get the full experience.

Now on newer released I notice that in /usr/share/gnome-session/hardware compatibility my graphics card is blacklisted. So when I comment out that line I get the gnome shell login screen, and I'm able to load the full experience, but any window I open has white borders and the content of whatever I'm trying to load is not visible. Is this a bug I should report or what?

what VideoCard do you have?

[smr54]

Using livecd-to-usb or unetbootin, couldn't get the 64 bit netinstall to boot. Will try with the DVD and see if I have any better luck. I see there's a problem with USB install but it's not considered a blocker, the problem apparently being with livecd tools.

[creataphysics]

@tox - It's an intel 865G.

I know the card can run the full experience, when it was first announced that gnome 3 would work on older cards, adam said we need these packages or newer:
mesa-*-7.11-9.fc17
cogl-1.8.2-4.fc17
gnome-session-3.3.1-2.fc17

Well, when I had those exact versions installed, it worked like a charm.

Now I'm facing the problems I posted previously. Gnome3 full experience loads, I just can't view anything I open due to it all being whited out.

[tox]

@tox - It's an intel 865G .

I know the card can run the full experience, when it was first announced that gnome 3 would work on older cards, adam said we need these packages or newer:
mesa-*-7.11-9.fc17
cogl-1.8.2-4.fc17
gnome-session-3.3.1-2.fc17

Well, when I had those exact versions installed, it worked like a charm.

Now I'm facing the problems I posted previously. Gnome3 full experience loads, I just can't view anything I open due to it all being whited out.
G-S from 3.4 and possibly onwards will work on most hardware http://fedoraproject.org/wiki/Features/Gnome_shell_software_rendering & http://fedoraproject.org/wiki/Features/DRI2DriversOnly

[creataphysics]

yes tox, I'm aware of those pages as I check them religiously for updates.

I know I'm one of the "most", as I've already ran the full experience flawlessly. I was just wondering if I should report my issue as a bug, considering I was able to run the full experience in earlier versions and now I'm not.

[tox]

yes tox, I'm aware of those pages as I check them religiously for updates.

I know I'm one of the "most", as I've already ran the full experience flawlessly. I was just wondering if I should report my issue as a bug, considering I was able to run the full experience in earlier versions and now I'm not. you could file a Bug and state your Hardware in it. but from what i have read, there is still a BIT to land yet regarding software rendering feature i think

[jensting]

feedback on install on Intel BIOS RAID (imsm Matrix raid). Install runs fine.

No actual reboot after clocking "reboot" :(

Boots fine and I can log in.

Importantly, it does shutdown cleanly. (mdadm had been failed to shutdown at reboot since Fedora 16)

Best Regards

Jens

[Apostate]

17 Alpha torrents now online

http://torrent.fedoraproject.org/

[tox]

RC4 was an is the Alpha :)

[smr54]

As Adam pointed out on the testiing list, read the common bug page. There's some that might catch you off guard, possibly because the last alpha, IIRC, was pretty smooth, and I think that holds for the one before it too.

Sigh.... I had to laugh though. Many years ago, sound always worked right away on Fedora. Then, they did some improvements (this was pre pulseaudio) and suddenly, you had to be sure to install consolekit or else edit another file--I forget which, but it wasn't at all obvious.

So....rather than fix this, the developer said, Ok, I'll make it impossible to disable consolekit. I'm sure there was some logic to it, but it just seemed like adding bloat to an already bloated distro. (These days, as I've gotten more experienced with the RH method, it's a bit easier to make it less bloated, but they still make it much more cumbersome than it should be, but that's a rant for another time.)

Now, they're removing consolekit. And...sound doesn't work.

There are also, all ranting aside, some other fairly serious bugs, so please do look at the common bugs before trying to install.

https://fedoraproject.org/wiki/Common_F17_bugs?wkanF17a

[tox]

just a note i have Added the F17_Common_Bugs link in the Fedora17 Release Schedule thread of mine which is stickied.

[bob]

Let's see, I've got F16 and Mint on my drive and was looking to add F17Alpha. Guess not! Postponed to Beta!!!

[tox]

Let's see, I've got F16 and Mint on my drive and was looking to add F17Alpha. Guess not! Postponed to Beta!!!

think i'll be doing the same , wait for F17 beta but going from This - about Gnome3.4 (http://afaikblog.wordpress.com/2012/02/28/looking-forward-to-gnome-3-4/) i dont see much difference between 3.4 an 3.2

[AdamW]

Hey folks, sorry I haven't been around this cycle - I'm now the QA team lead and I'm finding I really don't have enough time to keep up with all the Community Manager stuff too :/ we'll probably be fixing that up with hiring one way or another, stay tuned.

Anyhoo: smr54, the sound bug is silly but it's easily workaroundable and it's not really 'intrinsic' to PA or ConsoleKit or whatever. The story is just that PA has a stanza in its default config file which loads its ConsoleKit support module, and if you have that stanza present but CK not present, it won't manage to load properly.

Obviously the fix for this is just to remove that bit from the config file, and it would have taken us about twenty seconds to do so - if PulseAudio actually built in F17. Unfortunately it doesn't, for an entirely different reason: F17 includes GCC 4.7, and PA's source needs tweaks to compile with GCC 4.7. We couldn't get the tweaks figured out in time for Alpha, so we couldn't do a new build of PA with the appropriate config file change to make it work in the new, ConsoleKit-less world. The workaround is simply to take the relevant bit out of the config file yourself once Fedora's installed.

creataphysics: it's not worth reporting your Shell issue, no, because the i8xx cards are fundamentally considered incapable of properly rendering Shell, and that's why they're blacklisted. Neither the GNOME team nor the X.org devs consider it possible to 'fix' Shell rendering on the i8xx cards, so there's no point reporting a bug for 'Shell doesn't render correctly on i8xx'.

What you should be able to do with F17 is use software rendering to get Shell on your system. The way to test that is not to de-blacklist your card, but to run Shell in a way that forces software rendering:

LIBGL_ALWAYS_SOFTWARE=1 gnome-shell --replace

So far, though, testing is indicating that performance isn't entirely up to snuff yet, so if you have a somewhat older CPU (which, if you have an i8xx graphics card, seems very likely), you might find it's just not fast enough to be usable. Ajax is hopeful that he can improve things before release, and we'll probably have a test day to try and get a more organized picture of performance on different CPUs.

Your case is a bit of a corner case that hasn't entirely been figured out yet - you have an adapter that has a hardware-accelerated driver which is considered not capable of running Shell and blacklisted. The ultimate intention is that you should automatically get software rendering of Shell in this case, but that hasn't been wired up yet, because it actually turns out to be rather difficult to do without preventing hardware acceleration from being used for things you actually want it to be used for (like games). There's some discussion of this in a thread named "A question about "Software rendering for gnome-shell"" on the test list. So for right now, this is one of the few cases which still gets the fallback mode by default.

[AdamW]

bob: it's pretty easy to avoid the 'anaconda explodes if you have a non-RH distro installed' bug - just use the updates.img linked from the common bugs page. It does work, multiple testers have verified it.

For those of you having issues with nouveau and display corruption, what adapter do you have? An FX 5xxx by any chance?

[tox]

bob: it's pretty easy to avoid the 'anaconda explodes if you have a non-RH distro installed' bug - just use the updates.img linked from the common bugs page. It does work, multiple testers have verified it.

For those of you having issues with nouveau and display corruption, what adapter do you have? An FX 5xxx by any chance?

my problem is with Nouveau,, trying to boot a LiveCD all i get a DRM - Nouveau Video Corruption / my Vid Adaptor is a Geforce 550ti 1Gig Ram . Fedora16 works , F17 dont

[AdamW]

hum, that's a different bug from the one I was thinking of, then. have you reported it to bugzilla.redhat.com yet? if not, can you do so, against the xorg-x11-drv-nouveau component, and let me know the bug number? thanks!

[tox]

hum, that's a different bug from the one I was thinking of, then. have you reported it to bugzilla.redhat.com yet? if not, can you do so, against the xorg-x11-drv-nouveau component, and let me know the bug number? thanks!
as soon as i figure out how im gonna get that log i will. ( i dont use VM's )

[AdamW]

can you hit ctrl-alt-f2 to get to a console, maybe?

[tox]

can you hit ctrl-alt-f2 to get to a console, maybe?

i'll try that tomorrow

[Dan]

Posting from Alpha RC3~4 LiveCD in the Fukushima Special (HP dv9904ca) now. So far ... so good. No vunderborks detected. Theme's as ugly as a mud fence ... but that's to be expected. <..:p..>


EDIT: The wallpaper, on the other hand, is really nice.

[liveuser@localhost ~]$ uname -a
Linux localhost.localdomain 3.3.0-0.rc3.git7.2.fc17.x86_64 #1 SMP Fri Feb 17 18:55:53 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[liveuser@localhost ~]$


[liveuser@localhost ~]$ lspci
00:00.0 RAM memory: nVidia Corporation MCP67 Memory Controller (rev a2)
00:01.0 ISA bridge: nVidia Corporation MCP67 ISA Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP67 SMBus (rev a2)
00:01.2 RAM memory: nVidia Corporation MCP67 Memory Controller (rev a2)
00:01.3 Co-processor: nVidia Corporation MCP67 Co-processor (rev a2)
00:02.0 USB Controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller (rev a2)
00:02.1 USB Controller: nVidia Corporation MCP67 EHCI USB 2.0 Controller (rev a2)
00:04.0 USB Controller: nVidia Corporation MCP67 OHCI USB 1.1 Controller (rev a2)
00:04.1 USB Controller: nVidia Corporation MCP67 EHCI USB 2.0 Controller (rev a2)
00:06.0 IDE interface: nVidia Corporation MCP67 IDE Controller (rev a1)
00:07.0 Audio device: nVidia Corporation MCP67 High Definition Audio (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP67 PCI Bridge (rev a2)
00:09.0 IDE interface: nVidia Corporation MCP67 AHCI Controller (rev a2)
00:0a.0 Ethernet controller: nVidia Corporation MCP67 Ethernet (rev a2)
00:0c.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2)
00:0d.0 PCI bridge: nVidia Corporation MCP67 PCI Express Bridge (rev a2)
00:12.0 VGA compatible controller: nVidia Corporation C67 [GeForce 7150M / nForce 630M] (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
02:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
02:05.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
02:05.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
02:05.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)
03:00.0 Network controller: Broadcom Corporation BCM4321 802.11a/b/g/n (rev 03)
[liveuser@localhost ~]$

[smr54]

Great idea. I really do seem to remember the last two alphas being pretty trouble free, so this way, folks might avoid surprises.

[Dan]

Whoops! May have spoken too soon. Adam, keyboard screenshots is flakey. Might be a SNAFU with running the liveCD on a laptop, thereby requiring an extra keystroke, but it pretty much took an act of congress to get this screenshot taken. The lack of GIMP on the CD was a PITA too. <..:dis:..>

[AdamW]

dan: can't you just run gnome-screenshot like any other app? just hit Start and type 'screens' and it should be there. but yeah, i've found the key seems a bit flaky, though I haven't figured out why. For a while it was giving me a keybinding error. Now it seems to cause a sort of 'shutter effect' but not actually pop up gnome-screenshot...

[Dan]

The regular application from the menu works fine. It's just the keyboard function that either lags or completely ignores the keystrokes. Loading in the big desktop now. I'll test it there when it's up.

Ayup. It's weird in the desktop. too. A whole screen grab works ok, but a single window won't take at all.

So ...

[liveuser@localhost ~]$ lspci
00:00.0 Host bridge: ATI Technologies Inc RD790 Northbridge only dual slot PCI-e_GFX and HT3 K8 part
00:02.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (external gfx0 port A)
00:04.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port A)
00:05.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port B)
00:07.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port D)
00:09.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port E)
00:0a.0 PCI bridge: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port F)
00:11.0 SATA controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode]
00:12.0 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.1 USB Controller: ATI Technologies Inc SB7x0 USB OHCI1 Controller
00:12.2 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.1 USB Controller: ATI Technologies Inc SB7x0 USB OHCI1 Controller
00:13.2 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3c)
00:14.1 IDE interface: ATI Technologies Inc SB7x0/SB8x0/SB9x0 IDE Controller
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: ATI Technologies Inc SB7x0/SB8x0/SB9x0 LPC host controller
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:14.5 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Link Control
01:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce GTS 250] (rev a2)
02:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)
03:00.0 IDE interface: Marvell Technology Group Ltd. Device 91a3 (rev 11)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
06:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03)
06:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 03)
07:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)
[liveuser@localhost ~]$

[creataphysics]

@AdamW - Running LIBGL_ALWAYS_SOFTWARE=1 gnome-shell --replace fixed my issue. To think it was so simple. Thanks a bunch!

I understand why you'd think I had all crappy hardware since my graphics card is old, but about 10 years ago this was a high end performance machine. I have 2gb of ram and a 3.2ghz pentium 4 ht, so everything runs perfectly, it's just this old graphics card slowing me down.

I noticed that I have to keep the terminal open to run the shell, is there any way to make this all automatic?

Also I get these errors when I run that command in the terminal:


[matthew@Hal9000 ~]$ LIBGL_ALWAYS_SOFTWARE=1 gnome-shell --replace

Gvc-WARNING **: Failed to connect context: Connection refused
Window manager warning: Log level 16: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Faile d: An authentication agent already exists for the given subject
Window manager warning: Log level 16: Error registering polkit authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Faile d: An authentication agent already exists for the given subject (polkit-error-quark 0)
JS LOG: GNOME Shell started at Wed Feb 29 2012 15:40:05 GMT-0600 (CST)

Gvc-WARNING **: Failed to connect context: Connection refused
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-DEBUG: Connecting to session manager

[DBelton]

Yikes.. Made the mistake of installing the alpha today. :(

No screenshot using key combination as Dan mentioned above.

Gnome shell crashes randomly when I hit the upper left hot corner.

The wacom settings in gnome control center tell me I don't have a wacom tablet when I do and it is recognized and usable in every other application.

And I agree with Dan.. Nice background, but butt ugly theme. :p

Blah.. I also have to try and remember what I did in F16 to get decent looking fonts, too. I'm back to crappy fonts :(

[tox]

Yikes.. Made the mistake of installing the alpha today. :(

No screenshot using key combination as Dan mentioned above.

Gnome shell crashes randomly when I hit the upper left hot corner.

The wacom settings in gnome control center tell me I don't have a wacom tablet when I do and it is recognized and usable in every other application.

And I agree with Dan.. Nice background, but butt ugly theme. :p

Blah.. I also have to try and remember what I did in F16 to get decent looking fonts, too. I'm back to crappy fonts :(

show how sexy the theme looks

[enderandrew]

I've tried to upgrade from F16 to F17 following these instructions:

http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_16_-.3E_Fedora_17

"yum --releasever=17 --disableplugin=presto --skip-broken distro-sync" fails for me with:


Total size: 178 M
Is this ok [y/N]: y
Downloading Packages:
Running Transaction Check
ERROR with transaction check vs depsolve:
rpmlib(X-CheckUnifiedSystemdir) is needed by setup-2.8.48-1.fc17.noarch
rpmlib(X-CheckUnifiedSystemdir) is needed by filesystem-3-2.fc17.x86_64
xorg-x11-font-utils is needed by ghostscript-fonts-5.50-28.fc17.noarch
Please report this error in http://yum.baseurl.org/report
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
ghostscript-fonts-5.50-27.fc16.noarch has missing requires of xorg-x11-font-utils
Your transaction was saved, rerun it with: yum load-transaction /tmp/yum_save_tx-2012-02-29-18-51JSMok3.yumtx

[Apostate]

After sorting out the sound bug my f17 is running quite smoothly at present. Using the XFCE desktop :D

[AdamW]

creataphysics: you could set something up to export LIBGL_ALWAYS_SOFTWARE=1 system-wide at boot time...I'm not actually sure what's the Official Best Way to do that, but it may be via a script in /etc/profile.d, I guess.

[AdamW]

I've tried to upgrade from F16 to F17 following these instructions:

http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_16_-.3E_Fedora_17

"yum --releasever=17 --disableplugin=presto --skip-broken distro-sync" fails for me with:


Total size: 178 M
Is this ok [y/N]: y
Downloading Packages:
Running Transaction Check
ERROR with transaction check vs depsolve:
rpmlib(X-CheckUnifiedSystemdir) is needed by setup-2.8.48-1.fc17.noarch
rpmlib(X-CheckUnifiedSystemdir) is needed by filesystem-3-2.fc17.x86_64
xorg-x11-font-utils is needed by ghostscript-fonts-5.50-28.fc17.noarch
Please report this error in http://yum.baseurl.org/report
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
ghostscript-fonts-5.50-27.fc16.noarch has missing requires of xorg-x11-font-utils
Your transaction was saved, rerun it with: yum load-transaction /tmp/yum_save_tx-2012-02-29-18-51JSMok3.yumtx

Did you miss the 'yum --releasever=17 update rpm dracut' step?

[AdamW]

Yikes.. Made the mistake of installing the alpha today. :(

No screenshot using key combination as Dan mentioned above.

Gnome shell crashes randomly when I hit the upper left hot corner.

The wacom settings in gnome control center tell me I don't have a wacom tablet when I do and it is recognized and usable in every other application.

And I agree with Dan.. Nice background, but butt ugly theme. :p

Blah.. I also have to try and remember what I did in F16 to get decent looking fonts, too. I'm back to crappy fonts :(

Did you file the Shell crash? Is this in a VM or on metal? If metal, what graphics card? Thanks!

[DBelton]

Did you file the Shell crash? Is this in a VM or on metal? If metal, what graphics card? Thanks!


It is a bare metal install with Intel G31 graphics. I haven't been able to get it to crash again since I rebooted after a full update, though. So maybe it was just a fluke.

I will say that this was one of the smoothest installs I have done, though.

I pulled a 500GB drive off the shelf, threw Windows 7 on it, then went about installing F17. The install went smooth, picked up the Win7 install and set grub2 up properly to boot both Win7 and F17. I have had smooth installs with Windows XP before, but with Win7 it's usually not so trouble free. Usually something gets glitched in the install and Windows 7 won't boot or it takes some fiddling around with the grub config. So, I do give the anaconda team a big congrats :)

Edit:

Now I have to wipe and de-cootify my drive after installing Windows on it :lol:

[AdamW]

we actually just let grub2 do the job of detecting and booting existing OSes. so your congrats should be directed to the grub developers, not the anaconda team :)

[DBelton]

Well, I spoke too soon :(

I am still getting crashes when I hit the upper left hotcorner in Gnome 3 shell :(

I haven't been able to pin it down as to what causes it, though. It appears to happen at random times.

I will try and gather more information and file a bug report on this one.

[kkshethin]

1. Installed alpha f17_64_live in virtualbox. ok
2. updated- error- run with skip-broken- 28 packages prevented from update
3. updated again-ok
4. installed kernel-devel, kernel-headers, gcc, dkms-ok
5. installed virtualboxguestadditions-ok
6. fullscreen not working, laptop display is 1366*768, detected 1024*768. (may be virtualbox problem?)
7. everything is running slower, due to debugging mode-correct?

[tox]

1. Installed alpha f17_64_live in virtualbox. ok
2. updated- error- run with skip-broken- 28 packages prevented from update
3. updated again-ok
4. installed kernel-devel, kernel-headers, gcc, dkms-ok
5. installed virtualboxguestadditions-ok
6. fullscreen not working, laptop display is 1366*768, detected 1024*768. (may be virtualbox problem?)
7. everything is running slower, due to debugging mode-correct?

if i recall i had the same problem on a Nightly that kinda worked - 6

i do believe if ddebugging Mode is on, it'll make the system slow - 7

[DBelton]

Well, I have narrowed down my problem a little.

If I have my wacom tablet plugged in, I get constant crashes in th gnome-settings-daemon.

If I have the wacom tablet plugged in when I start Gnome shell, it gives me the big fail screen and won't start Gnome shell. If I start Gnome shell, and then plug in the tablet it works.

The .xsession-errors file when I try to start Gnome shell with teh tablet plugged in:



GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)

GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)

GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)

GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)

GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)

GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0)
GNOME_KEYRING_CONTROL=/tmp/keyring-fFJIL5
GNOME_KEYRING_CONTROL=/tmp/keyring-fFJIL5
SSH_AUTH_SOCK=/tmp/keyring-fFJIL5/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-fFJIL5
SSH_AUTH_SOCK=/tmp/keyring-fFJIL5/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-fFJIL5
SSH_AUTH_SOCK=/tmp/keyring-fFJIL5/ssh
GPG_AGENT_INFO=/tmp/keyring-fFJIL5/gpg:0:1

** WARNING **: Tablet 'usb:056a:0015' has no buttons defined, do something!

** WARNING **: Tablet 'usb:056a:0014' has no buttons defined, do something!

** WARNING **: Tablet 'usb:056a:0013' has no buttons defined, do something!

wacom-plugin-WARNING **: Failed to create fallback wacom device for '/dev/input/event6': Device '/dev/input/event6' is not a tablet (2)

wacom-plugin-WARNING **: Failed to get value for changed stylus ID on device '13

wacom-plugin-CRITICAL **: gsd_wacom_stylus_get_name: assertion `GSD_IS_WACOM_STYLUS (stylus)' failed

wacom-plugin-CRITICAL **: gsd_wacom_stylus_get_settings: assertion `GSD_IS_WACOM_STYLUS (stylus)' failed

GLib-GIO-CRITICAL **: g_settings_get_value: assertion `G_IS_SETTINGS (settings)' failed

GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed

GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed

GLib-CRITICAL **: g_variant_get_fixed_array: assertion `g_variant_is_of_type (value, G_VARIANT_TYPE_ARRAY)' failed

GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed

wacom-plugin-ERROR **: Pressurecurve requires 4 values.
gnome-session[3954]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-Message: Failed to load module "pk-gtk-module"
Initializing nautilus-open-terminal extension
Initializing nautilus-sound-converter extension
Failed to play sound: File or data not found
** Message: applet now removed from the notification area

libnotify-WARNING **: Failed to connect to proxy

** WARNING **: Tablet 'usb:056a:0015' has no buttons defined, do something!

** WARNING **: Tablet 'usb:056a:0014' has no buttons defined, do something!

** WARNING **: Tablet 'usb:056a:0013' has no buttons defined, do something!

wacom-plugin-WARNING **: Failed to create fallback wacom device for '/dev/input/event6': Device '/dev/input/event6' is not a tablet (2)

wacom-plugin-WARNING **: Failed to get value for changed stylus ID on device '13

wacom-plugin-CRITICAL **: gsd_wacom_stylus_get_name: assertion `GSD_IS_WACOM_STYLUS (stylus)' failed

wacom-plugin-CRITICAL **: gsd_wacom_stylus_get_settings: assertion `GSD_IS_WACOM_STYLUS (stylus)' failed

GLib-GIO-CRITICAL **: g_settings_get_value: assertion `G_IS_SETTINGS (settings)' failed

GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed

GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed

GLib-CRITICAL **: g_variant_get_fixed_array: assertion `g_variant_is_of_type (value, G_VARIANT_TYPE_ARRAY)' failed

GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed

wacom-plugin-ERROR **: Pressurecurve requires 4 values.
gnome-session[3954]: WARNING: App 'gnome-settings-daemon.desktop' respawning too quickly
gnome-session[3954]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal
Initializing nautilus-search-tool extension
Initializing nautilus-image-converter extension
JS LOG: GNOME Shell started at Fri Mar 02 2012 21:22:14 GMT-0600 (CST)
JS ERROR: !!! Exception was: Error: Error invoking TelepathyGLib.prepare_finish: The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files
JS ERROR: !!! lineNumber = '0'
JS ERROR: !!! fileName = '"gjs_throw"'
JS ERROR: !!! stack = '"("Error invoking TelepathyGLib.prepare_finish: The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files")@gjs_throw:0
([object _private_TelepathyGLib_AccountManager],[object _private_Gio_SimpleAsyncResult])@/usr/share/gnome-shell/js/ui/telepathyClient.js:302
wrapper([object _private_TelepathyGLib_AccountManager],[object _private_Gio_SimpleAsyncResult])@/usr/share/gjs-1.0/lang.js:167
"'
JS ERROR: !!! message = '"Error invoking TelepathyGLib.prepare_finish: The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files"'

folks-WARNING **: Error preparing Backend 'telepathy': The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files
** Message: applet now embedded in the notification area

folks-WARNING **: Failed to find primary PersonaStore with type ID 'eds' and ID 'system'.
Individuals will not be linked properly and creating new links between Personas will not work.
The configured primary PersonaStore's backend may not be installed. If you are unsure, check with your distribution.


So, Possibly I have enough to file a decent bug report now.

[Dutchy]

I am getting pretty excited about Fedora 17!
Let's hope all the features make it to the final.

Top features for desktop users of Fedora 17 (http://www.linuxbsdos.com/2012/02/29/top-features-for-desktop-users-of-fedora-17/)

Fedora 17 feature list wiki (http://fedoraproject.org/wiki/Releases/17/FeatureList)

Has anyone successfully used the firewalld tray applet already?
Mine keeps crashing :(

[DBelton]

I'm getting the same thing here. The firewalld applet crashes.

in my .xsession-errors file:

St-CRITICAL **: _st_paint_shadow_with_opacity: assertion `shadow_spec != NULL' failed
/usr/lib64/python2.7/site-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed
import gobject._gobject
Traceback (most recent call last):
File "/usr/bin/firewall-applet", line 267, in right_menu_cb
self.statusicon, button, time)
File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 1381, in popup
self.popup_for_device(None, parent_menu_shell, parent_menu_item, func, data, button, activate_time)
AttributeError: 'Menu' object has no attribute 'popup_for_device'
ABRT service is not running

Clutter-WARNING **: The meta of type 'StScrollViewFade' with name 'vfade' is not attached to the actor 'notification-scrollview'
abrt-applet: waitpid: No child processes


and abrt gives me this:

abrt_version: 2.0.7
cmdline: /usr/bin/python /usr/bin/firewall-applet
comment: crash when running firewalld applet
executable: /usr/bin/firewall-applet
kernel: 3.3.0-0.rc5.git3.1.fc17.x86_64
reason: Gtk.py:1381:popup:AttributeError: 'Menu' object has no attribute 'popup_for_device'
time: Sat 03 Mar 2012 07:50:53 AM CST
uid: 1000
username: Me

backtrace:
:Gtk.py:1381:popup:AttributeError: 'Menu' object has no attribute 'popup_for_device'
:
:Traceback (most recent call last):
: File "/usr/bin/firewall-applet", line 267, in right_menu_cb
: self.statusicon, button, time)
: File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 1381, in popup
: self.popup_for_device(None, parent_menu_shell, parent_menu_item, func, data, button, activate_time)
:AttributeError: 'Menu' object has no attribute 'popup_for_device'
:
:Local variables in innermost frame:
:parent_menu_item: None
:activate_time: 36696332L
:parent_menu_shell: None
:button: 3L
:func: <function position_function at 0x127d5f0>
:data: <StatusIcon object at 0x1275d70 (GtkStatusIcon at 0x1300680)>
:self: <Menu object at 0x1288190 (GtkMenu at 0x149f040)>

[tox]

I am getting pretty excited about Fedora 17!
Let's hope all the features make it to the final.

Top features for desktop users of Fedora 17 (http://www.linuxbsdos.com/2012/02/29/top-features-for-desktop-users-of-fedora-17/)

Fedora 17 feature list wiki (http://fedoraproject.org/wiki/Releases/17/FeatureList)

Has anyone successfully used the firewalld tray applet already?
Mine keeps crashing :(

i wouldnt be surprised if Gnome-shell software rendering doesnt make it

[Dutchy]

Isn't that already in it?
It is runs the shell in virtualbox without the guest additions installed.

[tox]

Isn't that already in it?
It is runs the shell in virtualbox without the guest additions installed.

its not completely finished feature yet so whether it makes it by the feature freeeze deadline i dunno

[weitjong]

I have F17 in KVM/Qemu with Gnome-shell running. So, the software rendering does work...... well to a certain extent. The only caveat is I have to switch to "cirrus" instead of "qxl" which would give me higher resolution option. But with the 'qxl' video, the Gnome-shell crashes like hell (in a few resolution settings that I have tried). The F17 Gnome-shell is much more stable when I use "cirrus".

Still, my F17 system seems to have a broken event handler for vertical scroller. Both vertical scrollers in my mouse and my Multimedia keyboard do not work properly. Both scrollers do not generate any events (observed using xev).

[zuser]

Installed RC4 lLive KDE-64 on my older Acer with amd 3600+ and nvidia gforce 9400.
I put root on 60 gb ssd and /tmp, /var, /home on 320 gb hd.

Also did initial 180+ file update and at 1st glace all seems ok. Did have minor issue on 1st start after downloading Chrome from google but seems to have sorted itself after big upgrade.

Nouveau driver working also , so will probably keep at least for a while rather than trying to install latest nvidia driver.

[AdamW]

weitjong: yeah, I've noticed both of those too. I've marked the constant crashing of Shell in spice/qxl VMs as a Beta blocker, so I'm hoping it'll get fixed soon. The vertical scroll thing isn't really critical enough to be a blocker, but it is annoying. I haven't filed a bug on that one yet, have you?

[weitjong]

Adam: thanks for confirming that I am not the only one. I have filed the vertical scroll issue. https://bugzilla.redhat.com/show_bug.cgi?id=800550
Cheers.