You are not logged in.

#301 2016-09-06 00:21:41

KrunchTime
Member
Registered: 2015-09-29
Posts: 857

Re: Tracking Debian testing/unstable with BunsenLabs

Head_on_a_Stick wrote:

Does the connection work if you add the details to /etc/network/interfaces and use `ifup wlps30`?

The stanza should look something like this:

auto wlp3s0
iface wlan0 inet dhcp
        wpa-ssid name_of_the_access_point
        wpa-psk the_password

No go.  Running

sudo ifup wlp3s0

produces the following output:

Internet Systems Consortium DHCP Client 4.3.4
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlp3s0/[MAC obfuscated]
Sending on   LPF/wlp3s0/[MAC obfuscated]
Sending on   Socket/fallback
DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
grep: /etc/resolv.conf: No such file or directory

Also, according to the Debian Wiki page pertaining to WiFi, I should have been able to setup an appropriately named interface file under /etc/network/interfaces.d, but I couldn't get that to work.  I resorted to just modifying /etc/network/interfaces.

Last edited by KrunchTime (2016-09-06 00:25:40)

Offline

#302 2016-09-06 06:54:50

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 8,759
Website

Re: Tracking Debian testing/unstable with BunsenLabs

Can you downgrade NetworkManager to the last version?

That is what I would do in Arch but I'm not sure if that's the "done thing" with Debian testing/unstable.

# dpkg --install --force-downgrade /var/cache/apt/archives/network-manager_version.deb

Replace "network-manager_version.deb" with the actual name of the .deb file -- tab completion is your friend here!
smile

Perhaps seek advice over at the siduction forums first though...

EDIT: Also, your /etc/resolv.conf is missing (it is usually created by NetworkManager), you can autogenerate one with:

# apt install resolvconf

Last edited by Head_on_a_Stick (2016-09-06 07:12:01)


“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII., 18.

Forum Rules   •   How to report a problem   •   Software that rocks

Offline

#303 2016-09-06 07:49:34

KrunchTime
Member
Registered: 2015-09-29
Posts: 857

Re: Tracking Debian testing/unstable with BunsenLabs

@HoaS:  Downgrade...might be possible to pull the version from Testing, but I run autoclean after each dist-upgrade, so no downgrading from my local downloads.  I might just suffer the inconvenience of being tethered to an ethernet cable until the Debian developers sort this out.

Siduction forums...posted as an upgrade warning, but no input from anyone about possible workarounds.

Thank you for pointing out how to resolve the issue with a missing /etc/resolv.conf.

Offline

#304 2016-09-06 08:21:07

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 8,759
Website

Re: Tracking Debian testing/unstable with BunsenLabs

Thinking about this a little more, `ifup` fails on the DHCP stage so you could try using static IPs instead.

Find the current IP range by loading up the BunsenLabs live ISO and running `ip r` after you have connected to your wireless access point.

The output should look something like this:

empty@alpine ~ % ip r
default via 192.168.1.254 dev wlan0
192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.17

In this case, "192.168.1.17" is the IP address assigned to this box, "192.168.1.254" is the gateway (ie, the IP address of the wireless router) and "/24" defines the netmask -- the non-CIDR equivalent is 255.255.255.0

You can then take these numbers and add them to /etc/network/interfaces and substitute "dhcp" for "static", like this:

auto wlp3s0
iface wlan0 inet static
        address 192.168.1.17
        netmask 255.255.255.0
        gateway 192.168.1.254
        wpa-ssid name_of_the_access_point
        wpa-psk the_password

`ifup` will then bring up the connection without using DHCP.


“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII., 18.

Forum Rules   •   How to report a problem   •   Software that rocks

Offline

#305 2016-09-06 20:13:01

KrunchTime
Member
Registered: 2015-09-29
Posts: 857

Re: Tracking Debian testing/unstable with BunsenLabs

Head_on_a_Stick wrote:

EDIT: Also, your /etc/resolv.conf is missing (it is usually created by NetworkManager), you can autogenerate one with:

# apt install resolvconf

Actually, /etc/resolv.conf does exist, but it's empty.  I looked at the same file under BL-Hydrogen, and it has text in it; something with 10.0.0.1 if my memory serves me correctly.  There was also a resolvconf file, but it appeared to be a sym-linked file.  I went ahead and installed resolvconf again.

