Recent Posts

Pages: 1 ... 5 6 [7] 8 9 10
61
Users / Re: Need some dedicated testers.
« Last post by maverick0815 on August 22, 2015, 02:35:20 pm »
They are tagged correctly. I remember tschak saying, They Wohle eventuelle Benachrichtigungen selectable by show, season, episode....something like that.
62
Developers / Re: Slow and steady ... moving from Trac to Gitlab
« Last post by tschak909 on August 22, 2015, 04:33:41 am »
Sweeet!  And thanks for your efforts! 

At work, we switched from Git/Trac to Git/Gitlab, and it's sooo much more of a productive environment. We've got hooks from certain projects into Jenkins for building RPM's 5 minutes after a commit, and that's sweet from a packaging point of view. Jenkins really rocks as well!  (BTW, there's a .deb builder plugin for Jenkins if that's of interest to you)

I have a small request of you and the core devs.  Gitlab represents a real opportunity to enable more people to get involved in LinuxMCE development and testing. In the past, I didn't want to have any form of SVN access;  I know enough to know I don't know enough about LMCE to event want any commit access (bull in a china shop syndrome). So, that limited me to filing tickets with diffs attached.

Gitlab changes all of that. The core devs can steward the main linuxmce project, and personal workspaces allow more novice folks like myself the opportunity to contribute through an isolated environment and merge requests. So, I would like to make the following request:

Could you folks create a wiki page with some example workflows that would enable folks like myself to contribute more, while minimizing the level of effort on the core devs to take advantage of what we do?

I'm thinking of example workflows like:
  • simple bug fix for existing code
  • significant bug fix for existing code or refactoring
  • simple new feature (new code)
  • significant new feature (majorly intrusive)

I think that giving us examples of how you want us to work would be good for us novices to learn, while making life easier for those already overcommitted core devs.   Maybe even a quick page on how issues should be filed might be good for standardizing and leveraging Gitlab's capabilities...

Just thought I'd put this out there for your consideration.

Thanks again for your hard work on this!  I'm sure it wasn't easy, but it will be worth it in the long run!

/Mike

A good post! Of course ,you're assuming we actually _have_ a workflow, but we don't....really....other than:

* File a ticket in trac
* assign your commits with Refs #1234 for that ticket
* make sure when you're done with it to close it, either with Fixes #1234, or by marking it closed or fixed. (depends on the ticket type).

Maybe we should... I dunno, what do you think, posde?

-Thom
63
Installation issues / Re: LMCE­ 1404­ 20150630062­730843 Nvidia Install Reboot Loop
« Last post by polly on August 21, 2015, 10:07:51 am »
Hey ...

iirc 1404 DVD install is not working atm.
Netinstall worked for me without any issues :-)

Cheers,
Jochen
64
Installation issues / LMCE­ 1404­ 20150630062­730843 Nvidia Install Reboot Loop
« Last post by huh on August 21, 2015, 06:40:33 am »
In observation of rules #1 and #2....

I installed the 14.04 20150630062­730843 snapshot tonight (on standard dual network setup) and everything seemed to work great, until it rebooted for the 2nd/3rd time and attempted to get nvidia drivers.

I'm transcribing from a recording on my phone, so bear with me with typos...

Code: [Select]
* Staring CheckAVWizard check_avwizard
/etc/X11/xorg.conf is missing.  Using video driver 'nvidia' for ....
*Installing nvidia driver this may take a few minutes . /usr/pluto/bin/nvidia-install.sh
* Starting AVWizard AVWizard_Run.sh

Then it attempts to pull the package, but fails on
Code: [Select]
Err http://archive.ubuntu.com/ubuntu/ trusty-updates/main dkms all 2.2.0.3-1.1ubuntu5.14.04
404 Not round [IP: 91.189.91.13 80]
Faied to fetch...

It thinks it pulled the nvidia driver and says
Code: [Select]
Nvidia driver installation requires a reboot
Please stand by while your system is rebooted

I let it do this 3 times just to make sure it wasn't a fluke.

Is there an easy way to get it to bypass the nvidia install?  I really could do with a headless install, but am perfectly fine with the generic (non-nvidia) driver for what I'm using this for.
65
Developers / Re: Slow and steady ... moving from Trac to Gitlab
« Last post by polly on August 21, 2015, 05:06:33 am »
Haven't been testing it yet.  Soon...  You'll have 1000 tickets to act on when you get back ;)

