LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page [SOLVED] kamoso broken in 64-current
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
Page 1 of 2 1 2
  Search this Thread
Old 01-23-2021, 12:00 AM   #1
josiah
Member
 
Registered: May 2004
Distribution: Slackware
Posts: 72

Rep: Reputation: 42
kamoso broken in 64-current

Kamoso doesn't seem to open. From the command line, I get the following error. I've abbreviated it to show what appears to be relevant, but the full error message is below.


Code:
Cyclic dependency detected between "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
[...snip...]
The webcam controller was unable to find or load wrappercamerabinsrc plugin; please make sure all required gstreamer plugins are installed.
Unrecoverable error occurred when initializing webcam. Exiting.
For the full error message, see below:

Code:
Cyclic dependency detected between "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ActionToolBar.qml:110:18: QML ToolBarLayout: Binding loop detected for property "actions"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ActionToolBar.qml:110:18: QML ToolBarLayout: Binding loop detected for property "actions"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ActionToolBar.qml:110:18: QML ToolBarLayout: Binding loop detected for property "actions"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:162:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:99:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:139:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/OverlayDrawer.qml:284:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/OverlayDrawer.qml:284:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:162:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:139:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:99:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/ActionButton.qml:221:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/ActionButton.qml:209:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:162:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:99:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:139:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:139:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:162:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:139:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:99:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:139:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:139:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:124: TypeError: Cannot read property 'globalToolBarStyle' of null
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:61:17: Unable to assign [undefined] to QQmlListProperty<QObject>
The webcam controller was unable to find or load wrappercamerabinsrc plugin; please make sure all required gstreamer plugins are installed.
Unrecoverable error occurred when initializing webcam. Exiting.
 
Old 01-23-2021, 01:25 AM   #2
gegechris99
Senior Member
 
Registered: Oct 2005
Location: France
Distribution: Slackware 15.0 64bit
Posts: 1,162
Blog Entries: 5

Rep: Reputation: 394Reputation: 394Reputation: 394Reputation: 394
kamoso seems to be missing wrappercamerabinsrc gstreamer plugin.
This plugin is available in package gst-plugins-bad which is not part of standard Slackware.
You can find it at SlackBuils.org
 
1 members found this post helpful.
Old 01-23-2021, 03:31 AM   #3
josiah
Member
 
Registered: May 2004
Distribution: Slackware
Posts: 72

Original Poster
Rep: Reputation: 42
That makes sense, thank you for the pointer. Since Kamoso is a part of the standard Slackware distribution as of the inclusion of ktown/vtown, it seems like this is an oversight in the migration.

