INTERACT FORUM
More => Old Versions => JRiver Media Center 20 for Linux => Topic started by: bob on April 10, 2015, 11:38:34 am
-
The latest build is up at:
https://files.jriver.com/mediacenter/channels/v20/latest/MediaCenter-20.0.131-amd64.deb (also in the latest apt repository)
20.0.131 (7/27/2015)
1. Changed: Relaxed system library requirements more to help with portability.
2. Changed: Changes from the main branch
20.0.129 (7/14/2015)
1. Fixed: The focus fix from 20.0.123 was incomplete and was preventing the DSP studio (amongst others) from showing properly on hover.
2. Changed: All MC windows are class hinted properly now.
20.0.123 (6/23/2015)
1. Fixed: MC will no longer take focus from other apps on state transitions (unless MC has the mouse cursor).
2. Fixed: Ratings in the Purity Skin.
20.0.122
1) Changed: Changes from the main branch.
20.0.114
1) Changed: Reduced use of system libraries.
20.0.110
This is compiled on the new (4/25/2015) debian Jessie release.
It will run on ubuntu 14.10 without needing non-ubuntu files.
It will NOT run on 14.04 (because of issues with libgnutls28). If you are using 14.04, stick with the i386 version.
For the linux specific changes see the i386 linux version announcement and for general changes see the most recent windows announcement.
Only amd64 specific issues should be added to this thread. Put general linux issues in the JRiver Media Center 20.0.xx for Debian threads.
-
hi there i was wondering i am using Ubuntu and i have tried media center 20 an older version
wasn't working well
so i removed it
but now i want to try again but as you can guess trail period has ended
now is there a way to get another trail period
because i also own a pono player ;D and pono lets me in the dark about there pmw app for linux and it seems the mc 20 also does the job
but i want to be sure before i purchase it
with kind regards erwin
-
hi there i was wondering i am using Ubuntu and i have tried media center 20 an older version
wasn't working well
so i removed it
but now i want to try again but as you can guess trail period has ended
now is there a way to get another trail period
because i also own a pono player ;D and pono lets me in the dark about there pmw app for linux and it seems the mc 20 also does the job
but i want to be sure before i purchase it
with kind regards erwin
I use MC on linux to copy files to the pono player. It works fine for me. You need to setup the player manually as a handheld device which may be more trouble than you are willing to go through.
-
Heads up, looks like libgcrypt11 isn't included with Ubuntu 15.04 by default. Have to manually download the .deb file for Trusty to successfully install MC on 15.04.
-
Debian Jessie is going to be released on 2015-04-25, making jessie stable and wheezy the oldstable. Maybe Bob already made plans to eventually move our builds over to jessie packages? :)
This would include gcrypt20 then, among a long list of other more up-to-date versions of everything.
-
Debian Jessie is going to be released on 2015-04-25, making jessie stable and wheezy the oldstable. Maybe Bob already made plans to eventually move our builds over to jessie packages? :)
This would include gcrypt20 then, among a long list of other more up-to-date versions of everything.
That would be great. Depending on which kernel and ALSA is included with Jessie final, should be able to get DSD working too... at least for *some* DACs. Nonetheless, I added a workaround for 15.04 in the setup thread.
-
That would be great. Depending on which kernel and ALSA is included with Jessie final, should be able to get DSD working too... at least for *some* DACs. Nonetheless, I added a workaround for 15.04 in the setup thread.
Jessie's been frozen for months, and the kernel will be some flavor of 3.16. The DSD patches are in 3.19 I think, so probably no DSD this Debian cycle (at least not in stable).
Debian Jessie is going to be released on 2015-04-25, making jessie stable and wheezy the oldstable. Maybe Bob already made plans to eventually move our builds over to jessie packages? :)
This would include gcrypt20 then, among a long list of other more up-to-date versions of everything.
This would be exciting.
-
It's going to be it bit difficult to determine when to update the build tree.
What do people think about forcing users to upgrade their systems to Jessie?
-
FWIW, Debian stable users (and I say this as someone running several debian stable systems) learn to expect two things: stability and out of date packages.
If you cut MC off at a certain version and say: versions later than this one will be available for Jessie, all earlier versions will still run on wheezy, you'll be doing no different than any other wheezy package. People running oldstable know to expect old packages. To cope with customer expectations, maybe make the cut at the major version number (when MC21 drops)?
By moving it up to Jessie, you'll also make life easier for folks running other distros as most of them are well past Wheezy's package versions at this point.
-
maybe make the cut at the major version number (when MC21 drops)?
This is what I was thought too.
-
OK. We'll do it tomorrow.
-
This is what I was thought too.
You really want to wait a couple more months for this to happen? Voluntarily? :)
For all I care, we could move the AMD64 build to jessie exclusively once jessie is out (because AMD64 has the most issues with dependencies), and maybe keep the 32-bit on wheezy, or package both for 32-bit, if thats not too much troubles code/build-system wise?
-
You really want to wait a couple more months for this to happen? Voluntarily? :)
For all I care, we could move the AMD64 build to jessie exclusively once jessie is out (because AMD64 has the most issues with dependencies), and maybe keep the 32-bit on wheezy, or package both for 32-bit, if thats not too much troubles code/build-system wise?
I like that idea Hendrik. It doesn't add complexity and still allows for backwards compatibility.
-
Yep, that works for me too.
-
So 20.0.100 is the first try with the new Debian Jessie release.
Requires:
libc >= 2.19
libasound2 >=1.0.27
libuuid1 >=2.20
libx11-6 >=2:1.6
libxcb1 >=1.10
libxdmcp6 >=1.1
libstdc++6
libgtk2.0-0 >=2.24
libp11-kit0 >=.20
libtasn1-6
libgnutls28
libgcrypt20 >=1.6
libidn11 >=1.28
libgl1 or libgl1-mesa-glx
xdg-utils
exo-utils or kde-runtime or konqueror or gvfs-bin or libgnome2-0 or pcmanfm
xfonts-75dpi
-
Works fine on Ubuntu 15.04. Though it's probably worth mentioning that libgnutls28 on 15.04 is called libgnutls-deb0-28.
-
I just installed MC 20 AMD64 in a VirtualBox VM with Debian stretch / KDE - Fresh installation.
dpkg -i Media Center 20.0.100-amd64.deb - that was it !!! Without installing any additional file ;) ;) ;) ;) ;) ;)
Whoa - works great. License with the GUI installed. The Resize works well. :)
Thanks for the good work.
Question:
On my main system (Debian Jessie) I have MC 20 I386 installed. Can I just install MC AMD64 there, after I uninstalled MC I386? Are the settings obtained?
-
Trying on TumbleWeed, I now have a:
libgnutils28 (<=libgnutls-deb0.so.28)
libhogweed2
libnettle4
but I get ldd libJRReader.so
./libJRReader.so: /usr/lib64/libgnutls-deb0.so.28: version `GNUTLS_DEBIAN_0_2_12' not found (required by ./libJRReader.so)
./libJRReader.so: /usr/lib64/libgnutls-deb0.so.28: version `GNUTLS_DEBIAN_0_1_4' not found (required by ./libJRReader.so)
Clearly my gnutils is not "compatible". Calling for these debian versions is set in stone as such?
-
I just installed MC 20 AMD64 in a VirtualBox VM with Debian stretch / KDE - Fresh installation.
dpkg -i Media Center 20.0.100-amd64.deb - that was it !!! Without installing any additional file ;) ;) ;) ;) ;) ;)
Whoa - works great. License with the GUI installed. The Resize works well. :)
Thanks for the good work.
Question:
On my main system (Debian Jessie) I have MC 20 I386 installed. Can I just install MC AMD64 there, after I uninstalled MC I386? Are the settings obtained?
Cool, I'm glad it works for you.
Yes, the settings should work with both the i386 and AMD64 builds and they will remain after you uninstall the i386 build.
Uninstall the i386 build BEFORE installing the amd64 build.
-
Trying on TumbleWeed, I now have a:
libgnutils28 (<=libgnutls-deb0.so.28)
libhogweed2
libnettle4
but I get ldd libJRReader.so
./libJRReader.so: /usr/lib64/libgnutls-deb0.so.28: version `GNUTLS_DEBIAN_0_2_12' not found (required by ./libJRReader.so)
./libJRReader.so: /usr/lib64/libgnutls-deb0.so.28: version `GNUTLS_DEBIAN_0_1_4' not found (required by ./libJRReader.so)
Clearly my gnutils is not "compatible". Calling for these debian versions is set in stone as such?
Tried as much as possible to get this to work. I think the version of gnutls28 you have is just too old. I get the same behavior on Ubuntu 14.04
If someone else has ideas on this I'd be interested in hearing them. gnutls is required for networking (it's what is used for secure connections).
This isn't an issue for the i386 build because it has gnutls statically linked in (not possible for amd64).
-
Installed Jessie 8.0 fresh last night after coming over from Mint 17.1.
Followed the installation tutorial from the forum here, but got version conflicts while trying to install the different dependencies. Found the latest version posted today. Installed the deb file and it worked straight away. Had to try 3 times to get to import my license from the license key file through the terminal. But at the third try it finally said registered.
But otherwise the program works flawlessly. Already streaming music to my smartphone through JRemote :D
-
Tried as much as possible to get this to work. I think the version of gnutls28 you have is just too old. I get the same behavior on Ubuntu 14.04
If someone else has ideas on this I'd be interested in hearing them. gnutls is required for networking (it's what is used for secure connections).
This isn't an issue for the i386 build because it has gnutls statically linked in (not possible for amd64).
Got the same thing when sym-linking to the default libgnutils(30) in TW. I'm going to try one more thing and then see if I can load up 13.2 somewhere....
-
Got the same thing when sym-linking to the default libgnutils(30) in TW. I'm going to try one more thing and then see if I can load up 13.2 somewhere....
There is some noise online about gnutls28 being some sort of transitory package with ABI differences from previous versions. There seems to be the need to know exactly what version it is hence the extra values?.
-
now I have MC 20 AMD 64 installed on my main system. First MC 20 I386 uninstalled. Super !! It works "out of the box". All settings are there as before - no new registration is necessary.
in /etc/apt/sources.list.d/mediacenter20.list the entry is :
#MC
deb [arch = i386] http://dist.jriver.com/latest/mediacenter/ wheezy main
I think this is not the correct entry
I'll comment out first
Edit:
must only the entry [arch = i386] in [ARCH = AMD64]
be changed?
Normally should the entry of "wheezy main" be changed to "jessie main"
-
You would just remove the entire arch entry if you want the amd64 version (its only required to get one not matching your system), and switch the wheezy to jessie.
Note that it may not be in the apt repository yet, since it was the first build for jessie, bob prefers to be cautious and post it here first.
-
You would just remove the entire arch entry if you want the amd64 version (its only required to get one not matching your system), and switch the wheezy to jessie.
Note that it may not be in the apt repository yet, since it was the first build for jessie, bob prefers to be cautious and post it here first.
Correct, there isn't a jessie in the repository yet.
-
Tried as much as possible to get this to work. I think the version of gnutls28 you have is just too old. I get the same behavior on Ubuntu 14.04
If someone else has ideas on this I'd be interested in hearing them. gnutls is required for networking (it's what is used for secure connections).
This isn't an issue for the i386 build because it has gnutls statically linked in (not possible for amd64).
Hi
I'm running SUSE 13.2 and had the same problem. I downloaded the lib "libgnutls-deb0-28_3.2.16-1ubuntu2_amd64" from the internet and extract it into "/usr/lib64". Now MC is working again, but the main window behavior is very strange and slow.
As soon as I move the cursor into the window, display action is slowing down, but the playback continues flawless.
I'm using the Bose Soundlink as a second device. Now, the remote control via soundlink is working! 8)
-
Some more things about the remote control:
I checked back to the previous version x.95: no remote action. With this version (x.100), the remote control is possible, but the MC-window must be the active window. As soon as you make a different window the active one, the remote is not functioning any more, 'til you give the control back to the MC-window.
I don't know, whether remote was possible before at other installations. I'm running SUSE 13.2 and it was never working.
-
Is this one expected to work on Arch x64?
I checked all the dependencies and I think they are all there, including gnutls26. When I run it I get a segmentation fault.
-
Is this one expected to work on Arch x64?
I checked all the dependencies and I think they are all there, including gnutls26. When I run it I get a segmentation fault.
No idea if it will run on Arch x64, I'd expect it would be easier to get running since it's based on Jessie.
You might want to check the forum post with the list of required libraries. It's been updated. We no longer use gnutls26. It's guntls28-deb0 or something like that.
-
Is this one expected to work on Arch x64?
I checked all the dependencies and I think they are all there, including gnutls26. When I run it I get a segmentation fault.
I spent a few hours with it both before and after the Jessie switch, and I can't get the 64-bit version running on Arch at all. I tried ldd and running an strace, but ultimately got nowhere. So I'll be sticking with the 32-bit version until someone smarter than me figures out how to satisfy the deps.
Arch is on libgnutls30, which may be part of the problem (that seemed to be the hangup in the strace).
-
Thanks.
I did install gnutls26 from AUR, I didn't know you moved it to 28. I dont think 28 is available though so that might be a problem.
-
gnutls is being kind of annoying, as Debian uses this special version with debian in the name, which happens to be available on Ubuntu, but not on other distributions really...
-
Hi bob,
if you use rar libs like libgnutls-deb0-28, isn't it possible to include it "usr/lib/jriver/Media Center 20" dir, since this is searched first for the presents of libs.
-
Bundling security-relevant libraries is rather ill-advised, as it puts the responsibility on us to keep them updated in case of a security issue, instead of the distributions.
-
Another satisfied Debian Jessie Gnome 64 customer here!! ;D
Congratulations on another milestone!!!
Media Center on all the things.
-
It's true that MC always searches the /usr/lib/jriver/Media Center xx/ directory for libraries first.
If one packages gnutls28 and it's dependencies so that it could be installed in there it would probably take care of the issue.
Other than removing the need for the multiarch libraries there is no particular reason to run the amd64 build as opposed to the i386 build.
-
Heads up everyone, I upgraded ALSA and Pulse on Ubuntu 15.04 (also using the 4.0.2 kernel) and tested DSD (DoP) output... it seems to be working fine! Awesome!
-
20.0.108 is in the apt repository as well. See the i386 build announcement for linux specific changes.
-
The window sizing and placement is much, much better in 108. However, I still notice a couple issues...
- By default for whatever reason the window is at the smallest size possible (e.g. on a clean install). If you don't see the faint window shadow, it's very hard to find the window on a large desktop.
- Still can't size the window to fill the entire window space on Ubuntu without maximizing the window. It seems to be a little glitchy, every time I try to size the window, it tends to 'glitch out' and produce a gap on the opposite side.
- I still randomly encounter the issue where the launcher will create multiple icons, e.g. the media center 20.desktop naming issue. It actually might be an internal issue that could potentially exist on Debian as well at random, not sure. I'll need to download Debian and test in my VM.
- The issues with skins, display of album art and closing the tree causing a libX11 segfault which I described here (http://yabb.jriver.com/interact/index.php?topic=96854.msg668859#msg668859) still exists. My video posted there also shows how to reproduce.
-
I've just installed Mc 108 (over 100]. The window sizing and placement is working very well.
Some small problems:
The icon is not displayed correctly. (in the tray and in the task bar). In my system, there were about 10 mediacenter20.desktop - files
example:
/home/hans/.local/share/applications/mediacenter20.desktop
/home/hans/.local/share/applications/media center 20.desktop
I think these are still some of the i 386 version left. But deleting was not the solution.
Do you have an idea to fix the icon- problem?
One more request:
Since ages the Mini-View does not work. Is it not possible to send the played tracks to the notifications? That would be a Great. The Mini - View would be almost unnecessary.
-
The window sizing and placement is much, much better in 108. However, I still notice a couple issues...
- By default for whatever reason the window is at the smallest size possible (e.g. on a clean install). If you don't see the faint window shadow, it's very hard to find the window on a large desktop.
- Still can't size the window to fill the entire window space on Ubuntu without maximizing the window. It seems to be a little glitchy, every time I try to size the window, it tends to 'glitch out' and produce a gap on the opposite side.
- I still randomly encounter the issue where the launcher will create multiple icons, e.g. the media center 20.desktop naming issue. It actually might be an internal issue that could potentially exist on Debian as well at random, not sure. I'll need to download Debian and test in my VM.
- The issues with skins, display of album art and closing the tree causing a libX11 segfault which I described here (http://yabb.jriver.com/interact/index.php?topic=96854.msg668859#msg668859) still exists. My video posted there also shows how to reproduce.
There still are some small issues with going between fullscreen/non-full screen.
As for the sizing to almost fullscreen within the desktop with Ubuntu, it appears to me there is something odd going on with the window manager and MC's skin size calculation.
I noticed that you can override this by using the alt-key method of move/resize.
I've never been able to reproduce your startup size issue. As a test you might try removing the Placement settings from the User Settings.ini file and restarting.
Hmm I just did that and reproduced your issue!
However as soon as I moved and expanded the window and exited from MC, it worked the next time.
What is your option setting for startup window mode in MC?
-
I've never been able to reproduce your startup size issue. As a test you might try removing the Placement settings from the User Settings.ini file and restarting.
Hmm I just did that and reproduced your issue!
However as soon as I moved and expanded the window and exited from MC, it worked the next time.
What is your option setting for startup window mode in MC?
Yes, it saves fine now. My location is last location and the mode is last exit view. I'll keep playing around with it more and see if I can encounter anything else. :) Good work, as always.
-
Yes, it saves fine now. My location is last location and the mode is last exit view. I'll keep playing around with it more and see if I can encounter anything else. :) Good work, as always.
Thanks for testing.
I'm trying to implement the checking on window placement that hasn't worked properly in linux to this point.
-
An update, I installed MC in a fresh Ubuntu 15.04 VM and noticed several issues.
- When first started MC is at the absolute smallest size possible with the very, very tiny window (with shadow) in the upper left corner.
- When trying to resize the window from above, MC will crash with the following in the terminal;
*** Error in 'mediacenter20': free(): invalid next size (fast): 0x00000000034afc30 ***
Aborted (core dumped)
On the positive side, it looks like MC can be installed without first installing any other dependencies (other than the ones installed when you install mediacenter20), which is great! :D
-
Has anyone noticed a graphical issue where dots appear within the skin (doesn't matter which skin - I see them in clean Ubuntu installs too)? They appeared with 108.
-
An update, I installed MC in a fresh Ubuntu 15.04 VM and noticed several issues.
- When first started MC is at the absolute smallest size possible with the very, very tiny window (with shadow) in the upper left corner.
- When trying to resize the window from above, MC will crash with the following in the terminal;
*** Error in 'mediacenter20': free(): invalid next size (fast): 0x00000000034afc30 ***
Aborted (core dumped)
On the positive side, it looks like MC can be installed without first installing any other dependencies (other than the ones installed when you install mediacenter20), which is great! :D
Think I've figured this one out. A new update will be posted today.
-
Specifically for the amd64 build, the unifonts are now required instead of recommended.
There are several fixes for the linux build in general that apply to the amd64 build. See the general linux MC posting for the changes.
-
In arch there are these problems:
libnettle.so.4 => not found
libhogweed.so.2 => not found
libgnutls-deb0.so.28 => not found
The last version of nettle in arch has libhogweed.so.4 and libnettle.so.6
The last version of gnutls in arch is libgnutls.so.30
I don't see an easy solution.
-
In arch there are these problems:
libnettle.so.4 => not found
libhogweed.so.2 => not found
libgnutls-deb0.so.28 => not found
The last version of nettle in arch has libhogweed.so.4 and libnettle.so.6
The last version of gnutls in arch is libgnutls.so.30
I don't see an easy solution.
Use the i386 Wheezy build instead.
-
Use the i386 Wheezy build instead.
That's basically where I am on Arch. The 32-bit build works great, I haven't gotten the 64-bit build running yet, primarily due to libgnutls.
-
In arch there are these problems:
libnettle.so.4 => not found
libhogweed.so.2 => not found
libgnutls-deb0.so.28 => not found
The last version of nettle in arch has libhogweed.so.4 and libnettle.so.6
The last version of gnutls in arch is libgnutls.so.30
I don't see an easy solution.
Like AD said, just use the 32 bit build. The reason for the AMD64 build is not because there's anything added by going to 64 bits, it's mainly because it reduces the packages you need to have when running on the supported (and very close) 64 bit distros.
-
The best distros for the AMD64 Jessie builds that I've found thus far is Debian Jessie and Ubuntu 15.04. With those two you just have to add the repository and install MC (and its dependencies automatically) from a Terminal and it works perfectly out-of-the-box. For everything else you'll probably have to use the i386 Wheezy build - especially Linux Mint 17.1 which is based on Ubuntu 14.04 LTS.
Speaking of Debian Jessie, do you think I should write a new tutorial for setting up MC in Debian Jessie?
-
Okay, here's an observation. I've noticed the default video directory for MC is ~/Video but instead it should be ~/Videos as it's the existing default videos directory on Debian, Ubuntu, etc.
-
Yes I am using the i386 version, see
https://aur.archlinux.org/packages/jriver-media-center/
But most people would like the amd64 version (not necessary to install all those lib32- libraries)
It would be nice to have this version on my AudioLinux distribution.
-
..
Speaking of Debian Jessie, do you think I should write a new tutorial for setting up MC in Debian Jessie?
That'd be great if you have the time.
-
Done and done. (http://yabb.jriver.com/interact/index.php?topic=97691.0) :)
-
Done and done. (http://yabb.jriver.com/interact/index.php?topic=97691.0) :)
Thanks!
BTW, I'm playing with a build that has statically linked libgnutls, libgcrypt, libidn, libgpg-error, libnettle and libhogweed.
It's a pita but it will probably make it easier to get the amd64 build running on ubuntu and others.
-
Excellent, how's it working?
-
Excellent, how's it working?
Works on 32 bit so far. Still in process on 64. If that goes I'll probably do arm as well.
-
The install of 20.0.110 for Debian (Jessie) AMD64 went very smoothly and it runs well, but I am having a problem getting the files to be played at the same volume. I've worked through the library tools, DSP studio, options, etc. Suggestions, please.
Thanks,
tlcmd
-
You could read about Audio Leveling on our wiki. The files must be analyzed first.
-
Assistance, please.
Can I now record with this version of Media Centre through my sound card (from my preamplifier. as I have with other versions of MC?
I have a fair number of vinyl records which I wish to transfer to my computer.
If not, can anyone suggest a good program to do this?
Thank you,
tlcmd
-
Assistance, please.
Can I now record with this version of Media Centre through my sound card (from my preamplifier. as I have with other versions of MC?
I have a fair number of vinyl records which I wish to transfer to my computer.
If not, can anyone suggest a good program to do this?
Thank you,
tlcmd
No, that function is not supported in Linux.
Audacity is a free and feature rich way to record on linux.
-
Audacity is a great option, it is what I have been using for years for my vinyl "rips". There are many tools built-in to help clean up your sources as well (pops, etc.)
-
Hovering over or clicking the DSP button to the right of the shuffle button doesn't do anything - the DSP/audio path window doesn't pop up at all.
-
Hovering over or clicking the DSP button to the right of the shuffle button doesn't do anything - the DSP/audio path window doesn't pop up at all.
Can you try a different skin?
Also, can you get at it from the Options menu?
-
Yep, it does it in Noire and others too. Yes, I can get it from the options menu without issue.
-
I am running 20.0.123 in both Ubuntu 15.04 and Mint 17 and after doing a re-install I discovered something that is not working the way that it did previously. In the standard view at the top of the main section (where the album art is displayed) there is a tab with the name of the view (Album, Artist, etc). Previously, if you right clicked on this tab you got a drop down menu with a number of options. That menu is no longer displayed when you right click, it now just says "Execute: (Name of view)". I did use that menu..
-
I am running 20.0.123 in both Ubuntu 15.04 and Mint 17 and after doing a re-install I discovered something that is not working the way that it did previously. In the standard view at the top of the main section (where the album art is displayed) there is a tab with the name of the view (Album, Artist, etc). Previously, if you right clicked on this tab you got a drop down menu with a number of options. That menu is no longer displayed when you right click, it now just says "Execute: (Name of view)". I did use that menu..
Ack.
It will be fixed in the next build Tuesday.
-
Use the i386 Wheezy build instead.
The current build just uploaded should have these incorporated IIRC.
-
Only one info:
I installed MC 20.0-129 in:
Debian Jessie (AMD 64)
Virtualox VMs (5.00):
Debian Stretch (AMD 64) KDE
Debian Stretch (AMD 64) Cinnamon
In all versions of MC runs great
Only the mini-view is not running for ages
-
Only one info:
I installed MC 20.0-129 in:
Debian Jessie (AMD 64)
Virtualox VMs (5.00):
Debian Stretch (AMD 64) KDE
Debian Stretch (AMD 64) Cinnamon
In all versions of MC runs great
Only the mini-view is not running for ages
Thanks.
I'm not seeing any trouble with the mini view.
Steps to reproduce your issue?
-
This build incorporates more libraries into MC to reduce dependencies when trying to get MC running on non-debian Jessie distros.
-
Hi Bob, the appearance is exact the same that I have described here.
http://yabb.jriver.com/interact/index.php?topic=94713.msg652567#msg652567 (http://yabb.jriver.com/interact/index.php?topic=94713.msg652567#msg652567)
nothing has changed so far.
-
Hi Bob, the appearance is exact the same that I have described here.
http://yabb.jriver.com/interact/index.php?topic=94713.msg652567#msg652567 (http://yabb.jriver.com/interact/index.php?topic=94713.msg652567#msg652567)
nothing has changed so far.
Exit MC.
Find your User Settings.ini file.
Make a backup of it.
Edit it
Find the line that starts:
Placement (Slim View)=b:....
Delete just that line.
Write it out.
Try MC again.
I can't reproduce this behavior since we "fixed" it.
-
What is that ?
I can open the file as read-only. Because the line length is more than 7000 characters ??. ? ?
Neither with Kate nor with kwrite. Even not as root
If the file is corrupt ??
-
I have a trick used: I have mounted the directory in a VM, and edit the file with gedit. [??]
The first time does the Mini-View well. The second time -----> the same as before.
The line is also again present:
Placement (Slim View) = b: "LAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAABjAAAAkQcAALwEAAA \ ="
-
I have a trick used: I have mounted the directory in a VM, and edit the file with gedit. [??]
The first time does the Mini-View well. The second time -----> the same as before.
The line is also again present:
Placement (Slim View) = b: "LAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAABjAAAAkQcAALwEAAA \ ="
That line is what you'd expect to see in the Settings file after you remove the line and re-run MC.
Still not sure why you are getting the distorted mini-view.
Are you using multiple monitors?
The default gnome desktop I assume?
-
another test:
I replaced the User Settings.ini with 704 KIB from KDE Jessie with the Cinnamon file (in VM) with 13 KIB (mini-view works in good cinnamon)
In KDE happened the same as before: In the first attempt mini-view works well. The second test gives the result as before
edit:
I use KDE
I have 1 Monitor with Dual-DVI (HP-LP3065) - see Signatur
mini and standard view have the same string?
Placement (Slim View)=b:"LAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAABjAAAAqQgAABwFAAA\="
Placement (Standard)=b:"LAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAABjAAAAqQgAABwFAAA\="
-
another test:
I replaced the User Settings.ini with 704 KIB from KDE Jessie with the Cinnamon file (in VM) with 13 KIB (mini-view works in good cinnamon)
In KDE happened the same as before: In the first attempt mini-view works well. The second test gives the result as before
edit:
I use KDE
I have 1 Monitor with Dual-DVI (HP-LP3065) - see Signatur
mini and standard view have the same string?
Placement (Slim View)=b:"LAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAABjAAAAqQgAABwFAAA\="
Placement (Standard)=b:"LAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAABjAAAAqQgAABwFAAA\="
Email me your settings file please
bob (at) jriver (dot) com
-
The latest build is up at:
http://files.jriver.com/mediacenter/channels/v20/latest/MediaCenter-20.0.129-amd64.deb (also in the latest apt repository)
20.0.131 (7/27/2015) ...
In case someone didn't notice this, the link is old. The correct link is of course:
http://files.jriver.com/mediacenter/channels/v20/latest/MediaCenter-20.0.131-amd64.deb
The apt repository is OK.
-
In case someone didn't notice this, the link is old. The correct link is of course:
http://files.jriver.com/mediacenter/channels/v20/latest/MediaCenter-20.0.131-amd64.deb
The apt repository is OK.
Fixed it, thanks.
-
Email me your settings file please
bob (at) jriver (dot) com
@ bob: did you get my mail?
-
@ bob: did you get my mail?
Yes.
The larger settings file has a lot of nulls in it following one of the custom view fields.
This seems like a bug but I don't think it's affecting the reading of the mini-view settings.
I'm in the middle of making a change to the redraw code. When the next build is posted it will be interesting to see if it solves the issue for you.
-
When the next build is posted it will be interesting to see if it solves the issue for you.
Fine - I hope it solves the Problem
-
I did a clean install of Ubuntu 15.04 x64 using my tutorial and man fonts are totally messed up by default - I made double sure xfonts-100dpi, xfonts-75dpi and unifont were all installed. And I rebooted several times.
-
I did a clean install of Ubuntu 15.04 x64 using my tutorial and man fonts are totally messed up by default - I made double sure xfonts-100dpi, xfonts-75dpi and unifont were all installed. And I rebooted several times.
What are your font settings in MC?
-
The default, changing to unifont or user defined doesn't make a difference.
-
The default, changing to unifont or user defined doesn't make a difference.
I'd guess the fonts have changed or are missing.
Try xlsfonts from a terminal
xlsfonts
The actual font string being used is detailed here:
http://yabb.jriver.com/interact/index.php?topic=96778.msg667657#msg667657
-
Here's the output;
-bitstream-bitstream charter-bold-i-normal--0-0-0-0-p-0-adobe-standard
-bitstream-bitstream charter-bold-i-normal--0-0-0-0-p-0-ascii-0
-bitstream-bitstream charter-bold-i-normal--0-0-0-0-p-0-iso10646-1
-bitstream-bitstream charter-bold-i-normal--0-0-0-0-p-0-iso8859-1
-bitstream-bitstream charter-bold-r-normal--0-0-0-0-p-0-adobe-standard
-bitstream-bitstream charter-bold-r-normal--0-0-0-0-p-0-ascii-0
-bitstream-bitstream charter-bold-r-normal--0-0-0-0-p-0-iso10646-1
-bitstream-bitstream charter-bold-r-normal--0-0-0-0-p-0-iso8859-1
-bitstream-bitstream charter-medium-i-normal--0-0-0-0-p-0-adobe-standard
-bitstream-bitstream charter-medium-i-normal--0-0-0-0-p-0-ascii-0
-bitstream-bitstream charter-medium-i-normal--0-0-0-0-p-0-iso10646-1
-bitstream-bitstream charter-medium-i-normal--0-0-0-0-p-0-iso8859-1
-bitstream-bitstream charter-medium-r-normal--0-0-0-0-p-0-adobe-standard
-bitstream-bitstream charter-medium-r-normal--0-0-0-0-p-0-ascii-0
-bitstream-bitstream charter-medium-r-normal--0-0-0-0-p-0-iso10646-1
-bitstream-bitstream charter-medium-r-normal--0-0-0-0-p-0-iso8859-1
-bitstream-courier 10 pitch-bold-i-normal--0-0-0-0-m-0-adobe-standard
-bitstream-courier 10 pitch-bold-i-normal--0-0-0-0-m-0-ascii-0
-bitstream-courier 10 pitch-bold-i-normal--0-0-0-0-m-0-iso10646-1
-bitstream-courier 10 pitch-bold-i-normal--0-0-0-0-m-0-iso8859-1
-bitstream-courier 10 pitch-bold-r-normal--0-0-0-0-m-0-adobe-standard
-bitstream-courier 10 pitch-bold-r-normal--0-0-0-0-m-0-ascii-0
-bitstream-courier 10 pitch-bold-r-normal--0-0-0-0-m-0-iso10646-1
-bitstream-courier 10 pitch-bold-r-normal--0-0-0-0-m-0-iso8859-1
-bitstream-courier 10 pitch-medium-i-normal--0-0-0-0-m-0-adobe-standard
-bitstream-courier 10 pitch-medium-i-normal--0-0-0-0-m-0-ascii-0
-bitstream-courier 10 pitch-medium-i-normal--0-0-0-0-m-0-iso10646-1
-bitstream-courier 10 pitch-medium-i-normal--0-0-0-0-m-0-iso8859-1
-bitstream-courier 10 pitch-medium-r-normal--0-0-0-0-m-0-adobe-standard
-bitstream-courier 10 pitch-medium-r-normal--0-0-0-0-m-0-ascii-0
-bitstream-courier 10 pitch-medium-r-normal--0-0-0-0-m-0-iso10646-1
-bitstream-courier 10 pitch-medium-r-normal--0-0-0-0-m-0-iso8859-1
-misc-fixed-medium-r-semicondensed--0-0-75-75-c-0-iso8859-1
-misc-fixed-medium-r-semicondensed--13-100-100-100-c-60-iso8859-1
-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1
-urw-standard symbols l-medium-r-normal--0-0-0-0-p-0-adobe-symbol
-urw-standard symbols l-medium-r-normal--0-0-0-0-p-0-iso10646-1
6x13
cursor
fixed
I don't see lucida or unifont listed, though they are installed.
-
Weird, updating Mesa using the Oibaf PPA fixed it after a reboot. The fonts are now listed in xlsfonts.
-
Weird, updating Mesa using the Oibaf PPA fixed it after a reboot. The fonts are now listed in xlsfonts.
Good find, though I don't know how that worked...
-
Yeah, I think it might be time for me to do some virtual machine testing...
-
Couldn't reproduce it in a virtual machine but I did notice something else that's strange on the main Ubuntu install. Without the updated Mesa (and the fonts were messed up) the issue with the "dead pixels" appearing in MC didn't occur, however after updating Mesa and getting the fonts to work the "dead pixels" issue is there. Maybe the issue with the "dead pixel" looking glitches is related to the fonts in some way?
Very strange.
-
Even more interesting, after purging the PPA and going back to stock Mesa MC's fonts work fine now. Maybe it's something only a clean MC install would fix? Very strange indeed and I might not be the only person who experienced this.
-
Even more interesting, after purging the PPA and going back to stock Mesa MC's fonts work fine now. Maybe it's something only a clean MC install would fix? Very strange indeed and I might not be the only person who experienced this.
I don't really understand how a clean install of MC would fix it.
Maybe just select a different font then back to the default?
There does seem to be some magic however in how the xfonts-75dpi are integrated into a running system.