Re: EFI El Torito image on ISO9660 (was: [PATCH] bli: Fix crash in get_part_uuid)

Hi, Pascal Hambourg wrote: > Tested with debian-12.6.0-amd64-netinst.iso on QEMU+OVMF and real hardware: > (proc) (memdisk) (cd0) (cd0,apple2) (cd0,apple1) (cd0,msdos2) I wonder from where (cd0,apple2) comes. A Debian amd64 netinst ISO has a single APM partition which marks the EFI El Torito

weekly crash

This lockup was different. System totally froze, clock stopped too while scrolling a long message from the coco mailing list using tbird. Gave it a 5 second tap on the reset button but the reset was delayed by the 30 second lag before it cleared the screen and dropped into the bios to reboot.

Re: Automatic reboot on kernel crash in Debian 12 - how?

On 16/04/2024 16:17, Michael Kjörling wrote: I have a handful of Debian 12 systems that I want to configure such that they reboot automatically in case of a problem. [...] That leaves kernel-level issues. I have not tried it, but I have seen some systemd options related to configuration of

Re: Automatic reboot on kernel crash in Debian 12 - how?

On 16/04/24 at 11:17, Michael Kjörling wrote: Do I need to set some more settings to ensure that the system will automatically reboot on a panic? If so, what? Hi, In the Linux kernel source are available two options to reboot on panic: config BOOTPARAM_SOFTLOCKUP_PANIC bool "Panic

Re: Automatic reboot on kernel crash in Debian 12 - how?

On 16 Apr 2024 11:42 +0200, from geo...@nsup.org (Nicolas George): >> Are you saying that the settings themselves are reasonable for the >> purpose, and that this particular crash just happened to be such a one >> that no software running on the system in question c

Re: Automatic reboot on kernel crash in Debian 12 - how?

Michael Kjörling (12024-04-16): > Are you saying that the settings themselves are reasonable for the > purpose, and that this particular crash just happened to be such a one > that no software running on the system in question can reasonably help > with that scenario? No, unfort

Re: Automatic reboot on kernel crash in Debian 12 - how?

On 16 Apr 2024 11:22 +0200, from geo...@nsup.org (Nicolas George): >> Do I need to set some more settings to ensure that the system will >> automatically reboot on a panic? If so, what? > > If the crash was bad enough to freeze the kernel before it could > trigger the reb

Re: Automatic reboot on kernel crash in Debian 12 - how?

Michael Kjörling (12024-04-16): > However, this morning I woke up to one of those systems showing a > kernel crash dump and being frozen. Unfortunately the first part of > the crash dump had scrolled past so I couldn't tell what class of > problem caused the crash. > > Do I nee

Automatic reboot on kernel crash in Debian 12 - how?

: No such file or directory kernel.panic_on_io_nmi = 1 # However, this morning I woke up to one of those systems showing a kernel crash dump and being frozen. Unfortunately the first part of the crash dump had scrolled past so I couldn't tell what class of problem caused the crash. Do I need

Re: problèmes de copie sur un montage smb, crash kernel

entre le SMB de syno et le noyau*6.1.0-17*, car avec le noyau *6.1.0-10* pas de soucis. Apriori tester de ton côté le SMB, amènera certainement un "crash kernel" je pense. Par contre sur le syno, la version de samba est (un peu ancienne) : Version 4.15.9 Synology Build 42934, Jul  5

Re: problèmes de copie sur un montage smb, crash kernel

fonctionnent sans problème. Dans mon cas, le serveur NFS est un NAS Synology DS216se Je ne me souviens plus pourquoi j'ai des options différentes pour les deux points de montage. Erwann Le 02/02/2024 à 21:28, testeur a écrit : J'ai tenté les trois options de montage mais pas mieux. Le log du crash

Re: problèmes de copie sur un montage smb, crash kernel

J'ai tenté les trois options de montage mais pas mieux. Le log du crash noyau est quasi identique. Ça semble venir du noyau 6.1.0-17. Car avec le noyau 6.1.0-10, pas de problèmes Je vais rester sur le noyau précédent... Cdlt On 01/02/2024 10:11, Michel Verdier wrote: Le 31 janvier 2024

Re: problèmes de copie sur un montage smb, crash kernel

Le 31 janvier 2024 testeur a écrit : > voici les droits du montage : > > ├─/mnt/xxx /etc/autoxxx.smb >autofs > rw,relatime,fd=12,pgrp=1561,timeout=30,minproto=5,maxproto=5,indirect,pipe_ino=22915 > │ └─/mnt/xxx/conf >

problèmes de copie sur un montage smb, crash kernel

Bonjour, J'ai un problème pour faire une copie simple de fichiers (cp hosts hosts.txt) au sein d'un partage SMB (monté par autofs). ça m'indique "Processus arrêté", puis après un nouvel essai ça reste bloqué/freezé, je n'ai plus la main sur la console (ctl+C, D, Z n'ont aucune action). Quand

Re: Isolated Web Co Session crash Firefox-ESR

On Wed, Dec 06, 2023 at 09:27:06PM +0700, Max Nikulin wrote: > On 06/12/2023 12:04, to...@tuxteam.de wrote: > > On Wed, Dec 06, 2023 at 02:42:32AM +0800, jeremy ardley wrote: > > > > > > sudo sync; sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches' > > > > > > Sadly it looks like I'll need to do

Re: Isolated Web Co Session crash Firefox-ESR

On 06/12/2023 01:42, jeremy ardley wrote: I have discovered a magic bullet for solving running out of memory sudo sync; sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches' Sadly it looks like I'll need to do this daily, simply for using Debian Bookworm with a variety of web browsers Magic does

Re: Isolated Web Co Session crash Firefox-ESR

On 06/12/2023 12:04, to...@tuxteam.de wrote: On Wed, Dec 06, 2023 at 02:42:32AM +0800, jeremy ardley wrote: sudo sync; sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches' Sadly it looks like I'll need to do this daily, See /etc/sysctl.conf and /etc/sysctl.conf.d if you want to make such things

Re: Isolated Web Co Session crash Firefox-ESR

Karl Vogel wrote: > On Wed, Dec 06, 2023 at 06:04:36AM +0100, to...@tuxteam.de wrote: > > On Wed, Dec 06, 2023 at 02:42:32AM +0800, jeremy ardley wrote: > > > > > I have discovered a magic bullet for solving running out of memory > > > sudo sync; sudo sh -c 'echo 3 >

Re: Isolated Web Co Session crash Firefox-ESR

On Wed, Dec 06, 2023 at 06:04:36AM +0100, to...@tuxteam.de wrote: > On Wed, Dec 06, 2023 at 02:42:32AM +0800, jeremy ardley wrote: > > > I have discovered a magic bullet for solving running out of memory > > sudo sync; sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches' > > Sadly it looks like I'll

Re: Isolated Web Co Session crash Firefox-ESR

On Wed, Dec 06, 2023 at 02:42:32AM +0800, jeremy ardley wrote: [...] > I have discovered a magic bullet for solving running out of memory > > sudo sync; sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches' > > Sadly it looks like I'll need to do this daily, See /etc/sysctl.conf and

Re: Isolated Web Co Session crash Firefox-ESR

On 4/12/23 10:26, Max Nikulin wrote: On 03/12/2023 13:33, jeremy ardley wrote: On 3/12/23 13:59, Phil Wyett wrote: What type of content is generally being viewed/used in firefox? A lot of video and otherwise news and search and GPT4 ---

Re: Isolated Web Co Session crash Firefox-ESR

On 4/12/23 10:49, Max Nikulin wrote: On 04/12/2023 09:39, jeremy ardley wrote: I think I've found a potential culprit using about:processes https://openai.com 110% CPU I would try it in chromium. Some sites relies on optimizations implemented in its JavaScript engine. My observation is

Re: Isolated Web Co Session crash Firefox-ESR

On 04/12/2023 09:39, jeremy ardley wrote: I think I've found a potential culprit using about:processes https://openai.com 110% CPU I would try it in chromium. Some sites relies on optimizations implemented in its JavaScript engine. My observation is that Firefox may be CPU hungry due to

Re: Isolated Web Co Session crash Firefox-ESR

On 4/12/23 10:26, Max Nikulin wrote: > I am curious if this creature may provide a summary on user-space OOM > killers. I have never tried them, but I expect that they may be more > intelligent than the kernel-space one. I have seen mentions of the > following ones: earlyoom, nohang, oomd.

Re: Isolated Web Co Session crash Firefox-ESR

On 03/12/2023 13:33, jeremy ardley wrote: On 3/12/23 13:59, Phil Wyett wrote: What type of content is generally being viewed/used in firefox? A lot of video and otherwise news and search and GPT4 --- I am curious if this creature may

Re: Isolated Web Co Session crash Firefox-ESR

On 12/3/23 01:00, jeremy ardley wrote: On 3/12/23 15:37, Phil Wyett wrote: Not to regurgitating info here, I will add a link below that will instruct how to adjust or disable oom-killer in a sensible manner if you wish to experiment (your choice and being cautious :-)) if it is in fact the

Re: Isolated Web Co Session crash Firefox-ESR

On 4/12/23 06:08, Michael Kjörling wrote: The reason for the system slowing down seems to me to likely be that once the system comes under memory pressure (quite possibly due to an increase in anonymous pages), it must evict something, and only non-anonymous (that is, backed) pages can be

Re: Isolated Web Co Session crash Firefox-ESR

On 3 Dec 2023 14:33 +0800, from jeremy.ard...@gmail.com (jeremy ardley): >> You have swap and it is enabled? > > No Swap. I prefer not on SSD Why not? You are definitely putting the VM allocator in a much more difficult spot than necessary by not providing any swap space. If I read what you

Re: Isolated Web Co Session crash Firefox-ESR

Hi. On Sun, Dec 03, 2023 at 12:58:47PM +0800, jeremy ardley wrote: > I noticed my Firefox -esr browser becoming progressively more sluggish. Then > suddenly I was back to the system login screen > > This is not the first time this has happened although previously when it > started

Re: Isolated Web Co Session crash Firefox-ESR

On Sun, Dec 3, 2023 at 6:21 AM jeremy ardley wrote: > > On 3/12/23 13:59, Phil Wyett wrote: > > Your system RAM total is? > > 32G You might also want to try compressed memory, like zram. > > You have swap and it is enabled? > > No Swap. I prefer not on SSD In this configuration, you may want

Re: Isolated Web Co Session crash Firefox-ESR

On Sun, 2023-12-03 at 16:00 +0800, jeremy ardley wrote: > > On 3/12/23 15:37, Phil Wyett wrote: > > Not to regurgitating info here, I will add a link below that will > > instruct how to adjust or disable oom-killer in a sensible manner if > > you wish to experiment (your choice and being

Re: Isolated Web Co Session crash Firefox-ESR

On Sun, 2023-12-03 at 14:59 +0800, jeremy ardley wrote: > > On 3/12/23 14:46, Phil Wyett wrote: > > The first thing I would do before any other is to enable swap and see > > what benefits that brings. I have no production laptop or desktop > > (laptop with 32G being daily driver with NVME

Re: Isolated Web Co Session crash Firefox-ESR

On 3/12/23 15:37, Phil Wyett wrote: Not to regurgitating info here, I will add a link below that will instruct how to adjust or disable oom-killer in a sensible manner if you wish to experiment (your choice and being cautious :-)) if it is in fact the oom-killer algorithm that is the main

Re: Isolated Web Co Session crash Firefox-ESR

. 2. Add Xfce panel widgets so that I can see what is going on. Between the two, I usually have enough time to kill problem apps before a crash. And, more memory would not hurt. David

Re: Isolated Web Co Session crash Firefox-ESR

On Sun, 2023-12-03 at 14:59 +0800, jeremy ardley wrote: > > On 3/12/23 14:46, Phil Wyett wrote: > > The first thing I would do before any other is to enable swap and see > > what benefits that brings. I have no production laptop or desktop > > (laptop with 32G being daily driver with NVME

Re: Isolated Web Co Session crash Firefox-ESR

jeremy ardley writes: > I don't think it is actually a lack of memory. What I do see is all > the web browsers are up there on CPU along with nvidia-modeset. What do you consider to be "up there"? 4.3% (your highest CPU usage in this output) hardly seems to qualify as something to be concerned

Re: Isolated Web Co Session crash Firefox-ESR

On 3/12/23 14:46, Phil Wyett wrote: The first thing I would do before any other is to enable swap and see what benefits that brings. I have no production laptop or desktop (laptop with 32G being daily driver with NVME (root) and an SSD (home) drive inside) that does not have swap. I have 8G

Re: Isolated Web Co Session crash Firefox-ESR

On Sun, 2023-12-03 at 14:33 +0800, jeremy ardley wrote: > > On 3/12/23 13:59, Phil Wyett wrote: > > Your system RAM total is? > > 32G > > > > You have swap and it is enabled? > > No Swap. I prefer not on SSD > > > Hi, The first thing I would do before any other is to enable swap and see

Re: Isolated Web Co Session crash Firefox-ESR

On 3/12/23 13:59, Phil Wyett wrote: Your system RAM total is? 32G You have swap and it is enabled? No Swap. I prefer not on SSD What Desktop Environment (DE) are you using - GNOME, KDE etc.? Mate with multiple panels. How many apps would you normally be running on the system at

Re: Isolated Web Co Session crash Firefox-ESR

On Sun, 2023-12-03 at 12:58 +0800, jeremy ardley wrote: > I noticed my Firefox -esr browser becoming progressively more sluggish. > Then suddenly I was back to the system login screen > > This is not the first time this has happened although previously when it > started getting sluggish I

Re: Isolated Web Co Session crash Firefox-ESR

jeremy ardley writes: > I noticed my Firefox -esr browser becoming progressively more > sluggish. Then suddenly I was back to the system login screen > > This is not the first time this has happened although previously when > it started getting sluggish I killed all Firefox related process > >

Isolated Web Co Session crash Firefox-ESR

I noticed my Firefox -esr browser becoming progressively more sluggish. Then suddenly I was back to the system login screen This is not the first time this has happened although previously when it started getting sluggish I killed all Firefox related process System logs show the start of the

Re: unexplained crash on Ubuntu 20.04 system

On 18 Nov 2023 01:36 -0500, from noloa...@gmail.com (Jeffrey Walton): > On Fri, Nov 17, 2023 at 7:11 PM Adam Weremczuk > wrote: >> Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive. > > [...] You should probably ask on the ubuntu-users list. [...] I agree. While Ubuntu is

Re: unexplained crash

On Fri, Nov 17, 2023 at 7:11 PM Adam Weremczuk wrote: > > Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive. > > The machine was responding to ping and "telnet 22" was briefly > connecting before connection closed. > > The graphical login prompt was visible, but when I tried

Re: unexplained crash

On Sat 18 Nov 2023 at 07:06:49 (+0100), to...@tuxteam.de wrote: > On Fri, Nov 17, 2023 at 07:17:08PM +, Adam Weremczuk wrote: > > Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive. > > > > The machine was responding to ping and "telnet 22" was briefly connecting > >

Re: unexplained crash

On Fri, Nov 17, 2023 at 07:17:08PM +, Adam Weremczuk wrote: > Hello, > > Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive. > > The machine was responding to ping and "telnet 22" was briefly connecting > before connection closed. Guessing from the context, you tried to

unexplained crash

Hello, Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive. The machine was responding to ping and "telnet 22" was briefly connecting before connection closed. The graphical login prompt was visible, but when I tried to log in, it threw me to the text console. No login

Re: crash probablement lié à amdgpu

Bonjour Le 27/09/2023 à 13:03, LECOQ Vincent a écrit : [...] Depuis mon dernier apt full-upgrade hier, je constate un crash assez rapide de ma session gnome wayland. [...] Linux b550 6.5.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.3-1 (2023-09-13) x86_64 GNU/Linux oktail@b550:~$ cat /etc

crash probablement lié à amdgpu

Bonjour, J'ai jeté un oeil (rapide, trop?) aux bugs ouverts sans trouver, donc je rapporte ma petite misère. Depuis mon dernier apt full-upgrade hier, je constate un crash assez rapide de ma session gnome wayland. mon dmesg indique alors: [ 4765.695352] [ cut here

[regle] Re: [testing] crash firefox 114.0-1

Le jeudi 22 juin 2023 à 22:33 +0200, Gaëtan Perrier a écrit : > Bonjour, > > Depuis ce soir suite aux mises à jours de testing du jour, firefox crash au > démarrage même en --safe-mode. > > ~$ firefox --safe-mode > ExceptionHandler::GenerateDump cloned chi

[testing] crash firefox 114.0-1

Bonjour, Depuis ce soir suite aux mises à jours de testing du jour, firefox crash au démarrage même en --safe-mode. ~$ firefox --safe-mode ExceptionHandler::GenerateDump cloned child ExceptionHandler::WaitForContinueSignal waiting for continue signal... 16491 ExceptionHandler

Re: [SOLVED] Re: crash with wine and nvidia-driver

gt; sadly this did not work. However, I got a solution: > > > > I purged all wine packages from debian, then reinstalled wine, but only > > minimalistic, say, all necessary packages. > > > > I spared all suggested packages - and it worked now. No crash any more and

Re: [SOLVED] Re: crash with wine and nvidia-driver

packages - and it worked now. No crash any more and "primusrun glxgears -info" is now running. Great! But maybe it was wine configuration files, you seem to be using only default profile ~/.wine, and maybe files there (Windows installation so to speak) got corrupted. So not rein

[SOLVED] Re: crash with wine and nvidia-driver

. No crash any more and "primusrun glxgears -info" is now running. Additionally also the games prior not working with nvidia legacy driver are working now, too. It looks for me, some additional package forced the crash, but I can nor say, which one. It is no need, to look at, because wine

Re: crash with wine and nvidia-driver

On 13/10/2022 17:43, Hans wrote: As I am not believing, this is related to the game (as ALL games are crashing), I believe, it is related to a systematical error in the relationship between wine and nvidia-driver. To verify this hypothesis, run for example: primusrun wine notepad.exe primusrun

running outdated software (was: crash with wine and nvidia-driver)

Am 13.10.2022 um 18:43 schrieb Hans: > Hi folks, > > maybe someone got into the same problem as me and can help. Well, i cannot help. Sorry But i am very used to running outdated software, as i am living the old recipe to "never change a working system". The only thing, that i am doing is to

crash with wine and nvidia-driver

Hi folks, maybe someone got into the same problem as me and can help. I am using a laptop with a graphic chip in the intel-cpu and an extern graphic card from NVidia. The nvidia chip is an NVS4200M and running with kernel module *legacy-340xx* Yes, I know, NVidia and also Debian says, it

Nautilus crash

Hi, Anyone is having problem with Nautilus crashing on launch using Buster ? Thanks -- Polyna-Maude R.-Summerside -Be smart, Be wise, Support opensource development

Re: had another crash, reboot usb failed, powerdown reboot usb failed

On Thursday, 2 June 2022 11:02:10 EDT David Wright wrote: > On Wed 01 Jun 2022 at 19:30:37 (-0400), gene heskett wrote: > > On Wednesday, 1 June 2022 16:34:01 EDT David Wright wrote: > > > On Wed 01 Jun 2022 at 01:23:08 (-0400), gene heskett wrote: > > > > On Wednesday, 1 June 2022 00:58:32 EDT

Re: had another crash, reboot usb failed, powerdown reboot usb failed

On Thursday, 2 June 2022 10:39:33 EDT gene heskett wrote: > On Thursday, 2 June 2022 04:08:45 EDT Anssi Saari wrote: > > gene heskett writes: > > > Do I have to reset those perms everytime I'm forced to reboot, > > > which > > > is usually in 5 to 10 days. Or is there someplace in > > >

Re: had another crash, reboot usb failed, powerdown reboot usb failed

On Thursday, 2 June 2022 10:39:33 EDT gene heskett wrote: > On Thursday, 2 June 2022 04:08:45 EDT Anssi Saari wrote: > > gene heskett writes: > > > Do I have to reset those perms everytime I'm forced to reboot, > > > which > > > is usually in 5 to 10 days. Or is there someplace in > > >

Re: had another crash, reboot usb failed, powerdown reboot usb failed

On Wed 01 Jun 2022 at 19:30:37 (-0400), gene heskett wrote: > On Wednesday, 1 June 2022 16:34:01 EDT David Wright wrote: > > On Wed 01 Jun 2022 at 01:23:08 (-0400), gene heskett wrote: > > > On Wednesday, 1 June 2022 00:58:32 EDT David Wright wrote: > > > > On Wed 01 Jun 2022 at 00:26:27 (-0400),

Re: had another crash, reboot usb failed, powerdown reboot usb failed

On Thursday, 2 June 2022 04:08:45 EDT Anssi Saari wrote: > gene heskett writes: > > Do I have to reset those perms everytime I'm forced to reboot, which > > is usually in 5 to 10 days. Or is there someplace in > > /lib/udev/rules.d where I can fix this until the next udev update? > > It seems

Re: had another crash, reboot usb failed, powerdown reboot usb failed

gene heskett writes: > Do I have to reset those perms everytime I'm forced to reboot, which is > usually in 5 to 10 days. Or is there someplace in /lib/udev/rules.d where > I can fix this until the next udev update? It seems almost certain the permissions for /dev/ttyUSB* won't stick, unless

Re: had another crash, reboot usb failed, powerdown reboot usb failed

On Wednesday, 1 June 2022 16:34:01 EDT David Wright wrote: > On Wed 01 Jun 2022 at 01:23:08 (-0400), gene heskett wrote: > > On Wednesday, 1 June 2022 00:58:32 EDT David Wright wrote: > > > On Wed 01 Jun 2022 at 00:26:27 (-0400), gene heskett wrote: > > > > On Tuesday, 31 May 2022 16:25:01 EDT

Re: had another crash, reboot usb failed, powerdown reboot usb failed

On Wednesday, 1 June 2022 16:34:01 EDT David Wright wrote: > On Wed 01 Jun 2022 at 01:23:08 (-0400), gene heskett wrote: > > On Wednesday, 1 June 2022 00:58:32 EDT David Wright wrote: > > > On Wed 01 Jun 2022 at 00:26:27 (-0400), gene heskett wrote: > > > > On Tuesday, 31 May 2022 16:25:01 EDT

Re: had another crash, reboot usb failed, powerdown reboot usb failed

On Wed 01 Jun 2022 at 01:23:08 (-0400), gene heskett wrote: > On Wednesday, 1 June 2022 00:58:32 EDT David Wright wrote: > > On Wed 01 Jun 2022 at 00:26:27 (-0400), gene heskett wrote: > > > On Tuesday, 31 May 2022 16:25:01 EDT Andrew M.A. Cater wrote: > > > > On Tue, May 31, 2022 at 03:25:59AM

Re: had another crash, reboot usb failed, powerdown reboot usb failed

On Wednesday, 1 June 2022 00:58:32 EDT David Wright wrote: > On Wed 01 Jun 2022 at 00:26:27 (-0400), gene heskett wrote: > > On Tuesday, 31 May 2022 16:25:01 EDT Andrew M.A. Cater wrote: > > > On Tue, May 31, 2022 at 03:25:59AM -0400, gene heskett wrote: > > I now know where the seriel convertors

Re: had another crash, reboot usb failed, powerdown reboot usb failed

On Wed 01 Jun 2022 at 00:26:27 (-0400), gene heskett wrote: > On Tuesday, 31 May 2022 16:25:01 EDT Andrew M.A. Cater wrote: > > On Tue, May 31, 2022 at 03:25:59AM -0400, gene heskett wrote: > I now know where the seriel convertors are so I can unplug them so I > could reinstall for about the

Re: had another crash, reboot usb failed, powerdown reboot usb failed

On Tuesday, 31 May 2022 16:25:01 EDT Andrew M.A. Cater wrote: > On Tue, May 31, 2022 at 03:25:59AM -0400, gene heskett wrote: > > See subject, mouse, keyboard, usb printers working, but /dev/ttyUSB* > > is not, > > > > "sudo lsusb -v|grep -C3 Couldn -" reports most devices can't be > > opened.>

Re: had another crash, reboot usb failed, powerdown reboot usb failed

On Tue, May 31, 2022 at 03:25:59AM -0400, gene heskett wrote: > See subject, mouse, keyboard, usb printers working, but /dev/ttyUSB* is > not, > > "sudo lsusb -v|grep -C3 Couldn -" reports most devices can't be opened. > Example: > gene@coyote:/etc/nut$ sudo lsusb -v|grep -c3 Couldn - > can't

had another crash, reboot usb failed, powerdown reboot usb failed

See subject, mouse, keyboard, usb printers working, but /dev/ttyUSB* is not, "sudo lsusb -v|grep -C3 Couldn -" reports most devices can't be opened. Example: gene@coyote:/etc/nut$ sudo lsusb -v|grep -c3 Couldn - can't get debug descriptor: Resource temporarily unavailable can't get device

Re: Crash on starting cheese

Hello Armin, did it work before? Might not be related, but I had the following experience with Cheese: I somehow managed to select an invalid resolution for my cam, which also made Cheese crash IIRC. The solution was to reset it's resolution settings with the dconf-editor. You can always report

Crash on starting cheese

Hi, I´ve just experienced the following crash on starting cheese on my installation. Since I´m not sure where to report the but I´m asking on this list for help. Camera device is: Bus 001 Device 007: ID 0c45:62c0 Microdia Sonix USB 2.0 Camera Here a stack trace: [?2004h[?2004l[?2004h

Subject: sync sync, was Re: Problem with crash post-install

On Fri Jul 30 10:11:24 2021 "Thomas Schmitt" wrote: > to...@tuxteam.de wrote: > >>> While I've read about issuing sync *twice* with the explanation >>> that sysadmins are a supersticious bunch > > Polyna-Maude Racicot-Summerside wrote: > >> I'm really asking why do it 3 time. >> In case it came

Re: Problem with crash post-install [ was: Update or reinstall ]

Hi, On 2021-07-29 3:13 p.m., David Wright wrote: > > I realise that we're not all receiving posts from Gunnar, but do we > actually know what the "update problem" is? > > I recall: > https://lists.debian.org/debian-user/2021/07/msg01003.html > Is this the origin of the system under discussion?

Re: Problem with crash post-install [ was: Update or reinstall ]

On Thu 29 Jul 2021 at 18:09:51 (+0200), Marco Möller wrote: > On 29.07.21 12:52, Polyna-Maude Racicot-Summerside wrote: > > I'm really asking why do it 3 time. > > In case it came back to the prompt *before* finishing to do it's job ? > > (...) > Misunderstanding: I wanted to suggest to run a

Re: sync sync, was Re: Problem with crash post-install

Hi, On 2021-07-29 7:35 a.m., Thomas Schmitt wrote: > Hi, > > to...@tuxteam.de wrote: >>> While I've read about issuing sync *twice* with the explanation >>> that sysadmins are a supersticious bunch > > Polyna-Maude Racicot-Summerside wrote: >> I'm really asking why do it 3 time. >> In case it

Re: Problem with crash post-install [ was: Update or reinstall ]

On 29.07.21 12:52, Polyna-Maude Racicot-Summerside wrote: Hi, On 2021-07-29 6:48 a.m., to...@tuxteam.de wrote: On Thu, Jul 29, 2021 at 12:29:16PM +0200, Marco Möller wrote: On 29.07.21 10:25, Polyna-Maude Racicot-Summerside wrote: Hi, (...) Gunnar ( Gunnar Gervin ) is having problem with

Re: Problem with crash post-install [ was: Update or reinstall ]

Dan Ritter wrote: ... > There are situations in which it can take much longer than a few > seconds. They require a large amount of data to write and a slow > storage mechanism. > > Specific example: recursive copying of music files to my USB-2 > attached music player, which has an actual write

Re: Problem with crash post-install [ was: Update or reinstall ]

Greg Wooledge wrote: > which says: > > On Linux, sync is only guaranteed to schedule the dirty blocks for > writing; it can actually take a short time before all the blocks are > finally written. The reboot(8) and halt(8) commands take this into >

Re: Problem with crash post-install [ was: Update or reinstall ]

On Thu, Jul 29, 2021 at 06:52:37AM -0400, Polyna-Maude Racicot-Summerside wrote: > As far as I know, sync doesn't work in the background ! On many systems, it does. I can't even find a clear statement in the bullseye sync(1) man page of whether it does or not. The bullseye sync(1) comes from

sync sync, was Re: Problem with crash post-install

Hi, to...@tuxteam.de wrote: > > While I've read about issuing sync *twice* with the explanation > > that sysadmins are a supersticious bunch Polyna-Maude Racicot-Summerside wrote: > I'm really asking why do it 3 time. > In case it came back to the prompt *before* finishing to do it's job ? I

Re: Problem with crash post-install [ was: Update or reinstall ]

Hi, On 2021-07-29 6:48 a.m., to...@tuxteam.de wrote: > On Thu, Jul 29, 2021 at 12:29:16PM +0200, Marco Möller wrote: >> >> On 29.07.21 10:25, Polyna-Maude Racicot-Summerside wrote: >>> Hi, >>> (...) >>> Gunnar ( Gunnar Gervin ) is having problem with >>> his laptop. >>> The system crashes

Re: Problem with crash post-install [ was: Update or reinstall ]

On Thu, Jul 29, 2021 at 12:29:16PM +0200, Marco Möller wrote: > > On 29.07.21 10:25, Polyna-Maude Racicot-Summerside wrote: > >Hi, > >(...) > >Gunnar ( Gunnar Gervin ) is having problem with > >his laptop. > >The system crashes post-update. > > > >He need to do clean install every time. > >And

Re: Problem with crash post-install [ was: Update or reinstall ]

Hi, On 2021-07-29 6:29 a.m., Marco Möller wrote: > > On 29.07.21 10:25, Polyna-Maude Racicot-Summerside wrote: >> Hi, >> (...) >> Gunnar  ( Gunnar Gervin ) is having problem with >> his laptop. >> The system crashes post-update. >> >> He need to do clean install every time. >> And this is

Re: Problem with crash post-install [ was: Update or reinstall ]

On 29.07.21 10:25, Polyna-Maude Racicot-Summerside wrote: Hi, (...) Gunnar ( Gunnar Gervin ) is having problem with his laptop. The system crashes post-update. He need to do clean install every time. And this is probably time consuming for him. If other user has some hints... Without

Problem with crash post-install [ was: Update or reinstall ]

Hi, On 2021-07-29 3:25 a.m., Gunnar Gervin wrote: > The *link* is your request of it. > Geg > > On Thu, 29 Jul 2021, 00:25 Polyna-Maude Racicot-Summerside, > mailto:deb...@polynamaude.com>> wrote: > > Hi, > > On 2021-07-28 3:16 p.m., Gunnar Gervin wrote: > > It is a Toshiba 160 gb

Re: Gimp Crash debug

p-2.10(file_open_from_command_line+0x1ad)[0x5640acb4e1cd] > gimp-2.10(app_run+0x2ec)[0x5640ac7bfc4c] > gimp-2.10(main+0x395)[0x5640ac7bf5b5] > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7fc2198ad09b] > gimp-2.10(_start+0x2a)[0x5640ac7bf73a] GIMP crash with floating point

Gimp Crash debug

``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured

RE: Sid random crash with no clue in log files

/10/28 14:00:50 Para: debian-user@lists.debian.org Assunto: Re: Sid random crash with no clue in log files On Wed, Oct 28, 2020 at 04:09:33PM +0100, Sébastien Kalt wrote: > Hello, > > I'm having random crashes on my ASUS PN50 mini PC : sometimes it's while > copying large files thr

Re: Sid random crash with no clue in log files

hing ... > > I can't manage to have a pattern for thoses craches. Today it craches 4 > times, the last week it didn't crash. > > I encoded a video with 100 % CPU charge during one hour and it didn't crash. > > When I look at the log files, I see nothing : syslog, messages, da

Re: Sid random crash with no clue in log files

On Wed, 28 Oct 2020 16:09:33 +0100 Sébastien Kalt wrote: > I'm having random crashes on my ASUS PN50 mini PC : sometimes it's > while copying large files through network, sometimes when watching a > youtube video, sometimes juste using LibreOffice, or going nothing ... > Do you have any

Re: Sid random crash with no clue in log files

the power button for a long time. [...] Hello, common things to test in case of random crashes are hardware-related issues like cooling (CPU temperatures?), power supply and RAM (memtest86+). Another thing to debug is: While the system is in the described crash state, you can still move

Sid random crash with no clue in log files

, the last week it didn't crash. I encoded a video with 100 % CPU charge during one hour and it didn't crash. When I look at the log files, I see nothing : syslog, messages, daemon.log, kern.log, Xorg.0.log.old, dmesg When it crashes, the system seems to be not responding, I can move the mouse

Re: GIMP Crash

Ryan Young writes: > Here is the bug info > > ``` > GNU Image Manipulation Program version 2.10.8 In that case, if you are in Debian, you would be send bug report. So that the maintainer can be know what problem is. https://www.debian.org/Bugs/Reporting Actually, you must add contain keywords

GIMP Crash

Here is the bug info ``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target:

Re: [crash] Evolution sous testing

Le Sat, 18 Apr 2020 11:14:39 +0200, Jean-Marc a écrit : > Et pour info, pour le moment, il y a pas mal de paquets migrés vers Gnome > 3.36. C'est peut-être une source possible de soucis. A mon humble avis, supprimer le "peut-être" de la phrase, les versions de gnome et les compatibilités c'est

Re: [crash] Evolution sous testing

Fri, 17 Apr 2020 23:48:02 +0200 Frederic Zulian écrivait : > Bonjour, salut Frédéric, > Je tente de sortir de ma dépendance à l'écosystème Google en commençant par > les mails avec Evolution. > L'installation et la configuration se sont déroulées sans problème. Okay. > Désormais lorsque je

Re: [crash] Evolution sous testing

apparemment il y a un problème avec la librairie GLib. Peut-être installer la dernière version de GLib et recompiler? e.e. Le vendredi 17 avril 2020 à 23:48:35 UTC+2, Frederic Zulian a écrit : Bonjour, Je tente de sortir de ma dépendance à l'écosystème Google en commençant par

  1   2   3   4   5   6   7   8   9   10   >