New network manager is exist bug.

You have a problem with Salix? Post here and we'll do what we can to help.
zw963
Posts: 82
Joined: 13. Mar 2014, 18:36

New network manager is exist bug.

Post by zw963 »

Only myself alone occur this bug?

behavior is:

in some case, especially when noontime, to have a lunch, my laptop is auto run screen
saver, when I come back, I often found, network manager icon is disconnect, could not
found any WiFi hot point, close and reenable network/wifi, still show disconnect. (red X)
(but in fact, I could still access network with WiFi.)
zw963
Posts: 82
Joined: 13. Mar 2014, 18:36

Re: New network manager is exist bug.

Post by zw963 »

This only happen after a recent update from salix.
User avatar
mimosa
Salix Warrior
Posts: 3311
Joined: 25. May 2010, 17:02
Contact:

Re: New network manager is exist bug.

Post by mimosa »

Maybe this will help:

viewtopic.php?f=30&t=7284
westms
Posts: 298
Joined: 17. Mar 2013, 18:51

Re: New network manager is exist bug.

Post by westms »

This page left intentionally blank
Last edited by westms on 23. Sep 2017, 13:52, edited 1 time in total.
zw963
Posts: 82
Joined: 13. Mar 2014, 18:36

Re: New network manager is exist bug.

Post by zw963 »

mimosa wrote:Maybe this will help:

viewtopic.php?f=30&t=7284

Not see that link carefully, But i think I use dhcp serve by router.
zw963
Posts: 82
Joined: 13. Mar 2014, 18:36

Re: New network manager is exist bug.

Post by zw963 »

