users April 2017

users@lists.fedoraproject.org

90 participants
89 discussions

strange log message
by François Patte 09 Apr '17

09 Apr '17

Bonjour, logwatch send a strange warning: WARNING: Device /dev/md1 has size of 0 sectors which is smaller than corresponding PV size of 976508928 sectors. Was device resized?: 1 Time(s) WARNING: Device /dev/md11 has size of 0 sectors which is smaller than corresponding PV size of 104346496 sectors. Was device resized?: 1 Time(s) What does that mean? These devices have not been resized. They are locate on disks which were not used during the installation and they were created during a previous installation (fedora 21). I added them to fstab after the f25 install. Who can give me some explanation? Thank you. -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 8394 5849 http://www.math-info.univ-paris5.fr/~patte

3 4

mcelog error output going to all open terminals
by ProPAAS DBA 09 Apr '17

09 Apr '17

Hi all; I've been seeing mcelog errors since a few updates back. After much, much digging it seems that the mcelog errors are due to spikes in cpu temperature. I have a Thinkpad x1 Carbon 4th generation running Fedora 25 - KDE I get why I'm seeing the cpu temp spikes since it usually happens when I'm doing a fair amount of gaphics processing with darktable and have 2-3 VM's running via VMware Workstation, however in the past I would see a notification popup on the system tray, now I see the notification on the system tray AND I also get output like this in EVERY terminal window I have open: Message from syslogd@F25Host at Apr 8 18:11:03 ... kernel:mce: [Hardware Error]: CPU 2: Machine Check: 0 Bank 128: 000000008812280b Message from syslogd@F25Host at Apr 8 18:11:03 ... kernel:mce: [Hardware Error]: TSC 16382416299d Message from syslogd@F25Host at Apr 8 18:11:03 ... kernel:mce: [Hardware Error]: PROCESSOR 0:406e3 TIME 1491696663 SOCKET 0 APIC 1 microcode 9e Message from syslogd@F25Host at Apr 8 18:11:03 ... kernel:mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 128: 000000008812280b Message from syslogd@F25Host at Apr 8 18:11:03 ... kernel:mce: [Hardware Error]: TSC 163824164344 Message from syslogd@F25Host at Apr 8 18:11:03 ... kernel:mce: [Hardware Error]: PROCESSOR 0:406e3 TIME 1491696663 SOCKET 0 APIC 0 microcode 9e Message from syslogd@F25Host at Apr 8 18:11:03 ... kernel:mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 128: 000000008813280 It's very frustrating... Is there a way I can keep he system from printing this info to all my open terminal windows? I even tried a "dnf erase mcelog" but I still get the same behavior. Thanks in advance

1 2

Strange VT switch issue
by Raman Gupta 08 Apr '17

08 Apr '17

I have an odd issue with VT switches after upgrading to Fedora 26. I'm in X, and when I switch VT's systemd creates a getty [1] and it suspends X [2], however the VT never actually switches to a terminal. It just sits on a "frozen" X display that has no audio, no video, and no cursor (as one would expect), until I switch back to VT-1. I *can* also switch back to to VT-1 using Alt-F1 instead of Ctrl-Alt-F1, which indicates to me that my keyboard input *is* going to the console VT -- just my display doesn't match. Is this related to modesetting? I am using the open source radeon / radeonsi driver with an HD7500 card, with three monitors. There are no error messages in any of the usual suspects (journalctl, dmesg, Xorg.0.log). Any ideas? [1] agetty processes after attempting Ctlr-Alt-F2 and Ctrl-Alt-F6: root 11513 1 0 03:47 tty2 00:00:00 /sbin/agetty --noclear tty2 linux root 29928 1 0 11:31 tty6 00:00:00 /sbin/agetty --noclear tty6 linux [2] Message in Xorg.0.log at the time of the VT switch attempt: [ 31645.194] (II) AIGLX: Suspending AIGLX clients for VT switch Message in Xorg.0.log when switching back to VT-1: [ 31645.798] (II) AIGLX: Resuming AIGLX clients after VT switch Regards, Raman