Thank you for the suggestion and info about using a static IP address.  I think I'll just use an ethernet cable until this gets resolved.

Edit:  Installing resolvconf resulted in /etc/resolv.conf being repopulated:

# Generated by NetworkManager
nameserver 10.0.1.1

Last edited by KrunchTime (2016-09-06 20:37:43)

Offline

#306 2016-09-07 06:22:52

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 8,759
Website

Re: Tracking Debian testing/unstable with BunsenLabs

KrunchTime wrote:

Thank you for the suggestion and info about using a static IP address.  I think I'll just use an ethernet cable until this gets resolved.

I don't suppose you could try my suggestion, if you have time of course?

The results might be useful for others who have problems with NetworkManager or DHCP in Debian testing/unstable.

Also, a bug report may be called for here.


“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII., 18.

Forum Rules   •   How to report a problem   •   Software that rocks

Offline

#307 2016-09-07 10:04:58

Snap
Member
Registered: 2015-10-02
Posts: 465

Re: Tracking Debian testing/unstable with BunsenLabs

In Sid ceni is a good TUI helper to deal with /etc/network/interfaces and forget about NetworkManager. It seems it can work in Stable too, but never tried that myself.

Last edited by Snap (2016-09-07 10:07:36)

Offline

#308 2016-09-07 18:26:10

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 8,759
Website

Re: Tracking Debian testing/unstable with BunsenLabs


“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII., 18.

Forum Rules   •   How to report a problem   •   Software that rocks

Offline

#309 2016-09-09 10:23:45

Snap
Member
Registered: 2015-10-02
Posts: 465

Re: Tracking Debian testing/unstable with BunsenLabs

There you go! wink

Offline

#310 2016-09-19 02:31:41

KrunchTime
Member
Registered: 2015-09-29
Posts: 857

Re: Tracking Debian testing/unstable with BunsenLabs

Head_on_a_Stick wrote:

I don't suppose you could try my suggestion, if you have time of course?

The results might be useful for others who have problems with NetworkManager or DHCP in Debian testing/unstable.

Also, a bug report may be called for here.

My sincere apologies, but I just don't feel like spending the time.  I dist-upgraded yesterday and WiFi still isn't working.  So far, the WiFi issue is the ugliest bug I've ran into so far running Unstable this year.

Bug report has been made; reference my post starting all this.  Unfortunately, the bug report was made AFTER I dist-upgraded.  roll

Last edited by KrunchTime (2016-09-19 02:35:51)

Offline

#311 2016-09-24 23:37:54

KrunchTime
Member
Registered: 2015-09-29
Posts: 857

Re: Tracking Debian testing/unstable with BunsenLabs

Perl 5.24 transition...rock 'n roll.  From the Siduction forums:

https://forum.siduction.org/index.php?topic=6368.0

Offline

#312 2016-09-26 22:50:43

paxmark1
Member
Registered: 2015-10-02
Posts: 45

Re: Tracking Debian testing/unstable with BunsenLabs

It came, it went 5.24 up so smooth.  However, still a few probably waiting for  the gtk 3.22-1 and such.

Offline

#313 2016-09-27 18:48:50

KrunchTime
Member
Registered: 2015-09-29
Posts: 857

Re: Tracking Debian testing/unstable with BunsenLabs

^Yep, successfully dist-upgraded early yesterday.  However, network-manager is still borked, even with a new update.

Last edited by KrunchTime (2016-09-27 18:49:43)

Offline

#314 2016-09-28 07:59:39

Snap
Member
Registered: 2015-10-02
Posts: 465

Re: Tracking Debian testing/unstable with BunsenLabs

NetworkManager has been a pita for quite a long while. Better don't expect it fixed and behaving in the near future.

Offline

#315 2016-09-28 17:28:25

Horizon_Brave
Operating System: Linux-Nettrix
Registered: 2015-10-18
Posts: 1,473

Re: Tracking Debian testing/unstable with BunsenLabs

In testing/unstable, was there a patch to openssl recently?


"I have not failed, I have found 10,000 ways that will not work" -Edison

Offline

#316 2016-09-28 17:34:40

damo
....moderator....
Registered: 2015-08-20
Posts: 5,592

Re: Tracking Debian testing/unstable with BunsenLabs

Horizon_Brave wrote:

In testing/unstable, was there a patch to openssl recently?

Menu -> Help -> Debian -> Package Tracker wink


Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Online

#317 2016-09-28 22:12:29

