Re: about 10th new install of bullseye

[gene heskett]

On 6/7/24 20:38, Tom Dial wrote:



On 6/6/24 23:14, gene heskett wrote:

On 6/6/24 19:00, Tom Dial wrote:



On 6/5/24 19:53, gene heskett wrote:

On 6/5/24 17:25, Tom Dial wrote:



On 6/5/24 08:58, gene heskett wrote:

On 6/5/24 02:05, Tom Dial wrote:



On 6/4/24 04:26, gene heskett wrote:

On 2/19/22 06:31, Andrew M.A. Cater wrote:

Hi Gene,

If this was someone calling you from a TV station saying they 
had a TV
transmitter that was varying in power output - you'd have a 
mental checklist.
You'd get down there, perhaps schedule some sort of power down 
/ reduced
power operation and then you'd check - power supplies, feeder 
cables, hot
spots on cables - whatever. Divide and conquer- working back to 
a baseline

of known working conditions and eliminating causes.

My suggestion to you of a reinstall is partly designed to get 
you out of this
"X happens, I did Y, now I've got Z" - to get to a known 
initial state.


Take out all the serial converters to UPS, lathe and so on. 
Wireless keyboard
doesn't present as serial in the same way that brltty does - if 
it did, I'd

have brltty with every install on this laptop.

Copy off your home directory as you did before - maybe using 
tar.gz and preserving permissions. Start with the .iso that 
includes firmware - the unofficial one.


Build back slowly - do an expert text mode install if you can. 
Then add your
Trinity desktop - I don't think any of us can help you there, 
since we don't

run trinity.

Check and you should find that brltty isn't installed at all. 
Then re-add thingsgradually until you have the working system 
you want. Document it - write down

the steps you take / copy configuration files you change.

That will also reveal logging / login slowdowns or whatever 
caused by

individual devices as you add them back. Keep a list as you go.

That's the counsel of perfection: alternatively:

apt rdepends brltty gives me:

me@mymachine:~$ apt rdepends brltty
brltty
Reverse Depends:
   Suggests: speechd-el (>= 3.7.2)
   Depends: brltty-espeak (= 6.3+dfsg-1+deb11u1)
   Suggests: orca
   Depends: brltty-x11 (= 6.3+dfsg-1+deb11u1)
   Depends: brltty-speechd (= 6.3+dfsg-1+deb11u1)
   Depends: brltty-flite (= 6.3+dfsg-1+deb11u1)

You could try apt-get remove (or equivalent) on each of those 
packages and
see if that clears it. I _know_ this is frustrating as all get 
out for you
but a clear approach, written down so that you can remember 
where you got

to will be very helpful.


Any attempt to remove cura or brltty, removes gnome leaving me I 
assume with a text only system by the time gnome takes all its 
dependency's with it.  Thanks Tom.


Have you actually tried uninstalling brltty only, as a separate 
action from all others?


I have a number of gnome installations, unfortunately for this 
discussion all bookworm. None of them has brltty.


I have a few installations of bullseye and an older stretch 
installation, but none with gnome installed. On all of them, 
though, "apt-rdepends -r gnome" fails to list brltty as a gnome 
dependency. And on the bookworm systems, simulated installation of 
gnome ("apt install -s gnome") shows brltty as a suggested package 
only and would not install it along with gnome; on the stretch 
system, gnome installation makes no reference at all to brltty.


While I have both with only the radio buttons for keyboard and 
rodent plugged into usb at install time. I have only one wired 
keyboard and no wired mice as I've had a lightning strike on the 
pole that serves this house reach up and tap me by way of my fingers 
on the keyboard. Wasn't that much of a tap, I've been tapped a lot 
harder that that, hard enough to trigger a 6 month round of shingles 
and the burns were months healing. And in this case did not damage 
the keyboard or computer, but I did get the message. I've had many 
strikes on that pole since I built a garage on the end of the house, 
which caused me to install a 200 amp service and bring my grounding 
specs up to NEC. Zero problems since then (2008)


Is it possible you have apt settings that automatically pull in 
suggested packages, and that is interfering with attempts to remove 
brltty? I am not expert enough wrt apt and its relatives to know 
whether that even makes sense, and it seems a bit far fetched if 
maybe barely possible.


Maybe if you post the output from "apt-rdepends -r brltty" and "apt 
purge --simulate brltty" it will be informative.


Neither of those utils are installed. Should they be?


apt should be installed. As far as I know it has been included by 
default in the Debian base system as the preferred command line 
package management program since buster or earlier. I have never had 
to install it. You probably should if it is missing.


apt-rdepends is at least partly redundant with apt.
The command "apt-rdepends -r ", and "apt rdepends 
" both show reverse dependencies of ; the 
latter also shows suggestions (packages that suggest think).

If you have apt installed, you 

Re: NVidia 340 video driver in Bookworm?

[Max Nikulin]

On 08/06/2024 03:29, Van Snyder wrote:

Has anybody been able to install the NVidia 340.108 video driver in
Debian 12?


I am not aware of current state of affairs. Several years ago it was 
possible to rebuild the .deb package (that uses DKMS) with additional 
patches to make the code compatible with changed kernel API. On that 
machine I had Ubuntu installed, but the procedure should be similar

https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750
You may try to find patches for newer kernels.

I do not remember graphics card model. The noveau driver caused more 
image artifacts that time.

Re: [SOLVED] Re: Debian bookworm fails to install

[Max Nikulin]

On 08/06/2024 00:48, Hans wrote:

BUT - grub-efi-amd64-bin conflicts with grub-efi-amd64-bin-signed


No it does not. I have both installed. I think, the latter needs .mod 
files provided by the former.

Re: [SOLVED] Re: Debian bookworm fails to install

[Jeffrey Walton]

On Fri, Jun 7, 2024 at 1:48 PM Hans  wrote:
>
> Got it! Found the reason and a fix for it.
>
> Just not easy to find. It is an dependency-problem!
>
> What happened?
>
> Well, in ~config/mylist.list.chroot I added the package "bootcd", which shoul 
> exist in my live-system. During build this made no problems and all 
> dependencies are ok. But - during install it appears, that there is a 
> dependency conflict with the installer as bootcd needs grub-efi-amd64-bin.
>
> However, when bootcd wants to install, this package will be installed, too as 
> it is dependent. So far, so well.
>
> BUT - grub-efi-amd64-bin conflicts with grub-efi-amd64-bin-signed
>
> and forces it to deinstall,
>
> which, you guess it, the debian-installer needs.
>
> And so the grub-installer crashes!
>
> Now the question, who should be asked for help? Maintainers of bootcd? 
> Maintainers of debian-installer? Or Maintainers of packages?
>
> I do not know, and as long as I do not know, I can not file a bugreport as 
> none of them (and this is fully correct and understandable) is responsible 
> from his sight on.
>
> However, the problem can easily be reproduced.

Forgive my ignorance... How does this translate into an intermittent
problem? It seems like you would never encounter it, or always
encounter it. What makes the problem come and go?

