Bug#925948: xfce4-power-manager: Display power management blanking cannot unblank

2019-03-28 Thread Ed Peguillan III 
Package: xfce4-power-manager
Version: 1.6.1-1
Severity: grave
Tags: a11y
Justification: causes non-serious data loss

Running Debian testing on Lenovo ThinkPad X1 Extreme, xfce4 desktop
environment.

I wished to have power manager blank my monitor after 1 minute of inactivity if
running on battery. Power manager does successfully blank monitor, but
cannot unblank. Moving the mouse or pressing any keys does not unblank
the monitor. Only way to fix is to hold power button to force a
shutdown.

EDIT: A workaround is to use CTRL + ALT + F<2,3,4,etc> to switch to a
new tty temporarily. Then CTRL + ALT + F1 switches back to xfce, which
will display the unlock screen.

Steps to reproduce:

1. Allow XFCE4 Power Manager to manage display power
2. Set 'Blank after' to One minute.
3. Wait 1 minute. Display blanks, cannot unblank.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (1000, 'testing'), (1000, 'stable'), (750, 'stable'), (50, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-4-amd64 (SMP w/8 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfce4-power-manager depends on:
ii  libc6 2.28-8
ii  libcairo2 1.16.0-4
ii  libgdk-pixbuf2.0-02.38.1+dfsg-1
ii  libglib2.0-0  2.58.3-1
ii  libgtk-3-03.24.5-1
ii  libnotify40.7.7-4
ii  libpango-1.0-01.42.4-6
ii  libpangocairo-1.0-0   1.42.4-6
ii  libupower-glib3   0.99.10-1
ii  libx11-6  2:1.6.7-1
ii  libxext6  2:1.3.3-1+b2
ii  libxfce4ui-2-04.12.1-3
ii  libxfce4util7 4.12.1-3
ii  libxfconf-0-2 4.12.1-1
ii  libxrandr22:1.5.1-1
ii  upower0.99.10-1
ii  xfce4-power-manager-data  1.6.1-1

Versions of packages xfce4-power-manager recommends:
ii  libpam-systemd   241-1
ii  xfce4-power-manager-plugins  1.6.1-1

xfce4-power-manager suggests no packages.

-- no debconf information

Bug#909551: qdirstat: Segfault immediately after choosing scan directory

2018-09-24 Thread Ed Peguillan III 
Package: qdirstat
Version: 1.4-2
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

   I installed qdirstat and launched it. It gave me a GTK(3?) prompt for
   choosing the directory I wish to scan. After choosing the directory
   and clicking "Open", it crashes. The message given when run from the
   terminal is "Segmentation fault". This happens when running
   with/without root privileges. Here is the log:

2018-09-24 22:36:10.956 [5046] Logger.cpp:143 openLogFile():  -- Log 
Start --
2018-09-24 22:36:10.956 [5046] main.cpp:44 logVersion():  
QDirStat-1.4 built with Qt 5.7.1
2018-09-24 22:36:11.070 [5046]DirTreeModel.cpp:549 sort():  Sorting 
by NameCol ascending
2018-09-24 22:36:11.070 [5046]TreemapView.cpp:124 
setSelectionModel():  
2018-09-24 22:36:11.071 [5046] Cleanup.cpp:415 desktopSpecificApps(): 
 Detected desktop "XFCE"
2018-09-24 22:36:11.071 [5046] Cleanup.cpp:468 desktopSpecificApps(): 
 %filemanager => "thunar"
2018-09-24 22:36:11.071 [5046] Cleanup.cpp:468 desktopSpecificApps(): 
 %terminal => "xfce4-terminal &"
2018-09-24 22:36:11.071 [5046]DebugHelpers.cpp:133 
dumpExcludeRules():  
2018-09-24 22:36:11.071 [5046] MainWindow.cpp:818 
toggleVerboseSelection():  Verbose selection is now off. Change this with 
Shift-F7.
2018-09-24 22:36:12.818 [5046] DirTree.cpp:95 startReading(): 
url: "/home/yankee"
2018-09-24 22:36:12.818 [5046] DirTree.cpp:98 startReading():  
device: /dev/sda5
2018-09-24 22:36:12.818 [5046]DirReadJob.cpp:349 stat():  url: 
"/home/yankee"
2018-09-24 22:36:12.818 [5046]MainWindow.cpp:589 
expandTreeToLevel():  Expanding tree to level 1
2018-09-24 22:36:12.835 [5046]DirReadJob.cpp:248 startReading():  
Found cache file .qdirstat.cache.gz
2018-09-24 22:36:12.836 [5046]DirReadJob.cpp:260 startReading():  
Using cache file /home/yankee/.qdirstat.cache.gz for /home/yankee
2018-09-24 22:36:12.836 [5046]DirReadJob.cpp:544 killAll():  NOT 
killing read job 
2018-09-24 22:36:12.836 [5046]DirReadJob.cpp:278 startReading():  
Deleting subtree /home/yankee
2018-09-24 22:36:12.836 [5046]DirTree.cpp:237 deletingChildNotify(): 
 Deleting child /home/yankee
2018-09-24 22:36:12.836 [5046]DirTreeModel.cpp:918 deletingChild():  
Deleting child /home/yankee
2018-09-24 22:36:12.836 [5046]DirTreeModel.cpp:926 deletingChild():  
beginRemoveRows for /home/yankee row 0
2018-09-24 22:36:12.836 [5046]DirTreeModel.cpp:984 
invalidatePersistent():  Invalidating 

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I attempted to start and use qdirstat, but it crashed when selecting
a directory to scan.

   * What was the outcome of this action?

   It crashed.

   * What outcome did you expect instead?

   It should not crash.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (1000, 'testing'), (1000, 'stable'), (750, 'stable'), (50, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-1-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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qdirstat depends on:
ii  libc62.27-6
ii  libgcc1  1:8.2.0-7
ii  libgl1   1.1.0-1
ii  libgl1-mesa-glx  18.1.7-1
ii  libqt5core5a 5.11.1+dfsg-8
ii  libqt5gui5   5.11.1+dfsg-8
ii  libqt5widgets5   5.11.1+dfsg-8
ii  libstdc++6   8.2.0-7
ii  liburi-perl  1.74-1
ii  perl 5.26.2-7
ii  zlib1g   1:1.2.11.dfsg-1

qdirstat recommends no packages.

qdirstat suggests no packages.

-- no debconf information

Bug#853831: libqt5gui5: font rendering broken

2017-09-04 Thread Ed Peguillan III 
I eventually fixed my issue by installing package 'freetype2-demos'. 
Your mileage may vary.


Ed

On Fri, 01 Sep 2017 18:12:33 -0500 Ed Peguillan III 
 wrote:

> Package: libqt5gui5
> Version: 5.9.1+dfsg-9
> Followup-For: Bug #853831
>
> Dear Maintainer,
>
> I think my problem is related. I initially thought the problem was with
> qjackctl specifically, but I realized that many qt5 applications would
> not start that depended on libqt5gui5, such as virtualbox.
>
> This error is given when starting qjackctl or virtualbox:
>
> $ virtualbox
> /usr/lib/virtualbox/VirtualBox: symbol lookup error:
> /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: undefined symbol:
> FT_Property_Set
>
> $ qjackctl
> qjackctl: symbol lookup error:
> /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: undefined symbol:
> FT_Property_Set
>
> See #873792 @
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873792
>
> After I deleted the file I mentioned in that bug report, virtualbox and
> qjackctl started, until I rebooted my machine. Now it is back to the
> same error.
>
> I had infinality fonts installed from this git repo
> https://github.com/cmpitg/infinality-debian-package
> This may be the cause of the conflict. Unfortunately, I don't know 
enough about this to figure out what is wrong. Uninstalling infinality 
did not fix the problem.

>
> # apt install --reinstall libqt5gui5
>
> did not work.
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers testing
> APT policy: (1000, 'testing'), (1000, 'stable'), (750, 'stable'), 
(50, 'unstable'), (1, 'experimental')

> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.12.0-1-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 /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages libqt5gui5 depends on:
> ii fontconfig 2.12.3-0.2
> ii libc6 2.24-14
> ii libdrm2 2.4.82-1
> ii libegl1-mesa [libegl1-x11] 13.0.6-1+b2
> ii libfontconfig1 2.12.3-0.2
> ii libfreetype6 2.8-0.2
> ii libgbm1 13.0.6-1+b2
> ii libgcc1 1:7.2.0-1
> ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2
> ii libglib2.0-0 2.53.4-3

Bug#873792: qjackctl will not start at all

2017-09-04 Thread Ed Peguillan III 
Just for posterity, qjackctl and virtualbox worked until I restarted my 
machine, then it started throwing the same errors again. I eventually 
found that installing package 'freetype2-demos' fixed it.


Ed

On Fri, 1 Sep 2017 12:38:56 +0200 Sebastian Ramacher 
 wrote:

> On 2017-09-01 03:38:28, Ed Peguillan III wrote:
> > My mail client replied to the wrong address, my apologies.
> >
> > After performing
> > $ sudo mv 
/usr/lib/x86_64-linux-gnu/freetype-infinality/liblibfreetype.so.6

> > ~
> >
> > qjackctl and virtualbox seem to start and work normally.
> >
> > It's too bad that I can't use infinality fonts anymore, my screen 
is back to

> > looking terrible.
> >
> > Thank you for your help! This bug can be closed.
>
> Thanks, closing.
> --
> Sebastian Ramacher

Bug#848102: [octave] crashed with some random typing in octave editor

2017-09-03 Thread Ed Peguillan III 
I confirm this issue. Typing in the editor causes octave to exit "with 
signal 11." I was able to stop it from crashing by disabling one or more 
text autocompletion features in preferences.


Menu: Edit -> Preferences... -> Editor -> Autocompletion

I just unchecked everything in that section, and it seems not to crash 
anymore.


Ed

On Wed, 14 Dec 2016 06:44:53 + lumin  wrote:
> Package: octave
> Version: 4.2.0-1
> Severity: normal
>
> Hi,
>
> Randomly typing something in octave editor will cause
> a crash with SIGSEGV.
>
> For example, I launched Octave and typed merely "asdfasdf"
> and then octave crashed.
>
> (gdb) run
> Starting program: /usr/bin/octave
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library 
"/lib/x86_64-linux-gnu/libthread_db.so.1".

> Gtk-Message: Failed to load module "canberra-gtk-module"
> octave exited with signal 11
> [Inferior 1 (process 12389) exited normally]
> (gdb)
>
>

Bug#853831: libqt5gui5: font rendering broken

2017-09-01 Thread Ed Peguillan III 
Package: libqt5gui5
Version: 5.9.1+dfsg-9
Followup-For: Bug #853831

Dear Maintainer,

I think my problem is related. I initially thought the problem was with
qjackctl specifically, but I realized that many qt5 applications would
not start that depended on libqt5gui5, such as virtualbox.

This error is given when starting qjackctl or virtualbox:

$ virtualbox 
/usr/lib/virtualbox/VirtualBox: symbol lookup error:
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: undefined symbol:
FT_Property_Set

$ qjackctl 
qjackctl: symbol lookup error:
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: undefined symbol:
FT_Property_Set

See #873792 @
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873792

After I deleted the file I mentioned in that bug report, virtualbox and
qjackctl started, until I rebooted my machine. Now it is back to the
same error.

I had infinality fonts installed from this git repo
https://github.com/cmpitg/infinality-debian-package
This may be the cause of the conflict. Unfortunately, I don't know enough about 
this to figure out what is wrong. Uninstalling infinality did not fix the 
problem.

# apt install --reinstall libqt5gui5

did not work.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (1000, 'testing'), (1000, 'stable'), (750, 'stable'), (50, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-1-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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libqt5gui5 depends on:
ii  fontconfig   2.12.3-0.2
ii  libc62.24-14
ii  libdrm2  2.4.82-1
ii  libegl1-mesa [libegl1-x11]   13.0.6-1+b2
ii  libfontconfig1   2.12.3-0.2
ii  libfreetype6 2.8-0.2
ii  libgbm1  13.0.6-1+b2
ii  libgcc1  1:7.2.0-1
ii  libgl1-mesa-glx [libgl1] 13.0.6-1+b2
ii  libglib2.0-0 2.53.4-3
ii  libharfbuzz0b1.4.2-1
ii  libice6  2:1.0.9-2
ii  libinput10   1.8.0-1
ii  libjpeg62-turbo  1:1.5.2-2
ii  libmtdev11.1.5-1+b1
ii  libpng16-16  1.6.31-1
ii  libqt5core5a [qtbase-abi-5-9-0]  5.9.1+dfsg-9
ii  libqt5dbus5  5.9.1+dfsg-9
ii  libqt5network5   5.9.1+dfsg-9
ii  libsm6   2:1.2.2-1+b3
ii  libstdc++6   7.2.0-1
ii  libudev1 234-2.3
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb-glx0  1.12-1
ii  libxcb-icccm40.4.1-1+b1
ii  libxcb-image00.4.0-1+b2
ii  libxcb-keysyms1  0.4.0-1+b2
ii  libxcb-randr01.12-1
ii  libxcb-render-util0  0.3.9-1+b1
ii  libxcb-render0   1.12-1
ii  libxcb-shape01.12-1
ii  libxcb-shm0  1.12-1
ii  libxcb-sync1 1.12-1
ii  libxcb-xfixes0   1.12-1
ii  libxcb-xinerama0 1.12-1
ii  libxcb-xkb1  1.12-1
ii  libxcb1  1.12-1
ii  libxi6   2:1.7.9-1
ii  libxkbcommon-x11-0   0.7.1-1
ii  libxkbcommon00.7.1-1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages libqt5gui5 recommends:
ii  libqt5svg5 5.9.1-2+b1
ii  qt5-gtk-platformtheme  5.9.1+dfsg-9

Versions of packages libqt5gui5 suggests:
pn  qt5-image-formats-plugins  
pn  qtwayland5 

-- no debconf information

Bug#873792: qjackctl will not start at all

2017-09-01 Thread Ed Peguillan III 

My mail client replied to the wrong address, my apologies.

After performing
$ sudo mv 
/usr/lib/x86_64-linux-gnu/freetype-infinality/liblibfreetype.so.6 ~


qjackctl and virtualbox seem to start and work normally.

It's too bad that I can't use infinality fonts anymore, my screen is 
back to looking terrible.


Thank you for your help! This bug can be closed.

Ed

On Thu, 31 Aug 2017 23:46:16 +0200 Sebastian Ramacher 
 wrote:

> Re-adding the bug to CC.
>
> On 2017-08-31 16:02:13, Ed Peguillan III wrote:
> > Sure.
> >
> > |$ ldd -r /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5||
> > || linux-vdso.so.1 (0x7ffd883f3000)||
> > || libxcb-xinerama.so.0 => 
/usr/lib/x86_64-linux-gnu/libxcb-xinerama.so.0

> > (0x7f6ec82f9000)||
> > || libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0
> > (0x7f6ec7fe4000)||
> > || libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
> > (0x7f6ec7da)||
> > || libfreetype.so.6 =>
> > /usr/lib/x86_64-linux-gnu/freetype-infinality/libfreetype.so.6
>
> And that's the issue. Please remove it and try again.
>
> Cheers
>
> > (0x7f6ec7aef000)||
> > || libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
> > (0x7f6ec7388000)||
> > || libQt5DBus.so.5 => /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
> > (0x7f6ec70fe000)||
> > || libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> > (0x7f6ec69b5000)||
> > || libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> > (0x7f6ec6798000)||
> > || libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6
> > (0x7f6ec6458000)||
> > || libX11-xcb.so.1 => /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
> > (0x7f6ec6256000)||
> > || libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6
> > (0x7f6ec6046000)||
> > || libSM.so.6 => /usr/lib/x86_64-linux-gnu/libSM.so.6
> > (0x7f6ec5e3e000)||
> > || libICE.so.6 => /usr/lib/x86_64-linux-gnu/libICE.so.6
> > (0x7f6ec5c21000)||
> > || libxcb-xkb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-xkb.so.1
> > (0x7f6ec5a05000)||
> > || libxcb-render-util.so.0 =>
> > /usr/lib/x86_64-linux-gnu/libxcb-render-util.so.0 
(0x7f6ec5801000)||

> > || libxcb-render.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-render.so.0
> > (0x7f6ec55f3000)||
> > || libxcb-sync.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-sync.so.1
> > (0x7f6ec53ec000)||
> > || libxcb-xfixes.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-xfixes.so.0
> > (0x7f6ec51e4000)||
> > || libxcb-randr.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-randr.so.0
> > (0x7f6ec4fd4000)||
> > || libxcb-image.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-image.so.0
> > (0x7f6ec4dcf000)||
> > || libxcb-shm.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-shm.so.0
> > (0x7f6ec4bcb000)||
> > || libxcb-keysyms.so.1 => /usr/lib/x86_64-linux-gnu/libxcb-keysyms.so.1
> > (0x7f6ec49c8000)||
> > || libxcb-icccm.so.4 => /usr/lib/x86_64-linux-gnu/libxcb-icccm.so.4
> > (0x7f6ec47c3000)||
> > || libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1

Bug#873792: qjackctl will not start at all

2017-08-31 Thread Ed Peguillan III 
Package: qjackctl
Version: 0.4.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
   I use jackd to facilitate realtime audio according to my limits.conf
   for some software called Pianoteq. In the last update, I tried to run
   qjackctl and received the following error:

   qjackctl: symbol lookup error:
   /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: undefined symbol:
   FT_Property_Set

   I am unable to start qjackctl

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

   I do not think I intentionally installed any extra packages that stops 
qjackctl from launching properly.

   * What was the outcome of this action?
   qjackctl does not launch

   * What outcome did you expect instead?
   qjackctl launches normally

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (1000, 'testing'), (1000, 'stable'), (750, 'stable'), (50, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-1-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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qjackctl depends on:
ii  jackd 5
ii  libasound21.1.3-5
ii  libc6 2.24-14
ii  libgcc1   1:7.2.0-1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.10+20150825git1ed50c92~dfsg-5
ii  libqt5core5a  5.9.1+dfsg-9
ii  libqt5dbus5   5.9.1+dfsg-9
ii  libqt5gui55.9.1+dfsg-9
ii  libqt5widgets55.9.1+dfsg-9
ii  libqt5x11extras5  5.9.1-2+b1
ii  libqt5xml55.9.1+dfsg-9
ii  libstdc++67.2.0-1
ii  libx11-6  2:1.6.4-3

qjackctl recommends no packages.

Versions of packages qjackctl suggests:
ii  pulseaudio-utils  10.0-2

-- no debconf information

Bug#872687: xfce4-pulseaudio-plugin: Unable to click or use volume slider

2017-08-22 Thread Ed Peguillan III 

Works a charm, Unit 193. Thanks.

On Mon, 21 Aug 2017 18:06:30 -0400 (EDT) Unit 193  
wrote:

> Howdy,
>
> This is not a bug specific to xfce4-pulseaudio-plugin but to GTK+3. 
You can see

> upstream reports in GTK+3[1], Xfce[2], and even one over at Arch[3].
>
> If you apply the simple patch by Carlos Garnacho and rebuild GTK+3 
you will no

> longer have this issue.
>
>
> [1]: https://bugzilla.gnome.org/show_bug.cgi?id=786029
> [2]: https://bugzilla.xfce.org/show_bug.cgi?id=13770
> [3]: https://bugs.archlinux.org/task/55114
>
>
> ~Unit 193
> Unit193 @ Freenode
> Unit193 @ OFTC
>
>

Bug#872687: xfce4-pulseaudio-plugin: Unable to click or use volume slider

2017-08-21 Thread Ed Peguillan III 

Downgrading did not work.

I did install KiCad recently, and one of the suggested packages was 
extra-xdg-menus, so I installed it. Not sure if that could be related to 
the problem.

Bug#872687: xfce4-pulseaudio-plugin: Unable to click or use volume slider

2017-08-19 Thread Ed Peguillan III 
Package: xfce4-pulseaudio-plugin
Version: 0.2.5-1
Severity: important

Dear Maintainer,


   * What led up to the situation?
   I attempted to use the pulse panel plugin to change my computer's
   playback volume, but the popup frame with the volume slider simply
   disappears the moment I try to click and drag on the slider. This has
   never happened before today.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   Note that the mute checkbox still works, and the menu item that
   starts pavucontrol still works. Only the slider does not work
   properly.

   Pavucontrol seems to work properly.

   I cannot think of any new packages I may have installed that would
   cause this issue.

   I ran 'apt install --reinstall xfce4-panel-plugin', and restarted X,
   but the behaviour remained.

   After submitting this bug report, I will attempt downgrading
   xfce4-panel-plugin to 0.2.4-1 to see if anything changes.

   * What was the outcome of this action?
   Attempting to click and drag the volume slider just results in the
   plugin frame disappearing immediately, without changing the volume.

   * What outcome did you expect instead?
   The volume slider should be clickable and draggable without the frame
   disappearing the moment the slider is clicked.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (1000, 'testing'), (1000, 'stable'), (750, 'stable'), (50, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-1-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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xfce4-pulseaudio-plugin depends on:
ii  libatk1.0-0  2.24.0-1
ii  libc62.24-12
ii  libcairo-gobject21.14.10-1
ii  libcairo21.14.10-1
ii  libdbus-1-3  1.11.16+really1.10.22-1
ii  libdbus-glib-1-2 0.108-2
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.53.4-3
ii  libgtk-3-0   3.22.18-1
ii  libkeybinder-3.0-0   0.3.1-1
ii  libnotify4   0.7.7-2
ii  libpango-1.0-0   1.40.6-1
ii  libpangocairo-1.0-0  1.40.6-1
ii  libpulse-mainloop-glib0  10.0-2
ii  libpulse010.0-2
ii  libxfce4panel-2.0-4  4.12.1-2
ii  libxfce4ui-2-0   4.12.1-2
ii  libxfce4util74.12.1-3
ii  libxfconf-0-24.12.1-1

Versions of packages xfce4-pulseaudio-plugin recommends:
ii  pavucontrol  3.0-3.1
ii  pulseaudio   10.0-2

xfce4-pulseaudio-plugin suggests no packages.

-- no debconf information

Bug#868315: kanatest: Kanatest cannot start, segfaults

2017-07-14 Thread Ed Peguillan III 
Package: kanatest
Version: 0.4.8-3+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

I installed Kanatest via apt and tried to start it from XFCE's
applications menu. It wouldn't start. Trying to start it from a terminal
doesn't give much information:

$ kanatest 
Segmentation fault

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I tried to start Kanatest from the applications menu, and from the
terminal, but it crashes.

   * What was the outcome of this action?

Kanatest crashes - segmentation fault.

   * What outcome did you expect instead?

   Kanatest should have started normally.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (1000, 'testing'), (1000, 'stable'), (750, 'stable'), (50, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-1-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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kanatest depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-12
ii  libcairo21.14.10-1
ii  libfontconfig1   2.12.3-0.2
ii  libfreetype6 2.8-0.2
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.52.3-1
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.6-1
ii  libpangocairo-1.0-0  1.40.6-1
ii  libpangoft2-1.0-01.40.6-1
ii  libxml2  2.9.4+dfsg1-3

Versions of packages kanatest recommends:
ii  fonts-ipafont-mincho [fonts-japanese-mincho]  00303-16

Versions of packages kanatest suggests:
pn  fonts-mikachan  

-- no debconf information

Bug#867366: installation-reports: Kernel panic: null pointer derefence at (null), first boot after install

2017-07-05 Thread Ed Peguillan III 
This same issue appears to be referenced here: 
http://forums.debian.net/viewtopic.php?f=17&t=133564


I followed the instructions and prevented the kernel from using 
nouveau.ko and I booted successfully. I suppose this bug can be closed, 
but it's still a problem that required manual intervention, so I'm not 
sure what to do as far as filing a bug in the appropriate place.


I also don't really know what it means to not be able to use nouveau 
drivers.


I got this far thanks to reddit user /u/akas84, our discussion is here: 
https://www.reddit.com/r/debian/comments/6liq1m/kernel_panic_null_pointer_dereference_first_boot/?st=j4ryrztn&sh=2226543c


They suggest the problem is with nouveau. What can I do in the meantime?

Thanks

On Wed, 05 Jul 2017 22:00:14 -0500 Ed Peguillan III 
 wrote:

> Package: installation-reports
> Severity: critical
> Tags: d-i
> Justification: breaks the whole system
>
> Dear Maintainer,
>
> * What led up to the situation?
>
> Image of panic (after installing stable): https://i.imgur.com/4uTKicf.jpg
>
> I reformatted my computer and tried installing Debian Testing.
> The very first reboot led to the kernel panic shown in the imgur image. I
> reformatted again, this time trying Debian 9.0 Stable from the link
> given in "Image version": debian-9.0.0-amd64-netinst.iso. I got the
> exact same kernel panic shown in the imgur image.
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> I simply installed Debian stable and rebooted.
>
> * What was the outcome of this action?
>
> I got a kernel panic about 6.7 seconds after booting. No time to
> login or anything, it seems to happen instantaneously after the tty
> shows the "login:" prompt.
>
> * What outcome did you expect instead?
>
> I hoped to have a working system.
>
> -- Package-specific info:
>
> Boot method: USB
> Image version: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.0.0-amd64-netinst.iso

> Date: 5 July, 2017
>
> Machine: Motherboard: Gigabyte EP45-UD3P (I can get more information if
> needed)
>
> Partitions: 
>
> During install, I wiped and created a new partition table on the hard
> drive to hold Debian. I created a single extended partition covering the
> entire drive, then a single ext4 partition covering that entire extended
> partition. This partition served as mountpoint for /. I set root's
> reserved block percentage to 0%.
>
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
>
> ALL WERE OK
>
> Initial boot: [O]
> Detect network card: [ ]
> Configure network: [ ]
> Detect CD: [ ]
> Load installer modules: [ ]
> Clock/timezone setup: [ ]

Bug#867366: installation-reports: Kernel panic: null pointer derefence at (null), first boot after install

2017-07-05 Thread Ed Peguillan III 
Package: installation-reports
Severity: critical
Tags: d-i
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?

Image of panic (after installing stable): https://i.imgur.com/4uTKicf.jpg

I reformatted my computer and tried installing Debian Testing.
The very first reboot led to the kernel panic shown in the imgur image. I
reformatted again, this time trying Debian 9.0 Stable from the link
given in "Image version": debian-9.0.0-amd64-netinst.iso. I got the
exact same kernel panic shown in the imgur image.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I simply installed Debian stable and rebooted.

   * What was the outcome of this action?

   I got a kernel panic about 6.7 seconds after booting. No time to
   login or anything, it seems to happen instantaneously after the tty
   shows the "login:" prompt.

   * What outcome did you expect instead?

   I hoped to have a working system.

-- Package-specific info:

Boot method: USB
Image version: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.0.0-amd64-netinst.iso
Date: 5 July, 2017

Machine: Motherboard: Gigabyte EP45-UD3P (I can get more information if
needed)

Partitions: 

During install, I wiped and created a new partition table on the hard
drive to hold Debian. I created a single extended partition covering the
entire drive, then a single ext4 partition covering that entire extended
partition. This partition served as mountpoint for /. I set root's
reserved block percentage to 0%.

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

ALL WERE OK

Initial boot:   [O]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[O]

Comments/Problems: All parts of the install completed successfully, but
I don't think Debian was installed properly, or there is some other
issue that needs to be resolved. I get a kernel panic upon the first
boot after install.



No indications given during the install that anything was wrong.
-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

IT may be difficult to get you these logs. I'll try to get them via an
Ubuntu liveUSB or something.

Once you have filled out this report, mail it to sub...@bugs.debian.org.


**
** THE HARDWARE SUMMARY BELOW IS NOT FOR THE AFFECTED SYSTEM,
** ONLY FOR THE COMPUTER I SUBMITTED THE REPORT FROM.
**

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20170620-00:06"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux steinsgate 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2 (2017-06-12) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core 
processor DRAM Controller [8086:0154] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:21f3]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd 
Gen Core processor PCI Express Root Port [8086:0151] (rev 09)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen 
Core processor Graphics Controller [8086:0166] (rev 09)
lspci -knn: Subsystem: Lenovo Device [17aa:21f4]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 
Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21f3]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: Kernel modules: xhci_pci
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 7 
Series/C216 Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21f3]
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM 
Gigabit Network Connection [8086:1502] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21f3]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: Kernel modules: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 
Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
lspci -knn: Subsystem: Lenovo Device [17aa:21f3]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Inte

Bug#865844: mount: Umount's tab-autocompletion fails for relative directories in Bash

2017-06-25 Thread Ed Peguillan III 
Package: mount
Version: 2.29.2-1
Severity: wishlist

Dear Maintainer,

   * What led up to the situation?

A directory in the current bash working directory was being used as a
mountpoint for a block device. I attempted to unmount it by using, for
example, 'sudo umount MyMountPoi' or 'sudo umount ./MyMountPoi'. The 
name was not autocompleted
and no autocomplete suggestions are given. Autocompletion does work,
however, for absolute paths to either the block device that was mounted,
or its mount point (as expected).

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I attempted to unmount a block device from a mountpoint by specifying a
relative path to the mountpoint as the {directory} argument in the 'umount' 
command.

   * What was the outcome of this action?

Bash autocompletion did not work for the relative path.

   * What outcome did you expect instead?

Bash autocompletion does work for the relative path.

I know this problem has existed for at least 2 or 3 years now, and it's
not really a big issue. It would just be nice if path autocompletion was
a little more consistent in one of UNIX's essential utilities.

External references of this issue (in other shells besides bash):
https://github.com/zimframework/zim/issues/3
https://unix.stackexchange.com/questions/318290/how-can-i-tab-complete-umount-restricting-to-volumes-in-a-specific-directory
http://zsh-users.zsh.narkive.com/i7HfOYLH/zsh-completion-for-umount

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (1000, 'testing'), (1000, 'stable'), (750, 'stable'), (50, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mount depends on:
ii  libblkid1  2.29.2-1
ii  libc6  2.24-12
ii  libmount1  2.29.2-1
ii  libselinux12.6-3+b1
ii  libsmartcols1  2.29.2-1
ii  libudev1   232-25

mount recommends no packages.

Versions of packages mount suggests:
pn  nfs-common  

-- no debconf information

Bug#857562: terminator: Shortcuts to "Open terminal here" broken in tuxcmd, thunar, ...

2017-05-21 Thread Ed Peguillan III 

I have had the same issue for nearly a year now.

|$ uname -a||
||Linux debian 4.9.0-2-amd64 #1 SMP Debian 4.9.18-1 (2017-03-30) x86_64 
GNU/Linux||

||
||$ lsb_release -a||
||Distributor ID:Debian||
||Description:Debian GNU/Linux 9.0 (stretch)||
||Release:9.0||
||Codename:stretch||
||
||$ apt-cache policy xfce4||
||xfce4:||
||  Installed: 4.12.3||
||
||$ thunar --version||
||Thunar 1.6.11 (Xfce 4.12)||
||
||$ terminator --version||
||terminator 1.90|

Bug#860011: xspim: white screen, broken gui

2017-04-10 Thread Ed Peguillan III 
Package: spim
Version: 8.0+dfsg-6+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I installed spim with the intention of trying out xspim. The command
line program "spim" seems to run fine, but xspim is completely unusable
with broken gui elements. See imgur link for screenshot:
https://i.imgur.com/gLnrbYe.png

   * What led up to the situation?
   Installed spim, tried running xspim.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 I ran xspim with default settings as it came from my package
 manager.

   * What was the outcome of this action?
   xspim is broken

   * What outcome did you expect instead?
   xspim is not broken?

I know from reading other bugs that this version is probably out of
date, and there is a new version of spim built on qt. So this bug report
is probably pointless. I'm going to try building the qt version from
source.

Regards,
Ed

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (1000, 'testing'), (1000, 'stable'), (750, 'stable'), (50, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (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
Init: systemd (via /run/systemd/system)

Versions of packages spim depends on:
ii  libc6 2.24-9
ii  libx11-6  2:1.6.4-3
ii  libxaw7   2:1.0.13-1+b2
ii  libxt61:1.1.5-1

Versions of packages spim recommends:
ii  xfonts-100dpi  1:1.0.4+nmu1
ii  xfonts-75dpi   1:1.0.4+nmu1

spim suggests no packages.

-- no debconf information

Bug#845380: calibre: GUI does not start, QXcbConnection errors

2017-01-25 Thread Ed Peguillan III 

I am running testing, same issue. Calibre will not start.