users June 2017

users@lists.fedoraproject.org

104 participants
95 discussions

Multifuncional Brother MFC-9320CW
by Lucélio Gomes de Freitas 25 Jun '17

25 Jun '17

Hi, Somebody helps? Old "Fedora 20-x86_64" installed and working(printer&scanner) with my Brother MFC-9320CW. Due to a hardware problem, I had to change my motherboard. All worked fine, until I decided to update the system. After I installed Fedora-Kde-live-25-1-3, I lost access to the scanner of the MFC-9320CW, and now I have 2 problems: 1) Don't have scangui anymore, skanlite seems that does't work with wi-fi devices. Printing is working ok. 2) When I shutdown the system, dolphin ends with a segmentation fault(11). Need help, please. Thanks.

2 1

Thunderbird and mailing lists
by Samuel Sieb 25 Jun '17

25 Jun '17

This is just a note for all the Thunderbird users that have been finding the reply button has stopped working properly and has been sending replies back to the sender instead of the list. According to https://www.mozilla.org/en-US/thunderbird/52.0/releasenotes/ : "When replying to a mailing list, reply will be sent to address in From header ignoring Reply-to header" There is a reply to list button at the top and for the shortcut users, it's CTRL-SHIFT-L.

2 1

Problem updating wine-core in FC25
by Jon Ingason 24 Jun '17

24 Jun '17

I get following error message when running "dnf update": ... Running transaction check Transaction check succeeded. Running transaction test The downloaded packages were saved in cache until the next successful transactio n. You can remove cached packages by executing 'dnf clean packages'. Error: Transaction check error: file /usr/share/doc/wine-core/ANNOUNCE from install of wine-core-2.10-1.fc25.i 686 conflicts with file from package wine-core-2.9-1.fc25.x86_64 file /usr/share/doc/wine-core/VERSION from install of wine-core-2.10-1.fc25.i6 86 conflicts with file from package wine-core-2.9-1.fc25.x86_64 Error Summary ------------- Someone having same problem? Some solution? -- Regards Jon Ingason

4 11

gdm won't start gnome (wayland) session after running once a gnome-classic session
by Joachim Backes 23 Jun '17

23 Jun '17

Hi all, 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? Kind regards Joachim Backes -- Fedora release 25 (Twenty Five) Kernel-4.10.10-200.fc25.x86_64 Joachim Backes <joachim.backes(a)rhrk.uni-kl.de> https://www-user.rhrk.uni-kl.de/~backes/

2 1

OT: smplayer will not play playlist
by JD 23 Jun '17

23 Jun '17

Version: 17.6.0 (revision 8580) Tried to play the YT link: https://www.youtube.com/playlist?list=PLwK8hxZy7wr-kuJ4a9UV2OeBlxon2oFHQ and nothing ....

1 0

[F25] only black screen with KDE Plasma session
by Frédéric Bron 23 Jun '17

23 Jun '17

Hi, Since this morning, after loging in on a Plasma KDE session, I can first see the desktop then only a black screen with only the mouse available, nothing else. Ctrl+Alt+Suppr, brings the log out screen so I can log out. I can also switch to a text terminal with Ctrl+Alt+F2. That's all. Before turning the computer off yesterday, I updated my packages (see below the details of the transaction). How can I get back my normal screen so that I can work again? Frédéric # dnf history info last ID de transaction : 220 Temps de début : Thu Jun 22 19:15:19 2017 Début de RPMDB : 3204:6cb0ac26f6ff78822ef897069e76afa82cd02c1b Temps de fin : 19:15:28 2017 (9 secondes) Fin de RPMDB : 3204:53773cfc24afe7f55b910af08d9d45c2fcc58ac5 Utilisateur : Frédéric Bron <fred> Code de retour : Réussi Ligne de commande : update -y Transaction effectuée avec : Installé dnf-1.1.10-6.fc25.noarch @updates Installé rpm-4.13.0.1-1.fc25.x86_64 @updates Paquets modifiés : Mis à niveau google-chrome-stable-59.0.3071.104-1.x86_64 @google-chrome Mettre à jour 59.0.3071.109-1.x86_64 @google-chrome Mis à niveau leptonica-1.74.1-1.fc25.x86_64 @updates Mettre à jour 1.74.4-1.fc25.x86_64 @updates Mis à niveau tbb-2017.6-1.fc25.x86_64 @updates Mettre à jour 2017.7-1.fc25.x86_64 @updates Sortie du scriplet : 1 Redirecting to /bin/systemctl start atd.service

5 20

Package conflict: chromium-libs-media-freeworld from rpmfusion
by K. Cong 22 Jun '17

22 Jun '17

Does anyone know the situation of Chromium and chromium-libs-media-freeworld? It seems the new chromium-libs-media-freeworld package from rpmfusion-free-updates has some conflicts with packages in updates. dnf update gives me the following: Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): chromium-libs-media-freeworld x86_64 59.0.3071.104-1.fc25 rpmfusion-free-updates 2.2 M

2 1

lightdm-gtk segfaults on first time login
by Kryptxy 22 Jun '17

22 Jun '17

Hello, I have been facing an issue with lightdm-gtk since I installed Fedora 25 (mate desktop) in my system. When I boot system and try login for the first time, lightdm-gtk segfaults and screen goes blacks for a second or so. Then lightdm-gtk re-appears asking for login credentials again. The second time I enter credentials, login is successful. dmesg - lightdm-gtk-gre[1143]: segfault at 10 ip 00007fa3023fbf70 sp 00007ffcf876f828 error 4 in libcairo.so.2.11400.8[7fa30238e000+122000] I filed a bug for same. Here: https://bugzilla.redhat.com/show_bug.cgi?id=1463847 Did anyone else had this issue? Is there a workaround for the same? It's really annoying to enter login credentials 2 times everytime when system boots. Thanks. Sent from ProtonMail mobile

3 2

Libvirtd Issues, QEMU/KVM Connecting..... Never does
by InvalidPath 22 Jun '17

22 Jun '17

So today I updated my system (Fedora 25) and it pulled the following virt related updates: > libvirt.x86_64 libvirt-client libvirt-daemon " "-config-network " "-nxfilter " "-driver-interface " " "=libxl " " "-lxc " " "-network " " "-nodedev " " "-nwfilter " " "-qemu " " "-secret " " "-storage " " "-uml " " "-vbox " " "-xen "-glib "-libs > Once these updates were complete I believe the install process restart libvirt because my open VM guest was closed and virt-manager was no longer connected to QEMU. So I right click, tell it to connect and it just sits there. Checking journalctl the only thing I find that's from today is: >Jun 22 10:57:51 Vostok libvirtd[14333]: libvirt version: 2.2.1, package: 2.fc25 (Fedora Project, 2017-05-30-23:29:39, buildvm-17.phx2.fedoraproject.org) Jun 22 10:57:51 Vostok libvirtd[14333]: hostname: Vostok Jun 22 10:57:51 Vostok libvirtd[14333]: Libvirt doesn't support VirtualBox API version 5001016 Jun 22 10:57:51 Vostok audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=libvirtd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jun 22 10:57:52 Vostok libvirtd[14333]: COMMAND_FAILED: '/usr/sbin/iptables -w2 -w --table filter --insert FORWARD --destination 192.168.100.0/24 --out-interface virbr0 --match conntrack --ctstate >ESTABLISHED,RELATED --jump ACCEPT' failed: Now the line about LIbvirt not supporting VirtualBox API version 5001016 has been happening for months. But this Iptables entry is new. Checking iptables I have: >$ sudo iptables-save # Generated by iptables-save v1.6.0 on Thu Jun 22 10:59:47 2017 *security :INPUT ACCEPT [480297:662444293] :FORWARD ACCEPT [3406:273312] :OUTPUT ACCEPT [401307:361870089] COMMIT # Completed on Thu Jun 22 10:59:47 2017 # Generated by iptables-save v1.6.0 on Thu Jun 22 10:59:47 2017 *mangle :PREROUTING ACCEPT [591835:807244244] :INPUT ACCEPT [480297:662444293] :FORWARD ACCEPT [3406:273312] :OUTPUT ACCEPT [401307:361870089] :POSTROUTING ACCEPT [405762:362240145] COMMIT # Completed on Thu Jun 22 10:59:47 2017 # Generated by iptables-save v1.6.0 on Thu Jun 22 10:59:47 2017 *raw :PREROUTING ACCEPT [591835:807244244] :OUTPUT ACCEPT [401307:361870089] COMMIT # Completed on Thu Jun 22 10:59:47 2017 # Generated by iptables-save v1.6.0 on Thu Jun 22 10:59:47 2017 *filter :INPUT ACCEPT [4416:6686704] :FORWARD ACCEPT [59:4713] :OUTPUT ACCEPT [3303:1718179] -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT COMMIT ># Completed on Thu Jun 22 10:59:47 2017 I cannot manually run that Insert either.. says the chain/target/match by that name. I'm assuming FORWARD but IDK for sure. Anyone else ran into something like this? Thanks! ***p.s. I know the Fedora community doesn't write/maintain libvirt, Im just hoping a fellow user has seen this.***

2 2

New Blog on Buildah
by Daniel Walsh 22 Jun '17

22 Jun '17

Buildah is a command line tool that can be used to build container images without requiring the docker daemon. Supports Dockerfile format as well as simple bash scripting. http://www.projectatomic.io/blog/2017/06/introducing-buildah

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →