Re: fedora-list Digest, Vol 69, Issue 203

From: fedora-list-request@xxxxxxxxxx <fedora-list-request@xxxxxxxxxx>
Subject: fedora-list Digest, Vol 69, Issue 203
To: fedora-list@xxxxxxxxxx
Date: Sunday, November 29, 2009, 5:42 PM

Send fedora-list mailing list submissions to
    fedora-list@xxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
    https://www.redhat.com/mailman/listinfo/fedora-list
or, via email, send a message with subject or body 'help' to
    fedora-list-request@xxxxxxxxxx

You can reach the person managing the list at
    fedora-list-owner@xxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of fedora-list digest..."


Today's Topics:

   1. 1 update available and no updates available
      (Allan Dreyer Andersen)
   2. Re: 1 update available and no updates available (Steven Stern)
   3. Re: Default keyring for NetworkManager (Tom H)
   4. Re: 1 update available and no updates available
      (Allan Dreyer Andersen)
   5. error message in yum (Fran?ois Patte)
   6. Re: Problem wih Installation (Mahmoud Abou-Eita)
   7. Re: Emacs fonts in F12 (Neal Becker)
   8. Re: Problem wih Installation (Mikkel)
   9. Re: kerneloops eating up cpu (jackson byers)
  10. Upgrade from F11 to F12 - problem with LVM and raid (jaivuk)
  11. Re: Setting up a VM to run an F12 guest on an XP host
      (john wendel)
  12. f12 updates kernel nomodeset option breaks radeon (Skunk Worx)
  13. Re: Default keyring for NetworkManager (Marko Vojinovic)
  14. Re: Default keyring for NetworkManager (Marko Vojinovic)


----------------------------------------------------------------------

Message: 1
Date: Sun, 29 Nov 2009 23:08:31 +0100
From: Allan Dreyer Andersen <swoop@xxxxxxxx>
Subject: 1 update available and no updates available
To: Fedora - User List <fedora-list@xxxxxxxxxx>
Message-ID: <20091129230831.75d2940f@xxxxxxxx>
Content-Type: text/plain; charset=US-ASCII

Hi all

Behind this strange sounding subject is strange occurence for me.
I'm new to Fedora and have installed F12. All updates are installed by
few days ago I notice the normal 'Updates available' icon in my Gnome
menu.

If I click on the icon I get 'All software are updated' just a few
seconds later.

If I try to run 'yum upgrade' I get no packages marked for update'.

I'm using Danish localized version of Fedora so have tired to translate
back to English but is not sure above is the exact and correct sounding.

Am I doing something wrong here?


--
Venlig hilsen / Best regards
Allan Dreyer Andersen



------------------------------

Message: 2
Date: Sun, 29 Nov 2009 16:13:10 -0600
From: Steven Stern <subscribed-lists@xxxxxxxxxxxxx>
Subject: Re: 1 update available and no updates available
To: "Community assistance, encouragement,    and advice for using
    Fedora." <fedora-list@xxxxxxxxxx>
Message-ID: <4B12F1F6.7000700@xxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1

On 11/29/2009 04:08 PM, Allan Dreyer Andersen wrote:
> Hi all
>
> Behind this strange sounding subject is strange occurence for me.
> I'm new to Fedora and have installed F12. All updates are installed by
> few days ago I notice the normal 'Updates available' icon in my Gnome
> menu.
>
> If I click on the icon I get 'All software are updated' just a few
> seconds later.
>
> If I try to run 'yum upgrade' I get no packages marked for update'.
>
> I'm using Danish localized version of Fedora so have tired to translate
> back to English but is not sure above is the exact and correct sounding.
>
> Am I doing something wrong here?
>
>
Try "yum clean metadata" then "yum update"  (not "upgrade").

--

  Steve



------------------------------

Message: 3
Date: Sun, 29 Nov 2009 23:24:24 +0100
From: Tom H <tomh0665@xxxxxxxxx>
Subject: Re: Default keyring for NetworkManager
To: gayleard@xxxxxxxxxx, fedora-list@xxxxxxxxxx
Message-ID:
    <6d4219cc0911291424j6642e708w6c7fe609cf082d7b@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1

