Bug#1080525: instaloader: cannot load IG pictures, need browser-cookies3 library

2024-09-05 Thread Eric Cooper
Package: instaloader
Version: 4.12.1+ds-1
Severity: normal

Attempts to download photos from IG fail with "Fetching Post metadata failed.".

A similar problem with downloading videos using yt-dlp was solved
using its --cookies-from-browser option, so I think that will solve
this issue too, but it's too difficult for me install a 3rd party
Python library on my system to check.

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

Kernel: Linux 6.9.9-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages instaloader depends on:
ii  python3   3.12.5-1
ii  python3-requests  2.31.0+dfsg-2

instaloader recommends no packages.

instaloader suggests no packages.

-- no debconf information



Bug#1052591: openscad: Preview renders garbage at difference-planes

2023-09-24 Thread Eric Cooper
Package: openscad
Version: 2021.01-6
Severity: important

Dear Maintainer,

When I open this SCAD source:

difference() {
cube([10, 10, 10], center = true);
cube([5, 5, 10], center = true);
}

the preview shows garbage in the "openings" created by the difference
operation. The display of the garbage changes as I rotate or zoom the
view.

To get rid of the garbage completely, I have to do a full render. That
is very time-consuming on a larger model, whereas the garbage effect makes
previewing almost useless, so I rated this severity "important".

The bug is independent of the objects being differenced.
It occurs when there is exact co-planarity of
a face of A and a face of B in
difference() { A; B; }

-- Package-specific info:
Output of /usr/share/bug/openscad:
$ glxinfo |grep 'OpenGL .* string:'
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 5700 XT (navi10, LLVM 15.0.7, DRM 3.52, 
6.4.0-4-amd64)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.1.6-1
OpenGL core profile shading language version string: 4.60
OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.1.6-1
OpenGL shading language version string: 4.60
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.1.6-1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

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

Kernel: Linux 6.4.0-4-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openscad depends on:
ii  lib3mf11.8.1+ds-4
ii  libboost-filesystem1.74.0  1.74.0+ds1-22
ii  libboost-program-options1.74.0 1.74.0+ds1-22
ii  libboost-regex1.74.0 [libboost-regex1.74.0-icu72]  1.74.0+ds1-22
ii  libc6  2.37-7
ii  libcairo2  1.17.8-3
ii  libdouble-conversion3  3.3.0-1
ii  libfontconfig1 2.14.2-5
ii  libfreetype6   2.13.2+dfsg-1
ii  libgcc-s1  13.2.0-2
ii  libgl1 1.6.0-1
ii  libglew2.2 2.2.0-4+b1
ii  libglib2.0-0   2.78.0-1
ii  libglu1-mesa [libglu1] 9.0.2-1.1
ii  libgmp10   2:6.3.0+dfsg-2
ii  libharfbuzz0b  8.0.1-1
ii  libmpfr6   4.2.0-1
ii  libopencsg11.5.0-1+b1
ii  libqscintilla2-qt5-15  2.14.1+dfsg-1
ii  libqt5core5a   5.15.10+dfsg-3
ii  libqt5dbus55.15.10+dfsg-3
ii  libqt5gamepad5 5.15.10-2
ii  libqt5gui5 5.15.10+dfsg-3
ii  libqt5multimedia5  5.15.10-2
ii  libqt5network5 5.15.10+dfsg-3
ii  libqt5widgets5 5.15.10+dfsg-3
ii  libspnav0  1.1-1
ii  libstdc++6 13.2.0-2
ii  libx11-6   2:1.8.6-1
ii  libxml22.9.14+dfsg-1.3
ii  libzip41.7.3-1+b1

Versions of packages openscad recommends:
ii  openscad-mcad  2019.05-1

Versions of packages openscad suggests:
pn  geomview  
pn  librecad  
pn  meshlab   
pn  openscad-testing  

-- no debconf information



Bug#1030189: Let regular users know need to put non-free-firmware in sources.list

2023-02-02 Thread Eric Cooper
On Wed, Feb 1, 2023 at 3:36 PM Sven Joachim  wrote:
> The release notes for Bookworm should and will certainly mention that.
> I think this is where this bug is actually actionable, so I am
> reassigning it there.
>
> > Yes, he should be regularly subscribed to debian-user, but that's too
> > much.
>
> I have sent a heads-up message[1] there a few days ago, but as you said it
> got lost in all the other topics discussed there.
>
> > Or https://lists.debian.org/debian-announce/, but that's too many boring
> > messages too.
>
> There was not even a prominent notice there, at least not in the past
> few weeks.
>
> > Yes, he uses apt-listchanges, but that won't tell him this.
> >
> > So I'm saying that Debian needs a mechanism to have his computer tell
> > him to do this.
> >
> > Maybe the next time he uses apt*, somehow the system should tell him...
>
> Somehow, but how exactly?  Good question that was brought up on
> debian-devel[2], alas without replies yet.

I got bitten by this, and only noticed it when my system's firmware
packages showed up in the output of "apt list ~g".
I'm sure I'm missing something, but why weren't transitional packages left
in non-free that depend on the new versions in non-free-firmware? Perhaps
they could also depend on a source-list-modifying package so the next
upgrade doesn't break.


Bug#1020242: wireplumber: volume on default sink is too high after waking from suspend

2022-09-18 Thread Eric Cooper
Package: wireplumber
Version: 0.4.11-5
Severity: normal

I'm not sure wireplumber is at fault here, but this has only started
happening since I switched from pulseaudio to pipewire a few days ago.
I usually have my default volume at about 30%, according to
pavucontrol. But when I wake my computer up after it suspends due to
inactivity, the volume is much higher, around 75%.

It doesn't happen when I manually suspend the computer though, at
least not when I wake it after a few seconds.

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

Kernel: Linux 5.19.0-1-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wireplumber depends on:
ii  init-system-helpers   1.64
ii  libc6 2.34-7
ii  libglib2.0-0  2.73.3-3
ii  libpipewire-0.3-0 0.3.57-1
ii  libwireplumber-0.4-0  0.4.11-5
ii  pipewire  0.3.57-1

Versions of packages wireplumber recommends:
ii  pipewire-pulse  0.3.57-1

Versions of packages wireplumber suggests:
pn  libspa-0.2-bluetooth  
pn  wireplumber-doc   

-- no debconf information



Bug#1019554: anacron: Anacron no longer seems to execute jobs

2022-09-17 Thread Eric Cooper
Package: anacron
Version: 2.3-34
Followup-For: Bug #1019554

Anacron seems to be failing for me recently also.
But in my case, an additional factor has changed (besides the new
version of anacron): I recently changed my power management settings
to suspend my computer when idle.

I have a backup script in root's crontab (set using "crontab -e") that
is supposed to run every night at 2am. Now the computer is asleep at
that hour, and the script does not get run any time the next day
either when the computer is awake.

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

Kernel: Linux 5.19.0-1-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages anacron depends on:
ii  libc6 2.34-7
ii  lsb-base  11.2

Versions of packages anacron recommends:
ii  cron [cron-daemon]  3.0pl1-149

Versions of packages anacron suggests:
ii  dma [mail-transport-agent]   0.13-1+b1
ii  powermgmt-base   1.37
ii  rsyslog [system-log-daemon]  8.2208.0-1

-- no debconf information



Bug#1011085: quassel-client: please remember GUI settings like width of channel list and nick list

2022-05-16 Thread Eric Cooper
Package: quassel-client
Version: 1:0.14.0-1+b1
Severity: wishlist

I have to adjust the width of these columns each time I start quassel-client.
Please store them in the config directory automatically, or allow them to be
specified in the settings.

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

Kernel: Linux 5.17.0-1-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages quassel-client depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.14.0-1
ii  dbus-x11 [dbus-session-bus]   1.14.0-1
ii  libc6 2.33-7
ii  libdbusmenu-qt5-2 0.9.3+16.04.20160218-2+b1
ii  libgcc-s1 12.1.0-1
ii  libkf5configwidgets5  5.90.1-4
ii  libkf5coreaddons5 5.90.0-1
ii  libkf5notifications5  5.90.0-1
ii  libkf5notifyconfig5   5.90.0-1
ii  libkf5sonnetui5   5.90.0-1
ii  libkf5textwidgets55.90.0-1
ii  libkf5widgetsaddons5  5.90.0-1
ii  libkf5xmlgui5 5.90.0-1
ii  libqt5core5a  5.15.2+dfsg-16+b1
ii  libqt5dbus5   5.15.2+dfsg-16+b1
ii  libqt5gui55.15.2+dfsg-16+b1
ii  libqt5multimedia5 5.15.2-3
ii  libqt5network55.15.2+dfsg-16+b1
ii  libqt5webenginewidgets5   5.15.8+dfsg-1+b2
ii  libqt5widgets55.15.2+dfsg-16+b1
ii  libstdc++612.1.0-1
ii  quassel-data  1:0.14.0-1
ii  zlib1g1:1.2.11.dfsg-4

quassel-client recommends no packages.

quassel-client suggests no packages.

-- no debconf information



Bug#1010673: quassel-client: "Layout engine couldn't workaround Qt bug 238249, please report!"

2022-05-06 Thread Eric Cooper
Package: quassel-client
Version: 1:0.14.0-1+b1
Severity: normal

I'm running Gnome with Wayland.
I get a screenful of these warnings when I have QT_QPA_PLATFORM=xcb.
When I have QT_QPA_PLATFORM=wayland, I get the warnings but the window never 
appears.

I also have these env vars set:
QT_ACCESSIBILITY=1
QT_QPA_PLATFORMTHEME=qt5ct

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

Kernel: Linux 5.17.0-1-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages quassel-client depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.14.0-1
ii  dbus-x11 [dbus-session-bus]   1.14.0-1
ii  libc6 2.33-7
ii  libdbusmenu-qt5-2 0.9.3+16.04.20160218-2+b1
ii  libgcc-s1 12-20220428-1
ii  libkf5configwidgets5  5.90.1-4
ii  libkf5coreaddons5 5.90.0-1
ii  libkf5notifications5  5.90.0-1
ii  libkf5notifyconfig5   5.90.0-1
ii  libkf5sonnetui5   5.90.0-1
ii  libkf5textwidgets55.90.0-1
ii  libkf5widgetsaddons5  5.90.0-1
ii  libkf5xmlgui5 5.90.0-1
ii  libqt5core5a  5.15.2+dfsg-16+b1
ii  libqt5dbus5   5.15.2+dfsg-16+b1
ii  libqt5gui55.15.2+dfsg-16+b1
ii  libqt5multimedia5 5.15.2-3
ii  libqt5network55.15.2+dfsg-16+b1
ii  libqt5webenginewidgets5   5.15.8+dfsg-1+b2
ii  libqt5widgets55.15.2+dfsg-16+b1
ii  libstdc++612-20220428-1
ii  quassel-data  1:0.14.0-1
ii  zlib1g1:1.2.11.dfsg-4

quassel-client recommends no packages.

quassel-client suggests no packages.

-- no debconf information



Bug#1008113: ubertooth: please update to latest upstream version (2020-12-R1)

2022-03-22 Thread Eric Cooper
Package: ubertooth
Version: 2018.12.R1-5
Severity: wishlist

Please update ubertooth and related packages to the latest upstream release.

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

Kernel: Linux 5.16.0-3-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ubertooth depends on:
ii  libbluetooth3  5.62-2
pn  libbtbb1   
ii  libc6  2.33-7
pn  libubertooth1  
ii  libusb-1.0-0   2:1.0.25-1
ii  python33.9.8-1
ii  python3-numpy  1:1.21.5-1

Versions of packages ubertooth recommends:
pn  python3-pyside2.qtcore 
pn  python3-pyside2.qtgui  
pn  python3-pyside2.qtwidgets  
pn  ubertooth-firmware 

Versions of packages ubertooth suggests:
pn  ubertooth-firmware-source  



Bug#1005999: gimp: overwriting existing PDF file does not preserve layers as pages

2022-02-18 Thread Eric Cooper
Package: gimp
Version: 2.10.30-1
Severity: normal

1. Open a multi-page PDF file, with pages as layers.
2. Choose the "File > Overwrite foo.pdf" option.
3. No option to save layers as pages was offered, and foo.pdf now contains only 
one page.

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gimp depends on:
ii  gimp-data2.10.30-1
ii  graphviz 2.42.2-6
ii  libaa1   1.4p5-50
ii  libbabl-0.1-01:0.1.88-1
ii  libbz2-1.0   1.0.8-5
ii  libc62.33-5
ii  libcairo21.16.0-5
ii  libfontconfig1   2.13.1-4.4
ii  libfreetype6 2.11.1+dfsg-1
ii  libgcc-s111.2.0-16
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libgegl-0.4-01:0.4.34-1
ii  libgexiv2-2  0.14.0-1
ii  libgimp2.0   2.10.30-1
ii  libglib2.0-0 2.70.4-1
ii  libgs9   9.55.0~dfsg-3
ii  libgtk2.0-0  2.24.33-2
ii  libgudev-1.0-0   237-2
ii  libharfbuzz0b2.7.4-1
ii  libheif1 1.12.0-2+b3
ii  libilmbase25 2.5.7-2
ii  libjpeg62-turbo  1:2.1.2-1
ii  libjson-glib-1.0-0   1.6.6-1
ii  liblcms2-2   2.12~rc1-2
ii  liblzma5 5.2.5-2
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.5-1 1.6.0-2
ii  libopenexr25 2.5.7-1
ii  libopenjp2-7 2.4.0-6
ii  libpango-1.0-0   1.50.3+ds1-6
ii  libpangocairo-1.0-0  1.50.3+ds1-6
ii  libpangoft2-1.0-01.50.3+ds1-6
ii  libpng16-16  1.6.37-3
ii  libpoppler-glib8 20.09.0-3.1
ii  librsvg2-2   2.52.5+dfsg-3+b1
ii  libstdc++6   11.2.0-16
ii  libtiff5 4.3.0-4
ii  libwebp6 0.6.1-2.1
ii  libwebpdemux20.6.1-2.1
ii  libwebpmux3  0.6.1-2.1
ii  libwmf0.2-7  0.2.12-5
ii  libx11-6 2:1.7.2-2+b1
ii  libxcursor1  1:1.2.0-2
ii  libxext6 2:1.3.4-1
ii  libxfixes3   1:6.0.0-1
ii  libxmu6  2:1.1.2-2+b3
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-4.1
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages gimp recommends:
ii  ghostscript  9.55.0~dfsg-3

Versions of packages gimp suggests:
pn  gimp-data-extras  
pn  gimp-help-en | gimp-help  
pn  gvfs-backends 
ii  libasound21.2.6.1-1

-- no debconf information



Bug#1005998: reportbug: cli version of reportbug crashes with Python IndexError

2022-02-18 Thread Eric Cooper
Package: reportbug
Version: 11.4.0
Severity: important

$ reportbug gimp
Warning: no reportbug configuration found.  Proceeding in novice mode.
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Eric Cooper ' as your from address.
Getting status for gimp...
Verifying package integrity...
Checking for newer versions at madison...

Your version (2.10.30-1) of gimp appears to be out of date.
The following newer release(s) are available in the Debian archive:
  unstable: 2.10.30-1+b1
Please try to verify if the bug you are about to report is already addressed by 
these releases.  Do you still want to file a report [y|N|q|?]? y
Will send report to Debian (per lsb_release).
Querying Debian BTS for reports on gimp src:gimp...
144 bug reports found:

Bugs with severity important
1)  #672894  gimp: toolbox window hangs in endless loop
2)  #682705  gimp 2nd level dialogs freeze
3)  #872419  gimp: Toolbox icons missed
4)  #902852  gimp: Crashes when trying to save a new animated gif, instant 
crash on recovery
5)  #918815  gimp: fatal error: speicherzugriffsfehler (gimp crash debug)
6)  #920205  gimp: Hangs at startup trying to show toolbox window
7)  #923452  gimp: fails with segfault when trying to change theme
8)  #926797  gimp: with KDE plasma 5.14 ( buster)  menus  are in mode 
transparency, so they are
9)  #928137  gimp: all Alpha layers are corrupted - vertical bars
   10)  #946714  gimp: GIMP crashed with a fatal error when a was editing an 
image
   11)  #949592  gimp crashes on startup
   12)  #952440  gimp: crashes on Edit then Copy
   13)  #953363  gimp: file dialogues use black font on black background
   14)  #954739  gimp: GIMP crashed with a fatal error: fatal error: 
Segmentation fault
   15)  #959235  gimp GUI font missing
   16)  #968005  gimp: install the application well, it did not give any error 
but when executing i
   17)  #979192  gimp: Just crashed when i clicked on the top of the gimp 
window bar
   18)  #988351  gimp crashes when copyq is running and i copy something from 
gimp to clipboard
   19)  #992109  gimp: save/export window doesn't popup
   20)  #992293  gimp: Can't select invert, crashing, lagging
(1-20/144) Is the bug you found listed above [y|N|b|m|r|q|s|f|e|?]? f
Enter the search pattern (a Perl-compatible regular expression)
or press ENTER to exit: pdf
 Bugs with severity minor: 2 reports
  1)  #525077  gimp stole .ps and .pdf associations in GNOME with lenny->sid 
upgrade
  2)  #759704  pcmanfm opens gimp instead of okular to view a PDF file

 Bugs with severity wishlist: 1 report
  3)  #499813  gimp: please allow saving multi-page PDFs
(1-3/3) Is the bug you found listed above [y|N|b|m|r|q|s|f|u|t|e|?]? y
Enter the number of the bug report you want to give more info on,
or press ENTER to exit: #3
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2356, in 
main()
  File "/usr/bin/reportbug", line 1090, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 1766, in user_interface