2 2

swell-foop working for anyone with nvidia drivers?
by Tom Horsley 08 Apr '17

08 Apr '17

I got an update that included both new nvidia drivers from rpmfusion and a new libglvnd, and now swell-foop stopped working (very critical bug :-). https://bugzilla.redhat.com/show_bug.cgi?id=1440353 Lots of other gnome stuff still works, so I don't think this busted GL completely, it is just busted for swell-foop. Anyone have any clues about who's bug this really is? I know swell-foop uses some idiotic library to mush gtk and java together, and it often seems to stumble over doing things "differently". Maybe that's where the bug really is. Or it could be the new libglvnd or the new nvidia drivers. Who can say?

2 1

Firefox question
by JD 07 Apr '17

07 Apr '17

For a long time I had my FF start up with the setting: Show my windows and tabs from last time. Well, for some reason, when I shut down FF (File -> Quit), and restart, it restarts not from the tabs and windows of previous Quit, but from a very very old set of tabs and windows. Hot sure why it is doing this. Any hints of what file contains that old set of tabs and windows so I can clear it? Thanx.

3 4

System alive but can't access from the monitor
by Paolo Galtieri 06 Apr '17

06 Apr '17

Folks, I have 2 F25 systems that have been updated today. These 2 systems share a monitor. One system is attached via a kvm switch to the monitor, the other system is attached via hdmi. This morning and twice this evening a problem has started to manifest itself. This configuration has been working fine for several years. I will call the systems A and B, system A is attached to the monitor via hdmi, system B via VGA. If I switch to system A for a while and then try to switch back to system B the monitor instead of staying on VGA cycles from VGA to DVI to HDMI and returns to system A. I can ssh into system B and everything looks fine, i.e. things that were running under my user id are still running, e.g. chrome and firefox. I looked at /var/log/messages and I see this: Mar 29 23:00:02 jackstraw systemd: Stopping User Manager for UID 0... Mar 29 23:00:02 jackstraw systemd: Stopped target Default. Mar 29 23:00:02 jackstraw systemd: Stopped target Basic System. Mar 29 23:00:02 jackstraw systemd: Stopped target Sockets. Mar 29 23:00:02 jackstraw systemd: Closed D-Bus User Message Bus Socket. Mar 29 23:00:02 jackstraw systemd: Stopped target Timers. Mar 29 23:00:02 jackstraw systemd: Stopped target Paths. Mar 29 23:00:02 jackstraw systemd: Reached target Shutdown. Mar 29 23:00:02 jackstraw systemd: Starting Exit the Session... Mar 29 23:00:02 jackstraw systemd: Received SIGRTMIN+24 from PID 17588 (kill). This was at the time I switched from system A to system B. Each of the other times I saw this problem I see the same set of messages in the log file. Can someone explain what they mean and could they be the cause of the problem? I see the same messages on the other system, but there they were part of other messages related to rebooting the system. The only way I can recover is reboot the system. Here's my video card info: 01:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce 8500 GT] (rev a1) Any assistance is appreciated. Thanks, Paolo

5 11

RE: Is there a way to stop ipv6 leakage without turning off ipv6?
by J.Witvliet＠mindef.nl 06 Apr '17

06 Apr '17

