Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #210334 > unrolled thread

Problem to locate bug

Back to article view | Back to linux.debian.user

Contents

  Problem to locate bug sj126@uranus.uni-freiburg.de - 2019-06-24 16:50 +0200
    Re: Problem to locate bug "Thomas Schmitt" <scdbackup@gmx.net> - 2019-06-24 20:20 +0200
      Re: Problem to locate bug "Julian Schreck" <schreck.julian@uranus.uni-freiburg.de> - 2019-06-28 14:10 +0200
        Re: Problem to locate bug "Thomas Schmitt" <scdbackup@gmx.net> - 2019-06-28 14:20 +0200
          Re: Problem to locate bug sj126@uranus.uni-freiburg.de - 2019-06-28 15:10 +0200
          Re: Problem to locate bug sj126@uranus.uni-freiburg.de - 2019-11-21 12:40 +0100
            Re: Problem to locate bug Jonas Smedegaard <jonas@jones.dk> - 2019-11-21 13:20 +0100
    Re: Problem to locate bug David Christensen <dpchrist@holgerdanske.com> - 2019-06-25 06:00 +0200

#210334 — Problem to locate bug

Dear all,
for some weeks (or months perhaps already), my screen freezes suddenly and once in a while without any chance to de-freeze it again. I don't know wether my input is recognized after such a freeze, but I don't think so. (I should've tested this before writing to you…)
The thing is that I don't know which package could cause this bug, therefore I'm writing to this list. As far as I can see, this behaviour may only be caused by [1-4] out of 4 programs: lxterminal, qutebrowser, evolution, openbox.
Or a package acting behind my knowledge may also be causing the freeze of my screen, which doesn't appear to come up after a specific uptime and not because I overestimate my system (at least it seems so).  
May you help me so that I can issue this to the causing package? System info will be sent when told which. (Commands for console/terminal/… preferred)

Kind regards,
 sj126

[toc] | [next] | [standalone]

#210338

Hi,

sj126@uranus.uni-freiburg.de wrote:
> As far as I can see, this behaviour may only be
> caused by [1-4] out of 4 programs: lxterminal, qutebrowser, evolution,
> openbox.

Consider to use alternatives for a few days until it is clear whether
avoiding one or more of the suspects makes the freeze vanish.


> Or a package acting behind my knowledge

Or the hardware or the firmware ...


> System info will be sent when told which.

A rough description of the kind of computer, details about the graphics
hardware, and possibly needed special graphics firmware might give ideas.

But probably you will have to use search engines to find rumors which
resemble your problem. "openbox screen freezes" shows a colorful bouquet
of symptoms. (Compare this with "fvwm screen freezes".)


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#210455

Hi,
I could narrow it down to lxterminal (autostarted), openbox or an automatically started process. Any other advice than changing the window manager (in case that was suggested/your intention)?

- A rough description of the kind of computer: ”# lshw“ gives
debian                      
    description: Desktop Computer
    product: To Be Filled By O.E.M. (To Be Filled By O.E.M.)
    vendor: To Be Filled By O.E.M.
    version: To Be Filled By O.E.M.
    serial: To Be Filled By O.E.M.
    width: 64 bits
[...]
  *-core
       description: Motherboard
       product: Z270M Pro4
       vendor: ASRock
       physical id: 0
       serial: M80-6C011101317
     *-firmware
          description: BIOS
          vendor: American Megatrends Inc.
          physical id: 0
          version: P2.50
          date: 03/16/2018
          size: 64KiB
          capacity: 16MiB
          capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi

- details about the graphics hardware: ”# lshw“ gives
        *-display
             description: VGA compatible controller
             product: Intel Corporation
             vendor: Intel Corporation
             physical id: 2
             bus info: pci@0000:00:02.0
             version: 04
             width: 64 bits
             clock: 33MHz
             capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
             configuration: driver=i915 latency=0
             resources: irq:126 memory:de000000-deffffff memory:c0000000-cfffffff ioport:f000(size=64) memory:c0000-dffff

- possibly needed special graphics firmware: some installed packages: libdrm-intel1, libwebrtc-audio-processing1, xserver-xorg-video-intel, firmware-linux-free, xserver-xorg-input-all, xserver-xorg-video-all, xserver-xorg

Kind regards,
sj126
--
> Hi,
> 
> sj126@uranus.uni-freiburg.de wrote:
> > As far as I can see, this behaviour may only be
> > caused by [1-4] out of 4 programs: lxterminal, qutebrowser, evolution,
> > openbox.
> 
> Consider to use alternatives for a few days until it is clear whether
> avoiding one or more of the suspects makes the freeze vanish.
> 
> 
> > Or a package acting behind my knowledge
> 
> Or the hardware or the firmware ...
> 
> 
> > System info will be sent when told which.
> 
> A rough description of the kind of computer, details about the graphics
> hardware, and possibly needed special graphics firmware might give ideas.
> 
> But probably you will have to use search engines to find rumors which
> resemble your problem. "openbox screen freezes" shows a colorful bouquet
> of symptoms. (Compare this with "fvwm screen freezes".)
> 
> 
> Have a nice day :)
> 
> Thomas

[toc] | [prev] | [next] | [standalone]

#210456

Hi,

Julian Schreck wrote:
> I could narrow it down to lxterminal (autostarted),

You could start another terminal program from the lxterminal and then
end the lxterminal. (I use "xterm", the old and sparse one.)
You could also check whether the lxterm menus give you an opportunity
to disable any fancy dynamic effects.


> openbox or an automatically started process.

An automatic process as culprit seems somewhat far-fetched. I understand
that you do not see a clear time pattern with the system freezes.
With an automat i'd expect some regularity.

Did you already find out whether the whole system freezes or whether it's
only about graphics and/or local user interaction ?


