Rhythmbox on Ubuntu 16.04 works only with sudo











up vote
1
down vote

favorite












When I try to run rhythmbox as a user it shows:



jakub@XenialHP:~$ rhythmbox
Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached
Aborted (core dump)


(the last line of the transcript is my translation into English, maybe not the exact message)



When I try to run it as a root, rhythmbox works well. Reinstalling and purging does not help.



What might be wrong?










share|improve this question
























  • Try closing rhythmbox and then running the following as an ordinary user: mv -v ~/.local/share/rhythmbox ~/.local/share/rhythmbox_bak and then restart rhythmbox.
    – andrew.46
    Aug 10 '16 at 9:14












  • Didn't help: jakub@XenialHP:~$ mv -v ~/.local/share/rhythmbox ~/.local/share/rhythmbox_bak '/home/jakub/.local/share/rhythmbox' -> '/home/jakub/.local/share/rhythmbox_bak' jakub@XenialHP:~$ rhythmbox ** Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached Przerwane (zrzut pamięci) jakub@XenialHP:~$
    – iacobus
    Aug 10 '16 at 9:35












  • More details: jakub@XenialHP:/etc/apparmor.d$ rhythmbox -d (12:02:30) [0x7f89dc0056a0] [rb_debug_init_match] rb-debug.c:240: Debugging enabled (12:02:30) [0x7f89dc0056a0] [construct_db] rb-shell.c:454: creating database object (12:02:30) [0x7f89dc0056a0] [impl_constructor] rb-ext-db.c:354: creating new metadata store instance album-art ** Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached Aborted (core dump)
    – iacobus
    Aug 10 '16 at 10:03















up vote
1
down vote

favorite












When I try to run rhythmbox as a user it shows:



jakub@XenialHP:~$ rhythmbox
Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached
Aborted (core dump)


(the last line of the transcript is my translation into English, maybe not the exact message)



When I try to run it as a root, rhythmbox works well. Reinstalling and purging does not help.



What might be wrong?










share|improve this question
























  • Try closing rhythmbox and then running the following as an ordinary user: mv -v ~/.local/share/rhythmbox ~/.local/share/rhythmbox_bak and then restart rhythmbox.
    – andrew.46
    Aug 10 '16 at 9:14












  • Didn't help: jakub@XenialHP:~$ mv -v ~/.local/share/rhythmbox ~/.local/share/rhythmbox_bak '/home/jakub/.local/share/rhythmbox' -> '/home/jakub/.local/share/rhythmbox_bak' jakub@XenialHP:~$ rhythmbox ** Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached Przerwane (zrzut pamięci) jakub@XenialHP:~$
    – iacobus
    Aug 10 '16 at 9:35












  • More details: jakub@XenialHP:/etc/apparmor.d$ rhythmbox -d (12:02:30) [0x7f89dc0056a0] [rb_debug_init_match] rb-debug.c:240: Debugging enabled (12:02:30) [0x7f89dc0056a0] [construct_db] rb-shell.c:454: creating database object (12:02:30) [0x7f89dc0056a0] [impl_constructor] rb-ext-db.c:354: creating new metadata store instance album-art ** Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached Aborted (core dump)
    – iacobus
    Aug 10 '16 at 10:03













up vote
1
down vote

favorite









up vote
1
down vote

favorite











When I try to run rhythmbox as a user it shows:



jakub@XenialHP:~$ rhythmbox
Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached
Aborted (core dump)


(the last line of the transcript is my translation into English, maybe not the exact message)



When I try to run it as a root, rhythmbox works well. Reinstalling and purging does not help.



What might be wrong?










share|improve this question















When I try to run rhythmbox as a user it shows:



jakub@XenialHP:~$ rhythmbox
Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached
Aborted (core dump)


(the last line of the transcript is my translation into English, maybe not the exact message)



When I try to run it as a root, rhythmbox works well. Reinstalling and purging does not help.



What might be wrong?







rhythmbox






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 10 '16 at 9:54









techraf

2,75092035




2,75092035










asked Aug 10 '16 at 9:09









iacobus

379114




379114












  • Try closing rhythmbox and then running the following as an ordinary user: mv -v ~/.local/share/rhythmbox ~/.local/share/rhythmbox_bak and then restart rhythmbox.
    – andrew.46
    Aug 10 '16 at 9:14












  • Didn't help: jakub@XenialHP:~$ mv -v ~/.local/share/rhythmbox ~/.local/share/rhythmbox_bak '/home/jakub/.local/share/rhythmbox' -> '/home/jakub/.local/share/rhythmbox_bak' jakub@XenialHP:~$ rhythmbox ** Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached Przerwane (zrzut pamięci) jakub@XenialHP:~$
    – iacobus
    Aug 10 '16 at 9:35












  • More details: jakub@XenialHP:/etc/apparmor.d$ rhythmbox -d (12:02:30) [0x7f89dc0056a0] [rb_debug_init_match] rb-debug.c:240: Debugging enabled (12:02:30) [0x7f89dc0056a0] [construct_db] rb-shell.c:454: creating database object (12:02:30) [0x7f89dc0056a0] [impl_constructor] rb-ext-db.c:354: creating new metadata store instance album-art ** Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached Aborted (core dump)
    – iacobus
    Aug 10 '16 at 10:03


















  • Try closing rhythmbox and then running the following as an ordinary user: mv -v ~/.local/share/rhythmbox ~/.local/share/rhythmbox_bak and then restart rhythmbox.
    – andrew.46
    Aug 10 '16 at 9:14












  • Didn't help: jakub@XenialHP:~$ mv -v ~/.local/share/rhythmbox ~/.local/share/rhythmbox_bak '/home/jakub/.local/share/rhythmbox' -> '/home/jakub/.local/share/rhythmbox_bak' jakub@XenialHP:~$ rhythmbox ** Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached Przerwane (zrzut pamięci) jakub@XenialHP:~$
    – iacobus
    Aug 10 '16 at 9:35












  • More details: jakub@XenialHP:/etc/apparmor.d$ rhythmbox -d (12:02:30) [0x7f89dc0056a0] [rb_debug_init_match] rb-debug.c:240: Debugging enabled (12:02:30) [0x7f89dc0056a0] [construct_db] rb-shell.c:454: creating database object (12:02:30) [0x7f89dc0056a0] [impl_constructor] rb-ext-db.c:354: creating new metadata store instance album-art ** Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached Aborted (core dump)
    – iacobus
    Aug 10 '16 at 10:03
















Try closing rhythmbox and then running the following as an ordinary user: mv -v ~/.local/share/rhythmbox ~/.local/share/rhythmbox_bak and then restart rhythmbox.
– andrew.46
Aug 10 '16 at 9:14






Try closing rhythmbox and then running the following as an ordinary user: mv -v ~/.local/share/rhythmbox ~/.local/share/rhythmbox_bak and then restart rhythmbox.
– andrew.46
Aug 10 '16 at 9:14














Didn't help: jakub@XenialHP:~$ mv -v ~/.local/share/rhythmbox ~/.local/share/rhythmbox_bak '/home/jakub/.local/share/rhythmbox' -> '/home/jakub/.local/share/rhythmbox_bak' jakub@XenialHP:~$ rhythmbox ** Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached Przerwane (zrzut pamięci) jakub@XenialHP:~$
– iacobus
Aug 10 '16 at 9:35






Didn't help: jakub@XenialHP:~$ mv -v ~/.local/share/rhythmbox ~/.local/share/rhythmbox_bak '/home/jakub/.local/share/rhythmbox' -> '/home/jakub/.local/share/rhythmbox_bak' jakub@XenialHP:~$ rhythmbox ** Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached Przerwane (zrzut pamięci) jakub@XenialHP:~$
– iacobus
Aug 10 '16 at 9:35














More details: jakub@XenialHP:/etc/apparmor.d$ rhythmbox -d (12:02:30) [0x7f89dc0056a0] [rb_debug_init_match] rb-debug.c:240: Debugging enabled (12:02:30) [0x7f89dc0056a0] [construct_db] rb-shell.c:454: creating database object (12:02:30) [0x7f89dc0056a0] [impl_constructor] rb-ext-db.c:354: creating new metadata store instance album-art ** Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached Aborted (core dump)
– iacobus
Aug 10 '16 at 10:03




More details: jakub@XenialHP:/etc/apparmor.d$ rhythmbox -d (12:02:30) [0x7f89dc0056a0] [rb_debug_init_match] rb-debug.c:240: Debugging enabled (12:02:30) [0x7f89dc0056a0] [construct_db] rb-shell.c:454: creating database object (12:02:30) [0x7f89dc0056a0] [impl_constructor] rb-ext-db.c:354: creating new metadata store instance album-art ** Rhythmbox:ERROR:rb-ext-db.c:362:impl_constructor: code should not be reached Aborted (core dump)
– iacobus
Aug 10 '16 at 10:03










1 Answer
1






active

oldest

votes

















up vote
2
down vote



accepted










I asked on GNOME bugzilla and get proper answer:



Jonathan Matthew [rhythmbox developer]:




You apparently don't have permission to create ~/.cache/rhythmbox and you should fix that. Rhythmbox could probably report the error better, but this has been the error handling mechanism for five years and no one has noticed before.




I used chown /home/jakub/ -R to fix it, and now rhythmbox works well.






