LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Closed Thread
  Search this Thread
Old 05-28-2016, 06:32 PM   #1111
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 2,338

Rep: Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930

Quote:
Originally Posted by Drakeo View Post
I really hope Pat does something with Network manager. It will not do a simple dhcpcd . Before everyone jumps on this and says I do not understand it.
Network manager has three things to do
1 bring the device up
2 make a hand shake
3 use crypto or not.
Other wise it prety much useless.
If it works for you on a fresh install I am on mars then.
Me and Bob sucking down some some cosmic babes.
I comment in some threads

1 - service not stopped if use more than 1 time , only aparently works the first time , later cant manage wireless devices
2 - dhcpcd for some users no work , need change to dhcp , and dhcp=internal , i think no work for no one.
3 - if want system autoconnect to your wifi at start time, need to check ..."all can connect to this network" ...or no connect on start up


all seems to be related to some permission problem, the question is

where ?
 
Old 05-28-2016, 07:29 PM   #1112
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
Blog Entries: 3

Rep: Reputation: 483Reputation: 483Reputation: 483Reputation: 483Reputation: 483
wow thanks for the wonderful reply. I just want it to work on a simple wired line.
I can just use default dhcpcd /etc/rc.inet1 but you know what caused this weird thing while I was a work.
I have a shop by my home out back hre on campus. Att came in to add the Uverse phone to my modem.
The guy was so nice as he set my modem back to factory reset.
heck who cares about the 2 severs and a virtual world simulator that we develop on.
His little laptop said reset. Which took me about ten hours of getting with people that used that UUID.
after that it screwed up. Had to just use /etc/rc.d/rc.inet.1 just wonder why after this last
networkmanager update that it no longer does what it is designed to do.
I am telling you it is a conspiracy and I need a cosmic babe.

Last edited by Drakeo; 05-28-2016 at 07:39 PM.
 
1 members found this post helpful.
Old 05-28-2016, 07:37 PM   #1113
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,558
Blog Entries: 15

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
Dhcpcd has really been fickle with NetworkManager. Nothing new really. The issue for me really was prevalent and noticeable when I tried out the SBo OpenRC script and init helper set. Dhcpcd just would not work period.

As UsuarioNuevo said, try dhcp=internal or dhcp=dhclient in the configuration file. Dhclient from the dhcp package tends to be more sane in how it operates. If you use dhcpcd, just use it by itself from netconfig.
 
Old 05-29-2016, 03:40 AM   #1114
DarkVision
Member
 
Registered: Jul 2007
Posts: 199

Rep: Reputation: Disabled
XScreenSaver updated to 5.35.

Note: /usr/man/man6/maze.6.gz will replace the same file included in xgames-0.3. I suggest either rename maze from xscreensaver to xmaze and the manpage to xmaze.6.gz or do something similar for xgames.

The no-expiration-patch for xscreensaver needs to be updated because it does not apply to the new sources. Updated patch :
Code:
diff -U3 -d -r -N xscreensaver-5.35/driver/prefs.c xscreensaver-5.35.fixed/driver/prefs.c
--- xscreensaver-5.35/driver/prefs.c	2016-05-24 05:08:27.000000000 +0200
+++ xscreensaver-5.35.fixed/driver/prefs.c	2016-05-29 10:29:07.578127838 +0200
@@ -1734,6 +1734,14 @@
      shipping the last version with the old license and then never
      upgrading it again -- which would be the worst possible outcome for
      everyone involved, most especially the users.
+
+     NOTE:  This feature is disabled by Slackware...  we do not ship multi-year
+     old versions, nor do we think it is a good idea to include nag screens
+     that activate when an expiration date is reached.  In this case, the
+     nag screen was activated after only one year, which practically insures
+     that this will be seen before the next stable Slackware release.
+     If there's a problem that needs fixing, we'll issue a fix.
+     No nag screens please.  Thanks for possibly reconsidering this!
   */
 
   time_t now = time ((time_t *) 0);				/*       */
@@ -1766,5 +1774,7 @@
   months = ((((tm->tm_year + 1900) * 12) + tm->tm_mon) -	/*   h   */
             (y * 12 + m));					/*   p   */
 							  	/*   .   */
-  return (months >= 17);					/*       */
+  /* Disable date checking for Slackware:  */
+  /* return (months >= 17); */
+  return ( 0 );
 }
Attached Files
File Type: txt xscreensaver.no.expiration.date.diff.txt (1.3 KB, 8 views)

Last edited by DarkVision; 05-29-2016 at 03:52 AM. Reason: Added patch file...
 
Old 05-29-2016, 04:04 AM   #1115
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 948

Rep: Reputation: Disabled
Hi,

I don't remember having issues using NetworkManager, so my guess is that it's hardware related stuff.
I have flawless operation using Ethernet, WiFi and mobile broadband.

Code:
$ /sbin/lspci
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) I218-V (rev 03)
02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
For mobile broadband I'm using Samsung GT-B2710.

Code:
$ cat /etc/NetworkManager/NetworkManager.conf
# /etc/NetworkManager/NetworkManager.conf
#
# See additional config files (such as for DHCP settings) in ./conf.d

$ cat /etc/NetworkManager/conf.d/00-dhcp-client.conf 
[main]
# Choose a DHCP client below.  Upstream recommends dhclient, but results may vary.
# dhcpcd is the DHCP client usually used by Slackware:
dhcp=dhcpcd
# dhclient is the ISC reference DHCP client, part of the dhcp package:
#dhcp=dhclient
# This is a simple DHCP client that is built into NetworkManager:
#dhcp=internal

$ cat /etc/NetworkManager/conf.d/00-rc-manager.conf 
[main]
rc-manager=file
I don't have a need to restart NM daemon, so I really don't know how it behaves after restarting.

Quote:
3 - if want system autoconnect to your wifi at start time, need to check ..."all can connect to this network" ...or no connect on start up
Isn't it sufficient to set the "Automatically connect to this network when it is available" ?

--
Best regards,
Andrzej Telszewski
 
Old 05-29-2016, 04:22 AM   #1116
DarkVision
Member
 
Registered: Jul 2007
Posts: 199

Rep: Reputation: Disabled
python-setuptools updated to 21.2.1

I think that SlackBuild requires the following patch for tar.gz files:
Code:
diff -U3 -d -r -N python-setuptools/python-setuptools.SlackBuild python-setuptools.fixed/python-setuptools.SlackBuild
--- python-setuptools/python-setuptools.SlackBuild	2015-10-15 22:40:29.000000000 +0200
+++ python-setuptools.fixed/python-setuptools.SlackBuild	2016-05-29 11:18:50.839298352 +0200
@@ -43,7 +43,7 @@
 mkdir -p $TMP $PKG
 cd $TMP
 rm -rf $SRCNAM-$VERSION
-tar xvf $CWD/$SRCNAM-$VERSION.tar.xz || exit 1
+tar xvf $CWD/$SRCNAM-$VERSION.tar.?z* || exit 1
 cd $SRCNAM-$VERSION || exit 1
 chown -R root:root .
 find -L . \
Attached Files
File Type: txt python-setuptools-21.2.1.diff.txt (533 Bytes, 7 views)
 
Old 05-29-2016, 04:56 AM   #1117
DarkVision
Member
 
Registered: Jul 2007
Posts: 199

Rep: Reputation: Disabled
gdk-pixbuf2 updated to 2.34.

Note: The sources are available as .tar.xz only but the Slackbuild script is using different search patterns for the source version (tar.?z*) and the tar archive (tar.xz). This minor issue is similar to the python-setuptools patch. Suggested patch:
Code:
diff -U3 -d -r -N gdk-pixbuf2/gdk-pixbuf2.SlackBuild gdk-pixbuf2.fixed/gdk-pixbuf2.SlackBuild
--- gdk-pixbuf2/gdk-pixbuf2.SlackBuild	2015-09-01 21:25:48.000000000 +0200
+++ gdk-pixbuf2.fixed/gdk-pixbuf2.SlackBuild	2016-05-29 11:49:56.810878203 +0200
@@ -59,7 +59,7 @@
 mkdir -p $TMP $PKG
 cd $TMP
 rm -rf $PKGNAM-$VERSION
-tar xvf $CWD/$PKGNAM-$VERSION.tar.xz || exit 1
+tar xvf $CWD/$PKGNAM-$VERSION.tar.?z* || exit 1
 cd $PKGNAM-$VERSION || exit 1
 chown -R root:root .
 find . \
Attached Files
File Type: txt gdk-pixbuf2-2.34.0.diff.txt (482 Bytes, 6 views)
 
1 members found this post helpful.
Old 05-29-2016, 10:00 AM   #1118
DarkVision
Member
 
Registered: Jul 2007
Posts: 199

Rep: Reputation: Disabled
OK, just a minor, really minor and more cosmetic fix:
Some packages seem to set the package version using a search pattern like '.tar.?z*' which includes tar.xz, .tar.bz2 and .tar.gz. On the other hand the SlackBuilds are using a hardcoded .tar.xz command to untar the sources. Examples are here and here.

A small and quick dirty fix (not recommended) would be to use the following sed-command:
Code:
find -name "*.SlackBuild" -exec grep -H -c -e ".tar.?x*" -e ".tar.xz" {} \; | grep -v ":1$" | sed "s,:.*,,g" | xargs sed -i "s,.tar.xz ||,.tar.?x* ||,"
I'm sure the above command can be fixed to add a variable using the search pattern and fix the two locations of the archive format using that variable. This is just a first try:
Code:
find -name "*.SlackBuild" -exec grep -H -c -e "^VERSION=.*.tar.?z*" {} \; | grep ":1$" | sed "s,:.*,,g" | xargs grep -H -m1 -e "^tar.*tar.xz" | sed "s,:.*,,g" | xargs sed -i -e "/^VERSION=/ iPKGTAR=tar.?z*" -e "s,\.tar.?z\* |,.\$PKGTAR |,g" -e "s,.tar.xz |,.\$PKGTAR |,g" -e "s,.tar.xz,.\$PKGTAR,g"
I made a diff from -current as of 'Fri May 27 23:08:17 UTC 2016' using the above command, see attached txt. No guarantee that it will match -current
Attached Files
File Type: txt slackware64-current-fix_search_pattern_v9.txt (85.1 KB, 26 views)
 