exinfo = ui.handle_bts_query(pkg, bts, self.options.timeout,
  File "/usr/lib/python3/dist-packages/reportbug/ui/text_ui.py", line 604, in 
handle_bts_query
return browse_bugs(hierarchy, count, bugs, bts, queryonly,
  File "/usr/lib/python3/dist-packages/reportbug/ui/text_ui.py", line 728, in 
browse_bugs
retval = search_bugs(hierarchy, bts, queryonly, mirrors, http_proxy, 
timeout, screen, title,
  File "/usr/lib/python3/dist-packages/reportbug/ui/text_ui.py", line 936, in 
search_bugs
return debbugs.get_report(number, timeout)[0]
  File "/usr/lib/python3/dist-packages/reportbug/debbugs.py", line 1204, in 
get_report
status = debianbts.get_status([number])[0]
IndexError: list index out of range

-- Package-specific info:
** Environment settings:
EDITOR="/home/ecc/bin/fastemacs"
PAGER="less"

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages reportbug depends on:
ii  apt2.3.15
ii  python33.9.8-1
ii  python3-reportbug  11.4.0
ii  sensible-utils 0.0.17

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail  
ii  debconf 1.5.79
ii  debsums 3.0.2
ii  dlocate 1.10
ii  dma [mail-transport-agent]  0.13-1
ii  emacs-bin-common1:27.1+1-3.1+b1
ii  file1:5.41-2
ii  gnupg  

Bug#1005712: hackrf_info prints "unknown" for version info

2022-02-13 Thread Eric Cooper
Package: hackrf
Version: 2021.03.1-2
Severity: normal

$ hackrf_info
hackrf_info version: unknown
libhackrf version: unknown (0.6)
Found HackRF
Index: 0
Serial number: 
Board ID Number: 2 (HackRF One)
Firmware Version: 2021.03.1 (API:1.04)
Part ID Number: 

It looks like this definition in host/cmake/set_release.cmake
set(RELEASE "2021.03.1")
is not being used when hackrf_info gets built.

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages hackrf depends on:
ii  libc6 2.33-5
ii  libfftw3-single3  3.3.8-2
ii  libhackrf02021.03.1-2

hackrf recommends no packages.

hackrf suggests no packages.

-- no debconf information



Bug#1004711: gimp uses ebook-viewer (from calibre package) for print preview

2022-02-02 Thread Eric Cooper
On Tue, Feb 1, 2022 at 3:37 PM Simon McVittie  wrote:

> If you're using a specific desktop environment, then
> that desktop environment should be installing its own
> opinionated, per-desktop-environment configuration in
> /usr/share/applications/$desktop-mimeapps.list, like GNOME does.
> Which desktop environment are you using?


I'm using xfce4. It does not ship or create any mimeapps.list file. I'll
try experimenting with my own ~/.config/mimeapps.list.


Bug#1004711: gimp uses ebook-viewer (from calibre package) for print preview

2022-02-01 Thread Eric Cooper
Thanks for this explanation. Unfortunately, I still can't find any place
that's specifying ebook-viewer (or any PDF viewer, for that matter) among
the various files you listed (none of which I've modified myself).

I purged calibre and tried the print preview again. Oddly, gimp still did
not use mupdf, it used itself: it popped up the "import pdf" dialog for the
pdf it was going to print, and opened a new (gimp) window for it.

On Tue, Feb 1, 2022 at 5:22 AM Simon McVittie  wrote:

> On Mon, 31 Jan 2022 at 18:36:11 -0500, Eric Cooper wrote:
> > I have both mupdf and calibre installed. When I choose File > Print,
> > and then Print Preview, gimp launches the ebook-viewer program from
> > calibre rather than mupdf, which appears before ebook-viewer in
> > /etc/mailcap (if that matters).
>
> The command used for print previews in GTK 2 comes from your GTK theme
> (for historical reasons) or from gtkrc (several locations are searched,
> ~/.gtkrc-2.0 is the highest-priority).
>
> Neither ebook-viewer nor mupdf is hard-coded anywhere in GTK or GIMP.
> The only hard-coded command related to print previews is GNOME's evince,
> which is used as a default if nothing else is configured.
>
> Rather than /etc/mailcap, it is more likely that the print preview is
> using your configured default PDF viewer according to this freedesktop.org
> specification:
> https://specifications.freedesktop.org/mime-apps-spec/latest/
>
> You can configure the preferred PDF viewer for each user via
> ~/.config/mimeapps.list, or system-wide via /etc/xdg/mimeapps.list.
>
> In a well-integrated desktop environment, defaults for several
> commonly-used
> applications are in /usr/share/applications/DESKTOP-mimeapps.list, where
> DESKTOP is the value of $XDG_CURRENT_DESKTOP transformed to lower-case.
> For example, the GNOME desktop environment uses XDG_CURRENT_DESKTOP=GNOME,
> and installs /usr/share/applications/gnome-mimeapps.list via the
> gnome-session-common package.
>
> /etc/mailcap is no longer used by most libraries and applications. It's
> generated from freedesktop.org .desktop files by the update-mime command
> for compatibility with libraries and applications that still use it,
> but for historical reasons it has its own preference order.
>
> smcv
>


Bug#1004711: gimp uses ebook-viewer (from calibre package) for print preview

2022-01-31 Thread Eric Cooper
Package: gimp
Version: 2.10.30-1
Severity: normal

I have both mupdf and calibre installed. When I choose File > Print,
and then Print Preview, gimp launches the ebook-viewer program from
calibre rather than mupdf, which appears before ebook-viewer in
/etc/mailcap (if that matters).

Here's an example of what it runs:
/usr/bin/python3.9 /usr/bin/ebook-viewer /tmp/previewGA5NG1.pdf

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gimp depends on:
ii  gimp-data2.10.30-1
ii  graphviz 2.42.2-5+b1
ii  libaa1   1.4p5-50
ii  libbabl-0.1-01:0.1.88-1
ii  libbz2-1.0   1.0.8-5
ii  libc62.33-5
ii  libcairo21.16.0-5
ii  libfontconfig1   2.13.1-4.3
ii  libfreetype6 2.11.1+dfsg-1
ii  libgcc-s111.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libgegl-0.4-01:0.4.34-1
ii  libgexiv2-2  0.14.0-1
ii  libgimp2.0   2.10.30-1
ii  libglib2.0-0 2.70.3-1
ii  libgs9   9.55.0~dfsg-3
ii  libgtk2.0-0  2.24.33-2
ii  libgudev-1.0-0   237-2
ii  libharfbuzz0b2.7.4-1
ii  libheif1 1.12.0-2+b3
ii  libilmbase25 2.5.7-2
ii  libjpeg62-turbo  1:2.1.2-1
ii  libjson-glib-1.0-0   1.6.6-1
ii  liblcms2-2   2.12~rc1-2
ii  liblzma5 5.2.5-2
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.5-1 1.6.0-2
ii  libopenexr25 2.5.7-1
ii  libopenjp2-7 2.4.0-6
ii  libpango-1.0-0   1.50.3+ds1-4
ii  libpangocairo-1.0-0  1.50.3+ds1-4
ii  libpangoft2-1.0-01.50.3+ds1-4
ii  libpng16-16  1.6.37-3
ii  libpoppler-glib8 20.09.0-3.1
ii  librsvg2-2   2.52.5+dfsg-3+b1
ii  libstdc++6   11.2.0-14
ii  libtiff5 4.3.0-3
ii  libwebp6 0.6.1-2.1
ii  libwebpdemux20.6.1-2.1
ii  libwebpmux3  0.6.1-2.1
ii  libwmf0.2-7  0.2.8.4-17+b1
ii  libx11-6 2:1.7.2-2+b1
ii  libxcursor1  1:1.2.0-2
ii  libxext6 2:1.3.4-1
ii  libxfixes3   1:5.0.3-2
ii  libxmu6  2:1.1.2-2+b3
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-4.1
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages gimp recommends:
ii  ghostscript  9.55.0~dfsg-3

Versions of packages gimp suggests:
pn  gimp-data-extras  
pn  gimp-help-en | gimp-help  
pn  gvfs-backends 
ii  libasound21.2.6.1-1

-- no debconf information



Bug#994429: gimp: missing SANE option under File > Create menu

2021-09-17 Thread Eric Cooper
On Thu, Sep 16, 2021 at 11:39:55AM +0200, Bernhard Übelacker wrote:
> Dear Maintainer,
> this might be the same as reported
> in #993293 against the xsane package.
>
> Kind regards,
> Bernhard
>
> https://bugs.debian.org/993293

I downgraded xsane and xsane-common to 0.999-10 and this fixes my
problem, so I think this confirms Bernhard's idea.

--
Eric Cooper e c c @ c m u . e d u



Bug#994429: gimp: missing SANE option under File > Create menu

2021-09-15 Thread Eric Cooper
Package: gimp
Version: 2.10.26-1
Severity: normal

I have both xsane and xsane-common installed, but there is no longer
an option to use SANE under the Create menu.

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

Kernel: Linux 5.10.0-8-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gimp depends on:
ii  gimp-data2.10.26-1
ii  graphviz 2.42.2-5
ii  libaa1   1.4p5-50
ii  libbabl-0.1-01:0.1.88-1
ii  libbz2-1.0   1.0.8-4
ii  libc62.31-17
ii  libcairo21.16.0-5
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgcc-s111.2.0-4
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libgegl-0.4-01:0.4.32-1
ii  libgexiv2-2  0.12.1-1
ii  libgimp2.0   2.10.26-1
ii  libglib2.0-0 2.68.4-1
ii  libgs9   9.53.3~dfsg-7+b1
ii  libgtk2.0-0  2.24.33-2
ii  libgudev-1.0-0   237-2
ii  libharfbuzz0b2.7.4-1
ii  libheif1 1.12.0-2+b1
ii  libilmbase25 2.5.7-1
ii  libjpeg62-turbo  1:2.0.6-4
ii  libjson-glib-1.0-0   1.6.6-1
ii  liblcms2-2   2.12~rc1-2
ii  liblzma5 5.2.5-2
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.5-1 1.6.0-2
ii  libopenexr25 2.5.7-1
ii  libopenjp2-7 2.4.0-3
ii  libpango-1.0-0   1.48.9+ds1-2
ii  libpangocairo-1.0-0  1.48.9+ds1-2
ii  libpangoft2-1.0-01.48.9+ds1-2
ii  libpng16-16  1.6.37-3
ii  libpoppler-glib8 20.09.0-3.1
ii  librsvg2-2   2.50.3+dfsg-1
ii  libstdc++6   11.2.0-4
ii  libtiff5 4.2.0-1
ii  libwebp6 0.6.1-2.1
ii  libwebpdemux20.6.1-2.1
ii  libwebpmux3  0.6.1-2.1
ii  libwmf0.2-7  0.2.8.4-17+b1
ii  libx11-6 2:1.7.2-1
ii  libxcursor1  1:1.2.0-2
ii  libxext6 2:1.3.3-1.1
ii  libxfixes3   1:5.0.3-2
ii  libxmu6  2:1.1.2-2+b3
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-4.1
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages gimp recommends:
ii  ghostscript  9.53.3~dfsg-7+b1

Versions of packages gimp suggests:
pn  gimp-data-extras  
pn  gimp-help-en | gimp-help  
pn  gvfs-backends 
ii  libasound21.2.5.1-1

-- no debconf information



Bug#994417: libvte-2.91-0: underscore character from DejaVu Sans Mono is invisible on last line

2021-09-15 Thread Eric Cooper
Package: libvte-2.91-0
Version: 0.64.2-2
Severity: normal

Underscore characters in the bottom line of a terminal window using
libvte are not shown when the font is DejaVu Sans Mono (at least for
10, 11, and 12 point size).  Both xfce4-terminal and
gnome-terminal exhibit this.

Downgrading to version 0.62.3-1 of libvte and libvte-common fixes the
problem.

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

Kernel: Linux 5.10.0-8-amd64 (SMP w/32 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libvte-2.91-0 depends on:
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-17
ii  libcairo21.16.0-5
ii  libfribidi0  1.0.8-2
ii  libgcc-s111.2.0-4
ii  libglib2.0-0 2.68.4-1
ii  libgnutls30  3.7.2-2
ii  libgtk-3-0   3.24.30-3
ii  libicu67 67.1-7
ii  libpango-1.0-0   1.48.9+ds1-2
ii  libpangocairo-1.0-0  1.48.9+ds1-2
ii  libpcre2-8-0 10.36-2
ii  libstdc++6   11.2.0-4
ii  libsystemd0  247.9-1
ii  libvte-2.91-common   0.64.2-2
ii  zlib1g   1:1.2.11.dfsg-2

libvte-2.91-0 recommends no packages.

libvte-2.91-0 suggests no packages.

-- no debconf information



Bug#989663: ferm --remote --slow does not produce deterministic output

2021-06-09 Thread Eric Cooper
Package: ferm
Version: 2.5.1-1
Severity: normal

Running "ferm --remote --slow" produces iptables rules in different
orders on different runs. This makes it difficult to compare outputs
for regression testing, version control, etc.

For example, on two successive runs this input produced the following
output:
table filter {
chain INPUT policy DROP;
chain FORWARD policy DROP;
chain OUTPUT policy ACCEPT;
}

run #1
iptables -t filter -P OUTPUT ACCEPT
iptables -t filter -P FORWARD ACCEPT
iptables -t filter -P INPUT ACCEPT
iptables -t filter -F
iptables -t filter -X
iptables -t filter -P FORWARD DROP
iptables -t filter -P INPUT DROP
run #2
iptables -t filter -P INPUT ACCEPT
iptables -t filter -P FORWARD ACCEPT
iptables -t filter -P OUTPUT ACCEPT
iptables -t filter -F
iptables -t filter -X
iptables -t filter -P INPUT DROP
iptables -t filter -P FORWARD DROP

I think this behavior comes from Perl's randomized hash tables and the use of 
while (my ($chain, $chain_info) = each %{$table_info->{chains}}) { ... }
constructs.  Changing these to loops over sorted keys should fix the problem.



Bug#989470: google-cloud-sdk: Python SyntaxWarning during installation

2021-06-04 Thread Eric Cooper
Package: google-cloud-sdk
Version: 343.0.0-0
Severity: normal

Installation produces this warning:
Setting up google-cloud-sdk (343.0.0-0) ...
lib/googlecloudsdk/api_lib/vmware/privateclouds.py:57: SyntaxWarning: 
"is" with a literal. Did you mean "=="?
  if bool(network_project is None or '' is network_project):

-- System Information:
Debian Release: 11.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing'), (400, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/32 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages google-cloud-sdk depends on:
ii  python3  3.9.2-3

Versions of packages google-cloud-sdk recommends:
pn  python3-crcmod  

Versions of packages google-cloud-sdk suggests:
pn  google-cloud-sdk-app-engine-java 
pn  google-cloud-sdk-app-engine-python   
pn  google-cloud-sdk-bigtable-emulator   
pn  google-cloud-sdk-datastore-emulator  
pn  google-cloud-sdk-pubsub-emulator 
pn  kubectl  

-- no debconf information



Bug#974070: nm.debian.org: column sorting on https://nm.debian.org/members/ is off-by-one

2020-11-09 Thread Eric Cooper
Package: nm.debian.org
Severity: normal

Sorting by "account name" actually sorts by "name", sorting by "since"
actually sorts by "account name", and there is no way to sort by "since".

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

Kernel: Linux 5.9.0-1-amd64 (SMP w/32 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



Bug#963582: pulseaudio: please split off X11-dependent package

2020-06-23 Thread Eric Cooper
Package: pulseaudio
Version: 13.0-5
Severity: wishlist

I am using pulseaudio on a headless Raspberry Pi, where there is no
need for any GUI apps or other dependencies on X11 libs.

Please separate the packages for the core pulseaudio server and
command-line tools from those that are X11-dependent.

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

Kernel: Linux 5.6.0-2-amd64 (SMP w/32 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 pulseaudio depends on:
ii  adduser  3.118
ii  init-system-helpers  1.57
ii  libasound2   1.2.2-2.2
ii  libasound2-plugins   1.2.2-1
ii  libc62.30-8
ii  libcap2  1:2.34-2
ii  libdbus-1-3  1.12.18-1
ii  libgcc-s110.1.0-3
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-14
ii  liborc-0.4-0 1:0.4.31-1
ii  libpulse013.0-5
ii  libsm6   2:1.2.3-1
ii  libsndfile1  1.0.28-8
ii  libsoxr0 0.1.3-4
ii  libspeexdsp1 1.2~rc1.2-1.1
ii  libstdc++6   10.1.0-3
ii  libsystemd0  245.6-1
ii  libtdb1  1.4.2-3+b1
ii  libudev1 245.6-1
ii  libwebrtc-audio-processing1  0.3-1+b1
ii  libx11-6 2:1.6.9-2+b1
ii  libx11-xcb1  2:1.6.9-2+b1
ii  libxcb1  1.14-2
ii  libxtst6 2:1.2.3-1
ii  lsb-base 11.1.0
ii  pulseaudio-utils 13.0-5

Versions of packages pulseaudio recommends:
ii  dbus-user-session1.12.18-1
ii  libpam-systemd [logind]  245.6-1
ii  rtkit0.13-4

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  4.0-2
pn  pavumeter
ii  udev 245.6-1

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; avoid-resampling = fals

Bug#941235: remmina-plugin-vnc: VNC plugin not registered

2020-06-18 Thread Eric Cooper
On Wed, Jun 17, 2020 at 2:43 PM Matteo F. Vescovi  wrote:

> has the situation changed with newer versions?
>
> Please, let me know so I can triage this bug report better... or even
> close it, if the issue doesn't show up anymore.
>

I can't reproduce the problem with the version currently in bullseye, so
feel free to close this. Thanks.


Bug#962627: eboard: playing against crafty causes "*** buffer overflow detected ***: eboard terminated"

2020-06-10 Thread Eric Cooper
Package: eboard
Version: 1.1.3-0.3
Severity: normal

Newly installed crafty and eboard.

Whan I run eboard, and choose Peer > Play against engine > Crafty > OK (all 
default
options), I get this message:

*** buffer overflow detected ***: eboard terminated
Aborted

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

Kernel: Linux 5.6.0-2-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_WARN
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 eboard depends on:
ii  libatk1.0-0  2.36.0-2
ii  libc62.30-8
ii  libcairo21.16.0-4
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.1-2
ii  libgcc-s1 [libgcc1]  10.1.0-3
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-4
ii  libglib2.0-0 2.64.3-1
ii  libgstreamer1.0-01.16.2-2
ii  libgtk2.0-0  2.24.32-4
ii  libpango-1.0-0   1.44.7-4
ii  libpangocairo-1.0-0  1.44.7-4
ii  libpangoft2-1.0-01.44.7-4
ii  libpng16-16  1.6.37-2
ii  libstdc++6   10.1.0-3
ii  zlib1g   1:1.2.11.dfsg-2

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

Versions of packages eboard suggests:
ii  crafty  23.4-7

-- no debconf information



Bug#962015: wlcs: apostrophe in package description is incorrect

2020-06-01 Thread Eric Cooper
Package: wlcs
Version: 1.1.0+dfsg-4
Severity: minor

The plural of "suite" is "suites". No apostrophe.



Bug#952827: calibre: Kindle not detected unless udisks2 package is installed; please add to Depends

2020-02-29 Thread Eric Cooper
Package: calibre
Version: 4.99.4+dfsg+really4.10.0+py3-2
Severity: normal

I have calibre installed on two Debian systems. My Kindle Paperwhite
was only being detected on one of them. I used calibre's "debug device
detection" to discover that it was trying to use a Python udisks
function and failing. The system where it worked already had udisks2
installed. Once I installed udisks2 on the other system, it worked
too.

I think udisks2 (or an underlying library?) should be a Depends, or at
least Recommended.

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

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

Versions of packages calibre depends on:
ii  calibre-bin  4.99.4+dfsg+really4.10.0+py3-2
ii  dpkg 1.19.7
ii  fonts-liberation 1:1.07.4-11
ii  imagemagick  8:6.9.10.23+dfsg-2.1+b2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1+b2
ii  libjpeg-turbo-progs  1:1.5.2-2+b1
ii  libjs-mathjax2.7.4+dfsg-1
ii  libjxr-tools 1.1-6+b1
ii  optipng  0.7.7-1+b1
ii  poppler-utils0.71.0-6
ii  python3  3.7.5-3
ii  python3-apsw 3.30.1-r1-1.1
ii  python3-bs4  4.8.2-1
ii  python3-chardet  3.0.4-4
ii  python3-chm  0.8.6-2
ii  python3-css-parser   1.0.4-2
ii  python3-cssselect1.1.0-2
ii  python3-cssutils 1.0.2-3
ii  python3-dateutil 2.7.3-3
ii  python3-dbus 1.2.16-1
ii  python3-feedparser   5.2.1-2
ii  python3-html2text2020.1.16-1
ii  python3-html5-parser 0.4.9-3
ii  python3-html5lib 1.0.1-2
ii  python3-lxml 4.5.0-1
ii  python3-markdown 3.1.1-2
ii  python3-mechanize1:0.4.5-2
ii  python3-msgpack  0.5.6-3
ii  python3-netifaces0.10.9-0.2
ii  python3-pil  6.2.1-2+b1
ii  python3-pkg-resources44.0.0-1
ii  python3-pygments 2.3.1+dfsg-1
ii  python3-pyparsing2.4.6-1
ii  python3-pyqt55.14.1+dfsg-3
ii  python3-pyqt5.qtsvg  5.14.1+dfsg-3
ii  python3-pyqt5.qtwebengine5.14.0-2
ii  python3-regex0.1.20190819-2
ii  python3-routes   2.4.1-2
ii  python3-zeroconf 0.23.0-1
ii  xdg-utils1.1.3-1

Versions of packages calibre recommends:
pn  python3-dnspython  

Versions of packages calibre suggests:
pn  python3-unrardll  

-- no debconf information



Bug#951597: RFA: approx -- caching proxy server for Debian archive files

2020-02-18 Thread Eric Cooper
Package: wnpp
Severity: normal

I request an adopter for the approx package.
I no longer use approx myself (I just use a Squid proxy now) and I
haven't done much OCaml coding recently, so it's time to move on.

I haven't done an upload since the move from alioth to salsa, and it
seems I no longer have permission to do so, so an adopter should
probably set the "Maintainer" to the OCaml team and remove the "Uploaders"
field.

The package description is:
 Approx is an HTTP-based proxy server for Debian-style package archives.
 It fetches files from remote repositories on demand,
 and caches them for local use.
 .
 Approx saves time and network bandwidth if you need to install or
 upgrade .deb packages for a number of machines on a local network.
 Each package is downloaded from a remote site only once,
 regardless of how many local clients install it.
 The approx cache typically requires a few gigabytes of disk space.
 .
 Approx also simplifies the administration of client machines:
 repository locations need only be changed in approx's configuration file,
 not in every client's /etc/apt/sources.list file.
 .
 Approx can be used as a replacement for apt-proxy,
 with no need to modify clients' /etc/apt/sources.list files,
 or as an alternative to apt-cacher.



Bug#948603: RFA: approx -- caching proxy server for Debian archive files

2020-01-10 Thread Eric Cooper
Package: wnpp
Severity: normal

I request an adopter for the approx package.
(I am no longer active with OCaml and have been using squid instead
of approx.)


The package description is:
 Approx is an HTTP-based proxy server for Debian-style package archives.
 It fetches files from remote repositories on demand,
 and caches them for local use.
 .
 Approx saves time and network bandwidth if you need to install or
 upgrade .deb packages for a number of machines on a local network.
 Each package is downloaded from a remote site only once,
 regardless of how many local clients install it.
 The approx cache typically requires a few gigabytes of disk space.
 .
 Approx also simplifies the administration of client machines:
 repository locations need only be changed in approx's configuration file,
 not in every client's /etc/apt/sources.list file.
 .
 Approx can be used as a replacement for apt-proxy,
 with no need to modify clients' /etc/apt/sources.list files,
 or as an alternative to apt-cacher.



Bug#872955: fstl: crashes with std::bad_alloc

2019-11-18 Thread Eric Cooper
On Mon, Nov 18, 2019 at 6:12 AM Jakob Haufe  wrote:
>
> Does this still apply to 0.9.3-1?

I cannot reproduce it with 0.9.3-1. It seems to work fine now.


Bug#941235: remmina-plugin-vnc: VNC plugin not registered

2019-09-27 Thread Eric Cooper
$ dpkg -l | grep vnc
ii  gir1.2-gtk-vnc-2.0:amd64  0.9.0-1.1+b1
amd64GObject introspection data for GTK-VNC
ii  libgtk-vnc-2.0-0:amd640.9.0-1.1+b1
amd64VNC viewer widget for GTK+3 (runtime libraries)
ii  libgvnc-1.0-0:amd64   0.9.0-1.1+b1
amd64VNC GObject wrapper (runtime libraries)
ii  libvncclient1:amd64   0.9.11+dfsg-1.3
   amd64API to write one's own VNC server - client library
ii  remmina-plugin-vnc:amd64  1.3.6+dfsg-2
amd64VNC plugin for Remmina
ii  tigervnc-viewer   1.9.0+dfsg-3
amd64Virtual network computing client for X

On Fri, Sep 27, 2019 at 8:25 AM Matteo F. Vescovi  wrote:

> Control: tag -1 + moreinfo
>
> Hi!
>
> On 2019-09-26 at 16:50 (-04), Eric Cooper wrote:
> > Package: remmina-plugin-vnc
> > Version: 1.3.6+dfsg-2
> > Severity: important
> >
> > $ dpkg --get-selections | grep remmina
>
> [...]
>
> I prefer the output of 'dpkg -l | grep vnc' for this case.
>
> Thanks.
>
>
> --
> Matteo F. Vescovi || Debian Developer
> GnuPG KeyID: 4096R/0x8062398983B2CF7A
>


Bug#941235: remmina-plugin-vnc: VNC plugin not registered

2019-09-26 Thread Eric Cooper
Package: remmina-plugin-vnc
Version: 1.3.6+dfsg-2
Severity: important

$ dpkg --get-selections | grep remmina
remmina install
remmina-common  install
remmina-plugin-nx:amd64 install
remmina-plugin-rdp:amd64install
remmina-plugin-secret:amd64 install
remmina-plugin-vnc:amd64install

When I start remmina, VNC is not listed in the dropdown
connection-type menu or in the Plugins window. Only SSH and SFTP are listed.



Bug#915549: gnome-mahjongg: dates in score list are not formatted according to locale

2018-12-04 Thread Eric Cooper
Package: gnome-mahjongg
Version: 1:3.22.0-3
Severity: minor

My locale (LANG and LC_*) are all set to en_US.UTF-8
But the date field in the high score dialog does not respect this;
today's date is shown as 04/12/2018 for example.

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

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

Versions of packages gnome-mahjongg depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-1
ii  libc62.27-8
ii  libcairo21.16.0-1
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-6
ii  libglib2.0-0 2.58.1-2
ii  libgtk-3-0   3.24.1-2
ii  librsvg2-2   2.44.9-1

Versions of packages gnome-mahjongg recommends:
pn  yelp  

gnome-mahjongg suggests no packages.

-- no debconf information



Bug#915138: gimp: complains that "SVG file does not specify a size!"

2018-11-30 Thread Eric Cooper
Package: gimp
Version: 2.10.8-1
Severity: normal

Here is the header of an SVG file that:
(1) displays correctly in programs like inkscape and eog
(2) used to open without problem in earlier versions of Gimp


http://purl.org/dc/elements/1.1/";
   xmlns:cc="http://creativecommons.org/ns#";
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
   xmlns:svg="http://www.w3.org/2000/svg";
   xmlns="http://www.w3.org/2000/svg";
   id="svg9"
   preserveAspectRatio="xMidYMid meet"
   viewBox="0 0 920.0001 161.99292"
   height="202.49115"
   width="1150.0001"
   version="1.0">
  
  
Created by potrace 1.8, written by Peter Selinger 2001-2007

  
image/svg+xml
http://purl.org/dc/dcmitype/StillImage"; />

  

[...]

Gimp no longer recognizes the size.

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

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

Versions of packages gimp depends on:
ii  gimp-data2.10.8-1
ii  libaa1   1.4p5-44+b2
ii  libbabl-0.1-00.1.60-1
ii  libbz2-1.0   1.0.6-9
ii  libc62.27-8
ii  libcairo21.16.0-1
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3
ii  libgcc1  1:8.2.0-9
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-6
ii  libgegl-0.4-00.4.12-1
ii  libgexiv2-2  0.10.8-1
ii  libgimp2.0   2.10.8-1
ii  libglib2.0-0 2.58.1-2
ii  libgs9   9.26~dfsg-1
ii  libgtk2.0-0  2.24.32-3
ii  libgudev-1.0-0   232-2
ii  libharfbuzz0b2.1.1-1+b1
ii  libheif1 1.3.2-1+b1
ii  libilmbase23 2.2.1-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3
ii  liblzma5 5.2.2-1.3
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.3-0 1.3.0-2
ii  libopenexr23 2.2.1-4
ii  libopenjp2-7 2.3.0-1
ii  libpango-1.0-0   1.42.4-4
ii  libpangocairo-1.0-0  1.42.4-4
ii  libpangoft2-1.0-01.42.4-4
ii  libpng16-16  1.6.34-2
ii  libpoppler-glib8 0.69.0-2
ii  librsvg2-2   2.44.9-1
ii  libstdc++6   8.2.0-9
ii  libtiff5 4.0.10-3
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libwmf0.2-7  0.2.8.4-14
ii  libx11-6 2:1.6.7-1
ii  libxcursor1  1:1.1.15-2
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages gimp recommends:
ii  ghostscript  9.26~dfsg-1

Versions of packages gimp suggests:
pn  gimp-data-extras  
pn  gimp-help-en | gimp-help  
pn  gimp-python   
pn  gvfs-backends 
ii  libasound21.1.7-1+b1

-- no debconf information



Bug#910809: ferm: IP tables output with --remote --slow is not reproducible

2018-10-11 Thread Eric Cooper
Package: ferm
Version: 2.4-1
Severity: normal


The output from "ferm --remote --slow" differs from run to run on the
same input file. As far as I can see, it's generating the "iptables
-P" commands in some non-deterministic order.

For example, this input file

table filter {
chain INPUT {
policy DROP;
mod state state (ESTABLISHED RELATED) ACCEPT;
}
chain FORWARD policy DROP;
chain OUTPUT policy ACCEPT;
}

generates different orderings each time it is run.

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

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

Versions of packages ferm depends on:
ii  debconf  1.5.69
ii  init-system-helpers  1.54
ii  iptables 1.6.2-1.1
ii  lsb-base 9.20170808
ii  perl 5.26.2-7

Versions of packages ferm recommends:
ii  libnet-dns-perl  1.17-1

ferm suggests no packages.

-- Configuration Files:
/etc/ferm/ferm.conf [Errno 13] Permission denied: '/etc/ferm/ferm.conf'

-- debconf information excluded



Bug#905542: xserver-xorg-video-nouveau: segmentation fault on startup every time

2018-08-05 Thread Eric Cooper
Thanks, I can confirm that rolling back to xserver-xorg-core 2:1.19.6-1
fixes the problem for me for now.

On Sun, Aug 5, 2018 at 3:55 PM Sven Joachim  wrote:

> Control: reassign -1 xserver-xorg-core
> Control: forcemerge 900550 -1
>
> On 2018-08-05 15:43 -0400, Eric Cooper wrote:
>
> > Package: xserver-xorg-video-nouveau
> > Version: 1:1.0.15-3
> > Severity: important
> >
> > I did an "apt-get upgrade" today that installed new
> > xserver-xorg-{core,nouveau} packages. Now X does not start on my system.
> > The same segmentation fault occurs every time I run "startx".
> > [...]
> > [   301.726] (EE)
> > [   301.726] (EE) Backtrace:
> > [   301.726] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d)
> [0x56123945b8dd]
> > [   301.726] (EE) 1: /usr/lib/xorg/Xorg (0x5612392a8000+0x1b7599)
> [0x56123945f599]
> > [   301.726] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
> (0x7f1b1ca8+0x128e0) [0x7f1b1ca928e0]
> > [   301.726] (EE) 3: /usr/lib/xorg/Xorg (miRenderColorToPixel+0xe)
> [0x5612393cfbde]
> > [   301.726] (EE) 4: /usr/lib/xorg/modules/libexa.so
> (0x7f1b19a8d000+0xf13b) [0x7f1b19a9c13b]
> > [   301.726] (EE) 5: /usr/lib/xorg/Xorg (0x5612392a8000+0x13a8b6)
> [0x5612393e28b6]
> > [   301.726] (EE) 6: /usr/lib/xorg/Xorg (0x5612392a8000+0x12ec1c)
> [0x5612393d6c1c]
> > [   301.726] (EE) 7: /usr/lib/xorg/Xorg (0x5612392a8000+0x5b008)
> [0x561239303008]
> > [   301.726] (EE) 8: /usr/lib/xorg/Xorg (0x5612392a8000+0x5f008)
> [0x561239307008]
> > [   301.726] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6
> (__libc_start_main+0xe7) [0x7f1b1c8e5b17]
> > [   301.727] (EE) 10: /usr/lib/xorg/Xorg (_start+0x2a) [0x5612392f0d0a]
> > [   301.727] (EE)
> > [   301.727] (EE) Segmentation fault at address 0x8
> > [   301.727] (EE)
> > Fatal server error:
> > [   301.727] (EE) Caught signal 11 (Segmentation fault). Server aborting
>
> This is bug #900550 in xserver-xorg-core, a fix is pending in git[1].
>
> Cheers,
>Sven
>
>
> 1.
> https://salsa.debian.org/xorg-team/xserver/xorg-server/commit/aa7aaeb5223830a3670dc658152e28f125c17de8
>


Bug#905542: xserver-xorg-video-nouveau: segmentation fault on startup every time

2018-08-05 Thread Eric Cooper
Package: xserver-xorg-video-nouveau
Version: 1:1.0.15-3
Severity: important

I did an "apt-get upgrade" today that installed new
xserver-xorg-{core,nouveau} packages. Now X does not start on my system.
The same segmentation fault occurs every time I run "startx".

-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 
440] [10de:0de0] (rev a1)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.17.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-26)) #1 SMP Debian 4.17.8-1 (2018-07-20)

Xorg X server log files on system:
--
-rw-r--r-- 1 ecc ecc 23081 Jul  9 14:39 /home/ecc/.local/share/xorg/Xorg.1.log
-rw-r--r-- 1 ecc ecc 35236 Aug  5 15:37 /home/ecc/.local/share/xorg/Xorg.0.log

Contents of most recent Xorg X server log file 
(/home/ecc/.local/share/xorg/Xorg.0.log):

[   300.857]
X.Org X Server 1.20.0
X Protocol Version 11, Revision 0
[   300.859] Build Operating System: Linux 4.9.0-6-amd64 x86_64 Debian
[   300.859] Current Operating System: Linux xyzzy 4.17.0-1-amd64 #1 SMP Debian 
4.17.8-1 (2018-07-20) x86_64
[   300.859] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.17.0-1-amd64 
root=UUID=1bd202e7-8d8c-4170-8388-abddc49cd075 ro quiet
[   300.861] Build Date: 01 July 2018  05:07:24PM
[   300.861] xorg-server 2:1.20.0-3 (https://www.debian.org/support)
[   300.862] Current version of pixman: 0.34.0
[   300.863]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   300.863] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   300.865] (==) Log file: "/home/ecc/.local/share/xorg/Xorg.0.log", Time: Sun 
Aug  5 15:37:14 2018
[   300.866] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   300.866] (==) No Layout section.  Using the first Screen section.
[   300.866] (==) No screen section available. Using defaults.
[   300.866] (**) |-->Screen "Default Screen Section" (0)
[   300.866] (**) |   |-->Monitor ""
[   300.867] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   300.867] (==) Automatically adding devices
[   300.867] (==) Automatically enabling devices
[   300.867] (==) Automatically adding GPU devices
[   300.867] (==) Max clients allowed: 256, resource mask: 0x1f
[   300.867] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   300.867]Entry deleted from font path.
[   300.867] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[   300.867] (==) ModulePath set to "/usr/lib/xorg/modules"
[   300.867] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   300.867] (II) Loader magic: 0x5612396eade0
[   300.867] (II) Module ABI versions:
[   300.867]X.Org ANSI C Emulation: 0.4
[   300.867]X.Org Video Driver: 24.0
[   300.867]X.Org XInput driver : 24.1
[   300.867]X.Org Server Extension : 10.0
[   300.868] (++) using VT number 1

[   300.871] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_31
[   300.873] (II) xfree86: Adding drm device (/dev/dri/card0)
[   300.874] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
[   300.882] (--) PCI:*(1@0:0:0) 10de:0de0:1043:83b7 rev 161, Mem @ 
0xf600/16777216, 0xe800/134217728, 0xf200/33554432, I/O @ 
0xcc00/128, BIOS @ 0x/131072
[   300.883] (II) LoadModule: "glx"
[   300.883] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   300.884] (II) Module glx: vendor="X.Org Foundation"
[   300.884]compiled for 1.20.0, module version = 1.0.0
[   300.884]ABI class: X.Org Server Extension, version 10.0
[   300.884] (==) Matched nouveau as autoconfigured driver 0
[   300.884] (==) Matched nv as autoconfigured driver 1
[   300.884] (==) Matched modesetting as autoconfigured driver 2
[   300.884] (==) Matched fbdev as autoconfigured driver 3
[   300.884] (==) Matched vesa as autoconfigured driver 4
[   300.884] (==) Assigned the driver to the xf86ConfigLayout
[   300.884] (II) LoadModule: "nouveau"
[   300.884] (II) Loading /usr/

Bug#904394: netperf: cannot run netserver as non-root due to logging in /var/log/

2018-07-23 Thread Eric Cooper
Package: netperf
Version: 2.6.0-2.1
Severity: normal

I'd prefer to run short-lived instances of netserver as a normal user,
not root, but that fails because netserver insists on trying to create
/var/log/netserver.debug_, which it can't.

A simple way to specify an alternate logfile or log directory would
fix this, I think.

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

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

Versions of packages netperf depends on:
ii  libc6  2.27-3

netperf recommends no packages.

netperf suggests no packages.

-- no debconf information



Bug#903426: libdrm-nouveau2: "[TTM] Buffer eviction failed" followed by system hanging

2018-07-09 Thread Eric Cooper
Package: libdrm-nouveau2
Version: 2.4.92-1
Severity: important

This has been happening frequently, but not repeatably so far.
It seems to be triggered by something Chromium is doing when I have
lots of browser windows and tabs open.

I've included the portion of syslog when this occurs.

Once it does happen, the system soon becomes unusable: I can't use X,
and if I ssh in from another machine, I can't kill X; all I can do is reboot.

Jul  9 12:53:47 xyz kernel: [ 3737.149732] WARNING: CPU: 1 PID: 9025 at 
/build/linux-uwVqDp/linux-4.16.16/drivers/gpu/drm/nouveau/nvif/vmm.c:71 
nvif_vmm_put+0x6a/0x80 [nouveau]
Jul  9 12:53:47 xyz kernel: [ 3737.149734] Modules linked in: ebtable_filter 
ebtables devlink ip6table_filter ip6_tables iptable_filter cpufreq_powersave 
cpufreq_conservative cpufreq_userspace usblp snd_usb_audio snd_usbmidi_lib 
snd_hwdep snd_rawmidi snd_seq_device snd_pcm nouveau intel_powerclamp mxm_wmi 
kvm_intel wmi snd_timer video snd evdev ttm drm_kms_helper drm i2c_algo_bit kvm 
irqbypass iTCO_wdt iTCO_vendor_support soundcore asus_atk0110 shpchp 
intel_cstate intel_uncore i7core_edac serio_raw lpc_ich sg button coretemp 
cdc_acm acpi_cpufreq binfmt_misc nfsd parport_pc auth_rpcgss ppdev nfs_acl 
lockd grace sunrpc lp parport ip_tables x_tables autofs4 ext4 crc16 mbcache 
jbd2 crc32c_generic fscrypto ecb crypto_simd cryptd glue_helper aes_x86_64 uas 
usb_storage hid_generic usbhid hid sr_mod cdrom sd_mod ata_generic ata_piix 
pata_via
Jul  9 12:53:47 xyz kernel: [ 3737.149793]  ehci_pci crc32c_intel libata 
ehci_hcd r8169 psmouse firewire_ohci i2c_i801 mii scsi_mod firewire_core 
usbcore crc_itu_t usb_common
Jul  9 12:53:47 xyz kernel: [ 3737.149807] CPU: 1 PID: 9025 Comm: kworker/1:2 
Not tainted 4.16.0-2-amd64 #1 Debian 4.16.16-2
Jul  9 12:53:47 xyz kernel: [ 3737.149808] Hardware name: System manufacturer 
System Product Name/P7P55-M, BIOS 110109/04/2012
Jul  9 12:53:47 xyz kernel: [ 3737.149859] Workqueue: events nouveau_cli_work 
[nouveau]
Jul  9 12:53:47 xyz kernel: [ 3737.149890] RIP: 0010:nvif_vmm_put+0x6a/0x80 
[nouveau]
Jul  9 12:53:47 xyz kernel: [ 3737.149891] RSP: 0018:b0094d6d3de0 EFLAGS: 
00010282
Jul  9 12:53:47 xyz kernel: [ 3737.149893] RAX: fffe RBX: 
b0094d6d3e08 RCX: 
Jul  9 12:53:47 xyz kernel: [ 3737.149895] RDX:  RSI: 
b0094d6d3d50 RDI: b0094d6d3df0
Jul  9 12:53:47 xyz kernel: [ 3737.149896] RBP: b0094d6d3e38 R08: 
05927000 R09: 
Jul  9 12:53:47 xyz kernel: [ 3737.149897] R10:  R11: 
0073 R12: a046fc484a80
Jul  9 12:53:47 xyz kernel: [ 3737.149899] R13: a0475f7ba280 R14: 
dead0100 R15: a046fc484a90
Jul  9 12:53:47 xyz kernel: [ 3737.149901] FS:  () 
GS:a0477f24() knlGS:
Jul  9 12:53:47 xyz kernel: [ 3737.149903] CS:  0010 DS:  ES:  CR0: 
80050033
Jul  9 12:53:47 xyz kernel: [ 3737.149904] CR2: 7fb227855818 CR3: 
00015540a000 CR4: 06e0
Jul  9 12:53:47 xyz kernel: [ 3737.149905] Call Trace:
Jul  9 12:53:47 xyz kernel: [ 3737.149958]  nouveau_vma_del+0x70/0xc0 [nouveau]
Jul  9 12:53:47 xyz kernel: [ 3737.150008]  
nouveau_gem_object_delete_work+0x2d/0x50 [nouveau]
Jul  9 12:53:47 xyz kernel: [ 3737.150058]  nouveau_cli_work_flush+0xf8/0x150 
[nouveau]
Jul  9 12:53:47 xyz kernel: [ 3737.150063]  process_one_work+0x17b/0x360
Jul  9 12:53:47 xyz kernel: [ 3737.150066]  worker_thread+0x2e/0x390
Jul  9 12:53:47 xyz kernel: [ 3737.150069]  ? process_one_work+0x360/0x360
Jul  9 12:53:47 xyz kernel: [ 3737.150072]  kthread+0x113/0x130
Jul  9 12:53:47 xyz kernel: [ 3737.150075]  ? 
kthread_create_worker_on_cpu+0x70/0x70
Jul  9 12:53:47 xyz kernel: [ 3737.150078]  ? SyS_exit+0x13/0x20
Jul  9 12:53:47 xyz kernel: [ 3737.150082]  ret_from_fork+0x35/0x40
Jul  9 12:53:47 xyz kernel: [ 3737.150084] Code: 00 00 00 48 89 e2 be 02 00 00 
00 48 c7 04 24 00 00 00 00 48 89 44 24 08 e8 74 eb ff ff 85 c0 75 0a 48 c7 43 
08 00 00 00 00 eb b7 <0f> 0b eb f2 e8 9d 32 59 e6 0f 1f 00 66 2e 0f 1f 84 00 00 
00 00
Jul  9 12:53:47 xyz kernel: [ 3737.150130] ---[ end trace b3857888a2e5e0a9 ]---
Jul  9 12:53:47 xyz kernel: [ 3737.151286] WARNING: CPU: 1 PID: 9025 at 
/build/linux-uwVqDp/linux-4.16.16/drivers/gpu/drm/nouveau/nvif/vmm.c:71 
nvif_vmm_put+0x6a/0x80 [nouveau]
Jul  9 12:53:47 xyz kernel: [ 3737.151287] Modules linked in: ebtable_filter 
ebtables devlink ip6table_filter ip6_tables iptable_filter cpufreq_powersave 
cpufreq_conservative cpufreq_userspace usblp snd_usb_audio snd_usbmidi_lib 
snd_hwdep snd_rawmidi snd_seq_device snd_pcm nouveau intel_powerclamp mxm_wmi 
kvm_intel wmi snd_timer video snd evdev ttm drm_kms_helper drm i2c_algo_bit kvm 
irqbypass iTCO_wdt iTCO_vendor_support soundcore asus_atk0110 shpchp 
intel_cstate intel_uncore i7core_edac serio_raw lpc_ich sg button coretemp 
cdc_acm acpi_cpufreq binfmt_misc nfsd parport_pc auth_rpcgss ppdev nfs_acl 
lockd grace

Bug#897948: approx: jessie approx no longer retrieves files from /var/cache/approx

2018-05-05 Thread Eric Cooper
I would recommend installing the current version of approx if that's not
too disruptive. The approx-gc program has been replaced with a simple find
script that just removes old files, rather than trying to determine whether
they're still referenced from Packages files (that was the source of
several bugs).

If you can locate a package you know is in your approx cache, and can
reproduce the problem (missing the cache) by doing an "apt-get install
--reinstall ...", please send the log corresponding to that.  I can't see where
the problem is from the portion you posted.


Bug#882342: approx logs

2017-11-21 Thread Eric Cooper
Package: approx
Severity: wishlist
--- Begin Message ---

hi Eric,

i've been using approx for some time and now i'd like to migrate to 
stretch. also, i'd like to get data from approx logs but i find it 
difficult (for what i want). don't know if things changed in more recent 
versions. i looked at the code but myself experimented a "system 
overflow" ;-)


i'd like to get something (one-liner) like this in the logs:

approx[pid]:  asked for [cached | uncached | non-existant] 
 


this would allow me to account clients, cache hits/fails, bytes served, 
bandwidth saved...


many thanks for your work in approx.


david


--- End Message ---


Bug#876418: perl-modules-5.26: "Argument isn't numeric" error from Net::Ping

2017-09-21 Thread Eric Cooper
Package: perl-modules-5.26
Version: 5.26.0-8
Severity: normal

When I execute a program that uses Net::Ping, I get the following
error message:

Argument "2.020_03" isn't numeric in numeric ge (>=) at 
/usr/share/perl/5.26/Net/Ping.pm line 1801.

On my machine, the line in question is
   1799   # address check
   1800   # new way
   1801   if ($Socket::VERSION >= 1.94) {

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

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

Versions of packages perl-modules-5.26 depends on:
ii  dpkg   1.18.24
ii  perl-base  5.26.0-8

Versions of packages perl-modules-5.26 recommends:
ii  perl  5.26.0-8

perl-modules-5.26 suggests no packages.

-- no debconf information



Bug#872955: fstl: crashes with std::bad_alloc

2017-08-22 Thread Eric Cooper
And here's a backtrace from gdb:

(gdb) run
Starting program: /usr/bin/fstl
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fcc27d49700 (LWP 4164)]
[New Thread 0x7fcc25067700 (LWP 4165)]
[New Thread 0x7fcc1d3df700 (LWP 4166)]
[Thread 0x7fcc1d3df700 (LWP 4166) exited]
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

Thread 1 "fstl" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x7fcc31dfe42a in __GI_abort () at abort.c:89
#2  0x7fcc32713bb5 in __gnu_cxx::__verbose_terminate_handler() ()
   from /lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x7fcc32711986 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x7fcc327119d1 in std::terminate() () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x7fcc32711c14 in __cxa_throw () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x7fcc32d03832 in qBadAlloc() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fcc32d80fba in QListData::detach(int) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fcc32d2d1ce in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fcc32ef1b8f in QCoreApplication::arguments() ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fcc33da64df in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#11 0x7fcc33da7014 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#12 0x7fcc2ad37d90 in _SmcProcessMessage () from
/lib/x86_64-linux-gnu/libSM.so.6
#13 0x7fcc2ab272a8 in IceProcessMessages () from
/lib/x86_64-linux-gnu/libICE.so.6
#14 0x7fcc32f19e51 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7fcc32f935ce in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7fcc32f26222 in QSocketNotifier::event(QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fcc337cbbec in QApplicationPrivate::notify_helper(QObject*,
QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7fcc337d3381 in QApplication::notify(QObject*, QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7fcc32eee850 in QCoreApplication::notifyInternal2(QObject*,
QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7fcc32f4286d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7fcc30360bf7 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcc30360e60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcc30360f0c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7fcc32f423bf in
QEventDispatcherGlib::processEvents(QFlags)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7fcc32eec83a in
QEventLoop::exec(QFlags) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7fcc32ef4edc in QCoreApplication::exec() ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0xa00b in ?? ()
#28 0x7fcc31dea2e1 in __libc_start_main (main=0x9fe0, argc=1,
argv=0x7fffe0f8, init=, fini=,
rtld_fini=, stack_end=0x7fffe0e8) at
../csu/libc-start.c:291
#29 0xa0f9 in ?? ()

On Tue, Aug 22, 2017 at 6:54 PM, Eric Cooper  wrote:
> Here's a core file created when running just "fstl" with no arguments
> (which first printed the following):
>
> terminate called after throwing an instance of 'std::bad_alloc'
>   what():  std::bad_alloc
> Aborted (core dumped)
>
> On Tue, Aug 22, 2017 at 6:09 PM, Jakob Haufe  wrote:
>> Control: tags -1 + moreinfo
>>
>> Unfortunately, it doesn't crash here. Can you provide me with a coredump or
>> backtrace? Automatic debug packages for fstl 0.9.2-1 exist as well.



Bug#872955: fstl: crashes with std::bad_alloc

2017-08-22 Thread Eric Cooper
Package: fstl
Version: 0.9.2-1
Followup-For: Bug #872955

When I invoke "fstl" with no arguments, I *sometimes* get the same
error, sometimes it's a segmentation fault with no error message, and
sometimes it opens correctly with its default model.

In the last case, I can then use the File menu to open my example model and
it also opens correctly.

I also kept trying to run "fstl bottom.stl", and it succeeded after I tried
about 5 times.



Bug#872955: fstl: crashes with std::bad_alloc

2017-08-22 Thread Eric Cooper
Package: fstl
Version: 0.9.2-1
Severity: normal

Trying to run fstl on the attached STL file causes it to crash.

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

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

Versions of packages fstl depends on:
ii  libc6 2.24-14
ii  libgcc1   1:7.1.0-13
ii  libgl1-mesa-dri   13.0.6-1+b2
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libqt5core5a  5.7.1+dfsg-4
ii  libqt5gui55.7.1+dfsg-4
ii  libqt5opengl5 5.7.1+dfsg-4
ii  libqt5widgets55.7.1+dfsg-4
ii  libstdc++67.1.0-13

fstl recommends no packages.

fstl suggests no packages.

-- no debconf information


bottom.stl
Description: Binary data


Bug#870384: gcalcli: importing ICS file fails

2017-08-01 Thread Eric Cooper
Package: gcalcli
Version: 4.0.0~a3-1
Severity: normal

I can access my calendar OK:
$ gcalcli list
 Access  Title
 --  -
  owner  Eric Cooper
[...]

$ gcalcli agenda

Tue Aug 01   [...]

But attempts to import calendar invitations are failing:

$ gcalcli import invite.ics
Traceback (most recent call last):
  File "/usr/bin/gcalcli", line 2500, in 
BowChickaWowWow()
  File "/usr/bin/gcalcli", line 2490, in BowChickaWowWow
gcal.ImportICS(FLAGS.verbose, FLAGS.dump, FLAGS.reminder, FLAGS.file)
AttributeError: 'Namespace' object has no attribute 'reminder'

This seems to happen with any ICS file.

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

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

Versions of packages gcalcli depends on:
ii  python3   3.5.3-3
ii  python3-dateutil  2.6.0-1
ii  python3-googleapi 1.5.5-1
ii  python3-httplib2  0.9.2+dfsg-1
ii  python3-oauth2client  3.0.0-1
ii  python3-six   1.10.0-4

Versions of packages gcalcli recommends:
pn  python3-parsedatetime  
pn  python3-vobject

gcalcli suggests no packages.

-- no debconf information



Bug#865919: approx-import doesn't work.

2017-06-25 Thread Eric Cooper
On Sun, Jun 25, 2017 at 09:59:41PM +0200, darthcat wrote:
> I tried to import the apt cache with approx-import 
> /var/cache/apt/archive/*.deb
> and I simply get the message : "There are no Packages files in the approx
> cache.
> Please run "apt-get update" first." and /var/cache/approx is empty.
>
> So I ran "apt-get update" but I get the same message.
> I didn't find any Packages file in my computer.
>
> I get the same result with Jessie, now the old-stable.

Does your sources.list file on the machine on which you ran "apt-get
update" use your approx server in its "deb ..." lines?  That's what
will cause /var/cache/approx to contain the Packages and
other files.  Sorry if that's not clear in the documentation.

It's fine to do an initial "apt-get update" or upgrade against the approx
server even when its cache is empty.  The apt-import command is
optional, in case you already have a lot of .deb files locally.

If it *does* already point to your approx server, then please enable
debugging (set "$debug true" in /etc/approx/approx.conf), and send the log
output from the "apt-get update" run.

--
Eric Cooper e c c @ c m u . e d u



Bug#817277: phantomjs: PhantomJS fails to run headless

2017-06-23 Thread Eric Cooper
Package: phantomjs
Version: 2.1.1+dfsg-2
Followup-For: Bug #817277

It shouldn't have any dependencies on X-related libraries.
The version downloaded from the phantomjs site has only these:

$ ldd phantomjs-2.1.1-linux-x86_64/bin/phantomjs
linux-vdso.so.1 (0x7ffe7977f000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f7da9e9c000)
libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 
(0x7f7da9c5e000)
libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 
(0x7f7da99af000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f7da97ab000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f7da95a3000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f7da9384000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f7da9002000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f7da8cfe000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f7da8ae7000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f7da8748000)
/lib64/ld-linux-x86-64.so.2 (0x55ec43795000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 
(0x7f7da851e000)
libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 
(0x7f7da82e9000)



Bug#864459: xserver-xorg-video-nouveau: lockup when running Android emulator with hardware acceleration

2017-06-08 Thread Eric Cooper
Package: xserver-xorg-video-nouveau
Version: 1:1.0.13-3
Severity: normal

If I create an "Android virtual device" with hardware graphics
acceleration (from the Android Studio "AVD Manager"), my desktop locks
up within a few seconds.  The following messages appeared in the log
the last two times I tried it:

Jun  7 18:02:39 localhost kernel: [159030.531816] kvm: zapping shadow pages for 
mmio generation wraparound
Jun  7 18:02:39 localhost kernel: [159030.534494] kvm: zapping shadow pages for 
mmio generation wraparound
Jun  7 18:02:39 localhost kernel: [159031.005259] kvm [15289]: vcpu0, guest 
rIP: 0x81ad00fd disabled perfctr wrmsr: 0xc1 data 0x
Jun  7 18:02:46 localhost kernel: [159037.914635] nouveau :01:00.0: fifo: 
PBDMA0: 0004 [] ch 11 [001f832000 qemu-system-x86[15289]] subc 0 mthd  
data 
[...]
Jun  7 18:25:46 localhost kernel: [  646.293031] kvm: zapping shadow pages for 
mmio generation wraparound
Jun  7 18:25:46 localhost kernel: [  646.298049] kvm: zapping shadow pages for 
mmio generation wraparound
Jun  7 18:26:02 localhost kernel: [  663.126945] nouveau :01:00.0: fifo: 
PBDMA0: 0004 [] ch 9 [001f99a000 qemu-system-i38[1787]] subc 0 mthd  
data 
Jun  7 18:26:02 localhost kernel: [  663.126962] nouveau :01:00.0: fifo: 
PBDMA0: 0004 [] ch 9 [001f99a000 qemu-system-i38[1787]] subc 0 mthd  
data 


-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jun 20  2011 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Mar  3 09:41 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 
440] [10de:0de0] (rev a1)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 281 Oct  9  2014 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
Section "Device"
  Identifier "Device"
  Driver "nouveau"
EndSection

Section "Monitor"
  Identifier "HDMI-1"
  Option "LeftOf" "DVI-I-1"
EndSection

Section "Screen"
  Identifier "Screen"
  Monitor "Monitor"
  SubSection "Display"
Virtual 3840 1200
  EndSubSection
EndSection

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170425 (Debian 6.3.0-16) ) #1 SMP Debian 4.9.25-1 (2017-05-02)

Xorg X server log files on system:
--
-rw-r--r-- 1 ecc ecc 37542 Jun  7 18:36 /home/ecc/.local/share/xorg/Xorg.0.log

Contents of most recent Xorg X server log file 
(/home/ecc/.local/share/xorg/Xorg.0.log):

[   122.666]
X.Org X Server 1.19.2
Release Date: 2017-03-02
[   122.668] X Protocol Version 11, Revision 0
[   122.668] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[   122.669] Current Operating System: Linux localhost 4.9.0-3-amd64 #1 SMP 
Debian 4.9.25-1 (2017-05-02) x86_64
[   122.669] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-3-amd64 
root=UUID=1bd202e7-8d8c-4170-8388-abddc49cd075 ro quiet
[   122.671] Build Date: 03 March 2017  03:14:41PM
[   122.671] xorg-server 2:1.19.2-1 (https://www.debian.org/support)
[   122.672] Current version of pixman: 0.34.0
[   122.674]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   122.674] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   122.677] (==) Log file: "/home/ecc/.local/share/xorg/Xorg.0.log", Time: Wed 
Jun  7 18:36:36 2017
[   122.699] (==) Using config file: "/etc/X11/xorg.conf"
[   122.700] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   122.720] (==) No Layout section.  Using the first Screen section.
[   122.720] (**) |-->Screen "Screen" (0)
[   122.720] (**) |   |-->Monitor ""
[   122.721] (==) No device specified for screen "Screen".
Using the first device section listed.
[   122.721] (**) |   |-->Device "Device"
[   122.721] (==) No monitor specified for screen "Screen".
Using a default monitor configuration.
[   122.721] (==) Automatically adding devices
[   122.721] (==) Automatically enabling devices
[   122.721] (==) Automatically adding GPU devices
[   122.721] (==) Max clients allowed: 256, resource mask: 0x1f
[   122.745] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   122.745]Entry deleted from font path.
[   122.749] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Ty

Bug#861947: approx-gc mentioned in manpage not available anymore

2017-05-06 Thread Eric Cooper
On Sat, May 06, 2017 at 12:19:13PM +0200, Benedikt Trefzer wrote:
> The manpage mentions approx-gc for removal of unneeded versions of
> packages.
> approx-gc was removed in version 5.7.1 of the debian package.
> The manpage should therefore mention the new way to clean up the cache.
> (I hope there is on, I did not yet figure out howto do it !)

Thanks for the report.  Until a better version of approx-gc returns,
there is a simple weekly cron job that just removes old files from the
cache.  Unfortunately, especially for jessie, these old files might
still be the current versions of those packages, so it's far from
perfect.

--
Eric Cooper e c c @ c m u . e d u



Bug#856854: approx cannot fetch packages from local approx cache either remote repository

2017-03-09 Thread Eric Cooper
On Thu, Mar 09, 2017 at 10:40:27AM +0800, 汪婧 wrote:
> [...] I attempt to create the local repo with same layout as remote
> under the approx’s cache. But it doesn’t work for apt to get
> packages. That’s what I do with the local repo. I meant to provide
> you more hint, if it confused you , just forget itJ

This could work, but only if you follow the *complete* structure of a
repository, which must include Release and Release.gpg files with the
correct checksums and signatures, etc.  Otherwise approx won't
consider the Packages files to be valid.

> [Vv] As you suggest I put file:///packages/ to approx.conf, but approx cannot
> find packages still.

I think this is the same problem (lack of Release files etc.) but I
can't be sure without seeing the debug log from approx.

> [Vv] As the debian version is 8.3, Jessie, on which the stable version of
> approx. is 5.5-1, apt-get installed this version for Jessie. But I cannot get
> 5.7 by modifying the source to sid, e.g.:
> deb http://ftp.pl.debian.org/debian sid main contrib non-free. I downloaded
> approx_5.7-3.debian.tar.xz, but it seems complex to build and install by
> checking https://www.debian.org/doc/manuals/debian-faq/ch-pkg_basics.en.html. 
> do
> you have any suggestion?

You can download the .deb (from
http://ftp.us.debian.org/debian/pool/main/a/approx/approx_5.7-3_amd64.deb
for example, or any other Debian mirror), and install it with "dpkg -i".
It does not have any dependencies not in jessie, so it should install OK.

--
Eric Cooper e c c @ c m u . e d u



Bug#856854: approx cannot fetch packages from local approx cache either remote repository

2017-03-07 Thread Eric Cooper
I'm not exactly sure what you're trying to do with "creating a local
repository".  approx-import simply places .deb files in the part of
the cache that corresponds to a *remote* repository, if it can find
one, so that it doesn't have to be downloaded again.  It's optional,
since the .debs will be downloaded when needed.

If you create your own repository with dpkg-scanpackages, you can't
place it in the approx cache.  Approx expects its cache to have a
specific layout, namely a collection of (partial) mirrors of remote
repositories.  You'd have to put your local repo somewhere else, and
use file:/// URLs in /etc/approx.conf to tell approx where to find it.

Otherwise, the current version of approx is 5.7.  If you still have
problems after addressing the above issue, please try that version.

--
Eric Cooper e c c @ c m u . e d u



Bug#856854: approx cannot fetch packages from local approx cache either remote repository

2017-03-06 Thread Eric Cooper
Please enable debugging on your approx server (add "$debug true" to
/etc/approx.conf) and send the relevant portion of /var/log/daemon.log
from the server when this problem occurs.  Thanks.

--
Eric Cooper e c c @ c m u . e d u



Bug#854732: python-selenium: incorrect default path for chromedriver executable

2017-02-09 Thread Eric Cooper
Package: python-selenium
Version: 2.53.2+dfsg1-1
Severity: normal

I have the Debian chromium-driver package installed.

When I try to use it via webdriver.Chrome(), I get the following exception:
  File [...]
browser = webdriver.Chrome()
  File 
"/usr/lib/python2.7/dist-packages/selenium/webdriver/chrome/webdriver.py", line 
61, in __init__
self.service.start()
  File 
"/usr/lib/python2.7/dist-packages/selenium/webdriver/common/service.py", line 
69, in start
os.path.basename(self.path), self.start_error_message)
WebDriverException: Message: 'chromedriver' executable needs to be in PATH. 
Please see https://sites.google.com/a/chromium.org/chromedriver/home

I made a symlink from /usr/lib/chromium/chromedriver to /usr/bin/chromedriver 
which seems to fix the problem.

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

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

Versions of packages python-selenium depends on:
pn  python:any  

Versions of packages python-selenium recommends:
pn  chromedriver | phantomjs  

Versions of packages python-selenium suggests:
ii  firefoxdriver  2.53.2-3

-- no debconf information



Bug#852141: ubertooth: Please package latest version (2015-10-R1 or later)

2017-01-21 Thread Eric Cooper
Source: ubertooth
Version: 2015.09.R2-4
Severity: normal

The current version of Ubertooth firmware and utilities is
https://github.com/greatscottgadgets/ubertooth/releases/tag/2015-10-R1

Thank you for maintaining this.



Bug#851220: mongodb-server: broken upgrade from 2.6 to 3.2

2017-01-12 Thread Eric Cooper
Package: mongodb-server
Version: 1:3.2.11-2
Severity: normal

My mongo database stopped working after upgrading to the latest
version in stretch, which changed from mongo 2.6 to 3.2.

mongod would not start, complaining that authSchemaUpgrade needed to
be run first (and only on a 2.6 server, which was no longer
available).

I ended up downloading the 2.6 tarball from the mongo website
and running that version of mongod against my database in /var/lib so
I could do the authSchemaUpgrade.  After that the new 3.2 version
seemed to work OK.

In case anyone else gets stuck like this, I basically did this:

$ sudo mongod2.6 --noauth --dbpath /var/lib/mongodb &
$ mongo
> use admin
> db.runCommand({authSchemaUpgrade:1})
^D

I'm not sure if this could be detected or automated, but I wasted a
lot of time.  I don't think there should be a "silent" upgrade across
major versions like this when there are such incompatible changes.
Perhaps have mongodb-2.6, mongodb-3.2, etc. packages available concurrently
in the archive, with mongodb pulling in the "current" one.



Bug#848312: approx: Approx fails to work at all

2016-12-16 Thread Eric Cooper
> Approx used to work fine on this server. At some point a few weeks ago it 
> simply stopped working. I am
> guessing it was an upgrade to of approx (5.7 from 5.4?) or some change in the 
> systemd configuration at the
> same time that caused the problem. However I was not able to investigate at 
> the time, I just had to switch
> all the machines to individual working rather than using the approx system.
>
> I have just retried and there is no approx service registered and no access 
> to port  on the server.

Can you try installing the openbsd-inetd package (and if there is no
/etc/inetd.conf, or no entry for approx in that file, please purge and
reinstall the approx package)?  Please let me know if that solves the
problem for you.

I think the problem is that this version no longer depends on
inet-superserver; there was a patch to include systemd support that
was supposed to make it unnecessary, but evidently that doesn't work correctly.

--
Eric Cooper e c c @ c m u . e d u



Bug#848312: approx: Approx fails to work at all

2016-12-16 Thread Eric Cooper
It looks like openbsd-inetd is not needed and the systemd support does
work, but it's not being enabled and started by default.  I think all
that's required is:

# systemctl enable approx.socket
# systemctl start approx.socket

I don't know why that isn't done automatically, since I don't know
much about systemd, but I'll look into it.

--
Eric Cooper e c c @ c m u . e d u



Bug#827426: Can't reproduce

2016-11-22 Thread Eric Cooper
I also don't see a problem in my current installation, which is now
go1.7.3, so feel free to close this.

On Mon, Nov 21, 2016 at 2:41 PM, Martín Ferrari  wrote:
> tags 827426 + moreinfo unreproducible
> thanks
>
> Hi,
>
> I have tried exactly what you have described (with the most current
> x/tools), and I can't reproduce the problem. And stringer leaves a
> generated file:
>
> $ cat mytype_string.go
> // Code generated by "stringer -type=MyType foo.go"; DO NOT EDIT
>
> package main
>
> import "fmt"
>
> const _MyType_name = "Alpha"
>
> var _MyType_index = [...]uint8{0, 5}
>
> func (i MyType) String() string {
> i -= 1
> if i < 0 || i >= MyType(len(_MyType_index)-1) {
> return fmt.Sprintf("MyType(%d)", i+1)
> }
> return _MyType_name[_MyType_index[i]:_MyType_index[i+1]]
> }
>
>
>
> --
> Martín Ferrari (Tincho)



Bug#707087: xword: Close button does not work on Help > About dialog

2016-11-17 Thread Eric Cooper
Package: xword
Version: 2.0.0~rc2-1
Followup-For: Bug #707087

Clicking the close button doesn't actually do *nothing*.  It prints
(but ignores) the following error on the console:

Traceback (most recent call last):
  File "/usr/share/games/xword/main.py", line 485, in 
dialog.connect('response', lambda *args: dialog.destroy())
NameError: free variable 'dialog' referenced before assignment in enclosing 
scope



Bug#844559: emacs: hard lockup in shell-script-mode when file has no final newline

2016-11-16 Thread Eric Cooper
Package: emacs
Version: 46.1
Severity: normal

When I visit the following file (which ends after "bar" without a newline):

cut here
#!/bin/sh

if foo; then
barcut here

If I move to the "if foo" line, Emacs gets into a 100% busy,
uninterruptible state.  If I visit it literally, or change the mode to
text or fundamental, the problem doesn't occur.

It also doesn't occur if the "bar" line is already indented.

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

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

Versions of packages emacs depends on:
ii  emacs24  24.5+1-7

emacs recommends no packages.

emacs suggests no packages.

-- no debconf information



Bug#818731: approx: weekly cronjob breaks with removal of Files field from Sources

2016-11-15 Thread Eric Cooper
On Sun, Mar 20, 2016 at 08:04:56AM +, Ian Campbell wrote:
> I've just received the following in a cron mail:
>
> /etc/cron.weekly/approx:
> File /var/cache/approx/debian/dists/experimental/main/source/Sources.xz, line 
> 1: missing "Files" field
> run-parts: /etc/cron.weekly/approx exited with return code 1
>
> Which I pressume relates to the changes announced in
> https://lists.debian.org/debian-devel-announce/2016/03/msg6.html
>
> Tagging as blocking the corresponding archive bug.
>
> There is a newer version in sid but the changelog doesn't indicate that it
> resolves this issue.

I can't reproduce this problem.  When I include a deb-src line for
experimental,  I don't see any Sources.xz files in my approx server's
cache.

Can you please send me the output of
ls -l /var/cache/approx/debian/dists/experimental/main/source/

Thanks, and sorry for the inconvenience.

--
Eric Cooper e c c @ c m u . e d u



Bug#841258: golang: incorrect upgrade from 1.6 to 1.7 when gccgo is also present

2016-10-18 Thread Eric Cooper
Package: golang
Version: 2:1.7~1
Severity: normal

I had both gccgo and golang installed.  Before the recent upgrade to
golang 1.7, /usr/bin/go was the golang compiler.

After a recent apt-get upgrade, I noticed compilation failures and
found that /usr/bin/go was now gccgo-6, even though golang-1.7 had
been installed.

I had to purge and reinstall golang to fix the problem.

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

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

Versions of packages golang depends on:
ii  golang-1.7  1.7.1-2
ii  golang-doc  2:1.7~1
ii  golang-go   2:1.7~1
ii  golang-src  2:1.7~1

golang recommends no packages.

golang suggests no packages.

-- no debconf information



Bug#805579: nouveau: lockup with "[TTM] Buffer eviction failed"

2016-09-26 Thread Eric Cooper
Package: src:linux
Version: 4.6.4-1
Followup-For: Bug #805579

For a long time I didn't experience these lockups, but in the past
week or so they have started occurring again, about once a day:

[397467.956723] nouveau :01:00.0: fifo: read fault at 956000 engine 15 
[PCE0] client 01 [PCOPY0] reason 02 [PAGE_NOT_PRESENT] on channel 0 [001fe74000 
DRM]
[397467.956728] nouveau :01:00.0: fifo: ce0 engine fault on channel 0, 
recovering...
[397497.955174] [TTM] Buffer eviction failed
[397527.955845] [TTM] Buffer eviction failed
[397542.956067] [TTM] Buffer eviction failed

I haven't changed any of the hardware since my original report.
The bug seems to occur most often when I have lots of tabs open in
chromium.

-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.6.0-1-amd64 
root=UUID=1bd202e7-8d8c-4170-8388-abddc49cd075 ro quiet

** Tainted: E (8192)
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[6.167715] systemd[1]: Started Remount Root and Kernel File Systems.
[6.183580] systemd[1]: Starting Load/Save Random Seed...
[6.192558] systemd[1]: Starting udev Coldplug all Devices...
[6.193067] systemd[1]: Activating swap /swap...
[6.242335] systemd[1]: Started udev Coldplug all Devices.
[6.360002] systemd[1]: Started Create list of required static device nodes 
for the current kernel.
[6.375615] systemd[1]: Starting Create Static Device Nodes in /dev...
[6.424481] systemd[1]: Started Set the console keyboard layout.
[6.433829] systemd[1]: Started Journal Service.
[6.725839] systemd-journald[1008]: Received request to flush runtime 
journal from PID 1
[6.781160] lp: driver loaded but no devices found
[6.812496] ppdev: user-space parallel port driver
[6.846108] parport_pc 00:07: reported by Plug and Play ACPI
[6.846173] parport0: PC-style at 0x378, irq 7 [PCSPP]
[6.850215] RPC: Registered named UNIX socket transport module.
[6.850217] RPC: Registered udp transport module.
[6.850218] RPC: Registered tcp transport module.
[6.850219] RPC: Registered tcp NFSv4.1 backchannel transport module.
[6.935616] lp0: using parport0 (interrupt-driven).
[6.994592] Installing knfsd (copyright (C) 1996 o...@monad.swb.de).
[7.442457] Adding 34179680k swap on /swap.  Priority:-1 extents:30 
across:38783584k FS
[8.463735] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[8.467167] ACPI Warning: SystemIO range 
0x0400-0x041F conflicts with OpRegion 
0x0400-0x040F (\SMRG) (20160108/utaddress-255)
[8.467172] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[8.475249] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input7
[8.475253] ACPI: Power Button [PWRB]
[8.475290] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
[8.475292] ACPI: Power Button [PWRF]
[8.540063] ACPI Warning: SystemIO range 
0x0828-0x082F conflicts with OpRegion 
0x0800-0x084F (\PMRG) (20160108/utaddress-255)
[8.540070] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[8.540074] ACPI Warning: SystemIO range 
0x0530-0x053F conflicts with OpRegion 
0x0500-0x053F (\GPS0) (20160108/utaddress-255)
[8.540077] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[8.540079] ACPI Warning: SystemIO range 
0x0500-0x052F conflicts with OpRegion 
0x0500-0x053F (\GPS0) (20160108/utaddress-255)
[8.540082] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[8.540117] lpc_ich: Resource conflict(s) found affecting gpio_ich
[8.634159] [drm] Initialized drm 1.1.0 20060810
[8.653154] wmi: Mapper loaded
[9.533626] EDAC MC: Ver: 3.0.0
[9.607130] EDAC MC0: Giving out device to module i7core_edac.c controller 
i7 core #0: DEV :3f:03.0 (POLLED)
[9.607166] EDAC PCI0: Giving out device to module i7core_edac controller 
EDAC PCI controller: DEV :3f:03.0 (POLLED)
[9.607172] EDAC i7core: Driver loaded, 1 memory controller(s) found.
[9.624166] sd 2:0:0:0: Attached scsi generic sg0 type 0
[9.624197] sr 3:0:0:0: Attached scsi generic sg1 type 5
[9.697431] nouveau :01:00.0: NVIDIA GF108 (0c1000a1)
[9.706592] input: Griffin PowerMate as 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8.3/2-1.8.3:1.0/input/input9
[9.706643] usbcore: registered new interface driver powermate
[9.789145] iTCO_vendor_support: vendor-support=0
[9.790831] iTCO_wdt: I

Bug#832271: xfwm4: maximize behavior differs between screens of a dual-screen setup

2016-07-23 Thread Eric Cooper
Package: xfwm4
Version: 4.12.3-3
Severity: normal

I have a dual-monitor desktop, using this xorg.conf:
Section "Device"
  Identifier "Device"
  Driver "nouveau"
EndSection

Section "Monitor"
  Identifier "HDMI-1"
  Option "LeftOf" "DVI-I-1"
EndSection

Section "Screen"
  Identifier "Screen"
  Monitor "Monitor"
  SubSection "Display"
Virtual 3840 1200
  EndSubSection
EndSection

I have 2 xfce4-panels configured identically along the bottom of both screens.
Neither one has the "Don't reserve space on borders" option checked.

When I maximize a window on the right monitor, it "respects" the panel
and doesn't overlap with it.  When I maximize move that window to the
left monitor and maximize it, it uses the full height of the screen
and overlaps (behind) the panel at the bottom.

I've tried this with terminal, Emacs, and Chromium windows: all
produce the same behavior.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages xfwm4 depends on:
ii  libc6 2.23-1
ii  libcairo2 1.14.6-1+b1
ii  libdbus-glib-1-2  0.106-1
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.48.1-2
ii  libgtk2.0-0   2.24.30-2
ii  libpango-1.0-01.40.1-1
ii  libstartup-notification0  0.12-4
ii  libwnck22 2.30.7-5
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfce4ui-1-04.12.1-2
ii  libxfce4util7 4.12.1-2
ii  libxfconf-0-2 4.12.0-2+b1
ii  libxfixes31:5.0.2-1
ii  libxrandr22:1.5.0-1
ii  libxrender1   1:0.9.9-2

Versions of packages xfwm4 recommends:
ii  librsvg2-common  2.40.16-1

Versions of packages xfwm4 suggests:
ii  xfce4 4.12.3
ii  xfwm4-themes  4.10.0-2

-- no debconf information



Bug#831518: pulseaudio: no sound after upgrade from 8.0.2+b2 to 9.0-1.1

2016-07-16 Thread Eric Cooper
Package: pulseaudio
Version: 9.0-1.1
Severity: important

I use USB-attached speakers (Audioengine 2+) on my desktop machine.
They worked fine until I upgraded pulseaudio to version 9.  I
reinstalled the version 8 pulseaudio packages and they work again.

Before realizing it was the pulseaudio package, I tried older (4.5) and
newer (4.7) Linux kernels, but the behavior was the same.
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; enable-remixing = yes
; enable-lfe-remixing = yes
; lfe-crossover-freq = 120

; flat-volumes = yes

; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-memlock = -1
; rlimit-locks = -1
; rlimit-sigpending = -1
; rlimit-msgqueue = -1
; rlimit-nice = 31
; rlimit-rtprio = 9
; rlimit-rttime = 20

; default-sample-format = s16le
; default-sample-rate = 44100
; alternate-sample-rate = 48000
; default-sample-channels = 2
; default-channel-map = front-left,front-right

; default-fragments = 4
; default-fragment-size-msec = 25

; enable-deferred-volume = yes
; deferred-volume-safety-margin-usec = 8000
; deferred-volume-extra-delay-usec = 0
#!/usr/bin/pulseaudio -nF
#
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

# This startup script is used only if PulseAudio is started per-user
# (i.e. not in system mode)

.nofail

### Load something into the sample cache
#load-sample-lazy x11-bell /usr/share/sounds/freedesktop/stereo/bell.oga
#load-sample-lazy pulse-hotplug 
/usr/share/sounds/freedesktop/stereo/device-added.oga
#load-sample-lazy pulse-coldplug 
/usr/share/sounds/freedesktop/stereo/device-added.oga
#load-sample-lazy 

Bug#827426: golang-golang-x-tools: stringer is broken

2016-06-15 Thread Eric Cooper
Package: golang-golang-x-tools
Version: 1:0.0~git20160315.0.f42ec61-2
Severity: important

The stringer program no longer understands how to import standard Go
packages.  For example, running "stringer -type=MyType foo.go" on the following
foo.go file:

package main

import (
"fmt"
)

type MyType int

//go:generate stringer -type=MyType

const (
Alpha MyType = 1
Beta MyType = 1
Gamma MyType = 1
)

func main() {
fmt.Println(Alpha)
}


produces the error:
stringer: checking package: foo.go:4:2: could not import fmt (can't find 
import: )

Running strace shows that it's looking here:
/usr/lib/go/pkg/linux_amd64/fmt.a
But the current golang system has it here:
/usr/lib/go-1.6/pkg/linux_amd64/fmt.a

And indeed, when I removed /usr/lib/go and symlinked it to
/usr/lib/go-1.6 instead, stringer worked correctly.  But I'm not sure
if that simple fix breaks anything else ...

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages golang-golang-x-tools depends on:
ii  golang-golang-x-tools-dev  1:0.0~git20160315.0.f42ec61-2
ii  libc6  2.22-9

golang-golang-x-tools recommends no packages.

golang-golang-x-tools suggests no packages.

-- no debconf information



Bug#821334: approx: 'apt-get update' yields 'Err http://approx wheezy-updates/main amd64 Packages'

2016-04-19 Thread Eric Cooper
On Mon, Apr 18, 2016 at 09:18:51PM -0700, David Christensen wrote:
> Please leave the bug report open.

Will do.

> Perhaps if Approx saved the IP address after the first name lookup and used
> that for all transfers, Approx would be more reliable (?).

Yes, that's been on my TODO list for a while.

> As a work-around, can I specify a host that is not round-robined in my
> approx.conf file?  How do I find such hosts?

If you use the host command (from the bind9-host package at least),
you'll see all the IP addresses that a name resolves to:

$ host ftp.us.debian.org
ftp.us.debian.org has address 64.50.236.52
ftp.us.debian.org has address 64.50.233.100
ftp.us.debian.org has address 128.61.240.89
ftp.us.debian.org has address 128.30.2.26
ftp.us.debian.org has IPv6 address 2610:148:1f10:3::89

(And if you do it a few times, you'll see that they're returned in
different order, hence the problem.)

You can then find the symbolic name for one:
$ host 64.50.236.52
52.236.50.64.in-addr.arpa domain name pointer ftp-chi.osuosl.org.
and verify that it's not round-robined:
$ host ftp-chi.osuosl.org
ftp-chi.osuosl.org has address 64.50.236.52

Hope this helps.

--
Eric Cooper e c c @ c m u . e d u



Bug#821334: approx: 'apt-get update' yields 'Err http://approx wheezy-updates/main amd64 Packages'

2016-04-18 Thread Eric Cooper
On Sun, Apr 17, 2016 at 08:51:27PM -0700, David Christensen wrote:
> I didn't notice until after upgrading that 'apt-get update' and Approx
> appeared to worked correctly prior to upgrading (?).  Any ideas?

I'm not sure, but due to the way mirrors work, it's often difficult to
reproduce some problems, and they often just "go away" when you retry.

For example, the ftp.us.debian.org mirror is actually round-robined
among multiple sites.  A longstanding problem with approx is that it
resolves the name on each transfer (because I'm lazy and just pass the
name to curl).  If it resolves to different sites between the Release
file and the Packages file, and those two sites are not in sync,
the update can fail with checksum errors.

Any way, I'm going to mark this closed as of version 5.5 unless you
object.  Sorry for the inconvenience.

--
Eric Cooper e c c @ c m u . e d u



Bug#821334: approx: 'apt-get update' yields 'Err http://approx wheezy-updates/main amd64 Packages'

2016-04-17 Thread Eric Cooper
Sorry, I should have noticed sooner that you're running the version
from wheezy. Can you try installing the version from wheezy-backports:
https://packages.debian.org/wheezy-backports/approx
and see if that works better?

--
Eric Cooper e c c @ c m u . e d u



Bug#821334: approx: 'apt-get update' yields 'Err http://approx wheezy-updates/main amd64 Packages'

2016-04-17 Thread Eric Cooper
Can you please enable debugging for the approx server
(add a "$debug true" line to /etc/approx/approx.conf),
and then send me the relevant part of the log (in /var/log/daemon.log
for example) when this error occurs.  Thanks.

--
Eric Cooper e c c @ c m u . e d u



Bug#810255: approx: Approx fails to load new versions of DEP-11 icon tarballs

2016-01-08 Thread Eric Cooper
> Forgot to add: the version of apt on the client is 1.1.10

Thanks for the information.  What command on the client causes these
icon files to be fetched in such a way that the hashes are checked?
I'm running the same version of apt, and none of these files are in my
approx cache, so I'm assuming it's something other than simple apt-get
updates and upgrades.

--
Eric Cooper e c c @ c m u . e d u



Bug#810255: approx: fdssf

2016-01-07 Thread Eric Cooper
On Thu, Jan 07, 2016 at 05:18:23PM +, Phil Armstrong wrote:
> Approx breaks with the DEP-11 icon tarballs that have recently been
> introduced to the stretch archives. Even though the hash in the
> InRelease file changes, approx is not downloading the changed file and
> is delivering the previous version to clients which then fail their
> entire apt update because of this hash sum mismatch. This means that
> as long as this bug exists, it’s impossible to update a stretch Debian
> system at all using an approx caching proxy, because no apt update can
> succeed whilst a hash sum mismatch in one of the downloaded files
> exists for a given release.

I use stretch and haven't observed this yet.  Can you enable $debug in
approx.conf and send me the portion of the system log that results when
this occurs?

Also, what does "fdssf" mean?

--
Eric Cooper e c c @ c m u . e d u



Bug#744166: nouveau: GPU lockup after "read fault at 0x0000039000 [PAGE_NOT_PRESENT]"

2016-01-04 Thread Eric Cooper
Package: src:linux
Version: 4.3.3-2
Followup-For: Bug #744166

I see something like this regularly too.  Here is the latest
occurrence:

[ 1550.657540] nouveau :01:00.0: fifo: read fault at dd engine 15 
[PCE0] client 01 [PCOPY0] reason 02 [PAGE_NOT_PRESENT] on channel 0 [001fe74000 
DRM]
[ 1550.657547] nouveau :01:00.0: fifo: ce0 engine fault on channel 0, 
recovering...
[ 1580.616767] [TTM] Buffer eviction failed

Once this happens, the mouse cursor moves, but the desktop is
otherwise unresponsive. I can't use ctrl-alt-Fn to get to a text
console. All I can so is ssh in from another machine and reboot.

It seems like it always occurs when I'm interacting with a web page in
either firefox or chromium, but that might just be because that's most
of the time.

-- Package-specific info:
** Version:
Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20151207 (Debian 5.3.1-3) ) #1 SMP Debian 4.3.3-2 (2015-12-17)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64 
root=UUID=1bd202e7-8d8c-4170-8388-abddc49cd075 ro quiet

** Not tainted

** Kernel log:
...
[7.966726] [drm] Initialized drm 1.1.0 20060810
[8.025126] wmi: Mapper loaded
[8.124410] nouveau :01:00.0: NVIDIA GF108 (0c1000a1)
[8.256383] nouveau :01:00.0: bios: version 70.08.4d.00.00
[8.257378] nouveau :01:00.0: fb: 512 MiB DDR3
[8.310001] [TTM] Zone  kernel: Available graphics memory: 16471022 kiB
[8.310005] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[8.310007] [TTM] Initializing pool allocator
[8.310016] [TTM] Initializing DMA pool allocator
[8.310039] nouveau :01:00.0: DRM: VRAM: 512 MiB
[8.310042] nouveau :01:00.0: DRM: GART: 1048576 MiB
[8.310048] nouveau :01:00.0: DRM: TMDS table version 2.0
[8.310052] nouveau :01:00.0: DRM: DCB version 4.0
[8.310056] nouveau :01:00.0: DRM: DCB outp 00: 01000302 00020030
[8.310061] nouveau :01:00.0: DRM: DCB outp 01: 02000300 
[8.310065] nouveau :01:00.0: DRM: DCB outp 02: 08011392 00020020
[8.310068] nouveau :01:00.0: DRM: DCB outp 03: 04022310 
[8.310072] nouveau :01:00.0: DRM: DCB conn 00: 1030
[8.310075] nouveau :01:00.0: DRM: DCB conn 01: 2161
[8.310079] nouveau :01:00.0: DRM: DCB conn 02: 0200
[8.314933] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[8.314935] [drm] Driver supports precise vblank timestamp query.
[8.372088] nouveau :01:00.0: DRM: MM: using COPY0 for buffer copies
[8.519644] nouveau :01:00.0: DRM: allocated 1920x1200 fb: 0x6, bo 
8807f97e5000
[8.519842] fbcon: nouveaufb (fb0) is primary device
[8.612157] Console: switching to colour frame buffer device 240x75
[8.614886] nouveau :01:00.0: fb0: nouveaufb frame buffer device
[8.629094] [drm] Initialized nouveau 1.3.0 20120801 for :01:00.0 on 
minor 0
...

** PCI devices:
...
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 
440] [10de:0de0] (rev a1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:83b7]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nouveau



Bug#759657: console-setup w/ systemd forgets font setting

2015-12-12 Thread Eric Cooper
On Sat, Dec 12, 2015 at 01:52:29PM +, Brian Potkin wrote:
> On Thu 10 Dec 2015 at 03:47:24 +0100, Michael Biebl wrote:
>
> > Am 10.12.2015 um 00:55 schrieb Samuel Thibault:
> > > Eric Cooper, on Thu 19 Nov 2015 13:31:57 -0500, wrote:
> > >> While booting, it looks like the font switches from VGA to Terminus
> > >> during the boot messages.  But then the screen is cleared and the
> > >> getty login prompts are back in VGA.  If I run "setupcon" manually, it
> > >> changes to Terminus.
> > >
> > > So it seems like something is resetting the font back to VGA (and it's
> > > not console-setup, which loads Terminus).
> > >
> > > systemd people, do you have any idea?  This has started happening with
> > > the switch to systemd.
> >
> > From a cursory look, it doesn't seem to be caused by systemd itself but
> > it's a race condition and the way console-setup works. And the timing
> > under systemd might simply the different then under sysvinit (it's
> > usually faster).
> >
> > When Karsten added the dependency on udev settle, it probably just
> > changed the timing (by delaying it a little) so made it less likely to
> > happen.
> >
> > It might be, that loading the KMS module resets the font.
> > So maybe console-setup should run when hardware shows up.
> > This is a shot in the dark, but can you try and create the following
> > udev rules file:
> >
> > $ cat /etc/udev/rules.d/90-setupcon.rules
> > ACTION=="add", SUBSYSTEM=="vtconsole", KERNEL=="vtcon*",
> > RUN+="/bin/setupcon"
>
> This file does it for me up to now. After about 10 reboots the font is
> not being reset back to VGA.

Yes, this solves the problem for my system too.  Please consider
adding this to the console-setup package.

--
Eric Cooper e c c @ c m u . e d u



Bug#807138: golang: gccgo triggers ar warning message when invoked as "go -compiler=gccgo"

2015-12-05 Thread Eric Cooper
Package: golang
Version: 2:1.5.1-4
Severity: normal
Tags: upstream patch

Whenever gccgo is used via the /usr/bin/go command, it calls "ar cru ...",
which causes this warning:
$ go build -compiler=gccgo
# github.com/ecc1/primes
ar: `u' modifier ignored since `D' is the default (see `U')

Details:
$ go build -x -compiler=gccgo
WORK=/tmp/go-build529072590
mkdir -p $WORK/github.com/ecc1/primes/_obj/
mkdir -p $WORK/github.com/ecc1/primes/_obj/exe/
cd /home/ecc/go/src/github.com/ecc1/primes
/usr/bin/gccgo -I $WORK -c -g -m64 
-fgo-relative-import-path=_/home/ecc/go/src/github.com/ecc1/primes -o 
$WORK/github.com/ecc1/primes/_obj/_go_.o ./primes.go
ar cru $WORK/github.com/ecc1/libprimes.a 
$WORK/github.com/ecc1/primes/_obj/_go_.o
# github.com/ecc1/primes
ar: `u' modifier ignored since `D' is the default (see `U')
cd .
/usr/bin/gccgo -o $WORK/github.com/ecc1/primes/_obj/exe/a.out 
$WORK/github.com/ecc1/primes/_obj/_go_.o -Wl,-( -m64 -Wl,-)
mv $WORK/github.com/ecc1/primes/_obj/exe/a.out primes

The attached patch simply uses "ar cr" instead.  The extra I/O for
unchanged archive members is probably negligible.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gccgo depends on:
ii  cpp  4:5.2.1-8
ii  gcc  4:5.2.1-8
ii  gccgo-5  5.2.1-23

gccgo recommends no packages.

Versions of packages gccgo suggests:
pn  gccgo-multilib  

-- no debconf information

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages golang depends on:
ii  golang-doc  2:1.5.1-4
ii  golang-go   2:1.5.1-4
ii  golang-src  2:1.5.1-4

golang recommends no packages.

golang suggests no packages.

-- no debconf information
--- src/cmd/go/build.go~	2015-09-08 21:24:01.0 -0400
+++ src/cmd/go/build.go	2015-12-05 14:08:48.360369642 -0500
@@ -2448,7 +2448,7 @@
 	for _, f := range ofiles {
 		absOfiles = append(absOfiles, mkAbs(objDir, f))
 	}
-	return b.run(p.Dir, p.ImportPath, nil, "ar", "cru", mkAbs(objDir, afile), absOfiles)
+	return b.run(p.Dir, p.ImportPath, nil, "ar", "cr", mkAbs(objDir, afile), absOfiles)
 }
 
 func (tools gccgoToolchain) ld(b *builder, root *action, out string, allactions []*action, mainpkg string, ofiles []string) error {


Bug#807136: golang: FTBFS due to new binutils relocations

2015-12-05 Thread Eric Cooper
Package: golang
Version: 2:1.5.1-4
Severity: normal
Tags: upstream patch

Building golang fails with these errors:

...
# cmd/trace
/build/golang-1.5.1/pkg/linux_amd64/runtime/cgo.a(_all.o): unknown 
relocation type 42; compiled without -fpic?
/build/golang-1.5.1/pkg/linux_amd64/runtime/cgo.a(_all.o): unknown 
relocation type 42; compiled without -fpic?
/build/golang-1.5.1/pkg/linux_amd64/runtime/cgo.a(_all.o): unknown 
relocation type 42; compiled without -fpic?
runtime/cgo(.text): unexpected relocation type 298
runtime/cgo(.text): unexpected relocation type 298
runtime/cgo(.text): unexpected relocation type 298
# cmd/pprof
/build/golang-1.5.1/pkg/linux_amd64/runtime/cgo.a(_all.o): unknown 
relocation type 42; compiled without -fpic?
/build/golang-1.5.1/pkg/linux_amd64/runtime/cgo.a(_all.o): unknown 
relocation type 42; compiled without -fpic?
/build/golang-1.5.1/pkg/linux_amd64/runtime/cgo.a(_all.o): unknown 
relocation type 42; compiled without -fpic?
runtime/cgo(.text): unexpected relocation type 298
runtime/cgo(.text): unexpected relocation type 298
runtime/cgo(.text): unexpected relocation type 298
# cmd/go
/build/golang-1.5.1/pkg/linux_amd64/runtime/cgo.a(_all.o): unknown 
relocation type 42; compiled without -fpic?
/build/golang-1.5.1/pkg/linux_amd64/runtime/cgo.a(_all.o): unknown 
relocation type 42; compiled without -fpic?
/build/golang-1.5.1/pkg/linux_amd64/runtime/cgo.a(_all.o): unknown 
relocation type 42; compiled without -fpic?
runtime/cgo(.text): unexpected relocation type 298
runtime/cgo(.text): unexpected relocation type 298
runtime/cgo(.text): unexpected relocation type 298
debian/rules:62: recipe for target 'override_dh_auto_build-arch' failed
make[1]: *** [override_dh_auto_build-arch] Error 2
make[1]: Leaving directory '/build/golang-1.5.1'
debian/rules:15: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

The problem is fixed upstream here:

https://github.com/golang/go/commit/914db9f060b1fd3eb1f74d48f3bd46a73d4ae9c7

but that commit does not apply cleanly to the current Debian version.
I've attached an equivalent patch that does, but I didn't manage to
preserve the original author, date, etc.  Please use the original
metadata from the github commit if you decide to apply this.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages golang depends on:
ii  golang-doc  2:1.5.1-4
ii  golang-go   2:1.5.1-4
ii  golang-src  2:1.5.1-4

golang recommends no packages.

golang suggests no packages.

-- no debconf information
>From 716b8354f9fba9e67543c07c91438fa382046023 Mon Sep 17 00:00:00 2001
From: Eric Cooper 
Date: Sat, 5 Dec 2015 15:19:25 -0500
Subject: [PATCH 3/3] The GNU binutils recently picked up support for new
 386/amd64 relocations. Add support for them in the Go linker when doing an
 internal link.

The 386 relocation R_386_GOT32X was proposed in
https://groups.google.com/forum/#!topic/ia32-abi/GbJJskkid4I .  It can
be treated as identical to the R_386_GOT32 relocation.

The amd64 relocations R_X86_64_GOTPCRELX and R_X86_64_REX_GOTPCRELX were
proposed in
https://groups.google.com/forum/#!topic/x86-64-abi/n9AWHogmVY0 .  They
can both be treated as identical to the R_X86_64_GOTPCREL relocation.

The purpose of the new relocations is to permit additional linker
relaxations in some cases.  We do not attempt to support those cases.

While we're at it, remove the unused and in some cases out of date
_COUNT names from ld/elf.go.

Fixes #13114.

Change-Id: I34ef07f6fcd00cdd2996038ecf46bb77a49e968b
Reviewed-on: https://go-review.googlesource.com/16529
Reviewed-by: Minux Ma 
Signed-off-by: Eric Cooper 
---
 src/cmd/link/internal/amd64/asm.go |   2 +-
 src/cmd/link/internal/ld/elf.go| 141 +
 src/cmd/link/internal/ld/ldelf.go  |   3 +
 src/cmd/link/internal/x86/asm.go   |   2 +-
 4 files changed, 86 insertions(+), 62 deletions(-)

diff --git a/src/cmd/link/internal/amd64/asm.go b/src/cmd/link/internal/amd64/asm.go
index 74ec9dd..4eb2092 100644
--- a/src/cmd/link/internal/amd64/asm.go
+++ b/src/cmd/link/internal/amd64/asm.go
@@ -141,7 +141,7 @@ func adddynrel(s *ld.LSym, r *ld.Reloc) {
 
 		return
 
-	case 256 + ld.R_X86_64_GOTPCREL:
+	case 256 + ld.R_X86_64_GOTPCREL, 256 + ld.R_X86_64_GOTPCRELX, 256 + ld.R_X86_64_REX_GOTPCRELX:
 		if targ.Type != obj.SDYNIMPORT {
 			// have symbol
 			if r.Off >= 2 && s.P[r.Off-2] == 0x8b {
diff --git a/src/cmd/link

Bug#807007: xserver-xorg-video-nouveau: graphics freeze with PCE0 engine fault

2015-12-03 Thread Eric Cooper
Package: xserver-xorg-video-nouveau
Version: 1:1.0.11-1+b1
Severity: normal

I get these error messages and then the graphics system is unresponsive:

[287179.390141] nouveau E[   PFIFO][:01:00.0] read fault at 0xe9 
[PAGE_NOT_PRESENT] from PCE0/PCOPY0 on channel 0x001fdb2000 [DRM]
[287179.390148] nouveau E[   PFIFO][:01:00.0] PCE0 engine fault on channel 
0, recovering...

The only thing I can do is ssh in from another machine and reboot.

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jun 20  2011 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Oct 27 19:43 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108 [GeForce GT 
440] [10de:0de0] (rev a1)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 281 Oct  9  2014 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
Section "Device"
  Identifier "Device"
  Driver "nouveau"
EndSection

Section "Monitor"
  Identifier "HDMI-1"
  Option "LeftOf" "DVI-I-1"
EndSection

Section "Screen"
  Identifier "Screen"
  Monitor "Monitor"
  SubSection "Display"
Virtual 3840 1200
  EndSubSection
EndSection

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.2.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.3 
(Debian 4.9.3-5) ) #1 SMP Debian 4.2.6-1 (2015-11-10)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 33983 Oct 15 06:01 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 13587.481]
X.Org X Server 1.17.2
Release Date: 2015-06-16
[ 13587.481] X Protocol Version 11, Revision 0
[ 13587.481] Build Operating System: Linux 4.1.0 x86_64 Debian
[ 13587.481] Current Operating System: Linux stratocaster 4.2.0-1-amd64 #1 SMP 
Debian 4.2.1-2 (2015-09-27) x86_64
[ 13587.481] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-1-amd64 
root=UUID=a89ff769-8289-453c-9ae3-665caa5ec8a7 ro quiet
[ 13587.481] Build Date: 11 August 2015  10:51:15AM
[ 13587.481] xorg-server 2:1.17.2-1.1 (http://www.debian.org/support)
[ 13587.481] Current version of pixman: 0.33.2
[ 13587.481]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 13587.481] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 13587.481] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 12 18:07:08 
2015
[ 13587.510] (==) Using config file: "/etc/X11/xorg.conf"
[ 13587.510] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 13587.538] (==) No Layout section.  Using the first Screen section.
[ 13587.538] (**) |-->Screen "Screen" (0)
[ 13587.538] (**) |   |-->Monitor ""
[ 13587.538] (==) No device specified for screen "Screen".
Using the first device section listed.
[ 13587.538] (**) |   |-->Device "Device"
[ 13587.538] (==) No monitor specified for screen "Screen".
Using a default monitor configuration.
[ 13587.538] (==) Automatically adding devices
[ 13587.538] (==) Automatically enabling devices
[ 13587.538] (==) Automatically adding GPU devices
[ 13587.577] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 13587.577]Entry deleted from font path.
[ 13587.609] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 13587.609] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 13587.609] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[ 13587.609] (II) Loader magic: 0x55977aaa8d40
[ 13587.609] (II) Module ABI versions:
[ 13587.609]X.Org ANSI C Emulation: 0.4
[ 13587.609]X.Org Video Driver: 19.0
[ 13587.609]X.Org XInput driver : 21.0
[ 13587.609]X.Org Server Extension : 9.0
[ 13587.610] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 13587.611] (--) PCI:*(0:1:0:0) 10de:0de0:1043:83b7 rev 161, Mem @ 
0xf600/16777216, 0xe800/134217728, 0xf200/33554432, I/O @ 
0xcc00/128, BIOS @ 0x/524288
[ 13587.611] (II) LoadModule: "glx"
[ 13587.632] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 13587.789] (II) Module glx: vendor="X.Org Foundation"
[ 13587.789]compiled for 1.17.2, module version = 1.0.0
[ 13587.789]ABI class: X.Org Server Extension, ve

Bug#805583: minidlna: please add option to remain in foreground

2015-11-19 Thread Eric Cooper
Package: minidlna
Version: 1.1.4+dfsg-4+b1
Severity: wishlist

When running minidlnad in a Docker container, it would be useful to
have minidlnad run in the foreground, but *without* all the debugging
output that "-d" produces. Please consider separate "--foreground" and
"--debug" flags ("-d" could imply both for compatibility).  Thanks.



Bug#805582: minidlna: man page has incorrect default location for pid-file

2015-11-19 Thread Eric Cooper
Package: minidlna
Version: 1.1.4+dfsg-4+b1
Severity: minor

minidlnad creates its pid-file by default in
/run/minidlna/minidlna.pid, not /run/minidlna.pid as the manpage says.



Bug#759657: console-setup w/ systemd forgets font setting

2015-11-19 Thread Eric Cooper
Package: console-setup
Version: 1.134
Followup-For: Bug #759657

I see the same problem on every reboot.

While booting, it looks like the font switches from VGA to Terminus
during the boot messages.  But then the screen is cleared and the
getty login prompts are back in VGA.  If I run "setupcon" manually, it
changes to Terminus.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages console-setup depends on:
ii  console-setup-linux 1.134
ii  debconf 1.5.58
ii  keyboard-configuration  1.134
ii  xkb-data2.16-1

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales   2.19-22
ii  lsb-base  9.20150917

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.58
ii  initscripts 2.88dsf-59.2
ii  liblocale-gettext-perl  1.07-1

Versions of packages console-setup-linux depends on:
ii  kbd 1.15.5-2
ii  keyboard-configuration  1.134

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common  
pn  console-data
pn  console-tools   
ii  kbd 1.15.5-2

-- debconf information:
  keyboard-configuration/modelcode: ibm_spacesaver
  keyboard-configuration/store_defaults_in_debconf_db: true
* console-setup/charmap47: UTF-8
  console-setup/framebuffer_only:
  keyboard-configuration/xkb-keymap: us
  keyboard-configuration/layoutcode: us
* console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
  keyboard-configuration/toggle: No toggling
  console-setup/guess_font:
  console-setup/fontsize-text47: 8x16
  keyboard-configuration/optionscode: ctrl:nocaps
* console-setup/fontsize-fb47: 8x16
  keyboard-configuration/unsupported_layout: true
* keyboard-configuration/compose: No compose key
* console-setup/fontface47: Terminus
  keyboard-configuration/variantcode:
  console-setup/use_system_font:
  console-setup/fontsize: 8x16
* keyboard-configuration/variant: English (US)
* keyboard-configuration/unsupported_config_options: true
  keyboard-configuration/other:
  keyboard-configuration/switch: No temporary switch
  keyboard-configuration/layout:
  debian-installer/console-setup-udeb/title:
  console-setup/store_defaults_in_debconf_db: true
  console-setup/codesetcode: Lat15
  keyboard-configuration/unsupported_config_layout: true
  keyboard-configuration/unsupported_options: true
* keyboard-configuration/model: IBM Space Saver
* keyboard-configuration/altgr: The default for the keyboard layout
* keyboard-configuration/ctrl_alt_bksp: false



Bug#805579: nouveau: lockup with "[TTM] Buffer eviction failed"

2015-11-19 Thread Eric Cooper
Package: libdrm-nouveau2
Version: 2.4.65-3
Severity: normal

My graphics system occasionally locks up, with error messages like the
following in the log:

[163467.868937] nouveau E[   PFIFO][:01:00.0] read fault at 0xe4f000 
[PAGE_NOT_PRESENT] from PCE0/PCOPY0 on channel 0x001fdb2000 [DRM]
[163467.868945] nouveau E[   PFIFO][:01:00.0] PCE0 engine fault on channel 
0, recovering...
[163507.492514] [TTM] Buffer eviction failed
[163537.456185] [TTM] Buffer eviction failed
[163567.483936] [TTM] Buffer eviction failed

When it happens, I am still able to ssh in from another machine, but
the shutdown also hangs and I have to manually power cycle it.

lspci says my video card is: NVIDIA Corporation GF108 [GeForce GT 440] (rev a1)
Here are the nouveau messages during startup:

[7.485439] nouveau  [  DEVICE][:01:00.0] BOOT0  : 0x0c1000a1
[7.485442] nouveau  [  DEVICE][:01:00.0] Chipset: GF108 (NVC1)
[7.485444] nouveau  [  DEVICE][:01:00.0] Family : NVC0
[7.617965] nouveau  [   VBIOS][:01:00.0] using image from PRAMIN
[7.618041] nouveau  [   VBIOS][:01:00.0] BIT signature found
[7.618042] nouveau  [   VBIOS][:01:00.0] version 70.08.4d.00.00
[7.618357] nouveau  [ PMC][:01:00.0] MSI interrupts enabled
[7.618387] nouveau W[ PFB][:01:00.0][0x] reclocking of this 
ram type unsupported
[7.618389] nouveau  [ PFB][:01:00.0] RAM type: DDR3
[7.618390] nouveau  [ PFB][:01:00.0] RAM size: 512 MiB
[7.618391] nouveau  [ PFB][:01:00.0]ZCOMP: 0 tags
[7.650175] nouveau  [  PTHERM][:01:00.0] FAN control: none / external
[7.650189] nouveau  [  PTHERM][:01:00.0] fan management: automatic
[7.650212] nouveau  [  PTHERM][:01:00.0] internal sensor: yes
[7.670155] nouveau  [ CLK][:01:00.0] 03: core 50 MHz memory 135 MHz
[7.670159] nouveau  [ CLK][:01:00.0] 07: core 405 MHz memory 324 MHz
[7.670162] nouveau  [ CLK][:01:00.0] 0f: core 810 MHz memory 900 MHz
[7.670310] nouveau  [ CLK][:01:00.0] --: core 405 MHz memory 324 MHz
[7.679396] nouveau  [ DRM] VRAM: 512 MiB
[7.679398] nouveau  [ DRM] GART: 1048576 MiB
[7.679404] nouveau  [ DRM] TMDS table version 2.0
[7.679407] nouveau  [ DRM] DCB version 4.0
[7.679410] nouveau  [ DRM] DCB outp 00: 01000302 00020030
[7.679414] nouveau  [ DRM] DCB outp 01: 02000300 
[7.679417] nouveau  [ DRM] DCB outp 02: 08011392 00020020
[7.679420] nouveau  [ DRM] DCB outp 03: 04022310 
[7.679423] nouveau  [ DRM] DCB conn 00: 1030
[7.679426] nouveau  [ DRM] DCB conn 01: 2161
[7.679429] nouveau  [ DRM] DCB conn 02: 0200
[7.694215] nouveau  [ DRM] MM: using COPY0 for buffer copies
[7.852772] nouveau  [ DRM] allocated 1920x1200 fb: 0x6, bo 
8807fa975000
[7.852873] fbcon: nouveaufb (fb0) is primary device
[7.948094] nouveau :01:00.0: fb0: nouveaufb frame buffer device
[7.948096] nouveau :01:00.0: registered panic notifier
[7.965941] [drm] Initialized nouveau 1.2.2 20120801 for :01:00.0 on 
minor 0

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages libdrm-nouveau2 depends on:
ii  libc62.19-22
ii  libdrm2  2.4.65-3

libdrm-nouveau2 recommends no packages.

libdrm-nouveau2 suggests no packages.

-- no debconf information



Bug#804812: blkid: fails silently if not root

2015-11-11 Thread Eric Cooper
Package: util-linux
Version: 2.27.1-1
Severity: normal

The blkid command returns successfully, with no error messages, when
it lacks permission to open a device (or if the device does not exist):

$ blkid /dev/sda1
$ echo $?
0
$ sudo blkid /dev/sda1
/dev/sda1: UUID=...



Bug#803115: flash-kernel: please provide an option to disable creation of backup files

2015-11-07 Thread Eric Cooper
Package: flash-kernel
Version: 3.48
Followup-For: Bug #803115

Here's a patch, tested on my Seagate Dockstar.

Default behavior:
$ sudo flash-kernel
DTB: kirkwood-dockstar.dtb
Installing kirkwood-dockstar.dtb into 
/boot/dtbs/4.2.0-0.bpo.1-kirkwood/kirkwood-dockstar.dtb
Taking backup of kirkwood-dockstar.dtb.
Installing new kirkwood-dockstar.dtb.
flash-kernel: installing version 4.2.0-0.bpo.1-kirkwood
flash-kernel: appending 
/usr/lib/linux-image-4.2.0-0.bpo.1-kirkwood/kirkwood-dockstar.dtb to kernel
Generating kernel u-boot image... done.
Taking backup of uImage.
Installing new uImage.
Generating initramfs u-boot image... done.
Taking backup of uInitrd.
Installing new uInitrd.
Taking backup of dtb.
Installing new dtb.

New behavior with NO_BACKUP_FILES=true set in /etc/default/flash-kernel:

$ sudo flash-kernel
DTB: kirkwood-dockstar.dtb
Installing kirkwood-dockstar.dtb into 
/boot/dtbs/4.2.0-0.bpo.1-kirkwood/kirkwood-dockstar.dtb
Skipping backup of kirkwood-dockstar.dtb.
Installing new kirkwood-dockstar.dtb.
flash-kernel: installing version 4.2.0-0.bpo.1-kirkwood
flash-kernel: appending 
/usr/lib/linux-image-4.2.0-0.bpo.1-kirkwood/kirkwood-dockstar.dtb to kernel
Generating kernel u-boot image... done.
Skipping backup of uImage.
Installing new uImage.
Generating initramfs u-boot image... done.
Skipping backup of uInitrd.
Installing new uInitrd.
Skipping backup of dtb.
Installing new dtb.
>From e111d107a0e9453d0af0eb0ed4708a1aea1f901e Mon Sep 17 00:00:00 2001
From: Eric Cooper 
Date: Sat, 7 Nov 2015 13:15:39 -0500
Subject: [PATCH] Add NO_BACKUP_FILES option to /etc/default/flash-kernel.

If set, no backups of kernel, initrd, and dtb files will be created,
to save space on systems with limited storage.

Signed-off-by: Eric Cooper 
---
 README|  9 ++---
 functions | 18 --
 2 files changed, 22 insertions(+), 5 deletions(-)

diff --git a/README b/README
index 4ca5a22..bc7493c 100644
--- a/README
+++ b/README
@@ -191,9 +191,12 @@ Configuration files currently supported:
   script snippets. See "Adding U-Boot Commands for Pre-Boot Execution"
   below for more details.
 
-* /etc/default/flash-kernel currently contains a single variable,
-  LINUX_KERNEL_CMDLINE, which should be used by bootscripts to set kernel
-  options.
+* /etc/default/flash-kernel currently contains the following variables:
+- LINUX_KERNEL_CMDLINE, which should be used by bootscripts to set kernel
+  options.
+- NO_BACKUP_FILES, which if set to "true" or "yes" will prevent
+  flash-kernel from creating backup versions of kernel, initrd,
+  and dtb files.
 
 
 Adding U-Boot Commands for Pre-Boot Execution
diff --git a/functions b/functions
index 35d872b..9bbef2c 100644
--- a/functions
+++ b/functions
@@ -404,13 +404,27 @@ mkimage_multi() {
 	echo "done." >&2
 }
 
+# Return a nonempty string *unless* NO_BACKUP_FILES is set.
+get_backup_preference() {
+. /etc/default/flash-kernel
+	case $(echo "$NO_BACKUP_FILES" | tr '[:upper:]' '[:lower:]') in
+	true|yes|1) ;;
+	*) echo yes ;;
+	esac
+}
+
 backup_and_install() {
 	local source="$1"
 	local dest="$2"
+	local do_backups=$(get_backup_preference)
 
 	if [ -e "$dest" ]; then
-		echo "Taking backup of $(basename "$dest")." >&2
-		mv "$dest" "$dest.bak"
+		if [ -n "$do_backups" ]; then
+			echo "Taking backup of $(basename "$dest")." >&2
+			mv "$dest" "$dest.bak"
+		else
+			echo "Skipping backup of $(basename "$dest")." >&2
+		fi
 	fi
 	echo "Installing new $(basename "$dest")." >&2
 	mv "$source" "$dest"
-- 
2.6.2



Bug#804359: flash-kernel: Little-endianness is tested incorrectly for NSLU2

2015-11-07 Thread Eric Cooper
Package: flash-kernel
Version: 3.48
Severity: normal
Tags: patch

The nslu2_swap() function incorrectly tests $little_endian and will
always think it is true.

Untested patch attached since I don't have a slug.
>From e719eabe8f4640fb192dae4ce44235653ce8e803 Mon Sep 17 00:00:00 2001
From: Eric Cooper 
Date: Sat, 7 Nov 2015 12:58:04 -0500
Subject: [PATCH] Test $little_endian correctly in nslu2_swap()

Signed-off-by: Eric Cooper 
---
 functions | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/functions b/functions
index ea69df7..35d872b 100644
--- a/functions
+++ b/functions
@@ -425,7 +425,7 @@ sercomm_header() {
 }
 
 nslu2_swap() {
-	if [ "$little_endian" ]; then
+	if [ "$little_endian" -eq 1 ]; then
 		devio "<<$1" "xp $,4"
 	else
 		cat "$1"
-- 
2.6.2



Bug#803115: flash-kernel: please provide an option to disable creation of backup files

2015-10-26 Thread Eric Cooper
Package: flash-kernel
Version: 3.46
Severity: wishlist

I'd like an option (configurable in /etc/default/flash-kernel ideally)
to prevent flash-kernel from creating .bak files for uImage, uInitrd,
and dtb, in order to same space on my system.  I'm willing to live
dangerously and keep a serial and JTAG cable handy :-)



Bug#799935: emacs24: double desktop entry in .desktop file does not work in cinnamon

2015-10-12 Thread Eric Cooper
Package: emacs24
Version: 24.5+1-2
Followup-For: Bug #799935

The same problem occurs in my XFCE desktop environment.



Bug#799386: docker.io: docker daemon startup fails with aufs stroage driver not supported

2015-09-18 Thread Eric Cooper
Package: docker.io
Version: 1.7.1~dfsg1-1
Followup-For: Bug #799386

Sorry, I changed "-s" to the wrong long option in the previous
report, without checking first.  It should be:

/etc/default/docker changed:
DOCKER_OPTS="--storage-driver overlay"



Bug#799386: docker.io: docker daemon startup fails with aufs stroage driver not supported

2015-09-18 Thread Eric Cooper
Package: docker.io
Version: 1.7.1~dfsg1-1
Severity: important

The docker daemon fails to start after installation of docker.io on my system:

Sep 18 12:03:08 stratocaster systemd[1]: Starting Docker Socket for the API.
Sep 18 12:03:08 stratocaster systemd[1]: Listening on Docker Socket for the 
API.
Sep 18 12:03:08 stratocaster systemd[1]: Started Docker Application 
Container Engine.
Sep 18 12:03:08 stratocaster docker[13720]: 
time="2015-09-18T12:03:08.067458484-04:00" level=error msg="[graphdriver] prior 
storage driver \"aufs\" failed: driver not supported"
Sep 18 12:03:08 stratocaster docker[13720]: 
time="2015-09-18T12:03:08.067524867-04:00" level=fatal msg="Error starting 
daemon: error initializing graphdriver: driver not supported"
Sep 18 12:03:08 stratocaster systemd[1]: docker.service: Main process 
exited, code=exited, status=1/FAILURE
Sep 18 12:03:08 stratocaster systemd[1]: docker.service: Unit entered 
failed state.

Once I add DOCKER_OPTS="--storage-opt overlay" to /etc/default/docker
 it starts correctly.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages docker.io depends on:
ii  adduser  3.113+nmu3
ii  init-system-helpers  1.23
ii  iptables 1.4.21-2+b1
ii  libapparmor1 2.9.2-3
ii  libc62.19-19
ii  libdevmapper1.02.1   2:1.02.104-1
ii  libsqlite3-0 3.8.11.1-1
ii  perl 5.20.2-6

Versions of packages docker.io recommends:
ii  aufs-tools1:3.2+20130722-1.1
ii  ca-certificates   20150426
pn  cgroupfs-mount | cgroup-lite  
ii  git   1:2.5.1-1
ii  xz-utils  5.1.1alpha+20120614-2.1

Versions of packages docker.io suggests:
pn  btrfs-tools  
ii  debootstrap  1.0.72
pn  lxc  
pn  rinse
pn  zfs-fuse | zfsutils  

-- Configuration Files:
/etc/default/docker changed:
DOCKER_OPTS="--storage-opt overlay"


-- no debconf information



Bug#798285: iceweasel: screen corruption in tab titles

2015-09-07 Thread Eric Cooper
Package: iceweasel
Version: 40.0.3-3
Severity: minor

(This problem appears to be similar to #725726, but occurs with
newly-created tabs.)

The title text displayed in tabs gets slightly corrupted.  I've attached
two examples.  When I mouse over the corrupted tab titles, they
redisplay cleanly.  I haven't yet narrowed down a repeatable series of
actions that causes them to be corrupted.

-- Package-specific info:

-- Extensions information
Name: Adblock Plus
Location: 
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}
Package: xul-ext-adblock-plus
Status: enabled

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

Name: Live HTTP headers
Location: 
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{8f8fe09b-0bd3-4470-bc1b-8cad42b8203a}
Package: xul-ext-livehttpheaders
Status: enabled

-- Plugins information
Name: Java(TM) Plug-in 10.51.2 (10.51.2)
Location: /usr/lib/jvm/jdk-7-oracle-x64/jre/lib/amd64/libnpjp2.so
Package: oracle-java7-jdk
Status: enabled

Name: MozPlugger 1.14.5 handles QuickTime and Windows Media Player Plugin 
(1.14.5)
Location: /usr/lib/mozilla/plugins/mozplugger.so
Package: mozplugger
Status: enabled

Name: Shockwave Flash (11.2.202.508)
Location: /usr/lib/flashplugin-nonfree/libflashplayer.so
Status: enabled


-- Addons package information
ii  iceweasel  40.0.3-3 amd64Web browser based on Firefox
ii  mozplugger 1.14.5-2 amd64Plugin allowing external viewers
ii  oracle-java7-j 7u51 amd64Java™ Platform, Standard Editio
ii  xul-ext-adbloc 2.6.10+dfsg- all  advertisement blocking extension
ii  xul-ext-liveht 0.17-4   all  add information about HTTP header

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages iceweasel depends on:
ii  debianutils   4.5.1
ii  fontconfig2.11.0-6.3
ii  libasound21.0.29-1
ii  libatk1.0-0   2.16.0-2
ii  libc6 2.19-19
ii  libcairo2 1.14.2-2
ii  libdbus-1-3   1.8.20-1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2
ii  libffi6   3.2.1-3
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-4
ii  libgcc1   1:5.2.1-16
ii  libgdk-pixbuf2.0-02.31.5-1
ii  libglib2.0-0  2.44.1-1.1
ii  libgtk2.0-0   2.24.28-1
ii  libhunspell-1.3-0 1.3.3-3
ii  libnspr4  2:4.10.9-2
ii  libnss3   2:3.20-1
ii  libpango-1.0-01.36.8-3
ii  libsqlite3-0  3.8.11.1-1
ii  libstartup-notification0  0.12-4
ii  libstdc++65.2.1-16
ii  libvpx2   1.4.0-4
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.8-1+b1
ii  libxt61:1.1.4-1+b1
ii  procps2:3.3.10-2
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages iceweasel recommends:
ii  gstreamer1.0-libav 1.4.5-3
ii  gstreamer1.0-plugins-good  1.4.5-2+b1

Versions of packages iceweasel suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-2.1
ii  libgnomeui-0   2.24.5-3
ii  libgssapi-krb5-2   1.13.2+dfsg-2
ii  mozplugger 1.14.5-2

-- no debconf information


Bug#797266: xserver-xorg-video-nouveau: freeze triggered by chromium

2015-08-28 Thread Eric Cooper
Package: xserver-xorg-video-nouveau
Version: 1:1.0.11-1+b1
Severity: normal

When I use chromium as my default browser, my system eventually
freezes, with the error messages listed below.  I'm currently using
chromium 44.0.2403.157-1 from sid, but the version from testing causes
the same problem.

It doesn't happen immediately, but typically within a day of using
multiple windows each with multiple tabs.  I've never seen any other
application trigger it, in particular the same kind of session using
iceweasel seems to work OK.

So this may be a bug in chromium, but the nouveau driver
shouldn't lock up due to misbehaving clients either.

[182651.686746] nouveau E[chromium[10939]] fail set_domain
[182651.686750] nouveau E[chromium[10939]] validating bo list
[182651.686754] nouveau E[chromium[10939]] validate: -22
[182720.798136] nouveau E[chromium[10939]] fail set_domain
[182720.798142] nouveau E[chromium[10939]] validating bo list
[182720.798148] nouveau E[chromium[10939]] validate: -22
[182742.252284] nouveau E[chromium[10939]] fail set_domain
[182742.252288] nouveau E[chromium[10939]] validating bo list
[182742.252292] nouveau E[chromium[10939]] validate: -22
[182742.252780] nouveau E[chromium[10939]] fail set_domain
[182742.252783] nouveau E[chromium[10939]] validating bo list
[182742.252786] nouveau E[chromium[10939]] validate: -22
[182742.253168] nouveau E[chromium[10939]] fail set_domain
[182742.253171] nouveau E[chromium[10939]] validating bo list
[182742.253174] nouveau E[chromium[10939]] validate: -22
[182742.253551] nouveau E[chromium[10939]] fail set_domain
[182742.253554] nouveau E[chromium[10939]] validating bo list
[182742.253556] nouveau E[chromium[10939]] validate: -22
[182742.253903] nouveau E[chromium[10939]] fail set_domain
[182742.253906] nouveau E[chromium[10939]] validating bo list
[182742.253909] nouveau E[chromium[10939]] validate: -22
[182742.254241] nouveau E[chromium[10939]] fail set_domain
[182742.254244] nouveau E[chromium[10939]] validating bo list
[182742.254247] nouveau E[chromium[10939]] validate: -22
[182742.254607] nouveau E[chromium[10939]] fail set_domain
[182742.254610] nouveau E[chromium[10939]] validating bo list
[182742.254613] nouveau E[chromium[10939]] validate: -22
[182742.255327] nouveau E[chromium[10939]] fail set_domain
[182742.255330] nouveau E[chromium[10939]] validating bo list
[182742.255333] nouveau E[chromium[10939]] validate: -22
[182742.255701] nouveau E[chromium[10939]] fail set_domain
[182742.255704] nouveau E[chromium[10939]] validating bo list
[182742.255706] nouveau E[chromium[10939]] validate: -22
[182742.256083] nouveau E[chromium[10939]] fail set_domain
[182742.256086] nouveau E[chromium[10939]] validating bo list
[182742.256089] nouveau E[chromium[10939]] validate: -22
[182742.256462] nouveau E[chromium[10939]] fail set_domain
[182742.256464] nouveau E[chromium[10939]] validating bo list
[182742.256467] nouveau E[chromium[10939]] validate: -22
[182742.256560] nouveau E[chromium[10939]] fail set_domain
[182742.256563] nouveau E[chromium[10939]] validating bo list
[182742.256565] nouveau E[chromium[10939]] validate: -22
[182742.263233] nouveau E[chromium[10939]] fail set_domain
[182742.263236] nouveau E[chromium[10939]] validating bo list
[182742.263238] nouveau E[chromium[10939]] validate: -22
[182742.264461] nouveau E[chromium[10939]] fail set_domain
[182742.264467] nouveau E[chromium[10939]] validating bo list
[182742.264474] nouveau E[chromium[10939]] validate: -22
[182742.295788] nouveau E[  PGRAPH][:01:00.0] TRAP ch 6 [0x001fb04000 
chromium[10939]]
[182742.295805] nouveau E[  PGRAPH][:01:00.0] GPC0/PROP trap: 
ZETA_STORAGE_TYPE_MISMATCH
[182742.295813] nouveau E[  PGRAPH][:01:00.0] x = 1016, y = 40, format = 0, 
storage type = fe
[184443.182469] nouveau E[chromium[10939]] fail set_domain
[184443.182472] nouveau E[chromium[10939]] validating bo list
[184443.182475] nouveau E[chromium[10939]] validate: -22
[184443.183217] nouveau E[chromium[10939]] fail set_domain
[184443.183219] nouveau E[chromium[10939]] validating bo list
[184443.183222] nouveau E[chromium[10939]] validate: -22
[184523.178257] nouveau E[chromium[10939]] fail set_domain
[184523.178263] nouveau E[chromium[10939]] validating bo list
[184523.178268] nouveau E[chromium[10939]] validate: -22
[184523.180359] nouveau E[chromium[10939]] fail set_domain
[184523.180369] nouveau E[chromium[10939]] validating bo list
[184523.180377] nouveau E[chromium[10939]] validate: -22
[184630.755855] nouveau E[chromium[10939]] fail set_domain
[184630.755861] nouveau E[chromium[10939]] validating bo list
[184630.755868] nouveau E[chromium[10939]] validate: -22
[184773.627930] nouveau E[chromium[10939]] fail set_domain
[184773.627935] nouveau E[chromium[10939]] validating bo list
[184773.627944] nouveau E[chromium[10939]] validate: -22
[184773.660304] nouveau E[chromium[10939]] fail set_domain
[184773.660308] nouveau E[chromium[10939]] validating bo list
[184773.660314] nouveau E[chromiu

Bug#793435: v4l2loopback-source: v4l2loopback_formats.h missing

2015-07-23 Thread Eric Cooper
Package: v4l2loopback-source
Version: 0.9.1-1
Severity: important

Looks like this file was omitted from the -source version, but it's
present in the -dkms version.

It causes this failure when using module-assistant:

  CC [M]  /usr/src/modules/v4l2loopback/v4l2loopback.o
  /usr/src/modules/v4l2loopback/v4l2loopback.c:376:34: fatal error: 
v4l2loopback_formats.h: No such file or directory
   #include "v4l2loopback_formats.h"
 ^
 compilation terminated.

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

Kernel: Linux 3.16.0-4-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
Init: systemd (via /run/systemd/system)

Versions of packages v4l2loopback-source depends on:
ii  bzip2  1.0.6-8
ii  debhelper  9.20150628
ii  make   4.0-8.1

Versions of packages v4l2loopback-source recommends:
ii  module-assistant  0.11.7

v4l2loopback-source 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#789133: transition: ocaml 4.02.2

2015-06-23 Thread Eric Cooper
I've updated approx to version 5.5-2 to fix the build failure due to
deprecation of String.create in 4.02.

Unfortunately I'm unable to upload it, because I haven't been able to
transition to a 4096 bit key yet (no DDs in my area to sign the new one).

So I'd appreciate it if someone could build it from the master branch
of git.debian.org/git/pkg-ocaml-maint/packages/approx.git and upload
it.

BTW, I still believe -warn-error is good engineering practice, even
though it's inconvenient during transitions like this.  So rather than
turn it off completely, I turned off only the warning due to
deprecated features.

--
Eric Cooper e c c @ c m u . e d u


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



Bug#789133: transition: ocaml 4.02.2

2015-06-18 Thread Eric Cooper
On Thu, Jun 18, 2015 at 09:50:44AM +0200, Stéphane Glondu wrote:
> Attached is the list of packages appearing in the tracker, with an
> annotation:
>  - "unstable" if the package can be binNMUed
>  - "experimental" if the package has to be uploaded from experimental
>  - "UNRELEASED" if the package has to be uploaded from git (though I
>am not sure I've pushed everything I should have)
>  - "MISSING" if the package has not been built for some reason (FTBFS,
>missing dependency, resource exhaustion)

Is any further information (build logs etc.) available about the
MISSING packages?

--
Eric Cooper e c c @ c m u . e d u


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



Bug#788500: pepperflashplugin-nonfree: fails with error "The certificate of ‘people.debian.org’ is not trusted"

2015-06-11 Thread Eric Cooper
Package: pepperflashplugin-nonfree
Version: 1.8.1
Severity: important

I have this package installed on 2 machines on my home network. It
works fine on one, and fails every time on the other.  Same
version, and same version of wget and ca-certificates.  The only
difference is that the one that works is an i386 machine and the one
that fails is amd64.

Using curl to retrieve the file works on both machines.

I don't know much about SSL and certificates, but would be happy to
try various things to debug this.

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

Kernel: Linux 3.16.0-4-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
Init: systemd (via /run/systemd/system)

Versions of packages pepperflashplugin-nonfree depends on:
ii  binutils   2.25-8
ii  ca-certificates20150426
ii  debconf [debconf-2.0]  1.5.56
ii  gnupg  1.4.19-3
ii  libatk1.0-02.16.0-2
ii  libcairo2  1.14.2-2
ii  libcurl3-gnutls7.42.1-2
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.5.2-4
ii  libgcc11:5.1.1-9
ii  libglib2.0-0   2.44.1-1
ii  libgtk2.0-02.24.25-3
ii  libnspr4   2:4.10.8-2
ii  libnss32:3.19.1-2
ii  libpango-1.0-0 1.36.8-3
ii  libpango1.0-0  1.36.8-3
ii  libstdc++6 5.1.1-9
ii  libx11-6   2:1.6.3-1
ii  libxext6   2:1.3.3-1
ii  libxt6 1:1.1.4-1+b1
ii  wget   1.16.3-2+b2

pepperflashplugin-nonfree recommends no packages.

Versions of packages pepperflashplugin-nonfree suggests:
ii  chromium   43.0.2357.65-1
pn  hal
ii  ttf-dejavu 2.35-1
ii  ttf-mscorefonts-installer  3.6
pn  ttf-xfree86-nonfree

-- 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#784273: cc1111: incompletely-disabled warning message 18

2015-05-08 Thread Eric Cooper
tags 784273 patch
thanks

On Thu, May 07, 2015 at 06:04:04PM -0600, Bdale Garbee wrote:
> Eric Cooper  writes:
> 
> > Why does the __code storage class affect it?
> 
> Neither Keith nor I have any idea.  Have you tried the same code with
> current SDCC to see if things perhaps work better there?

Yes, sdcc compiles both versions (with and without __code) with no
warnings.  The warning is still in the code (in SDCCglue.c), but I
couldn't come up with any input that would trigger it.

While I was looking at the code, I saw that the fix for my original
complaint was pretty trivial, so I've attached a patch.

-- 
Eric Cooper e c c @ c m u . e d u
>From 0ac4b0e0021c0664e12fa060ffdf59c7ebd0e679 Mon Sep 17 00:00:00 2001
From: Eric Cooper 
Date: Fri, 8 May 2015 12:32:53 -0400
Subject: [PATCH] suppress additional output when disabling warning 18

Signed-off-by: Eric Cooper 
---
 src/SDCCglue.c | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/src/SDCCglue.c b/src/SDCCglue.c
index f753441..46c1ead 100644
--- a/src/SDCCglue.c
+++ b/src/SDCCglue.c
@@ -352,7 +352,8 @@ initPointer (initList * ilist, sym_link *toType)
   IS_AST_OP(expr->right) && expr->right->opval.op=='&') {
 if (compareType(toType, expr->left->ftype)!=1) {
   werror (W_INIT_WRONG);
-  printFromToType(expr->left->ftype, toType);
+  if (!_SDCCERRG.disabled[W_INIT_WRONG])
+  printFromToType(expr->left->ftype, toType);
 }
 // skip the cast ???
 expr=expr->right;
@@ -1075,7 +1076,8 @@ printIvalPtr (symbol * sym, sym_link * type, initList * ilist, struct dbuf_s * o
   /* check the type  */
   if (compareType (type, val->type) == 0) {
 werrorfl (ilist->filename, ilist->lineno, W_INIT_WRONG);
-printFromToType (val->type, type);
+if (!_SDCCERRG.disabled[W_INIT_WRONG])
+printFromToType (val->type, type);
   }
 
   /* if val is literal */
-- 
2.1.4



Bug#784273: cc1111: incompletely-disabled warning message 18

2015-05-04 Thread Eric Cooper
Package: cc
Version: 2.9.0-4
Severity: normal

When I compile the following code:

struct s {
int v;
};

struct t {
struct s *ptr;
};

void *address;

struct t __code problem = {
(struct s *) &address,
};

I get the following warning messages:

bug.c:12: warning 18: Initializer different levels of indirections
from type 'struct s near* '
to type 'struct s generic* '
bug.c:12: warning 18: Initializer different levels of indirections
from type 'void generic*  near* '
to type 'struct s generic* '

(A minor bug is that it's printed twice.)

If I compile with --disable-warning 18, I expect to see no warnings,
but instead I get:

from type 'struct s near* '
to type 'struct s generic* '
from type 'void generic*  near* '
to type 'struct s generic* '

The two "extra" lines of each warning are not properly suppressed.

A final mystery (to me, at least) is that the declaration

struct t no_problem = {
(struct s *) &address,
};

compiles without any warnings.  Why does the __code storage class
affect it?


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



Bug#783678: cc1111: mcs51 assembler is not a drop-in replacement for sdcc's

2015-05-02 Thread Eric Cooper
On Wed, Apr 29, 2015 at 10:02:16AM -0600, Bdale Garbee wrote:
> I suspect, without looking, that this was a name change made in sdcc
> since the 2.9.0 release.  Not a very high priority for us, but in the
> meantime, if someone wants to offer up a suitable patch, I suspect we'd
> be happy to merge it.

Thanks, patch attached.

-- 
Eric Cooper e c c @ c m u . e d u
>From f692101d00016cef00817d1ae5a6b512b029f479 Mon Sep 17 00:00:00 2001
From: Eric Cooper 
Date: Sat, 2 May 2015 14:04:21 -0400
Subject: [PATCH] install symlink for sdas8051

Signed-off-by: Eric Cooper 
---
 debian/cc.links | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 debian/cc.links

diff --git a/debian/cc.links b/debian/cc.links
new file mode 100644
index 000..efc8db3
--- /dev/null
+++ b/debian/cc.links
@@ -0,0 +1 @@
+usr/bin/asx8051 usr/bin/sdas8051
-- 
2.1.4



Bug#783678: cc1111: mcs51 assembler is not a drop-in replacement for sdcc's

2015-04-28 Thread Eric Cooper
Package: cc
Version: 2.9.0-4
Severity: normal

The sdcc package ships its mcs51 assembler as sdas8051, while the
cc package ships it as asx8051.  Installing it also with the
latter name would make it more likely that existing Makefiles would
work unmodified.


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



Bug#782114: exuberant-ctags: conflicting default alternatives for ctags vs. etags

2015-04-07 Thread Eric Cooper
On Tue, Apr 07, 2015 at 06:16:12PM -0700, Edward Z. Yang wrote:
> Hello Eric,
> 
> I dug around for why I filed for the change in behavior.
> Here is the bug report that prompted it:
> 
> https://coq.inria.fr/bugs/show_bug.cgi?id=2726
> 
> ctags -e is not a perfect replacement for etags; in this
> example, 'make tags' calls out to etags and expects the Emacs
> version.
> 
> etags = emacs tags.  It seems only natural for it to have priority,
> and tools which refer to it are likely to assume emacs tags. If
> I am an emacs user, and I install 'ctags', I don't expect my 'etags'
> executable to suddenly change; I should ask for it specifically.
> 
> Though, yes, I agree the behavior change is unexpected and confusing,
> if you had been using ctags and then installed emacs.
> 
> Cheers,
> Edward

Thanks, seems reasonable.  Fine with me to close this.

-- 
Eric Cooper e c c @ c m u . e d u


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



Bug#782114: exuberant-ctags: conflicting default alternatives for ctags vs. etags

2015-04-07 Thread Eric Cooper
Package: exuberant-ctags
Version: 1:5.9~svn20110310-8
Severity: normal

After installing exuberant-ctags:

$ sudo update-alternatives --config ctags
There are 2 choices for the alternative ctags (providing /usr/bin/ctags).

  SelectionPath  Priority   Status
  
  * 0/usr/bin/ctags-exuberant   30auto mode
1/usr/bin/ctags-exuberant   30manual mode
2/usr/bin/ctags.emacs24 27manual mode
  

$ sudo update-alternatives --config etags
There are 2 choices for the alternative etags (providing /usr/bin/etags).

  SelectionPath  Priority   Status
  
  * 0/usr/bin/etags.emacs24 27auto mode
1/usr/bin/ctags-exuberant   10manual mode
2/usr/bin/etags.emacs24 27manual mode

This was unexpected and confusing.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-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
Init: systemd (via /run/systemd/system)

Versions of packages exuberant-ctags depends on:
ii  libc6  2.19-15

exuberant-ctags recommends no packages.

Versions of packages exuberant-ctags suggests:
ii  emacs24 [emacsen]  24.4+1-5
ii  nvi1.81.6-11+b1

-- 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#749090: minidlna: allow M-SEARCH from clients on other subnets

2015-03-11 Thread Eric Cooper
On Tue, Mar 10, 2015 at 02:55:46AM +0300, Alexander Gerasiov wrote:
> Could you please test this patch. I've updated it according current
> minidlna's version:
> http://anonscm.debian.org/cgit/collab-maint/minidlna.git/plain/debian/patches/08_fix_multicast_from_other_subnet.patch?id=02e74952c8714809c43c9aa7ed80ff07a0d7d82e

I built version 1.1.4+dfsg-1 with this patch, in a wheezy/i386 chroot,
and it's working fine for me.  In my setup, I have WiFi clients
(Android phones and tablets) talking through a router to the minidlna
server on my wired network.

Thanks for maintaining this package.

-- 
Eric Cooper e c c @ c m u . e d u


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



  1   2   3   4   5   6   7   8   >