Bug#1068845: fwbuilder: fwbuilder crashes when trying to create almost any type of new object

[Sudip Mukherjee]

Package: fwbuilder
Version: 5.3.7-5+b2
Severity: normal
Tags: patch

Dear Maintainer,

fwbuilder crashes when trying to create almost any type of new object

To reproduce:
* start fwbuilder without any arguments
* click "New Object"
* click "New Library"
* fwbuilder will crash

The attached debdiff with upstream commit will fix the problem.

--
Regards
Sudip

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

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

Versions of packages fwbuilder depends on:
ii  fwbuilder-common5.3.7-5
ii  libc6   2.37-15
ii  libgcc-s1   14-20240201-3
ii  libqt5core5t64  5.15.10+dfsg-7.2+b1
ii  libqt5gui5t64   5.15.10+dfsg-7.2+b1
ii  libqt5network5t64   5.15.10+dfsg-7.2+b1
ii  libqt5printsupport5t64  5.15.10+dfsg-7.2+b1
ii  libqt5widgets5t64   5.15.10+dfsg-7.2+b1
ii  libsnmp40t645.9.4+dfsg-1.1+b1
ii  libstdc++6  14-20240201-3
ii  libxml2 2.9.14+dfsg-1.3+b2
ii  libxslt1.1  1.1.35-1
ii  zlib1g  1:1.3.dfsg-3+b1

Versions of packages fwbuilder recommends:
ii  fwbuilder-doc  5.3.7-5
ii  rcs5.10.1-1

fwbuilder suggests no packages.

-- no debconf information
diff -Nru fwbuilder-5.3.7/debian/changelog fwbuilder-5.3.7/debian/changelog
--- fwbuilder-5.3.7/debian/changelog2022-01-23 23:01:26.0 +
+++ fwbuilder-5.3.7/debian/changelog2024-04-11 23:04:28.0 +0100
@@ -1,3 +1,10 @@
+fwbuilder (5.3.7-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream commit to fix crash creating new object.
+
+ -- Sudip Mukherjee   Thu, 11 Apr 2024 23:04:28 
+0100
+
 fwbuilder (5.3.7-5) unstable; urgency=medium
 
   [ Lukas Mardian ]
diff -Nru 
fwbuilder-5.3.7/debian/patches/0001-adding-fix-for-crash-if-you-create-some-new-objects-.patch
 
fwbuilder-5.3.7/debian/patches/0001-adding-fix-for-crash-if-you-create-some-new-objects-.patch
--- 
fwbuilder-5.3.7/debian/patches/0001-adding-fix-for-crash-if-you-create-some-new-objects-.patch
  1970-01-01 01:00:00.0 +0100
+++ 
fwbuilder-5.3.7/debian/patches/0001-adding-fix-for-crash-if-you-create-some-new-objects-.patch
  2024-04-11 23:04:28.0 +0100
@@ -0,0 +1,38 @@
+From 102d68c3917950c688c1a3ca9bee42c3ff24b57f Mon Sep 17 00:00:00 2001
+From: bluelineXY 
+Date: Thu, 22 Feb 2018 21:43:53 +0100
+Subject: [PATCH] adding fix for crash if you create some new objects type out
+ of the menu (e.g. ip addess)
+
+Origin: upstream, 
https://github.com/fwbuilder/fwbuilder/commit/102d68c3917950c688c1a3ca9bee42c3ff24b57f
+Last-Update: 2024-04-11
+---
+ src/libgui/ObjectManipulator_tree_ops.cpp | 12 
+ 1 file changed, 8 insertions(+), 4 deletions(-)
+
+diff --git a/src/libgui/ObjectManipulator_tree_ops.cpp 
b/src/libgui/ObjectManipulator_tree_ops.cpp
+index ec80537d5..b3327f375 100644
+--- a/src/libgui/ObjectManipulator_tree_ops.cpp
 b/src/libgui/ObjectManipulator_tree_ops.cpp
+@@ -774,10 +774,14 @@ void ObjectManipulator::moveItems(ObjectTreeViewItem 
*dest,
+   const list )
+ {
+ string folder;
+-if (dest->getUserFolderParent() != 0) {
+-folder = dest->getUserFolderName().toUtf8().constData();
+-} else {
+-folder = dest->getFWObject()->getStr("folder");
++
++if(dest != NULL)
++{
++if (dest->getUserFolderParent() != 0) {
++folder = dest->getUserFolderName().toUtf8().constData();
++} else {
++folder = dest->getFWObject()->getStr("folder");
++}
+ }
+ 
+ FWCmdMacro *macro = new FWCmdMacro(tr("Move objects"));
+-- 
+2.39.2
+
diff -Nru fwbuilder-5.3.7/debian/patches/series 
fwbuilder-5.3.7/debian/patches/series
--- fwbuilder-5.3.7/debian/patches/series   2022-01-20 13:09:55.0 
+
+++ fwbuilder-5.3.7/debian/patches/series   2024-04-11 23:04:10.0 
+0100
@@ -6,3 +6,4 @@
 pkg-config_libxml2.patch
 pkg-config_libxslt.patch
 ed4db20ec6cabfaea9c36187b7ce40d9d93c6c79.patch
+0001-adding-fix-for-crash-if-you-create-some-new-objects-.patch
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug#1049952: csh: maintained by ubuntu-devel-discuss@lists.ubuntu.com

[Steven Robbins]

On Thu, 17 Aug 2023 11:34:56 +0200 Lucas Nussbaum  wrote:
> Source: csh
> Version: 20110502-7
> Severity: serious

Is this really a serious enough issue to warrant removal from Debian?

> 
> Hi,
> 
> this package is maintained by ubuntu-devel-discuss@lists.ubuntu.com,
> which is not a suitable contact point for Debian packages maintenance
> according to https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
> 
> This is most likely due to generating the source package on an Ubuntu
> machine. I think there's some magic that replaces the Maintainer field
> in the Ubuntu tooling.
> 
> 


signature.asc
Description: This is a digitally signed message part.
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug#1044860: csh: Fails to build source after successful build

[Lucas Nussbaum]

Source: csh
Version: 20110502-7
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -S
> 
> 
> dpkg-buildpackage: info: source package csh
> dpkg-buildpackage: info: source version 20110502-7
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Alastair McKinstry 
> 
>  dpkg-source --before-build .
>  fakeroot debian/rules clean
> dh clean --buildsystem=bmake
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> dh_auto_clean
>   bmake cleandir
> bmake[2]: Entering directory `/<>'
> rm -f a.out [Ee]rrs mklog core *.core  csh alloc.o char.o const.o csh.o dir.o 
> dol.o error.o exec.o exp.o file.o func.o glob.o hist.o init.o lex.o misc.o 
> parse.o proc.o sem.o set.o str.o time.o  alloc.ln char.ln const.ln csh.ln 
> dir.ln dol.ln error.ln exec.ln exp.ln file.ln func.ln glob.ln hist.ln init.ln 
> lex.ln misc.ln parse.ln proc.ln sem.ln set.ln str.ln time.ln error.h const.h 
> .depend alloc.d char.d const.d csh.d dir.d dol.d error.d exec.d exp.d file.d 
> func.d glob.d hist.d init.d lex.d misc.d parse.d proc.d sem.d set.d str.d 
> time.d y.tab.d *.tmp.d
> rm -f .depend alloc.d char.d const.d csh.d dir.d dol.d error.d exec.d exp.d 
> file.d func.d glob.d hist.d init.d lex.d misc.d parse.d proc.d sem.d set.d 
> str.d time.d y.tab.d *.tmp.d
> rm -f .depend /<>/tags
> bmake[2]: Leaving directory `/<>'
> dh_auto_clean -- -C USD.doc
>   bmake cleandir -C USD.doc
> bmake[2]: Entering directory `/<>/USD.doc'
> rm -f paper.* [eE]rrs mklog 
> bmake[2]: Leaving directory `/<>/USD.doc'
> make[1]: Leaving directory '/<>'
>dh_autoreconf_clean -O--buildsystem=bmake
>dh_clean -O--buildsystem=bmake
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building csh using existing ./csh_20110502.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  csh-20110502/csh.cat1
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/csh_20110502-7.diff.4c8rOj
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage 
> --sanitize-env -us -uc -rfakeroot -S' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/13/csh_20110502-7_unstable.log

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Kernel Bug in 6.2.0-26-generic

[joy-ubu]

To whomever it may concern.

I'm writing to inform you that after your most recent kernel update to kernel 
6.2.0-26-generic
from kernel 5.19.0-50-generic I have - once again - had the issue that some of 
the programs on
my computer have had difficulty starting as most of the time they've crashed, 
suffering from a
segmentation fault. On the occasion that they do star - something that is more 
rare than not -
they usually ether temporarily hang or crash while loading.

So far it seems that this bug only occurs with the 64-bit versions of unity3d 
games and while
some games do have a 32-bit version (which seems to always run just fine) not 
all do.

>From what I can discern this problem might be connected to the 64-bit version 
>of the libmono.so
file. It's also to my knowledge not possible to just remove it or replace it 
with the 32-bit version. The very
same problem occurred back in July when kernel 6.1.0-1015-oem replaced kernel 
5.19.0-46-generic
and disappeared with kernel 5.19.0-50-generic only to now re-appear again.

While searching on GOG I did found a thread were some Debian users had the same 
or a very similar
problem back in June. As well as someone who'd managed a workaround by 
LD-preloading a shim that
removed the MAP_32BIT flag since that was apparently what randomly failed.

<http://www.gog.com/forum/general/dungeon_2_debian_12>


I'm running Ubuntu Jammy Jellyfish and have had this problem on several 
computers with different
hardware - both AMD and Intel as wells as NVIDIA Discrete and Intel Integrated 
graphics.

Sincerly
Joy

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

BUG: drivers/usb/host/xhci: memleak in alloc from xhci_disable_usb3_lpm_timeout()

[Mirsad Goran Todorovac]

Hi all!

Here are again the good news and the bad news:

BAD:  another kernel memory leak detected (one more to hunt down and fix)
GOOD: another kernel memory leak detected (one less unaccounted for)

I tried to make some fun, but maintainers are busy folks, so let's get down
to business:

---
Nine (9) new systemd-udevd kernel memory leaks occurred (unable to reproduce).

The platform is Ubuntu 22.10 with (relatively recent) systemd 251.4-1ubuntu7.1
on LENOVO_MT_82H8_BU_idea_FM_IdeaPad 3 15ITL6 with BIOS GGCN51WW from 
11/16/2022.

The symptom (/sys/kernel/debug/kmemleak output):

unreferenced object 0x909698ff9280 (size 64):
  comm "systemd-udevd", pid 436, jiffies 4294893239 (age 6287.088s)
  hex dump (first 32 bytes):
e0 51 bb 99 96 90 ff ff 00 00 00 00 00 00 00 00  .Q..
40 5b bb 99 96 90 ff ff 00 00 00 00 00 00 00 00  @[..
  backtrace:
[] slab_post_alloc_hook+0x8c/0x320
[] __kmem_cache_alloc_node+0x1c7/0x2b0
[] kmalloc_node_trace+0x2b/0xa0
[] xhci_alloc_command+0x7c/0x1b0
[] xhci_alloc_command_with_ctx+0x21/0x70
[] xhci_change_max_exit_latency+0x2e/0x1c0
[] xhci_disable_usb3_lpm_timeout+0x7b/0xb0
[] usb_disable_link_state+0x57/0xe0
[] usb_disable_lpm+0x86/0xc0
[] usb_unlocked_disable_lpm+0x31/0x60
[] usb_disable_device+0x136/0x250
[] usb_set_configuration+0x583/0xa70
[] usb_generic_driver_disconnect+0x2d/0x40
[] usb_unbind_device+0x32/0x90
[] device_remove+0x65/0x70
[] device_release_driver_internal+0xc3/0x140
unreferenced object 0x909699bb5b40 (size 32):
  comm "systemd-udevd", pid 436, jiffies 4294893239 (age 6287.088s)
  hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
50 5b bb 99 96 90 ff ff 50 5b bb 99 96 90 ff ff  P[..P[..
  backtrace:
[] slab_post_alloc_hook+0x8c/0x320
[] __kmem_cache_alloc_node+0x1c7/0x2b0
[] kmalloc_node_trace+0x2b/0xa0
[] xhci_alloc_command+0xf4/0x1b0
[] xhci_alloc_command_with_ctx+0x21/0x70
[] xhci_change_max_exit_latency+0x2e/0x1c0
[] xhci_disable_usb3_lpm_timeout+0x7b/0xb0
[] usb_disable_link_state+0x57/0xe0
[] usb_disable_lpm+0x86/0xc0
[] usb_unlocked_disable_lpm+0x31/0x60
[] usb_disable_device+0x136/0x250
[] usb_set_configuration+0x583/0xa70
[] usb_generic_driver_disconnect+0x2d/0x40
[] usb_unbind_device+0x32/0x90
[] device_remove+0x65/0x70
[] device_release_driver_internal+0xc3/0x140
unreferenced object 0x909699bb51e0 (size 32):
  comm "systemd-udevd", pid 436, jiffies 4294893239 (age 6287.088s)
  hex dump (first 32 bytes):
02 00 00 00 20 04 00 00 00 a0 ff 98 96 90 ff ff   ...
00 a0 ff 18 01 00 00 00 00 00 00 00 00 00 00 00  
  backtrace:
[] slab_post_alloc_hook+0x8c/0x320
[] __kmem_cache_alloc_node+0x1c7/0x2b0
[] kmalloc_node_trace+0x2b/0xa0
[] xhci_alloc_container_ctx+0x7e/0x140
[] xhci_alloc_command_with_ctx+0x39/0x70
[] xhci_change_max_exit_latency+0x2e/0x1c0
[] xhci_disable_usb3_lpm_timeout+0x7b/0xb0
[] usb_disable_link_state+0x57/0xe0
[] usb_disable_lpm+0x86/0xc0
[] usb_unlocked_disable_lpm+0x31/0x60
[] usb_disable_device+0x136/0x250
[] usb_set_configuration+0x583/0xa70
[] usb_generic_driver_disconnect+0x2d/0x40
[] usb_unbind_device+0x32/0x90
[] device_remove+0x65/0x70
[] device_release_driver_internal+0xc3/0x140
.
.
.

Please find the config, lshw output and complete /sys/kernel/debug/kmemleak
output here:

https://domac.alu.unizg.hr/~mtodorov/linux/bugreports/systemd-udevd/kmemleak.log

https://domac.alu.unizg.hr/~mtodorov/linux/bugreports/systemd-udevd/lshw.txt
https://domac.alu.unizg.hr/~mtodorov/linux/bugreports/systemd-udevd/config-6.3.0-rc3-kobj-rlse-00317-g65aca32efdcb

The systemd issue tracker said they accept issues only for the most recent 253 
and
252, 251.4 seems too old for them despite being issued on May 21, 2022
(Source: https://github.com/systemd/systemd/releases).

It is not that I want to dump this on Linux kernel developers, but I felt
like it is a kernel memory leak problem rather than a bug in systemd-udevd.

Of course, my hunch might be wrong ...

As per Code of Conduct, I have checked for the developers and maintainers with
scripts/get_maintainers.pl.

Best regards,
Mirsad

-- 
Mirsad Goran Todorovac
Sistem inženjer
Grafički fakultet | Akademija likovnih umjetnosti
Sveučilište u Zagrebu
 
System engineer
Faculty of Graphic Arts | Academy of Fine Arts
University of Zagreb, Republic of Croatia
The European Union

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: BUG: drivers/usb/host/xhci: memleak in alloc from xhci_disable_usb3_lpm_timeout()

[Mirsad Goran Todorovac]

On 27.3.2023. 11:41, Mathias Nyman wrote:

On 25.3.2023 13.33, Mirsad Goran Todorovac wrote:

On 25. 03. 2023. 12:27, Mirsad Goran Todorovac wrote:

Hi all!

Here are again the good news and the bad news:

BAD:  another kernel memory leak detected (one more to hunt down and fix)
GOOD: another kernel memory leak detected (one less unaccounted for)

I tried to make some fun, but maintainers are busy folks, so let's get down
to business:

---
Nine (9) new systemd-udevd kernel memory leaks occurred (unable to reproduce).

The platform is Ubuntu 22.10 with (relatively recent) systemd 251.4-1ubuntu7.1
on LENOVO_MT_82H8_BU_idea_FM_IdeaPad 3 15ITL6 with BIOS GGCN51WW from 
11/16/2022.

The symptom (/sys/kernel/debug/kmemleak output):

unreferenced object 0x909698ff9280 (size 64):
   comm "systemd-udevd", pid 436, jiffies 4294893239 (age 6287.088s)
   hex dump (first 32 bytes):
 e0 51 bb 99 96 90 ff ff 00 00 00 00 00 00 00 00  .Q..
 40 5b bb 99 96 90 ff ff 00 00 00 00 00 00 00 00  @[..
   backtrace:
 [] slab_post_alloc_hook+0x8c/0x320
 [] __kmem_cache_alloc_node+0x1c7/0x2b0
 [] kmalloc_node_trace+0x2b/0xa0
 [] xhci_alloc_command+0x7c/0x1b0
 [] xhci_alloc_command_with_ctx+0x21/0x70
 [] xhci_change_max_exit_latency+0x2e/0x1c0>>  [] 
xhci_disable_usb3_lpm_timeout+0x7b/0xb0

 [] usb_disable_link_state+0x57/0xe0


Thanks for the report.

I think I found the leak, and wrote a patch for it.
Any chance you could test it with the same setup?

https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git/commit/?h=for-usb-linus=8bacee588602ed74cc22aaf4c56b796300e5a943


Hi, Mathias,

Great you have found the leak!

I cannot make testing in the same setup because I can access that particular box
until after I finish my day job.

I will prioritise it.

If this is the catch, it will save me almost a dozen bisect builds. :-)

Best regards,
Mirsad

--
Mirsad Todorovac
System engineer
Faculty of Graphic Arts | Academy of Fine Arts
University of Zagreb
Republic of Croatia, the European Union

Sistem inženjer
Grafički fakultet | Akademija likovnih umjetnosti
Sveučilište u Zagrebu


--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: BUG: BISECTED: drivers/usb/host/xhci: memleak in alloc from xhci_disable_usb3_lpm_timeout()

[Mirsad Goran Todorovac]

On 27. 03. 2023. 11:41, Mathias Nyman wrote:
> On 25.3.2023 13.33, Mirsad Goran Todorovac wrote:
>> On 25. 03. 2023. 12:27, Mirsad Goran Todorovac wrote:
>>> Hi all!
>>>
>>> Here are again the good news and the bad news:
>>>
>>> BAD:  another kernel memory leak detected (one more to hunt down and fix)
>>> GOOD: another kernel memory leak detected (one less unaccounted for)
>>>
>>> I tried to make some fun, but maintainers are busy folks, so let's get down
>>> to business:
>>>
>>> ---
>>> Nine (9) new systemd-udevd kernel memory leaks occurred (unable to 
>>> reproduce).
>>>
>>> The platform is Ubuntu 22.10 with (relatively recent) systemd 
>>> 251.4-1ubuntu7.1
>>> on LENOVO_MT_82H8_BU_idea_FM_IdeaPad 3 15ITL6 with BIOS GGCN51WW from 
>>> 11/16/2022.
>>>
>>> The symptom (/sys/kernel/debug/kmemleak output):
>>>
>>> unreferenced object 0x909698ff9280 (size 64):
>>>    comm "systemd-udevd", pid 436, jiffies 4294893239 (age 6287.088s)
>>>    hex dump (first 32 bytes):
>>>  e0 51 bb 99 96 90 ff ff 00 00 00 00 00 00 00 00  .Q..
>>>  40 5b bb 99 96 90 ff ff 00 00 00 00 00 00 00 00  @[..
>>>    backtrace:
>>>  [] slab_post_alloc_hook+0x8c/0x320
>>>  [] __kmem_cache_alloc_node+0x1c7/0x2b0
>>>  [] kmalloc_node_trace+0x2b/0xa0
>>>  [] xhci_alloc_command+0x7c/0x1b0
>>>  [] xhci_alloc_command_with_ctx+0x21/0x70
>>>  [] xhci_change_max_exit_latency+0x2e/0x1c0>>  
>>> [] xhci_disable_usb3_lpm_timeout+0x7b/0xb0
>>>  [] usb_disable_link_state+0x57/0xe0
> 
> Thanks for the report.
> 
> I think I found the leak, and wrote a patch for it.
> Any chance you could test it with the same setup?
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git/commit/?h=for-usb-linus=8bacee588602ed74cc22aaf4c56b796300e5a943

As I have already been half-through bisect, I took the liberty to finish it.

# good: [5ce036b98dd3301fc43bb06a6383ef07b6c776bc] xhci: dbc: create and remove 
dbc structure in dbgtty driver.
git bisect good 5ce036b98dd3301fc43bb06a6383ef07b6c776bc
# bad: [d016cbe4d7acf5100df83ecf4d02db4e9f607c1d] usb: typec: Support the 
WUSB3801 port controller
git bisect bad d016cbe4d7acf5100df83ecf4d02db4e9f607c1d
# bad: [cd36facf104afbde7e8fa25cd6f5b6dd9fa97bb2] usb: remove Link 
Powermanagement (LPM) disable before port reset.
git bisect bad cd36facf104afbde7e8fa25cd6f5b6dd9fa97bb2
# good: [6aec50009d52f28ef8b512cba0f5078b3928064d] xhci: dbc: Don't call 
dbc_tty_init() on every dbc tty probe
git bisect good 6aec50009d52f28ef8b512cba0f5078b3928064d
# bad: [5c2a380a5aa8c15985359904b6d47466528d2993] xhci: Allocate separate 
command structures for each LPM command
git bisect bad 5c2a380a5aa8c15985359904b6d47466528d2993
# good: [e1ec140f273e1e30cea7e6d5f50934d877232121] xhci: dbgtty: use IDR to 
support several dbc instances.
git bisect good e1ec140f273e1e30cea7e6d5f50934d877232121
# first bad commit: [5c2a380a5aa8c15985359904b6d47466528d2993] xhci: Allocate 
separate command structures for each LPM command

Interesting enough, Mr. Greg predicted this is an xhci problem already in 
November [1],
but I did not embolden myself to bisect until this weekend, seeing that it was
still leaking.

But then I was brand new to the CONFIG_DEBUG_KMEMLEAK feature.

[1] https://lore.kernel.org/lkml/y2zcywnnvqwpp...@kroah.com/

I think the culprit patch is otherwise awesome, reducing latency and locking, 
especially
welcome in multimedia use.

So far, I was unable to exploit this leak as non-superuser or automate it like 
gpio-sim
to exhaust the kernel's limited memory, but this doesn't prove that smarter 
hackers
couldn't devise some means to do that exploit.

BTW: Full designation of the patch is 
5.17.0-rc4-kmemlk-xhci-00071-g5c2a380a5aa8, so all
kernels 5.17-rc4+ appear affected by the issue.

Thank you and if you will need any more testing, I am available in my off hours.

Really nice working to assist your dynamic team.

To compare, another developer from another project was desperate about a 
software giant
being unwilling to abandon deprecated MODP 1024 DH renegotiation for its native 
VPN,
now for a couple of years ...

Best regards,
Mirsad

-- 
Mirsad Goran Todorovac
Sistem inženjer
Grafički fakultet | Akademija likovnih umjetnosti
Sveučilište u Zagrebu
 
System engineer
Faculty of Graphic Arts | Academy of Fine Arts
University of Zagreb, Republic of Croatia
The European Union

"I see something approaching fast ... Will it be friends with me?"


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: BUG: drivers/usb/host/xhci: memleak in alloc from xhci_disable_usb3_lpm_timeout()

[Mathias Nyman]

On 25.3.2023 13.33, Mirsad Goran Todorovac wrote:

On 25. 03. 2023. 12:27, Mirsad Goran Todorovac wrote:

Hi all!

Here are again the good news and the bad news:

BAD:  another kernel memory leak detected (one more to hunt down and fix)
GOOD: another kernel memory leak detected (one less unaccounted for)

I tried to make some fun, but maintainers are busy folks, so let's get down
to business:

---
Nine (9) new systemd-udevd kernel memory leaks occurred (unable to reproduce).

The platform is Ubuntu 22.10 with (relatively recent) systemd 251.4-1ubuntu7.1
on LENOVO_MT_82H8_BU_idea_FM_IdeaPad 3 15ITL6 with BIOS GGCN51WW from 
11/16/2022.

The symptom (/sys/kernel/debug/kmemleak output):

unreferenced object 0x909698ff9280 (size 64):
   comm "systemd-udevd", pid 436, jiffies 4294893239 (age 6287.088s)
   hex dump (first 32 bytes):
 e0 51 bb 99 96 90 ff ff 00 00 00 00 00 00 00 00  .Q..
 40 5b bb 99 96 90 ff ff 00 00 00 00 00 00 00 00  @[..
   backtrace:
 [] slab_post_alloc_hook+0x8c/0x320
 [] __kmem_cache_alloc_node+0x1c7/0x2b0
 [] kmalloc_node_trace+0x2b/0xa0
 [] xhci_alloc_command+0x7c/0x1b0
 [] xhci_alloc_command_with_ctx+0x21/0x70
 [] xhci_change_max_exit_latency+0x2e/0x1c0>>  
[] xhci_disable_usb3_lpm_timeout+0x7b/0xb0
 [] usb_disable_link_state+0x57/0xe0


Thanks for the report.

I think I found the leak, and wrote a patch for it.
Any chance you could test it with the same setup?

https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git/commit/?h=for-usb-linus=8bacee588602ed74cc22aaf4c56b796300e5a943

Thanks
-Mathias


--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: ntfs-3g app deadlock bug report

[Alex Murray]

Hi

Thanks for reporting this issue - in general it is better to report bugs
via launchpad than email (e.g. by running the following command (without
the quotation marks) in a terminal: "ubuntu-bug ntfs-3g" or by
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+filebug)

I notice you also appear to have reported this to the upstream nfts-3g
project at https://github.com/tuxera/ntfs-3g/issues/56 but have had no
response.

However, my initial thoughts when looking at this is that it appears you
can trigger a livelock within the kernel from an unprivileged user in
userspace - as such I wonder if this is a bug in the FUSE subsystem
within the Linux kernel and hence whether it should be reported to the
upstream kernel developers as well? As per
https://www.kernel.org/doc/html/v4.15/admin-guide/reporting-bugs.html it
would appear that this should be reported to the following email
addresses (assuming this is a real kernel bug rather than a bug within
the ntfs-3g userspace project):

$ ./scripts/get_maintainer.pl fs/fuse/fuse_i.h
Miklos Szeredi  (maintainer:FUSE: FILESYSTEM IN USERSPACE)
linux-fsde...@vger.kernel.org (open list:FUSE: FILESYSTEM IN USERSPACE)
linux-ker...@vger.kernel.org (open list)

Thanks,
Alex

On Sat, 2022-12-10 at 13:02:41 +0900, 박영준 wrote:

> Hi I find live lock bug in ntfs-3g app.
> I post it but not respond from its public repos.
> so I report it this mailing list
>
> the bug I found is written below.
>
>
> [Environment]
> 22.04 5.15.0-43-generic ubuntu kernel.
> ntfs-3g version ntfs-3g 2021.8.22 integrated FUSE 28 - Third Generation NTFS 
> Driver
> [Problem]
> I bumped on livelock and analyze it. and concluded that it is needed to be 
> fixed.
> it happens when 3 operation concurrently progressing.
>
> usb detach by user. and kernel detect it.
> mount.ntfs umount request & device release operation
> pool-udisksd umount operation.
>
> [Conclusion]
>
> mounted target device file must be released after /dev/fuse release. it makes 
> deadlocky scenario.
> fuse file system "fuse_simple_request" should not be waiting forever. it is 
> hard to solve this situation by interrupting application. huntask panic 
> configuration make user kernel panic. user
> don't know why.
>
> [Analysis]
> I got a kernel crash dump file. and analyze it.
> here is the scenario description.
>
> kworker detect usb is detached from computer.
> it is blocked by umount operation (pool-udiskd)
> PID: 8 TASK: 88810029e400 CPU: 0 COMMAND: "kworker/0:1"
> 0 [c906f6f0] __schedule at 81d57c0d
> 1 [c906f778] schedule at 81d57fae
> 2 [c906f798] rwsem_down_read_slowpath at 81d5a2de
> 3 [c906f830] down_read at 81d5a373 // wait s_umount
> 4 [c906f848] get_super at 813799ca
> 5 [c906f878] fsync_bdev at 815c6f46
> 6 [c906f8a0] delete_partition at 815e9328
> 7 [c906f8c0] blk_drop_partitions at 815e9b3e
> 8 [c906f8e8] del_gendisk at 815e75f1 // lock mutex
> 9 [c906f930] sd_remove at 818cd325
> 10 [c906f958] __device_release_driver at 8184006f
> 11 [c906f990] device_release_driver at 818400a9
> 12 [c906f9b0] bus_remove_device at 8183f28e
> 13 [c906f9d8] device_del at 818399ac
> 14 [c906fa28] __scsi_remove_device at 818c2628
> 15 [c906fa50] scsi_forget_host at 818c029f
> 16 [c906fa70] scsi_remove_host at 818b3727
> 17 [c906fa98] usb_stor_disconnect at c0659b20 [usb_storage]
> 18 [c906fac0] usb_unbind_interface at 8194ef30
> 19 [c906fb18] __device_release_driver at 8184006f
> 20 [c906fb50] device_release_driver at 818400a9
> 21 [c906fb70] bus_remove_device at 8183f28e
> 22 [c906fb98] device_del at 818399ac
> 23 [c906fbe8] usb_disable_device at 8194cdce
> 24 [c906fc30] usb_disconnect.cold at 81d19e09
> 25 [c906fc80] hub_port_connect at 81944bb8
> 26 [c906fd00] hub_port_connect_change at 819454b1
> 27 [c906fd70] port_event at 81945d77
> 28 [c906fe08] hub_event at 819460a7
> 29 [c906fe78] process_one_work at 810d9e7b
> 30 [c906fec8] worker_thread at 810da073
> 31 [c906ff10] kthread at 810e1cba
> 32 [c906ff50] ret_from_fork at 81004bc2
>
> 3 [c906f830] down_read at 81d5a373
> c906f838: [888154d36800:kmalloc-2k] c906f870
> c906f848: get_super+154
>
> it request umount. and release /dev/sdc file before release /dev/fus

Bug#1027473: fwbuilder: Link to Quick Start Guide does not work, no alternatives found

[Omer Zak]

Package: fwbuilder
Version: 5.3.7-4.1
Severity: normal
Tags: upstream

When starting fwbuilder after installing fwbuilder, fwbuilder-common,
fwbuilder-doc
(each of them is version 5.3.7-4.1), I am offered the option to watch
the Quick Start Guide by clicking on the "Watch the guide" in bottom
right corner of the pop up dialog.

This action gets the browser to open the link:
http://www.fwbuilder.org/4.0/quick_start_guide_1.html
However, as of today, the domain www.fwbuilder.org cannot be resolved.

1. fwbuilder.org is registered in the whois database.
2. The quick start guide does not seem to be available from
   fwbuilder-doc.
   At any case, in /usr/share/doc/fwbuilder-doc, there is no
   file whose name may hint at its being the quick start guide.
3. I looked for the file in Internet Archive:
  
https://web.archive.org/web/*/http://www.fwbuilder.org/4.0/quick_start_guide_1.html*
   and even there, I did not find the quick start guide.


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

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

Versions of packages fwbuilder depends on:
ii  fwbuilder-common 5.3.7-4.1
ii  libc62.31-13+deb11u5
ii  libgcc-s110.2.1-6
ii  libqt5core5a 5.15.2+dfsg-9
ii  libqt5gui5   5.15.2+dfsg-9
ii  libqt5network5   5.15.2+dfsg-9
ii  libqt5printsupport5  5.15.2+dfsg-9
ii  libqt5widgets5   5.15.2+dfsg-9
ii  libsnmp405.9+dfsg-4+deb11u1
ii  libstdc++6   10.2.1-6
ii  libxml2  2.9.10+dfsg-6.7+deb11u3
ii  libxslt1.1   1.1.34-4+deb11u1
ii  zlib1g   1:1.2.11.dfsg-2+deb11u2

Versions of packages fwbuilder recommends:
ii  fwbuilder-doc  5.3.7-4.1
ii  rcs5.10.0-1

fwbuilder suggests no packages.

-- no debconf information

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

ntfs-3g app deadlock bug report

[박영준]

Hi I find live lock bug in ntfs-3g app.
I post it but not respond from its public repos.
so I report it this mailing list

the bug I found is written below.


[Environment]
22.04 5.15.0-43-generic ubuntu kernel.
ntfs-3g version ntfs-3g 2021.8.22 integrated FUSE 28 - Third Generation NTFS 
Driver
[Problem]
I bumped on livelock and analyze it. and concluded that it is needed to be 
fixed.
it happens when 3 operation concurrently progressing.

usb detach by user. and kernel detect it.
mount.ntfs umount request & device release operation
pool-udisksd umount operation.

[Conclusion]

mounted target device file must be released after /dev/fuse release. it makes 
deadlocky scenario.
fuse file system "fuse_simple_request" should not be waiting forever. it is 
hard to solve this situation by interrupting application. huntask panic 
configuration make user kernel panic. user
don't know why.

[Analysis]
I got a kernel crash dump file. and analyze it.
here is the scenario description.

kworker detect usb is detached from computer.
it is blocked by umount operation (pool-udiskd)
PID: 8 TASK: 88810029e400 CPU: 0 COMMAND: "kworker/0:1"
0 [c906f6f0] __schedule at 81d57c0d
1 [c906f778] schedule at 81d57fae
2 [c906f798] rwsem_down_read_slowpath at 81d5a2de
3 [c906f830] down_read at 81d5a373 // wait s_umount
4 [c906f848] get_super at 813799ca
5 [c906f878] fsync_bdev at 815c6f46
6 [c906f8a0] delete_partition at 815e9328
7 [c906f8c0] blk_drop_partitions at 815e9b3e
8 [c906f8e8] del_gendisk at 815e75f1 // lock mutex
9 [c906f930] sd_remove at 818cd325
10 [c906f958] __device_release_driver at 8184006f
11 [c906f990] device_release_driver at 818400a9
12 [c906f9b0] bus_remove_device at 8183f28e
13 [c906f9d8] device_del at 818399ac
14 [c906fa28] __scsi_remove_device at 818c2628
15 [c906fa50] scsi_forget_host at 818c029f
16 [c906fa70] scsi_remove_host at 818b3727
17 [c906fa98] usb_stor_disconnect at c0659b20 [usb_storage]
18 [c906fac0] usb_unbind_interface at 8194ef30
19 [c906fb18] __device_release_driver at 8184006f
20 [c906fb50] device_release_driver at 818400a9
21 [c906fb70] bus_remove_device at 8183f28e
22 [c906fb98] device_del at 818399ac
23 [c906fbe8] usb_disable_device at 8194cdce
24 [c906fc30] usb_disconnect.cold at 81d19e09
25 [c906fc80] hub_port_connect at 81944bb8
26 [c906fd00] hub_port_connect_change at 819454b1
27 [c906fd70] port_event at 81945d77
28 [c906fe08] hub_event at 819460a7
29 [c906fe78] process_one_work at 810d9e7b
30 [c906fec8] worker_thread at 810da073
31 [c906ff10] kthread at 810e1cba
32 [c906ff50] ret_from_fork at 81004bc2

3 [c906f830] down_read at 81d5a373
c906f838: [888154d36800:kmalloc-2k] c906f870
c906f848: get_super+154

it request umount. and release /dev/sdc file before release /dev/fuse. but. it 
is blocked by usb detach.
PID: 18681 TASK: 88810e5b8000 CPU: 1 COMMAND: "mount.ntfs"
0 [c9ea7c50] __schedule at 81d57c0d
1 [c9ea7cd8] schedule at 81d57fae
2 [c9ea7cf8] schedule_preempt_disabled at 81d5839e
3 [c9ea7d08] __mutex_lock.constprop.0 at 81d59053
4 [c9ea7d80] __mutex_lock_slowpath at 81d59353
5 [c9ea7d90] mutex_lock at 81d59394 // wait open mutex
6 [c9ea7da8] blkdev_put at 815c765a
7 [c9ea7de0] blkdev_close at 815c86e7
8 [c9ea7df8] __fput at 8137704f
9 [c9ea7e30] fput at 8137724e
10 [c9ea7e40] task_work_run at 810deb6d
11 [c9ea7e68] exit_to_user_mode_loop at 81160fc0
12 [c9ea7e90] exit_to_user_mode_prepare at 8116106c
13 [c9ea7ea8] syscall_exit_to_user_mode at 81d4f327
14 [c9ea7ec0] do_syscall_64 at 81d4b1b9
15 [c9ea7ef8] exit_to_user_mode_prepare at 81161007
16 [c9ea7f10] syscall_exit_to_user_mode at 81d4f327
17 [c9ea7f28] do_syscall_64 at 81d4b1b9
RIP: 7f3e315fb117 RSP: 7fff16bcb628 RFLAGS: 0246
RAX:  RBX: 55cc1b45c710 RCX: 7f3e315fb117
RDX:  RSI: 0006 RDI: 0003
RBP: 55cc1b45c970 R8: 55cc1b476940 R9: 
R10: 0005 R11: 0246 R12: 7f3e314e36c0
R13: 55cc1b45c710 R14: 55cc1b467030 R15: 
ORIG_RAX: 0003 CS: 0033 SS: 002b

3 [c9ea7d08] __mutex_lo

ntfs-3g app deadlock bug report

[박영준]

Hi I find live lock bug in ntfs-3g app.
I post it but not respond from its public repos.
so I report it this mailing list

the bug I found is written below.


[Environment]
22.04 5.15.0-43-generic ubuntu kernel.
ntfs-3g version ntfs-3g 2021.8.22 integrated FUSE 28 - Third Generation NTFS 
Driver
[Problem]
I bumped on livelock and analyze it. and concluded that it is needed to be 
fixed.
it happens when 3 operation concurrently progressing.

usb detach by user. and kernel detect it.
mount.ntfs umount request & device release operation
pool-udisksd umount operation.

[Conclusion]

mounted target device file must be released after /dev/fuse release. it makes 
deadlocky scenario.
fuse file system "fuse_simple_request" should not be waiting forever. it is 
hard to solve this situation by interrupting application. huntask panic 
configuration make user kernel panic. user
don't know why.

[Analysis]
I got a kernel crash dump file. and analyze it.
here is the scenario description.

kworker detect usb is detached from computer.
it is blocked by umount operation (pool-udiskd)
PID: 8 TASK: 88810029e400 CPU: 0 COMMAND: "kworker/0:1"
0 [c906f6f0] __schedule at 81d57c0d
1 [c906f778] schedule at 81d57fae
2 [c906f798] rwsem_down_read_slowpath at 81d5a2de
3 [c906f830] down_read at 81d5a373 // wait s_umount
4 [c906f848] get_super at 813799ca
5 [c906f878] fsync_bdev at 815c6f46
6 [c906f8a0] delete_partition at 815e9328
7 [c906f8c0] blk_drop_partitions at 815e9b3e
8 [c906f8e8] del_gendisk at 815e75f1 // lock mutex
9 [c906f930] sd_remove at 818cd325
10 [c906f958] __device_release_driver at 8184006f
11 [c906f990] device_release_driver at 818400a9
12 [c906f9b0] bus_remove_device at 8183f28e
13 [c906f9d8] device_del at 818399ac
14 [c906fa28] __scsi_remove_device at 818c2628
15 [c906fa50] scsi_forget_host at 818c029f
16 [c906fa70] scsi_remove_host at 818b3727
17 [c906fa98] usb_stor_disconnect at c0659b20 [usb_storage]
18 [c906fac0] usb_unbind_interface at 8194ef30
19 [c906fb18] __device_release_driver at 8184006f
20 [c906fb50] device_release_driver at 818400a9
21 [c906fb70] bus_remove_device at 8183f28e
22 [c906fb98] device_del at 818399ac
23 [c906fbe8] usb_disable_device at 8194cdce
24 [c906fc30] usb_disconnect.cold at 81d19e09
25 [c906fc80] hub_port_connect at 81944bb8
26 [c906fd00] hub_port_connect_change at 819454b1
27 [c906fd70] port_event at 81945d77
28 [c906fe08] hub_event at 819460a7
29 [c906fe78] process_one_work at 810d9e7b
30 [c906fec8] worker_thread at 810da073
31 [c906ff10] kthread at 810e1cba
32 [c906ff50] ret_from_fork at 81004bc2

3 [c906f830] down_read at 81d5a373
c906f838: [888154d36800:kmalloc-2k] c906f870
c906f848: get_super+154

it request umount. and release /dev/sdc file before release /dev/fuse. but. it 
is blocked by usb detach.
PID: 18681 TASK: 88810e5b8000 CPU: 1 COMMAND: "mount.ntfs"
0 [c9ea7c50] __schedule at 81d57c0d
1 [c9ea7cd8] schedule at 81d57fae
2 [c9ea7cf8] schedule_preempt_disabled at 81d5839e
3 [c9ea7d08] __mutex_lock.constprop.0 at 81d59053
4 [c9ea7d80] __mutex_lock_slowpath at 81d59353
5 [c9ea7d90] mutex_lock at 81d59394 // wait open mutex
6 [c9ea7da8] blkdev_put at 815c765a
7 [c9ea7de0] blkdev_close at 815c86e7
8 [c9ea7df8] __fput at 8137704f
9 [c9ea7e30] fput at 8137724e
10 [c9ea7e40] task_work_run at 810deb6d
11 [c9ea7e68] exit_to_user_mode_loop at 81160fc0
12 [c9ea7e90] exit_to_user_mode_prepare at 8116106c
13 [c9ea7ea8] syscall_exit_to_user_mode at 81d4f327
14 [c9ea7ec0] do_syscall_64 at 81d4b1b9
15 [c9ea7ef8] exit_to_user_mode_prepare at 81161007
16 [c9ea7f10] syscall_exit_to_user_mode at 81d4f327
17 [c9ea7f28] do_syscall_64 at 81d4b1b9
RIP: 7f3e315fb117 RSP: 7fff16bcb628 RFLAGS: 0246
RAX:  RBX: 55cc1b45c710 RCX: 7f3e315fb117
RDX:  RSI: 0006 RDI: 0003
RBP: 55cc1b45c970 R8: 55cc1b476940 R9: 
R10: 0005 R11: 0246 R12: 7f3e314e36c0
R13: 55cc1b45c710 R14: 55cc1b467030 R15: 
ORIG_RAX: 0003 CS: 0033 SS: 002b

3 [c9ea7d08] __mutex_lo

Bug#1024011: gtksourceview4: autopkgtest regression

[Sebastian Ramacher]

Source: gtksourceview4
Version: 4.8.4-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gtksourceview4/27967119/log.gz

# Start of file-loader tests
# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation local 
(GLocalVfs) for ?gio-vfs?
(/usr/libexec/installed-tests/gtksourceview-4/test-file-loader:6343): 
GLib-GIO-DEBUG: 15:17:49.746: _g_io_module_get_default: Found default 
implementation local (GLocalVfs) for ?gio-vfs?
ok 1 /file-loader/end-line-stripping
ok 2 /file-loader/end-new-line-detection
ok 3 /file-loader/begin-new-line-detection
# End of file-loader tests
PASS: gtksourceview-4/test-file-loader.test
Running test: gtksourceview-4/test-language-specs.test
**
GtkSourceView:ERROR:../testsuite/test-language-specs.c:47:main: 'srcdir' should 
not be NULL
Bail out! GtkSourceView:ERROR:../testsuite/test-language-specs.c:47:main: 
'srcdir' should not be NULL
FAIL: gtksourceview-4/test-language-specs.test (Child process killed by signal 
6)
SUMMARY: total=23; passed=3; skipped=0; failed=20; user=0.9s; system=0.4s; 
maxrss=70476
FAIL: gtksourceview-4/test-completion-words.test (Child process killed by 
signal 5)
FAIL: gtksourceview-4/test-mark.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-printcompositor.test (Child process killed by signal 
5)
FAIL: gtksourceview-4/test-regex.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-languagemanager.test (Child process killed by signal 
5)
FAIL: gtksourceview-4/test-iter.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-completion-model.test (Child process killed by 
signal 5)
FAIL: gtksourceview-4/test-buffer.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-file-saver.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-stylescheme.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-region.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-styleschememanager.test (Child process killed by 
signal 5)
FAIL: gtksourceview-4/test-space-drawer.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-encoding.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-search-context.test (Child process killed by signal 
5)
FAIL: gtksourceview-4/test-view.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-undo-manager.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-utils.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-language.test (Child process killed by signal 5)
FAIL: gtksourceview-4/test-language-specs.test (Child process killed by signal 
6)
autopkgtest [15:17:50]: test installed-tests: ---]
autopkgtest [15:17:50]: test installed-tests:  - - - - - - - - - - results - - 
- - - - - - - -
installed-tests  FAIL non-zero exit status 2
autopkgtest [15:17:50]:  summary
installed-tests  FAIL non-zero exit status 2

Cheers
-- 
Sebastian Ramacher

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug in PopTop

[Kolusion K]

Hello

 

 

There is a bug in PoPToP with the package version '1.4.0-11build1' in Ubuntu 20.04 LTS.

 

If you try and connect to a VPN server and the connection times out, then the service 'pptp' continues trying to connect in the background. This can be confirmed by checking the system log.

 

 

Kolusion

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Apache2 mpm_event bug still present in Ubuntu repositories

[Christian Ehrhardt]

On Fri, Jun 24, 2022 at 6:53 PM Mike Luttikhuis
 wrote:
>
> Hi,
>
> A bug in the apache2 package where mpm_event does not always gracefully kill 
> child processes after a graceful reload of the service is not patched in the 
> Ubuntu repositories. This is a nasty bug because if for example a SSL 
> certificate is replaced inside a vhost configuration, then older child 
> processes will still serve the older certificate, resulting in certificate 
> errors. Please check out PR 63169. Apache fixed this bug in 2.4.49, but the 
> bugfix is still not included in the Ubuntu repository. Since this bug is 
> pretty frustrating, I was wondering if this particular bugfix can be patched 
> in Ubuntu's version of the apache2 package.

Hi Mike,
thanks for your report, at a first glimpse the case looks valid and
doable, therefore I have converted this into a proper bug [1] to be
tracked.
You could help the team to have a look by providing steps to recreate
the situation via an update on that bug.

[1]: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1979942

> Kind regards,
>
> Mike
> --
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss



-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Apache2 mpm_event bug still present in Ubuntu repositories

[Mike Luttikhuis]

Hi,

A bug in the apache2 package where mpm_event does not always gracefully
kill child processes after a graceful reload of the service is not patched
in the Ubuntu repositories. This is a nasty bug because if for example a
SSL certificate is replaced inside a vhost configuration, then older child
processes will still serve the older certificate, resulting in certificate
errors. Please check out PR 63169
<https://bz.apache.org/bugzilla/show_bug.cgi?id=63169>. Apache fixed this
bug in 2.4.49
<https://git.openembedded.org/meta-openembedded/commit/meta-webserver/recipes-httpd/apache2?h=honister=54a96fa4feb1a7712f9f3d1190c0d95d89eb6c7c>,
but the bugfix is still not included in the Ubuntu repository. Since this
bug is pretty frustrating, I was wondering if this particular bugfix can be
patched in Ubuntu's version of the apache2 package.

Kind regards,

Mike
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

possible bug in udev?

[Martin Renwanz]

Hi everyone,

I stumbled recently over an interesting issue. I have an external 
bluray-drive, connected via usb. I have 20.04.3 LTS running, with latest 
patches applied.
Now, whenever I open the cd-tray with the button, the tray opens, the 
activity LED starts blinking fast, and I am unable to close the tray, as 
it is ejected immediately after closing it.


I hooked myself with udevadm monitor -u, and noticed an endless loop of 
events coming in. The only way to stop this is to disconnected the drive.


I was able to fix this (although creating another problem) by copying 
and modifying /lib/udev/rules.d/60-cdrom_id.rules - after removing the 
RUN+= part from the line which handles the cd eject, the problem was 
gone. (and udevadm did not show an endless loop of event when the eject 
button is pressed!)


I posted my problem (and the solution) on a stackexchange site, if 
anyone cares for further details.


https://unix.stackexchange.com/questions/668928/unable-to-close-cd-tray

My question is: my "fix" obviously is only a workaround, I have not been 
able to find the root cause. Is this a bug inside ubuntu / systemd, or 
did I make a mistake somewhere ?


Best Regards,
Martin Renwanz

--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug#986512: libunity: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

[Baptiste Beauplat]

On 2021/05/11 11:00 PM, Baptiste Beauplat wrote:
> The issue may be related to this upstream issue:
> 
> https://gitlab.gnome.org/GNOME/vala/-/issues/1167
> 
> I'll test using a patched version of vala and reassign if needed.

The pachted version of vala in sid works and libunity build correctly
with it. This is a regression in vala, reassigning the bug.

-- 
Baptiste Beauplat - lyknode


signature.asc
Description: PGP signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug#986512: libunity: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

[Baptiste Beauplat]

I started a bit of digging up on that FTBFS and I found that libunity
build correctly with vala <= 0.48.13-1.

A changed introduced in 0.48.14 must be at the origin of the bug.

(I don't have sufficient knowledge of vala to get to the bottom of this
issue, I just wanted to share this info)

-- 
Baptiste Beauplat - lyknode


signature.asc
Description: PGP signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug#986512: libunity: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

[Baptiste Beauplat]

The issue may be related to this upstream issue:

https://gitlab.gnome.org/GNOME/vala/-/issues/1167

I'll test using a patched version of vala and reassign if needed.

-- 
Baptiste Beauplat - lyknode


signature.asc
Description: PGP signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

update-notifier crashes (bug spotted in source code)

[Xu Zhongxing]

In the source code update-notifier_3.192.40.tar.xz, when there is file 
/var/lib/update-notifier/user.d/incomplete-language-support-gnome.note.

In hooks.c, at line 108, when the file test is true, the program will execute 
"goto out" at line 112.

Then at line 137, pathdirs is in uninitialized state and triggers a 
segmentation fault in g_strfreev().



if(cargv[0][0] == '/' &&
  g_file_test(cargv[0], G_FILE_TEST_EXISTS|G_FILE_TEST_IS_EXECUTABLE)) {
  result = TRUE;
  g_debug_hooks("command exists");
  goto out; // THIS IS EXECUTED
   }

   g_debug_hooks("'%s' is not a valid absolute path", cargv[0]);

   gchar **pathdirs = g_strsplit(getenv("PATH"), ":", 100);
   if(!pathdirs) goto out;

   for(int i = 0; pathdirs[i] != NULL; i++) {
  gchar *pathdir = pathdirs[i];
  char *fname = g_strdup_printf("%s/%s", pathdir, cargv[0]);
  if(g_file_test(fname, G_FILE_TEST_EXISTS|G_FILE_TEST_IS_EXECUTABLE)) {
  g_debug_hooks("command exists at '%s'", fname);
  g_free(fname);
  result = TRUE;
  goto out;
  }
  g_free(fname);
   }

   g_debug_hooks("failed to find command in PATH");

out:
   if(error) g_error_free(error);
   if(cargv) g_strfreev(cargv);
   if(pathdirs) g_strfreev(pathdirs); // THIS IS THE CRASH SITE BECAUSE 
pathdirs IS IN UNINITIALIZED STATE.
   if(unquoted) g_free(unquoted);
   return result;-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug#979436: resolvconf: Missing cleanup for obsolete dnscache conffile

[Guillem Jover]

Package: resolvconf
Version: 1.86
Severity: normal

Hi!

This package used to ship the /etc/resolvconf/update.d/dnscache conffile,
which stopped being shipped in version 1.75, but the conffile was
never cleaned up in the maintainer scripts, so it is left behind in
the system and marked as obsolete in the dpkg database.

Thanks,
Guillem

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug#979431: resolvconf: Unconditional use of systemctl

[Guillem Jover]

Package: resolvconf
Version: 1.86
Severity: normal

Hi!

This package makes unconditional use of systemctl in at least the
/etc/dhcp/dhclient-enter-hooks.d/resolvconf script, which on a
sysvinit system then shows the following message:

  ,---
  /sbin/dhclient-script: 19: /etc/dhcp/dhclient-enter-hooks.d/resolvconf: 
systemctl: not found
  `---

Thanks,
Guillem

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug#979431: marked as done (resolvconf: Unconditional use of systemctl)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jan 2021 18:08:07 +
with message-id 
and subject line Bug#979431: fixed in resolvconf 1.87
has caused the Debian Bug report #979431,
regarding resolvconf: Unconditional use of systemctl
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
979431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: resolvconf
Version: 1.86
Severity: normal

Hi!

This package makes unconditional use of systemctl in at least the
/etc/dhcp/dhclient-enter-hooks.d/resolvconf script, which on a
sysvinit system then shows the following message:

  ,---
  /sbin/dhclient-script: 19: /etc/dhcp/dhclient-enter-hooks.d/resolvconf: 
systemctl: not found
  `---

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: resolvconf
Source-Version: 1.87
Done: Andrej Shadura 

We believe that the bug you reported is fixed in the latest version of
resolvconf, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated resolvconf package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 06 Jan 2021 18:54:17 +0100
Source: resolvconf
Architecture: source
Version: 1.87
Distribution: unstable
Urgency: medium
Maintainer: resolvconf team 
Changed-By: Andrej Shadura 
Closes: 943735 979431 979436
Changes:
 resolvconf (1.87) unstable; urgency=medium
 .
   * Undo the damage on an incorrect merge commit:
 - Fix the maintainer’s address (Closes: #943735)
 - Revert "Skip pulling data into resolvconf, if isc-dhcp/ifupdown
   already push the same data to systemd-resolved and it is in use".
   Debian does not ship said hooks in ifupdown or isc-dhcp-client,
   so these fixes won’t work. Also, they use systemctl unconditionally
   which is fine in Ubuntu but not in Debian.
   (Closes: #979431)
   * Clean up the old conffile (Closes: #979436)
Checksums-Sha1:
 a3cd188fbd03edd2ddf7cfdfd8fe130d5faf1992 1483 resolvconf_1.87.dsc
 4c85aa4482f9ed933cb2c2efdd9ce8531ff1877a 73452 resolvconf_1.87.tar.xz
Checksums-Sha256:
 22c98325f1ba298a9b00f461a1943f00c36b419d9fdfba94a1624c81654560a1 1483 
resolvconf_1.87.dsc
 e86869b6c0ed3e9b4cab2b409e27d28294df8c71ef361c10545c81243c48e39f 73452 
resolvconf_1.87.tar.xz
Files:
 e269ce79e7ca79eabd0304d7c6928734 1483 net optional resolvconf_1.87.dsc
 3da444b2152726d84e6957b9d93687bd 73452 net optional resolvconf_1.87.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl/1+aUACgkQXkCM2RzY
OdLCjwgAhxeA9j817F6godyCAWxCpP9OeEHcsqX5vbRvrVx7JufpmtXNIK5h+FQE
HBj3erl+EDo+FXhaTeN8ZDrGr8pK/eRiQ4nc9XMNHE+rjesqbfXCnqu2V3Ff39NK
q1HmCtFOnLLUL4pj5JCnSEv9gKHKB1N5unAle7cPAiEeqX3dyWfvb1t+zjzbYimn
D8samJy/B5VYbBFUzIt/S89BMZ7mx89D/nDLCnO5yBg87ucu7v+//0hqI6VwRVuv
2rCEQhKa5niItAPzg4+oAndnLLNlVEOrtTa2K774TFfFG4M74NCM7UsDbxqGmxad
QNYZYr61ks9+BdsBx69vzfpH5zckvQ==
=Zftd
-END PGP SIGNATURE End Message ---
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug in torbrowser-launcher

[LinusMcFly42]

Hi all,

there ist a bug in torbrowser-launcher, actually 0.3.2-9 in ubuntu repositorys. 
i hope you know
about the bug, it breaks torbrowser while upgrading to version 10.0.
now, the maintainer of torbrowser-launcher fixed it in version 0.3.2-14 and 
uploaded it today
in debian backports-repository. here's the bug report 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970768
do you know when the patch is also available in ubuntu repositorys, to fix the 
bug with apt-get upgrade?

thanks in advance
Linus

Sent with [ProtonMail](https://protonmail.com) Secure Email.-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug in torbrowser-launcher

[Thomas Ward]

I am working on SRUing the fixes - patience please as it needs my eyes and also 
SRU team eyes for approvals.

⁣Get BlueMail for Android ​


 Original Message 
From: LinusMcFly42 
Sent: Fri Sep 25 14:55:13 EDT 2020
To: "ubuntu-devel-discuss@lists.ubuntu.com" 

Subject: Bug in torbrowser-launcher

Hi all,

there ist a bug in torbrowser-launcher, actually 0.3.2-9 in ubuntu repositorys. 
i hope you know
about the bug, it breaks torbrowser while upgrading to version 10.0.
now, the maintainer of torbrowser-launcher fixed it in version 0.3.2-14 and 
uploaded it today
in debian backports-repository. here's the bug report 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970768
do you know when the patch is also available in ubuntu repositorys, to fix the 
bug with apt-get upgrade?

thanks in advance
Linus

Sent with [ProtonMail](https://protonmail.com) Secure Email.



--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Audacity on Mint XFCE 19.3 - bug

[Robie Basak]

Hi,

On Tue, Mar 03, 2020 at 11:56:00AM +0100, Richard wrote:
> Audacity doesn't load on the above OS. Not sure how to post a bug report.

This should go to Mint community support channels in the first instance.

Alternatively if you can provide steps to reproduce and confirm they
still reproduce on Ubuntu itself (not Mint), then a bug report to Ubuntu
would also be appropriate.

HTH,

Robie


signature.asc
Description: PGP signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Audacity on Mint XFCE 19.3 - bug

[Richard]

Hello,

Audacity doesn't load on the above OS. Not sure how to post a bug report.


Best regards

--


/Richard /

Tél: 04 50 20 30 55
Mobile: 06 09 03 55 59

/Skype adresse: richardapalmer/

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug Reports - network-manager-openvpn-gnome

[Andreas Hasenack]

For network-manager-openvpn-gnome, use
https://launchpad.net/ubuntu/+source/network-manager-openvpn/+filebug

On Thu, Feb 27, 2020 at 1:15 PM Umair Ashraf  wrote:

> How can I report a bug in a package?
>
> Bug Reports
> <https://launchpad.net/distros/ubuntu/+source/network-manager-openvpn/+bugs>
> link is down.
>
> $ apt-cache policy network-manager-openvpn-gnome
>> network-manager-openvpn-gnome:
>>   Installed: 1.8.2-1
>>   Candidate: 1.8.2-1
>>   Version table:
>>  *** 1.8.2-1 500
>> 500 http://ca.archive.ubuntu.com/ubuntu bionic/universe amd64
>> Packages
>> 100 /var/lib/dpkg/status
>
>
> --
>
> --
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
>
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug Reports - network-manager-openvpn-gnome

[Umair Ashraf]

How can I report a bug in a package?

Bug Reports
<https://launchpad.net/distros/ubuntu/+source/network-manager-openvpn/+bugs>
link is down.

$ apt-cache policy network-manager-openvpn-gnome
> network-manager-openvpn-gnome:
>   Installed: 1.8.2-1
>   Candidate: 1.8.2-1
>   Version table:
>  *** 1.8.2-1 500
> 500 http://ca.archive.ubuntu.com/ubuntu bionic/universe amd64
> Packages
> 100 /var/lib/dpkg/status


--
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

fnfxd - new bug

[Łukasz Konieczny]

Hello.

I have filed a bug in fnfxd package here:

https://bugs.launchpad.net/ubuntu/+source/fnfx/+bug/1843416

Regards.

Łukasz Konieczny


--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug#935747: Removed package(s) from unstable

[Debian FTP Masters]

Version: 1.5.0+dfsg-0.1+rm

Dear submitter,

as the package choreonoid has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/935747

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug#874844: [choreonoid] Future Qt4 removal from Buster

[Reiner Herrmann]

Control: tags -1 + fixed-upstream

Qt5 is supported upstream since 1.5.0.


signature.asc
Description: PGP signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Very critical bug with GRUB-installer in UEFI on HP 250 G6 Notebook!!!

[Artyom Pozharov]

Hello, Ubuntu Developers. I noticed the critical error with GRUB-installer
package, if I use UEFI mode (but not BIOS-compability). Please, take
attention to it. Thank you for your support!
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1835664
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: grub2 package is still on version 2.02, although version 2.04 solves a big bug

[Colin Watson]

On Sat, Jul 13, 2019 at 12:51:11PM +0200, Oskar Roesler wrote:
> grub2 (and therefore, Ubuntu) can't be installed on some UEFIs because
> of this bug: http://wiki.linuxfromscratch.org/lfs/ticket/4354
> 
> The bugfix
> <http://git.savannah.gnu.org/cgit/grub.git/commit/util?id=842c390469e2c2e10b5aa36700324cd3bde25875>
> is already there for over a half year, but even though this bug is that
> big, you still have to build the fixed grub version manually.
> 
> Debian has version 2.04 still in sid, but I would consider to jump to
> 2.04 earlier, to make installing Ubuntu on those problematic UEFIs
> possible for unexperienced users again.

Upgrading stable releases to 2.04 is extremely unlikely, but the Ubuntu
grub2 maintainers can and do cherry-pick individual fixes instead.  I
suggest filing a bug against the Ubuntu grub2 package to request that.

-- 
Colin Watson   [cjwat...@ubuntu.com]

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

grub2 package is still on version 2.02, although version 2.04 solves a big bug

[Oskar Roesler]

Dear Maintainers,


grub2 (and therefore, Ubuntu) can't be installed on some UEFIs because
of this bug: http://wiki.linuxfromscratch.org/lfs/ticket/4354

The bugfix
<http://git.savannah.gnu.org/cgit/grub.git/commit/util?id=842c390469e2c2e10b5aa36700324cd3bde25875>
is already there for over a half year, but even though this bug is that
big, you still have to build the fixed grub version manually.

Debian has version 2.04 still in sid, but I would consider to jump to
2.04 earlier, to make installing Ubuntu on those problematic UEFIs
possible for unexperienced users again.


Regards,

Oskar Roesler



signature.asc
Description: OpenPGP digital signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Xen hypervisor patches for Intel MDS bug, XSA 297

[Wiebe Cazemier]

Hi,

I'm unsure what the fate of [1] should be. Upstream released patches for all 
minor versions, and Debian included a new upstream [2], albeit only in their 
unstable release.

Qemu is also 'universe' (partly?), so it's unclear to me why Qemu is patched, 
but Xen isn't. All required patches seem available.

Regards,

Wiebe



[1] https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1829550
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929129

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Kernel 3.13.0-166, -167 and -168 USB bug

[John Travell]

Hi,

Summary: USB keyboard and mouse non responsive at login
Product: Drivers
Version: 2.5
Kernel Version: 3.13.0-166-generic
Kernel Version: 3.13.0-167-generic
Kernel Version: 3.13.0-168-generic

USB keyboard and mouse stop working between 3.13.0-165 and 3.13.0-166
PS2 keyboard works, no PS2 mouse available to test.

First discovered on reboot after kernel update to latest offered by 
distro (3.13.0-167)
Reboot to prior version installed (3.13.0-160) restored functionality. 
All intermediate kernels tried, all versions up to 3.13.0-165 work OK.
3.13.0-166 is first version where USB KB/M non functional, same loss of 
functionality exists in  3.13.0-167 and 3.13.0-168.


Linux Mint 17.3, Intel Core2 Quad Q9450 on Asus P5Q-pro mainboard

How do I isolate more detail to help identify this bug?

Probably low priority as distro versions dependent on kernel 3.* going 
EOL soon.


John Travell

--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Processed (with 2 errors): fixing ftbfs bug metadata

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # reassign to source package
> reassign 790912 src:kcov
Bug #790912 [kcov] FTBFS: ld: CMakeFiles/kcov.dir/capabilities.cc.o .. 
recompile with -fPIC
Bug reassigned from package 'kcov' to 'src:kcov'.
No longer marked as found in versions kcov/25+dfsg-1.
Ignoring request to alter fixed versions of bug #790912 to the same values 
previously set
> # reassign to source package
> reassign 804369 src:netexpect
Bug #804369 [netexpect] netexpect: FTBFS with wireshark 2.0
Bug reassigned from package 'netexpect' to 'src:netexpect'.
No longer marked as found in versions netexpect/0.22-2.
Ignoring request to alter fixed versions of bug #804369 to the same values 
previously set
> # reassign to source package
> reassign 811639 src:choreonoid
Bug #811639 {Done: Dimitri John Ledkov } [choreonoid] FTBFS 
with GCC 6: multiple errors
Bug reassigned from package 'choreonoid' to 'src:choreonoid'.
No longer marked as found in versions choreonoid/1.1.0+dfsg-6.2.
No longer marked as fixed in versions choreonoid/1.5.0+dfsg-0.1.
> # reassign to source package
> reassign 811845 src:doscan
Bug #811845 [doscan] doscan: FTBFS with GCC 6: no match for
Bug reassigned from package 'doscan' to 'src:doscan'.
No longer marked as found in versions doscan/0.3.3-1.
Ignoring request to alter fixed versions of bug #811845 to the same values 
previously set
> # reassign to source package
> reassign 811887 src:duma
Bug #811887 [duma] duma: FTBFS with GCC 6: declaration of ... has a different 
exception specifier
Bug reassigned from package 'duma' to 'src:duma'.
No longer marked as found in versions duma/2.5.15-1.1.
Ignoring request to alter fixed versions of bug #811887 to the same values 
previously set
> # reassign to source package
> reassign 811896 src:src:percona-xtrabackup
Unknown command or malformed arguments to command.
> # reassign to source package
> reassign 811919 src:objcryst-fox
Bug #811919 [objcryst-fox] objcryst-fox: FTBFS with GCC 6: use of deleted 
function
Bug reassigned from package 'objcryst-fox' to 'src:objcryst-fox'.
No longer marked as found in versions objcryst-fox/1.9.6.0-2.1.
Ignoring request to alter fixed versions of bug #811919 to the same values 
previously set
> # reassign to source package
> reasign 811980 src:libusbtc08
Unknown command or malformed arguments to command.
> # reassign to source package
> reassign 812619 src:libtm-perl
Bug #812619 [libtm-perl] libtm-perl: FTBFS - Failed test 'assertions applying 
to identical topics are found'
Bug reassigned from package 'libtm-perl' to 'src:libtm-perl'.
No longer marked as found in versions libtm-perl/1.56-9 and libtm-perl/1.56-7.
Ignoring request to alter fixed versions of bug #812619 to the same values 
previously set
> # reassign to source package
> reassign 812704 src:nbibtex
Bug #812704 [nbibtex] nbibtex: FTBFS - nbib.dvi: file contents does not seem to 
settle
Bug reassigned from package 'nbibtex' to 'src:nbibtex'.
No longer marked as found in versions nbibtex/0.9.18-11.
Ignoring request to alter fixed versions of bug #812704 to the same values 
previously set
> # reassign to source package
> reassign 826473 src:kdesrc-build
Bug #826473 [kdesrc-build] kdesrc-build: FTBFS with Perl 5.26: Unescaped left 
brace in regex is deprecated
Bug reassigned from package 'kdesrc-build' to 'src:kdesrc-build'.
No longer marked as found in versions kdesrc-build/1.15.1-1.
Ignoring request to alter fixed versions of bug #826473 to the same values 
previously set
> # reassign to source package
> reassign 861550 src:docker-swarm
Bug #861550 [docker-swarm] docker-swarm: FTBFS with latest golang-go.crypto
Bug reassigned from package 'docker-swarm' to 'src:docker-swarm'.
No longer marked as found in versions docker-swarm/1.2.5+dfsg-2.
Ignoring request to alter fixed versions of bug #861550 to the same values 
previously set
> # reassign to source package
> reassign 881897 src:mosh
Bug #881897 [mosh] Please avoid the unconditional locales build-dependency to 
support cross-building
Bug reassigned from package 'mosh' to 'src:mosh'.
No longer marked as found in versions mosh/1.3.2-2.
Ignoring request to alter fixed versions of bug #881897 to the same values 
previously set
> # reassign to source package
> reassign 883525 src:pdf2htmlex
Bug #883525 [pdf2htmlex] pdf2htmlex: FTBFS with poppler 0.61.1
Bug reassigned from package 'pdf2htmlex' to 'src:pdf2htmlex'.
No longer marked as found in versions pdf2htmlex/0.14.6+ds-3.
Ignoring request to alter fixed versions of bug #883525 to the same values 
previously set
> # missing affects
> affects 891394 + src:src:kannel-sqlbox src:libdbi-drivers src:opensp 
> src:pgpool2 src:plr src:slony1-2 src:gtkextra
Bug #891394 [libostyle1c2] multiarchify libostyle1c2
Added indication that 891394 affects src:src:kannel-sqlbox, src:libdbi-drivers, 
src:opensp, src:pgpool2, src:plr, src:slony1-2, and src:gtk

Re: anyone still use 'import-bug-from-debian'?

[Dimitri John Ledkov]

On Wed, 13 Feb 2019 at 13:42, Dan Streetman  wrote:
>
> As far as I can tell, this hasn't been used by anyone in a long time,
> or at least only a small number of times.
>
> Can anyone who uses it let me know?
>

I used to use it, but last few times I have tried to do it, it either
failed to open the bug report, or it was incomplete - as in, it didn't
copy the body of the bug as it used to. At the time, I did not have
time to dig into the import-bug-from-debian code to fix it up.

I'd use it more, if it's known to work again.

-- 
Regards,

Dimitri.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: anyone still use 'import-bug-from-debian'?

[Dan Streetman]

On Wed, Feb 13, 2019 at 10:04 AM Colin Watson  wrote:
>
> On Wed, Feb 13, 2019 at 08:40:39AM -0500, Dan Streetman wrote:
> > As far as I can tell, this hasn't been used by anyone in a long time,
> > or at least only a small number of times.
> >
> > Can anyone who uses it let me know?
>
> If it's helpful, there are 409 bugs in Launchpad whose description
> starts with the string "Imported from Debian bug"; the most recent one
> (https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1694425) was

Yeah, the most recent i found was
https://bugs.launchpad.net/ubuntu/+source/freevo/+bug/1699078
which is also from 2017.

I asked for comments from users since I'm overhauling u-d-t and
noticed it did not seem to be getting used by anyone.

> created on 2017-05-30.  It was quite heavily used up to 2015 or so; my
> general impression is that it's a slightly obscure tool so not widely
> used, but probably used enough to justify keeping it around.
>
> --
> Colin Watson   [cjwat...@ubuntu.com]
>
> --
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: anyone still use 'import-bug-from-debian'?

[Colin Watson]

On Wed, Feb 13, 2019 at 08:40:39AM -0500, Dan Streetman wrote:
> As far as I can tell, this hasn't been used by anyone in a long time,
> or at least only a small number of times.
> 
> Can anyone who uses it let me know?

If it's helpful, there are 409 bugs in Launchpad whose description
starts with the string "Imported from Debian bug"; the most recent one
(https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1694425) was
created on 2017-05-30.  It was quite heavily used up to 2015 or so; my
general impression is that it's a slightly obscure tool so not widely
used, but probably used enough to justify keeping it around.

-- 
Colin Watson   [cjwat...@ubuntu.com]

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

anyone still use 'import-bug-from-debian'?

[Dan Streetman]

As far as I can tell, this hasn't been used by anyone in a long time,
or at least only a small number of times.

Can anyone who uses it let me know?

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug 1781699 DHCPv6 server crashes regularly (bionic)

[Steffen Sledz]

Hi Debian/Ubuntu isc-dhcp-server maintainers,

when will be a fix for 
<https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1781699> available?

It is pending for some weeks. :(

This is really a critical bug in the Debian/Ubuntu network infrastructure.

Thx,
Steffen


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: No localization available for Thunderbird Lightning (open bug since early 2010!)

[Rolando Gorgs]

I probably used the wrong words. The Thunderbird people are well aware of
this mess (and there are several closed bug reports on this topic over at
Bugzilla) but they stated that Thunderbird is ok but the ubuntu package for
thunderbird is broken and has to be fixed by its maintainer. The thing is
... 'ubuntu core developer mailing list' is listed as the 'maintainer' of
Thunderbird package: https://packages.ubuntu.com/bionic/thunderbird

But the fact, that this bug (
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/545778) is
ignored for so many years now brings me to the conclusion that nobody cares
for this package anymore. So is there any person who is responsible for
this package and is able to fix it? Or will Thunderbird translation be
broken forever? ;-(

Regards
 Rolando
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: No localization available for Thunderbird Lightning (open bug since early 2010!)

[Joe]

Don't know about localizations, but For Thunderbird bugs:

https://bugzilla.mozilla.org/

Joe

On 12/29/18 11:13 PM, Rolando Gorgs wrote:
> Hello everybody!
>
> I hope you all had a nice Christmas.
> As I don't see any progress regarding this topic for one month now -
> here and on Launchpad - I assume that this mailing list was the wrong
> place to ask. Would anyone please point me to the right go-to
> direction for Thunderbird bugs or in general broken translations in
> Ubuntu? Thanks a lot for your help!
>
> Regards
> Rolando Gorgs
>
> Am Fr., 30. Nov. 2018 um 01:40 Uhr schrieb Rolando Gorgs
> mailto:rolando.go...@gmail.com>>:
>
> Hello together,
>
> this is my first mail on this list because I don't want to
> escalate 'small' things that could better be solved within
> launchpad, but I really think this very long lasting bug should be
> brought to your attention:
>
> https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/545778
>
> Since I remember the localization of Lightning - the Thunderbird
> Calendar - in Ubuntu is broken (better to say: not present). In
> Ubuntu wikis all over the world the recommended (dirty) workaround
> has ever been to avoid the official xul-ext-lightning package and
> instead install Lightning via Thunderbird Addon functionality.
>
> This workaround often caused problems in the past because the
> Lightning versions provided by Thunderbird Addons and the
> installed Thunderbird from ubuntu packages didn't fit together.
>
> Some months ago the Thunderbird people finally decided to
> distribute lightning (and its localization) as integrated part of
> their official downloadable thunderbird install package. Because
> of this they stopped the distribution of separate lightning
> packages via Addons.
>
> At this time there is no practical way to have Thunderbird +
> Lightning completely translated in Ubuntu! The thunderbird
> localization of ubuntu doesn't include lightning translation and
> xul-ext-lightning has no localization too. The only way to get a
> working and localized Lightning is to download the official
> Thunderbird package from www.thunderbird.net
> <http://www.thunderbird.net>, extract the installer and copy the
> included (translated) lightning addon into the right sub folder of
> your own thunderbird. (And those steps have to be repeated
> manually for every new Thunderbird/Lightning version!)
>
> Please (PLEASE) find a solution for this. The bugreport I linked
> above is nearly nine years old but the problem itself exists even
> longer. I don't see any progress here and I think this is due to
> misunderstanding and confusion where the localization of lightning
> has to take place. In my opinion the best solution would be to
> integrate lightning completely into the ubuntu thunderbird package
> as the Thunderbird people did and then provide the translation as
> part of thunderbird localization. But I'm neither developer nor
> package maintainer. Perhaps a separate xul-ext-lightning +
> separate localization is the better way. But please do something! :-)
>
> Thanks for time and your attention!
>
> Golando Gorgs
>
>

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: No localization available for Thunderbird Lightning (open bug since early 2010!)

[Rolando Gorgs]

Hello everybody!

I hope you all had a nice Christmas.
As I don't see any progress regarding this topic for one month now - here
and on Launchpad - I assume that this mailing list was the wrong place to
ask. Would anyone please point me to the right go-to direction for
Thunderbird bugs or in general broken translations in Ubuntu? Thanks a lot
for your help!

Regards
Rolando Gorgs

Am Fr., 30. Nov. 2018 um 01:40 Uhr schrieb Rolando Gorgs <
rolando.go...@gmail.com>:

> Hello together,
>
> this is my first mail on this list because I don't want to escalate
> 'small' things that could better be solved within launchpad, but I really
> think this very long lasting bug should be brought to your attention:
>
> https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/545778
>
> Since I remember the localization of Lightning - the Thunderbird Calendar
> - in Ubuntu is broken (better to say: not present). In Ubuntu wikis all
> over the world the recommended (dirty) workaround has ever been to avoid
> the official xul-ext-lightning package and instead install Lightning via
> Thunderbird Addon functionality.
>
> This workaround often caused problems in the past because the Lightning
> versions provided by Thunderbird Addons and the installed Thunderbird from
> ubuntu packages didn't fit together.
>
> Some months ago the Thunderbird people finally decided to distribute
> lightning (and its localization) as integrated part of their official
> downloadable thunderbird install package. Because of this they stopped the
> distribution of separate lightning packages via Addons.
>
> At this time there is no practical way to have Thunderbird + Lightning
> completely translated in Ubuntu! The thunderbird localization of ubuntu
> doesn't include lightning translation and xul-ext-lightning has no
> localization too. The only way to get a working and localized Lightning is
> to download the official Thunderbird package from www.thunderbird.net,
> extract the installer and copy the included (translated) lightning addon
> into the right sub folder of your own thunderbird. (And those steps have to
> be repeated manually for every new Thunderbird/Lightning version!)
>
> Please (PLEASE) find a solution for this. The bugreport I linked above is
> nearly nine years old but the problem itself exists even longer. I don't
> see any progress here and I think this is due to misunderstanding and
> confusion where the localization of lightning has to take place. In my
> opinion the best solution would be to integrate lightning completely into
> the ubuntu thunderbird package as the Thunderbird people did and then
> provide the translation as part of thunderbird localization. But I'm
> neither developer nor package maintainer. Perhaps a separate
> xul-ext-lightning + separate localization is the better way. But please do
> something! :-)
>
> Thanks for time and your attention!
>
> Golando Gorgs
>
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

No localization available for Thunderbird Lightning (open bug since early 2010!)

[Rolando Gorgs]

Hello together,

this is my first mail on this list because I don't want to escalate 'small'
things that could better be solved within launchpad, but I really think
this very long lasting bug should be brought to your attention:

https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/545778

Since I remember the localization of Lightning - the Thunderbird Calendar -
in Ubuntu is broken (better to say: not present). In Ubuntu wikis all over
the world the recommended (dirty) workaround has ever been to avoid the
official xul-ext-lightning package and instead install Lightning via
Thunderbird Addon functionality.

This workaround often caused problems in the past because the Lightning
versions provided by Thunderbird Addons and the installed Thunderbird from
ubuntu packages didn't fit together.

Some months ago the Thunderbird people finally decided to distribute
lightning (and its localization) as integrated part of their official
downloadable thunderbird install package. Because of this they stopped the
distribution of separate lightning packages via Addons.

At this time there is no practical way to have Thunderbird + Lightning
completely translated in Ubuntu! The thunderbird localization of ubuntu
doesn't include lightning translation and xul-ext-lightning has no
localization too. The only way to get a working and localized Lightning is
to download the official Thunderbird package from www.thunderbird.net,
extract the installer and copy the included (translated) lightning addon
into the right sub folder of your own thunderbird. (And those steps have to
be repeated manually for every new Thunderbird/Lightning version!)

Please (PLEASE) find a solution for this. The bugreport I linked above is
nearly nine years old but the problem itself exists even longer. I don't
see any progress here and I think this is due to misunderstanding and
confusion where the localization of lightning has to take place. In my
opinion the best solution would be to integrate lightning completely into
the ubuntu thunderbird package as the Thunderbird people did and then
provide the translation as part of thunderbird localization. But I'm
neither developer nor package maintainer. Perhaps a separate
xul-ext-lightning + separate localization is the better way. But please do
something! :-)

Thanks for time and your attention!

Golando Gorgs
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

bug reporter broken

[contactopublico57]

Attempting to initiate bug report here: 
 https://login.launchpad.net/EmWfYtHa6XonNhcn/+decide
 
shows message: Invalid OpenID transaction
 
Third notice:  booting ubuntu-mate live iso to desktop with grub2, mate panel shows message 'no indicators'. There are no indicators for network, battery nor sound.  
 
How can I file a bug report if the link to bug reporter shows message: Invalid OpenID transaction?
 
 
 
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

network-manager-openconnect-gnome annoying bug

[Yuriy Pitometsu]

Hello there!

One bug some time ago reported here
https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1764047
Any information about actual maintainers of this (issue tracker, source
repository)?



-- 
*With best regards,*
*Yuriy Pitomets*
Haskell developer *|* Strong solution
For beautiful ideas[image: I'm a Haskeller]
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

[fix included] found bug package in xdg-utils

[Michael Hass]

found bug in package in xdg-utils:

apt-cache policy xdg-utils
xdg-utils:
  Installiert:   1.1.2-1ubuntu2.2
  Installationskandidat: 1.1.2-1ubuntu2.2
  Versionstabelle:
 *** 1.1.2-1ubuntu2.2 500
    500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main
amd64 Packages
    500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main i386
Packages
    500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
    500 http://security.ubuntu.com/ubuntu bionic-security/main i386
Packages
    100 /var/lib/dpkg/status
 1.1.2-1ubuntu2 500
    500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
    500 http://de.archive.ubuntu.com/ubuntu bionic/main i386 Packages


--> procedure:
root:/xdg-mime query default inode/directory
/usr/bin/xdg-mime: 946: local: icewm-: bad variable name

Line 946 of  /usr/bin/xdg-mime shows:
local prefix=$(echo "$desktop-" | tr '[:upper:]' '[:lower:]')

the "-" at the end of $desktop is wrong.

If you take it away to get
local prefix=$(echo "$desktop" | tr '[:upper:]' '[:lower:]')

Everything works fine again:
root:/xdg-mime query default inode/directory
nautilus-folder-handler.desktop





--
Mit freundlichen Grüßen

i. A. Michael Hass
Systemadministrator

*critical care *
Kirchhoffstraße 1-5
24568 Kaltenkirchen
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Julian Andres Klode]

On Thu, May 10, 2018 at 03:19:13PM +, Shawn Landden wrote:
> I re-wrote command-not-found in C. It consists of two C programs:
> command-not-found, which gets triggered by bash, and
> update-command-not-found, which digests the data obtained with apt-file
> update.
> 
> AFAIK there is only one rough edge, in that the parsing of
> /etc/apt/sources.list is not the same as apt's parsing. I do not know
> enough C++ to use libapt to do this.
> 
> https://github.com/shawnl/command-not-found/

We know. We're not sure entirely where to go yet, given that
we also need snaps and stuff in c-n-f.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

BUG in default video player

[vini gambhir]

Hello everyone!
I am new to Ubuntu and have already fallen in love with it.
I found one issue not particularly of Ubuntu's default Videos App worth to
be addressed. If my 'Videos' player is active in the task bar and I play
another video from the documents, the video player doesn't pops up and the
video starts playing while I am still on the documents page.
If there exists some functionality to deal with this, I would be glad to be
informed:)
Please do not recommend other awesome video players, I hope the default one
gets rectified.
Thanks,
Varshika.
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug Network Installer Artful

[Olnei]

Hello everyone!

In an installation of Artful via Network Installer, in the selection of
packages, when I select the vanilla-gnome-desktop package to install, the
meta-package is not installed on Ubuntu 17.10. Is it possible to correct
for 18.04?
Thanks!


Olnei A Araujo
Comunidade ubuntu-br
Revisor voluntário da Revista LibreOffice Magazine
http://wiki.ubuntu-br/InstalacaoUbuntu
http://ubuntu.com
Comunidade Brasileira LibreOffice
pt-br.libreoffice.org
31-987120747
twitter:@olneiaa
linux user # 484050
ubuntu user # 26374-2007
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models - Bug #1734147

[Xen]

Oh Ralf,

Ralf Mardorf schreef op 28-11-2017 19:22:


I'm not a developer, however, consider to explain what makes you think
that this is an Ubuntu related bug.


On 28th of November this user reported this bug to this list. It had 
already been reported a few days prior.


On 29th of November I questioned why people were not getting informed.

On 19th of December Canonical confirmed it was a bug caused by an 
(Ubuntu) kernel and removed the download link from the website after 
they had basically already completely discovered both the issue and the 
fix.


For 20 days users were exposed to a risk that may not have completely 
destroyed their laptops, but surely caused some of them to return it to 
Lenovo and caused others to spend money on repairs.


--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#885104: SystemTap out of date and no longer functions

[Ritesh Raj Sarraf]

Please file Ubuntu bugs in Ubuntu's tracker.

s3nt fr0m a $martph0ne, excuse typ0s

On 24-Dec-2017 2:51 AM, "Farhan Khan"  wrote:

Package: systemtap
Priority: optional
Section: devel
Installed-Size: 2741
Maintainer: Ubuntu Developers 
Architecture: amd64
Version: 2.9-2ubuntu2
Depends: systemtap-runtime (= 2.9-2ubuntu2), libavahi-client3 (>= 0.6.16),
libavahi-common3 (>= 0.6.16), libc6 (>= 2.15), libdw1 (>= 0.158), libelf1
(>= 0.142), libgcc1 (>= 1:3.0), libnspr4 (>= 2:4.9-2~) | libnspr4-0d (>=
1.8.0.10), libnss3 (>= 2:3.13.4-2~) | libnss3-1d (>= 3.12.6), libsqlite3-0
(>= 3.5.9), libstdc++6 (>= 5.2), systemtap-common (= 2.9-2ubuntu2), make

SystemTap works by producing a new kernel module source, compiling the
module and installing it. The current version of systemtap uses an
extremely old series of kernel sources that do not work against Kernel
4.x.x. As a result, systemtap does not work AT ALL and will always produce
error messages.

For example:

$ sudo stap -l 'kernel.function("*")'
Tip: /usr/share/doc/systemtap/README.Debian should help you get started.

The only solution is to upgrade to the latest version of systemtap.
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models - Bug #1734147

[Xen]

Ralf Mardorf schreef op 29-11-2017 6:15:


3. Google also might help to report the bug to those responsible for
it. Maybe Ubuntu isn't the culprit.


The point that I'm trying to make is that even if it is simply a kernel 
issue not specific to Ubuntu, to the user Ubuntu is Ubuntu.


Also if these few inexperienced users manage to get their... somehow 
discover or learn to understand...


Or even solve it.

Everyone else who hasn't fallen into the trap yet will not.

You cannot expect inexperienced computer USERS to know AHEAD OF TIME 
what to look out for.


If you are also not going to broadcast this, I mean publicise this.

Then new people will walk into it time and time again.

At minimum there must be an advisory on the public download site not to 
use Ubuntu 17.10 with those laptops.


I mean like, are you going to inform anyone?

--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models - Bug #1734147

[Xen]

Ralf Mardorf schreef op 29-11-2017 6:15:


1. Before I bought my new mobo, I ensured that it doesn't force me to
use U/EFI/secure boot, to avoid all the known issues.


Can you tell me how Windows... I could look it up, but I have used.. or 
maybe I haven't... All I' m saying is that I am running Windows 10 
non-UEFI.



Perhaps the OP's
laptop allows this, too, so getting rid of an operating system 
enforcing

its usage, repairing the laptop and then reinstalling Ubuntu or any
other Linux distro without U/EFI/secure boot might be a solution.


Probably except that none of them can repair it, a few seem to be 
capable of reflashing the BIOS, a lone person basically desoldered the 
chip and reflashed it.


My own motherboard has issues with USB since booting Linux that seem to 
be persistent.


Ie. all of my smaller cq. cheaper hubs have stopped working all at once.

This isn't a pure Linux issue for me but Linux definitely aggravates it 
and it's really troublesome that I can't use any hubs at a distance.


My USB modem will work on 2 ports of a USB 3 card, but not on the 
internal port, while another device works on it just fine. But I'm sure 
in Windows, it does work on the internal port.


I was in a live session... played with a KVM switch... monitor went into 
standby... (16.04) -- no keyboard or mouse still worked and I lost the 
document I had been writing, and since it doesn't install an SSH server 
by default I couldn't retrieve it otherwise.


That was a good document too.

Why not use USB to store it? Well the stick I ought to use for that had 
issues with another motherboard where it would no longer work after 
rebooting from Linux, so I am fearful of using it.


That is to say, I wanted to get rid of it already etc...

Why write in a live sesion? LVM destroyed my system again after I merged 
a disconnected cache pool expecting it, a cache volume expecting it to 
clean its own metadata before reconnecting.


Until the LVM in Zesty I believe it seriously will... it will not clean 
the cache before connecting it.


Why am I still on 16.04? Well the last time... The last time LVM 
destroyed my system because I had dd'd a harddisk and ran "lvs" after 
that, and the LVM from Xenial will take the chance to happily...








2. Complete the Ubuntu bug report. Google might help you. Since the bug
report is flagged as being incomplete, the OP much likely already got
an email with hints, what is missing to complete it.


These were inexperienced users that saw their Laptop bricked.

I watched one bug report and there was no one actually asking for more 
info.



3. Google also might help to report the bug to those responsible for
it. Maybe Ubuntu isn't the culprit.


Ubuntu is the representative of its own system.

--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models - Bug #1734147

[Ralf ranfyy]

Ralf Mardorf <ralf.mard...@alice-dsl.net> schrieb am Mi., 29. Nov. 2017 um
06:16 Uhr:

>
> Hi,
>
> no, if you read the complete mail, you should notice that it does say
> three things.
>
> 1. Before I bought my new mobo, I ensured that it doesn't force me to
> use U/EFI/secure boot, to avoid all the known issues. Perhaps the OP's
> laptop allows this, too, so getting rid of an operating system enforcing
> its usage, repairing the laptop and then reinstalling Ubuntu or any
> other Linux distro without U/EFI/secure boot might be a solution.
>
> 2. Complete the Ubuntu bug report. Google might help you. Since the bug
> report is flagged as being incomplete, the OP much likely already got
> an email with hints, what is missing to complete it.
>
> 3. Google also might help to report the bug to those responsible for
> it. Maybe Ubuntu isn't the culprit.
>
> Regards,
> Ralf
>
>
just a quick FYI:
  https://youtu.be/iffTJ1vPCSo

Article in German:

https://www.golem.de/news/freie-linux-firmware-google-will-server-ohne-intel-me-und-uefi-1710-130840.html

-- 
http://ranfs.de
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models - Bug #1734147

[Ralf Mardorf]

On Tue, 28 Nov 2017 20:35:17 +0100, Xen wrote:
>Ralf Mardorf schreef op 28-11-2017 19:22:
>
>> There are far more known issues, Google is your friend. I doubt that
>> you will find a lot, if any known issues caused by Linux
>> distribution, but there are a vast number of known issues, that are
>> not caused by Linux distros.  
>
>Doesn't help the person now does it.
>
>What you say means "Suck it up."

Hi,

no, if you read the complete mail, you should notice that it does say
three things.

1. Before I bought my new mobo, I ensured that it doesn't force me to
use U/EFI/secure boot, to avoid all the known issues. Perhaps the OP's
laptop allows this, too, so getting rid of an operating system enforcing
its usage, repairing the laptop and then reinstalling Ubuntu or any
other Linux distro without U/EFI/secure boot might be a solution.

2. Complete the Ubuntu bug report. Google might help you. Since the bug
report is flagged as being incomplete, the OP much likely already got
an email with hints, what is missing to complete it.

3. Google also might help to report the bug to those responsible for
it. Maybe Ubuntu isn't the culprit.

Regards,
Ralf

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models - Bug #1734147

[Xen]

Ralf Mardorf schreef op 28-11-2017 19:22:


There are far more known issues, Google is your friend. I doubt that
you will find a lot, if any known issues caused by Linux distribution,
but there are a vast number of known issues, that are not caused by
Linux distros.


Doesn't help the person now does it.

What you say means "Suck it up."

--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Fwd: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models - Bug #1734147

[Xen]

I see the EFI fun has begun.

Not predictable at all of course.

Tobia schreef op 28-11-2017 12:06:

UBUNTU 17.10 CORRUPTING BIOS - MANY LENOVO LAPTOPS MODELS - BUG 
#1734147


All of us affected cannot use their PCs anymore.

Best regards,

Tobia Antoniolli


--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models - Bug #1734147

[Ralf Mardorf]

On Tue, 28 Nov 2017 12:06:19 +0100, Tobia wrote:
>I know that you are extremely busy I would like to report this bug
>since it's very, very serious and I do not know if you already know
>this issue.
>
>Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models - Bug
>#1734147
>
>All of us affected cannot use their PCs anymore.

Hi,

I'm not a developer, however, consider to explain what makes you think
that this is an Ubuntu related bug. At least consider to provide a
proper bug report.

For good reasons
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1734147 is falgged
as "Incomplete".

I'm to lazy to do all the googling for you, since I don't use all this
EFI crap, I did it nearly a year ago, before I bought my new desktop
computer, too avoid issues.

However, for example did you read the Wiki?

"Firmware issues

The increased prominence of UEFI firmware in devices has also led to a
number of technical issues blamed on their respective
implementations.[114]

Following the release of Windows 8 in late 2012, it was discovered that
certain Lenovo computer models with secure boot had firmware that was
hardcoded to allow only executables named "Windows Boot Manager" or
"Red Hat Enterprise Linux" to load, regardless of any other
setting.[115] Other issues were encountered by several Toshiba laptop
models with secure boot that were missing certain certificates required
for its proper operation.[114]

In January 2013, a bug surrounding the UEFI implementation on some
Samsung laptops was publicized, which caused them to be bricked after
installing a Linux distribution in UEFI mode. While potential conflicts
with a kernel module designed to access system features on Samsung
laptops were initially blamed (also prompting kernel maintainers to
disable the module on UEFI systems as a safety measure), Matthew
Garrett discovered that the bug was actually triggered by storing too
many UEFI variables to memory, and that the bug could also be triggered
under Windows under certain conditions. In conclusion, he determined
that the offending kernel module had caused kernel message dumps to be
written to the firmware, thus triggering the bug.[37][116][117]"

https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Firmware_issues

There are far more known issues, Google is your friend. I doubt that
you will find a lot, if any known issues caused by Linux distribution,
but there are a vast number of known issues, that are not caused by
Linux distros.

Regards,
Ralf

Regards,
Ralf
-- 
$ pacman -Q linux{,-rt{,-cornflower,-pussytoes}}|awk '{print $2}'
4.14-2
4.13.13_rt5-1
4.11.12_rt16-1
4.14_rt1-1

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Fwd: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models - Bug #1734147

[Tobia]

Hello guys,
I know that you are extremely busy I would like to report this bug since
it's very, very serious and I do not know if you already know this issue.

Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models - Bug #1734147

All of us affected cannot use their PCs anymore.

Thank you,

Best regards,

Tobia Antoniolli
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Shawn Landden]

On Mon, Nov 13, 2017 at 11:50 PM, Julian Andres Klode  wrote:
> (forwarding this to ubuntu-devel-discuss and Zygmunt)
>
> On Mon, Nov 13, 2017 at 10:33:39PM -0800, Shawn Landden wrote:
>> Package: command-not-found
>> Severity: wishlist
>>
>> I re-wrote command-not-found to get rid of the python dependancy, and
>> to reduce the database size, as to reduce memory usage.
>>
>> https://github.com/shawnl/command-not-found
>>
>> I was preparing to upload it to mentors as command-not-found-ng
>
> I also rewrote it years ago, but using the same database format,
> just in C. It was a lot faster. I don't understand the memory usage
> bit - it should not matter how large the database is, it's memory
> mapped, and not read into memory, as such memory usage should be
> roughly constant.
>
> Questions/Comments for your approach:
>
> * Did you test your format on a slow HDD with caches dropped? It
>   must not be slower than the Python one (that one is way too slow
>   already) - I did, it seems to be faster (0.4 vs 0.68 seconds)
>   - I believe the database-based C rewrite was even much faster,
>   though.
I switched it to mmap() and am now getting 0.27-0.45 with caches
dropped, even after adding translations. It is 100% C and sh. (same
postinst and postrm)

Ping.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Shawn Landden]

>
>
> Ruby is just a major no go.

Re-written in C.

And in the future, what about Lua? It is only 300KB.

> At that system level, the best choices
> are Perl, Shell, and C++. Maybe Python (on Ubuntu it's in ubuntu-minimal,
> but in Debian it's only used by standard priority and less, perl on the
> other hand is required and essential). Ruby has the lowest priority
> - optional.
>
> --
> Debian Developer - deb.li/jak | jak-linux.org - free software dev
> Ubuntu Core Developer  de, en speaker
>
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Julian Andres Klode]

On Thu, Nov 16, 2017 at 11:55:07PM -0800, Shawn Landden wrote:
> On Thu, Nov 16, 2017 at 11:39 PM, Xen  wrote:
> 
> > Julian Andres Klode schreef op 14-11-2017 8:50:
> >
> > * You should not depend on grep, sed, coreutils, they are Essential.
> >>
> >
> > Can I ask what this means?
> >
> > I actually assume that these dependencies are not *required*, not that you
> > can't use the tools.
> 
> Required: yes. The highest priority. sysvinit was Required: yes until
> systemd came along https://www.debian.org/doc/debian-policy/#priorities

What it actually means is that you don't have to declare them in Depends
fields. And required is a priority, that's distinct. Essential basically
is the set of packages dpkg needs for its own operation.

> 
> Speaking of, I can't use 'apt-get indextargets' from shell and had to
> rewrite in ruby, because sed doesn't not support lazy matching, and I don't
> know how else to match NOT \n\n. (it also doesn't seem to support multiples
> of submatches.) Old regular expression implementations are showing their
> age (not to mention perl's non-regular features).

Ruby is just a major no go. At that system level, the best choices
are Perl, Shell, and C++. Maybe Python (on Ubuntu it's in ubuntu-minimal,
but in Debian it's only used by standard priority and less, perl on the
other hand is required and essential). Ruby has the lowest priority
- optional.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
Ubuntu Core Developer  de, en speaker

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Xen]

Shawn Landden schreef op 17-11-2017 8:55:


On Thu, Nov 16, 2017 at 11:39 PM, Xen  wrote:
Julian Andres Klode schreef op 14-11-2017 8:50:

* You should not depend on grep, sed, coreutils, they are Essential. 
Can I ask what this means?


I actually assume that these dependencies are not *required*, not that 
you can't use the tools.


Required: yes. The highest priority. sysvinit was Required: yes until 
systemd came along https://www.debian.org/doc/debian-policy/#priorities


--

What I mean is that since they are already on a system you don't have to 
require them.


"Packages are not required to declare any dependencies they have on 
other packages which are marked Essential (see below), and should not do 
so unless they depend on a particular version of that package. [4]"


From the same document.


As to sed, yeah it has issue with multi-line matching anyway.

Some people use perl to achieve the same.

--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Shawn Landden]

On Thu, Nov 16, 2017 at 11:39 PM, Xen  wrote:

> Julian Andres Klode schreef op 14-11-2017 8:50:
>
> * You should not depend on grep, sed, coreutils, they are Essential.
>>
>
> Can I ask what this means?
>
> I actually assume that these dependencies are not *required*, not that you
> can't use the tools.

Required: yes. The highest priority. sysvinit was Required: yes until
systemd came along https://www.debian.org/doc/debian-policy/#priorities

Speaking of, I can't use 'apt-get indextargets' from shell and had to
rewrite in ruby, because sed doesn't not support lazy matching, and I don't
know how else to match NOT \n\n. (it also doesn't seem to support multiples
of submatches.) Old regular expression implementations are showing their
age (not to mention perl's non-regular features).
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Xen]

Julian Andres Klode schreef op 14-11-2017 8:50:


* You should not depend on grep, sed, coreutils, they are Essential.


Can I ask what this means?

I actually assume that these dependencies are not *required*, not that 
you can't use the tools.


--
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Shawn Landden]

On Thu, Nov 16, 2017 at 6:44 PM, Colin Watson  wrote:

> On Thu, Nov 16, 2017 at 05:10:19PM -0800, Shawn Landden wrote:
> > On Mon, Nov 13, 2017 at 11:50 PM, Julian Andres Klode 
> > wrote:
> > > * It needs to be translated - also very important.
> >
> > I made a pot file and used translations from the python version, but I
> > can't get my app to look for translations (as examined through strace). I
> > read the gettext manual and do not know what I am doing wrong.
>
> Looking at
> https://github.com/shawnl/command-not-found/blob/master/
> command-not-found.c,
> your problem appears to be that you aren't calling setlocale().  You
> should normally call this before calling bindtextdomain() and
> textdomain():
>
>   setlocale(LC_ALL, "");
>
> (The gettext manual does cover this, but possibly you were looking at
> some different bit of it.)
>
Managed to re-use all the translations from launchpad of the existing
command-not-found.

>
> --
> Colin Watson   [cjwat...@ubuntu.com]
>
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Colin Watson]

On Thu, Nov 16, 2017 at 05:10:19PM -0800, Shawn Landden wrote:
> On Mon, Nov 13, 2017 at 11:50 PM, Julian Andres Klode 
> wrote:
> > * It needs to be translated - also very important.
> 
> I made a pot file and used translations from the python version, but I
> can't get my app to look for translations (as examined through strace). I
> read the gettext manual and do not know what I am doing wrong.

Looking at
https://github.com/shawnl/command-not-found/blob/master/command-not-found.c,
your problem appears to be that you aren't calling setlocale().  You
should normally call this before calling bindtextdomain() and
textdomain():

  setlocale(LC_ALL, "");

(The gettext manual does cover this, but possibly you were looking at
some different bit of it.)

-- 
Colin Watson   [cjwat...@ubuntu.com]

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Shawn Landden]

> * Did you test your format on a slow HDD with caches dropped? It
>>   must not be slower than the Python one (that one is way too slow
>>   already) - I did, it seems to be faster (0.4 vs 0.68 seconds)
>>   - I believe the database-based C rewrite was even much faster,
>>   though
>>
> I tested with kyotocabinet backend and it was slower with dropped caches
on a hard drive (1 second), which is the slow case I am most concerned
with. Small  makes a difference. The code is at
https://github.com/shawnl/command-not-found/tree/kyotocabinet
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Shawn Landden]

On Nov 14, 2017 8:15 AM, "Julian Andres Klode"  wrote:

On Tue, Nov 14, 2017 at 03:35:02PM +, John Lenton wrote:
> On 14 November 2017 at 12:34, Julian Andres Klode  wrote:
> > On Tue, Nov 14, 2017 at 01:00:54PM +0100, Zygmunt Krynicki wrote:
> >> I would love if we have a compact representation of mapping from name
> >> to list of bits of information where each bit can be a small structure
> >> with some data. Apart from components for ubuntu archive it could be
> >> used to store facts about snap packages, flatpaks, etc. I would try to
> >> avoid a simplistic command -> package mapping as that will force us to
> >> encode things into strings in an ad-hoc way.
> >
> > That makes sense to me. But then we're back on a db, I guess. I sort
> > like this minimal approach.
>
> I was thinking in the other direction, was going to see how it behaved
> with sqlite as the store. Would that be objectionable?

Using a relational database for a simple key -> structure mapping seems
overkill and a mismatch for the problem, and the SQL does not make it
more readable.

I'd play with lmdb and kyotocabinet, these are two high-performance
key-value file databases and then encode a structure as mentioned
before.

I had some kyotocabinet code, (i maintain that package, which btw is in
mentors) but this way is at least half the size. (Kyotocabinet is 1mb and
it almost doubles the size of the db, even using lower overhead b-tree back
end. These entries are just very small.

For the text file approach, we can even go human, readable, like git:

git just encodes a number in a fixed-length decimal number, we can do
the same, and then just encode (length, key), (length, data) pairs after
each other (or as mentioned, just use the "index" as the field id, and
store field ids in the progrma). Uses a bit more space, but encodes
everything in a format you could read with a text editor, and should
not be terribly less efficient.

The thing is: This needs to be as efficient as possible: it should
be below 100ms (or better 50ms), regardless of whether caches are dropped
or not.

Python code |   Shawn's code

SSD, cache  50ms5ms
SSD, " dropped 256ms   15ms
HDD, cache  50ms5ms
HDD, " dropped 530ms   15ms

I guess Shawn's code could even be improved in performance by
avoiding the subprocess execution, avoiding various ld cache
lookups and library loads.

I am going to have to bring it in process to add the spell check code.


That said, space requirements might matter too.
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
Ubuntu Core Developer  de, en speaker
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Julian Andres Klode]

On Tue, Nov 14, 2017 at 03:35:02PM +, John Lenton wrote:
> On 14 November 2017 at 12:34, Julian Andres Klode  wrote:
> > On Tue, Nov 14, 2017 at 01:00:54PM +0100, Zygmunt Krynicki wrote:
> >> I would love if we have a compact representation of mapping from name
> >> to list of bits of information where each bit can be a small structure
> >> with some data. Apart from components for ubuntu archive it could be
> >> used to store facts about snap packages, flatpaks, etc. I would try to
> >> avoid a simplistic command -> package mapping as that will force us to
> >> encode things into strings in an ad-hoc way.
> >
> > That makes sense to me. But then we're back on a db, I guess. I sort
> > like this minimal approach.
> 
> I was thinking in the other direction, was going to see how it behaved
> with sqlite as the store. Would that be objectionable?

Using a relational database for a simple key -> structure mapping seems
overkill and a mismatch for the problem, and the SQL does not make it
more readable.

I'd play with lmdb and kyotocabinet, these are two high-performance
key-value file databases and then encode a structure as mentioned
before.

For the text file approach, we can even go human, readable, like git:

git just encodes a number in a fixed-length decimal number, we can do
the same, and then just encode (length, key), (length, data) pairs after
each other (or as mentioned, just use the "index" as the field id, and
store field ids in the progrma). Uses a bit more space, but encodes
everything in a format you could read with a text editor, and should
not be terribly less efficient.

The thing is: This needs to be as efficient as possible: it should
be below 100ms (or better 50ms), regardless of whether caches are dropped
or not.

Python code |   Shawn's code

SSD, cache  50ms5ms
SSD, " dropped 256ms   15ms
HDD, cache  50ms5ms
HDD, " dropped 530ms   15ms

I guess Shawn's code could even be improved in performance by
avoiding the subprocess execution, avoiding various ld cache
lookups and library loads.

That said, space requirements might matter too.
-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
Ubuntu Core Developer  de, en speaker

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[John Lenton]

On 14 November 2017 at 12:34, Julian Andres Klode  wrote:
> On Tue, Nov 14, 2017 at 01:00:54PM +0100, Zygmunt Krynicki wrote:
>> I would love if we have a compact representation of mapping from name
>> to list of bits of information where each bit can be a small structure
>> with some data. Apart from components for ubuntu archive it could be
>> used to store facts about snap packages, flatpaks, etc. I would try to
>> avoid a simplistic command -> package mapping as that will force us to
>> encode things into strings in an ad-hoc way.
>
> That makes sense to me. But then we're back on a db, I guess. I sort
> like this minimal approach.

I was thinking in the other direction, was going to see how it behaved
with sqlite as the store. Would that be objectionable?

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Julian Andres Klode]

On Tue, Nov 14, 2017 at 01:00:54PM +0100, Zygmunt Krynicki wrote:
> Hey everyone.
> 
> Thank you for your interest in command-not-found.
> 
> On Tue, Nov 14, 2017 at 8:50 AM, Julian Andres Klode  wrote:
> > (forwarding this to ubuntu-devel-discuss and Zygmunt)
> >
> > On Mon, Nov 13, 2017 at 10:33:39PM -0800, Shawn Landden wrote:
> >> Package: command-not-found
> >> Severity: wishlist
> >>
> >> I re-wrote command-not-found to get rid of the python dependancy, and
> >> to reduce the database size, as to reduce memory usage.
> >>
> >> https://github.com/shawnl/command-not-found
> >>
> >> I was preparing to upload it to mentors as command-not-found-ng
> >
> > I also rewrote it years ago, but using the same database format,
> > just in C. It was a lot faster. I don't understand the memory usage
> > bit - it should not matter how large the database is, it's memory
> > mapped, and not read into memory, as such memory usage should be
> > roughly constant.
> >
> > Questions/Comments for your approach:
> >
> > * Did you test your format on a slow HDD with caches dropped? It
> >   must not be slower than the Python one (that one is way too slow
> >   already) - I did, it seems to be faster (0.4 vs 0.68 seconds)
> >   - I believe the database-based C rewrite was even much faster,
> >   though.
> 
> > * update-command-not-found should use apt-get indextargets
> 
> > * You don't store components, hence you cannot tell people to enable
> >   component. That's a very important use case for Ubuntu, where
> >   not all components are enabled by default, but the database is
> >   shipped in the package.
> >
> >   You could just append / to each package name I think,
> >   and strip it away when displaying.
> 
> I would love if we have a compact representation of mapping from name
> to list of bits of information where each bit can be a small structure
> with some data. Apart from components for ubuntu archive it could be
> used to store facts about snap packages, flatpaks, etc. I would try to
> avoid a simplistic command -> package mapping as that will force us to
> encode things into strings in an ad-hoc way.

That makes sense to me. But then we're back on a db, I guess. I sort
like this minimal approach. An approach of course would be to store
a key/value map after the package, something like:

filepackage name
followed by multiple:
key
value

where lengths are 32-bit (16 bit?) integers.

Should not be too hard. Alternatively, this also works

filepackagename
   for each field
 value  for each field

and then you can index stuff

offset(attr_i) = offset(attr_i) + attrs[i]

Lots of options to extend.

> 
> > * You should use getopt_long() to parse command-line options, and
> >   support -h, --help :)
> 
> > * pts_lbsearch belongs into usr/lib/..., not usr/share/...
> >
> > * You don't implement a closest matches function:
> >
> > $ command-not-found thunderbrd
> > No command 'thunderbrd' found, did you mean:
> >  Command 'thunderbird' from package 'thunderbird' (main)
> > thunderbrd: command not found
> > $ ./command-not-found thunderbrd
> > thunderbrd: command not found
> >
> >This one is really important. People do make typos or misremember
> >command names, so the tool needs to be able to deal with that
> 
> +1 on this, the function should be not too hard to implement in C.
> 
> >Should be easy to implement though, although you might hav
> 
> > * You need to Conflict with command-not-found and not Break AFAIUI
> 
> Ideally, to ease the transition, you should do something about the
> python APIs. If yo can keep them (either as pure-python bindings or
> just as a compatible implementation) that would be a plus. If you want
> to drop them then please announce that and see if anything rdepends on
> it.

Oh, hmm.

> 
> > * You do have to Depend on apt-file, as that configures apt to download
> >   the Contents files
> 
> I didn't look at the details but I (hope) this is a build dependency
> and this will be processed somewhere on the archive side.

That's a Debian-only dependency forced upon us by ftpmaster, on Ubuntu 
we can ship the data in the package (or preferably a separate 
command-not-found-data source package).


> 
> > I think it's a worthwhile approach, and I can see it replacing
> > command-not-found if those tiny issues have been fixed. Then you
> > could also avoid the -ng moniker, and just take over the main
> > package (if Zygmunt does not mind), which also avoids a month
> > long NEW process :)
> 
> Yes, though I'd like to participate as we're working on
> command-not-found improvements in snapd and would like to have
> something that fits Debian, Ubuntu as well as (eventually but not
> conflicting at least) Fedora and openSUSE (at least the snapd part).

I'd like that.

-- 
Debian Developer - 

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Zygmunt Krynicki]

Hey everyone.

Thank you for your interest in command-not-found.

On Tue, Nov 14, 2017 at 8:50 AM, Julian Andres Klode  wrote:
> (forwarding this to ubuntu-devel-discuss and Zygmunt)
>
> On Mon, Nov 13, 2017 at 10:33:39PM -0800, Shawn Landden wrote:
>> Package: command-not-found
>> Severity: wishlist
>>
>> I re-wrote command-not-found to get rid of the python dependancy, and
>> to reduce the database size, as to reduce memory usage.
>>
>> https://github.com/shawnl/command-not-found
>>
>> I was preparing to upload it to mentors as command-not-found-ng
>
> I also rewrote it years ago, but using the same database format,
> just in C. It was a lot faster. I don't understand the memory usage
> bit - it should not matter how large the database is, it's memory
> mapped, and not read into memory, as such memory usage should be
> roughly constant.
>
> Questions/Comments for your approach:
>
> * Did you test your format on a slow HDD with caches dropped? It
>   must not be slower than the Python one (that one is way too slow
>   already) - I did, it seems to be faster (0.4 vs 0.68 seconds)
>   - I believe the database-based C rewrite was even much faster,
>   though.

> * update-command-not-found should use apt-get indextargets

