Bug#1071335: upstream commits

[James Cameron]

You may be interested in these upstream commits;

b01478d ("Fix some parts of macro expansion are not guarded")
0194b80 ("strerror and memset require string.h")

Bug#1068511: caddy: does not satisfy httpd virtual package

[Cameron Steffen]

Package: caddy
Version: 2.6.2-5
Severity: normal

Dear Maintainer,

I would like to be able to install the wordpress package with caddy,
without installing apache2 or another server. I believe the caddy
package should fulfill the httpd package and then this would be
possible.

Thanks!
Cameron


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

Kernel: Linux 6.1.0-18-cloud-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.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 caddy depends on:
ii  libc6  2.36-9+deb12u4
ii  libnss3-tools  2:3.87.1-1
ii  libzstd1   1.5.4+dfsg2-5
ii  media-types10.0.0

caddy recommends no packages.

caddy suggests no packages.

-- Configuration Files:
/etc/caddy/Caddyfile changed [not included]

-- no debconf information

Bug#1054988: pulseaudio: Incorrect device selected when headphones are plugged in

[Cameron Cawley]

output to Front and Subwoofer speakers
surround40:CARD=Intel,DEV=0
HDA Intel, STAC9227 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=Intel,DEV=0
HDA Intel, STAC9227 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=Intel,DEV=0
HDA Intel, STAC9227 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=Intel,DEV=0
HDA Intel, STAC9227 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=Intel,DEV=0
HDA Intel, STAC9227 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
dmix:CARD=Intel,DEV=0
HDA Intel, STAC9227 Analog
Direct sample mixing device
usbstream:CARD=Intel
HDA Intel
USB Stream Output
Module #1
Name: libpipewire-module-rt
Argument: {
nice.level= -11
#rt.prio  = 88
#rt.time.soft = -1
#rt.time.hard = -1
}
Usage counter: n/a
Properties:
module.name = "libpipewire-module-rt"
object.id = "1"
object.serial = "1"
module.author = "Wim Taymans "
module.description = "Use realtime thread scheduling, falling 
back to RTKit"
module.usage = "[nice.level=] [rt.prio=] [rt.time.soft=Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 110
Tile Size: 65472
User Name: cameron
Host Name: debian
Server Name: PulseAudio (on PipeWire 0.3.65)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-_00_1b.0.analog-stereo
Default Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor
Cookie: a22e:c7d5

Bug#1053861: systemd-journal-remote: systemd-joural-uploading killed by watchdog every 3 minutes

[Tom Cameron]

Package: systemd-journal-remote
Version: 254.5-1
Severity: normal

Dear Maintainer,

After upgrading a test host from stable to testing, I noticed 
systemd-journal-upload
stopped sending logs to my logging host running Debian stable. The test
host notes that the service is killed for watchdog failure, and when the
service restarts the receiver logs a message about handshake message out
of context.

I have attempted to remove the upload state file, in the event there was
an issue with the last log data uploaded. This did not change the
status.


Source Host:
systemd 254 (254.5-1)

Log entries:
Oct 09 23:40:51 host-04 systemd[1]: Started systemd-journal-upload.service - 
Journal Remote Upload Service.
Oct 09 23:43:51 host-04 systemd[1]: systemd-journal-upload.service: Watchdog 
timeout (limit 3min)!
Oct 09 23:43:51 host-04 systemd[1]: systemd-journal-upload.service: Killing 
process 4709 (systemd-journal) with signal SIGABRT.
Oct 09 23:43:51 host-04 systemd[1]: systemd-journal-upload.service: Main 
process exited, code=killed, status=6/ABRT
Oct 09 23:43:51 host-04 systemd[1]: systemd-journal-upload.service: Failed with 
result 'watchdog'.


Destination Host:
systemd 252 (252.17-1~deb12u1)

Log entries:
Oct 09 19:43:51 rhodes systemd-journal-remote[6125]: microhttpd: Error: 
received handshake message out of context.


I can confirm that no log lines appear from this host on the target
host, while log lines from other Debian stable hosts do appear. The
journal files for this particular host don't seem have any updates since
around the time the upgrade from stable to testing completed.

I have checked the libmicrohttpd bug tracker to see if anything recent
seemed to matchi this behavior in the event that the hosts aren't
handshaking due to incompatible crypto settings, but nothing stands out
to me.

I have also looked at the systemd issue tracker on github, and while
there has historically be several issues with journal-upload, none of
them seem to have been reported recently.



-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 6.5.0-1-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
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 systemd-journal-remote depends on:
ii  libc6  2.37-12
ii  libcurl4   8.3.0-2
ii  libmicrohttpd120.9.77-3
ii  libsystemd-shared  254.5-1
ii  systemd254.5-1

systemd-journal-remote recommends no packages.

systemd-journal-remote suggests no packages.

-- no debconf information

Bug#1053741: systemd-journal-remote: systemd-joural-uploading killed by watchdog every 3 minutes

[Tom Cameron]

Package: systemd-journal-remote
Version: 254.5-1
Severity: normal

Dear Maintainer,

After upgrading a test host from stable to testing, I noticed
systemd-journal-upload stopped sending logs to my logging host running
Debian stable. The test host notes that the service is killed for
watchdog failure, and when the service restarts the receiver logs a
message about handshake message out of context.

I have attempted to remove the upload state file, in the event there
was an issue with the last log data uploaded. This did not change the
status.


Source Host:
systemd 254 (254.5-1)

Log entries:
Oct 09 23:40:51 host-04 systemd[1]: Started
systemd-journal-upload.service - Journal Remote Upload Service.
Oct 09 23:43:51 host-04 systemd[1]: systemd-journal-upload.service:
Watchdog timeout (limit 3min)!
Oct 09 23:43:51 host-04 systemd[1]: systemd-journal-upload.service:
Killing process 4709 (systemd-journal) with signal SIGABRT.
Oct 09 23:43:51 host-04 systemd[1]: systemd-journal-upload.service:
Main process exited, code=killed, status=6/ABRT
Oct 09 23:43:51 host-04 systemd[1]: systemd-journal-upload.service:
Failed with result 'watchdog'.


Destination Host:
systemd 252 (252.17-1~deb12u1)

Log entries:
Oct 09 19:43:51 rhodes systemd-journal-remote[6125]: microhttpd:
Error: received handshake message out of context.


I can confirm that no log lines appear from this host on the target
host, while log lines from other Debian stable hosts do appear. The
journal files for this particular host don't seem to have any updates
since around the time the upgrade from stable to testing completed.

I have checked the libmicrohttpd bug tracker to see if anything recent
seemed to matchi this behavior in the event that the hosts aren't
handshaking due to incompatible crypto settings, but nothing stands
out to me.

I have also looked at the systemd issue tracker on github, and while
there has historically be several issues with journal-upload, none of
them seem to have been reported recently.



-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 6.5.0-1-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
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 systemd-journal-remote depends on:
ii  libc6  2.37-12
ii  libcurl4   8.3.0-2
ii  libmicrohttpd120.9.77-3
ii  libsystemd-shared  254.5-1
ii  systemd254.5-1

systemd-journal-remote recommends no packages.

systemd-journal-remote suggests no packages.

-- no debconf information

Bug#1025629: Use of PolicyKit by Sugar

[James Cameron]

Sugar uses pkexec to elevate privilege to control backlight and get
device serial number.  Processes are forked to run shell scripts.  The
command line is prefixed with pkexec.

I don't know of any D-Bus use of PolicyKit, nor any use of the
PyGObject API.

Hope that helps!

Bug#1023795: Please undo the replace of pgplot with giza-pgplot

[James Cameron]

reassign 1023795 libpgplot-perl
retitle 1023795 Use pgplot5
thanks

Thanks for your permission to reassign.  My users see what Debian
provide as coming from and therefore part of Debian, even when it is
in contrib and non-free.  We value all of Debian, not only the parts
of the distribution in main.

Bug#1023795: Please undo the replace of pgplot with giza-pgplot

[James Cameron]

Hello Ole, seeking to clarify your latest.

My understanding is that pgplot5 is in Debian now under Debian Policy
section 2.2.3, in the non-free archive area.

Also, libpgplot-perl is in Debian now under Debian Policy section
2.2.2, in the contrib archive area for Stretch, and main for later
releases.

So I don't think the license of pgplot is the main problem or indeed a
cause of the problems described here.

The problems can be traced to the changes in libpgplot-perl, so I also
suggest this bug be reassigned to that package.  I agree that you
should reassign it.

I don't think the problems in this bug can be efficiently fixed in
Giza, when compared to the effort required to change libpgplot-perl.

I suggest you change the Giza source package Description from
"drop-in, modern replacement" to "mostly compatible, modern
replacement".  If you'd like another bug for that, let me know.

I agree a license change to pgplot would help, but it hasn't happened
yet.  Let's not make the perfect the enemy of the good.

A risk to Debian is to create an unnecessary derivative distribution
for a substantial group of users.  This group of users has a very slow
deployment cycle, so it can take longer than a Debian release or two
for critical issues to arise.

Thank you for your time on this bug.

Bug#1023795: Additional

[James Cameron]

Hello Debian Developers!  Thanks for your work.

I'm the developer responsible for upgrading the instrument software
referenced by https://github.com/sso-aat/libpgplot-perl/wiki

On porting to Giza, here are the regressions I found and my analysis;

1.  plot window not staying on display is because Giza does not
implement the PGPLOT /xs or /xserve device, instead collapsing it into
the same as the /xw or /xwindow device.

https://github.com/danieljprice/giza/blob/a6cefc4c0b1e2060ed40ff6f0a46525365952674/src/giza-drivers.c#L897

2.  content rendering - background; our existing plot scripts showed a
black background, but on using Giza the background changed to white;
not investigated, probably requires effort porting the script from
PGPLOT to Giza,

3.  content rendering - curve colours; this also changed, not
investigated,

4.  content rendering - fonts; the size of text changed, not
investigated,

5.  content rendering - overall dimensions; the width and height of
the plot changed, not investigated.

It was cheaper in developer time to undo #869135 and create a local
derivative package.

In discussions with astronomers, they've told me Giza is not a drop-in
replacement, but rather a poor substitute.  Until this week, I had no
idea.  Hope you can do something about it.  Let me know if you have
any questions.

Bug#881075: Update

[Cameron Tacklind]

I'm a new maintainer on dfu-programmer. I've been pushing to have CI
scripts on GitHub do any necessary building and bundling. Can I help with
this in any way?

New homepage (needs some updates):
https://dfu-programmer.github.io/

New public code repo:
https://github.com/dfu-programmer/dfu-programmer

Original code repo:
https://sourceforge.net/projects/dfu-programmer/

Related Bug:
https://bugs.launchpad.net/ubuntu/+source/dfu-programmer/+bug/1738813

 - Cameron

On Tue, 06 Sep 2022 10:09:55 +0200 Johannes Schauer Marin Rodrigues <
jo...@debian.org> wrote:
> Hi Rodolphe,
>
> On Thu, 6 Aug 2020 21:54:55 +0200 Rodolphe Pelloux-Prayer <
rodol...@damsy.net> wrote:
> > Sorry for the very long delay on this issue.
> >
> > I've just push a new version to
> > https://mentors.debian.net/package/dfu-programmer/
> >
> > FYI, the git repo is now on salsa :
> > https://salsa.debian.org/ropp-guest/dfu-programmer.
>
> I just saw this bug. Do you need a sponsor to upload the new version? I am
> willing to sponsor your upload if that is what you are missing.
>
> Thanks!
>
> cheers, josch

Bug#1022100: skycat: no rtd images, rtdServer and rtdClient hang while getopt

[James Cameron]

Package: skycat
Version: 3.1.2+starlink1~b+dfsg-7
Severity: important
X-Debbugs-Cc: james.came...@anu.edu.au

Dear Maintainer,

Both rtdServer and rtdClient hang when run, with a CPU loop.  Using gdb,
the loop is in main, calling getopt, which returns 255 instead of -1, so
the while loop never terminates.  It is as if "char" has become "unsigned
char".  Changing "char c" to "int c" and recompiling seems to fix it for
rtdServer and rtdClient.

However, there are also other problems; receiving an image from a camera
that sent a data type of -16 (USHORT) is ignored because the data type
is interpreted as 240 in rtd/generic/RtdCamera.C

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

