The officially official Devuan Forum!

You are not logged in.

#2 Re: Other Issues » Execuable files not running... » 2020-10-20 12:03:03

ComputerBob wrote:
-rwxr-xr-x 1 root root 3487264 Oct  9 10:58 linbpq

Please forgive me if I'm asking a stupid question (it wouldn't be the first time), but does that line mean that the file is owned/must be run by root?

Nope, the 'x' at the end means that 'others' have execution privileges. rwxr-xr-x means owner has full privileges, group has read/execute, and other has read/execute.

#3 Re: Devuan » Looking for a new system » 2020-09-21 15:40:07

I'm curious, how do you see systemd 'encroaching' in Chimaera?

What Devuan is doing is a heck of a lot more complicated than you seem to think.

#4 Re: Desktop and Multimedia » Beowulf crashes often » 2020-09-10 18:58:26

erdos wrote:

I use nvidia proprietary driver installed through 'synaptics' on this computer.  i believe it's a 9300 series card from nvidia.

Perhaps you could try the open source nouveau driver, just to help narrow things down. I gave up on Nvidia when my last Nvidia card died a few years ago, but there seems to be no end of glitches and trouble and version mismatches and whatnot with the proprietary drivers. Hopefully an Nvidia expert will chime in...

#5 Re: Desktop and Multimedia » Beowulf crashes often » 2020-09-10 16:33:22

erdos wrote:

hi,  it seems that Beowulf on my computer is crashing often.  typically the screen would freeze and keyboard is not responsive.  I use Beowulf on my HTPC and usually firefox and kodi are opened on the desktop.  It's installed on a HP computer with Nvidia card and solid state HD.

anyone else has beowulf crashing issues?

No such problems here. In fact, Beowulf has been totally reliable on my system.  I, too, have an HP desktop with an SSD, but I run just the integrated Intel graphics. It wouldn't surprise me if your issue was Nvidia related. Are you using nouveau or the proprietary drivers?

#6 Re: Hardware & System Configuration » Post Your Sources List » 2020-09-07 00:08:15

My sources.list is pretty plain vanilla:

deb http://deb.devuan.org/merged beowulf main non-free contrib
#deb-src http://deb.devuan.org/merged beowulf main non-free contrib

deb http://deb.devuan.org/merged beowulf-security main non-free contrib
#deb-src http://deb.devuan.org/merged beowulf-security main non-free contrib

deb http://deb.devuan.org/merged beowulf-updates main non-free contrib
#deb-src http://deb.devuan.org/merged beowulf-updates main non-free contrib

deb http://deb.devuan.org/merged beowulf-backports main non-free contrib

[Edit: just remembered that this is in sources.list.d, for Pale Moon:]

deb http://download.opensuse.org/repositories/home:/stevenpusser/Debian_10 /

#7 Re: News & Announcements » Latest repositories for Devuan 3 ! » 2020-08-16 00:40:14

brday wrote:
sgage wrote:

The repositories for Devuan 3 (Beowulf) are those of Debian 10 (Buster), with some exceptions required by forking/substitution of packages to avoid systemd dependencies. For Devuan 3, you won't see lots of version updates of software, but you will see regular security updates and bugfixes, a la Debian.

Why doesn't the software automatically update every new version available as Linux Mint systems or other systems like FreeBSD do?  For example, it cannot be that Firefox or Falkon browsers, among other software, continue to have older versions that generate system vulnerability.

The older versions in Devuan/Debian continue to receive security updates. If you think you need the most recent versions of everything, Devuan/Debian is probably not for you. But there are backports to get more recent versions, and there's a whole 'testing' release, called chimaera, which I am running right now.

If you are comfortable with systemd, use Linux Mint/Ubuntu/etc.  You seem to be missing the point of Devuan, which is to be a systemd-free fork of Debian, and which it accomplishes quite nicely.

#8 Re: News & Announcements » Latest repositories for Devuan 3 ! » 2020-08-15 23:05:07

The repositories for Devuan 3 (Beowulf) are those of Debian 10 (Buster), with some exceptions required by forking/substitution of packages to avoid systemd dependencies. For Devuan 3, you won't see lots of version updates of software, but you will see regular security updates and bugfixes, a la Debian.

#9 Re: Desktop and Multimedia » dist-upgrade on ceres still wants to remove wicd » 2020-08-12 16:07:23

HevyDevy wrote:

it needs to be converted to python3 i think due to python2 being deprecated. If no one is able or wants to pick it up it will just get relegated to the dustbin for future releases of debian stable/testing. This is why im glad i learnt how to use backend tools like ifupdown, wpa_supplicant and iwd.

It's why I'm glad I just use a wired ethernet connection :-)

#10 Re: Other Issues » Install grub so that EFI directory is 'devuan' » 2020-08-09 12:13:30

Head_on_a_Stick wrote:
sgage wrote:

I want to have a separate devuan and debian directory.

Why? If it's that important to you then install GRUB from an Arch live ISO (use the --boot-directory= & --efi-directory= options to avoid the need to chroot).

I can't find a reference in the changlelog but I presume $ESP/EFI/debian is being created because of https://bugs.debian.org/cgi-bin/bugrepo … bug=925309

It's not that important. Thanks for the bug reference.

#11 Re: Hardware & System Configuration » Packages Kept Back (Ceres) » 2020-08-09 11:44:06

brocashelm wrote:

I've been using the "unstable" Ceres for a few weeks. It's going along just fine, perhaps better than Chimaera or even Beowulf. The only problem is I've been noticing more packages are kept back when I check for updates. I just put the repositories for Chimaera and Beowulf back on (temporarily) in order to recover some missing Python packages (due to still being at 2.7.17-2, despite Python2 and others being at 2.7.18-2). I also did that to make Youtube-dl functional again.

Now, I'm seeing a growing list of packages that can't be upgraded. In this situation, should I just ignore it and wait until newer versions are available from upstream?

The following packages have been kept back:
 cpp-10 cpp-9 g++-10 g++-10-multilib g++-9 g++-9-multilib gcc-10 gcc-10-base gcc-10-base:i386 gcc-10-multilib gcc-9 gcc-9-base gcc-9-multilib gfortran-9 lib32asan5 lib32asan6 lib32atomic1 lib32gcc-10-dev lib32gcc-9-dev lib32gcc-s1 lib32gomp1 lib32itm1 lib32quadmath0 lib32stdc++-10-dev lib32stdc++-9-dev lib32stdc++6 lib32stdc++6-10-dbg lib32ubsan1 libasan5 libasan6 libatomic1 libatomic1:i386 libcc1-0 libgcc-10-dev libgcc-9-dev libgcc-s1 libgcc-s1:i386 libgfortran-9-dev libgfortran5 libgomp1 libgomp1:i386 libitm1 liblsan0 libpython-all-dbg libpython-all-dev libpython2-dbg libpython2-dev libpython2-stdlib libquadmath0 libstdc++-10-dev libstdc++-9-dev libstdc++6 libstdc++6:i386 libtsan0 libubsan1 libx32asan5 libx32asan6 libx32atomic1 libx32gcc-10-dev libx32gcc-9-dev libx32gcc-s1 libx32gomp1 libx32itm1 libx32quadmath0 libx32stdc++-10-dev libx32stdc++-9-dev libx32stdc++6 libx32stdc++6-10-dbg libx32ubsan1 python-all python-all-dbg python-all-dev python2 python2-dbg python2-dev python2-minimal

I just apt update/upgraded my system, and these all upgraded without incident. Except 3 python2 packages - there has been some funny business with python2 for a while.

#12 Re: Other Issues » Install grub so that EFI directory is 'devuan' » 2020-08-08 21:23:37

rolfie wrote:

That will work if you don't use Secure Boot. But you still will have a debian and a devuan EFI directory.

Use the efibootmgr to boot the devuan entry. If that works, you can delete the debian entry with the file manager.

rolfie

I want to have a separate devuan and debian directory. The problem is, that in Ceres (this did not happen in Beowulf), I can not get grub-install to generate a devuan directory at all. No matter what I've tried, grub-install generates a debian directory in /boot/efi/EFI. I know how to use efibootmgr to set boot order and such.

#13 Other Issues » Install grub so that EFI directory is 'devuan' » 2020-08-08 20:36:39

sgage
Replies: 6

I am running Ceres (which is running very well with MATE). How can I install grub so that the EFI directory is 'devuan' instead of 'debian'. Using the '--bootloader-id=devuan' argument to grub-install still creates a 'debian' directory. My os-release file has 'ID=devuan'. I don't know what else to try. Any ideas?

TIA...

#14 Re: Devuan » Stupid question about Devuan Testing and Debian Testing » 2020-07-24 15:50:14

brocashelm wrote:

I switched to Chimaera yesterday, and had to do a couple of APT workarounds, followed by a reboot or two (just to make sure nothing breaks). I noticed that my system is recognized as BOTH Testing and Unstable, even though my sources list is pulling packages from Chimaera only.

Distro: Devuan GNU/Linux 4 (chimaera/ceres)

Here are my sources:

deb http://deb.devuan.org/merged chimaera main non-free contrib
deb http://deb.devuan.org/merged chimaera-updates main non-free contrib
deb http://deb.devuan.org/merged chimaera-proposed-updates main non-free contrib

Is there anything else that I'm missing?

All of my 'testing' installations have always reported as testing/unstable. For example, my current Debian bullseye system reports 'bullseye/sid'. I've never worried about it.

#15 Re: Devuan » Stupid question about Devuan Testing and Debian Testing » 2020-07-16 21:45:19

thierrybo wrote:

Hi,

After several years using only Debian stable and then Devuan stable, I recently upgraded my computer to Devuan testing/chimaera. I use "testing" in my source.list and not "chimaera".

My stupid question: packages are pulled from Debian testing/bullseye. Knowing that Devuan follows Debian releases 6 to 12 months later, which codename packages will be pulled from after Debian Bullseye become stable and before Devuan Chimaera become stable when using "testing" in source.list? Debian Bullseye or Debian Bookworm?

If you have 'testing' in your sources, I believe you will start pulling from bookworm. Just use chimaera!

#16 Re: Devuan » The point of Devuan? » 2020-07-08 20:01:50

"Lets not get caught up in what it is to me, as what it should be to everybody else."

Exactly. and let's not get caught up in 'it really needs to implement/include these features and defaults that I think are best'.

Devuan is intended to be used as the base for derivatives, and many are springing up, with different approaches to features and minimalism, etc. This is a very good thing!

#17 Re: Devuan » The point of Devuan? » 2020-06-29 22:26:00

brocashelm wrote:

I first got into Devuan two years ago when there was talk of non-Systemd distros in the market. Having used GNU/Linux Mint 18.3 (the last one to allow "some" sort of init choice), I kept waiting for the right moment to jump right in. I tried Devuan when ASCII was out, but I had problems with metapackages (i.e. removing SLiM affects essential system functions, such as UDisks), so I left it alone and went back to my daily driver. Come Beowulf, it FINALLY showed promise, but I still didn't quite feel right with it.

That's when I'd heard that a Devuan spin by the name of Refracta existed, so I honestly gave it a go. I was surprised how lightweight it was, and the necessary drivers were provided to me in the form of binaries (I definitely needed those for my AMD GPU). On top of that, its default sound drivers shipped with ALSA (instead of PulseAudio, which I can't quite wrap my head around for such a non-Systemd distro to use as default). Even better is that you get to create your own live installer with ease.

After spending all of yesterday tweaking my Refracta system to how I see fit, I can safely say that this will tide me by for a really long time. Surprised how stable it is, and it's superior to other non-Systemd champions Artix GNU/Linux, MX GNU/Linux,  and Void GNU/Linux.

So, to sum it up, the "point" of using Devuan is to get away from Red Hat and Poettering bollocks by ways of Systemd, PulseAudio, and other such rubbish. Canonical putting the final nail in the coffin was when they announced Snap. Well, at least GNU/Linux Mint's developers had enough common sense to reject that, but it looks like they will continue to use Systemd, even on GNU/Linux Mint Debian Edition (here's their perfect chance to join forces with Devuan and usher in the best of both worlds).

The stated purpose of the Devuan Project from the get-go was to produce a systemd-free Debian. That's all. They mostly use the Debian repos and general system of meta-stuff except for those packages that absolutely needed to be forked to work without systemd. A lot of that is pretty tricky infrastructure/plumbing type stuff. They do not have an army of developers - what they have done so far is incredible, and I fear the job doesn't get easier going forward...

All the other minimalism and such that people project upon it is just that - their projection. Devuan encourages derivatives, so you get things like Refracta and others, which is great. But Devuan has done really tricky stuff just to get a systemd-free Debian, and that's their mission, and their plate is pretty full. That was the point of my original post to start off this thread.

#18 Re: Other Issues » Calibre bug » 2020-06-16 16:34:50

"Here's the one and only non-commented out line in my /etc/apt/sources.list file:  deb http://deb.devuan.org/merged ceres main non-free contrib."

Aha! You are on ceres (unstable = sid). My sources.list is on chimaera (testing = bullseye). Until Beowulf was released (declared stable), chimaera and ceres were the same, but then chimaera became 'testing' and started tracking bullseye. This is why the Devuan folks strongly recommend not using suite names, but rather the code names.

In any case, I'm all caught up and Calibre works properly again...

#19 Re: Other Issues » Calibre bug » 2020-06-15 11:23:54

garyk wrote:
sgage wrote:

Hi garyk,

Just wanted to let you know of my latest exploits. I am thinking that the problem doesn't lie with Calibre, as such. In both Chimaera  and Debian bullseye (on which Chimaera is based), Calibre worked fine this morning. After a sizeable update, both exhibited the problem you describe - the reader window comes up for a second, then... gone. Calibre was not among the updated packages. There were a few python related odds and ends. I suspect an interaction with some new python component that hadn't been tested against. You just happened to get it before me.

I think you're right - we are probably going to see rapid updates of Calibre as it dances along with continuing component updates in Python.

Just to let you know, I did an upgrade tonight and the following python file was upgraded:  python3-pyqt5.qtwebengine (5.15.0-1.  Calibre is now working fine once again.  Good call on a python package being the problem.  cool

Hmmm... still on 5:14 here. I wonder why you get upgrades before I do? Luck of the draw on mirrors? I'll probably get it tomorrow. Good to know it's fixed - for now...  :-)

#20 Re: Other Issues » Calibre bug » 2020-06-14 20:30:08

Hi garyk,

Just wanted to let you know of my latest exploits. I am thinking that the problem doesn't lie with Calibre, as such. In both Chimaera  and Debian bullseye (on which Chimaera is based), Calibre worked fine this morning. After a sizeable update, both exhibited the problem you describe - the reader window comes up for a second, then... gone. Calibre was not among the updated packages. There were a few python related odds and ends. I suspect an interaction with some new python component that hadn't been tested against. You just happened to get it before me.

I think you're right - we are probably going to see rapid updates of Calibre as it dances along with continuing component updates in Python.

#21 Re: Other Issues » Calibre bug » 2020-06-14 11:36:40

garyk wrote:
sgage wrote:

OK, Calibre has no problems opening/reading epub and mobi on my ceres system. However, I seem to be running a slightly different version. The package version is 4.99.4+dfsg+really4.17.0-1. And apt update doesn't offer anything newer. And the program itself reports 4.99.5!

In any case, it's working nominally here...

I did an update yesterday in which Calibre was upgraded to the new version.  I suspect that's where the bug I'm experiencing came from as I use Calibre on a daily basis.  I was reading a pdf book yesterday so when I finished that book and went to read an epub book today that's when I ran into the problem. 

Calibre is moving from Python 2.x to 3.x and there have been a bunch of bugs affecting it in the last couple of months.  There have been frequent updates to it.  On my machine Calibre itself reports the same version as you see.  There are going to be a lot of 4.99.x versions during the Python upgrade as when the entire upgrade to Python 3 is finished Calibre will be termed version 5. Until then it's going to be version 4.99.x

Ah, that's why the package is named +'really4.17'. It will be good when the P2-P3 changeover is completed. Hopefully there won't be many (any) more hiccups...

#22 Re: Other Issues » Calibre bug » 2020-06-13 19:04:22

OK, Calibre has no problems opening/reading epub and mobi on my ceres system. However, I seem to be running a slightly different version. The package version is 4.99.4+dfsg+really4.17.0-1. And apt update doesn't offer anything newer. And the program itself reports 4.99.5!

In any case, it's working nominally here...

#23 Re: Other Issues » Calibre bug » 2020-06-13 18:46:37

garyk wrote:
sgage wrote:
garyk wrote:

Calibre's internal viewer crashes upon opening any book no matter what the file format is.  The only books now readable are ones that use an external viewer such as pdf, doc, or odt files.  As I do a lot of reading and the vast majority of my books are in epub format this is a big deal to me as it makes more than 3100 of my books unavailable.

As reportbug also does not work I am using this site to report the bug.

I am not seeing this issue at all with epub or mobi. This is on an up-to-date beowulf installation. Calibre version 3.39.1.

My bad.  I should have given the version #.

I'm running Ceres and the Calibre version is 4.99.4+dfsg+really4.18.0-1.

Aha! Let me boot into my ceres system and see if I can duplicate the issue...

#24 Re: Other Issues » Calibre bug » 2020-06-13 15:48:24

garyk wrote:

Calibre's internal viewer crashes upon opening any book no matter what the file format is.  The only books now readable are ones that use an external viewer such as pdf, doc, or odt files.  As I do a lot of reading and the vast majority of my books are in epub format this is a big deal to me as it makes more than 3100 of my books unavailable.

As reportbug also does not work I am using this site to report the bug.

I am not seeing this issue at all with epub or mobi. This is on an up-to-date beowulf installation. Calibre version 3.39.1.

#25 Re: Installation » quick note on chimaera installs (attn: fsmithred) » 2020-06-07 19:05:42

No problem with polkit stuff here. I now see that -backend is gone. The upgrade from fresh clean-installed beowulf seemed to take it in stride.

I wonder if it wasn't something left over from ascii... I have a beowulf that I upgraded from ascii ages ago - next time I'm over there I'm gonna see what polkit stuff it uses. It's so old that I can't possibly recall all the wrestling I did with it over the months when beowulf was pretty rough. Some of the workarounds for weird circular dependency dilemmas were like magic spells - had to do everything in just the right order.  I have mostly used MATE for years now, probably since Debian Wheezy, so pretty much my entire experience with Devuan has been MATE.

Board footer

Forum Software