> * You don't store components, hence you cannot tell people to enable
>   component. That's a very important use case for Ubuntu, where
>   not all components are enabled by default, but the database is
>   shipped in the package.
>
>   You could just append / to each package name I think,
>   and strip it away when displaying.

I would love if we have a compact representation of mapping from name
to list of bits of information where each bit can be a small structure
with some data. Apart from components for ubuntu archive it could be
used to store facts about snap packages, flatpaks, etc. I would try to
avoid a simplistic command -> package mapping as that will force us to
encode things into strings in an ad-hoc way.

> * You should use getopt_long() to parse command-line options, and
>   support -h, --help :)

> * pts_lbsearch belongs into usr/lib/..., not usr/share/...
>
> * You don't implement a closest matches function:
>
> $ command-not-found thunderbrd
> No command 'thunderbrd' found, did you mean:
>  Command 'thunderbird' from package 'thunderbird' (main)
> thunderbrd: command not found
> $ ./command-not-found thunderbrd
> thunderbrd: command not found
>
>This one is really important. People do make typos or misremember
>command names, so the tool needs to be able to deal with that

+1 on this, the function should be not too hard to implement in C.

>Should be easy to implement though, although you might hav

> * You need to Conflict with command-not-found and not Break AFAIUI

Ideally, to ease the transition, you should do something about the
python APIs. If yo can keep them (either as pure-python bindings or
just as a compatible implementation) that would be a plus. If you want
to drop them then please announce that and see if anything rdepends on
it.