Jeff

Re: Debian bookworm fails to install

[Jeffrey Walton]

On Fri, Jun 7, 2024 at 3:08 PM Hans  wrote:
>
> Hi folks,
>
> I am running into an issue, I can not explain.
>
> Let me please shortly describe:
>
> For my own purposes I am building a live-debian ISO with installer. As I am
> finetuning some things (not related to the system itself), I am building
> several ISOs a day.
>
> The live-build is set to bookworm (not bullseye, as lb config does).
>
> However, everything is going fine., the live-system is booting well.
>
> But: When I want to install it, the installer always breaks, when it wants to
> install grub. (grub-installer fails).
>
> As I am doing always a fresh install with completely formatting the harddrive,
> it can not be explained, why this happens.
>
> And more strange: When I build one version, it is working well. Changing
> nothing, and building again, suddenly the installer crashes at grub
> installation and then it will never work again.
>
> To declare: I can build several times, and every installation is working well,
> and suddenly without any reason, it breakes. Doing then using one version
> before (the last one, which worked well), it is still working, but the next
> build is crashing.
>
> Ok, I think you understood, what I meant. Well, one reason I could imagine,
> that the debian mirror, I add during installation process is changing. I am
> using "deb.debian.org", but when using another mirror in my near, I am running
> into the same issue.
>
> I also tried to install grub manually in the console during installation
> process, using "grub-installer /target", but this did neither work nor show
> much usefull information.
>
> Any idea, why this is happening? I saw similar messages in some forums, but
> they are all related to Debian 10, which is rather old (and I suppose, these
> bugs are fixed).

You might have a look at grub2 bugs in Bookworm, and see if any look
like they apply to you:
.

Jeff

Re: about 10th new install of bullseye

[Tom Dial]

On 6/6/24 23:14, gene heskett wrote:

On 6/6/24 19:00, Tom Dial wrote:



On 6/5/24 19:53, gene heskett wrote:

On 6/5/24 17:25, Tom Dial wrote:



On 6/5/24 08:58, gene heskett wrote:

On 6/5/24 02:05, Tom Dial wrote:



On 6/4/24 04:26, gene heskett wrote:

On 2/19/22 06:31, Andrew M.A. Cater wrote:

Hi Gene,

If this was someone calling you from a TV station saying they had a TV
transmitter that was varying in power output - you'd have a mental checklist.
You'd get down there, perhaps schedule some sort of power down / reduced
power operation and then you'd check - power supplies, feeder cables, hot
spots on cables - whatever. Divide and conquer- working back to a baseline
of known working conditions and eliminating causes.

My suggestion to you of a reinstall is partly designed to get you out of this
"X happens, I did Y, now I've got Z" - to get to a known initial state.

Take out all the serial converters to UPS, lathe and so on. Wireless keyboard
doesn't present as serial in the same way that brltty does - if it did, I'd
have brltty with every install on this laptop.

Copy off your home directory as you did before - maybe using tar.gz and 
preserving permissions. Start with the .iso that includes firmware - the 
unofficial one.

Build back slowly - do an expert text mode install if you can. Then add your
Trinity desktop - I don't think any of us can help you there, since we don't
run trinity.

Check and you should find that brltty isn't installed at all. Then re-add 
thingsgradually until you have the working system you want. Document it - write 
down
the steps you take / copy configuration files you change.

That will also reveal logging / login slowdowns or whatever caused by
individual devices as you add them back. Keep a list as you go.

That's the counsel of perfection: alternatively:

apt rdepends brltty gives me:

me@mymachine:~$ apt rdepends brltty
brltty
Reverse Depends:
   Suggests: speechd-el (>= 3.7.2)
   Depends: brltty-espeak (= 6.3+dfsg-1+deb11u1)
   Suggests: orca
   Depends: brltty-x11 (= 6.3+dfsg-1+deb11u1)
   Depends: brltty-speechd (= 6.3+dfsg-1+deb11u1)
   Depends: brltty-flite (= 6.3+dfsg-1+deb11u1)

You could try apt-get remove (or equivalent) on each of those packages and
see if that clears it. I _know_ this is frustrating as all get out for you
but a clear approach, written down so that you can remember where you got
to will be very helpful.


Any attempt to remove cura or brltty, removes gnome leaving me I assume with a 
text only system by the time gnome takes all its dependency's with it.  Thanks 
Tom.


Have you actually tried uninstalling brltty only, as a separate action from all 
others?

I have a number of gnome installations, unfortunately for this discussion all 
bookworm. None of them has brltty.

I have a few installations of bullseye and an older stretch installation, but none with gnome 
installed. On all of them, though, "apt-rdepends -r gnome" fails to list brltty as a 
gnome dependency. And on the bookworm systems, simulated installation of gnome ("apt install 
-s gnome") shows brltty as a suggested package only and would not install it along with gnome; 
on the stretch system, gnome installation makes no reference at all to brltty.


While I have both with only the radio buttons for keyboard and rodent plugged 
into usb at install time. I have only one wired keyboard and no wired mice as 
I've had a lightning strike on the pole that serves this house reach up and tap 
me by way of my fingers on the keyboard. Wasn't that much of a tap, I've been 
tapped a lot harder that that, hard enough to trigger a 6 month round of 
shingles and the burns were months healing. And in this case did not damage the 
keyboard or computer, but I did get the message. I've had many strikes on that 
pole since I built a garage on the end of the house, which caused me to install 
a 200 amp service and bring my grounding specs up to NEC. Zero problems since 
then (2008)


Is it possible you have apt settings that automatically pull in suggested 
packages, and that is interfering with attempts to remove brltty? I am not 
expert enough wrt apt and its relatives to know whether that even makes sense, 
and it seems a bit far fetched if maybe barely possible.

Maybe if you post the output from "apt-rdepends -r brltty" and "apt purge --simulate 
brltty" it will be informative.


Neither of those utils are installed. Should they be?


apt should be installed. As far as I know it has been included by default in 
the Debian base system as the preferred command line package management program 
since buster or earlier. I have never had to install it. You probably should if 
it is missing.

apt-rdepends is at least partly redundant with apt.
The command "apt-rdepends -r ", and "apt rdepends " both 
show reverse dependencies of ; the latter also shows suggestions (packages that suggest 



Regards,
Tom Dial



If all else fails, you can then share it with the list and say "I got to
step X 

Re: about 10th new install of bullseye

[gene heskett]

On 6/7/24 18:12, David Christensen wrote:

On 6/6/24 22:14, gene heskett wrote:
In experimenting I've found a name clash, there are appprently two 
orca's. one is a speech synth, one is a slicer for 3d printers I don't 
use. Typing orca in a shell locks the shell wo any output, for several 
minutes but comes back to a prompt with a ctl-c, so I've NDC which was 
being executed. Whatevver, the installation is quite voluminous:

gene@coyote:~/AppImages$ locate orca |wc -l
1560

So I took orca out, which took gnome out. But now gnomes dependencies 
will put orca back in. So now I can't run autoremove. So one more time 
this broken damned bookworm install has bit me in a rear.


No Cheers, Gene Heskett, CET.



Here are my installation notes from when I migrated my daily driver from 
Debian 9 to Debian 11.  It has orca, and orca has never bothered me:


January 9, 2022

1.  Wipe Intel SSD 520 Series 60 GB drive in Intel DQ67SW.  Insert
     debian-11.2.0-amd64-netinst USB flash drive into USB 3.0 port
     adjacent Gigabit port. Boot:

 Debian GNU/Linux installer menu (BIOS mode)
     install
 Language    C
 Continent or region    North America
 Country, territory or area    United States
 Keymap to use    American English
 Hostname    laalaa
 Domain name    tracy.holgerdanske.com
 Root password    
 Re-enter password    
 Full name for new user    debian
 Username for your account    debian
 Choose a password    
 Re-enter password    
 Select your time zone    Pacific
 Partitioning method    Manual
   Select a partition...    SCSI1 (0,0,0) (sda) - 60.0 GB ATA INTEL 
SSDSC2CW06

     Create partition table    Yes
   Select a partition...    pri/log 60.0 GB FREE SPACE
     Create a new partition
   New partition size    1 GB
   Type    Primary
   Location    Beginning
   Partition settings
     Use as    Ext4 journaling file system
     Mount point    /boot
     Mount options    defaults
     Label    laalaa_boot
     Reserved blocks    5%
     Typical usage    standard
     Bootable flag    on
     Done setting up the partition
   Select a partition...    pri/log 59.0 GB FREE SPACE
     Create a new partition
   New partition size    1 GB
   Type    Primary
   Location    Beginning
   Partition settings
     Use as    physical volume for encryption
     Encryption method    Device-mapper (dm-crypt)
     Encryption    aes
     Key size    256
     IV algorithm    xts-plain64
     Encryption key    Random key
     Erase data    no
     Bootable flag    off
     Done setting up the partition
   Select a partition...    pri/log 58.0 GB FREE SPACE
     Create a new partition
   New partition size    13 GB
   Type    Primary
   Location    Beginning
   Partition settings
     Use as    physical volume for encryption
     Encryption method    Device-mapper (dm-crypt)
     Encryption    aes
     Key size    256
     IV algorithm    xts-plain64
     Encryption key    Passphrase
     Erase data    no
     Bootable flag    off
     Done setting up the partition
   Configure encrypted volumes
     Write the changes to disk    Yes
     Encryption configuration    Create encrypted volumes
     Devices to encrypt
   [*] /dev/sda2 (1000MB; crypto)
   [*] /dev/sda3 (13000MB; crypt)
     Continue
     Encryption configuration    Finish
     Encryption passphrase    
     Re-enter passphrase    
   Select a partition...    #1 13.0 GB f ext4
     Partition settings
   Use as    Ext4 journaling file system
   Mount point    /
   Mount options    defaults
   Label    laalaa_root
   Reserved blocks    5%
   Typical usage    standard
   Done setting up the partition
   Finish partitioning and write changes to disk
     Write the changes to disks    Yes
 Debian archive mirror country    United States
 Debian archive mirror    deb.debian.org
 HTTP proxy information    
 Package usage survey    No
 Choose software    Debian desktop environment
     Xfce
     SSH server
     standard system utiilties
 Device for boot loader installation
     /dev/sdb (ata-INTEL_SSDSC2CW060A3_)
 Installation complete    Continue

     Push and hold power button at POST; release when computer turns
 

Re: about 10th new install of bullseye

[David Christensen]

On 6/6/24 22:14, gene heskett wrote:
In experimenting I've found a name clash, there are appprently two 
orca's. one is a speech synth, one is a slicer for 3d printers I don't 
use. Typing orca in a shell locks the shell wo any output, for several 
minutes but comes back to a prompt with a ctl-c, so I've NDC which was 
being executed. Whatevver, the installation is quite voluminous:

gene@coyote:~/AppImages$ locate orca |wc -l
1560

So I took orca out, which took gnome out. But now gnomes dependencies 
will put orca back in. So now I can't run autoremove. So one more time 
this broken damned bookworm install has bit me in a rear.


No Cheers, Gene Heskett, CET.



Here are my installation notes from when I migrated my daily driver from 
Debian 9 to Debian 11.  It has orca, and orca has never bothered me:


January 9, 2022

1.  Wipe Intel SSD 520 Series 60 GB drive in Intel DQ67SW.  Insert
debian-11.2.0-amd64-netinst USB flash drive into USB 3.0 port
adjacent Gigabit port. Boot:

Debian GNU/Linux installer menu (BIOS mode)
install
LanguageC
Continent or region North America
Country, territory or area  United States
Keymap to use   American English
Hostnamelaalaa
Domain name tracy.holgerdanske.com
Root password   
Re-enter password   
Full name for new user  debian
Username for your account   debian
Choose a password   
Re-enter password   
Select your time zone   Pacific
Partitioning method Manual
  Select a partition... SCSI1 (0,0,0) (sda) - 60.0 GB ATA INTEL 
SSDSC2CW06
Create partition table  Yes
  Select a partition... pri/log 60.0 GB FREE SPACE
Create a new partition
  New partition size1 GB
  Type  Primary
  Location  Beginning
  Partition settings
Use as  Ext4 journaling file system
Mount point /boot
Mount options   defaults
Label   laalaa_boot
Reserved blocks 5%
Typical usage   standard
Bootable flag   on
Done setting up the partition
  Select a partition... pri/log 59.0 GB FREE SPACE
Create a new partition
  New partition size1 GB
  Type  Primary
  Location  Beginning
  Partition settings
Use as  physical volume for encryption
Encryption method   Device-mapper (dm-crypt)
Encryption  aes
Key size256
IV algorithmxts-plain64
Encryption key  Random key
Erase data  no
Bootable flag   off
Done setting up the partition
  Select a partition... pri/log 58.0 GB FREE SPACE
Create a new partition
  New partition size13 GB
  Type  Primary
  Location  Beginning
  Partition settings
Use as  physical volume for encryption
Encryption method   Device-mapper (dm-crypt)
Encryption  aes
Key size256
IV algorithmxts-plain64
Encryption key  Passphrase
Erase data  no
Bootable flag   off
Done setting up the partition
  Configure encrypted volumes
Write the changes to disk   Yes
Encryption configurationCreate encrypted volumes
Devices to encrypt  
  [*] /dev/sda2 (1000MB; crypto)
  [*] /dev/sda3 (13000MB; crypt)
Continue
Encryption configurationFinish
Encryption passphrase   
Re-enter passphrase 
  Select a partition... #1 13.0 GB f ext4
Partition settings
  Use asExt4 journaling file system
  Mount point   /
  Mount options defaults
  Label laalaa_root
  Reserved blocks   5%
  Typical usage standard
  Done setting up the partition
  Finish partitioning and 

Re: NVidia 340 video driver in Bookworm?

[Van Snyder]

On Fri, 2024-06-07 at 22:47 +0200, Hans wrote:
> Just a hint: Sometimes the nvidia-config module says, you need 340.xx, but 
> this is not always true. My card (with th eolder kernel) was running 390.xx, 
> although th esystem told me, I have to use 340.xx. 390.xx was running like a 
> charm, 340.xx crashed. So it lied.
> 
> Sorry, that I can help no further and for the bad news, but do not try too 
> much - I fear, you will fail!

So far, this is the best advice, so don't apologize.

I had assumed that when NVidia said I need 340 that it is undoubtedly
true. I'll try 390.

Re: about 10th new install of bullseye

[gene heskett]

On 6/7/24 14:15, mick.crane wrote:

On 2024-06-07 12:32, gene heskett wrote:


Where did you get that beta trixie installer? bookworm does not allow
that removal of orca without also removing gnome. brltty yes, but not
orca.


I don't think I've got any gnome stuff.
here probably.
https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-dvd/
mick

.

Got it, thanks mick.

Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: NVidia 340 video driver in Bookworm?

[Hans]

Am Freitag, 7. Juni 2024, 22:29:30 CEST schrieb Van Snyder:
Hi! Sadly to tell, that I treid hard to get 340.xx running in Bookworm. The 
problem is: You can not get it build with the actual kernel sources.

I checked and the developers missed some dependencies, the NVidia driver needs 
at build time.

You can get running it, if you are using an old kernel, like th eone from 
buster, maybe bullseye. In these kernels the dependencies and the libs, the 
sources are searching, are existent.

However, maybe you can trick the build by adding the needed dependencies and 
things, the driver is searching. But I dunno, if this is a good idea.

I also tried the orginal sources from nvidia.com, but here the same dependency 
problem appeared.

In some former mails I asked the kernel developers for help, but there was no 
big interest in fixing things with closed source drivers (however, the kernel 
module is not closed source as far as I know). 

Most people are pointing to nouveau, but this is pita. Development in nouveau 
is also not much any more people told.

Thus, with this old graphics card in linux is a problem, although they are in 
many notebooks people still use (I am running a Lenovo T520, several years 
old, but still fast enough). It has also a NVidia-card built in which needs 
340.xx but I can not use it due to the lack of the kernel driver.

Just a hint: Sometimes the nvidia-config module says, you need 340.xx, but 
this is not always true. My card (with th eolder kernel) was running 390.xx, 
although th esystem told me, I have to use 340.xx. 390.xx was running like a 
charm, 340.xx crashed. So it lied.

Sorry, that I can help no further and for the bad news, but do not try too 
much - I fear, you will fail!

Have a nice day!

Hans 


> Has anybody been able to install the NVidia 340.108 video driver in
> Debian 12?
> 
> The messages I found said "Support for it ended in 2019. Use nouveau."
> 
> But I seem to have trouble with nouveau. When I was running Debian 10
> on a Dell Vostro 1700 laptop with NVidia GeForce 8400M graphics, I had
> been able to install the driver, and had no trouble. I made the mistake
> of installing Debian 12.5 on the same partition, so I don't have the
> Debian 10 install anymore. It freezes so completely that the keyboard
> doesn't work, so I can't switch to a TTY screen. Even if I "ssh" to it
> from my desktop, I can't kill and restart the graphics. I have a script
> to restart KDE, but it does nothing. Even "init 3" doesn't do the
> trick. I have to hold down the power key to reboot. I don't think it's
> a hardware problem that amazingly manifested simultaneously with a new
> install.
> 
> Here's some too-late advice I've given to myself: Never blow away your
> old install that appears to be working. If you don't have a new disk,
> and you have room on the old one, make new boot and root partitions.
> Mark only the new boot partition as the bootable one. Hook both boot
> partitions to grub.

NVidia 340 video driver in Bookworm?

[Van Snyder]

Has anybody been able to install the NVidia 340.108 video driver in
Debian 12?

The messages I found said "Support for it ended in 2019. Use nouveau."

But I seem to have trouble with nouveau. When I was running Debian 10
on a Dell Vostro 1700 laptop with NVidia GeForce 8400M graphics, I had
been able to install the driver, and had no trouble. I made the mistake
of installing Debian 12.5 on the same partition, so I don't have the
Debian 10 install anymore. It freezes so completely that the keyboard
doesn't work, so I can't switch to a TTY screen. Even if I "ssh" to it
from my desktop, I can't kill and restart the graphics. I have a script
to restart KDE, but it does nothing. Even "init 3" doesn't do the
trick. I have to hold down the power key to reboot. I don't think it's
a hardware problem that amazingly manifested simultaneously with a new
install.

Here's some too-late advice I've given to myself: Never blow away your
old install that appears to be working. If you don't have a new disk,
and you have room on the old one, make new boot and root partitions.
Mark only the new boot partition as the bootable one. Hook both boot
partitions to grub.

Re: Impossible to install extensions with Gnome browser plugin

[Jan Krapivin]

On gnome you can just run

$ *gnome-shell --version*

пт, 7 июн. 2024 г. в 22:04, David Wright :

> On Fri 07 Jun 2024 at 20:06:27 (+0300), Jan Krapivin wrote:
> > Yes, you are right, maybe. Though Debian is probably a rare (if not the
> > only) distro that still uses Gnome 43.9, which is, as i use Debian, my
> > case. And (maybe) a problem?
>
> I searched for gnome in https://packages.debian.org/index
> and got 65 package matches for bookworm. I repeated for
> trixie and got 63 matches. Finally I tried sid and got
> 94 matches. However, I failed to find the string 43.9
> on any of these pages. How do you come by it? (I don't
> run gnome myself.)
>
> Cheers,
> David.
>
>

Re: [SOLVED] Re: Debian bookworm fails to install

[Hans]

Looks like a typo from me. 

apt-cache search grub-efi-amd | grep signed 
grub-efi-amd64-signed - GRand Unified Bootloader, version 2 (amd64 UEFI signed 
by Debian) 
grub-efi-amd64-signed-template - GRand Unified Bootloader, Version 2 
(Signaturvorlage für 
EFI-AMD64)

It is grub-efi-amd64-signed. 

Sorry for that. 

I checked after install: If I want to install package bootcd after 
installation, no packages will be 
deinstalled, just several added.

Not sure, what is the difference, between the installation process and the 
finished installation. 

Best

Hans


> 
> I can't find the package grub-efi-amd64-bin-signed.
> Where should I look?
> 
> Cheers,
> David.

Re: Impossible to install extensions with Gnome browser plugin

[David Wright]

On Fri 07 Jun 2024 at 20:06:27 (+0300), Jan Krapivin wrote:
> Yes, you are right, maybe. Though Debian is probably a rare (if not the
> only) distro that still uses Gnome 43.9, which is, as i use Debian, my
> case. And (maybe) a problem?

I searched for gnome in https://packages.debian.org/index
and got 65 package matches for bookworm. I repeated for
trixie and got 63 matches. Finally I tried sid and got
94 matches. However, I failed to find the string 43.9
on any of these pages. How do you come by it? (I don't
run gnome myself.)

Cheers,
David.

Re: [SOLVED] Re: Debian bookworm fails to install

[David Wright]

On Fri 07 Jun 2024 at 19:48:21 (+0200), Hans wrote:
> Got it! Found the reason and a fix for it.
> Just not easy to find. It is an dependency-problem!
> 
> What happened?
> 
> Well, in ~config/mylist.list.chroot I added the package "bootcd", which shoul 
> exist in my live-
> system. During build this made no problems and all dependencies are ok. But - 
> during install it 
> appears, that there is a dependency conflict with the installer as bootcd 
> needs grub-efi-amd64-
> bin.
> 
> However, when bootcd wants to install, this package will be installed, too as 
> it is dependent. So 
> far, so well. 
> BUT - grub-efi-amd64-bin conflicts with grub-efi-amd64-bin-signed 
> and forces it to deinstall, 
> which, you guess it, the debian-installer needs. 
> 
> And so the grub-installer crashes!

I can't find the package grub-efi-amd64-bin-signed.
Where should I look?

Cheers,
David.

Re: about 10th new install of bullseye

[mick.crane]

On 2024-06-07 12:32, gene heskett wrote:


Where did you get that beta trixie installer? bookworm does not allow
that removal of orca without also removing gnome. brltty yes, but not
orca.


I don't think I've got any gnome stuff.
here probably.
https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-dvd/
mick

Re: Souci de montage avec pcloud.com

[Étienne Mollier]

Bonsoir Pierre,

Pierre Meurisse, on 2024-06-07:
> j'ai testé plusieurs anciens noyaux, en remontant même jusqu'à
> linux-image-6.1.0.16-amd64 mais rien n'y fait.

D'accord, donc ce n'est visiblement pas une régression
introduite par la version de noyau.  Du coup je sèche et vais en
rester là pour le moment ; la piste webdav relevée par Erwan
vaut probablement le détour.

Bonne soirée,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/3, please excuse my verbosity
   `-


signature.asc
Description: PGP signature

[SOLVED] Re: Debian bookworm fails to install

[Hans]

Got it! Found the reason and a fix for it.
Just not easy to find. It is an dependency-problem!

What happened?

Well, in ~config/mylist.list.chroot I added the package "bootcd", which shoul 
exist in my live-
system. During build this made no problems and all dependencies are ok. But - 
during install it 
appears, that there is a dependency conflict with the installer as bootcd needs 
grub-efi-amd64-
bin.

However, when bootcd wants to install, this package will be installed, too as 
it is dependent. So 
far, so well. 
BUT - grub-efi-amd64-bin conflicts with grub-efi-amd64-bin-signed 
and forces it to deinstall, 
which, you guess it, the debian-installer needs. 

And so the grub-installer crashes!

Now the question, who should be asked for help? Maintainers of bootcd? 
Maintainers of debian-
installer? Or Maintainers of packages? 

I do not know, and as long as I do not know, I can not file a bugreport as none 
of them (and 
this is fully correct and understandable) is responsible from his sight on.

However, the problem can easily be reproduced.

Thanks for reading this, hope it helps. For me, this issue can be closed.

Best regards

Hans

Re: Impossible to install extensions with Gnome browser plugin

[Jan Krapivin]

Yes, you are right, maybe. Though Debian is probably a rare (if not the
only) distro that still uses Gnome 43.9, which is, as i use Debian, my
case. And (maybe) a problem?

пт, 7 июн. 2024 г. в 20:01, :

> Jan Krapivin  wrote:
> > Thank you for your reply. This topic is not about Debian packages, but
> > about a performance of a plugin for browsers, it is not a Debian
> > package.
> >
> >
> https://wiki.gnome.org/action/show/Projects/GnomeShellIntegration?action=show=Projects%2FGnomeShellIntegrationForChrome
> >
> > I am trying to install Gnome extensions with it. They are also not
> > Debian packages.
> >
> > https://extensions.gnome.org/about/
>
> So maybe a Gnome forum or list or one about the specific plugin or even
> one about the browser is a better place to look for help than a debian
> mailing list?
>
>

Re: Impossible to install extensions with Gnome browser plugin

[debian-user]

Jan Krapivin  wrote:
> Thank you for your reply. This topic is not about Debian packages, but
> about a performance of a plugin for browsers, it is not a Debian
> package.
> 
> https://wiki.gnome.org/action/show/Projects/GnomeShellIntegration?action=show=Projects%2FGnomeShellIntegrationForChrome
> 
> I am trying to install Gnome extensions with it. They are also not
> Debian packages.
> 
> https://extensions.gnome.org/about/

So maybe a Gnome forum or list or one about the specific plugin or even
one about the browser is a better place to look for help than a debian
mailing list?

Re: Debian bookworm fails to install

[Hans]

Am Freitag, 7. Juni 2024, 18:24:11 CEST schrieb Michael Kjörling:
Hi Michael,
> On 7 Jun 2024 18:01 +0200, from hans.ullr...@loop.de (Hans):
> > For my own purposes I am building a live-debian ISO with installer.
> 
> How are you doing this?
I am starting with lb config (to get a straight live-build environment).

After this I am edititing all entries in ~/config/bootstrap | binary | common 
from "bullseye" to 
"bookworm".

At last I am editing the entry for the name of the image from "live-image" to 
"RustDesk-live-
image" (I want it so be named).

Then lb config --purge.

After this, I am starting with my own shell script, which contents this line:



...

lb config --purge

lb config --debian-installer live --bootappend-live "boot=live username=myname 
hostname=my_hostname..." (keyboard definitions and so on)

lb build



This worked, but from one day to another no more, and this is strange! 
I also did a fresh live-build-environment installation, then it worked 3 or 4 
times, and then it 
broke again.



> 
> Can you post a script (or something similar) which reliably
> demonstrates the issue when executed within a fresh Debian system?
> 

The issue is not in the Debian itself, but it happens, when I want to install 
it. It happens as well 
on a native system as in Virtualbox itself.

Maybe I could upload the ISO somewhere, it can be used in Virtualbox and shows 
the crash 
there, too. However, the ISO is 700MB and you need 8GB harddrive in Virtualbox. 
Think, not a 
goo idea.

> > I also tried to install grub manually in the console during installation
> > process, using "grub-installer /target", but this did neither work nor
> > show
> > much usefull information.
> 
> Should we take this to mean that it did show _some_ "useful
> information"? If so, what _did_ it show?

No, it did not show any usefull information. Messages like "grub-installer 
failed" is no usefull 
information! No reason why...
> 
> It appears that you are trying something; having some issue; see
> symptoms; draw conclusions; and then tell us about your conclusions
> and ask for a solution to your issue so as to be able to continue with
> what you're trying to do. But without us being able to see what you
> are doing and what happens when you do, _in full_, it's nearly
> impossible to guess from your conclusions what might cause the issue
> you're having in the first place.
> 
Yeah, I know. If I got more information for myself, maybe I could find the 
reason for myself, 
too. But the installer does not show 

> Show us _exactly_ what's happening, as far as you are able. At a
> minimum, make it easy for others to recreate a situation in which you
> see the specific problem.
> 
> In other words, a minimal (non)working example.

At the moment, I try to use the installer from bullsyeye and the system of 
bookworm. It can be 
set in the live-build configurations.

Maybe it is a problem with the debian-bookworm repo (mirroring in process, 
whatever) and 
tomorrow it will magiacally work again.

So, I suppose, we should wait. I will try some things here and maybe I can fix 
it though.

Thanks for help anyway.

Best regards


Hans

Re: Debian bookworm fails to install

[Michael Kjörling]

On 7 Jun 2024 18:01 +0200, from hans.ullr...@loop.de (Hans):
> For my own purposes I am building a live-debian ISO with installer.

How are you doing this?

Can you post a script (or something similar) which reliably
demonstrates the issue when executed within a fresh Debian system?


> I also tried to install grub manually in the console during installation
> process, using "grub-installer /target", but this did neither work nor show
> much usefull information.

Should we take this to mean that it did show _some_ "useful
information"? If so, what _did_ it show?

It appears that you are trying something; having some issue; see
symptoms; draw conclusions; and then tell us about your conclusions
and ask for a solution to your issue so as to be able to continue with
what you're trying to do. But without us being able to see what you
are doing and what happens when you do, _in full_, it's nearly
impossible to guess from your conclusions what might cause the issue
you're having in the first place.

Show us _exactly_ what's happening, as far as you are able. At a
minimum, make it easy for others to recreate a situation in which you
see the specific problem.

In other words, a minimal (non)working example.

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Re: Arranque muy lento con SSD

[jerigondor78]

El viernes, 7 de junio de 2024 0:11:26 (CEST) JavierDebian escribió:
> El 5/6/24 a las 13:34, jerigondo...@gmail.com escribió:
> > Activado el "verbose". Adjunto foto de cuando se ha parado:
> > 
> > https://pixelfed.au/i/web/post/704004287090466433
> > 
> > Doy por hecho que los numeros entre corchetes son algun tipo de marca de
> > tiempo, pero no se corresponden con la realidad.
> > Entre 3.822528 y 3.822600 han pasado varios minutos. Al igual que entre
> > 3.82279 y 4.046965. A partir de ahí, ha aparecido el SSDM.
> > 
> > Saludos.
> 
> Tiene problemas con la cámara.
> 
> https://bbs.archlinux.org/viewtopic.php?id=124204
> 
> http://files.atlanty.ru/?id=usb:064e-a103
> 
> La detecta, y se toma los 3 minutos de espera para tratar de activarla.
> Empezá a escarbar por ahí.
> 
> JAP

Pues la cosa empieza a ponerse rara. Ahona se queda parado en:

[3.027879] input : SynPS/2 Synaptics TouchPad as /devices/platform/i8042/
serio1/input/input7

...durante varios minutos. El touchpad funciona perfectamente.
Despues se ha parado en:

[3.416086] random: rng init done

...durante varios minutos. Y desde ahí, de un tiron hasta el SSDM.

No ha vuelto a pararse en lo de la camara. Que por otra parte, jamas he 
utilizado. Por lo que no me importaria eliminarla. [Rectificación: En otra 
prueba ha vuelto a parar en lo de la camara].

Por ahí he leido que cuando se para en "random...", espera que se mueva el 
ratón para poder generar números aleatorios...

De todas formas con el kernel 6.1.0-18, va bien... pero me queda una espinita. 
Ya veremos.

Saludos.

Debian bookworm fails to install

[Hans]

Hi folks,

I am running into an issue, I can not explain.

Let me please shortly describe:

For my own purposes I am building a live-debian ISO with installer. As I am 
finetuning some things (not related to the system itself), I am building 
several ISOs a day. 

The live-build is set to bookworm (not bullseye, as lb config does).

However, everything is going fine., the live-system is booting well.

But: When I want to install it, the installer always breaks, when it wants to 
install grub. (grub-installer fails). 

As I am doing always a fresh install with completely formatting the harddrive, 
it can not be explained, why this happens.

And more strange: When I build one version, it is working well. Changing 
nothing, and building again, suddenly the installer crashes at grub 
installation and then it will never work again. 

To declare: I can build several times, and every installation is working well, 
and suddenly without any reason, it breakes. Doing then using one version 
before (the last one, which worked well), it is still working, but the next 
build is crashing.

Ok, I think you understood, what I meant. Well, one reason I could imagine, 
that the debian mirror, I add during installation process is changing. I am 
using "deb.debian.org", but when using another mirror in my near, I am running 
into the same issue.

I also tried to install grub manually in the console during installation 
process, using "grub-installer /target", but this did neither work nor show 
much usefull information.

Any idea, why this is happening? I saw similar messages in some forums, but 
they are all related to Debian 10, which is rather old (and I suppose, these 
bugs are fixed).

Thanks for any hints and help!

Best regards

Hans   

Re: about 10th new install of bullseye

[gene heskett]

On 6/7/24 07:16, Greg Wooledge wrote:

On Fri, Jun 07, 2024 at 01:14:16AM -0400, gene heskett wrote:

In experimenting I've found a name clash, there are appprently two orca's.
one is a speech synth, one is a slicer for 3d printers I don't use.


Oh!  That sounds super relevant.


I forgot to mention the speech synth is "orca", the slicer is "Orca"


If you're not using the second one, where did it come from?  If it's
interfering with your desktop environment, but you're not using it,
maybe you can get rid of it.


An AppImage, rm it.


That would be one solution path to explore.  The other... you're already
exploring, so see below.


Typing
orca in a shell locks the shell wo any output, for several minutes but comes
back to a prompt with a ctl-c, so I've NDC which was being executed.


"type orca" will tell you what the shell has chosen.

"type -a orca" will tell you all the places the shell sees it, in order.


So I took orca out, which took gnome out. But now gnomes dependencies will
put orca back in. So now I can't run autoremove.


Install "equivs".  Read its documentation.  Read it a second time,
because it's probably too subtle to get all at once.

Pick one of the example templates (mail-transport-agent is the smallest,
so I'd use that one), make a copy of it, and modify the copy.  Get rid of
the Provides and Conflicts, and replace them with a Depends: line that's
identical to the one from "gnome", except get rid of orca.  Change the
Package name and the Description to be something meaningful to you.

I'd suggest the name gene-gnome because it's a fun pun.

Build your new .deb which depends on all the parts of GNOME except for
orca.  Install it with dpkg -i.

Since the gnome Depends: line has versioned dependencies, your custom
replacement probably won't survive a dist-upgrade, so be prepared to
undo and redo this hack when you upgrade to a new version of Debian.

.


Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: about 10th new install of bullseye

[gene heskett]

On 6/7/24 07:16, Greg Wooledge wrote:

On Fri, Jun 07, 2024 at 01:14:16AM -0400, gene heskett wrote:

In experimenting I've found a name clash, there are appprently two orca's.
one is a speech synth, one is a slicer for 3d printers I don't use.


Oh!  That sounds super relevant.

If you're not using the second one, where did it come from?  If it's
interfering with your desktop environment, but you're not using it,
maybe you can get rid of it.

That would be one solution path to explore.  The other... you're already
exploring, so see below.


Typing
orca in a shell locks the shell wo any output, for several minutes but comes
back to a prompt with a ctl-c, so I've NDC which was being executed.


"type orca" will tell you what the shell has chosen.

"type -a orca" will tell you all the places the shell sees it, in order.


So I took orca out, which took gnome out. But now gnomes dependencies will
put orca back in. So now I can't run autoremove.


Install "equivs".  Read its documentation.  Read it a second time,
because it's probably too subtle to get all at once.


Where are the docs, it doesn't come with a manpage? Buried someplace in 
/usr/share/docs? Found it, instructs are in the README-Debian file but 
quite sparse.  Looks like it could work however. Needs more 
coffee...Lots more.


Thanks.


Pick one of the example templates (mail-transport-agent is the smallest,
so I'd use that one), make a copy of it, and modify the copy.  Get rid of
the Provides and Conflicts, and replace them with a Depends: line that's
identical to the one from "gnome", except get rid of orca.  Change the
Package name and the Description to be something meaningful to you.

I'd suggest the name gene-gnome because it's a fun pun.


Interesting. and something I've not tried on x86-64 machines. I do build 
stuff on the arm64, but this looks different from making a buildbot or 
rt kernel.


Build your new .deb which depends on all the parts of GNOME except for
orca.  Install it with dpkg -i.

Since the gnome Depends: line has versioned dependencies, your custom
replacement probably won't survive a dist-upgrade, so be prepared to
undo and redo this hack when you upgrade to a new version of Debian.


Noted but short term memory will probably fail.

Thank you Greg.

.


Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: about 10th new install of bullseye

[gene heskett]

On 6/7/24 04:33, mick.crane wrote:

On 2024-06-07 06:14, gene heskett wrote:


So I took orca out, which took gnome out. But now gnomes dependencies
will put orca back in. So now I can't run autoremove. So one more time
this broken damned bookworm install has bit me in a rear.

I delayed logging in after starting the PC some time ago when a voice 
boomed out the keys I was typing.

"What the.."
Reading this thread I purged orca and brltty on trixie and everything 
still seems to be working.

mick

.
Where did you get that beta trixie installer? bookworm does not allow 
that removal of orca without also removing gnome. brltty yes, but not orca.


Thanks mick.

Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: about 10th new install of bullseye

[Greg Wooledge]

On Fri, Jun 07, 2024 at 01:14:16AM -0400, gene heskett wrote:
> In experimenting I've found a name clash, there are appprently two orca's.
> one is a speech synth, one is a slicer for 3d printers I don't use.

Oh!  That sounds super relevant.

If you're not using the second one, where did it come from?  If it's
interfering with your desktop environment, but you're not using it,
maybe you can get rid of it.

That would be one solution path to explore.  The other... you're already
exploring, so see below.

> Typing
> orca in a shell locks the shell wo any output, for several minutes but comes
> back to a prompt with a ctl-c, so I've NDC which was being executed.

"type orca" will tell you what the shell has chosen.

"type -a orca" will tell you all the places the shell sees it, in order.

> So I took orca out, which took gnome out. But now gnomes dependencies will
> put orca back in. So now I can't run autoremove.

Install "equivs".  Read its documentation.  Read it a second time,
because it's probably too subtle to get all at once.

Pick one of the example templates (mail-transport-agent is the smallest,
so I'd use that one), make a copy of it, and modify the copy.  Get rid of
the Provides and Conflicts, and replace them with a Depends: line that's
identical to the one from "gnome", except get rid of orca.  Change the
Package name and the Description to be something meaningful to you.

I'd suggest the name gene-gnome because it's a fun pun.

Build your new .deb which depends on all the parts of GNOME except for
orca.  Install it with dpkg -i.

Since the gnome Depends: line has versioned dependencies, your custom
replacement probably won't survive a dist-upgrade, so be prepared to
undo and redo this hack when you upgrade to a new version of Debian.

Re: Impossible to install extensions with Gnome browser plugin

[Jan Krapivin]

Thank you for your reply. This topic is not about Debian packages, but
about a performance of a plugin for browsers, it is not a Debian package.

https://wiki.gnome.org/action/show/Projects/GnomeShellIntegration?action=show=Projects%2FGnomeShellIntegrationForChrome

I am trying to install Gnome extensions with it. They are also not Debian
packages.

https://extensions.gnome.org/about/

The problem can be reproduced only if you use Gnome.

For this you must install a special Gnome *BROWSER* plugin and try to
install any Gnome extension.

It is not a big deal, as I am still able to install Gnome extensions with
regular files.

But i wonder if it is a universal problem, and if it is not, what is wrong
with me, as i haven't done any major changes in OS.

пт, 7 июн. 2024 г. в 03:50, George at Clug :

> Hi Jan Krapivin,
>
> I am hoping someone can help you with your answer as I do not use Gnome or
> have much experience with Gnome.
>
> Which Debian package or packages are you installing?
>
> I found a list of Debian Gnome packages at
> https://packages.debian.org/stable/gnome/
>
> But I was not able to find a  "GNOME Shell integration" package ?
>
> You said, "i am unable to install new extensions with browser plugin
> "GNOME Shell integration"".
>
> Could you please explain the steps to reproduce your problem, including
> installation of the browser plugin package, how in the web browser you add
> the extension, and an example extension you were not able to install?
>
> Thanks,
>
> George.
>
>
> On Friday, 07-06-2024 at 05:27 Jan Krapivin wrote:
>
> Guys, can you please spend 30 seconds and check if it is a universal
> problem..?
>
> чт, 6 июн. 2024 г. в 13:41, Jan Krapivin :
>
>> I have a problem with a Gnome browser plugin. I have even created an
>> issue report (see below).
>>
>> Unfortunately I don't know if I am the only one with this problem.
>>
>> If you use Debian 12 stable with Gnome, please let me know about your
>> experience.
>>
>> "Hello! I use Debian 12 stable with Gnome 43.9. Recently i have found out
>> that i am unable to install new extensions with browser plugin "GNOME Shell
>> integration". I have tried different browsers: Firefox stable, Firefox-ESR,
>> Chrome. In all of them it is impossible to install a new extension.
>> Switching a tumbler from "OFF" to "ON" does nothing. Though it is possible
>> to view already installed extensions and switch them off and on. It is also
>> possible to install an extension from file.
>>
>> What i have tried: 1) Switching "Disable version validation" on and off.
>> 2) Gnome-shell reinstall. 3) gnome-browser-connector reinstall."
>>
>> https://gitlab.gnome.org/GNOME/gnome-browser-extension/-/issues/62
>>
>

Re: about 10th new install of bullseye

[mick.crane]

On 2024-06-07 06:14, gene heskett wrote:


So I took orca out, which took gnome out. But now gnomes dependencies
will put orca back in. So now I can't run autoremove. So one more time
this broken damned bookworm install has bit me in a rear.

I delayed logging in after starting the PC some time ago when a voice 
boomed out the keys I was typing.

"What the.."
Reading this thread I purged orca and brltty on trixie and everything 
still seems to be working.

mick

Re: Global Server

[Camaleón]

El 2024-06-07 a las 02:15 -0300, Carlos Villiere escribió:

> El jue, 6 jun 2024 a las 3:55, Camaleón () escribió:
> 
> > El 2024-06-05 a las 19:55 -0500, Luz Victoria Rivera escribió:
> >
> > > Buenas noches, estoy encargada de proveer el software de Global Server
> > para
> > > Linux Debían 12, podrían indicarnos con quién podemos hacer la consulta?
> >
> > No conozco esa aplicación (Global Server) y Google tampoco me despeja
> > la duda :-?
> >
> > https://www.google.com/search?q=Global+Server
> >
> > Si nos das más datos podremos orientarte mejor.

> Hola Camaleon!!
> Global Server. *Solución integrada con reconocimiento facial, inteligencia
> artificial y almacenamiento en la nube*. Las puertas automáticas son parte
> esencial de una completa solución de acceso. GLOBAL SERVER asesora, diseña
> y fabrica toda clase de puertas con control.
> https://globalserver.com.co/
> Saludos

Hum... ¿y qué tiene que ver una empresa de servicios y sistemas de 
automatización y seguridad con Debian? No veo que tengan software de 
gestión, como indica la OP, ni nada parecido o instalable :-?

No sé, necesito más datos o me falta alguna pieza del rompecabezas.

Saludos,

-- 
Camaleón 

Re: Souci de montage avec pcloud.com

[Erwan David]

Le 06/06/2024 à 11:38, Pierre Meurisse a écrit :

Bonjour,

je suis abonné à https://www.pcloud.com et je rencontre des difficultés avec le 
montage proposé.

Avec la version web, firefox,  https://my.pcloud.com, en utilisant le bouton 
"Téléversement",
le fichier IMGtest.tar de 86 Mo est téléchargé en quelques secondes.


Si par contre je lance l'application pcloud fournie, elle me crée bien le 
montage :

pCloud.fs 500G138G  363G  28% /home/pier/pCloudDrive

mais l'instruction :

cp -iv pierh/tar_gz/IMGtest.tar pCloudDrive/

ne charge qu'une vingtaine de Mo en 5 minutes

Par contre une instruction comme

pier@msi~/pCloudDrive% find . -maxdepth 1 -type d ! -name "."  -exec du -hs {} 
\;

fonctionne très bien.

Il s'agirait donc d'un pb d'upload vers pCloudDrive.
Tout fonctionnait convenablement depuis il y a environ un mois.

Je suis sur debian stable à jour.
J'ai bien sûr contacté supp...@pcloud.com. Ils m'ont fait faire des tas de 
tests et de réglages,
j'ai téléchargé la dernière version de pcloud mais rien à faire.
Nous finissons par nous demander le souci ne vient pas du côté de debian, par 
exemple depuis
la dernière maj du noyau.

Je me tourne donc vers vous pour essayer de trouver une éventuelle solution.
Merci d'avance pour les éclairages que vous pourrez apporter.


Je vois que pcloud supporte le protocole webdav 
(https://www.clubic.com/stockage-en-ligne/pcloud/tutoriel-468081-comment-acceder-a-pcloud-via-webdav.html)
 peut-être essayer via un client webdav comme cadaver, rclone ou davfs2 ? Déjà 
voir si le problème vient de leur client


--
Erwan David

Re: Souci de montage avec pcloud.com

[Pierre Meurisse]

Le Thu, Jun 06, 2024 at 10:08:48PM +0200, Étienne Mollier a écrit :
> Étienne Mollier, on 2024-06-06:
> > Pierre Meurisse, on 2024-06-06:
> > > Je suis sur debian stable à jour.
> > > J'ai bien sûr contacté supp...@pcloud.com. Ils m'ont fait faire des tas 
> > > de tests et de réglages, 
> > > j'ai téléchargé la dernière version de pcloud mais rien à faire.
> > > Nous finissons par nous demander le souci ne vient pas du côté de debian, 
> > > par exemple depuis 
> > > la dernière maj du noyau.
> > 
> > Il est possible de rétrograder la version de noyau à l'allumage
> > de la machine, depuis le menu de démarrage "GNU GRUB".  Il faut
> > choisir dans le premier panneau :
> > 
> >   * Advanced options for Debian GNU/Linux
> > 
> > Et dans le panneau suivant, choisir une version plus ancienne à
> > tester ; par défaut le sélecteur sera sur la version la plus
> > récente.  Par exemple, sur une machine de test, je choisirais :
> > 
> >   * Debian GNU/Linux, with Linux 6.1.0-20-amd64
> > 
> > afin de démarrer sur la version qui précède l'actuel Linux
> > 6.1.0-21-amd64.  Si le problème remonte à longtemps et que les
> > versions de noyau à tester ne sont plus installées, alors il est
> > possible de les rétablir en installant les paquets linux-image
> > et linux-headers anciens.  Par exemple pour rétablir la version
> > 6.1.0-18-amd64, il est toujours possible d'installer les paquets
> > suivants :
> > 
> >   * linux-image-6.1.0-18-amd64
> >   * ainsi que linux-headers-6.1.0-18-amd64 s'il est nécessaire
> > d'installer des pilotes tiers, du genre pilotes graphiques
> > propriétaires, qui auraient besoin d'être reconstruits pour
> > se raccorder à l'ancienne version de noyau.
> > 
> > Le démarreur continuera à démarrer sur le noyau le plus récent,
> > donc il ne faut pas oublier d'intercepter le menu pour choisir
> > l'ancienne version nouvellement installée.  Note : laissez de
> > côté le recovery mode, il sert à démarrer en mode de dépannage
> > chargeant aussi peu de services que possible, pour réparrer des
> > problèmes de démarrage par exemple.
> 
> J'ai oublié de préciser que si rétrograder le noyau résoud le
> problème, ce n'est en rien une solution pérenne.  L'idée est de
> faciliter au support l'identification du changement qui affecte
> leur système de fichier.  Comme dit :
> > Si ça peut aider à diagnostiquer ce qu'il se passe,
> 
> Bonne soirèe,  :)
> -- 
>   .''`.  Étienne Mollier 
>  : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
>  `. `'   sent from /dev/tty1, please excuse my verbosity
>`-on air: Deep Purple - Cry Free - (Roger Glover Remix)

Merci Etienne,

j'ai testé plusieurs anciens noyaux, en remontant même jusqu'à
linux-image-6.1.0.16-amd64 mais rien n'y fait.

Bonne journée

--
Pierre Meurisse 



-- 
Pierre Meurisse