Horizon_Brave
Operating System: Linux-Nettrix
Registered: 2015-10-18
Posts: 1,473

Re: Tracking Debian testing/unstable with BunsenLabs

damo wrote:
Horizon_Brave wrote:

In testing/unstable, was there a patch to openssl recently?

Menu -> Help -> Debian -> Package Tracker wink

I walked into this one! Sorry


"I have not failed, I have found 10,000 ways that will not work" -Edison

Offline

#318 2016-10-02 22:17:45

KrunchTime
Member
Registered: 2015-09-29
Posts: 857

Re: Tracking Debian testing/unstable with BunsenLabs

Snap wrote:

In Sid ceni is a good TUI helper to deal with /etc/network/interfaces and forget about NetworkManager. It seems it can work in Stable too, but never tried that myself.

I recently checked the packages page on the Debian site and ceni is not found anywhere.

On another note, I dist-upgraded on my desktop today and wireless is now working.  Don't know if it was the network-manager upgrade or one of the firmware-xxx upgrades, but who cares.  It works now.  Woo hoo!

snoopy_dancing_by_jessie4508.jpg

Offline

#319 2016-10-03 06:36:43

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 8,759
Website

Re: Tracking Debian testing/unstable with BunsenLabs

KrunchTime wrote:

I recently checked the packages page on the Debian site and ceni is not found anywhere.

If you ever need it again, you are welcome to use our version smile

See https://forums.bunsenlabs.org/viewtopic … 619#p36619


“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII., 18.

Forum Rules   •   How to report a problem   •   Software that rocks

Offline

#320 2016-11-04 02:58:02

AllanDaemon
New Member
Registered: 2016-02-08
Posts: 2

Re: Tracking Debian testing/unstable with BunsenLabs

Hi.

I'm using Bunsenlabs with sid a few months, almost a year. I have a lot of troubles, like this one with the polkit.

First, I would like to know, when I have some trouble with sid updates, where is the best place to ask help?

And when I solve the problem, is there a way to document it? Like the openbox autostart script (https://github.com/BunsenLabs/bunsen-co … /autostart) that needs changes in future versions?

I'm having problems with polkit for a while, like default configuration to ask password to mount anything. Usually I edit it in /usr/... and do it again when a new update overwrite it. All the (very few) documentation about how configure it in /etc files never worked.

Some update in the latest 2 weeks, everything stopped to work. Trying to mount something with thunar just give a error:

Failed to mount "partition name".
Not authorized to perform operation.

It don't even ask for a password. Running `pkexec bash -i` ask the password then, with the right password given, outputs this:

```
(...)
polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized
(...)
```

I found out the polkit agent daemon wasn't running. It's initialized in the .config/openbox/autostart in the line:

```
## for authentication
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &
```

But this file doesn't exists. The package polkit-1-gnome was installed and upgraded, but the `dpkg-query -L polkit-1-gnome` showed the the file is now on

/usr/lib/polkit-gnome-authentication-agent-1

instead. Changing this solved the problem by now. But I believe that some day someone will have to update the bunsenlabs openbox autostart script to this new path (when this change get to stable channel). So, perhaps would be nice to warn this person about this future change and avoid time solving the problem again. IDK if this is really needed or don't.

Another thing I would like to say: wouldn't be nice to create forks of the bunsenlabs projects on github to keep them updated for sid? People using unstable could contribute, so making things easier, and creating a place to discuss sid issues.

Offline

#321 2016-11-04 07:24:09

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 8,759
Website

Re: Tracking Debian testing/unstable with BunsenLabs

AllanDaemon wrote:

Some update in the latest 2 weeks, everything stopped to work.

This is quite normal for Debian sid and is to be expected.

Debian named the branch after the character in the Toy Story movies because it breaks all the toys...

The Debian development branches (testing and unstable) are supposed to be used by bug hunters and people interested in improving the next stable release, they are *not* intended for general, day-to-day use and cannot be expected to be usable at all times.

API changes are frequent (such as the polkit issues to which you refer) and this is in complete contrast to the stable release in which the API is fixed, or "stable" in the Debian parlance.

This is one of the many reasons why BunsenLabs tracks Debian stable smile


“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII., 18.

Forum Rules   •   How to report a problem   •   Software that rocks

Offline

#322 2016-11-04 18:39:48

KrunchTime
Member
Registered: 2015-09-29
Posts: 857

Re: Tracking Debian testing/unstable with BunsenLabs

Heads up to those tracking Unstable: current QT5 transition.  Following is what a dist-upgrade wants to do on my machines because of the new qt5-gtk-platformtheme package:

The following packages were automatically installed and are no longer required:
  libdouble-conversion1 libmysqlclient18 libqt5clucene5 libqt5designer5
  libqt5help5 libqt5test5 python3-dbus.mainloop.pyqt5 python3-sip xsane
  xsane-common
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  hplip-gui python3-pyqt5
The following NEW packages will be installed:
  libmysqlclient20 qt5-gtk-platformtheme

In my case, I'm able to avert the installation of the new qt5-gtk-platformtheme package, as well as the automatic and suggested removal of packages, by marking the hplip-gui and python3-pyqt5 packages to be held.

Offline

#323 2016-11-05 01:41:32

AllanDaemon
New Member
Registered: 2016-02-08
Posts: 2

Re: Tracking Debian testing/unstable with BunsenLabs

Head_on_a_Stick wrote:

This is quite normal for Debian sid and is to be expected.

Well, I kinda know it. But I believe that I (emphasis on I) have more trouble and pain with stable releases than with unstable like sid. I would like a rolling release that break less on each update, but I rather go this way than suffering with MY stable problems, which for most people I understand that is not the case. I also have criticism against the Freeze Releases with sable model, but this is another question.


KrunchTime wrote:

Heads up to those tracking Unstable: current QT5 transition.  Following is what a dist-upgrade wants to do on my machines because of the new qt5-gtk-platformtheme package:

The following packages were automatically installed and are no longer required:
  libdouble-conversion1 libmysqlclient18 libqt5clucene5 libqt5designer5
  libqt5help5 libqt5test5 python3-dbus.mainloop.pyqt5 python3-sip xsane
  xsane-common
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  hplip-gui python3-pyqt5
The following NEW packages will be installed:
  libmysqlclient20 qt5-gtk-platformtheme

In my case, I'm able to avert the installation of the new qt5-gtk-platformtheme package, as well as the automatic and suggested removal of packages, by marking the hplip-gui and python3-pyqt5 packages to be held.

yeah. I saw that. Hopefully I always check before `apt full-upgrade`, after once I hadn't checked it right and shit happened. But since the time I almost removed vim in one of these broken updates, I just do `apt upgrade` now. To avoid things like this.

I would like to know how many people use bunsen with sid. And Also if there is a better place to communicate than a unique dozens page long thread on a forum (a forum sub-area could be a good one). I would like to exchange more experiences and ideas with the (few?) ones daring to go with bleeding edge unstable.

Last edited by AllanDaemon (2016-11-05 01:42:19)

Offline

#324 2016-11-05 07:28:40

Snap
Member
Registered: 2015-10-02
Posts: 465

Re: Tracking Debian testing/unstable with BunsenLabs

Check this regularly or add it to your RSS feeds:

https://forum.siduction.org/index.php?P … board=22.0

Upgrade warnings are typically announced there.

Usually the Sid based distro forums are rather quiet. You'll have more activity/support on IRC, though I never use it. For me apt (and friends) is the best package manager to track a rolling/unstable release. Normally in other distros things break and then it's time to search for solutions and fix it. With apt and some attention you can avoid breakages. I hardly ever have any. There are different methods: apt pinning, holding packages with dpkg or apt-mark, and also using helpers like apt-listbugs, debsecan, etc...

A good practice is doing simulations (-s or --simulate) and performing the big or critical dist-upgrades outside the X-server; the tty (killing the display manager to do it can be a mess sometimes) and better switching to init 3. It's not that hard to avoid breakages. The downside is that it takes time and attention. As they use to say, rolling releases need more dedication than a jealous girlfriend.

Offline

#325 2016-11-05 09:31:49

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 8,759
Website

Re: Tracking Debian testing/unstable with BunsenLabs

AllanDaemon wrote:

I would like a rolling release that break less on each update

You should use Arch smile

Also:

if there is a better place to communicate than a unique dozens page long thread on a forum

You are welcome to open threads in Help & Support (Other) for any testing/unstable issues.

Last edited by Head_on_a_Stick (2016-11-05 13:30:48)


“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII., 18.

Forum Rules   •   How to report a problem   •   Software that rocks

Offline

Board footer

Powered by FluxBB