Welcome, Guest. Please login or register.
Did you miss your activation email?

Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
I don't understand the problem (except that 902 files to be upgraded suggests a LONG time since the last upgrade ....)

Several siduction systems here, all fully upgraded -- here is one:

Code: [Select]
[sudo] password for don:
base-files:
  Installed: 13.5
  Candidate: 13.5
  Version table:
 *** 13.5 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
22
Installation - Support / Re: Update kernel only for security
« Last post by lanig on 2024/09/16, 21:41:03 »
OK, Thanks.
23
Not new issue, but not solved yet.
Overcoming it here by putting base-files 13.3 on hold for now.

regards

Reiner
24
Hi people,

I'm a long (and till today quiet) siduction user and everything worked like a charm till today - but now I've got a situation I'm not able to solve:

Trying a apt dist-upgrade fails with the following message:
Code: [Select]
root@tightan-siduction:/# apt dist-upgrade
...
Summary:
  Upgrading: 902, Installing: 104, Removing: 2, Not Upgrading: 0
  Download size: 0 B / 1.693 MB
  Space needed: 1.421 MB / 34,4 GB available

Continue? [J/n]
Extracting templates from packages: 100%
Preconfiguring packages ...
setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
(Lese Datenbank ... 296598 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../base-files_13.5_amd64.deb ...


******************************************************************************
*
* The base-files package cannot be installed because
* /bin is a symbolic link and not pointing at usr/bin exactly.
*
* This is an unexpected situation. Cannot proceed with the upgrade.
*
* For more information please read https://wiki.debian.org/UsrMerge.
*
******************************************************************************


dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/base-files_13.5_amd64.deb (--unpack):
 »neues pre-installation-Skript des Paketes base-files«-Unterprozess gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
 /var/cache/apt/archives/base-files_13.5_amd64.deb
needrestart is being skipped since dpkg has failed
Error: Sub-process /usr/bin/dpkg returned an error code (1)

But after reading the linked wiki and looking at the filesystem, see:
Code: [Select]
root@tightan-siduction:/# ls -lah /
insgesamt 76K
drwxr-xr-x  19 root root 4,0K  9. Sep 21:43 .
drwxr-xr-x  19 root root 4,0K  9. Sep 21:43 ..
-rw-r--r--   1 root root    0  5. Jun 2021  .autorelabel
lrwxrwxrwx   1 root root    8  5. Jun 2021  bin -> /usr/bin
drwxr-xr-x   4 root root 4,0K 14. Aug 06:51 boot
drwxr-xr-x  19 root root 4,4K 16. Sep 17:53 dev
drwxr-xr-x  10 root root 4,0K  5. Jun 2021  disks
drwxr-xr-x 168 root root  12K 16. Sep 17:53 etc
drwxr-xr-x   4 root root 4,0K 17. Aug 2021  home
lrwxrwxrwx   1 root root   40 14. Aug 06:51 initrd.img -> boot/initrd.img-6.10.4-1-siduction-amd64
lrwxrwxrwx   1 root root   40 14. Aug 06:51 initrd.img.old -> boot/initrd.img-6.10.2-1-siduction-amd64
lrwxrwxrwx   1 root root    8  5. Jun 2021  lib -> /usr/lib
lrwxrwxrwx   1 root root   10  5. Jun 2021  lib64 -> /usr/lib64
drwx------   2 root root  16K  5. Jun 2021  lost+found
drwxr-xr-x  15 root root 4,0K  9. Sep 20:59 media
drwxr-xr-x   2 root root 4,0K 14. Feb 2021  mnt
drwxr-xr-x   4 root root 4,0K 27. Feb 2023  opt
dr-xr-xr-x 505 root root    0 16. Sep 19:53 proc
drwx------  10 root root 4,0K 16. Sep 19:54 root
drwxr-xr-x  37 root root 1,1K 16. Sep 19:55 run
lrwxrwxrwx   1 root root    9  5. Jun 2021  sbin -> /usr/sbin
drwxr-xr-x   2 root root 4,0K 14. Feb 2021  srv
dr-xr-xr-x  12 root root    0 16. Sep 20:13 sys
drwxrwxrwt  19 root root  480 16. Sep 20:26 tmp
drwxr-xr-x  12 root root 4,0K  3. Sep 2023  usr
drwxr-xr-x  11 root root 4,0K 28. Nov 2023  var
lrwxrwxrwx   1 root root   37 14. Aug 06:51 vmlinuz -> boot/vmlinuz-6.10.4-1-siduction-amd64
lrwxrwxrwx   1 root root   37 14. Aug 06:51 vmlinuz.old -> boot/vmlinuz-6.10.2-1-siduction-amd64
I don't really understand what apt is trying to tell me - any help is highly appreciated! I can happily provide further details if requested and can also answer in German, if that's preferred...

Thanks in advance
Brom
25
Hardware - Support / Re: Drucker druckt nicht jedes pdf
« Last post by ro_sid on 2024/09/16, 19:32:14 »
Solche Probleme gab es früher bei vielen Druckern, wenn das Seitenformat (A4 (DIN), Letter (US)) nicht stimmte. Viele Drucker haben eine Einstellung Letter (kleinere Länge) auch auf DIN-A4 (eben "länger") zu drucken. Oft hilft dann auch in der druckenden Software, "Anpassen ans Druckformat" ("scale to") einzuschalten.
26
Hardware - Support / Drucker druckt nicht jedes pdf
« Last post by NochEinNeuer on 2024/09/16, 17:59:27 »
Hallo,

ich habe hier einen Brother HL L3220CWE Farblaser der via USB mit meinem Computer verbunden ist.
Installiert ist siduction mate mit aktuellen Updates.

Drucker mit cups eingerichtet. Drucker, Testseite und 95% aller PDF's, funzt problemlos.

Von einer Firma erhalte ich Rechnungen als pdf per Mail. Diese pdf kann ich an den Drucker senden, dieser meldet sich "Ready" aber nix tut sich (Drucker ist natürlich angeschaltet). Bei anderen pdf wacht der Drucker gleich auf aus dem Schlafmodus und druckt dann auch.

Ich hab keine Ahnung woran das liegen könnte. Grundsätzlich ist es ja doch etwas blöd wenn der Drucker nicht alle pdf Drucken will.

Hat jemand von Euch eine Idee wo der Fehler liegen könnte?
Danke,
Jürgen
27
Installation - Support / Re: Update kernel only for security
« Last post by towo on 2024/09/16, 10:50:53 »
Quote
Is there a way to know if a kernel is updated for security reasons? I would like to hold the current kernel and upgrade it only for security reasons.

No, there is not. You may read the upstream changelog.
28
Installation - Support / Re: Update kernel only for security
« Last post by lanig on 2024/09/16, 10:28:08 »
Up!
29
Quote
I totally missed the top part of this post

It was mentioned a couple times. Best thing is to full-upgrade/dist-upgrade at least a few times a week. You may see package replacements rather than a version upgrade like we see in your first post. Other times it can be complete transitions. These can be problematic until complete. Sometime you just have to ride it out. Usually problems are posted so if you do have an issue check there before proceeding. Always best to pay attention to what's going to happen before committing.
30
You're good to upgrade, as far as I can see. I have 4 KDE/Plasma systems, now all using wayland. Here is output from one:

Code: [Select]
# apt policy libkf6guiaddons-bin kwayland-data kwin-wayland
libkf6guiaddons-bin:
  Installed: 6.5.0-2
  Candidate: 6.5.0-2
  Version table:
 *** 6.5.0-2 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
kwayland-data:
  Installed: (none)
  Candidate: 4:5.115.0-2
  Version table:
     4:5.115.0-2 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
kwin-wayland:
  Installed: 4:5.27.11-2
  Candidate: 4:5.27.11-2
  Version table:
 *** 4:5.27.11-2 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

"A few weeks" is not generally advisable to wait to upgrade your sid system. If I don't see a warning on this forum, mine get upgraded almost daily.

Oh wow. I’ve been on my mobile all day. I totally missed the top part of this post. All I saw was….. "A few weeks" is not generally advisable to wait to upgrade your sid system. If I don't see a warning on this forum, mine get upgraded almost daily.

My response was totally off based off the info you provided. My apologies sir and thank you.
Pages: 1 2 [3] 4 5 ... 10