-----Original Message----- From: Ed Greshko [mailto:ed.greshko@greshko.com] Sent: donderdag 6 april 2017 11:47 To: Community support for Fedora users Subject: Re: Is there a way to stop ipv6 leakage without turning off ipv6? On 04/06/17 15:53, J.Witvliet(a)mindef.nl wrote: > Remember that V6 is some option you do NOT have the option to ignore. And that strange quirks could be solved by "net.ipv6.conf.all.disable_ipv6 = 1" > Some countries make haste implementing it, while others don't. > > I was expecting that it would be countries like CN and CU where visitors would be confronted with an IPv6-only situation. > However, last February I found out that our appliance didn't work, because of IPv6-only. Here, in Europe, just some miles away in Belgium, Brussels. > So you better get your head out of the sand. Sounds as if yours was just recently pulled from it. :-) :-) You do realize my "suggestion" was only meant to address a single issue by a single user. Right? Yet, if an ISP supplies only IPv6 services you'd think they would also either supply you with a DNS64/NAT64-resolver address or inform you that you should use one of the public DNS64/NAT64-resolvers. I suspect that is how you got your appliance working in that environment? -----Original Message----- At home, I got one of the first HE-tunnels, at the time that they were only located in Fremont, and a happy camper ever since. At work however, this quite another struggle :-(((((( And yes, Ed, I realise that disabling V6 is some duck-tape (not even a Q&D-fix) to get-on for a while. Unfortunately, googling on it, this is suggested way too often as a permanent solution. That location used indeed DNS64 and NAT64, that worked for almost all my laptops, phones etc, but not for my box. Reason? One of my colleges had also disabled V6 on the readonly appliance. Sigh. So when I see that suggestion, I stand up :-) Hans 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.

1 0

LS in a script file
by Patrick Dupre 06 Apr '17

06 Apr '17

Hello, How can I put this command in a script file? FILES=`ls -d !(*(a)(-e)).bib` I get an error because of the ( =========================================================================== Patrick DUPRÉ | | email: pdupre(a)gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================

12 26

RE: Is there a way to stop ipv6 leakage without turning off ipv6?
by J.Witvliet＠mindef.nl 06 Apr '17

06 Apr '17

See below -----Original Message----- From: Ed Greshko [mailto:ed.greshko@greshko.com] Sent: donderdag 6 april 2017 1:20 To: Community support for Fedora users Subject: Re: Is there a way to stop ipv6 leakage without turning off ipv6? On 04/06/17 06:57, Stephen Morris wrote: > Hi Ed, just as a side issue to this, because my ISP (I don't know > about my VPN provider) IPv6 at all for anything, I was setting IPv6 to > 'ignore' via Networkmanager in KDE (Gnome doesn't seem to have the > same options) but that was causing messages in the logs at boot time > about IPv6 not being ready. How do we stop the network from attempting > to activate IPv6 and then producing these messages when it has been > turned off? <snip> I decided to do a test and add ipv6.disable=1 to the kernel parameter on one of my VM's. In the past, this was sufficient. However, doing only this now results in selinux errors. To avoid those you also need to add "net.ipv6.conf.all.disable_ipv6 = 1" to /etc/sysctl.conf. -----Original Message----- Remember that V6 is some option you do NOT have the option to ignore. And that strange quirks could be solved by "net.ipv6.conf.all.disable_ipv6 = 1" Some countries make haste implementing it, while others don't. I was expecting that it would be countries like CN and CU where visitors would be confronted with an IPv6-only situation. However, last February I found out that our appliance didn't work, because of IPv6-only. Here, in Europe, just some miles away in Belgium, Brussels. So you better get your head out of the sand. HW 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.

2 1

Really?
by Tom Horsley 06 Apr '17

06 Apr '17

I was just checking my logs to see if I successfully squashed the endless random messages minidlna was generating and I found this: Apr 5 13:46:34 zooty systemd[2007]: Starting Evince document viewer... Apr 5 13:46:34 zooty dbus-daemon[2056]: [session uid=2304 pid=2056] Successfully activated service 'org.gnome.evince.Daemon' Apr 5 13:46:34 zooty systemd[2007]: Started Evince document viewer. Really? They have managed to make looking at a pdf file dependent on systemd and dbus? And there is some reason to log such trivia? Next thing I know, I'll find all my keystrokes and mouse movements in the log :-).

7 7

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