Today's update prevents graphic shutdown
by Antonio M
here again...another cyclic bug.
If you click on the gdm window there is no way to shutdown your
machine...you get the message failed to stop computer!!!!!!
--
Antonio Montagnani
Skype : antoniomontag
14 years, 6 months
Login as root is impossible
by Antonio M
After latest updates from gdm there is no way to log as root!!!!!
I am pretty sure as I can su or start any application requiring root
privilege....so....what is going on?? shall I file a bug???
--
Antonio Montagnani
Skype : antoniomontag
14 years, 6 months
yum update ==> paperweight :-)
by Tom Horsley
Just grabbed a slew of updates from rawhide for my F10 alpha
partition, and now F10 alpha has been rendered a paperweight.
Any attempt to login (as any user, not just root) reports failed
to authenticate user, and after the first login attempt, the
USB keyboard also stops working.
I can use the accessibility stuff to bring up the onscreen
keyboard (the mouse is still working) and try to login with it,
but it still says failed to authenticate.
When I give up and try to press restart or shutdown button,
I get an instant popup saying restart or shutdown failed, so
the only way to recover (that I've found so far) is to hit
the reset button.
I tried booting the old kernel, but all the same symptoms
persist, so it was one of the other updates that did me in,
but there were so many of them, I have no way to guess which
one might be the culprit (which makes it hard to submit
a bugzilla, since I haven't got the slightest clue what
component to report against).
I'm off to try runlevel 3 and see if I can authenticate any
user in console mode (if that works, at least I'll be able
to get new updates :-).
14 years, 6 months
strange behaviour of kernel 2.6.26.3-29.fc9.i686
by Adrin Jalali
Hi there,
I have still problems with this new kernel. If I remove the quiet tag on the
boot, the kernel will boot normally and fast, but while booting quiet,
booting the kernel will take long time and I found that if I press my laptop
power button at that time, kernel will boot almost instantly.
Any ideas?
Best,
Adrin.
14 years, 6 months
Sunday's Rawhide Install Fails looking for repmod.xml
by Chuck Forsberg WA7KGX
I used Sunday's x86_64 boot.iso with the tagline "text askmethod".
Things proceeded normally until the installer failed with the complaint
that repmod.xml was missing.
While still in the installation environment I was able to switch terminals,
mount the NFS share I with the Rawhide tree and browse it.
Still in the installation environment I was able to ssh into
my server and determine there is no repmod.xml anywhere
on the system
I also noticed there was no ext4 option in the disk setup menu.
--
Chuck Forsberg caf(a)omen.com www.omen.com 503-614-0430
Developer of Industrial ZMODEM(Tm) for Embedded Applications
Omen Technology Inc "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231 FAX 629-0665
14 years, 6 months
Re: updated to KDE 4.1 (Fedora 9 x86_64 on Acer TravelMate 6291 Laptop)
by yunus
> yunusf9 tester <yunus.tji.nyan <at> gmail.com> writes:
> > After doing
> > #yum update
> > last night (12 Sep 08), It showed me the same problem.
>
> su -c "yum install phonon-backend-xine"
> Does it still happen then?
>
> As the notes for the update say:
> NOTE: Users of previous KDE 4.1.0 packages from updates-testing should "yum
> install phonon-backend-xine" which is now the default Phonon backend again.
> (When upgrading from KDE 4.0.x, yum will pick the right one by default.)
>
> Kevin Kofler
>
su -c 'yum --enablerepo=updates-testing-newkey update'
bring me to KDE 4.1.1, but I still faced the same problem.
After applying
su -c 'yum install phonon-backend-xine'
the problem disappeared
Thanks Kevin
yunus
14 years, 6 months
Need help testing updates transition for 8 and 9
by Jesse Keating
We're quite close to releasing the transition fedora-release package to
bring users of Fedora 8 and Fedora 9 to the new updates location with
the new key. However we're seeing some mixed results in our limited
testing and thus we'd like to open it for a wider testing audience.
In particular we're looking for users of PackageKit on Fedora 9 to test
this, as our yum and pirut results have been pretty rock solid.
To test, you will need to modify your fedora-updates.repo file in the
[updates] section, comment out the mirrorlist url, uncomment the baseurl
line and make the line read:
baseurl=http://kojipkgs.fedoraproject.org/mash/updates/f$releasever-updat...
(note, if you have updates-testing enabled, you should disable it during this test)
Save the file and initiate an update with PackageKit (System ->
Administration -> Update System)
This should show you 5 or so updates:
fedora-release
PackageKit-*
unique
gnome-packagekit
Once these updates are installed, you'll have a new set of .repo files,
fedora-updates(-testing)-newkey.repo. These repo files will be pointing
you to mirror manager to find mirrors that have all the newly resigned
updates as well as some new updates you haven't seen before. PackageKit
should automatically notice these updates a few minutes after installing
the previously mentioned 5 or so updates, and prompt you to install the
rest of them.
This is where things get dicey. Once PackageKit downloads all your
updates, you'll be prompted to import a new key (see
https://fedoraproject.org/keys for currently used keys). After clicking
yes to import the key (after you verified it) the PackageKit dialog will
disappear while it does the import, and it should come back, or at least
the panel icon will come back to indicate that it is trying once again
to install your updates. The update installation /should/ succeed,
that's what we're looking for.
You can monitor all of this activity with 'pkmon' on the terminal, which
is a good idea because if it fails for you in some way, the output from
pkmon during the failure will be important to resolving the issue.
Please keep good notes if you experience failures and capture
screenshots.
Known problems resemble something like
http://togami.com/~warren/temp/policykit-error.png or
https://bugzilla.redhat.com/show_bug.cgi?id=461553
Thanks everybody for the testing!
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
14 years, 6 months
Cannot grant PolicyKit authorizations
by Andrew Farris
Hey folks,
I just got an install of rawhide done and configuring it using much of
my previous home directory. I've got a problem with policykit
authorizations though... I can't grant them to any users.
I've tried with a fresh user, and my main user, and polkit-gnome-
authorization does nothing when I try to grant an authorization, it
just has a disabled 'grant' button in the dialog after choosing a user
and limits for the authorization.
All I'm getting from packagekit is a denied access dialog, no offer to
let me grant authorization (no dialog to use root credentials to grant
auth for a user?) for updates or new software installs.
Any chance this is effected by my old home directory (unlikely, it
happens for a fresh user as well)? Does anyone else see this, and did
I miss a bug or other mention of this?
Andrew Farris <lordmorgul(a)gmail.com>
gpg 0x8300BF29 fingerprint 071D FFE0 4CBC 13FC 7DEB 5BD5 5F89 8E1B
8300 BF29
http://www.lordmorgul.net
14 years, 6 months
FC9 GNOME Error and KDE Wireless Failure
by James J Catchpole
When I updated my FC9 System to reflect the
latest updates I had the Following Issues; I don't
know if they have been reported before.
GNOME Startup:
There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not work
correctly.
The last error message was:
Message did not receive a reply (timeout by message bus)
GNOME will still try to restart the Settings Daemon next time you log in.
KDE 4.11 Startup:
KDE was unable to initiate my Wireless Connection. I was unable to use
the Network Manager Tools or Network Configuration Tools. Wireless
works fine with GNOME.
Kernel; kernel-2.6.26.3-29.fc9.i686
KDE: kdebase-4.1.1-1.fc9.i386
Lenovo (IBM) T60
Jim
fedora-test-list-request(a)redhat.com wrote:
> Send fedora-test-list mailing list submissions to
> fedora-test-list(a)redhat.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www.redhat.com/mailman/listinfo/fedora-test-list
> or, via email, send a message with subject or body 'help' to
> fedora-test-list-request(a)redhat.com
>
> You can reach the person managing the list at
> fedora-test-list-owner(a)redhat.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of fedora-test-list digest..."
>
>
> Today's Topics:
>
> 1. Re: kmod-nvidia for kernel-2.6.26.3-14.fc8 (Thorsten Leemhuis)
> 2. Re: updated to KDE 4.1 (Fedora 9 x86_64 on Acer TravelMate
> 6291 Laptop) (Kevin Kofler)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 13 Sep 2008 14:16:34 +0200
> From: Thorsten Leemhuis <fedora(a)leemhuis.info>
> Subject: Re: kmod-nvidia for kernel-2.6.26.3-14.fc8
> To: For testers of Fedora Core development releases
> <fedora-test-list(a)redhat.com>
> Message-ID: <48CBAF22.8040408(a)leemhuis.info>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> On 12.09.2008 22:11, Mike wrote:
>
>> Does anyone know if a kmod-nvidia package is soon going to be available for
>> kernel-2.6.26.3-14.fc8? (Also for the new 2.6.26 kernel in f9?
>>
>
> A few hours after the buildsys for livna is up again. No ETA known yet
> when that will be the case, sorry. Hopefully soon.
>
> CU
> knurd
>
> P.S.: We'll hopefully have a more reliable setup soon for RPM Fusion
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 13 Sep 2008 12:20:11 +0000 (UTC)
> From: Kevin Kofler <kevin.kofler(a)chello.at>
> Subject: Re: updated to KDE 4.1 (Fedora 9 x86_64 on Acer TravelMate
> 6291 Laptop)
> To: fedora-test-list(a)redhat.com
> Message-ID: <loom.20080913T121742-374(a)post.gmane.org>
> Content-Type: text/plain; charset=us-ascii
>
> yunusf9 tester <yunus.tji.nyan <at> gmail.com> writes:
>
>> After doing
>> #yum update
>> last night (12 Sep 08), It showed me the same problem.
>>
>
> su -c "yum install phonon-backend-xine"
> Does it still happen then?
>
> As the notes for the update say:
> NOTE: Users of previous KDE 4.1.0 packages from updates-testing should "yum
> install phonon-backend-xine" which is now the default Phonon backend again.
> (When upgrading from KDE 4.0.x, yum will pick the right one by default.)
>
> Kevin Kofler
>
>
>
> ------------------------------
>
> --
> fedora-test-list mailing list
> fedora-test-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-test-list
>
> End of fedora-test-list Digest, Vol 55, Issue 35
> ************************************************
>
>
14 years, 6 months
Re: updated to KDE 4.1 (Fedora 9 x86_64 on Acer TravelMate 6291 Laptop)
by yunus
> yunusf9 tester <yunus.tji.nyan <at> gmail.com> writes:
> > phonon
> > The audio playback device HDA Intel (ALC268 Analog) does not work.
> > Falling back to HDA Intel (ALC268 Analog).
>
> That's probably the "Phonon does not default to PulseAudio" issue. We fixed
> that already, but we can't push the fix out due to the infrastructure outages.
>
> Kevin Kofler
Hi,
After doing
#yum update
last night (12 Sep 08), It showed me the same problem.
Now I am still trying to
#yum --enablerepo=updates-testing-newkey update
It seems that it will bring me to KDE 4.1.1
Do you think my problem has to do with Bug 455299
Thank you
yunus
14 years, 6 months
