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.
Robby, I've often wondered, do you have scripts you like to use for testing Slackware? Or do you exercise individual packages by hand and look around for signs of trouble?
No scripts :-)
If it passes the "works for me" test and there aren't any obvious issues, it gets queued up. Sometimes it fails the "works for volkerdi" test or the "works for some other team member" test, and so we regroup and take another look :-)
nfs-utils >= 1.3.0 wont compile on current with nfs4 and krb5 support. Looks like keyutils is too old. If you are going to upgrade nfs-utils could you look at keyutils too.
keyutils-1.5.5 > 1.5.9
Got it; thanks! Do you use nfs4 (I'm guessing you rebuild nfs-utils then??) I'd love to see a writeup on the slackdocs wiki about nfs4...
---------- Post added Dec 23rd, 2014 at 13:17 ----------
Quote:
Originally Posted by ReaperX7
All the alsa related packages are now at version 1.0.28 with the exception of pyalsa-1.0.26.
By the way, why is that Doxygen is at 1.8.5 (release date 23-08-2013).
When I tried to build weston or libinput (don't remember really) there were some warnings about missing flags (as in not supported) from doxygen.
On latest version warnings were gone. Perhaps latest version (1.8.8) should be tested and added?
[QUOTE=rworkman;5289668]Done, but I haven't used wicd in quite some time, so I'd like someone to confirm that these work.../QUOTE]
Robby thanks for the upgrade on wicd,
Here is some feedbacks on my machine (slackware64-current with xfce4 as window manager, no KDE4 stuff whatsoever).
The wicd icon is not displayed in the taskbar (I've got a white/blank icon with a red cross in It) but the GTK interface works.
The "curses" interface (in a terminal) wouldn't start.
A basic test would be to launch wicd in a terminal like this:
Code:
$ wicd-curses
I tested with urwid-1.0.2, urwid-1.1.2, urwid-1.2.2, with all these releases I could use wicd in a terminal, nonetheless only urwid-1.0.2 works properly, with the others wicd display errors on quitting like these:
Code:
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
---------- Post added Dec 23rd, 2014 at 15:47 ----------
Quote:
Originally Posted by heiser891
By the way, why is that Doxygen is at 1.8.5 (release date 23-08-2013).
When I tried to build weston or libinput (don't remember really) there were some warnings about missing flags (as in not supported) from doxygen.
On latest version warnings were gone. Perhaps latest version (1.8.8) should be tested and added?
Done, but I haven't used wicd in quite some time, so I'd like someone to confirm that these work...
Robby thanks for the upgrade on wicd,
Here is some feedbacks on my machine (slackware64-current with xfce4 as window manager, no KDE4 stuff whatsoever).
The wicd icon is not displayed in the taskbar (I've got a white/blank icon with a red cross in It) but the GTK interface works.
I can't reproduce this - what you're seeing is the gtk stock "not found" icon. Is there someplace to declare a custom icon, and if so, do you have anything there? If not, see if you can find any icon mention in wicd's config directories (user-specific maybe) - we had a similar issue in upstream blueman after they did a similar change wrt using themed icons.
Quote:
The "curses" interface (in a terminal) wouldn't start.
A basic test would be to launch wicd in a terminal like this:
Code:
$ wicd-curses
I tested with urwid-1.0.2, urwid-1.1.2, urwid-1.2.2, with all these releases I could use wicd in a terminal, nonetheless only urwid-1.0.2 works properly, with the others wicd display errors on quitting like these:
Code:
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
Well, as far as I'm concerned, we'll just stay with 1.0.2 then.
That leads to a question: should I understand that brltty (requested in post #46, build material proposed in post #98) won't be upgraded, is not ready, or that no decision has been made yet (at least by yourself)?
Oh, and IMHO that would deserve to be moved from /extra to /slackware{,64}.
Last edited by Didier Spaier; 12-23-2014 at 04:10 PM.
That leads to a question: should I understand that brltty (requested in post #46, build material proposed in post #98) won't be upgraded, is not ready, or that no decision has been made yet (at least by yourself)?
Oh, and IMHO that would deserve to be moved from /extra to /slackware{,64}.
I've never touched the brltty code, and I don't think now is a good time to start. I'm going to leave that for volkerdi, as he's always been the one to mess with that, and I like it that way :-)
Just because I don't have something in my queue is not at all an indication that it isn't queued elsewhere or won't be later; it simply means that *I* haven't done anything with it.
I tried out your updated wicd-1.7.3, it seems to work for me here (checked wicd-gtk and wicd-curses).
However when I upgraded urwid, wicd-curses did not start and I got-
Code:
$ wicd-curses
Traceback (most recent call last):
File "/usr/share/wicd/curses/wicd-curses.py", line 1307, in <module>
main()
File "/usr/share/wicd/curses/wicd-curses.py", line 1224, in main
ui.run_wrapper(run)
File "/usr/lib64/python2.7/site-packages/urwid/display_common.py", line 757, in run_wrapper
return fn()
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 1234, in run
app = appGUI()
File "/usr/share/wicd/curses/wicd-curses.py", line 754, in __init__
self.update_status()
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 924, in update_status
self.set_status):
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 177, in check_for_wireless
('$C', ip))
File "/usr/share/wicd/curses/wicd-curses.py", line 974, in set_status
self.update_ui()
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 1156, in update_ui
input_data = ui.get_input_nonblocking()
AttributeError: 'Screen' object has no attribute '
xf86-video-intel was upgraded to 2.99.917 a few days ago. This version works better for me than the previous pre-release versions. No more glitches in firefox and fbpanel.
Done, but I haven't used wicd in quite some time, so I'd like someone to confirm that these work.../QUOTE]
Robby thanks for the upgrade on wicd,
Here is some feedbacks on my machine (slackware64-current with xfce4 as window manager, no KDE4 stuff whatsoever).
The wicd icon is not displayed in the taskbar (I've got a white/blank icon with a red cross in It) but the GTK interface works.
The "curses" interface (in a terminal) wouldn't start.
A basic test would be to launch wicd in a terminal like this:
Code:
$ wicd-curses
I tested with urwid-1.0.2, urwid-1.1.2, urwid-1.2.2, with all these releases I could use wicd in a terminal, nonetheless only urwid-1.0.2 works properly, with the others wicd display errors on quitting like these:
Code:
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
I had some issues with wicd-curses from 1.7.x and urwid 1.3 on my manjaro install. There was a patch at archlinux: https://projects.archlinux.org/svnto...cd3f4343dbf2fd
There is an update of wicd just a few days and have not tried it.
1.7.x had no issues with urwid 1.2.x on my manjaro install.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.