Bug#1068969: csound-utils installs /usr/bin/extractor which has no manual page.

[Martin Guy]

Package: csound-utils
Version: 1:6.18.1+dfsg-1
Severity: normal
X-Debbugs-Cc: martinw...@gmail.com

extractor --help says

--Csound version 6.18 (double samples) 2022-11-24
[commit: none]
libsndfile-1.2.0
util extractor:
Usage:  extractor [-flags] soundfile
Legal flags are:
-o fnamesound output filename
-N  notify (ring the bell) when done
-S integer  sample number at which to start file
-Z integer  sample number at which to end file
-Q integer  number of samples to read
-T fpnumtime in secs at which to start file
-E fpnumtime in secs at which to end file
-D fpnumduration in secs of extract
-R  Rewrite header
-H  Heartbeat
-v  verbose mode for debugging
-- fnameLog output to file
flag defaults: extractor -otest -S 0
extractor: error: unknown flag --
end of score.  overall amps:  0.0
   overall samples out of range:0
0 errors in performance
Elapsed time at end of performance: real: 0.001s, CPU: 0.000s

so I guess it's some kind of sound convertor.
A manual page saying what it is and what it does and how to use it
would be nice.

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

Kernel: Linux 6.1.0-15-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages csound-utils depends on:
ii  csound   1:6.18.1+dfsg-1
ii  libc62.36-9+deb12u4
ii  libcsound64-6.0  1:6.18.1+dfsg-1
ii  libsamplerate0   0.2.2-3
ii  libsndfile1  1.2.0-1

csound-utils recommends no packages.

csound-utils suggests no packages.

-- no debconf information

Bug#1067057: tcpdump: Environment undocumented in the man page, yet the TZ variable has effect on the timezone

[Guy Harris]

> I'll look at getting the man pages fixed.

I've filed https://bugzilla.kernel.org/show_bug.cgi?id=218711 against the 
strftime man page.

For localtime(), it may be sufficient that the man page indicates that 
localtime() behaves as if tzset() were called, and that the tzset man page 
indicates that TZ is used.  The macOS man page, however, *does* mention TZ, and 
that may also be true of the ctime man page in other BSDs.

Bug#1067057: tcpdump: Environment undocumented in the man page, yet the TZ variable has effect on the timezone

[Guy Harris]

> Very little, if anything, of strftime() needs to handle TZ, because it's 
> handed a const struct tm *, generated either by a call to localtime() or 
> gmtime() If generated by a call to localtime(), localtime() has already done 
> all the work of converting a time_t to local time, meaning that it's 
> localtime(), not strftime(), that uses TZ.

I just checked the tip-of-the-main-branch GNU libc, and, in the time 
subdirectory:

strftime_l.c does *not* call getenv(), and thus strftime() does *not* 
directly look at TZ;

tzset.c *does* call getenv("TZ") - which it has to do, as it sets the 
current time information for the current process based on the setting of TZ.

I'll look at getting the man pages fixed.

Bug#1067057: tcpdump: Environment undocumented in the man page, yet the TZ variable has effect on the timezone

[Guy Harris]

> tcpdump has no special handling of TZ, it just calls strftime() which handles 
> TZ as described in strftime(3).

Very little, if anything, of strftime() needs to handle TZ, because it's handed 
a const struct tm *, generated either by a call to localtime() or gmtime()  If 
generated by a call to localtime(), localtime() has already done all the work 
of converting a time_t to local time, meaning that it's localtime(), not 
strftime(), that uses TZ.

If, as I suspect, this is a bug inherited from another project's man pages, 
I'll file a bug there.

> Users of tcpdump wouldn’t generally know that strftime() is in use and thus 
> don’t know to visit that man page.

Would users of ls generally know that 1) ls uses localtime() and 2) that, 
therefore, the setting of TZ affects its behavior?  Even if they know 1), they 
wouldn't know 2) if all they did was look at the localtime() man page, as, at 
least in Debian 12.5, that man page does *not* mention that its behavior is 
affected by the TZ environment variable.

If they also wouldn't know that TZ affects ls, how is ls different from tcpdump 
in this regard?

Note that ls isn't the only command affected by TZ; date is also affected by 
TZ, and there are plenty of others.  Must all commands that happen either to 
take local time inputs (and convert them to time_t values by using mktime()) or 
product local time outputs converted from time_t values by using localtime() 
mention that the TZ environment variable affects their behavior?

Bug#1065553: fonts-jetbrains-mono: Jetbrains-Mono 2.304 broken in Gnome Terminal

[Guy Rutenberg]

Package: fonts-jetbrains-mono
Version: 2.304+ds-4
Severity: normal
X-Debbugs-Cc: guyrutenb...@gmail.com

Dear Maintainer,

After updating fonts-jetbrains-mono from version 2.242+ds-3 to 2.304+ds-4, the
font is displayed as gibbrish in Gnome Terminal. Other apps do render the font
correctly. Reverting back to 2.242+ds-3 fixes the issue.

Thanks,
Guy

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 6.7.7-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Bug#1063640: adwaita-icon-theme: cursor theme not found

[Guy Rutenberg]

Package: mutter
Version: 44.8-3
Followup-For: Bug #1063640
X-Debbugs-Cc: guyrutenb...@gmail.com

Dear Maintainer,

I just experienced the same bug using mutter 44.8-3 and adwaita-icon-them
46~beta-1. Reverting back to adwaita-icon-theme 45.0-2 resolved the issue.

Guy

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 6.6.13-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mutter depends on:
ii  adwaita-icon-theme45.0-2
ii  gnome-settings-daemon-common  45.1-1
ii  gsettings-desktop-schemas 45.0-2
ii  libc6 2.37-15
ii  libgles2  1.7.0-1
ii  libglib2.0-0  2.78.3-2
ii  libmutter-12-044.8-3
ii  libwayland-client01.22.0-2.1+b1
ii  mutter-common 44.8-3
ii  zenity4.0.1-1

mutter recommends no packages.

Versions of packages mutter suggests:
ii  gnome-control-center  1:46~alpha-2
ii  xdg-user-dirs 0.18-1

-- no debconf information

Bug#1051409: podman: Podman man pages use en-dash instead of dash

[Guy Rutenberg]

Hi,

The issue seems to no longer reproduce as of 2024-01-30 in Debian Sid. I'm
not sure when the change happened, but the issue can be closed.

Thanks,
Guy
On Fri, 8 Sep 2023 11:41:17 +0300 Guy Rutenberg 
wrote:
> Thanks, you're right. The unicode characters are introduced in the
> Markdown->roff conversion. Specifically, go-md2man depends on Blackfriday
(
> https://github.com/russross/blackfriday) for the actual conversion and, it
> automatically converts dashs to en-dashs.
>
> I've opened a bug report with go-md2man upstream:
> https://github.com/cpuguy83/go-md2man/issues/101
>
> On Thu, 7 Sept 2023 at 16:50, Reinhard Tartler  wrote:
>
> > Control: reassign -1 go-md2man-v2
> > stop
> >
> > Thanks for your report Guy,
> >
> > All manpages in podman are written in markdown, and you can review the
> > sources at
> >
https://github.com/containers/podman/blob/main/docs/source/Introduction.rst
> > -- as you can see the sources do not contain any unicode characters.
> >
> > I strongly suspect that the unicode characters are introduced via the
> > go-md2man utility. I'm reassigning this to that package for additional
> > thoughts and suggestions. Please feel free to reassign back if this
isn't
> > coming from e.g.
> > https://github.com/cpuguy83/go-md2man/blob/master/md2man/roff.go but
> > something in the libpod packaging.
> >
> >
> >
> >
> > On Thu, Sep 7, 2023 at 9:24 AM Guy Rutenberg 
> > wrote:
> >
> >> Package: podman
> >> Version: 4.3.1+ds1-8+b2
> >> Severity: minor
> >> X-Debbugs-Cc: guyrutenb...@gmail.com
> >>
> >> Dear Maintainer,
> >>
> >> The man pages supplied by the podman package use unicode en-dash (‐) to
> >> document flags instead of regular dash (-). This is both inconvinient
> >> when try
> >> to search the man page, and incorrect (as you would use normal dash in
the
> >> shell).
> >>
> >> Thanks,
> >> Guy
> >>
> >>
> >> -- System Information:
> >> Debian Release: trixie/sid
> >>   APT prefers unstable-debug
> >>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
> >> 'experimental')
> >> Architecture: amd64 (x86_64)
> >> Foreign Architectures: i386
> >>
> >> Kernel: Linux 6.4.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
> >> Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en

Bug#1055506: fonts-noto-core: Please update the Noto Hebrew fonts

[Guy Rutenberg]

Package: fonts-noto-core
Version: 20201225-2
Severity: wishlist
Tags: upstream
X-Debbugs-Cc: guyrutenb...@gmail.com

Dear Maintainer,

Google Fonts has a newer versions of the Noto Hebrew font families. The new
version has to main advantages:
1. It includes latin glyphs as well, which makes the font usable in programs
which fail to handle missing glyps gracefully (for exampel Firefox would
replace the missing latin glyphs in Noto Sans Hebrew with a serif font).
2. It has a variable font variant.

Thanks,
Guy

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description
+++-==-=--=
ii  fontconfig 2.14.2-6  amd64generic font configuration 
library - support binaries
ii  libfreetype6:amd64 2.13.2+dfsg-1 amd64FreeType 2 font engine, 
shared library files
ii  libfreetype6:i386  2.13.2+dfsg-1 i386 FreeType 2 font engine, 
shared library files
ii  libxft2:amd64  2.3.6-1   amd64FreeType-based font drawing 
library for X

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

Kernel: Linux 6.5.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fonts-noto-core depends on:
ii  fonts-noto-mono  20201225-2

fonts-noto-core recommends no packages.

fonts-noto-core suggests no packages.

-- no debconf information

Bug#1051409: podman: Podman man pages use en-dash instead of dash

[Guy Rutenberg]

Thanks, you're right. The unicode characters are introduced in the
Markdown->roff conversion. Specifically, go-md2man depends on Blackfriday (
https://github.com/russross/blackfriday) for the actual conversion and, it
automatically converts dashs to en-dashs.

I've opened a bug report with go-md2man upstream:
https://github.com/cpuguy83/go-md2man/issues/101

On Thu, 7 Sept 2023 at 16:50, Reinhard Tartler  wrote:

> Control: reassign -1 go-md2man-v2
> stop
>
> Thanks for your report Guy,
>
> All manpages in podman are written in markdown, and you can review the
> sources at
> https://github.com/containers/podman/blob/main/docs/source/Introduction.rst
> -- as you can see the sources do not contain any unicode characters.
>
> I strongly suspect that the unicode characters are introduced via the
> go-md2man utility. I'm reassigning this to that package for additional
> thoughts and suggestions. Please feel free to reassign back if this isn't
> coming from e.g.
> https://github.com/cpuguy83/go-md2man/blob/master/md2man/roff.go but
> something in the libpod packaging.
>
>
>
>
> On Thu, Sep 7, 2023 at 9:24 AM Guy Rutenberg 
> wrote:
>
>> Package: podman
>> Version: 4.3.1+ds1-8+b2
>> Severity: minor
>> X-Debbugs-Cc: guyrutenb...@gmail.com
>>
>> Dear Maintainer,
>>
>> The man pages supplied by the podman package use unicode en-dash (‐) to
>> document flags instead of regular dash (-). This is both inconvinient
>> when try
>> to search the man page, and incorrect (as you would use normal dash in the
>> shell).
>>
>> Thanks,
>> Guy
>>
>>
>> -- System Information:
>> Debian Release: trixie/sid
>>   APT prefers unstable-debug
>>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
>> 'experimental')
>> Architecture: amd64 (x86_64)
>> Foreign Architectures: i386
>>
>> Kernel: Linux 6.4.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
>> Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en
>> Shell: /bin/sh linked to /usr/bin/dash
>> Init: systemd (via /run/systemd/system)
>> LSM: AppArmor: enabled
>>
>> Versions of packages podman depends on:
>> ii  conmon   2.1.6+ds1-1
>> ii  golang-github-containers-common  0.50.1+ds1-4
>> ii  libc62.37-7
>> ii  libdevmapper1.02.1   2:1.02.185-2
>> ii  libgpgme11   1.18.0-3+b1
>> ii  libseccomp2  2.5.4-1+b3
>> ii  libsubid41:4.13+dfsg1-1+b1
>> ii  runc 1.1.5+ds1-1+b2
>>
>> Versions of packages podman recommends:
>> ii  buildah1.28.2+ds1-3+b2
>> ii  dbus-user-session  1.14.10-1
>> ii  fuse-overlayfs 1.10-1
>> ii  slirp4netns1.2.0-1
>> ii  tini   0.19.0-1
>> ii  uidmap 1:4.13+dfsg1-1+b1
>>
>> Versions of packages podman suggests:
>> pn  containers-storage  
>> pn  docker-compose  
>> ii  iptables1.8.9-2
>>
>> -- Configuration Files:
>> /etc/cni/net.d/87-podman-bridge.conflist [Errno 13] Permission denied:
>> '/etc/cni/net.d/87-podman-bridge.conflist'
>>
>> -- no debconf information
>>
>
>
> --
> regards,
> Reinhard
>

Bug#1051409: podman: Podman man pages use en-dash instead of dash

[Guy Rutenberg]

Package: podman
Version: 4.3.1+ds1-8+b2
Severity: minor
X-Debbugs-Cc: guyrutenb...@gmail.com

Dear Maintainer,

The man pages supplied by the podman package use unicode en-dash (‐) to
document flags instead of regular dash (-). This is both inconvinient when try
to search the man page, and incorrect (as you would use normal dash in the
shell).

Thanks,
Guy


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

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

Versions of packages podman depends on:
ii  conmon   2.1.6+ds1-1
ii  golang-github-containers-common  0.50.1+ds1-4
ii  libc62.37-7
ii  libdevmapper1.02.1   2:1.02.185-2
ii  libgpgme11   1.18.0-3+b1
ii  libseccomp2  2.5.4-1+b3
ii  libsubid41:4.13+dfsg1-1+b1
ii  runc 1.1.5+ds1-1+b2

Versions of packages podman recommends:
ii  buildah1.28.2+ds1-3+b2
ii  dbus-user-session  1.14.10-1
ii  fuse-overlayfs 1.10-1
ii  slirp4netns1.2.0-1
ii  tini   0.19.0-1
ii  uidmap 1:4.13+dfsg1-1+b1

Versions of packages podman suggests:
pn  containers-storage  
pn  docker-compose  
ii  iptables1.8.9-2

-- Configuration Files:
/etc/cni/net.d/87-podman-bridge.conflist [Errno 13] Permission denied: 
'/etc/cni/net.d/87-podman-bridge.conflist'

-- no debconf information

Bug#1037026: bugs.debian.org: Thinkpad button led issue

[Anonymous thinkpad guy]

Package: bugs.debian.org
Severity: normal
X-Debbugs-Cc: raga_plonge...@icloud.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I wanted to mute the mic of mmy computer with the f4 button, and the
led of the button should turn on, but it doesn't.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?
The led on the mute mic button to turn on

*** End of the template - remove these template lines ***

Bug#1034826: RFP: vt-cli -- A cli interface for Virus Total

[Guy Rutenberg]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: guyrutenb...@gmail.com

* Package name: vt-cli
  Version : 0.13.0
  Upstream Contact: N/A
* URL : https://virustotal.github.io/vt-cli/
* License : Apache-2.0
  Programming Lang: Go
  Description : A cli interface for Virus Total

a tool designed for those who love both VirusTotal and command-line interfaces.
With this tool you can do everything you'd normally do using the VirusTotal's
web page, including:

Retrieve information about a file, URL, domain name, IP address, etc.
Search for files and URLs using VirusTotal Intelligence query syntax.
Download files.
Manage your LiveHunt YARA rules.
Launch Retrohunt jobs and get their results.

And much more...

Bug#1033732: [PATCH v2] x86/acpi/boot: Do not register processors that cannot be onlined for x2apic

[Guy Durrieu]

Le 02/04/2023 à 12:57, Borislav Petkov a écrit :


On April 2, 2023 12:41:46 PM GMT+02:00, Guy Durrieu  
wrote:

My system worked fine with kernel 6.1.15, but stopped booting after
upgrading to 6.1.20 and resulted in a kernel panic:

Does this fix it:

https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=x86/urgent

Thx.


Yes it does.

Regards.

-- Guy Durrieu

Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message

[Guy Durrieu]

I sent the requested report. And indeed received a new patch to be 
tested.  In progress...


Le 02/04/2023 à 10:30, Diederik de Haas a écrit :

On Sunday, 2 April 2023 00:24:26 CEST Diederik de Haas wrote:

2) The commit that Bjørn identified also contained a "Link:" tag:
https://lore.kernel.org/r/20230105041059.39366-1-kvija...@amd.com

The best thing to do is to respond to that thread and explain the issue you
ran into.

If you feel 'uncomfortable' or something like that, we can do this part too.
If/when a new patch arrives, we will need your help in testing that though.

Bug#1033732: [PATCH v2] x86/acpi/boot: Do not register processors that cannot be onlined for x2apic

[Guy Durrieu]

Le 05/01/2023 à 05:10, Kishon Vijay Abraham I a écrit :


Section 5.2.12.12 Processor Local x2APIC Structure in the ACPI v6.5
spec mandates that both "enabled" and "online capable" Local APIC Flags
should be used to determine if the processor is usable or not.

However, Linux doesn't use the "online capable" flag for x2APIC to
determine if the processor is usable. As a result, cpu_possible_mask has
incorrect value and results in more memory getting allocated for per_cpu
variables than it is going to be used.

Make sure Linux parses both "enabled" and "online capable" flags for
x2APIC to correctly determine if the processor is usable.

Fixes: aa06e20f1be6 ("x86/ACPI: Don't add CPUs that are not online capable")
Reviewed-by: Borislav Petkov (AMD) 
Reported-by: Leo Duran 
Signed-off-by: Kishon Vijay Abraham I 


Hello everyone,

My system worked fine with kernel 6.1.15, but stopped booting after
upgrading to 6.1.20 and resulted in a kernel panic:

