Your message dated Sun, 18 Jan 2015 17:24:08 -0800 with message-id <cafuqieb+2vgnepw2gktdmcam1tfele0qztlbma4brsi5xmh...@mail.gmail.com> and subject line Re: Bug#752380: fvwm: FvwmPager is permanently crashing has caused the Debian Bug report #752380, regarding fvwm: FvwmPager is permanently crashing to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 752380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752380 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: fvwm Version: 1:2.6.5.ds-3 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? 1. Clicking on Pager. 2. Restarting Fvwm * What exactly did you do (or not do) that was effective (or ineffective)? 1. I clicked on Page to switch to another Virtual desktop 2. Or I restarted Fvwm because pager was not there. Sometimes I need to restart 3-4 times till the pager stays running. * What was the outcome of this action? Pager disapears. And I do not see it among the running processes. I observe this problem already longer time. Sometimes it is frequent and sometimes just once a month. * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'testing'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10.5 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fvwm depends on: ii libc6 2.19-1 ii libcairo2 1.12.16-2 ii libfontconfig1 2.11.0-5 ii libfreetype6 2.5.2-1 ii libfribidi0 0.19.6-1 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libice6 2:1.0.8-2 ii libperl4-corelibs-perl 0.003-1 ii libpng12-0 1.2.50-1 ii libreadline6 6.3-6 ii librplay3 3.3.2-14 ii librsvg2-2 2.40.2-1 ii libsm6 2:1.2.1-2 ii libstroke0 0.5.1-6 ii libtinfo5 5.9+20140118-1 ii libx11-6 2:1.6.2-2 ii libxcursor1 1:1.1.14-1 ii libxext6 2:1.3.2-1 ii libxft2 2.3.1-2 ii libxinerama1 2:1.1.3-1 ii libxpm4 1:3.5.10-1 ii libxrender1 1:0.9.8-1 ii perl 5.18.2-4 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages fvwm recommends: ii fvwm-icons 20070101-2 ii libx11-protocol-perl 0.56-6 ii perl-tk 1:804.032-2 Versions of packages fvwm suggests: ii cpp 4:4.8.2-4 pn fvwm-themes <none> ii m4 1.4.17-4 ii menu 2.1.46 pn wm-icons <none> -- no debconf information
--- End Message ---
--- Begin Message ---Version: 1:2.6.5.ds-3 Since the submitter did not provide a way to reliably reproduce this bug, I am now closing this report. Feel free to reopen this bug if the issue remains unresolved. Regards, Vincent Chen
--- End Message ---
