Re: Debian 12.5 upgrade error
On Sun, 2024-02-11 at 21:37 +0900, Byunghee HWANG (황병희) wrote: > Hellow Alexis, > > > What command did you type exactly? > > In normal cases, i do like this: > > > sudo su - > apt update > apt upgrade > > I logged on as root on tty1 /etc/init.d/lightdm stop apt update apt upgrade I always do minor and major version updates on a tty with no GUI running.
Debian 12.5 upgrade error
I have encountered an error upgrading to 12.5 from 12.4 regarding the nvidia-driver and linux-image 6.1.0.18. The error is: env NV_VERBOSE=1 make -j8 modules KERNEL_UNAME=6.1.0-18- amd64(bad exit status: 2) I get that error twice. After the upgrade I get a non-bootable 6.1.0-18 image. Doing some fiddling, I got a bootable 6.1.0-18 image but no GUI. I removed linux-image and linux-headers 6.1.0.-18 an I now have 6.1.0.-17 working. Has anyone else encounter this issue?
Re: Mouse single click handling?
On Tue, 2023-12-19 at 17:01 +0100, local10 wrote: > Dec 19, 2023, 15:30 by hfollm...@itcfollmann.com: > > I've been replacing them, I have 4-5 mice like that, they all fail > with the same defect after 6-12 months or so. So I thought perhaps > there was a way to fix them instead of buying a new one every 6-12 > months. > Been there done that. Cheap mice have cheap switches which fail sooner than later. Gaming mice are more expensive, but they are rated for 10- 20million clicks. Way more than than the cheap ones. In the long run those gaming mice come cheaper. I have an Evga X3 mouse at work i got in 2018. It still works and it cost just 30 euros.
Re: Problem with php after upgrading to Bookworm
On Thu, 2023-12-14 at 12:28 -0700, Charles Curley wrote: > On Thu, 14 Dec 2023 19:24:19 +0200 > Alexis Grigoriou wrote: > > > All > > I see is probably the php code. If I remember correctly, before the > > upgrade php 7.4 was installed in my Bulleye installation. There is > > a > > directory in /etc/php/7.4, although 8.2 is the default in Bookworm, > > but there is no /etc/php/8.2 directory. > > Do you know for a fact that you have php 8.2 installed? The > /etc/php/8.2 directory should be there. What do you get when you run: > > dpkg-query --show 'php*' > Please run that in a terminal window, and copy and paste the results, > including the command prompt and the trailing prompt, into your reply > email. root@bfs# dpkg-query --show 'php*' php-amqp php-apcu php-ast php-calendar php-cgi php-cli php-common 2:93 php-crypt-gpg php-ctype php-ds php-exif php-facedetect php-ffi php-fileinfo php-ftp php-gd php-gearman php-gmagick php-gnupg php-iconv php-igbinary php-imagick php-json php-libvirt-php php-lua php-mailparse php-memcache php-memcached php-mongodb php-msgpack php-mysqli php-mysqlnd php-mysqlnd-ms php-oauth php-opcache php-pcov php-pdo php-pdo-mysql php-pear php-pecl-http php-phar php-posix php-ps php-psr php-radius php-raphf php-readline php-redis php-rrd php-shmop php-smbclient php-sockets php-ssh2 php-stomp php-sysvmsg php-sysvsem php-sysvshm php-tideways php-tokenizer php-uopz php-uploadprogress php-uuid php-xdebug php-xmlrpc php-yac php-yaml php-zmq php5.6-common php5.6-json php7.0-common php7.0-curl php7.1-common php7.2-common php7.2-sodium php7.3-common php7.4-calendar php7.4-cgi 7.4.33-1+deb11u4 php7.4-cli 7.4.33-1+deb11u4 php7.4-common 7.4.33-1+deb11u4 php7.4-ctype php7.4-exif php7.4-ffi php7.4-fileinfo php7.4-ftp php7.4-gd 7.4.33-1+deb11u4 php7.4-gettext php7.4-iconv php7.4-json 7.4.33-1+deb11u4 php7.4-mysql7.4.33-1+deb11u4 php7.4-mysqli php7.4-mysqlnd php7.4-opcache 7.4.33-1+deb11u4 php7.4-pdo php7.4-pdo-mysql php7.4-phar php7.4-posix php7.4-readline 7.4.33-1+deb11u4 php7.4-shmop php7.4-sockets php7.4-sysvmsg php7.4-sysvsem php7.4-sysvshm php7.4-tokenizer php8.0-common php8.1-common phpapi-20190902 root@invader:/etc/php/7.4# apt update > Even if php8.2 itself is installed, you will likely need other php8.2 > packages. > > Also, to make things easier down the road, install the generic > equivalent of a php package. E.g. php-imagick rather than > php8.2-imagick. > I also installed php-imagick along with it's dependencies but I still get the same result.
Re: Problem with php after upgrading to Bookworm
On Thu, 2023-12-14 at 18:07 +, Michael Kjörling wrote: > On 14 Dec 2023 19:24 +0200, from ale...@nanoid.net (Alexis > Grigoriou): > > As the subject states pages using php won't disply in the browser. > > All > > I see is probably the php code. > > Well, first things first. What web server are you using to try to > serve those pages? > I am using apache root@bfs:apt show apache2 Package: apache2 Version: 2.4.57-2
Problem with php after upgrading to Bookworm
Greetings, As the subject states pages using php won't disply in the browser. All I see is probably the php code. If I remember correctly, before the upgrade php 7.4 was installed in my Bulleye installation. There is a directory in /etc/php/7.4, although 8.2 is the default in Bookworm, but there is no /etc/php/8.2 directory. I don't code/script, so I am completely lost here. Any help would be appreciated. Any more info need to help out will be available. TIA
Re: IMPORTANT: do NOT upgrade to new stable point release
On Sat, 2023-12-09 at 13:09 -0500, Dan Ritter wrote: > > > The new kernel release is reported to contain an ext4 data > corruption bug. It's prudent not to upgrade, or if you have > started to upgrade, not to reboot, until a new kernel release > is prepared. > I just upgraded to Bookworm this morning. I did reboot a couple of times but there seems to be no problem (yet). Is there anything I should look for or do other than rebooting?
Re: questions about cron.daily
On Thu, 2023-04-06 at 19:05 +0200, Thomas Schmitt wrote:
> Hi,
>
>
> Pierre Frenkiel wrote:
> > crontab -l
>
> Plus:
> man 5 crontab
> which has in its section "EXAMPLE CRON FILE"
>
> # run five minutes after midnight, every day
> 5 0 * * * $HOME/bin/daily.job >> $HOME/tmp/out 2>&1
>
> and explains further up
>
> The format of a cron command is very much the V7 standard,
> with a num‐
> ber of upward-compatible extensions. Each line has five time
> and date
> fields, followed by a command, followed by a newline character
> ('\n').
> ...
> field allowed values
> - --
> minute 0-59
> hour 0-23
> day of month 1-31
> month 1-12 (or names, see below)
> day of week 0-7 (0 or 7 is Sun, or use names)
>
> So the command shown by Greg Wooledge runs at 6:25 am the comand
>
> test -x /usr/sbin/anacron || ( cd / && run-parts --report
> /etc/cron.daily )
>
> which runs the programs in /etc/cron.daily (by run-parts(8)) if not
> /usr/sbin/anacron exists and is executable.
>
https://crontab.guru has a very nice explaining also.
Re: Can not start a script with systemd
On Sun, 2022-03-13 at 16:46 -0400, Greg Wooledge wrote: > If it requires environment variables like HOME to be defined, then > you > might need to add those. Either in the unit file, or in the wrapper > script. > > Looks like the systemd version uses an "Environment=" directive, from > systemd.exec(5). (The hardest part of all this is guessing which man > page each thing is in, because there are at least three separate man > pages -- systemd.unit, systemd.service, systemd.exec.) I got it working, but not how I would rather like it. But I will post my solution just in case anyone benefits from it. It seems that the User= directive does not load the user's environment, so I ommited that directive. From the unit file I call a script that does 'su -c aaserver' and everything after runs as the aaserver user. aas.service === [Unit] Description=Alien Arena Dedicated Server [Service] Type=forking WorkingDirectory=/home/aaserver ExecStart=/home/aaserver/saas.sh [Install] WantedBy=multi-user.target === saas.sh === #!/bin.sh su -c aaserver '/home/aaserver/aas.sh' > /dev/null & === aas.sh === #!/bin/sh screen -S cir -d -m rlwrap -A /home/aaserver/aa/alienarena-ded +set \ game arena +exec ctfir.cfg === In my 1st post I ommited the screen command to keep things simple. And thanks again for your help and time, much appreciated
Re: Can not start a script with systemd
On Sun, 2022-03-13 at 10:17 -0400, Greg Wooledge wrote: > Or, if you want to get rid of the wrapper script entirely: > > = > [Unit] > Description=Alien Arena Dedicated Server > > [Service] > Type=exec > User=aaserver > WorkingDirectory=/home/aaserver/aa > ExecStart=/home/aaserver/aa/alienarena-ded +set game arena +exec > ctfir.cfg > > [Install] > WantedBy=multi-user.target > = Thanks for your informative reply and making things more clearer to me. I still get an error and alienarena-ded does not load. I forgot to mention that the server doesn't run in the background but when loaded it stays in it's console. I tried all the options you suggested, with and without the wrapper script and as exec and forking type. I did like your last approach which I hoped would have worked. It does seem more simple to let systemd handle the whole thing. Oh, and one more thing, the .cfg file is in a other directory (~/.local/share/cor- games/arena) I do believe this has to do with some XDG stuff, but I assume that the User=aaserver directive handles that.
Can not start a script with systemd
Hello list, I'm running a game server on a VPS (Alien Arena). I have a script to load it and it works fine when I invoke it. However when trying to load it from systemd it always fails. Also this is my first attemp to load something from systemd. Fresh install debian stable fully updated. The script to start alienarena-ded: #! /bin/sh killall alienarena-ded sleep 5 cd /home/aaserver/aa ./alienarena-ded +set game arena +exec ctfir.cfg exit 0 And the unit file: [Unit] Description=Alien Arena Dedicated Server [Service] Type=exec User=aaserver ExecStart=/home/aaserver/aas.sh ExecStop=/usr/bin/killall alienarena-ded ExecReload=/home/aaserver/aas.sh [Install] WantedBy=multi-user.target For the service type I have tried exec, simple and forking. All have the same behaviour: aas.service - Alien Arena Dedicated Server Loaded: loaded (/etc/systemd/system/aas.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2022-03-13 12:13:40 CET; 7min ago Process: 3053 ExecStart=/home/aaserver/aas.sh (code=exited, status=0/SUCCESS) Process: 3059 ExecStop=/usr/bin/killall alienarena-ded (code=exited, status=1/FAILURE) Main PID: 3053 (code=exited, status=0/SUCCESS) CPU: 11ms Mar 13 12:13:35 nanos systemd[1]: Starting Alien Arena Dedicated Server... Mar 13 12:13:35 nanos systemd[1]: Started Alien Arena Dedicated Server. Mar 13 12:13:35 nanos aas.sh[3054]: alienarena-ded: no process found Mar 13 12:13:40 nanos killall[3059]: alienarena-ded: no process found Mar 13 12:13:40 nanos systemd[1]: aas.service: Control process exited, code=exited, status=1/FAILURE Mar 13 12:13:40 nanos systemd[1]: aas.service: Failed with result 'exit-code' Any help is appreciated TIA
Re: how many W a PSU for non-gaming Debian?
On Fri, 2022-03-04 at 16:24 +0100, Emanuel Berg wrote: > I've heard that for gaming you would want a 600~800W PSU [1] > but how do I know how many W I need for my computer use? > I think the most resource-intense I do would be compiling and > watching multimedia on mpv. [2] > Cooler Master has a PSU calculator. https://www.coolermaster.com/power-supply-calculator/ You have to enter CPU, GPU (make and model), HDD, SDD and so on, and it calculates how much wattage is required. Add another 25% as stated above and you're good to go.
Re: Android apps on Debian
On Sat, 2022-01-29 at 13:07 -0600, John Hasler wrote:
> Thank you both. Now to get a copy of the ("free") app without
> opening a Google
> Play account...
Everything nowadays "needs" an app... I hate it.
Re: Debian 11 xfce
On Wed, 2022-01-12 at 11:27 -0500, Dan Ritter wrote: > c. marlow wrote: > > I honestly don't see what people see in XFCE > > > > To me, XFCE looks VERY DATED and out of the 90s. > > It works; it rarely breaks after a version upgrade; and it is > configurable. > > That's three advantages over GNOME. > > -dsr- GNOME was ok when it looked like XFCE. v2.0 IIRC But yes, XFCE is rock solid, simple and ugly. Just like VLC.
No icon in notification area for qt applications
Greetings, Debian users I have Debian Buster fully updated. After fiddling with some themes, qt applications (vlc, qbittorrent and others I guess) stopped showing their icons in the xfce notification area. I tried removing and adding again the notification area thingie, but no luck.
Re: Disk problem whilst attempting to install Buster (10.7)
On Mon, 2021-01-25 at 12:19 -0500, Dan Ritter wrote: > Peter Hillier-Brook wrote: > > Trying to install Buster to a new Acer Aspire A515-56. The install > > (from > > live DVD) hangs asking for disk device ID. This info is at least 12 > > screws from immediate resolution, except for the BIOS(?)/UEFI > > output of: > > > > HFM512GDJIN-82A0A for the HD > > That's an M2-connected SSD, so it probably appears as > > /dev/nvme0 > > and partitions on it as > > /dev/nvme0p1 > /dev/nvme0p2 > > and so forth. > > -dsr- It's more like: /dev/nvme0n1p1 /dev/nvme0n1p2
Re: Boot so slow it never completes, while Windows boots fine
On Thu, 2020-04-23 at 16:57 +0200, Marcin Owsiany wrote: > TL;DR: My laptop starts ~20x slower than normal. Booting Debian hangs > before the kernel starts. Windows 10 boots slow, but then works fine. > Hardware problem? > > My only theories now are: > - a hardware problem (but why does it go away once Windows boots?) > - a botched CPU microcode update (but I suppose there are checksums > which > would prevent it from happening, so not likely). > > Any thoughts? > > Marcin I also believe it is a harware problem. I would first run a memtest to ensure RAM is good.
Re: Any way to open Thunar as root beside this?
On Wed, 2020-04-08 at 01:40 +0800, kaye n wrote: > Hello Friends! > > I was just wondering if there are easier ways to open Thunar file > manager > as root? > > Right now what I do is this: > > Open xfce4-terminal, > Execute: sudo thunar > Type my password. > > Not a big deal but if there is an easier way I'd like to know. > > Thank you! You could press Alt-F2 and enter sudo thunar. Since I don't use sudo, I can't test if it works. But I can see no reason why it shouldn't work.
Re: chromium error: Error initializing NSS without a persistent database: NSS error code: -8023
I get the exact same error. It happened after an apt-get upgrade. Searching the net I too did not find anything helpful.
