Good day, friends.
Have some trouble with a52dec package. During dnf upgrade a52dec it need liba52, and finaly we get conflict
file /usr/lib64/liba52.so.0.0.0 from installing package liba52-0.7.4-25.fc24.x86_64 conflict with file from package a52dec-libs-0.7.4-20.fc24.x86_64
Please fix this.
Информация, содержащаяся в этом документе и приложениях к нему, может быть использована только получателем. Отправитель не несет юридической ответственности за содержание данного сообщения. Если это письмо попало к Вам случайно, пожалуйста, срочно удалите данный документ. Не посвящайте в содержание этого документа кого либо еще и не делайте копий. Совершение данных действий является противозаконным.
I'm using Fedora 25 on an HP laptop with KDE. I commonly use a VPN
service, but it leaks ipv6 addresses. This seems to be a common
problem with VPN and ipv6, from what I've read on the internet.
So, I've turned off ipv6 for my wireless interface, and that seems to
solve the problem. However, I just can't help but think that this will
eventually cause a problem somewhere.
Is there a better solution for ipv6 leakage with a vpn on Fedora 25
other than just turning it off?
Since upgrading to F25, I no longer get a graphical login page.
I have run systemctl set-default graphical.target and runlevel5.target and
default.target both point to graphical.target but I still get the
normally, I'm using a gnome (wayland) desktop sessions. If I started
(only once) the gnome classic session, then logging out and
thenre-logging in again with the usage of gnome (wayland), I still get a
gnome classic session. Only after restarting my box, I can again run
gnome (wayland) sessions.
My login manager is gdm.
Anybody sees this too?
Fedora release 25 (Twenty Five)
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
I am trying out multiple video editors on Fedora, with very poor results
and a ton of crashes.
Anyone have recommendations on how to stablize one of these or can you
video editor that just works (like kdenlive used to when I used it last a
I am having the same results on two Fedora 25, 64-bit systems, fully
updated. The packages
are from rpmfusion and on one of the two systems from unitedrpms. My main
system is an
older 6-core AMD with 8G of RAM so it should handle it.
The files I am testing with are:
JPG images from a DSLR
Quicktime from my DSLR (MVI_xxx.MOV),
Movie from my Android phone xxxxxxxxx.m2ts
Movie from a DVD xxx.mpg
Movie from a digital camcorder (Sony AVCHD): xxxx.MTS
My goto editor was Kdenlive, but it won't open files. I keep getting "clip
The terminal outputs:
mlt_repository_init: failed to dlopen /usr/lib64/mlt/libmltavformat.so
(/lib64/libavdevice.so.57: symbol av_buffersink_get_sample_aspect_ratio,
version LIBAVFILTER_6 not defined in file libavfilter.so.6 with link time
I think there is a lib miss-match.
Pitivi is nice, but I can't keep it running. Multiple core dumps.
I really love OpenShot. I tried the one from rpmfusion and it crashed all
for example when trying transitions. I also tried the latest version via
This seemed much more stable, but I could still crash it with transitions,
an MP3 file for audio, etc.
Anyone have a good, stable video editor or have suggestions on how to run
one of these
in a stable platform?
Note, I am filing bug reports on many of these crashes....
I occasionally have this strange mouse issue in VirtualBox.
Running an update version of Fedora 25 with GNOME and wayland. (64 bit)
Most recent VirtualBox 5.1.22
Guest Windows 10 with Guest Additions Installed.
Sometimes the mouse partially stops working and the only way to reset it I've found is to power off
When I say partially I mean
1) mouse pointer still moves
3) it can be used to trigger the GNOME task switcher (top left corner)
4) no other control responds to clicks
As soon as the Guest stops, everything starts working again.
Keyboard still works and this is what I use to gracefully shut down the guest.
Somehow the mouse click event is trapped by Virtual Box and cannot be used.
I know it makes little sense, but this is my best description at the moment.
The "f24 boot fails; need help" problem set me back a week. I'm still
catching up. I seriously believe it would be foolish for me to just
forget it. I should for the benefit of others try to get at the real
cause and possible prevention.
A few hours before the failure, I received and looked at an e-mail that
I'm almost certain was at least a spoof, and possibly malicious. I know
it contained html and links. I did *** not ***
click any of the links. I looked at it, and deleted it. It was viewed
in Thunderbird only. The message's "From" ended with "yahoo.com". My
question: It is highly improbable that that message had anything to do
with the boot failure. Am I correct?
Also a few hours before the failure, I did some web browsing using
Firefox with NoScript and uBlock Origin. As best as I recall, the
"riskiest" sites that I visited were finance.yahoo.com (and a few of its
sub-pages, I clicked no ads, no ad links) and indeed.com (possibly and a
posting or two). My question: It is highly improbable that my web
browsing had anything to do with the boot failure. Am I correct?
Begin forwarded message:
I forwarded this to test since F26 is still not released, and they are
deciding whether to release this week. You are much more likely to get
an answer to your question there.
Date: Mon, 29 May 2017 16:46:05 +0200
From: Andrej Podzimek <andrej(a)podzimek.org>
Subject: Systemd keeps trying to re-open an already active LUKS volume
I need a piece of advice concerning an encrypted root partition on
Fedora 26. I'm running a custom manual setup created using dnf.
* The installation procedure is outlined in this tread -- and quite
likely irrelevant to this question anyway:
* The disk layout is described in this comment:
Unlike Fedora 23 and 24, both of which booted just fine, Fedora 26 has
two glitches related to my encrypted LUKS root partition:
1. Dracut fails to automatically add the crypt module. It doesn't seem
to care about LUKS-related settings in /etc/default/grub and/or about
the fact that the system runs off an encrypted volume. I had to
manually add add_dracutmodules+="crypt" into /etc/dracut.conf, or else
I wouldn't get a password prompt on boot and the early systemd would
freeze waiting for the root partition to appear. It works normally with
2. Possibly as a consequence of (1), systemd doesn't realize that the
root partition has been already activated and luksOpen'ed at boot time
and keeps trying to unlock it over and over. The consoles are spammed
by messages like this one, basically on every sudo invocation: Password
entry required for 'Please enter passphrase for disk cryptprdell-luks
(plainprdell)!' (PID 5492). Please enter password with the
Of course I tried to run the systemd-tty-ask-password-agent tool and
type in the password. But then systemctl --failed showed a failure in
systemd-cryptsetup(a)plainprdell.service, the auto-generated unit for the
LUKS volume. Presumably, journalctl revealed that the error message had
been "Failed to activate: Device or resource busy". Well, that's indeed
what happens when you try to open a LUKS volume that's already opened.
If I don't use systemd-tty-ask-password-agent at all, systemctl status
permanently shows "starting" and never reaches "running", because of
the LUKS volume it thinks it needs to activate. (I tried systemctl
disable, but nope, that had no effect.)
This appears to have something in common with an ancient bug from 2013:
Has anything changed (1) in the way Dracut finds out whether the crypt
module is needed (which worked at least up to Fedora 24) or (2) in the
way systemd generates its automatic units for encrypted volumes?
Something must have changed, but I have no idea what it is and how to
get the old behavior back. :-/
My /etc/default/grub and /etc/crypttab are attached. The current kernel
version is 4.11.0-2.fc26.x86_64.
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
I asked on AskFedora and got no response. Hoping this list is more active.
I have a f24 workstation (nfs client). It is updated regularly.
The server is f19, so no updates there.
A problem started in the last few weeks. When I examine a file on the server it
looks OK. The file is updated every minute (collecting some stats) and 'tail' shows
the added lines as they arrive.
Examining the same file from the workstation is initially OK, but then, as the file
grows, I get binary zeroes at the end of the file. The same with tail, less, vi, etc.
The amount of zeroes seems to be the size of the extra data appended to the file.
'ls' shows the actual (full) size of the file. It looks like the utilities see the
correct size but bad data is delivered at the tail.
After a few minutes the full data is showing but then, as the file grows, again I get
zeroes for a few minutes.
Where do I look next?
Eyal Lebedinsky (eyal(a)eyal.emu.id.au)