SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I struggled for a long time with minidlna and mediatomb, and those never worked well. Then I switched to Universal Media Server and stuck with that.
I second that opinion; UMS is really easy to use and setup on Slackware. UMS in my experience just works....all I'm missing is a decent startup script so I start it manually on the rare reboots, but I can live with that.
I second that opinion; UMS is really easy to use and setup on Slackware. UMS in my experience just works....all I'm missing is a decent startup script so I start it manually on the rare reboots, but I can live with that.
I just run "/usr/local/ums/UMS.sh" under my own account after unpacking the tarball in /usr/local and making a "/usr/local/ums" symlink to the versioned UMS directory.
I use BubbleUPnP as my favorite DLNA client on my phone and tablet, so I added the following content to a new "BubbleUPnP.conf" file in the ./renderers subdirectory:
Code:
#----------------------------------------------------------------------------
# Profile for BubbleUPnP
# Based on Android.conf
# See DefaultRenderer.conf for a description of all possible configuration options.
#
# User-Agent: Android/4.4.4 UPnP/1.0 BubbleUPnP/2.0.6
RendererName = BubbleUPnP
UpnpDetailsSearch = Bubblesoft , BubbleUPnP Media Renderer
LoadingPriority = 1
UserAgentSearch=BubbleUPnP
TranscodeAudio = MP3
DefaultVBVBufSize = true
MuxDTSToMpeg = true
WrapDTSIntoPCM = false
H264Level41Limited = false
StreamExtensions = mkv,hdmov,hdm,flac,fla,dts,ogg,asf,asx,m2v,mp4,mpg,mpeg,avi,mov,wmv
ChunkedTransfer = true
SupportedExternalSubtitlesFormats = SUBRIP,ASS,MICRODVD
The most important line in there is "SupportedExternalSubtitlesFormats = SUBRIP,ASS,MICRODVD" because that enables the magic of subtitle rendering using external .SRT files when playing movies.
Just an idea to begin some foundation work that could be useful:
Add package wayland to Slackware. http://wayland.freedesktop.org/releases.html Mesa and xorg-server packages would require a rebuild to gain wayland support, also gtk+-3 and cairo(?) has backend support for wayland. Although SBo only for now, packages like SDL2, QT5, and a few other libraries and compositors have wayland support.
Pros: Slackware would already have wayland support capabilities which would be useful for developers and packagers to avoid out-of-tree stand-alone mesa package maintenance.
Cons: Adds a dependency to which packages built against it might have to be rebuilt if upgraded. Would possibly, but hopefully not, require packages libxkbcommon and libinput for application input support for compositors using wayland strictly.
From my own experiences i can say that i build the whole KDE stack from source on each release for frameworks, plasma and apps. There are still some things i don't like but maybe this is just some configuration issue (or some missing patches). Anyway i find KDE4 rock-solid and i would prefer Slackware to stick with KDE4 for now.
A wise old master stood over a meadow with his much younger pupil. As the pupil looked on he saw a grasshopper waiting patiently on a leaf. "Master," the young pupil said curiously, "Why does the grasshopper wait on the leaf? It is spring time and the grasshopper must be hungry." "Ah!" said the old master smiling, "The grasshopper has shown great wisdom! You must remember that in earnest my pupil!" "But master," the young pupil replied as he looked closely at the grasshopper sitting on the leaf, "Why does it wait? Isn't it hungry?" The old master smiled and pointed at the grass growing in the meadow. "The grasshopper waits patiently for the grass to be fully grown so that it can eaten after it releases it's seeds and new grass can grow afterwards. If it ate it now, the grasshopper would have no grass to eat next year." "But it's such a long time master," the young pupil replied trying to feed the grasshopper a leaf, "It must hurt to wait so long for good things." "Yes it do my pupil," the old master replied as he gazed over the meadow, "But the best things come to those with patience."
From my own experiences i can say that i build the whole KDE stack from source on each release for frameworks, plasma and apps. There are still some things i don't like but maybe this is just some configuration issue (or some missing patches). Anyway i find KDE4 rock-solid and i would prefer Slackware to stick with KDE4 for now.
I use kde since longtime (kde-1.0), but I've never been a big fan of the look of kde, but it just my opinion, currently, i use kf5, the look is better, it is as stable as kde4
When i updated to current from 14.1, scim korean seem to be broken. I can type korean but i cant type space
I'm sorry, but without a way to reproduce the problem I have no way of even knowing what's wrong. I tried it already multiple times, but I have no problems typing spaces here with korean input.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
