ttkv | msg NickServ REGISTER password youremail@example.com | 02:30 |
---|---|---|
ttkv | oops | 02:30 |
olblak8 | /!\ АTΤN: Tһіs ⅽһaᥒnеl һas mо∨ed tο іrc.frᥱenоⅾe.net #osirisⅼab ∕ǃ\ | 02:45 |
DocScrutinizer05 | ttkv: you don't want to send that commend, even with correct leading / | 03:08 |
amarsh04 | I have plasmashell running fine on my i386 installation but not my x86-64 installation on another machine - do you think I'd be alright asking for troubleshooting help in #debian-kde ? | 07:47 |
golinux | That might not work because devuan uses eudev not udev and the session management is tailored differently. | 07:51 |
golinux | You might want to look a the release notes. https://files.devuan.org/devuan_ascii/Release_notes.txt | 07:51 |
golinux | Everything is explained in there. Debian devs won't know a thing about that. Of course your issue might be independent of that . . . | 07:53 |
amarsh04 | thanks golinux - given that aside from the i386 / x86-64 difference, the two machines are running the same versions of KDE-related software and this issue has persisted for several weeks in the x86-64 machine, I suspect it is more of a configuration issue than the actual executables / libraries | 08:08 |
amarsh04 | if I can see where the behaviour differs that might help | 08:08 |
amarsh04 | I tried in a different user account on the x86-64 machine and had the same problem | 08:09 |
amarsh04 | next I might create a completely new account to see what happens | 08:10 |
golinux | Good luck! Sorry I know next to nothing about KDE . . . | 08:12 |
amarsh04 | that's ok, thanks for commenting | 08:19 |
premoboss | hello. devuan 2.0 here. When i do "dmesg" and i am unprivileged user, i got reply: "read kernel buffer failed: Operation not permitted". Shall i be forced to root just to read dmesg? is not a problem, but is annoing. what is the tecnical reason to dont allow to not-root user to see dmesg? | 09:44 |
golinux | There are more annoying permission changes than that coming down the tubes in beowulf . . . | 09:45 |
premoboss | golinux, "fun" wews never stop to came, i see. | 09:46 |
golinux | I've been trying to work through it for a few days. | 09:47 |
golinux | Indeed . . . it never seems to stop. | 09:47 |
premoboss | untill devian take me far from systemd, is ok to me. | 09:49 |
KatolaZ | premoboss: no you are not forced to be root | 09:53 |
KatolaZ | you should put | 09:53 |
KatolaZ | echo 0 > /proc/sys/kernel/dmesg_restrict | 09:53 |
KatolaZ | in your rc.local | 09:53 |
KatolaZ | /etc/rc.local | 09:53 |
premoboss | KatolaZ, thanks | 09:53 |
KatolaZ | if you execute that command as root, you should be able to see dmesg as regular user | 09:54 |
KatolaZ | access to dmesg has been disabled by default in the kernel | 09:54 |
KatolaZ | (not by Devuan) | 09:54 |
KatolaZ | and I think it's a good thing overall | 09:54 |
premoboss | KatolaZ, why this... ah, by kernel. ok | 09:54 |
premoboss | maybe they thin an attacker can find some clues into dmesg to do further attacks | 09:55 |
premoboss | ok | 09:55 |
KatolaZ | premoboss: i guess the reason is not J Random Hacker | 09:57 |
KatolaZ | :) | 09:57 |
* man_in_shack hacks KatolaZ | 09:57 | |
premoboss | "J Random Hacker"... what do you mean? | 09:57 |
KatolaZ | bbl | 09:58 |
man_in_shack | what DON'T you mean? | 09:59 |
premoboss | i dont undestand what KatolaZ what to say with the sentence: "i guess the reason in not J Random Hacker". | 10:02 |
* KatolaZ has been hacked....feels dizzy.....faints....falls on the floor... | 10:02 | |
man_in_shack | GOOD | 10:03 |
rrq | premoboss: I think it's blocked by default as it otherwise breaks the perceived isolation between "containers" (LXC); that a program in one container can gain information about other containers, which has a long-shot implication of badness happening. | 10:16 |
furrymcgee | container everywhere in kernel and on freenode | 10:26 |
* rrq back from washing my mouth with soap | 10:33 | |
man_in_shack | GOOD | 10:41 |
devoid_ | god damn | 11:15 |
devoid_ | what an edgy satanist fellow | 11:15 |
RebelCoderRU | Guys, is there an ISO with Testing (beowolf) branch ? I have installed the ascii and changed repos to beowolf, but a fukll-upgrade actually broke the system. | 14:31 |
RebelCoderRU | Is there an ISO I can install with Testing branch ? | 14:31 |
furrymcgee | No, I dont think there iso beowulf already available, what went wrong in fukk-upgrade? | 14:39 |
xrogaan | There are some dbus calls with a --systemd argument in the files located at /etc/X11/Xsession.d/ | 17:00 |
xrogaan | one, for example, dbus-x11: /etc/X11/Xsession.d/95dbus_update-activation-env | 17:01 |
gnu_srs2 | furrymcgee: https://pkgmaster.devuan.org/devuan/dists/unstable/main/installer-i386/current/images/netboot/mini.iso for i386 and | 17:02 |
gnu_srs2 | https://pkgmaster.devuan.org/devuan/dists/unstable/main/installer-amd64/20181125/images/netboot/mini.iso for amd64. | 17:02 |
_abc_ | Hi. | 19:24 |
_abc_ | What's the upgrade paths from ascii 1.0.0 to 2.0.0 please? | 19:25 |
_abc_ | And is it worth it | 19:25 |
KatolaZ | _abc_: ascii is Devuan 2.0.0 | 19:26 |
_abc_ | I am confused then? /topic : Latest | 19:27 |
_abc_ | (2018-06-09): ASCII 2.0.0 | 19:27 |
KatolaZ | _abc_: you asked: | 19:27 |
_abc_ | I think I'm on ascii release 1.0.0 ? Or is that not possible | 19:27 |
KatolaZ | 19:27 < _abc_> What's the upgrade paths from ascii 1.0.0 to 2.0.0 please? | 19:27 |
KatolaZ | I am telling you that Devuan 2.0.0 is called ascii | 19:27 |
KatolaZ | while Devuan 1.0.0 is called "jessie" | 19:27 |
KatolaZ | so your question is ill-posed | 19:27 |
_abc_ | But is ASCII 2.0.0 one and the same with devuan 2.0.0 ? | 19:27 |
KatolaZ | 19:30 <+KatolaZ> I am telling you that Devuan 2.0.0 is called ascii | 19:28 |
KatolaZ | ascii is the *codename* for Devuan 2.0.0 | 19:28 |
_abc_ | Ok. | 19:28 |
_abc_ | ls there a place to put a /etc/Release file on devuan? A standard one? | 19:29 |
_abc_ | Or a high level upgrade/update log? A la "$(date): upgrade from ascii to xxx" ? | 19:29 |
KatolaZ | _abc_: what do you mean by a "/etc/Release" file? | 19:31 |
_abc_ | Just a file which documents what the presently running system is called and versions and such | 19:31 |
KatolaZ | /etc/devuan_version | 19:31 |
KatolaZ | /etc/issue | 19:32 |
KatolaZ | but the most important thing is what you actually have in /etc/apt/sources.list | 19:32 |
KatolaZ | that determines which distribution you are actually running | 19:33 |
_abc_ | version is ascii/ceres | 19:33 |
_abc_ | I assume that is the "latest" then | 19:33 |
KatolaZ | _abc_: what do yu have in /etc/apt/sources.list? | 19:35 |
_abc_ | deb http://pkgmaster.devuan.org/merged ascii main contrib non-free etc etc | 19:41 |
KatolaZ | then you are on ascii | 19:45 |
mchasard | hi | 20:23 |
mchasard | i installed crowz devuan distro under vbox it works fine | 20:23 |
mchasard | but when i try to install really under another 32bits machine | 20:24 |
mchasard | with liveusb the install stop cause it doesn't find any cd ....but its an usblive key | 20:24 |
mchasard | its the same iso file that i used | 20:25 |
mchasard | i really wanted to install it | 20:25 |
mchasard | is it due to the usb live key ? | 20:26 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!