firefexx's profile - activity

Thanks. Still wondering why the dedicated pages are down. And the live images you linked also lead to 404. But ok, if th

What happened to the Security Lab in Fedora 29 Does someone know what happened to the Security Lab in Fedora 29? Everyt

deleting ~/.config/pulse and reboot fixed it for me :)

unfortunately journalctl -b does not contain anything related to resolved or DNS

I wanted to try systemd-networkd and systemd-resolved. While they generally seem to work well, I noticed that resolved is not starting automatically on boot despite it is enabled. I have to start it manually afterwards to get working DNS resolution.

After reboot:

# systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: disabled)
   Active: inactive (dead)
     Docs: man:systemd-resolved.service(8)
           http://www.freedesktop.org/wiki/Software/systemd/resolved
           http://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
           http://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients

# systemctl start systemd-resolved

# systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2017-08-15 19:51:07 CEST; 2s ago
     Docs: man:systemd-resolved.service(8)
           http://www.freedesktop.org/wiki/Software/systemd/resolved
           http://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
           http://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
 Main PID: 1321 (systemd-resolve)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/systemd-resolved.service
           └─1321 /usr/lib/systemd/systemd-resolved

Aug 15 19:51:07 ... systemd[1]: Starting Network Name Resolution...
Aug 15 19:51:07 ... systemd-resolved[1321]: Positive Trust Anchors:
Aug 15 19:51:07 ... systemd-resolved[1321]: . IN DS ...
Aug 15 19:51:07 ... systemd-resolved[1321]: . IN DS ...
Aug 15 19:51:07 ... systemd-resolved[1321]: Negative trust anchors: ...
Aug 15 19:51:07 ... systemd-resolved[1321]: Using system hostname '...'.
Aug 15 19:51:07 ... systemd[1]: Started Network Name Resolution.

Does someone know what's going on there?

EDIT: I was not able to reproduce the issue on a fresh Fedora 26 installation. Maybe it was a bug that survived the upgrade path 24 -> 25 -> 26. Since it is working now, this is fine for me.

Since the single Fedora installation was split into Workstation, Server, and Cloud, I was wondering if the installed systems differ in any central point. When I read the Server Proposal Wiki page [0], I expect at least the repositories to be different due to statements like

However, at Fedora 23, we release "Fedora Server 1.0". At this time, we agree to freeze the interfaces and make clear demands on backwards-compatibility. For the remaining life of Fedora Server 1.x, it will be a stable platform (and understood to be extremely conservative with its updates).

Did this really happen? I cannot find any difference regarding the repositories. And I can't find any Fedora Server version number such as "1.0" or "1.1".

Are there any plans to let the installers actually install different systems? Or will it remain as it is (i.e. only different preinstalled packages, etc).

[0] https://fedoraproject.org/wiki/Server...

both problems vanished with latest updates

After the upgrade to F23, I noticed that rpmfusion-free-updates-testing and rpmfusion-nonfree-updates-testing repositories were enabled. Initially I thought I did something wrong in the past and enabled the regular updates repos for rpmfusion. But after I activated rpmfusion on a fresh F23 install, I recognized the same behavior.

Does someone know why rpmfusion uses the testing repositories by default for now? And would it be better to use the regular or testing repositories for rpmfusion?

After the upgrade to F23, I encounter some issues related to snd stuff (libsndfile ?!).

When I try to start audacity-freeworld, it crashed immediately:

$ audacity
ALSA lib pcm_dsnoop.c:614:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1024:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_dmix.c:1024:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden
Cannot connect to server request channel
jack server is not running or cannot be started
Expression 'stream->capture.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4589
audacity: symbol lookup error: audacity: undefined symbol: _ZN9_VampHost4Vamp7HostExt12PluginLoader11listPluginsEv

When I erase audacity-freeworld and install audacity from standard repository, it launches but gives similar errors on the terminal.

Now the bigger problem:

When I try to use octave (version 4.0 from repo) and call the audioread function, it gives me the following error:

>> audioread("test.wav");
error: sndfile not found on your system and thus audioread is not functional

Does someone know what I could do to circumvent the problems?

Thanks for your answer. But it seems the settings are already correct: $ localectl status System Locale: LANG=de_DE.UTF-8 VC Keymap: de-nodeadkeys X11 Layout: de X11 Variant: nodeadkeys And according to the man page, localectl is only responsible for the keyboard layout when the system is already booted. This is not the case when I entered GRUB and want to get a GRUB shell or edit boot parameters.

Thanks for your answer. Unfortunately didn't work for me. Added rd.vconsole.keymap=de-latin1-nodeadkeys rd.locale.LANG=de_DE.UTF-8 to GRUB_CMDLINE_LINUX variable (font was already present), executed grub2-mkconfig -o /boot/grub2/grub.cfg and dracut --force but when I try to type my supervisor password in GRUB, it's still qwerty layout. Indeed, would have wondered me because the generated initial ramdisk isn't loaded at this time (when in GRUB w/o booting a specific entry).

Fedora comes with firewalld by now, the dynamic firewall daemon from RedHat. I thought it is intended to replace iptables.

Then, I read about nftables, which is obviously intended to replace iptables, too. And this technique is going to be included in the kernel by default.

So, I'm wondering what plans RedHat and Fedora have concerning firewalld and nftables. Are they competing techniques? Or will they collaborate in some way?

Hi, I want to change GRUB2's keyboard layout to the German qwertz layout.

This would be useful when editing boot parameters, entering the GRUB shell or typing supervisor names and passwords.

I experimented a bit but wasn't successful so far.

Could someone explain me how this works?

Hi,

I'm using gnome-boxes for virtualization. Current setup: Fedora 21 host, Fedora 21 guest.

USB forwarding works very well for my external BluRay drive but it does not for any of my USB storage (sticks or hard drives).

The storage devices are simply not recognized by the guest OS, after I toggled the appropriate USB forwarding switch in the boxes settings.

Some ideas on how to debug the issue?

EDIT: it seems that all USB 2.0 devices are working, while I was not successful to pass through USB 3.0 devices. I thought this is possible with recent QEMU versions. Am I doing something wrong?

are you sure your B+ got an ARMv7? All articles I read about the Pi 2 wrote that the architecture changed. Additionally uname -m on my B model says armv6l... But nevertheless, even if newer Pi 1 models have an ARMv7: The architecture changed at some time and now the standard Fedora could maybe work. Beside that: According to the Server Lifecycle wiki page, the Server flavor has it's own repository and once it reaches final 1.0 state it will have a more conservative update policy which is more appropriate for a server than a usual bleeding edge workstation Fedora

thanks for your answer. The big difference between the first and the second generation of Raspberry Pi is the architecture switch from ARMv6 to ARMv7. Therefore it could be possible that no special remix is required and standard Fedora runs on it. But I don't know, so this is the question. Additionally, Pidora seems to be more a Workstation Fedora. I would prefer the Server variant.

When I edit the settings for a wifi network in NetworkManager, switching off IPv6 seems to have no effect.

In the settings, there is this blue toggle button, I switched off for IPv6. Before connecting to the network, ifconfig shows neither an IPv4 nor an IPv6 addess. Fine so far...

Now I connect to the network, and ifconfig shows an IPv4 as well as an IPv6 (link local) address. When observing the traffic via Wireshark, I see outgoing ICMPv6 packets from my machine.

My question is now: Why?

Is this a bug oder didn't I understand the toggle button's functionality correctly?

Fedora 21, NetworkManager 0.9.10.0

thanks. Too bad that this bug isn't fixed yet.