> * You do have to Depend on apt-file, as that configures apt to download
>   the Contents files

I didn't look at the details but I (hope) this is a build dependency
and this will be processed somewhere on the archive side.

> I think it's a worthwhile approach, and I can see it replacing
> command-not-found if those tiny issues have been fixed. Then you
> could also avoid the -ng moniker, and just take over the main
> package (if Zygmunt does not mind), which also avoids a month
> long NEW process :)

Yes, though I'd like to participate as we're working on
command-not-found improvements in snapd and would like to have
something that fits Debian, Ubuntu as well as (eventually but not
conflicting at least) Fedora and openSUSE (at least the snapd part).

Best regards
ZK

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug#881692: command-not-found: I re-wrote command-not-found

[Julian Andres Klode]

(forwarding this to ubuntu-devel-discuss and Zygmunt)

On Mon, Nov 13, 2017 at 10:33:39PM -0800, Shawn Landden wrote:
> Package: command-not-found
> Severity: wishlist
> 
> I re-wrote command-not-found to get rid of the python dependancy, and
> to reduce the database size, as to reduce memory usage.
> 
> https://github.com/shawnl/command-not-found
> 
> I was preparing to upload it to mentors as command-not-found-ng

I also rewrote it years ago, but using the same database format,
just in C. It was a lot faster. I don't understand the memory usage
bit - it should not matter how large the database is, it's memory
mapped, and not read into memory, as such memory usage should be
roughly constant. 

