You are not logged in.
same in ceres/sid, with atril 1.26.0-2 .
(topic shouldn't be marked as solved imho, installing another app, doesn't solve atril's problem.)
in my case i see these in .xsession-errors :
(atril:12486): WARNING **: 12:17:46.086: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Avahi was not provided by any .service files
[ 13/12/2022 12:18:06.680 x_create_picture_with_pictfmt_and_pixmap ERROR ] failed to create picture (X error 9 DRAWABLE request 139 minor 4 serial 6369528)
[ 13/12/2022 12:18:06.693 paint_one ERROR ] Window 0x03001f39 is missing painting data.
[ 13/12/2022 12:18:06.694 x_create_picture_with_pictfmt_and_pixmap ERROR ] failed to create picture (X error 9 DRAWABLE request 139 minor 4 serial 6369559)
this should be asked on fluxbb forum, not here.. i don't think devuan chose to leave some messaging option out, it's probably not supported by forum software (fluxbb).
btw, mastodon is social media, not a messaging application.. so i don't think even fluxbb would care about it.
was sure i had that posted before : https://dev1galaxy.org/viewtopic.php?pid=24970#p24970
https://sledjhamr.org/apt-panopticon/results/Report-web.html even lists devuan.bio.lmu.de as a "faulty mirror"! Will this lead to this one being removed, or will the maintainers be contacted? I wrote some email to the LMU Munich, but I'm not sure if they will reach the correct addressee …
better contact mirrors@devuan.org
deb mirror+file:/etc/apt/mirror_list.txt chimaera main
mirror_list.txt should contain only mirror urls , eg
https://pkgmaster.devuan.org/merged
it's not supposed to be the same as https://pkgmaster.devuan.org/mirror_list.txt. not the same format to use.. completely different things...
and no, i don't know of a similar netselect tool for devuan.
1. use a single mirror that works. eg.
deb $mirror_url chimaera main
2. use a mirrors.txt file with mirrors you want to use. exclude the one you don't want. eg.
deb mirror://path/to/mirrors.txt chimaera main
3. contact mirrors@devuan.org to fix broken mirror.
offtopic.
still on ceres and runit. still can boot, still got network, still got all devices.. (no nvidia sh*t).
from my experience, you can't just adjust the guide for bullseye to sid. releases can differ a lot.
in anycase, base-files should/could be replaced too. devuan version for sid/ceres is 12.2devuan2.
so, remove all debian repos, and post the output of `apt install base-files/unstable`..
edit] hoas beat me to it.
deepforest wrote:I am on Ceres almost year and nothing is broke yet.
Give it time
i'm on sid/ceres for more than 15years and will never change it
And enjoy the massively outdated packages during the upcoming freeze. The Debian devs sometimes even leave critical bugs unfixed in the development branches until the release is done...
oh come on, having more outdated packages than stable is never true for sid.. (testing having newer packages prior to release, might) ;-)
golinux wrote:Ceres is always fluid and unstable. It never freezes.
Debian sid certainly freezes. There may be a few package updates but not many. At least in my recent experience.
this.
sid also "freezes". no updates coming in while testing freezes to become stable. exception might be some last RC updates, but even that, stop completely a few days prior to release.
and sid is not always fluid and unstable. most of the time it's pretty stable, but oh well, not always. (and stable is not always stable either..)
for those wanting to try sid/ceres, keep backups at all times.for that moment something breaks in sid, you'll certainly want a backup available.
so dns looks fine now and it's just a browser problem. better send a bug report in those browser projects.
dig and ping only work for domain names, not HTTP urls...
so try :
dig lists.alpinelinux.org
ping lists.alpinelinux.org
dig distrowatch.com
ping distrowatch.com
etc...
you can also try
dig distrowatch.com @8.8.8.8
and post output here...
nothing seems wrong above.. curl which works with urls seems to work just fine. an "output a mile wrong" probably seems correct...
your `curl https://lists.alpinelinux.org` shows 404 (works fine here), which mean it resolves succesfully, but didn't find the resource..
in general i would say you're experiencing network issues. or clock is failing, or something was manually changed in /etc/hosts or local resolver or router or isp or....
no outrage here, chill out.
just saying you wrote something wrong... you could have admitted it's true, but still dont.
and this nobody-cares-thread was revived today by others.. that's how i saw it, didn't search 6months back threads.. pff..
btw, you need special tools to check fakes/rootkits/backdoors on any system.
anyway, got better things to do than argue about obvious things, such as misinformation.
always wondered about avatars here
thx
I have no edit privileges, the post is too old. Also it's not completely wrong, it's still mostly true, and if you had had systemd packages.
checking is one thing, everyone should do with/without systemd.
but saying that systemd packages contain backdoors is completely wrong.
these backdoors, have nothing to do with systemd other than using some systemd daemons name to hide from users/admins.
so, the backdoor was not discovered on systemd (source/binary) packages, just uses these names to hide itself : "systemd-daemon" and "gvfsd-helper" .
OP i think you should rephrase the title and description, it's completely wrong. (=clickbait).
right, did you check page source? well : "Some search results derived from Microsoft. Privacy Policy"
so, they're just using Bing (=M$) which is more relaxed to "resellers" and collects same amount of data as google.
just use a metasearch like searx, or yacy search engine or some other one.. lots of search/metasearch engines around.
tl;dr: use a signed, unified kernel image verified by TPM, all integrated into the boot process by the init system that shall not be named. Full encryption support is also provided, just like BitLocker.
I have to say that I do approve of this. I've been booting with signed, unified kernel images for quite a while now :-)
excuse my ignorance, but do you care to explain a bit more.. (?)
in particular, everything seems to be dependent on TPM chip/firmware.. what happens in the case of "evil"/broken/taken out TPM?
how's that (=putting another "middle man" in boot process) a good thing?
p.s. not understanding much on UEFI/SecureBoot/TPM, so it can be that i'm completely ignorant on these
fuck off nazi scum.
i have the exact opposite question, but without nvidia @#%#%.
why are slowwwwww windoze still around?
had to check a friends laptop (similar specs to mine) with win7 and waited to open a browser for ~15". opens up instantly here (devuan ceres x64)...
ofcourse many factors count. running processes, drivers, hdd, ram, etc.
the only time i had to admit windoze felt smoother-faster, was winxp on a really old laptop, compared to debian lenny (or squeeze?) at the time (not sure which one).
even tried older debian releases on floppy, but still i couldn't get descent system response like on winxp.. anyway, that was a decade+ ago...
ps. win7 are not supported anymore, so no updates. etc..
no issues here, but not running gnome or vmware nor virtualbox.
anything strange on ~/.xsession-errors | dmesg | messages ?
you need to check why gnome-keyring is using 100% cpu to locate the issue.
perhaps stop some services that use it (cups, avahi, dnscrypt-proxy, bluetoothd, other?) to see if that helps..
p.s. packages don't install without consent. check your dpkg/apt log to see what happened. something else happened during dist-upgraded, you probably consented without taking much attention...
suggestion : better not dist-upgrade next time. simple `apt upgrade` will save you some ceres trouble next time.
no such problem here (same version - testing/ceres). not a single libsoup message in virt-manager --debug. vms window open/work normally as always.
i would say problem is on some virt-manager installed recommendation, and not on actual virt-manager. eg. check this bug, it's similar :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019339
maybe some gnome thingy(?)
tor browser uses it's own bundled tor server running in port 9051 iirc.
so it actually uses a different onion circuit than your locally installed tor server.
just tried official devuan onion repo and it downloads slowly( average : 65,6 kB/s), but no connection errors so far..
what devuan/tor version are you using?
liquorix is the only kernel i've tried that doesn't post errors on boot about tpm module missing.
default debian kernel, antix kernel and linux-libre, keep displaying not found messages about it....
so i prefer to use those instead of liquorix...