>> I got this to work myself. However, I think that the only way to both
>> autologin from gdm/kdm, and unlock the keyring, is to set an empty
>> password on your keyring.
>> Use seahorse to set a blank password on your keyring. If it won't let you,
>> delete your keyring completely. On the next login you'll be prompted to
>> create one, create it with a blank password.

> What can one do on a KDE system?
> As far as I can see, seahorse is a Gnome speciality.
> Would knetworkmanager be any help?

kwalletmanager



------------------------------

Message: 4
Date: Sun, 29 Nov 2009 23:25:15 +0100
From: Allan Dreyer Andersen <swoop@xxxxxxxx>
Subject: Re: 1 update available and no updates available
To: fedora-list@xxxxxxxxxx
Message-ID: <20091129232515.4bc69477@xxxxxxxx>
Content-Type: text/plain; charset=UTF-8

On Sun, 29 Nov 2009 16:13:10 -0600

Hi Steve

> Try "yum clean metadata" then "yum update"  (not "upgrade").
>

Thank you for quick answer.

Clean metadate gives:
Indlæste udvidelsesmoduler: presto, refresh-packagekit
32 metadata filer slettet
17 sqlite filer slettet
0 metadata filer slettet

And the 'yum update' gives no update available but the little orange
star still apears on my menu.


--
Venlig hilsen / Best regards
Allan Dreyer Andersen



------------------------------

Message: 5
Date: Sun, 29 Nov 2009 23:49:40 +0100
From: Fran?ois Patte <francois.patte@xxxxxxxxxxxxxxxxxxxx>
Subject: error message in yum
To: "Community assistance, encouragement,    and advice for using
    Fedora." <fedora-list@xxxxxxxxxx>
Message-ID: <4B12FA84.9090808@xxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bonsoir,

I am running f10.

trying to update I get this error message from yum:

ERREUR de résolution de dépendance par rpm_check_debug :
mono(Mono.Addins) is needed by f-spot-0.6.1.3-1.fc10.i386
mono(Mono.Addins.Gui) is needed by f-spot-0.6.1.3-1.fc10.i386
mono(Mono.Addins.Setup) is needed by f-spot-0.6.1.3-1.fc10.i386
Terminé !
(1, [u'Veuillez reporter cette erreur dans http://yum.baseurl.org/report'])


OK. There is some problem and I must report it there:
http://yum.baseurl.org/report

Going there, I don't understand where I can make a "report"...

thanks for lights.

- --
François Patte
UFR de mathématiques et informatique
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 4286 2145
http://www.math-info.univ-paris5.fr/~patte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAksS+oQACgkQdE6C2dhV2JV4ZACaAzhOaH+5npwixI4+OhSERzto
pQUAn1OlreUUINPcLrDqWoL4ccbw4wYH
=O233
-----END PGP SIGNATURE-----



------------------------------

Message: 6
Date: Sun, 29 Nov 2009 14:46:54 -0800
From: Mahmoud Abou-Eita <mahmoud.aboueita@xxxxxxxxx>
Subject: Re: Problem wih Installation
To: "Community assistance, encouragement,    and advice for using
    Fedora." <fedora-list@xxxxxxxxxx>
Message-ID:
    <29bf45d20911291446u24267e40ue3ed81b28afc4b4a@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Skipped content of type multipart/alternative-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 226 bytes
Desc: not available
Url : https://www.redhat.com/archives/fedora-list/attachments/20091129/f4048769/attachment.gif

------------------------------

Message: 7
Date: Sun, 29 Nov 2009 18:35:46 -0500
From: Neal Becker <ndbecker2@xxxxxxxxx>
Subject: Re: Emacs fonts in F12
To: fedora-list@xxxxxxxxxx
Message-ID: <hev0gi$u0s$1@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="ISO-8859-1"

Matthew Saltzman wrote:

> In F11, selecting the same font in Emacs as the system monospace
font
> (in my case, Monospace Regular 7-point) resulted in an Emacs window
with
> a typeface that looked the same as the one in a gnome-terminal.  In
F21,
> the same font looks (a) much smaller and (b) more widely spaced than
the
> gnome-terminal font (which looks the same as it did in F11).
>
> Any idea what changed in Emacs and how I can get the font I want?
>
> TIA.
>
emacs-23 happened.  Fonts are MUCH better.  Emacs can now use non-
bitmapped fonts.

Here are some suggestions:
1.
(cond
((display-graphic-p)
  (set-face-attribute 'default                nil :font "DejaVu Sans
Mono-9" :slant 'normal :weight 'normal)))

2. If you'd like to adjust font size using Ctrl-mouse wheel (like many
other apps):

(require 'zoom-frm)
(global-set-key (kbd "<C-mouse-5>") 'zoom-in)
(global-set-key (kbd "<C-mouse-4>") 'zoom-out)

For this you'll need:
zoom-frm.el
frame-fns.el
frame-cmds.el
You can find them all here: (e.g.)
http://www.emacswiki.org/emacs/zoom-frm.el



------------------------------

Message: 8
Date: Sun, 29 Nov 2009 17:36:36 -0600
From: Mikkel <mikkel@xxxxxxxxxxxxxxxx>
Subject: Re: Problem wih Installation
To: fedora-list@xxxxxxxxxx
Message-ID: <4B130584.8030404@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

On 11/29/2009 04:46 PM, Mahmoud Abou-Eita wrote:
> Thanks all, I burnt the 5 CDS, but when I boot from the CD-ROM nothing
> happens also. Windows loads just normally .
>  I'm downloading the Live cd!
>
Dumb questions:

- what is the boot order set up in your BIOS? Is it set to boot off
the hard drive as the first choice?

- can you hit a key during the boot process to let you select what
media to boot from?

- if you open the CD in Windows, do you see multiple files and
directories, or just one .iso file?

Mikkel
--

A:  Because it messes up the order in which people normally read text.
Q:  Why is top-posting a bad thing?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
Url : https://www.redhat.com/archives/fedora-list/attachments/20091129/d7596bbd/signature.bin

------------------------------

Message: 9
Date: Sun, 29 Nov 2009 15:54:25 -0800
From: jackson byers <byersjab@xxxxxxxxx>
Subject: Re: kerneloops eating up cpu
To: fedora-list@xxxxxxxxxx, byersjab <byersjab@xxxxxxxxx>
Message-ID:
    <3e5960ed0911291554q14ebdf4bw8b74e6df1ddc27ee@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8

After googling I found this to be a common problem
when some error message is flooding /var/log/messages.

Apparently it is ok to  killall kerneloops;
I did,
and this does of course stop it from eating cpu.

But it doesn't solve the basic problem, what is flooding the messages file?
In my case it is huge number of lines:

Nov 29 13:27:04 localhost kernel: [drm:mga_dma_reset] *ERROR*
mga_dma_reset called without lock held, held  0 owner f4041ae0
f4041ae0
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_flush] *ERROR*
mga_dma_flush called without lock held, held  0 owner f4041ae0
f4041ae0
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_reset] *ERROR*
mga_dma_reset called without lock held, held  0 owner f4041ae0
f4041ae0
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_flush] *ERROR*
mga_dma_flush called without lock held, held  0 owner f4041ae0
f4041ae0
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_reset] *ERROR*
mga_dma_reset called without lock held, held  0 owner f4041ae0
f4041ae0
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_flush] *ERROR*
mga_dma_flush called without lock held, held  0 owner f4041ae0
f4041ae0
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_reset] *ERROR*
mga_dma_reset called without lock held, held  0 owner f4041ae0
f4041ae0
Nov 29 13:27:04 localhost kernel: [drm:mga_dma_flush] *ERROR*
mga_dma_flush called without lock held, held  0 owner f4041ae0
f4041ae0


Any advice on this?
Might it be tied to my somewhat frequent X-freezes?

As it stands now I will still continue to get the large messages file
requiring me to truncate the file, every day or so

Jack



------------------------------

Message: 10
Date: Mon, 30 Nov 2009 00:03:34 +0000
From: jaivuk <jaivuk@xxxxxxxxxxxxxx>
Subject: Upgrade from F11 to F12 - problem with LVM and raid
To: "Community assistance, encouragement,    and advice for using
    Fedora." <fedora-list@xxxxxxxxxx>
Message-ID:
    <a4a0c8c90911291603w7ccaefedu51131e47eb7dab7a@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Hi guys,

I tried to upgrade F11 with soft raid F12. So far I used yum to upgrade
Fedora 1 up to F11. My yum update went wrong and my server wes forcefully
rebooted in the middle so none kernel from F11 works anymore.

After I booted F12 DVD - if I select "Install or Upgrade" and  "Replace
existing Linux System" the probem is that my original raid raids are not
mounted. I can see:

<6>md6: radi1: raid set md0 active with 2 out of 2 mirrors
<6>md0: detected capacity change from 0 to xxxx

<3>"Buffer I/O error on device md0, logical block 0"
...
<3>"Buffer I/O error on device md0, logical block 9"
<6>md0: detected capacity change from xxxx to 0
...
<6>md: md0 is stopped

This whole raid process repeats iteslf several times and it takes about
10-15 minutes.

However with "Replace existing Linux System" option, raid arrays are not
mounted successfuly and I cannot install F12 over F11.

But when I select rescue option from F12 DVD, the same errors are displayed
but my all old arrays are eventually mounted, so I can see all the files.
Also once arrays are mounted they appear working and healthy.

Do you please have any hint how can I refresh or repair my md arrayrs so it
does not take ages before these are mounted and at the first place they are
mounted every time?
Is there any safe raid command I can do in rescue mode so this is achieved
and I won't loss my data?
Do you think that my raid arrays created in times of Fefdora 1 can cause
this problem?

This situation is very painful as I killed my day today trying to fix it
without luck :(

Thank you very much gyus,

Jaiv

PS: During my initial tries I reinstalled swap (as it was encrypted on the
old system and Anaconda always asked for pw which I do not have) and I did
it with the command:
mkswap -f -L swap /dev/VolGrolup00/LogVol00
Do you think I could have damaged my raid arrays by using "-f" option?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.redhat.com/archives/fedora-list/attachments/20091130/a431ce87/attachment.html

------------------------------

Message: 11
Date: Sun, 29 Nov 2009 16:16:18 -0800
From: john wendel <jwendel10@xxxxxxxxxxx>
Subject: Re: Setting up a VM to run an F12 guest on an XP host
To: fedora-list@xxxxxxxxxx
Message-ID: <4B130ED2.6060208@xxxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8; format=flowed

On 11/29/2009 01:35 PM, Alan Milnes wrote:
> 2009/11/28 john wendel<jwendel10@xxxxxxxxxxx>:
>>
>> I know very little about Windows, so I'm seeking your advice.
>>
>> I'd like to run F12 on an XP box (so I can get some work done), could
>> someone point me to the right software. The big problem is that I don't have
>> admin privs on the XP box so I can't install anything. Is it even possible?
>
> You don't install F12 from within XP so as long as you can boot from a
> CD/DVD this won't be an issue.  Just boot from a F12 LiveCD and the
> installer should sort it all out for you - this is called "Dual Boot",
> each time the computer starts you have the choice to run F12 or
> Windows XP (one will be set as a default and you will have 10 seconds
> to make a decision when the screen comes up).
>
> Alan
>

Unfortunately, there is an intrusion detection system on the network
that keeps me from setting up a dual-boot system. If I boot the F12 live
cd, my network connection is disabled and the admins come and beat me
about the head. So I think running F12 in a VM is going to be the best I
can do.

Thanks,

John



------------------------------

Message: 12
Date: Sun, 29 Nov 2009 16:27:59 -0800
From: Skunk Worx <skunkworx@xxxxxxxxxxx>
Subject: f12 updates kernel nomodeset option breaks radeon
To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
Message-ID: <4B13118F.6050603@xxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

After updates today my radeon driver does not start properly if the
kernel nomodeset option is used.

The X log has a message :

"Couldn't find valid PLL dividers"

Good news though in other areas :

--I can shell into the machine with ssh, it's not a hard crash.

--If I set up the kernel with "rhgb quiet" and do not use the
"nomodeset" option X starts up normally.

--I no longer need an xorg.conf with "XAA" accel enabled to prevent X
crashes. EXA seems to be working reliably now. (I previously reported
that www.newegg.com and wiki.centos.org were crashing X with EXA enabled.)

EXA seems stable with kernel modesetting though...great!

Smolt :

http://www.smolts.org/client/show/pub_2eb94c68-e819-4003-aa96-47783092c4ab

---
John



------------------------------

Message: 13
Date: Mon, 30 Nov 2009 00:36:35 +0000
From: Marko Vojinovic <vvmarko@xxxxxxxxx>
Subject: Re: Default keyring for NetworkManager
To: fedora-list@xxxxxxxxxx, gayleard@xxxxxxxxxx
Message-ID: <200911300036.35353.vvmarko@xxxxxxxxx>
Content-Type: Text/Plain;  charset="iso-8859-1"

On Sunday 29 November 2009 21:54:11 Timothy Murphy wrote:
> Sam Varshavchik wrote:
> > Use seahorse to set a blank password on your keyring. If it won't let
> > you, delete your keyring completely. On the next login you'll be prompted
> > to create one, create it with a blank password.
>
> What can one do on a KDE system?
> As far as I can see, seahorse is a Gnome speciality.

Yes, but it won't hurt much. Do a "yum install seahorse" (it will have one or
two dependencies), use it to set an empty password, then "yum remove seahorse"
and its dependency, and you are done. :-)

> Would knetworkmanager be any help?

I tried it instead of nm-applet, but somehow didn't feel stable enough. Since
nm-applet was favored to knetworkmanager on the very KDE spin, I guess the
latter is not quite there yet. Besides, I got used to nm-applet, and it works
ok for me.

> This NetworkManager password business seems completely crazy to me.

The whole thing has nothing to do with NM itself. The issue is between nm-
applet and default keyring (Gnome) or knetworkmanager and kde wallet (KDE).
It's all about where to store the wireless keys and who can read them.

Best, :-)
Marko



------------------------------

Message: 14
Date: Mon, 30 Nov 2009 00:43:19 +0000
From: Marko Vojinovic <vvmarko@xxxxxxxxx>
Subject: Re: Default keyring for NetworkManager
To: fedora-list@xxxxxxxxxx, gayleard@xxxxxxxxxx
Message-ID: <200911300043.19415.vvmarko@xxxxxxxxx>
Content-Type: Text/Plain;  charset="iso-8859-1"

On Sunday 29 November 2009 20:35:51 Timothy Murphy wrote:
> Marko Vojinovic wrote:
> > So, given that I have autologin set up, it *can* be done. I push the
> > power button on my laptop, wait until the system settles down, and I am
> > logged in, connected to wireless, ktorrent and openvpn are already
> > working, and all is well. The problem was just to move that "default
> > keyring" thing out of the way. This was solved by making it accept an
> > empty password.
>
> How do you make it accept an empty password?

I'm writing this from memory, as I deleted seahorse already and cannot start
it up.

First install seahorse. Then start it. The UI is not quite intuitive, but you
should basically see one line in the main part of the window representing the
default keys stuff (in my case it was the only line available). Click on it,
and then find something like "properties" or similar. In there you will find an
option to change the password. It will open a dialog asking for the old
password, and the new one (twice). Type in the old password, leave blank fields
for the new one. You should get an "are you sure" type of warning, but it will
accept it on if you insist :-). Close seahorse and uninstall if you wish.

That should do it.

Best, :-)
Marko




------------------------------

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-list

End of fedora-list Digest, Vol 69, Issue 203
********************************************