You are not logged in.
Anyone else found this? Perhaps there is a uBlock Origin update to counter it?
Yes, but not all videos - black screen appears; I mute the audio (shortcut M) until the skip button appears (after 5 seconds).
Searching the uBlock Origin issue tracker reveals it to be a common issue:
//github.com/uBlockOrigin/uBlock-issues/issues?q=youtube
It isn't clear from the "ALL youtube.com issues #7636" whether it needs a fix via uBlock Origin or via the filters or both.
-
I will stop using YT is this goes on.
Statements like that are meaningless. Even if YouTube saw it, they don't care.
Irrespective of what happens in the browser, you can always use yt-dlp to download the videos, bypassing any in-browser advertising, and play the video offline.
I did a KDE Plasma install with --no-install-recommends once.
The result was useless.
It still gave me numerous packages I absolutely did not need, and it took me a while to figure out the reason a bunch of things were not working was because several actually useful packages were mis-labelled as recommends.
-
It would be nice if package maintainers were required to state why something is recommended/suggested, so that people could make informed decisions about when to include/exclude them, (and maybe get the maintainers to think a bit harder about which level a dependency belongs in).
I tried to lookup at the debtree for kde-plasma-desktop but it timed out, and now pkginfo.devuan.org is returning 504 Gateway Time-out even for simple package lookups - I guess the KDE dependencies were too complicated and something crashed or locked up?
-
Anyway, what does apt rdepends systemd-coredump return?
Probably drkonqi ("Crash handler for Qt applications"), which plasma-workspace depends on.
Bullseye/Chimaera version of drkonqi didn't require systemd, but seems Bookworm/Daedalus version might:
https://packages.debian.org/bullseye/drkonqi
https://packages.debian.org/bookworm/drkonqi
According to the banned package list, both systemd and systemd-coredump is banned for "daedalus" and "daedalus-proposed-updates" but not "daedalus-security" and "daedalus-updates" ?
So Alex having the daedalus-proposed-updates repo enabled may explain the difference, though not clear why systemd packages are not banned for ALL repos?
It's a lot.
And to get an idea of how much a lot...
awk '$1=="Size:" {qty+=1;size+=$2}
ENDFILE {print "qty: "qty,"size: "size,"(~"int(1+size/1024^3) "G)","file:" FILENAME}
' /var/lib/apt/lists/*Packages
No point downloading an entire repository when the most common stuff is in the 4GB "desktop" ISO, and that can be supplemented with other necessary packages in various different ways.
I would possibly start with reading //blends.debian.org/blends
You'll be waiting a long time unless you actually provide details on what you are trying to do.
Your Bluetooth would seem to be working.
How to use it is different for attaching a mouse/keyboard, or transferring files, or playing audio via a speaker, or receiving GPS data, or ..., etc.
Again, we cannot read your mind - you need to provide details (both in the title and first post) rather than have people squeeze the information out of you.
A search that combines "bluetooth" with "xfce" and whatever you're actually trying may well provide the answer - if not, detail what you're trying, and where you're stuck. (If you're following any guides, include the links; but beware guides for Ubuntu or Arch which may be common but may do things differently to Devuan.)
DistroWatch also provides the ability to review and rank a distro and reports the averages of the ratings.
In that ranking, when limited to distros with over 100 reviews, six of the top ten are non-systemd distros:
1 Void
2 Devuan
3 Artix
4 Arch
5 TrueNAS
6 Slackware
7 Debian
8 Mint
9 openSUSE
10 Q4OS
Although, since ~75% of them have a "Most Frequent Rating" of either 10 or 1, they're clearly not objective/reliable ratings... *shrug*
DistroWatch is working exactly as it should/describes:
The following distributions match your criteria (sorted by popularity):
They simply show the number of times a distribution page on DistroWatch was accessed each day, nothing more.
So it isn't necessarily a meaningful stat, but at the same time it probably encourages people to go for distros higher in the list.
The correct conclusion is not that the search results are wrong, but that Devuan does not have enough people interested in it.
A bigger problem may be the general lack of popularity of any non-systemd distros - because, given MX Linux supports sysvinit or systemd, there are actually none in the top 10...
Start by running inxi --system --bluetooth --extra 3 (or inxi -SExxx) and showing the results here (within [code]..[/code] tags to preserve formatting).
If inxi isn't installed, install it. You may need to be root to get bluetooth info, and you can also try rfkill list as root to confirm the hardware is active.
about:preferences is a user-friendly front-end, for the real settings, check about:config and/or the prefs.js file in the profile directory (which gets updated when you exit the browser).
Also check whether there's any "safebrowsing" crap that's blocking it?
A quick search reveals the main setting is (should be) a three option radio group, looking something like this:
https://assets-prod.sumo.prod.webservic … a011a8.png
The documentation also shows how to configure the per-site setting, which has an explicit On/Off drop-down:
//support.mozilla.org/en-US/kb/https-only-prefs#firefox:linux:fx102
Of course. Devuan is intended to do everything Debian does, except systemd-related stuff.
If you've identified a situation where that isn't the case, you need to provide details.
I hope someone will manage to restore it to the repos in due course.
Hoping wont make it happen any quicker.
On the other hand, a polite nudge to the relevant Debian maintainer - asking if the changes made were sufficient, or if there is still more to do - may well have a positive impact.
Since there's no systemd involved, this is not a Devuan issue.
The answers for why packages are removed from Debian repos can be found via the Debian package tracker via //tracker.debian.org/PACKAGE_NAME
Migration status for pysolfc (- to 2.6.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Updating pysolfc would introduce bugs in testing: #1008708, #1039723
The root issue seems to involve a potential license violation which was since clarified so maybe someone interested needs to prod the relevant Debian maintainer to see if the latest version can be restored.
jue-gen, you quoted my entire post (despite it being the immediately preceding message), but didn't actually respond to any of it...?
You haven't said why you want to do this. ("I did it with Debian" is not a reason.)
Testing and Unstable (whether Sid or Ceres) are not an upgrade, they are development tools for those helping to test potential future versions of packages - i.e. software that has yet to be verified as stable and secure.
If one actually wants to help test, great. Or as a learning tool (as above), fine. Other reasons for running Unstable are probably the result of a misunderstanding and would be better served by running something else, but what else depends on the specific reason(s) for running it.
Anyone with good reason to run Devuan Testing or Devuan Unstable should have an understanding of the mechanism through which Debian becomes Devuan. Anyone who understands that process would also understand the potential additional issues involved, and wouldn't need to ask about differences between Sid and Ceres. (Put another way, to know the differences, learn how Devuan works.)
Now I am itching to try testing or even Ceres.
What does that even mean? What exactly do you want to try?
Testing and Unstable are developer tools, for those that wish to assist with finding and fixing bugs.
They are explicitly not a released distro and frequently do not get timely security updates.
Do NOT install Testing or Unstable:
1) on any system you cannot afford to have out of action;
AND
2) if you are not willing to diagnose and report issues via the appropriate bug trackers.
If one has an obsession with shiny things and no desire to help develop/test, use a distro like Artix Linux instead, otherwise stick to a supported stable release, and use Backports if one needs specific newer firmware/software for whatever reason.
Yeah, like if you had this situation:
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 50G 20G 30G 40% /
/dev/sda2 450G 80G 270G 18% /home
You'd want a single 100GB sparse file, which still retains the 500GB capacity.
Anyone know how to copy an entire hard drive onto a qcow2 image but with only the space being used as being counted?
No, but I have spent a significant amount of time trying various solutions that didn't work, before eventually giving up and converting each partition to its own file, with qemu-image convert.
So you have a bad config file, which is likely why the service fails to start.
cupsd.conf should not be a binary file - what is telling you that it is? (The error log say there are unknown directives, which suggest it is not binary, but maybe for a different version.)
Try checking file /etc/cups/*cupsd* to see if you have a backup that reports as "ASCII text" - if so, you could try diff to see if it can identify a problem, and/or rename the current bad file and copy the backup file into its place.
my up to date FF-ESR tells me no connection to https://localhost:631.
Browsers frequently hide real errors, and complicate things with caches and cookies; usually better to diagnose things directly.
What does curl -Iv localhost:631 say?
Check with ss -ltnp sport 631 (as sudo/root) whether the server is running?
Anything relevant in the logs - i.e: tail /var/log/cups/*_log ?
You posted this in "Documentation" section, which is intended as "How-tos and Tips & Tricks contributed by Devuan users", but didn't give details.
It may help others to be explicit about which of the various settings within logind.conf solved the problem?
Charon795 wrote:I write this command but it gives me an error:
bash: .themes: command not found
what should I do?Hello.
Please, check, maybe this dir (.themes) already exist.
Nope, it's because they exactly copied what was written in the other thread $mkdir .themes
Since there is no variable "mkdir" it evaluated to empty string, and thus was removed, leaving ".themes" which Bash tried to execute as a command, and since there isn't such a command, it displayed "command not found".
-
Open a terminal and type
ls -a
If this dir does not exist, create this dir with command:
$ mkdir .themes
...
The command is mkdir .themes - no dollar - just like you didn't put a dollar for the ls -a command.
Yes, the dollar is the prompt - experienced users know that, but new users don't - so it should be explicitly pointed out, or not used - personally, I'll only include a prompt when displaying both input and output. When offering advice for a specific command to run, it's less confusing to not use it. (Especially when one forgets the space and doesn't spot it whilst proofreading. Or writes one command with it and one without.)
-
Charon795:
It's a good practice to always verify what a command does before you enter it. Putting "man $mkdir" into a search engine would have clarified that the correct command is "mkdir" and explained what it does. The best source for Devuan is Debian man pages //manpages.debian.org
A dollar at the start of a command is usually the shell prompt (and thus not intended to be typed), but elsewhere in a command it can be a shell variable, and those can significantly change what a command does.
Something else worth pointing out - when a file or directory name starts with a "." it is considered "hidden" and not always displayed. This is why the need for ls -a instead of just ls. If you use a graphical file manager, it will have an option to toggle hidden resources on/off, which you would want to do if managing this folder with such a tool.
Also, if you prefer to reduce the number of files/directories directly in your home, you might prefer to use .local/share/themes instead of .themes
Someone just sent me this: https://transfer.sh/Lr44QJPhCW/powered_by_devuan.png
Would look better to get the text off of the swoosh and jammed in the corner. I'd line it up to the RH side. Would be much more balanced.
I guess since I didn't specify a font it varies based on whatever the system's default might be - on the system I tested that the +0+6 meant there was enough space, but obviously other fonts need different numbers.
I'm happy to experiment with some fancier variant(s) with colours/borders/shadows/etc and see what people think - is the swoosh with dots emblem from that page still valid?
Adding text to an image is easy enough...
curl -LO https://git.devuan.org/devuan/documentation/raw/branch/master/art/graphics/devuan-logo-1000x200.png
convert devuan-logo-1000x200.png \
-gravity south -extent 1000x280 \
-gravity northwest -pointsize 72 -annotate +0+6 'Powered by' \
-scale 20% \
powered_by_devuan.png
If convert doesn't exist, try gm convert or convert-im6 and if those also fail, they can be obtained from either GraphicsMagick or ImageMagick.
(Or just use the regular image inside a HTML div with some basic CSS styling.)