Updated info about disabling tracker related processes?
by Gianluca Cecchi
Hello,
I have recently begun to use again gnome session and I have reinstalled
nautilus.
I see that nautilus depends on tracker and so the reinstall put in tracker
and its things
And this morning in my F28 system with SSD disk (I don't imagine on a
normal sata based environment) I had to kill tracker-extract and
tacker-miner processes because they hogged my cpu for several minutes..
Searching with google I found different info about disabling (or at least
calm down) tracker, but they all seem not updated, in the sense that
several commands/services are not present in my f28 environment.
Any pointer about configuring and/or disabling it?
Thanks in advance,
Gianluca
1 month, 3 weeks
VPN options
by Keith Lofstrom
I am planning on running a Virtual Private Network from my Fedora
firewall out to a UML virtual colo (running RH9) at another site.
That site will be the place I present services to the world;
httpd, ssh, sftp, smtp. This is to comply with the "no servers"
and dynamic ip restrictions on my Comcast connection to the net;
if my firewall always drives an outbound connection to the
colocation site, I am not worried about changes of ip address,
and I am not opening any inbound ports.
There are a number of options for the VPN - the most attractive
are cipe ( http://sites.inka.de/sites/bigred/devel/cipe.html )
and FreeSwan ( http://www.freeswan.org/ ), though I am told that
one can do all this through an ssh tunnel. I would rather have
simple and secure than super-duper; I have plenty of bandwidth,
and will send outbound http and smtp from the firewall, so the
main bandwidth user will be incoming spam/b/b/b/b mail.
Anyone have some experiences to share about setting up VPN? Is
there anything about either cipe or FreeSwan that is likely to
break with FC1 or FC2?
Keith
--
Keith Lofstrom keithl(a)ieee.org Voice (503)-520-1993
KLIC --- Keith Lofstrom Integrated Circuits --- "Your Ideas in Silicon"
Design Contracting in Bipolar and CMOS - Analog, Digital, and Scan ICs
3 months, 1 week
ACPI errors (was: f24 boot fails; need help).
by William
Good evening,
One of the problems reported in the log file "rdsosreport.txt" generated
by the failed boots discussed in the "f24 boot fails; need help" topic
was a set of "ACPI" errors. Here are the relevant lines (with added
line numbers) from that log file (the first and last lines are just for
context):
----------
862 [ 1.218683] coyote kernel: ata4: SATA link up 1.5 Gbps
(SStatus 113 SControl 300)
863 [ 1.218927] coyote kernel: ACPI Error: [DSSP] Namespace
lookup failure, AE_NOT_FOUND (20160930/psargs-359)
864 [ 1.219196] coyote kernel: ACPI Error: Method parse/execution
failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff92ef8e0db488), AE_NOT_FOUND
(20160930/psparse-543)
865 [ 1.219856] coyote kernel: ata2.00: ATA-8:
ST2000DM001-1CH164, CC24, max UDMA/133
866 [ 1.220017] coyote kernel: ata2.00: 3907029168 sectors, multi
16: LBA48 NCQ (depth 31/32), AA
867 [ 1.220812] coyote kernel: ACPI Error: [DSSP] Namespace
lookup failure, AE_NOT_FOUND (20160930/psargs-359)
868 [ 1.221100] coyote kernel: ACPI Error: Method parse/execution
failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff92ef8e0db488), AE_NOT_FOUND
(20160930/psparse-543)
869 [ 1.221620] coyote kernel: ACPI Error: [DSSP] Namespace
lookup failure, AE_NOT_FOUND (20160930/psargs-359)
870 [ 1.221909] coyote kernel: ACPI Error: Method parse/execution
failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff92ef8e0dbac8), AE_NOT_FOUND
(20160930/psparse-543)
871 [ 1.222200] coyote kernel: ata6.00: ATAPI: HL-DT-ST BD-RE
BH14NS40, 1.00, max UDMA/100
872 [ 1.222374] coyote kernel: ata2.00: configured for UDMA/133
873 [ 1.222582] coyote kernel: ACPI Error: [DSSP] Namespace
lookup failure, AE_NOT_FOUND (20160930/psargs-359)
874 [ 1.222908] coyote kernel: ACPI Error: Method parse/execution
failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND
(20160930/psparse-543)
875 [ 1.222919] coyote kernel: scsi 1:0:0:0: Direct-Access
ATA ST2000DM001-1CH1 CC24 PQ: 0 ANSI: 5
876 [ 1.223466] coyote kernel: ata4.00: ATAPI: PIONEER BD-RW
BDR-208M, 1.10, max UDMA/100
877 [ 1.226360] coyote kernel: ata7: SATA link down (SStatus 0
SControl 300)
878 [ 1.226407] coyote kernel: ata9: SATA link down (SStatus 0
SControl 300)
879 [ 1.226501] coyote kernel: ACPI Error: [DSSP] Namespace
lookup failure, AE_NOT_FOUND (20160930/psargs-359)
880 [ 1.226507] coyote kernel: ACPI Error: Method parse/execution
failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff92ef8e0dbac8), AE_NOT_FOUND
(20160930/psparse-543)
881 [ 1.226519] coyote kernel: ata6.00: configured for UDMA/100
882 [ 1.227197] coyote kernel: ACPI Error: [DSSP] Namespace
lookup failure, AE_NOT_FOUND (20160930/psargs-359)
883 [ 1.227204] coyote kernel: ACPI Error: Method parse/execution
failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff92ef8e0db348), AE_NOT_FOUND
(20160930/psparse-543)
884 [ 1.227217] coyote kernel: ata4.00: configured for UDMA/100
----------
What is this all about? Is this a real problem or a false alarm? How
do I fix it?
thanks,
Bill.
1 year, 1 month
Install on Zotac Zbox CI327?
by wwp
Hello there,
(after a looong time not using Fedora, just back to it!)
I've tried installing Fedora on a Zotac Zbox CI327 (Intel Celeron
N3450 inside) but this happens to fail. I've tried F25 but it has
not the right kernel to make it (I've read about 4.10 minimum), then
tried F26-Alpha-1.7 Live and Rawhide-20170518 Live but none could
reach the graphical login. They both boot, some steps take a lot of
time and I end up in a state I don't understand but which is not
friendly ;-).
Here's a link to a rdsosreport.txt file generated using Rawhide, I must
admit that I don't know what to do now..
https://paste.fedoraproject.org/paste/iRx8d~7Luk2TC3bsaDuuT15M1UNdIGYhyRL...
BTW, I could install and run a Ubuntu 17.10 daily
(artful-desktop-amd64-20170519.iso) - wow it starts up pretty quickly -
and that gave me hope!
Any hint or experience w/ such hardware?
Regards,
--
wwp
1 year, 2 months
How to turn on networking from rescue boot
by vendor＠billoblog.com
So... I did a "sudo dnf upgrade" and things seemed to do well.
However, when I rebooted, it hangs on bootup with the statment "Holding
until bootup processes complete" or something like that -- I'm doing
this from memory. I tried with a couple of older kernels, but they also
hung.
I assume that this is some transient thing associated with the upgrade.
Over the years, I've had glitches appear on an upgrade and disappear on
the next upgrade. Accordingly, I'd like to boot into rescue mode and
see if I can upgrade again.
However, I've forgotten how to turn on wifi networking from rescue mode.
Can anybody point me to a tutorial?
Thanks,
billo
1 year, 3 months
Makemkv Incompatible with mmdtsdec
by Stephen Morris
Hi,
With the sudo dnf upgrade I have just done I received the following
messages, which I'm not sure what to do about.
Problem: package makemkv-1.12.2-2.fc27.x86_64 obsoletes mmdtsdec <
1.12.2-2.fc27 provided by mmdtsdec-1.12.0-1.fc27.i686
- cannot install the best update candidate for package
mmdtsdec-1.12.0-1.fc27.i686
- cannot install the best update candidate for package
makemkv-1.12.0-1.fc27.x86_64
regards,
Steve
1 year, 7 months
[SOLVED] Re: Very slow boot in F27 after recent update
by Gianluca Cecchi
On Fri, May 4, 2018 at 9:32 AM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
> I'm not subscribed to receive all the e-mails, so I answer to my own.
> Hope not to scramble the thread order...
>
> Thanks for answering.
> Here the output requested.
> Possibly before the update, chronyd and gssproxy (and I see also libvirtd)
> went into a sort of parallel background not preventing display manager
> login completion?
> In fact in about 10-13 seconds (I have an SSD disk on the laptop) I had
> the gdm login page....
>
> [g.cecchi@ope46 ~]$ sudo systemd-analyze time
> Startup finished in 1.379s (kernel) + 1.965s (initrd) + 1min 49.668s
> (userspace) = 1min 53.012s
> [g.cecchi@ope46 ~]$
>
> [g.cecchi@ope46 ~]$ sudo systemd-analyze blame
> 1min 30.134s gssproxy.service
> 1min 15.937s chronyd.service
> 30.043s NetworkManager-wait-online.service
> 17.876s libvirtd.service
> 1.102s dracut-initqueue.service
> 1.015s lvm2-monitor.service
>
>
It seems latest updates have solved my problems, both if network cable is
connected and without it.
My network card on laptop is this one from "lspci -v":
05:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet
(rev c0)
Subsystem: ASUSTeK Computer Inc. Device 1851
Flags: bus master, fast devsel, latency 0, IRQ 35
Memory at dc800000 (64-bit, non-prefetchable) [size=256K]
I/O ports at 9000 [size=128]
Capabilities: [40] Power Management version 3
Capabilities: [48] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [58] Express Endpoint, MSI 00
Capabilities: [6c] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [180] Device Serial Number ff-bd-21-9b-14-da-e9-ff
Kernel driver in use: atl1c
Kernel modules: atl1c
It seems combination of latest kernel (4.16.6-202.fc27.x86_64) and latest
packages I have again my old behavior.
With network cable connected to an automatic dhcp connection:
[g.cecchi@ope46 ~]$ sudo systemd-analyze time
Startup finished in 1.386s (kernel) + 1.328s (initrd) + 8.891s (userspace)
= 11.606s
[g.cecchi@ope46 ~]$
[g.cecchi@ope46 ~]$ sudo systemd-analyze blame
4.568s ntpdate.service
2.145s NetworkManager-wait-online.service
1.168s cups.service
1.158s plymouth-quit-wait.service
1.019s abrtd.service
819ms lvm2-monitor.service
716ms systemd-udev-settle.service
712ms libvirtd.service
. . .
Without network cable connected (and without wirelsss autoconnect)
[g.cecchi@ope46 ~]$ sudo systemd-analyze time
Startup finished in 1.389s (kernel) + 2.002s (initrd) + 8.702s (userspace)
= 12.094s
[g.cecchi@ope46 ~]$
and
[g.cecchi@ope46 ~]$ sudo systemd-analyze blame
6.337s NetworkManager-wait-online.service
1.189s cups.service
1.181s dracut-initqueue.service
1.021s abrtd.service
971ms lvm2-monitor.service
886ms plymouth-quit-wait.service
865ms systemd-udev-settle.service
682ms firewalld.service
641ms libvirtd.service
. . .
dnf summary for latest updates has been:
Installed:
kernel.x86_64 4.16.6-202.fc27 kernel-core.x86_64
4.16.6-202.fc27
kernel-devel.x86_64 4.16.6-202.fc27 kernel-modules.x86_64
4.16.6-202.fc27
kernel-modules-extra.x86_64 4.16.6-202.fc27
python2-ntlm-auth.noarch 1.1.0-1.fc27
Upgraded:
ansible.noarch 2.5.2-1.fc27
cinnamon-themes.noarch 1:1.6.2-1.fc27
copy-jdk-configs.noarch 3.3-9.fc27
httpd.x86_64 2.4.33-5.fc27
httpd-filesystem.noarch 2.4.33-5.fc27
httpd-tools.x86_64 2.4.33-5.fc27
hwdata.noarch 0.312-1.fc27
kdiagram.x86_64 2.6.1-2.fc27
kernel-headers.x86_64 4.16.6-202.fc27
libpsl.x86_64 0.18.0-2.fc27
mate-panel.x86_64 1.20.1-5.fc27
mate-panel-libs.x86_64 1.20.1-5.fc27
mint-themes.noarch 1:1.6.2-1.fc27
mint-themes-gtk3.noarch 1:1.6.2-1.fc27
mint-x-icons.noarch 1.4.7-1.fc27
mint-y-icons.noarch 1.1.4-1.fc27
mint-y-theme.noarch 1:1.6.2-1.fc27
mod_ssl.x86_64 1:2.4.33-5.fc27
opencv.x86_64 3.2.0-15.fc27
opencv-contrib.x86_64 3.2.0-15.fc27
opencv-core.x86_64 3.2.0-15.fc27
powerdevil.x86_64 5.12.4-2.fc27
publicsuffix-list-dafsa.noarch 20180419-1.fc27
python2-opencv.x86_64 3.2.0-15.fc27
python2-requests_ntlm.noarch 1.1.0-1.fc27
python2-winrm.noarch 0.3.0-1.fc27
selinux-policy.noarch 3.13.1-283.34.fc27
selinux-policy-devel.noarch 3.13.1-283.34.fc27
selinux-policy-targeted.noarch 3.13.1-283.34.fc27
spirv-tools-libs.i686 2018.3.0-0.1.20180407.git26a698c.fc27
spirv-tools-libs.x86_64 2018.3.0-0.1.20180407.git26a698c.fc27
vim-common.x86_64 2:8.0.1788-1.fc27
vim-enhanced.x86_64 2:8.0.1788-1.fc27
vim-filesystem.noarch 2:8.0.1788-1.fc27
vim-minimal.x86_64 2:8.0.1788-1.fc27
vulkan.i686 1.1.73.0-1.fc27
vulkan.x86_64 1.1.73.0-1.fc27
vulkan-filesystem.noarch 1.1.73.0-1.fc27
Cheers,
Gianluca
1 year, 7 months
Could LightDM be bad?? (LONG)
by Beartooth
I keep three PCs on my desk, running Fedora behind a KVM switch: #1 is
my present biggest fastest, #2 its predecessor, and #3 that one's
predecessor; I try try keep them as similar as is feasible.
They've all been having troubles for months, which have only gotten worse.
Under F27, they kept filling up with some sort of cruft, to the point
of refusing dnf upgrade; but when I found any of the cruft, it was in
places where I dared not lay about me with a cyber-battleaxe. I jumped
to F28 the day of release.
At this point, none of the three is usable at all without some dodge or
other.
#2 and #3 have each been wiped, twice, with different releases of DBAN,
followed each time with a netinstall of F28 with Mate, and then dnf
upgrade daily. All their boot messages show green OK. Those end with
"Started Light Display Manager."
Usually they proceed to a login box in front of the F28 display of blue
light-conducting fibers. That accepts my password, churns a little way,
and ends with a monitor full of blue horizontal lines, plus a few white
lines in the middle and at the bottom; there is nothing legible.
By doing Alt-Ctrl-F2, I get a display which lets me log in as root; I
keep doing dnf upgrades, and trying startx, every day. I also reboot
whenever there's a kernel change.
Startx always flashes a couple times, then fails with a few lines of
text, beginning with an attempt to adopt my monitor size (called "1920
1080" -- not 1920x1080),losing contact, and ending by saying that the
Xserver "terminated successfully."
I'd like to try replacing LDM with something else; how do I do that??
(I like Mate well, and would prefer not to swap it out,too)
Finally, #1 has two F28 kernels -- which do no better than on #2 nor #3
-- and a rescue kernel from F26. Sic. Twenty-six, not 27 nor 28. But
that rescue kernel does support almost my whole GUI (I miss Pan badly.),
and I don't have to descend to the console.
#1 got F28 by upgrading with dnf from F27, and still has a lot of stuff
on it that I'd rather copy to #2 and #3 directly than by way of solid
state storage, if I dare risk malware. (I don't know where else all the
cruft could have come from, apart from malware, but I hope someone here
does.)
--
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.
1 year, 7 months
F28 suspend
by Berend De Schouwer
I've got a laptop that has started misbehaving on suspend.
About 1 in 10 suspends the laptop fails to fully suspend. It switches
mostly off (screen off, etc.) but some of the motherboard keeps
running. I know some of the motherboard keeps running because:
- the wifi light remains on
- the laptop will get hot because the fans don't start
The laptop does not respond to the power button to wake up. It's
necessary to force halt & reboot the laptop by holding the power button
down for a few seconds.
9 out of 10 times suspend works fine.
This appears to be a BIOS or kernel issue, since the last entries in
the logs are:
May 29 09:02:17 sieve-deschouwer-co-za systemd[1]: Reached target
Sleep.
May 29 09:02:17 sieve-deschouwer-co-za systemd[1]: Starting Suspend...
May 29 09:02:17 sieve-deschouwer-co-za systemd-sleep[21435]: Suspending
system...
May 29 09:02:17 sieve-deschouwer-co-za kernel: PM: suspend entry (deep)
-- Reboot --
On a successful suspend I will additionally get:
May 29 08:21:32 sieve-deschouwer-co-za kernel: PM: Syncing filesystems
... done.
This started at the same time as I upgraded to F28. The laptop has
previously worked fine since F24 or F25, or maybe earlier.
It's happened with a few different F28 kernel patchlevels.
product: HP ProBook 450 G2 (L8A81ES#ACQ)
model name : Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI
(rev 09)
Linux sieve-deschouwer-co-za 4.16.11-300.fc28.x86_64 #1 SMP Tue May 22
18:29:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Can anyone help me debug before I enter a bugzilla?
Berend
1 year, 7 months