J.

Jiiiha! .... ;-)
66
Users / Re: GSD issues - all devices died.
« Last post by mkbrown69 on August 21, 2015, 04:32:54 am »
Jason,

Thanks for the tip on using screen. Here's the output from each time the device dies.

Code: [Select]
LOG: ========== NEW LOG SECTION ==========
1       08/20/15 22:23:57       189 (spawning-device)   Starting... 40
1       08/20/15 22:23:57       189 (spawning-device)   Starting... 40
1       08/20/15 22:23:57       189 (spawning-device)   Found /usr/pluto/bin/Generic_Serial_Device
1       08/20/15 22:23:57       189 (spawning-device)   Found /usr/pluto/bin/Generic_Serial_Device
Generic_Serial_Device, v.2.0.0.46.15060430777
Visit www.plutohome.com for source code and license information

embed: [BUG] Segmentation fault
ruby 1.9.3p0 (2011-10-30 revision 33570) [i686-linux]

-- Control frame information -----------------------------------------------
c:0001 p:0000 s:0002 b:0002 l:ffffdfc4 d:ffffdfc4 TOP


-- C level backtrace information -------------------------------------------
/usr/lib/libruby-1.9.1.so.1.9(+0x15e4dd) [0x26e4dd]
/usr/lib/libruby-1.9.1.so.1.9(+0x4e111) [0x15e111] vfscanf.c:1784
/usr/lib/libruby-1.9.1.so.1.9(rb_bug+0x44) [0x15e8f4] vfscanf.c:1013
/usr/lib/libruby-1.9.1.so.1.9(+0xf7b5c) [0x207b5c] argp.h:586
[0xa20410]
/usr/lib/libruby-1.9.1.so.1.9(+0x63b24) [0x173b24] fxprintf.c:47
/usr/lib/libruby-1.9.1.so.1.9(+0x63c37) [0x173c37] printf-parsemb.c:152
/usr/lib/libruby-1.9.1.so.1.9(+0x656bf) [0x1756bf] libioP.h:985
/usr/lib/libruby-1.9.1.so.1.9(rb_newobj+0x23c) [0x17624c] iopopen.c:346
/usr/lib/libruby-1.9.1.so.1.9(+0x102d65) [0x212d65] ../sysdeps/unix/sysv/linux/readonly-area.c:88
/usr/lib/libruby-1.9.1.so.1.9(rb_enc_str_new+0x2a) [0x214faa] wcpcpy_chk.c:38
/usr/lib/libruby-1.9.1.so.1.9(+0xa252e) [0x1b252e] ../stdlib/strtod_l.c:1615
/usr/lib/libruby-1.9.1.so.1.9(+0xab6e7) [0x1bb6e7] getdate.c:270
/usr/lib/libruby-1.9.1.so.1.9(+0xb8dd5) [0x1c8dd5] ../sysdeps/unix/sysv/linux/i386/setgid.c:36
/usr/lib/libruby-1.9.1.so.1.9(+0x160601) [0x270601]
/usr/lib/libruby-1.9.1.so.1.9(+0xa24e1) [0x1b24e1] ../stdlib/strtod_l.c:1601
/usr/lib/libruby-1.9.1.so.1.9(rb_iseq_compile_with_option+0x64) [0x255cc4] ../sysdeps/i386/i686/multiarch/strcmp-ssse3.S:1853
/usr/lib/libruby-1.9.1.so.1.9(rb_iseq_compile+0x3b) [0x255eeb] ../sysdeps/i386/i686/multiarch/strcmp-ssse3.S:1950
/usr/lib/libruby-1.9.1.so.1.9(+0x15358a) [0x26358a]
/usr/lib/libruby-1.9.1.so.1.9(rb_eval_string+0x4f) [0x263bff]
/usr/pluto/bin/Generic_Serial_Device(_ZN7EMBRUBY11RubyEmbeder9_loadcodeEm+0x23) [0x8077e1d] RubyEmbeder.cpp:109
/usr/lib/libruby-1.9.1.so.1.9(rb_protect+0xce) [0x16299e] vfscanf.c:2318
/usr/pluto/bin/Generic_Serial_Device() [0x8077b54] RubyEmbeder.cpp:79
/usr/pluto/bin/Generic_Serial_Device() [0x808d448] RubyIOManager.cpp:463
/usr/pluto/bin/Generic_Serial_Device(_ZN3DCE8IOThread11_threadprocEPv+0x2a) [0x80775fe] IOThread.cpp:79
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c) [0x597d4c] pthread_create.c:308
/lib/i386-linux-gnu/libc.so.6(clone+0x5e) [0xe46b8e] ../sysdeps/unix/sysv/linux/i386/clone.S:130

-- Other runtime information -----------------------------------------------

* Loaded script: embed

* Loaded features:

    0 enumerator.so

* Process memory map:

00110000-0030e000 r-xp 00000000 fd:01 131209     /usr/lib/libruby-1.9.1.so.1.9.1
0030e000-00311000 r--p 001fd000 fd:01 131209     /usr/lib/libruby-1.9.1.so.1.9.1
00311000-00313000 rw-p 00200000 fd:01 131209     /usr/lib/libruby-1.9.1.so.1.9.1
00313000-00323000 rw-p 00000000 00:00 0
00323000-00341000 r-xp 00000000 fd:01 654464     /usr/pluto/lib/libSerializeClass.so
00341000-00342000 r--p 0001d000 fd:01 654464     /usr/pluto/lib/libSerializeClass.so
00342000-00343000 rw-p 0001e000 fd:01 654464     /usr/pluto/lib/libSerializeClass.so
00343000-00357000 r-xp 00000000 fd:01 1442801    /lib/i386-linux-gnu/libz.so.1.2.3.4
00357000-00358000 r--p 00013000 fd:01 1442801    /lib/i386-linux-gnu/libz.so.1.2.3.4
00358000-00359000 rw-p 00014000 fd:01 1442801    /lib/i386-linux-gnu/libz.so.1.2.3.4
00359000-00383000 r-xp 00000000 fd:01 1455536    /lib/i386-linux-gnu/libm-2.15.so
00383000-00384000 r--p 00029000 fd:01 1455536    /lib/i386-linux-gnu/libm-2.15.so
00384000-00385000 rw-p 0002a000 fd:01 1455536    /lib/i386-linux-gnu/libm-2.15.so
00385000-0038d000 r-xp 00000000 fd:01 1455548    /lib/i386-linux-gnu/libcrypt-2.15.so
0038d000-0038e000 r--p 00007000 fd:01 1455548    /lib/i386-linux-gnu/libcrypt-2.15.so
0038e000-0038f000 rw-p 00008000 fd:01 1455548    /lib/i386-linux-gnu/libcrypt-2.15.so
0038f000-003b6000 rw-p 00000000 00:00 0
003d5000-003dc000 r-xp 00000000 fd:01 654359     /usr/pluto/lib/libSerial.so
003dc000-003dd000 r--p 00006000 fd:01 654359     /usr/pluto/lib/libSerial.so
003dd000-003de000 rw-p 00007000 fd:01 654359     /usr/pluto/lib/libSerial.so
003de000-004bf000 r-xp 00000000 fd:01 655506     /usr/pluto/lib/libDCECommon.so
004bf000-004c0000 r--p 000e0000 fd:01 655506     /usr/pluto/lib/libDCECommon.so
004c0000-004c3000 rw-p 000e1000 fd:01 655506     /usr/pluto/lib/libDCECommon.so
004c3000-004d4000 rw-p 00000000 00:00 0
0056c000-0058c000 r-xp 00000000 fd:01 1455488    /lib/i386-linux-gnu/ld-2.15.so
0058c000-0058d000 r--p 0001f000 fd:01 1455488    /lib/i386-linux-gnu/ld-2.15.so
0058d000-0058e000 rw-p 00020000 fd:01 1455488    /lib/i386-linux-gnu/ld-2.15.so
00591000-005a8000 r-xp 00000000 fd:01 1447355    /lib/i386-linux-gnu/libpthread-2.15.so
005a8000-005a9000 r--p 00016000 fd:01 1447355    /lib/i386-linux-gnu/libpthread-2.15.so
005a9000-005aa000 rw-p 00017000 fd:01 1447355    /lib/i386-linux-gnu/libpthread-2.15.so
005aa000-005ac000 rw-p 00000000 00:00 0
005e9000-0064a000 r-xp 00000000 fd:01 654266     /usr/pluto/lib/libPlutoUtils.so
0064a000-0064b000 r--p 00061000 fd:01 654266     /usr/pluto/lib/libPlutoUtils.so
0064b000-0064d000 rw-p 00062000 fd:01 654266     /usr/pluto/lib/libPlutoUtils.so
00692000-0076a000 r-xp 00000000 fd:01 131619     /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16
0076a000-0076b000 ---p 000d8000 fd:01 131619     /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16
0076b000-0076f000 r--p 000d8000 fd:01 131619     /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16
0076f000-00770000 rw-p 000dc000 fd:01 131619     /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16
00770000-00777000 rw-p 00000000 00:00 0
00782000-0078d000 r-xp 00000000 fd:01 1454921    /lib/i386-linux-gnu/libnss_files-2.15.so
0078d000-0078e000 r--p 0000a000 fd:01 1454921    /lib/i386-linux-gnu/libnss_files-2.15.so
0078e000-0078f000 rw-p 0000b000 fd:01 1454921    /lib/i386-linux-gnu/libnss_files-2.15.so
007c4000-007e0000 r-xp 00000000 fd:01 1439086    /lib/i386-linux-gnu/libgcc_s.so.1
007e0000-007e1000 r--p 0001b000 fd:01 1439086    /lib/i386-linux-gnu/libgcc_s.so.1
007e1000-007e2000 rw-p 0001c000 fd:01 1439086    /lib/i386-linux-gnu/libgcc_s.so.1
00887000-008c1000 r-xp 00000000 fd:01 654944     /usr/pluto/lib/libMessageTranslation.so
008c1000-008c2000 r--p 0003a000 fd:01 654944     /usr/pluto/lib/libMessageTranslation.so
008c2000-008c3000 rw-p 0003b000 fd:01 654944     /usr/pluto/lib/libMessageTranslation.so
008c3000-008c4000 rw-p 00000000 00:00 0
0093a000-0093d000 r-xp 00000000 fd:01 1455565    /lib/i386-linux-gnu/libdl-2.15.so
0093d000-0093e000 r--p 00002000 fd:01 1455565    /lib/i386-linux-gnu/libdl-2.15.so
0093e000-0093f000 rw-p 00003000 fd:01 1455565    /lib/i386-linux-gnu/libdl-2.15.so
00a20000-00a21000 r-xp 00000000 00:00 0          [vdso]
00a40000-00cdc000 r-xp 00000000 fd:01 135635     /usr/lib/i386-linux-gnu/libmysqlclient.so.18.0.0
00cdc000-00cdf000 r--p 0029c000 fd:01 135635     /usr/lib/i386-linux-gnu/libmysqlclient.so.18.0.0
00cdf000-00d55000 rw-p 0029f000 fd:01 135635     /usr/lib/i386-linux-gnu/libmysqlclient.so.18.0.0
00d55000-00d58000 rw-p 00000000 00:00 0
00d58000-00efb000 r-xp 00000000 fd:01 1455578    /lib/i386-linux-gnu/libc-2.15.so
00efb000-00efd000 r--p 001a3000 fd:01 1455578    /lib/i386-linux-gnu/libc-2.15.so
00efd000-00efe000 rw-p 001a5000 fd:01 1455578    /lib/i386-linux-gnu/libc-2.15.so
00efe000-00f01000 rw-p 00000000 00:00 0
00f2c000-00f33000 r-xp 00000000 fd:01 1455485    /lib/i386-linux-gnu/librt-2.15.so
00f33000-00f34000 r--p 00006000 fd:01 1455485    /lib/i386-linux-gnu/librt-2.15.so
00f34000-00f35000 rw-p 00007000 fd:01 1455485    /lib/i386-linux-gnu/librt-2.15.so
08048000-080b3000 r-xp 00000000 fd:01 552583     /usr/pluto/bin/Generic_Serial_Device
080b3000-080b4000 r--p 0006b000 fd:01 552583     /usr/pluto/bin/Generic_Serial_Device
080b4000-080b5000 rw-p 0006c000 fd:01 552583     /usr/pluto/bin/Generic_Serial_Device
09364000-09478000 rw-p 00000000 00:00 0          [heap]
b4800000-b4828000 rw-p 00000000 00:00 0
b4828000-b4900000 ---p 00000000 00:00 0
b4a00000-b4afa000 rw-p 00000000 00:00 0
b4afa000-b4b00000 ---p 00000000 00:00 0
b4bff000-b4c00000 ---p 00000000 00:00 0
b4c00000-b5400000 rw-p 00000000 00:00 0
b5400000-b545e000 rw-p 00000000 00:00 0
b545e000-b5500000 ---p 00000000 00:00 0
b5538000-b55dc000 rw-p 00000000 00:00 0
b55ff000-b5600000 ---p 00000000 00:00 0
b5600000-b5e00000 rw-p 00000000 00:00 0
b5e00000-b5e21000 rw-p 00000000 00:00 0
b5e21000-b5f00000 ---p 00000000 00:00 0
b5f1f000-b5f20000 ---p 00000000 00:00 0
b5f20000-b6720000 rw-p 00000000 00:00 0
b6720000-b6721000 ---p 00000000 00:00 0
b6721000-b6f21000 rw-p 00000000 00:00 0
b6f21000-b6f22000 ---p 00000000 00:00 0
b6f22000-b7728000 rw-p 00000000 00:00 0
b773d000-b773e000 rw-p 00000000 00:00 0
b773e000-b773f000 ---p 00000000 00:00 0
b773f000-b7746000 rw-p 00000000 00:00 0
bfe5b000-bfe7c000 rw-p 00000000 00:00 0          [stack]


[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html

/usr/pluto/bin/Spawn_Device.sh: line 170: 17427 Aborted                 (core dumped) /usr/pluto/bin/Spawn_Wrapper.sh "$Path$cmd_line" -d "$device_id" -r "$ip_of_router" -l "$LogFile"
LOG: Return code: 134
3       08/20/15 22:23:57       189 (spawning-device)   Device died... count=40/50 dev=189
3       08/20/15 22:23:57       189 (spawning-device)   Device died... count=40/50 dev=189
LOG: Thu Aug 20 22:23:58 EDT 2015 died
^C
[screen is terminating]


It's 12.04 updated to the latest GSD package and Ruby 1.9.1. The GSD device is segfaulting. Someone more knowledgeable about the GSD device and C have any ideas?

Thanks!

/Mike
67
Developers / Re: Link Aggregation in LMCE
« Last post by Armor Gnome on August 21, 2015, 12:06:14 am »
Being my first project involving true development for LMCE and not just testing or basic feature troubleshooting the research type legwork I am referring to is a better understand of key concepts you all know second hand.  UDEV, modprobe, install order etc are all things I will want to look at before I brush up on bash and dig down to rough in something that not just works but makes sense at every level.

I'm still looking at a few weeks or more until I am ready to begin initial testing and hacking something in to test it manually.  I may be ignorant or unrealistically hopeful but I believe with available information from different sources I can get it working with direct manipulation after installation and my challenge will be in making it sharable as something other than a dirty hack.   Another first for me would be ensuring that any needed packages are available in supported repos and that I understand that process in detail.

You've all been very supportive and helpful so far.  I hope that my desire to understand this process better before I dive in and get stuck shows I appreciate it.
68
Developers / Re: Slow and steady ... moving from Trac to Gitlab
« Last post by phenigma on August 20, 2015, 08:59:43 pm »
Haven't been testing it yet.  Soon...  You'll have 1000 tickets to act on when you get back ;)

J.
69
Users / Re: Need some dedicated testers.
« Last post by golgoj4 on August 20, 2015, 07:39:32 pm »
I got the new qorbiter  and I like the way it looks....however I seem to have some trouble using it. When I want to watch my tv-shows, and select that from  videos, the list seems quite chaotic, so I switch to filenames, but with the new qorbiter, the buttons for this don't work.

I will take a look @ this. Im assuming the tv shows are tagged?
70
Developers / Re: Slow and steady ... moving from Trac to Gitlab
« Last post by polly on August 20, 2015, 08:33:25 am »
No issues at all? ... can't be! ;-)
Pages: 1 ... 5 6 [7] 8 9 10