Kernel: Linux 5.8.18-t4.03 (SMP w/8 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages skycat depends on:
ii  blt   2.5.3+dfsg-4.1
ii  iwidgets4 4.1.1-2.1
ii  libc6 2.35-3
ii  libcfitsio9   4.1.0-1
ii  libgcc-s1 12.2.0-5
ii  libstdc++612.2.0-5
ii  libtk-img 1:1.4.13+dfsg-2
ii  libwcstools1  3.9.7-1
ii  libx11-6  2:1.8.1-2
ii  libxext6  2:1.3.4-1+b1
ii  tcl-expect5.45.4-2+b1
ii  tcl8.68.6.12+dfsg-1+b1
ii  tk8.6 8.6.12-1+b1
ii  tk8.6-blt2.5  2.5.3+dfsg-4.1

skycat recommends no packages.

skycat suggests no packages.

-- no debconf information

Bug#877106: pinta: Pinta 1.6-2 crashes on image scaling and other image manipulation.

[Cameron White]

This issue has been frequently reported upstream (I'm the upstream Pinta
maintainer) and seemed to be a bug in some versions of Mono / gtksharp.
Updating to the latest stable Mono release was reported to avoid the
crashes.
This is also obsolete with the recently-released Pinta 2.0, which uses
dotnet-runtime-6.0

Cameron

Bug#982662: python3-jarabe: Language control panel hangs Sugar

[James Cameron]

Package: python3-jarabe
Version: 0.118-1
Severity: normal

Dear Maintainer,

Selecting the Language control panel in My Settings leads to a hang of the 
desktop, requiring a system reset or restart.

It is caused by new version of Python package removing a deprecated API.

This is a known problem with a fix available;
https://github.com/sugarlabs/sugar/commit/63885ed7b98beeb2e7cae7448c5cabeabf947c5a

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

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

Versions of packages python3-jarabe depends on:
ii  gir1.2-gdkpixbuf-2.0   2.42.2+dfsg-1
ii  gir1.2-glib-2.01.66.1-1+b1
ii  gir1.2-gstreamer-1.0   1.18.3-1
ii  gir1.2-gtk-3.0 3.24.24-1
ii  gir1.2-gtksource-3.0   3.24.11-2
ii  gir1.2-pango-1.0   1.46.2-3
ii  gir1.2-sugarext-1.00.118-3
ii  gir1.2-telepathyglib-0.12  0.24.1-3
ii  gir1.2-webkit2-4.0 2.30.4-1
ii  gir1.2-wnck-3.03.36.0-1
ii  gir1.2-xkl-1.0 5.4-4
ii  metacity   1:3.38.0-2
ii  policykit-10.105-30
ii  python33.9.1-1
ii  python3-cairo  1.16.2-4+b2
ii  python3-dbus   1.2.16-5
ii  python3-gwebsockets0.7-2
ii  python3-sugar3 0.118-3
ii  python3-xapian 1.4.18-1

Versions of packages python3-jarabe recommends:
ii  avahi-autoipd 0.8-5
ii  dbus-user-session [default-dbus-session-bus]  1.12.20-1
ii  dbus-x11 [dbus-session-bus]   1.12.20-1
ii  libpam-systemd247.3-1
ii  modemmanager  1.14.10-0.1
ii  network-manager   1.28.0-2+b1
ii  openssh-client1:8.4p1-3
ii  python3-carquinyol0.118-1
ii  xdg-user-dirs 0.17-2

Versions of packages python3-jarabe suggests:
ii  sugar-session  0.118-1

-- no debconf information

Bug#975373: Upstream patch proposed

[James Cameron]

Upstream has a patch and would like reviewers.

https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/454

-- 
James Cameron
http://quozl.netrek.org/

Bug#975374: [Pkg-sugar-devel] Bug#975374: sugar-calculate-activity: reproducible builds: Embeds build path in .desktop file

[James Cameron]

Upstream bug
https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/453

sugar-toolkit-gtk3 does not provide DESTDIR support yet, and
cdbs passes DEB_DESTDIR as PREFIX.

Bug#975373: [Pkg-sugar-devel] Bug#975373: sugar-read-activity: reproducible builds: Embeds build path in .desktop files

[James Cameron]

Upstream bug
https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/453

sugar-toolkit-gtk3 does not provide DESTDIR support yet, and
cdbs passes DEB_DESTDIR as PREFIX.

Bug#970983: sugar-themes: does not define @text_view_bg named colour

[James Cameron]

On Mon, Sep 28, 2020 at 09:18:56AM +0100, Simon McVittie wrote:
> On Mon, 28 Sep 2020 at 13:20:59 +1000, James Cameron wrote:
> > I've just tested Debian Testing (Bullseye), with src:sugar
> > 0.117-3, src:sugar-artwork:0.117-1, src:sugar-terminal-activity
> > version 47-1, src:vte2.91 version 0.62.0-1, and GTK 3.24.23-1 but
> > do not see any problem.
> > 
> > The terminal is correctly rendered in black on white or white on
> > black modes.
> 
> If sugar-terminal-activity hard-codes its background colour, you
> wouldn't see a problem.

Yes, sugar-terminal-activity hard-codes background colour of the Vte.

> The problem case is when vte is configured to inherit its colours
> from the theme. I don't know whether this is even possible with
> sugar-terminal-activity, but it is possible in gnome-terminal:
> https://gitlab.gnome.org/GNOME/vte/-/issues/284
> 
> Note that src:vte2.91 0.62.0-2 has a workaround, so you will need to
> hold src:vte2.91 at version 0.62.0-1 to reproduce this. Upstream
> asked me not to apply the workaround on the 0.63.x branch, so it is
> likely to go away after bullseye.

Yes, I checked that I used src:vte2.91 0.62.0-1 after seeing your
later changes on salsa git.  Thanks for warning, and sorry for not
mentioning.

> To reproduce this in GNOME (I used a test VM):
> - Run a gnome-terminal and gnome-tweaks
> - In gnome-terminal, right-click -> Preferences
> - profile -> Colors -> Text and Background -> Use colors from system
>   theme
> - In gnome-tweaks: Appearance -> Themes -> Applications ->
>   Sugar-100 or Sugar-72
> - Drag the two windows around to see the misrendering

Thanks.  It does reproduce.

> (I realise the Sugar themes are probably not *intended* to be used
> to theme non-Sugar GTK-based environments like GNOME and XFCE, but
> there is nothing that prevents it!)

Yes, an unexpected outcome.  Perhaps we should make the theme local to
Sugar and activities rather than make it available for other uses.

> The client-side-decoration window titlebar seems to have the same
> issue, so there are probably other named colours missing? Depending
> on the age of the theme, you might also need to add
> @theme_text_color and @unfocused_insensitive_color. See
> gtk/theme/Adwaita/_colors-public.scss in the gtk+3.0 source package
> for the full set.

Thanks.  I added these, which further fixed the Vte rendering, making
gnome-terminal useful again.  Window titlebar rendering was still
broken, even after I added _all_ remaining named colors from the full
set.  I don't know what is missing.

https://github.com/sugarlabs/sugar-artwork/pull/118

> > Please review
> > https://github.com/sugarlabs/sugar-artwork/pull/117
> 
> That looks suitable, although I haven't tested it.
> 
> smcv

-- 
James Cameron
http://quozl.netrek.org/

Bug#970983: sugar-themes: does not define @text_view_bg named colour

[James Cameron]

Thanks Simon,

I've just tested Debian Testing (Bullseye), with src:sugar 0.117-3,
src:sugar-artwork:0.117-1, src:sugar-terminal-activity version 47-1,
src:vte2.91 version 0.62.0-1, and GTK 3.24.23-1 but do not see any
problem.

The terminal is correctly rendered in black on white or white on black
modes.

I've looked at our GTK themes in https://github.com/sugarlabs/sugar-artwork
but they are unmaintained; changes to the GTK builtin theme since 3.20
are yet to be cascaded.

Is there a way to reproduce the problem?

Please review
https://github.com/sugarlabs/sugar-artwork/pull/117

-- 
James Cameron
http://quozl.netrek.org/

Bug#970819: linux-image-4.19.0-10-amd64: Suspend and hibernate fail to work

[Cameron DeCoster]

Package: src:linux
Version: 4.19.132-1
Severity: important

Dear Maintainer,

I'm running Debian 10 on by Dell Latitude 7490. It recently updated to kernel
4.19.0-10 and the suspend and hibernate functions stopped working. I noticed
this when I opened my laptop after closing it previously to engage suspend. The
screen stayed off and the system was non-responsive. I had to do a hard reboot
to get things working again. Upon testing, I also found that this happens when
suspending or hibernating from the power off menu. I tried booting with the
previous kernel, 4.19.0-9, and suspend and hibernate started working again. I
did some searching online and found this report that could be caused by a
similar problem:
https://www.dell.com/community/Latitude/Latitude-7490-CPU-failure-occurs-after-
sleep/td-p/7316847

I'm happy to provide more information if it's needed. Thank you.

Cam



-- Package-specific info:
** Version:
Linux version 4.19.0-10-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.132-1 (2020-07-24)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-10-amd64 
root=UUID=fb6ca44e-dd7c-4ed6-b141-e25c6e73aa4d ro quiet

** Not tainted

** Kernel log:
[5.019467] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[5.025504] input: Dell WMI hotkeys as 
/devices/platform/PNP0C14:01/wmi_bus/wmi_bus-PNP0C14:01/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input20
[5.142083] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: 
(null)
[5.149233] Intel(R) Wireless WiFi driver for Linux
[5.149234] Copyright(c) 2003- 2015 Intel Corporation
[5.149642] iwlwifi :02:00.0: enabling device ( -> 0002)
[5.167691] iwlwifi :02:00.0: firmware: direct-loading firmware 
iwlwifi-8265-36.ucode
[5.168374] iwlwifi :02:00.0: loaded firmware version 36.9f0a2d68.0 
op_mode iwlmvm
[5.182289] input: DELL081C:00 044E:121F Mouse as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-7/i2c-DELL081C:00/0018:044E:121F.0002/input/input21
[5.182408] input: DELL081C:00 044E:121F Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-7/i2c-DELL081C:00/0018:044E:121F.0002/input/input22
[5.182500] input: DELL081C:00 044E:121F UNKNOWN as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-7/i2c-DELL081C:00/0018:044E:121F.0002/input/input23
[5.182564] hid-multitouch 0018:044E:121F.0002: input,hidraw1: I2C HID v1.00 
Mouse [DELL081C:00 044E:121F] on i2c-DELL081C:00
[5.191966] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3246: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[5.191969] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[5.191971] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[5.191972] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[5.191973] snd_hda_codec_realtek hdaudioC0D0:inputs:
[5.191975] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
[5.191977] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
[5.191979] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[5.209749] audit: type=1400 audit(1600891583.780:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-oopslash" 
pid=685 comm="apparmor_parser"
[5.210251] audit: type=1400 audit(1600891583.780:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=684 
comm="apparmor_parser"
[5.210255] audit: type=1400 audit(1600891583.780:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=684 comm="apparmor_parser"
[5.210580] audit: type=1400 audit(1600891583.780:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/lib/snapd/snap-confine" pid=686 comm="apparmor_parser"
[5.210583] audit: type=1400 audit(1600891583.780:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=686 
comm="apparmor_parser"
[5.212372] audit: type=1400 audit(1600891583.784:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=689 comm="apparmor_parser"
[5.212603] audit: type=1400 audit(1600891583.784:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=698 comm="apparmor_parser"
[5.213170] audit: type=1400 audit(1600891583.784:9): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" 
pid=683 comm="apparmor_parser"
[5.213992] audit: type=1400 audit(1600891583.784:10): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=700 
comm="apparmor_parser"
[5.295762] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 
8265, REV=0x230
[5.357424] intel_rapl: Found 

Bug#964167: Chromium heavily loads the processor and crashes

[Cameron H]

Another one here, same bug as of this morning after the upgrade to 83. Very 
high CPU load, even for loading a page like Craigslist. Very clunky response 
times all around. No crashes yet.

Bug#925444: smokeping: --pid-dir doesn't worj as expected

[Cameron Davidson]

Hi Gabriel,
thanks for getting back to me - the timing was good, because the issue 
has just recurred on my system.

You are of course correct in what _should_ have happened based on the
contents of the unit file.
I just jumped to the wrong conclusion based on the error message, and
that my redundant change seemed to have worked at the time.

My system (this is at home) is on a Xen VM (x86_64), all Debian 10,
which should be up to date on stable.

I am not running slave mode.

smokeping is 2.7.3-2

systemd is 241-7~deb10u3

I get a problem like this about every second reboot, and it is not
always smokeping.  I am beginning to suspect something wrong with the
systemd sequencing.

The most recent time I booted:

1. smokeping said /run/smokeping did not exist.

2. bind9 was running, however any requests for external domains timed
out.  This would have caused problems for smokeping, except that it died
before getting that far.

3. another USB data logger could not find its device, but lsusb could.
(not sure if udev missed something)


I was able to simply "systemctl restart" each of smokeping and bind9 and
they worked.

The only thing I can think that could relate to some of these is that
the network config is still based on the old ifup/down style.

I know, from the occasional problem starting my openvpn server at boot,
that the "after=network-online" does nothing and the openvpn server
sometimes  fails to bind to a specific address that has yet to be
created.  I can't say for sure if that was only on Debian 9 or on 10
also.  And I can't see how that would crash smokeping.


So, in summary, I don't think my issue is really a smokeping problem, it
is just the poor victim.


Cheers,

Cameron.

Bug#881879: [Pkg-sugar-devel] Bug#881879: sugar-browse-activity: does not start, missing collabwrapper

[James Cameron]

Agreed, is fixed, thanks.

By the way, sugar-browse-activity:debian/watch continues to refer to
github tags instead of download.sugarlabs.org.  Also affects Chat,
Pippy and Write.  But not many of the others.

Bug#953591: bash: colors should be enabled by default (force_color_prompt)

[Cameron Tacklind]

Package: bash
Version: 5.0-4ubuntu1
Severity: minor
Tags: a11y

Dear Maintainer,

It is now 2020 and colors on a terminal are generally very well supported.
That colors are not enabled by default does not make sense to me. When a
terminal does not support colors, I've rarely, if ever, had that
incorrectly detected.

The Debian Wiki for [BashColors](https://wiki.debian.org/BashColors)
says "Its output can be colorized to increase human readability." However,
that seems to go against the text in `/etc/skel/.bashrc` that states
colors are "turned off by default to not distract the user".

Frankly, imho, the reasoning in the `.bashrc` file does not make sense,
nor does it to all of the people that have commented on the Stack
Exchange post referenced on the Wiki (the title, and thus URL, has been
changed and thus the link in the wiki is broken):
https://unix.stackexchange.com/questions/329581/why-is-debians-default-bash-shell-colorless

It looks to me like the Debian package is where the offending `.bashrc`
is defined and thus copied to many other systems.

It is my opinion that the color handling section of `.bashrc` should be
rewritten. There is already some confusion about `force_color_prompt`
because it does not *force* colors in all cases. I think a more
appropriate variable/setting would be something like `colorless_prompt`
or `force_colorless_prompt` for those that prefer bash to be colorless.

Thank you for considering this request.

-- System Information:
Debian Release: buster/sid
  APT prefers eoan-updates
  APT policy: (500, 'eoan-updates'), (500, 'eoan-security'), (500, 'eoan'), 
(100, 'eoan-backports')
Architecture: amd64 (x86_64)

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

Versions of packages bash depends on:
ii  base-files   10.2ubuntu7
ii  debianutils  4.8.6.3
ii  libc62.30-0ubuntu2
ii  libtinfo66.1+20190803-1ubuntu1

Versions of packages bash recommends:
ii  bash-completion  1:2.9-1ubuntu1

Versions of packages bash suggests:
pn  bash-doc  

-- Configuration Files:
/etc/skel/.bashrc changed [not included]

-- no debconf information

Bug#925444: smokeping: --pid-dir doesn't worj as expected

[Cameron Davidson]

This has just started hapenning to my also.

The cause, I think, that evenutally a tmpfile cleanup will delete
/run/smokeping - maybe depends on age and/or  because it is not owned by
root.

One solution (I found for other systemd processes run as non-root) is to
add a config file:

/usr/lib/tmpfiles.d/smokeping.conf

Contents should be something like:

   d    /run/smokeping   0755   smokeping   smokeping   -   -

to have systemd recreate the dir when smokeping is started.


Regards,

Cameron.

Bug#925444: smokeping: --pid-dir doesn't worj as expected

[Cameron Davidson]

Sorry, a followup to my incomplete previous post...

After upgrade from Debian 9 to 10...

/run on my system is now mounted on a tmpfs and is therefore recreated
empty at reboot. 

The old pidfile location /var/run is symlinked to /run.

The folder /run/smokeping needs to be recreated each reboot with
permissions to allow user smokeping to write to it.



Regards,

Cameron.

Bug#944513: opendkim: Signing via TCP socket works, unix socket fails with SSL error

[Cameron L Spitzer]

Package: opendkim
Version: 2.11.0~alpha-12
Severity: normal

Dear Maintainer,

I'm using opendkim to sign outbound messages in Postfix.
My previous installation used a TCP socket, that configuration still
works.   According to Debian Wiki and upstream, we should use a unix
socket now, not TCP.   Postfix is in a chroot at /var/spool/postfix.

I switched the socket, as advised, to
local:/var/spool/postfix/var/run/opendkim/opendkim.sock
in /etc/opendkim.conf and gave
smtpd_milters = unix:/var/run/opendkim/opendkim.sock
non_smtpd_milters = unix:/var/run/opendkim/opendkim.sock
in /etc/postfix/main.cf.

After restarting postfix and opendkim, signing outbound messages fails.
The postfix submission process returns an error to the client.
The error message in /var/log/mail.info is
Nov 10 20:47:03 seed10 opendkim[24709]: 120F6205B0: SSL error:0D06B08E:asn1 
encoding routines:asn1_d2i_read_bio:not enough data
Nov 10 20:47:03 seed10 opendkim[24709]: 120F6205B0: dkim_eom(): resource 
unavailable: d2i_PrivateKey_bio() failed

I expected a localhost:TCP socket and a unix socket would behave the
same.   It looks as if SSL is not receiving all the information
it needs from opendkim.

I worked around the failure by reverting the socket change.


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

Kernel: Linux 4.19.0-6-cloud-amd64 (SMP w/1 CPU core)
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 opendkim depends on:
ii  adduser3.118
ii  dns-root-data  2019031302
ii  libbsd00.9.1-2
ii  libc6  2.28-10
ii  libdb5.3   5.3.28+dfsg1-0.5
ii  libldap-2.4-2  2.4.47+dfsg-3+deb10u1
ii  liblua5.1-05.1.5-8.1+b2
ii  libmemcached11 1.0.18-4.2
ii  libmemcachedutil2  1.0.18-4.2
ii  libmilter1.0.1 8.15.2-14~deb10u1
ii  libopendbx11.4.6-13+b1
ii  libopendkim11  2.11.0~alpha-12
ii  librbl12.11.0~alpha-12
ii  libssl1.1  1.1.1d-0+deb10u2
ii  libunbound81.9.0-2+deb10u1
ii  libvbr22.11.0~alpha-12
ii  lsb-base   10.2019051400

opendkim recommends no packages.

Versions of packages opendkim suggests:
ii  opendkim-tools  2.11.0~alpha-12
pn  unbound 

-- Configuration Files:
/etc/default/opendkim changed:
RUNDIR=/var/spool/postfix/var/run/opendkim
SOCKET=local:$RUNDIR/opendkim.sock
USER=opendkim
GROUP=opendkim
PIDFILE=$RUNDIR/$NAME.pid
EXTRAAFTER=

/etc/dkimkeys/README.PrivateKeys [Errno 13] Permission denied: 
'/etc/dkimkeys/README.PrivateKeys'
/etc/opendkim.conf changed:
Syslog  yes
UMask   007
KeyFile /etc/dkimkeys/truffula.private
Domain  truffula.us
Selectormail
Socket  inet:12301@localhost
PidFile   /run/opendkim/opendkim.pid
OversignHeaders From
TrustAnchorFile   /usr/share/dns/root.key
UserIDopendkim


-- no debconf information

Bug#932085: grub-common: Grub can't load initrd for Xen after upgrade to Buster

[Cameron Davidson]

I also had the same problem after upgrading from 9.9 to 10.1. (from
network repos 8 November 2019).

The symptoms were the same, on the video console, the message appeared
(not verbatim as I forgot to transcribe it)

 loading xen-4.11
 then the same old warning about no available console for the kernel
 loading linux-4.19.0-6   
 loading initrd...
 error writing to console (then nothing)

This is just as it appeared when booting Xen from EFI in Stretch, except
that the version numbers were updated.

Neither of the workarounds made any difference. There was no evidence of
HDD activity, no network interfaces were activated, no logs were generated.

Only after trying the workarounds did I noticed that the grub boot menu
screen was displaying the suspicious-looking version 2.02~beta3-5+deb9u1.

The only file in /boot/efi/EFI/debian was (I think) grubx64.efi.

I manually ran grub-install and it seems to have fixed everything.  I
have no idea why it was not run automatically at some stage during the
upgrade.

The system now boots via the file shimx64.efi. 

Bug#927747: [Pkg-samba-maint] Bug#927747: bind9_dlz backend is entirely broken in Debian

[Cameron Davidson]

I would like to add my observations on this bug after upgrading from
stretch to 10.1.

The apparmor fixes seem OK so far.

My samba system was originally created by moving a samba-3 system from
CentOS 6 to Debian 9 and then using the samba tools to migrate to an
ad-dc system. I mention this, because that migration path, while
surprisingly smooth, was not without a need for some manual
intervention.  So some of what I obseved might be specific  to my
situation, since it was not installed on Debian from scratch.

At the end of the Buster upgrade, everything seemed to be running OK,
however once I needed to make some changes to and check the bind9 config
the problems became apparent.

1. the bind config was still pointing at
/var/lib/samba/private/named.conf and that file was still loading the
9.10 library, rather than 9.11.

2. After fixing that, I ran the suggested test of  "samba_dnsupdate 
--verbose --all-names"  and every line reported "failed".

3. I then tried the suggestion from the samba wiki of "samba_upgradedns
--dns-backend=BIND9_DLZ"

That failed due to the non-existence of the /var/lib/samba/bind-dns
directory, which led me to this bug report.

I manually created that directory, gave it what I guessed might be
suitable group ownership and permissions, and reran the samba_upgradedns
script.

The result of that was that there were no errors, and the program
reported that I needed to manually adjust the two entries in the bind9
config files to point to the new directory.


So it seems to me that the problem could be safely fixed by changing the
samba_upgradedns script to check for and create the bind-dns folder if
necessary. (I suppose that is an upstream issue and the full
ramifications would need to be considered)

Running this script in postinst would be appropriate, but you would
somehow need to determine that the user was already using the bind9_dlz
backend.


The result of the upgrade script running is that:

1. the new config file is created, that loads the correct version dlz
library (but "including" that file needs to be manually edited in main
bind9 config (options or local - wiki says .local, but mine was in
.options))

2. the gssapi-key  file is created as a hard link between private and
bind-dns locations, so old config still works, but user is advised to
manually update the bind9 .options file.


Cameorn.

Bug#939180: RM: bittornado-- removal triggered by the Python2 removal

[Cameron Dale]

retitle 939180 RM: bittornado-- removal triggered by the Python2 removal
reassign 939180 ftp.debian.org

I think this package should be removed.

There is only one reverse dependency, "cfv
<https://packages.debian.org/unstable/cfv>", which only suggests the
installation of bittornado or bittorrent.

The popcon graph has been steadily declining and is now below 1,000.

The upstream has been dead for a long time: no releases since 2007, and
their website has seen no activity since the forum was shutdown in 2011.

Cameron

Bug#930668: lxc-usernsexec: "Failed to find subuid or subgid allocation"

[Cameron Nemo]

Package: lxc
Version: 1:3.1.0+really3.0.3-8

I believe that the patch in the PR below fixes the issue.

https://github.com/lxc/lxc/pull/2740
From c14ea11dccbfa80021a9b169b94bd86e8b359611 Mon Sep 17 00:00:00 2001
From: Cameron Nemo 
Date: Wed, 28 Nov 2018 19:42:29 -0800
Subject: [PATCH] lxc-usernsexec: fix default map functionality

* Place NULL bytes at the end of strings so that
  lxc_safe_ulong() can parse them correctly

* Only free the newly created id_map on error,
  to avoid passing garbage to lxc_map_ids()

Signed-off-by: Cameron Nemo 
---
 src/lxc/cmd/lxc_usernsexec.c | 34 --
 1 file changed, 20 insertions(+), 14 deletions(-)

diff --git a/src/lxc/cmd/lxc_usernsexec.c b/src/lxc/cmd/lxc_usernsexec.c
index 10557dd519..ab0dffcffc 100644
--- a/src/lxc/cmd/lxc_usernsexec.c
+++ b/src/lxc/cmd/lxc_usernsexec.c
@@ -200,6 +200,7 @@ static int read_default_map(char *fnam, int which, char *user)
 {
 	size_t len;
 	char *p1, *p2;
+	unsigned long ul1, ul2;
 	FILE *fin;
 	int ret = -1;
 	size_t sz = 0;
@@ -224,37 +225,42 @@ static int read_default_map(char *fnam, int which, char *user)
 		if (!p2)
 			continue;
 
-		newmap = malloc(sizeof(*newmap));
-		if (!newmap)
-			goto on_error;
+		line[strlen(line) - 1] = '\0';
+		*p2 = '\0';
 
-		ret = lxc_safe_ulong(p1 + 1, >hostid);
+		ret = lxc_safe_ulong(p1 + 1, );
 		if (ret < 0)
-			goto on_error;
+			break;
 
-		ret = lxc_safe_ulong(p2 + 1, >range);
+		ret = lxc_safe_ulong(p2 + 1, );
 		if (ret < 0)
-			goto on_error;
+			break;
+
+		ret = -1;
+		newmap = malloc(sizeof(*newmap));
+		if (!newmap)
+			break;
 
 		newmap->nsid = 0;
 		newmap->idtype = which;
+		newmap->hostid = ul1;
+		newmap->range = ul2;
 
-		ret = -1;
 		tmp = malloc(sizeof(*tmp));
-		if (!tmp)
-			goto on_error;
+		if (!tmp) {
+			free(newmap);
+			break;
+		}
 
 		tmp->elem = newmap;
 		lxc_list_add_tail(_map, tmp);
+
+		ret = 0;
 		break;
 	}
 
-	ret = 0;
-
-on_error:
 	fclose(fin);
 	free(line);
-	free(newmap);
 
 	return ret;
 }

Bug#929251: sugar-browse-activity: Browse activity will start if libgli2.0-dev is installed. This should be a dependency.

[James Cameron]

libglib2.0-bin is the minimum dependency.

Cause is the os.system() call to /usr/bin/glib-compile-schemas

Only affects first run.  To reproduce after first run, delete the
.sugar/default/log/org.laptop.WebActivity directory before testing.

An alternative is for the package to compile the schemas.

-- 
James Cameron
http://quozl.netrek.org/

Bug#871223: Bug #871223

[Cameron Hall]

The Debian neverball-common package is missing
/usr/share/games/neverball/geom/goal/goal.png
(star image) along with the other .png files and material files in the geom
directory. Make sure these files are present in the package.

/usr/share/games/neverball/geom/back/back.sol
/usr/share/games/neverball/geom/beam/beam
/usr/share/games/neverball/geom/beam/beam.png
/usr/share/games/neverball/geom/beam/beam.sol
/usr/share/games/neverball/geom/flag/flag.sol
/usr/share/games/neverball/geom/flag/red
/usr/share/games/neverball/geom/flag/red.png
/usr/share/games/neverball/geom/flag/white
/usr/share/games/neverball/geom/flag/white.png
/usr/share/games/neverball/geom/goal/goal
/usr/share/games/neverball/geom/goal/goal.png
/usr/share/games/neverball/geom/goal/goal.sol
/usr/share/games/neverball/geom/jump/jump
/usr/share/games/neverball/geom/jump/jump.png
/usr/share/games/neverball/geom/jump/jump.sol
/usr/share/games/neverball/geom/mark/mark.sol
/usr/share/games/neverball/geom/vect/vect
/usr/share/games/neverball/geom/vect/vect.png
/usr/share/games/neverball/geom/vect/vect.sol

Bug#877748: python-sugar3 needs gstreamer1.0-plugins-good for autoaudiosink element

[James Cameron]

This is probably fixed, as 0.112-3 does have dependency on 
gstreamer1.0-plugins-good

Bug#923924: Please review and apply attached patch to support shutdown on SIGPWR

[Cameron Norman]

On Mon, 11 Mar 2019 20:51:29 +0100 Andras Korn 
wrote:
> On Mon, Mar 11, 2019 at 06:12:06PM +, Dmitry Bogatov wrote:
>
> > > On Fri, Mar 08, 2019 at 02:39:47PM +, Dmitry Bogatov wrote:
> > > > [2019-03-07 12:57] Andras Korn 
> > > > > part 1 text/plain 218
> > > > > Sorry, I sent an earlier version of the patch by mistake.
> > > > >
> > > > > I'm attaching the correct one, which I tested and which works for
me.
> > > > > [...]
> > > > > -  if (sigc && (stat(STOPIT, ) != -1) && (s.st_mode &
S_IXUSR)) {
> > > > > +  if ((sigp) || (sigc && (stat(STOPIT, ) != -1) &&
(s.st_mode & S_IXUSR))) {
> > > >
> > > > As far as I can tell by glance on patch, you want SIGPWR trigger
reboot.
> > > > If so, why don't you create REBOOT file in, say, /etc/rc.local and
make
> > > > lxc controller to send SIGCONT?
> > >
> > > No -- I want SIGPWR to trigger a halt.
> > >
> > > For the purposes of LXC, any signal will do; I just need for a signal
to
> > > trigger a shutdown regardless of the permissions on runit.stopit and
> > > runit.reboot.
> >
> > Halt. Fine. But why can't you pre-provision you container with apporiate
> > `stop.*' file with apporiate permissions?
>
> Because that adds complexity elsewhere -- /etc/runit/1 as shipped creates
> /run/runit.stopit with mode 0, so either all containers would need ot
have a
> custom /etc/runit/1, or run a custom script to chmod 100 /run/runit.stopit
> on every boot, or have an immutable /run/runit.stopit.
>
> It's not just about me; this affects everyone who wants to use runit
inside
> an lxc container.
>
> My goal is to make using runit as hassle-free as possible, without
> sacrificing any of its core values.
>
> > > > By the way, SIGPWR is not in POSIX, according to signal(7).
> > >
> > > You're right; in that case, maybe we can use SIGQUIT?
> >
> > SIGTERM feels better, imho. TERM is graceful termination, while SIGQUIT
> > creates coredump. By default.
>
> SIGPWR would be nice to use as the halt signal because it's the lxc
default,
> so that runit could be a drop-in replacement for sysvinit in LXC
containers.

We should recognize that SIGPWR was chosen in a fairly arbitrary way.
Of course, SIGPWR is in use today by LXC and powerstatd so it is useful to
support.

>
> If we're not going to use SIGPWR it's pretty much all the same which
signal
> we use, because it will need to be configured explicitly in LXC (but
that's
> acceptable -- POSIX is important enough).
>
> > But this naming only matters if you explain to me, how solution not
> > involving changing C code does not suffice. Two lines for convenience in
> > this case, three there -- and we all know where it ends.
>
> I'm sorry, I don't buy the slippery slope argument. I'm not adding a DNS
> resolver, a DHCP client or a QR encoder, merely making the user interface
a
> tiny bit more similar to sysvinit's, to make integration easier. This is
> entirely in line with The Unix Way: making one program a drop-in
replacement
> for another such that other programs interfacing with them don't see a
> difference unless they need to. It's why bzip2 and gzip take most of the

You are taking a previously portable codebase and making it not portable.
As a distribution patch, this might be acceptable. However it is an
unfortunate compromise.

Personally, I elect to replace the runit-init program entirely and only use
the supervision suite.
There is absolutely zero reason for an init system to call reboot(2). It is
simply unnecessary.

I have written a guide to do exactly this. It leverages two small C
programs:

* linit:
  * Reaps zombies
  * Ignores SIGCHLD, preventing new zombies
  * Sets up signal handlers for SIGINT and SIGPWR that spawn hooks
  * Spawns a boot hook
  * Calls pause()
* lreboot: calls reboot(2)

The rest is simply some scripting to emulate what runit-init does.
Please review the guide and source code for the above C programs:

https://gitlab.com/chinstrap/linit/blob/master/README.runit.md

Regards,
--
Cameron Nemo

Bug#844452: ITA: json-c -- JSON manipulation library

[Cameron Norman]

Control: retitle -1 ITA: json-c -- JSON manipulation library

I intend to adopt this package.

--
Cameron Nemo

On Wed, 25 Jul 2018 14:47:50 +0800 Nicolas Braud-Santoni <
nico...@braud-santoni.eu> wrote:
> Control: reopen -1
> Control: reassign -1 wnpp
> Control: retitle -1 O: json-c -- JSON manipulation library
> Control: severity -1 normal
>
> Hi,
>
> Tobias pointed out that the package now needs a WNPP bug.
> I am transmuting the old bug so as to preserve the context.
>
> Best,
>
>   nicoo
>
> On Tue, Jul 24, 2018 at 12:00:10AM +, Nicolas Braud-Santoni wrote:
> > Source: json-c
> > Source-Version: 0.13.1+dfsg-1
> >
> > We believe that the bug you reported is fixed in the latest version of
> > json-c, which is due to be installed in the Debian FTP archive.
> > [...]
> >* QA upload.
> >* Orphan the package (Closes: 844452)
> >* New upstream version (2018-03-05)
> >  - Remove obsolete patches
> >  - Bump library SONAME & update symbols file

Bug#826286: ITA: libnih -- NIH Utility Library

[Cameron Norman]

Control: retitle -1 ITA: libnih -- NIH Utility Library

I intend to adopt this package.

--

Cameron Nemo

Bug#872039: why the severity?

[Cameron Norman]

On Fri, 12 Jan 2018 03:56:42 +0100 Adam Borowski 
wrote:
> On Wed, Jan 10, 2018 at 08:38:39PM +0100, John Paul Adrian Glaubitz wrote:
> > > Please tell me why this would be serious: any filesystem from this
millenium
> > > can handle unclean shutdown fine -- especially if there's a sync
before
> > > reboot/poweroff.
> >
> > That's hardly an argument. There is still very much the possibility that
> > this bug causes data-loss, so the severity is definitely justified.
>
> Technically, yes.  If your filesystem is ext2, and there's a process that
> hasn't been killed, and continues to write after the final sync.
>
> But if you use ext2 for anything, you made the decision yourself.
>

Not necessarily, an admin could just have to use ext2 for internal company
policy reasons.

Let's not punish people for being stuck in a bad situation.

/usr is already mounted ro. Can we not remount other filesystems ro like
/var at the same time?

> > On the other hand, only a very small minority are still using sysvinit
on
> > Debian, so this I think it's ok to have the severity set to serious.
>
> According to my last data, 14% of unstable users; less on stable as those
> tend to be non-technical users.  Not a "very small minority".

Ignore him. He trolls non-systemd inits and actively roots for their exit
from Debian.

Regards,
--
Cameron nemo

Bug#848841: python-jarabe: journal view multiple select does not show actions toolbar

[James Cameron]

This bug no longer happens with the 0.112 packages, thanks.

-- 
James Cameron
http://quozl.netrek.org/

Bug#877812: python-jarabe: desktop does not start, requires WebKit 3.0 API, uses WebKit2 4.0 API

[James Cameron]

This bug no longer happens with the 0.112 packages, thanks.

-- 
James Cameron
http://quozl.netrek.org/

Bug#894642: [Pkg-sugar-devel] Bug#894642: gst-plugins-espeak: diff for NMU version 0.4.0-3.1

[James Cameron]

Will you be sending this upstream?

https://github.com/sugarlabs/gst-plugins-espeak

-- 
James Cameron
http://quozl.netrek.org/

Bug#896872: csound: python import ctcsound requires libcsound64-dev

[james cameron]

Package: csound
Version: 1:6.10.0~dfsg-1
Severity: minor

Dear Maintainer,

   * What led up to the situation?

Install Csound.  Write a test program for ctcsound module.

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

Python "import ctcsound".

   * What was the outcome of this action?

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/ctcsound.py", line 29, in 
libcsound = CDLL("libcsound64.so")
  File "/usr/lib/python2.7/ctypes/__init__.py", line 366, in __init__
self._handle = _dlopen(self._name, mode)
OSError: libcsound64.so: cannot open shared object file: No such file or 
directory

   * What outcome did you expect instead?

Successful import.

python-csound package is installed, same version as csound.

Expected that the python-csound package would provide everything needed to 
support the import of ctcsound module.

Workaround is to install libcsound64-dev package, which adds an unversioned 
symlink to the library.

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages csound depends on:
ii  libc62.24-11+deb9u3
ii  libcsound64-6.0  1:6.10.0~dfsg-1
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libstdc++6   6.3.0-18+deb9u1

Versions of packages csound recommends:
ii  csound-utils  1:6.10.0~dfsg-1

csound suggests no packages.

-- no debconf information

Bug#896848: csound: segfault on start

[james cameron]

Package: csound
Version: 1:6.10.0~dfsg-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Installing Csound and Sugar.

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

Download and run Sugar activity Music Keyboard.

   * What was the outcome of this action?

Segmentation fault.

   * What outcome did you expect instead?

No segmentation fault.

Upstream patch df5658c solves this problem, see also upstream issue 948.

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages csound depends on:
ii  libc62.24-11+deb9u3
ii  libcsound64-6.0  1:6.10.0~dfsg-1
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libstdc++6   6.3.0-18+deb9u1

Versions of packages csound recommends:
ii  csound-utils  1:6.10.0~dfsg-1

csound suggests no packages.

-- no debconf information

Bug#857230: [Pkg-sugar-devel] Bug#857230: closed by Santiago Ruano Rincón <santi...@debian.org> (Bug#857230: fixed in sugar 0.112-4)

[James Cameron]

On Thu, Apr 19, 2018 at 04:02:12PM +0200, Michael Biebl wrote:
> Am 19.04.2018 um 11:06 schrieb Debian Bug Tracking System:
> >  sugar (0.112-4) unstable; urgency=medium
> >  .
> >* Stop depending on gir1.2-nmgtk-1.0 (Closes: #857230)
> 
> Hm, you dropped the dependency, but I don't think this is actually a
> proper fix, as I still see this in the code:
> 
> $ grep import -R | grep NM
> extensions/cpsection/network/model.py:from gi.repository import NMClient
> 
> I.e., sugar still uses the old libnm-glib based GIR bindings (
> gir1.2-networkmanager-1.0 to be precise).

Agreed.

> The code should be ported to use gir1.2-nm-1.0, the libnm based GIR
> bindings.

Takes longer to talk about it than do it.  ;-)

Nobody told upstream.  Upstream has ported now.  You may cherry-pick.

https://github.com/sugarlabs/sugar/commit/04c63f6dd2b6f10a80376a43c735822f5283bda7

For your interest, neither the new nor the old API actually works on
recent Debian or Ubuntu; silently failing.

https://github.com/sugarlabs/sugar/issues/794

-- 
James Cameron
http://quozl.netrek.org/

Bug#886041: Sugar GConf removal patches

[James Cameron]

G'day,

Upstream has landed patches for each of these bugs, and a patch for
src:python-sugar3 that doesn't have a bug yet.

for src:sugar #886040 cherry-pick from 38b173d ("jarabe, extensions -
remove GConf compatibility").

for src:sugar-browse-activity #886041 use v202 release, or cherry-pick
a7f2e19 ("Add Gio.Settings for home-page") and fadd3a3 ("Port from
GConf to Gio.Settings").

for src:sugar-read-activity #886042 cherry-pick 225983e ("Port from
GConf").

for src:sugar-write-activity #886042 cherry-pick 6bd08c5 ("Port from
GConf - font face and size) and 2663064 ("Port from GConf - speech
rate and pitch").

for src:python-sugar3 (NO BUG NUMBER) cherry-pick 30139a3
("sugar3.speech - remove GConf compatibility support").

My thanks to Rahul Bothra and Yash Agrawal (BCC'd) for review and
testing.

-- 
James Cameron
http://quozl.netrek.org/

Bug#886040: [Pkg-sugar-devel] Bug#886041: sugar: raising severity of gconf dependency bug

[James Cameron]

Upstream has begun patch review for moving away from gconf.

The patches are in pull requests linked from a GitHub project;

https://github.com/orgs/sugarlabs/projects/2

-- 
James Cameron
http://quozl.netrek.org/

Bug#577281: add --nohostroute option

[James Cameron]

Upstream review of #577281; an option --nohostroute was added in 2011,
reference is commit 5ff2452 ("add --nohostroute option"), so this is
already done.

Specifying the table isn't a feature though.

-- 
James Cameron
http://quozl.netrek.org/

Bug#887370: pptp-linux: when redirecting all traffic the host routing entry to VPNserver via old eth0 is not added automatically

[James Cameron]

Speculating.

If your iproute2 package crossed the 4.10.0 boundary, then "ip route
get" will show uid, which pptp-linux will not handle as it parses the
output carelessly.

Upstream pptp-linux patch is 7d9a428 ("Remove uid from ip route get
output.").

https://github.com/quozl/pptp/commit/7d9a428a0744b3053767dc2d239f305c86f1fcee

-- 
James Cameron
http://quozl.netrek.org/

Bug#886160: pptpd FTCBFS: fails to propagate CC to plugins/Makefile

[James Cameron]

On Tue, Jan 02, 2018 at 07:49:13PM +0100, Christoph Biedl wrote:
> Helmut Grohne wrote...
> 
> > pptpd fails to cross build from source, because it fails to propagate CC
> > to plugins/Makefile. It is correctly detected by configure and correctly
> > forwarded to Makefile.am, but fails being forwarded to plugins/Makefile.
> > After making that forwarding explicit, pptpd cross builds successfully.
> > Please consider applying the attached patch.
> 
> Thanks for the report, and I trust your patch will do the right thing.
> Allow me a few days to handle it - besides technical issues on my side,
> perhaps upstream (*wave*) will use this as well, and I could cherry-pick
> then.

Accepted upstream, thanks!

4da603da51f41d6a7d58c3138e79f3ff12bc8c74

-- 
James Cameron
http://quozl.netrek.org/

Bug#881879: sugar-browse-activity: does not start, missing collabwrapper

[James Cameron]

Package: sugar-browse-activity
Version: 201.3-1
Severity: important

Dear Maintainer,

On installing sugar-browse-activity and trying to start it, the shell reported
failure, and logs contained;

Traceback (most recent call last):
  File "/usr/bin/sugar-activity", line 220, in 
main()
  File "/usr/bin/sugar-activity", line 164, in main
module = __import__(module_name)
  File "/usr/share/sugar/activities/Browse.activity/webactivity.py", line 58, 
in 
from collabwrapper.collabwrapper import CollabWrapper
ImportError: No module named collabwrapper.collabwrapper

See also #848840.

In Debian package git repository, collabwrapper directory is empty, because
debian/watch refers to github and collabwrapper is a submodule.  GitHub doesn't
include the submodules in tagged downloads of releases.

http://download.sugarlabs.org/sources/sucrose/fructose/Browse/ has tarballs
with collabwrapper included.


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

Kernel: Linux 4.9.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sugar-browse-activity depends on:
ii  gir1.2-evince-3.0 3.22.1-3+deb9u1
ii  gir1.2-gconf-2.0  3.2.6-4+b1
ii  gir1.2-gdkpixbuf-2.0  2.36.5-2+deb9u1
ii  gir1.2-glib-2.0   1.50.0-1+b1
ii  gir1.2-gtk-3.03.22.11-1
ii  gir1.2-pango-1.0  1.40.5-1
ii  gir1.2-rsvg-2.0   2.40.16-1+b1
ii  gir1.2-soup-2.4   2.56.0-2+deb9u1
ii  gir1.2-sugarext-1.0   0.110.0-4
ii  gir1.2-webkit2-4.02.16.6-0+deb9u1
ii  python2.7.13-2
ii  python-cairo  1.8.8-2.2
ii  python-dbus   1.2.4-1+b1
ii  python-gi 3.22.0-2
ii  python-sugar3 0.110.0-4
ii  python-telepathy  0.15.19-3

Versions of packages sugar-browse-activity recommends:
ii  ca-certificates  20161130+nmu1

sugar-browse-activity suggests no packages.

-- no debconf information

-- 
James Cameron
http://quozl.netrek.org/

Bug#790158: [Pkg-sugar-devel] Bug#790158: Upstream comment

[James Cameron]

On Mon, Oct 16, 2017 at 10:20:16AM +0200, Jonas Smedegaard wrote:
> Quoting James Cameron (2017-10-16 07:03:24)
> > Upstream could bring python-rsvg source into the code base; would that 
> > be okay?
> 
> No.
> 
> The team in Debian familiar with librsvg decides that its end of life is 
> reached.  I will not be comfortable with sidestepping that decision by 
> essentially taking over maintenance with Sugarlabs as new upstream!

Okay.

Actually, librsvg2 isn't end of life, but gnome-python-desktop is; a
strange place for the binding, but hey, it's what we have.

The binding is really tiny.

wc --lines ...

  135 rsvg.defs
   35 rsvgmodule.c
  229 rsvg.override

Or fork to run librsvg2-bin /usr/bin/rsvg-convert

> > Porting from python-rsvg to gir1.2-rsvg-2.0 would also require porting 
> > to GTK+ 2 GObject introspection.  This would break compatibility with 
> > downloaded Sugar activities.
> 
> GTK+ 2.x is on its way out.  And _that_ is really what breaks activities 
> depending on GTK+ 2.x.
> 
> Activities using GTK+ 2.x is expected to stop working with Debian 
> relatively soon.

Okay.  For Buster or later?

> I don't see any other (realistic) option than porting to modern stuff 
> like GTK+ 3.x and gir.

Agreed.  I've heard that hundreds of programs are affected, but they
aren't in Debian, so not our problem here.

I've checked Sid dependencies, to predict next steps, described below;
have I understood consequences correctly?

Debian will remove src:sugar-toolkit and python-sugar-toolkit, which
will cascade to;

- remove the python-sugar-toolkit recommends in package sucrose,

- remove gtk2-engines-sugar from src:sugar-artwork, and the recommends
  in package sucrose,

- remove package sugar-presence-service, (python-sugar-toolkit held
  the last dependency),

- remove or package new upstream releases for
  sugar-{poll,physics,irc}-activity

- remove or wait for new upstream release for
  sugar-jigsawpuzzle-activity, logged upstream as
  https://github.com/sugarlabs/jigsaw-puzzle-branch/issues/1

>  - Jonas
> 
> -- 
>  * Jonas Smedegaard - idealist & Internet-arkitekt
>  * Tlf.: +45 40843136  Website: http://dr.jones.dk/
> 
>  [x] quote me freely  [ ] ask before reusing  [ ] keep private

-- 
James Cameron
http://quozl.netrek.org/

Bug#790158: Upstream comment

[James Cameron]

Upstream could bring python-rsvg source into the code base; would that
be okay?

Porting from python-rsvg to gir1.2-rsvg-2.0 would also require porting
to GTK+ 2 GObject introspection.  This would break compatibility with
downloaded Sugar activities.

-- 
James Cameron
http://quozl.netrek.org/

Bug#790156: v44 already moved from python-rsvg to gir1.2-rsvg-2.0

[James Cameron]

New upstream release v44 fixed this, and was packaged, with gir-deps
of rsvg-2.0, so next step is to remove the python-rsvg dependency in
debian/rules.

-- 
James Cameron
http://quozl.netrek.org/

Bug#878611: New upstream version available

[Cameron Norman]

Package: libnginx-mod-http-dav-ext
Vesion: 1.13.1-2

A new version of this module was released recently.

https://github.com/arut/nginx-dav-ext-module/releases

This version has support for building as a dynamic module, which is
currently patched in on Debian.

Thanks
--
Cameron Norman

Bug#877750: test passed

[James Cameron]

Tested gstreamer1.0-espeak 0.4.0-3 ... it does fix the problem, thanks.

Bug#877812: python-jarabe: desktop does not start, requires WebKit 3.0 API, uses WebKit2 4.0 API

[James Cameron]

Package: python-jarabe
Version: 0.110.0-5
Severity: important

Dear Maintainer,

Sugar desktop does not start, and ~/.sugar/default/logs/shell.log has

Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File "/usr/lib/python2.7/dist-packages/jarabe/main.py", line 61, in 
gi.require_version('WebKit', '3.0')
  File "/usr/lib/python2.7/dist-packages/gi/__init__.py", line 118, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace WebKit not available

Package correctly declares dependency on WebKit2 4.0.

Source code incorrectly declares a dependency on WebKit 3.0 in
jarabe/main.py, yet uses WebKit2 4.0 in jarabe/view/viewhelp.py

Fixed upstream by removing the require_version call, and was released
in Sugar 0.111.

Workarounds are;

1.  install gir1.2-webkit-3.0, or

2.  delete the require_version call from jarabe/main.py

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python-jarabe depends on:
ii  gir1.2-gconf-2.0  3.2.6-4+b1
ii  gir1.2-gdkpixbuf-2.0  2.36.11-1
ii  gir1.2-glib-2.0   1.54.1-1
ii  gir1.2-gstreamer-1.0  1.12.3-1
ii  gir1.2-gtk-3.03.22.24-1
ii  gir1.2-gtksource-3.0  3.24.5-1
ii  gir1.2-pango-1.0  1.40.12-1
ii  gir1.2-soup-2.4   2.60.0-1
ii  gir1.2-sugarext-1.0   0.110.0-5
ii  gir1.2-webkit2-4.02.18.0-2+b1
ii  gir1.2-wnck-3.0   3.24.1-1
ii  gir1.2-xkl-1.05.4-2
ii  metacity  1:3.26.0-1
ii  policykit-1   0.105-18
ii  python2.7.14-1
ii  python-cairo  1.8.8-2.2
ii  python-dbus   1.2.4-1+b2
ii  python-gwebsockets0.4-3
ii  python-sugar3 0.110.0-5
ii  python-telepathy  0.15.19-3
ii  python-xapian 1.4.4-3

Versions of packages python-jarabe recommends:
ii  avahi-autoipd 0.7-3
ii  dbus-user-session [default-dbus-session-bus]  1.11.20-1
ii  dbus-x11 [dbus-session-bus]   1.11.20-1
ii  gconf23.2.6-4+b1
ii  libpam-systemd234-3
ii  modemmanager  1.6.8-1
ii  network-manager   1.8.4-2
ii  openssh-client1:7.5p1-10
ii  python-carquinyol 0.110.0-2
ii  xdg-user-dirs 0.15-3

Versions of packages python-jarabe suggests:
ii  sugar-session  0.110.0-5

-- no debconf information

-- 
James Cameron
http://quozl.netrek.org/

Bug#877750: is caused by espeak-ng 1.49.2 "Always use 'en' as the default voice/language."

[James Cameron]

espeak-ng change which caused this regression is
https://github.com/espeak-ng/espeak-ng/commit/59ca718d40955fe597bee74a56df3f049cdd6982

-- 
James Cameron
http://quozl.netrek.org/

Bug#877750: gstreamer1.0-espeak: silence, loops, and errors if no voice set

[James Cameron]

Package: gstreamer1.0-espeak
Version: 0.4.0-2
Severity: normal

Dear Maintainer,

Leading up to situation; install of Debian Sid and gstreamer1.0-espeak
package.

Ineffective was; shell command:

gst-launch-1.0 espeak text="hello world" ! autoaudiosink

as it did not speak, and continued to loop without termination,
with very frequent GStreamer errors.

Ineffective was; using espeak instead of espeak-ng, because
gstreamer1.0-espeak depends on libespeak-ng1 only.

Effective was; adding a voice property to the espeak element:

gst-launch-1.0 espeak text="hello world" voice="english" ! autoaudiosink

Outcome was; errors and loop when voice property not given.

Expected was; spoken words.

Possibly related; "espeak -v default hello" works, but "espeak-ng -v
default hello" says "Error; The specified espeak-ng voice does not
exist."

Both espeak and espeak-ng have no "default" in list of voices shown
with --voices argument.

Perhaps might be fixed by changing ESPEAK_DEFAULT_VOICE to "english"
in gst-plugins-espeak, so that the package will work with espeak-ng
which does not have "default".

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

Kernel: Linux 4.12.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gstreamer1.0-espeak depends on:
ii  libc6   2.24-17
ii  libespeak-ng1   1.49.1+dfsg-2
ii  libglib2.0-02.54.1-1
ii  libgstreamer-plugins-base1.0-0  1.12.3-1
ii  libgstreamer1.0-0   1.12.3-1

gstreamer1.0-espeak recommends no packages.

gstreamer1.0-espeak suggests no packages.

-- no debconf information

-- 
James Cameron
http://quozl.netrek.org/

Bug#877748: python-sugar3 needs gstreamer1.0-plugins-good for autoaudiosink element

[James Cameron]

Package: python-sugar3
Version: 0.110.0-5
Severity: normal

Dear Maintainer,

Leading up to situation; install of Debian Sid and sucrose package.

Ineffective was; use of sugar3.speech module, because autoaudiosink element was 
not available.

Effective was; installing gstreamer1.0-plugins-good.

Outcome was; successful use of speech synthesis feature.

Expected was; automatic install of gstreamer1.0-plugins-good as a result of 
installing python-sugar3.

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

Kernel: Linux 4.12.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python-sugar3 depends on:
ii  gir1.2-atspi-2.0  2.26.0-2
ii  gir1.2-gconf-2.0  3.2.6-4+b1
ii  gir1.2-gdkpixbuf-2.0  2.36.11-1
ii  gir1.2-glib-2.0   1.54.1-1
ii  gir1.2-gtk-3.03.22.22-1
ii  gir1.2-pango-1.0  1.40.12-1
ii  gir1.2-rsvg-2.0   2.40.18-1
ii  gir1.2-sugarext-1.0   0.110.0-5
ii  python2.7.14-1
ii  python-cairo  1.8.8-2.2
ii  python-dateutil   2.6.1-1
ii  python-dbus   1.2.4-1+b2
ii  python-decorator  4.1.2-1
ii  python-gi 3.24.1-3
ii  python-gi-cairo   3.24.1-3
ii  python-telepathy  0.15.19-3

Versions of packages python-sugar3 recommends:
ii  alsa-utils   1.1.3-1
ii  gir1.2-webkit2-4.0   2.18.0-2+b1
ii  shared-mime-info 1.9-1
ii  telepathy-mission-control-5  1:5.16.4-2
ii  telepathy-salut  0.8.1-5.1
ii  unzip6.0-21

Versions of packages python-sugar3 suggests:
ii  git1:2.14.2-1
ii  ipython5.1.0-3
ii  python-carquinyol  0.110.0-2
ii  python-jarabe  0.110.0-5

-- no debconf information

-- 
James Cameron
http://quozl.netrek.org/

Bug#848841: Was fixed in 0.111

[James Cameron]

Was fixed in Sugar 0.111

-- 
James Cameron

Bug#861052: Is fixed

[James Cameron]

Problem was in sugar-browse-activity, and was fixed for v201, latest
is v201.2.

-- 
James Cameron
http://quozl.netrek.org/

Bug#617285: pptpsetup: use absolute path for pptp in tunnel file

[James Cameron]

Thanks, taken upstream.

63eea745af41f781b60cfdd39813e4f000ead5f0

pptpsetup - use absolute path to pptp

/usr/sbin may not be in PATH, especially when pptp is configured for use
by non-root user.

See discussion in Debian bug 617285.

Bug#646881: pptp-linux: pptpsetup fails to properly store password with quotation mark (") in /etc/ppp/chap-secrets

[James Cameron]

Thanks, taken upstream.

e62bfa7f11b0af355ff0367f8e1f22c42328639b

Bug#872751: [Pkg-sugar-devel] Bug#872751: Bug#872751: Cannot change colour when run from xsession

[James Cameron]

On Sun, Aug 20, 2017 at 10:15:55PM +0200, martin f krafft wrote:
> Sorry, was unclear. I am asked to change the colour, but clicking on
> the X doesn't actually do anything. So I can only click "Next" and
> be forced to use the colour that was selected on startup (always the
> same).

Sounds like something is broken.  When I click on the icon in the
centre of the screen, the colour changes.

Please post ~/.sugar/default/logs/shell.log

-- 
James Cameron
http://quozl.netrek.org/

Bug#872747: [Pkg-sugar-devel] Bug#872747: Please make gender choice non-binary

[James Cameron]

Third option is to click between the two gender icons.

However, there is no fourth or fifth option, and it isn't clear why
Sugar asks the question in the first place.

Being discussed upstream.

-- 
James Cameron
http://quozl.netrek.org/

Bug#872752: [Pkg-sugar-devel] Bug#872752: Following user config, nothing happens, strace exposes Heisenbug

[James Cameron]

Behaviour that Martin reports is expected.  There are many ways that
Sugar fails to start if any of the dependencies are missing.

The strace contains the traceback, but it is not as easy as
reading the traceback in ~/.sugar/default/logs/shell.log so please
post that next time you have a problem starting Sugar.

All I can see is that it was in homewindow.py -> meshbox.py ->
neighborhood.py, which suggests Telepathy Salut is missing, and that
correlates with Martin's "Versions of packages sugar-session
recommends" list.

As sugar-session contains tools that don't need Telepathy Salut to be
installed, I'm fine with the dependency remaining as Recommends.

On IRC Martin mentioned installing sugar-session package; my usual
recommendation is to install the sucrose package, and that's what is
maintained on the Sugar Wiki;

http://wiki.sugarlabs.org/go/Debian

-- 
James Cameron
http://quozl.netrek.org/

Bug#851052: Fix flickering

[James Cameron]

Extra text insertion cursor (caret) blinks were scheduled.

Each blink invalidated the window and redrew it.

I've submitted a patch upstream on 13791.  I'm interested to hear if
it fixes it for others.

http://dev.laptop.org/~quozl/z/1diDDl.txt

-- 
James Cameron
http://quozl.netrek.org/

Bug#866649: Read-119 removes gir1.2-webkit-3.0 dependency

[James Cameron]

Upstream release v119 has removed this dependency.

-- 
James Cameron
http://quozl.netrek.org/

Bug#870953: [Debian-olpc-devel] Bug#870953: sugar-jigsawpuzzle-activity: should sugar-jigsawpuzzle-activity be removed from unstable?

[James Cameron]

Comment from upstream.

http://people.sugarlabs.org/~quozl/JigsawPuzzle-11.tar.bz2 removes
Abiword dependency, thus fixing #842066.

-- 
James Cameron
http://quozl.netrek.org/

Bug#842066: new version fixes this bug

[James Cameron]

Upstream version 11 does not have this bug.

http://people.sugarlabs.org/~quozl/JigsawPuzzle-11.tar.bz2

Abiword dependency has been removed with the embedded lessons moved to
the Help activity.

-- 
James Cameron
http://quozl.netrek.org/

Bug#870950: [Debian-olpc-devel] Bug#870950: sugar-poll-activity: should sugar-poll-activity be removed from unstable?

[James Cameron]

Comment from upstream.

#842067 may have been a serious bug that blocked this package for
stretch and jessie, but #842067 can be fixed with a new upstream
version ... not yet packaged by Debian.

http://download.sugarlabs.org/sources/honey/Poll/

-- 
James Cameron
http://quozl.netrek.org/

Bug#842067: new version fixes this bug

[James Cameron]

Upstream version 30 does not have this bug.

Upstream git commit 3981527560a0fbbf73d59770697e2984b6e27630 in
2014-08-16 removed Abiword dependency when the embedded lessons were
moved to the Help activity.

-- 
James Cameron
http://quozl.netrek.org/

Bug#646880: pptp-linux: pptpsetup creates /etc/ppp/peers/$PEERNAME world-readable

[James Cameron]

Christoph Biedl wrote:
> James Cameron wrote...
> > pptpsetup preserves mode on /etc/ppp/chap-secrets, but uses root
> > umask 0022 on /etc/ppp/peers/$TUNNEL, and group dip because of
> > setgid bit on /etc/ppp/peers.
> > 
> > My perl is rusty.  As far as I can see, it would be a call to chmod
> > after open, or a call to umask before open.  Latter seems easy, but
> > overrides user choice.
> ...
> > Patch attached, will be upstreamed after review.
> 
> That is almost the thing I was about to suggest, go for it.

Was pushed.  d33e18d.

> And, when convenient, please replace the two-argument form of open
> [...]

Was pushed.  c0dbacf.

-- 
James Cameron
http://quozl.netrek.org/

Bug#646880: pptp-linux: pptpsetup creates /etc/ppp/peers/$PEERNAME world-readable

[James Cameron]

pptpsetup preserves mode on /etc/ppp/chap-secrets, but uses root
umask 0022 on /etc/ppp/peers/$TUNNEL, and group dip because of
setgid bit on /etc/ppp/peers.

My perl is rusty.  As far as I can see, it would be a call to chmod
after open, or a call to umask before open.  Latter seems easy, but
overrides user choice.

Patch attached, will be upstreamed after review.

Test method;

# umask 0022 && \
  pptpsetup --create tunnel --server s --username u --password p && \
  ls -l /etc/ppp/peers/tunnel && \
  pptpsetup --delete tunnel
-rw-r- 1 root dip 131 Aug  4 18:03 /etc/ppp/peers/tunnel

-- 
James Cameron
http://quozl.netrek.org/
>From d33e18ddfd7d6c78c0a7166bde147b6811b4c351 Mon Sep 17 00:00:00 2001
From: James Cameron <qu...@laptop.org>
Date: Fri, 4 Aug 2017 18:05:19 +1000
Subject: [PATCH] Fix for world-readable peers file

pptpsetup preserves mode on /etc/ppp/chap-secrets, but uses root
umask 0022 on /etc/ppp/peers/$TUNNEL, and group dip because of
setgid bit on /etc/ppp/peers.

Debian default umask is 0022, so override umask to 0027 and prevent
world-readable file.

Fixes Debian #646880.
---
 pptpsetup | 1 +
 1 file changed, 1 insertion(+)

diff --git a/pptpsetup b/pptpsetup
index fdfd00a..52d279a 100644
--- a/pptpsetup
+++ b/pptpsetup
@@ -64,6 +64,7 @@ sub create {
 # create or add lines to the /etc/ppp/chap-secrets file,
 # which holds usernames and passwords
 my $chap_secrets_file = '/etc/ppp/chap-secrets';
+umask( 0027 );
 open( FILE, ">>$chap_secrets_file" )
   or die "$0: can't write to '$chap_secrets_file': $!\n";
 
-- 
2.7.4

Bug#575644: marked as done (pptp-linux mtu & mru bug)

[James Cameron]

Thanks Christoph.

Ivan's workaround of --clamp-mss-to-pmtu was valid for a path MTU
discovery failure where intermediate hosts refuse to forward ICMP
fragmentation needed responses.

http://pptpclient.sourceforge.net/howto-diagnosis.phtml#connections_freeze

In that scenario, changing network interface MTU using the mru and mtu
pppd options is effective for the interface, but doesn't solve the
problem, because the cause is somewhere else in the network, not on
the host running Debian.

Perhaps Ivan thought it could be a feature of pptp, but with Network
Manager taking over these corner cases we're unlikely to take the idea
upstream in pptp.

-- 
James Cameron
http://quozl.netrek.org/

Bug#869802: [Debian-olpc-devel] Bug#869802: sugar-physics-activity: Request to move the package to be maintained by the Sugar team.

[James Cameron]

G'day Rishabh,

I'm not a Debian developer, yet.  ;-)

I've a derivative package of Physics.  Written by Gonzalo Odiard and
Martin Abente Lahaye two years ago, and maintained by me since.  We
use it at OLPC for building our images.

It is non-compliant with current Debian standards, so some work would
be needed to bring it up to date.

https://github.com/quozl/physics/commits/olpc-packaging

In case it is a problem, we can relicense as required.

For more on Debian Derivatives, see
https://wiki.debian.org/Derivatives/

-- 
James Cameron
http://quozl.netrek.org/

Bug#848838: sugar-write-activity: constant flicker of cursor and document

[James Cameron]

Well, #851052 is a duplicate of #848838, as mine was first.  ;-)

Upstream bug in Sugar is
https://bugs.sugarlabs.org/ticket/4915

-- 
James Cameron
http://quozl.netrek.org/

Bug#868296: [Pkg-sugar-devel] Bug#868296: sugar-browse-activity: Unusable package sugar installs by default in Xfce

[James Cameron]

something wrong with dependencies is my guess.

sugar-browse-activity is best used within the Sugar desktop, which
is the sucrose package on Debian.

sugar-activity provided by python-sugar3 package does not work
very well outside the Sugar user interface shell; just tried it then
and huge traceback because python-carquinyol wasn't installed, but
that's a recommends for python-jarabe so my mistake.

python-carquinyol installed and the sugar-browse-activity starts up,
but without any window manager decorations (in wmaker), because it is
written to be used within the Sugar desktop, which is a fullscreen app
design without windows.

sugar-browse-activity does suggest python-jarabe for the user
interface shell; perhaps it should require or recommend instead.

upstream has some more details if you're interested, see

http://www.sugarlabs.org/
http://wiki.sugarlabs.org/go/Debian

not surprised forums didn't know, see also

https://wiki.debian.org/Sugar

Bug#862576: [Pkg-sugar-devel] Bug#862576: etoys: Doesn't get beyond Squeak security key generation

[James Cameron]

@Petter, thanks for asking.

@Bert, etoys 5.0.2408 does not complete "Initializing Squeak security
system" on Debian Stretch, but it did on Debian Jessie.

I don't know what's wrong, yet.

I've reproduced the problem.

CPU is 100%.  strace shows the process making syscalls, of which the
most frequent are gettimeofday and recvfrom on socket, with occasional
SIGARLM.  http://dev.laptop.org/~quozl/z/1dHfBq.txt

The process has one thread with a backtrace;

(gdb) thread apply all bt

Thread 1 (Thread 0x7f46b3f3c500 (LWP 954)):
#0  0x55f77704d270 in ?? ()
#1  0x55f77704d40b in ?? ()
#2  0x55f777013f77 in interpret ()
#3  0x55f776ff9d39 in main ()

Repeated continue, ctrl+c and backtrace shows the squeak-vm is
actually doing something, but I've no idea what;

#0  0x55f777007800 in success ()
#1  0x55f77704cef8 in ?? ()
#2  0x55f777013f77 in interpret ()
#3  0x55f776ff9d39 in main ()

#0  0x55f77700f758 in stObjectat ()
#1  0x55f77700f861 in commonAt ()
#2  0x55f777013f77 in interpret ()
#3  0x55f776ff9d39 in main ()

#0  0x55f77700d8e0 in primitiveFloatSubtractfromArg ()
#1  0x55f777014d90 in interpret ()
#2  0x55f776ff9d39 in main ()

#0  0x55f7770078cd in sweepPhase ()
#1  0x55f77700946c in incrementalGC ()
#2  0x55f777009a35 in instantiateClassindexableSize ()
#3  0x55f77704b4d0 in ?? ()
#4  0x55f77704dc45 in ?? ()
#5  0x55f777013f77 in interpret ()
#6  0x55f776ff9d39 in main ()

#0  0x55f777013dc0 in interpret ()
#1  0x55f776ff9d39 in main ()

#0  0x7ffc4053ed80 in gettimeofday ()
#1  0x55f77701955e in ioMSecs ()
#2  0x55f777007f9d in checkForInterrupts ()
#3  0x55f777013e3c in interpret ()
#4  0x55f776ff9d39 in main ()

generate-core-file can be used, and the resulting core file can be
reloaded in gdb.  http://dev.laptop.org/~quozl/z/1dHfAf.txt

Perhaps one of the libraries changed between Jessie and Stretch to
cause this problem; but finding which one will be a long task.

Perhaps etoys upstream may have some ideas.  I've copied Bert.

On Sun, Jun 04, 2017 at 10:23:51PM +0200, Petter Reinholdtsen wrote:
> This issue is going to cause etags to be removed from Stretch.
> Anyone have any idea what is wrong?

-- 
James Cameron
http://quozl.netrek.org/

Bug#848840: closed by Jonas Smedegaard <d...@jones.dk> (Bug#848840: fixed in sugar-browse-activity 200+20170502-1)

[James Cameron]

Tested.  Does fix.

Bug#861052: patch available

[James Cameron]

I've a patch that works, and it has been queued for review.
https://github.com/sugarlabs/browse-activity/pull/51

But it doesn't handle .xo files from other places.

-- 
James Cameron
http://quozl.netrek.org/

Bug#861052: sugar-session: Doesn't recognize Activity bundles

[James Cameron]

On Mon, Apr 24, 2017 at 07:56:07AM -0500, Sebastian Silva wrote:
> I downloaded with Browse an activity to the Journal, then attempted
> to launch it, but it is not installed or started.

Thanks, now I recognise the symptom.

Maybe a problem with sugar-browse-activity; a wrong mime-type is set.

Upstream bug https://github.com/sugarlabs/browse-activity/issues/48

(Sorry about that ... I hadn't tried to reproduce it that way because
of #848840, and you had said in your original mail that it was the
journal that didn't know what to do with the bundle, rather than the
bundle "Kind" being wrong.)

I've been looking for the cause.  I've reviewed all commits since
v157.3 but drawn a blank; next step is to instrument the code with
debugging.

You're welcome to have a look too.

-- 
James Cameron
http://quozl.netrek.org/

Bug#860943: sugar-jukebox-activity does not start

[James Cameron]

Package: sugar-jukebox-activity
Version: 32+20160926-1

Jukebox does not start.  Logs contain error "ImportError: cannot
import name ImageTk".

Is fixed upstream in sugar-toolkit-gtk3 495eed8 "Prepend instead of
append to path".

-- 
James Cameron

Bug#855676: New release available

[James Cameron]

Package: sugar-physics-activity
Version: 7+dfsg-1.2

Physics-32 is available.
https://github.com/sugarlabs/physics

-- 
James Cameron
http://quozl.netrek.org/

Bug#790156: Patch available

[James Cameron]

Hey Jonas!

Can be fixed by applying
https://github.com/sugarlabs/sugarlabs-calculate/pull/39/commits/5d8c1aeb99b04ef40f137365e0075188ba73aa0b
along with the usual debian/rules changes.

I've done this in my derivative package.

-- 
James Cameron
http://quozl.netrek.org/

Bug#848840: Fixed by touch __init__.py

[James Cameron]

Caused by missing empty __init__.py file in
/usr/share/sugar/activities/Browse.activity/collabwrapper/

Python needs the empty file to mark the directory as a module.

(I did try to figure out how to propose this as a patch to VCS, but
after using gbp pq import/export the patches seemed a bit noisy;
perhaps there's a better way.)

-- 
James Cameron
http://quozl.netrek.org/

Bug#752094: pptpd: Restarting daemon breaks existing connections

[James Cameron]

On Sat, Dec 24, 2016 at 11:17:18PM +0100, Christoph Biedl wrote:
> Unfortunately this has an unpleaseant side effect: Since the new
> pptpd instance has no knowlegde of the old one's children, it will
> happily allocate connection slots (by IP address) that are already
> in use. So the second client will not see any traffic.

Yes, but only when IP address allocation is controlled by pptpd.

Other IP address allocation methods are radius, chap-secrets (pppd),
and remote (ipcp-accept-remote).  For this pptpd takes --delegate
option.

> The only way to solve this AFAICS was the old instance persists all
> the childrens' information so the new one will not allocate them
> while they are running. There might be some race conditions to
> consider as well. James (upstream) is reading this, if you can solve
> this by Jan 20th I'll be happy to include it for stretch. Afterwards
> it might be too late.

I've no plans to fix this by that date, but I'm interested in patches
to do so.

My preference is a /var/run/pptpd/ip directory containing a file for
each active connection, name equal to IP address, content is PID.

pptpmanager.c slot_* functions would maintain these files as a mirror
of struct slot *slots.

Here's a quick pseudo-code plan;

void slot_set_pid(int i, pid_t pid)
{
  struct slot *slot = [i];
  // if pid is zero, {
  //   delete file,
  // } else {
  //   create and write pid to file
  // }
  slot->pid = pid; 
}

int slot_find_by_pid(pid_t pid)
{
  int i;
  for(i=0; i<slot_count; i++) {
struct slot *slot = [i];
if (slot->pid == pid)
  // if file exists, {
  //   read pid from file,
  //   if pid exists (kill with sig zero), {
  // continue (skip slot),
  //   } else {
  // unlink file,
  // }
  return i;
  }
  return -1;
}

-- 
James Cameron
http://quozl.netrek.org/

Bug#817602: olpc-xo1: Removal of debhelper compat 4

[James Cameron]

Thanks to Paul Wise for the heads-up.

OLPC still has a software and hardware organisation (me), and is
using a Debian derivative (Ubuntu) on our latest hardware (NL3), using
the Debian packages of Sugar desktop.

Debian should drop olpc-xo1, olpc-powerd, and olpc-kbdshim.

OLPC models are XO-1, XO-1.5, XO-1.75, XO-4, and now NL3.

Right now, OLPC has manufacturing capability for XO-4 and NL3.

Debian only really worked well on the XO-1 and XO-1.5 models; these
are no longer manufactured, units in the field are past end of life,
and are failing at an expected high rate.

Anybody relying on an XO-1 or XO-1.5 should buy a new laptop.  ;-)

Disclosure: I'm paid by OLPC.

-- 
James Cameron
http://quozl.netrek.org/

Bug#848841: python-jarabe: journal view multiple select does not show actions toolbar

[James Cameron]

Package: python-jarabe
Version: 0.110.0-2
Severity: normal

Dear Maintainer,

After creating a few journal objects, and opening the journal,
the user clicked on the checkbox next to an object.

Outcome was checkbox tick, but there was no change to the toolbar.

Expected were the deselect all, select all, copy, and erase options.

Workaround was to click on the detail view button for an object then
click on back.

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

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

Versions of packages python-jarabe depends on:
ii  gir1.2-gconf-2.0  3.2.6-4
ii  gir1.2-gdkpixbuf-2.0  2.36.1-1
ii  gir1.2-glib-2.0   1.50.0-1
ii  gir1.2-gstreamer-1.0  1.10.2-1
ii  gir1.2-gtk-3.03.22.5-1
ii  gir1.2-gtksource-3.0  3.22.1-1
ii  gir1.2-pango-1.0  1.40.3-3
ii  gir1.2-soup-2.4   2.56.0-1
ii  gir1.2-sugarext-1.0   0.110.0-2
ii  gir1.2-webkit2-4.02.14.2-1
ii  gir1.2-wnck-3.0   3.20.1-2
ii  gir1.2-xkl-1.05.4-2
ii  metacity  1:3.22.1-1
ii  policykit-1   0.105-17
ii  python2.7.11-2
ii  python-cairo  1.8.8-2.1
ii  python-dbus   1.2.4-1
ii  python-gwebsockets0.4-3
ii  python-sugar3 0.110.0-2
ii  python-telepathy  0.15.19-3
ii  python-xapian 1.4.1-1
pn  python:any

Versions of packages python-jarabe recommends:
ii  avahi-autoipd  0.6.32-1
ii  dbus-x11   1.10.14-1
ii  gconf2 3.2.6-4
ii  libpam-systemd 232-8
ii  modemmanager   1.6.4-1
ii  network-manager1.4.2-3
ii  openssh-client 1:7.3p1-5
ii  python-carquinyol  0.110.0-1
ii  xdg-user-dirs  0.15-2

Versions of packages python-jarabe suggests:
ii  sugar-session  0.110.0-2

-- no debconf information

-- 
James Cameron
http://quozl.netrek.org/

Bug#848840: sugar-browse-activity: does not start, complains about collabwrapper

[James Cameron]

Package: sugar-browse-activity
Version: 200+20161203-1
Severity: important

Dear Maintainer,

On installing sugar-browse-activity and trying to start it, the shell reported
failure, and logs contained;

Traceback (most recent call last):
  File "/usr/bin/sugar-activity", line 220, in 
main()
  File "/usr/bin/sugar-activity", line 164, in main
module = __import__(module_name)
  File "/usr/share/sugar/activities/Browse.activity/webactivity.py", line 52, 
in 
from collabwrapper.collabwrapper import CollabWrapper
ImportError: No module named collabwrapper.collabwrapper

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

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

Versions of packages sugar-browse-activity depends on:
ii  gir1.2-evince-3.0 3.22.1-3
ii  gir1.2-gconf-2.0  3.2.6-4
ii  gir1.2-gdkpixbuf-2.0  2.36.1-1
ii  gir1.2-glib-2.0   1.50.0-1
ii  gir1.2-gtk-3.03.22.5-1
ii  gir1.2-pango-1.0  1.40.3-3
ii  gir1.2-rsvg-2.0   2.40.16-1
ii  gir1.2-soup-2.4   2.56.0-1
ii  gir1.2-sugarext-1.0   0.110.0-2
ii  gir1.2-webkit2-4.02.14.2-1
ii  python2.7.11-2
ii  python-cairo  1.8.8-2.1
ii  python-dbus   1.2.4-1
ii  python-gi 3.22.0-2
ii  python-sugar3 0.110.0-2
ii  python-telepathy  0.15.19-3

Versions of packages sugar-browse-activity recommends:
ii  ca-certificates  20161130

sugar-browse-activity suggests no packages.

-- no debconf information

-- 
James Cameron
http://quozl.netrek.org/

Bug#848838: sugar-write-activity: constant flicker of cursor and document

[James Cameron]

Package: sugar-write-activity
Version: 97+20160926-1
Severity: important

Dear Maintainer,

On installing sugar-write-activity and starting it from the Sugar shell,
the text insertion cursor and upper section of display flickers continually,
and system load is high.

Appearance was almost identical to my comments on these two bugs;

http://bugzilla.abisource.com/show_bug.cgi?id=13791
https://bugs.launchpad.net/bugs/1574278

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

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

Versions of packages sugar-write-activity depends on:
ii  gir1.2-abiword-3.0  3.0.2-2
ii  gir1.2-gconf-2.03.2.6-4
ii  gir1.2-glib-2.0 1.50.0-1
ii  gir1.2-gtk-3.0  3.22.5-1
ii  python  2.7.11-2
ii  python-dbus 1.2.4-1
ii  python-gi   3.22.0-2
ii  python-sugar3   0.110.0-2
ii  python-telepathy0.15.19-3

Versions of packages sugar-write-activity recommends:
ii  gir1.2-gstreamer-1.0  1.10.2-1
ii  gstreamer1.0-espeak   0.4.0-2

sugar-write-activity suggests no packages.

-- no debconf information

-- 
James Cameron
http://quozl.netrek.org/

Bug#848633: [Pkg-sugar-devel] Bug#848633: sugar-toolkit-gtk3: please make the build reproducible

[James Cameron]

You wrote:
> Please, consider sending this patch upstream.

Is in review upstream, thanks.

https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/350

-- 
James Cameron
http://quozl.netrek.org/

Bug#831032: pptp-linux: Please update patches and packaging

[James Cameron]

Everything beautiful was merged and released in pptp-1.9.0

-- 
James Cameron
http://quozl.netrek.org/

Bug#831032: pptp-linux: Please update patches and packaging

[James Cameron]

On Sat, Nov 26, 2016 at 02:51:44PM +0100, Christoph Biedl wrote:
> * Convince upstream to remove pptpsetup.8 in the clean target

Taken, pushed as 0080ac8.

I'll take a look at the other patches.

-- 
James Cameron
http://quozl.netrek.org/

Bug#831502: [Pkg-sugar-devel] Bug#831502: Bug#831502: sucrose: Freezes X after initial configuration

[James Cameron]

On 18/07/2016, at 6:22 AM, Helge Kreutzmann wrote:

> 

Hmm, yes, missing telepathy components, please try installing the recommends?

Bug#831502: [Pkg-sugar-devel] Bug#831502: Bug#831502: sucrose: Freezes X after initial configuration

[James Cameron]

On 17/07/2016, at 3:52 PM, Helge Kreutzmann wrote:
> Ok, I switched to lightdm. When I select sugar, my credentials are
> accepted, I briefly see this thick cursor and then I'm immediately
> returned to lighted.

After this, you may find an explanation in ~/.sugar/default/logs/shell.log

Post this file, and I'll be pleased to look at it if someone else hasn't by the 
time I wake up.  ;-)

Bug#825869: new upstream release of netrek-client-cow

[James Cameron]

Package: netrek-client-cow
Version: 3.3.0-3.1

New upstream release available; 3.3.1

http://www.netrek.org/files/COW/netrek-client-cow-3.3.1.tar.gz
http://mailman.us.netrek.org/pipermail/netrek-dev/2011-October/005754.html

We restored server from an older backup after 3.3.1 release.

Happy to take any patches.

-- 
James Cameron
http://quozl.netrek.org/

Bug#554906: Breaks Sugar Maze Activity

[James Cameron]

A comment about impact.

When the Sugar desktop is used on Debian, the Maze activity fails if
python-pil is installed, because

from player import Player

uses /usr/bin/player.py from python-pil instead of player.py from the
activity itself.

Traceback (most recent call last):
  File "/usr/bin/sugar-activity", line 169, in 
main()
  File "/usr/bin/sugar-activity", line 121, in main
module = __import__(module_name)
  File "/usr/share/sugar/activities/Maze.activity/activity.py", line 21, in 

import game
  File "/usr/share/sugar/activities/Maze.activity/game.py", line 43, in 
from player import Player
  File "/usr/bin/player.py", line 14, in 
from PIL import Image, ImageTk
ImportError: cannot import name ImageTk

https://github.com/godiard/maze-activity/blob/master/game.py#L43

-- 
James Cameron
http://quozl.netrek.org/

Bug#798242: systemd: Failed to execute operation: Connection timed out

[James Cameron]

Martin Pitt wrote:
> This sounds like another case of
> https://github.com/systemd/systemd/issues/1505, which finally got
> fixed in version 228.

Thanks, very interesting.  Yes, it sounds likely.

> ...
> 
> I don't close this for now, it would be interesting to see whether
> this still happens with >= 228 in any case.

I agree.  Not sure how.

The problem system sources.list points to jessie.

systemd in jessie is 215.

systemd in stretch is 228.

Is 228 planned for jessie, or should we temporarily repoint sources to
stretch and try an update of systemd only?

The problem system is still in the state it was left in when #798242
was raised.  We've been unable to take the risk of a reboot; yet.  Can
you speculate if reboot would be bad idea?

-- 
James Cameron
http://quozl.netrek.org/

Bug#798242: systemd: Failed to execute operation: Connection timed out

[James Cameron]

Martin Pitt wrote:
> James Cameron wrote:
> > The problem system is still in the state it was left in when
> > #798242 was raised.  We've been unable to take the risk of a
> > reboot; yet.  Can you speculate if reboot would be bad idea?
> 
> No, a reboot is probably the only thing which will reset the state
> properly. The "35 not upgraded" packages should be okay, and
> unconfigured systemd is ok as it only failed in the trigger. But
> leaving udev unconfigured could lead to boot troubles, so maybe try
> a round (or two) of "dpkg --configure -a" first?

Thanks.  Only rsyslog.postinst did hang, process tree shows;

 8781 pts/0S+ 0:00  \_ dpkg --configure -a
 8782 pts/0S+ 0:00  \_ /bin/sh 
/var/lib/dpkg/info/rsyslog.postinst configure 8.4.2-1
 8793 pts/0S+ 0:00  \_ /bin/sh /usr/sbin/invoke-rc.d 
rsyslog restart
 8812 pts/0S+ 0:00  \_ systemctl restart rsyslog.service
 8813 pts/0S+ 0:00  \_ 
/bin/systemd-tty-ask-password-agent --watch

System is up after reboot.

-- 
James Cameron
http://quozl.netrek.org/

Bug#797359: universal-ctags

[Cameron Eagans]

Hello! I'm one of the maintainers of universal-ctags (though certainly not the 
most active one). My interest is more on the packaging and distribution side of 
things, as well as maintaining the website (http://ctags.io ).

Some of the work that has been done up till this point has been committing old 
patches that have been sitting in the mailing list for years. A lot of it has 
been modernizing the parsers and adding a ton of test coverage. In terms of 
hard performance metrics, I'm not aware of any, but if you open an issue about 
it in the Github repo (ideally with specific scenarios that you want to 
measure), I don't think anyone would be opposed to the idea.

We were considering the use of OpenSUSE's OBS to package universal ctags for 
all the distros + travis for mac builds and appveyor for windows builds, but 
nothing has been set in stone yet. If someone were to provide the necessary 
files for debian packaging in a PR, I would happily review and merge it myself 
(feel free to @cweagans if you open a PR for this).

In terms of a stable release, there are no formalized plans, but it's 
definitely coming up. I'm hoping to get something out the door by Q1 2016. Over 
the next week or two, I'll start organizing a release. Things are fairly stable 
right now, but there are definitely some things that we want to wrap up before 
being locked into a 1.0 release. We might look at doing smaller 0.x.x releases 
in the mean time, but there's been some resistance to that idea.

Hope this helps!