share|improve this answer

















  • 1




    Remember not to use sudo rhythmbox in the future; that was the cause of root owning your ~/.cache/rhythmbox.
    – edwinksl
    Aug 10 '16 at 10:50










  • I tried to replicate this and it seems to have nothing with sudo: 'ls -al ~/.cache/rhythmbox' shows no chagne after 'sudo rhythmbox'
    – iacobus
    Aug 10 '16 at 10:56











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f810430%2frhythmbox-on-ubuntu-16-04-works-only-with-sudo%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
2
down vote



accepted










I asked on GNOME bugzilla and get proper answer:



Jonathan Matthew [rhythmbox developer]:




You apparently don't have permission to create ~/.cache/rhythmbox and you should fix that. Rhythmbox could probably report the error better, but this has been the error handling mechanism for five years and no one has noticed before.




I used chown /home/jakub/ -R to fix it, and now rhythmbox works well.






share|improve this answer

















  • 1




    Remember not to use sudo rhythmbox in the future; that was the cause of root owning your ~/.cache/rhythmbox.
    – edwinksl
    Aug 10 '16 at 10:50










  • I tried to replicate this and it seems to have nothing with sudo: 'ls -al ~/.cache/rhythmbox' shows no chagne after 'sudo rhythmbox'
    – iacobus
    Aug 10 '16 at 10:56















up vote
2
down vote



accepted










I asked on GNOME bugzilla and get proper answer:



Jonathan Matthew [rhythmbox developer]:




You apparently don't have permission to create ~/.cache/rhythmbox and you should fix that. Rhythmbox could probably report the error better, but this has been the error handling mechanism for five years and no one has noticed before.




I used chown /home/jakub/ -R to fix it, and now rhythmbox works well.






share|improve this answer

















  • 1




    Remember not to use sudo rhythmbox in the future; that was the cause of root owning your ~/.cache/rhythmbox.
    – edwinksl
    Aug 10 '16 at 10:50










  • I tried to replicate this and it seems to have nothing with sudo: 'ls -al ~/.cache/rhythmbox' shows no chagne after 'sudo rhythmbox'
    – iacobus
    Aug 10 '16 at 10:56













up vote
2
down vote



accepted







up vote
2
down vote



accepted






I asked on GNOME bugzilla and get proper answer:



Jonathan Matthew [rhythmbox developer]:




You apparently don't have permission to create ~/.cache/rhythmbox and you should fix that. Rhythmbox could probably report the error better, but this has been the error handling mechanism for five years and no one has noticed before.




I used chown /home/jakub/ -R to fix it, and now rhythmbox works well.






share|improve this answer












I asked on GNOME bugzilla and get proper answer:



Jonathan Matthew [rhythmbox developer]:




You apparently don't have permission to create ~/.cache/rhythmbox and you should fix that. Rhythmbox could probably report the error better, but this has been the error handling mechanism for five years and no one has noticed before.




I used chown /home/jakub/ -R to fix it, and now rhythmbox works well.







share|improve this answer












share|improve this answer



share|improve this answer










answered Aug 10 '16 at 10:44









iacobus

379114




379114








  • 1




    Remember not to use sudo rhythmbox in the future; that was the cause of root owning your ~/.cache/rhythmbox.
    – edwinksl
    Aug 10 '16 at 10:50










  • I tried to replicate this and it seems to have nothing with sudo: 'ls -al ~/.cache/rhythmbox' shows no chagne after 'sudo rhythmbox'
    – iacobus
    Aug 10 '16 at 10:56














  • 1




    Remember not to use sudo rhythmbox in the future; that was the cause of root owning your ~/.cache/rhythmbox.
    – edwinksl
    Aug 10 '16 at 10:50










  • I tried to replicate this and it seems to have nothing with sudo: 'ls -al ~/.cache/rhythmbox' shows no chagne after 'sudo rhythmbox'
    – iacobus
    Aug 10 '16 at 10:56








1




1




Remember not to use sudo rhythmbox in the future; that was the cause of root owning your ~/.cache/rhythmbox.
– edwinksl
Aug 10 '16 at 10:50




Remember not to use sudo rhythmbox in the future; that was the cause of root owning your ~/.cache/rhythmbox.
– edwinksl
Aug 10 '16 at 10:50












I tried to replicate this and it seems to have nothing with sudo: 'ls -al ~/.cache/rhythmbox' shows no chagne after 'sudo rhythmbox'
– iacobus
Aug 10 '16 at 10:56




I tried to replicate this and it seems to have nothing with sudo: 'ls -al ~/.cache/rhythmbox' shows no chagne after 'sudo rhythmbox'
– iacobus
Aug 10 '16 at 10:56


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • 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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f810430%2frhythmbox-on-ubuntu-16-04-works-only-with-sudo%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Quarter-circle Tiles

build a pushdown automaton that recognizes the reverse language of a given pushdown automaton?

Mont Emei