Bug 374072

Summary:	plasmashell spams log with "QFileInfo::absolutePath: Constructed with empty filename"
Product:	[Plasma] plasmashell	Reporter:	azrdev
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED FIXED
Severity:	minor	CC:	bshah, grgoffe, justin.zobel, kevin.paetzold, plasma-bugs-null
Priority:	NOR
Version First Reported In:	5.8.4
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=384653
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	gziped flat file of /var/log/messages

Description azrdev 2016-12-23 09:44:00 UTC

KF5 install on Archlinux here. Having the machine running idle, syslog/journal is spammed with this message every 5s:
Dec 23 10:21:47 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:21:47 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:21:47 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:21:52 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:21:52 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:21:52 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:21:57 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:21:57 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:21:57 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:22:02 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:22:02 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:22:02 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:22:07 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:22:07 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:22:07 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:22:12 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename
Dec 23 10:22:12 rusuf plasmashell[10348]: QFileInfo::absolutePath: Constructed with empty filename

Comment 1 David Edmundson 2016-12-23 13:50:24 UTC

Grepping for all things with a 5 second timeout, it seems it could be klipper.

Can you disable the klipper plasmoid temporarily to confirm that's the cause of the warning?

If so, can you also upload your ~/.config/klipperrc and ~/.config/plasma-org.kde.plasma.desktop-appletsrc

then reset the bug status to "confirmed" thanks.

Comment 2 Christoph Feck 2016-12-31 21:24:30 UTC

If you can provide the information requested in comment #1, please add a comment.

Comment 3 azrdev 2017-03-22 11:07:04 UTC

After disabling the klipper plasmoid this still occurs occasionally (i.e. not permanent, but if it occurs, then in 5s intervals for longer durations).

also, `pgrep klipper` yields nothing, and I rebooted the system in the meantime.

Looking at the log messages surrounding start/end of such durations, what stands out are messages about (de)attaching of my Android phone via USB, maybe it's related to this?

Comment 4 George R. Goffe 2017-07-29 12:37:13 UTC

Created attachment 106951 [details]
gziped flat file of /var/log/messages

Hi,

I'm running Fedora 27 (rawhide) and am seeing TONS of these and other messages from plasmashell. See attachment.

George...

Comment 5 kevin paetzold 2017-08-31 12:46:14 UTC

i see tons of these messages.  i am running fedora 27 with Mate (although there are various/many kde packages loaded).   This seems to be provoked by copying large (multi gb) files using the gui interface (caja).

Comment 6 kevin paetzold 2017-08-31 12:46:54 UTC

i lied.  i am running fedora 26.

Comment 7 Justin Zobel 2020-11-10 04:08:50 UTC

I'm running Plasma and associated apps from git master and I cannot reproduce this issue.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" when you respond, thanks.

Comment 8 George R. Goffe 2020-11-11 03:42:57 UTC

Justin,

Let's close this one too. I haven't seen it in a while.

George...

Comment 9 Justin Zobel 2020-11-11 03:51:45 UTC

(In reply to George R. Goffe from comment #8)
> Justin,
> 
> Let's close this one too. I haven't seen it in a while.
> 
> George...

Thanks George.

If this issue arises again for anyone don't hesitate to report again.