1 members found this post helpful.
Old 05-29-2016, 12:06 PM   #1119
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 11,241

Rep: Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322Reputation: 5322
I can tell you what I'd definitely like to see not only in -current, but in 14.2: the tmux and tmux-256color terminfo entries.

The correct way to set up tmux these days is to set the following in tmux.conf:

Code:
set -g default-terminal "tmux-256color"
That gets you both italic support and 256-color support.

For that to work, you need the tmux-256 terminfo entry. Slackware doesn't include it, so as per tmux/FAQ, you need to generate it manually with:


Code:
cat <<EOF|tic -x -
tmux|tmux terminal multiplexer,
	ritm=\E[23m, rmso=\E[27m, sitm=\E[3m, smso=\E[7m, Ms@,
	use=xterm+tmux, use=screen,

tmux-256color|tmux with 256 colors,
	use=xterm+256setaf, use=tmux,
EOF
That creates the following files:
  • ~/.terminfo/t/tmux
  • ~/.terminfo/t/tmux-256color

Slackware should ship them and have them in /usr/share/terminfo.

This is true for tmux 2.1 and above. 14.2 has 2.1.

Last edited by dugan; 05-29-2016 at 12:14 PM.
 
6 members found this post helpful.
Old 05-29-2016, 02:16 PM   #1120
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 2,338

Rep: Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930
Quote:
Isn't it sufficient to set the "Automatically connect to this network when it is available" ?
no

if no check "all can connect" .. no auto conection at start time..need connect manually , this is not new , is comment some times in forum.
 
Old 05-29-2016, 04:30 PM   #1121
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
Blog Entries: 3

Rep: Reputation: 483Reputation: 483Reputation: 483Reputation: 483Reputation: 483
Quote:
Dhcpcd has really been fickle with NetworkManager. Nothing new really. The issue for me really was prevalent and noticeable when I tried out the SBo OpenRC script and init helper set. Dhcpcd just would not work period.
Thanks ReaperX7 I will fiddle with it. Jiggle the handle LOL. I am sure it isn't writing to the /etc/NetworkManager/NetworkManager.conf
I also think it has to do with kwallet on user level as root it should not have been a problem. I Think.
 
Old 05-29-2016, 06:40 PM   #1122
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,558
Blog Entries: 15

Rep: Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097Reputation: 2097
Yeah, I'm not sure why it seems to work with Slackware's bsd-init scripts, but with OpenRC it doesn't work until you switch it to dhclient. It's still problematic, and each time I fiddle with the package, I check the NetworkManager.conf and reset the dhcp backend to dhclient.
 
Old 05-29-2016, 09:02 PM   #1123
alex14641
Member
 
Registered: Feb 2016
Distribution: Slackware64_14.2, Slackware 15.0, Slackware64_current
Posts: 322

Rep: Reputation: Disabled
blueman 2.0.4 is out. https://github.com/blueman-project/b...hive/2.0.4.zip
 
Old 05-30-2016, 02:06 AM   #1124
Thom1b
Member
 
Registered: Mar 2010
Location: France
Distribution: Slackware
Posts: 485

Rep: Reputation: 339Reputation: 339Reputation: 339Reputation: 339
curl-7.49.1 is released.

https://curl.haxx.se/download/curl-7.49.1.tar.bz2
https://curl.haxx.se/download/curl-7.49.1.tar.bz2.asc
 
Old 05-30-2016, 04:49 AM   #1125
OldHolborn
Member
 
Registered: Jul 2012
Posts: 229

Rep: Reputation: 190Reputation: 190
@Dugan

& urxvt
 
  


Closed Thread



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
[SOLVED] how to show the current time at the top in the current shell Always ? rohitchauhan Linux - General 5 04-09-2014 03:05 PM
Slackware ARM (current) epic mistake: the current Android kernels are kicked out! Darth Vader Slackware 16 08-25-2013 04:36 PM
[SOLVED] setup fails on most current Slackware-current March 26, 2012 AlleyTrotter Slackware 15 04-09-2012 06:05 AM
Observation of Feb -current vs March -current Hangaber Slackware 14 03-12-2010 08:26 AM
cvs diff the most current and second last current version powah Linux - Software 1 03-30-2006 01:02 PM

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

All times are GMT -5. The time now is 03:39 PM.

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