Rather, it is a problem with the Advanced Configuration and Power Interface events (ACPI). Depending on how low the ACPI state in the power management is caused by the Xscreensaver
I install salix in my laptop, but I could not found any power tray icon showed in my panel. (only user name + network manager)
and, when this issue happen, I never use battery, the power is full.
(but in fact, I could still access network with WiFi.)
Maybe this describe not accurate, when I back, network manager is disconnect.
I could not connect to internet, after toggle `Enable networking` option,
Wifi is connected, But the icon is still keep red X, today all afternoon, keep this status
I even don't know I connect to which hot point .... I have no idea to controller which
wifi hot point to connect, But when I connect with `eth0', the icon is show connected.
By the way, what does "recent update from salix" mean to you? You may have damaged a configuration or the interrelations in the Salix installation.
I don't remember which update caused this, I just remember I have network-manager update.
I don't know where to read update log, following is the recently installed packag, sort by time DESC:

-

Code: Select all

rw-r--r-- 1 root root  2370148 2017-04-27 03:03 ./patches/packages/xfce4-weather-plugin-0.8.9-x86_64-1_slack14.2.txz
-rw-r--r-- 1 root root   975088 2017-04-24 17:32 ./salix/xap/network-manager-applet-1.2.6-x86_64-1gv.txz
-rw-r--r-- 1 root root  3776492 2017-04-24 17:29 ./salix/n/NetworkManager-1.2.6-x86_64-1gv.txz
-rw-r--r-- 1 root root   127232 2017-04-24 17:27 ./salix/ap/salixtools-1.11.1-noarch-1gv.txz
-rw-r--r-- 1 root root   160320 2017-04-24 16:52 ./salix/ap/slapt-get-0.10.2t-x86_64-2gv.txz
-rw-r--r-- 1 root root  1992104 2017-04-21 01:49 ./patches/packages/ntp-4.2.8p10-x86_64-1_slack14.2.txz
-rw-r--r-- 1 root root  4709376 2017-04-12 16:40 ./salix/l/flash-plugin-25.0.0.148-x86_64-1gv.txz
-rw-r--r-- 1 root root   445384 2017-04-08 03:31 ./patches/packages/libtiff-4.0.7-x86_64-1_slack14.2.txz
-rw-r--r-- 1 root root 10854352 2017-04-01 05:22 ./patches/packages/samba-4.4.13-x86_64-1_slack14.2.txz
-rw-r--r-- 1 root root 50366000 2017-03-29 02:04 ./patches/packages/mozilla-firefox-52.0.2esr-x86_64-1_slack14.2.txz
-rw-r--r-- 1 root root 26572068 2017-03-27 03:14 ./patches/packages/mariadb-10.0.30-x86_64-1_slack14.2.txz
-rw-r--r-- 1 root root 10854232 2017-03-24 02:59 ./patches/packages/samba-4.4.12-x86_64-1_slack14.2.txz
-rw-r--r-- 1 root root  4700232 2017-03-16 18:18 ./salix/l/flash-plugin-25.0.0.127-x86_64-1gv.txz
-rw-r--r-- 1 root root  6431428 2017-03-11 03:16 ./patches/packages/pidgin-2.12.0-x86_64-1_slack14.2.txz
-rw-r--r-- 1 root root 48636000 2017-03-07 17:35 ./salix/xap/mozilla-firefox-45.8.0esr-x86_64-1gv.txz
-rw-r--r-- 1 root root   117784 2017-03-02 03:04 ./patches/packages/libcgroup-0.41-x86_64-2_slack14.2.txz
-rw-r--r-- 1 root root  7199360 2017-02-17 18:53 ./salix/xap/ffmpeg-3.0.7-x86_64-2gv.txz
-rw-r--r-- 1 root root  5244320 2017-02-15 17:23 ./salix/l/flash-plugin-24.0.0.221-x86_64-1gv.txz
-rw-r--r-- 1 root root  7204012 2017-02-12 17:24 ./salix/xap/ffmpeg-3.0.7-x86_64-1gv.txz
-rw-r--r-- 1 root root   366140 2017-02-11 04:55 ./patches/packages/tcpdump-4.9.0-x86_64-1_slack14.2.txz
-rw-r--r-- 1 root root   274848 2017-02-11 04:52 ./patches/packages/libpcap-1.8.1-x86_64-1_slack14.2.txz
-rw-r--r-- 1 root root   424984 2017-02-10 11:54 ./slackware64/a/lilo-24.2-x86_64-2.txz
-rw-r--r-- 1 root root  7198256 2017-02-07 16:21 ./salix/xap/ffmpeg-3.0.6-x86_64-1gv.txz
-rw-r--r-- 1 root root  1069532 2017-02-04 05:33 ./patches/packages/openssl-solibs-1.0.2k-x86_64-1_slack14.2.txz
-rw-r--r-- 1 root root  3542620 2017-02-04 05:33 ./patches/packages/openssl-1.0.2k-x86_64-1_slack14.2.txz
-rw-r--r-- 1 root root 48592880 2017-01-31 19:25 ./salix/xap/mozilla-firefox-45.7.0esr-x86_64-1gv.txz
-rw-r--r-- 1 root root 63038720 2017-01-31 16:30 ./chromium/chromium-56.0.2924.76-x86_64-1alien.txz
-rw-r--r-- 1 root root 26550132 2017-01-19 03:58 ./patches/packages/mariadb-10.0.29-x86_64-1_slack14.2.txz
-rw-r--r-- 1 root root  5246124 2017-01-12 05:09 ./salix/l/flash-plugin-24.0.0.194-x86_64-1gv.txz
-rw-r--r-- 1 root root  2414244 2017-01-11 09:30 ./patches/packages/gnutls-3.5.8-x86_64-1_slack14.2.txz
-rw-r--r-- 1 root root  5228436 2017-01-11 05:15 ./chromium-pepperflash-plugin/pkg64/14.1/chromium-pepperflash-plugin-24.0.0.194-x86_64-1alien.txz
-rw-r--r-- 1 root root 14379636 2017-01-09 01:55 ./patches/packages/python-2.7.13-x86_64-2_slack14.2.txz
-rw-r--r-- 1 root root  1444692 2017-01-06 20:27 ./salix/xap/zim-0.65-x86_64-2gv.txz
I think this bug is occur after update following package:

Code: Select all

-rw-r--r-- 1 root root   975088 2017-04-24 17:32 ./salix/xap/network-manager-applet-1.2.6-x86_64-1gv.txz
-rw-r--r-- 1 root root  3776492 2017-04-24 17:29 ./salix/n/NetworkManager-1.2.6-x86_64-1gv.txz
BTW: from I install salix, I could not see many icon in start menu, panel, and even directory icon in file manager is
is not showed , I have to try to run sorts of command to restoredesktop icons, no effect, but after recent update,
all icons is showed, I think this issue initial caused by my home directory is shared, because my laptop all linux
distribution shared one home partition, anywhy, this is worked now.
User avatar
gapan
Salix Wizard
Posts: 6241
Joined: 6. Jun 2009, 17:40

Re: New network manager is exist bug.

Post by gapan »

You can find the previous version of the packages here:
http://backup.salixos.org/monthly.4/rep ... 64-1gv.txz
http://slackware.uk/slackware/slackware ... 6_64-2.txz

If you believe that the upgrade is the cause for this, install the old packages and see if it still happens.
Image
Image
User avatar
mimosa
Salix Warrior
Posts: 3311
Joined: 25. May 2010, 17:02
Contact:

Re: New network manager is exist bug.

Post by mimosa »

Not see that link carefully, But i think I use dhcp serve by router.
Well, if other suggestions don't work, it may be worth a try. It probably makes no difference to NM what your router is using.
westms
Posts: 298
Joined: 17. Mar 2013, 18:51

Re: New network manager is exist bug.

Post by westms »

This page left intentionally blank
Last edited by westms on 23. Sep 2017, 13:53, edited 1 time in total.
westms
Posts: 298
Joined: 17. Mar 2013, 18:51

Re: New network manager is exist bug.

Post by westms »

This page left intentionally blank
Last edited by westms on 23. Sep 2017, 13:53, edited 1 time in total.
Post Reply