Directories created with garbage filenames, might be related to logging in to gnome and/or `gnome-shell: assertion 'path != NULL' failed`
Clash Royale CLAN TAG#URR8PPP
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_dir_open_with_errno: assertion 'path != NULL' failed
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_dir_open_with_errno: assertion 'path != NULL' failed
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
It looks like these messages happen at the time I log in. These messages look like they could be associated with timestamps, that I see for directories with garbage filenames that have been mysteriously created in my home directory. All of the directories seem to match messages, but there seem to be a couple of messages which do not have a matching directory.
$ ls -lt
total 60
drwxr-xr-x. 9 alan alan 4096 Jan 21 20:58 Documents
drwxr-xr-x. 2 alan alan 4096 Jan 20 10:16 'p'$'346'' '$'304''7V'
drwxr-xr-x. 9 alan alan 4096 Jan 17 11:19 Downloads
drwxr-xr-x. 2 alan alan 4096 Jan 17 10:53 ''$'360354'
drwxr-xr-x. 2 alan alan 4096 Jan 16 12:49 ''$'3600201250''w'$'177'
drwxr-xr-x. 2 alan alan 4096 Jan 15 12:36 'p'$'20367''z'$'21''V'
...
My current version of gnome-shell is gnome-shell-3.30.2-1.fc29.x86_64. Running journalctl | grep gnome-shell-3 shows that the upgrade to this version occurred on Jan 08, when I upgraded from Fedora 28 to Fedora 29. And the first of the assertion messages happened on Jan 08.
Are the garbage filenames caused by a bug in software packaged by Fedora 29?
If so, when this is fixed in Fedora 29, which package version(s) fix this bug? :-P
(Note to self: try running fatrace in a text console, while you log in to gnome.)
fedora
asked Jan 21 at 21:26
sourcejedisourcejedi
24.1k439106
add a comment |
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_dir_open_with_errno: assertion 'path != NULL' failed
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_dir_open_with_errno: assertion 'path != NULL' failed
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
It looks like these messages happen at the time I log in. These messages look like they could be associated with timestamps, that I see for directories with garbage filenames that have been mysteriously created in my home directory. All of the directories seem to match messages, but there seem to be a couple of messages which do not have a matching directory.
$ ls -lt
total 60
drwxr-xr-x. 9 alan alan 4096 Jan 21 20:58 Documents
drwxr-xr-x. 2 alan alan 4096 Jan 20 10:16 'p'$'346'' '$'304''7V'
drwxr-xr-x. 9 alan alan 4096 Jan 17 11:19 Downloads
drwxr-xr-x. 2 alan alan 4096 Jan 17 10:53 ''$'360354'
drwxr-xr-x. 2 alan alan 4096 Jan 16 12:49 ''$'3600201250''w'$'177'
drwxr-xr-x. 2 alan alan 4096 Jan 15 12:36 'p'$'20367''z'$'21''V'
...
My current version of gnome-shell is gnome-shell-3.30.2-1.fc29.x86_64. Running journalctl | grep gnome-shell-3 shows that the upgrade to this version occurred on Jan 08, when I upgraded from Fedora 28 to Fedora 29. And the first of the assertion messages happened on Jan 08.
Are the garbage filenames caused by a bug in software packaged by Fedora 29?
If so, when this is fixed in Fedora 29, which package version(s) fix this bug? :-P
(Note to self: try running fatrace in a text console, while you log in to gnome.)
fedora
asked Jan 21 at 21:26
sourcejedisourcejedi
24.1k439106
add a comment |
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_dir_open_with_errno: assertion 'path != NULL' failed
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_dir_open_with_errno: assertion 'path != NULL' failed
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
It looks like these messages happen at the time I log in. These messages look like they could be associated with timestamps, that I see for directories with garbage filenames that have been mysteriously created in my home directory. All of the directories seem to match messages, but there seem to be a couple of messages which do not have a matching directory.
$ ls -lt
total 60
drwxr-xr-x. 9 alan alan 4096 Jan 21 20:58 Documents
drwxr-xr-x. 2 alan alan 4096 Jan 20 10:16 'p'$'346'' '$'304''7V'
drwxr-xr-x. 9 alan alan 4096 Jan 17 11:19 Downloads
drwxr-xr-x. 2 alan alan 4096 Jan 17 10:53 ''$'360354'
drwxr-xr-x. 2 alan alan 4096 Jan 16 12:49 ''$'3600201250''w'$'177'
drwxr-xr-x. 2 alan alan 4096 Jan 15 12:36 'p'$'20367''z'$'21''V'
...
My current version of gnome-shell is gnome-shell-3.30.2-1.fc29.x86_64. Running journalctl | grep gnome-shell-3 shows that the upgrade to this version occurred on Jan 08, when I upgraded from Fedora 28 to Fedora 29. And the first of the assertion messages happened on Jan 08.
Are the garbage filenames caused by a bug in software packaged by Fedora 29?
If so, when this is fixed in Fedora 29, which package version(s) fix this bug? :-P
(Note to self: try running fatrace in a text console, while you log in to gnome.)
fedora
asked Jan 21 at 21:26
sourcejedisourcejedi
24.1k439106
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_dir_open_with_errno: assertion 'path != NULL' failed
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_dir_open_with_errno: assertion 'path != NULL' failed
Jan 17 10:53:07 alan-laptop gnome-shell[2033]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
It looks like these messages happen at the time I log in. These messages look like they could be associated with timestamps, that I see for directories with garbage filenames that have been mysteriously created in my home directory. All of the directories seem to match messages, but there seem to be a couple of messages which do not have a matching directory.
$ ls -lt
total 60
drwxr-xr-x. 9 alan alan 4096 Jan 21 20:58 Documents
drwxr-xr-x. 2 alan alan 4096 Jan 20 10:16 'p'$'346'' '$'304''7V'
drwxr-xr-x. 9 alan alan 4096 Jan 17 11:19 Downloads
drwxr-xr-x. 2 alan alan 4096 Jan 17 10:53 ''$'360354'
drwxr-xr-x. 2 alan alan 4096 Jan 16 12:49 ''$'3600201250''w'$'177'
drwxr-xr-x. 2 alan alan 4096 Jan 15 12:36 'p'$'20367''z'$'21''V'
...
My current version of gnome-shell is gnome-shell-3.30.2-1.fc29.x86_64. Running journalctl | grep gnome-shell-3 shows that the upgrade to this version occurred on Jan 08, when I upgraded from Fedora 28 to Fedora 29. And the first of the assertion messages happened on Jan 08.
Are the garbage filenames caused by a bug in software packaged by Fedora 29?
If so, when this is fixed in Fedora 29, which package version(s) fix this bug? :-P
(Note to self: try running fatrace in a text console, while you log in to gnome.)
fedora
fedora
asked Jan 21 at 21:26
sourcejedisourcejedi
24.1k439106
asked Jan 21 at 21:26
sourcejedisourcejedi
24.1k439106
edited Jan 21 at 21:35
sourcejedi
asked Jan 21 at 21:26
sourcejedisourcejedi
24.1k439106
asked Jan 21 at 21:26
sourcejedisourcejedi
24.1k439106
asked Jan 21 at 21:26
sourcejedisourcejedi
24.1k439106
24.1k439106
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495858%2fdirectories-created-with-garbage-filenames-might-be-related-to-logging-in-to-gn%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495858%2fdirectories-created-with-garbage-filenames-might-be-related-to-logging-in-to-gn%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
