Bug#1004457: okular segfaults upon opening specific pdf (worked with previous version)

2022-01-27 Thread Dov Feldstern
Package: okular
Version: 4:21.08.3-1
Severity: important

Dear Maintainer,

After updating my system, Okular segfaults upon opening a specific pdf file. I 
have previously viewed it using okular (not sure exactly which version was 
previously installed) -- and can still view it with zathura -- without incident.

I can provide the offending file, though I would prefer to do so off-list.

Backtrace:

(gdb) r 211227-zichron-menachem-NIS-1750.pdf
Starting program: /usr/bin/okular 211227-zichron-menachem-NIS-1750.pdf
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x718f8640 (LWP 21480)]

(okular:21462): dbind-WARNING **: 01:05:01.357: AT-SPI: Error retrieving 
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.a11y.Bus was not provided by any .service files
[New Thread 0x7fffebf6d640 (LWP 21481)]
Icon theme "nuoveXT-1.6" not found.
Icon theme "Tango" not found.
Icon theme "gnome" not found.
Icon theme "crystalsvg" not found.
Icon theme "breeze" not found.

Thread 1 "okular" received signal SIGSEGV, Segmentation fault.
Poppler::Document::signatures (this=0x55ba7e40) at 
./qt5/src/poppler-document.cc:822
Download failed: Invalid argument.  Continuing without source file 
./obj-x86_64-linux-gnu/qt5/src/./qt5/src/poppler-document.cc.
822 ./qt5/src/poppler-document.cc: No such file or directory.
(gdb) bt
#0  Poppler::Document::signatures (this=0x55ba7e40) at 
./qt5/src/poppler-document.cc:822
#1  0x7fffe90b73a4 in PDFGenerator::loadPages 
(this=this@entry=0x55ab2a00, pagesVector=..., rotation=rotation@entry=0, 
clear=clear@entry=false) at ./generators/poppler/generator_pdf.cpp:790
#2  0x7fffe90b789a in PDFGenerator::init (this=0x55ab2a00, 
pagesVector=..., password=...) at ./generators/poppler/generator_pdf.cpp:654
#3  0x7fffeb468639 in Okular::DocumentPrivate::openDocumentInternal 
(this=0x5566ae00, offer=..., isstdin=isstdin@entry=false, docFile=..., 
filedata=..., password=...) at ./core/document.cpp:890
#4  0x7fffeb468d81 in Okular::Document::openDocument 
(this=this@entry=0x5575abb0, docFile=..., url=..., _mime=..., password=...) 
at ./core/document.cpp:2330
#5  0x7fffeb5c0205 in Okular::Part::doOpenFile 
(this=this@entry=0x5571f000, mimeA=..., fileNameToOpenA=..., 
isCompressedFile=isCompressedFile@entry=0x7fffda47) at ./part/part.cpp:1393
#6  0x7fffeb5c0fb3 in Okular::Part::openFile (this=0x5571f000) at 
./part/part.cpp:1511
#7  0x77f78325 in KParts::ReadOnlyPartPrivate::openLocalFile 
(this=this@entry=0x55699200) at ./src/readonlypart.cpp:180
#8  0x77f793fe in KParts::ReadOnlyPart::openUrl 
(this=this@entry=0x5571f000, url=...) at ./src/readonlypart.cpp:141
#9  0x7fffeb5b1983 in Okular::Part::openUrl (this=, 
_url=..., swapInsteadOfOpening=) at ./part/part.cpp:1743
#10 0x5556a761 in Shell::openUrl (this=, url=..., 
serializedOptions=...) at ./shell/shell.cpp:285
#11 0x5556aa53 in Shell::openDocument (serializedOptions=..., 
url=..., this=0x55669a30) at ./shell/shell.cpp:236
#12 Shell::openDocument (this=this@entry=0x55669a30, url=..., 
serializedOptions=...) at ./shell/shell.cpp:224
#13 0x55561d8a in Okular::main (paths=..., serializedOptions=...) 
at ./shell/okular_main.cpp:162
#14 0x55561a6b in main (argc=, argv=) 
at ./shell/main.cpp:91
quit)

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-3-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IL:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages okular depends on:
ii  kinit 5.88.0-1
ii  kio   5.88.0-1
ii  libc6 2.33-4+b1
ii  libfreetype6  2.11.1+dfsg-1
ii  libjpeg62-turbo   1:2.1.2-1
ii  libkf5activities5 5.88.0-1
ii  libkf5archive55.88.0-1
ii  libkf5bookmarks5  5.88.0-1
ii  libkf5codecs5 5.88.0-1
ii  libkf5completion5 5.88.0-1
ii  libkf5configcore5 5.88.0-1
ii  libkf5configgui5  5.88.0-1
ii  libkf5configwidgets5  5.88.0-1
ii  libkf5coreaddons5 5.88.0-1
ii  libkf5crash5  5.88.0-1
ii  libkf5i18n5   5.88.0-2
ii  libkf5itemviews5  5.88.0-1
ii  libkf5jobwidgets5 5.88.0-1
ii  libkf5kexiv2-15.0.0   21.08.0-1
ii  libkf5kiocore55.88.0-1
ii  libkf5kiowidgets5 5.88.0-1
ii  libkf5parts5  5.88.0-1
ii  libkf5pty55.88.0-1
ii  libkf5purpose-bin 5.88.0-1
ii  libkf5purpose55.88.0-1
ii  

