running F20 but still have F17, F18, F19 packages installed, why?
by Frédéric Bron
I am running F20. I first installed F18 I guessed or F17, I do not
remember well and used fedup to update my installation.
However, when I can see that packages with .fc17 .fc18 and .fc19 in
there name are still installed (see below). Is that normal?
Frédéric
# yum list installed|grep "\(fc17\|fc18\|fc19\)"
a52dec.x86_64 0.7.4-18.fc19 installed
akmods.noarch 0.5.1-3.fc19 installed
amrnb.x86_64 7.0.0.2-7.fc19
@rpmfusion-nonfree/19
amrwb.x86_64 7.0.0.3-7.fc19
@rpmfusion-nonfree/19
automake14.noarch 1.4p6-24.fc19 installed
automake17.noarch 1.7.9-18.fc19 installed
bouncycastle-tsp.noarch 1.46-6.fc19 installed
btparser.x86_64 0.26-1.fc19 installed
cinepaint-libs.x86_64 1.3-9.fc19
@fedora/19
dansguardian.x86_64 2.10.1.1-11.fc19 installed
directfb.x86_64 1.6.2-3.fc19 installed
easymock2.noarch 2.5.2-9.fc19 installed
fedora-usermgmt.noarch 0.11-1409.fc19 installed
fedora-usermgmt-core.noarch 0.11-1409.fc19 installed
0.11-1409.fc19 installed
0.11-1409.fc19 installed
firstboot.x86_64 19.2-1.fc19 installed
freemind.noarch 0.9.0-13.fc19 installed
gstreamer-plugins-espeak.x86_64 0.4.0-2.fc19 installed
irrXML18.x86_64 1.8-0.12.svn3629.fc18
@updates/18
irrlicht18.x86_64 1.8-0.12.svn3629.fc18
@updates/18
lame.x86_64 3.99.5-2.fc19 installed
lame-libs.x86_64 3.99.5-2.fc19 installed
libdca.x86_64 0.0.5-7.fc19 installed
libdvdcss.x86_64 1.2.12-1.fc17.remi @livna/18
libgssglue.x86_64 0.4-2.fc19 installed
liblqr-1.x86_64 0.4.1-5.fc19 installed
libmad.x86_64 0.15.1b-16.fc19 installed
libmimic.x86_64 1.0.4-6.fc19 installed
libmms.x86_64 0.6.2-3.fc19 installed
libmpeg2.x86_64 0.5.1-10.fc19 installed
opencore-amr.x86_64 0.1.3-3.fc19 installed
pdftk.x86_64 1.44-11.fc19 installed
python-urlgrabber.noarch 3.10-0.fc19
@updates/19
twolame-libs.x86_64 0.3.13-3.fc19 installed
vcdimager.x86_64 0.7.24-6.fc19 installed
vcdimager-libs.x86_64 0.7.24-6.fc19 installed
vo-amrwbenc.x86_64 0.1.2-1.fc19 installed
xorg-x11-drv-modesetting.x86_64 0.8.0-3.fc19
@updates/19
10 years, 3 months
No sound after fedup to F20
by Frédéric Bron
I am under KDE and I can see the sound icon which is not disabled.
Internal analog stereo audio is at 100% but no sound when I listen to
mp3 in VLC or in DragonPlayer or anything else.
I upgraded from F18 using fedup and everything was fine apart from this.
What can I do to find what's the issue?
Regards,
Frédéric
10 years, 3 months
Install problem
by Doug
Trying to install Fedora 32 KDE on second hard drive. This drive has
been partitioned with /dev/sdb1 formatted as NTFS, and /dev/sdb5 and
/dev/sdb6
formatted as ext4. The Fedora install disk says there is only 2.77MB
available on the disk. What gives, and how do I fix it?
After mounting the disk partitions using PCLOS, I do a df -a and see this:
Filesystem Size Used Avail Use% Mounted on
/dev/sdb6 49G 180M 46G 1%
/media/662eba9a-9b8f-41c3-83b9-ebe7a99a27c9
/dev/sdb1 51G 67M 51G 1% /media/094E20372CEB488B
/dev/sdb5 49G 180M 46G 1%
/media/a0ba2017-3c90-4dfb-b946-f737050f63e7
Please advise--doug
10 years, 3 months
Re: Fedup F17 --> F20
by JUSTIN TAYLOR
Well, I wasn't able to find an F18 ISO (guess I wasn't asking Google nicely enough). So, I tried a yum upgrade to F18. Everything looked OK until I rebooted. It gets to the blue bar that moves across the bottom (it says Fedora 18). Then my PC reboots. Normally, I would boot into recovery mode using the disk, but here I don't have one.
Any ideas how to diagnose/fix this?
------------------------------
On Sun, Jan 5, 2014 8:28 PM CST Eddie G. O'Connor Jr. wrote:
>On 01/05/2014 10:01 AM, JUSTIN TAYLOR wrote:
>> Sorry about leaving off the subject... I had a brain fart I guess.
>>
>> So F17 doesn't support fedup huh? A little odd since yum installed it
>> for me. But no matter, I'll download an F18 ISO when I get the chance.
>>
>>
>> Thank you very much!
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>> *From:* Frank Murphy <frankly3d(a)gmail.com>
>> *To:* Frank Murphy <frankly3d(a)gmail.com>
>> *Cc:* users(a)lists.fedoraproject.org; JUSTIN TAYLOR <justay(a)swbell.net>
>> *Sent:* Sunday, January 5, 2014 8:27 AM
>> *Subject:* Re: Fedup F17 --> F20
>>
>> On Sun, 5 Jan 2014 14:22:35 +0000
>> Frank Murphy <frankly3d(a)gmail.com <mailto:frankly3d@gmail.com> wrote:
>>
>>
>> > You can't use fedup to go from F17 --> F20 in one go.
>> > You would need to go to F18 first then maybe F20
>> >
>>
>> Actually fedup want' available for F17, preupgrade was the method.
>> fedup was fro F18+
>>
>>
>>
>> ___
>> Regards,
>> Frank
>> www.frankly3d.com
>>
>>
>>
>>
>>
>I would even go further and say you'd be better off going from F18 to
>F19...and THEN going from F19 to F20.....(I had a few problems going
>F18-->F20....but when I went from F18-->F19-->F20....things seemed to go
>smoother!) just my two cents...
>
>
>EGO II
10 years, 3 months
Is there a akmod like tool for user code?
by Tom Horsley
It is becoming clear that I'm going to have to invent
my own source patches for systemd to make my computers
useable.
Is there any kind of automated tool that will notice
a new version of systemd in the repos, download the source,
apply patches, and build a replacement rpm containing
the patch?
10 years, 3 months
OK, how do I start pulseaudio?
by Tom Horsley
Up through fedora 19 running /usr/bin/start-pulseaudio-x11 in
my ~/.xsession got pulse running. Now on 20 all it does is
provide a pluse daemon that can only speak "dummy output"
How the devil do I get pulse started in a non-gnome,
non-kde session that manually runs my own init script?
10 years, 3 months
Re: Updated to f20, but can only boot f19.
by William Mattison
Good evening,
I followed Chris's suggestions. Thank-you, Chris. Here are relevant
session portions:
=========================
bash.6[~]: grub2-install /dev/sda
Installation finished. No error reported.
bash.7[~]:
-------------------------
[edited /etc/default/grub. here are the new contents]
GRUB_TIMEOUT=8
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 $([ -x
/usr/sbin/rhcrashkernel-para
m ] && /usr/sbin/rhcrashkernel-param || :) rd.luks=0 vconsole.keymap=us
rhgb qui
et nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off"
GRUB_DISABLE_RECOVERY="true"
GRUB_THEME="/boot/grub2/themes/system/theme.txt"
GRUB_GFXPAYLOAD_LINUX=text
-------------------------
bash.14[~]: grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub.cfg ...
Found theme: /boot/grub2/themes/system/theme.txt
Found linux image: /boot/vmlinuz-3.12.8-200.fc19.x86_64
Found initrd image: /boot/initramfs-3.12.8-200.fc19.x86_64.img
Found linux image: /boot/vmlinuz-3.12.7-200.fc19.x86_64
Found initrd image: /boot/initramfs-3.12.7-200.fc19.x86_64.img
Found linux image: /boot/vmlinuz-3.12.6-200.fc19.x86_64
Found initrd image: /boot/initramfs-3.12.6-200.fc19.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-70857e3fb05849139515e66a3fdc6b38
Found initrd image:
/boot/initramfs-0-rescue-70857e3fb05849139515e66a3fdc6b38.img
Found Windows 7 (loader) on /dev/sda1
done
bash.15[~]:
-------------------------
bash.19[~]: fedup --network 20 --debuglog fedupdebug.log
=========================
I also ran the upgrade. I saw no signs of trouble. When the boot menu
came back, Fedora-20 was at the top; it appeared to boot fine, and I
signed in fine. So far, it looks like everything worked ok. The debug
log is fpasted:
bash.4[~]: fpaste fedupdebug.log
Uploading (263.0KiB)...
http://ur1.ca/ghn3f -> http://paste.fedoraproject.org/71198/28951139
bash.5[~]:
I don't know how to determine whether my system is UEFI or BIOS. How do
I do that?
thanks,
Bill.
10 years, 3 months
font selection for chrome tabs
by Ed Greshko
Does anyone know how/where the fonts used in Google Chrome tabs are defined?
I have a system which was upgraded to F20 via fedup from F19. The problem I'm having is that the text in a tab is not being displayed properly when the text is Chinese. Firefox is OK. Also, a newly installed F20 system is also OK.
--
Getting tired of non-Fedora discussions and self-serving posts
10 years, 3 months
Re: F18: new boot-up sequence, but old partitions still in /boot/grub2/grub.cfg !?!?!?
by Rob
Let me comment on my own message:
I believe I forgot to scrutinize the file /etc/default/grub.
This file is 'automagically' created when fedora (grub2 ?) is installed the very first time, and its contents is based on the boot conditions at that time.
When changing the boot conditions later, those changes are NOT 'automagically' progressed into a new /etc/default/grub. I guess this has to be done manually.
The "grub2-mkconfig -o /boot/grub2/grub.cfg" uses the settings in /etc/default/grub to create the grub.cfg file. Hence, without changing the default grub file, the old boot conditions still appear in the /boot/grub2/grub.cfg file.
I found many manual on the web about "how to make a new grub2 boot loader", but none mention to scrutinize the default grub file for old configuration settings.....
(I currently have no access to the troublesome PC, so I will try this later).
R.
On Thu Jan 23 01:10:13 UTC 2014 Chris Murphy <lists at colorremedies.com>
wrote:
>On Jan 22, 2014, at 1:23 AM, Stub <spamrefuse at yahoo.com> wrote:
>>Hi,
>>
>>I have F18 on an i686 PC.
>>
>>Why does the /boot/grub2/grub.cfg still have entries to the logical volumes?
>It's clearly confused, I think the chroot isn't correctly set up.
Thanks Chris Murphy for your feedback.
In fact, I do believe my basic idea was OK, of copying the system files from one disk on the logical volumes to another disk with regular partitions. I could do this safely while booted from a Live USB medium.
It turned out that /etc/default/grub was the culprit that stopped the boot process. This file contains the boot conditions as configured during that first install. The file is 'automagically' created by anaconda during the first full install of the OS. There is a python script in the anaconda package that is responsible for this, but it is (for me) unusable as a stand-alone module.
I you are changing the boot conditions later, then that file needs to be adjusted manually. Unfortunately there is very little information around about what changes should go in there for a given boot sequence......
Fortunately I have another fedora PC that boots from regular partitions and I copied the /etc/default/grub from that PC. After that I created a new /boot/grub2/grub.cfg and recreated the initramfs with dracut (I'm not sure the latter is really necessary).
Then the PC booted flawlessly.
I figured that /etc/default/grub is still a rather undocumented 'feature' of the new grub2 bootloader.....
Regards,
R.
10 years, 3 months
Trying to use mailx for logwatch
by Robert Moskowitz
And the mail is failing. Here is what I have done:
I determined that in: /usr/share/logwatch/default.conf/logwatch.conf
mailer = "/usr/sbin/sendmail -t"
so in: /etc/logwatch/conf/logwatch.conf
mailer = "/usr/bin/mailx -t"
In /etc/aliases I have:
# Person who should get root's mail
root: rgm
and I ran newaliases
'journalctl |grep -i logwatch' shows the following (along with other lines):
Jan 02 03:32:01 lx120e.htt-consult.com run-parts[16112]:
(/etc/cron.daily) starting 0logwatch
Jan 02 03:32:12 lx120e.htt-consult.com run-parts[16429]:
(/etc/cron.daily) finished 0logwatch
Jan 02 03:32:16 lx120e.htt-consult.com setroubleshoot[16427]: dbus
avc(node=lx120e.htt-consult.com type=AVC msg=audit(1388651532.024:734):
avc: denied { write } for pid=16425 comm="mailx" name="root"
dev="dm-0" ino=1308161
scontext=system_u:system_r:logwatch_mail_t:s0-s0:c0.c1023
tcontext=system_u:object_r:admin_home_t:s0 tclass=dir
node=lx120e.htt-consult.com type=SYSCALL msg=audit(1388651532.024:734):
arch=40000003 syscall=5 success=no exit=-13 a0=9b15128 a1=8441 a2=1b6
a3=809134c items=0 ppid=1 pid=16425 auid=0 uid=0 gid=0 euid=0 suid=0
fsuid=0 egid=0 sgid=0 fsgid=0 ses=15 tty=(none) comm="mailx"
exe="/usr/bin/mailx"
subj=system_u:system_r:logwatch_mail_t:s0-s0:c0.c1023 key=(null)
Jan 02 03:32:16 lx120e.htt-consult.com setroubleshoot[16427]:
AuditRecordReceiver.add_record_to_cache(): node=lx120e.htt-consult.com
type=AVC msg=audit(1388651532.24:734): avc: denied { write } for
pid=16425 comm="mailx" name="root" dev="dm-0" ino=1308161
scontext=system_u:system_r:logwatch_mail_t:s0-s0:c0.c1023
tcontext=system_u:object_r:admin_home_t:s0 tclass=dir
Jan 02 03:32:16 lx120e.htt-consult.com setroubleshoot[16427]:
AuditRecordReceiver.add_record_to_cache(): node=lx120e.htt-consult.com
type=SYSCALL msg=audit(1388651532.24:734): arch=40000003 syscall=5
success=no exit=-13 a0=9b15128 a1=8441 a2=1b6 a3=809134c items=0 ppid=1
pid=16425 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0
ses=15 tty=(none) comm="mailx" exe="/usr/bin/mailx"
subj=system_u:system_r:logwatch_mail_t:s0-s0:c0.c1023 key=(null)
Jan 02 03:32:16 lx120e.htt-consult.com setroubleshoot[16427]:
analyze_avc()
avc=scontext=system_u:system_r:logwatch_mail_t:s0-s0:c0.c1023
tcontext=system_u:object_r:admin_home_t:s0 access=['write'] tclass=dir
tpath=/root
oh, here are the mail files:
# ls -ls /var/spool/mail/
total 8
0 -rw-rw----. 1 rgm mail 0 Jan 2 16:47 rgm
8 -rw-------. 1 root mail 5886 Dec 31 12:27 root
0 -rw-rw----. 1 rpc mail 0 Dec 25 13:27 rpc
The content in root mail is from when I had postfix installed. I have
since deleted it to work on getting mailx to work instead.
=================================
perhaps /var/spool/mail/root needs 660 permissions?
10 years, 3 months