Anyone else enjoying Rawhide?

[tbelvin]

Originally Posted by hadrons123

Time after time whenever I get the urge to kill my Fedora installation, I upgrade it to rawhide to see what new in there. Most of the times it won't boot or even if it does, too many apps crashed for no apparent reason. I wonder how some people really run rawhide all the time. Debian unstable is far more usable and stable than rawhide, I do understand that Debian unstable packages are older than Fedora release packages , but I have a working computer with Debian unstable which is usable. Debian has experimental too. But you cannot be running all your packages from experimental, you can only select a few packages which in a way looks lot sane way of experimenting packages.

Trying out the current Fedora release after Rawhide won't boot is always a surprise at how well everything works!

[dcharlespyle]

I'd try to enjoy it if I could get it to install without a hitch. So far I can't seem to get past a major SELinux error about not being able to find a suitable profile, which, following this, then gives me the choices of system maintenance, kernel panic or no firstboot and no user to login, and that is after fighting with all the dependency issues with shotwell and gvfs, and watching gpk-update-viewer fail repeatedly with the following:

GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk _5ftransaction_5ferror.Code21: Too many packages to process (2704/2500).

This then leaves my system in a partially upgraded state because when the program manages to run it forces a restart and/or logoff before the updating is finished.

I have tried every method given in the documentation on the wiki--to the letter--with no joy.

Well, there is one method I did not try and that was with a live cd. Maybe the eighth time is a charm? Maybe I just need to get some real rest and be fresh before trying this again.

[tbelvin]

I had a dependency problem with shotwell too, but I ignored it and Rawhide boots fine for me with a fresh install. I have gvfs installed without a dependency problem in Anaconda now. At the end of the install Anaconda seemed to hang after installing all the packages before installing the bootloader, but unplugging a replugging my internet connection seemed to wake it back up.

I also had no firstboot after login, but then again I relabled with SELinux right away, so maybe that threw it off. I just logged in as root and created my normal user instead of using firstboot.

I wish I was a programmer and could be more helpful.

[dcharlespyle]

Could you let me know whether or not Shotwell runs on your installation? I am now running Rawhide but I got to that point by removing it.

I did not do an Anaconda install. I used the gpk-update-viewer method. I could not get past that dependency error and do the update until I removed both Shotwell and gvfs.

Now that I want to reinstall those packages, I now get the same dependency error and the packages cannot be installed. I checked the directory where the requisite libraries are supposed to be. They are present and accounted for.

I am also getting another tainted kernel message from ABRT but running su -c 'dmesg | grep taints' shows nothing.

I also keep seeing the error from SELinux: "unable to find a usable policy file" at bootup. And, User Accounts STILL doesn't load without slamming the hard drive and killing System Settings. I have had the same problem since Fedora 17. This is even the case on a clean install of Fedora 17.

I am not enjoying Rawhide as yet but at least now I am running it.

[tbelvin]

Originally Posted by dcharlespyle

Could you let me know whether or not Shotwell runs on your installation? I am now running Rawhide but I got to that point by removing it.

I did not do an Anaconda install. I used the gpk-update-viewer method. I could not get past that dependency error and do the update until I removed both Shotwell and gvfs.

Now that I want to reinstall those packages, I now get the same dependency error and the packages cannot be installed. I checked the directory where the requisite libraries are supposed to be. They are present and accounted for.

I am also getting another tainted kernel message from ABRT but running su -c 'dmesg | grep taints' shows nothing.

I also keep seeing the error from SELinux: "unable to find a usable policy file" at bootup. And, User Accounts STILL doesn't load without slamming the hard drive and killing System Settings. I have had the same problem since Fedora 17. This is even the case on a clean install of Fedora 17.

I am not enjoying Rawhide as yet but at least now I am running it.

shotwell-0.12.3-1.fc18.x86_64 is installed by Anaconda, but running it I get: shotwell: error while loading shared libraries: libgphoto2.so.2: cannot open shared object file: No such file or directory. I tried removing shotwell to be installed with Anaconda, but it kept getting added back, eventhough it can be removed on its own in yum.

If I get a kernel crash warning with ABRT, but the kernel was listed as being tainted, it won't let me report the error. Sometimes I get random kernel crash warnings that seem to have no affect, or sometimes the kernel is listed as tainted. Maybe someone else can answer your question on those empty kernel crashes.

I also get the "unable to find usable policy file" with this fresh install of Rawhide while booting. I don't get any noticable problems after, but I did relable with SELinux, and later on after booting I see the SELinux policy loaded. Try permissive mode and seeing if setroubleshoot shows anything, or relabling.

[dcharlespyle]

It looks like the dependencies are missing from Rawhide. Shotwell expects certain versions of the libraries to be there and they are not there in the installation and cannot be found in the Rawhide repository--at least that it what the errors say during installation. The libraries just aren't there. In order for Shotwell to work in Fedora 18 Rawhide, I ended up having to copy the two libraries and their symbolic links to the /usr/lib64/ directory from an old Fedora 13 package. Installing the programs caused the error to continue to state that the requirements were not met. However, using rpm and forcing the installation made it install and it now works.

I also now know the cause of the tainted kernel error and the cause of my User Accounts woes. It is the linux firmware for cx18 television tuner devices. Either that, or it is the cx18 module itself when the kernel loads it. I am not sure why that it but I confirmed it by multiple times installing and uninstalling the Hauppauge firmware for cx18. When it is not installed in the /usr/lib/firmware directory, User Accounts loads just fine and there is no tainted kernel error generated and caught by ABRT.

When the firmware is in the directory, the network interface is delayed in its proper functionality, I get the tainted kernel errors, and User Accounts in System Settings fails to launch after slamming the processor and hard drive and filling memory to capacity.

I do not yet know or understand why that is but I am anxious to get to the bottom of it. It was never a problem on either Fedora 15 or Fedora 16, but on Fedora 17 and now 18 Rawhide, it is a serious problem potentially for any one with a Hauppauge HVR-1600 television tuner card installed in their systems.

Thing is, I never install the module for cx18. It just loads. It does not function properly without the firmware, however. But, for some odd reason, when the firmware is installed, something is interfered with in the kernel that affects User Accounts. Anyone else have any idea why that might be?

---------- Post added 4th August 2012 at 12:59 AM ---------- Previous post was 3rd August 2012 at 06:13 PM ----------

Originally Posted by tbelvin

If I get a kernel crash warning with ABRT, but the kernel was listed as being tainted, it won't let me report the error. Sometimes I get random kernel crash warnings that seem to have no affect, or sometimes the kernel is listed as tainted. Maybe someone else can answer your question on those empty kernel crashes.

I only see the ABRT crash warnings about a tainted kernel on kernel 3.6.0-x. I did not see them on previous kernels with the exception of 3.5.0-1. I am not yet sure why that is. I, too, do not get the option to report the errors relating to the kernel. What is maddening is that dmesg | grep taints reveals nothing about what is going on but dmesg | grep tainted gives me this:

$ dmesg | grep tainted
[    5.181219] Pid: 162, comm: usb-storage Not tainted 3.6.0-0.rc0.git9.3.fc18.x86_64 #1

I have never seen this "error" on any previous Fedora installation but only on Rawhide.

I am also experiencing various keychain errors when I do try to report some errors and crashes I have been experiencing with Rawhide. Sometimes, I am asked for and can provide my password to unlock the keychain, but at other times this does not work, I cannot authenticate, and then cannot send the crash data. So, I cannot report even half of the crashes and errors I have experienced other than anecdotally. That, of course, does not make for good troubleshooting and debugging so the developers can find and squash the bugs.

Holy crap! I can run Cheese in Rawhide! I haven't been able to run Cheese since Fedora 15. I wonder if the firmware situation also has something to do with that problem, too...

[dcharlespyle]

Confirmed. Having the cx18 firmware in /usr/lib/firmware also causes Cheese to fail. Taking the firmware files out of the directory results in Cheese working as programmed.

But, the question of the day is why it is that a bjorked Fedora 17 upgrade from Fedora 16 resulted in a working Cheese in spite of the firmware files being in the aforementioned directory.

[tbelvin]

Dunno, maybe the /usr move for F17 lets you have conflicting packages installed from F16.
http://fedoraproject.org/wiki/Features/UsrMove

Since you're running Rawhide, have you tried the latest git for LinuxTV?

git clone git://linuxtv.org/media_build.git
cd media_build
./build
make install

I got it to build on my Rawhide system, but I don't have the hardware or experience to help. Maybe someone else who uses LinuxTV can answer your questions.

[dcharlespyle]

Originally Posted by tbelvin

Dunno, maybe the /usr move for F17 lets you have conflicting packages installed from F16.
http://fedoraproject.org/wiki/Features/UsrMove

Since you're running Rawhide, have you tried the latest git for LinuxTV?

git clone git://linuxtv.org/media_build.git
cd media_build
./build
make install

I got it to build on my Rawhide system, but I don't have the hardware or experience to help. Maybe someone else who uses LinuxTV can answer your questions.

I have no development software installed on the system at the moment. I plan to do another reinstall in a day or so that will include the developer packages and try this suggestion. I am also thinking about swapping in another revision of the same card that has the problematic firmware to see what difference that might make.

But, why that firmware would cause problems in Cheese and User Accounts is another question. Maybe shared memory somewhere? If I can reallocate the memory used by the card it might solve the problem. Now, to find out which kernel flags I can use to do that for the pci card accessed by cx18.

[kellermanrivero]

I enjoy my rawhide instalation. Two pics :





My instalation running gnome shell

[flokip]

I dit a upgrade to rawhide. Used yum update --skip-broken --nogpgcheck to update.
Reboot stared in shell. startx worked to run GUI.
There was no sound.
Now F18 wont boot.

[errorxp]

I can't get cinnamon to install in f18. Too bad cos I really don't like any other DE out there.

[root@localhost user]# yum install cinnamon
Loaded plugins: fastestmirror, presto
Loading mirror speeds from cached hostfile
 * fedora: mirrors.linux.edu.lv
 * updates: www.nic.funet.fi
 * updates-testing: www.nic.funet.fi
Resolving Dependencies
--> Running transaction check
---> Package cinnamon.i686 0:1.5.2-8.fc18 will be installed
--> Processing Dependency: muffin(x86-32) >= 1.0.5 for package: cinnamon-1.5.2-8.fc18.i686
--> Processing Dependency: libmuffin.so.0 for package: cinnamon-1.5.2-8.fc18.i686
--> Processing Dependency: libcogl.so.9 for package: cinnamon-1.5.2-8.fc18.i686
--> Processing Dependency: dbus-python for package: cinnamon-1.5.2-8.fc18.i686
--> Running transaction check
---> Package cinnamon.i686 0:1.5.2-8.fc18 will be installed
--> Processing Dependency: libcogl.so.9 for package: cinnamon-1.5.2-8.fc18.i686
---> Package dbus-python.i686 0:1.1.1-1.fc18 will be installed
---> Package muffin.i686 0:1.0.6-3.fc18 will be installed
--> Processing Dependency: libcogl.so.9 for package: muffin-1.0.6-3.fc18.i686
--> Finished Dependency Resolution
Error: Package: cinnamon-1.5.2-8.fc18.i686 (updates-testing)
           Requires: libcogl.so.9
           Available: cogl-1.10.4-2.fc18.i686 (fedora)
               libcogl.so.9
           Installed: cogl-1.11.4-1.fc18.i686 (@updates-testing)
               Not found
Error: Package: muffin-1.0.6-3.fc18.i686 (fedora)
           Requires: libcogl.so.9
           Available: cogl-1.10.4-2.fc18.i686 (fedora)
               libcogl.so.9
           Installed: cogl-1.11.4-1.fc18.i686 (@updates-testing)
               Not found
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

[nonamedotc]

See this - http://forums.fedoraforum.org/showthread.php?t=284017

In particular, this - http://forums.fedoraforum.org/showpo...33&postcount=4

[hadrons123]

Leigh's packages have already reached the repos. One has to do a

yum clean all -y && yum install cinnamon -y

[errorxp]

The rpm-s in the post are for 64 bit, I have x86 arch in virtualbox.
Anyway the ones in the repo seem newer but I still get the same dependency error after running yum clean.
Nothing more to do than wait i guess