08-06-2020, 01:11 PM
Yes, I saw the out of memory error but the challenge is to provide a way for me to reproduce that condition, otherwise it won't be possible to troubleshoot.
Thank you for your donation!
Official moOde 6.7.1 support thread
|
08-06-2020, 01:11 PM
Yes, I saw the out of memory error but the challenge is to provide a way for me to reproduce that condition, otherwise it won't be possible to troubleshoot.
08-06-2020, 02:17 PM
@petfr
I'm running an official Raspberry Pi 7 inch display on a RPi3B+ and I have never experienced this issue. The xinit error "received unexpected number of handles" (shown in your "not working" image) can be found in a number of posts on the InterWeb but the answers to those posts aren't very informative. It appears to be an all-purpose error message which doesn't suggest a specific issue with moOde. One long shot: have you tried clearing the Browser cache for the local display? It's an option in the System Config screen. The xinit error "FontService unique font name matching request did not receive a response" (shown in your "working" image) is interesting. I see it too. Some recent InterWeb posts suggest that this message has been popping up in systems with one or more Chrome browser updates in 2020 which somehow bork certain fonts. I'll dig a little deeper. Regards, Kent
08-06-2020, 03:05 PM
@petfr
Seems unlikely that shutting down and starting up is the culprit here. I do this all the time with various test systems. As I dig a little deeper I find that the FontService message is not necessarily an indicator of something seriously broken. As one poster said in relation to Chrome, "it's been around for years." Still, it seems like something fixable. How far south is "south of Germany"? Should I be saying Grüss Gott or Guten Tag? My sister has resided for many years in Munich but decades ago she lived in Untereglfing. Regards, Kent
08-06-2020, 03:23 PM
@petfr
Quote:As you can see, the south of Germany is not automatically Bavaria. That's not what the Bavarians tell me ![]() We have a similar issue here in the USA. I used to have to explain to people that New Mexico, where I lived for some years, isn't part of Texas. Regards, Kent
When Bluetooth renderer is active, /var/log/auth is spam every 3 seconds with this:
Code: moode sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/pgrep -l bluealsa-aplay Ive manage to get rid of those with this procedure: Code: sudo nano /etc/sudoers.d/010_root Code: Defaults:root !logfile, !syslog Code: sudo chmod 440 /etc/sudoers.d/010_root Edit sudo pam files and add 1 line (session...): Editing this file can break ur system if u do something wrong, so i prefer changed permissions before: Code: sudo chmod 666 /etc/pam.d/sudo Code: #%PAM-1.0 Run any sudo command, if no error: Code: sudo chmod 644 /etc/pam.d/sudo It should be good
Sorry, i misleaded you, it is not related to ur problem, just a fix for peoples who wants to fix log's spam.
08-17-2020, 02:22 PM
(07-22-2020, 10:15 PM)Tim Curtis Wrote: Hi, Hi Tim, Once again, good job with this release ! For my needs, everything works properly (moOde is the only distribution I am able to use with samba shares...), except for one feature : the spotify renderer. It works well, but after a few minutes, it just stops playing music from the active playlist (even though there are still songs in the queue list). Music just stops. I have to take my smartphone and hit play again. Is it something other users encounter ? I have a premium Spotify family account. Music plays during hours without interruption from the radio stations or from samba shares. Smartphone is a Huawei P20 with Emui 10 (Spotify app management is handled manually). As far as I remember, it worked well with moOde 6.5.2. Will test again with a previous moOde version if needs be. Kind regards, Renaud
08-17-2020, 03:21 PM
(08-17-2020, 02:22 PM)zazouboy Wrote:(07-22-2020, 10:15 PM)Tim Curtis Wrote: Hi, Well, I tested the same playlist, but this time with "random" button activated in Spotify. The music does not stop ! It should be a bug in the Spotify app... Not related with moOde. So please forget this unuseful contribution ;-) Kind regards, keep safe. Renaud
08-17-2020, 04:37 PM
(This post was last modified: 08-17-2020, 04:37 PM by Tim Curtis.)
Checking the repo, v0.1.3 librespot was recently released and it contains a number of bug fixes related to playback suddenly stopping.
https://github.com/librespot-org/libresp...tag/v0.1.3 I'll plan to bump to this or a later release for moOde 7.
08-19-2020, 06:35 AM
Hi Tim and all,
I am on moode audio 6.7.1. with allo usbridge signature, today in the morning I noticed that my DAC (TOPPING DX7S) MPD configuration is missing. I didn't do any changes, I didn't connect or disconnect anything new to allo. Unfortunately I don't see my DAC in drop down list in MPD config I tried to shutdown or restart mo0de couple of times already. All I see is in MPD config audio output drop down list 2 options "Pi HDMI " and Pi Headphone jack". Previously I could see my DAC there? I think that if I do a fresh mo0de installation my dac will be visible again after a fresh boot up. That comes down to the question. Can I somehow set my DAC (TOPPING DX7S) as a default kind of constant output device? I don't plan to change my DAC anytime soon. Pawel, |
« Next Oldest | Next Newest »
|