Bug#999553: Info received (After further upgrade (though not of lxpanel itself), the problem disappeared)

2021-12-08 Thread Dov Feldstern
Oops, I spoke to soon... I just rebooted again, and the problem
occurred :/ So it's apparently not deterministic, but does still
occur...

On Wed, Dec 8, 2021 at 10:06 PM Debian Bug Tracking System
 wrote:
>
> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian LXDE Maintainers 
>
> If you wish to submit further information on this problem, please
> send it to 999...@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.
>
> --
> 999553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999553
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems



Bug#999553: After further upgrade (though not of lxpanel itself), the problem disappeared

2021-12-08 Thread Dov Feldstern
Hi!

I just performed another aptitude safe-upgrade, and the problem has
disappeared, Since I don't think lxpanel itself has been upgraded, I
guess the issue must have been in some other component, which *did*
get updated.

So I guess the issue can be closed...

Sorry for the noise!
Dov



Bug#999553: lxpanel starts totally empty (manually restarting it, loads fine)

2021-11-12 Thread Dov Feldstern
Package: lxpanel
Version: 0.10.1-2
Severity: normal

Dear Maintainer,

When logging in, lxpanel appears, but is completely empty. 'ps aux' shows the
process is indeed running, with command line 'lxpanel --profile LXDE'. If I
kill the process and then manually run it with the same comamnd line, it loads
as expected. This happens after each reboot, since having done an 'aptitude
safe-upgrade'.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.14.0-4-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IL:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lxpanel depends on:
ii  libasound2   1.2.5.1-1
ii  libc62.32-4
ii  libcairo21.16.0-5
ii  libcurl3-gnutls  7.79.1-2
ii  libfm-gtk4   1.3.2-1
ii  libfm-modules1.3.2-1
ii  libfm4   1.3.2-1
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.70.1-1
ii  libgtk2.0-0  2.24.33-2
ii  libiw30  30~pre9-13.1
ii  libkeybinder00.3.1-2.1
ii  libmenu-cache3   1.1.0-1.1
ii  libpango-1.0-0   1.48.10+ds1-1
ii  libwnck222.30.7-6+b1
ii  libx11-6 2:1.7.2-2+b1
ii  libxml2  2.9.12+dfsg-5
ii  lxmenu-data  0.1.5-2.1
ii  lxpanel-data 0.10.1-2

Versions of packages lxpanel recommends:
ii  libnotify-bin 0.7.9-3
ii  lxterminal [x-terminal-emulator]  0.4.0-1
ii  mlterm [x-terminal-emulator]  3.9.0-1+b1
ii  notification-daemon   3.20.0-4+b1
ii  pavucontrol   5.0-2
ii  xkb-data  2.33-1
ii  xterm [x-terminal-emulator]   369-1

Versions of packages lxpanel suggests:
ii  firefox [www-browser]   94.0-1
ii  google-chrome-stable [www-browser]  95.0.4638.69-1
pn  menu

-- no debconf information



Bug#995443: appears to be fixed in linux-image-5.14.0-3-amd64 (5.14.12-1)

2021-10-19 Thread Dov Feldstern
Hi!

This appears to be fixed in linux-image-5.14.0-3-amd64 (5.14.12-1) --
I had downgraded the kernel back to stable (5.10) until now; now I
just upgraded back to the latest kernel image (though I upgraded the
full system, so possibly the issue was somewhere else rather than the
kernel) and hibernate is now working as expected!

So I think the issue can be closed.

Thanks!
Dov



Bug#995443: linux-image-5.14.0-1-amd64: after waking from hibernate system immediately reboots

2021-10-01 Thread Dov Feldstern
Package: src:linux
Version: 5.14.6-3
Severity: normal

Dear Maintainer,

After upgrading to the 5.14 kernel, waking from hibernation *appears* to
initially succeed (the 10%, 20%, ... is printed to the screen), but then the
system immediately reboots.
If I boot (and then hibernate and then wake) with the previous kernel image
(linux-image-5.10.0-8-amd64), everything works as expected.

Suspend to ram works fine also on 5.14.

Unfortunately, I was not able to glean any useful information from the kernel
logs -- it appears that no information from the failed restoration attempt is
persisted (maybe the problem is somehow related to incorrect filesystem
restoration?). See below in the "Kernel log" section a comparison of the logs
from a successful resotration (on 5.10), versus the logs of a failed
restoration (on 5.14).

Any ideas for how to debug this would be appreciated...

Thanks!
Dov

-- Package-specific info:
** Version:
Linux version 5.14.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.3.0-11) 10.3.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Debian 
5.14.6-3 (2021-09-28)

** Command line:
BOOT_IMAGE=/__active/boot/vmlinuz-5.14.0-1-amd64 
root=UUID=38a750b6-e969-4efc-88b3-0491d0a68241 ro 
rootflags=subvol=__active/rootfs

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

 * Kernel 5.10, successful hibernation and restoration:

Oct  1 12:50:42 jacaranda systemd[1]: Reached target Sleep.
Oct  1 12:50:42 jacaranda systemd[1]: Starting Hibernate...
Oct  1 12:50:42 jacaranda systemd-sleep[1909]: Suspending system...
Oct  1 12:50:42 jacaranda kernel: [   35.634434] PM: hibernation: hibernation 
entry
Oct  1 12:52:03 jacaranda kernel: [   38.500028] Filesystems sync: 2.608 seconds
Oct  1 12:52:03 jacaranda kernel: [   38.500130] Freezing user space processes 
... (elapsed 0.001 seconds) done.
Oct  1 12:52:03 jacaranda kernel: [   38.501698] OOM killer disabled.
Oct  1 12:52:03 jacaranda kernel: [   38.501835] PM: hibernation: Marking 
nosave pages: [mem 0x-0x0fff]
Oct  1 12:52:03 jacaranda kernel: [   38.501836] PM: hibernation: Marking 
nosave pages: [mem 0x000a-0x000f]
Oct  1 12:52:03 jacaranda kernel: [   38.501839] PM: hibernation: Marking 
nosave pages: [mem 0x09e02000-0x09ff]
Oct  1 12:52:03 jacaranda kernel: [   38.501846] PM: hibernation: Marking 
nosave pages: [mem 0x0a20-0x0a20]
Oct  1 12:52:03 jacaranda kernel: [   38.501847] PM: hibernation: Marking 
nosave pages: [mem 0x0b00-0x0b01]
Oct  1 12:52:03 jacaranda kernel: [   38.501849] PM: hibernation: Marking 
nosave pages: [mem 0xd751a000-0xd751cfff]
Oct  1 12:52:03 jacaranda kernel: [   38.501850] PM: hibernation: Marking 
nosave pages: [mem 0xd766-0xd76bcfff]
Oct  1 12:52:03 jacaranda kernel: [   38.501852] PM: hibernation: Marking 
nosave pages: [mem 0xdb347000-0xdddfefff]
Oct  1 12:52:03 jacaranda kernel: [   38.501987] PM: hibernation: Marking 
nosave pages: [mem 0xdf00-0x]
Oct  1 12:52:03 jacaranda kernel: [   38.502495] PM: hibernation: Basic memory 
bitmaps created
Oct  1 12:52:03 jacaranda kernel: [   38.505071] PM: hibernation: Preallocating 
image memory
Oct  1 12:52:03 jacaranda kernel: [   38.951480] PM: hibernation: Allocated 
512157 pages for snapshot
Oct  1 12:52:03 jacaranda kernel: [   38.951588] PM: hibernation: Allocated 
2048628 kbytes in 0.44 seconds (4655.97 MB/s)
Oct  1 12:52:03 jacaranda kernel: [   38.951619] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
Oct  1 12:52:03 jacaranda kernel: [   38.953011] printk: Suspending console(s) 
(use no_console_suspend to debug)
Oct  1 12:52:03 jacaranda kernel: [   38.953249] r8169 :2a:00.0 enp42s0: 
Link is Down
Oct  1 12:52:03 jacaranda kernel: [   38.953361] serial 00:04: disabled
Oct  1 12:52:03 jacaranda kernel: [   39.158263] ACPI: Preparing to enter 
system sleep state S4
Oct  1 12:52:03 jacaranda kernel: [   39.492661] PM: Saving platform NVS memory
Oct  1 12:52:03 jacaranda kernel: [   39.506638] Disabling non-boot CPUs ...
Oct  1 12:52:03 jacaranda kernel: [   39.508275] smpboot: CPU 1 is now offline
Oct  1 12:52:03 jacaranda kernel: [   39.511109] smpboot: CPU 2 is now offline
Oct  1 12:52:03 jacaranda kernel: [   39.513124] smpboot: CPU 3 is now offline
Oct  1 12:52:03 jacaranda kernel: [   39.514833] smpboot: CPU 4 is now offline
Oct  1 12:52:03 jacaranda kernel: [   39.516622] smpboot: CPU 5 is now offline
Oct  1 12:52:03 jacaranda kernel: [   39.518466] smpboot: CPU 6 is now offline
Oct  1 12:52:03 jacaranda kernel: [   39.520115] smpboot: CPU 7 is now offline
Oct  1 12:52:03 jacaranda kernel: [   39.521988] smpboot: CPU 8 is now offline
Oct  1 12:52:03 jacaranda kernel: [   39.523829] smpboot: CPU 9 is now offline
Oct  1 12:52:03 jacaranda kernel: [   39.525447] smpboot: CPU 10 is now offline
Oct  

Bug#894684: python3-virtualenv: missing dependency: python3-distutils ?

2018-04-03 Thread Dov Feldstern
Package: python3-virtualenv
Version: 15.1.0+ds-1
Severity: important

Dear Maintainer,

After a recent upgrade, attempts to create a new virtualenv failed as follows:

  $ virtualenv 
  Traceback (most recent call last):
File "/usr/bin/virtualenv", line 11, in 
  load_entry_point('virtualenv==15.1.0', 'console_scripts', 'virtualenv')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 480, 
in load_entry_point
  return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2693, 
in load_entry_point
  return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2324, 
in load
  return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2330, 
in resolve
  module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python3/dist-packages/virtualenv.py", line 25, in 
  import distutils.sysconfig
  ModuleNotFoundError: No module named 'distutils.sysconfig'

This was solved for me by installing python3-distutils. Perhaps this should be 
a required dependency pf python3-virtualenv?

Thanks!
Dov

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IL.UTF8, LC_CTYPE=en_IL.UTF8 (charmap=UTF-8), LANGUAGE=en_IL:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages python3-virtualenv depends on:
ii  python-pip-whl 9.0.1-2
ii  python33.6.5~rc1-1
ii  python3-pkg-resources  39.0.1-1

python3-virtualenv recommends no packages.

python3-virtualenv suggests no packages.

-- no debconf information



Bug#856645: docker.io: can't install in sid: docker.io 1.11 depends on runc which breaks docker < 1.12

2017-07-02 Thread Dov Feldstern
Indeed, I now have 1.13.1~ds1-2 installed in sid. Thanks!

On Tue, Jun 27, 2017 at 12:39 AM, Antoine Beaupre <anar...@debian.org>
wrote:

> Control: fixed -1 1.13.1~ds1-2
>
> On Fri, Mar 03, 2017 at 11:11:36AM +0200, Dov Feldstern wrote:
> > Current versions of docker.io and runc conflict; docker.io depends on
> runc, but:
> >
> >   runc : Breaks: docker.io (< 1.12) but 1.11.2~ds1-6 is to be installed
>
> I believe this is now fixed: I installed docker.io from sid in stretch
> without problems.
>
> A.
>


Bug#856645: docker.io: can't install in sid: docker.io 1.11 depends on runc which breaks docker < 1.12

2017-03-03 Thread Dov Feldstern
Source: docker.io
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Current versions of docker.io and runc conflict; docker.io depends on runc, but:

  runc : Breaks: docker.io (< 1.12) but 1.11.2~ds1-6 is to be installed

Thanks!

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
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: sysvinit (via /sbin/init)



Bug#808433:

2016-01-25 Thread Dov Feldstern



Bug#810050: kde-telepathy-call-ui: can't install kde-telepathy-call-ui in sid (dependency conflicts)

2016-01-05 Thread Dov Feldstern
Package: kde-telepathy-call-ui
Version: 0.9.0-2+b1
Severity: important

Dear Maintainer,

I am unable to install kde-telepathy-call-ui in sid, installation fails with:

The following packages have unmet dependencies:
 qml-module-org-kde-telepathy : Breaks: kde-telepathy-declarative (< 15.03) but
0.9.0-2 is to be installed.

It seems that perhaps parts of the needed stack (ktp-common-internals) have
been upgraded to version 0.15.x, while others (ktp-call-ui?) are still at
version 0.9.x?

I'm not familiar with kde-telepathy or its debian packaging, so I may be
completely wrong in diagnosing the problem... Any help would be appreciated.

Thanks!
Dov



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-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: sysvinit (via /sbin/init)



Bug#762650: lxpanel: Still seeing the issue with 0.7.2-1

2014-11-02 Thread Dov Feldstern
Package: lxpanel
Version: 0.7.2-1
Followup-For: Bug #762650

Dear Maintainer,

I still seem to be seeing the issue after taking 0.7.2-1 from unstable -- when 
I maximize a window, the bottom part is hidden by the panel; changing the value 
of Reserve space, and not covered by maximized windows in the Advanced tab of 
the Panel Preferences seems to have no effect on this.