Questions/Comments for your approach:

* Did you test your format on a slow HDD with caches dropped? It
  must not be slower than the Python one (that one is way too slow
  already) - I did, it seems to be faster (0.4 vs 0.68 seconds)
  - I believe the database-based C rewrite was even much faster,
  though.
* update-command-not-found should use apt-get indextargets
* You don't store components, hence you cannot tell people to enable
  component. That's a very important use case for Ubuntu, where
  not all components are enabled by default, but the database is
  shipped in the package.

  You could just append / to each package name I think,
  and strip it away when displaying.
* You should use getopt_long() to parse command-line options, and
  support -h, --help :)
* pts_lbsearch belongs into usr/lib/..., not usr/share/...

* You don't implement a closest matches function:

$ command-not-found thunderbrd
No command 'thunderbrd' found, did you mean:
 Command 'thunderbird' from package 'thunderbird' (main)
thunderbrd: command not found
$ ./command-not-found thunderbrd
thunderbrd: command not found

   This one is really important. People do make typos or misremember
   command names, so the tool needs to be able to deal with that

   Should be easy to implement though, although you might have to
   search multiple times - once for each alternative. All you need is

def similar_words(word):
""" return a set with spelling1 distance alternative spellings

based on http://norvig.com/spell-correct.html"";
alphabet = 'abcdefghijklmnopqrstuvwxyz-_'
s = [(word[:i], word[i:]) for i in range(len(word) + 1)]
deletes= [a + b[1:] for a, b in s if b]
transposes = [a + b[1] + b[0] + b[2:] for a, b in s if len(b)>1]
replaces   = [a + c + b[1:] for a, b in s for c in alphabet if b]
inserts= [a + c + b for a, b in s for c in alphabet]
return set(deletes + transposes + replaces + inserts)

And search for what that returns. And you don't need to search for those
at all if you have a direct match.

* It needs to be translated - also very important.

* You need to Conflict with command-not-found and not Break AFAIUI

* You should not depend on grep, sed, coreutils, they are Essential.

* You do have to Depend on apt-file, as that configures apt to download
  the Contents files

* You should not have identifiers starting with _ in the program, these
  are reserved for the C implementation (like _cleanup_free_).

Yes, and these are basically the same reasons my C prototype is
not in the archive. Also, I did not put a lot of work into it, as
I was waiting for PackageKit to take that over, but that was not
done yet.

I think it's a worthwhile approach, and I can see it replacing
command-not-found if those tiny issues have been fixed. Then you
could also avoid the -ng moniker, and just take over the main
package (if Zygmunt does not mind), which also avoids a month
long NEW process :)

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
Ubuntu Core Developer  de, en speaker

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: apache2 update for semi-critical "optionsbleed" bug

[Marc Deslauriers]

On 2017-09-19 10:30 AM, Glen Willmot wrote:
> Good morning,
> 
> Just curious on when we'll see an update on the apache2 release to version
> 2.4.28 to patch against the "Optionsbleed" bug detailed by CVE-2017-9798.
> 
> More info on the severity of this bug can be seen at:
> https://blog.fuzzing-project.org/60-Optionsbleed-HTTP-OPTIONS-method-can-leak-Apaches-server-memory.html
> 
> Thank you,
> Glen
> 
> 

https://usn.ubuntu.com/usn/usn-3425-1/

Marc.


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: apache2 update for semi-critical "optionsbleed" bug

[Robie Basak]

On Tue, Sep 19, 2017 at 10:30:20AM -0400, Glen Willmot wrote:
> Just curious on when we'll see an update on the apache2 release to
> version 2.4.28 to patch against the "Optionsbleed" bug detailed by
> CVE-2017-9798.

Already done, but by backporting the fix (as usual for Linux
distributions) rather than updating to 2.4.28.

See:

https://usn.ubuntu.com/usn/usn-3425-1/
https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-9798.html


signature.asc
Description: PGP signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

apache2 update for semi-critical "optionsbleed" bug

[Glen Willmot]

Good morning,

Just curious on when we'll see an update on the apache2 release to version
2.4.28 to patch against the "Optionsbleed" bug detailed by CVE-2017-9798.

More info on the severity of this bug can be seen at:
https://blog.fuzzing-project.org/60-Optionsbleed-HTTP-OPTIONS-method-can-leak-Apaches-server-memory.html

Thank you,
Glen
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug#874844: [choreonoid] Future Qt4 removal from Buster

[Lisandro Damián Nicanor Pérez Meyer]

Source: choreonoid
Version: 1.1.0+dfsg-6.2
1.5.0+dfsg-0.1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 
<https://lists.debian.org/debian-devel-announce/2017/08/msg6.html>

Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522>

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in <https://wiki.debian.org/Qt4Removal>

Lisandro,
on behalf of the Qt4 maintainers

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: BUG: Intel-8260 not init'd by intel-microcode=3.20170707.1~ubuntu16.04.0

[Yarko Tymciurak]

Will do, thanks!

On Mon, Aug 28, 2017 at 6:18 AM Robie Basak <robie.ba...@ubuntu.com> wrote:

> Hi Yarko,
>
> Thank you for this report. Please could you file a bug against the
> intel-microcode package in Ubuntu so that we can track this? Use the
> following link:
>
> https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+filebug
>
> Thanks!
>
> Robie
>
> On Sat, Aug 26, 2017 at 08:43:54PM -0500, Yarko Tymciurak wrote:
> > Hi -
> >
> > Just posting here from email in 'apt-cache show' list.
> >
> > I'm running:
> >
> > LSB Version:
> >
> core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
> > Distributor ID: Ubuntu
> > Description: Ubuntu 16.04.3 LTS
> > Release: 16.04
> > Codename: xenial
> >
> > On a NUC6i5SYH, with 32G RAM, and BIOS 0061
> >
> > Recently, the following package update happened:
> > intel-microcode=3.20170707.1~ubuntu16.04.0
> >
> > Upon reboot, bluetooth was unavailable / uninitialized.
> > Poking around w/ various tools, I think the insightful bit came from:
> > [image: Inline image 1]
> >
> > Rolling back to:
> > intel-microcode=3.20151106.1
> >
> > and rebooting restored bluetooth function (I use a bluetooth keyboard).
> >
> > I did try (and leave) changing /etc/bluetooth/main.conf as follows:
> > Autoenable=true
> >
> > It didn't help under the new intel-micorcode, and seems to have no
> > noticable deleterious effect under the old intel-microcode.
> >
> > Let me know if there's any other / more information I can provide to
> help.
> >
> > Regards,
> > Yarko
> >
> > @yarkot
> > yark...@gmail.com
>
>
>
> > --
> > Ubuntu-devel-discuss mailing list
> > Ubuntu-devel-discuss@lists.ubuntu.com
> > Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
>
>
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: BUG: Intel-8260 not init'd by intel-microcode=3.20170707.1~ubuntu16.04.0

[Robie Basak]

Hi Yarko,

Thank you for this report. Please could you file a bug against the
intel-microcode package in Ubuntu so that we can track this? Use the
following link:

https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+filebug

Thanks!

Robie

On Sat, Aug 26, 2017 at 08:43:54PM -0500, Yarko Tymciurak wrote:
> Hi -
> 
> Just posting here from email in 'apt-cache show' list.
> 
> I'm running:
> 
> LSB Version:
> core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
> Distributor ID: Ubuntu
> Description: Ubuntu 16.04.3 LTS
> Release: 16.04
> Codename: xenial
> 
> On a NUC6i5SYH, with 32G RAM, and BIOS 0061
> 
> Recently, the following package update happened:
> intel-microcode=3.20170707.1~ubuntu16.04.0
> 
> Upon reboot, bluetooth was unavailable / uninitialized.
> Poking around w/ various tools, I think the insightful bit came from:
> [image: Inline image 1]
> 
> Rolling back to:
> intel-microcode=3.20151106.1
> 
> and rebooting restored bluetooth function (I use a bluetooth keyboard).
> 
> I did try (and leave) changing /etc/bluetooth/main.conf as follows:
> Autoenable=true
> 
> It didn't help under the new intel-micorcode, and seems to have no
> noticable deleterious effect under the old intel-microcode.
> 
> Let me know if there's any other / more information I can provide to help.
> 
> Regards,
> Yarko
> 
> @yarkot
> yark...@gmail.com



> -- 
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss@lists.ubuntu.com
> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss



signature.asc
Description: PGP signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: LibreOffice bug - cannot load calc 5.1.4.2

[Nrbrtx]

Dear paul!

It seems that you have not installed all updates to your system.
What version <https://linuxmint.com/download_all.php> of LinuxMint do you
use? Have you added libreoffice PPA?

According to version of libreoffice - 1:5.1.4-0ubuntu1 (
https://launchpad.net/ubuntu/+source/libreoffice/1:5.1.4-0ubuntu1) it is
based on Ubuntu 16.04 LTS Xenial Xerus.

You can try
sudo apt-get purge libreoffice libreoffice-base libreoffice-draw
libreoffice-impress libreoffice-math libreoffice-writer
sudo apt-get update
sudo apt-get install aptitude
sudo aptitude safe-upgrade
sudo apt-get install -f
sudo apt-get upgrade -f
sudo apt-get dist-upgrade -f
sudo apt-get install libreoffice libreoffice-base libreoffice-draw
libreoffice-impress libreoffice-math libreoffice-writer


With best regards,
Norbert.


On Wed, Jun 28, 2017 at 9:26 PM, paulwhee...@cox.net <paulwhee...@cox.net>
wrote:

> LibreOffice bug - cannot load calc 5.1.4.228 June, 2017
>
>
> You are getting this bug report, because you are listed as the
> 'maintainer' for this package. See: 'Maintainer of LibreOffice package.png'
>
>
> If you are not at fault, then send the information to libreoffice.
>
>
> I would appreciate not getting any excuses for why your team is not
> responsible for this package, because the attached photo says you are! I
> doubt that hardware or OS has anything to do with this bug,
>
>
> Bug Report:
>
> I created a new linuxmint installation. I installed libreOffice. I tried
> to look at a calc file. Got the attached error message.
>
> (see '/media/paul/26 Sep 2016 New/MyDocuments/Bug Reports - Not
> church/LibreOffice broken package - cannot load calc.png')
>
>
> Also, I have attached a picture showing that the lost file is, indeed, in
> the directory!
>
>
> REALLY?
>
>
> I have run linuxmint on this hardware and even the same version of mint
> for quite a while.
>
> Now your package does not include a needed library?
> Now what do I do, besides cry?
>
>
> Frustrated, and falling behind in my work, because of your bug.
>
> paul
>
>
> --
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/ubuntu-devel-discuss
>
>
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: LibreOffice bug - cannot load calc 5.1.4.2

[Tom H]

On Wed, Jun 28, 2017 at 2:26 PM, paulwhee...@cox.net
<paulwhee...@cox.net> wrote:
> LibreOffice bug - cannot load calc 5.1.4.228 June, 2017
>
> ...
>
> I created a new linuxmint installation. I installed libreOffice. I tried to
> look at a calc file. Got the attached error message.
>
> ...
>
> I have run linuxmint on this hardware and even the same version of mint for
> quite a while.

Linux Mint?!

That ".so" is provided by "libreoffice-calc". Have you tried
re-installing it? With "apt-get install --reinstall libreoffice-calc".

You should check whether it's installed automatically and, if it is,
mark it back as automatic after the re-install. With "apt-mark auto
libreoffice-calc".

But this stuff belongs on a Mint list...

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: LibreOffice bug - cannot run office because of 'missing file' in 5.1.4.2 28 June, 2017

[Ralf Mardorf]

On Thu, 29 Jun 2017 08:17:00 +0200, Ralf Mardorf wrote:
>On Wed, 28 Jun 2017 12:49:06 -0700, paulwhee...@cox.net wrote:
>>Frustrated, and falling behind in my work, because of your bug.  
>
>No, because you are ignoring the messages you get by synaptic

PS:

If you would use an Ubuntu flavour, you could expect help by the Ubuntu
users mailing list,
https://lists.ubuntu.com/mailman/listinfo/ubuntu-users.

"Users of Ubuntu and officially supported derivatives (Kubuntu,
Edubuntu, Xubuntu, Lubuntu) can get support here. Users of derivatives
(such as Backtrack and Linux Mint) are not officially supported." -
https://wiki.ubuntu.com/UbuntuUsersListFAQ#FAQ1

The list of Ubuntu flavours is outdated, anyway, Mint still isn't an
Ubuntu flavour, https://www.ubuntu.com/download/ubuntu-flavours ,
https://www.ubuntu.com/about/about-ubuntu/flavours . Consider to
migrate to an Ubuntu flavour or ask for help by Mint support.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: LibreOffice bug - cannot run office because of 'missing file' in 5.1.4.2 28 June, 2017

[Ralf Mardorf]

Hi,

On Wed, 28 Jun 2017 12:49:06 -0700, paulwhee...@cox.net wrote:
>Frustrated, and falling behind in my work, because of your bug.

No, because you are ignoring the messages you get by synaptic, as well
as sending tons of requests, instead of just one smart request and apart
from this you are sending it to a mailing list of the wrong distro.
It's all your fault.

Take a look at http://www.catb.org/esr/faqs/smart-questions.html .

On Wed, 28 Jun 2017 12:28:23 -0700, paulwhee...@cox.net wrote:
>Also, if the program was installed by synaptic, and all entries
>looked good during that installation, then how can there be a problem
>resolving dependencies?

This could happen if you are e.g. using official Ubuntu repositories
with a third party repository, maybe a Mint repository. However, in your
case it might be an user error, related to held packages, at least the
messages complain about a possible hold package.

On Wed, 28 Jun 2017 11:35:32 -0700, paulwhee...@cox.net wrote:
>I would appreciate not getting any excuses for why your team is not 
>responsible for this package, because the attached photo says you are!
>I doubt that hardware or OS has anything to do with this bug,
>
>
>Bug Report:
>
>I created a new linuxmint installation.

Mint isn't an Ubuntu flavour, IOW you sent your request to a mailing
list of another distro.

Regards,
Ralf

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

LibreOffice bug - cannot load calc 5.1.4.2 28 June, 2017

[paulwhee...@cox.net]

LibreOffice bug - cannot load calc 5.1.4.228 June, 2017

You are getting this bug report, because you are listed as the 
'maintainer' for this package. See: 'Maintainer of LibreOffice package.png'



If you are not at fault, then send the information to libreoffice.


I would appreciate not getting any excuses for why your team is not 
responsible for this package, because the attached photo says you are! I 
doubt that hardware or OS has anything to do with this bug,



Bug Report:

I created a new linuxmint installation. I installed libreOffice. I tried 
to look at a calc file. Got the attached error message.


(see '/media/paul/26 Sep 2016 New/MyDocuments/Bug Reports - Not 
church/LibreOffice broken package - cannot load calc.png')



Also, I have attached a picture showing that the lost file is, indeed, 
in the directory! See: 'LibreOffice file is where it should be.png'



REALLY?


I have run linuxmint on this hardware and even the same version of mint 
for quite a while.


Now your package does not include a needed library?
Now what do I do, besides cry?


Frustrated, and falling behind in my work, because of your bug.

paul

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

LibreOffice bug - cannot run office because of 'missing file' in 5.1.4.2 28 June, 2017

[paulwhee...@cox.net]

LibreOffice bug - cannot run office because of 'missing file' in 
5.1.4.228 June, 2017



You are getting this bug report, because you are listed as the 
'maintainer' for this package. See: 'Maintainer of LibreOffice package.png'



If you are not at fault, then send the information to libreoffice.


I would appreciate not getting any excuses for why your team is not 
responsible for this package, because the attached photo says you are! I 
doubt that hardware or OS has anything to do with this bug,



Bug Report:

I created a new linuxmint installation. I reinstalled libreOffice (for 
3rd time) after the removal problems listed in my prior emails. I tried 
clicking on a calc file I needed, and which I have opened dozens of 
times. Libreoffice barfed the same error message it had already 
complanied about. See: LibreOffice broken package - cannot load calc.png


I then checked to see if the file was 'missing'. No, it is exactly where 
LO thinks it shoud be!! See: LibreOffice file is where it should be! 
See: LibreOffice file is where it should be.png




REALLY?



This sounds like a programming or compiler or packaging bug! Whatever it 
is, needs to be fixed, so I can do my work of entry billable hours.




I have run linuxmint on this hardware for quite a while. Now your 
package cannot not include a needed library?


How is this possible? That section has worked for years!


Now what do I do, besides cry?


Frustrated, and falling behind in my work, because of your bug.

paul

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

LibreOffice bug - cannot load calc 5.1.4.2 28 June, 2017

[paulwhee...@cox.net]

LibreOffice bug - cannot load calc 5.1.4.228 June, 2017


You are getting this bug report, because you are listed as the 
'maintainer' for this package. See: 'Maintainer of LibreOffice package.png'



If you are not at fault, then send the information to libreoffice.


I would appreciate not getting any excuses for why your team is not 
responsible for this package, because the attached photo says you are! I 
doubt that hardware or OS has anything to do with this bug,



Bug Report:

I created a new linuxmint installation. I installed libreOffice. I tried 
to look at a calc file. Got the attached error message.


(see '/media/paul/26 Sep 2016 New/MyDocuments/Bug Reports - Not 
church/LibreOffice broken package - cannot load calc.png')



Also, I have attached a picture showing that the lost file is, indeed, 
in the directory!



REALLY?


I have run linuxmint on this hardware and even the same version of mint 
for quite a while.


Now your package does not include a needed library?
Now what do I do, besides cry?


Frustrated, and falling behind in my work, because of your bug.

pau

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

LibreOffice bug - cannot load calc 5.1.4.2

[paulwhee...@cox.net]

LibreOffice bug - cannot load calc 5.1.4.228 June, 2017


You are getting this bug report, because you are listed as the 
'maintainer' for this package. See: 'Maintainer of LibreOffice package.png'



If you are not at fault, then send the information to libreoffice.


I would appreciate not getting any excuses for why your team is not 
responsible for this package, because the attached photo says you are! I 
doubt that hardware or OS has anything to do with this bug,



Bug Report:

I created a new linuxmint installation. I installed libreOffice. I tried 
to look at a calc file. Got the attached error message.


(see '/media/paul/26 Sep 2016 New/MyDocuments/Bug Reports - Not 
church/LibreOffice broken package - cannot load calc.png')



Also, I have attached a picture showing that the lost file is, indeed, 
in the directory!



REALLY?


I have run linuxmint on this hardware and even the same version of mint 
for quite a while.


Now your package does not include a needed library?
Now what do I do, besides cry?


Frustrated, and falling behind in my work, because of your bug.

paul

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug#859357: choreonoid shouldn't disable PIE

[Adrian Bunk]

Source: choreonoid
Version: 1.5.0+dfsg-0.1
Severity: normal
Tags: patch

With gcc in stretch defaulting to PIE, hardening=+all,-pie changed
semantics from "enable hardening but not PIE" to "enable all hardening
and explicitely disable the default PIE".
The latter is usually not intended.

The -pie in hardening flags was in some cases required in pre-stretch
releases to avoid build failures caused by (incorrectly) passing -fPIE
to the compiler when building shared libraries or plugins.
This problem does no longer exist.

Please consider applying the following change:

--- debian/rules.old2017-04-02 18:35:57.0 +
+++ debian/rules2017-04-02 18:36:10.0 +
@@ -2,7 +2,7 @@
 # -*- makefile -*-
 
 # Hardening.
-export DEB_BUILD_MAINT_OPTIONS=hardening=+all,-pie,+fortify
+export DEB_BUILD_MAINT_OPTIONS=hardening=+all,+fortify
 
 CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS)
 CFLAGS:=$(shell dpkg-buildflags --get CFLAGS)

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Fwd: e1000e nvm checksum bug presence?

[Андрій Шелунцов]

Hello.
My question is simple.
Is this bug
<https://superuser.com/questions/1104537/how-to-repair-the-checksum-of-the-non-volatile-memory-nvm-of-intel-ethernet-co>
still
present in current versions of ubuntu(LTS and Non-LTS)?
Thanks for your answer.
Andriy.
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Bug#817302: marked as done (openjdk-6: Removal of dh_desktop)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2017 16:59:33 +0200
with message-id <20170123145933.wkuzox72oojbut3b@localhost>
and subject line This has been fixed in 6b39-1.13.11-1
has caused the Debian Bug report #817302,
regarding openjdk-6: Removal of dh_desktop
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
817302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-6
Severity: important
Tags: dh_desktop-removal

Hi,

The package openjdk-6 is still using dh_desktop according to lintian.
This command was obsoleted in 2009 and has since then done nothing but
print a warning.

 * Please remove all remaining calls to dh_desktop at your
   earliest convenience.

 * I will remove dh_undocumented from debhelper in the first upload
   after 1st of April.


If your package is *also* affected by any of the following debhelper
related deprecations, please consider fixing them at the same time:

 * debhelper compat 4 is deprecated and is expected to be removed
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * If your package does *not* have a debian/compat, please add one with
   the correct compat level.
   - The compat file will be required by 15th of April.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Version: 6b39-1.13.11-1


openjdk-6 (6b39-1.13.11-1) experimental; urgency=medium

  [ Tiago Stürmer Daitx ]
...
  * debian/rules: remove deprecated dh_desktop call. Closes #817302
...
 -- Matthias Klose <d...@ubuntu.com>  Fri, 06 May 2016 21:32:49 +0200


cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

blender bug

[Aldrin P. S. Castro]

In My Ubuntu the Blender has a bug. By maximizing and start to spin the 
object in 3D The screen begin flash.


To help, the exit of the my lshw:

reginaldo-desktop
description: Desktop Computer
product: To Be Filled By O.E.M. (To Be Filled By O.E.M.)
vendor: To Be Filled By O.E.M.
version: To Be Filled By O.E.M.
serial: To Be Filled By O.E.M.
width: 64 bits
capabilities: smbios-2.4 dmi-2.4 vsyscall32
configuration: boot=normal chassis=desktop family=To Be Filled By 
O.E.M. sku=To Be Filled By O.E.M. uuid=00020003-0004-0005-0006-000700080009

  *-core
   description: Motherboard
   product: Phitronics G31VS2-M
   physical id: 0
 *-firmware
  description: BIOS
  vendor: American Megatrends Inc.
  physical id: 0
  version: P1.00
  date: 03/17/2010
  size: 64KiB
  capacity: 448KiB
  capabilities: pci upgrade shadowing cdboot bootselect 
socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 
int5printscreen int9keyboard int14serial int17printer int10video acpi 
usb ls120boot zipboot biosbootspecification netboot

 *-cpu
  description: CPU
  product: Intel(R) Celeron(R) D CPU 3.06GHz
  vendor: Intel Corp.
  physical id: 4
  bus info: cpu@0
  version: Intel(R) Celeron(R) D CPU 3.06GHz
  serial: To Be Filled By O.E.M.
  slot: CPUSocket
  size: 3833MHz
  width: 64 bits
  clock: 133MHz
  capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce 
cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse 
sse2 ss ht tm pbe syscall nx x86-64 constant_tsc pebs bts nopl pni 
dtes64 monitor ds_cpl cid cx16 xtpr pdcm lahf_lm

*-cache:0
 description: L1 cache
 physical id: 5
 slot: L1-Cache
 size: 16KiB
 capacity: 16KiB
 capabilities: internal write-back data
 configuration: level=1
*-cache:1
 description: L2 cache
 physical id: 6
 slot: L2-Cache
 size: 512KiB
 capacity: 512KiB
 capabilities: internal write-back unified
 configuration: level=2
 *-memory
  description: System Memory
  physical id: c
  slot: System board or motherboard
  size: 2304MiB
*-bank:0
 description: DIMM SDRAM Synchronous
 product: PartNum0
 vendor: Manufacturer0
 physical id: 0
 serial: SerNum0
 slot: DIMM0
 size: 2GiB
 width: 64 bits
*-bank:1
 description: DIMM SDRAM Synchronous
 product: PartNum1
 vendor: Manufacturer1
 physical id: 1
 serial: SerNum1
 slot: DIMM1
 size: 256MiB
 width: 64 bits
 *-pci
  description: Host bridge
  product: 82G33/G31/P35/P31 Express DRAM Controller
  vendor: Intel Corporation
  physical id: 100
  bus info: pci@:00:00.0
  version: 10
  width: 32 bits
  clock: 33MHz
  configuration: driver=agpgart-intel
  resources: irq:0
*-display
 description: VGA compatible controller
 product: 82G33/G31 Express Integrated Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 10
 width: 32 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:27 memory:fea8-feaf 
ioport:dc00(size=8) memory:e000-efff memory:fe90-fe9f

*-multimedia
 description: Audio device
 product: NM10/ICH7 Family High Definition Audio Controller
 vendor: Intel Corporation
 physical id: 1b
 bus info: pci@:00:1b.0
 version: 01
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list
 configuration: driver=snd_hda_intel latency=0
 resources: irq:28 memory:fea78000-fea7bfff
*-pci:0
 description: PCI bridge
 product: NM10/ICH7 Family PCI Express Port 1
 vendor: Intel Corporation
 physical id: 1c
 bus info: pci@:00:1c.0
 version: 01
 width: 32 bits
 clock: 33MHz
 capabilities: pci pciexpress msi pm normal_decode 
bus_master cap_list

 configuration: driver=pcieport
 resources: irq:24 ioport:1000(size=4096) 
memory:9000-903f ioport:fdf0(size=1048576)

*-pci:1
 description: PCI bridge
 product

Re: Bug in python-wxgtk3.0 using DisplayCAL

[Gianfranco Costamagna]

Hi Will,

>I have been attempting to calibrate my monitor using DisplayCAL.
>Have informed the DisplayCAL developer Florian Höch
> but he insists it is a bug
>within python-wxgtk3.0.

sudo apt install dispcalgui
displaycal

works here, on both xenial amd64 and trusty amd64 (chroot after xhost +).
with trusty chroot I get a little bad graphic, and the command has a different 
naming, but
I can start it correctly.

G.



signature.asc
Description: OpenPGP digital signature
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug in ubuntu package for Mailman

[Philip Colmer]

Hi Christian

Yes, you have correctly identified the diff.

Just to make sure I understand correctly, you want me to mark the *Mailman*
bug that I linked to as New again?

I don't want to get yelled at by the GNU Mailman people if I'm doing the
wrong thing :)

Regards

Philip


On 18 November 2016 at 06:45, Christian Ehrhardt <
christian.ehrha...@canonical.com> wrote:

>
> On Thu, Nov 17, 2016 at 5:18 PM, Philip Colmer <philip.col...@linaro.org>
> wrote:
>
>> It looks as if https://bugs.launchpad.net/mailman/+bug/1251495 has not
>> been applied to the ubuntu package for Mailman. I have checked both
>> 1:2.1.16-2ubuntu0.2 and 1:2.1.16-2, and Tagger.py has the bug in it.
>> Hand-altering the file to implement the fix does correct the problem.
>>
>
> Hi Phillip,
> thanks for your report.
> The old bug unfortunately doesn't have a lot of information.
> Would that be this Diff that is missing?:
>
> @@ -71,7 +73,7 @@
>  if hits:
>  msgdata['topichits'] = hits.keys()
>  change_header('X-Topics', NLTAB.join(hits.keys()),
> -  mlist, msg, msgdata, Delete=False)
> +      mlist, msg, msgdata, delete=False)
>
> I wasn't sure so I didn't want to flag the bug improperly - but If so
> please just add this snippet (or whatever else is the diff that is missing)
> to the bug and set it to "new" again.
> That should let it enter the normal pipeline to get handled and cleaned up.
>
>
> --
> Christian Ehrhardt
> Software Engineer, Ubuntu Server
> Canonical Ltd
>
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Bug in ubuntu package for Mailman

[Philip Colmer]

Thanks for your help with this, Christian. Very much appreciated.

Regards

Philip


On 18 November 2016 at 09:57, Christian Ehrhardt <
christian.ehrha...@canonical.com> wrote:

>
> On Fri, Nov 18, 2016 at 10:07 AM, Philip Colmer <philip.col...@linaro.org>
> wrote:
>
>> Just to make sure I understand correctly, you want me to mark the
>> *Mailman* bug that I linked to as New again?
>>
>
> I'll try to clarify.
> The linked bug is a mailman bug you are right on that.
> What has to be done is to add an Ubuntu Task for the versions affected -
> in this case only trusty.
> This is then a Ubuntu bug for the packaging of mailman - so not a "mailman
> bug" in that sense.
> It is easy, I did it for you and subscribed you to the bug since
> developers will want a reporter to verify once a fix was made available.
>
>
>> I don't want to get yelled at by the GNU Mailman people if I'm doing the
>> wrong thing :)
>>
>
> You were right to ask for clarification - and no yelling was intened or
> planned for anybody :-)
>
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss