The officially official Devuan Forum!

You are not logged in.

#1 Re: Installation » Devuan Jessie: Many packages moved to local/obsolete » 2019-05-31 03:02:57

I don't know who fixed what, but the packages that got moved to local/obsolete appears normal again. Thanks to whoever it was.

Looks like /jessie/main/binary-amd64/Packages is supposed to say that apache2 version is "2.4.10-10+deb8u12". It's actually /jessie-security/main/binary-amd64/Packages that says apache2 version is "2.4.10-10+deb8u14". Something must have happened in jessie-security a month ago, but has been fixed within the past week.

#2 Installation » Devuan Jessie: Many packages moved to local/obsolete » 2019-04-30 16:47:26

Replies: 3

On my Devuan Jessie PC, many packages have been moved to the Installed (local or obsolete) status, such as apache2, openssh-client, perl, python, samba, tar.

The problem appears to be caused by a Packages file containing older versions of these packages: … ackages.gz
Last modified date: 2019-04-30 05:17
size: 8.7M

For example, apache2: My installed apache2 version is "2.4.10-10+deb8u14", but the Packages file version is "2.4.10-10+deb8u12". Any idea what's going on?

Package: apache2
Version: 2.4.10-10+deb8u12
Installed-Size: 527
Maintainer: Debian Apache Maintainers <>
Architecture: amd64
Replaces: apache2.2-common, libapache2-mod-macro (<< 1:2.4.6-1~)
Provides: httpd, httpd-cgi
Depends: lsb-base, procps, perl, mime-support, apache2-bin (= 2.4.10-10+deb8u12), apache2-utils (>= 2.4), apache2-data (= 2.4.10-10+deb8u12)
Conflicts: apache2.2-common (<< 2.3~)
Pre-Depends: dpkg (>= 1.17.14)
Breaks: libapache2-mod-macro (<< 1:2.4.6-1~)
Recommends: ssl-cert
Description: Apache HTTP Server
Description-md5: d02426bc360345e5acd45367716dc35c
Suggests: www-browser, apache2-doc, apache2-suexec-pristine | apache2-suexec-custom
Tag: role::metapackage, suite::apache
Section: httpd
Priority: optional
Filename: pool/DEBIAN/main/a/apache2/apache2_2.4.10-10+deb8u12_amd64.deb
Size: 208468
MD5sum: 0c54378f55125582eae37c07bdaab8d5
SHA1: 1c3ece302d94bc854abd1859edcdd713dbd91ebd
SHA256: a7890679b519b12578b8fe3485a2a235c8f2d5ee9f6b045e5e218aff9fef1da5

#3 Re: Installation » Latest devuan jessie update causing authentication problems » 2018-08-04 19:44:08

All of my original problems have been resolved. I think the repackaging of policykit-1 fixed it. Please pass a thank-you to Centurion_Dan for updating policykit-1.

#4 Re: Installation » Latest devuan jessie update causing authentication problems » 2018-08-01 16:02:51

golinux - I don't think I'm doing any kind of redirecting for the way my devuan mirror is set up. I followed these apt-mirror instructions, and to expose the from my local mirror server to my devuan jessie PC, I think I just need to change my /var/www/merged symlink to point to my local mirror of the packages, as shown in these instructions.

#5 Re: Installation » Latest devuan jessie update causing authentication problems » 2018-08-01 03:47:50

Oh I didn't know there were instructions for mirroring the Devuan repositories. I used the apt-mirror script, which had previously worked for mirroring Ubuntu 10.04 repositories, and has also been working for Devuan Jessie.

#6 Re: Installation » Latest devuan jessie update causing authentication problems » 2018-07-31 18:33:49

I'm in the middle of mirroring 147.3 GB from the new URL at, which will take a few days on my slow home connection, so I haven't tested if this will fix my problems.

I found a workaround: Downgrade libpolkit-agent-1-0, libpolkit-backend-1-0, and libpolkit-gobject-1-0 from 0.105-15~deb8u3 to 0.105-9+devuan1.

- Launch Synaptic Package Manager.

gksudo synaptic-pkexec

- Find each of the 3 packages and press CTRL+E, or from the menu: Package -> Force Version.

- Select 0.105-9+devuan1.

This fixed the 3 problems I reported in my original post.

#7 Installation » Latest devuan jessie update causing authentication problems » 2018-07-31 04:45:10

Replies: 25

Here's the log of today's update from /var/log/apt/term.log. Several packages are related to a "policy kit", which seems related to the authentication problems reported below.

Log started: 2018-07-30  20:41:59
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 154568 files and directories currently installed.)
Preparing to unpack .../libssl1.0.0_1.0.1t-1+deb8u9_amd64.deb ...
Unpacking libssl1.0.0:amd64 (1.0.1t-1+deb8u9) over (1.0.1t-1+deb8u8) ...
Preparing to unpack .../libidn11_1.29-1+deb8u3_amd64.deb ...
Unpacking libidn11:amd64 (1.29-1+deb8u3) over (1.29-1+deb8u2) ...
Preparing to unpack .../libpolkit-gobject-1-0_0.105-15~deb8u3_amd64.deb ...
Unpacking libpolkit-gobject-1-0:amd64 (0.105-15~deb8u3) over (0.105-9+devuan1) ...
Preparing to unpack .../libpolkit-agent-1-0_0.105-15~deb8u3_amd64.deb ...
Unpacking libpolkit-agent-1-0:amd64 (0.105-15~deb8u3) over (0.105-9+devuan1) ...
Preparing to unpack .../libpolkit-backend-1-0_0.105-15~deb8u3_amd64.deb ...
Unpacking libpolkit-backend-1-0:amd64 (0.105-15~deb8u3) over (0.105-9+devuan1) ...
Preparing to unpack .../busybox_1%3a1.22.0-9+deb8u2_amd64.deb ...
Unpacking busybox (1:1.22.0-9+deb8u2) over (1:1.22.0-9+deb8u1) ...
Preparing to unpack .../openssl_1.0.1t-1+deb8u9_amd64.deb ...
Unpacking openssl (1.0.1t-1+deb8u9) over (1.0.1t-1+deb8u8) ...
Processing triggers for man-db ( ...
Setting up libssl1.0.0:amd64 (1.0.1t-1+deb8u9) ...
Setting up libidn11:amd64 (1.29-1+deb8u3) ...
Setting up libpolkit-gobject-1-0:amd64 (0.105-15~deb8u3) ...
Setting up libpolkit-agent-1-0:amd64 (0.105-15~deb8u3) ...
Setting up libpolkit-backend-1-0:amd64 (0.105-15~deb8u3) ...
Setting up busybox (1:1.22.0-9+deb8u2) ...
Setting up openssl (1.0.1t-1+deb8u9) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Log ended: 2018-07-30  20:42:03

Three issues found so far:

1. The package "policykit-1" cannot be updated. The new version "0.105-15~deb8u3" cannot be updated because of "Broken dependencies". The Dependencies tab says the upgrade breaks gdm3 (<3.8.4-7~). My installed version is 0.105-9+devuan1.

On a side note, on Saturday Jul 28, I see that Debian put out a security patch for "policykit-1, 0.105-15~deb8u3". That explains where these changes are coming from. … 00042.html

2. In my MATE desktop, I cannot launch System -> Adminstration -> Synaptic Package Manager. Nothing happens.

From the cmd line, I see a "wrong number of arguments" reported (I changed my real name in the output to John Doe):

~$ synaptic-pkexec 
==== AUTHENTICATING FOR com.ubuntu.pkexec.synaptic ===
Authentication is required to run the Synaptic Package Manager
Authenticating as: John Doe,,, (jdoe)
polkit-agent-helper-1: wrong number of arguments. This incident has been logged.
Error executing command as another user: Not authorized

This incident has been reported.

I can work around this problem by running the command as root:

~$ gksudo synaptic-pkexec

3. I also can't shut down the PC from the MATE shutdown button. And I can't change the PC's date time - the Time Settings button is grayed out. I suspect this is all related to the authentication failures like the Synaptic Package Manager.

I can work around this problem from the cmd line:

~$ sudo shutdown -h now

Any ideas on how to fix this?

#8 Re: Other Issues » Compiling, debugging: How do I know what compile settings devuan uses? » 2017-09-26 10:18:12

I've found the cause of the memory leak of the list view object which leads to the crash. This memory leak has been around since Nautilus 2.30.1 (Ubuntu 10.04). Also, I looked at the caja source code on github (1.19.1), and I think the memory leak is still there.

The memory leak fix is pretty simple, and I'd like to submit a patch to it for Devuan Jessie. How do I do that?

Really disappointed that Mate never fixed any of this stuff at least by the version we're using in jessie (1.8.2), I thought that was part of the point of Mate in the first place.

To be fair, the leak is pretty small and only occurs when the user opens and closes the split pane. The callbacks that eventually lead to the crash looks correct to me. The list view object remaining in memory after the split pane is closed is what should NOT be happening.

It's possible that no one figured out that the crash is triggered by both the split pane and Preferences dialog. You can open and close the split pane, do a bunch of other stuff for a few hours, then open the Preferences dialog, and crash.

#9 Re: Other Issues » Compiling, debugging: How do I know what compile settings devuan uses? » 2017-09-23 01:13:51

Are you on jessie? hardware?

Yes, I'm using devuan jessie. I have only the MATE desktop installed, no XFCE or any other desktop.

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 1.0 (jessie)
Release:	1.0
Codename:	jessie

Based on what I've seen in the code, I don't think hardware matters. But in case it somehow does, it's a PC that I built a while back:

CPU: Athlon II X4 620e
Motherboard: Jetway NC84E-LF

I have no explanation why caja doesn't crash for you. From what I've seen in the code so far, caja must crash when in list view, if the split pane has been opened and closed, and you launch the File Management Preferences dialog.

- When you launch the File Management Preferences dialog, the code initializes the GUI in the "List Columns" tab.
- The act of initializing this GUI causes settings to be saved to "org.mate.caja.list-view". You can view these settings using dconf-editor.
- Whenever the settings for "org.mate.caja.list-view" are changed, each tab in the main pane or the split pane is called back, so the tab can add or remove columns or change the order to match the new settings.

- Caja creates a list view memory object for each tab that you open.
- When you close each tab, caja properly deletes the list view memory object from memory.
- But when you close the split pane, caja does NOT delete the list view memory object - it remains in memory!
- So when the "org.mate.caja.list-view" settings are changed, the list view memory object representing the closed split pane is still called back! Some of its data contents are now NULL, and when the code tries to use this NULL data, caja crashes.

If I can figure out why the split pane's list view memory object isn't properly deleted from memory when the split pane is closed, I think that will fix the crash, and possibly fix a memory leak as well.

#10 Re: Other Issues » Compiling, debugging: How do I know what compile settings devuan uses? » 2017-09-21 19:40:36

Not happening here. Cannot reproduce on two different machines.

I just discovered that this crash only occurs in List View. It does not occur in Icon View, or Compact View.

#11 Re: Other Issues » Compiling, debugging: How do I know what compile settings devuan uses? » 2017-09-20 22:52:46

Could be a trick question,

Nope, it's not a trick question. I didn't want to waste my time debugging a problem that ended up being a configuration or compiler option.

I've done the same thing at work when I write my own compiling scripts on my local PC - I check what the build scripts do on our build server and make sure my local build scripts use the same config or compiler defined options. This ensures my local builds that I debug with are the same as the ones the customers get.

For example, if my local build had a TIMEOUT variable of 30 sec, but the customer build had a TIMEOUT of 1 sec, my local build will never see the customer's problem. That's what I'm trying to avoid and why I wanted to know how devuan builds the packages.

apt-get source caja

Yeah, I got the source code using this command. I can see that the command downloaded the original caja.1.8.2 source and some debian patches, which the command automatically applied.

Curious if you located the source of the crash (bug) and what it was?

Nope, not yet. That's coming up next once I ensure that my compiled caja has the same settings as the installed caja.

The steps to reproduce the crash:
- Open any caja file manager window.
- Press F3 to open a split pane.
- Press F3 to close the split pane.
- Go to the menu: Edit > Preferences.
- Crash.

This problem doesn't occur in Nautilus 2.30.1 (on Ubuntu 10.04).

#12 Other Issues » Compiling, debugging: How do I know what compile settings devuan uses? » 2017-09-20 09:31:21

Replies: 11

Caja is the MATE desktop's file browsing app. I want to compile and debug caja to fix a crash I found. However, my compiled caja looks different than devuan's installed caja. My caja has no menu, no toolbar, and no keyboard shortcuts.

I followed the warning message: "Unable to load ui file caja-shell-ui.xml" through the code. Eventually, I figured out that for my compiled caja, the DATADIR macro was defined as "/usr/local/share". But caja installs its files under "/usr/share".

The solution is that when I run to create the Makefile, I specify the DATADIR path, like this:

./ --datadir="/usr/share"

But my larger question is: If I want to be sure my compiled code is the same as Devuan's compiled code, how do I know what cmd line options Devuan used to compile code? This is not just for caja, but for any other package I might compile and debug in the future.

Board footer

Forum Software