Thanks!
Dov

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-2-amd64 (SMP w/8 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 lxpanel depends on:
ii  libasound2  1.0.28-1
ii  libc6   2.19-11
ii  libcairo2   1.12.16-5
ii  libfm-gtk4  1.2.2.1-3
ii  libfm-modules   1.2.2.1-3
ii  libfm4  1.2.2.1-3
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.42.0-2
ii  libgtk2.0-0 2.24.25-1
ii  libiw30 30~pre9-8
ii  libmenu-cache3  1.0.0~rc1-1
ii  libpango-1.0-0  1.36.8-2
ii  libwnck22   2.30.7-2
ii  libx11-62:1.6.2-3
ii  libxml2 2.9.1+dfsg1-4
ii  lxmenu-data 0.1.4-1
ii  lxpanel-data0.7.2-1

Versions of packages lxpanel recommends:
ii  xkb-data  2.12-1

Versions of packages lxpanel suggests:
ii  iceweasel [www-browser]  31.1.0esr-1
ii  lxsession0.4.9.2-1
ii  menu 2.1.47
ii  w3m [www-browser]0.5.3-17

-- 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#762650: lxpanel: Still seeing the issue with 0.7.2-1

2014-11-02 Thread Dov Feldstern
On Sun, Nov 2, 2014 at 11:22 AM, Dov Feldstern dovde...@gmail.com wrote:

 Package: lxpanel
 Version: 0.7.2-1
 Followup-For: Bug #762650

 Dear Maintainer,

 I still seem to be seeing the issue after taking 0.7.2-1 from unstable --
 when I maximize a window, the bottom part is hidden by the panel; changing
 the value of Reserve space, and not covered by maximized windows in the
 Advanced tab of the Panel Preferences seems to have no effect on this.


Ah, apparently the issue has to do with a dual-monitor setup: my panel is
being displayed on monitor 1, but the space for it was being reserved on
monitor 2. I see a panel setting that allows me to move the panel itself to
monitor 2, so that now the space is reserved as expected. However, If I
really want the monitor (and, presumably, the space reserved for it) to be
on monitor 1, I don't see how that can be done.

Not sure whether you want to reopen this issue, or file a new one...


Bug#766059:

2014-10-21 Thread Dov Feldstern
Turns out that 'pulseaudio-module-jack' is *not* necessary -- after
adding my user to the 'audio' group I'm getting sound even without it
installed :/ .

However, it does still appear that 'gstreamer0.10-plugins-bad' is
necessary, so I think that part of the bug report is still valid...

Sorry for the noise!
Dov


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



Bug#766059: radiotray: missing dependencies (in jessie)

2014-10-20 Thread Dov Feldstern
Package: radiotray
Version: 0.7.3-2
Severity: normal

Dear Maintainer,

Starting with a rather minimal installation of jessie with lxde, radiotray
would seem to play (based on the systemtray icon), but no sound could be heard.
Ultimately, it turns out there were two separate issues, which were solved by
installing these two packages:

  1. pulseaudio-module-jack
  2. gstreamer0.10-plugins-bad

The first issue seems to be the same issue as reported at [1] for banshee: when
started from the command line, gstreamer keeps emitting

Cannot connect to server request channel
jack server is not running or cannot be started

Installing pulseaudio-module-jack, as suggested there, solves this issue.

The second issue seems to be the same as [2]: it manifests as an error
notification:

Radio Error gstplaysink.c(1906): gen_audio_chain ():
/GstPlayBin2:player/GstPlaySink:playsink0

Installing gstreamer0.10-plugins-bad, as suggested in [3] (linked to from [2])
solves the problem.

Thanks!
Dov

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727062
[2] http://unix.stackexchange.com/questions/51882/radiotray-error-gstplaysink
[3] http://ubuntuforums.org/showthread.php?t=2055871p=12230252#post12230252


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-2-amd64 (SMP w/8 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 radiotray depends on:
ii  gstreamer0.10-plugins-base  0.10.36-2
ii  gstreamer0.10-plugins-good  0.10.31-3+nmu4
ii  gstreamer0.10-plugins-ugly  0.10.19-2.1
ii  python  2.7.8-1
ii  python-dbus 1.2.0-2+b3
ii  python-glade2   2.24.0-4
ii  python-gobject  3.14.0-1
ii  python-gst0.10  0.10.22-3
ii  python-gtk2 2.24.0-4
ii  python-lxml 3.4.0-1
ii  python-notify   0.1.1-3
ii  python-xdg  0.25-4

radiotray recommends no packages.

radiotray 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#766059:

2014-10-20 Thread Dov Feldstern
Hmmm... after a reboot I'm getting the error message about jack
server is not running or cannot be started again, even though
pulseaudio-module-jack *is* now installed, so I'm not sure what
exactly is going on here...


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



Bug#740088:

2014-09-22 Thread Dov Feldstern
Was a bug ever opened for this upstream? I was not able to find it...

(still seeing this issue in jessie)

Thanks!
Dov


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



Bug#740163: lxsession: lxlock/dm-tool lock is easily circumvented

2014-09-18 Thread Dov Feldstern
This seems to have been fixed upstream last November (by not using
dm-tool for locking anymore):

https://github.com/lxde/lxsession/commit/9dfe4035a6b555452046db7d4e430507d7c0e469


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



Bug#724490: vit: help accesses /usr/etc/vit-commands, but help file is at /etc/vit-commands

2013-09-24 Thread Dov Feldstern
Package: vit
Version: 1.1-1
Severity: normal

Dear Maintainer,

When attempting to access vit help (:help command), vit opens
/usr/etc/vit-commands, which does not exist, and therefore no help is
displayed.

In fact, dpkg -L shows that the file is placed by the package at
/etc/vit-commands (*not* under /usr).

Thanks!
Dov


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.10-3-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages vit depends on:
ii  libcurses-perl  1.28-1+b3
ii  perl5.18.1-4
ii  task2.2.0-3

vit recommends no packages.

vit suggests no packages.

-- no debconf information


Bug#689704: arista: most presets require faac, but that isn't found

2012-10-05 Thread Dov Feldstern
Package: arista
Version: 0.9.7-4
Severity: normal
Tags: patch

Dear Maintainer,

I'm using a clean install of arista (only just installed now, no preexsiting
..arista/ directory in my $HOME). Attempt a transcoding using the gui: start
arista-gtk - Create Conversion - choose the source and destination, and
the N900 MPEG preset - Create.

At this point, I expect the transcoding to begin. What actually happens is
a Search for suitable plugin? window pops up, and the message 
arista.presets [435]: INFO Attempting to install elements: faac
is printed to the console. Regardless of whether I search or just cancel,
ultimately the conversion fails because of missing elements (in the console:
arista.presets [444]: ERROR Unable to install required elements!).

While googling this, I came across a discussion from mageia [1], which seems
to be the same issue I'm observing, and where they explain that faac is
problematic in that it is both non-free and tainted (not sure if this
terminology applies to debian, as well?). At the very end of the thread,
Christiaan Welvaart mentions having uploaded a patched arista, which uses the
unencumbered vo-aacenc package instead of faac. Further googling produced what
appears to be the mentioned patch [2]. Applying that patch to the current tip
of arista from github indeed fixes the problem (the presets have to be reset
with the patched arista, as per Christiaan's message). Once the presets have
been reset, the transcoding even works with debian's arista (i.e., the changes
are only to the code which generates the presets, I guess).

As far as I can tell, this has not been reported upstream, and I'm not sure
whether or not it should be, or whether this a problem of the distributions
(mageia, and also debian?).

Thanks!
Dov

[1] http://comments.gmane.org/gmane.linux.mageia.devel/16460
[2] 
http://sophie.zarb.org/distrib/Mageia/cauldron/i586/by-pkgid/f53eb919643c7b5ac76579ce7e7a4377/files/1

-- System Information:
Debian Release: wheezy/sid
Architecture: i386 (i686)

Kernel: Linux 3.2.0-3-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages arista depends on:
ii  gnome-icon-theme3.4.0-2
ii  gstreamer0.10-ffmpeg0.10.13-5
ii  gstreamer0.10-plugins-base  0.10.36-1
ii  gstreamer0.10-plugins-good  0.10.31-3
ii  lxde-icon-theme 0.5.0-1
ii  python  2.7.3-2
ii  python-cairo1.8.8-1+b2
ii  python-dbus 1.1.1-1
ii  python-gconf2.28.1+dfsg-1
ii  python-gobject  3.2.2-1
ii  python-gst0.10  0.10.22-3
ii  python-gtk2 2.24.0-3
ii  python-gudev147.2-3
ii  python-simplejson   2.6.1-1
ii  python2.6   2.6.8-0.2
ii  python2.7   2.7.3-5

Versions of packages arista recommends:
ii  gnome-codec-install 0.4.7+nmu1
ii  gstreamer0.10-plugins-bad   0.10.23-7
ii  gstreamer0.10-plugins-ugly  0.10.19-2+b2

Versions of packages arista suggests:
ii  python-notify  0.1.1-3
ii  python-webkit  1.1.8-2

-- 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