---
[ 0.117782] Kernel panic — not syncing: timer doesn’t work through 
Interrupt-remapped IO-APIC
[ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1 Debian 
6.1.20-1
[ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming 
3/AB350M-Gaming 3-CF, BIOS F50d 07/02/2020
[ 0.117982] Call Trace:
[ 0.118634] 
[ 0.118685] dump_stack_lvl+0x44/0x5c
[ 0.118143] panic+0x118/0x2ed
[ 0.118198] panic_if_irq_remap.cold+0x5/0x5
[ 0.118256] setup_I0_APIC+0x3db/0x64b
[ 0.118313] ? _raw_spin_unlock_irqrestore+0x23/0x40
[ 0.118372] ? clear_IO_APIC_pin+0x169/0x240
[ 0.118429] apic_intr_node_init+0x101/0x106
[ 0.118485] x86_late_time_init+0x20/0x34
[ 0.118542] start_kerne1+0x667/0x727
[ 0.118598] secondary_startup_64_no_verify+0xe5/0xeb
[ 0.118658] 
[ 0.118711] ---[ end Kernel panic - not syncing: timer doesn’t work through 
Interrupt-remapped IO-APIC J---
---
I tried an update of the BIOS up to F51h without any effect.

I sent a bug report to Debian Bug Tracking System. In reply Bjørn Mork 
identified ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b from the linux-6.1.y 
branch as the likely culprit.


After building a 6.1.20 kernel with just that commit reverted, my system boots 
normally again.

I reported that all tohttps://bugs.debian.org/1033732  and were asked to report 
the issue 'upstream' (which is what that mail is).

Hope it will help!

Best regards.

-- Guy Durrieu

Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message

[Guy Durrieu]

Hello everybody,

I just finished to build the patched kernel. After installing it, the 
system 6.1.0-7 boots again and run fine. Thus the source was well 
identified by Bjørn Mork. I just had problems trying to install 
linux-headers-6.1.0-7-amd64_6.1.20-1a~test_amd64.deb, for dependencies 
reasons not so clear for me. It is not mandatory anyway.


Thanks a lot to all of you for your help !

What next ?

Best regards.

-- Guy

Le 01/04/2023 à 19:48, Guy Durrieu a écrit :

Thanks for your help !

That was more or less my conclusion, but it would indeed be useful to 
clarify that 4.1 and 4.21. are mutually exclusive.


And I must admit that the # vs $ steps had escaped me :(

Best regards.

-- Guy

Le 01/04/2023 à 18:56, Diederik de Haas a écrit :

On Saturday, 1 April 2023 17:44:21 CEST Guy Durrieu wrote:
I am in trouble... I first did "Obtaining the kernel source", and at 
the

end I got a /root/linux-source-6.1/ directory.

Then I did "Rebuilding official Debian kernel packages" and
"Preparation", and then I got among others a
/root/linux-source-6.1/linux-6.1.20 the content of which is similar to
the parent one, and where I can find, by the way, a debian directory.

It seems strange to me, is it correct?
No, this is not correct. No worries though as this is a great way to 
learn how

we can improve the documentation :-)

With "Preparation" I meant paragraph 4.2.1 and you don't need to 
follow 4.1.
Also worth noting is that command prefixed by `#` should be done as 
root, but

the commands prefixed by `$` should be done as (normal) user.

So this is what you need to do:
# apt-get install build-essential fakeroot
# apt-get build-dep linux

While we're 'root', do this too:
# apt-get install devscripts

And then (as user):
$ apt-get source linux
$ cd linux-6.1.20

If you then do ``ls -lh`` you will see a ``debian`` directory.
So now you can run this:
$ bash debian/bin/test-patches 

And now it should build a patched kernel for you.


If it is correct, in what order to do the patches (debian patches and
the revert patch)?
When you look at the output of the ``apt-get source linux`` you'll 
see it
download the linux source code and (automatically) applies the debian 
patches

which are always applied when building a debian kernel.
This is excluding the patch I send earlier, but that gets applied 
when you run

the ``bash debian/bin/test-patches`` command.

HTH,
Diederik

Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message

[Guy Durrieu]

Thanks for your help !

That was more or less my conclusion, but it would indeed be useful to 
clarify that 4.1 and 4.21. are mutually exclusive.


And I must admit that the # vs $ steps had escaped me :(

Best regards.

-- Guy

Le 01/04/2023 à 18:56, Diederik de Haas a écrit :

On Saturday, 1 April 2023 17:44:21 CEST Guy Durrieu wrote:

I am in trouble... I first did "Obtaining the kernel source", and at the
end I got a /root/linux-source-6.1/ directory.

Then I did "Rebuilding official Debian kernel packages" and
"Preparation", and then I got among others a
/root/linux-source-6.1/linux-6.1.20 the content of which is similar to
the parent one, and where I can find, by the way, a debian directory.

It seems strange to me, is it correct?
No, this is not correct. No worries though as this is a great way to 
learn how

we can improve the documentation :-)

With "Preparation" I meant paragraph 4.2.1 and you don't need to 
follow 4.1.
Also worth noting is that command prefixed by `#` should be done as 
root, but

the commands prefixed by `$` should be done as (normal) user.

So this is what you need to do:
# apt-get install build-essential fakeroot
# apt-get build-dep linux

While we're 'root', do this too:
# apt-get install devscripts

And then (as user):
$ apt-get source linux
$ cd linux-6.1.20

If you then do ``ls -lh`` you will see a ``debian`` directory.
So now you can run this:
$ bash debian/bin/test-patches 

And now it should build a patched kernel for you.


If it is correct, in what order to do the patches (debian patches and
the revert patch)?

When you look at the output of the ``apt-get source linux`` you'll see it
download the linux source code and (automatically) applies the debian 
patches

which are always applied when building a debian kernel.
This is excluding the patch I send earlier, but that gets applied when 
you run

the ``bash debian/bin/test-patches`` command.

HTH,
Diederik

Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message

[Guy Durrieu]

Thanks for your help !

That was more or less my conclusion, but it would indeed be useful to 
clarify that 4.1 and 4.21. are mutually exclusive.


And I must admit that the # vs $ steps had escaped me :(

Best regards.

-- Guy

Le 01/04/2023 à 18:56, Diederik de Haas a écrit :

On Saturday, 1 April 2023 17:44:21 CEST Guy Durrieu wrote:

I am in trouble... I first did "Obtaining the kernel source", and at the
end I got a /root/linux-source-6.1/ directory.

Then I did "Rebuilding official Debian kernel packages" and
"Preparation",  and then I got among others a
/root/linux-source-6.1/linux-6.1.20 the content of which is similar to
the parent one, and where I can find, by the way, a debian directory.

It seems strange to me, is it correct?

No, this is not correct. No worries though as this is a great way to learn how
we can improve the documentation :-)

With "Preparation" I meant paragraph 4.2.1 and you don't need to follow 4.1.
Also worth noting is that command prefixed by `#` should be done as root, but
the commands prefixed by `$` should be done as (normal) user.

So this is what you need to do:
# apt-get install build-essential fakeroot
# apt-get build-dep linux

While we're 'root', do this too:
# apt-get install devscripts

And then (as user):
$ apt-get source linux
$ cd linux-6.1.20

If you then do ``ls -lh`` you will see a ``debian`` directory.
So now you can run this:
$ bash debian/bin/test-patches 

And now it should build a patched kernel for you.


If it is correct, in what order to do the patches (debian patches and
the revert patch)?

When you look at the output of the ``apt-get source linux`` you'll see it
download the linux source code and (automatically) applies the debian patches
which are always applied when building a debian kernel.
This is excluding the patch I send earlier, but that gets applied when you run
the ``bash debian/bin/test-patches`` command.

HTH,
   Diederik

Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message

[Guy Durrieu]

I am in trouble... I first did "Obtaining the kernel source", and at the 
end I got a /root/linux-source-6.1/ directory.


Then I did "Rebuilding official Debian kernel packages" and 
"Preparation",  and then I got among others a 
/root/linux-source-6.1/linux-6.1.20 the content of which is similar to 
the parent one, and where I can find, by the way, a debian directory.


It seems strange to me, is it correct?

If it is correct, in what order to do the patches (debian patches and 
the revert patch)?


Thanks in advance for your help !

Best regards.

-- Guy


Le 01/04/2023 à 16:55, Diederik de Haas a écrit :
 > > On April 1, 2023 4:31:49 PM GMT+02:00, Guy Durrieu > 
 wrote: >> Thanks for your help ! >> >> There 
is something not clear for me in the section 4.2.2. Simple >> patching 
and building... >> >> I ran apt-get install devscripts but I can't find 
any debian >> directory nor patches. Is it sufficient to apply the patch 
given by >> Diederik de Haas ? > > I'm guessing you forgot to do the 
Preparation from 4.2.1 > >> Le 01/04/2023 à 15:28, Salvatore Bonaccorso 
a écrit : >>> Hi, >>> >>> On Sat, Apr 01, 2023 at 11:51:38AM +0200, Guy 
Durrieu wrote: >>>> Hello, >>>> >>>> This is something I have never 
done, but I can try. >>>> >>>> However some time ago, for solving a 
previous issue, a guy from >>>> Debian compiled for me an unofficial 
release including the >>>> patch to be tested, along with some 
credentials. I know this is >>>> not the recommended procedure :) but it 
worked. >>> Seems there was a race on responding. If you look at the >>> 
documentation referenced by Diederik there are instructions on >>> how 
to do it with a single patch applied on top. If you run into >>> trouble 
let us know though. >>> >>> Regards, Salvatore >> >

Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message

[Guy Durrieu]

Thanks for your help !

There is something not clear for me in the section 4.2.2. Simple 
patching and building...


I ran apt-get install devscripts but I can't find any debian directory 
nor patches. Is it sufficient to apply the patch given by Diederik de Haas ?


Regards.

-- Guy

Le 01/04/2023 à 15:28, Salvatore Bonaccorso a écrit :

Hi,

On Sat, Apr 01, 2023 at 11:51:38AM +0200, Guy Durrieu wrote:

Hello,

This is something I have never done, but I can try.

However some time ago, for solving a previous issue, a guy from Debian
compiled for me an unofficial release including the patch to be tested,
along with some credentials. I know this is not the recommended procedure :)
but it worked.

Seems there was a race on responding. If you look at the documentation
referenced by Diederik there are instructions on how to do it with a
single patch applied on top. If you run into  trouble let us know
though.

Regards,
Salvatore

Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message

[Guy Durrieu]

Hello,

This is something I have never done, but I can try.

However some time ago, for solving a previous issue, a guy from Debian 
compiled for me an unofficial release including the patch to be tested, 
along with some credentials. I know this is not the recommended 
procedure :) but it worked.


Best regards,

-- Guy

Le 01/04/2023 à 11:00, Salvatore Bonaccorso a écrit :

Control: tags -1 + moreinfo

Hi Guy,

On Sat, Apr 01, 2023 at 10:09:09AM +0200, Guy Durrieu wrote:

Hello,

Thanks for your answer !

Before receiving it I tried to update my BIOS to the last available version
(F51h). Without any effect.

I am not sure I understand everything that is said in your link, except I
must wait for the next updates... Right ?

AFAIK there is no commit upstream with fixes tag on that commit. But
Bjorn suspects that might be the suspicious commit introducing the
issue.

Would you be able to build a kernel 6.1.20 with that patch reverted on
top and see if it resolved your issue?

Regards,
Salvatore

Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message

[Guy Durrieu]

Hello,

Thanks for your answer !

Before receiving it I tried to update my BIOS to the last available 
version (F51h). Without any effect.


I am not sure I understand everything that is said in your link, except 
I must wait for the next updates... Right ?


Best regards.

-- Guy

Le 01/04/2023 à 09:25, Bjørn Mork a écrit :

Guy Durrieu  writes:



[ 0.117782] Kernel panic — not syncing: timer doesn’t work through
Interrupt-
remapped I0-APIC
[ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1
Debian
6.1.20-1
[ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming
3/AB350M-Gaming 3-CF, BIOS F50d 07/02/2020
[ 0.117982] Call Trace:
[ 0.118634] 
[ 0.118685] dump_stack_lvl+0x44/0x5c
[ 0.118143] panic+0x118/0x2ed
[ 0.118198] panic_if_irq_remap.cold+0x5/0x5
[ 0.118256] setup_I0_APIC+0x3db/0x64b
[ 0.118313] ? _raw_spin_unlock_irqrestore+0x23/0x40
[ 0.118372] ? clear_IO_APIC_pin+0x169/0x240
[ 0.118429] apic_intr_node_init+0x101/0x106
[ 0.118485] x86_late_time_init+0x20/0x34
[ 0.118542] start_kerne1+0x667/0x727
[ 0.118598] secondary_startup_64_no_verify+0xe5/0xeb
[ 0.118658] 
[ 0.118711] ---[ end Kernel panic - not syncing: timer doesn’t work through
Interrupt-remapped IO-APIC J---


Extremely suspiscious commit in the v6.1.15..v6.1.20 update:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b



Bjørn

Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message

[Guy Durrieu]

Package: src:linux
Version: 6.1.20-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

Up to now I worked with Linux 6.1.0-7-amd64, without any trouble. I just
installed Linux 6.1.0-7-amd64 and I get a kernel panic when launching it.

Here is a transcription of what appears on the screen (OCR on a screen 
picture,

I hope there are no remaining errors).


[ 0.117782] Kernel panic — not syncing: timer doesn’t work through 
Interrupt-

remapped I0-APIC
[ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1 
Debian

6.1.20-1
[ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming
3/AB350M-Gaming 3-CF, BIOS F50d 07/02/2020
[ 0.117982] Call Trace:
[ 0.118634] 
[ 0.118685] dump_stack_lvl+0x44/0x5c
[ 0.118143] panic+0x118/0x2ed
[ 0.118198] panic_if_irq_remap.cold+0x5/0x5
[ 0.118256] setup_I0_APIC+0x3db/0x64b
[ 0.118313] ? _raw_spin_unlock_irqrestore+0x23/0x40
[ 0.118372] ? clear_IO_APIC_pin+0x169/0x240
[ 0.118429] apic_intr_node_init+0x101/0x106
[ 0.118485] x86_late_time_init+0x20/0x34
[ 0.118542] start_kerne1+0x667/0x727
[ 0.118598] secondary_startup_64_no_verify+0xe5/0xeb
[ 0.118658] 
[ 0.118711] ---[ end Kernel panic - not syncing: timer doesn’t work through
Interrupt-remapped IO-APIC J---


Hope it helps.
Thanks in advance for your help.
Best regards.

-- Guy Durrieu


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Gigabyte Technology Co., Ltd.
product_name: AB350M-Gaming 3
product_version: Default string
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: F50d
board_vendor: Gigabyte Technology Co., Ltd.
board_name: AB350M-Gaming 3-CF
board_version: x.x


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

Kernel: Linux 6.1.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 linux-image-6.1.0-7-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod    30+20221128-1
ii  linux-base  4.9

Versions of packages linux-image-6.1.0-7-amd64 recommends:
ii  apparmor 3.0.8-3
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-6.1.0-7-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.06-8
pn  linux-doc-6.1   

Versions of packages linux-image-6.1.0-7-amd64 is related to:
ii  firmware-amd-graphics 20230210-4
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x    
pn  firmware-brcm80211    
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
ii  firmware-linux-nonfree    20230210-4
ii  firmware-misc-nonfree 20230210-4
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
ii  firmware-realtek  20230210-4
pn  firmware-samsung  
pn  firmware-siano    
pn  firmware-ti-connectivity  
pn  xen-hypervisor    

-- no debconf information

Bug#1033001: darktable: Missing application icon after launching

[Guy Rutenberg]

On Sat, 18 Mar 2023 at 12:42, David Bremner  wrote:

>
>
> For the record, this issue is wayland specific.
>
> Adding
>
> StartupWMClass=darktable
>
> to the end of /usr/share/applications/org.darktable.darktable.desktop
> seems to fix it for me.
>
>
Thanks, David, that seems to fix it for me as well.

Bug#1033001: darktable: Missing application icon after launching

[Guy Rutenberg]

Package: darktable
Version: 4.2.1-3
Severity: normal
X-Debbugs-Cc: guyrutenb...@gmail.com

Dear Maintainer,

Under GNOME (43.3), the Darktable icon is visible when searching for the app,
but once the window is spawned, it is associated with a generic missing icon
(for example in Alt+Tab or the Activities overview).

The associated wmclass is "darktable", which seems fine. Not sure why the icon
disappears.

Thanks,
Guy


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

Kernel: Linux 6.1.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages darktable depends on:
ii  libavif150.11.1-1
ii  libc62.36-8
ii  libcairo21.16.0-7
ii  libcolord-gtk1   0.3.0-3
ii  libcolord2   1.4.6-2.2
ii  libcups2 2.4.2-2
ii  libcurl3-gnutls  7.88.1-6
ii  libexiv2-27  0.27.6-1
ii  libgcc-s112.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-1
ii  libgomp1 12.2.0-14
ii  libgphoto2-6 2.5.30-1
ii  libgphoto2-port122.5.30-1
ii  libgraphicsmagick-q16-3  1.4+really1.3.40-2
ii  libgtk-3-0   3.24.37-2
ii  libheif1 1.15.1-1
ii  libicu72 72.1-3
ii  libimath-3-1-29  3.1.6-1
ii  libjpeg62-turbo  1:2.1.5-2
ii  libjson-glib-1.0-0   1.6.6-1
ii  libjxl0.70.7.0-10
ii  liblcms2-2   2.14-2
ii  liblensfun1  0.3.3-1
ii  liblua5.4-0  5.4.4-3
ii  libopenexr-3-1-303.1.5-4
ii  libopenjp2-7 2.5.0-1+b1
ii  libosmgpsmap-1.0-1   1.2.0-2
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libpng16-16  1.6.39-2
ii  libportmidi0 1:217-6.1
ii  libpugixml1v51.13-0.2
ii  librsvg2-2   2.54.5+dfsg-1
ii  libsdl2-2.0-02.26.4+dfsg-1
ii  libsecret-1-00.20.5-3
ii  libsoup2.4-1 2.74.3-1
ii  libsqlite3-0 3.40.1-1
ii  libstdc++6   12.2.0-14
ii  libtiff6 4.5.0-5
ii  libwebp7 1.2.4-0.1
ii  libwebpmux3  1.2.4-0.1
ii  libx11-6 2:1.8.4-2
ii  libxml2  2.9.14+dfsg-1.1+b3
ii  libxrandr2   2:1.5.2-2+b1
ii  zlib1g   1:1.2.13.dfsg-1

darktable recommends no packages.

darktable suggests no packages.

-- no debconf information

Bug#1023700: Confirmed

[Guy Rutenberg]

On Fri, 24 Feb 2023 10:25:29 -0500 micah anderson  wrote:
>
> I've tried the same thing, and get the same results. It appears that the
> systemd support is there, the cryptsetup support is ithere, but just
> cryptsetup-initramfs is not somehow there also.

The old/regular cryptsetup is a different binary than the
systemd-cryptsetup. Only systemd-cryptsetup supports fido2 unlocking.

> It would be a shame to release bookworm with just the initramfs feature
> missing, when all the other pieces are there. Do you have any idea what
> might be blocking this?
>
> For what it is worth, dracut does work.
>

dracut works because it's based on systemd, so it uses systemd-cryptsetup.

See
https://www.guyrutenberg.com/2022/02/17/unlock-luks-volume-with-a-yubikey/.

Thanks,
Guy

Bug#1032054: darktable: AVIF support is missing in Darktable

[Guy Rutenberg]

Package: darktable
Version: 4.2.0-2+b1
Severity: wishlist
X-Debbugs-Cc: guyrutenb...@gmail.com

Dear Maintainer,

Darktable isn't compiled against libavif, resulting in no AVIF support.
libavif15 is available in the repos, so there should be no problem to depend on
it.

Thanks for you work,
Guy


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

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

Versions of packages darktable depends on:
ii  libc62.36-8
ii  libcairo21.16.0-7
ii  libcolord-gtk1   0.3.0-3
ii  libcolord2   1.4.6-2.1
ii  libcups2 2.4.2-1+b2
ii  libcurl3-gnutls  7.87.0-2
ii  libexiv2-27  0.27.6-1
ii  libgcc-s112.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.5-1
ii  libgomp1 12.2.0-14
ii  libgphoto2-6 2.5.30-1
ii  libgphoto2-port122.5.30-1
ii  libgraphicsmagick-q16-3  1.4+really1.3.40-2
ii  libgtk-3-0   3.24.36-4
ii  libheif1 1.14.2-1
ii  libicu72 72.1-3
ii  libimath-3-1-29  3.1.6-1
ii  libjpeg62-turbo  1:2.1.5-2
ii  libjson-glib-1.0-0   1.6.6-1
ii  libjxl0.70.7.0-10
ii  liblcms2-2   2.14-2
ii  liblensfun1  0.3.3-1
ii  liblua5.4-0  5.4.4-3
ii  libopenexr-3-1-303.1.5-4
ii  libopenjp2-7 2.5.0-1+b1
ii  libosmgpsmap-1.0-1   1.2.0-2
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libpng16-16  1.6.39-2
ii  libportmidi0 1:217-6.1
ii  libpugixml1v51.13-0.2
ii  librsvg2-2   2.54.5+dfsg-1
ii  libsdl2-2.0-02.26.3+dfsg-1
ii  libsecret-1-00.20.5-3
ii  libsoup2.4-1 2.74.3-1
ii  libsqlite3-0 3.40.1-1
ii  libstdc++6   12.2.0-14
ii  libtiff6 4.5.0-5
ii  libwebp7 1.2.4-0.1
ii  libwebpmux3  1.2.4-0.1
ii  libx11-6 2:1.8.3-3
ii  libxml2  2.9.14+dfsg-1.1+b3
ii  libxrandr2   2:1.5.2-2+b1
ii  zlib1g   1:1.2.13.dfsg-1

darktable recommends no packages.

darktable suggests no packages.

-- no debconf information

Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection

[Guy Durrieu]

Hi Salvatore,

I did the test using the kernel image you built for me. After 
reactivating rasdaemon (and rebooting), all apparently work fine.


I have a last question: Do I keep this version, and what will happen 
when the next kernel update occurs ? And what about the 6.0.0.2 one ?


Thanks for your help !

Best regards.

-- Guy.

Le 09/11/2022 à 19:21, Salvatore Bonaccorso a écrit :

Hi Guy,

On Wed, Nov 09, 2022 at 06:05:58PM +0100, Guy Durrieu wrote:

Hi Salvatore,

OK, I will try that as soon as possible. Am I supposed to re-enable the
rasdeamon once the patch applied ? Anyway I will report you the result (f I
don't make any mistake).

Yes right, the idea would be to boot the new kernel with rasdeamon
enabled again and see if the system is stable again.

Be aware though that rasdaemon itself might segfault, there is a
second issue, where rasdaemon needs fixing as well, see #1023725.

Regards,
Salvatore

Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection

[Guy Durrieu]

Hi Diederik,

Thanks for your useful answer, that is what I more or less understood 
after thinking about it, but it's better to have a confirmation :)


And don't worry, my emails were a bit messy anyway !

Best regards.

-- Guy Durrieu.

Le 10/11/2022 à 12:15, Diederik de Haas a écrit :

On donderdag 10 november 2022 11:54:59 CET Diederik de Haas wrote:

Perhaps I didn't understand what you meant... Does the linux image
6.0.0.3 (6.0.7.2) include the patch correcting my issue ? And in this
case, is it sufficient to download the linux image and the linux headers
in order to test the result ?

No. In order to test the patch, you do need to build a kernel.

Oh boy, I probably should've stayed out of it completely ...

In another response to this bug, Salvatore did provide an alternative means
and that is using the kernel package he build for you.

See this part:

On woensdag 9 november 2022 17:42:44 CET Salvatore Bonaccorso wrote:

Additionnally, I am not sure to know how to proceed in order to apply the
patch you sent. Could you give me some hint ?

There is our documentation at
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4
.2.2 . But would you be willing to test (but be aware, unsigned!) test
packages fetched byhttps://people.debian.org  ?

https://people.debian.org/~carnil/tmp/linux/6.0.7-2/

I have put a sha256sum file with signature on it with my gpg key to
have an additional verification on those.

https://db.debian.org/fetchkey.cgi?fingerprint=04A4407CB9142C23030C17AE789D6
F057FD863FE

So you have 2 options:
- build it yourself from source (with instructions from 4.2.2)
- Use the packages Salvatore build for you at the above location

Keep in mind that you normally shouldn't install programs ('deb' on Debian or
'exe' if on Windows) from "strangers on the internet". Salvatore did provide a
(gpg) signed file to provide some mitigation against the risks.
But you would still need to trust Salvatore.

If you build it yourself, then you don't download programs from "strangers on
the internet". But that obviously is more work. Which can be daunting if you
hadn't done that before.

HTH

(And now I'm really staying out of it ;-))

Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection

[Guy Durrieu]

Hi Salvatore,

Le 10/11/2022 à 09:41, Guy Durrieu a écrit :
I am not sure I am able to do that :) 


Perhaps I didn't understand what you meant... Does the linux image 
6.0.0.3 (6.0.7.2) include the patch correcting my issue ? And in this 
case, is it sufficient to download the linux image and the linux headers 
in order to test the result ?


Thanks and my apologies !

Best regards.

-- Guy

Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection

[Guy Durrieu]

Hi Salvatore,

Le 09/11/2022 à 17:42, Salvatore Bonaccorso a écrit :

There is our documentation at
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
. But would you be willing to test (but be aware, unsigned!) test
packages fetched byhttps://people.debian.org  ?


I am not sure I am able to do that :)

The first thing to do would be to perform the check you suggested 
yesterday. Am I wrong or do I have to rebuild a whole kernel from the 
source code? In this case would it be possible to install the source 
code elsewhere than on my (relatively small) SSD ?


Excuse me for my maybe basic questions, I've never done this before, and 
thanks in advance for your help !


Best regards.

-- Guy

Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection

[Guy Durrieu]

Hi Salvatore,

OK, I will try that as soon as possible. Am I supposed to re-enable the 
rasdeamon once the patch applied ? Anyway I will report you the result 
(f I don't make any mistake).


Thanks a lot for your help !

Best regards.


Le 09/11/2022 à 17:46, Salvatore Bonaccorso a écrit :

Hi Guy,

On Wed, Nov 09, 2022 at 05:20:25PM +0100, Guy Durrieu wrote:

Hi Salvatore,

Sorry. My first attempt was under 6.0.0-2... I tried again disabling
rasdaemon under 5.19.0-2 (it worked). Then I restarted 6.0.0-2 and the issue
seems to have disapeared (after a first bad start).

Thanks for confirming, so there is good indication you are seeing the
same as #1023726 and will later merge those.


Concerning the patch, my question remains (I don't have the source for
ring_buffer).

It looks I was too slow, my answer was on the way and overlapped with
this followup. There are instructions on how to "simple test patches".
But I have uploaded as well intermediate deb files (unsigned) which
you can use if you have enough trust level on the path to fetch them.

Regards,
Salvatore

Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection

[Guy Durrieu]

Hi Salvatore,

Sorry. My first attempt was under 6.0.0-2... I tried again disabling 
rasdaemon under 5.19.0-2 (it worked). Then I restarted 6.0.0-2 and the 
issue seems to have disapeared (after a first bad start).


Concerning the patch, my question remains (I don't have the source for 
ring_buffer).


Thanks for your help.

Best regards.

-- Guy Durrieu.


Le 09/11/2022 à 16:55, Guy Durrieu a écrit :


Hi Salvatore,

Thanks for your quick answer !

I tried the command "rasdaemon --disable" (as sudoer) , but it blocks 
and apparently doesn't product any effect. I also tried to directly 
kill the rasdaemon process, without success.


Additionnally, I am not sure to know how to proceed in order to apply 
the patch you sent. Could you give me some hint ?


Thanks in advance for your help.

Best regards.

-- Guy Durrieu.

Le 09/11/2022 à 16:19, Salvatore Bonaccorso a écrit :

Looking through the above the issue seems to be the same as #1023726.

Can you verify if the issue disapears if you disable rasdaemon?

Can you verify if the attached patch fixes the problem as well for
you?

Regards,
Salvatore

Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection

[Guy Durrieu]

Hi Salvatore,

Thanks for your quick answer !

I tried the command "rasdaemon --disable" (as sudoer) , but it blocks 
and apparently doesn't product any effect. I also tried to directly kill 
the rasdaemon process, without success.


Additionnally, I am not sure to know how to proceed in order to apply 
the patch you sent. Could you give me some hint ?


Thanks in advance for your help.

Best regards.

-- Guy Durrieu.

Le 09/11/2022 à 16:19, Salvatore Bonaccorso a écrit :

Looking through the above the issue seems to be the same as #1023726.

Can you verify if the issue disapears if you disable rasdaemon?

Can you verify if the attached patch fixes the problem as well for
you?

Regards,
Salvatore

Bug#1023734: linux-image-6.0.0-2-amd64: No network connection, no pulseaudio server connection

[Guy Durrieu]

Package: src:linux
Version: 6.0.5-1
Severity: normal (I would say serious...)

Dear Maintainer,

Until today, my linux-image-6.0.0-2-amd64 was OK. After the recent 
updates I get a serious problem: no more network connection (neither 
ethernet, wifi nor USB), and no more pulseaudio server connection.


When rebooting with the previous available version 
(linux-image-5.19.0-2-amd64) all work fine.


I thus send this report using thisversion of the kernel but you will 
find below the 200 lines of the kernel.log when booting 
linux-image-6.0.0-2-amd64. Hope it will help.


Thanks in advance for your help !

Best regards.

-- Guy Durrieu



2022-11-09T10:10:15.885062+01:00 ITI kernel: [    3.701731] amdgpu
:06:00.0: No more image in the PCI ROM
2022-11-09T10:10:15.885063+01:00 ITI kernel: [    3.701751] amdgpu
:06:00.0: amdgpu: Fetched VBIOS from ROM BAR
2022-11-09T10:10:15.885063+01:00 ITI kernel: [    3.701753] amdgpu: ATOM 
BIOS:

115-D009PI2-101
2022-11-09T10:10:15.885065+01:00 ITI kernel: [    3.701768] [drm] UVD is
enabled in VM mode
2022-11-09T10:10:15.885066+01:00 ITI kernel: [    3.701769] [drm] UVD ENC is
enabled in VM mode
2022-11-09T10:10:15.885066+01:00 ITI kernel: [    3.701770] [drm] VCE 
enabled

in VM mode
2022-11-09T10:10:15.885066+01:00 ITI kernel: [    3.701771] amdgpu
:06:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
2022-11-09T10:10:15.885067+01:00 ITI kernel: [    3.701812] [drm] vm 
size is 64

GB, 2 levels, block size is 10-bit, fragment size is 9-bit
2022-11-09T10:10:15.885067+01:00 ITI kernel: [    3.701850] amdgpu
:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_mc.bin
2022-11-09T10:10:15.885069+01:00 ITI kernel: [    3.701856] amdgpu
:06:00.0: amdgpu: VRAM: 8192M 0x00F4 - 0x00F5
(8192M used)
2022-11-09T10:10:15.885070+01:00 ITI kernel: [    3.701859] amdgpu
:06:00.0: amdgpu: GART: 256M 0x00FF - 0x00FF0FFF
2022-11-09T10:10:15.885070+01:00 ITI kernel: [    3.701863] [drm] 
Detected VRAM

RAM=8192M, BAR=256M
2022-11-09T10:10:15.885070+01:00 ITI kernel: [    3.701865] [drm] RAM width
256bits GDDR5
2022-11-09T10:10:15.885071+01:00 ITI kernel: [    3.701900] [drm] 
amdgpu: 8192M

of VRAM memory ready
2022-11-09T10:10:15.885071+01:00 ITI kernel: [    3.701901] [drm] 
amdgpu: 7975M

of GTT memory ready.
2022-11-09T10:10:15.885072+01:00 ITI kernel: [    3.701911] [drm] GART: 
num cpu

pages 65536, num gpu pages 65536
2022-11-09T10:10:15.885074+01:00 ITI kernel: [    3.702755] sr 15:0:0:0:
Attached scsi CD-ROM sr0
2022-11-09T10:10:15.885074+01:00 ITI kernel: [    3.703580] [drm] PCIE 
GART of

256M enabled (table at 0x00F40090).
2022-11-09T10:10:15.885074+01:00 ITI kernel: [    3.703686] amdgpu
:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_pfp_2.bin
2022-11-09T10:10:15.885075+01:00 ITI kernel: [    3.703702] amdgpu
:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_me_2.bin
2022-11-09T10:10:15.885075+01:00 ITI kernel: [    3.703717] amdgpu
:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_ce_2.bin
2022-11-09T10:10:15.885076+01:00 ITI kernel: [    3.703719] [drm] Chained IB
support enabled!
2022-11-09T10:10:15.885078+01:00 ITI kernel: [    3.703738] amdgpu
:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_rlc.bin
2022-11-09T10:10:15.885078+01:00 ITI kernel: [    3.703813] amdgpu
:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_mec_2.bin
2022-11-09T10:10:15.885078+01:00 ITI kernel: [    3.703887] amdgpu
:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_mec2_2.bin
2022-11-09T10:10:15.885079+01:00 ITI kernel: [    3.704362] amdgpu
:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_sdma.bin
2022-11-09T10:10:15.885116+01:00 ITI kernel: [    3.704383] amdgpu
:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_sdma1.bin
2022-11-09T10:10:15.885117+01:00 ITI kernel: [    3.704403] amdgpu:
hwmgr_sw_init smu backed is polaris10_smu
2022-11-09T10:10:15.885119+01:00 ITI kernel: [    3.704495] amdgpu
:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_uvd.bin
2022-11-09T10:10:15.885120+01:00 ITI kernel: [    3.704497] [drm] Found UVD
firmware Version: 1.130 Family ID: 16
2022-11-09T10:10:15.885120+01:00 ITI kernel: [    3.705128] amdgpu
:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_vce.bin
2022-11-09T10:10:15.885121+01:00 ITI kernel: [    3.705131] [drm] Found VCE
firmware Version: 53.26 Binary ID: 3
2022-11-09T10:10:15.885121+01:00 ITI kernel: [    3.705702] amdgpu
:06:00.0: firmware: direct-loading firmware amdgpu/polaris10_k_smc.bin
2022-11-09T10:10:15.885122+01:00 ITI kernel: [    3.759276] usbcore: 
registered

new interface driver usbhid
2022-11-09T10:10:15.885122+01:00 ITI kernel: [    3.759280] usbhid: USB HID
core driver
2022-11-09T10:10:15.885124+01:00 ITI kernel

Bug#1013887: totem: Unable to play DVDs

[Guy Durrieu]

Dear Maintainer,

Have you any idea about the problem I reported in june ?

Totem is still unable to play DVDs on my PC, although all necessary 
dependencies are installed, but maybe this is not directly related to 
Totem ?


Thanks in advance for your help !

Best regards.

-- Guy Durrieu


Package: totem
Version: 42.0-1
Severity: normal

Dear Maintainer,

Totem worked fine in the past, but now when trying to DVD with totem I 
get the

following error message:


Missing plugin: gstreamer|1.0|totem|Source DVD|urisource-dvd


However, all gstreamer packages are installed, especially 
gstreamer1.0-plugins-bad.



What happens ?

Thanks in advance for your help !

Best regards.

-- Guy Durrieu



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

Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE not set

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages totem depends on:
ii  grilo-plugins-0.3   0.3.14-1
ii  gsettings-desktop-schemas   42.0-1
ii  gstreamer1.0-gl 1.20.3-dmo1
ii  gstreamer1.0-gtk3   1.20.3-dmo1
ii  gstreamer1.0-plugins-base   1.20.3-dmo1
ii  gstreamer1.0-plugins-good   1.20.3-dmo1
ii  gstreamer1.0-x  1.20.3-dmo1
ii  libc6   2.33-7
ii  libcairo2   1.16.0-5
ii  libgdk-pixbuf-2.0-0 2.42.8+dfsg-1
ii  libglib2.0-0    2.72.2-2
ii  libgstreamer-plugins-base1.0-0  1.20.3-dmo1
ii  libgstreamer1.0-0   1.20.3-1
ii  libgtk-3-0  3.24.34-1
ii  libhandy-1-0    1.6.2-1
ii  libpango-1.0-0  1.50.7+ds-1
ii  libpangocairo-1.0-0 1.50.7+ds-1
ii  libtotem-plparser18 3.26.6-1
ii  libtotem0   42.0-1
ii  libx11-6    2:1.7.5-1
ii  totem-common    42.0-1

Versions of packages totem recommends:
ii  gstreamer1.0-libav 1:1.20.3-dmo1
ii  gstreamer1.0-plugins-bad   1:1.20.3-dmo1
ii  gstreamer1.0-plugins-ugly  1:1.20.3-dmo1
ii  gstreamer1.0-pulseaudio    1.20.3-dmo1
ii  totem-plugins  42.0-1

Versions of packages totem suggests:
pn  gnome-codec-install  

-- no debconf information

Bug#1018105: gimp: crashes when adding text to image

[guy]

Package: gimp
Version: 2.99.10-1
Followup-For: Bug #1018105
X-Debbugs-Cc: otsd...@proton.me

Dear Maintainer,
Same bug. Seg crash when trying to add text or manipulate text layer. 100%
failure on any attempt. Started on previous 2.10.32-1. No problem with previous
versions.


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

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

Versions of packages gimp depends on:
ii  gimp-data2.99.10-1
ii  graphviz 2.42.2-7
ii  libaa1   1.4p5-50
ii  libappstream-glib8   0.8.1-1
ii  libarchive13 3.6.0-1
ii  libasound2   1.2.7.2-1
ii  libbabl-0.1-01:0.1.96-1
ii  libbz2-1.0   1.0.8-5+b1
ii  libc62.35-1
ii  libcairo21.16.0-6
ii  libfontconfig1   2.13.1-4.5
ii  libfreetype6 2.12.1+dfsg-3
ii  libgcc-s112.2.0-3
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libgegl-0.4-01:0.4.38-1+b1
ii  libgexiv2-2  0.14.0-1+b1
ii  libgimp-3.0-02.99.10-1
ii  libglib2.0-0 2.74.0-1
ii  libgs9   9.56.1~dfsg-1
ii  libgtk-3-0   3.24.34-3
ii  libgudev-1.0-0   237-2
ii  libharfbuzz0b5.2.0-2
ii  libheif1 1.13.0-1
ii  libilmbase25 2.5.7-2+b1
ii  libjpeg62-turbo  1:2.1.2-1+b1
ii  libjson-glib-1.0-0   1.6.6-1
ii  libjxl0.70.7.0~git20220805.980c90f-3
ii  liblcms2-2   2.13.1-1+b1
ii  liblzma5 5.2.5-2.1
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.5-1 1.6.0-2
ii  libopenexr25 2.5.7-1
ii  libopenjp2-7 2.5.0-1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpangocairo-1.0-0  1.50.10+ds-1
ii  libpangoft2-1.0-01.50.10+ds-1
ii  libpng16-16  1.6.38-2
ii  libpoppler-glib8 22.08.0-2.1
ii  librsvg2-2   2.54.5+dfsg-1
ii  libstdc++6   12.2.0-3
ii  libtiff5 4.4.0-4
ii  libwebp7 1.2.2-2+b1
ii  libwebpdemux21.2.2-2+b1
ii  libwebpmux3  1.2.2-2+b1
ii  libwmf-0.2-7 0.2.12-5
ii  libwmflite-0.2-7 0.2.12-5
ii  libx11-6 2:1.8.1-2
ii  libxcursor1  1:1.2.1-1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-1
ii  libxmu6  2:1.1.3-3
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-4.1
ii  zlib1g   1:1.2.11.dfsg-4.1

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

Versions of packages gimp suggests:
ii  gimp-data-extras  1:2.0.2-1.1
ii  gimp-help-en [gimp-help]  2.10.0-1
pn  gjs   
pn  gvfs-backends 
pn  luajit
ii  python3   3.10.6-1

-- no debconf information

Bug#1013887: totem: Unable to play DVDs

[Guy Durrieu]

Package: totem
Version: 42.0-1
Severity: normal

Dear Maintainer,

Totem worked fine in the past, but now when trying to DVD with totem I 
get the

following error message:


Missing plugin: gstreamer|1.0|totem|Source DVD|urisource-dvd


However, all gstreamer packages are installed, especially 
gstreamer1.0-plugins-bad.



What happens ?

Thanks in advance for your help !

Best regards.

-- Guy Durrieu



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

Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages totem depends on:
ii  grilo-plugins-0.3   0.3.14-1
ii  gsettings-desktop-schemas   42.0-1
ii  gstreamer1.0-gl 1.20.3-dmo1
ii  gstreamer1.0-gtk3   1.20.3-dmo1
ii  gstreamer1.0-plugins-base   1.20.3-dmo1
ii  gstreamer1.0-plugins-good   1.20.3-dmo1
ii  gstreamer1.0-x  1.20.3-dmo1
ii  libc6   2.33-7
ii  libcairo2   1.16.0-5
ii  libgdk-pixbuf-2.0-0 2.42.8+dfsg-1
ii  libglib2.0-0    2.72.2-2
ii  libgstreamer-plugins-base1.0-0  1.20.3-dmo1
ii  libgstreamer1.0-0   1.20.3-1
ii  libgtk-3-0  3.24.34-1
ii  libhandy-1-0    1.6.2-1
ii  libpango-1.0-0  1.50.7+ds-1
ii  libpangocairo-1.0-0 1.50.7+ds-1
ii  libtotem-plparser18 3.26.6-1
ii  libtotem0   42.0-1
ii  libx11-6    2:1.7.5-1
ii  totem-common    42.0-1

Versions of packages totem recommends:
ii  gstreamer1.0-libav 1:1.20.3-dmo1
ii  gstreamer1.0-plugins-bad   1:1.20.3-dmo1
ii  gstreamer1.0-plugins-ugly  1:1.20.3-dmo1
ii  gstreamer1.0-pulseaudio    1.20.3-dmo1
ii  totem-plugins  42.0-1

Versions of packages totem suggests:
pn  gnome-codec-install  

-- no debconf information

Bug#900821: apache reads wrong data over cifs filesystems served by samba

[Guy Elsmore-Paddock]

I recently encountered this bug without using Apache. It is reproducible using 
Nextcloud PHP on nginx, as explained in this bug report I filed earlier today 
in the Nextcloud issue queue:
https://github.com/nextcloud/server/issues/31361

We saw it on both nginx and Apache, so that rules out Apache as one of the 3 
components that are involved in causing the issue. It appears that the issue is 
related to mmap(), which IMO points to the kernel but I suppose that the 
Samba/CIFS driver could be handling buffers improperly. We saw this in two 
different Kubernetes clusters, one running kernel 4.15.0-1113-azure and 
5.4.0-1068-azure

Guy Elsmore-Paddock | he/him/his
Lead Architect/Chief Technology Officer
Inveniem
[Inveniem Logo]

Bug#997919: pipewire: Automatich profile selection for bluetooth headsets fails since 0.3.39

[Guy Rutenberg]

Hi,

On Wed, 27 Oct 2021 21:24:51 +0200 =?UTF-8?B?RHlsYW4gQcOvc3Np?= <
dai...@debian.org> wrote:

> Could you check if you have both wireplumber and libspa-0.2-bluetooth
> installed on your system?
>
> bluez-hardware.conf has moved from pipewire-media-session to
> libspa-0.2-bluetooth in 0.3.37-1
>

I think the problem is that wireplumber simply doesn't support bluetooth
autoswitching yet. See
https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/90.
As I understand it, there is no reason in 0.3.39 not to provide
pipewire-media-session alongside wireplumber and let the user decide which
media session manager they want to use. I believe that approach was taken
by Arch.

Thanks,
Guy

Bug#993389: libcanberra-pulse: Add pipewire-pulse as alternative dependency to pulseaudio

[Guy Rutenberg]

Package: libcanberra-pulse
Severity: wishlist
X-Debbugs-Cc: guyrutenb...@gmail.com

Dear Maintainer,

libcanberra-pulse is the default backend for playing notification sounds in
GNOME. Currently it depends directly on pulseaudio. When one wants to
transition from pulseaudio to pipewire, this dependency makes it problematic to
completely remove pulseaudio. The solution is to add "pulseaudio | pipewire-
pulse" as the dependency instead of only pulseaudio.

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992686.

Thanks,
Guy

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

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

Versions of packages libcanberra-pulse depends on:
ii  libc6 2.31-17
ii  libcanberra0  0.30-7+b1
ii  libpulse0 15.0+dfsg1-2
pn  pulseaudio

libcanberra-pulse recommends no packages.

Bug#991129: systemd: FIDO2 tokens not supported on this build.

[Guy Rutenberg]

> src:systemd is built without libfido support, so what you see is expected.

I guessed someone made a decision to build it without libfido support.
I mainly wonder why, as it breaks some new functionality (like
enrolling FIDO keys to unlock LUKS drives at startup).

Thanks,
Guy

Bug#991129: systemd: FIDO2 tokens not supported on this build.

[Guy Rutenberg]

Package: systemd
Version: 249-1
Severity: normal
X-Debbugs-Cc: guyrutenb...@gmail.com

Dear Maintainer,

I'm trying to test out the new FIDO2 support for LUKS via systemd-cryptenroll.
However, when trying to use the --fido2-device switch, for example in the
following command
```
systemd-cryptenroll --fido2-device list
```
The command fails and reports

```
FIDO2 tokens not supported on this build.
```

Additional information:
I have the `libfido2-1` package installed. I don't know if that should be
required or not.

Thanks,
Guy


-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-10
ii  libapparmor1 2.13.6-10
ii  libaudit11:3.0-2
ii  libblkid12.36.1-7
ii  libc62.31-13
ii  libcap2  1:2.44-1
ii  libcrypt11:4.4.18-4
ii  libcryptsetup12  2:2.3.5-1
ii  libgcrypt20  1.8.7-6
ii  libgnutls30  3.7.1-5
ii  libgpg-error01.38-2
ii  libip4tc21.8.7-1
ii  libkmod2 28-1
ii  liblz4-1 1.9.3-2
ii  liblzma5 5.2.5-2
ii  libmount12.36.1-7
ii  libpam0g 1.4.0-7
ii  libseccomp2  2.5.1-1
ii  libselinux1  3.1-3
ii  libsystemd0  249-1
ii  libzstd1 1.4.8+dfsg-2.1
ii  mount2.36.1-7
ii  systemd-timesyncd [time-daemon]  249-1
ii  util-linux   2.36.1-7

Versions of packages systemd recommends:
ii  dbus  1.12.20-2

Versions of packages systemd suggests:
ii  policykit-10.105-31
ii  systemd-container  249-1

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.140
pn  libnss-systemd   
ii  libpam-systemd   249-1
ii  udev 247.3-5

-- no debconf information

Bug#973737: systemd: wtmp not updated after unexpected reboot

[Guy Geens]

Package: systemd
Version: 241-7~deb10u4
Severity: normal

Dear Maintainer,

Recently, I had a power loss on one of my machines.

After the reboot, wtmp contained the following entries:

$ last reboot
reboot   system boot  4.19.0-12-amd64  Tue Nov  3 09:09   still running
reboot   system boot  4.19.0-12-amd64  Mon Oct 19 14:54   still running
reboot   system boot  4.19.0-11-amd64  Sat Sep 26 12:27 - 14:54 (23+02:26)

The previous reboot is still listed as "running", while it should have
been updated.

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-4
ii  libapparmor1 2.13.2-10
ii  libaudit11:2.8.4-3
ii  libblkid12.33.1-0.1
ii  libc62.28-10
ii  libcap2  1:2.25-2
ii  libcryptsetup12  2:2.1.0-5+deb10u2
ii  libgcrypt20  1.8.4-5
ii  libgnutls30  3.6.7-4+deb10u5
ii  libgpg-error01.35-1
ii  libidn11 1.33-2.2
ii  libip4tc01.8.2-4
ii  libkmod2 26-1
ii  liblz4-1 1.8.3-1
ii  liblzma5 5.2.4-1
ii  libmount12.33.1-0.1
ii  libpam0g 1.3.1-5
ii  libseccomp2  2.3.3-4
ii  libselinux1  2.8-1+b1
ii  libsystemd0  241-7~deb10u4
ii  mount2.33.1-0.1
ii  util-linux   2.33.1-0.1

Versions of packages systemd recommends:
ii  dbus1.12.20-0+deb10u1
ii  libpam-systemd  241-7~deb10u4

Versions of packages systemd suggests:
ii  policykit-10.105-25
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.133+deb10u1
ii  udev 241-7~deb10u4

-- no debconf information

Bug#970805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970805.

[Bernard, Guy (GE Healthcare)]

Hello Joerg,
One way to fix the issue could be to update the abort option or create a 
bind/unbind option to unbind/bind the device.
Best Regards
Guy

PS:
What I found for Scientific Linux 7
cd /sys/bus/scsi/drivers/sr
echo "4:0:0:0" > unbind
echo "4:0:0:0" > bind

where 400 is the scsi identifier of the device

Bug#970805: Unable to mount after burning a CD with wodim

[Bernard, Guy (GE Healthcare)]

Package:cdrkit

Hello,
On Scientific Linux 7.8, I have an issue with wodim-1.1.11.
After burning a CD, it's not possible to mount the media.
I am obliged to eject the media and then reload it manually in order to check 
the content.
Is this issue known? Are there some actions to execute so that I can mount and 
check the content of the burnt media without a manual intervention?

Best Regards
Guy

Bug#949369: Info received (Bug#949369: i915: kernel crash in i915_active_acquire())

[Guy Baconniere]

@John try to install Linux Kernel 5.5.13 (aka 5.5.0-1) from sid

https://packages.debian.org/sid/kernel/linux-image-5.5.0-1-amd64-unsigned

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.12/CHANGES

 Chris Wilson (1):

  drm/i915/execlists: Track active elements during dequeue
 Matt Roper (1):

  drm/i915: Handle all MCR ranges
 Caz Yokoyama (1):

  Revert "drm/i915/tgl: Add extra hdc flush workaround"

Check the comment on Debian Bug #954817
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954817#17

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/comments/29

Bug#949369: i915: kernel crash in i915_active_acquire()

[Guy Baconniere]

FYI
My bug report
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551

I ported the patch
https://launchpadlibrarian.net/470860672/ubuntu-focal-1868551-i915_active_acquire.patch

Official Issue #827
https://gitlab.freedesktop.org/drm/intel/issues/827

Good article on the subject
https://linuxreviews.org/Linux_Kernel_5.5_Will_Not_Fix_The_Frequent_Intel_GPU_Hangs_In_Recent_Kernels

Best Regards,
Guy Baconniere

Bug#954181: Please stop disabling Bluetooth monitor support in libpcap

[Guy Harris]

Package: libpcap0.8
Version: 1.8.1-6

That version of the package has a patch, patches/bluez-build.diff, that 
"[Includes] bluetooth/mgmt.h in bt-monitor compile test to make it fail with 
BlueZ 5.x."

This has already caused at least one complaint with Wireshark running on a 
Debian derivative, Linux Mint (well, a derivative of a derivative...):


https://ask.wireshark.org/question/15232/how-to-modify-link-layer-header-for-bluetooth-captures/

Please remove this, so that people can use the bluetooth-monitor device on 
Debian - and on its derivatives, once it trickles down to all the derivatives.  
I built the current master-branch versions of libpcap and tcpdump on Ubuntu 
18.04, and they work Just Fine, at least on my VMware Fusion VM with my Mac's 
Bluetooth adapter turned on (they may have found some problems in the Wireshark 
*dissector* for Bluetooth monitor messages, but that's another matter).

Bug#953880: gimp: segmentation fault on startup

[guy]

Package: gimp
Version: 2.10.14-2+b1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? unknown - perhaps sid update
   * What exactly did you do (or not do) that was effective (or
 ineffective)? reinstalled - no change
   * What was the outcome of this action? same problem
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



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

Kernel: Linux 5.6.0-rc5-siduction-amd64 (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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 gimp depends on:
ii  gimp-data2.10.14-2
ii  libaa1   1.4p5-46+b1
ii  libbabl-0.1-00.1.74-1
ii  libbz2-1.0   1.0.8-2
ii  libc62.30-2
ii  libcairo21.16.0-4
ii  libfontconfig1   2.13.1-2+b1
ii  libfreetype6 2.10.1-2
ii  libgcc-s110-20200304-1
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-3
ii  libgegl-0.4-00.4.22-1
ii  libgexiv2-2  0.12.0-2
ii  libgimp2.0   2.10.14-2+b1
ii  libglib2.0-0 2.64.0-2
ii  libgs9   9.51~dfsg-1
ii  libgtk2.0-0  2.24.32-4
ii  libgudev-1.0-0   233-1
ii  libharfbuzz0b2.6.4-1
ii  libheif1 1.6.1-1
ii  libilmbase24 2.3.0-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-4+b1
ii  liblzma5 5.2.4-1+b1
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.5-1 1.5.1-1
ii  libopenexr24 2.3.0-6
ii  libopenjp2-7 2.3.1-1
ii  libpango-1.0-0   1.42.4-8
ii  libpangocairo-1.0-0  1.42.4-8
ii  libpangoft2-1.0-01.42.4-8
ii  libpng16-16  1.6.37-2
ii  libpoppler-glib8 0.71.0-6
ii  librsvg2-2   2.46.4-1
ii  libstdc++6   10-20200304-1
ii  libtiff5 4.1.0+git191117-2
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libwmf0.2-7  0.2.8.4-17
ii  libx11-6 2:1.6.9-2
ii  libxcursor1  1:1.2.0-2
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2+b3
ii  libxpm4  1:3.5.12-1
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-2

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

Versions of packages gimp suggests:
pn  gimp-data-extras  
pn  gimp-help-en | gimp-help  
pn  gvfs-backends 
ii  libasound21.2.2-2.1
```
GNU Image Manipulation Program version 2.10.14
git-describe: GIMP_2_10_12-511-ga4f55d6c7e
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 
9.2.1-31' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-9 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch 
--disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none,hsa --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean 
--enable-link-mutex
Thread model: posix
gcc version 9.2.1 20200306 (Debian 9.2.1-31) 

using babl version 0.1.74 (compiled against version 0.1.74)
using GEGL version 0.4.22 (compiled against version 0.4.22)
using GLib version 2.64.0 (compiled against version 2.64.0)
using GdkPixbuf version 2.40.0 (compiled against version 2.40.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Segmentation fault

Stack trace:
```

Bug#943874: pure-ftpd: pure-ftp error on upgrade

[Guy Geens]

Hello

I also encountered this error.

As far as I can see, the documentation (/usr/share/doc/pure-ftp) is
included in both pure-ftp and pure-ftp-common packages.

Bug#943993: smplayer doesn't manage time properly

[Guy Durrieu]

Package: smplayer
Version: 18.10.0~ds0-1
Severity: important

Dear Maintainer,

Due, I suppose, to a recent update, smplayer doesn't manage time 
properly anymore:


- current time and total duration are displayed as 00:00:00.
- when restarting, a video correctly restarts from a previously stored 
time (when smplayer worked normally).
- but if the video is paused, it will not restart at all; as a matter of 
fact, the displayed button from the beginning is always |>, not ||...
- when restarting again, the video always restarts from the same time 
(the laast stop time is not stored).


I tried to reset the smplayer directory (within .config) without any 
effect (except all videos restart from 00:00:00).


Thanks in advance for your help !

Regards.

-- Guy Durrieu.

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages smplayer depends on:
ii  libc6   2.29-2
ii  libgcc1 1:9.2.1-8
ii  libqt5core5a    5.11.3+dfsg1-4
ii  libqt5dbus5 5.11.3+dfsg1-4
ii  libqt5gui5  5.11.3+dfsg1-4
ii  libqt5network5  5.11.3+dfsg1-4
ii  libqt5script5   5.11.3+dfsg-3
ii  libqt5widgets5  5.11.3+dfsg1-4
ii  libqt5xml5  5.11.3+dfsg1-4
ii  libstdc++6  9.2.1-8
ii  libx11-6    2:1.6.8-1
ii  mplayer 4:1.4-dmo5
ii  mpv 1:0.30.0-dmo1
ii  zlib1g  1:1.2.11.dfsg-1+b1

Versions of packages smplayer recommends:
ii  smplayer-l10n    18.10.0~ds0-1
ii  smplayer-themes  1:18.6.0-1

smplayer suggests no packages.

-- no debconf information

Bug#722496: debdiff v2

[Callum Guy]

I believe the issue relates to if-pre-up.d/vlan - a comparison is performed
to evaluate the actual device MTU against that of the interface being
provisioned however when actioning the change the raw device name is used
in the ip link command:

if [ -n "$IF_MTU" -a -n "$IF_VLAN_RAW_DEVICE" ]; then
CUR_DEV_MTU=$(cat /sys/class/net/$IF_VLAN_RAW_DEVICE/mtu)
# increase the vlan raw device mtu if needed
if [ -n "$CUR_DEV_MTU" ] && [ $CUR_DEV_MTU -lt $IF_MTU ]; then
*ip link set dev $IF_VLAN_RAW_DEVICE mtu $IF_MTU*
fi
fi

Shouldn't this be:

if [ -n "$IF_MTU" -a -n "$IF_VLAN_RAW_DEVICE" ]; then
CUR_DEV_MTU=$(cat /sys/class/net/$IF_VLAN_RAW_DEVICE/mtu)
# increase the vlan raw device mtu if needed
if [ -n "$CUR_DEV_MTU" ] && [ $CUR_DEV_MTU -lt $IF_MTU ]; then
*ip link set dev $IFACE mtu $IF_MTU*
fi
fi

I would be happy to submit a patch if i knew where

On Mon, 12 Sep 2016 18:35:29 -0400 Dan Streetman <
dan.street...@canonical.com> wrote:
> sorry, there was a problem with the last patch; it didn't work if the
> vlan interface already existed, even if the raw device mtu was too
> low.  this updated debdiff checks and increases the dev mtu even if
> the vlan interface already exists.

-- 





*0333 332   |  www.x-on.co.uk   |   ** 
    
   *


X-on
is a trading name of Storacall 
Technology Ltd a limited company registered in
England and Wales.


Registered Office : Avaland House, 110 London Road, Apsley, Hemel 
Hempstead,
Herts, HP3 9SD. Company Registration No. 2578478.

The 
information in this e-mail is confidential and for use by the addressee(s)

only. If you are not the intended recipient, please notify X-on immediately 
on +44(0)333 332  and delete the
message from your computer. If you are 
not a named addressee you must not use,
disclose, disseminate, distribute, 
copy, print or reply to this email. Views
or opinions expressed by an 
individual
within this email may not necessarily
reflect the views of X-on 
or its associated companies. Although X-on routinely
screens for viruses, 
addressees should scan this email and any attachments
for
viruses. X-on 
makes no representation or warranty as to the absence of viruses
in this 
email or any attachments.

Bug#927219: closing

[Guy De Lathouwer]

Hello,
I see that you cannot reproduce the problem, however it seems I have a similar 
one.

Cannot start Xorg without Nomodeset with a Radeon 6630HD (Mac mini Mid 2011), 
Ubuntu 19.04

Seems a quite common issue. MacBookPro users tend to desactivate the ATI 
discrete card and rely on the Intel integrated, which is not possible on a Mini 
(only discrete card).

Cheers

Guy



[59.653] (--) Log file renamed from "/var/log/Xorg.pid-2807.log" to 
"/var/log/Xorg.0.log"
[59.696] 
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[59.696] Build Operating System: Linux 4.4.0-143-generic x86_64 Ubuntu
[59.696] Current Operating System: Linux enterprise 5.0.0-25-generic 
#26-Ubuntu SMP Thu Aug 1 12:04:58 UTC 2019 x86_64
[59.696] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=6e0dbfe0-7de9-47ff-bb01-911e4e3e9356 ro nomodeset
[59.696] Build Date: 03 April 2019  09:03:57AM
[59.696] xorg-server 2:1.20.4-1ubuntu3 (For technical support please see 
http://www.ubuntu.com/support) 
[59.696] Current version of pixman: 0.36.0
[59.696]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[59.696] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[59.697] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Aug 16 12:33:35 
2019
[59.829] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[59.918] (==) No Layout section.  Using the first Screen section.
[59.918] (==) No screen section available. Using defaults.
[59.918] (**) |-->Screen "Default Screen Section" (0)
[59.918] (**) |   |-->Monitor ""
[59.919] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[59.920] (==) Automatically adding devices
[59.920] (==) Automatically enabling devices
[59.920] (==) Automatically adding GPU devices
[59.920] (==) Automatically binding GPU devices
[59.920] (==) Max clients allowed: 256, resource mask: 0x1f
[59.968] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[59.968]Entry deleted from font path.
[59.968] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[59.968]Entry deleted from font path.
[59.968] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[59.968]Entry deleted from font path.
[59.968] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[59.968]Entry deleted from font path.
[59.968] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[59.968]Entry deleted from font path.
[59.968] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
[59.968] (==) ModulePath set to "/usr/lib/xorg/modules"
[59.968] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[59.968] (II) Loader magic: 0x559356e0f020
[59.968] (II) Module ABI versions:
[59.968]X.Org ANSI C Emulation: 0.4
[59.968]X.Org Video Driver: 24.0
[59.968]X.Org XInput driver : 24.1
[59.968]X.Org Server Extension : 10.0
[59.971] (++) using VT number 2

[59.977] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_31
[59.986] (--) PCI: (0@0:2:0) 8086:0126:106b:00f0 rev 9, Mem @ 
0xa800/4194304, 0xa000/134217728, I/O @ 0x3000/64
[59.986] (--) PCI:*(1@0:0:0) 1002:6741:106b:00e8 rev 0, Mem @ 
0x9000/268435456, 0xa880/131072, I/O @ 0x2000/256, BIOS @ 
0x/131072
[59.986] (II) LoadModule: "glx"
[59.986] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[60.131] (II) Module glx: vendor="X.Org Foundation"
[60.131]compiled for 1.20.4, module version = 1.0.0
[60.131]ABI class: X.Org Server Extension, version 10.0
[60.131] (==) Matched ati as autoconfigured driver 0
[60.131] (==) Matched modesetting as autoconfigured driver 1
[60.131] (==) Matched fbdev as autoconfigured driver 2
[60.131] (==) Matched vesa as autoconfigured driver 3
[60.131] (==) Assigned the driver to the xf86ConfigLayout
[60.131] (II) LoadModule: "ati"
[60.132] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[60.132] (II) Module ati: vendor="X.Org Foundation"
[60.132]compiled for 1.20.4, module version = 19.0.1
[60.132]Module class: X.Org Video Driver
[60.132]ABI class: X.Org Video Driver, version 24.0
[60.204] (II) LoadModule: "radeon"
[  

Bug#924791: kea-dhcp-ddns-server: won't start on boot because of mis-typed WantedBy in the .service file

[Jason Guy]

Hi Markus,

We are trying to get this in Buster, but not sure how that is going...or
why it is taking so long.
However, in the meantime, you can simply add the sid repo to the sources,
and add an apt preference to pin the Kea packages to use Sid.

Jason

On Thu, Jun 6, 2019 at 10:54 AM Markus Schönhaber <
debian-b...@ddt-consult.de> wrote:

> Hi Jason,
>
> how is one supposed to upgrade the package to 1.5.0 on a
> released/supported Debian version (i. e. without moving to sid or create
> some kind of a frankendebian)?
>
> Jason Guy:
>
> > The version 1.1.0 package is not supported anymore. Please upgrade to the
> > 1.5.0 package.
>

Bug#924105: Need to add group creation to postinst script

[Jason Guy]

I see now...

dpkg-statoverride: error: group '_kea' does not exist

I will fix this...

Jason


On Thu, Jun 6, 2019 at 10:06 AM Jason Guy  wrote:

> Hi Shane,
>
> Thanks for the help on this. I thought the username is automatically
> created with a group of the same name, as part of user creation.
> Is the _kea group not getting created when you installed it? Please let me
> know what OS and version you tested on.
>
> I see there is a loop that also set the user and group for all files in
> /var/log/kea:
>
>for d in /var/log/kea /var/lib/kea; do
> if ! dpkg-statoverride --list $d >/dev/null 2>&1; then
> dpkg-statoverride --update --add *_kea _kea 0750 $d*
> fi
> done
>
> This _kea user is new in 1.5.0, for security, so it is only done for the
> debian/ubuntu package installs.
>
> Thanks,
> Jason
>
> On Fri, Apr 26, 2019 at 4:33 PM Shane Spencer  wrote:
>
>> addgroup --force-bad-name --system _kea
>> adduser ...
>> adduser _kea _kea
>>
>> That way kea is run as _kea.nogroup with access to _kea group.
>>
>> Not sure about those names either.  Is that standard for kea installs?
>>
>> <https://about.me/ShaneSpencer?promo=email_sig_source=product_medium=email_sig_campaign=gmail_api_content=thumb>
>> Shane Spencer
>> about.me/ShaneSpencer
>> <https://about.me/ShaneSpencer?promo=email_sig_source=product_medium=email_sig_campaign=gmail_api_content=thumb>
>>
>

Bug#924791: kea-dhcp-ddns-server: won't start on boot because of mis-typed WantedBy in the .service file

[Jason Guy]

Hi Markus,

The version 1.1.0 package is not supported anymore. Please upgrade to the
1.5.0 package.

Jason

On Sun, Mar 17, 2019 at 1:33 PM Markus Schönhaber <
debian-b...@ddt-consult.de> wrote:

> Package: kea-dhcp-ddns-server
> Version: 1.1.0-1
> Severity: important
>
> Dear Maintainer,
>
> the service names given in the WantedBy entires of kea's .service
> file contain an additional character 'v' that is not present in the
> names of the services referenced - for example
> kea-dhcp*v*4-server.service instead of kea-dhcp4-server.service.
> Therefore, the .service.wants directories created by systemd on
> enabling the service have the wrong name and the symlinks created in there
> are ignored when calculating the dependencies.
> The trivial patch which is attached solves this problem for me.
>
> -- System Information:
> Debian Release: 9.8
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
> LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages kea-dhcp-ddns-server depends on:
> ii  kea-common 1.1.0-1
> ii  libboost-system1.62.0  1.62.0+dfsg-4
> ii  libc6  2.24-11+deb9u4
> ii  libgcc11:6.3.0-18+deb9u1
> ii  libstdc++6 6.3.0-18+deb9u1
>
> kea-dhcp-ddns-server recommends no packages.
>
> Versions of packages kea-dhcp-ddns-server suggests:
> ii  kea-doc  1.1.0-1
>
> -- Configuration Files:
> /etc/kea/kea-dhcp-ddns.conf changed [not included]
>
> -- no debconf information
>

Bug#924105: Need to add group creation to postinst script

[Jason Guy]

Hi Shane,

Thanks for the help on this. I thought the username is automatically
created with a group of the same name, as part of user creation.
Is the _kea group not getting created when you installed it? Please let me
know what OS and version you tested on.

I see there is a loop that also set the user and group for all files in
/var/log/kea:

   for d in /var/log/kea /var/lib/kea; do
if ! dpkg-statoverride --list $d >/dev/null 2>&1; then
dpkg-statoverride --update --add *_kea _kea 0750 $d*
fi
done

This _kea user is new in 1.5.0, for security, so it is only done for the
debian/ubuntu package installs.

Thanks,
Jason

On Fri, Apr 26, 2019 at 4:33 PM Shane Spencer  wrote:

> addgroup --force-bad-name --system _kea
> adduser ...
> adduser _kea _kea
>
> That way kea is run as _kea.nogroup with access to _kea group.
>
> Not sure about those names either.  Is that standard for kea installs?
>
> 
> Shane Spencer
> about.me/ShaneSpencer
> 
>

Bug#927337: uzbl: Please update to a to current upstream version

[Martin Guy]

On 18/04/2019, Martin Guy  wrote:
> The v0.9.1 branch "make install"s for me, however, and that is from
> October 2016.

Ah. It seemed to work when I tested it, but stopped doing so when I
removed the stable Debian package. Now it gives a blank screen because
uzbl-event-manager fails to start.

Sorry for the noise

   M

Bug#927337: uzbl: Please update to a to current upstream version

[Martin Guy]

On Thu, 11 Apr 2019 18:35:04 +0200 Nicolas Schier  wrote:
> On https://github.com/uzbl/uzbl there is a tag 'v0.9.1' available, but
> probably the 'master' or 'next' branch could also make sense...

The master branch doesn't build on current Debian stable - "git bisect
run make" thinks that the last commit that made out of the box is
commit d0f0d from January 2013.

The v0.9.1 branch "make install"s for me, however, and that is from
October 2016.

Blessings

M

Bug#910671: kea-dhcp4-server: Missing /var/kea and /var/run/kea

[Jason Guy]

Hi Baptiste,

Apologies for this, but I fixed this bug months ago. I am somewhat new at
maintaining a package, and apparently I failed to do something to get the
debian build system to pickup the changes for P1-4 and P1-5. I will figure
out how to do this critical step, and make sure it gets pushed to Sid. I am
starting to package 1.5, and wanted to make sure 1.4 was moved to
testing but I have to first make sure it is actually pushed to Sid
first. :(

Thanks
Jason

On Fri, Nov 9, 2018 at 10:56 AM Jason Guy  wrote:

> Thanks for sharing Martin. In 1.3 I had all the directories defined
> correctly, but we made a bunch of changes and I thought I fixed all of the
> directories in 1.4, but you are correct, the localstatedir SHOULD be
> /var/lib/kea, which should be created during the install. I will take a
> look over the weekend, and fix this.
>
> Cheers,
> Jason
>
> On Wed, Nov 7, 2018 at 10:30 AM Martin Weinelt 
> wrote:
>
>> I temporarily fixed this using systemd-tmpfiles:
>>
>> # cat /etc/tmpfiles.d/kea.conf
>> #Type Path Mode UID  GID  Age Argument
>> d /run/kea 0755 root root -   -
>>
>> # systemd-tmpfiles --create
>>
>> Instead of using /var/kea I used /var/lib/kea which existed from before
>> the upgrade.
>>
>> Set a "name", actually a path, for your lease-database:
>>
>> "lease-database": {
>> // Memfile is the simplest and easiest backend to use. It's a
>> in-memory
>> // C++ database that stores its state in CSV file.
>> "type": "memfile",
>> "lfc-interval": 3600,
>> "name": "/var/lib/kea/dhcp4.leases"
>> },
>>
>>
>> Best regards
>>
>> Martin
>>
>>

Bug#910671: kea-dhcp4-server: Missing /var/kea and /var/run/kea

[Jason Guy]

Thanks for sharing Martin. In 1.3 I had all the directories defined
correctly, but we made a bunch of changes and I thought I fixed all of the
directories in 1.4, but you are correct, the localstatedir SHOULD be
/var/lib/kea, which should be created during the install. I will take a
look over the weekend, and fix this.

Cheers,
Jason

On Wed, Nov 7, 2018 at 10:30 AM Martin Weinelt 
wrote:

> I temporarily fixed this using systemd-tmpfiles:
>
> # cat /etc/tmpfiles.d/kea.conf
> #Type Path Mode UID  GID  Age Argument
> d /run/kea 0755 root root -   -
>
> # systemd-tmpfiles --create
>
> Instead of using /var/kea I used /var/lib/kea which existed from before
> the upgrade.
>
> Set a "name", actually a path, for your lease-database:
>
> "lease-database": {
> // Memfile is the simplest and easiest backend to use. It's a
> in-memory
> // C++ database that stores its state in CSV file.
> "type": "memfile",
> "lfc-interval": 3600,
> "name": "/var/lib/kea/dhcp4.leases"
> },
>
>
> Best regards
>
> Martin
>
>

Bug#905977: kea-ctrl-agent: missing dependency on python3

[Jason Guy]

Thanks Adrian, I have made the changes to fix this, but I am running into
issues building the package. The odd part is the errors seem unrelated to
the changes. I just wanted to let you know I am working on it.




On Sun, Aug 12, 2018 at 1:58 PM, Adrian Bunk  wrote:

> Package: kea-ctrl-agent
> Version: 1.4.0.P1-3
> Severity: serious
>
> kea-ctrl-agent lacks a python3 dependency
> for /usr/sbin/kea-shell
>
> This can be fixed by adding dh-python to the build dependencies
> plus python3 to the "dh $@ --with" in debian/rules.
>

Bug#906134: RFS

[Jason Guy]

Hi Kai-Chung,

I agree. I will do that. Thanks.

Jason

On Fri, Sep 21, 2018 at 6:20 AM 殷啟聰 | Kai-Chung Yan 
wrote:

> Hello Jason,
>
> I am not a DD, but this thread might seem inappropriate to appear as a
> "sponsorship-requests" bug. How about posting it to debian-mentors [1] and
> then closing this bug?
>
> [1]: https://lists.debian.org/debian-mentors
>
>

Bug#906134: RFS

[Jason Guy]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I have been doing a lot of work on the isc-kea package. The new maintainer
Ondrej Sury suggested I get a mentor to help me refine my packaging skills.

I am fairly comfortable with the package layout, and most of the basics of
building. I have read everything I can find on maintaining debian packages,
but it would be great to expand on that and learn more.

Thanks,
Jason

Bug#901525: TAG: isc-kea -- Next-gen DHCP server

[Jason Guy]

Package: wnpp
Severity: important

The current version of the isc-kea package in the debian repo is 1.1. ISC
is about to release version 1.4. The user community has been requesting the
Debian packages get updated, with the current version of Kea 1.3 pushed to
stable, and provide beta version 1.4 in testing.

I have been trying to contact the maintainer for over a year, with minimal
success getting a response. In one reply, he mentioned back in December he
is very busy. I have offered my help many times and I actually went ahead
and packaged Kea 1.3, and sent him the patches. He gladly took the patches,
and updated the git repo, but unfortunately he never pushed the package to
the Sid repo for users to test. Furthermore, I have some bug fixes, which I
have sent him and have not seen them merged on the git repo.

Adam has not replied to me in over 6 months, and it seems he has no
interest actively maintaining this package. I will be more than happy to
take over the maintenance or become a co-maintainer of this package.

Currently it looks like there is an error with the build system accessing
the git repo, which needs fixed. Most of the bugs should be fixed with
latest patches I have.


Thanks,
Jason Guy

Bug#883016: ITP: isc-kea -- New upstream version 1.3.0 released

[Jason Guy]

Hi Ivan,

I have been working with Adam to update this. The git repo does not have
the latest fixes, but I have a patch for the final patch for 1.3.0. I do
not have the permissions to get make the 1.3.0 marked stable, or pushed to
the APT repo. I am starting work on 1.4.0, but yes, I agree we need to be
better about pushing the packages out.

Jason

On Fri, Jun 1, 2018 at 3:32 AM, Ivan Stenda  wrote:

> as 1.4.0-beta released already, I would kindly ask for update at least to
> last stable  [1.3.0] ...
>
> regards
> i
>

Bug#883016: ITP: isc-kea -- New upstream version 1.3.0 released

[Jason Guy]

Hi Adam,

Apologies, I see you pushed my changes. I didn't see the package tracker
update the testing or unstable versions. How do we get this page updated?
https://tracker.debian.org/pkg/isc-kea

Thanks for pushing my changes to the git repo. I am going to pull it down
and build it.

Cheers,
Jason

On Fri, Feb 2, 2018 at 10:47 AM, Jason Guy <jason.e@gmail.com> wrote:

> Hi Adam,
>
> What is the status on getting the Kea 1.3 package done. Is it possible for
> me to create a branch for the kea1.3 so users can at least build the
> package themselves, and use it? People are unicasting me for help building
> this package, and I am more than happy to help you maintain this.
>
> Thanks,
> Jason
>
> On Wed, Dec 6, 2017 at 10:25 PM, Jason Guy <jason.e@gmail.com> wrote:
>
>> Hi Adam,
>>
>> Attached is a patch file with all the changes I made, which are
>> documented in the changelog. Please let me know if you have any questions.
>> I created a branch with the committed changes I made locally, and can
>> push that to the repo if that is easier.
>> I was not sure what the appropriate method was for contributing my
>> changes.
>>
>> Cheers,
>> Jason
>>
>>
>> On Wed, Dec 6, 2017 at 11:28 AM, Adam Majer <ad...@zombino.com> wrote:
>>
>>>
>>>
>>> On 12/06/2017 03:09 PM, Jason Guy wrote:
>>>
>>>> Hi Adam,
>>>>
>>>> I emailed you and didn't get any response, so I guessed you were really
>>>> busy. My apologies for misusing the term "orphaned", I am trying to learn
>>>> about packaging, and contributing to debian packages. Perhaps I
>>>> misunderstood the procedure, but I found no ITP for the new Kea package, so
>>>> I opened the ITP assuming nobody was working on it.
>>>>
>>>> Anyway, I just completed the build of the isc-kea 1.3.0 package. I made
>>>> a lot of improvements (I think) and tried to clean up some of the lintian
>>>> errors/warnings. I would be happy to create a pull request or whatever with
>>>> my changes. I have a few other minor tweaks to do, but I can provide the
>>>> updates I made as well. Please let me know how you would like me to 
>>>> proceed.
>>>>
>>>
>>>
>>> https://packages.qa.debian.org/i/isc-kea.html
>>>
>>> No problem. There is a Git repository for packaging. If you would like,
>>> you can marge your package changes in there and send me the patches in
>>> email.
>>>
>>> I've had my "dinner plate full" with non-Debian things for some time.
>>> But I will try to find some time to update my packages this week.
>>>
>>> Sorry for delay on this.
>>>
>>> - Adam
>>>
>>> PS. I have a patch already to update to 1.3.0, but if you send me yours
>>> I can merge them.
>>>
>>>
>>
>

Bug#883016: ITP: isc-kea -- New upstream version 1.3.0 released

[Jason Guy]

Hi Adam,

What is the status on getting the Kea 1.3 package done. Is it possible for
me to create a branch for the kea1.3 so users can at least build the
package themselves, and use it? People are unicasting me for help building
this package, and I am more than happy to help you maintain this.

Thanks,
Jason

On Wed, Dec 6, 2017 at 10:25 PM, Jason Guy <jason.e@gmail.com> wrote:

> Hi Adam,
>
> Attached is a patch file with all the changes I made, which are documented
> in the changelog. Please let me know if you have any questions.
> I created a branch with the committed changes I made locally, and can push
> that to the repo if that is easier.
> I was not sure what the appropriate method was for contributing my changes.
>
> Cheers,
> Jason
>
>
> On Wed, Dec 6, 2017 at 11:28 AM, Adam Majer <ad...@zombino.com> wrote:
>
>>
>>
>> On 12/06/2017 03:09 PM, Jason Guy wrote:
>>
>>> Hi Adam,
>>>
>>> I emailed you and didn't get any response, so I guessed you were really
>>> busy. My apologies for misusing the term "orphaned", I am trying to learn
>>> about packaging, and contributing to debian packages. Perhaps I
>>> misunderstood the procedure, but I found no ITP for the new Kea package, so
>>> I opened the ITP assuming nobody was working on it.
>>>
>>> Anyway, I just completed the build of the isc-kea 1.3.0 package. I made
>>> a lot of improvements (I think) and tried to clean up some of the lintian
>>> errors/warnings. I would be happy to create a pull request or whatever with
>>> my changes. I have a few other minor tweaks to do, but I can provide the
>>> updates I made as well. Please let me know how you would like me to proceed.
>>>
>>
>>
>> https://packages.qa.debian.org/i/isc-kea.html
>>
>> No problem. There is a Git repository for packaging. If you would like,
>> you can marge your package changes in there and send me the patches in
>> email.
>>
>> I've had my "dinner plate full" with non-Debian things for some time. But
>> I will try to find some time to update my packages this week.
>>
>> Sorry for delay on this.
>>
>> - Adam
>>
>> PS. I have a patch already to update to 1.3.0, but if you send me yours I
>> can merge them.
>>
>>
>

Bug#883016: ITP: isc-kea -- New upstream version 1.3.0 released

[Jason Guy]

Hi Adam,

Attached is a patch file with all the changes I made, which are documented
in the changelog. Please let me know if you have any questions.
I created a branch with the committed changes I made locally, and can push
that to the repo if that is easier.
I was not sure what the appropriate method was for contributing my changes.

Cheers,
Jason


On Wed, Dec 6, 2017 at 11:28 AM, Adam Majer <ad...@zombino.com> wrote:

>
>
> On 12/06/2017 03:09 PM, Jason Guy wrote:
>
>> Hi Adam,
>>
>> I emailed you and didn't get any response, so I guessed you were really
>> busy. My apologies for misusing the term "orphaned", I am trying to learn
>> about packaging, and contributing to debian packages. Perhaps I
>> misunderstood the procedure, but I found no ITP for the new Kea package, so
>> I opened the ITP assuming nobody was working on it.
>>
>> Anyway, I just completed the build of the isc-kea 1.3.0 package. I made a
>> lot of improvements (I think) and tried to clean up some of the lintian
>> errors/warnings. I would be happy to create a pull request or whatever with
>> my changes. I have a few other minor tweaks to do, but I can provide the
>> updates I made as well. Please let me know how you would like me to proceed.
>>
>
>
> https://packages.qa.debian.org/i/isc-kea.html
>
> No problem. There is a Git repository for packaging. If you would like,
> you can marge your package changes in there and send me the patches in
> email.
>
> I've had my "dinner plate full" with non-Debian things for some time. But
> I will try to find some time to update my packages this week.
>
> Sorry for delay on this.
>
> - Adam
>
> PS. I have a patch already to update to 1.3.0, but if you send me yours I
> can merge them.
>
>


kea-1.3.0.patch
Description: Binary data

Bug#883016: ITP: isc-kea -- New upstream version 1.3.0 released

[Jason Guy]

Hi Adam,

I emailed you and didn't get any response, so I guessed you were really
busy. My apologies for misusing the term "orphaned", I am trying to learn
about packaging, and contributing to debian packages. Perhaps I
misunderstood the procedure, but I found no ITP for the new Kea package, so
I opened the ITP assuming nobody was working on it.

Anyway, I just completed the build of the isc-kea 1.3.0 package. I made a
lot of improvements (I think) and tried to clean up some of the lintian
errors/warnings. I would be happy to create a pull request or whatever with
my changes. I have a few other minor tweaks to do, but I can provide the
updates I made as well. Please let me know how you would like me to
proceed.

Cheers,
Jason

On Wed, Dec 6, 2017 at 4:16 AM, Adam Majer <ad...@zombino.com> wrote:

> On 11/28/2017 08:39 PM, Jason Guy wrote:
>
>> This package has not had a lot of updates as the new versions come out.
>> The latest version brings a lot of improvements that would be great to make
>> available.
>>
>> I am not sure if the maintainer has orphaned it, but I would like to help
>> by updating the existing package for the latest upstream source.
>>
>>
> It's not orphaned. Orphaned packages have a bu filed against wnpp. Yes, I
> am rather busy with other things than Debian for a while. But an update
> version is pending thanks to patch by Baptiste Jonglez - I just need to
> upload it. Hopefully I will have time tonight (and not forget about it ;)
>
> - Adam
>
>

Bug#883016: ITP: isc-kea -- New upstream version 1.3.0 released

[Jason Guy]

Package: isc-kea
Version: 1.3.0-1
Severity: Wishlist
X-Debbugs-CC: debian-de...@lists.debian.org

This package has not had a lot of updates as the new versions come out. The
latest version brings a lot of improvements that would be great to make
available.

I am not sure if the maintainer has orphaned it, but I would like to help
by updating the existing package for the latest upstream source.

Bug#877181: libwxgtk3.0-0v5: wxExecute fails with non-ascii characters

[Guy Rutenberg]

Package: libwxgtk3.0-0v5
Version: 3.0.2+dfsg-4
Severity: normal
Tags: patch

Dear Maintainer,

wxWidgets has a known bug which prevents wxExecute for correctly handling
arguments with non-ascii characters. The bug was discussed and reported in
http://trac.wxwidgets.org/ticket/16206
Upstream fixed the issue in the development version (wxWidgets-3.1).

The bug affects all the programs relyig on wxExecute functionality, for example
`hugin` (see https://groups.google.com/forum/#!topic/hugin-ptx/FCi7ykPDZ5E).

The fix is a simple one-line patch
(https://github.com/wxWidgets/wxWidgets/commit/704055f200d97f327a8ee5212762b41bf1d6d503)
which works for the current version (3.0.3.1) as well.

Thanks,
Guy



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

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

Versions of packages libwxgtk3.0-0v5 depends on:
ii  libc6 2.24-11+deb9u1
ii  libcairo2 1.14.8-1
ii  libgcc1   1:6.3.0-18
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u1
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libglib2.0-0  2.50.3-2
ii  libgtk2.0-0   2.24.31-2
ii  libjpeg62-turbo   1:1.5.1-2
ii  libnotify40.7.7-2
ii  libpango-1.0-01.40.5-1
ii  libpangocairo-1.0-0   1.40.5-1
ii  libpng16-16   1.6.28-1
ii  libsm62:1.2.2-1+b3
ii  libstdc++66.3.0-18
ii  libtiff5  4.0.8-2+deb9u1
ii  libwxbase3.0-0v5  3.0.2+dfsg-4
ii  libx11-6  2:1.6.4-3
ii  libxxf86vm1   1:1.1.4-1+b2

libwxgtk3.0-0v5 recommends no packages.

libwxgtk3.0-0v5 suggests no packages.

-- no debconf information

Bug#866306:

[Guy Lunardi]

This issue still appears to exist against Linux 4.13.3.

Have not looked at haveged at all but noticed that passing "--data=16"
instead on relying on the fallback seems to allow haveged to start properly.

Tested with armbian on a LibreComputer Le Potato.

HTH (I might try to look into haveged if I have time but I doubt)

Bug#868209: Others dependencies problems

[Guy Marcenac]

hi,
It looks like it is not the only dependency error
samba-common-bin depends on libncurses5 (>=6), and the jessie version is 
5.9+20140913-1+b1

smbclient depends on libreadline7 (>=6) which I cannot find in jessie

Bug#705224: manpage: tcp section problems

[Guy Harris]

On Thu, 11 Apr 2013 09:53:21 +0200 Jorgen Grahn  
wrote:
> 
> 2. The annotated example printouts include things like:
> 
> > rtsg.1023 > csam.login: P 2:21(19) ack 1 win 4096
> > The notation is 'first:last(nbytes)' which means 'sequence numbers
> > first up to but not including last which is nbytes bytes of user data'.
> 
> This is indeed what tcpdump used to do -- it corresponds with what Stevens
> shows in "TCP/IP Illustrated".  But in the current tcpdump (and the one in 
> stable),
> the (nbytes) part is not present, and there is no obvious option to enable it.
> Not even -v makes a difference.
> 
> I must assume that nbytes, being last-first, was deemed superfluous at some 
> point
> and removed, without a corresponding update to the documentation.

The output format description was out of date in many places.  It has been 
updated in tcpdump commit e48f4ca6ca99cab11eba2dec7dcb4915fa5533dc.

Bug#705224: manpage: tcp section problems

[Guy Harris]

On Thu, 11 Apr 2013 09:53:21 +0200 Jorgen Grahn  
wrote:
> 1. The section starts with this disclaimer:
> 
> > (N.B.:The following description assumes familiarity with the TCP
> > protocol described in RFC-793.  If you are not familiar with the
> > protocol, neither this description nor tcpdump will be of much use to
> > you.)
> 
> The "nor tcpdump" part is obviously false -- most people I know use tcpdump
> to look at the link or IP layer, and know little about TCP.

I've changed it to "...this description will not be of much use to you." in 
tcpdump change 5f718c2742d458c305c6f3dc8cb8fe6a13ef5d63.

Bug#841161: /usr/sbin/tcpdump: tcpdump -d impossible as normal user

[Guy Harris]

On Tue, 18 Oct 2016 09:43:37 +0200 =?utf-8?q?Uwe_Kleine-K=C3=B6nig?= 
 wrote:

> I wonder why I need to be root (well, probably "only" need a net related
> capability) when generating a bpf filter:

Because

1) in order to generate a BPF filter, you need a link-layer header type;

2) when tcpdump was written, the -d option didn't take a "use this 
link-layer header type" argument to specify the link-layer header type, so it 
used the link-layer header type of whatever input source would have been used 
without -d;

3) that means opening the input source;

4) and opening a device for capturing on most platforms requires some 
form of privilege by default.

> So the obvious improvement is to not use a socket at all with -d which
> would allow to call this program with less capabilities.

...and would require a way to specify the link-layer read type, so the only way 
not to use a socket with -d, as it exists, is to use -r and read from a file.

If you don't want that, the only alternative is to add a new flag that works 
like -d but that takes a name for a link-layer header type as an argument, e.g.

tcpdump --dump-bpf-with-dlt EN10MB ip

("default to DLT_EN10MB" isn't the right answer - it provides no alternative 
for people who want a program for 802.11 or PPP or...).

Bug#851779: chromium: crashes at startup

[Guy Durrieu]

Package: chromium
Version: 55.0.2883.75-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since last recent release, chromium does not start anymore.

Wen typing the command in a shell, I get the following message:

---

chromium
/usr/bin/chromium: 122: /usr/bin/chromium: Syntax error: "fi" unexpected 
(expecting "}")---


--

but when having a look to the script, I do not understand why this 
syntax error appears.


Thanks in advance for your help !

Regards.

-- GD.


System Information:
Debian Release: 9.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 
'testing'), (500, 'stable')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 10:3.2.2-dmo3
ii  libavformat5710:3.2.2-dmo3
ii  libavutil55  10:3.2.2-dmo3
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libcups2 2.2.1-5
ii  libdbus-1-3  1.10.14-1
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libexpat12.2.0-2
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.3.0-2
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libicu57 57.1-5
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpng16-16  1.6.28-1
ii  libpulse09.0-5
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-2
ii  libvpx4  1.6.1-2
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libx11-6 2:1.6.4-2
ii  libx11-xcb1  2:1.6.4-2
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.8-2
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
ii  chromium-l10n  55.0.2883.75-4
pn  chromium-shell 
pn  chromium-widevine  

-- no debconf information

Bug#851360: linux: ACPI error messages on boot

[Guy Durrieu]

Package: src:linux
Version: 4.9.2-2
Severity: normal
File: linux

Dear Maintainer,


I installed this morning the 4.9.0-1 linux kernel, and at boot I got a 
lot of error messages related to ACPI (see below). These messages did 
not appear with the previous kernel version (4.8.0-2).


However, the system seems to work normally.

I hope this mail contains all required data (by the way, reportbug 
currently does not work in interactive mode, and I do not usually use 
the text version).


Thanks in advance for your help !

Best regards.

-- GD.

-- Package-specific info:

** Version:
Linux version 4.9.0-1-amd64 (debian-ker...@lists.debian.org) (gcc 
version 6.3.0 20161229 (Debian 6.3.0-2) ) #1 SMP Debian 4.9.2-2 (2017-01-12)


** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-1-amd64 
root=UUID=658b2e7d-23bf-4283-bf37-452cd31564cd ro 
init=/lib/systemd/systemd quiet


** Not tainted

** Kernel log:
[   10.320232] snd_hda_codec_realtek hdaudioC0D0:  Rear Mic=0x18
[   10.320233] snd_hda_codec_realtek hdaudioC0D0:  Line=0x1a
[   10.330182] input: HDA Intel PCH Front Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input8
[   10.330210] input: HDA Intel PCH Rear Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input9
[   10.330236] input: HDA Intel PCH Line as 
/devices/pci:00/:00:1b.0/sound/card0/input10
[   10.330261] input: HDA Intel PCH Line Out as 
/devices/pci:00/:00:1b.0/sound/card0/input11
[   10.330286] input: HDA Intel PCH Front Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input12

[   10.343561] input: PC Speaker as /devices/platform/pcspkr/input/input13
[   10.417769] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 
163840 ms ovfl timer

[   10.417771] RAPL PMU: hw unit of domain pp0-core 2^-16 Joules
[   10.417771] RAPL PMU: hw unit of domain package 2^-16 Joules
[   10.417772] RAPL PMU: hw unit of domain pp1-gpu 2^-16 Joules
[   10.539650] [drm] Memory usable by graphics device = 2048M
[   10.539653] checking generic (d000 30) vs hw (d000 1000)
[   10.539654] fb: switching to inteldrmfb from EFI VGA
[   10.539689] Console: switching to colour dummy device 80x25
[   10.539756] [drm] Replacing VGA console driver
[   10.546496] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   10.546496] [drm] Driver supports precise vblank timestamp query.
[   10.548857] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=none:owns=io+mem
[   10.553494] ACPI: Video Device [PEGP] (multi-head: no  rom: yes  
post: no)
[   10.553635] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:19/LNXVIDEO:00/input/input14
[   10.553968] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  
post: no)

[   10.554651] acpi device:45: registered as cooling_device7
[   10.554716] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input15
[   10.554737] [drm] Initialized i915 1.6.0 20160919 for :00:02.0 on 
minor 0

[   10.577615] fbcon: inteldrmfb (fb0) is primary device
[   10.654606] Console: switching to colour frame buffer device 160x64
[   10.675015] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[   10.826330] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[   10.826481] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)
[   10.827022] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20160831/nsarguments-95)

[   10.827360] pci :01:00.0: optimus capabilities: enabled, status
[   10.827365] VGA switcheroo: detected Optimus DSM method 
\_SB_.PCI0.PEG0.PEGP handle

[   10.827395] nouveau :01:00.0: enabling device (0100 -> 0103)
[   10.827576] nouveau :01:00.0: NVIDIA GF119 (0d91b0a1)
[   10.905915] nouveau :01:00.0: bios: version 75.19.76.00.1b
[   10.999059] nouveau :01:00.0: fb: 1024 MiB DDR3
[   11.057493] vga_switcheroo: enabled
[   11.057566] [TTM] Zone  kernel: Available graphics memory: 1959484 kiB
[   11.057568] [TTM] Initializing pool allocator
[   11.057572] [TTM] Initializing DMA pool allocator
[   11.057591] nouveau :01:00.0: DRM: VRAM: 1024 MiB
[   11.057592] nouveau :01:00.0: DRM: GART: 1048576 MiB
[   11.057595] nouveau :01:00.0: DRM: TMDS table version 2.0
[   11.057596] nouveau :01:00.0: DRM: DCB version 4.0
[   11.140479] nouveau :01:00.0: DRM: MM: using COPY0 for buffer copies
[   11.140486] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 
on minor 1

[   11.213297] iTCO_vendor_support: vendor-support=0
[   11.217152] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[   11.217198] iTCO_wdt: Found a Cougar Point TCO device (Version=2, 
TCOBASE=0x0460)

[   11.217316] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   11.351756] ACPI Error: Field [D128] at 1152 exceeds 

Bug#842184: policykit-1: synaptic-pkexec no more work

[Guy Rouger]

Package: policykit-1
Version: 0.105-16
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
launch Synaptic
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
using menu
   * What was the outcome of this action?
in command line
debian:~$ synaptic-pkexec
..
polkit-agent-helper-1: error response to PolicyKit daemon:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
 AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

This incident has been reported.

   * What outcome did you expect instead?
Display of authentification box
*** End of the template - remove these template lines ***



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

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

Versions of packages policykit-1 depends on:
ii  dbus   1.10.12-1
ii  libc6  2.24-5
ii  libglib2.0-0   2.50.1-1
ii  libpam-systemd 231-9
ii  libpam0g   1.1.8-3.3
ii  libpolkit-agent-1-00.105-16
ii  libpolkit-backend-1-0  0.105-16
ii  libpolkit-gobject-1-0  0.105-16

policykit-1 recommends no packages.

policykit-1 suggests no packages.

-- no debconf information

Bug#838085: apt: Jessie InRelease file don't exist on mirrors

[Guy Rouger]

Package: apt
Version: 1.3~rc4
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Run apt update
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
root@desktop:/home/guy# apt update
Atteint:1 http://security.debian.org jessie/updates InRelease
Atteint:3 http://security.debian.org stretch/updates InRelease
Atteint:5 http://repos.fds-team.de/stable/debian stretch InRelease
Atteint:6 http://repo.linrunner.de/debian jessie InRelease
Atteint:7 http://archive.canonical.com xenial InRelease
Ign:2 http://debian.bononia.it/debian jessie InRelease
Atteint:4 http://debian.bononia.it/debian jessie-updates InRelease
Atteint:8 http://debian.univ-lorraine.fr/debian stretch InRelease
Atteint:9 http://debian.bononia.it/debian jessie Release
Atteint:10 https://dl.winehq.org/wine-builds/debian stretch InRelease
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
All packages are up to date.

   * What outcome did you expect instead?
Not to have any errors
*** End of the template - remove these template lines ***



-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "i386";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "true";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-3\.16\.0-4-686-pae$";
APT::NeverAutoRemove:: "^linux-image-4\.6\.0-0\.bpo\.1-686-pae$";
APT::NeverAutoRemove:: "^linux-headers-3\.16\.0-4-686-pae$";
APT::NeverAutoRemove:: "^linux-headers-4\.6\.0-0\.bpo\.1-686-pae$";
APT::NeverAutoRemove:: "^linux-image-extra-3\.16\.0-4-686-pae$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.6\.0-0\.bpo\.1-686-pae$";
APT::NeverAutoRemove:: "^linux-signed-image-3\.16\.0-4-686-pae$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.6\.0-0\.bpo\.1-686-pae$";
APT::NeverAutoRemove:: "^kfreebsd-image-3\.16\.0-4-686-pae$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.6\.0-0\.bpo\.1-686-pae$";
APT::NeverAutoRemove:: "^kfreebsd-headers-3\.16\.0-4-686-pae$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.6\.0-0\.bpo\.1-686-pae$";
APT::NeverAutoRemove:: "^gnumach-image-3\.16\.0-4-686-pae$";
APT::NeverAutoRemove:: "^gnumach-image-4\.6\.0-0\.bpo\.1-686-pae$";
APT::NeverAutoRemove:: "^.*-modules-3\.16\.0-4-686-pae$";
APT::NeverAutoRemove:: "^.*-modules-4\.6\.0-0\.bpo\.1-686-pae$";
APT::NeverAutoRemove:: "^.*-kernel-3\.16\.0-4-686-pae$";
APT::NeverAutoRemove:: "^.*-kernel-4\.6\.0-0\.bpo\.1-686-pae$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.16\.0-4-686-pae$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.6\.0-0\.bpo\.1-686-pae$";
APT::NeverAutoRemove:: "^linux-tools-3\.16\.0-4-686-pae$";
APT::NeverAutoRemove:: "^linux-tools-4\.6\.0-0\.bpo\.1-686-pae$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs&qu

Bug#836511: vlc: screencapture failed on vlc 2.2.4

[Guy Rouger]

Package: src:vlc
Version: 2.2.4-3+b1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
use
VLC media player 2.2.4 Weatherwax (revision 2.2.3-37-g888b7e89)
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
impossible to get a sceencapture
   * What was the outcome of this action?
Error messages while using -vvv

7f8e4471dbd8] core filter debug: Filter 0x7f8e3ff8 removed from chain
[7f8e3ff8] core filter debug: removing module "swscale"
[7f8e17c8] core video output error: Failed to convert image for
snapshot

   * What outcome did you expect instead?
Get a picture in Images folder
*** End of the template - remove these template lines ***



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

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

Versions of packages vlc depends on:
ii  dpkg1.18.10
ii  fonts-freefont-ttf  20120503-4
ii  libaa1  1.4p5-44
ii  libc6   2.23-5
ii  libcaca00.99.beta19-2+b1
ii  libcairo2   1.14.6-1+b1
ii  libegl1-mesa [libegl1-x11]  11.2.2-1
ii  libfreerdp-client1.11.1.0~git20140921.1.440916e+dfsg1-10
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-10
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-10
ii  libfreetype62.6.3-3+b1
ii  libfribidi0 0.19.7-1
ii  libgcc1 1:6.1.1-11
ii  libgl1-mesa-glx [libgl1]11.2.2-1
ii  libgles1-mesa [libgles1]11.2.2-1
ii  libgles2-mesa [libgles2]11.2.2-1
ii  libglib2.0-02.48.1-3
ii  libpulse0   9.0-2
ii  libqt5core5a5.6.1+dfsg-3+b1
ii  libqt5gui5  5.6.1+dfsg-3+b1
ii  libqt5widgets5  5.6.1+dfsg-3+b1
ii  libqt5x11extras55.6.1-2
ii  librsvg2-2  2.40.16-1
ii  libsdl-image1.2 1.2.12-5+b7
ii  libsdl1.2debian 1.2.15+dfsg1-4
ii  libstdc++6  6.1.1-11
ii  libva-drm1  1.7.1-2
ii  libva-x11-1 1.7.1-2
ii  libva1  1.7.1-2
ii  libvlccore8 2.2.4-3+b1
ii  libvncclient1   0.9.10+dfsg-3+b1
ii  libx11-62:1.6.3-1
ii  libxcb-composite0   1.11.1-1.1
ii  libxcb-keysyms1 0.4.0-1
ii  libxcb-randr0   1.11.1-1.1
ii  libxcb-shm0 1.11.1-1.1
ii  libxcb-xv0  1.11.1-1.1
ii  libxcb1 1.11.1-1.1
ii  libxext62:1.3.3-1
ii  libxi6  2:1.7.6-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.11-1+b1
ii  vlc-nox 2.2.4-3+b1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages vlc recommends:
pn  vlc-plugin-notify  
pn  vlc-plugin-samba   
ii  xdg-utils  1.1.1-1

vlc suggests no packages.

Versions of packages vlc-nox depends on:
ii  dpkg   1.18.10
ii  liba52-0.7.4   0.7.4-18
ii  libasound2 1.1.2-1
ii  libass50.13.2-1
ii  libavahi-client3   0.6.32-1
ii  libavahi-common3   0.6.32-1
ii  libavc1394-0   0.5.4-4
ii  libbasicusageenvironment1  2016.08.07-1
ii  libbluray1 1:0.9.3-2
ii  libbz2-1.0 1.0.6-8
ii  libc6  2.23-5
ii  libcddb2   1.3.2-5
ii  libcdio13  0.83-4.2+b1
ii  libchromaprint01.3-1+b1
ii  libcrystalhd3  1:0.0~git20110715.fdd2f19-11+b1
ii  libdbus-1-31.10.10-1
ii  libdc1394-22   2.2.4-1
ii  libdca00.0.5-10
ii  libdirectfb-1.2-9  1.2.10.0-5.2+b1
ii  libdvbpsi101.3.0-4
ii  libdvdnav4 5.0.3-1
ii  libdvdread45.0.3-1
ii  libebml4v5 1.3.4-1
ii  libfaad2   2.8.0~cvs20150510-1
ii  libflac8   1.3.1-4
ii  libfontconfig1 2.11.94-0ubuntu1
ii  libfreetype6   2.6.3-3+b1
ii  libfribidi00.19.7-1
ii  libgcc11:6.1.1-11
ii  libgcrypt201.7.3-1
ii  libgme00.6.0-3
ii  libgnutls303.5.3-3
ii  libgpg-error0  1.24-1
ii  libgroupsock8  2016.08.07-1
ii  libgsm11.0.13-4
ii  libjpeg62-turbo1:1.5.0-1
ii  libkate1   0.4.1-7+b1
ii  liblircclient0 0.9.0~pre1-1.2
ii  liblivemedia52

Bug#833278: firefox-esr: lack of apparmor profile

[Guy Rouger]

Package: firefox-esr
Version: 45.2.0esr-1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Run Firefox-esr on Debian Stretch with Apparmor active
   * What exactly did you do (or not do) that was effective (or ineffective)?
Run Firefox-esr
   * What was the outcome of this action?
Firefox-esr is running without protection
   * What outcome did you expect instead?
Firefox-esr would run with apparmor protection
but there is no profile
root@debian:/etc/apparmor.d# ls
abstractions  usr.lib.dovecot.dovecot-lda
apache2.d usr.lib.dovecot.imap
bin.ping  usr.lib.dovecot.imap-login
cache usr.lib.dovecot.lmtp
disable   usr.lib.dovecot.log
force-complainusr.lib.dovecot.managesieve
gst_plugin_scannerusr.lib.dovecot.managesieve-login
local usr.lib.dovecot.pop3
sbin.klogdusr.lib.dovecot.pop3-login
sbin.syslogd  usr.lib.dovecot.ssl-params
sbin.syslog-ngusr.sbin.apt-cacher-ng
tunables  usr.sbin.avahi-daemon
usr.bin.chromium-browser  usr.sbin.cups-browsed
usr.bin.evinceusr.sbin.cupsd
usr.bin.icedove   usr.sbin.dnsmasq
usr.bin.irssi usr.sbin.dovecot
usr.bin.pidginusr.sbin.identd
usr.bin.totem usr.sbin.mdnsd
usr.bin.totem-previewers  usr.sbin.nmbd
usr.lib.dovecot.anvil usr.sbin.nscd
usr.lib.dovecot.auth  usr.sbin.smbd
usr.lib.dovecot.configusr.sbin.smbldap-useradd
usr.lib.dovecot.deliver   usr.sbin.tcpdump
usr.lib.dovecot.dict  usr.sbin.traceroute
usr.lib.dovecot.dovecot-auth



*** End of the template - remove these template lines ***



-- Package-specific info:

-- Extensions information
Name: Adguard AdBlocker
Location: ${PROFILE_EXTENSIONS}/adguardadbloc...@adguard.com.xpi
Status: enabled

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

Name: Firefox Hello Beta
Location: ${PROFILE_EXTENSIONS}/l...@mozilla.org.xpi
Status: enabled

Name: Français Language Pack locale
Location: 
/usr/lib/firefox-esr/browser/extensions/langpack...@firefox-esr.mozilla.org.xpi
Package: firefox-esr-l10n-fr
Status: enabled

Name: Zoom Page
Location: ${PROFILE_EXTENSIONS}/zoomp...@dw-dev.xpi
Status: enabled

-- Plugins information
Name: IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3))
Location: /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so
Package: icedtea-8-plugin:amd64
Status: enabled

