The what should be updated in -current thread

Originally Posted by aaditya With patched wicd-1.7.3 and urwid-1.3.0, wicd-curses seems to work here, but only partially.. wicd-curses showed up when executed, but the keyboard commands did not work, and when I pressed enter it started connecting, then crashed (it got connected as the wicd-gtk --tray icon turned green). The crashes seem reproducible here, whenever I press enter it connects/disconnects, but crashes. Here is the output: $ wicd-curses ERROR:dbus.connection:Exception in handler for D-Bus signal: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 230, in maybe_handle_message self._handler(*args, **kwargs) File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper return func(*args, **kargs) File "/usr/share/wicd/curses/wicd-curses.py", line 850, in update_netlist self.wiredCB.get_body().set_list(wiredL) File "/usr/share/wicd/curses/wicd-curses.py", line 469, in set_list wired.ReadWiredNetworkProfile(self.get_selected_profile()) File "/usr/share/wicd/curses/wicd-curses.py", line 535, in get_selected_profile return self.theList[loc] IndexError: list index out of range

On my machine, the program does not stop cleanly when It's been compiled with urwid-1.1.2, urwid-1.2.2, urwid-1.3.0, I get that kind of error.

Originally Posted by _gin On my machine, the program does not stop cleanly when It's been compiled with urwid-1.1.2, urwid-1.2.2, urwid-1.3.0, I get that kind of error.

I think this error could be because of the patch applied to it (wicd-curses), without the patch it did not start for me (with urwid-1.3.0).

diff --git a/curses/wicd-curses.py b/curses/wicd-curses.py
index 641aa52..603609b 100755
--- a/curses/wicd-curses.py
+++ b/curses/wicd-curses.py
@@ -927,9 +927,10 @@ class appGUI():
         if not ui._started:
             return False
 
-        input_data = ui.get_input_nonblocking()
+        ui.set_input_timeouts(max_wait=0)
+        input_data = ui.get_input()
         # Resolve any "alarms" in the waiting
-        self.handle_keys(input_data[1])
+        self.handle_keys(input_data)
 
         # Update the screen
         canvas = self.frame.render( (self.size),True )

Originally Posted by rworkman I think pprkut has that one.

Indeed I do. To extend rworkman's list, here's what I currently have in my queue:

boost
exiv2
fftw
flac
gc
icu4c
ilmbase
jemalloc
judy
libao
libcdio
libcdio-paranoia
libdiscid
libdvdread
liblastfm
libogg
libraw1394
libvncserver
libvorbis
llvm
mariadb
net-snmp
openexr
pcre
php
python-setuptools
wavpack
xine-ui
xsane
yasm

I also have updates for giflib, libwpd and xine (1.2) under testing, but they need some more time.

Originally Posted by ReaperX7 Does Slackware use anything other than Clang from the LLVM project?

My 3.5 update adds clang-tools-extra and compiler-rt. I had a look at lldb as well, but the fact that it's not really supported on 32bit linux yet made me wait a bit longer.

Is python-setuptools is the same as pysetuptools in SBo?

Originally Posted by willysr Is python-setuptools is the same as pysetuptools in SBo?

Yes. I changed the name to match what other distros are calling it.

Originally Posted by ppr:kut I also have updates for...xine (1.2) under testing...

Hi ppr:kut,

Out of curiosity, did you link xine-1.2.x with ffmpeg or libav, shared or static linking?

Originally Posted by _gin Hi ppr:kut, Out of curiosity, did you link xine-1.2.x with ffmpeg or libav, shared or static linking?

ffmpeg, statically linked

binutils 2.25 - http://ftp.gnu.org/gnu/binutils/?C=M;O=D

Originally Posted by aaditya I think this error could be because of the patch applied to it (wicd-curses), without the patch it did not start for me (with urwid-1.3.0). diff --git a/curses/wicd-curses.py b/curses/wicd-curses.py index 641aa52..603609b 100755 --- a/curses/wicd-curses.py +++ b/curses/wicd-curses.py @@ -927,9 +927,10 @@ class appGUI(): if not ui._started: return False - input_data = ui.get_input_nonblocking() + ui.set_input_timeouts(max_wait=0) + input_data = ui.get_input() # Resolve any "alarms" in the waiting - self.handle_keys(input_data[1]) + self.handle_keys(input_data) # Update the screen canvas = self.frame.render( (self.size),True )

Should we report upstream?

For wicd/urwid, we may be able to get something out of this:

https://bugzilla.redhat.com/show_bug.cgi?id=894646

https://bugzilla.redhat.com/attachme...81&action=diff

Originally Posted by heiser891 binutils 2.25 - http://ftp.gnu.org/gnu/binutils/?C=M;O=D

Try that once and you'll see that it's a clusterheadache. I'm leaving that one for volkerdi :-)

Originally Posted by ryanpcmcquen For wicd/urwid, we may be able to get something out of this: https://bugzilla.redhat.com/show_bug.cgi?id=894646 https://bugzilla.redhat.com/attachme...81&action=diff

I just pushed an update to the wicd directory linked earlier and included a couple of those patches, but I think the proper thing to do for now is leave urwid at 1.0.2 since everything works with it. I'm leaving the fix for urwid-1.3.0 in the build directory but commented out the line to apply it. Feel free to play around with it (and more importantly, someone should report a bug upstream), but until/unless things change, we'll keep urwid 1.0.2 for wicd.

Originally Posted by rworkman I just pushed an update to the wicd directory linked earlier and included a couple of those patches, but I think the proper thing to do for now is leave urwid at 1.0.2 since everything works with it. I'm leaving the fix for urwid-1.3.0 in the build directory but commented out the line to apply it. Feel free to play around with it (and more importantly, someone should report a bug upstream), but until/unless things change, we'll keep urwid 1.0.2 for wicd.

Thanks Robby. There is also urwid 1.0.3 that was released on github only, but in my testing it has the same issue as 1.3.0.

Originally Posted by rworkman Try that once and you'll see that it's a clusterheadache. I'm leaving that one for volkerdi :-)

fair enough, just wanted to point out that there is a fresh update.

Originally Posted by rworkman I just pushed an update to the wicd directory linked earlier and included a couple of those patches, but I think the proper thing to do for now is leave urwid at 1.0.2 since everything works with it. I'm leaving the fix for urwid-1.3.0 in the build directory but commented out the line to apply it. Feel free to play around with it (and more importantly, someone should report a bug upstream), but until/unless things change, we'll keep urwid 1.0.2 for wicd.

I think thats the simpler option.

Originally Posted by ryanpcmcquen Should we report upstream?

I dont use wicd-curses much, but there is an upstream report I found:
https://bugs.launchpad.net/wicd/+bug/1075399

I added a comment there.