Re: Update Dependancies broken for the past few days.
Am 22.09.2013 23:57, schrieb Dan Thurman: >> # dnf upgrade --exclude=kernel\* > dnf *upgrade* or dnf update? doe smost likely not matter because you can also use "yum update" or "yum upgrade" which is in no case a dist-upgrade (would be yum --releasever=version distro-sync) signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: yum repo help needed
Allegedly, on or about 21 September 2013, Pete Stieber sent: > On 9/20/2013 4:04 PM, MW = Mike Wright wrote: > MW> MW = Mike Wright wrote: > MW> MW> > MW> How did you do that? What a great way > MW> to follow who is on a thread. > MW> Seems to me to make it more personal. > MW> > MW> Very nice. > > I noticed this format on the wxWidgets mailing list. Used on the Amiga, back in the 1990s, and probably on even older BBS mailing software. But it needs mailing clients that understand it, to stop that recursive crap that happened above, and other author's initials being inserted in front of the wrong person, because they quoted it but didn't write it. And so that author prefix initials stay on the left, and more > characters are added to the right. e.g. MW>> something ... PS> something next... When it works, it really helps with following multi-generational email, especially amongst clods who damn well will not edit out unnecessary quoted crap bloating each and every damn mail they send to the list. But considering the general crapness in email clients at just basic quoting (with bad wrapping, no wrapping, then broken wrapping), and quote prefixes with messy spaces in between some > symbols, I just don't see this working. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
On 23.09.2013 03:08, Rex Dieter wrote: > poma wrote: > >> Conditions of the repos reached affects both tools, > > I'm curious why you mentioned it (dnf) in a thread about broken dependencies > then? > > -- Rex > http://etjune.brochure.examtime.com/files/2013/01/ex-an-16.jpg poma -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Getting Samba to play with OpenLDAP/Kerberos
I have an existing OpenLDAP/Kerberos setup that I'm trying to get Samba to play with. I have no trouble signing on via Kerberos. However, when testing with smbclient: $ smbclient -k -L //rail/ session setup failed: NT_STATUS_LOGON_FAILURE In smb.conf I have: [global] security = ADS realm = ENDOFRAME.NET kerberos method = secrets and system keytab encrypt passwords = yes I added the keytab as follows: kadmin: ktadd -e rc4-hmac:normal cifs/rail.endoframe.net Any suggestions? -- Braden McDaniel -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
On Sun, Sep 22, 2013 at 3:59 PM, Dan Thurman wrote: > ok, so update is a depreciated alias, so upgrade it is! Back in the day `yum upgrade` was the equivalent of `yum update --obsoletes`, which means that if a package has been renamed or replaced, you'd get the new version, whereas a plain `yum update` would not replace those packages. This was rather confusing, and approximately nobody doesn't want Obsoletes to work when updating, so they were later unified to follow the `yum upgrade` behavior, but the `yum update` syntax was kept since that was burned into many peoples' skulls. dnf is intended to replace yum, and one day in the not too distant future people will be running `yum update` and be none the wiser that it is actually what we now call dnf doing the work. So dnf must inherit all yum's little weird oddities, which means `(yum|dnf) upgrade` and `(yum|dnf) update` will probably do the same thing until on or about the heat death of the universe. So, there's no need to change your muscle memory if you don't want to. ;-) -T.C. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
poma wrote: > Conditions of the repos reached affects both tools, I'm curious why you mentioned it (dnf) in a thread about broken dependencies then? -- Rex -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
linuxnuts...@videotron.ca wrote: > You are not alone. It's been pretty bad for quite some time. I've been > having to remove libdvdcss2 before updating and then putting it back. That's a bug in libdvdcss2 packaging (Id recommend informing whoever is providing it that it is broken). -- rex -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
Scott Beamer wrote: > On Sun, 22 Sep 2013 14:17:33 -0500, Rex Dieter wrote: > > [.] > >> >> Looks like a broken dependency with contour, I'll look into it. >> >> In the meantime, you could >> >> yum remove contour >> >> temporarily, until it is fixed. >> > > Thanks! That did the trick! Fix on the way, https://admin.fedoraproject.org/updates/contour-0.3-4.fc19 -- rex -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Accessing usb in text
Allegedly, on or about 22 September 2013, Joe Zeff sent: > It will be in /run/media/$USER/$DEVICE where $DEVICE is the drive's > label if you set it, or whatever the OEM set up if you haven't. BTW, > /run/media itself only exists when there's need for it, so looking > there ahead of time won't work. Does automounting even work in text mode? I thought Gnome or KDE stuck their oars in to do automounting. If it doesn't, one could always manually mount it. Find out what it's device is (e.g. dmesg|tail), then mount /dev/sdb1 /media (or mount point of your own choice). -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
On 23.09.2013 01:29, Dan Thurman wrote: > On 09/22/2013 03:59 PM, Dan Thurman wrote: >> On 09/22/2013 03:55 PM, poma wrote: >>> On 22.09.2013 23:57, Dan Thurman wrote: >>> dnf *upgrade* or dnf update? >>> man 8 dnf ;) >>> >>> >>> poma >>> >> ok, so update is a depreciated alias, so upgrade it is! > > Hmm... I tried dnf with a list of non-existing and existing > packages and dnf reported some errors and quit, so I tried > yum and yum reported and skipped the non-existing files, > and found 9 packages to be installed. It seems that dnf is > not ready to replace yum (yet), or so it seems. > Conditions of the repos reached affects both tools, and these conditions are variable. Like any other. However if you notice anything awkward, please contact the author - Aleš Kozumplík. poma -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: How to unlock HFS+ -
On 22.09.2013 23:25, Bob Goodwin ~ Zuni, Virginia, USA wrote: > I have a hard drive removed from an Apple Mac computer that I need to > reformat but fdisk and gparted show it locked and neither are able to > change anything. The drive is connected through a universal adapter via USB. > > Can anyone tell me how to deal with this? > > Bob > man 8 umount poma -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
On 09/22/2013 03:59 PM, Dan Thurman wrote: On 09/22/2013 03:55 PM, poma wrote: On 22.09.2013 23:57, Dan Thurman wrote: dnf *upgrade* or dnf update? man 8 dnf ;) poma ok, so update is a depreciated alias, so upgrade it is! Hmm... I tried dnf with a list of non-existing and existing packages and dnf reported some errors and quit, so I tried yum and yum reported and skipped the non-existing files, and found 9 packages to be installed. It seems that dnf is not ready to replace yum (yet), or so it seems. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
On 09/22/2013 03:55 PM, poma wrote: On 22.09.2013 23:57, Dan Thurman wrote: dnf *upgrade* or dnf update? man 8 dnf ;) poma ok, so update is a depreciated alias, so upgrade it is! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
On 22.09.2013 23:57, Dan Thurman wrote: > dnf *upgrade* or dnf update? man 8 dnf ;) poma -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Suspension problem last 2 days
On 09/23/13 01:51, Timothy Murphy wrote: > Ed Greshko wrote >> When you boot your system, don't you have a menu to select up to 3 >> kernels? > You are quite right, of course, I was being stupid. I'm a charter member of that club. > > I find that when I boot into 3.10.10-200.fc19.i686.PAE > there appears to be no problem. > (I'm currently running 3.11.1-200.fc19.i686.PAE.) > Sounds like bugzilla time then. -- Getting tired of non-Fedora discussions and self-serving posts -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
On 09/22/2013 12:18 PM, poma wrote: On 22.09.2013 20:53, Scott Beamer wrote: Greetings all, I'm running KDE on Fedora 19 X64 For the past 2-3 days I've had problems updating a number of packages because of failed dependencies. For a while I figured it was a problem that would resolve itself once the mirrors were updated, but so far, the problem persists. II've done 'yum clean all' numerous times to no avail. Is this a problem on my end or Fedora's end? Here is the the output of 'yum update': $ sudo yum update Loaded plugins: langpacks, refresh-packagekit Resolving Dependencies --> Running transaction check ---> Package kcm_colors.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kcm_colors.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kde-workspace.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kde-workspace.x86_64 0:4.11.1-2.fc19 will be an update --> Processing Dependency: libxcb-keysyms.so.1()(64bit) for package: kde-workspace-4.11.1-2.fc19.x86_64 --> Processing Dependency: libxcb-image.so.0()(64bit) for package: kde-workspace-4.11.1-2.fc19.x86_64 ---> Package kde-workspace-libs.x86_64 0:4.10.5-3.fc19 will be updated --> Processing Dependency: libsolidcontrol.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 --> Processing Dependency: libsolidcontrolifaces.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 ---> Package kde-workspace-libs.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kdeartwork.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdeartwork-kxs.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork-kxs.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdeartwork-screensavers.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork-screensavers.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdm.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kdm.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kgreeter-plugins.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kgreeter-plugins.x86_64 0:4.11.1-2.fc19 will be an update ---> Package konsole.x86_64 0:4.10.5-1.fc19 will be updated ---> Package konsole.x86_64 0:4.11.1-1.fc19 will be an update ---> Package konsole-part.x86_64 0:4.10.5-1.fc19 will be updated ---> Package konsole-part.x86_64 0:4.11.1-1.fc19 will be an update ---> Package libkworkspace.x86_64 0:4.10.5-3.fc19 will be updated ---> Package libkworkspace.x86_64 0:4.11.1-2.fc19 will be an update ---> Package mesa-libwayland-egl.x86_64 0:9.2-1.20130902.fc19 will be updated ---> Package mesa-libwayland-egl.x86_64 0:9.2-1.20130919.fc19 will be an update ---> Package plasma-scriptengine-python.x86_64 0:4.10.5-3.fc19 will be updated ---> Package plasma-scriptengine-python.x86_64 0:4.11.1-2.fc19 will be an update --> Running transaction check ---> Package kde-workspace-libs.x86_64 0:4.10.5-3.fc19 will be updated --> Processing Dependency: libsolidcontrol.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 --> Processing Dependency: libsolidcontrolifaces.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 ---> Package xcb-util-image.x86_64 0:0.3.9-2.fc19 will be installed ---> Package xcb-util-keysyms.x86_64 0:0.3.9-2.fc19 will be installed --> Finished Dependency Resolution Error: Package: contour-0.3-2.fc19.x86_64 (@fedora) Requires: libsolidcontrolifaces.so.4()(64bit) Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates) libsolidcontrolifaces.so.4()(64bit) Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates) Not found Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora) libsolidcontrolifaces.so.4()(64bit) Error: Package: contour-0.3-2.fc19.x86_64 (@fedora) Requires: libsolidcontrol.so.4()(64bit) Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates) libsolidcontrol.so.4()(64bit) Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates) Not found Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora) libsolidcontrol.so.4()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Thanks. Scott I've done this, # yum install dnf # dnf upgrade --exclude=kernel\* dnf *upgrade* or dnf update? poma Beam me up, Scotty. :) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Suspension problem last 2 days
Ed Greshko wrote: I've been having a problem on my Thinkpad T61 for the last 2 days. In fact since "yum update" installed kernel-PAE-3.11.1-200.fc19.i686, though that is probably a coincidence. >>> Would it be possible to boot into the previous kernel to verify if it is >>> a coincidence? >> I'm afraid I'm not sure how to do that. >> I'd be happy to try if someone could suggest the way. > When you boot your system, don't you have a menu to select up to 3 > kernels? You are quite right, of course, I was being stupid. I find that when I boot into 3.10.10-200.fc19.i686.PAE there appears to be no problem. (I was running 3.11.1-200.fc19.i686.PAE when the problem occurred.) -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
How to unlock HFS+ -
I have a hard drive removed from an Apple Mac computer that I need to reformat but fdisk and gparted show it locked and neither are able to change anything. The drive is connected through a universal adapter via USB. Can anyone tell me how to deal with this? Bob -- http://www.qrz.com/db/W2BOD box10 Fedora-19 Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: hidden GRUB menu -> Re: Suspension problem last 2 days
On 09/22/2013 09:08 AM, Reindl Harald wrote: i agree in a perfect world you would not need it but this perfect world doe snot exist IMAO, anybody who argues that something isn't needed because "in a perfect world" nobody would use it has already admitted that they're wrong. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Accessing usb in text
On 09/21/2013 06:17 PM, Richard Vickery wrote: I'm stuck in a text environment. I want to save stuff in /home to a USB drive but I forget how it is mapped / how the GUI accesses it; I know that it is under /run, and after this I am lost. It will be in /run/media/$USER/$DEVICE where $DEVICE is the drive's label if you set it, or whatever the OEM set up if you haven't. BTW, /run/media itself only exists when there's need for it, so looking there ahead of time won't work. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Goa daemon eats all my cpu
On 09/21/2013 01:59 PM, Reindl Harald wrote: if it is really a daemon -> systemctl list-units | grep service systemctl disable whatever.service systemctl stop whatever.service This will prevent systemd from starting the daemon at boot, but won't prevent other programs or services from starting it. If you really want to drive a stake through its heart use this: systemctl mask whatever.service -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Ananconda on 19
On 09/21/2013 08:16 AM, Reindl Harald wrote: AFAIK you need to answer a few questions in the installer to get different options enabled - no idea what all the developers talking about modern human interfaces are smoking Neither do I, but I'll bet that neither Latakia nor Perique are included in the blend. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 19, KDE 4.11.1, no login screen
On 09/21/2013 07:52 AM, Reindl Harald wrote: somewhere at start of the boot process you need to press a key or whatever to see the grub-menu at all because "smart" people decided it is more beautiful to hide basic things from users It's not so much their hiding things from users that I object to, it's making it the default. Yes, you should be able to hide the menu if that's what floats your boat, but it shouldn't start out hidden; it should (IMAO) start out visible, with a fairly easy method of toggling. That way, newcomers to Linux will see the menu every time until they learn enough (and get enough confidence) to turn it off, and by that time, they should at least know that the menu's there even if they've forgotten how to toggle it. If nothing else, it should be active on a new install until firstboot runs. That way, if you need to boot into either rescue or CLI mode because your install b0rk, you've got the chance. (If so, firstboot can always ask if you want the menu, with an explanation for beginners of why it might be a Good Idea.) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Fedora 19 and hdmi sound works on Toshiba but not HP
Everyone, I have an HP 2000-2a22NR notebook with an hdmi interface with a new install of fc19. The hdmi video works perfectly, but I am unable to get the sound to the hdmi interface. When I activate 'sound settings' I am able to see sound output device that is labeled " Speakers - Built-in Audio I do not see an hdmi interface option on this screen When i use aplay -i I get the following results : > List of PLAYBACK Hardware Devices > card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 1: Generic_1 [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC > Analog] > Subdevices: 1/1 > Subdevice #0: subdevice #0 I have another fresh install of F19 on a Toshiba Satellite C55-A5249 and the hdmi video and sound work perfectly. On the Toshiba there is an hdmi sound option present on the 'sound settings' screen, and the results of aplay - are : > List of PLAYBACK Hardware Devices > card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > I would sure like to get the HP to work as well as the Toshiba. If any of you any ideas I would appreciate your help. Thanks, Greg Ennis -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Accessing usb in text
Hi gang, I'm stuck in a text environment. I want to save stuff in /home to a USB drive but I forget how it is mapped / how the GUI accesses it; I know that it is under /run, and after this I am lost. Thanks for any help, Richard -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: hidden GRUB menu -> Re: Suspension problem last 2 days
Am 22.09.2013 18:13, schrieb Jan Kratochvil: > On Sun, 22 Sep 2013 03:21:32 +0200, Reindl Harald wrote: >> now we have exactly what i said will happen: users in trouble does not know >> how to >> boot the still installed older kernel because they never learned that there >> are >> more than one because they never faced it as all the years before > > My grandfather still believes those are multiple _different_ Fedora > installations, each having different games/files. As he has also CentOS menu > item there having multiple Fedora items is just too much for him. explain it to him > A proper fix would need to be more thorough as in the case of multiple > different OSes installed you should always get the menu choice: > > * Always present only the latest kernel there, >hide all older kernels under the menu item "Advanced options for Fedora". > > * Do not display the menu if there is only one option available. >(Sure not counting the "Advanced options for Fedora" menu item.) >Sure still the menu gets displayed on holding the SHIFT/ARROW key. > > Failed boot of a new kernel is a rare case needing assistance of someone more > capable of admin work. Such person knows how to display the menu says who? * as i faced the first unbootable system after a kernel update it was Fedora Core 3 * i had no big Fedora expierience at this time * i did not need assistance of someone more capable of admin work why? * because i saw the menu from the very first beginning * because doing nothing the next boot-step after that menu failed * so what did i: look waht happens if i chosse something other from the menu signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: hidden GRUB menu -> Re: Suspension problem last 2 days
Am 22.09.2013 18:30, schrieb Jan Kratochvil: > On Sun, 22 Sep 2013 18:24:45 +0200, Reindl Harald wrote: >> Am 22.09.2013 18:13, schrieb Jan Kratochvil: >>> My grandfather still believes those are multiple _different_ Fedora >>> installations, each having different games/files. As he has also CentOS >>> menu >>> item there having multiple Fedora items is just too much for him. >> >> explain it to him > > I have tried many times for many years but he still insists on it. > > >> * because i saw the menu from the very first beginning >> * because doing nothing the next boot-step after that menu failed >> * so what did i: look waht happens if i chosse something other from the menu > > There is never a perfect solution, everything has its pros and cons. yes and the chance having a unbootable system has more cons > So it could wait for 5 secs, just displaying a message "Hit SHIFT to display > a boot menu.". That hopefully should not confuse users while it would still > help you to solve your problem place a descriptive text *above* the menu and display it as default would be the best one, but i guess pragmatic solutions edcuating users are not the ones developers these days perfer wondering from which tress in 10 years the advanced users will fall if all advanced options are more and more hidden beause the could confuse somebody signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Goa daemon eats all my cpu
Am 21.09.2013 22:51, schrieb William Murray: > Go daemon keeps grabbing 100% of my cpu. I don't really know what it is, good > tells me it is something to do with online accounts (which I never use). Is > there some > way to tame it? Or any way to switch it off completely? who did it switch on? what package is it? why is it installed? in other words: output of "ps aux" and if possible package if it is really a daemon -> systemctl list-units | grep service systemctl disable whatever.service systemctl stop whatever.service signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: hidden GRUB menu -> Re: Suspension problem last 2 days
Am 22.09.2013 18:00, schrieb drago01: > On Sun, Sep 22, 2013 at 5:41 PM, Reindl Harald wrote: >> Am 22.09.2013 17:36, schrieb drago01: >>> On Sun, Sep 22, 2013 at 3:21 AM, Reindl Harald >>> wrote: Am 22.09.2013 02:52, schrieb Ed Greshko: > On 09/22/13 08:39, Timothy Murphy wrote: >> Ed Greshko wrote: >> I've been having a problem on my Thinkpad T61 for the last 2 days. In fact since "yum update" installed kernel-PAE-3.11.1-200.fc19.i686, though that is probably a coincidence. >>> Would it be possible to boot into the previous kernel to verify if it >>> is a >>> coincidence? >> I'm afraid I'm not sure how to do that. >> I'd be happy to try if someone could suggest the way. > > When you boot your system, don't you have a menu to select up to 3 > kernels? and that is why i cried on @devel about the idea to hide the GRUB menu as default >>> >>> Err you know that we do *not* hide the grub menu in F19? >> >> no - because i do not care about Fedora defaults in many cases for my >> machines > > You seem to care enough to write mails about it. yes, becuase i am not that asshole some think and care about others i wish the future users have the same chance to learn things as i had in the past >>> If anything you have just proven that just because the menu is shown >>> people will not automatically know what the options there mean. >> >> no - it is proven that even if it is there it's hard to understand >> hide it does not make this better > > Showing an option that people do not understand does not solve anything. then *explain* the menu instead hide it >>> So can you stop "crying about the idea to hide the GRUB menu as(by) >>> default" now? >> >> no, simply because if it is hard to move the cursor down in a >> already displayed menu for some users you can be sure that they >> never have a chance to learn about the existing older kernel >> by hide it > > You should not have to learn what a kernel is to be able to use your computer this makes no sense why do you have to learn it? because there is a menu giving you options? does this menu *force* someobody to learn? how would it be able to demand anything from a user? > I am pretty sure you disagree here but we should just agree to > disagree instead of having a useless "discussion". if Fedora Core would have had the same attitude than today i would never have switched to Linux completly - this boot option where people say nobody needs to see it saved my first machine and a lot of time for me because it did not boot after a kernel update and so i took the only working thing: a menu at begin i agree in a perfect world you would not need it but this perfect world doe snot exist but you are not in the position than *anybody* else to guarantee that a kernel update will never have regresions, not now and not in the future >> if the affected machine is their only one they also have >> no chance to ask for help and are lost >> >> P.S.: >> do not give thunderbird a negative karma because some extension >> is not updated / rebuilt, file a bugreport for the extension! > > OT but no. If an update introduces broken deps it should not be pushed > until they are resolved. > Giving negative karma here is common practice not common, bad practice at least in that case signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
hidden GRUB menu -> Re: Suspension problem last 2 days
Am 22.09.2013 02:52, schrieb Ed Greshko: > On 09/22/13 08:39, Timothy Murphy wrote: >> Ed Greshko wrote: >> I've been having a problem on my Thinkpad T61 for the last 2 days. In fact since "yum update" installed kernel-PAE-3.11.1-200.fc19.i686, though that is probably a coincidence. >>> Would it be possible to boot into the previous kernel to verify if it is a >>> coincidence? >> I'm afraid I'm not sure how to do that. >> I'd be happy to try if someone could suggest the way. > > When you boot your system, don't you have a menu to select up to 3 kernels? and that is why i cried on @devel about the idea to hide the GRUB menu as default now we have exactly what i said will happen: users in trouble does not know how to boot the still installed older kernel because they never learned that there are more than one because they never faced it as all the years before developers these days forgot how we learned things in the early days and that wil always be the price if you give up good technical solutions for a more shiny look which does only interest if this are going well signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: hidden GRUB menu -> Re: Suspension problem last 2 days
Am 22.09.2013 17:36, schrieb drago01: > On Sun, Sep 22, 2013 at 3:21 AM, Reindl Harald wrote: >> Am 22.09.2013 02:52, schrieb Ed Greshko: >>> On 09/22/13 08:39, Timothy Murphy wrote: Ed Greshko wrote: >> I've been having a problem on my Thinkpad T61 for the last 2 days. >> In fact since "yum update" installed kernel-PAE-3.11.1-200.fc19.i686, >> though that is probably a coincidence. > Would it be possible to boot into the previous kernel to verify if it is a > coincidence? I'm afraid I'm not sure how to do that. I'd be happy to try if someone could suggest the way. >>> >>> When you boot your system, don't you have a menu to select up to 3 kernels? >> >> and that is why i cried on @devel about the idea to hide the GRUB menu as >> default > > Err you know that we do *not* hide the grub menu in F19? no - because i do not care about Fedora defaults in many cases for my machines > If anything you have just proven that just because the menu is shown > people will not automatically know what the options there mean. no - it is proven that even if it is there it's hard to understand hide it does not make this better > So can you stop "crying about the idea to hide the GRUB menu as(by) > default" now? no, simply because if it is hard to move the cursor down in a already displayed menu for some users you can be sure that they never have a chance to learn about the existing older kernel by hide it if the affected machine is their only one they also have no chance to ask for help and are lost P.S.: do not give thunderbird a negative karma because some extension is not updated / rebuilt, file a bugreport for the extension! signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Ananconda on 19
Am 21.09.2013 17:10, schrieb Phil Dobbin: > On 09/21/2013 03:55 PM, Reindl Harald wrote: >> >> Am 21.09.2013 16:35, schrieb poma: >>> On 21.09.2013 15:57, Phil Dobbin wrote: Hi, all. I've just tried to install Fedora 19 over the top of CentOS I.(e. erasing Centos) & I can't figure out how to do it. There's no option for erase & install as with other distros. Could anybody point me in the right direction? Cheers, Phil... >>> >>> Can you point us in the right direction? :) >>> It's not so clear what and with what you want to do install >> >> what is not clear in "Anaconda"? >> it's the Fedora installer >> >> well, with F18 the whole thing was rewritten and hase a >> complete different UI - look on the whole screen for >> possible switches to display extended options >> >> there is for sure somewhere manual partitioning >> >> luckily never faced Anaconda past F14 - god save yum upgrades >> > > Most of the manual options are greyed out & are pretty useless AFAIK you need to answer a few questions in the installer to get different options enabled - no idea what all the developers talking about modern human interfaces are smoking > I suppose I could re-install 17 & upgrade via yum to 18 then 19 > from there but it's a hell of way to do things IMO would be a solution > I suppose the netinstall is the way to go... you can also make a minimal install with the DVD and so following dist-upgrades with yum are tiny and fast - i had to do this somewhere around F17 because the F17 installer insisted in GPT crap and di not allow me to manually specify teh 3 RAID paritions i wanted - after it was solved i found somewhere the kernel-param to disable the GPT nonsense nobody needs on 1 TB drives if you completly want to delete the existing CentOS boot the LiveCD and opena tmerinal "su -" -> "yum install gparted" -> make the partitioning at your own - i am working this way for more than 10 years because i never trusted *nay* os-installer enough to play around with my partitions except on blank machines signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Ananconda on 19
Am 21.09.2013 19:51, schrieb poma: > On 21.09.2013 16:42, Phil Dobbin wrote: >> However there is no option to install over CentOS to utilise the whole >> disk that I could see anyway no matter what I try. I want to erase >> CentOS completely & just have Fedora on the disk. >> >> > There is, not only you can delete the complete partition layout and > create a new one, but you can pass with reformatting only. > However to be sure of what we're really talking about, what exact > version of the CentOS is that *argh* read before reply "version of the CentOS is that" doe snot matter if someone want to kill it completly and replace it with Fedora 19, thanks to moderation i think the problem is sorted out off-list in the meantime his problem is the still broken shiny Anaconda and while i know every piece of my Linux systems Anaconda is the only piece of software i try to avoid to any price i have to pay not face it signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Ananconda on 19
Am 21.09.2013 16:35, schrieb poma: > On 21.09.2013 15:57, Phil Dobbin wrote: >> Hi, all. >> >> I've just tried to install Fedora 19 over the top of CentOS I.(e. >> erasing Centos) & I can't figure out how to do it. There's no option for >> erase & install as with other distros. >> >> Could anybody point me in the right direction? >> >> Cheers, Phil... > > Can you point us in the right direction? :) > It's not so clear what and with what you want to do install what is not clear in "Anaconda"? it's the Fedora installer well, with F18 the whole thing was rewritten and hase a complete different UI - look on the whole screen for possible switches to display extended options there is for sure somewhere manual partitioning luckily never faced Anaconda past F14 - god save yum upgrades signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 19, KDE 4.11.1, no login screen
Am 21.09.2013 16:39, schrieb andrea: > I've just updated F19 and after reboot I do not get the usual kdm login > screen. > The graphic screen with the F stays there forever. > > I can login in text mode and run 'startx' and I get to the normal KDE session. > > Looking at the logs I only noticed > [FAILED] Wait for Plymouh Boot Screen to quit > > and in /var/log/messages > > there is something about > Sep 21 15:24:35 localhost kdm[335]: plymouth --ping -> 0 > Sep 21 15:24:35 localhost kdm[335]: plymouth is running ... > Sep 21 15:24:35 localhost kdm[335]: plymouth deactivate -> 0 > Sep 21 15:24:35 localhost kdm[335]: plymouth --has-active-vt -> 0 > Sep 21 15:24:35 localhost kdm[335]: plymouth should quit when server starts > Sep 21 15:24:36 localhost kdm[335]: plymouth is active on VT 1, reusing for :0 > Sep 21 15:24:36 localhost kdm[335]: X server startup timeout, terminating > Sep 21 15:24:36 localhost kdm[335]: X server for display :0 cannot be > started, session disabled add the following params to the kernel line rd.plymouth=0 plymouth.enable=0 somewhere at start of the boot process you need to press a key or whatever to see the grub-menu at all because "smart" people decided it is more beautiful to hide basic things from users signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Kernel 3.11 & BTRFS: system doesn't boot
Am 21.09.2013 12:52, schrieb Manuel Escudero: > I have a problem with BTRFS and Kernel 3.11, all the info, images, logs and > more are available in my question > at #Askfedora Can anyone help me? > > http://ask.fedoraproject.org/question/32716/kernel-311-btrfs-system-doesnt-boot/ you say 3.10.x and 3.12 works - what help do you imagine? use one of the working kernels and write a bugreport https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora after that most likely the next 3.11 will also work and most likely also without a bugreport because 3.12 works and so whatever causes the problem is fixed signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Rescue Disk
Am 21.09.2013 06:21, schrieb Robert McBroom: > On 09/20/2013 06:06 PM, Reindl Harald wrote: >> Am 21.09.2013 00:03, schrieb Robert McBroom: >>> Do any of the spins have a rescue mode in the trouble shooting menu? The >>> KDE Spin does not. I do not see a rescue >>> .iso disk in the mirrors. I've scrambled grub2 on my boot partition >> what more do you need than "grub2-install /dev/your-partition" out from the >> live-CD? >> > Multi boot system with Win7, /boot is /dev/sda5 as the first logical > partition of a extended partition on a 2T > drive since the Win7 system could be shrunk without disturbing it. The root > partition is /dev/sda6. Before I've > started a rescue system and used a sequence similar to > > mount /dev/sda6 /mnt/Fed19 > mount /dev/sda5 /mnt/Fed19/boot > chroot /mnt/Fed19 > mount -o remount -rw / > mount -t proc proc /proc > grub2-install /dev/sda > > and grub2-install would get the system layout from /etc/fstab amd what of that you can't do with a Live-OS? the recuse mode is nothing magical the Live-OS is a *full featured* Linux with even yum working signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: yum repo help needed
Am 21.09.2013 00:04, schrieb Mike Wright: > 09/20/2013 02:47 PM, Ranjan Maitra wrote: >> Btw, I do wonder why this laptop will not install past F14what is >> the problem? >> > No idea. Would not install f12 either. Liked f10 this is *not* a helpful reply what "no idea"? how far do you come with the install? did you try text-only mode? signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: port forwarding
Am 20.09.2013 22:39, schrieb bruce:
> I'd like to be able to change the ip adress of the gearman processes
> from localhost, to the actual ipaddress of the machine. This of course
> involves changing the port forwarding from the client to the server
> machine.
>
> Thoughts/Comments would be useful
simple with a systemd-unit which also survives a reboot of the target machine
because the command in ExecStart (which is *one* line inclduing the port
22 of the forwarded service, in this case SSH of a internal machine)
will fail in that case and the SSH command is executed 60 seconds later
/etc/sysconfig/forwarding contains the IP-address where the forwarding
should listen instead 127.0.0.1, done this way because there is a fallback
machine, more than one such services and so the systemd-units can be re-used
the result in short is 192.168.0.35:11025 is the forwarded 192.168.1.15:22
192.168.0.0/24 is a different subnet than 192.168.1.0/24, the numbers are
generic to not disclose network-configurations, the files below are
from a live-machine in all other parts
[root@localhost:~]$ cat /etc/sysconfig/forwarding
LOCAL_ADDRESS=192.168.0.35
[root@localhost:~]$ cat /etc/systemd/system/forward-fileserver.service
[Unit]
Description=SSH-Forwarding Fileserver
After=network.service openvpn.service hostapd.service
network-wlan-bridge.service network-bonding-bridge.service
[Service]
Type=simple
EnvironmentFile=/etc/sysconfig/forwarding
ExecStart=/usr/bin/ssh -i /home/ssh-gateway/.ssh/id_rsa
ssh-gateway@192.168.1.15 -N -C
-L${LOCAL_ADDRESS}:11025:127.0.0.1:22
Restart=always
RestartSec=60
TimeoutSec=30
CapabilityBoundingSet=CAP_NET_BIND_SERVICE CAP_DAC_OVERRIDE
[Install]
WantedBy=multi-user.target
signature.asc
Description: OpenPGP digital signature
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Re: USB memory stick - where?
Am 20.09.2013 14:57, schrieb Mihai T. Lazarescu: > On Fri, Sep 20, 2013 at 02:38:05PM +0200, ppq wrote: > >> Am 20.09.2013 14:35, schrieb Timothy Murphy: >>> If I install a memory stick in a Fedora-19 laptop, >>> is there a simple command that will tell me >>> where it is on the filesystem, eg /dev/sdb1 ? >>> I know I can find this indirectly, >>> but is there eg a switch to lsusb that will tell me? >>> >> lsblk is quite useful > > Great, thanks! I was wondering if there was no better way than > "dmesg | tail"... :-) in case of unmounted devices (what DE on a notebook does not support to mount it with one cick?) "lsscsi" will most likely be the best option because you see the devicetype lsblk is not much helpful in case of many devices [root@srv-rhsoft:~]$ lsscsi [0:0:0:0]diskATA ST2000NM0011 SN02 /dev/sda [1:0:0:0]diskATA ST2000NM0011 SN02 /dev/sdb [2:0:0:0]diskATA WDC WD2002FAEX-0 05.0 /dev/sdc [3:0:0:0]diskATA WDC WD2003FYYS-0 01.0 /dev/sdd [6:0:0:0]diskGeneric- Compact Flash1.00 /dev/sde [6:0:0:1]diskGeneric- SM/xD-Picture1.00 /dev/sdf [6:0:0:2]diskGeneric- SD/MMC 1.00 /dev/sdg [6:0:0:3]diskGeneric- MS/MS-Pro/HG 1.00 /dev/sdh [6:0:0:4]diskGeneric- SD/MMC/MS/MSPRO 1.00 /dev/sdi signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Rescue Disk
Am 21.09.2013 00:03, schrieb Robert McBroom: > Do any of the spins have a rescue mode in the trouble shooting menu? The KDE > Spin does not. I do not see a rescue > .iso disk in the mirrors. I've scrambled grub2 on my boot partition what more do you need than "grub2-install /dev/your-partition" out from the live-CD? signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: yum repo help needed
Am 20.09.2013 22:59, schrieb Mike Wright: > I have an very old and cranky laptop that won't install past f14, used mostly > as a scanner/print station. > > I'm trying to update some of its software using yum. I created a repo, > fedora-archive.repo: > > [archive] > name=Fedora 14 - i386 > failovermethod=priority > baseurl=http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/14/Fedora/i386/os/ > enabled=1 > metadata_expire=7d > gpgcheck=1 > > Given this command: > > yum --disablerepo=* --enablerepo=fedora-archive.repo update -y > > fails with: > > Error getting repository data for fedora-archive.repo, repository not found. > > The baseurl is accessible and does point to a repo and you did run the command "createrepo" inside the folder? yum needs the repo-metadata and not only a folder with packages signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: firewalld equivalent of iptabled --sport?
the question was *sport* not dport sport == source port (remote client) dport == target port (your machine running iptables) Am 19.09.2013 16:46, schrieb Shelby, James: > I believe the syntax is: firewall-cmd --permanent --add-port 5002/udp > > > From: users-boun...@lists.fedoraproject.org > [users-boun...@lists.fedoraproject.org] On Behalf Of Richard Shaw > [hobbes1...@gmail.com] > Sent: Thursday, September 19, 2013 7:40 AM > To: Community support for Fedora users > Subject: firewalld equivalent of iptabled --sport? > > I have a HDHomeRun (network based TV tuner) on my home network. In order to > get it to work I had to add the following to my iptables config: > > -A INPUT -m state --state NEW -m udp -p udp --sport 5002 -j ACCEPT > -A INPUT -m state --state NEW -m udp -p udp --sport 5004 -j ACCEPT > -A INPUT -m state --state NEW -m udp -p udp --sport 65001 -j ACCEPT > > Which from my limited knowledge of how iptables work, is the opposite of what > you usually do for most services (--dport) because in this case the the > return port is random. > > I have not been able to find any setting in firewall-config or in the > documentation that mentions source ports, only destination ports. > > If this is not possible it would appear to be a fairly large flaw in > firewalld in general signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: USB memory stick - where?
Am 20.09.2013 14:35, schrieb Timothy Murphy: > If I install a memory stick in a Fedora-19 laptop, > is there a simple command that will tell me > where it is on the filesystem, eg /dev/sdb1 ? > I know I can find this indirectly, > but is there eg a switch to lsusb that will tell me? df signature.asc Description: OpenPGP digital signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
On Sun, 22 Sep 2013 14:17:33 -0500, Rex Dieter wrote: [.] > > Looks like a broken dependency with contour, I'll look into it. > > In the meantime, you could > > yum remove contour > > temporarily, until it is fixed. > Thanks! That did the trick! Scott -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
On 09/22/2013 03:26 PM, linuxnuts...@videotron.ca wrote: On 09/22/2013 02:53 PM, Scott Beamer wrote: Greetings all, I'm running KDE on Fedora 19 X64 For the past 2-3 days I've had problems updating a number of packages because of failed dependencies. For a while I figured it was a problem that would resolve itself once the mirrors were updated, but so far, the problem persists. II've done 'yum clean all' numerous times to no avail. Is this a problem on my end or Fedora's end? Here is the the output of 'yum update': $ sudo yum update Loaded plugins: langpacks, refresh-packagekit Resolving Dependencies --> Running transaction check ---> Package kcm_colors.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kcm_colors.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kde-workspace.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kde-workspace.x86_64 0:4.11.1-2.fc19 will be an update --> Processing Dependency: libxcb-keysyms.so.1()(64bit) for package: kde-workspace-4.11.1-2.fc19.x86_64 --> Processing Dependency: libxcb-image.so.0()(64bit) for package: kde-workspace-4.11.1-2.fc19.x86_64 ---> Package kde-workspace-libs.x86_64 0:4.10.5-3.fc19 will be updated --> Processing Dependency: libsolidcontrol.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 --> Processing Dependency: libsolidcontrolifaces.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 ---> Package kde-workspace-libs.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kdeartwork.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdeartwork-kxs.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork-kxs.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdeartwork-screensavers.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork-screensavers.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdm.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kdm.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kgreeter-plugins.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kgreeter-plugins.x86_64 0:4.11.1-2.fc19 will be an update ---> Package konsole.x86_64 0:4.10.5-1.fc19 will be updated ---> Package konsole.x86_64 0:4.11.1-1.fc19 will be an update ---> Package konsole-part.x86_64 0:4.10.5-1.fc19 will be updated ---> Package konsole-part.x86_64 0:4.11.1-1.fc19 will be an update ---> Package libkworkspace.x86_64 0:4.10.5-3.fc19 will be updated ---> Package libkworkspace.x86_64 0:4.11.1-2.fc19 will be an update ---> Package mesa-libwayland-egl.x86_64 0:9.2-1.20130902.fc19 will be updated ---> Package mesa-libwayland-egl.x86_64 0:9.2-1.20130919.fc19 will be an update ---> Package plasma-scriptengine-python.x86_64 0:4.10.5-3.fc19 will be updated ---> Package plasma-scriptengine-python.x86_64 0:4.11.1-2.fc19 will be an update --> Running transaction check ---> Package kde-workspace-libs.x86_64 0:4.10.5-3.fc19 will be updated --> Processing Dependency: libsolidcontrol.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 --> Processing Dependency: libsolidcontrolifaces.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 ---> Package xcb-util-image.x86_64 0:0.3.9-2.fc19 will be installed ---> Package xcb-util-keysyms.x86_64 0:0.3.9-2.fc19 will be installed --> Finished Dependency Resolution Error: Package: contour-0.3-2.fc19.x86_64 (@fedora) Requires: libsolidcontrolifaces.so.4()(64bit) Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates) libsolidcontrolifaces.so.4()(64bit) Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates) Not found Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora) libsolidcontrolifaces.so.4()(64bit) Error: Package: contour-0.3-2.fc19.x86_64 (@fedora) Requires: libsolidcontrol.so.4()(64bit) Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates) libsolidcontrol.so.4()(64bit) Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates) Not found Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora) libsolidcontrol.so.4()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Thanks. Scott You are not alone. It's been pretty bad for quite some time. I've been having to remove libdvdcss2 before updating and then putting it back. Updating to kernel 3.11.1-200 was a disaster on three of my machines, all using nvidia chipsets. I was rebooting to a black screen. I'm not sure how to troubleshoot this one since reinstalling kmod-nvidia and/or akmod-nvidia didn't do much. I'm closer to the newbie side of the road. One machine with an ATI chipset was ok after a fresh install and update to this latest kernel. Update, I just launched yumex and checkmarking everything marked testing. A newer nvidia driver, which was not there yesterday, w
Re: Update Dependancies broken for the past few days.
On 09/22/2013 12:26 PM, linuxnuts...@videotron.ca wrote: You are not alone. It's been pretty bad for quite some time. I've been having to remove libdvdcss2 before updating and then putting it back. Updating to kernel 3.11.1-200 was a disaster on three of my machines, all using nvidia chipsets. I was rebooting to a black screen. I'm not sure how to troubleshoot this one since reinstalling kmod-nvidia and/or akmod-nvidia didn't do much. I'm closer to the newbie side of the road. One machine with an ATI chipset was ok after a fresh install and update to this latest kernel. I had the same problem. Here's the answer: http://forums.fedoraforum.org/showthread.php?t=294091 Share and enjoy! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
On 09/22/2013 03:18 PM, poma wrote: On 22.09.2013 20:53, Scott Beamer wrote: Greetings all, I'm running KDE on Fedora 19 X64 For the past 2-3 days I've had problems updating a number of packages because of failed dependencies. For a while I figured it was a problem that would resolve itself once the mirrors were updated, but so far, the problem persists. II've done 'yum clean all' numerous times to no avail. Is this a problem on my end or Fedora's end? Here is the the output of 'yum update': $ sudo yum update Loaded plugins: langpacks, refresh-packagekit Resolving Dependencies --> Running transaction check ---> Package kcm_colors.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kcm_colors.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kde-workspace.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kde-workspace.x86_64 0:4.11.1-2.fc19 will be an update --> Processing Dependency: libxcb-keysyms.so.1()(64bit) for package: kde-workspace-4.11.1-2.fc19.x86_64 --> Processing Dependency: libxcb-image.so.0()(64bit) for package: kde-workspace-4.11.1-2.fc19.x86_64 ---> Package kde-workspace-libs.x86_64 0:4.10.5-3.fc19 will be updated --> Processing Dependency: libsolidcontrol.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 --> Processing Dependency: libsolidcontrolifaces.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 ---> Package kde-workspace-libs.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kdeartwork.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdeartwork-kxs.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork-kxs.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdeartwork-screensavers.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork-screensavers.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdm.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kdm.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kgreeter-plugins.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kgreeter-plugins.x86_64 0:4.11.1-2.fc19 will be an update ---> Package konsole.x86_64 0:4.10.5-1.fc19 will be updated ---> Package konsole.x86_64 0:4.11.1-1.fc19 will be an update ---> Package konsole-part.x86_64 0:4.10.5-1.fc19 will be updated ---> Package konsole-part.x86_64 0:4.11.1-1.fc19 will be an update ---> Package libkworkspace.x86_64 0:4.10.5-3.fc19 will be updated ---> Package libkworkspace.x86_64 0:4.11.1-2.fc19 will be an update ---> Package mesa-libwayland-egl.x86_64 0:9.2-1.20130902.fc19 will be updated ---> Package mesa-libwayland-egl.x86_64 0:9.2-1.20130919.fc19 will be an update ---> Package plasma-scriptengine-python.x86_64 0:4.10.5-3.fc19 will be updated ---> Package plasma-scriptengine-python.x86_64 0:4.11.1-2.fc19 will be an update --> Running transaction check ---> Package kde-workspace-libs.x86_64 0:4.10.5-3.fc19 will be updated --> Processing Dependency: libsolidcontrol.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 --> Processing Dependency: libsolidcontrolifaces.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 ---> Package xcb-util-image.x86_64 0:0.3.9-2.fc19 will be installed ---> Package xcb-util-keysyms.x86_64 0:0.3.9-2.fc19 will be installed --> Finished Dependency Resolution Error: Package: contour-0.3-2.fc19.x86_64 (@fedora) Requires: libsolidcontrolifaces.so.4()(64bit) Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates) libsolidcontrolifaces.so.4()(64bit) Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates) Not found Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora) libsolidcontrolifaces.so.4()(64bit) Error: Package: contour-0.3-2.fc19.x86_64 (@fedora) Requires: libsolidcontrol.so.4()(64bit) Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates) libsolidcontrol.so.4()(64bit) Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates) Not found Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora) libsolidcontrol.so.4()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Thanks. Scott I've done this, # yum install dnf # dnf upgrade --exclude=kernel\* poma Beam me up, Scotty. :) Thanks for posting that. I now know what dnf is... and it's very interesting. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
On 09/22/2013 02:53 PM, Scott Beamer wrote: Greetings all, I'm running KDE on Fedora 19 X64 For the past 2-3 days I've had problems updating a number of packages because of failed dependencies. For a while I figured it was a problem that would resolve itself once the mirrors were updated, but so far, the problem persists. II've done 'yum clean all' numerous times to no avail. Is this a problem on my end or Fedora's end? Here is the the output of 'yum update': $ sudo yum update Loaded plugins: langpacks, refresh-packagekit Resolving Dependencies --> Running transaction check ---> Package kcm_colors.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kcm_colors.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kde-workspace.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kde-workspace.x86_64 0:4.11.1-2.fc19 will be an update --> Processing Dependency: libxcb-keysyms.so.1()(64bit) for package: kde-workspace-4.11.1-2.fc19.x86_64 --> Processing Dependency: libxcb-image.so.0()(64bit) for package: kde-workspace-4.11.1-2.fc19.x86_64 ---> Package kde-workspace-libs.x86_64 0:4.10.5-3.fc19 will be updated --> Processing Dependency: libsolidcontrol.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 --> Processing Dependency: libsolidcontrolifaces.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 ---> Package kde-workspace-libs.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kdeartwork.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdeartwork-kxs.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork-kxs.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdeartwork-screensavers.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork-screensavers.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdm.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kdm.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kgreeter-plugins.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kgreeter-plugins.x86_64 0:4.11.1-2.fc19 will be an update ---> Package konsole.x86_64 0:4.10.5-1.fc19 will be updated ---> Package konsole.x86_64 0:4.11.1-1.fc19 will be an update ---> Package konsole-part.x86_64 0:4.10.5-1.fc19 will be updated ---> Package konsole-part.x86_64 0:4.11.1-1.fc19 will be an update ---> Package libkworkspace.x86_64 0:4.10.5-3.fc19 will be updated ---> Package libkworkspace.x86_64 0:4.11.1-2.fc19 will be an update ---> Package mesa-libwayland-egl.x86_64 0:9.2-1.20130902.fc19 will be updated ---> Package mesa-libwayland-egl.x86_64 0:9.2-1.20130919.fc19 will be an update ---> Package plasma-scriptengine-python.x86_64 0:4.10.5-3.fc19 will be updated ---> Package plasma-scriptengine-python.x86_64 0:4.11.1-2.fc19 will be an update --> Running transaction check ---> Package kde-workspace-libs.x86_64 0:4.10.5-3.fc19 will be updated --> Processing Dependency: libsolidcontrol.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 --> Processing Dependency: libsolidcontrolifaces.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 ---> Package xcb-util-image.x86_64 0:0.3.9-2.fc19 will be installed ---> Package xcb-util-keysyms.x86_64 0:0.3.9-2.fc19 will be installed --> Finished Dependency Resolution Error: Package: contour-0.3-2.fc19.x86_64 (@fedora) Requires: libsolidcontrolifaces.so.4()(64bit) Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates) libsolidcontrolifaces.so.4()(64bit) Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates) Not found Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora) libsolidcontrolifaces.so.4()(64bit) Error: Package: contour-0.3-2.fc19.x86_64 (@fedora) Requires: libsolidcontrol.so.4()(64bit) Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates) libsolidcontrol.so.4()(64bit) Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates) Not found Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora) libsolidcontrol.so.4()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Thanks. Scott You are not alone. It's been pretty bad for quite some time. I've been having to remove libdvdcss2 before updating and then putting it back. Updating to kernel 3.11.1-200 was a disaster on three of my machines, all using nvidia chipsets. I was rebooting to a black screen. I'm not sure how to troubleshoot this one since reinstalling kmod-nvidia and/or akmod-nvidia didn't do much. I'm closer to the newbie side of the road. One machine with an ATI chipset was ok after a fresh install and update to this latest kernel. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http
Re: Update Dependancies broken for the past few days.
Scott Beamer wrote: > Greetings all, > > I'm running KDE on Fedora 19 X64 > > For the past 2-3 days I've had problems updating a number of packages > because of failed dependencies. ... > Error: Package: contour-0.3-2.fc19.x86_64 (@fedora) >Requires: libsolidcontrolifaces.so.4()(64bit) >Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates) >libsolidcontrolifaces.so.4()(64bit) >Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates) >Not found >Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora) >libsolidcontrolifaces.so.4()(64bit) Looks like a broken dependency with contour, I'll look into it. In the meantime, you could yum remove contour temporarily, until it is fixed. -- rex -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
On 22.09.2013 20:53, Scott Beamer wrote: > Greetings all, > > I'm running KDE on Fedora 19 X64 > > For the past 2-3 days I've had problems updating a number of packages > because of failed dependencies. > > For a while I figured it was a problem that would resolve itself once > the mirrors were updated, but so far, the problem persists. > > II've done 'yum clean all' numerous times to no avail. > > Is this a problem on my end or Fedora's end? > > Here is the the output of 'yum update': > > > $ sudo yum update > Loaded plugins: langpacks, refresh-packagekit > Resolving Dependencies > --> Running transaction check > ---> Package kcm_colors.x86_64 0:4.10.5-3.fc19 will be updated > ---> Package kcm_colors.x86_64 0:4.11.1-2.fc19 will be an update > ---> Package kde-workspace.x86_64 0:4.10.5-3.fc19 will be updated > ---> Package kde-workspace.x86_64 0:4.11.1-2.fc19 will be an update > --> Processing Dependency: libxcb-keysyms.so.1()(64bit) for package: > kde-workspace-4.11.1-2.fc19.x86_64 > --> Processing Dependency: libxcb-image.so.0()(64bit) for package: > kde-workspace-4.11.1-2.fc19.x86_64 > ---> Package kde-workspace-libs.x86_64 0:4.10.5-3.fc19 will be updated > --> Processing Dependency: libsolidcontrol.so.4()(64bit) for package: > contour-0.3-2.fc19.x86_64 > --> Processing Dependency: libsolidcontrolifaces.so.4()(64bit) for > package: contour-0.3-2.fc19.x86_64 > ---> Package kde-workspace-libs.x86_64 0:4.11.1-2.fc19 will be an update > ---> Package kdeartwork.x86_64 0:4.10.5-1.fc19 will be updated > ---> Package kdeartwork.x86_64 0:4.11.1-1.fc19 will be an update > ---> Package kdeartwork-kxs.x86_64 0:4.10.5-1.fc19 will be updated > ---> Package kdeartwork-kxs.x86_64 0:4.11.1-1.fc19 will be an update > ---> Package kdeartwork-screensavers.x86_64 0:4.10.5-1.fc19 will be updated > ---> Package kdeartwork-screensavers.x86_64 0:4.11.1-1.fc19 will be an update > ---> Package kdm.x86_64 0:4.10.5-3.fc19 will be updated > ---> Package kdm.x86_64 0:4.11.1-2.fc19 will be an update > ---> Package kgreeter-plugins.x86_64 0:4.10.5-3.fc19 will be updated > ---> Package kgreeter-plugins.x86_64 0:4.11.1-2.fc19 will be an update > ---> Package konsole.x86_64 0:4.10.5-1.fc19 will be updated > ---> Package konsole.x86_64 0:4.11.1-1.fc19 will be an update > ---> Package konsole-part.x86_64 0:4.10.5-1.fc19 will be updated > ---> Package konsole-part.x86_64 0:4.11.1-1.fc19 will be an update > ---> Package libkworkspace.x86_64 0:4.10.5-3.fc19 will be updated > ---> Package libkworkspace.x86_64 0:4.11.1-2.fc19 will be an update > ---> Package mesa-libwayland-egl.x86_64 0:9.2-1.20130902.fc19 will be updated > ---> Package mesa-libwayland-egl.x86_64 0:9.2-1.20130919.fc19 will be an > update > ---> Package plasma-scriptengine-python.x86_64 0:4.10.5-3.fc19 will be updated > ---> Package plasma-scriptengine-python.x86_64 0:4.11.1-2.fc19 will be an > update > --> Running transaction check > ---> Package kde-workspace-libs.x86_64 0:4.10.5-3.fc19 will be updated > --> Processing Dependency: libsolidcontrol.so.4()(64bit) for package: > contour-0.3-2.fc19.x86_64 > --> Processing Dependency: libsolidcontrolifaces.so.4()(64bit) for > package: contour-0.3-2.fc19.x86_64 > ---> Package xcb-util-image.x86_64 0:0.3.9-2.fc19 will be installed > ---> Package xcb-util-keysyms.x86_64 0:0.3.9-2.fc19 will be installed > --> Finished Dependency Resolution > Error: Package: contour-0.3-2.fc19.x86_64 (@fedora) >Requires: libsolidcontrolifaces.so.4()(64bit) >Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates) >libsolidcontrolifaces.so.4()(64bit) >Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates) >Not found >Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora) >libsolidcontrolifaces.so.4()(64bit) > Error: Package: contour-0.3-2.fc19.x86_64 (@fedora) >Requires: libsolidcontrol.so.4()(64bit) >Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates) >libsolidcontrol.so.4()(64bit) >Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates) >Not found >Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora) >libsolidcontrol.so.4()(64bit) > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest > > > Thanks. > > Scott > I've done this, # yum install dnf # dnf upgrade --exclude=kernel\* poma Beam me up, Scotty. :) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Update Dependancies broken for the past few days.
On 09/22/2013 11:53 AM, Scott Beamer wrote: II've done 'yum clean all' numerous times to no avail. Is this a problem on my end or Fedora's end? If it didn't work the first time, why did you try again? The odds are that this is at Fedora's end. However, if you want to be sure, try package-cleanup --problems and see what it says. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Update Dependancies broken for the past few days.
Greetings all, I'm running KDE on Fedora 19 X64 For the past 2-3 days I've had problems updating a number of packages because of failed dependencies. For a while I figured it was a problem that would resolve itself once the mirrors were updated, but so far, the problem persists. II've done 'yum clean all' numerous times to no avail. Is this a problem on my end or Fedora's end? Here is the the output of 'yum update': $ sudo yum update Loaded plugins: langpacks, refresh-packagekit Resolving Dependencies --> Running transaction check ---> Package kcm_colors.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kcm_colors.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kde-workspace.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kde-workspace.x86_64 0:4.11.1-2.fc19 will be an update --> Processing Dependency: libxcb-keysyms.so.1()(64bit) for package: kde-workspace-4.11.1-2.fc19.x86_64 --> Processing Dependency: libxcb-image.so.0()(64bit) for package: kde-workspace-4.11.1-2.fc19.x86_64 ---> Package kde-workspace-libs.x86_64 0:4.10.5-3.fc19 will be updated --> Processing Dependency: libsolidcontrol.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 --> Processing Dependency: libsolidcontrolifaces.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 ---> Package kde-workspace-libs.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kdeartwork.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdeartwork-kxs.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork-kxs.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdeartwork-screensavers.x86_64 0:4.10.5-1.fc19 will be updated ---> Package kdeartwork-screensavers.x86_64 0:4.11.1-1.fc19 will be an update ---> Package kdm.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kdm.x86_64 0:4.11.1-2.fc19 will be an update ---> Package kgreeter-plugins.x86_64 0:4.10.5-3.fc19 will be updated ---> Package kgreeter-plugins.x86_64 0:4.11.1-2.fc19 will be an update ---> Package konsole.x86_64 0:4.10.5-1.fc19 will be updated ---> Package konsole.x86_64 0:4.11.1-1.fc19 will be an update ---> Package konsole-part.x86_64 0:4.10.5-1.fc19 will be updated ---> Package konsole-part.x86_64 0:4.11.1-1.fc19 will be an update ---> Package libkworkspace.x86_64 0:4.10.5-3.fc19 will be updated ---> Package libkworkspace.x86_64 0:4.11.1-2.fc19 will be an update ---> Package mesa-libwayland-egl.x86_64 0:9.2-1.20130902.fc19 will be updated ---> Package mesa-libwayland-egl.x86_64 0:9.2-1.20130919.fc19 will be an update ---> Package plasma-scriptengine-python.x86_64 0:4.10.5-3.fc19 will be updated ---> Package plasma-scriptengine-python.x86_64 0:4.11.1-2.fc19 will be an update --> Running transaction check ---> Package kde-workspace-libs.x86_64 0:4.10.5-3.fc19 will be updated --> Processing Dependency: libsolidcontrol.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 --> Processing Dependency: libsolidcontrolifaces.so.4()(64bit) for package: contour-0.3-2.fc19.x86_64 ---> Package xcb-util-image.x86_64 0:0.3.9-2.fc19 will be installed ---> Package xcb-util-keysyms.x86_64 0:0.3.9-2.fc19 will be installed --> Finished Dependency Resolution Error: Package: contour-0.3-2.fc19.x86_64 (@fedora) Requires: libsolidcontrolifaces.so.4()(64bit) Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates) libsolidcontrolifaces.so.4()(64bit) Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates) Not found Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora) libsolidcontrolifaces.so.4()(64bit) Error: Package: contour-0.3-2.fc19.x86_64 (@fedora) Requires: libsolidcontrol.so.4()(64bit) Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates) libsolidcontrol.so.4()(64bit) Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates) Not found Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora) libsolidcontrol.so.4()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Thanks. Scott -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Suspension problem last 2 days
Ed Greshko wrote: I've been having a problem on my Thinkpad T61 for the last 2 days. In fact since "yum update" installed kernel-PAE-3.11.1-200.fc19.i686, though that is probably a coincidence. >>> Would it be possible to boot into the previous kernel to verify if it is >>> a coincidence? >> I'm afraid I'm not sure how to do that. >> I'd be happy to try if someone could suggest the way. > When you boot your system, don't you have a menu to select up to 3 > kernels? You are quite right, of course, I was being stupid. I find that when I boot into 3.10.10-200.fc19.i686.PAE there appears to be no problem. (I'm currently running 3.11.1-200.fc19.i686.PAE.) -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 19, KDE 4.11.1, no login screen
On 22/09/13 09:01, Anthony Messina wrote: > > What did you find "damaged" in /var/log/journal? I ask because I see this > KDM > failure as well, only on one of my machines, but journalctl --verify passes > with flying colors. Also, when I issue systemctl restart display-manager > after the initial failure, KDM starts properly. no idea I followed this suggestion. http://www.linuxquestions.org/questions/fedora-35/fedora-boot-problem-4175468468/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Problems booting Fedora 19 with UEFI
Hi, I recently purchased a Dell Inspiron 5721 which came with Windows 8. I would like to dual boot this with Fedora but am having problems running the Fedora Install. I have Fedora-19-x86_64-DVD.iso on usb, and whenever I boot with UEFI (secure on or off), the boot process hangs at the line, Reached target Basic System: [ 12.650116] localhost systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [ 12.650553] localhost systemd[1]: Starting Paths. [ 12.650962] localhost systemd[1]: Reached target Paths. [ 12.651376] localhost systemd[1]: Starting Basic System. [ 12.651829] localhost systemd[1]: Reached target Basic System. And then bails out after a few minutes and starts up the Dracut Emergency Shell: [ 35.729286] localhost multipathd[108]: sdc: add path (uevent) [ 35.915042] localhost multipathd[108]: sdc: update path write_protect to '0' (uevent) [ 36.008982] localhost multipathd[108]: sdc: update path write_protect to '1' (uevent) [ 197.571596] localhost dracut-initqueue[395]: Warning: Could not boot. [ 197.574126] localhost dracut-initqueue[395]: Warning: /dev/root does not exist [ 197.578383] localhost systemd[1]: Starting Dracut Emergency Shell... I have pasted the full sosreport.txt at http://pastebin.com/4stUgUDN Please note that if I install in basic graphics mode, I still get the same result. The only way I can get the install to work, is if I boot in legacy mode. Unfortunately after doing this, I can no longer boot up Windows. If anyone knows how to fix this, I'd be really grateful for some help :-) Many thanks, Ed -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 19, KDE 4.11.1, no login screen
On Saturday, September 21, 2013 07:34:42 PM andrea wrote: > > [FAILED] Wait for Plymouh Boot Screen to quit > > > > > > > > and in /var/log/messages > > > > > > > > there is something about > > > > > > > > Sep 21 15:24:35 localhost kdm[335]: plymouth --ping -> 0 > > Sep 21 15:24:35 localhost kdm[335]: plymouth is running ... > > Sep 21 15:24:35 localhost kdm[335]: plymouth deactivate -> 0 > > Sep 21 15:24:35 localhost kdm[335]: plymouth --has-active-vt -> 0 > > Sep 21 15:24:35 localhost kdm[335]: plymouth should quit when server > > starts > > Sep 21 15:24:36 localhost kdm[335]: plymouth is active on VT 1, reusing > > for :0 Sep 21 15:24:36 localhost kdm[335]: X server startup timeout, > > terminating Sep 21 15:24:36 localhost kdm[335]: X server for display :0 > > cannot be started, session disabled> > > > > > > any idea? > > > > > > in the end something damaged in /var/log/journal > > google it, it turned out that some services took too long to start. > not too sure, but renaming that folder fixed it. What did you find "damaged" in /var/log/journal? I ask because I see this KDM failure as well, only on one of my machines, but journalctl --verify passes with flying colors. Also, when I issue systemctl restart display-manager after the initial failure, KDM starts properly. -A -- Anthony - http://messinet.com - http://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E signature.asc Description: This is a digitally signed message part. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
not been configured -
After an update I noticed the following and wonder if it has any bearing on this computer's inability to print crosswords from Firefox. The print GUI menu comes up but is grayed (printing works normally from other app's) ... Seamonkey and Midori do print them. snip ... Cleanup: mesa-libGL-9.2-1.20130902.fc19 47/62 Cleanup: mesa-libGLES-9.2-1.20130902.fc19.x86_64 48/62 Cleanup: mesa-dri-drivers-9.2-1.20130902.fc19.x86_64 49/62 Cleanup: 1:java-1.7.0-openjdk-devel-1.7.0.60-2.4.2.1.fc19.x86_64 50/62 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.1.fc19.x86_64/bin/javac has not been configured as an alternative for javac /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.1.fc19.x86_64 has not been configured as an alternative for java_sdk_openjdk /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.1.fc19.x86_64 has not been configured as an alternative for java_sdk_1.7.0 Cleanup: mesa-filesystem-9.2-1.20130902.fc19.x86_64 51/62 Cleanup: mesa-libglapi-9.2-1.20130902.fc19 52/62 Cleanup: systemd-libs-204-11.fc19 53/62 Cleanup: 1:java-1.7.0-openjdk-1.7.0.60-2.4.2.1.fc19.x86_64 54/62 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.1.fc19.x86_64/jre/bin/java has not been configured as an alternative for java /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.1.fc19.x86_64/jre has not been configured as an alternative for jre_openjdk /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.1.fc19.x86_64/jre has not been configured as an alternative for jre_1.7.0 Cleanup: mesa-libglapi-9.2-1.20130902.fc19 . snip . A minor problem but an annoyance. Bob -- http://www.qrz.com/db/W2BOD box10 Fedora-19 Linux/XFCE -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Goa daemon eats all my cpu
On Sat, 21 Sep 2013 23:06:43 +0200 William Murray wrote: > Thanks Reindl, > Of course I stupidly killed it and do not know what > causes it to start. I'll > try to post this when I next have the problem -might be a couple > of days. Bill > https://fedoraproject.org/wiki/Features/OnlineAccountsService -- Regards, Frank www.frankly3d.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
