fedora-24, avahi-daemon log erros
by Roman
Hi all.
Recently i installed fedora-24 on my laptop and everything looks fine.
But i decided to check boot logs and found some error about avahi
daemon:
here is 'journalctl -u avahi-daemon' output:
-- Reboot --
авг 04 15:45:04 venomous.localdomain systemd[1]: Starting Avahi
mDNS/DNS-SD Stack...
авг 04 15:45:04 venomous.localdomain avahi-daemon[1090]: Found user
'avahi' (UID 70) and group 'avahi' (GID 70).
авг 04 15:45:04 venomous.localdomain avahi-daemon[1090]: Successfully
dropped root privileges.
авг 04 15:45:04 venomous.localdomain avahi-daemon[1090]: avahi-daemon
0.6.32 starting up.
авг 04 15:45:04 venomous.localdomain systemd[1]: Started Avahi
mDNS/DNS-SD Stack.
авг 04 15:45:04 venomous.localdomain avahi-daemon[1090]: Successfully
called chroot().
авг 04 15:45:04 venomous.localdomain avahi-daemon[1090]: Successfully
dropped remaining capabilities.
авг 04 15:45:04 venomous.localdomain avahi-daemon[1126]: chroot.c:
open() failed: No such file or directory
авг 04 15:45:04 venomous.localdomain avahi-daemon[1090]: Failed to open
/etc/resolv.conf: Invalid argument
авг 04 15:45:04 venomous.localdomain avahi-daemon[1090]: No service
file found in /etc/avahi/services.
авг 04 15:45:04 venomous.localdomain avahi-daemon[1090]: Network
interface enumeration completed.
авг 04 15:45:04 venomous.localdomain avahi-daemon[1090]: Server startup
complete. Host name is venomous.local. Local service cookie is
2621676609.
авг 04 15:45:06 venomous.localdomain avahi-daemon[1090]: Joining mDNS
multicast group on interface wlp3s0.IPv4 with address 192.168.1.121.
авг 04 15:45:06 venomous.localdomain avahi-daemon[1090]: New relevant
interface wlp3s0.IPv4 for mDNS.
авг 04 15:45:06 venomous.localdomain avahi-daemon[1090]: Registering
new address record for 192.168.1.121 on wlp3s0.IPv4.
авг 04 15:45:07 venomous.localdomain avahi-daemon[1090]: Joining mDNS
multicast group on interface wlp3s0.IPv6 with address
fe80::f079:4615:1830:acaf.
авг 04 15:45:07 venomous.localdomain avahi-daemon[1090]: New relevant
interface wlp3s0.IPv6 for mDNS.
авг 04 15:45:07 venomous.localdomain avahi-daemon[1090]: Registering
new address record for fe80::f079:4615:1830:acaf on wlp3s0.*.
авг 04 15:45:29 venomous.localdomain avahi-daemon[1126]: chroot.c:
open() failed: No such file or directory
авг 04 15:45:29 venomous.localdomain avahi-daemon[1090]: Failed to open
/usr/share/dbus-1/interfaces/org.freedesktop.Avahi.Server.xml: Invalid
argument
авг 04 15:45:29 venomous.localdomain avahi-daemon[1090]: Failed to load
introspection data.
авг 04 15:45:29 venomous.localdomain avahi-daemon[1126]: chroot.c:
open() failed: No such file or directory
авг 04 15:45:29 venomous.localdomain avahi-daemon[1090]: Failed to open
/usr/share/dbus-1/interfaces/org.freedesktop.Avahi.ServiceBrowser.xml:
Invalid argument
авг 04 15:45:29 venomous.localdomain avahi-daemon[1090]: Failed to load
introspection data.
авг 04 15:45:29 venomous.localdomain avahi-daemon[1126]: chroot.c:
open() failed: No such file or directory
авг 04 15:45:29 venomous.localdomain avahi-daemon[1090]: Failed to open
/usr/share/dbus-1/interfaces/org.freedesktop.Avahi.DomainBrowser.xml:
Invalid argument
авг 04 15:45:29 venomous.localdomain avahi-daemon[1090]: Failed to load
introspection data.
авг 04 15:45:29 venomous.localdomain avahi-daemon[1126]: chroot.c:
open() failed: No such file or directory
авг 04 15:45:29 venomous.localdomain avahi-daemon[1090]: Failed to open
/usr/share/dbus-1/interfaces/org.freedesktop.Avahi.EntryGroup.xml:
Invalid argument
авг 04 15:45:29 venomous.localdomain avahi-daemon[1090]: Failed to load
introspection data.
actually i dont c any impact on my system :) but im wondering why my
logs r colored red by errors. also i never used avahi directly.
Maybe someone could advise me something about this error?
Thanks
7 years, 8 months
batti issue on Fedora 24
by Ranjan Maitra
Hello,
I have lately been having this issue on batti:
Neither UPower nor DeviceKit.Power could be initialized!
This can have multiple reasons.
Here is the error for UPower:
org.freedesktop.DBus.Error.InvalidArgs: No such property 'type'
And this is the error for DeviceKit.Power:
org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.DeviceKit.Power was not provided by any .service files
What does this mean? How can this be fixed?
Many thanks,
Ranjan
--
Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses.
____________________________________________________________
FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family!
Visit http://www.inbox.com/photosharing to find out more!
7 years, 8 months
gsl-2
by Patrick Dupre
Hello,
Since I update fc22 to fc24 I am in trouble with several of my
applications which require gsl.
Actually, gsl has been updated from 1 to 2 with major changes.
It results that perl-Math::GSL is not anymore compatible with gsl-2.
The maintainer of this package is not ready to make the changes
required by the new version of gsl and I have several crucial
applications based on gsl and perl-Math::GSL.
Is there any way to install gsl-1 with fc24 ?
Thank for your help.
===========================================================================
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
===========================================================================
7 years, 8 months
old packages
by Patrick Dupre
Hello,
I do have a bunch of old pacakges installed.
Is there any update of ?
smart
system-config-lvm
perl-define
system-config-boot
perl-Forest
perl-Sort-Fields
SOAPpy
celt
systemd-ui
anaconda-yum-plugins
createrepo
aic94xx-firmware
system-config-firewall
Should I just remove them ?
Thank
===========================================================================
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
===========================================================================
7 years, 8 months
F23, Nouveau, and GeForce 750 Ti
by Justin Moore
I have a GeForce 750 Ti card and I'm having issues with stability and
features with the nouveau driver on Fedora 23. Per lspci, I have
NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2)
and kernel 4.6.4-201.fc23.x86_64. It appears that I'm running into the same
(or a similar) issue as here:
https://bugs.freedesktop.org/show_bug.cgi?id=95251
I can get it to work on each output port (DisplayPort, HDMI, and DVI) and
I'm driving all three monitors simultaneously. However vdpauinfo shows that
none of the hardware acceleration is working:
Decoder capabilities:
name level macbs width height
----------------------------------------------------
MPEG1 --- not supported ---
MPEG2_SIMPLE --- not supported ---
MPEG2_MAIN --- not supported ---
[ etc etc ]
When I start X I do see this message:
[ 26.829] (II) modeset(0): [DRI2] VDPAU driver: nouveau
but I also see this repeated a few times:
[ 26.355] (EE) Unknown chipset: NV117
I'm getting conflicting messages from Freedesktop.org about whether this
should work at all, so I can't tell if this is an upstream issue or a
Fedora issue. I have a 750 Ti, which per
https://nouveau.freedesktop.org/wiki/CodeNames/#NV110
is the Maxwell chipset NV117 with the GM107 chipset.
The video acceleration matrix
https://nouveau.freedesktop.org/wiki/VideoAcceleration/
seems to indicate that this is VP6, and everything is TODO. However the
main Nouveau wiki page at https://nouveau.freedesktop.org/wiki/ has this
entry:
* Apr, 2015: GM107 acceleration support merged into 4.1
and
https://www.phoronix.com/scan.php?page=news_item&px=GTX-750-Nouveau-Linux...
indicates that as of 4.1 acceleration should start to work. I'm on kernel
4.6.4.
Can anyone help me understand whether VDPAU is even supported on my
hardware/kernel/driver combination, and if so, what I need to do to get it
to work?
Thanks,
-jdm
7 years, 8 months
Drive ordering mechanism /dev/sda /dev/sdb etc
by Philip Rhoades
People,
I know that it is possible to refer to drives by various naming
conventions:
https://wiki.archlinux.org/index.php/Persistent_block_device_naming
but it is annoying that the "SCSI" drive (SATA and USB) order in which
their corresponding device nodes are added is arbitrary - is there some
way of forcing the order to what I want? ie I have the boot disk as
/dev/sda of course but I want to specify the drive letter of the other
physical SATA and USB drives . .
Thanks,
Phil.
--
Philip Rhoades
PO Box 896
Cowra NSW 2794
Australia
E-mail: phil(a)pricom.com.au
7 years, 8 months
gcc 4.9
by Amadeus W.M.
I want to do some parallel programming on my nvidia GPU, and for that I
need cuda. The latest is cuda 7.5 and that requires gcc 4.9. I installed
cuda on my machine, but little did I know that fedora 24, which I recently
installed, came with gcc 6.1. I wasn't able to compile any of the cuda
examples. I asked on the nvidia forums about this and the next cuda
(version 8.0) will require gcc-5.3 or so. No indication when cuda will
work with gcc-6.1.
So what do I do now? From some posts I read it appears that debian
provides a gcc49 package, and so I hoped fedora would provide one too, but
no such luck. Can I rebuild the gcc-4.9 rpm on F24 without messing up the
stock gcc-6.1? Or, can I convert the gcc49.deb package into the equivalent
rpm? I can try these things and try to be careful not to mess up, but I
was wondering if anyone had any experience with this or any suggestions.
Thanks!
7 years, 8 months
missing ldconfig somewhere?
by Tom Horsley
I just tried to run neverputt and it gave libGL errors
and hung:
tomh> neverputt
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
With nvidia drivers on my system, I'm pretty sure I shouldn't
be trying to use swrast, so as root I ran "ldconfig"
and neverputt started working again.
So some rpm somewhere must be missing an ldconfig call
in postinstall. Anyone know how to detect which
package that might be?
7 years, 8 months
systemd vs. autofs/nfs
by David A. De Graaf
systemd and autofs/nfs are at war and have been ever since systemd
appeared.
Specifically, if machine A has an open connection to machine B
and B goes down or become inaccessible, then A cannot shutdown.
A's shutdown sequence hangs, waiting for B to respond to an unmount
command, which will not/cannot happen.
WAITING WILL NOT HELP.
Only a dirty disconnect will work; there's no way to avoid it.
Here's what I've tried:
- Precede 'shutdown' or 'reboot' or 'systemctl reboot' with
umount -fl -t nfs <each nfs-mounted-filesystem>
(You might expect a forced lazy umount to do the job.
It doesn't work; umount just hangs)
- Change nfs mount option to 'soft' instead of 'hard'.
Edit /etc/nfsmount.conf to say:
Hard=False
Soft=True
(This did change the autofs/nfs mount option, but didn't improve
the tolerance for a dirty disconnect. Shutdown still hangs.)
- Reduce systemd's timeout values from 90 to 10 sec;
edit /etc/systemd/system.conf to say:
DefaultTimeoutStartSec=10s
DefaultTimeoutStopSec=10s
(During shutdown, systemd displays two times; the time it has waited
for an unmount event, and the time limit to wait. Incomprehensibly,
when the time limit is reached, it bumps it up and continues to wait.
Changing the default timeout values seems to accelerate this recycling,
but doesn't do anything for the actual time limit.)
- Change the nfs timeout from 600 (default) to 20 decisec to reduce
the time nfs waits for any response, including umount, before
declaring a timeout. Edit /etc/nfsmount.conf to say:
# Timeo=600
Timeo=20
(The option displayed by the mount command did change, but it did not
help the shutdown hangup.)
- That leaves ONLY TWO WAYS to shutdown machine A, both ugly:
SysReq R E I S U B - which forces a reboot NOW
Hold the Power button - which just stops everything.
This is NOT NEW. Systemd has had this design defect from day one.
SysV never hung on shutdown. It Just Knew when a dirty disconnect
was the only viable way and handled it.
How many more years must we wait?
Have I overlooked something obvious? Is there a way to make systemd
perform the simple function 'shutdown' smoothly, reliably and quickly?
If anyone knows how, I would love to hear it.
--
David A. De Graaf DATIX, Inc. Hendersonville, NC
dad(a)datix.us www.datix.us
"Tolerance becomes a crime when applied to evil."
-- Thomas Mann
7 years, 8 months
gsl-1 and gsl-2
by Patrick Dupre
Hello,
It seems that I need to have both installed gsl-1 and gsl-2 on
a fc24 machine.
How can I install gsl-1 into a "special" directory ?
Can I use rpmbuild ?
Thank for your help.
Regards.
===========================================================================
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
===========================================================================
7 years, 8 months