Edit to note: after installing gst-plugins-bad (cobbling together the SBo SlackBuild and Pat's gst-plugins-good SlackBuild to bring it in line with 1.18.3), kamoso does in fact work. I suppose then that this is more of a bug report that there's a dependency problem with kamoso in -current.
Last edited by josiah; 01-23-2021 at 04:01 AM. Reason: more complete response
 
Old 01-23-2021, 03:59 AM   #4
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
Quote:
Originally Posted by josiah View Post
That makes sense, thank you for the pointer. Since Kamoso is a part of the standard Slackware distribution as of the inclusion of ktown/vtown, it seems like this is an oversight in the migration.
Kamoso in Slackware-current works the exact same way, with the exact same error, as my past ktown version of it. No migration issue.
 
Old 01-23-2021, 02:46 PM   #5
josiah
Member
 
Registered: May 2004
Distribution: Slackware
Posts: 72

Original Poster
Rep: Reputation: 42
Quote:
Originally Posted by Alien Bob View Post
Kamoso in Slackware-current works the exact same way, with the exact same error, as my past ktown version of it. No migration issue.
But as I recall, you provide gst-plugins-bad in your repository, so someone using third-party repositories (including ktown and your standard SlackBuilds) was able to satisfy the dependency. As part of the standard Slackware KDE distribution, it is now a program that simply doesn't work out of the box without relying upon third-party repositories, which to my knowledge is outside of the typical Slackware practice.

I guess what I'm suggesting is that it seems to me that either Slackware should provide gst-plugins-bad or Kamoso should be cut from the standard installation and should rather be provided by third-party repositories, but I'd defer to others here.
Last edited by josiah; 01-23-2021 at 03:02 PM.
 
Old 01-24-2021, 02:53 AM   #6
z80
Member
 
Registered: Jul 2019
Location: Europe
Distribution: Slackware64-current
Posts: 136

Rep: Reputation: 99
The real issue could be a problem with the v4l driver in the kernel.
At least that's the problem in my case with Kernel 5.10.x.
 
Old 01-24-2021, 06:44 AM   #7
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,979

Rep: Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556
Quote:
Originally Posted by josiah View Post
Edit to note: after installing gst-plugins-bad (cobbling together the SBo SlackBuild and Pat's gst-plugins-good SlackBuild to bring it in line with 1.18.3), kamoso does in fact work. I suppose then that this is more of a bug report that there's a dependency problem with kamoso in -current.
A bit confused about the cobbling together part. Does this mean you do have a full installation of slackware64-current? Just wondering.

I have gst-plugins-bad installed for webkit2gtk, kamoso works just fine. I see no issues with the programs operation, it is fully functional.

Yes it does fail without gst-plugins-bad.

It is a noisy program from Konsole though.
Code:
Cyclic dependency detected between "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ActionToolBar.qml:110:18: QML ToolBarLayout: Binding loop detected for property "actions"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ActionToolBar.qml:110:18: QML ToolBarLayout: Binding loop detected for property "actions"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ActionToolBar.qml:110:18: QML ToolBarLayout: Binding loop detected for property "actions"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:162:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:99:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:139:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/OverlayDrawer.qml:284:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/OverlayDrawer.qml:284:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:162:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:139:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:99:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/ActionButton.qml:221:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/ActionButton.qml:209:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:162:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:99:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:139:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:139:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:162:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:139:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:99:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:139:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:139:9: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:124: TypeError: Cannot read property 'globalToolBarStyle' of null
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:61:17: Unable to assign [undefined] to QQmlListProperty<QObject>
Creating QUrl("file:///home/chris/Pictures/Kamoso")
skipping message... imagebin-filesink
video saved successfully
Creating QUrl("file:///home/chris/Pictures/Kamoso")
skipping message... imagebin-filesink
Creating QUrl("file:///home/chris/Pictures/Kamoso")
skipping message... imagebin-filesink
Creating QUrl("file:///home/chris/Pictures/Kamoso")
skipping message... imagebin-filesink
 
Old 01-24-2021, 07:25 PM   #8
josiah
Member
 
Registered: May 2004
Distribution: Slackware
Posts: 72

Original Poster
Rep: Reputation: 42
Quote:
Originally Posted by chrisretusn View Post
A bit confused about the cobbling together part. Does this mean you do have a full installation of slackware64-current? Just wondering.

I have gst-plugins-bad installed for webkit2gtk, kamoso works just fine. I see no issues with the programs operation, it is fully functional.
I do indeed have a full installation of slackware64-current. In order to get gst-plugins-bad that is the same version as the gst-plugins-good that is installed by default (rather than gst-plugins-bad0), I had to change the SBo script to accommodate the meson build system and simply used the configuration and build lines from Pat's gst-plugins-good SlackBuild. Not a difficult change, but I also was tired and probably didn't pay close enough attention to the script to know if I was missing anything. So, er, I meant cobbled together more in the sense that I was being inattentive and lazy rather than that it was some daunting and difficult task.

Now that I have gst-plugins-bad installed, Kamoso works fine. But again, it seems out of character to have a program that is part of the default distribution that is useless without a) providing a runtime dependency, b) providing some message to indicate that a third party package is required for its use, or c) letting third party repositories handle both Kamoso and gst-plugins-bad.

Quote:
Yes it does fail without gst-plugins-bad.
...and silently, I might add, from a desktop user perspective.

Quote:
It is a noisy program from Konsole though.
omg yes.
Last edited by josiah; 01-24-2021 at 07:27 PM.
 
Old 01-25-2021, 10:10 AM   #9
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,979

Rep: Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556
Ok, understand. I don't use SBo builds, I build my own SlackBuilds. My gst-plugins-bad.SlackBuild also uses the meson build. I don't see a problem with just adding gst-plugins-bad to get Kamoso to work if you want to use it. Just so happens I have the gst-plugins-bad installed for other programs. There is another program called Kamerka that comes with Slackware that does basically the same things as Kamoso and doesn't need gst-plugins-bad.

There does not seem to be any licensing problems with bad like with ugly, but the bad is called bad for a reason. So I do not see it being added to Slackware. That said, I'm not the guy in charge, so that just a guess. I would have not have any problems if Kamoso is removed either. I don't use it.
Last edited by chrisretusn; 01-25-2021 at 10:12 AM.
 
Old 01-26-2021, 04:40 AM   #10
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,979

Rep: Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556
never mind, still broken.

Work with cam plugged in, fails when it is.

This is a pretty old issue.

https://bugs.kde.org/show_bug.cgi?id=356133
Last edited by chrisretusn; 01-26-2021 at 04:55 AM.
 
Old 02-17-2021, 03:47 PM   #11
hugok
LQ Newbie
 
Registered: Feb 2014
Location: Portugal
Distribution: Slackware, Salix, Bodhi, Pardus
Posts: 23

Rep: Reputation: Disabled
Kamoso should work out of the box... without the need to install gst-plugins-bad.

The way I see it, this has to be fixed.
 
Old 02-17-2021, 04:35 PM   #12
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
Quote:
Originally Posted by hugok View Post
Kamoso should work out of the box... without the need to install gst-plugins-bad.

The way I see it, this has to be fixed.
Why do you think that? Can you fix the error?
 
Old 02-18-2021, 07:08 AM   #13
hugok
LQ Newbie
 
Registered: Feb 2014
Location: Portugal
Distribution: Slackware, Salix, Bodhi, Pardus
Posts: 23

Rep: Reputation: Disabled
What is the purpose of having a program that does not work after installing slackware?
 
Old 02-18-2021, 07:34 AM   #14
ZhaoLin1457
Senior Member
 
Registered: Jan 2018
Posts: 1,032

Rep: Reputation: 1238Reputation: 1238Reputation: 1238Reputation: 1238Reputation: 1238Reputation: 1238Reputation: 1238Reputation: 1238Reputation: 1238
Quote:
Originally Posted by hugok View Post
What is the purpose of having a program that does not work after installing slackware?
From what I understand, the Slackware, Inc. cannot ship freely certain codecs because of the patents from US of America.

So, please keep your rhetoric questions for the Patents Overlords who put copyrights even on the ergonomic ways of farting...
Last edited by ZhaoLin1457; 02-18-2021 at 07:42 AM.
 
Old 02-18-2021, 07:56 AM   #15
hugok
LQ Newbie
 
Registered: Feb 2014
Location: Portugal
Distribution: Slackware, Salix, Bodhi, Pardus
Posts: 23

Rep: Reputation: Disabled
Ok ok... I get the picture.
But what we have here is not an example of having a multimedia player that opens but due to the licenses it does not come with the necessary codecs to play certain types of video files...
We simple have a app that doesn’t open at all... for a common user like me to have something that doesn't open is at least strange.
 
  


Reply
Page 1 of 2 1 2



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Recovery broken OS after broken drive DangerSchwob Debian 6 11-02-2020 02:38 AM
libxslt in -current broken? Slim Backwater Slackware 8 06-23-2006 11:14 PM
AdBlocK Filters broken: KDE 3.5.1 slackware-current mailman0 Slackware 2 04-19-2006 03:36 PM
slackware current broken? sweetnsourbkr Slackware 8 03-11-2006 06:26 AM
wget broken after new packages in -current sh1ft Slackware 3 12-22-2004 11:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:33 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration