The officially official Devuan Forum!

You are not logged in.

#1 Re: Desktop and Multimedia » Freezing in XFCE4 » 2018-05-07 03:03:04

Very odd behaviour, it might be useful to mention which hardware you use. Any chance you use nvidia graphics? Depending on your model that might explain it since the stock driver can be unstable on some chips.

#2 Re: Documentation » dev1fanboy's "Maintainer walkthrough" » 2018-05-07 02:57:59

stanz wrote:

humm, here I am again - in an old topic.
I tried to check,  '', but never loaded!

I happened to archive the old content at the dev1fanboy installation wiki before dissapeared(?), see … ging-guide

It's not well formatted as it's just a backup of what was there, and see that I've changed my post above to reflect that.

#3 Re: Installation » Palemoon installation from source » 2018-04-04 14:28:52

Also, thanks for your efforts. I'm not so good with packaging myself, but I will try to provide some input at some point.

#4 Re: Installation » Legal on Pale Moon potential packaging and distribution » 2018-04-04 14:19:04

I'm not an expert but I think this would do it:

Change --enable-official-branding to --disable-official-branding and rename your package in debian/control to whatever name you like. I think so long as you don't use their artwork and don't call it palemoon you should be fine.

lf I remember the browser will call itself "New Moon" by default. That would seem ok in the meantime, but you'd want to rename eventually I think.

Otherwise just use the mozconfig they provide, but it will limit you to the defaults.

#5 Re: Installation » Palemoon installation from source » 2018-04-03 20:21:30

Nice posts but I should point to this though (for your own benefit) which recently came up on the maling list.

It would seem it's best to rebrand or disable branding when packaging, especially if you want to make changes to the build process.

Also, I notice you mentioned grsecurity (the unofficial forward ports I guess). When I last looked they can't yet integrate meltdown/kpti, is much different there now?

#6 Re: DIY » Tips for using Palemoon » 2018-03-19 16:08:11

golinux wrote:

Firejail does the same thing on firefox.  It is a feature not a bug.  Since information can pass both ways, it prevents access to your personal information.  It took me a while to adjust to it.

Indeed the sandbox only lets you access downloads. So if you want to upload something into your browser (e.g an email attachment) just drop it in downloads first. If you want to add more append whitelist <directory path> to /etc/firejail/palemoon.profile.

It's worth noting about Firejail that Steve Pusser also offers a newer version of firejail that's compatible with Palemoon (which releases quickly and has no LTS), so it's best to use his builds.

#7 News & Announcements » Jessie install guide for new Devuan users » 2018-02-23 18:03:36

Replies: 0

An install guide is now available for the Jessie release. It should be useful to anyone who has ever installed an OS before. …

There is also a companion document for full disk encryption, since this is provided with ease in some distributions but requires a few more steps in Devuan. …

This ought to work without any problems but please report any issue or anything you feel is missing. Replying to this thread should make me aware of it very quickly.



#8 News & Announcements » Updated install guide with screenshots » 2018-02-21 10:08:30

Replies: 0

There is now a usable install guide on Friends of Devuan. Originally it was for alpha2, but I've updated it for use with the stable release, and added a few more screenshots. Suitable for users who are familiar with Debian or derivatives.

#9 Re: Off-topic » "I am devuan" advertisement » 2018-02-21 09:55:28

Interesting idea, maybe some additional stuff specific to Devuan would help that. Showing no systemd, or showing eudev in ascii.. a look at the installer (maybe in the beta isos).

#10 Re: Other Issues » How to fix the meltdown and spectre issue in Devuan » 2018-02-04 04:49:59

greenjeans wrote:

Just need to maybe get with a packager and have them package the newest version, the microcode version in the repo is the next-to-latest version, it's from July 2017 and the newest one is November 2017, so it's not like the current jessie microcode package is way old or anything.

I kinda doubt it has any fixes for meltdown in it.

Also Intel looks to have pulled the latest microcode for 2018, so most people have to wait for this to change.

#11 Re: Off-topic » What's the point to keep maintaining DEVUAN? » 2018-02-03 13:09:44

cynwulf wrote:
spartrekus.git wrote:


I see not really a point to keep DEVUAN being maintained.[etc] Wayland, SystemD, Pulseaudio, ... is the future !   
Another Unix BSD user.

Great trolling!

I would say it's a little late to the party. This isn't that annoying considering Devuan is doing quite well.

As for BSD, I don't see hardened Devuan users switching any time soon.

#12 Re: Other Issues » How to fix the meltdown and spectre issue in Devuan » 2018-02-03 12:49:56

fungus wrote:

Thank you for the information but your subject is slightly misleading.
Spectre has only partially been dealt with and the fix seems very far away.

True, the title was poorly chosen. Really this should be titled "How to mitigate Meltdown and Spectre" as it's unclear if they will ever be fixed. This is basically just how to apply the mitigations if/when they are available.

From what I can tell about Spectre it needs mitigations in userland, and maybe even mitigations during compile time using a patched gcc.

#13 Re: Installation » Palemoon a browser that doesn't convince! » 2018-02-03 12:14:28

HTML5 video support should be available with gstreamer. Try with gstreamer1.0-libav and gstreamer1.0-plugins-good installed.

#14 Re: Installation » sans-dbus, Questions, Tips and Tricks on its Implementation » 2018-01-19 16:55:42

@miroR I've made some initial changes for that and more to follow, please let me know in a couple of days if you find more. A couple of pages are gone now, so I need to try to remember their locations but with any luck I should be able to unbreak most of the links. If you have a git account, I'd appreciate any other feedback you have or opening of issues.

#15 Re: Installation » sans-dbus, Questions, Tips and Tricks on its Implementation » 2018-01-18 23:10:10

There's a little confusion about my name, I go by dev1fanboy only on the wiki but it remains under that name so that users can still find what they are looking for. A little bit of changing in links were required due to naming the pages after releases, because it's clearer what releases they can be used for. On the other hand, because it's frustrating for users the wiki pages should mirror the git repo soon. So I'll have a contributors area and a more readable area for users.

If you could point out which links are breaking that would be helpful. I'll of course fix those, or redirect to the renamed pages.

About the D-Bus pages, ascii has surf2 so when ascii is released I may just use that instead of Firefox.

#16 Re: Installation » sans-dbus, Questions, Tips and Tricks on its Implementation » 2018-01-18 18:17:05

miroR wrote:

And I don't even remember where I posted that I would contact dev1fanboy about something related to sans-dbus. I can tell that I tried (and contacted wrong Devuaner instead -- Ralph Ronquest I PM'ed, having mixed the nicknames somehow... But dev1fanboy's old email expired, which I had from Devuan DNG ML. So I have to post it here:

dev1fanboy, pls. either revert to the old locations that you previously had, or at least do not change those addresses any more...
( I'm referring to your Devuan Install, and esp. sans-dbus wiki pages. )

And also, cosider my new posts, as well as:
sans-dbus in Devuan: low level core installation of dbus remain

Correct me if I'm wrong, or confirm my research if you find it correct!

There's a fair bit of reading for the topic(s) but if I understand, there is something wrong with the Ceres APT pinning? I believe in Ceres you won't be able to avoid systemd that way if you use either dbus or xorg, and will have to make do with libsystemd0 being installed (also for ascii in some areas). I am actually considering removing that document, since it's not that useful anymore for that reason.. unless anyone finds it still useful somehow?

As far as full D-Bus removal it's very difficult if you need a fully featured browser from the Devuan repos. Firefox was mentioned mostly because you don't need to have the dbus daemon installed and running, so maybe your suggestion is not to be concerned about features and go with no dbus at all?

The changes to the wiki do seem to be confusing people, what I'll point to.. is that contributors can't easily view the source of those pages with the older location. Just as a note you can update older posts on d1g, but I may have to revert things anyway if enough people are finding it confusing. Does anyone agree with that? It would be good to have some feedback about that.

#17 Other Issues » How to fix the meltdown and spectre issue in Devuan » 2018-01-13 23:17:33

Replies: 10

Some information about mitigating the recent issues for Devuan users. I don't own any AMD hardware, so these instructions are for intel only.

Upgrade the kernel

It's worth knowing that Devuan does nothing to change the kernel images, and provides the Debian packaged kernels. So you can check with the Debian security tracker for the current status of the kernel packages. … kage/linux

Meltdown is fixed in all the Devuan branches, so you can upgrade your kernel right now to protect against meltdown.

apt-get update
apt-get dist-upgrade

This should be enough to get the kernel updates if you have the linux-image-<insertyourarch> virtual package installed. Otherwise search for the latest image version.

apt-cache search ^linux-image-

And install it like this for example.

apt-get install linux-image-3.16.0-5-amd64
Update the microcode using GRUB

Intel recently released new microcode. It's not known for sure if it's related to meltdown/spectre yet, but if you want to update the microcode anyway here's how to go about it. You don't need to do this if your motherboard vendor has released a BIOS update with the microcode.

Find and download the latest microcode from The latest at time of writing is here.

Change to the /lib/firmware directory (as root).

cd /lib/firmware/

And unpack the tarball here.

tar xf /home/youruser/Downloads/microcode*tgz

The Gentoo wiki page here explains how to convert the ucode into an initrd image that grub can use.

On Devuan install the iucode-tool package.

apt-get install iucode-tool

And generate the image for grub to use (if you use a boot partition make sure it's mounted).

iucode_tool -S --write-earlyfw=/boot/early_ucode.cpio /lib/firmware/intel-ucode/*

And you will need to make the changes in /etc/grub.d/10_linux as pointed out in the grub section. When you're happy with the changes update grub like this.

dpkg-reconfigure grub-pc

And you'll need to reboot for the changes to take effect.


And see the verification section from the gentoo wiki as well.

If you're an NVIDIA driver user you should update those to 384.111 for the stable release and 390.25 for the latest version (not covered here). You'll need to use the driver search feature to find those versions.

#18 Re: Other Issues » Meltdown and Spectre » 2018-01-07 04:00:53

It's a good idea to have a read of this page. A lot of devices out there are effected, and Nvidia graphics drivers should be updated for most people.

#19 Re: Installation » Black Screen on Devuan Ascii - acpi=off solves it (undesirable) » 2017-12-16 19:45:19

lunario wrote:

After upgrading and installing the new kernel as you suggested, the situation was exactly the same as before, I could not even get into a virtual console unless I was in recovery mode. What helped a bit was replacing the intel driver with vesa because then I could at least get into a normal virtual console, however starting slim or X still did not work (Permission denied).

So you probably can get around the issue by forcing xorg to use only the vesa driver for now. That seems like the best option to me unless you really do need the accelerated driver, at least until you can find a better work-around.

I think the problem with xorg permissions is already known and I noticed there was an update yesterday for the xserver-xorg-legacy package that allows setting permissions for xorg (dpkg-reconfigure xserver-xorg-legacy). Using the console users only setting and starting as root works fine for me.

You seem to have narrowed it down quite a bit there. You only have problems when the intel driver loads so you could try a few work-arounds if you want, like disabling modesetting or maybe try the pci=noacpi boot parameter.

#20 Re: Installation » Black Screen on Devuan Ascii - acpi=off solves it (undesirable) » 2017-12-16 01:02:43

You should upgrade the kernel after the dist-upgrade. If the backported kernel doesn't solve the problem you could just remove it and the backports repo.

To make testing the screen problem a bit easier you could disable the display manager.

update-rc.d -f slim remove

Do this before you dist-upgrade. That should let you upgrade the kernel and make other tests without having to recover.

To start the display manager and test the xserver you can just use

/etc/init.d/slim start

#21 Re: Installation » Black Screen on Devuan Ascii - acpi=off solves it (undesirable) » 2017-12-15 16:23:21

So it's probably the same as this issue.

You could try using noapic or nolapic as a kernel parameter, it's been known to fix some blank screen issues in the past.

Or try with the latest kernel from ascii-backports.

apt-get -t ascii-backports install linux-image-4.13.0-0.bpo.1-amd64

Failing that you could try to use the xorg vesa driver instead of the intel driver.

#22 Re: Installation » Black Screen on Devuan Ascii - acpi=off solves it (undesirable) » 2017-12-15 10:35:56

It's helpful to narrow down the issue a bit. At what point does the screen go black? Is it immediate or only when the xserver starts?

#23 News & Announcements » Migration to ASCII instructions » 2017-12-15 09:57:57

Replies: 0

Instructions for migrating to ascii are now available.

So far I have tested these instructions as working for migrating from Debian Jessie and Stretch. The newer instructions include migrating away from the GNOME desktop and network-manager (there is no transitional package for that in ascii yet).

Please open an issue if you encounter problems. Also feel free to open an issue if you spot something that has changed at a later time, and I will update the migration steps.

#24 Re: News & Announcements » Upgrading to ASCII instructions » 2017-12-09 04:11:38

[Updated post]

Instructions to migrate from Debian are now available here.

#25 News & Announcements » Upgrading to ASCII instructions » 2017-12-07 18:49:28

Replies: 6

For those who want to upgrade to ASCII, I have made the instructions available on my wiki here. The instructions are only for upgrading from Devuan Jessie to Devuan ASCII. I expect this to be straight forward except for non-standard installs, but please open an issue if you experience any problems.

Board footer

Forum Software