Re: FC6 KDE No Keyboard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Disable the "sticky keys" in the KDE control center.
My bet is that you pressed the shift key for more than a few secs, and
activated that feature.

> -----Messaggio originale-----
> Da: fedora-list-bounces@xxxxxxxxxx 
> [mailto:fedora-list-bounces@xxxxxxxxxx] Per conto di 
> fedora-list-request@xxxxxxxxxx
> Inviato: lunedì 14 maggio 2007 20.10
> A: fedora-list@xxxxxxxxxx
> Oggetto: fedora-list Digest, Vol 39, Issue 94
> 
> 
> 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. Re: USB flash drives won't mount (Mikkel L. Ellertson)
>    2. Lenovo Thinkpad T61 Linux Support (Derek Tracy)
>    3. emacs !!! (Oliver Ruebenacker)
>    4. Re: X window woes (yk)
>    5. Re: emacs !!! (Derek Tracy)
>    6. Re: No eth1 wireless (Dotan Cohen)
>    7. Re: Inspiron 9400, ATI Radeon 1400, external digital display
>       (Nat Gross)
>    8. Re: going back to a previous kernel (Nigel Henry)
>    9. Re: emacs !!! (Alexander Dalloz)
>   10. FC6 KDE No Keyboard (Gene Poole)
>   11. Re: FC6 KDE No Keyboard (Kam Leo)
>   12. Re: Lenovo Thinkpad T61 Linux Support (Thorsten Leemhuis)
>   13. Re: emacs !!! (William Case)
>   14. Re: X window woes (Mikkel L. Ellertson)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 14 May 2007 11:00:46 -0500
> From: "Mikkel L. Ellertson" <mikkel@xxxxxxxxxxxxxxxx>
> Subject: Re: USB flash drives won't mount
> To: For users of Fedora <fedora-list@xxxxxxxxxx>
> Message-ID: <464887AE.9050203@xxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Tim wrote:
> > On Sun, 2007-05-13 at 14:28 -0500, Mikkel L. Ellertson wrote:
> >> you may be able to solve the problem giving the drive a 
> "name". For 
> >> an ext2/3 partition, e2label works. For a FAT partition, 
> it is easy 
> >> to do in Windows, but I am not sure how to do it in Linux 
> except on a 
> >> new partition. (mkdosfs -n option.)
> > 
> > The mlabel command allows you to label DOS-like things.  
> The manpage 
> > for it is a bit less than helpful in how you pick the drive to work 
> > on, you use a drive letter, like DOS, but something else configures 
> > what the letters refer to.  The /etc/mtools.conf file is used to 
> > associate a device on Linux with a DOS-like drive letter.
> > 
> Thanks Tim,
>  I had forgotten the mlabel command. I will have to set up a 
> drive letter that points to the first USB flash drive just 
> for labeling. (Actually 4 entries for by USB card reader - 
> each slot is a SCSI
> device.) If I get some spare time, maybe I'll grab the code 
> for mlabel, and see if I can modify it to accept /dev entries 
> directly.
> 
> Mikkel
> -- 
> 
>   Do not meddle in the affairs of dragons,
> for thou art crunchy and taste good with Ketchup!
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Mon, 14 May 2007 12:05:53 -0400
> From: "Derek Tracy" <tracyde@xxxxxxxxx>
> Subject: Lenovo Thinkpad T61 Linux Support
> To: fedora-list@xxxxxxxxxx
> Message-ID:
> 	<9999810b0705140905y3c169abby30fddf7ceba1358@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="utf-8"
> 
> Has anybody heard of Lenovo Thinkpad T61 support in Linux?  I 
> have been searching everywhere and have been unable to turn 
> anything up.  My current laptop just died on me two days ago 
> and I was thinking about the T61, I am willing to wait for 
> Linux support (although not long).  I think the problem will 
> lie with the Intel Santa Rosa platform, does anybody know 
> anything about this currently working with Linux?
> 
> 
> 
> -- 
> ---------------------------------
> Derek Tracy
> tracyde@xxxxxxxxx
> ---------------------------------
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> https://www.redhat.com/archives/fedora-list/attachments/200705
> 14/825345ae/attachment.html
> 
> ------------------------------
> 
> Message: 3
> Date: Mon, 14 May 2007 12:33:27 -0400
> From: "Oliver Ruebenacker" <curoli@xxxxxxxxx>
> Subject: emacs !!!
> To: fedora-list@xxxxxxxxxx
> Message-ID:
> 	<5639badd0705140933y4345304coa04edc1ee3368dd8@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
>      Dear friends,
> 
>   As if things were not already bad enough, after updates 
> today, emacs stopped working on two different machines. 
> Remove and reinstall does not change anything. What can I do? Thanks!
> 
>      Take care
>      Oliver
> 
> [oliver@dhcp-0000006281-c4-1f ~]$ emacs
> *** glibc detected *** emacs: corrupted double-linked list: 
> 0x0937fd28 *** ======= Backtrace: ========= 
> /lib/libc.so.6[0x1b0dd8] /lib/libc.so.6(__libc_malloc+0x7e)[0x1b204e]
> emacs[0x8145b1d]
> /lib/libc.so.6(__libc_malloc+0x35)[0x1b2005]
> /usr/lib/libX11.so.6(XOpenDisplay+0x509)[0x43af15a9]
> emacs[0x80c5721]
> emacs[0x8056a14]
> emacs[0x80f3b76] /lib/libc.so.6(__libc_start_main+0xe0)[0x15df30]
> emacs[0x8051b31]
> ======= Memory map: ========
> 00110000-00124000 r-xp 00000000 fd:00 4522070    
> /lib/libpthread-2.5.90.so
> 00124000-00125000 r-xp 00013000 fd:00 4522070    
> /lib/libpthread-2.5.90.so
> 00125000-00126000 rwxp 00014000 fd:00 4522070    
> /lib/libpthread-2.5.90.so
> 00126000-00128000 rwxp 00126000 00:00 0
> 00128000-00147000 r-xp 00000000 fd:00 4523682    
> /lib/libncurses.so.5.6
> 00147000-00148000 rwxp 0001f000 fd:00 4523682    
> /lib/libncurses.so.5.6
> 00148000-00296000 r-xp 00000000 fd:00 4522031    /lib/libc-2.5.90.so
> 00296000-00298000 r-xp 0014e000 fd:00 4522031    /lib/libc-2.5.90.so
> 00298000-00299000 rwxp 00150000 fd:00 4522031    /lib/libc-2.5.90.so
> 00299000-0029c000 rwxp 00299000 00:00 0
> 008e5000-008e6000 r-xp 008e5000 00:00 0          [vdso]
> 009d2000-009ed000 r-xp 00000000 fd:00 4521999    /lib/ld-2.5.90.so
> 009ed000-009ee000 r-xp 0001a000 fd:00 4521999    /lib/ld-2.5.90.so
> 009ee000-009ef000 rwxp 0001b000 fd:00 4521999    /lib/ld-2.5.90.so
> 00ad5000-00afc000 r-xp 00000000 fd:00 4522051    /lib/libm-2.5.90.so
> 00afc000-00afd000 r-xp 00026000 fd:00 4522051    /lib/libm-2.5.90.so
> 00afd000-00afe000 rwxp 00027000 fd:00 4522051    /lib/libm-2.5.90.so
> 00b15000-00b20000 r-xp 00000000 fd:00 4521993 
> /lib/libgcc_s-4.1.2-20070503.so.1 00b20000-00b21000 rwxp 
> 0000a000 fd:00 4521993 /lib/libgcc_s-4.1.2-20070503.so.1
> 00c1e000-00c26000 r-xp 00000000 fd:00 5576283    
> /usr/lib/libgif.so.4.1.3
> 00c26000-00c27000 rwxp 00007000 fd:00 5576283    
> /usr/lib/libgif.so.4.1.3
> 00da1000-00da2000 r-xp 00000000 fd:00 5576285    
> /usr/lib/libungif.so.4.1.3
> 00da2000-00da3000 rwxp 00000000 fd:00 5576285    
> /usr/lib/libungif.so.4.1.3
> 00f99000-00f9c000 r-xp 00000000 fd:00 4522041    /lib/libdl-2.5.90.so
> 00f9c000-00f9d000 r-xp 00002000 fd:00 4522041    /lib/libdl-2.5.90.so
> 00f9d000-00f9e000 rwxp 00003000 fd:00 4522041    /lib/libdl-2.5.90.so
> 08048000-081d1000 r-xp 00000000 fd:00 5593919    /usr/bin/emacs-x
> 081d1000-09591000 rwxp 00188000 fd:00 5593919    /usr/bin/emacs-x
> 0a3d6000-0a3db000 rwxp 0a3d6000 00:00 0
> 42ed6000-42ee6000 r-xp 00000000 fd:00 5576203    
> /usr/lib/libXpm.so.4.11.0
> 42ee6000-42ee7000 rwxp 00010000 fd:00 5576203    
> /usr/lib/libXpm.so.4.11.0
> 436a0000-436b5000 r-xp 00000000 fd:00 4526639    /lib/libtinfo.so.5.6
> 436b5000-436b8000 rwxp 00014000 fd:00 4526639    /lib/libtinfo.so.5.6
> 436cd000-43723000 r-xp 00000000 fd:00 5573760    
> /usr/lib/libtiff.so.3.8.2
> 43723000-43725000 rwxp 00056000 fd:00 5573760    
> /usr/lib/libtiff.so.3.8.2
> 43a10000-43a22000 r-xp 00000000 fd:00 4526619    /lib/libz.so.1.2.3
> 43a22000-43a23000 rwxp 00011000 fd:00 4526619    /lib/libz.so.1.2.3
> 43a25000-43ac3000 r-xp 00000000 fd:00 4526616    
> /lib/libglib-2.0.so.0.1200.11
> 43ac3000-43ac4000 rwxp 0009d000 fd:00 4526616    
> /lib/libglib-2.0.so.0.1200.11
> 43ac6000-43bc4000 r-xp 00000000 fd:00 5584772    
> /usr/lib/libX11.so.6.2.0
> 43bc4000-43bc8000 rwxp 000fe000 fd:00 5584772    
> /usr/lib/libX11.so.6.2.0
> 43bca000-43bcc000 r-xp 00000000 fd:00 5584770    
> /usr/lib/libXau.so.6.0.0
> 43bcc000-43bcd000 rwxp 00001000 fd:00 5584770    
> /usr/lib/libXau.so.6.0.0
> 43bcf000-43bd4000 r-xp 00000000 fd:00 5584771    
> /usr/lib/libXdmcp.so.6.0.0
> 43bd4000-43bd5000 rwxp 00004000 fd:00 5584771    
> /usr/lib/libXdmcp.so.6.0.0
> 43bf1000-43c2f000 r-xp 00000000 fd:00 4526618 
> /lib/libgobject-2.0.so.0.1200.11 43c2f000-43c30000 rwxp 
> 0003e000 fd:00 4526618 /lib/libgobject-2.0.so.0.1200.11 
> 43c32000-43c34000 r-xp 00000000 fd:00 4526617 
> /lib/libgmodule-2.0.so.0.1200.11 43c34000-43c35000 rwxp 
> 00002000 fd:00 4526617 /lib/libgmodule-2.0.so.0.1200.11
> 43c37000-43c46000 r-xp 00000000 fd:00 5584777    
> /usr/lib/libXext.so.6.4.0
> 43c46000-43c47000 rwxp 0000e000 fd:00 5584777    
> /usr/lib/libXext.so.6.4.0
> 43c49000-43ccf000 r-xp 00000000 fd:00 5584768    
> /usr/lib/libfreetype.so.6.3.15
> 43ccf000-43cd3000 rwxp 00086000 fd:00 5584768    
> /usr/lib/libfreetype.so.6.3.15
> 43cd5000-43cfc000 r-xp 00000000 fd:00 5584769    
> /usr/lib/libfontconfig.so.1.2.0
> 43cfc000-43d04000 rwxp 00027000 fd:00 5584769    
> /usr/lib/libfontconfig.so.1.2.0
> 43d06000-43d2b000 r-xp 00000000 fd:00 5584765    
> /usr/lib/libpng12.so.0.16.0
> 43d2b000-43d2c000 rwxp 00024000 fd:00 5584765    
> /usr/lib/libpng12.so.0.16.0
> 43d2e000-43d4d000 r-xp 00000000 fd:00 4526621    
> /lib/libexpat.so.0.5.0
> 43d4d000-43d4f000 rwxp 0001e000 fd:00 4526621    
> /lib/libexpat.so.0.5.0
> 43d51000-43d59000 r-xp 00000000 fd:00 5584773    
> /usr/lib/libXrender.so.1.3.0
> 43d59000-43d5a000 rwxp 00007000 fd:00 5584773    
> /usr/lib/libXrender.so.1.3.0
> 43d5c000-43d63000 r-xp 00000000 fd:00 5584779    
> /usr/lib/libXi.so.6.0.0
> 43d63000-43d64000 rwxp 00006000 fd:00 5584779    
> /usr/lib/libXi.so.6.0.0
> 43d66000-43d6c000 r-xp 00000000 fd:00 5584780    
> /usr/lib/libXrandr.so.2.1.0
> 43d6c000-43d6d000 rwxp 00005000 fd:00 5584780    
> /usr/lib/libXrandr.so.2.1.0
> 43d6f000-43dec000 r-xp 00000000 fd:00 5584774    
> /usr/lib/libcairo.so.2.11.2
> 43dec000-43dee000 rwxp 0007c000 fd:00 5584774    
> /usr/lib/libcairo.so.2.11.2
> 43df0000-43e7a000 r-xp 00000000 fd:00 5584783 
> /usr/lib/libgdk-x11-2.0.so.0.1000.11
> 43e7a000-43e7d000 rwxp 0008a000 fd:00 5584783 
> /usr/lib/libgdk-x11-2.0.so.0.1000.11
> 43e7f000-43e95000 r-xp 00000000 fd:00 5584766 
> /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11
> 43e95000-43e96000 rwxp 00016000 fd:00 5584766 
> /usr/lib/libgdk_pixbuf-2.0.so.0.1000.11
> 43e98000-43ea0000 r-xp 00000000 fd:00 5584776 
> /usr/lib/libpangocairo-1.0.so.0.1600.4
> 43ea0000-43ea1000 rwxp 00007000 fd:00 5584776 
> /usr/lib/libpangocairo-1.0.so.0.1600.4
> 43ea3000-43eac000 r-xp 00000000 fd:00 5584782    
> /usr/lib/libXcursor.so.1.0.2
> 43eac000-43ead000 rwxp 00008000 fd:00 5584782    
> /usr/lib/libXcursor.so.1.0.2
> 43eaf000-43eb1000 r-xp 00000000 fd:00 5584778    
> /usr/lib/libXinerama.so.1.0.0
> 43eb1000-43eb2000 rwxp 00001000 fd:00 5584778    
> /usr/lib/libXinerama.so.1.0.0
> 43eb4000-43ef4000 r-xp 00000000 fd:00 5584767 
> /usr/lib/libpango-1.0.so.0.1600.4 43ef4000-43ef6000 rwxp 
> 0003f000 fd:00 5584767 /usr/lib/libpango-1.0.so.0.1600.4
> 43ef8000-43efc000 r-xp 00000000 fd:00 5584781    
> /usr/lib/libXfixes.so.3.1.0
> 43efc000-43efd000 rwxp 00003000 fd:00 5584781    
> /usr/lib/libXfixes.so.3.1.0
> 43eff000-43f2d000 r-xp 00000000 fd:00 5584775 
> /usr/lib/libpangoft2-1.0.so.0.1600.4
> 43f2d000-43f2e000 rwxp 0002e000 fd:00 5584775 
> /usr/lib/libpangoft2-1.0.so.0.1600.4
> 43f30000-442c6000 r-xp 00000000 fd:00 5584785 
> /usr/lib/libgtk-x11-2.0.so.0.1000.11
> 442c6000-442cc000 rwxp 00396000 fd:00 5584785 
> /usr/lib/libgtk-x11-2.0.so.0.1000.11
> 442cc000-442cd000 rwxp 442cc000 00:00 0
> 442cf000-442e9000 r-xp 00000000 fd:00 5584784    
> /usr/lib/libatk-1.0.so.0.1809.1
> 442e9000-442eb000 rwxp 0001a000 fd:00 5584784    
> /usr/lib/libatk-1.0.so.0.1809.1
> 44422000-44443000 r-xp 00000000 fd:00 5585018    
> /usr/lib/libjpeg.so.62.0.0
> 44443000-44444000 rwxp 00020000 fd:00 5585018    
> /usr/lib/libjpeg.so.62.0.0
> 44446000-4445d000 r-xp 00000000 fd:00 5584786    
> /usr/lib/libICE.so.6.3.0
> 4445d000-4445e000 rwxp 00016000 fd:00 5584786    
> /usr/lib/libICE.so.6.3.0
> 4445e000-44460000 rwxp 4445e000 00:00 0
> 44462000-4446a000 r-xp 00000000 fd:00 5584787    
> /usr/lib/libSM.so.6.0.0
> 4446a000-4446b000 rwxp 00007000 fd:00 5584787    
> /usr/lib/libSM.so.6.0.0
> 44568000-4457a000 r-xp 00000000 fd:00 5586903    
> /usr/lib/libXft.so.2.1.2
> 4457a000-4457b000 rwxp 00012000 fd:00 5586903    
> /usr/lib/libXft.so.2.1.2
> b7c00000-b7c08000 rw-p b7c00000 00:00 0
> b7c08000-b7d00000 ---p b7c08000 00:00 0
> b7da2000-b7fa2000 r--p 00000000 fd:00 5574275    
> /usr/lib/locale/locale-archive
> b7fa2000-b7fac000 rw-p b7fa2000 00:00 0
> bff22000-bff37000 rw-p bff22000 00:00 0          [stack]
> Fatal error (6)Aborted
> 
> 
> -- 
> Oliver Ruebenacker, Post-Doc Researcher
> Theoretical Biological Physics and Soft Statistical Mechanics 
> Cell Biology at UConn Health Center and Physics at Harvard 
> http://people.deas.harvard.edu/~oliver/
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Tue, 15 May 2007 01:10:28 +0800
> From: yk <qiongkun123@xxxxxxx>
> Subject: Re: X window woes
> To: For users of Fedora <fedora-list@xxxxxxxxxx>
> Message-ID: <46489804.6070305@xxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Mikkel L. Ellertson wrote:
> >> It could be a DNS problem. Try running " nslookup $(hostname)" and 
> >> see if it shows an IP address, or an error message. (You 
> can use dig 
> >> in place of nslookup, but nslookup produces a cleaner output.)
> >>
> >> Mikkel
> >>     
> >> Mikkel,thanks for the attention!
> >> I'm quite sure that both of them will return error 
> messages, because 
> >> We can only access the network through some kind of authentication.
> >> BTW:  Why the dns concerned?
> >>     
> 
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Mon, 14 May 2007 13:11:18 -0400
> From: "Derek Tracy" <tracyde@xxxxxxxxx>
> Subject: Re: emacs !!!
> To: "For users of Fedora" <fedora-list@xxxxxxxxxx>
> Message-ID:
> 	<9999810b0705141011w3bb25ce5g734823ffafece7c7@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="utf-8"
> 
> On 5/14/07, Oliver Ruebenacker <curoli@xxxxxxxxx> wrote:
> >
> >      Dear friends,
> >
> >   As if things were not already bad enough, after updates 
> today, emacs 
> > stopped working on two different machines. Remove and 
> reinstall does 
> > not change anything. What can I do? Thanks!
> >
> >
> Use vi
> :-)
> 
> 
> -- 
> ---------------------------------
> Derek Tracy
> tracyde@xxxxxxxxx
> ---------------------------------
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> https://www.redhat.com/archives/fedora-list/attachments/200705
> 14/6e3f9c4b/attachment.html
> 
> ------------------------------
> 
> Message: 6
> Date: Mon, 14 May 2007 20:14:00 +0300
> From: "Dotan Cohen" <dotancohen@xxxxxxxxx>
> Subject: Re: No eth1 wireless
> To: "For users of Fedora" <fedora-list@xxxxxxxxxx>
> Message-ID:
> 	<880dece00705141014l6982d742q9e44c88038793ec5@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> On 14/05/07, David G. Miller <dave@xxxxxxxxxxxxx> wrote:
> > "Dotan Cohen" <dotancohen@xxxxxxxxx> wrote:
> >
> > > I seem to have corrupted system-config-network while playing with 
> > > firestarter. I've since gone back to the default Fedora firewall 
> > > (system-config-securitylevel). I see two devices in the 
> Devices tab: 
> > > eth0 (Type: Ethernet), which is active, and eth1 (Type: 
> Wireless), 
> > > which is inactive. When I try to activate eth1, I get this 
> > > inappropriate error: Determining IP information for 
> eth1... failed; 
> > > no link present.  Check cable?
> > >
> > > Why does it think that there should be a cable? Before 
> rebooting I 
> > > was getting this error: When I try to activate eth1 (wireless):
> > > Determining IP information for eth1...dhclient(4733) is already
> > > running - exiting.
> > > exiting.
> > >  failed.
> > >
> > > How can I start eth1? Note that SELinux is set to Permissive.
> > >
> > > Thanks in advance.
> > >
> > > Dotan Cohen
> > The "check cable" message is just a carry-over from 
> pre-wireless.  It 
> > means that the wireless can't establish a link level 
> connection.  With 
> > a wired connection, this is equivalent to having a working cable in 
> > place.  Thus, "check cable."
> 
> Alright.
> 
> > Some things to try are:
> >
> > Open up your access point (no encryption, authentication, ESSID is 
> > broadcast, no MAC filtering) and see if you can connect.  Your 
> > security exposure is fairly minimal if you only leave it 
> open briefly.
> 
> It's not my access point, it's the university's. I have no 
> control over the router settings.
> 
> > What gets reported if you do a "iwlist eth1 scan"?  If nothing then 
> > your system isn't even talking to the radio.  If you get a list of 
> > APs, then some higher level glitch like authentication is 
> causing the 
> > problem.
> 
> [root@localhost ~]# iwlist eth1 scan
> eth1      No scan results
> 
> However, there is something there:
> 
> [root@localhost ~]# iwconfig eth1
> eth1      unassociated  ESSID:off/any  
> Nickname:"localhost.localdomain"
>           Mode:Managed  Frequency=nan kHz  Access Point: 
> Not-Associated
>           Bit Rate=0 kb/s   Tx-Power:16 dBm
>           Retry limit:15   RTS thr:off   Fragment thr:off
>           Encryption key:off
>           Power Management:off
>           Link Quality:0  Signal level:0  Noise level:0
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:130   Missed beacon:0
> 
> > I get the "Determining IP information for eth1...dhclient(4733) is 
> > already running..." message whenever I switch my laptop 
> from wired to 
> > wireless.  Just do a "kill 4733" (or whatever PID gets 
> reported in the 
> > error message) and try it again.
> 
> I didn't think of that. I'll try tomorrow at the university. Thanks.
> 
> Dotan Cohen
> 
> http://dotancohen.com/howto/command_line.php
> http://lyricslist.com/lyrics/artist_albums/600/abs.html
> 
> 
> 
> ------------------------------
> 
> Message: 7
> Date: Mon, 14 May 2007 13:23:20 -0400
> From: "Nat Gross" <nat101l@xxxxxxxxx>
> Subject: Re: Inspiron 9400, ATI Radeon 1400, external digital display
> To: "For users of Fedora" <fedora-list@xxxxxxxxxx>
> Message-ID:
> 	<cf66298c0705141023s14dfebd8se572c4ea87a6f5ee@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> On 5/12/07, David Timms <dtimms@xxxxxxxxxxxx> wrote:
> > Nat Gross wrote:
> > > [For those that followed my 'install thread': next step] 
> Trying to 
> > > connect a Dell Inspiron 9400, with ATI mobility 1400, to 
> a Samsung 
> > > 213T *DIGITAL* port. Simple question: How? <g>
> > >
> > > The same machine/setup with Vista worked automatically. When I 
> > > plugged in the DVI monitor cable into the laptop, Vista prompted 
> > > (just like a usb device, neat)  with various options how 
> I want to 
> > > run both monitors. (Duplicated, different areas of 
> desktop, laptop 
> > > monitor off
> > > - which is the option I chose.) It doesn't always work perfectly,
> > > sometimes I get both displays, but at least it works.
> >                                                  "sort off"
> > > I tried running system-config-display, but I get an error when 
> > > trying to save<OK>.
> > >
> > > So, pray tell me, how do I get my external display to 
> show off its 
> > > Fedora stuff?
> > Which fedora ?
> FC 6 32 bit latest kernel
> > open or ati proprietary driver ?
> driver included with Fedora.
> > Err messages ?
> Depending what I [resolution] choose, I have different 
> problems, sometimes it seems ok until reboot and then have to 
> resort to a new default xorg.conf. Most of the time I can't 
> the following error on the system-config-display console.
> -----------
> Traceback (most recent call last):
>   File "/usr/share/system-config-display/xConfigDialog.py", 
> line 136, in ok
>     lower_vrefresh, upper_vrefresh = 
> string.split(str(self.second_monitor_vrefresh), "-")
> ValueError: need more than 1 value to unpack
> ----------
> and it wouldn't even attempt a save.
> > start a terminal and run
> > system-config-display
> > from there. If you get some messages in the terminal, please search
> > http://bugzilla.redhat.com  fedora   system-config-display 
> first, and if
> > no matching issue, create a new bug including version:
> > rpm -q system-config-display
> > cat /etc/fedora-release
> > In the bug report, attach the output of:
> > lspci
> > and describe the exact sequence that causes the problem.
> >
> > DaveT.
> 
> Will try to follow up with Bugzilla, thanks.
> nat
> PS. In today's news, amd/ati announced that they will open 
> source the drivers! 
> http://enterpriselinuxlog.blogs.techtarget.com/2007/05/09/amd-
> will-deliver-open-graphics-drivers/
> 
> 
> 
> ------------------------------
> 
> Message: 8
> Date: Mon, 14 May 2007 19:27:08 +0200
> From: Nigel Henry <cave.dnb@xxxxxxxxxx>
> Subject: Re: going back to a previous kernel
> To: fedora-list@xxxxxxxxxx
> Message-ID: <200705141927.09430.cave.dnb@xxxxxxxxxx>
> Content-Type: text/plain;  charset="utf-8"
> 
> On Monday 14 May 2007 04:30, Scott Berry wrote:
> > Hi Nigel,
> >
> > Two more questions for you.
> >
> > 1.  How would one add repositories to apt?  I have quite a 
> few I would 
> > like to add.
> 
> These are the 2 that I have in /etc/apt/sources.list in FC6.
> 
> # Add any local / 3rd party repositories here..
> 
> rpm http://ayo.freshrpms.net fedora/linux/6/i386 freshrpms
> 
> rpm http://macromedia.mplug.org/ rpm macromedia
> 
> They are set out differently to the ones for the Fedora 
> repositories, as the 
> Fedora repositories are using a later version of Apt, which uses repo 
> metadata, so you see an entry like this for the Fedora repo's.
> 
> # Fedora Core 
> repomd http://download.fedora.redhat.com/pub/ 
> fedora/linux/core/$(VERSION)/$(ARCH)/os/
> 
> Basically though, if you go to the site of a third part repo, 
> there are 
> instructions there for adding the repo to your apt 
> sources.list. Sometimes 
> you might have to add the necessary line to 
> /etc/apt/sources.list manually, 
> on other sites you can just click on a link, and the repo 
> will be added to 
> your /etc/apt/sources.list.
> 
> Either way you also need to download and import the GPG keys for the 
> repositories, so that the packages you want to download can 
> be verified.
> 
> I normally create a directory named "keys" in my /home/user 
> directory, and 
> download them to that location. Then cd to the keys directory 
> on the CLI, su 
> to root, and run. rpm --import <keyname>.
> 
> You need to be a bit carefull about having too many third 
> party repositories 
> enabled when doing an apt-get update. You can get some nasty package 
> conflicts when subsequently doing an apt-get dist-upgrade.
> 
> 
> >
> > 2.  How do I exclude kernels from being updated?
> 
> Not sure about this using Apt, as I always let the kernel 
> updates go ahead. 
> But I can see the kernels on the Grub menu, and you can't. No 
> text to speech 
> at this stage. I'll post the question to Panu at   
> apt-rpm@xxxxxxxxxxxxxxxxxxxxx
> 
> Perhaps he will have a suggestion.
> 
> Nigel.
> 
> Btw. I apologise if you don't understand some of what I've 
> said. I'm sighted, 
> but find it difficult explaining something that I can see, to 
> someone who is 
> blind. Perhaps I should just speak to you, just like I would 
> with a sighted 
> person, perhaps leaving out the GUI stuff. 
> 
> 
> >
> > Scott
> > ----- Original Message -----
> > From: "Nigel Henry" <cave.dnb@xxxxxxxxxx>
> > To: <fedora-list@xxxxxxxxxx>
> > Sent: Sunday, May 13, 2007 4:26 PM
> > Subject: Re: going back to a previous kernel
> >
> > > On Sunday 13 May 2007 21:21, Scott Berry wrote:
> > >> Hello there,
> > >>
> > >> How do you go back to a previous kernel?  I read something about 
> > >> grub on the dektop but I don't remember where that is.
> > >>
> > >> Scott
> > >
> > > Hi Scott. You will find the grub config file, as root on 
> the CLI, at 
> > > /boot/grub/grub.conf.
> > >
> > > There are a couple of lines you can make changes to. One is named 
> > > "hiddenmenu" . Put a # at the start of the line, and when 
> you boot 
> > > up, Grubs menu will be shown, showing you all available kernels. 
> > > Also you can change the "timeout" line. changing this 
> from 5 to 30 
> > > will give you more time to choose which kernel you want to boot.
> > >
> > > If you are using Apt for getting updates to the system, apt-get 
> > > update, followed by apt-get dist-upgrade, all kernels 
> will be saved 
> > > to Grubs menu.
> > >
> > > If you are using Yum, it only saves as default, the 2 latest 
> > > kernels. You can change this behaviour by editing 
> > > /etc/yum/pluginconf.d/installonlyn.conf
> > > . Just change the line "enabled=1" to "enabled=0" . This will 
> > > disable the plugin, and subsequent kernel updates will 
> all be saved 
> > > to Grubs config file, and will show up on Grubs menu.
> > >
> > > All the best.
> > >
> > > Nigel.
> > >
> > >
> > >
> > > --
> > > fedora-list mailing list
> > > fedora-list@xxxxxxxxxx
> > > To unsubscribe: 
> https://www.redhat.com/mailman/listinfo/fedora-list
> > >
> > >
> > >
> > > --
> > > No virus found in this incoming message.
> > > Checked by AVG Free Edition.
> > > Version: 7.5.467 / Virus Database: 269.7.0/803 - Release Date: 
> > > 5/13/2007 12:17 PM
> 
> 
> 
> ------------------------------
> 
> Message: 9
> Date: Mon, 14 May 2007 19:42:09 +0200
> From: Alexander Dalloz <ad+lists@xxxxxxxxx>
> Subject: Re: emacs !!!
> To: For users of Fedora <fedora-list@xxxxxxxxxx>
> Message-ID: <46489F71.6050807@xxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Oliver Ruebenacker schrieb:
> >     Dear friends,
> > 
> >  As if things were not already bad enough, after updates 
> today, emacs 
> > stopped working on two different machines. Remove and 
> reinstall does 
> > not change anything. What can I do? Thanks!
> > 
> >     Take care
> >     Oliver
> 
> You are not running a stable Fedora release. Please check the 
> fedora-test list for discussion about this problem and test 
> release in general.
> 
> Alexander
> 
> 
> 
> 
> ------------------------------
> 
> Message: 10
> Date: Mon, 14 May 2007 12:34:04 -0400
> From: Gene Poole <Gene.Poole@xxxxxxx>
> Subject: FC6 KDE No Keyboard
> To: fedora-list@xxxxxxxxxx
> Message-ID:
> 	
> <OF087A9468.C13FFADB-ON852572DB.005AD0B3-852572DB.005AFD56@xxxxxxx>
> Content-Type: text/plain; charset=US-ASCII
> 
> 
> For some unknown reason key strokes from the keyboard stopped 
> work stopped working when running FC6 KDE 3.5.  When I 
> switched the session to gnome, everything works just great!  
> Any ideas on how to track and correct this problem?
> 
> Thanks,
> Gene Poole
> gene.poole@xxxxxxx
> 
> 
> 
> ------------------------------
> 
> Message: 11
> Date: Mon, 14 May 2007 09:53:47 -0800
> From: "Kam Leo" <kam.leo@xxxxxxxxx>
> Subject: Re: FC6 KDE No Keyboard
> To: "For users of Fedora" <fedora-list@xxxxxxxxxx>
> Message-ID:
> 	<f84880b00705141053y54375af4uf0d9fd06bf6776d0@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> On 5/14/07, Gene Poole <Gene.Poole@xxxxxxx> wrote:
> >
> > For some unknown reason key strokes from the keyboard stopped work 
> > stopped working when running FC6 KDE 3.5.  When I switched 
> the session 
> > to gnome, everything works just great!  Any ideas on how to 
> track and 
> > correct this problem?
> >
> > Thanks,
> > Gene Poole
> > gene.poole@xxxxxxx
> 
> Quick fix is to rename the .kde directory in your home 
> folder. When you start a new session the folder will be 
> recreated. Copy over any bookmarks or other customizations 
> later after you have logged off.
> 
> 
> 
> ------------------------------
> 
> Message: 12
> Date: Mon, 14 May 2007 19:55:06 +0200
> From: Thorsten Leemhuis <fedora@xxxxxxxxxxxxx>
> Subject: Re: Lenovo Thinkpad T61 Linux Support
> To: For users of Fedora <fedora-list@xxxxxxxxxx>
> Message-ID: <4648A27A.8080107@xxxxxxxxxxxxx>
> Content-Type: text/plain; charset=UTF-8
> 
> On 14.05.2007 18:05, Derek Tracy wrote:
> > Has anybody heard of Lenovo Thinkpad T61 support in Linux?  I have 
> > been searching everywhere and have been unable to turn 
> anything up.  
> > My current laptop just died on me two days ago and I was thinking 
> > about the T61, I am willing to wait for Linux support (although not 
> > long).  I think the problem will lie with the Intel Santa Rosa 
> > platform, does anybody know anything about this currently 
> working with 
> > Linux?
> 
> Display driver for the 965GM (which is used in some Santa Rosa
> notebooks) is there for some days now. I was told it'll be 
> part for F7.
> 
> WLAN is not yet supported afaik. And with such new there is 
> always a risk that new Audio-Codecs or other yet-unsupported 
> stuff gets used.
> 
> CU
> thl
> 
> 
> 
> ------------------------------
> 
> Message: 13
> Date: Mon, 14 May 2007 14:07:34 -0400
> From: William Case <billlinux@xxxxxxxxxx>
> Subject: Re: emacs !!!
> To: For users of Fedora <fedora-list@xxxxxxxxxx>
> Message-ID: <1179166054.29647.71.camel@CASE>
> Content-Type: text/plain
> 
> Hi; 
> I had the same problem -- I think.  Easy to fix.
> 
> On mine /usr/bin/emacs had been removed by the emacs package 
> and replaced by has emacs-22.0.99.  A simple bash alieas, or 
> hard/soft symbolic link or change the launch command in a 
> desktop launcher served as temporary fixes until a new 
> package is created.
> 
> On Mon, 2007-05-14 at 12:33 -0400, Oliver Ruebenacker wrote:
> >      Dear friends,
> > 
> >   As if things were not already bad enough, after updates 
> today, emacs 
> > stopped working on two different machines. Remove and 
> reinstall does 
> > not change anything. What can I do? Thanks!
> > 
> >      Take care
> >      Oliver
> > 
> > [oliver@dhcp-0000006281-c4-1f ~]$ emacs
> > *** glibc detected *** emacs: corrupted double-linked list: 
> 0x0937fd28 
> > ***
> [big snip]
> > Oliver Ruebenacker, Post-Doc Researcher
> > Theoretical Biological Physics and Soft Statistical Mechanics Cell 
> > Biology at UConn Health Center and Physics at Harvard 
> > http://people.deas.harvard.edu/~oliver/
> > 
> -- 
> Regards Bill
> 
> 
> 
> ------------------------------
> 
> Message: 14
> Date: Mon, 14 May 2007 13:09:28 -0500
> From: "Mikkel L. Ellertson" <mikkel@xxxxxxxxxxxxxxxx>
> Subject: Re: X window woes
> To: For users of Fedora <fedora-list@xxxxxxxxxx>
> Message-ID: <4648A5D8.8010509@xxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> yk wrote:
> > Mikkel L. Ellertson wrote:
> >> It could be a DNS problem. Try running " nslookup $(hostname)" and 
> >> see if it shows an IP address, or an error message. (You 
> can use dig 
> >> in place of nslookup, but nslookup produces a cleaner output.)
> >>
> >> Mikkel
> >     Mikkel,thanks for the attention!
> > I'm quite sure that both of them will return error 
> messages, because 
> > We can only access the network through some kind of authentication.
> > BTW:  Why the dns concerned?
> > 
> Your hostname needs to be resolvable on the local machine. 
> This can be through any of the methods listed in 
> /etc/hosts.conf. You will get a DNS timeout delay if it is 
> not. (An entry in /etc/hosts is enough on most systems.) The 
> reason X needs to be able to resolve your hostname is because 
> it is a client/server system. It will try to resolve your 
> hostname as part of the startup process, and you will get a 
> fairly long delay while it tries. (This is also why 
> restarting X when you change your hostname is a good idea.)
> 
> The thing that people tend to forget is that X is a network 
> service. It is designed so that the programs or even the 
> entire desktop do not have to be running on the machine that 
> where the X server is running on. (The X server is the part 
> reading the keyboard/pointing device, and driving the display.)
> 
> Oh yes, X is not the only service that will have problems if 
> you hostname does not resolve properly.
> 
> Mikkel
> -- 
> 
>   Do not meddle in the affairs of dragons,
> for thou art crunchy and taste good with Ketchup!
> 
> 
> 
> ------------------------------
> 
> --
> fedora-list mailing list
> fedora-list@xxxxxxxxxx 
> https://www.redhat.com/mailman/listinfo/fedora-list
> 
> End of fedora-list Digest, Vol 39, Issue 94
> *******************************************
> 
> -- 
> Il messaggio e' stato analizzato alla ricerca di virus o 
> contenuti pericolosi da MailScanner, ed e' risultato non infetto.
> 


-- 
Il messaggio e' stato analizzato alla ricerca di virus o
contenuti pericolosi da MailScanner, ed e'
risultato non infetto.



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux