Bug#639173: debian-reference-en: Typo in APT packages location

2011-08-24 Thread Wirawan Purwanto
Package: debian-reference-en
Version: 2.46
Severity: minor


I found an error in the online version of debian reference,

http://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_local_copies_of_the_fetched_packages

The current version says:

2.5.7. Local copies of the fetched packages

All the remotely fetched packages via APT mechanism are stored in the
/var/cache/apt/packages until they are cleaned.

Isn't he correct directory name /var/cache/apt/archives ? I checked this
against my debian system (squeeze).

Thanks,
Wirawan

-- System Information:
Debian Release: 6.0.2
  APT prefers stable
  APT policy: (700, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#649047: xpdf: Random stray characters added to filepath when invoking Open dialog

2011-11-16 Thread Wirawan Purwanto
Package: xpdf
Version: 3.02-12
Severity: normal

*** Please type your report below this line ***


This is how I cause this bug to appear:

* For this case, I am using sample pdf that you can get from
 http://samplepdf.com/sample.pdf . Any other PDF files will do, but
 let's use that for uniformity.

* On a subdirectory whose total path length (of the absolute path) is
more than 22 characters, I open a pdf file. For this example, I am
making subdirectory /tmp/012345678901234567 -- 23 characters in
length including all the slashes -- and download the sample PDF
there. So, it's roughly like this:

  $ mkdir /tmp/012345678901234567
  $ cd /tmp/012345678901234567
  $ wget http://samplepdf.com/sample.pdf
  $ xpdf sample.pdf

* Now press o which will bring the open dialog.

I found that in my case, the path in the Filter box becomes:

  /tmp/012345678901234567/NG/*.[Pp][Dd][Ff]

and the Selection becomes

  /tmp/012345678901234567/NG/

The random characters (NG in this case) always differ from
invocation to invocation.
Apparently 22 characters in the directory name length is the boundary
where things are still sane; beyond that this crazy thing happens.

This is what I observe:

* If I invoke xpdf without argument and then press o, this bug
 does not appear.

* If I invoke xpdf /tmp/012345678901234567/sample.pdf then this bug
 does not appear.

Something is screwy in one corner case described above only.

Can somebody else reproduce this bug with their xpdf? I never observed
this in xpdf in, e.g. Ubuntu 10.04 or earlier edition of Ubuntu.
My experience with Debian is rather limited as far as versions go.

Wirawan

-- System Information:
Debian Release: 6.0.3
 APT prefers stable-updates
 APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-bpo.2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xpdf depends on:
ii  lesstif2                      1:0.95.2-1 OSF/Motif 2.1 implementation relea
ii  libc6                         2.11.2-10  Embedded GNU C Library: Shared lib
ii  libgcc1                       1:4.4.5-8  GCC support library
ii  libpoppler5                   0.12.4-1.2 PDF rendering library
ii  libstdc++6                    4.4.5-8    The GNU Standard C++ Library v3
ii  libx11-6                      2:1.3.3-4  X11 client-side library
ii  libxt6                        1:1.0.7-1  X11 toolkit intrinsics library

Versions of packages xpdf recommends:
pn  gsfonts-x11                   none     (no description available)
pn  poppler-data                  none     (no description available)
ii  poppler-utils                 0.12.4-1.2 PDF utilitites (based on libpopple

xpdf suggests no packages.

-- no debconf information



-- 
Wirawan Purwanto
Research Scientist
College of William and Mary
Physics Department
Williamsburg, VA 23187



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#650748: xserver-xorg-video-intel: [i915] Intel Mobile 4 Series: Libreoffice 3.4.3 main window content not drawn or updated properly

2011-12-12 Thread Wirawan Purwanto
Sorry it took so long to reply this question. I tested today on 3.1
(Linux 3.1.0-1-amd64 from Debian testing); it still shown the exact
same problem---i.e. the gray background in the libreoffice's front
page not being painted properly.

Wirawan

On Sat, Dec 3, 2011 at 10:49 AM, Julien Cristau jcris...@debian.org wrote:
 On Fri, Dec  2, 2011 at 09:57:47 -0500, Wirawan Purwanto wrote:

 Notice that I am using backport version of the kernel (2.6.38), and this
 debian OS is configured to use software from stable repository by
 default.

 Is it reproducible with 3.0 or 3.1?

 Cheers,
 Julien



-- 
Wirawan Purwanto
Research Scientist
College of William and Mary
Physics Department
Williamsburg, VA 23187



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#652102: xpdf wrapper incorrectly quotes arguments for -z, -g, -remote, etc.

2011-12-14 Thread Wirawan Purwanto
Package: xpdf
Version: 3.02-21
Severity: normal


Just got a new xpdf from testing repo.
It turns out that xpdf is now a shell script, but the logic to quote the
argument of -g, -z, etc is not correct. Example:

/tmp $ /usr/bin/xpdf -g 1024x768 sample.pdf
Warning: Shell widget xpdf.real has an invalid geometry specification: 
'1024x768'
Warning: Shell widget win has an invalid geometry specification: 
'1024x768'

The culprit is here (snippet from /usr/bin/xpdf):

while [ $# -gt 0 ]; do
case $1 in

-z|-g|-geometry|-remote|-rgb|-papercolor|-eucjp|-t1lib|-ps|-paperw|-paperh|-upw)
cmd=$cmd $1 '$2'  shift ;;

In the last line, the single quotes are added, but later it gets digested
as literal single quote characters.
I don't have an idea right now on how to fix this, but just pass this on
to you all.

Thanks,
Wirawan

-- System Information:
Debian Release: 6.0.3
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (50, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xpdf depends on:
ii  lesstif2 1:0.95.2-1  OSF/Motif 2.1 implementation relea
ii  libc62.11.2-10   Embedded GNU C Library: Shared lib
ii  libgcc1  1:4.4.5-8   GCC support library
ii  libpoppler13 0.16.7-2+b1 PDF rendering library
ii  libstdc++6   4.6.2-4 GNU Standard C++ Library v3
ii  libx11-6 2:1.3.3-4   X11 client-side library
ii  libxt6   1:1.0.7-1   X11 toolkit intrinsics library

Versions of packages xpdf recommends:
pn  gsfonts-x11   none (no description available)
pn  poppler-data  none (no description available)
ii  poppler-utils 0.12.4-1.2 PDF utilitites (based on libpopple

xpdf suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#668470: alsa-base: Intel Corporation 82801I (ICH9 Family) HD Audio microphone not working (squeeze stable)

2012-04-11 Thread Wirawan Purwanto
Package: alsa-base
Version: 1.0.23+dfsg-2
Severity: normal


Ever since I installed Debian squeeze on my laptop (Thinkpad T400) the
internal microphone did not work.
I tried to tweak the volume settings via alsamixer, no sound coming out.
Tested recording with arecord or audacity, no sound at all.
Also the recording volume level meter on audacity did not indicate any
signal at all coming from the microphone (whether it is internal mic or
external one plugged via the analog mic jack).
Some people gave up and simply used PulseAudio, e.g.

http://forums.debian.net/viewtopic.php?f=6t=76099p=429287#p429287

but I think this error should be resolved so user can use plain ALSA for
the sound system if so desired.

I have tried kernel 2.6.38-bpo and 3.2.0-bpo and in both the mic did not
seem to work.

Wirawan

-- Package-specific info:
--- Begin additional package status ---
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  
  Description
+++-==-==-
ii  libasound2 1.0.23-2.1   
  shared library for ALSA applications
--- End additional package status ---
--- Begin /proc/asound/version ---
Advanced Linux Sound Architecture Driver Version 1.0.24.
--- End /proc/asound/version ---
--- Begin /proc/asound/cards ---
 0 [Intel  ]: HDA-Intel - HDA Intel
  HDA Intel at 0xfc02 irq 48
29 [ThinkPadEC ]: ThinkPad EC - ThinkPad Console Audio Control
  ThinkPad Console Audio Control at EC reg 0x30, fw 
7VHT12WW-1.01
--- End /proc/asound/cards ---
--- Begin /dev/snd/ listing ---
total 0
drwxr-xr-x  2 root root   80 Mar 29 12:10 by-path
crw-rw+ 1 root audio 116,  7 Mar 29 12:10 controlC0
crw-rw+ 1 root audio 116,  2 Mar 29 12:10 controlC29
crw-rw+ 1 root audio 116,  6 Mar 29 12:10 hwC0D0
crw-rw+ 1 root audio 116,  5 Mar 29 12:10 hwC0D1
crw-rw+ 1 root audio 116,  4 Apr 11 23:13 pcmC0D0c
crw-rw+ 1 root audio 116,  3 Apr 11 23:13 pcmC0D0p
crw-rw+ 1 root audio 116,  1 Mar 29 12:10 seq
crw-rw+ 1 root audio 116, 33 Mar 29 12:10 timer
--- End /dev/snd/ listing ---

-- System Information:
Debian Release: 6.0.4
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (500, 'stable'), (50, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-0.bpo.2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages alsa-base depends on:
ii  linux-sound-base   1.0.23+dfsg-2 base package for ALSA and OSS soun
ii  lsof   4.81.dfsg.1-1 List open files
ii  module-init-tools  3.12-2tools for managing Linux kernel mo
ii  udev   164-3 /dev/ and hotplug management daemo

Versions of packages alsa-base recommends:
ii  alsa-utils1.0.23-3   Utilities for configuring and usin

Versions of packages alsa-base suggests:
pn  alsa-oss  none (no description available)
ii  apmd  3.2.2-14   Utilities for Advanced Power Manag
pn  oss-compatnone (no description available)

Versions of packages libasound2 depends on:
ii  libc6 2.11.3-3   Embedded GNU C Library: Shared lib

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#719918: quodlibet: Quod Libet sometimes crashes when an external drive (USB) is mounted

2013-08-16 Thread Wirawan Purwanto
Package: quodlibet
Version: 2.4-1
Severity: normal

I found that quodlibet that comes with Debian 7 stable always crashes when an
external USB drive is inserted and mounted. My system is debian 7 xfce edition,
x86_64. I notice that at least once it coincides with thunar going down (also
crashing). I put this bug notice here first in hope that others would notice
it. I will include more technical info if and when it becomes available.
Apparently, being a python script, quodlibet does not produce debugging output
or core dump by default.

Wirawan



-- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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 quodlibet depends on:
ii  exfalso 2.4-1
ii  gstreamer0.10-plugins-base  0.10.36-1.1
ii  gstreamer0.10-plugins-good  0.10.31-3+nmu1
ii  gstreamer0.10-plugins-ugly  0.10.19-2+b2
ii  python  2.7.3-4
ii  python-gst0.10  0.10.22-3

Versions of packages quodlibet recommends:
ii  gstreamer0.10-alsa [gstreamer0.10-audiosink]  0.10.36-1.1
ii  gstreamer0.10-plugins-bad [gstreamer0.10-audiosink]   0.10.23-7.1
ii  gstreamer0.10-plugins-good [gstreamer0.10-audiosink]  0.10.31-3+nmu1
ii  media-player-info 17-1
ii  python-dbus   1.1.1-1
ii  python-feedparser 5.1.2-1
ii  python-gpod   0.8.2-7
ii  python-mmkeys 1.6.2.1-5
ii  udisks1.0.4-7

Versions of packages quodlibet suggests:
ii  gstreamer0.10-gconf0.10.31-3+nmu1
ii  gstreamer0.10-plugins-bad  0.10.23-7.1
ii  quodlibet-plugins  1:2.4-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#720059: xfwm4: Window resize with keyboard failed to repeat with right- and down-arrow keys

2013-08-17 Thread Wirawan Purwanto
Package: xfwm4
Version: 4.8.3-2
Severity: normal

Dear Maintainer,

I found that xfce4 window manager that shipped with Debian 7 (stable) failed to
let right and down arrow keys to resize the window manually.  On my system I
set SuperF8 to begin the manual resizing of the active window. I was able to
use left and up keys to resize the window. But when pressing the right and down
arrow keys, the window would resize only a small size, then it would not resize
anymore. This is bizzare behavior; I remember from long time ago that such
buggy behavior is not present.

Wirawan



-- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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 xfwm4 depends on:
ii  libc6 2.13-38
ii  libdbus-glib-1-2  0.100.2-1
ii  libgdk-pixbuf2.0-02.26.1-1
ii  libglib2.0-0  2.33.12+really2.32.4-5
ii  libgtk2.0-0   2.24.10-2
ii  libpango1.0-0 1.30.0-1
ii  libstartup-notification0  0.12-1
ii  libwnck22 2.30.7-1
ii  libx11-6  2:1.5.0-1+deb7u1
ii  libxcomposite11:0.4.3-2
ii  libxdamage1   1:1.1.3-2
ii  libxext6  2:1.3.1-2+deb7u1
ii  libxfce4ui-1-04.8.1-1
ii  libxfce4util4 4.8.2-1
ii  libxfconf-0-2 4.8.1-1
ii  libxfixes31:5.0-4+deb7u1
ii  libxrandr22:1.3.2-2+deb7u1
ii  libxrender1   1:0.9.7-1+deb7u1

Versions of packages xfwm4 recommends:
ii  librsvg2-common  2.36.1-1
ii  xfwm4-themes 4.6.0-3

Versions of packages xfwm4 suggests:
ii  xfce4  4.8.0.3

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#710138: xfce4: Tab completion not working as expected in file selection dialog text entry (Ctrl+L)

2013-05-28 Thread Wirawan Purwanto
Package: xfce4
Version: 4.8.0.3
Severity: normal

I notice that the xfce4 version 4.8 in Debian 7 have problem with tab
completion int he file selection dialog (usually used for File/Open or
File/Save As operations). As for specific examples, I can notice this problem
in LibreOffice (The one shipped with Debian 7 stable) or Firefox Aurora (v 22),
or mousepad --it really does not matter as long the xfce file dialog is shown.
I notice that the first tab completion in the text entry (shown by Ctrl+L
shortcut) would work, but then it would not do the second filename completion.
Say, I want to save a text file in mousepad to /home/wirawan/test.txt ; I can
begin using /ho TAB -- completed to /home. I would expect /home/wi
TAB would complete to /home/wirawan, but it would not. Rather the focus
moves to the next element (Places sidebar below the Name and Save in
folder entries). So, why is this behavior? This is not desirable from power
user perspective. Unless I misunderstand how xfce file dialog should work.

Wirawan



-- System Information:
Debian Release: 7.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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 xfce4 depends on:
ii  gtk2-engines-xfce  2.8.1-3
ii  orage  4.8.3-2
ii  thunar 1.2.3-4+b1
ii  xfce4-appfinder4.8.0-3
ii  xfce4-mixer4.8.0-3+b1
ii  xfce4-panel4.8.6-4
ii  xfce4-session  4.8.3-3
ii  xfce4-settings 4.8.3-2
ii  xfce4-utils4.8.3-2
ii  xfconf 4.8.1-1
ii  xfdesktop4 4.8.3-2
ii  xfwm4  4.8.3-2

Versions of packages xfce4 recommends:
ii  desktop-base  7.0.3
ii  tango-icon-theme  0.8.90-5
ii  thunar-volman 0.6.1-1
ii  xfce4-notifyd 0.2.2-2
ii  xorg  1:7.7+2

Versions of packages xfce4 suggests:
ii  xfce4-goodies  4.8.2
ii  xfprint4   4.6.1-3

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#710297: cups: server-error-internal-error encountered when setting up new printer (Dell 5130cdn color laser)

2013-05-29 Thread Wirawan Purwanto
Package: cups
Version: 1.5.3-5
Severity: normal

Dear Maintainer,

In Debian 7 stable with the provided cups (1.5.3-5) I tried to add a new
printer with external PPD file. The printer is: Dell C3760DN color laser
printer, and I used the PPD given by Dell.
The driver (PPD actually) was obtained from

http://www.dell.com/support/drivers/us/en/04/DriverDetails/Product/dell-
c3760dn?driverId=YN48JosCode=LNUXfileId=2998271512languageCode=ENcategoryId=DD

I converted the RPM to DEB with alien. Installed it, and tried to set up the
printer using the GTK GUI (system-config-printer command). I then specified the
PPD location manually in the dialog titled Choose Driver. But when I clicked
Apply in the Describe Printer, an error message shows up with this error:

   CUPS server error
   There was an error during the CUPS operation: 'server-error-internal-error'.

I increased the log level to 'debug2' in /etc/cups/cupsd.conf and I found this
portion surrounding the error message in /var/log/cups/error_log:

d [29/May/2013:11:59:33 -0400] cupsdAddPrinter(dellcolor)
d [29/May/2013:11:59:33 -0400] cupsdAddPrinter: Adding dellcolor to Printers
I [29/May/2013:11:59:33 -0400] Setting dellcolor device-uri to
socket://prism.physics.wm.edu:9100 (was file:///dev/null.)
d [29/May/2013:11:59:33 -0400] set_printer_defaults: printer-info
d [29/May/2013:11:59:33 -0400] set_printer_defaults: printer-location
d [29/May/2013:11:59:33 -0400] set_printer_defaults: device-uri
d [29/May/2013:11:59:33 -0400] copy_file(/var/spool/cups/0001,
/etc/cups/interfaces/dellcolor)
D [29/May/2013:11:59:33 -0400] CUPS-Add-Modify-Printer server-error-internal-
error: Unable to copy interface script - No such file or directory
E [29/May/2013:11:59:33 -0400] Returning IPP server-error-internal-error for
CUPS-Add-Modify-Printer (ipp://localhost/printers/dellcolor) from localhost
d [29/May/2013:11:59:33 -0400] cupsdProcessIPPRequest: ippLength(response)=153

I checked that in my installation (which is debian 7 amd64, xfce desktop,
installed from LiveCD), there is no subdir /etc/cups/interfaces . I made that
subdirectory manually, and the printer setup process continues. But in the end
I saw a blank /etc/cups/interfaces/dellcolor, while I saw no
/etc/cups/interfaces/dellcolor.ppd . This is strange!

I am reporting this bug per chance someone can help out and fix this problem.

Thanks,
Wirawan



-- System Information:
Debian Release: 7.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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 cups depends on:
ii  adduser3.113+nmu3
ii  bc 1.06.95-2+b1
ii  cups-client1.5.3-5
ii  cups-common1.5.3-5
ii  cups-filters   1.0.18-2.1
ii  cups-ppdc  1.5.3-5
ii  debconf [debconf-2.0]  1.5.49
ii  dpkg   1.16.10
ii  ghostscript9.05~dfsg-6.3
ii  libavahi-client3   0.6.31-2
ii  libavahi-common3   0.6.31-2
ii  libc-bin   2.13-38
ii  libc6  2.13-38
ii  libcups2   1.5.3-5
ii  libcupscgi11.5.3-5
ii  libcupsimage2  1.5.3-5
ii  libcupsmime1   1.5.3-5
ii  libcupsppdc1   1.5.3-5
ii  libdbus-1-31.6.8-1
ii  libgcc11:4.7.2-5
ii  libgnutls262.12.20-6
ii  libgssapi-krb5-2   1.10.1+dfsg-5
ii  libkrb5-3  1.10.1+dfsg-5
ii  libldap-2.4-2  2.4.31-1+nmu2
ii  libpam0g   1.1.3-7.1
ii  libpaper1  1.1.24+nmu2
ii  libslp11.2.1-9
ii  libstdc++6 4.7.2-5
ii  libusb-1.0-0   2:1.0.11-1
ii  lsb-base   4.1+Debian8
ii  poppler-utils  0.18.4-6
ii  procps 1:3.3.3-3
ii  ssl-cert   1.0.32

Versions of packages cups recommends:
ii  avahi-daemon   0.6.31-2
pn  colord none
ii  foomatic-filters   4.0.17-1
ii  ghostscript-cups   9.05~dfsg-6.3
ii  printer-driver-gutenprint  5.2.9-1

Versions of packages cups suggests:
ii  cups-bsd   1.5.3-5
pn  cups-pdf   none
ii  foomatic-db-compressed-ppds [foomatic-db]  20120523-1
ii  hplip  3.12.6-3.1
ii  printer-driver-hpcups  3.12.6-3.1
ii  smbclient  2:3.6.6-6
ii  udev   175-7.2

-- debconf information:
  cupsys/raw-print: true
  cupsys/backend: ipp, lpd, socket, usb, snmp, dnssd


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#710297: cups: server-error-internal-error encountered when setting up new printer (Dell 5130cdn color laser)

2013-05-29 Thread Wirawan Purwanto
One more thing I found: the dellcolor printer was shown as Local
System V Printer as the Model. This is not correct. This is why the
ppd does not exist.

Upon inspecting the source code of cups (using apt-get source cups
to download), I found a probable explanation. See file
cups-1.5.3/scheduler/ipp.c  , subroutine add_printer , where it
detects the file type (whether it is a PPD file or an interface
script file). This means that either:

1) the compressed PPD file (Dell_C3760dn_Color_Laser.ppd.gz) was not
read in properly. If this is the case, then the PPD is not
decompressed before being passed to add_printer function call.

2) something was erroneous in uncompressing the .ppd.gz file, because
I discovered that the final copied file
(/etc/cups/interfaces/dellcolor) is empty.

I would lean toward hypothesis 2. If anyone I can do to help hunt the
problem, let me know.

Wirawan


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#710297: Wrong title

2013-05-29 Thread Wirawan Purwanto
Sorry, the title of the bug report should have read:

 cups: server-error-internal-error encountered when setting up new
printer (Dell C3760dn color laser)

Not critical, but I just want to correct it.
-- 
Wirawan


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#668470: [Pkg-alsa-devel] Bug#668470: alsa-base: Intel Corporation 82801I (ICH9 Family) HD Audio microphone not working (squeeze stable)

2012-04-25 Thread Wirawan Purwanto
Here it is:

Simple mixer control 'Master',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
  Playback channels: Mono
  Limits: Playback 0 - 74
  Mono: Playback 58 [78%] [-16.00dB] [on]
Simple mixer control 'Headphone',0
  Capabilities: pvolume pswitch penum
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 74
  Mono:
  Front Left: Playback 74 [100%] [0.00dB] [on]
  Front Right: Playback 74 [100%] [0.00dB] [on]
Simple mixer control 'Speaker',0
  Capabilities: pvolume pswitch penum
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 74
  Mono:
  Front Left: Playback 74 [100%] [0.00dB] [on]
  Front Right: Playback 74 [100%] [0.00dB] [on]
Simple mixer control 'PCM',0
  Capabilities: pvolume penum
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 255
  Mono:
  Front Left: Playback 234 [92%] [-4.20dB]
  Front Right: Playback 234 [92%] [-4.20dB]
Simple mixer control 'Mic',0
  Capabilities: cvolume penum
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 80
  Front Left: Capture 63 [79%] [-11.00dB]
  Front Right: Capture 63 [79%] [-11.00dB]
Simple mixer control 'Mic Boost',0
  Capabilities: volume penum
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 4
  Front Left: 2 [50%] [20.00dB]
  Front Right: 2 [50%] [20.00dB]
Simple mixer control 'Beep',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
  Playback channels: Mono
  Limits: Playback 0 - 3
  Mono: Playback 0 [0%] [-18.00dB] [on]
Simple mixer control 'Auto-Mute Mode',0
  Capabilities: enum
  Items: 'Disabled' 'Enabled'
  Item0: 'Enabled'
Simple mixer control 'Digital',0
  Capabilities: cvolume penum
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 120
  Front Left: Capture 23 [19%] [-18.50dB]
  Front Right: Capture 23 [19%] [-18.50dB]
Simple mixer control 'Dock Mic',0
  Capabilities: cvolume penum
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 80
  Front Left: Capture 74 [92%] [0.00dB]
  Front Right: Capture 74 [92%] [0.00dB]
Simple mixer control 'Dock Mic Boost',0
  Capabilities: volume penum
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 4
  Front Left: 0 [0%] [0.00dB]
  Front Right: 0 [0%] [0.00dB]
Simple mixer control 'Internal Mic',0
  Capabilities: cvolume penum
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 80
  Front Left: Capture 72 [90%] [-2.00dB]
  Front Right: Capture 72 [90%] [-2.00dB]
Simple mixer control 'Internal Mic Boost',0
  Capabilities: volume penum
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 4
  Front Left: 2 [50%] [24.00dB]
  Front Right: 2 [50%] [24.00dB]


Wirawan

On Sat, Apr 14, 2012 at 2:38 AM, Elimar Riesebieter riese...@lxtec.de wrote:

 * Wirawan Purwanto wiraw...@gmail.com [2012-04-11 23:51 -0400]:

  Package: alsa-base
  Version: 1.0.23+dfsg-2
  Severity: normal
 
 
  Ever since I installed Debian squeeze on my laptop (Thinkpad T400) the
  internal microphone did not work.
  I tried to tweak the volume settings via alsamixer, no sound coming out.

 Please post the output of
 $ amixer

 Elimar

 --
   the keyboard of life you have always
  to keep a finger at the escape key;-)




--
Wirawan Purwanto
Research Scientist
College of William and Mary
Physics Department
Williamsburg, VA 23187



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#704090: Wheezy RC1 (x86_64) failed to detect disks on computer with fake RAID1 disks

2013-03-27 Thread Wirawan Purwanto
Package: mdadm-udeb
Version: 3.2.5-3

I am trying to install Debian Wheezy RC1 (x86_64 architecture) on a
desktop PC that has a fake RAID1 disks (2 disks, each 1 TB) and it
failed to detect the disks. I am using email to report this bug and
don't know for sure which package to report it against, so I am
starting with mdadm that is in the installer itself. The PC itself has
quad-core Intel Core i7-3770 3.4 GHz CPU (if that matters).

When I arrive at the Detect disks stage, the installer reported back
saying that there was no disk detected. This is not correct, since I
can see the disks in /proc/partition. Moreover, the syslog shows that
the raid was actually detected:

Mar 27 17:56:39 md-devices: mdadm: Container /dev/md/imsm0 has been
assembled with 2 drives
Mar 27 17:56:39 kernel: [  559.191806] md: md127 stopped.
Mar 27 17:56:39 kernel: [  559.192733] md: bindsda
Mar 27 17:56:39 kernel: [  559.192811] md: bindsdb
Mar 27 17:56:40 md-devices: mdadm: Started /dev/md/Volume0 with 2 devices
Mar 27 17:56:40 kernel: [  559.426254] md: md126 stopped.
Mar 27 17:56:40 kernel: [  559.426338] md: bindsdb
Mar 27 17:56:40 kernel: [  559.426385] md: bindsda
Mar 27 17:56:40 kernel: [  559.427207] md: raid1 personality
registered for level 1
Mar 27 17:56:40 kernel: [  559.427349] bio: create slab bio-1 at 1
Mar 27 17:56:40 kernel: [  559.427413] md/raid1:md126: active with 2
out of 2 mirrors
Mar 27 17:56:40 kernel: [  559.427426] md126: detected capacity change
from 0 to 1000202043392
Mar 27 17:56:40 kernel: [  559.428003]  md126: p1 p2
Mar 27 17:56:40 kernel: [  559.718222] device-mapper: uevent: version 1.0.3
Mar 27 17:56:40 kernel: [  559.718274] device-mapper: ioctl:
4.22.0-ioctl (2011-10-19) initialised: dm-de...@redhat.com

When I inspected the syslog after the failure to detect disks, I found
kernel error reports, all happening at this location:

kernel BUG at 
/build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/drivers/md/md.c:6936!
invalid opcode:  [#15] SMP
CPU 0
Modules linked in: efivars dm_mod raid1 md_mod xfs jfs ext4 crc16 jbd2
ext3 jbd btrfs crc32c libcrc32c zlib_deflate ext2 mbcache r8169 mii
nls_cp437 vfat fat nls_utf8 isofs usb_storage usbhid hid sg sr_mod
sd_mod

Please see the attached syslog for more details. The PCI devices on this PC are:

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core
processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core
processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200
v2/3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset
Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210
Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset
Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset
Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset
Family PCI Express Root Port 1 (rev c4)
00:1c.4 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset
Family PCI Express Root Port 5 (rev c4)
00:1c.5 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset
Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation H77 Express Chipset LPC
Controller (rev 04)
00:1f.2 RAID bus controller: Intel Corporation 82801 SATA Controller
[RAID mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family
SMBus Controller (rev 04)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 09)
04:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI
Bridge (rev 03)

Device 00:1f.2 is the fake RAID controller.
--
Wirawan Purwanto
Research Scientist
College of William and Mary
Physics Department
Williamsburg, VA 23187


syslog.bz2
Description: BZip2 compressed data


Bug#728812: lesstif2: xmgrace with LessTif still crashes when Esc key is pressed on a LOCAL menu

2013-11-05 Thread Wirawan Purwanto
Package: lesstif2
Version: 1:0.95.2-1.1
Severity: important

Dear Maintainer,

Xmgrace still crashes when I press Esc on a local menu.
This bug must be related to old bug #356017, which is basically lesstif2's
bug, not xmgrace itself.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=356017


System: Debian 7 (Wheezy stable) on x86-64 laptop.

Package versions from dpkg -l:

||/ Name Version ArchitectureDescription
+++--===-===-=
ii  lesstif2:amd64   1:0.95.2-1.1amd64   OSF/Motif 2.1
implementation released under LGPL
ii  grace1:5.1.22-13 amd64   XY graphing and plotting
tool


How to reproduce the bug?
-

 * Open up xmgrace from terminal (to ease the debugging).
 * On the empty plot, double click--the Set Appearance dialog box will
   appear.
 * On the box captioned Select set:, right-click the mouse; a local menu
   will appear.
 * Press Esc here, it will NOT crash.

 * Now create a new dataset:
   - On the empty plot, double click--the Set Appearance dialog box will
 appear.
   - On the box captioned Select set:, right-click the mouse; a local menu
 will appear.
   - Click Create New - In Spreadsheet
   - Put in a few data points and click Accept

   For your convenience I attached a sample that has one dataset
   (sample-crash.agr)--it will cause the crash when the action in the
   next point is invoked::

 * Now right click again on the box captioned Select set:, then press Esc
   key.

The error message will appear on the terminal console:

Oops! Got SIGSYS

Please use Help/Comments to report the bug.
NB. This version of Grace was compiled with LessTif.
Make sure to read the FAQ carefully prior to
reporting the bug, ESPECIALLY is the problem might
be related to the graphical interface.
Aborted (core dumped)

On my system the gdb traceback is like this:

(gdb) where
#0  0x7f5d89a8b475 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f5d89a8e6f0 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x004173f6 in ?? ()
#3  signal handler called
#4  0x7f5d8b8d7604 in _XmMenuEscape () from /usr/lib/x86_64-linux-
gnu/libXm.so.2
#5  0x7f5d8b3e348d in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
#6  0x7f5d8b3e38e1 in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
#7  0x7f5d8b3e467d in _XtTranslateEvent () from /usr/lib/x86_64-linux-
gnu/libXt.so.6
#8  0x7f5d8b3bcb1b in XtDispatchEventToWidget () from /usr/lib/x86_64
-linux-gnu/libXt.so.6
#9  0x7f5d8b3bd26e in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
#10 0x7f5d8b3bd334 in XtDispatchEvent () from /usr/lib/x86_64-linux-
gnu/libXt.so.6
#11 0x7f5d8b3c9049 in XtAppProcessEvent () from /usr/lib/x86_64-linux-
gnu/libXt.so.6
#12 0x7f5d8b3bd7ad in XtAppMainLoop () from /usr/lib/x86_64-linux-
gnu/libXt.so.6
#13 0x0048c279 in ?? ()
#14 0x0040a905 in ?? ()
#15 0x7f5d89a77ead in __libc_start_main () from /lib/x86_64-linux-
gnu/libc.so.6
#16 0x0040bc05 in ?? ()
#17 0x7fffb49de6d8 in ?? ()
#18 0x001c in ?? ()
#19 0x0002 in ?? ()
#20 0x7fffb49df3a4 in ?? ()
#21 0x7fffb49df3ac in ?? ()
#22 0x in ?? ()
(gdb)

and the location of crash in _XmMenuEscape is very much like what I
reported in

https://bugs.launchpad.net/ubuntu/+source/lesstif2/+bug/124573 ,

which corresponds to Debian bug #356017:

(gdb) disas 0x7f5d8b8d7604
...
---Type return to continue, or q return to quit---
   0x7f5d8b8d75da +746:   nopw   0x0(%rax,%rax,1)
   0x7f5d8b8d75e0 +752:   movzbl 0x1d9(%rbp),%eax
   0x7f5d8b8d75e7 +759:   jmp0x7f5d8b8d75a8
_XmMenuEscape+696
   0x7f5d8b8d75e9 +761:   nopl   0x0(%rax)
   0x7f5d8b8d75f0 +768:   mov0x148(%rbp),%rsi
   0x7f5d8b8d75f7 +775:   lea0xf(%rsp),%rcx
   0x7f5d8b8d75fc +780:   mov%rbx,%rdx
   0x7f5d8b8d75ff +783:   mov$0xd,%edi
   0x7f5d8b8d7604 +788:   mov0x10(%rsi),%rax
 LOCATION OF CRASH
   0x7f5d8b8d7608 +792:   mov0x8(%rax),%r8
   0x7f5d8b8d760c +796:   xor%eax,%eax
   0x7f5d8b8d760e +798:   callq  *0x170(%r8)
   0x7f5d8b8d7615 +805:   jmpq   0x7f5d8b8d73af
_XmMenuEscape+191
   0x7f5d8b8d761a +810:   mov0x10(%rbp),%rsi
   0x7f5d8b8d761e +814:   jmpq   0x7f5d8b8d7524
_XmMenuEscape+564




-- System Information:
Debian Release: 7.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (50, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-0.bpo.2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, 

Bug#728812: lesstif2: xmgrace with LessTif still crashes when Esc key is pressed on a LOCAL menu

2013-12-06 Thread Wirawan Purwanto
Hi Paul,

Sorry it took me long to get to this issue. I just tested the newer grace
on testing repository of Debian, here's the result:

(1) no more crash as we press Esc -- but see point (3) below

From this testing I found that there are some notable differences between
motif and lesstif2 from user's experience:

(2) When we press a menu shortcut key from main window (say, Alt+F), then
pressing down arrow will NOT bring the highlight to one item below the
current; rather it simply closes the menu. This is surprising.

(3) In the Set Appearance window, when I right-click the mouse on the
dataset list, as soon as the mouse button is released, the local context
menu disappears! Of course, I don't have a chance to press Esc!

Are these intended behavior of the original libmotif? So it appears that
these may introduce surprise to those who are used to xmgrace built against
lesstif2.


Note:
My testing system (run under KVM) is using Debian Wheezy amd64 as the base
installation, then I simply added testing repo and use `apt-get -t testing
install grace' to upgrade to the newer grace that uses libmotif.




On Tue, Nov 5, 2013 at 2:35 PM, Paul Gevers elb...@debian.org wrote:

 Hi Wirawan,

 Thanks for taking the time to report issues.

 On 05-11-13 20:07, Wirawan Purwanto wrote:
  Xmgrace still crashes when I press Esc on a local menu.
  This bug must be related to old bug #356017, which is basically
 lesstif2's
  bug, not xmgrace itself.

 Well, the good news is: we are getting rid of lesstif2 in Debian, so in
 the next release it should be gone. grace is already build against
 libmotif. Would you be in the position to test a newer xmgrace from
 testing (or from Ubuntu Trusty 13.10 as you seem to have been Ubuntu as
 well).

 Paul





-- 
Wirawan Purwanto
Research Scientist
College of William and Mary
Physics Department
Williamsburg, VA 23187


Bug#711658: wildmidi: Wildmidi segfaults when running with reverb (-b option)

2013-06-08 Thread Wirawan Purwanto
Package: wildmidi
Version: 0.2.3.4-2.1
Severity: normal

Dear Maintainer,

I found that wildmidi in my system (x86-64, debian 7 stable) segfaulted when
playing the attached MIDI file with reverb (command-line -b).

(gdb) run -b e0460.mid
Starting program: /usr/bin/wildmidi -b e0460.mid
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.

WildMidi 0.2.3.4 Open Source Midi Sequencer
Copyright (C) Chris Ison 2001-2010 wildc...@users.sourceforge.net

WildMidi comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under the terms and conditions of the GNU General Public License version 3.
For more information see COPYING

Report bugs to http://sourceforge.net/tracker/?group_id=42635atid=433744
WildMIDI homepage at http://wildmidi.sourceforge.net

Initializing Sound System
Initializing WildMidi Processing Library 0.2.3.4

 +  Volume upe  Better resamplingn  Next Midi
 -  Volume down  l  Log volume   q  Quit
 ,  1sec Seek Back   r  Reverb   .  1sec Seek Forward
 p  Pause On/Off

Playing e0460.mid

Program received signal SIGSEGV, Segmentation fault.
0x778c8466 in ?? () from /usr/lib/x86_64-linux-gnu/libWildMidi.so.1
(gdb) where
#0  0x778c8466 in ?? () from /usr/lib/x86_64-linux-gnu/libWildMidi.so.1
#1  0x778d93bd in WildMidi_GetOutput () from /usr/lib/x86_64-linux-
gnu/libWildMidi.so.1
#2  0x004023a1 in ?? ()
#3  0x77558ead in __libc_start_main () from /lib/x86_64-linux-
gnu/libc.so.6
#4  0x00402a2d in ?? ()
#5  0x7fffe228 in ?? ()
#6  0x001c in ?? ()
#7  0x0003 in ?? ()
#8  0x7fffe552 in ?? ()
#9  0x7fffe564 in ?? ()
#10 0x7fffe567 in ?? ()
#11 0x in ?? ()
(gdb) quit

I am using xfce4 desktop, ALSA sound (no pulseaudio).

The same crash happens if we play without -b, then press r to enable reverb
while playing the song. This crash does not happen with other files (see
e0001.mid attached later).

Wirawan



-- System Information:
Debian Release: 7.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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 wildmidi depends on:
ii  libasound21.0.25-4
ii  libc6 2.13-38
ii  libwildmidi1  0.2.3.4-2.1

wildmidi recommends no packages.

wildmidi suggests no packages.

-- no debconf information


e0460.mid
Description: MIDI audio


e0001.mid
Description: MIDI audio


Bug#734623: iceweasel: Iceweasel CPU utilization goes 100% upon resuming laptop from sleep

2014-01-08 Thread Wirawan Purwanto
Package: iceweasel
Version: 24.2.0esr-1~bpo70+1
Severity: normal

Dear Maintainer,

I found that the 24esr version of iceweasel (linux debian 7.3 stable, x86-64
laptop, dual-core Intel Core2 duo) often causes 100% CPU utilization upon
resuming from sleep. I don't know which tab causes this though. I have a
suspicion that perhaps gmail is the cause (since I always have that open), but
I am not sure.

I have noticed that this issue also exists on the mainline version of firefox
(specifically, aurora branch up to version 27; perhaps v 28 also have it but
I don't know that for sure).

This is what typically happens:

- I close the laptop and it goes to sleep-to-RAM
- upon resuming, I notice the CPU being hot--and iceweasel uses 100% CPU. Also,
xorg uses about 50% CPU
- I tried to close tabs one by one, it did not cause the CPU usage to decrease
- nevertheless, iceweasel is still fully responding and functioning (but
somewhat slow, of course)
- I tried to close the program, the iceweasel GUI window(s) was closed, but at
the same time, the CPU utilization goes  100% (i.e. all two cores were
occupied by iceweasel), often to ~200%.
- The only resort is to kill the process using kill command and restart
iceweasel.

- Comment: The last time I noticed this problem, the laptop was plugged on AC
before sleep, and was on battery upon resuming. Also I woke the laptop up in a
different building (thus, different wi-fi SSID).

Too bad that firefox/iceweasel does not have tab process viewer, akin to
“ps” that can show CPU utilization per thread. I imagine this is not too
hard to do for one who knows the code well.

This is a very annoying problem that I have noticed for many months. I decide
to report this, in case someone can help pinpoint the issue. I have not
restarted afresh with a blank profile (I have too much information deposited on
my current profile.)


Wirawan



-- Package-specific info:

-- Extensions information
Name: Default theme
Location: 
/usr/lib/iceweasel/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled

Name: DuckDuckGo Plus
Location: ${PROFILE_EXTENSIONS}/jid1-zadieub7xoz...@jetpack.xpi
Status: user-disabled

Name: Flashblock
Location: ${PROFILE_EXTENSIONS}/{3d7eb24f-2740-49df-8937-200b1cc08f8a}
Status: enabled

Name: Font Information
Location: ${PROFILE_EXTENSIONS}/{70ded480-0a45-4099-84d1-65aa1cb1575e}.xpi
Status: enabled

Name: NoSquint
Location: ${PROFILE_EXTENSIONS}/nosqu...@urandom.ca.xpi
Status: enabled

Name: Test Pilot
Location: ${PROFILE_EXTENSIONS}/testpi...@labs.mozilla.com.xpi
Status: enabled

Name: Troubleshooter
Location: ${PROFILE_EXTENSIONS}/troubleshoo...@mozilla.org.xpi
Status: enabled

-- Plugins information
Name: Shockwave Flash (11,2,202,327)
Location: /home/wirawan/.local/flashplayer/11.2.r202.327/lib/libflashplayer.so
Status: enabled


-- Addons package information
ii  iceweasel  24.2.0esr-1~ amd64Web browser based on Firefox

-- System Information:
Debian Release: 7.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (50, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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 iceweasel depends on:
ii  debianutils 4.3.2
ii  fontconfig  2.9.0-7.1
ii  libc6   2.13-38
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-02.33.12+really2.32.4-5
ii  libgtk2.0-0 2.24.10-2
ii  libsqlite3-03.7.13-1+deb7u1
ii  libstdc++6  4.7.2-5
ii  procps  1:3.3.3-3
ii  xulrunner-24.0  24.2.0esr-1~bpo70+1

iceweasel recommends no packages.

Versions of packages iceweasel suggests:
pn  fonts-mathjax  none
ii  fonts-oflb-asana-math  000.907-4
ii  fonts-stix [otf-stix]  1.1.0-1
ii  libgssapi-krb5-2   1.10.1+dfsg-5+deb7u1
pn  mozplugger none

Versions of packages xulrunner-24.0 depends on:
ii  libasound21.0.25-4
ii  libatk1.0-0   2.4.0-2
ii  libbz2-1.01.0.6-4
ii  libc6 2.13-38
ii  libcairo2 1.12.2-3
ii  libdbus-1-3   1.6.8-1+deb7u1
ii  libdbus-glib-1-2  0.100.2-1
ii  libevent-2.0-52.0.19-stable-3
ii  libfontconfig12.9.0-7.1
ii  libfreetype6  2.4.9-1.1
ii  libgcc1   1:4.7.2-5
ii  libgdk-pixbuf2.0-02.26.1-1
ii  libglib2.0-0  2.33.12+really2.32.4-5
ii  libgtk2.0-0   2.24.10-2
ii  libhunspell-1.3-0 1.3.2-4
ii  libmozjs24d   24.2.0esr-1~bpo70+1
ii  libpango1.0-0 1.30.0-1
ii  libstartup-notification0  0.12-1
ii  libstdc++64.7.2-5
ii  libvpx1   1.1.0-1
ii  libx11-6  2:1.5.0-1+deb7u1
ii  libxext6  2:1.3.1-2+deb7u1
ii  libxrender1   1:0.9.7-1+deb7u1
ii  libxt6 

Bug#704865:

2015-04-21 Thread Wirawan Purwanto
This error seems to affect many other people and in different
settings, although most are screensaver-related, but the root cause
may not be the screensaver itself:

https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706

On my computer, running Linux Mint 17 based on Ubuntu 14.04, the
cinnamon screensaver was affected. It came up with this error shown on
syslog:

cinnamon-screensaver-dialog: pam_ecryptfs: seteuid error

This was 15 seconds after the last event recorded on the syslog
(issued by NetworkManager, wpa_supplicant, and anacron).

Wirawan


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#793305: openssh-client: Sensitivity to extra whitespace characters in known_hosts file

2015-07-22 Thread Wirawan Purwanto
Package: openssh-client
Version: 1:6.7p1-5
Severity: normal

Dear Maintainer,

The openssh client included with Debian 8 is overly sensitive to the
extra intervening whitespace characters between the key type and the
value in the known_hosts file.
To me, this is a known problem for *this* version of openssh.
An older version (6.1p1, release 11.fc18, included with Fedora Core
18) did not have this problem.
The version that comes with Debian 7 (1:6.0p1-4+deb7u2) did not have
this issue as well.

For example, consider this entry in ~/.ssh/known_hosts:

192.168.0.120 ecdsa-sha2-nistp256 E2Vj...=

Here, 192.168.0.120 is the IP address or hostname (doesn't matter; the
failure does not pertain that).
The ecdsa-sha2-nistp256 is the type of the host public key, and
E2Vj...= represents the value of the key.
That entry works fine.
If I add an extra whitespace between the IP address and the key type,
it still works fine:

192.168.0.120  ecdsa-sha2-nistp256 E2Vj...=

But if I add the extra whitespace after the word
ecdsa-sha2-nistp256, then the host key matching fails.

192.168.0.120 ecdsa-sha2-nistp256  E2Vj...=

The 'ssh -vvv 192.168.0.120' will print, among others,

debug3: load_hostkeys: loading entries for host 192.168.0.120
from file /home/user/.ssh/known_hosts
debug3: load_hostkeys: loaded 0 keys

So it failed to load the key for some reason.


This is an unwanted behavior, as I tend to keep ~/.ssh/known_hosts in
a column-aligned fashion, which means I introduce extra whitespaces
everywhere between items.

A cursory look into the source code tracks the possible error here
(in file:function format):
- hostfile.c:hostfile_read_key
- key.c:key_read
- sshkey.c:sshkey_read

It looks like the bug is in the last function.


Thanks,
Wirawan

-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openssh-client depends on:
ii  adduser   3.113+nmu3
ii  dpkg  1.17.25
ii  libc6 2.19-18
ii  libedit2  3.1-20140620-2
ii  libgssapi-krb5-2  1.12.1+dfsg-19
ii  libselinux1   2.3-2
ii  libssl1.0.0   1.0.1k-3+deb8u1
ii  passwd1:4.2-3
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages openssh-client recommends:
ii  xauth  1:1.0.9-1

Versions of packages openssh-client suggests:
pn  keychain  none
pn  libpam-sshnone
pn  monkeysphere  none
pn  ssh-askpass   none

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#793065: evince-gtk: SIGSEGV upon viewing a particular postscript file

2015-07-20 Thread Wirawan Purwanto
 Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages evince-gtk depends on:
ii  evince-common  3.14.1-2
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-18
ii  libcairo-gobject2  1.14.0-2.1
ii  libcairo2  1.14.0-2.1
ii  libevdocument3-4   3.14.1-2
ii  libevview3-3   3.14.1-2
ii  libgdk-pixbuf2.0-0 2.31.1-2+b1
ii  libglib2.0-0   2.42.1-1
ii  libgtk-3-0 3.14.5-1
ii  libpango-1.0-0 1.36.8-3
ii  libpangocairo-1.0-01.36.8-3
ii  libxml22.9.1+dfsg1-5
ii  shared-mime-info   1.3-1
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages evince-gtk recommends:
ii  dbus-x11  1.8.18-0+deb8u1

Versions of packages evince-gtk suggests:
ii  gvfs  1.22.2-1
pn  nautilus  none
ii  poppler-data  0.4.7-1
pn  unrar none

-- no debconf information


-- 
Wirawan Purwanto
Research Scientist
College of William and Mary
Physics Department
Williamsburg, VA 23187


fitting.ps
Description: PostScript document


Bug#793066: ddclient: Missing support for freedns protocol in interactive configuration tool

2015-07-20 Thread Wirawan Purwanto
Package: ddclient
Version: 3.8.2-2
Severity: normal

Dear Maintainer,

I installed ddclient with the intention of using freedns service,
following this web page:

http://freedns.afraid.org/scripts/freedns.clients.php

I found that the perl configuration script that comes with ddclient
Debian package does not support freedns protocol.
The ddclient script itself supports it, so I ended up having to
manually set up the configuration file (/etc/ddclient.conf).
This missing feature should be added to the configuration script.
Looking at sample config found in

/usr/share/doc/ddclient/examples/sample-etc_ddclient.conf.gz ,

there are other protocols too that should be added
to the current config script such as: hammernode1, dnspark, namecheap.

Wirawan

-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ddclient depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  initscripts2.88dsf-59
ii  lsb-base   4.1+Debian13+nmu1
ii  perl [perl5]   5.20.2-3+deb8u1

Versions of packages ddclient recommends:
ii  libio-socket-ssl-perl  2.002-2

ddclient suggests no packages.

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#851067: Screenshots and sample documents

2017-02-22 Thread Wirawan Purwanto
Nobody responded to this thread yet? Surprised that nobody else get
affected by this bug, given the prevalence of Intel graphics hardware out
there?

Update: I managed to test Debian testing (Stretch RC2) with the Intel
graphics. Here are the relevant versions:

* kernel version 4.9 (package: linux-image-4.9.0-1-amd64, version: 4.9.6-3).
* Intel DDX (package: xserver-xorg-video-intel, version:
2:2.99.917+git20161206-1)
* Xserver ( xserver-xorg  ver 1:7.7+18 ;  xserver-xorg-core ver 2:1.19.0-3 )
* libdrm2 version 2.4.74-1
* libreoffice version 1:5.2.4-2

All packages provided by debian testing.

Turns out the screen corruptions above was still there too! I was able to
reproduce the "spreadsheet cell update" problem (see previous posting in
the bug report). Now, that alone is an annoying problem.

Given that the modesetting has its own issues, how can we get the Intel ddx
problem solved? See here for modesetting issue:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835123

Wirawan


Bug#835123: xserver-xorg-video-modesetting: Keyboard events become extremely unresponsive after certain X events

2016-08-22 Thread Wirawan Purwanto
nput/mouse0
E: DEVPATH=/devices/platform/i8042/serio1/input/input2/mouse0
E: ID_INPUT=1
E: ID_INPUT_TOUCHPAD=1
E: ID_PATH=platform-i8042-serio-1
E: ID_PATH_TAG=platform-i8042-serio-1
E: ID_SERIAL=noserial
E: MAJOR=13
E: MINOR=32
E: SUBSYSTEM=input
E: USEC_INITIALIZED=42272

P: /devices/platform/pcspkr/input/input10
E: DEVPATH=/devices/platform/pcspkr/input/input10
E: EV=40001
E: ID_FOR_SEAT=input-platform-pcspkr
E: ID_INPUT=1
E: ID_PATH=platform-pcspkr
E: ID_PATH_TAG=platform-pcspkr
E: ID_SERIAL=noserial
E: MODALIAS=input:b0010v001Fp0001e0100-e0,12,kramls1,2,fw
E: NAME="PC Speaker"
E: PHYS="isa0061/input0"
E: PRODUCT=10/1f/1/100
E: PROP=0
E: SND=6
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=33643

P: /devices/platform/pcspkr/input/input10/event7
N: input/event7
S: input/by-path/platform-pcspkr-event-spkr
E: DEVLINKS=/dev/input/by-path/platform-pcspkr-event-spkr
E: DEVNAME=/dev/input/event7
E: DEVPATH=/devices/platform/pcspkr/input/input10/event7
E: ID_INPUT=1
E: ID_PATH=platform-pcspkr
E: ID_PATH_TAG=platform-pcspkr
E: ID_SERIAL=noserial
E: MAJOR=13
E: MINOR=71
E: SUBSYSTEM=input
E: USEC_INITIALIZED=41871

P: /devices/platform/thinkpad_acpi/input/input7
E: DEVPATH=/devices/platform/thinkpad_acpi/input/input7
E: EV=33
E: ID_FOR_SEAT=input-platform-thinkpad_acpi
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=platform-thinkpad_acpi
E: ID_PATH_TAG=platform-thinkpad_acpi
E: KEY=10040 0 1804 0 10 0 1501b02102004
c000280041114000 10e 0
E: 
MODALIAS=input:b0019v17AAp5054e4101-e0,1,4,5,k71,72,73,78,8E,90,94,98,9E,AB,AD,BE,BF,C2,CD,D4,D9,E0,E1,E3,E4,EC,EE,F0,174,1D2,1DB,1DC,246,250,ram4,lsfw3,
E: MSC=10
E: NAME="ThinkPad Extra Buttons"
E: PHYS="thinkpad_acpi/input0"
E: PRODUCT=19/17aa/5054/4101
E: PROP=0
E: SUBSYSTEM=input
E: SW=8
E: TAGS=:seat:
E: USEC_INITIALIZED=21875

P: /devices/platform/thinkpad_acpi/input/input7/event5
N: input/event5
S: input/by-path/platform-thinkpad_acpi-event
E: BACKSPACE=guess
E: DEVLINKS=/dev/input/by-path/platform-thinkpad_acpi-event
E: DEVNAME=/dev/input/event5
E: DEVPATH=/devices/platform/thinkpad_acpi/input/input7/event5
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=platform-thinkpad_acpi
E: ID_PATH_TAG=platform-thinkpad_acpi
E: KEYBOARD_KEY_01=screenlock
E: KEYBOARD_KEY_02=battery
E: KEYBOARD_KEY_03=sleep
E: KEYBOARD_KEY_04=wlan
E: KEYBOARD_KEY_06=switchvideomode
E: KEYBOARD_KEY_07=f21
E: KEYBOARD_KEY_08=f24
E: KEYBOARD_KEY_0b=suspend
E: KEYBOARD_KEY_0f=brightnessup
E: KEYBOARD_KEY_10=brightnessdown
E: KEYBOARD_KEY_11=kbdillumtoggle
E: KEYBOARD_KEY_13=zoom
E: KEYBOARD_KEY_14=volumeup
E: KEYBOARD_KEY_15=volumedown
E: KEYBOARD_KEY_16=mute
E: KEYBOARD_KEY_17=prog1
E: KEYBOARD_KEY_1a=f20
E: MAJOR=13
E: MINOR=69
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=41247
E: XKBLAYOUT=us
E: XKBMODEL=pc105


DRM Information from dmesg:
---
[62425.631780] [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun


-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xserver-xorg-video-modesetting depends on:
ii  libc6  2.19-18+deb8u4
ii  libdrm22.4.58-2
ii  libudev1   215-17+deb8u4
ii  xserver-xorg-core [xorg-video-abi-18]  2:1.16.4-1

xserver-xorg-video-modesetting recommends no packages.

xserver-xorg-video-modesetting suggests no packages.

-- no debconf information


-- 
Wirawan Purwanto
Computational Scientist, HPC Group
Information Technology Services
Old Dominion University
Norfolk, VA 23529



Bug#851067: linux-image-4.8.0-0.bpo.2-amd64: X display corruptions with kernels 4.4 - 4.8 (Broadwell Intel graphics, Intel driver)

2017-01-11 Thread Wirawan Purwanto
Package: src:linux
Version: 4.8.11-1~bpo8+1
Severity: important

Dear Maintainer,


Screen corruption was randomly (but consistently) observed on several
programs: LibreOffice 5, xpdf, iSilo under wine.
I do not know which precise piece of the software stack is causing this
error, but I want to start from the kernel-level driver, since I noticed
the problem for the first time when I upgraded my kernel version
from 4.3 to 4.6.
The problem was observed also on the newer kernel releases (4.7, 4.8).
And I tested today, and found that some of the problems also appeared
using the old kernel 4.3.

This is a problem that I began to observe since July 2016, when I upgraded
the backport kernel in my computer to version 4.6 onward, and the
xserver-xorg-video-intel driver to version 2.99.917+git20160522-1~bpo8+1 .

Some of these problems happen consistently; the others happen somewhat
intermittently, but frequently enough to be annoying.

This problem happens on the following hardware platform:

* Lenovo Thinkpad T450s

* CPU: Intel i5-5200U (Broadwell)

* OS: Debian 8 (Jessie) 64-bit

* Kernel versions affected: 4.3, 4.6, 4.7, 4.8  as provided by
  "jessie-backports" repository

* Xorg driver: intel with "sna" acceleration.
  I used the newest Intel driver software provided by jessie-backports,
  since the official release (kernel 3.16) have a lot of issues with
  Broadwell hardware.

* Kernel command line: (UUID erased)
 BOOT_IMAGE=/boot/vmlinuz-4.3.0-0.bpo.1-amd64 root=UUID=xxx ro 
intel_iommu=igfx_off



Additional comments:

* This corruption was observed on both the physical screen, as well as
  the virtual screen when viewed via x11vnc.

* I tried "modesetting" X11 DDX to replace the "intel" driver.
  It came with its own set of problems, see
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835123

I am a long-time user of Linux/GNU systems, but I am not a Linux kernel
expert. If you need me to gather some information from my running system,
I should be able to help.



Here are some account of the real cases:


LibreOffice 5 (concretely: 5.2; other versions could be affected too)
-

I noticed the following actions were conducive to triggering the bug:

1) editing a spreadsheet cell that already has a content
2) editing text document
3) page up/page down in a text document
4) pasting a moderate length of a paragraph onto a text document (say,
the length of the paragraph is about half a screen's height)

Here is an example of a consistent problem.
Easy step to reproduce bug in the worksheet in LibreOffice 5.2:

* Open this sample document: "Video-training-sheet.ods"
* Go to the cell B29 with content:
  "Lord's table on 1/15 and 1/22 will begin at 9:30am"
* Press F2
* Move the cursor to somewhere in the middle, say to the beginning of the
  word "will"
* insert some text -- then the text to the right of the cursor will be
  corrupted because of overwriting of old pixels with new pixels without
  erasing the old ones.

I did several tests with other version of LibreOffice, as well as a
different host. Here is the summary table:

Hostname Host OS metal?   software   Corruption?
compsci-wp   Linux 3.16  docker   LO-5.2.4 official buildNo
wirawan2 Linux 4.3   docker   LO-5.2.4 official buildYes
wirawan2 Linux 4.3   docker   LO-4.3.3 debian official   No
wirawan2 Linux 4.7   direct   LO-5.2.4 debian backports  Yes

"Corruption" refers to whether the screen corruption occured when I edited
the sample document "Video-training-sheet.ods" above.



Xpdf


Please view the enclosed file, "sunway-report-2016.pdf", which
can be downloaded from: 
http://www.netlib.org/utk/people/JackDongarra/PAPERS/sunway-report-2016.pdf
(md5:f8bf0f6f7859987714d1df66de016e6c).

On page 8, as the picture was being composed, the top left corner of
the document blinks with with "animating" images until that picture is
fully composed.
This problem occurs with Kernel backport version 4.3 and 4.8.

The following problem (the picture shown as xpdf-screen-5.png) seems to
only occur on newer kernels (4.6, 4.7, 4.8):
When one nagivates with Page-Up and Page-Down keys, at some (seemingly)
random moments, the displayed picture was corrupt.
See that attached picture file.



iSilo under Wine


This is a more complex setup. It is a 32-bit wine running under Docker
container (with 32-bit Ubuntu-14 base image), which is used to run
Windows version of "iSilo" software (a electronic document reader).
Other than the iSilo itself, I used software provided by Ubuntu
14.04.3 repository.

Often the document is drawn with corruption, see file isilo-screen-1.png .


(Attachments will be included in a subsequent email.)



In summary: I think this is an important problem to address, as I have
been having a lot of pains with graphics issues on this Intel Broadwell

Bug#993903: xfce4-session: After resuming from suspend, the synaptic touchpad was no longer working

2021-09-07 Thread Wirawan Purwanto
Package: xfce4-session
Version: 4.12.1-6
Severity: important

Dear Maintainer,

My laptop is running stock Debian 10 with up-to-date software,
and no custom kernel or such modifications.
I am using the stock XFCE packages provided by Debian.
I notice that at random times (not quite sure the context of the
happenings, i.e. the precise cause of the issue), the synaptic
touchpad was no longer working after the laptop was suspended to RAM
then resumed.

Note: I file this bug against "xfce4-session" initially because I do
not know which package may cause the issue.

Desktop: XFCE, under Debian 10
Hardware: Lenovo Thinkpad T450s
Screen-saver: xscreensaver
(It has light-locker installed but not running)

After resume from suspend, the mouse was locked.
Clicking works, but the mouse would not move.

The last time this happened, the sequence of events was as follows:

1) the computer was completely connected to external USB mouse and keyboard

2) the computer was suspended using "xfce4-session-logout --suspend"

3) the peripheral devices were removed

4) the computer was resumed

Upon resumption, the mouse no longer moves according to the synaptic
touchpad's input.
But pressing the mechanical buttons (left/right buttons) worked.

I am not 100% confident if the external device being removed when
sleeping was the cause of the touchpad not working.

At first I thought this was a hardware error.
But today I diagnosed the situation with "libinput debug-events",
the movements of finger on the touchpad were registered, like:

event12  POINTER_MOTION+4.68s0.00/ -0.48 ( +0.00/ -1.00)
event12  POINTER_MOTION+4.70s0.48/  0.00 ( +1.00/ +0.00)
event12  POINTER_MOTION+4.70s0.00/ -1.04 ( +0.00/ -2.00)
event12  POINTER_MOTION+4.71s0.00/ -0.52 ( +0.00/ -1.00)
event12  POINTER_MOTION+4.74s   -0.38/  0.00 ( -1.00/ +0.00)
event12  POINTER_MOTION+4.75s0.00/ -0.38 ( +0.00/ -1.00)
event12  POINTER_MOTION+4.76s   -0.48/  0.00 ( -1.00/ +0.00)
event12  POINTER_MOTION+4.77s   -1.03/  0.00 ( -2.00/ +0.00)

Which means, the hardware was fine, and the hardware driver was fine too.
But for some reason the events was ignored by the desktop or the GUI.
Or was the touchpad input grabbed by a program--a screen saver??

This laptop has been running on Debian 10 since April 2021.
The issue only happened a few times.
Usually, when this issue happened, I could put the laptop through one
more suspend/resume cycle, then the touchpad became responsive again.
Which is annoying but not too bad.

But with the latest system reboot, the issue happened again only within 2-3
suspend/resume cycles from the boot-up.
This was "the last time this issue happened" again as described in
detail above.
But this time, the touchpad never became responsive again, despite the
"libinput" program showed activites from the hardware while my finger
was moving on the touchpad.
This is now counterproductive, since I am treating the OS as a
"server OS", i.e. I expect to rarely reboot the system so that I don't
have to restart all the open windows and documents.

PS: I will wait for responses from the community for a while before
rebooting the current OS.  I am doing so to keep this system running
in this erroneous state so that you can get whatever diagnostics
needed from this buggy state, if at all possible.

Thanks,
Wirawan

-- System Information:
Debian Release: 10.10
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfce4-session depends on:
ii  libatk1.0-02.30.0-2
ii  libc6  2.28-10
ii  libcairo2  1.16.0-4+deb10u1
ii  libdbus-1-31.12.20-0+deb10u1
ii  libdbus-glib-1-2   0.110-4
ii  libfontconfig1 2.13.1-2
ii  libfreetype6   2.9.1-3+deb10u2
ii  libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii  libglib2.0-0   2.58.3-2+deb10u3
ii  libgtk2.0-02.24.32-3
ii  libice62:1.0.9-2
ii  libpango-1.0-0 1.42.4-8~deb10u1
ii  libpangocairo-1.0-01.42.4-8~deb10u1
ii  libpangoft2-1.0-0  1.42.4-8~deb10u1
ii  libpolkit-gobject-1-0  0.105-25
ii  libsm6 2:1.2.3-1
ii  libwnck22  2.30.7-6
ii  libx11-6   2:1.6.7-1+deb10u2
ii  libxfce4ui-1-0 4.12.1-3
ii  libxfce4util7  4.12.1-3
ii  libxfconf-0-2  4.12.1-1
ii  xfce4-settings 4.12.4-1
ii  xfconf 4.12.1-1

Versions of packages xfce4-session recommends:
ii  dbus-x11   1.12.20-0+deb10u1
ii  libpam-systemd 241-7~deb10u8
ii  light-locker   1.8.0-3
ii  systemd-sysv   241-7~deb10u8

Bug#993903: Acknowledgement (xfce4-session: After resuming from suspend, the synaptic touchpad was no longer working)

2021-09-25 Thread Wirawan Purwanto
, your message was also forwarded to
>   wiraw...@gmail.com
> (after having been given a Bug report number, if it did not have one).
>
> Your message has been sent to the package maintainer(s):
>  Debian Xfce Maintainers 
>
> If you wish to submit further information on this problem, please
> send it to 993...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 993903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993903
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems



-- 
Wirawan Purwanto
Computational Scientist, HPC Group
Information Technology Services
Old Dominion University
Norfolk, VA 23529

~ https://bfa.org ~
"Get your own copy of a free study Bible"