INTERACT FORUM
More => Old Versions => JRiver Media Center 21 for Linux => Topic started by: bob on August 07, 2015, 04:15:39 pm
-
The latest build is up at:
https://files.jriver.com/mediacenter/channels/v21/latest/MediaCenter-21.0.90-amd64.deb (also in the latest apt repository)
See the linux x86 log for specific linux changes and the windows log for general MC changes.
Only changes that apply specifically to the amd64 build will be posted here.
21.0.90 (7/14/2016)
See the main linux changelog
21.0.88 (6/10/2016)
See the main linux changelog
21.0.85 (5/27/2016)
See the main linux changelog
21.0.83 (5/20/2016)
1. Fixed: Linux detect cifs filesystems for timer supported auto imports
21.0.76 (4/29/2016)
See the main linux changelog
21.0.76 (4/12/2016)
See the main linux changelog.
21.0.63 (3/21/2016)
See the main linux changelog
21.0.61 (3/18/2016)
See the main linux changelog
21.0.54 (3/4/2016)
Changes from the main branch. Should be considered for stable repo but is in latest for now.
21.0.51 (2/26/2016)
See the main changelog for linux in this forum. More work on eliminating hard killed threads. Needs testing for stability.
21.0.48-3 (2/16/2016)
1. Changed: Recompiled eveything with GCC/G++ 4.8 to help with portability on non-debian systems that didn't support libstdc++-4.9
2. Fixed: libJRReader wasn't being properly loaded/unloaded. Could have caused instability in that code.
21.0.48 (2/15/2016)
See the main linux changelog
21.0.39 (1/25/2016)
See the main linux changelog.
21.0.37 (1/15/2016)
Changes from the main branch
21.0.34 (1/8/2016)
1. Fixed: Poor image creation performance on amd64 platforms.
2. Fixed: Options window size and placement troubles that showed up on some systems.
21.0.28 (12/17/2015)
1. Fixed socket hangs/leaks/crashes.
21.0.23 (11/23/2015)
1. Fixed: Memory leak.
21.0.16 (10/16/2015)
21.0.7 (9/15/2015)
21.0.6 (9/4/2015)
21.0.5-1 (9/1/2015)
21.0.5 (8/28/2015)
1. NEW: mimetype association for the .mjr file. This means you can click on an .mjr file in the linux file browser to install a license and it should work through a browser form the restore page as well. Works silently, needs testing.
2. Fixed: Problems with premature timeout of trialware.
3. Fixed: Library paths for the gnutls support libs under the Media Center library directory.
-
Is the apt repository using the same mediacenter20 link or will it change for MC21? I'll post the tutorials updated for MC 21 over the weekend!
EDIT: Derp, access denied error!
-
Yup, getting an access denied error. Can't wait to try this out.
-
Tomorrow will be the last day of the special price. Thanks for the great response!
[Edit July 31 -- Upgrades are now $22.98 for Mac or Windows, $26.98 for a Master License.]
This will be our best month ever, and not by a little. This year's upgrade response will beat our old monthly record by about 30%.
These big bursts of business give us tremendous financial ability to continue to try to do our best for you. We don't always succeed, but we do always try, and we do sincerely enjoy your encouragement. Thank you.
Is there already a possibility to buy a license for MC 21 for linux?
-
Help! I'm getting the notice below:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>B248011287E73E63</RequestId><HostId>6CncfbPcPzhAjg0OYtbr112/6kdGTVrpAkzk/g+Y5qL5Xa55bQ2cDxdMy4m1XDyrjRSeu1pZT+M=</HostId></Error>
Thanks,
tlcmd (have the Linux MC20 license)
-
Fixed now. Sorry.
-
Check out the new fonts!
-
Hey bob, might it be better to just combine the two build threads? The changelog could denote 64-bit specific changes. It's just one less place we've got to check for new bugs/discussion since most of the x64 specific issues have been ironed out.
-
I fixed the apt-repo and updated to 21.0.3 MC.
Super --- I can select dozens of fonts - and it works! Thanks a lot for this feature! :) :)
But the window with the best new features is the only one that does not have focus. If you click on "Select fonts", it remains only in the taskbar
Now I have again a 30-day trial-period. Version 21.0.2 did not start, because the trial period stood at 0 days
I ask again: When can I buy an update license for MC21 ???
Is the License for MC 20 also valid for MC21?
-
I fixed the apt-repo and updated to 21.0.3 MC.
Super --- I can select dozens of fonts - and it works! Thanks a lot for this feature! :) :)
But the window with the best new features is the only one that does not have focus. If you click on "Select fonts", it remains only in the taskbar
Now I have again a 30-day trial-period. Version 21.0.2 did not start, because the trial period stood at 0 days
I ask again: When can I buy an update license for MC21 ???
Is the License for MC 20 also valid for MC21?
Normally you install a version 20 license code into version 21 then do "Buy Media Center" from the help menu which would get you the reduced price.
We have discovered that's not working right now and we are checking into it...
-
I installed MC in multiple VMs. On my main system (KDE Jessie) is running MC 20 + 21
When updating MC 21.0.2. to 21.0.3 I got a 30-day trial. I could start MC 21.0.2 once only.
In Cinnamon and Gnome (Stretch) I could start 21.0.3 once only to .
Trying - as you described - the Version 20 license-code entering in MC 21, failed -
but now I got since yesterday from you 4 mjr - files for MC 20, and have only one chance to make a restore . :-[ :-[
--- not so good.
-
I installed MC in multiple VMs. On my main system (KDE Jessie) is running MC 20 + 21
When updating MC 21.0.2. to 21.0.3 I got a 30-day trial. I could start MC 21.0.2 once only.
In Cinnamon and Gnome (Stretch) I could start 21.0.3 once only to .
Trying - as you described - the Version 20 license-code entering in MC 21, failed -
but now I got since yesterday from you 4 mjr - files for MC 20, and have only one chance to make a restore . :-[ :-[
--- not so good.
I reset your restores so that shouldn't be an issue for now.
I see where the upgrade is failing. Matt and I are working on it.. It will be done before the 30 days runs out!
-
Hey bob, might it be better to just combine the two build threads? The changelog could denote 64-bit specific changes. It's just one less place we've got to check for new bugs/discussion since most of the x64 specific issues have been ironed out.
I think that would be OK but we don't always build them together, for example I had an issue specific to the arm build and just got it resolved today so it's lagging behind the others...
-
Thank you Bob, but I think I'll run together for safety MC 20 and MC 21, until the issues are resolved.
-
Thank you Bob, but I think I'll run together for safety MC 20 and MC 21, until the issues are resolved.
It's totally fine to run them both on the same machine.
-
The log reading function will only work with a newer version of xdg-open that got the latest bug fixes.
It doesn't work right in wheezy or jessie but does on ubuntu vivid.
-
1 question, please about MC21.0.4 for linux. I've just downloaded and installed it, but it is not registered as MC20 is.
I cannot use my MC 20 install key or my MC20 buy button because I get the message that it has been used too many times. What do I do?
Thank you,
tlcmd
-
1 question, please about MC21.0.4 for linux. I've just downloaded and installed it, but it is not registered as MC20 is.
I cannot use my MC 20 install key or my MC20 buy button because I get the message that it has been used too many times. What do I do?
Thank you,
tlcmd
I reset your restores, try again...
-
Bob, I saw you mention that MC doesn't do any file associations on Linux but perhaps this should be changed where MC has a file association for .mjr license files so it could be a little easier to get the license working (for those users having issues)?
I remember looking at the documentation for this, I'll see if I can dig it up if you're interested (or need it).
-
Bob, I saw you mention that MC doesn't do any file associations on Linux but perhaps this should be changed where MC has a file association for .mjr license files so it could be a little easier to get the license working (for those users having issues)?
I remember looking at the documentation for this, I'll see if I can dig it up if you're interested (or need it).
Sure that'd be great. It should make the association for .mjr at least upon installation of the .dpkg.
-
Sure that'd be great. It should make the association for .mjr at least upon installation of the .dpkg.
Here's some stuff for Debian: https://wiki.debian.org/MimeTypesSupport
I'll hunt down the stuff I was looking at before.
http://www.freedesktop.org/wiki/Specifications/AddingMIMETutor/
http://www.freedesktop.org/wiki/Specifications/mime-apps-spec/
http://standards.freedesktop.org/shared-mime-info-spec/shared-mime-info-spec-latest.html
-
Good day, I've been using 21.0.4 on Jessie 64 for a few days now and it's been working well.
A few observations:
1) Issues with window resizing: When switching from 'mini view' to 'standard view' when the standard view is not maximized, the mouse pointer does not change for resizing the window except on the left edge in the upper left corner. If the window is resized horizontally using that, a black box expands, but the window does not redraw to fill the space.
2) Since this upgrade to v21 I notice that when in 'mini view' using the Noire theme, that the play button can extend slightly outside the top of the window boundary. I noticed that 'mini view' in v21 is 3-5 pixels smaller in the vertical dimension.
3) Hovering over the rewind/play/pause/stop/ffwd buttons in 'mini view' leaves the buttons in various states of highlighting. This does not seem to be an issue in standard view.
Thanks!
EDIT: added #3
-
The registration association could use some testing under different desktops and the library fixes on non-debian distros.
i386 and arm builds coming soon.
-
Works good here on Ubuntu 15.04 x64. Good work Bob! :D
-
The registration association could use some testing under different desktops and the library fixes on non-debian distros.
The new mime type worked fine on Debian Jessie 64.
Mediacenter was not running. I downloaded the mjr file to ~/Downloads
double-clicking the mjr icon did not *appear* to do anything, but evidently it silently ran the registration. Although this is certainly superior to having to do the registration from the command line, I think would be better if MediaCenter actually launched if it's not already running and display a message that the registration was accepted.
Thanks for the continuous improvement to MediaCenter!!
-
I just purchased a license for Linux MC21.0.5, but was not offered the option of purchasing a MASTER LICENSE. How may I now purchase a MASTER LICENSE for the difference between the cost of the MC21 license and the reduced cost of the MASTER LICENSE??
Thanks,
tlcmd
-
I just purchased a license for Linux MC21.0.5, but was not offered the option of purchasing a MASTER LICENSE. How may I now purchase a MASTER LICENSE for the difference between the cost of the MC21 license and the reduced cost of the MASTER LICENSE??
Thanks,
tlcmd
The Master License upgrade direct link is here: http://jriver.com/purchase_21_master_as_upgrade.html
-
Why can I not simply pay the difference between the MC21 Linux license and the Master License rather than having to pay the price for both since the Master License also includes the MC21 License for Linux?
-
Why can I not simply pay the difference between the MC21 Linux license and the Master License rather than having to pay the price for both since the Master License also includes the MC21 License for Linux?
Was your errant purchase a result of this?: http://yabb.jriver.com/interact/index.php?topic=99696.msg690953#msg690953
If so, you might want to bring it to Jim's attention in this thread: http://yabb.jriver.com/interact/index.php?topic=98538.150
-
In a word, YES.
-
The libX11 segfault still exists - it's still easily reproducible.
http://yabb.jriver.com/interact/index.php?topic=96854.msg668859#msg668859
Should I start a new topic on this?
-
Also the issue still exists where library backups dates are set ahead to the next date at 6PM every day. The date change is 6 hours too fast. Try it at 6PM your local time (which is Central US for me).
-
And when manually saving a library backup (and one exists already for that day) there's no prompt to override the file like there is in Windows and Mac.
-
Thanks for the last 3 posts AD. We'll check into the segfault and date issue. I wasn't able to reproduce the date issue in the past but it does sound suspiciously like a timezone issue. I think 2 and 3 may be related.
-
No problem. :)
After thinking about it some more, perhaps the third issue with the override prompt is more of an issue with with the file browser, e.g. Nautilus in this case than MC? Not sure.
-
Added a graphical feedback to license install.
Important fixes from the main stream.
-
Awesome work. BTW, you should be able to easily reproduce the library backup date issue right now.
-
The libX11 segfault still exists - it's still easily reproducible.
http://yabb.jriver.com/interact/index.php?topic=96854.msg668859#msg668859
Should I start a new topic on this?
I can easily reproduce this as well but it crashes in the debugger without leaving a stack trace behind. I'm assuming it's related to the display window not going away.
-
It's fixed.
Also skins are now easy to install/manage - I'll add that to the tutorial later this weekend! :)
-
Changes listed here http://yabb.jriver.com/interact/index.php?topic=100183.0
-
nowadays I checked for a long time where MC stores its files. I found strange things:
In /usr/lib/JRiver/ there are two identical directories (see picture)
The program file is not in this directory, only a link to /usr/bin/ mediacenter21. There, the program is with 18.3 MiB.
I think, in Linux makes everyone what he wants now. I just installed SparkyLinux, and find a wallpaper folder in / opt / ??
To my knowledge, programs must be installed to / opt /, which are not provided by the distribution. See here (http://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s13.html).
I have all additional programs which are not come from the Debian repos installed in /opt/. I also have such a good overview of additional programs
If I'm doing a new installation I just need to copy the /opt/ directory to the new installation, copy the ~/home/ - directories of the program. I then make a entry in the start menu - that's all.
What is the reason why not JRiver makes this so?
Good news:
MC is working well now in Debian Stretch (KDE) (since the updates in the last week)
MC is also working well in SparkyLinux (LXQT and XFCE) - SparkyLinux is Debian-Stretch based
A question about the Skins:
Earlier you could download Skins as *.zip files. The files could be extracted and copied in the skin directory.
Now these are little *.mjp - files. What to do with these files?
-
What is the reason why not JRiver makes this so?
MC is installed using the normal package manager, on Debian and Ubuntu at least, and as such there is no reason to move to /opt/, IMHO. We even provide a repository for automatic updating and everything.
Why you have a MC21 dir next to Media Center 21 I cannot tell you. MC does not use that. But considering both contain the exact same files, maybe MC21 is a symlink?
-
Why you have a MC21 dir next to Media Center 21 I cannot tell you. MC does not use that. But considering both contain the exact same files, maybe MC21 is a symlink?
I have now examined: It is indeed a symlink. I have the symlink now renamed. MC starts as before.
I'll wait a while and then delete it
In this installation (SparkyLinux XFCE based on Debian Stretch), I never installed MC by hand. I have added the repo of JRiver right after installation. From there I have MC installed.
The updates were always done only with the normal dist-upgrade. Last yesterday to version 21.0.7.
This symlink can therefore only come from JRiver
-
It appears Bob added the symlink to the .deb recently. I guess its easier to access without the spaces. I would just leave it in place, its not like it harms anyone in the JRiver directory there.
-
It does not hurt - but it's confusing. It would be good if the directory /usr/lib/JRiver/Media Center 21/ would then at some point disappear.
That's what I meant by: I think, in Linux makes everyone what he wants now.
MC is installed using the normal package manager, on Debian and Ubuntu at least, and as such there is no reason to move to /opt/, IMHO.
However, there are examples where the normal installer installs the program files - in my opinion - correct to the / opt / directory.
One example is OpenOffice
-
It does not hurt - but it's confusing. It would be good if the directory /usr/lib/JRiver/Media Center 21/ would then at some point disappear.
That's what I meant by: I think, in Linux makes everyone what he wants now.
However, there are examples where the normal installer installs the program files - in my opinion - correct to the / opt / directory.
One example is OpenOffice
/opt has been the "standardized" location for installation of third party apps since at least System V unix.
It's also basically been ignored for that long as well.
Since we are installing as a package with our own repository as Hendrik said I see no issues with installing to /usr/lib/jriver
The MC21 symlink to the Media Center 21 directory is deliberate and was needed to get some of the libraries in /usr/lib/jriver/Media Center 21 to link to other libraries in /usr/lib/jriver/Media Center 21 properly because of shortcomings with spaces in pathnames in the build system. You should leave that in place as well as anything that's part of the MC .deb package.
-
Hi Bob,
I installed MC21.0.7 and bought the master license. But I can' install the license: it says:
CRegistrationHelper::GetLicenseFileFromRegistrationCode: error = There was a problem communicating with the license server.
ot I tried the other way by importing the .mjr file. It still says, there is no license and 29 days left.
-
Hi Bob,
I installed MC21.0.7 and bought the master license. But I can' install the license: it says:
CRegistrationHelper::GetLicenseFileFromRegistrationCode: error = There was a problem communicating with the license server.
ot I tried the other way by importing the .mjr file. It still says, there is no license and 29 days left.
If you are internet connected on your linux box the error likely comes from not using debian and the root certificate store being somewhere other than the standard debian place.
From the command line, try the .mjr without the switch.
i.e.
mediacenter21 "whatever your mjr file name is.mjr" and see if you get a success popup box.
Remember .mjr's are only good for 14 days. Request another if yours is older.
-
If you are internet connected on your linux box the error likely comes from not using debian and the root certificate store being somewhere other than the standard debian place.
From the command line, try the .mjr without the switch.
i.e.
mediacenter21 "whatever your mjr file name is.mjr" and see if you get a success popup box.
Remember .mjr's are only good for 14 days. Request another if yours is older.
Thanks Bob,
I tried the commandline and it works fine. :D
-
This is the first 64-bit release I try.
When I click anywhere in the dark area on top (around the current file/slider/search box), MediaCenter responds as if I clicked the Max/Restore button.
I think in one of the recent 32-bit release this was (accidently?) solved, unless it was reintroduced?
I realize this may not be high prio, but it is kind of annoying and it's been there from the start ;).
-
This is the first 64-bit release I try.
When I click anywhere in the dark area on top (around the current file/slider/search box), MediaCenter responds as if I clicked the Max/Restore button.
I think in one of the recent 32-bit release this was (accidently?) solved, unless it was reintroduced?
I realize this may not be high prio, but it is kind of annoying and it's been there from the start ;).
Sorry I tried this on both 32 and 64 bit debian without being able to reproduce it.
-
Sorry I tried this on both 32 and 64 bit debian without being able to reproduce it.
Weird. Maybe it depends on distro/window manager.
I'm on Arch Linux 64-bit with XFCE4. I thought I read a few others mention this issue but I don't remember which distro/WM they were running.
-
Hi,
Just updated to all my systems to MC21, and can confirm the windows buttons are working with Fluxbox as Window Manager (Debian & Arch).
If the /mediaserver switch is used there is some strange behavior: the maximize button must be clicked twice;
What puzzles me are the different looks of the buttons on AMD64 vs ARM using the Noire Skin.
On Arm you get tidy looking windows 10 style buttons on AMD64 not.
It isn't the skin it self, i copied it form ARM to AMD64 after renaming it with no result.
-
This is the first 64-bit release I try.
When I click anywhere in the dark area on top (around the current file/slider/search box), MediaCenter responds as if I clicked the Max/Restore button.
I think in one of the recent 32-bit release this was (accidently?) solved, unless it was reintroduced?
I realize this may not be high prio, but it is kind of annoying and it's been there from the start ;).
Weird. Maybe it depends on distro/window manager.
I'm on Arch Linux 64-bit with XFCE4. I thought I read a few others mention this issue but I don't remember which distro/WM they were running.
Seen this on a arm-board with XFCE4/Debian-Jessie
-
HI Bob,
I'm running MC now for a few days non stop and it ends up to eat up my memory. I was wondering, why the playback was stalling, when I worked with my computer.
I checked my resources and found that mc uses a little as 12Gb of memory. (see attached images)
After restarting MC, the memory starts reasonable, but if seems like every new song played increments the used memory by some hundreds of kilobytes.
It looks like every time a new song starts, a new buffer is used, but not flushed after playback stops.
-
HI Bob,
I'm running MC now for a few days non stop and it ends up to eat up my memory. I was wondering, why the playback was stalling, when I worked with my computer.
I checked my resources and found that mc uses a little as 12Gb of memory. (see attached images)
After restarting MC, the memory starts reasonable, but if seems like every new song played increments the used memory by some hundreds of kilobytes.
It looks like every time a new song starts, a new buffer is used, but not flushed after playback stops.
Hi Bob,
here some detailed information about memory usage.
-
Hi,
Just updated to all my systems to MC21, and can confirm the windows buttons are working with Fluxbox as Window Manager (Debian & Arch).
If the /mediaserver switch is used there is some strange behavior: the maximize button must be clicked twice;
What puzzles me are the different looks of the buttons on AMD64 vs ARM using the Noire Skin.
On Arm you get tidy looking windows 10 style buttons on AMD64 not.
It isn't the skin it self, i copied it form ARM to AMD64 after renaming it with no result.
The top level window buttons are provided by the Window Manager.
-
Hi Bob,
here some detailed information about memory usage.
It could be a memory leak triggered by a misbehaving DLNA device or some issue with thumbnailing or the audio analyzer. It could also be an issue with somewhat incompatible libraries on a non-debian system.
Can you try with Media Network disabled and see if that makes a difference?
-
It could be a memory leak triggered by a misbehaving DLNA device or some issue with thumbnailing or the audio analyzer. It could also be an issue with somewhat incompatible libraries on a non-debian system.
Can you try with Media Network disabled and see if that makes a difference?
I disabled the server, but it still counting up. The heap gained 108Mb within 17min.
-
I disabled the server, but it still counting up. The heap gained 108Mb within 17min.
Ok, thanks.
Hoping it's not an incompatible library.
Another possibility I though about would be a audio driver bug.
You could try a simpler device like onboard audio if you aren't already.
Also perhaps a certain input plugin has a leak. What filetypes are you playing?
-
I disabled the server, but it still counting up. The heap gained 108Mb within 17min.
Would you try turning off the spectrum analyzer (right click on it) and see if that changes anything?
-
The top level window buttons are provided by the Window Manager.
But this is the (undecorated) main window...
-
Would you try turning off the spectrum analyzer (right click on it) and see if that changes anything?
I turned off the spectrum analyzer and it seems to low down using memory. I run the system now for more than 24h and it build up to 771Mb, far less than before, but still counting up.
The heap increases when you start a new song, sometime more, sometimes less.
-
This is the first 64-bit release I try.
When I click anywhere in the dark area on top (around the current file/slider/search box), MediaCenter responds as if I clicked the Max/Restore button.
I think in one of the recent 32-bit release this was (accidently?) solved, unless it was reintroduced?
I realize this may not be high prio, but it is kind of annoying and it's been there from the start ;).
I tried the 64 bit version on ubuntu 15.10 and I can't get this to happen.
-
But this is the (undecorated) main window...
You're right of course, I don't see how it can be different though unless the wm is mucking with it. It's totally different on my RPI than it is on my debian box.
-
I upgraded from 21.0.7 64-bit. It was pretty stable, rarely crashed and would generally close when I clicked close.
This version often randomly crashes. It no longer closes when I click close. Music will continue to play until the song is done, but the screen doesn't update and when I minimize/maximize it, it will stay white. I need to kill it from the terminal.
The only notable change I made is I installed and configured Pulseaudio. I had to because Spotify >=1.0 requires it. I removed Pulse to test but it doesn't matter for MC.
I can configure MC to output to Pulse or directly to an ALSA device but it makes no difference.
Is anyone else seeing a regression with this version? I can supply logs or more info, just ask what you need.
I am on Arch Linux, XFCE4, 64-bit.
Thanks!
-
I upgraded from 21.0.7 64-bit. It was pretty stable, rarely crashed and would generally close when I clicked close.
This version often randomly crashes. It no longer closes when I click close. Music will continue to play until the song is done, but the screen doesn't update and when I minimize/maximize it, it will stay white. I need to kill it from the terminal.
The only notable change I made is I installed and configured Pulseaudio. I had to because Spotify >=1.0 requires it. I removed Pulse to test but it doesn't matter for MC.
I can configure MC to output to Pulse or directly to an ALSA device but it makes no difference.
Is anyone else seeing a regression with this version? I can supply logs or more info, just ask what you need.
I am on Arch Linux, XFCE4, 64-bit.
Thanks!
I see something similar. If I've been listening for a while, closing MC will just cause the window to freeze until I kill it from the terminal (I left it for an hour or so to see if it would eventually close, but no dice). It doesn't exhibit the behavior if I just open MC and close it again, I need to have been playing something for a while. I too had no issues with 21.0.07.
No crashes to speak of, but all versions after 21.0.07 have a memory leak for me, so if you listen for very long it may eventually crash due to the leak. I just have 16GB of system memory so I don't hit the OOM state very often. Bob says he can see the memory leak in 21.0.07, but I can't reproduce it on Arch on two different machines, so I'd advise folks running the 64-bit version on Arch to roll back to 21.0.07 until the leak gets fixed.
-
Could it be related?
http://yabb.jriver.com/interact/index.php?topic=100628.0
-
Bug in MCWS?
I'm issuing:
(mcwsBase::exec(const QUrl&, bool)::<lambda:86) - "Error downloading http://localhost:52199/MCWS/v1/Library/GetStats - server replied: Internal server error"
and getting back:
<Response Status="Failure">
<Item Name="Files">27126</Item>
<Item Name="Artists">638</Item>
<Item Name="Albums">1826</Item>
</Response>
Just noticed it because I added some extra error detection to my networkReply....
Happening at least back to .7
fwiw, I'm on .17
-
Bug in MCWS?
I'm issuing:
(mcwsBase::exec(const QUrl&, bool)::<lambda:86) - "Error downloading http://localhost:52199/MCWS/v1/Library/GetStats - server replied: Internal server error"
and getting back:
<Response Status="Failure">
<Item Name="Files">27126</Item>
<Item Name="Artists">638</Item>
<Item Name="Albums">1826</Item>
</Response>
Just noticed it because I added some extra error detection to my networkReply....
Happening at least back to .7
fwiw, I'm on .17
Looks like it returns the proper information but indicates failure, correct?
-
Looks like it returns the proper information but indicates failure, correct?
Yep, I'd say so. Also, along with the "failure" status, it appears to be returning internal server error (401), at least that's what's bubbling up to my app through the QT plumbing.
-
We'll try to get the error calling:
http://localhost:52199/MCWS/v1/Library/GetStats
Fixed in one of the next coming builds. Thanks for letting us know.
-
Just to follow up, the error will be fixed next build. Thanks again for letting us know.
-
After my recent upgrade of MC21 to 21.0.16, my smartlists disappeared. I am running Linux Mint Debian Edition. Is anyone else having this problem, and is there a solution to it in installing future upgrades?
Thanks.
tlcmd
-
The memory leak that was affecting the amd64 build especially bad should be fixed now. It's working properly on my build machine and the 2 test bottles I've tried so far.
-
Fired up the VM with JRiver AMD64 for testing.
Report back, if there is something specific you'd like to test let me (us) know.
for reference the graph of a MC21-16 AMD 64 test.
teaser update: looks good after 1h playing!
-
Fired up the VM with JRiver AMD64 for testing.
Report back, if there is something specific you'd like to test let me (us) know.
for reference the graph of a MC21-16 AMD 64 test.
teaser update: looks good after 1h playing!
Thanks!
I got it to happen most egregiously when MC was displaying a list view and cycling through a long playlist of short files so there were lots of window updates in MC.
-
New build also seems more snappy to me, especially when opening and closing.
Glad the memory leak is sorted. :)
-
the leak is fixed!
It's playing for several hours, in diverend views (about the same as the MC21-16 test before) without a growing mem footprint.
(ditto for MC-arm version, that's fixed too!)
-
the leak is fixed!
It's playing for several hours, in diverend views (about the same as the MC21-16 test before) without a growing mem footprint.
(ditto for MC-arm version, that's fixed too!)
Thanks for testing it!
-
Hi Bob,
I'm playing it for 2 days now, without any problems. Memory usage is bouncing around between 150 to 260 MB. No more leak.
-
Hi Bob,
I'm playing it for 2 days now, without any problems. Memory usage is bouncing around between 150 to 260 MB. No more leak.
Great, thanks for reporting.
My test X86_64 box has been running for 6 days with no increase in memory footprint as well.
-
21.0.28 Should fix the crashes caused by bugs in the socket code. Feedback requested.
-
Hi
I'm running SUSE Leap 42.1 with the Plasma 5 desktop for testing purpose and run into a strange bug. Since Plasma 5 is buggy, I don't know, if it is a plasma- or MC bug. When I try to save any file during playback, it's not possible until I stop it. It seems like MC is locking the entire home drive. I can read, but I can't write. Is any one else have this problem using Leaf? When I boot into SUSE 13.2 and KDE, everything runs fine (my home drive is nfs based and used by both OS.) Only MC shows this problem and I tried x.16, x.23 and x.28.
-
21.0.28 Should fix the crashes caused by bugs in the socket code. Feedback requested.
Hi Bob,
Thanks and Merry Christmas.
I am on Debian 8.2 3.16.0-4-amd64 and upgraded to 21.0.28
I am not sure if it is the new version or installing libgl1-nvidia-glx:i386 (I had just installed the i386 drivers when the upgrade came through) but it is markedly more stable it has been running for more than 24 hours without issue. I will pull the i386 drivers off and report back in a few days.
Nick
-
21.0.28 Should fix the crashes caused by bugs in the socket code. Feedback requested.
I have removed the :i386 drivers and architecture and 21.0.28 remains solid as a rock ;D
Thanks Bob
Nick
-
Thanks for the report!
-
Some fixes for speed and window placement issues. See the first post.
-
I believe it is only since the version MC 21 034: Using the Skins Black on Black and Purity tooltips are no longer readable. The font is too bright (standard settings - no effects) I have no setting found to make the font in the tooltips darker.
-
Anyone running Ubuntu 14.04.x LTS or Linux Mint 17.x needs to update their GCC libs or else Media Center won't function correctly. You can do so by opening a Terminal and running the following commands;
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
If you're running Ubuntu 15.10 this is a non-issue - Media Center will function correctly.
-
Anyone running Ubuntu 14.04.x LTS or Linux Mint 17.x needs to update their GCC libs or else Media Center won't function correctly. You can do so by opening a Terminal and running the following commands;
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
If you're running Ubuntu 15.10 this is a non-issue - Media Center will function correctly.
Thanks for the info.
-
This update seemed to have broke my media center 21 on ubuntu 14.04. Try to start the app, but it never comes up. Please advise.
-
Read two posts above yours for the solution.
-
Just saw the fix. Many thanks. Need to understand how to navigate this forum better. 8)
-
Desktop integration changes and removing the lame dependency are in this build.
-
Nice!
Fixed: Bug in calculating the offset from UTC.
Does this fix the issue where time was ahead by 6 hours when saving library backups?
-
Nice!
Does this fix the issue where time was ahead by 6 hours when saving library backups?
That would be my guess. Give it a try!
-
That would be my guess. Give it a try!
Confirmed, fixed. Thanks Bob! :)
-
Hi Bob,
I have upgraded to 21.0.39 and it is crashing for me. How can I help troubleshoot, what do you need?.
Kind regards,
Nick
-
If you want to follow the linux build changes a bit less on the leading edge, try the stable dist.
Using Awesome Donkeys tutorial, just substitute the word stable where you see latest.
Currently all builds in stable are 21.0.34
Hi Bob I just saw this, will go .34 and see how it goes for me. Let me know if you want any into re .39
Cheers, Nick
-
Run MC from the Terminal and post the error here. If you're using Ubuntu 14.04 LTS, Linux Mint or Elementary OS you may need to use the fix above.
-
Hi Bob,
I have upgraded to 21.0.39 and it is crashing for me. How can I help troubleshoot, what do you need?.
Kind regards,
Nick
Please state what distro you are running on if it's not Debian Jessie.
There are issues with older versions of ubuntu (non-Debian distros are user supported).
-
Run MC from the Terminal and post the error here. If you're using Ubuntu 14.04 LTS, Linux Mint or Elementary OS you may need to use the fix above.
Thanks Awesome Donkey great idea, I will do that good call.
I am running vanilla Debian so don't think I need the fix.
Please state what distro you are running on if it's not Debian Jessie.
There are issues with older versions of ubuntu (non-Debian distros are user supported).
Hi Bob,
Thanks for the response.
No it is Debian Jessie not something else.
In better news I have gone back to 0.39 and it has been stable for two days now not a blip. I am not sure if it is the reinstall or bringing the system up to date though it was not far behind, a few weeks maximum.
I will update if I find anything.
Cheers, Nick
-
Run MC from the Terminal and post the error here. If you're using Ubuntu 14.04 LTS, Linux Mint or Elementary OS you may need to use the fix above.
Hi bob and Awesome Donkey
I had a failure today.
From the command line:
>>>
:~$ mediacenter21
Found 0 devices (devices will be listed below)
Total time: 4 ms
Result: 0
Segmentation fault
>>>
From syslog
>>>
Feb 3 20:16:51 Octo kernel: [285236.337746] mediacenter21[2452]: segfault at 47b4000 ip 00007ff1aadcd9c0 sp 00007ffd76dc06e0 error 4 in libX11.so.6.3.0[7ff1aad88000+13c000]
>>>
-
Hi bob and Awesome Donkey
I had a failure today.
From the command line:
>>>
:~$ mediacenter21
Found 0 devices (devices will be listed below)
Total time: 4 ms
Result: 0
Segmentation fault
>>>
From syslog
>>>
Feb 3 20:16:51 Octo kernel: [285236.337746] mediacenter21[2452]: segfault at 47b4000 ip 00007ff1aadcd9c0 sp 00007ffd76dc06e0 error 4 in libX11.so.6.3.0[7ff1aad88000+13c000]
>>>
Ubuntu 15.10 64 bit.
I am familiar with this error- segmentatation fault and found 0 devices. I also have no video/visualization when I tried to play my mkv. It thinks my mkv are txt files.
-
Hi bob and Awesome Donkey
I had a failure today.
From the command line:
>>>
:~$ mediacenter21
Found 0 devices (devices will be listed below)
Total time: 4 ms
Result: 0
Segmentation fault
>>>
From syslog
>>>
Feb 3 20:16:51 Octo kernel: [285236.337746] mediacenter21[2452]: segfault at 47b4000 ip 00007ff1aadcd9c0 sp 00007ffd76dc06e0 error 4 in libX11.so.6.3.0[7ff1aad88000+13c000]
>>>
The 0 devices message is from JRWorker. It will always find 0 devices for the time being since CD support isn't in MC for linux yet.
The segfault could be from JRWorker or something else. (like a parse of a bad media file).
You could turn on logging and look at the end of the log.
You could also turn off Media Network for testing purposes and see if the segfault still happens.
-
The 0 devices message is from JRWorker. It will always find 0 devices for the time being since CD support isn't in MC for linux yet.
The segfault could be from JRWorker or something else. (like a parse of a bad media file).
You could turn on logging and look at the end of the log.
You could also turn off Media Network for testing purposes and see if the segfault still happens.
Hi bob,
Will do. Might be a dumb question but how do I turn on logging? Is there a command line switch or a config file or a setting?
Turning off Media Network will be a challenge I am using Media Centre on linux primarily as a server. Will see how I go.
Nick
-
Hi bob,
Will do. Might be a dumb question but how do I turn on logging? Is there a command line switch or a config file or a setting?
Turning off Media Network will be a challenge I am using Media Centre on linux primarily as a server. Will see how I go.
Nick
Logging is under the Help menu.
It leaves a log file in the ~/.jriver/Media Center 21 directory.
-
This one isn't up in the repository yet as I'd like to get some feedback first. Read the changelog for the base 21.0.48 in this forum.
-
MC's way quicker to exit now, which I like.
-
MC's way quicker to exit now, which I like.
I noticed that too.
Can you try 21.0.48-3 and see how that works?
-
Yep, still pretty quick to exit. That pretty much deals with one of the two performance issues I've noticed for a long time now. The other being there's a significant lag/lockup between the transition of Importing Media (when manually running Auto-Import) to displaying the Import Summary. Of course, this 'issue' doesn't exist on Windows or Mac.
There's another thing I've noticed for awhile now... when opening MC I notice the mouse cursor (on Ubuntu as the example here) appears as busy/spinning and not the normal mouse cursor for about the first 30 seconds. I thought it might be media network, but I disabled it completely (and all other features, actually).
-
... when opening MC I notice the mouse cursor (on Ubuntu as the example here) appears as busy/spinning and not the normal mouse cursor for about the first 30 seconds. I thought it might be media network, but I disabled it completely (and all other features, actually).
Launch feedback specified in the .desktop or elsewhere?
-
Launch feedback specified in the .desktop or elsewhere?
Good idea, I fixed it now.
StartupNotify= needs to be set to false instead of true.
-
While I'm on the subject, I've been looking into further why MC randomly will still open additional launchers in the dash even though using StartupWMClass *should* fix it properly. Even with the fixes lately I'm still noticing the issue and I'm trying to get to the bottom of it.
Some links:
http://askubuntu.com/questions/36434/how-can-i-remove-duplicate-icons-for-launched-java-programs-in-the-launcher
http://askubuntu.com/questions/248826/set-multiple-values-for-startupwmclass-to-group-under-same-launcher-in-unity
http://askubuntu.com/questions/367396/what-represent-the-startupwmclass-field-of-a-desktop-file
So, when I run xprop|grep WM_CLASS on MC I get the following;
WM_CLASS(STRING) = "JRiver Media Center 21", "Media Center 21"
I've tried setting StartupWMClass to JRiver Media Center 21 from Media Center 21 to see if it makes any difference, and it doesn't seem to. It'll still randomly launch with an additional launcher in the dash. I then ran xprop|grep WM_CLASS on other apps including Chrome, Firefox, Synaptic, Image Viewer, GIMP, gedit, etc. I'm beginning to wonder if it's because of the spaces/name itself of the MC class causing this. Looking at other apps none of them have spaces in the names - in fact they use dashes instead of spaces.
Maybe it'd work if MC's class was changed to something like this (based off what other apps are doing);
WM_CLASS(STRING) = "mediacenter21", "Media-center-21"
Thoughts? I wish this could be tested to see if it fixes the multiple launchers issue once and for all.
EDIT: Link for the WM_CLASS property: https://tronche.com/gui/x/xlib/ICC/client-to-window-manager/wm-class.html
-
Good idea, I fixed it now.
StartupNotify= needs to be set to false instead of true.
It was added to the desktop file because of this thread.
http://yabb.jriver.com/interact/index.php?topic=102752.0
I've noticed that it's not unusual for the spinner to stay around for a while when apps are started.
-
While I'm on the subject, I've been looking into further why MC randomly will still open additional launchers in the dash even though using StartupWMClass *should* fix it properly. Even with the fixes lately I'm still noticing the issue and I'm trying to get to the bottom of it.
Some links:
http://askubuntu.com/questions/36434/how-can-i-remove-duplicate-icons-for-launched-java-programs-in-the-launcher
http://askubuntu.com/questions/248826/set-multiple-values-for-startupwmclass-to-group-under-same-launcher-in-unity
http://askubuntu.com/questions/367396/what-represent-the-startupwmclass-field-of-a-desktop-file
So, when I run xprop|grep WM_CLASS on MC I get the following;
WM_CLASS(STRING) = "JRiver Media Center 21", "Media Center 21"
I've tried setting StartupWMClass to JRiver Media Center 21 from Media Center 21 to see if it makes any difference, and it doesn't seem to. It'll still randomly launch with an additional launcher in the dash. I then ran xprop|grep WM_CLASS on other apps including Chrome, Firefox, Synaptic, Image Viewer, GIMP, gedit, etc. I'm beginning to wonder if it's because of the spaces/name itself of the MC class causing this. Looking at other apps none of them have spaces in the names - in fact they use dashes instead of spaces.
Maybe it'd work if MC's class was changed to something like this (based off what other apps are doing);
WM_CLASS(STRING) = "mediacenter21", "Media-center-21"
Thoughts? I wish this could be tested to see if it fixes the multiple launchers issue once and for all.
EDIT: Link for the WM_CLASS property: https://tronche.com/gui/x/xlib/ICC/client-to-window-manager/wm-class.html
I don't want to arbitrarily change the MC window class and name.
There isn't anything in the link or in my X manuals that indicate that the Class name and app name must not have spaces in them.
Seems to be a desktop bug to me.
-
I don't want to arbitrarily change the MC window class and name.
There isn't anything in the link or in my X manuals that indicate that the Class name and app name must not have spaces in them.
It's odd, I've ran xprop|grep WM_CLASS on every app in Debian and Ubuntu and every single one doesn't use spaces - just dashes or dots.
Seems to be a desktop bug to me.
I thought so too, but Unity works fine with every other launcher. Maybe Unity is able to trigger this issue, whereas other DE's don't?
I'll keep digging around.
-
I'm hoping we are about done with the threading changes. Would appreciate some testing before it gets into the repository.
-
Working fine here thus far.
-
For possible move to the stable repository, currently up in the latest repo.
-
Is the stable repo working yet? I still get a 404 on it: http://dist.jriver.com/stable/mediacenter/mediacenter21.list
-
I'm seeing strange behavior with the progress bar on Arch with Gnome (using the amd64 build of jriver). Once I seek the progress bar gets "stuck" and flashes on the screen indefinitely until I change the volume or do something else that forces the lower OSD to redraw.
Another user is seeing it as well: https://yabb.jriver.com/interact/index.php?topic=103590.0
-
Bob:
On another TW machine, this time I uninstalled i386 and installed amd64 and now I get the "trial period has expired" (which happens everytime I try amd64 after having i386 installed).
Anyway, after the "expired" msg, it segfaults with this:
mediacenter21[8168]: segfault at 2378000 ip 00007f3a20833a60 sp 00007ffc0d3d23c0 error 4 in libX11.so.6.3.0[7f3a207ed000+13a000]
kernel 4.4.3 and mesa 11.1.2, fwiw. Is this of any use?
-
Bob:
On another TW machine, this time I uninstalled i386 and installed amd64 and now I get the "trial period has expired" (which happens everytime I try amd64 after having i386 installed).
Anyway, after the "expired" msg, it segfaults with this:
mediacenter21[8168]: segfault at 2378000 ip 00007f3a20833a60 sp 00007ffc0d3d23c0 error 4 in libX11.so.6.3.0[7f3a207ed000+13a000]
kernel 4.4.3 and mesa 11.1.2, fwiw. Is this of any use?
I've seen a lot of segfaults recently -> http://yabb.jriver.com/interact/index.php?topic=103140.0
some of them have been "fixed" by deleting ~/.jriver , i.e. effectively a fresh installation, but not all
-
Since a few day MC21 crashes (shutdown) when I try to connect to my audio files via library management...
so I have to play each file individually to prevent MC21 to shutdown. not very practical!
used to work perfect...
I did a clean install (again) of Ubuntu Studio 14.04.4 64 bit...and JRiver via terminal procedure.
same problem...shutdown as soon as I want to make a new library for my audio files...
My guess is that it has something to do with chrome stopped supporting 32 bit...happened around the same time as I got errors about 32 bit chrome...
now everything is 64 bit (I hope)...but problems with jriver are still there...
what can I do to fix this?
-
Is the cover art (Get From Internet) feature to blame for the crashes in 21.0.61 like it is on the Windows and Mac side?
-
Is the cover art (Get From Internet) feature to blame for the crashes in 21.0.61 like it is on the Windows and Mac side?
Most likely. Should have a new one up in a few minutes.
-
Thought so, that's why it didn't affect me as I don't use that feature (I manually handle all cover art). ;)
-
Thought so, that's why it didn't affect me as I don't use that feature (I manually handle all cover art). ;)
And I didn't see it on testing since I wasn't missing any coverart on my test machine.
-
Fixed the cover art crashing bug and reverted a change for DLNA renderer volume getting that caused sluggish GUI performance when used with a slow renderer.
-
So far testing the multiple MC Unity launcher issue has been positive. I've opened and closed MC over 20 times now without issue. I'll still be testing this another 20+ times but so far it's looking good. :D
EDIT: Just happened once twice three times thus far! >_<
-
So far testing the multiple MC Unity launcher issue has been positive. I've opened and closed MC over 20 times now without issue. I'll still be testing this another 20+ times but so far it's looking good. :D
EDIT: Just happened once twice three times thus far! >_<
Sorry, what "happened"? Multiple MC's or multiple icons or something else?
-
Multiple icons appearing in the Unity launcher when opening MC. It's definitely a lot better now with it only happening 3 out of 40 times.
-
Multiple icons appearing in the Unity launcher when opening MC. It's definitely a lot better now with it only happening 3 out of 40 times.
I don't see anything wrong with the way MC is setup now regarding that.
My guess is that there is something weird about the timing of the startup notification and the amount of time it takes MC to start.
I notice the spinny wheel for what seems to be an inordinate amount of time.
-
I don't see anything wrong with the way MC is setup now regarding that.
My guess is that there is something weird about the timing of the startup notification and the amount of time it takes MC to start.
Yeah, it's an odd one but it seems to happen rarely now, which is fine with me as I can just close MC and reopen it. Nonetheless I've switched from Unity to GNOME + Dash to Dock and it's much, much better than Unity.
I notice the spinny wheel for what seems to be an inordinate amount of time.
Ah, that. Yeah, I believe that's caused by using StartupNotify. As far as I know, StartupNotify is needed for the launcher stuff to work correctly. Hmmm.
-
21.0.63 has been running well for me, mostly. The only thing I'm regularly experiencing is a crash on Server copy when I close a client copy connecting to the Server library. I see this in the syslog on the Server:
mediacenter21[5588]: segfault at 33d9000 ip 00007f0ef6a03ab0 sp 00007ffe56b1d2e0 error 4 in libX11.so.6.3.0[7f0ef69c5000+130000]
Both Server and client are running MC 21.0.63. The server is Ubuntu Server 14.04 LTS, the client is Linux Mint 17.3.
-
Hello.
Linux Debian Jessie 8.3
JRiver 21.0.63 with Linux license.
After few days - don't start, with no massage. Reboot don't help.
Please help.
-
In console say: segmentation error.
-
In console say: segmentation error.
Can you post the whole error message? It should also show up in the output from dmesg
-
in Russian: "Ошибка сегментации", in translation: "Segmentation error" :)
-
Hello.
Linux Debian Jessie 8.3
JRiver 21.0.63 with Linux license.
After few days - don't start, with no massage. Reboot don't help.
Please help.
Perhaps a corrupted settings file.
remove the
~/.jriver/Media Center 21/Settings
directory and restart MC.
You will lose your settings and license but not the library. You can just re-enter your license code.
-
Great thanks, Bob.
It's work.
but why it occurs already the second time?
-
Great thanks, Bob.
It's work.
but why it occurs already the second time?
I don't know why that would happen unless perhaps the machine crashed while MC was running?
-
The 21.0.70 build has a change to the copy/paste method. Some testing would be good. We are looking to see if we broke other control key functions (we found a few that didn't work before already). Also to make sure it doesn't crash MC under an unusual situation.
-
So far it's working pretty good here. :D
-
Okay, more testing in my Linux VMs - copy and paste doesn't seem to work into Customize Display. Anyone else confirm? The clipboard is correctly copied from the host to guest VM, so that isn't an issue. However if I attempt to copy anything within MC (e.g song title, artist name, etc.) and paste that into gedit (all within the VM), it doesn't work.
I'll test from the native Arch install here in a few mins.
EDIT: Anything I'm writing into gedit/Text Editor then highlighting and copying via the right click menu works (and thus the contents are in the clipboard) however trying to paste said contents in MC via Paste from right click or CTRL+V doesn't work. Paste isn't selectable so it's not reading the clipboard.
EDIT 2: Okay, tested from the native Arch install and the results are the same. Copying from outside MC (e.g gedit) and pasting to MC doesn't work. Nor does copying from MC and pasting to gedit. However copying and pasting within MC itself seems to be working fine. So that's pretty much it here - I've confirmed this behaviour in the native Arch install, Ubuntu VM, Arch VM and Mint VM. I'll test the Debian VM here in a few mins, but I suspect the result will be the same.
EDIT 3: Same result with the Debian VM.
-
Okay, more testing in my Linux VMs - copy and paste doesn't seem to work into Customize Display. Anyone else confirm? The clipboard is correctly copied from the host to guest VM, so that isn't an issue. However if I attempt to copy anything within MC (e.g song title, artist name, etc.) and paste that into gedit (all within the VM), it doesn't work.
I'll test from the native Arch install here in a few mins.
EDIT: Anything I'm writing into gedit/Text Editor then highlighting and copying via the right click menu works (and thus the contents are in the clipboard) however trying to paste said contents in MC via Paste from right click or CTRL+V doesn't work. Paste isn't selectable so it's not reading the clipboard.
EDIT 2: Okay, tested from the native Arch install and the results are the same. Copying from outside MC (e.g gedit) and pasting to MC doesn't work. Nor does copying from MC and pasting to gedit. However copying and pasting within MC itself seems to be working fine. So that's pretty much it here - I've confirmed this behaviour in the native Arch install, Ubuntu VM, Arch VM and Mint VM. I'll test the Debian VM here in a few mins, but I suspect the result will be the same.
EDIT 3: Same result with the Debian VM.
Interesting, I copied in and out of abiword without an issue....
-
Good day.
Definition of testing system ... a) I have no .Xdefaults nor .Xresources files on my system. b) I am using twm for window manager ;D. c) I had to ask where the Customized Display menu was (right-click on "JRiver Media Center 21" text) located.
With gedit, I can type there and select (double/triple click for example) and then control-C (or right button->copy). Go to MediaCenter and control-V to paste (or right button->paste).
The opposite shows how broken various X applications are with regards to CLIPBOARD/PRIMARY cut and paste. If you control-V into gedit, it pastes. The right button->Paste is greyed out in gedit. But, control-V works fine.
I do not have the middle button paste of selections from PRIMARY working. If you select in Media Center, it stays in MediaCenter. It does not do a selection clear event to whoever the owner of the PRIMARY selection property is, nor does it change the PRIMARY property to contain the selection. (On the list ...along with virtual keys and control keys for menu options...)
-
I am guessing that the "Paste" menu un-grayed-out in gedit depends on the selection clear event for PRIMARY property arriving. "Most interesting..." ?
-
Interesting, I copied in and out of abiword without an issue....
Retested 21.0.76 and copy/paste still doesn't work too well. Using gedit for the copy/paste to and from MC21.
-
Retested 21.0.76 and copy/paste still doesn't work too well. Using gedit for the copy/paste to and from MC21.
Noted. It works sometimes for me but not all of the time.
-
Hello, I'm evaluating JRiver Media as a media player for my linux machine but it seems like it doesn't support hidpi, is there any workaround for this?
Here is the screenshot: http://imgur.com/1YdNL2O
-
Hello, I'm evaluating JRiver Media as a media player for my linux machine but it seems like it doesn't support hidpi, is there any workaround for this?
Here is the screenshot: http://imgur.com/1YdNL2O
You can manually increase the size of MC in the View -> Size menu, as well as adjusting fonts in the Options, Tree & View -> Select Font...
These two combined should be able to make MC look properly on any DPI.
-
It'd be nice to get some feedback on this from people that were still getting the occassional segfault on Debian.
-
It'd be nice to get some feedback on this from people that were still getting the occassional segfault on Debian.
I gave up using mc21 on my linux machines...mc 20 works...mc 21 does not...
Clean install linux ubuntu studio 14 and 16...same problem...stops starting up after a while...3 different computers...everything else works perfect, so I am shure it is mc 21 that is causing the problem...
Now I am getting mails for mc 22 upgrade...but why should I upgrade if mc 21 is not working properly...
I think It would be wise to get things working properly before asking people to spend money again for a new adventure...
It works fine in windows...but I do not wish to use windows for my audio...
-
I gave up using mc21 on my linux machines...mc 20 works...mc 21 does not...
Clean install linux ubuntu studio 14 and 16...same problem...stops starting up after a while...3 different computers...everything else works perfect, so I am shure it is mc 21 that is causing the problem...
Now I am getting mails for mc 22 upgrade...but why should I upgrade if mc 21 is not working properly...
I think It would be wise to get things working properly before asking people to spend money again for a new adventure...
It works fine in windows...but I do not wish to use windows for my audio...
I'm not sure if is MC problem at all.
I'm running MC 21 on opensuse without problems, same for deepin (based on debian).
Maybe you should post a debug output here to see what happen.
Personally, I'm interested in buying MC, but at this moment, I want to wait to that the "detach display" can move and stay overall windows, is a strange mode for work but I like that (I'm doing it with smplayer actually)
Regards.
-
I'm not sure if is MC problem at all.
I'm running MC 21 on opensuse without problems, same for deepin (based on debian).
Maybe you should post a debug output here to see what happen.
Personally, I'm interested in buying MC, but at this moment, I want to wait to that the "detach display" can move and stay overall windows, is a strange mode for work but I like that (I'm doing it with smplayer actually)
Regards.
well I really do not care if it is MC 21 or not...it works in win 10, it works in Ubuntu Studio 14.04 it does not work in 16.04...
I am shure all the others players work fine and this one is not...so no MC21 on linux for me till it is fixed...
and no upgrade to MC22 as long as it is not working properly...
I will check status regularly...
I think it is not professional to release a product and ask a price for it when it is not properly tested...and it is not the buyer who needs to debug it...it should work fine if you pay for it...
-
Well, running on Ubuntu is technically unsupported, and I've never attempted to run MC21 on Ubuntu Studio. However, MC21 works fine on normal Ubuntu 16.04 LTS though.