Name: Shockwave Flash (22.0.0.192)
Location: /usr/lib/pipelight/libpipelight-flash.so
Status: enabled

Name: Silverlight Plug-In (5.1.30214.0)
Location: /usr/lib/pipelight/libpipelight-silverlight5.0.so
Status: enabled

Name: Widevine Media Optimizer (6.0.0.12442)
Location: /usr/lib/pipelight/libpipelight-widevine.so
Status: enabled


-- Addons package information
ii  firefox-esr45.2.0esr-1  amd64Mozilla Firefox web browser - Ext
ii  firefox-esr-l1 45.2.0esr-1  all  French language package for Firef
ii  icedtea-8-plug 1.6.2-3  amd64web browser plugin based on OpenJ

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

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

Versions of packages firefox-esr depends on:
ii  debianutils   4.8
ii  fontconfig2.11.0-6.4
ii  libasound21.1.1-2
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.23-4
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.8-1
ii  libdbus-glib-1-2  0.106-1
ii  libevent-2.0-52.0.21-stable-2+b1
ii  libffi6   3.2.1-4
ii  libfontconfig12.11.94-0ubuntu1
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.1.1-10
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.48.1-2
ii  libgtk2.0-0   2.24.30-4
ii  libhunspell-1.4-0 1.4.1-2
ii  libnspr4  2:4.12-2
ii  libnss3   2:3.23-2
ii  libpango-1.0-01.40.1-1
ii  libsqlite3-0  3.13.0-1
ii  libstartup-notification0  0.12-4
ii  libstdc++66.1.1-10
ii  libvpx3   1.5.0-3
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.2-1
ii  libxrender1   

Bug#833184: icedove: apparmor profile for icedove denied on local mail

[Guy Rouger]

Package: icedove
Version: 1:45.2.0-2
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
use of icedove with apparmor
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
impossible to read local mail
   * What was the outcome of this action?
error message in icedove, notification of apparmor
   * What outcome did you expect instead?
read local mail in icedove
*** End of the template - remove these template lines ***



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

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

Versions of packages icedove depends on:
ii  debianutils   4.8
ii  fontconfig2.11.0-6.4
ii  libasound21.1.1-2
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.23-4
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.8-1
ii  libdbus-glib-1-2  0.106-1
ii  libevent-2.0-52.0.21-stable-2+b1
ii  libffi6   3.2.1-4
ii  libfontconfig12.11.94-0ubuntu1
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.1.1-10
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.48.1-2
ii  libgtk2.0-0   2.24.30-4
ii  libhunspell-1.4-0 1.4.1-2
ii  libicu55  55.1-7
ii  libnspr4  2:4.12-2
ii  libnss3   2:3.23-2
ii  libpango-1.0-01.40.1-1
ii  libpangocairo-1.0-0   1.40.1-1
ii  libpangoft2-1.0-0 1.40.1-1
ii  libpixman-1-0 0.33.6-1
ii  libsqlite3-0  3.13.0-1
ii  libstartup-notification0  0.12-4
ii  libstdc++66.1.1-10
ii  libvpx3   1.5.0-3
ii  libx11-6  2:1.6.3-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.2-1
ii  libxrender1   1:0.9.9-2
ii  libxt61:1.1.5-1
ii  psmisc22.21-2.1+b1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages icedove recommends:
ii  hunspell-en-us [hunspell-dictionary] 20070829-6
ii  hunspell-fr-classical [hunspell-dictionary]  1:5.6-1
ii  iceowl-extension 1:45.2.0-2

Versions of packages icedove suggests:
ii  apparmor  2.10.95-4
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.14.2+dfsg-1

-- Configuration Files:
/etc/apparmor.d/usr.bin.icedove changed:
@{MOZ_LIBDIR}=/usr/lib/icedove
profile icedove /usr/lib/icedove/icedove {
  #include 
  #include 
  #include 
  # TODO: finetune this for required accesses
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  # for crash reports?
  ptrace (read,trace) peer=@{profile_name},
  # Pulseaudio
  /usr/bin/pulseaudio Pixr,
  owner @{HOME}/.{cache,config}/dconf/user rw,
  owner /run/user/[0-9]*/dconf/user rw,
  owner @{HOME}/.config/gtk-3.0/bookmarks r,
  deny owner @{HOME}/.local/share/gvfs-metadata/* r,
  # potentially extremely sensitive files
  audit deny @{HOME}/.gnupg/** mrwkl,
  audit deny @{HOME}/.ssh/** mrwkl,
  # rw access to HOME is useful when sending/receiving attachments
  owner @{HOME}/** rw,
  # Required for LVM setups
  /sys/devices/virtual/block/dm-[0-9]*/uevent r,
  # Addons (too lax for icedove)
  ##include 
  # for networking
  network inet stream,
  network inet6 stream,
  @{PROC}/[0-9]*/net/if_inet6 r,
  @{PROC}/[0-9]*/net/ipv6_route r,
  @{PROC}/[0-9]*/net/dev r,
  @{PROC}/[0-9]*/net/wireless r,
  # should maybe be in abstractions
  /etc/ r,
  /etc/mime.types r,
  /etc/mailcap r,
  /etc/xdg/*buntu/applications/defaults.listr, # for all derivatives
  /etc/xfce4/defaults.list r,
  /usr/share/xubuntu/applications/defaults.list r,
  owner @{HOME}/.local/share/applications/defaults.list r,
  owner @{HOME}/.local/share/applications/mimeapps.list r,
  owner @{HOME}/.local/share/applications/mimeinfo.cache r,
  owner /tmp/** m,
  owner /var/tmp/** m,
  /tmp/.X[0-9]*-lock r,
  /etc/udev/udev.conf r,
  # Doesn't seem to be required, but noisy. Maybe allow 'r' for 'b*' if needed.
  # Possibly move to an abstraction if anything else needs it.
  deny /run/udev/data/** r,
  /etc/timezone r,
  /etc/wildmidi/wildmidi.cfg r,
  # icedove specific
  /etc/icedove/ r,
  /etc/icedove/** r,
  /etc/xul-ext/** r,
  /etc/xulrunner-2.0*/ r,
  /etc/xulrunner-2.0*/** r,
  /etc/gre.d/ r,
  /etc/gre.d/* r,
  # noisy
  deny @{MOZ_LIBDIR}/** w,
  deny /usr/lib/icedove-addons/** w,
  deny 

Bug#823365: Ahh ... Probably already fixed upstream

[Guy Heatley]

On 21/05/2016 22:31, Reiner Herrmann wrote:
> Hi Guy,

> 
> Did you already have the possibility to check if firejail works again
> without the workaround?
> 
> Kind regards,
>   Reiner
> 

Hi Reiner,
Apologies for my tardy response!
Yes - it worked without requiring to apply the workaround, once the new
SE Linux version was installed.

Cheers,
-- 
Guy



signature.asc
Description: OpenPGP digital signature

Bug#825152: emacs24: icons in tool bar are missing

[Guy Durrieu]

Package: emacs24
Version: 24.5+1-6+b2
Followup-For: Bug #824667

Dear Norbert, dear Maintainer,

I experience the same problem regarding toolbar icons. I also tested 
removing .emacs.el, without any effect.


Regards.

-- GD.

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

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

Versions of packages emacs24 depends on:
ii  emacs24-bin-common 24.5+1-6+b2
ii  gconf-service  3.2.6-3
ii  libacl12.2.52-3
ii  libasound2 1.1.0-1
ii  libatk1.0-02.20.0-1
ii  libc6  2.22-9
ii  libcairo-gobject2  1.14.6-1+b1
ii  libcairo2  1.14.6-1+b1
ii  libdbus-1-31.10.8-1
ii  libfontconfig1 2.11.0-6.4
ii  libfreetype6   2.6.3-3+b1
ii  libgconf-2-4   3.2.6-3
ii  libgdk-pixbuf2.0-0 2.34.0-1
ii  libgif75.1.4-0.2
ii  libglib2.0-0   2.48.1-1
ii  libgnutls303.4.12-1
ii  libgomp1   6.1.1-4
ii  libgpm21.20.4-6.2
ii  libgtk-3-0 3.20.5-2
ii  libice62:1.0.9-1+b1
ii  libjpeg62-turbo1:1.4.2-2
ii  libm17n-0  1.7.0-3+b1
ii  libmagickcore-6.q16-2  8:6.8.9.9-7+b2
ii  libmagickwand-6.q16-2  8:6.8.9.9-7+b2
ii  libotf00.9.13-3
ii  libpango-1.0-0 1.40.1-1
ii  libpangocairo-1.0-01.40.1-1
ii  libpng16-161.6.21-5
ii  librsvg2-2 2.40.15-1
ii  libselinux12.5-3
ii  libsm6 2:1.2.2-1+b1
ii  libtiff5   4.0.6-1
ii  libtinfo5  6.0+20160319-1
ii  libx11-6   2:1.6.3-1
ii  libxft22.3.2-1
ii  libxinerama1   2:1.1.3-1+b1
ii  libxml22.9.3+dfsg1-1
ii  libxpm41:3.5.11-1+b1
ii  libxrandr2 2:1.5.0-1
ii  libxrender11:0.9.9-2
ii  zlib1g 1:1.2.8.dfsg-2+b1

emacs24 recommends no packages.

Versions of packages emacs24 suggests:
pn  emacs24-common-non-dfsg  

-- no debconf information

Bug#633825: synaptic: origin view incorrectly handles packages with multiple versions

[Guy Rouger]

On Thu, 14 Jul 2011 12:18:42 +0800 Daniel Hartwig  wrote:
> > $ apt-cache policy
> > [...]
> >  origin ftp.iinet.net.au
> > Pinned packages:
> > $ apt-cache policy iceweasel
>
> sources.list changed from ftp.iinet.net.au to ftp.au.debian.org
> between invocation of the two apt-cache lines; this does not effect
> the reported bug.
>
>
>

Hello
Any progress to fix this bug?
Very annoying.
Example

root@debian:/# apt-cache policy adduser
adduser:
  Installé : 3.114
  Candidat : 3.114
 Table de version :
 *** 3.114 500
500 http://httpredir.debian.org/debian stretch/main amd64 Packages
500 http://httpredir.debian.org/debian stretch/main i386 Packages
100 /var/lib/dpkg/status

Synaptic display 4 iterations of adduser packages

​

Bug#823365: Ahh ... Probably already fixed upstream

[Guy Heatley]

On 04/05/2016 18:28, Reiner Herrmann wrote:

>> https://github.com/netblue30/firejail/issues/494

> I also assume that you ran into this libselinux1 regression.
> Can you please recheck with libselinux1 2.5-1 (when it lands in testing)
> and tell me if it solved your problem?
> 
> Kind regards,
>   Reiner
> 


Hi Reiner,
I certainly will.

BTW, the workaround detailed on the github site seems to work, namely
adding this switch to the commandline:

--seccomp.drop=umount2,ptrace,kexec_load,kexec_file_load,open_by_handle_at,init_module,finit_module,delete_module,iopl,ioperm,swapon,swapoff,syslog,process_vm_readv,process_vm_writev,sysfs,_sysctl,adjtimex,clock_adjtime,lookup_dcookie,perf_event_open,fanotify_init,kcmp,add_key,request_key,keyctl,uselib,acct,modify_ldt,pivot_root,io_setup,io_destroy,io_getevents,io_submit,io_cancel,remap_file_pages,mbind,get_mempolicy,set_mempolicy,migrate_pages,move_pages,vmsplice,chroot,tuxcall,reboot,nfsservctl,get_kernel_syms


Cheers,
-- 
Guy



signature.asc
Description: OpenPGP digital signature

Bug#823365: Ahh ... Probably already fixed upstream

[Guy Heatley]

https://github.com/netblue30/firejail/issues/494
"A recent libselinux1 update (2.5-1) introduces a bug where it attempts
to re-mount /proc directory."

This issue is closed on the Github site so hopefully will shortly filter
down into testing.
-- 
Guy



signature.asc
Description: OpenPGP digital signature

Bug#823365: firejail no longer allows some programs to run

[Guy Heatley]

Subject: firejail no longer allows some programs to run
Package: firejail
Version: 0.9.38-1
Severity: important

Dear Maintainer,

Firejail no longer allows certain programs to run in the sandbox e.g.
iceweasel (and other programs based on firefox e.g. tor browser,
icedove), and java programs. It simply exits without starting the
program (parent is shutting down) or hangs in the case of java.

The Chromium browser seems to start normally, though.

I have classed this as "important" as many of the programs I would
normally use firejail with, no longer run!

This started very recently - firejail used to work as expected.

Thanks for any advice!

Guy

$ firejail --debug iceweasel



Save seccomp filter, size 744 bytes
Dropping all capabilities
noroot user namespace installed
Starting "iceweasel"
execvp argument 0: /bin/bash
execvp argument 1: -c
execvp argument 2: "iceweasel"
Child process initialized
Sandbox monitor: waitpid 2 retval 2 status 31

parent is shutting down, bye...

< exits >


$ firejail --debug --profile=/etc/firejail/firefox.profile java -jar
JDownloader.jar



Save seccomp filter, size 744 bytes
Dropping all capabilities
noroot user namespace installed
Starting "java" "-jar" "JDownloader.jar"
execvp argument 0: /bin/bash
execvp argument 1: -c
execvp argument 2: "java" "-jar" "JDownloader.jar"
Child process initialized
JarHandlerWorkaroundOracle:setURLStreamHandlerFactory
JarHandlerWorkaroundOracle:replaceLauncherFactory
JarHandlerWorkaroundOracle:replaceURLClassPath
JarHandlerWorkaroundOracle:replacejarHandler
JarHandlerWorkaroundOracle:replaceLoaders:1
JarHandlerWorkaroundOracle:replaceLoader:0:handler
JarHandlerWorkaroundOracle:replaceLoader:0:handler:jar:file:/home/user1/bin/jd2/JDownloader.jar!/

< hangs until ctrl-c is pressed >

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

Kernel: Linux 4.5.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages firejail depends on:
ii  libc6  2.22-7

firejail recommends no packages.

firejail suggests no packages.

-- no debconf information

Bug#817059: vagrant: domain_name gem not found

[Guy Hughes]

Package: vagrant
Version: 1.8.1+dfsg-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

Until #817011 on ruby-domain-name is fixed by the maintainer, vagrant
does not work without a manual fix (gemspec file) available in the bts
report.[1] See below.

I'm reporting this against your package for the benefit of others,
especially those using virtualbox from sid.

Guy Hughes

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817011

$ vagrant
Vagrant experienced a version conflict with some installed plugins!
This usually happens if you recently upgraded Vagrant. As part of the
upgrade process, some existing plugins are no longer compatible with
this version of Vagrant. The recommended way to fix this is to remove
your existing plugins and reinstall them one-by-one. To remove all
plugins:

rm -r ~/.vagrant.d/plugins.json ~/.vagrant.d/gems

Note if you have an alternate VAGRANT_HOME environmental variable
set, the folders above will be in that directory rather than your
user's home directory.

The error message is shown below:

Bundler could not find compatible versions for gem "domain_name":
  In Gemfile:
vagrant (= 1.8.1) was resolved to 1.8.1, which depends on
  rest-client (< 2.0, >= 1.6.0) was resolved to 1.8.0, which depends on
http-cookie (< 2.0, >= 1.0.2) was resolved to 1.0.2, which depends on
  domain_name (~> 0.5)

Could not find gem 'domain_name (~> 0.5)', which is required by gem 
'http-cookie (< 2.0, >= 1.0.2)', in any of the sources.
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJW3bWUAAoJEP5VHtX/6ko8rYIP/1IsuCxSQUi5ifmyxaxxhN3j
Hk+fa73j/nAWXPI/in4lky+heiWwbstvgvoir5zK9fftQAv58q6h/d1ExIvsqHei
ZfNdVJKFE0DYSCxjJYS6a33xof7/WhuhoE33kThuvbuinwnMOh4i5XN+x3Pr9KPx
mD7zBUDhbiEsbLYFguo1rpz6b05bkJD+NLbhgVSQ0z1G54AQPze9ZUfAqRmtgkWW
wU6p67zDWSn0E1NyRUPDOo8al7bXaqZ++D6B70Psk+7yxxaZF3HzqjSZUDRcgjMK
8f+4e4lQHccFJSAvdz0RRXMWUm+egVDpRSex71he4Z14g6MDoPUsodU3gvI4ns5M
sLrL2+q8r/UeDaVNEsJSQY1Igot+jQt0e8P1gsOxbaCM//SoW+1dqa9Hfza9HfQX
2D4TAXAamdxWvzBdViKCp4+8Dj4MfFBMrtyT3vWaJ/C80X5GyEQDNb9TEL2Owvvv
zxbG4i4D/bqLMFrEBB59q4u3V9XCFjh069fIMHVkgU60Lu3kVIZFQyhNUVlRtmfL
SOHoJfp1OQJEBH+ZPY/wx06BgR0xDKmz2cSf2C8heHkMberBrOvKrawHhIa4gqB+
iBhPAoMMzpaUThZkBMPAD8XvdhkkA1mxnB5zNbVLT+O/tBk7xF5YqlV5QYqLJBsj
PO0cwls0qMxPJftBuOr1
=7KLp
-END PGP SIGNATURE-

Bug#815917: phpmyadmin crashes silently

[Guy Durrieu]

Le 25/02/2016 20:21, Guy Durrieu a écrit :


OK, I should have a look to that:

error.log:[Thu Feb 25 17:39:42.283655 2016] [:error] [pid 16091] 
[client ::1:55330] PHP Fatal error:  require_once(): Failed opening 
required './libraries/php-gettext/gettext.inc' (include_path='.') in 
/usr/share/phpmyadmin/libraries/sql-parser/autoload.php on line 70, 
referer: http://localhost/phpmyadmin/import.php




In my config the required file is located here: 
/usr/share/php/php-gettext/gettext.inc


-- Regards.

-- GD.

Bug#815917: phpmyadmin crashes silently

[Guy Durrieu]

Le 25/02/2016 19:09, Michal Čihař a écrit :

Hi

Dne 25.2.2016 v 18:29 Guy Durrieu napsal(a):

Package: phpmyadmin
Version: 4:4.5.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I again got a problem with phpmyadmin...

After today last upgrade(from 4:4.5.4.1-2 to 4:4.5.5-1), phpmyadmin
silently crashes after login. I get a blank screen with iceweasel, and a
server error 500 with chromium, wjth the following details (sorry, in
french):
---
Le site Web a rencontré une erreur lors de l'extraction de*
http://localhost/phpmyadmin/index.php?target=import.php=0ef11afdf0092fafdb39d194dbf8baf0*.

Cela peut être dû à une opération de maintenance ou à une configuration
incorrecte.
---

However, no error messages were displayed, neither during upgrade nor in
log files:

Is there something in the Apache error logs?



OK, I should have a look to that:

error.log:[Thu Feb 25 17:39:42.283655 2016] [:error] [pid 16091] [client 
::1:55330] PHP Fatal error:  require_once(): Failed opening required 
'./libraries/php-gettext/gettext.inc' (include_path='.') in 
/usr/share/phpmyadmin/libraries/sql-parser/autoload.php on line 70, 
referer: http://localhost/phpmyadmin/import.php


Regards.

-- GD.

Bug#815917: phpmyadmin crashes silently

[Guy Durrieu]

Package: phpmyadmin
Version: 4:4.5.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I again got a problem with phpmyadmin...

After today last upgrade(from 4:4.5.4.1-2 to 4:4.5.5-1), phpmyadmin 
silently crashes after login. I get a blank screen with iceweasel, and a 
server error 500 with chromium, wjth the following details (sorry, in 
french):


---
Le site Web a rencontré une erreur lors de l'extraction de*
http://localhost/phpmyadmin/index.php?target=import.php=0ef11afdf0092fafdb39d194dbf8baf0*. 

Cela peut être dû à une opération de maintenance ou à une configuration 
incorrecte.

---

However, no error messages were displayed, neither during upgrade nor in 
log files:


---
apt/term.log:Dépaquetage de phpmyadmin (4:4.5.5-1) sur (4:4.5.4.1-2) ...
apt/term.log:Paramétrage de phpmyadmin (4:4.5.5-1) ...
apt/term.log:dbconfig-common: writing config to 
/etc/dbconfig-common/phpmyadmin.conf
apt/term.log:Replacing config file /etc/dbconfig-common/phpmyadmin.conf 
with new version
apt/term.log:Replacing config file /etc/phpmyadmin/config-db.php with 
new version

apt/term.log:apache2_invoke phpmyadmin: already enabled
---

Regards.

-- GD.

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

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

Versions of packages phpmyadmin depends on:
ii  dbconfig-common2.0.3
ii  dbconfig-mysql 2.0.3
ii  debconf [debconf-2.0]  1.5.58
ii  libapache2-mod-php55.6.18+dfsg-1
ii  libjs-sphinxdoc1.3.5-1
ii  perl   5.22.1-7
ii  php-gettext1.0.11-2
ii  php-phpseclib  2.0.1-1
ii  php5   5.6.18+dfsg-1
ii  php5-common5.6.18+dfsg-1
ii  php5-json  1.3.7-1
ii  php5-mysql 5.6.18+dfsg-1
ii  ucf3.0035

Versions of packages phpmyadmin recommends:
ii  apache2 [httpd]  2.4.18-1
ii  mysql-client 5.6.28-1
ii  mysql-client-5.6 [virtual-mysql-client]  5.6.28-1
ii  php-tcpdf6.0.093+dfsg-1
ii  php5-gd  5.6.18+dfsg-1

Versions of packages phpmyadmin suggests:
ii  chromium [www-browser]   48.0.2564.116-1
ii  iceweasel [www-browser] 46.0~a2+20160217064514-1
ii  mysql-server 5.6.28-1
ii  mysql-server-5.6 [virtual-mysql-server]  5.6.28-1
ii  w3m [www-browser]0.5.3-26

-- debconf information:
  phpmyadmin/install-error: ignore
  phpmyadmin/mysql/method: Unix socket
  phpmyadmin/upgrade-error: abort
  phpmyadmin/remove-error: abort
  phpmyadmin/dbconfig-reinstall: false
  phpmyadmin/upgrade-backup: true
  phpmyadmin/remote/host: localhost
  phpmyadmin/db/dbname: phpmyadmin
* phpmyadmin/mysql/admin-user: debian-sys-maint
  phpmyadmin/database-type: mysql
* phpmyadmin/dbconfig-upgrade: true
* phpmyadmin/reconfigure-webserver: apache2
  phpmyadmin/internal/reconfiguring: false
  phpmyadmin/passwords-do-not-match:
  phpmyadmin/setup-username: admin
  phpmyadmin/remote/port:
  phpmyadmin/internal/skip-preseed: false
* phpmyadmin/dbconfig-install: true
  phpmyadmin/dbconfig-remove: true
  phpmyadmin/purge: false
  phpmyadmin/db/app-user: root
  phpmyadmin/remote/newhost:
  phpmyadmin/missing-db-package-error: abort

Bug#815125: Boot failure with Debian linux 4.4.2 package

[Guy Durrieu]

Le 21/02/2016 04:45, Ben Hutchings a écrit :

 Hi Ben !

This test version is now available at
https://people.debian.org/~benh/packages/unstable/

Please report back whether this does or doesn't fix the problem for
you.

Ben.



It works for me.

Thanks !

Regards.

-- GD.

Bug#815125: Boot failure with Debian linux 4.4.2 package

[Guy Durrieu]

Le 20/02/2016 18:43, Ben Hutchings a écrit :

Hi Ben. Thanks for your answer !

I apologise for this regression, which of course didn't affect any of
the several machines I was able to test on.

Please can you each reply to the bug address with the following
details:

- Does the affected system boot using the BIOS boot protocol
   (including CSM) or UEFI boot protocol?

My system boots using the UEFI boot protocol.

- If you boot with the added kernel parameter "earlyprintk=vga" or
   "earlyprintk=serial" (and without "quiet"), do any boot messages
   appear before the hang/reboot?  PLease send them (a photo is fine).

No boot message at all. Same result as previously.

- If it boots with UEFI, does the kernel parameter "efi=noruntime"
   work around the problem?

Yes, it does. The system boots normally.

- If you haven't already reported this, does the Linux 4.5-rc4 package
   from experimental have the same problem?

Hangs same way. But also starts normally using "efi=noruntime".

Ben.

Regards.

-- GD.

Bug#815126: linux-image-4.4.0-1-amd64 hangs after 'Loading initial ramdisk ...'

[Guy Durrieu]

Package: src:linux
Version: 4.4.2-2
Followup-For: Bug #815126

Dear Jim, dear Maintainer,

I get exactly the same problem on my computer.

As additional information, a new update of linux-image-4.4.0-1-amd64 
came later, but the problem still remains.


Regards.

-- GD.

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Hewlett-Packard
product_name: 110-114ef
product_version: 1.00
chassis_vendor: Hewlett-Packard
chassis_version:
bios_vendor: AMI
bios_version: 80.20
board_vendor: Hewlett-Packard
board_name: 2AFB
board_version: 1.02

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor DRAM Controller [8086:0150] (rev 09)
Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core 
processor DRAM Controller [103c:2afb]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
SERR- 
Latency: 0
Capabilities: 
Kernel driver in use: ivb_uncore
Kernel modules: ie31200_edac

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor PCI Express Root Port [8086:0151] (rev 09) (prog-if 00 
[Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR+ 
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 24
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: e000-efff
Memory behind bridge: f600-f70f
Prefetchable memory behind bridge: e000-e9ff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- 

BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 
v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) 
(prog-if 00 [VGA controller])

DeviceName:  Onboard IGD
Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [103c:2afb]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
SERR- 
Latency: 0
Interrupt: pin A routed to IRQ 29
Region 0: Memory at f740 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at d000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at f000 [size=64]
Expansion ROM at  [disabled]
Capabilities: 
Kernel driver in use: i915
Kernel modules: i915

00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 
Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset 
Family MEI Controller [103c:2afb]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
Latency: 0
Interrupt: pin A routed to IRQ 27
Region 0: Memory at f790a000 (64-bit, non-prefetchable) [size=16]
Capabilities: 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series 
Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05) 
(prog-if 20 [EHCI])
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset 
Family USB Enhanced Host Controller [103c:2afb]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at f7908000 (32-bit, non-prefetchable) [size=1K]
Capabilities: 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series 
Chipset Family High Definition Audio Controller [8086:1c20] (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset 
Family High Definition Audio Controller [103c:2afb]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 28
Region 0: Memory at f790 (64-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5) 

Bug#813190: phpmyadmin: Error encounterd while configuring phpmyadmin with, dbconfig-common

[Guy Durrieu]

Le 08/02/2016 22:39, Guy Durrieu a écrit :
>

Hi Michal,


I just upgraded to 4:4.5.4.1-2. All works fine now.

Thanks for your help !

Regards.

-- GD.

Bug#813190: phpmyadmin: Error encounterd while configuring phpmyadmin with, dbconfig-common

[Guy Durrieu]

Le 08/02/2016 17:46, Michal Čihař a écrit :

Hi

Dne 30.1.2016 v 18:49 Guy Durrieu napsal(a):

I never did anything manually on the phpadmin database.

Probably I prevously had installed the 4:4.5.0.2-1 version; all worked
fine until the last upgrade (4:4.5.4-1 yesterday); now debian only
proposes 4.4.2.12-2+deb8u1 as possible alternative.

Okay, it seems that phpmyadmin can do auto upgrade of the tables when
accessed with enough privileges. This seems to collide with dbconfig
upgrade we're using. I need to figure out best approach to handle this.

To workaround this for now, you can execute following query:

ALTER TABLE `pma__column_info`
   DROP `input_transformation`,
   DROP `input_transformation_options`;

And the upgrade should work.




Hi Michal,

Thanks for your help.

I tried the workaround you suggest.

After removing the above columns, the upgrade seems correctly done (no 
error displayed):


---
aptitude safe-upgrade
Résolution des dépendances…
Les paquets suivants seront mis à jour :
  phpmyadmin
1 paquets mis à jour, 0 nouvellement installés, 0 à enlever et 7 non mis 
à jour.
Il est nécessaire de télécharger 0 o/4 018 ko d'archives. Après 
dépaquetage, 563 ko seront utilisés.

Voulez-vous continuer ? [Y/n/?]
Lecture des fichiers de modifications (« changelog »)... Terminé
Préconfiguration des paquets...
(Lecture de la base de données... 364760 fichiers et répertoires déjà 
installés.)

Préparation du dépaquetage de .../phpmyadmin_4%3a4.5.4-1_all.deb ...
Dépaquetage de phpmyadmin (4:4.5.4-1) sur (4:4.2.12-2+deb8u1) ...
Traitement des actions différées (« triggers ») pour hicolor-icon-theme 
(0.13-1) ...

Traitement des actions différées (« triggers ») pour man-db (2.7.5-1) ...
Paramétrage de phpmyadmin (4:4.5.4-1) ...
Installation de la nouvelle version du fichier de configuration 
/etc/phpmyadmin/apache.conf ...
Installation de la nouvelle version du fichier de configuration 
/etc/phpmyadmin/config.inc.php ...

dbconfig-common: writing config to /etc/dbconfig-common/phpmyadmin.conf
creating database backup in 
/var/cache/dbconfig-common/backups/phpmyadmin_4:4.2.12-2+deb8u1.2016-02-08-22.29.21.

applying upgrade sql for 4:4.2.12-2+deb8u1 -> 4:4.5.0.2-1.
dbconfig-common: flushing administrative password
apache2_invoke phpmyadmin: already enabled
---

(in french again, sorry).

However, phpmyadmin still doesn't work (empty screen with iceweasel, 
error 500 displayed with chromium).


-- GD.