users June 2014

users@lists.fedoraproject.org

150 participants
151 discussions

Problem installing google-earth-stable.
by Erik P. Olsen 20 Jun '14

20 Jun '14

Have downloaded google-earth-stable and got the following installing the package: Installing: google-earth-stable x86_64 7.1.2.2041-0 /google-earth-stable_current_x86_64 194 M Transaction Summary ================================================================================ Install 1 Package Total size: 194 M Installed size: 194 M Is this ok [y/d/N]: y Downloading packages: Member: google-earth-stable.x86_64 0:7.1.2.2041-0 - u Adding Package google-earth-stable-7.1.2.2041-0.x86_64 in mode u Running transaction check Transaction check time: 0.026 Running transaction test Transaction check error: file /usr/bin from install of google-earth-stable-7.1.2.2041-0.x86_64 conflicts with file from package filesystem-3.2-19.fc20.x86_64 Is it a sick package? -- Erik

3 3

Re: The new skype-4.3.0.37 is out. Build your own rpm for Fedora 20
by Rahul Sundaram 20 Jun '14

20 Jun '14

Hi On Fri, Jun 20, 2014 at 2:47 PM, Paul Cartwright wrote: > On 06/20/2014 02:44 PM, Rahul Sundaram wrote: > > Well, the older versions will stop working at some point and you won't > > get any support for it. So unless you want to stop using Skype > > completely, you don't really have a choice. > > > > Rahul > or do it on: > [snipped alternative operating system list] Sure. This being, the Fedora users mailing list, the default context is naturally just Fedora unless stated otherwise. Rahul

1 0

Re: The new skype-4.3.0.37 is out. Build your own rpm for Fedora 20
by Sudhir Khanger 20 Jun '14

20 Jun '14

On Fri, Jun 20, 2014 at 9:09 PM, Paul Cartwright <pbcartwright(a)gmail.com> wrote: > What is wrong with the official RPM? sudo yum -y install libXv.i686 > libXScrnSaver.i686 qt.i686 qt-x11.i686 pulseaudio-libs.i686 > pulseaudio-libs-glib2.i686 alsa-plugins-pulseaudio.i686 qtwebkit.i686 > sudo yum install skype-<version>-fedora.i586.rpm works just fine. > > No package skype-4.3.0.37-1.fc20.i686.rpm available. > No packages marked for update > [root@pauls-server backups]# yum update skype-4.3.0.37-1.fc20.i586.rpm > Loaded plugins: langpacks > No Match for argument: skype-4.3.0.37-1.fc20.i586.rpm > No package skype-4.3.0.37-1.fc20.i586.rpm available. > No packages marked for update > [root@pauls-server backups]# yum update skype-4.3.0.37-1.fedora.i586.rpm > Loaded plugins: langpacks > No Match for argument: skype-4.3.0.37-1.fedora.i586.rpm > No package skype-4.3.0.37-1.fedora.i586.rpm available. > No packages marked for update > [root@pauls-server backups]# yum update skype-4.3.0.37-1.fedora.i686.rpm > Loaded plugins: langpacks > No Match for argument: skype-4.3.0.37-1.fedora.i686.rpm > No package skype-4.3.0.37-1.fedora.i686.rpm available. > No packages marked for update > > > -- > Paul Cartwright > Registered Linux User #367800 and new counter #561587 > What are you doing? Skype is a closed source package. What made you think it might be available in Fedora repository. You are suppose to download the Skype package from official source skype.com. 64 bit system - Install both dependencies and skype package. 32 bit system - Just install the skype package. For those wanting hassle free updates I highly suggest negativo's repository[1]. [1] http://negativo17.org/skype-and-skype-pidgin-plugin/ -- Regards, Sudhir Khanger. sudhirkhanger.com https://github.com/donniezazen

1 0

yum update from 3.14.4 looks ok, but still stuck 3.14.4-200.fc20.x86_64
by Jackson Byers 19 Jun '14

19 Jun '14

yum update from 3.14.4 looks ok in /boot vmlinuz-3.14.3-200.fc20.x86_64 vmlinuz-3.14.4-200.fc20.x86_64 vmlinuz-3.14.7-200.fc20.x86_64 I can't seem to get 3.14.7 to 'take' after reboot still in 3.14.4 exact command used for update: yum update && grub2-mkconfig -o /boot/grub2/grub.cfg followed by a reboot, still get: $ uname -r 3.14.4-200.fc20.x86_64

6 8

SMB Browser Election Thread (Was: Case for an occasional system refresh or clean install)
by Temlakos 19 Jun '14

19 Jun '14

To Tim in Australia: That must be it. The machine I was retiring (see the other thread) was indeed the Master Browser. The replacement machine and the laptop both accepted it in that role. And after I retired the machine, neither of the other machines could browse. After awhile, they would see the Windows machine. Which does not run all the time, by the way, but I will address that in another thread. Anyway: after several hours of running the replacement machine and the laptop, and correcting the configuration file and service-start instructions on both, they seem to have settled on a regular Master Browser. Hosts come up very quickly, without delay. With that said: you mentioned installing Network File System in a Windows environment. (Mine's Windows 8.1.) I'd like to know how to get NFS to run between two Linux boxes. That would be a start. Then I could think about installing an NFS service and configurator on the Windows machine. Temlakos

2 1

Video capture in Windows and Linux
by Temlakos 18 Jun '14

18 Jun '14

Tim in Australia: You asked, in another thread: > I'd be interested to know what you use for that (software and hardware). > I've yet to find anything that isn't painful, or actually works. The current hardware: Lenovo IdeaCenter K450. 12 GB RAM, Intel Core i5, clock speed > 3 GHz. Has three clock-speed settings and a "hardware switch" to set them. I run it in Turbo mode, described as suitable for gaming. Hauppauge Computer Works' HD-PVR2, the Gaming Edition. Set for a Sony Playstation. Accepts component video from a set-top box. (They can't encrypt component video, but they can and do encrypt HDMI.) Hauppauge Video Capture application and service. The service listens to a physical button on the capture box. Push the button, and the capture will begin at once. The product: a video using the H.264 video and MP4 audio codecs. Sampling rate: set at 14 Kbps and constant. Uses the Transfer Stream (.ts) container. I then use Nero's Platinum (version 14) software for authoring of DVD and Blu-Ray disks. To produce the latter, I replaced the existing optical drive with a Blu-Ray burner from LG. (I forget the model number just now. It's rated at 14-spin.) Hauppauge Computer Works is the clear winner for video capture devices. And they are the only company that builds a capture device for American high-definition television (1920 x 1080, interlaced). Level of satisfaction: fair. Every now and again, a captured video will not transcode. It will hang at a certain scene--always the same scene if I try to abort and restart, so nothing will serve except to capture it all over again. (Which is why I always capture a DVR recording, or at least have a DVR running to back me up in case the live capture fails.) I have found that nothing less than two hours of total down time (physical power-off shutdown) will suffice to cool down the processor before I can make another capture. (If I try to "just be patient" and let the authoring tool complete the transcode, it will transcode all right--but the optical disk it produces will be unplayable--a "coaster.") And even then--well, just now I am waiting to try for the third time to capture a recording. And I have enough coasters to set a table for an IT banquet. Now anyone here can jump in to tell me whether the MythTV project has anything going with the Hauppauge HD-PVR2. And how soon Linux will be able to "just play" a Blu-Ray disk, either commercial or one of my home-burn jobs. Temlakos

2 3

Save everybody some surprises in Fedora 22!
by Ales Kozumplik 18 Jun '14

18 Jun '14

Hello, The time when DNF will take over from Yum in Fedora is nearing. We're wondering: is there stuff people are still missing from DNF that they have got recently in Yum? Or even something else! We've put together a very short and simple survey. Let your opinion be heard! http://dnf.baseurl.org/2014/06/06/vote-for-yum-features-that-you-miss-in-dn… Ales

33 103

Why won't smbd and nmbd start automatically on system start?
by Temlakos 18 Jun '14

18 Jun '14

Everyone: I have two computers, one desktop and one laptop. I did clean installs on both. In the process, I retired a third computer that had been running samba without incident for years. Today I can get samba running on both machines. But: I have to execute two commands: $ sudo /sbin/smbd -D $ sudo /sbin/nmbd -D by hand, in a terminal (Konsole), every time I start or restart either computer. The system-config-services app fails to note that smbd or nmbd are even available for starting. How do I get those two daemons to start automatically, so that I don't have to type those two commands every time? Because until I do, I have no file-sharing capability. (I have yet another computer on my network: a dedicated Windows box that I use for video capturing. I've said on other threads I am not satisfied with the video-capture and DVD authoring support Linux provides, and note that Linux does not support Blu-ray, in playback or especially in burning. So samba is a must for me.) Temlakos

6 8

Case for an occasional system refresh or clean install
by Temlakos 18 Jun '14

18 Jun '14

Everyone: No complaints here. Just some insights from some recent experiences. Bottom line: everyone who administers a Fedora system, should do a "clean install" or an effective system refresh (reinstalling the OS and all apps on a system having a separate /home partition) at least, I would say, once for every three new versions of Fedora. The "fedup" app lets too many minor faults accumulate in a system over time. Result: you are cheating yourself and your users of a good user experience. Long ago I did a yum upgrade from F14 to F17. At first everything went swimmingly. And then I got the problem some of you might remember my complaining about: after two hours of operation, or maybe four or five or six hours if I were especially blessed (or as quickly as five minutes if I were under a special curse), new windows and dialog boxes would open as an unrelieved black. (Some KDE pop-up menus and notifications would pop up as a transparent outline.) I filed bug after bug after bug with Bugzilla. I re-filed with every new upgrade, which I accomplished with fedup. From F17->F18, F18->F19, and F19->F20, the problem persisted. Frankly I'm surprised the PTB's didn't CLOSE the bug as WONTFIX. Two weeks ago I acquired a new, replacement machine for one of the two mini-towers on myh network. At the same time, the mouse on my F20 machine went wild, opening and closing windows and pushing buttons without my conscious input, so I couldn't stop it. Finally the mouse just quit. I figured out what happened: the mouse cable had frayed. Happily, with the new shipment, I got a USB mouse and a USB keyboard that I now can keep as spares. But I decided to put F20 on another machine I had intended to replace. (It was a video-capture machine, and I needed a faster processor with more memory to do it properly.) I figured, why not go from a Pentium Dual-Core with 3 GB RAM and a 500-GB HDD to an Intel Core 2 Quattro with 8 MB RAM and a 1TB HDD? This involved downloading and burning an F20 KDE live spin, inserting it into the intended replacement machine, and doing a complete system format--reclaim the drive space, put in the new automatic partition (50 GB for /, 8 GB of swap, 500-MB physical boot partition, and all the rest, 790 GB, for /home), install F20 from the Internet, and painstakingly replicate my old environment--or at least those parts of it I wanted. Fresh install of samba, Firefox, Thunderbird, gnucash, and any other application I used regularly. I learned later that the old machine had been providing a crutch for samba connectivity to other machines on the network. When I retired the old machine, I lost that. Temporarily. I had to relearn everything I'd learned and forgotten about configuring samba by directly editing the smb.conf file. But now I have two machines--a desktop and a laptop--that can establish samba connectivity independently. But that black rectangle problem I complained about? That is now solved! And something else: dialog buttons have a new, "more modern" look. This should have come with the F19->F20 fedup upgrade. But it did not. It came with a clean install on a brand-new physical box, to which I have migrated all my "stuff." I can only conclude that the yum upgrade introduced the first of several cumulative errors. Every upgrade since then, introduced another one, and another, and another. These errors pile up. They won't cause a catastrophic failure, but they will create several annoying problems you might never solve. To the development team that gave us fedup, listen up! Your application is not taking care of all these little things. With /home partitioned off separately (as an LVM partition), I assume I can install F21 "cleanly" in the / partition without risking losing the contents of /home or my access to them. But I still have to write down every modification I made to a configuration file--or else keep copies of those files in /home. They would include, I also assume, things like the files holding the UIDs, GIDs, and passwords for Users and Groups. That's the only reason I don't plan to do a clean install every time. But I wouldn't mind doing it every other time, or every third time. To make sure these cumulative errors don't build up again. Again, I offer this to provide some insight into problems that we "amateur system administrators" sometimes have. Temlakos

5 6

Routing table suddenly limited
by Temlakos 18 Jun '14

18 Jun '14

Everyone: Have you ever seen this result from the command route -n? Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 1024 0 0 wlp3s0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp3s0 The "wlp3s0" is a wireless interface. But I have another computer that uses a regular Ethernet interface. The result, except for a different interface name, is the same. As a result, Samba suddenly won't work for me anymore. The only difference is, I permanently retired an old computer from my home network. That computer had been running Fedora 20, and I had made updates since Fedora 12. Now, with that computer no longer part of the network, neither of the two Linux boxes can see the other. But either of them can see a Windows physical box, so long as that box is turned on. Temlakos

4 5

← Newer
1
...
6
7
8
9
10
11
12
...
16
Older →

Jump to page: