[Bug 1929622] [NEW] backport fix for upstream bug: kdeinit5 crashes in ThumbnailProtocol::get() every time I take a screenshot or start the computer

[Matthew Hall]

Public bug reported:

See:

https://bugs.kde.org/show_bug.cgi?id=430862

Would it be possible to backport this fix to affected Ubuntu releases
ASAP as it's quite irritating every time you take a screenshot.

I detected it on hirsute, not sure what other releases could be
affected.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: kinit 5.80.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue May 25 15:38:55 2021
InstallationDate: Installed on 2020-07-28 (301 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: kinit
UpgradeStatus: Upgraded to hirsute on 2021-05-03 (22 days ago)

** Affects: kinit (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: kio-extras (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

** Also affects: kio-extras (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929622

Title:
  backport fix for upstream bug: kdeinit5 crashes in
  ThumbnailProtocol::get() every time I take a screenshot or start the
  computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kinit/+bug/1929622/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1890517] [NEW] redis-server crashes with jemalloc error if activedefrag is enabled

[Matthew Hall]

Public bug reported:

journalctl output:

Aug 05 18:20:25 mhall-xps redis-server[555286]: *** FATAL CONFIG FILE ERROR ***
Aug 05 18:20:25 mhall-xps redis-server[555286]: Reading the configuration file, 
at line 1352
Aug 05 18:20:25 mhall-xps redis-server[555286]: >>> 'activedefrag yes'
Aug 05 18:20:25 mhall-xps redis-server[555286]: active defrag can't be enabled 
without proper jemalloc support

I am in the process of debugging this more fully, but it appears that
part of the problem is caused by the difference between the USE_JEMALLOC
and USE_SYSTEM_JEMALLOC flags in the debian/rules and debian/patches for
the package.

When you run ldd on redis-server, it is linked against libjemalloc, but
it seems that the logic in the redis-server binary itself is not
detecting this because the ifdefs involved depend on USE_JEMALLOC being
set and the packaging code is not setting this flag. However, rebuilding
the package from the Ubuntu source with the flag set did not seem to
help.

The latest Debian source on Git is giving me some FTBFS issues, probably
user error because I am not that familiar with using the special Debian
package Git repos and some of the distro specific patches probably did
not get applied:

cc: error: ../deps/lua/src/lua_struct.o: No such file or directory
cc: error: ../deps/lua/src/lua_cmsgpack.o: No such file or directory

...

cc: error: ../deps/jemalloc/lib/libjemalloc.a: No such file or directory

Using the Debian source from the latest unstable tarball, 6.0.6, the
error received changes:

Aug 05 19:43:23 mhall-xps redis-server[595179]: Active defragmentation
cannot be enabled: it requires a Redis server compiled with a modified
Jemalloc like the one shipped by default with the Redis source
distribution

Reading the code some more from there, it appears that, when using the
system jemalloc, as the Redis package is trying to do, because the
system jemalloc does not define the symbol JEMALLOC_FRAG_HINT checked in
zmalloc.h to fully enable defrag support.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: redis-server 5:5.0.7-2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed Aug  5 19:03:06 2020
InstallationDate: Installed on 2020-07-28 (8 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: redis
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.redis.redis.conf: 2020-08-05T18:24:16.836149

** Affects: redis (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890517

Title:
  redis-server crashes with jemalloc error if activedefrag is enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1890517/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1674492] Re: cron: /etc/default/cron should not actually be deprecated

[Matthew Hall]

This bug is related to two other bugs:

Similar issue where /etc/default/cron is still relevant:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1078607

Inaccurate commit where file was wrongly marked deprecated, for a bad boot 
speed related reason, in the now deprecated Upstart system. This should 
probably be reverted in some way.
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/794082

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674492

Title:
  cron: /etc/default/cron should not actually be deprecated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1674492/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1674492] [NEW] cron: /etc/default/cron should not actually be deprecated

[Matthew Hall]

Public bug reported:

The /etc/default/cron file claims that it has been deprecated in its own
comments, and refers to an upstart configuration file (which is deprecated in
Ubuntu 15.10 and up, in favor of systemd):

$ cat /etc/default/cron
# This file has been deprecated. Please add custom options for cron to
# /etc/init/cron.conf and/or /etc/init/cron.override directly. See
# the init(5) man page for more information.
EXTRA_OPTS="-L 15" *** (added on my system for debugging) ***

Yet, the systemd cron.service actually respects the content of the file:

$ cat /lib/systemd/system/cron.service
[Unit]
Description=Regular background program processing daemon
Documentation=man:cron(8)

[Service]
EnvironmentFile=-/etc/default/cron
ExecStart=/usr/sbin/cron -f $EXTRA_OPTS
IgnoreSIGPIPE=false
KillMode=process

[Install]
WantedBy=multi-user.target
(venv) arceo@lab-dev-01:~/poc-connectors/scripts$

So, the inaccurate comments in /etc/default/cron, and other such files (if
this was perhaps an automated error by debhelper or similar tools), should be
corrected accordingly.

** Affects: cron (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674492

Title:
  cron: /etc/default/cron should not actually be deprecated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1674492/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1556330] Re: upstream curl bug #1371: p12 client certificates code is broken

[Matthew Hall]

Hello,

I am very sorry for the delay in testing this.

I noticed that the package libcurl4-doc is missing. I wasn't sure if it
was obsolete, or a mistake, or not included in the test packages only.

Otherwise the package is working perfectly and is ready for release to
Ubuntu 14.04 LTS.

Thanks for all of your help to make this fix possible.

Sincerely,
Matthew.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556330

Title:
  upstream curl bug #1371: p12 client certificates code is broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1556330/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1556330] Re: upstream curl bug #1371: p12 client certificates code is broken

[Matthew Hall]

> On Mar 12, 2016, at 8:55 AM, LocutusOfBorg  
> wrote:
> 
> unfortunately it doesn't seem to build.

It built perfectly when I modified the source for 14.04 LTS.

Also thanks for the more detailed stable release diff procedures. I did
read the stable release update page to write the original report but it
didn't explain the commands to run as a community member. Who has access
to add the additional procedures you wrote into the page? This would be
very helpful for other technical users without knowledge of the special
Debian and Ubuntu processes.

Matthew.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556330

Title:
  upstream curl bug #1371: p12 client certificates code is broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1556330/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1556330] Re: upstream curl bug #1371: p12 client certificates code is broken

[Matthew Hall]

Brian, I was hoping for some community assistance on the changelog and
debdiff area because I am absolutely not expert at creating and
maintaining custom Debian and Ubuntu packaging related files. If there
are some things I should do to create these items documentation is of
course welcome.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556330

Title:
  upstream curl bug #1371: p12 client certificates code is broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1556330/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1556330] Re: upstream curl bug #1371: p12 client certificates code is broken

[Matthew Hall]

Requested nomination for stable release update from Ubuntu Bug Control
at 2016-03-12T00:08.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556330

Title:
  upstream curl bug #1371: p12 client certificates code is broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1556330/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1556330] [NEW] upstream curl bug #1371: p12 client certificates code is broken

[Matthew Hall]

Public bug reported:

The following bug from upstream libcurl should be fixed in Ubuntu Stable
and Ubuntu LTS trains:

https://sourceforge.net/p/curl/bugs/1371/

The bug fix consists of one missing break statement at the end of a case
in a switch statement.

I personally patched the bug using source code release
curl_7.35.0-1ubuntu2.6.dsc, used in Ubuntu 14.04 LTS, and verified it
does indeed fix the bug and all of the package's tests still pass
afterwards.

Impact: The bug makes it impossible to use PKCS#12 secure storage of
client certificates and private keys with any affected Ubuntu releases.
The fix is one line fixing a broken switch statement and was already
tested against Ubuntu 14.04 LTS with a rebuilt curl package.

Testing: The bug can be reproduced using the following libcurl
parameters (even via CLI, pycurl, etc.).

CURLOPT_SSLCERTTYPE == "P12"
CURLOPT_SSLCERT = path to PKCS#12
CURLOPT_SSLKEY = path to PKCS#12
CURLOPT_SSLKEYPASSWD = key for PKCS#12 if needed

Basically, just use a PKCS#12 format client certificate and private key
against some certificate protected web server.

Regression Potential: If it could possibly break anything, which is
extraordinarily unlikely, it would break one of the three client
certificate formats (most likely PKCS#12 but also PEM or DER). Note 1/3
formats is already broken due to the bug. Client certificates of all
three types could be checked to prevent this.

** Affects: curl (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "official libcurl patch from Daniel Stenberg"
   
https://bugs.launchpad.net/bugs/1556330/+attachment/4596446/+files/libcurl_broken_pkcs12.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556330

Title:
  upstream curl bug #1371: p12 client certificates code is broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1556330/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1411330] Re: vmlinuz permissions

[Matthew Hall]

Confirmed in Ubuntu 15.10 Wily. This is a massively irritating defect.
Profiling tools can't read the kernel file by default to help do
performance tuning and nothing is gained from making the kernel secret
because anybody can extract it from a deb file anyways.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1411330

Title:
  vmlinuz permissions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411330/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com

[Matthew Hall]

This bug has been open two years and it's still occurring. I've noticed
it during development of an open-source network security sensor I'm
planning to publish in the next few weeks:

{ source: dns, port_id: 0, direction: 1, self: 0, length:
76, eth_type: 2048, smac: 50:e5:49:36:0a:db, dmac:
78:96:84:71:ea:c0, sip: 192.168.1.5, dip: 192.168.1.254,
ip_protocol: 17, ttl: 0, l4_length: 42, icmp_type: 255,
icmp_code: 255, sport: 37657, dport: 53, dns_name:
daisy.ubuntu.com. }

It's a little unbelievable it's been open this long with no concrete
plan taking shape.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/991481

Title:
  Constant dns traffic for daisy.ubuntu.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/whoopsie/+bug/991481/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1315344] Re: Grub install failed on disks with software RAID

[Matthew Hall]

In my case it also failed. I had a precreated series of /dev/md devices
I set up using gdisk.

/dev/md0 for swap, /dev/md1 for root (/), and /dev/md2 for home (/home).

The install died during the grub installation. Now, there is no longer
an Alternate Ubuntu CD with the Debian Installer (which, sadly, after
all these years and all these shiny UIs, still works better than the
Ubuntu one does). So it's pretty tough to work around the problem
either.

I am not sure where to get all of the error logs from the install
because the location of them and most of the behavior of the Ubiquity
installed is undocumented as far as I can tell. It seems like it
segfaulted on me after the failure. I attached the stuff I could find in
/var/log/syslog. But given there's not a lot of decent workarounds I
think this is a pretty severe bug... installers shouldn't segfault...

Jul 28 06:33:02 kubuntu kernel: [ 3143.574987] ubiquity[29163]: segfault
at 70c000c ip 7f04d7379e88 sp 7fff1862fa08 error 4 in
libQtCore.so.4.8.6[7f04d71eb000+2d8000]

** Attachment added: Logs from RAID Grub failure and Ubiquity crash
   
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1315344/+attachment/4164162/+files/ubiquity-log.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315344

Title:
  Grub install failed on disks with software RAID

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1315344/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1315344] Re: Grub install failed on disks with software RAID

[Matthew Hall]

Adding the grub probe output requested from other reporters.

** Attachment added: more grub probe output
   
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1315344/+attachment/4164163/+files/grub-probe.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315344

Title:
  Grub install failed on disks with software RAID

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1315344/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 568288] Re: init: main process can respawn even when the job is stopping

[Matthew Hall]

This bug is 3 years old and has a patch. Can we patch it and get this
over with?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/568288

Title:
  init: main process can respawn even when the job is stopping

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/568288/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1013597] Re: No default route for stateful DHCPv6

[Matthew Hall]

Hello,

This bug is crippling IPv6 on my machine.

Would it be possible to get this fixed for 12.04 LTS?

Thanks,
Matthew.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013597

Title:
  No default route for stateful DHCPv6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1013597/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1013597] Re: No default route for stateful DHCPv6

[Matthew Hall]

P.S.: I just found a possible workaround for the fact that configuring
accept_ra does not work. In addition to the above one, up sysctl
net.ipv6.conf.$IFACE.accept_ra=1, you can install the ndisc6 package and
add up /bin/rdisc6 $IFACE to cause a manual discovery from userspace.
However I'm not sure if the kernel will also get the response and
process it. Maybe someone who knows more on this part could comment...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013597

Title:
  No default route for stateful DHCPv6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1013597/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 858265] Re: No support for power management

[Matthew Hall]

Hey, this bug is quite serious and does not seem to be getting much
attention.

It was causing crashing and overheating on my HP 8510w. It would be nice
if the old 2D only nv driver could be supported in addition to nouveau
as that driver did not cause nearly as much of an issue.

If nothing will be fixed then at least the workaround should be made
clearly available. I had to disassemble the system and look for broken /
hot components to find the cause of the issues.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858265

Title:
  No support for power management

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/858265/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1080978] [NEW] apport forcefully overrides sysctl kernel.core_pattern from values set in /etc/sysctl.*

[Matthew Hall]

Public bug reported:

I think that the way apport registers itself as a core dump handler with
the system is badly behaved with respect to other configuration
processes one would expect to follow on a Debian or Ubuntu based system.
It forcibly overrides settings specified by a user in /etc/sysctl.conf,
and does not employ /etc/sysctl.d. Thus it is overriding settings that
have been configured elsewhere upon start and upon shutdown.

I think perhaps it should be checking for non-default values in these
settings and not dynamically playing with them while it starts and
stops.

Thanks,
Matthew.

mhall@mhsm:src$ sudo fgrep kernel.core /etc/sysctl.conf
kernel.core_pattern = /var/crash/core.%e.%u.%t
kernel.core_uses_pid = 1
mhall@mhsm:src$ 

$ sudo sysctl -a | fgrep -i kernel.core
kernel.core_uses_pid = 1
kernel.core_pattern = |/usr/share/apport/apport %p %s %c
kernel.core_pipe_limit = 0

$ cat /etc/init/apport.conf 
... SNIP ...
pre-start script
... SNIP ...
echo |/usr/share/apport/apport %p %s %c  /proc/sys/kernel/core_pattern
... SNIP ...
post-stop script
... SNIP ...
if [ `dd if=/proc/sys/kernel/core_pattern count=1 bs=1 2/dev/null` != 
| ]
then
exit 1
else
echo core  /proc/sys/kernel/core_pattern
fi
end script

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1080978

Title:
  apport forcefully overrides sysctl kernel.core_pattern from values set
  in /etc/sysctl.*

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1080978/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs