Opera Mail & Browser after upgrading Fedora31 to Fedora32 . Ed
Greshko.
by Ger van Dijck
Hi all , Hi Ed ,
I did some thinking and studying : A long time ago I found somewhere
opera-stable-54.0.2952.71-1.fc29R.x86_64.rpm but I don't know and have
fotgotten where .
I installed it and in the version fc29, -fc30, and -fc31 it runs fine. In
the version fc32 the application won't launch : So I reinstalled it and
got the message already installed.
I can imagine that this old rpm (fc29) is outdated ,so the question is
where can I find the newest version (opera-stable-68.0.3618.63-0 ((fc32R))
.x86_64.rpm if it exists and install it and then try to launch this newest
application onder fc32 ?
Second problem : Also a long time ago , don't ask me when or where I found
opera-12.16-1860.x86_64.rpm and installed it. Purpose was and is the
possibility to use opera mail wich long ago was under fedora to use and
since the browser was separated opera mail is not running under fedora .
In the versions fc28 , -fc29 , -fc-30 and -fc31 no problems runs fine . In
the version fc32 it is gone . So I tried the reinstall it and got the
following messages
Libgstreamer-0.10.so.0
Libgstbase-0.10.so.0
Libgstvideo-0.10.so.0
are missing.
How going on ?
Kind regards ,
Ger van Dijck.
--
Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/
4 years
Failure to boot after update to Fedora 32
by Andrew Wood
Hello,
I had Fedora 31 installed on my laptop and I decided to update it to
Fedora 32.
After the reboot then Fedora stops and brings up a terminal session.
I'm invited to inspect the system log with 'journalctrl'.
Looking through the log then I have:
May 04 17:03:09 localhost systemd[1]: Started dracut pre-mount hook.
May 04 17:03:09 localhost systemd[1]: Starting File System Check on
/dev/mapper/fedora-root...
May 04 17:03:09 localhost systemd-fsck[544]: /dev/mapper/fedora-root
contains a file system with errors, check forced.
May 04 17:03:12 localhost systemd[1]: Received SIGRTMIN+20 from PID 436
(plymouthd).
May 04 17:03:18 localhost systemd-fsck[544]: /dev/mapper/fedora-root:
Inodes that were part of a corrupted orphan linked list found.
May 04 17:03:18 localhost systemd-fsck[544]: /dev/mapper/fedora-root:
UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
May 04 17:03:18 localhost systemd-fsck[544]: (i.e., without -a
or -p options)
May 04 17:03:19 localhost systemd-fsck[544]: fsck failed with error code 4.
May 04 17:03:19 localhost systemd-fsck[544]: Running request
emergency.target/start/replace
May 04 17:03:19 localhost systemd[1]: systemd-fsck-root.service: Main
process exited, code=exited, status=1/FAILURE
May 04 17:03:19 localhost systemd[1]: Failed to start File System Check
on /dev/mapper/fedora-root.
May 04 17:03:19 localhost systemd[1]: Dependency failed for /sysroot.
May 04 17:03:19 localhost systemd[1]: Dependency failed for Initrd Root
File System.
Any suggestions of how I might fix this? One thing which I don't
understand is the device here. Is it systemd[1]??
Thanks for your help and assistance,
Andrew. Oxford UK
4 years
python3 and gnome packages
by Paolo Galtieri
Folks,
about a week ago I posted an email regarding bindings to libgnome,
but I never did see the post on the list, just one person's response.
The issue is that the program I use for doing backups, sbackup, fails
with python 3. The 2 main failures are in regard to the following:
import gnome.ui
and
import gnome.vfs
or more specifically the packages:
gnome-python2-gnomevfs-2.28.1-23.fc29.x86_64
gnome-python2-gnome.x86_64
so my question is how do I get the same features in python 3?
The gnome.vfs failure occurred after I upgraded from F31 to F32. Under
F31 the front end of sbackup fails because of the lack of gnome.ui.
Under F32 the back end now fails due to the lack of gnome.vfs.
Any help is appreciated.
Paolo
4 years
NetworkManager stymies me again
by Tom Horsley
I was finally going to try to setup my network using nm
in fedora 32. I figured after 10 years or so all the
bits I use might finally work :-).
But, I've defined a bridge with (seemingly) all the
same properties as the fedora 31 bridge I created
with network-scripts, yet my virtual machines using
bridge networking never get an IP address, as if the
router dhcp server never sees them.
Is there some magic I'm missing to make things on the
bridge visible on the physical network?
Here's the commands I used to setup the bridge:
nmcli con show
nmcli con add ifname br0 type bridge con-name br0
nmcli con add type bridge-slave ifname eth0 master br0
nmcli con mod br0 ipv4.ignore-auto-dns yes
nmcli con mod br0 bridge.mac-address xx:xx:...
nmcli con modify br0 bridge.stp no
nmcli con down "Wired connection 1"
nmcli con up br0
nmcli con show
The bridge gets an IP address from the router, but virtual
machines do not:
<interface type="bridge">
<mac address="52:54:00:1c:57:9f"/>
<source bridge="br0"/>
<model type="virtio"/>
<address type="pci" domain="0x0000" bus="0x01" slot="0x00" function="0x0"/>
</interface>
4 years
homed
by Javier Perez
Reading this article, I am beginning to really detest systemd....
Why does it have to hang its tentacles on the home directory?
https://www.techrepublic.com/article/linux-home-directory-management-is-a...
If we continue like this, soon Linux will have a "Registry" and "Registry
Editor"
JP
--
------------------------------
/\_/\
|O O| pepebuho(a)gmail.com
~~~~ Javier Perez
~~~~ While the night runs
~~~~ toward the day...
m m Pepebuho watches
from his high perch.
4 years
minor gnome annoyance
by Tom Horsley
They finally got rid of the "you have to scroll the screen all the
way up from the bottom" to get out of the lock screen.
Now it says click or hit any key.
If you hit a key, it does get you out of the lock screen, but that
key also winds up being passed to the password entry field as the
first character of your password, so then you type your actual
password and get a login error :-).
Stick to clicking.
4 years
Re: Upgrade to 32 stymied
by Frank
On 2020-05-03 2:10 p.m., Ranjan Maitra wrote:
> So, it appears based on your description that rxvt on F32 is behind rxvt on F31. I suspect that in this situation I would do one of two things.
>
> 1. Wait a few days and let the problem take care of itself as the F32 package gets updated.
>
> 2. dnf erase rxvt and upgrade. Then, after the system comes back with F32, dnf install rxvt. Of course, this assumes that you have some terminal window option.
>
> HTH,
>
> Many thanks and best wishes,
> Ranjan
>
>
>
> On Sun, 3 May 2020 12:24:22 -0400 Frank <beacon(a)videotron.ca> wrote:
>
>> I am blocked upgrading my 31 to 32. Updated 31, and did the "sudo dnf
>> system-upgrade download --releasever=32 --allowerasing". It dl 1.2 gigs of
>>
>> packages, and at the very end told me rxvt was being blocked because of
>> a conflict with the newer version.
>>
>> I then ran "sudo dnf system-upgrade reboot" and it said system is not
>> ready for upgrade.
>>
>> I am stumped!
>>
>> Any suggestions??
>>
>>
That's what I ended up doing. It appeared after close examination
that RXVT was the only
thing blocking the upgrade. DNF had not removed the old one even though
I ran DNF with
allow-erasing on the command line.
After I removed RXVT and re-ran DNF system-upgrade with an additional
--setopt=keepcache=1 on the command
line when it finished quite quickly....then dnf system-upgrade reboot
worked fine. A long time later I had my F32 desktop
back. Since then I've had a few crashes but nothing serious.
Thanks
4 years
Re: homed
by J.Witvliet＠mindef.nl
From: "Javier Perez" <pepebuho(a)gmail.com<mailto:pepebuho@gmail.com>>
Date: Sunday, 3 May 2020 at 08:02:29
To: "Community support for Fedora users" <users(a)lists.fedoraproject.org<mailto:users@lists.fedoraproject.org>>
Subject: Re: homed
I wonder about that "encryption". They are encrypting MY home directories with a key that I do not know. I imagine it will be somewhat associated to my login password, but still, what could go wrong?
Encrypting you’re data with a key unknown to you? What could go wrong?
Well, it’s party time at the NSA & CIA.
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
4 years