> Any other advice than changing the window manager
> (in case that was suggested/your intention)?

The window manager and its interaction with the system appears as first
suspect, when i ask the web.


>     description: Desktop Computer
>        description: Motherboard
>        vendor: ASRock
>        product: Z270M Pro4
>         *-display
>             description: VGA compatible controller
>             product: Intel Corporation
>             vendor: Intel Corporation

ASRock says the mainboard has AMD/ATI "Quad CrossfireX".
Am i mistaken if i assume that you currently use a plugged-in graphics
board ?


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#210458

Hi,
I tried to shut down the pc with ctrl + alt + 1 -> [login] -> sudo poweroff -> no reaction.
I had some music file playing. A snippet (< 1 s) was repeated roughly between 5 and 10 times before I didn't hear anything further on.
Ctrl + SysRq + k normally reboot immediately. In my case, no reaction.
I'm changing my terminal emulator for now…

Kind regards,
sj126
--
> Hi,
> 
> Julian Schreck wrote:
> > I could narrow it down to lxterminal (autostarted),
> 
> You could start another terminal program from the lxterminal and then
> end the lxterminal. (I use "xterm", the old and sparse one.)
> You could also check whether the lxterm menus give you an opportunity
> to disable any fancy dynamic effects.
> 
> 
> > openbox or an automatically started process.
> 
> An automatic process as culprit seems somewhat far-fetched. I understand
> that you do not see a clear time pattern with the system freezes.
> With an automat i'd expect some regularity.
> 
> Did you already find out whether the whole system freezes or whether it's
> only about graphics and/or local user interaction ?
> 
> 
> > Any other advice than changing the window manager
> > (in case that was suggested/your intention)?
> 
> The window manager and its interaction with the system appears as first
> suspect, when i ask the web.
> 
> 
> >     description: Desktop Computer
> >        description: Motherboard
> >        vendor: ASRock
> >        product: Z270M Pro4
> >         *-display
> >             description: VGA compatible controller
> >             product: Intel Corporation
> >             vendor: Intel Corporation
> 
> ASRock says the mainboard has AMD/ATI "Quad CrossfireX".
> Am i mistaken if i assume that you currently use a plugged-in graphics
> board ?
> 
> 
> Have a nice day :)
> 
> Thomas

[toc] | [prev] | [next] | [standalone]

#216311

Hi,
if it (from around June 28th) still matters for somebody: I re-installed my whole system and I couldn't re-recognise the behaviour described. I also can't remember having changed anything in the "deeper settings of the system"…

However, best regards,
 Julian Schreck
--
> Hi,
> 
> Julian Schreck wrote:
> > I could narrow it down to lxterminal (autostarted),
> 
> You could start another terminal program from the lxterminal and then
> end the lxterminal. (I use "xterm", the old and sparse one.)
> You could also check whether the lxterm menus give you an opportunity
> to disable any fancy dynamic effects.
> 
> 
> > openbox or an automatically started process.
> 
> An automatic process as culprit seems somewhat far-fetched. I understand
> that you do not see a clear time pattern with the system freezes.
> With an automat i'd expect some regularity.
> 
> Did you already find out whether the whole system freezes or whether it's
> only about graphics and/or local user interaction ?
> 
> 
> > Any other advice than changing the window manager
> > (in case that was suggested/your intention)?
> 
> The window manager and its interaction with the system appears as first
> suspect, when i ask the web.
> 
> 
> >     description: Desktop Computer
> >        description: Motherboard
> >        vendor: ASRock
> >        product: Z270M Pro4
> >         *-display
> >             description: VGA compatible controller
> >             product: Intel Corporation
> >             vendor: Intel Corporation
> 
> ASRock says the mainboard has AMD/ATI "Quad CrossfireX".
> Am i mistaken if i assume that you currently use a plugged-in graphics
> board ?
> 
> 
> Have a nice day :)
> 
> Thomas

[toc] | [prev] | [next] | [standalone]

#216313

[Multipart message — attachments visible in raw view] — view raw

Hi Julian,

Quoting sj126@uranus.uni-freiburg.de (2019-11-21 11:39:14)
> if it (from around June 28th) still matters for somebody: I 
> re-installed my whole system and I couldn't re-recognise the behaviour 
> described. I also can't remember having changed anything in the 
> "deeper settings of the system"…

Thanks for sharing.

In future, however, please strongly consider debbugs to, well, track 
bugs: https://www.debian.org/Bugs/Reporting


Debbugs is kinda designed for that, unlike this mailinglist which is not 
very good for tracking issues and triangulating them with time and 
dependencies and versions and other states.


Thanks for considering, and sincerely hope you enjoy Debian,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

[toc] | [prev] | [next] | [standalone]

#210349

On 6/24/19 6:52 AM, sj126@uranus.uni-freiburg.de wrote:
> Dear all,
> for some weeks (or months perhaps already), my screen freezes suddenly and once in a while without any chance to de-freeze it again. I don't know wether my input is recognized after such a freeze, but I don't think so. (I should've tested this before writing to you…)
> The thing is that I don't know which package could cause this bug, therefore I'm writing to this list. As far as I can see, this behaviour may only be caused by [1-4] out of 4 programs: lxterminal, qutebrowser, evolution, openbox.
> Or a package acting behind my knowledge may also be causing the freeze of my screen, which doesn't appear to come up after a specific uptime and not because I overestimate my system (at least it seems so).
> May you help me so that I can issue this to the causing package? System info will be sent when told which. (Commands for console/terminal/… preferred)
> 
> Kind regards,
>   sj126

If you have another computer with an SSH client, you could install 
openssh-server on the machine in question.  The next time it locks up, 
log in via SSH from the other machine and investigate.


David

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web