users May 2017

users@lists.fedoraproject.org

87 participants
80 discussions

Strange mouse issue in VirtualBox
by andrea 18 Jun '17

18 Jun '17

Hi 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 the guest. 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. Andrea

5 7

post-mortem: f24 boot fails; need help.
by William 13 Jun '17

13 Jun '17

Good morning, 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? thanks, Bill.

9 32

Fw: Systemd keeps trying to re-open an already active LUKS volume
by stan 04 Jun '17

04 Jun '17

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> To: users(a)lists.fedoraproject.org Subject: Systemd keeps trying to re-open an already active LUKS volume Hi, I need a piece of advice concerning an encrypted root partition on Fedora 26. I'm running a custom manual setup created using dnf. Further context: * The installation procedure is outlined in this tread -- and quite likely irrelevant to this question anyway: https://lists.fedorahosted.org/archives/list/users@lists.fedoraproject.org/… * The disk layout is described in this comment: https://bugzilla.redhat.com/show_bug.cgi?id=1297188#c2 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 add_dracutmodules+="crypt". 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 systemd-tty-ask-password-agent tool! 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: https://bugzilla.redhat.com/show_bug.cgi?id=924581 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. Cheers, Andrej _______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)lists.fedoraproject.org

2 1

nfs problem
by Eyal Lebedinsky 03 Jun '17

03 Jun '17

I asked on AskFedora and got no response. Hoping this list is more active. https://ask.fedoraproject.org/en/question/104010/nfs-showing-bad-data-f24/ 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? TIA -- Eyal Lebedinsky (eyal(a)eyal.emu.id.au)

5 13

Migrating an existing system with a different OS
by Walter H. 02 Jun '17

02 Jun '17

Hello, I'm using Windows with several virtual machines (VMware); is there a way to use these virtual machines with Fedora as host OS? Thanks, Walter

8 12

hdmi monitor blanks when starting some apps
by DJ Delorie 31 May '17

31 May '17

I have multiple monitors on my system, one of which is HDMI (the rest are DP or DVI). It's not the main monitor. When I start some apps (esp games), the HDMI monitor blanks for a few seconds until the app's window comes up (not full screen). Is this a normal thing? Can it be prevented? Fedora 24 GTX980 nvidia drivers

2 2

dependencies for kdm and gdm
by Rick Leir 31 May '17

31 May '17

Hi all It seems that Fedora 26 allowed me to have KDM and LightDM installed without gdm, gnome-shell, and mutter. I had a crash while attempting to login using LightDM: # journalctl -e #2 0x00007feb273ed783 gtk_css_static_style_compute_value (libgtk-3.so.0) #3 0x00007feb273d900c _gtk_css_lookup_resolve (libgtk-3.so.0) #4 0x00007feb273ed6bc gtk_css_static_style_new_compute (libgtk-3.so.0) #5 0x00007feb273ed715 gtk_css_static_style_get_default (libgtk-3.so.0) #6 0x00007feb273d99a2 gtk_css_node_init (libgtk-3.so.0) #7 0x00007feb25bde390 g_type_create_instance (libgobject-2.0.so.0) #8 0x00007feb25bbf4b8 g_object_new_internal (libgobject-2.0.so.0) Many neurons were lost trying to track the cause down, but then the fix was: # yum install gdm Last metadata expiration check: 0:51:01 ago on Tue May 30 03:01:28 2017 CDT. Dependencies resolved. ============================================================================================================================================================================================================ Package Arch Version Repository Size ============================================================================================================================================================================================================ Installing dependencies: gdm x86_64 1:3.24.2-1.fc26 updates-testing 501 k gnome-shell x86_64 3.24.2-1.fc26 updates-testing 1.9 M mutter x86_64 3.24.2-1.fc26 updates-testing 2.2 M How do you troubleshoot dependencies? Or is there some other mis-configuration which could have caused the problem? cheers -- Rick

2 8

sudo su
by Peter Gueckel 30 May '17

30 May '17

I opened a second tab in konsole and immediately ran sudo su to obtain a prompt as root. I ran a program and then I forgot to exit and just closed the tab. Am I still root somewhere? Or did closing the tab do the same thing as a proper exit?

10 17

Moderator approval?
by wwp 30 May '17

30 May '17

Hello there, sorry to disturb w/ list management issues.. I've been tried to post here but my message is waiting for moderator approval (since 2017-05-19). Nothing scary, but I wonder if it's because of its contents.. There was a text attachment, I tried to sent it w/ the text inserted in body instead, no luck. Is there really a moderator or am I blacklisted in some way for an obscure reason? (I could post a reply to another thread) Regards, -- wwp

2 3

Fedora command for motherboard clock condition (from: f24 boot fails; need help).
by William 30 May '17

30 May '17

Good afternoon, In the "f24 boot fails; need help" topic, a log file extract had these 2 lines: 1533 [ 4.022605] coyote systemd-fsck[428]: /dev/sda6: Superblock last mount time is in the future. 1534 [ 4.022745] coyote systemd-fsck[428]: (by less than a day, probably due to the hardware clock being incorrectly set) One person noted "The time problem suggests that the little pancake battery on the MB that maintains the clock might be out of juice. I think these are 2032 style for PCs. It would be a good idea to replace it." I responded "I didn't know workstations nowadays had batteries. When the system is back on its feet, I'll try to check that. It was bought in 2013." I knew that the older motherboards had batteries. But I thought the newer ones used something like flash (or other persistent) memory. It did not occur to me that booting might want the date/time before the boot process reached the point of being able to access the internet. Two people corrected me. Someone else in the discussion said it well: I sit corrected! Fedora seems to have a huge number of commands. Does Fedora have a command to report the condition of a full-sized tower motherboard battery? If yes, what is that command? thanks, Bill.

5 8