[Bug 2056743] Re: Keyboard stops working after suspend on Dell XPS 13

[Axel G. Rossberg]

With the latest kernel update from Ubuntu (5.15.0-106-generic) the
problem has been solved.

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

Title:
  Keyboard stops working after suspend on Dell XPS 13

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


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

[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

[Axel Schneck]

Running an apt upgrade rather than apt-get upgrade installed the new kernel now.
Just installed on testserver and tried CIFS mounts with a short test.
It seems working now, thanks !
I'll install as soon as possible this kernel on 2 more productive servers and 
try what's happen  
Bye
Axel

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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


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

[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

[Axel Schneck]

Seems apt-upgrade will not download new kernel:
Die folgenden Pakete sind zurückgehalten worden:
  linux-generic linux-headers-generic linux-image-generic 
ubuntu-advantage-tools ubuntu-pro-client-l10n

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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


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

[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

[Axel Schneck]

I'm totally confused now. Last note her says you're wating for confirmation, 
but I got 2 emails telling me, that the fixed kernel has been released now. But 
when I do a apt-get update and apt-get upgrade still 104 will be installed? Did 
I misunderstood something?
Axel

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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


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

Antw: [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

[Axel Schneck]

Thanks a lot !
Axel
>>> engaging374 <2060...@bugs.launchpad.net> 19.04.2024 10:16 >>>
@Alex

Well it's officially released now. It's up to you to install the patch.
:-)

I think someone needs to verify the patch as soon as it's in -proposed
state. Without verification it will be dropped from the source code. (
-> no official fix will be provided in -updates.)

Normally it's not the case if multiple users are affected. Someone just
needs to do the verification work.

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/2060780


Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

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

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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


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

[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

[Axel Schneck]

This bug was the first time I came into this forum, so sorry if this a dumb 
question:
today I got 3 emails that that a fix might be available and I have to test it. 
If I do nbot the fix will be removed from kernel?
Really? Is it really needed that I do some tests after so many already did? 
Currently I'm out of office so it's complicated to test anything.
As far as I understand it is already fixed and confirmed?

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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


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

[Bug 1793465] Re: Mate Panel consumes huge amount of memory even when idling

[Axel G. Rossberg]

I am running (vanilla) Ubuntu 22.04.4 LTS and see the exact same issues
that Saptarshi Roy reported 4 years ago.

I might add that I am using Evolution EWS. If the issue stems from this,
it might explain why most users don't have it.

My clock in the indicator bar also shows time in seconds.

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

Title:
  Mate Panel consumes huge amount of memory even when idling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1793465/+subscriptions


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

[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

[Axel Schneck]

Hello,

I just tested your suggestion wit 104
It's working here with this kernel
Dont understand why you will still provide a faulty kernel until end of month?
We have a lot of servers here using CIFS mounts and we have to prevent all of 
them now from getting a faulty kernel.
bye
Axel

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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


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

[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

[Axel Schneck]

Same problems here. Get error messages like "Too many symlinks" and exactly the 
same as in this description. 
Found also, that CIFS mounts to Netapp mostly works, but df -h doesnt show them 
and mounts to other CIFS shares doesnt work.
Verified it on 5 Linux Boxes, all started failing after patch and working again 
when go back to snapshot from yesterday (before kernel patch): These patches 
are he "bad ones":

Start-Date: 2024-04-09  06:21:54
Commandline: /usr/bin/unattended-upgrade
Install: linux-image-5.15.0-102-generic:amd64 (5.15.0-102.112, automatic), 
linux-modules-5.15.0-102-generic:amd64 (5.15.0-102.112, automatic), 
linux-headers-5.15.0-102:amd64 (5.15.0-102.112, automatic), 
linux-modules-extra-5.15.0-102-generic:amd64 (5.15.0-102.112, automatic), 
linux-headers-5.15.0-102-generic:amd64 (5.15.0-102.112, automatic)
Upgrade: linux-headers-generic:amd64 (5.15.0.101.98, 5.15.0.102.99), 
linux-generic:amd64 (5.15.0.101.98, 5.15.0.102.99), linux-image-generic:amd64 
(5.15.0.101.98, 5.15.0.102.99)
End-Date: 2024-04-09  06:22:23

Start-Date: 2024-04-09  06:22:26
Commandline: /usr/bin/unattended-upgrade
Remove: linux-modules-5.15.0-101-generic:amd64 (5.15.0-101.111), 
linux-modules-extra-5.15.0-101-generic:amd64 (5.15.0-101.111), 
linux-image-5.15.0-101-generic:amd64 (5.15.0-101.111)
End-Date: 2024-04-09  06:22:30

Start-Date: 2024-04-09  06:22:33
Commandline: /usr/bin/unattended-upgrade
Remove: linux-headers-5.15.0-101-generic:amd64 (5.15.0-101.111)
End-Date: 2024-04-09  06:22:34

Start-Date: 2024-04-09  06:22:36
Commandline: /usr/bin/unattended-upgrade
Remove: linux-headers-5.15.0-101:amd64 (5.15.0-101.111)
End-Date: 2024-04-09  06:22:37

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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


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

[Bug 2057924] [NEW] Display after a computer sleep

[Axel SILVY]

Public bug reported:

After a computer sleep, each window appear under the dock launcher. See
the attachment for and example.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 14 13:06:45 2024
DistUpgraded: 2022-08-14 08:22:53,939 ERROR Cache can not be locked (E:Could 
not get lock /var/lib/dpkg/lock-frontend. It is held by process 35271 (jammy), 
W:Be aware that removing the lock file is not a solution and may break your 
system., E:Impossible d'obtenir le verrou de dpkg 
(/var/lib/dpkg/lock-frontend). Il est possible qu'un autre processus l'utilise.)
DistroCodename: jammy
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 [1028:0816]
InstallationDate: Installed on 2021-03-01 (1108 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 005: ID 0a5c:5834 Broadcom Corp. 5880
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 5490
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-25-generic 
root=UUID=2243852e-cb82-44e5-9287-eb132a652223 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-08-14 (578 days ago)
dmi.bios.date: 12/12/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0DH2HV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd12/12/2023:br1.33:svnDellInc.:pnLatitude5490:pvr:rvnDellInc.:rn0DH2HV:rvrA00:cvnDellInc.:ct10:cvr:sku0816:
dmi.product.family: Latitude
dmi.product.name: Latitude 5490
dmi.product.sku: 0816
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy ubuntu wayland-session

** Attachment added: "Capture d’écran du 2024-03-14 13-09-46.png"
   
https://bugs.launchpad.net/bugs/2057924/+attachment/5755960/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202024-03-14%2013-09-46.png

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

Title:
  Display after a computer sleep

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


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

[Bug 2056743] [NEW] Keyboard stops working after suspend on Dell XPS 13

[Axel G. Rossberg]

Public bug reported:

The problem occurs with the 5.15.0-102 kernel but not with 5.15.0-100.

The issue seems to be identical to the problem reported for 6.7.0 here:
https://bbs.archlinux.org/viewtopic.php?id=292203

On the page linked above is says a patch was submitted 2024-01-26 and
the problem solved 2024-03-04 in linux 6.7.5 or linux-lts 6.6.17.

I'm concerned that this still needs fixing in the 5.xxx kernel branch.

Touchpad does not freeze and mouse-control of windows still works, so
it's different from a bug reported elsewhere.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-102-generic 5.15.0-102.112
ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143
Uname: Linux 5.15.0-100-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  axel   2494 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 11 09:54:23 2024
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378
InstallationDate: Installed on 2018-08-31 (2018 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9370
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-100-generic 
root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-100-generic N/A
 linux-backports-modules-5.15.0-100-generic  N/A
 linux-firmware  20220329.git681281e4-0ubuntu3.29
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2022
dmi.bios.release: 1.21
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.21.0
dmi.board.name: 0W970W
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001

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


** Tags: amd64 apport-bug jammy package-from-proposed

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

Title:
  Keyboard stops working after suspend on Dell XPS 13

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


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

[Bug 1964538] [NEW] package libclojure-java 1.9.0-6~18.04 failed to install/upgrade: installed libclojure-java package post-installation script subprocess returned error exit status 2

[Axel Amthor]

Public bug reported:

-

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libclojure-java 1.9.0-6~18.04
ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262
Uname: Linux 4.4.0-210-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
Date: Thu Mar 10 23:33:34 2022
Dependencies:
 libcore-specs-alpha-clojure 0.1.24-1
 libjsr166y-java 1.7.0-2
 libspec-alpha-clojure 0.1.143-1
Ec2AMI: ami-0af467454b869e2cf
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-west-1a
Ec2InstanceType: m3.2xlarge
Ec2Kernel: aki-52a34525
Ec2Ramdisk: unavailable
ErrorMessage: installed libclojure-java package post-installation script 
subprocess returned error exit status 2
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.14
SourcePackage: clojure
Title: package libclojure-java 1.9.0-6~18.04 failed to install/upgrade: 
installed libclojure-java package post-installation script subprocess returned 
error exit status 2
UpgradeStatus: Upgraded to bionic on 2022-03-10 (0 days ago)

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


** Tags: amd64 apport-package bionic ec2-images

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

Title:
  package libclojure-java 1.9.0-6~18.04 failed to install/upgrade:
  installed libclojure-java package post-installation script subprocess
  returned error exit status 2

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


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

Re: [Bug 1963276] Re: Qutebrowser not launching on arm64

[Axel Beckert]

Hi,

avdzm wrote:
> I saw on debian uses a newer version than what is on ubuntu mate's repo.

Right, I noticed this, too. (Was surprised how old the version in
20.04 is. But then again there were indeed a lot of qutebrowser
releases since early 2020.)

For Debian I could have been able to help out with Backports, but for
Ubuntu someone else would need to do that (in case it would have
helped in your case, too).

> So I have tried downloading source code for qutebrowser
> https://github.com/qutebrowser/qutebrowser/archive/refs/tags/v2.4.0.tar.gz
> run "setup.py install" runs successfully, but fails to launch with the same 
> error message. 
> 
> CRITICAL: Could not initialize GLX

Thanks for testing this. Indeed interesting that this still shows up
with 2.4.0. This points towards the issue being indeed in the Qt
version of Ubuntu 20.04.

Have you tried upstream's suggestion in the Debian bug report and
installed and tried another web browser with the same rendering
engine, e.g. "falkon"?

If falkon fails with the same error, the cause of the issue is not in
qutebrowser. (But it is obviously affected nevertheless.)

> I'll post a bug report on qutebrowser's page.

Could help as well although I suspect that he will ask to try out
falkon as well. But maybe he knows a workaround (in case it's indeed a
Qt issue).

    Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

Title:
  Qutebrowser not launching on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1963276/+subscriptions


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

[Bug 1963276] Re: Qutebrowser not launching on arm64

[Axel Beckert]

@alecos85: "No solution" is not true. That bug has been closed by the
reporter that upgrading qutebrowser to a more recent version has solved
the issue. (Although I suspect that actually an Qt upgrade in the same
timeframe was the real reason for this being fixed. See upstream's
comment in that bug report.)

Hint: Don't rely on external mailing list archives when reading Debian
bug reports. Read the bug report in Debian's Bug Tracking System
directly: https://bugs.debian.org/960384

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

Title:
  Qutebrowser not launching on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1963276/+subscriptions


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

[Bug 1963276] Re: Qutebrowser not launching on arm64

[Axel Beckert]

** Bug watch added: Debian Bug tracker #960384
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960384

** Also affects: qutebrowser (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960384
   Importance: Unknown
   Status: Unknown

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

Title:
  Qutebrowser not launching on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1963276/+subscriptions


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

[Bug 1961494] [NEW] Gimp asks for password to manage units upon startup

[Axel]

Public bug reported:

When I started gimp on my freshly updated impish system, gimp showed the
startup splash screen, showed loading scanimage and then prompted me for
a password to "manage units".

I would have expected to start gimp without getting greeted by a
privileges dialogue.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gimp 2.10.24-2
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 19 11:51:12 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-12-29 (1878 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: gimp
UpgradeStatus: Upgraded to impish on 2022-02-19 (0 days ago)

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


** Tags: amd64 apport-bug impish

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

Title:
  Gimp asks for password to manage units upon startup

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


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

[Bug 1960842] Re: failed to load module `zsh/mathfunc': /lib/x86_64-linux-gnu/libm.so.6

[Axel Beckert]

@crashbit-gmail: There was no update of zsh in Jammy so far. If an
update fixed this, it was not in zsh but maybe in a library. And indeed,
one day after this bug report, glibc 2.35 (as mentioned in the missing
symbol) got uploaded to jammy as well:
https://launchpad.net/ubuntu/+source/glibc/2.35-0ubuntu1

Weird that zsh was already built against it before it reached jammy —
that looks like weird buildd setup in Ubuntu — but still had a
dependency on "libc6 (>= 2.34)".

Nevertheless the latter might be the actual bug, but then again, it
might be an issue in debhelper or so. There though might be other
causes. I though still kinda doubt that this is cause by zsh's build
system.

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

Title:
  failed to load module `zsh/mathfunc': /lib/x86_64-linux-gnu/libm.so.6

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


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

[Bug 1960842] Re: failed to load module `zsh/mathfunc': /lib/x86_64-linux-gnu/libm.so.6

[Axel Beckert]

Seems to be an Ubuntu-only issue. Can't reproduce on Debian Unstable.

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

Title:
  failed to load module `zsh/mathfunc': /lib/x86_64-linux-gnu/libm.so.6

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


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

[Bug 1960727] Re: When apt holds back updates, it fails to inform the user of the reason

[Axel Beckert]

** Package changed: aptitude (Ubuntu) => apt (Ubuntu)

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

Title:
  When apt holds back updates, it fails to inform the user of the reason

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


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

[Bug 1860323] Re: fping not working if ipv6 is disabled

[Axel Beckert]

Closing as fix-released since the fix should now be also in the most
recent Ubuntu LTS version (i.e. Ubuntu 20.04 LTS).

** Changed in: fping (Ubuntu)
   Status: New => Fix Released

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

Title:
  fping not working if ipv6 is disabled

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


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

[Bug 1959485] Re: reproducible crash in jammy

[Axel Beckert]

If you can still reproduce this, can you run "aptitude-create-state-
bundle lp-1959485-crash-dist-upgrade.tbz2" and send me the resulting tar
ball?

(You probably need to upload the tar-ball somewhere as these can have a
size around several hundred megabytes. Not sure if Launchpad can host
such big files as attachement to bug reports.)

** Changed in: aptitude (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- reproducible crash in jammy
+ reproducible crash in jammy: Uncaught exception: ../../src/ui.cc:1549: void 
auto_fix_broken(): Assertion "resman->resolver_exists()" failed.

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

Title:
  reproducible crash in jammy: Uncaught exception: ../../src/ui.cc:1549:
  void auto_fix_broken(): Assertion "resman->resolver_exists()" failed.

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


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

[Bug 1951424] Re: No audio after install ubuntu 21.10 on Acer swift 3

[Axel Lin]

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  No audio after install ubuntu 21.10 on Acer swift 3

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


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

[Bug 1951424] Re: No audio after install ubuntu 21.10 on Acer swift 3

[Axel Lin]

Any workaround available to fix this bug? Or I have to wait until next
linux-image package update?

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

Title:
  No audio after install ubuntu 21.10 on Acer swift 3

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


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

[Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

[Axel Beckert]

** Bug watch added: Debian Bug tracker #18
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18

** Also affects: zsh (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18
   Importance: Unknown
   Status: Unknown

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

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


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

[Bug 1951424] [NEW] No audio after install ubuntu 21.10 on Acer swift 3

[Axel Lin]

: hci0: Device booted in 14633 usecs
[4.212604] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
[4.214524] Bluetooth: hci0: Applying Intel DDC parameters completed
[4.217520] Bluetooth: hci0: Firmware revision 0.4 build 164 week 35 2021
[4.277577] Bluetooth: hci0: MSFT filter_enable is already on
[4.282349] NET: Registered protocol family 38
[4.417930] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[4.509512] rfkill: input handler disabled
[6.839147] intel-sdw intel-sdw.1: Clock stop failed -110
[6.839152] intel-sdw intel-sdw.1: cannot enable clock stop on suspend
[6.839160] intel-sdw intel-sdw.0: Clock stop failed -110
[6.839161] intel-sdw intel-sdw.0: cannot enable clock stop on suspend

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-modules-5.13.0-21-generic 5.13.0-21.21
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  axel   1389 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 18 21:45:07 2021
InstallationDate: Installed on 2021-11-17 (1 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: Acer Swift SF314-511
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=7ff3fa96-2956-40c5-8019-34ad3e574c1c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-21-generic N/A
 linux-backports-modules-5.13.0-21-generic  N/A
 linux-firmware 1.201.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/03/2021
dmi.bios.release: 1.9
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Sake_TL
dmi.board.vendor: TGL
dmi.board.version: V1.09
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.09
dmi.ec.firmware.release: 1.5
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd09/03/2021:br1.9:efr1.5:svnAcer:pnSwiftSF314-511:pvrV1.09:rvnTGL:rnSake_TL:rvrV1.09:cvnAcer:ct10:cvrV1.09:sku:
dmi.product.family: Swift 3
dmi.product.name: Swift SF314-511
dmi.product.sku: 
dmi.product.version: V1.09
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug impish wayland-session

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

Title:
  No audio after install ubuntu 21.10 on Acer swift 3

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


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

[Bug 1941786] Re: OpenMPI 4.0.3 forgets to link open-pal

[Axel Huebl]

There is a patch available in
  https://github.com/open-mpi/ompi/pull/9077
which will be part of OpenMPI 4.0.7

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

Title:
  OpenMPI 4.0.3 forgets to link open-pal

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


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

[Bug 1941786] Re: OpenMPI 4.0.3 forgets to link open-pal

[Axel Huebl]

Cross-ref GitHub: https://github.com/open-mpi/ompi/issues/9317

** Bug watch added: github.com/open-mpi/ompi/issues #9317
   https://github.com/open-mpi/ompi/issues/9317

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

Title:
  OpenMPI 4.0.3 forgets to link open-pal

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


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

[Bug 1941786] [NEW] OpenMPI 4.0.3 forgets to link open-pal

[Axel Huebl]

Public bug reported:

Hi,

I am trying to compile a C++ program with CMake 3.16.3 on Ubuntu 20.04
LTS, which ships OpenMPI 4.0.3.

I realized that the
  mpic++ --showme:link
flags forget to link `-lopen-pal`, which is part of the OpenMPI lib dir.
  -pthread -L/usr/lib/x86_64-linux-gnu/openmpi/lib -lmpi_cxx -lmpi

Following that, a CMake CXX program compiled with clang++ that checks for 
`find_package(MPI REQUIRED)` will error out with:
```
-- Found MPI_C: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so (found version 
"3.1") 
-- Could NOT find MPI_CXX (missing: MPI_CXX_WORKS) 
CMake Error at 
/usr/local/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:230 
(message):
-- Configuring incomplete, errors occurred!
  Could NOT find MPI (missing: MPI_CXX_FOUND CXX) (found version "3.1")
```

The reason for that is in the compile check
```
/opt/rocm/llvm/bin/clang++   -pthread 
CMakeFiles/cmTC_abf94.dir/test_mpi.cpp.o  -o cmTC_abf94  
-Wl,-rpath,/usr/lib/x86_64-linux-gnu/openmpi/lib 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so 
ld.lld: error: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so: undefined 
reference to opal_class_init_epoch [--no-allow-shlib-undefined]
ld.lld: error: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so: undefined 
reference to opal_list_item_t_class [--no-allow-shlib-undefined]
ld.lld: error: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so: undefined 
reference to opal_class_initialize [--no-allow-shlib-undefined]
ld.lld: error: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so: undefined 
reference to opal_uses_threads [--no-allow-shlib-undefined]
```

where the linker refuses the missing lib and fails the check.

The solution to this is to make sure that
  mpic++ --showme:link
appends
  -lopen-pal
as well.

User-side work-around until fix is applied:
  export LDFLAGS="-lopen-pal"

** Affects: openmpi (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/1941786

Title:
  OpenMPI 4.0.3 forgets to link open-pal

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


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

[Bug 1920808] Re: ubuntu-20.04.2 for raspberry, updating and installing errors

[Axel Keller]

Hi Paride,

I'm so sorry, but I cannot reproduce the problem.

In the last 2 weeks I setup my Raspberry PI3 about 20 times, always with
the same image. Booting the fresh installed system I got the problem
with the system clock. But after I could solve the problem it doesn't
appear again, even with new installations.

Thank you for your help. I'm a little bit at a loss.

Regards
Axel

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

Title:
  ubuntu-20.04.2 for raspberry, updating and installing errors

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

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

[Bug 1920808] Re: ubuntu-20.04.2 for raspberry, updating and installing errors

[Axel Keller]

The workaround described only works only once, but not any more after
boot.

The reason is the missing service 'chrony' since the service 'ntp' isn't longer 
supported by timedatectl. So the problem can be solved with:
$ sudo apt-get install chrony
$ sudo timedatectl set-ntp true
The option 'set-ntp' is quite irritating, but works with chrony.


** Package changed: ubuntu => chrony (Ubuntu)

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

Title:
  ubuntu-20.04.2 for raspberry, updating and installing errors

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

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

[Bug 1920808] [NEW] ubuntu-20.04.2 for raspberry, updating and installing errors

[Axel Keller]

Public bug reported:

Running ubuntu-20.04.2-preinstalled-server-arm64+raspi.img on a
Raspberry PI 3

After installation of the Ubuntu software updating apps and installing
new apps fail. Several repositories cannot be accessed because their
certificates aren't yet valid. The reason is that the 'timedate' service
does not synchronize the system clock after boot. At the moment the
system clock will be set on the first system start 1 year behind
(1.4.2020).

Workaround: After replacing timedate with ntp all works fine.

$ sudo timedatectl set-ntp no
$ sudo apt install ntp
$ ntpq -p

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: 20.04.2 arm64 installing raspberry ubuntu updating

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

Title:
  ubuntu-20.04.2 for raspberry, updating and installing errors

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

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

[Bug 1920682] Re: Lenovo x1 Yoga freeze after stylus touches the display

[Axel Hack]

Stylus-problem occurs with kernel 5.8.0-45.51~20.04-generic 5.8.18.
After booting into kernel 5.8.0-44.50~20.04-generic 5.8.18 there is NO PROBLEM. 
kernel 5.8.0-44.50~20.04-generic 5.8.18

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

Title:
  Lenovo x1 Yoga freeze after stylus touches the display

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

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

[Bug 1920682] Re: Lenovo x1 Yoga freeze after stylus touches the display

[Axel Hack]

just tried to use an external Wacom tablet(Bamboo): Works with no problems. 
Only the built in stylus lets the x1 Yoga freeze.
I'm using a Wacom one on another machine. Same kernel (Ubuntu 
5.8.0-45.51~20.04.1-generic 5.8.18). No problem there. Installed software very 
similar.
It seems to only freeze my x1 Yoga

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

Title:
  Lenovo x1 Yoga freeze after stylus touches the display

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

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

[Bug 1920611] Re: ubuntu-20.04.2 for raspberry, java installation fails

[Axel Keller]

Problem solved:

Booting the Ubuntu system the timedate service didn't work (bug?). The
date was one year behind. Therefore some certificates failed and thus
some connections to repositories.

I changed timedate to ntp and all works fine!

   $ sudo timedatectl set-ntp no
   $ sudo apt install ntp   
   $ ntpq -p
   $ date

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

Title:
  ubuntu-20.04.2 for raspberry, java installation fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-11/+bug/1920611/+subscriptions

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

[Bug 1920682] Re: Lenovo x1 Yoga freeze after stylus touches the display

[Axel Hack]

nut shure about the package

** Package changed: ubuntu => libwacom (Ubuntu)

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

Title:
  Lenovo x1 Yoga freeze after stylus touches the display

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

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

[Bug 1920682] [NEW] Lenovo x1 Yoga freeze after stylus touches the display

[Axel Hack]

Public bug reported:

Had no problem with stylus. Since one of the last updates the stylus
freezes the notebook. No reaction to nothing. Only power off by holding
hardware button works. Is also mentionned in
https://askubuntu.com/questions/1324000/thinkpad-yoga-x1-gen-2-freezes-
completely-when-stylus-is-used-ubuntu-20-04-2

** Affects: ubuntu
 Importance: Undecided
 Status: New

** Attachment added: "lspci-vv.log"
   
https://bugs.launchpad.net/bugs/1920682/+attachment/5478756/+files/lspci-vv.log

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

Title:
  Lenovo x1 Yoga freeze after stylus touches the display

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

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

[Bug 1075629] Re: new upstream release(s)

[Axel Navarro]

Could you please update the tldr package? the current version in Ubuntu
apt is really old.

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

Title:
  new upstream release(s)

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

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

[Bug 1915205] Re: CVE-2020-9366

[Axel Beckert]

Actually this never made it into any LTS release as only 4.7.x versions
were affected and 18.04 has a 4.6.x version and 20.04 has 4.8.0.

** Bug watch added: Debian Bug tracker #950896
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950896

** Also affects: screen (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950896
   Importance: Unknown
   Status: Unknown

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

Title:
  CVE-2020-9366

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

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

[Bug 1915205] Re: CVE-2020-9366

[Axel Beckert]

Marking as "fix release" as Ubuntu already has 4.8.0-1.

** Changed in: screen (Ubuntu)
   Status: New => Fix Released

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

Title:
  CVE-2020-9366

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

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

[Bug 1914929] Re: Raspberry Pi u-boot-rpi package version 2020.10+dfsg-1ubuntu0~20.10.1 prevents Bluetooth Devices Connecting

[axel]

** Description changed:

  After updating this package version from 2020.04+dfsg-2ubuntu1 to
  2020.10+dfsg-1ubuntu0~20.10.1 any Bluetooth device on a Raspberry Pi 4
  8GB will no longer be able to pair.
  
  After the package install all previously paired devices disappear.
  
- The devices when attempting to repair will then connect then disconnect
- immediately afterwards, Subsequent attempts to connect will fail with
- "no route to host error". Not attempts to remove and re add the devices
- seems to resolve the problem
+ The devices when attempting to re-pair will then connect then disconnect
+ immediately afterwards on initial pairing. Subsequent attempts to
+ connect will fail with "no route to host" error. No subsequentattempts
+ to remove and re add the devices seems to resolve the problem.
  
  To fix the issue you have to uninstall this package and go back to the
  previous versions.
  
  Any devices you had paired before the upgrade will re appear ... but if
- you tried to pair them after the upgrade they will continue to have the
- same connect and disconnect behavior. However this time removing the
+ you tried to pair them *after* the upgrade they will continue to have
+ the same connect and disconnect behavior. However this time removing the
  device and repairing will fix the problem.
  
  Any device you did not attempt to connect / re pair after the upgrade
- work seamlessly again without any need to remove the device.
+ work seamlessly again without any need to remove and repair the device.
  
  I have recreated this issue on Ubuntu MATE Ubuntu 20.10 Groovy

** Description changed:

- After updating this package version from 2020.04+dfsg-2ubuntu1 to
- 2020.10+dfsg-1ubuntu0~20.10.1 any Bluetooth device on a Raspberry Pi 4
- 8GB will no longer be able to pair.
+ After updating this package (u-boot-rpi) version from 2020.04+dfsg-
+ 2ubuntu1 to 2020.10+dfsg-1ubuntu0~20.10.1 any Bluetooth device on a
+ Raspberry Pi 4 8GB will no longer be able to pair.
  
  After the package install all previously paired devices disappear.
  
  The devices when attempting to re-pair will then connect then disconnect
  immediately afterwards on initial pairing. Subsequent attempts to
  connect will fail with "no route to host" error. No subsequentattempts
  to remove and re add the devices seems to resolve the problem.
  
  To fix the issue you have to uninstall this package and go back to the
  previous versions.
  
  Any devices you had paired before the upgrade will re appear ... but if
  you tried to pair them *after* the upgrade they will continue to have
  the same connect and disconnect behavior. However this time removing the
  device and repairing will fix the problem.
  
  Any device you did not attempt to connect / re pair after the upgrade
  work seamlessly again without any need to remove and repair the device.
  
  I have recreated this issue on Ubuntu MATE Ubuntu 20.10 Groovy

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

Title:
  Raspberry Pi u-boot-rpi package version 2020.10+dfsg-1ubuntu0~20.10.1
  prevents Bluetooth Devices Connecting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1914929/+subscriptions

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

[Bug 1914929] [NEW] Raspberry Pi u-boot-rpi package version 2020.10+dfsg-1ubuntu0~20.10.1 prevents Bluetooth Devices Connecting

[axel]

Public bug reported:

After updating this package version from 2020.04+dfsg-2ubuntu1 to
2020.10+dfsg-1ubuntu0~20.10.1 any Bluetooth device on a Raspberry Pi 4
8GB will no longer be able to pair.

After the package install all previously paired devices disappear.

The devices when attempting to repair will then connect then disconnect
immediately afterwards, Subsequent attempts to connect will fail with
"no route to host error". Not attempts to remove and re add the devices
seems to resolve the problem

To fix the issue you have to uninstall this package and go back to the
previous versions.

Any devices you had paired before the upgrade will re appear ... but if
you tried to pair them after the upgrade they will continue to have the
same connect and disconnect behavior. However this time removing the
device and repairing will fix the problem.

Any device you did not attempt to connect / re pair after the upgrade
work seamlessly again without any need to remove the device.

I have recreated this issue on Ubuntu MATE Ubuntu 20.10 Groovy

** Affects: u-boot (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/1914929

Title:
  Raspberry Pi u-boot-rpi package version 2020.10+dfsg-1ubuntu0~20.10.1
  prevents Bluetooth Devices Connecting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1914929/+subscriptions

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

[Bug 1906131] Re: No rule to make target 'scripts/module.lds' while building out-of-tree modules

[Axel Siebenwirth]

This is happening to my NVIDIA module build with kernel 5.10.12 as well.

root@jaxel:~# dpkg-reconfigure nvidia-dkms-460 
Removing all DKMS Modules
Done.
update-initramfs: deferring update (trigger activated)
update-initramfs: Generating /boot/initrd.img-5.9.16-050916-generic
INFO:Enable nvidia
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
Loading new nvidia-460.39 DKMS files...
Building for 5.9.16-050916-generic 5.10.12-051012-generic
Building for architecture x86_64
Building initial module for 5.9.16-050916-generic
Secure Boot not enabled on this system.
Done.

nvidia.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.9.16-050916-generic/updates/dkms/

nvidia-modeset.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.9.16-050916-generic/updates/dkms/

nvidia-drm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.9.16-050916-generic/updates/dkms/

nvidia-uvm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.9.16-050916-generic/updates/dkms/

depmod...

DKMS: install completed.
Building initial module for 5.10.12-051012-generic
ERROR (dkms apport): kernel package linux-headers-5.10.12-051012-generic is not 
supported
Error! Bad return status for module build on kernel: 5.10.12-051012-generic 
(x86_64)
Consult /var/lib/dkms/nvidia/460.39/build/make.log for more information.

--- /var/lib/dkms/nvidia/460.39/build/make.log

make -f ./scripts/Makefile.modpost
  sed 's/ko$/o/' /var/lib/dkms/nvidia/460.39/build/modules.order | 
scripts/mod/modpost  -a   -o /var/lib/dkms/nvidia/460.39/build/Module.symvers 
-e -i Module.symvers   -T -
make -f ./scripts/Makefile.modfinal
make[3]: *** No rule to make target 'scripts/module.lds', needed by 
'/var/lib/dkms/nvidia/460.39/build/nvidia-drm.ko'.  Stop.
make[3]: *** Waiting for unfinished jobs
  cc -Wp,-MMD,/var/lib/dkms/nvidia/460.39/build/.nvidia-drm.mod.o.d  -nostdinc 
-isystem /usr/lib/gcc/x86_64-linux-gnu/9/include -I./arch/x86/include 
-I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi 
-I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi 
-include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h 
-D__KERNEL__ -fmacro-prefix-map=./= -Wall -Wundef -Werror=strict-prototypes 
-Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE 
-Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type 
-Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx 
-m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 
-mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone 
-mcmodel=kernel -DCONFIG_X86_X32_ABI -Wno-sign-compare 
-fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern 
-mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks 
-Wno-frame-address -Wno-format-truncation -Wno-format-overflow 
-Wno-address-of-packed-member -O2 --param=allow-store-data-races=0 
-Wframe-larger-than=1024 -fstack-protector-strong -Wno-unused-but-set-variable 
-Wimplicit-fallthrough -Wno-unused-const-variable -fno-omit-frame-pointer 
-fno-optimize-sibling-calls -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY 
-Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-stringop-truncation 
-Wno-array-bounds -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized 
-fno-strict-overflow -fno-stack-check -fconserve-stack -Werror=date-time 
-Werror=incompatible-pointer-types -Werror=designated-init -fcf-protection=none 
-Wno-packed-not-aligned  -DMODULE  -DKBUILD_BASENAME='"nvidia_drm.mod"' 
-DKBUILD_MODNAME='"nvidia_drm"' -c -o 
/var/lib/dkms/nvidia/460.39/build/nvidia-drm.mod.o 
/var/lib/dkms/nvidia/460.39/build/nvidia-drm.mod.c
make[2]: *** [scripts/Makefile.modpost:117: __modpost] Error 2
make[1]: *** [Makefile:1709: modules] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.10.12-051012-generic'

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

Title:
  No rule to make target 'scripts/module.lds' while building out-of-tree
  modules

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

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

[Bug 1796034] Re: lubuntu 18.10 falkon nouveau test on qutebrowser crashed with SIGSEGV in __GI_____strtoul_l_internal()

[Axel Beckert]

I assume that since https://bugs.debian.org/910317 is fixed for a long
time, this issue is no more present either.

Please file a new bug report if you still can reproduce this (or seeming
identical) issues in recent versions of qutebrowser, e.g. 1.14.1 or
2.0.1 and above.

** Changed in: qutebrowser (Ubuntu)
   Status: New => Fix Released

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

Title:
  lubuntu 18.10 falkon nouveau test on qutebrowser crashed with SIGSEGV
  in __GI_strtoul_l_internal()

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

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

[Bug 1913205] [NEW] [libadios-dev] adios.pc file missing on focal+

[Axel Huebl]

Public bug reported:

Hi,

on the libadios-dev package lacks the adios.pc file (and adios_config
executable script) on focal and newer.

On bionic, the file is still shipped:
  https://packages.ubuntu.com/bionic/libadios-dev

Can this please be added again?

Thank you for your help,
Axel

** Affects: adios (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/1913205

Title:
  [libadios-dev] adios.pc file missing on focal+

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

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

[Bug 1723392] Re: Please update backuppc to 4.x release (now 4.2.1) - major improvements and lots of bugfixes

[Axel Beckert]

4.4.0-2 is in hirsute-proposed (and in Debian Testing).

** Changed in: backuppc (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Please update backuppc to 4.x release (now 4.2.1) - major improvements
  and lots of bugfixes

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

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

[Bug 1907932] Re: irqtop emits a warning

[Axel Beckert]

Note: The cited commit and "fix" was in the package ruby, but the
problem in ruby-curses still exists as ruby only silenced the
deprecation warnings by default.

** Summary changed:

- irqtop emits a warning
+ ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby 3.0", 
affects at least irqtop

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

Title:
  ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby
  3.0", affects at least irqtop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1907932/+subscriptions

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

[Bug 1907932] Re: irqtop emits a warning

[Axel Beckert]

This is an issue in ruby-curses, not irqtop. See https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=958973

Interestingly this no more happens on Debian Unstable/Testing. This
seems to have fixed upstream a few months ago:

commit df3f52a6331f1a47af9933b77311a8650727d8d1
  Author: nagachika 
  Date:   2020-09-29 22:43:25 +0900

merge revision(s) 996af2ce086249e904b2ce95ab2fcd1de7d757be:
[Backport #16345] [Backport #17000]

Disable deprecation warning by the default [Feature #16345]

And `-w` option turns it on.

That commit likely made it into ruby 2.7.2, which hit Debian Unstable in
mid-October 2020.

Nevertheless this obviously needs to be fixed in ruby-curses.

** Bug watch added: Debian Bug tracker #958973
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958973

** Also affects: ruby-curses (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ruby-curses (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958973
   Importance: Unknown
   Status: Unknown

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

Title:
  ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby
  3.0", affects at least irqtop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1907932/+subscriptions

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

[Bug 1900008] Re: Sessions of screen does not keep running in background

[Axel Beckert]

@paelzer: This does not sound like exiting the last shell inside the
screen session but closing the xterm/gnome-terminal/lxterminal etc. it
is running in. (Back to "New" for that.)

So in the end this sounds a lot like one of these annoying systemd bugs,
e.g. similar to https://bugs.debian.org/825394, especially with these
systemd messages.

Could though also be the terminal itself, depending on which terminal is
actually being used. Never heard of such a case so far, though. So in
which terminal did this happen? (Might though validate an "Incomplete"
again for this question. Unsure.)

** Changed in: screen (Ubuntu)
   Status: Incomplete => New

** Changed in: screen (Ubuntu)
   Status: New => Incomplete

** Changed in: screen (Ubuntu)
   Status: Incomplete => New

** Bug watch added: Debian Bug tracker #825394
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394

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

Title:
  Sessions of screen does not keep running in background

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

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

[Bug 1896777] [NEW] wireguard-dkms 1.0.20200611-1ubuntu1~16.04.1: wireguard kernel module failed to build

[Axel Chauvin]

Public bug reported:

Appended when I tried to install wireguard

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: wireguard-dkms 1.0.20200611-1ubuntu1~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
DKMSKernelVersion: 4.15.0-42-generic
Date: Wed Sep 23 15:46:34 2020
DuplicateSignature: 
dkms:wireguard-dkms:1.0.20200611-1ubuntu1~16.04.1:/var/lib/dkms/wireguard/1.0.20200611/build/socket.c:139:18:
 error: ‘const struct ipv6_stub’ has no member named ‘ipv6_dst_lookup_flow’
InstallationDate: Installed on 2017-06-20 (1191 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
PackageVersion: 1.0.20200611-1ubuntu1~16.04.1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29
SourcePackage: wireguard-linux-compat
Title: wireguard-dkms 1.0.20200611-1ubuntu1~16.04.1: wireguard kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: wireguard-linux-compat (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  wireguard-dkms 1.0.20200611-1ubuntu1~16.04.1: wireguard kernel module
  failed to build

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

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

[Bug 1893020] [NEW] snap fails to pass chromium arguments

[Axel]

Public bug reported:

$ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04

$ snap --version
snap2.45.3.1
snapd   2.45.3.1
series  16
ubuntu  20.04
kernel  5.4.0-21-generic

$ snap list chromium
Name  VersionRev   Tracking   Publisher   Notes
chromium  84.0.4147.135  1269  latest/stable  canonical✓  -

GOOD:
$ /snap/chromium/current/usr/lib/chromium-browser/chrome --headless  --dump-dom 
/usr/share/doc/bc/bc.html

produces output, while

BAD:
$ /snap/bin/chromium --headless --dump-dom /usr/share/doc/bc/bc.html

fails with

[0826/093125.490825:ERROR:headless_shell.cc(174)] Open multiple tabs is
only supported when remote debugging is enabled.


Debugging hint: I get the same error when calling

$ /snap/chromium/current/usr/lib/chromium-browser/chrome --headless  -- 
dump-dom /usr/share/doc/bc/bc.html
[0826/093139.340093:ERROR:headless_shell.cc(174)] Open multiple tabs is only 
supported when remote debugging is enabled.

(note the extra space between "--" and "dump-dom".


Apologies if this turns out to be an issue with snap-confine or one of its 
siblings!

** Affects: snap (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/1893020

Title:
  snap fails to pass chromium arguments

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

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

[Bug 1663316] Re: package libglib2.0-cil 2.12.10-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Axel Mueller]

libglib2.0-cil has failed during upgrade of 18.04 to 20.04

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

Title:
  package libglib2.0-cil 2.12.10-5 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk-sharp2/+bug/1663316/+subscriptions

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

[Bug 1888280] Re: dctrl-tools should be dependency of debian-goodies

[Axel Beckert]

Nope. It's exactly as it should be for packages with a collection of
small tools like e.g. debian-goodies or devscripts:

* Dependencies of all or at least most tools are in Depends.
* Hard dependencies which just appear in one or very few tools are in 
Recommends. (Other tools in the package are still usable then and if you only 
need them, there must to be a way to not install dependencies of the other, 
unused tools.)
* Optional dependencies of any tool are just in Suggests.

Besides:

* Recommends are installed by default. As you've shown, you explicitly
need to disable them to get into that situation. And as the
documentation (at least Debian's) says: You're then on your own if
something doesn't work because of that.

* The package description explains very verbose which tool needs which
of the Recommends and Suggests.

** Changed in: debian-goodies (Ubuntu)
   Status: New => Invalid

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

Title:
  dctrl-tools should be dependency of debian-goodies

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-goodies/+bug/1888280/+subscriptions

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

[Bug 1883983] Re: MD5 is comprehensively broken at this point

[Axel Beckert]

debsums uses MD5 because dpkg uses MD5.

** Also affects: dpkg (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: Debian Bug tracker #849377
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849377

** Also affects: debsums (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849377
   Importance: Unknown
   Status: Unknown

** Bug watch added: Debian Bug tracker #540215
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540215

** Also affects: debhelper (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540215
   Importance: Unknown
   Status: Unknown

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

Title:
  MD5 is comprehensively broken at this point

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

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

[Bug 1882366] Re: After Installed Oh My Zsh, in taskbar shortcut icon widgets dont have icons and can't open.

[Axel Beckert]

On a first glance, this looks more like an issue in oh-my-zsh than in
zsh.

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

Title:
  After Installed Oh My Zsh, in taskbar shortcut icon widgets dont have
  icons and can't open.

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

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

[Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later

[Axel Leroy]

I'm also impacted, but unlike other users on this thread, I'm not
running Ryzen but I do use a Vega GPU:

CPU : Intel Core i5-3570K
Motherboard : Gigabyte GA-Z77-DS3H
GPU : AMD Radeon Vega 56

Reverting to 5.3.0-51 solves the issue.

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

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

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

[Bug 1875242] Re: Do not fail if using fping6 with -6 flag

[Axel Beckert]

Uploaded the fix to Debian Unstable. Should reach Ubuntu Groovy via
automatic sync from Debian Unstable.

** Changed in: fping (Ubuntu)
   Status: New => Fix Committed

** Changed in: fping (Ubuntu)
 Assignee: (unassigned) => Axel Beckert (xtaran)

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

Title:
  Do not fail if using fping6 with -6 flag

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

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

[Bug 1873423] Re: package zsh-common 5.8-3ubuntu1 failed to install/upgrade: conffile difference visualiser subprocess returned error exit status 127

[Axel Beckert]

It's not your .zshrc (which would be in your home directory) but the
system's /etc/zsh/zshrc which has been deleted and tried to compare.

This issue seems though unrelated to the deletion of /etc/zsh/zshrc,
with which at coped properly:

Configuration file '/etc/zsh/zshrc'
 ==> Deleted (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.

It seems not a zsh issue at all but a general release upgrade issue
which just happened to happen while handling conffiles of the package
zsh-common:

*** zshrc (Y/I/N/O/D/Z) [default=N] ? d
sh: 1: pager: not found
diff: standard output: Broken pipe

So for some reason, /usr/bin/pager (or /bin/pager or so) was not
available during the release upgrade. /usr/bin/pager is usually
/etc/alternatives/pager. Unfortunately, I have not really an idea
against which package this could have caused. Reassigning to ubuntu-
release-upgrader-core for now.

** Package changed: zsh (Ubuntu) => ubuntu-release-upgrader (Ubuntu)

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

Title:
  package zsh-common 5.8-3ubuntu1 failed to install/upgrade: conffile
  difference visualiser subprocess returned error exit status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1873423/+subscriptions

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

[Bug 1255747] Re: lubuntu 13.10 installation (encrypted home, no swap) fails

[axel]

Thanks for your feedback, i've been waiting for something for over 5
years in this matter.

To be honest, I can't tell if this is still an issue on a maintained
version of Ubuntu because in the meantime I've turned my focus away from
Ubuntu, one reason being that bug reports are ignored for extended
amounts of time.

So yeah, let this bug expire...

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

Title:
  lubuntu 13.10 installation (encrypted home, no swap) fails

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

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

[Bug 1865091] [NEW] Backport broken scatter/gather Signatures

[Axel Huebl via ubuntu-bugs]

Public bug reported:

Ubuntu 18.04 LTS ships CUDA 9.1.85 which is broken with provided GCC
compilers in a slightly complex way.

By default, the g++ compiler version is 7.4.0, which is not supported by 
CUDA/NVCC 9.1.85.
Next, CUDA/NVCC 9.1.85 should have provided support for g++ 6. But the release 
overlooked an incompatibility with std::tuple which renders this compiler 
combination not useful either:
  https://gist.github.com/ax3l/9489132

Consequently, users that want to use mature C++11/14 features can still switch 
to install a g++-5 package on Ubuntu 18.04 but this compiler has another set of 
bugs in signatures of gather/scatter intrinsics which were fixed in later GCC 
releases. This fix was unfortunately not backported to GCC 5.5 .
  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=76731

In order to make NVCC+GCC work together on Ubuntu 18.04, I would recommend to 
backport the small patches of three intrinsic files with broken signatures to 
the g++-5 (specifically the libgcc-5-dev) packages:
  https://stackoverflow.com/a/50815334/2719194

Thanks a lot for considering,
Axel

** Affects: gcc-5 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: nvidia-cuda-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: nvidia-cuda-toolkit (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  Ubuntu 18.04 LTS ships CUDA 9.1.85 which is broken with provided GCC
  compilers in a slightly complex way.
  
  By default, the g++ compiler version is 7.4.0, which is not supported by 
CUDA/NVCC 9.1.85.
  Next, CUDA/NVCC 9.1.85 should have provided support for g++ 6. But the 
release overlooked an incompatibility with std::tuple which renders this 
compiler combination not useful either:
-   https://gist.github.com/ax3l/9489132
+   https://gist.github.com/ax3l/9489132
  
- Consequently, users that want to use mature C++11/14 features can still 
switch to install a g++-5 package on Ubuntu 18.04 but this compilers has 
another set of bugs in gather/scatter intrinsics which were fixed in later GCC 
releases. This fix was unfortunately not backported to GCC 5.5 .
-   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=76731
+ Consequently, users that want to use mature C++11/14 features can still 
switch to install a g++-5 package on Ubuntu 18.04 but this compiler has another 
set of bugs in gather/scatter intrinsics which were fixed in later GCC 
releases. This fix was unfortunately not backported to GCC 5.5 .
+   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=76731
  
  In order to make NVCC+GCC work together on Ubuntu 18.04, I would recommend to 
backport the small patches of three intrinsic files with broken signatures to 
the g++-5 (specifically the libgcc-5-dev) packages:
-   https://stackoverflow.com/a/50815334/2719194
+   https://stackoverflow.com/a/50815334/2719194
  
  Thanks a lot for considering!
  Axel

** Description changed:

  Ubuntu 18.04 LTS ships CUDA 9.1.85 which is broken with provided GCC
  compilers in a slightly complex way.
  
  By default, the g++ compiler version is 7.4.0, which is not supported by 
CUDA/NVCC 9.1.85.
  Next, CUDA/NVCC 9.1.85 should have provided support for g++ 6. But the 
release overlooked an incompatibility with std::tuple which renders this 
compiler combination not useful either:
    https://gist.github.com/ax3l/9489132
  
  Consequently, users that want to use mature C++11/14 features can still 
switch to install a g++-5 package on Ubuntu 18.04 but this compiler has another 
set of bugs in gather/scatter intrinsics which were fixed in later GCC 
releases. This fix was unfortunately not backported to GCC 5.5 .
    https://gcc.gnu.org/bugzilla/show_bug.cgi?id=76731
  
  In order to make NVCC+GCC work together on Ubuntu 18.04, I would recommend to 
backport the small patches of three intrinsic files with broken signatures to 
the g++-5 (specifically the libgcc-5-dev) packages:
    https://stackoverflow.com/a/50815334/2719194
  
- Thanks a lot for considering!
+ Thanks a lot for considering,
  Axel

** Description changed:

  Ubuntu 18.04 LTS ships CUDA 9.1.85 which is broken with provided GCC
  compilers in a slightly complex way.
  
  By default, the g++ compiler version is 7.4.0, which is not supported by 
CUDA/NVCC 9.1.85.
  Next, CUDA/NVCC 9.1.85 should have provided support for g++ 6. But the 
release overlooked an incompatibility with std::tuple which renders this 
compiler combination not useful either:
    https://gist.github.com/ax3l/9489132
  
- Consequently, users that want to use mature C++11/14 features can still 
switch to install a g++-5 package on Ubuntu 18.04 but this compiler has another 
set of bugs in gather/scatter intrinsics which were fixed in later GCC 
releases. This fix was unfortunately not backported to GCC 5.5 .
+ Consequently, users that want to use mature C++11/14 features can still 
switch to install a g++-5 package on Ubuntu 18.04 but this compiler has another 
set of bugs

[Bug 1098531] Re: Wrong path to global config files mentioned in man page

[Axel Beckert]

This has been fixed in 5.2-3ubuntu1 (i.e. with Yakkety) when these
ubuntu-specific changes were dropped:

* Drop yodl from Build-Depends.
* prebuild docs.


** Changed in: zsh (Ubuntu)
   Status: New => Fix Released

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

Title:
  Wrong path to global config files mentioned in man page

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

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

[Bug 1098531] Re: Wrong path to global config files mentioned in man page

[Axel Beckert]

** Tags added: xenial

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

Title:
  Wrong path to global config files mentioned in man page

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

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

[Bug 1860323] Re: fping not working if ipv6 is disabled

[Axel Beckert]

> There seems to be a fix on github... (since july 2018!)

Yes, and according to the fping version you mentioned, you're running
Ubuntu 18.04 Bionic from _April_ 2018. So that Ubuntu release was
released before the bug was fixed upstream.

Upgrading to a more recent version of Ubuntu will fix this as this is
fixed in package version 4.1-1 and all later and supported versions of
Ubuntu do have at least 4.2-1.

So this bug is more or less fixed—also in Ubuntu—from the general point
of view. It's just not fixed in Ubuntu 18.04 Bionic. But since this
neither a severe nor a security issue, chances that the fix gets
backported to 18.04 are not very high.

** Bug watch added: Debian Bug tracker #891704
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891704

** Also affects: fping (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891704
   Importance: Unknown
   Status: Unknown

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

Title:
  fping not working if ipv6 is disabled

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

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

[Bug 1860323] Re: fping not working if ipv6 is disabled

[Axel Beckert]

** Tags added: bionic

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

Title:
  fping not working if ipv6 is disabled

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

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

[Bug 1859314] Re: aptitude deletes drivers manager(?)

[Axel Beckert]

** Changed in: aptitude (Ubuntu)
   Status: New => Incomplete

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

Title:
  aptitude deletes drivers manager(?)

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

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

Re: [Bug 1859314] [NEW] aptitude deletes drivers manager(?)

[Axel Beckert]

Hi,

Launchpad Bug Tracker wrote:
> 4) script doing autojob (renewing packages since you are connected
> to internet.

Can you provide this script? Or is it a part of some package? There's
a chance that this is the culprit.

> 5) aftermath (after instalation) instal aptitude because some pro
> said  "aptitude is better than apt"

If that is true or untrue depends heavily on your use-case and can't
be said generally. Both tools have their adavantages and
disadvantages. (Saying this with my aptitude package maintainer hat
on.)

Which tool is better suited for you depends mostly on this things:

*  If you want

   - a TUI, or
   - want to manually interfere with dependency resolution, or
   - want to be able to match packages with patterns on package
 properties, or
   - want to use debtags to select or find package,

   then aptitude is the right tool for you. But these features come
   with one drawback: aptitude takes a moment to read (and later save)
   all the data it needs to provide these features, i.e. it's the
   slowest of the mentioned tools.

* If you prefer

  - solely the commandline,
  - prefer a fast program, and
  - don't want to change the proposed dependency resolutions, and
  - don't care about a still occasionally changing UI, CLI and output
format,

  then apt (the command) is for you.

* If you want to

  - have a stable UI, CLI and output format
  - script things,
  - don't need aptitude's pattern matching for that, and
  - prefer fast programs

  then apt-get, apt-cache and friends (from the apt package) are the
  best tools for you.

Additionally the defaults for all three options are slightly
different, especially wrt. to automatically removing packages, but
also wrt. progress bars, colored output, stable UI/API, etc.

> 7) try to install mc --> aptitude install mc
> 8) aptitude offering you to UNinstall all proprietary drivers while u just 
> want to install mc ...

One difference between apt-get, apt and aptitude (with default
settings) is that apt-get does not remove unused packages
automatically but just warns about them. aptitude uninstalls them by
default and apt IIRC does something inbetween. In all tools, this
setting can be changed, either on the commandline, in configuration
files and in aptitude also in the TUI.

But the main question in this case is:

_What_ marked those drivers as "automatically installed"?

None of the tools does this unless these packages were pulled in as a
dependency while installing other packages or if the admin explicitly
set this flag. (They all share the same database for these flags.)

So something must have set that "automatically installed" flag,
otherwise aptitude wouldn't have removed them automatically.

This can also be seen in the occurrences of "NOT USED" in the provided
log.

I currently see only two possibilities:

1. The above mentioned, but unknown script fiddled with the
   "automatically installed" flag, e.g. via "apt-mark auto".

2. The installation image already contained these flags for some
   reason, but since apt-get (and partially apt) doesn't automatically
   remove these packages, the creator of the image didn't care about
   these flags and this only surfaced when aptitude was used.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

Title:
  aptitude deletes drivers manager(?)

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

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

[Bug 1857340] [NEW] Setting "IPv6 Method" to "Disable" does not disable IPv6

[Axel Taferner via ubuntu-bugs]

Public bug reported:

Setting "IPv6 Method" to "Disable" does not disable IPv6

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 23 06:50:59 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-11-21 (31 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  Setting "IPv6 Method" to "Disable" does not disable IPv6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1857340/+subscriptions

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

[Bug 1853458] Re: "host not found" when navigating to dev.lemmy.ml

[Axel Beckert]

I can confirm this behaviour with any hostname I tried (including e.g.
www.google.com).

The "problem" seems the interaction between links2 and "torsocks" (and
also "torify" which does more or less the same).

It surely not a DNS or TLD detection issue, because both, "links2
https://dev.lemmy.ml/communities/page/1; as well as "links2 -socks-proxy
localhost:9050 -only-proxies 1 https://dev.lemmy.ml/communities/page/1;
(which is the official way of using links2 with Tor).

And "tor-resolve dev.lemmy.ml" works as expected, too.

It is though currently unclear to me, _why_ links2 doesn't seem to work
with "torsocks" or "torify".

** Changed in: links2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  "host not found" when navigating to dev.lemmy.ml

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

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

Re: [Bug 1851925] Re: Fresh install of aptitude is broken - missing dependency?

[Axel Beckert]

Hi,

NeilGreenwood wrote:
> That was indeed the problem, which is why i marked this bug as invalid.

Yeah, sorry, your second mail and my question crossed each other. I
only read your second mail after I'd sent my mail.

That's also why I corrected the state afterwards.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

Title:
  Fresh install of aptitude is broken - missing dependency?

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

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

[Bug 1851925] Re: Fresh install of aptitude is broken - missing dependency?

[Axel Beckert]

** Changed in: aptitude (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Fresh install of aptitude is broken - missing dependency?

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

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

[Bug 1851925] Re: Fresh install of aptitude is broken - missing dependency?

[Axel Beckert]

I'm sorry, but I can't reproduce this issue in a clean 18.04 chroot:

aptitude is installed at version 0.8.10-6ubuntu1, too, and has a
dependency on libsigc++-2.0-0v5 (version 2.10.0-2 installed as in your
case) which contains /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0.

And aptitude works for me.

Can you run "dpkg -C libsigc++-2.0-0v5" to check if all files of that
package are there and undamaged?

** Changed in: aptitude (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  Fresh install of aptitude is broken - missing dependency?

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

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

[Bug 1849917] Re: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem)

[Axel Meunier via ubuntu-bugs]

Additional dmesg output, right after the problem appears for the first
time (sometime after booting, definitely not related to suspend as I
supposed in my first message).


** Attachment added: "dmesg-2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+attachment/5303375/+files/dmesg-2.txt

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

Title:
  [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause
  GUI stuttering in kernel 5.3 (but 5.0 has no problem)

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

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

[Bug 1849917] Re: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem)

[Axel Meunier via ubuntu-bugs]

And the dmesg.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+attachment/5303370/+files/dmesg.txt

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

Title:
  [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause
  GUI stuttering in kernel 5.3 (but 5.0 has no problem)

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

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

[Bug 1849917] Re: [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause GUI stuttering in kernel 5.3 (but 5.0 has no problem)

[Axel Meunier via ubuntu-bugs]

I'm affected by what seems to be the same bug or a very similar one.
Also Ubuntu 19.10 fresh install.
Additional information from what I have observed on my machine :
- It's not only the cursor that stutters but the whole machine freezes for an 
instant. It's most noticeable while scrolling or watching videos.
- it does not start right away. Maybe after suspend ? I'm not yet sure.
- I have the same information re the Inter wireless 8260 driver than mentioned 
by the other user (namely that it does not function).
- On the other hand, I have tried disabling Wifi but it did not seem to have 
any effect (I will check again).
Here are the dmesg and lpsci text files.
Thanks for your help. 


** Attachment added: "lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849917/+attachment/5303369/+files/lspcik.txt

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

Title:
  [iwlwifi] Repeated kernel crashes in iwl_mvm_async_handlers_wk cause
  GUI stuttering in kernel 5.3 (but 5.0 has no problem)

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

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

[Bug 1851128] Re: Stylus Use leads to Crash Application in Wayland Sessions

[Axel]

Yes, that's exactly what I am doing. There is a work-around.

To have it in Wayland is a matter of comfort since I try to stay on
Wayland. It will be the future, right?

Thanks again.

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

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1851128/+subscriptions

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

[Bug 1851128] Re: Stylus Use leads to Crash Application in Wayland Sessions

[Axel]

Thank you very much.

In which time-frame can I expect the fix being on my machine?
And how do I notice, can I check that it is here?

Sorry again for these questions, but I need to learn a lot how this
system works.

Best regards

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

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1851128/+subscriptions

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

[Bug 1851128] Re: Stylus Use leads to Crash Application in Wayland Sessions

[Axel]

I'm using Ubuntu 19.10 Eoan Ermine.

Sorry I did not mention that.

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

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1851128/+subscriptions

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

[Bug 1851128] [NEW] Stylus Use leads to Crash Application in Wayland Sessions

[Axel]

Public bug reported:

There is an issue in gtk. In Wayland sessions the use of a stylus leads
to crash of the application. It is apparently fixed in Gnome gtk.

When asking what should I do I got the answer that I should ask the
ubuntu gtk maintainers to  backport <
https://gitlab.gnome.org/GNOME/gtk/merge_requests/1121> and
, which I do
here and now.

Best regards

** Affects: gtk+3.0 (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/1851128

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1851128/+subscriptions

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

[Bug 920968] Re: samba: FTBFS on Lucid with pbuilder or as user plus fakeroot: configure: WARNING: unrecognized options: --without-smbmount

[Axel Beckert]

** Summary changed:

- FTBFS on Lucid with pbuilder or as user plus fakeroot: configure: WARNING: 
unrecognized options: --without-smbmount
+ samba: FTBFS on Lucid with pbuilder or as user plus fakeroot: configure: 
WARNING: unrecognized options: --without-smbmount

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

Title:
  samba: FTBFS on Lucid with pbuilder or as user plus fakeroot:
  configure: WARNING: unrecognized options: --without-smbmount

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

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

[Bug 1832377] Re: Cannot handle firmware requirement not-child

[Axel Beckert]

** Bug watch added: Debian Bug tracker #931794
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931794

** Also affects: fwupd (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931794
   Importance: Unknown
   Status: Unknown

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

Title:
  Cannot handle firmware requirement not-child

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

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

[Bug 1832377] Re: Cannot handle firmware requirement not-child

[Axel Beckert]

@superm1: #1820768 looks completely unrelated to me. Additionally, this
still happens with 1.2.6-1 as currently in Debian Unstable.

This issue has been fixed upstream in
https://github.com/hughsie/fwupd/pull/1144 (Original upstream bug report
at https://github.com/hughsie/fwupd/issues/1139)

** Bug watch added: github.com/hughsie/fwupd/issues #1139
   https://github.com/hughsie/fwupd/issues/1139

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

Title:
  Cannot handle firmware requirement not-child

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

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

[Bug 1830047] Re: iptables-netflow 2.3-5ubuntu1 ADT test failure with linux 5.2.0-0.1

[Axel Beckert]

Compilation with kernel 5.1 has been fixed upstream in
https://github.com/aabc/ipt-
netflow/commit/fd37b58a81c3df1f375fe784547b77b7a9d1ebc4.

I don't know if this also fixes compilation with kernel 5.2 (i.e. if
#1827106 really is a duplicate of this bug).

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

Title:
  iptables-netflow 2.3-5ubuntu1 ADT test failure with linux 5.2.0-0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1830047/+subscriptions

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

[Bug 1827106] Re: iptables-netflow 2.3-5ubuntu1 ADT test failure with linux 5.1.0-1.1

[Axel Beckert]

*** This bug is a duplicate of bug 1830047 ***
https://bugs.launchpad.net/bugs/1830047

This has been fixed upstream in https://github.com/aabc/ipt-
netflow/commit/fd37b58a81c3df1f375fe784547b77b7a9d1ebc4.

I don't know if this also fixes compilation with kernel 5.2.

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

Title:
  iptables-netflow 2.3-5ubuntu1 ADT test failure with linux 5.1.0-1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1827106/+subscriptions

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

[Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

[Axel Beckert]

zsh is not really fixed. Please see the changelog entry of 5.6.2-3 which
states:

  * [92175749] Revert "Switch from the deprecated libpcre3 to the newer
(!) libpcre2." libpcre2 is not a drop-in replacement and not detected
by zsh's configure script. (Closes: #909084, reopens LP#1792544)

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

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

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

Re: [Bug 1819949] Re: ZSH not working

[Axel Beckert]

Hi Mohammad,

Mohammad Shoriful Islam Ronju wrote:
> ~/.zshenv is not there. debsums was not installed. I installed it and
> attached the output.

Thanks! Unfortunately I'm starting to run out of ideas what else could
cause this issue. :-(

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

Title:
  ZSH not working

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

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

Re: [Bug 1819949] Re: ZSH not working

[Axel Beckert]

Hi Mohammad,

Mohammad Shoriful Islam Ronju wrote:
> Yeah tried opening new terminal every time when commented out a line.
> Finally logged out and logged in to check. No luck :(

Does a ~/.zshenv exist, too? That one gets sourced before .zshrc (and
can change the path for .zshrc).

If you have debsums installed, does "debsums -e zsh-common" show any
modified files under /etc/zsh/? Because "zsh -f" also skips them (or
at least some of them).

    Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

Title:
  ZSH not working

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

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

Re: [Bug 1819949] Re: ZSH not working

[Axel Beckert]

Hi Mohammad,

Mohammad Shoriful Islam Ronju wrote:
> Running "zsh -f" works fine.

Ok.

> However comment out all the lines on .zshrc file still didn't work.

You need to start a new zsh to test those changes, i.e. open a new
terminal or starting zsh from bash.

> I'm attaching "/usr/share/bug/zsh 3>&1" commands output here.

Thanks. Nothing suspicious on a first glance.

> Note: Is there any way to source changed .zshrc file? Tried ".
> ~/.zshrc" and "source ~/.zshrc" nothing worked. I use those commands
> in mac.

These commands generally work on Linux, too. Point is just that they
don't undo things which have been commented out from .zshrc. Hence you
need to start a new zsh everytime you comment out or remove something
from your .zshrc.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

Title:
  ZSH not working

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

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

Re: [Bug 1819949] Re: ZSH not working

[Axel Beckert]

Hi Mohammad,

Mohammad Shoriful Islam Ronju wrote:
> https://linuxhint.com/install_zsh_shell_ubuntu_1804/

Ok, according to this tutorial(*) that prompt in your screenshot is
the default prompt from oh-my-zsh -- which doesn't come from any
official Ubuntu repo.

So please disable oh-my-zsh first and see if that fixes the issue
already.

If that doesn't fix the issue, please check if running "zsh -f"
(disables the parsing of .zshrc; call it e.g. from bash) still shows
the issue.

If "zsh -f" shows the issue, there is definitively a bug, either in
zsh or the terminal. (Since zsh seems to start at least and does not
crash, it might also be a terminal issue.)

If "zsh -f" works fine, you need to start commenting lines from your
.zshrc until the issue vanishes. The last line you commented out then
likely caused the issue. If that line is known, one can continue to
figure out why that line causes this issue.

It might also be helpful if you could post the output of
"/usr/share/bug/zsh 3>&1" to see which other packages on your system
provide zsh-sourced files.

Footnotes:

(*) IMHO this tutotal is crap:

* "whereis" is overkill if you can use "which"
* The user shoudn't use usermod as root (sudo …) to change a user shell
  but chsh (as you did).
* There's no need to reboot just to make a change of a user shell
  effective.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

Title:
  ZSH not working

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

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

[Bug 1819949] Re: ZSH not working

[Axel Beckert]

> Also followed this tutorial but same result.

Which tutorial? There was no link except to the screen shot in your
message...

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

Title:
  ZSH not working

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

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

[Bug 1819378] Re: package xymon 4.3.28-3build1 failed to install/upgrade: installed xymon package post-installation script subprocess returned error exit status 1

[Axel Beckert]

** Changed in: xymon (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  package xymon 4.3.28-3build1 failed to install/upgrade: installed
  xymon package post-installation script subprocess returned error exit
  status 1

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

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

[Bug 1819378] Re: package xymon 4.3.28-3build1 failed to install/upgrade: installed xymon package post-installation script subprocess returned error exit status 1

[Axel Beckert]

Dear Sukhvir,

thanks for your bug report.

sukhvir wrote:
> I was trying to install xymon on ubuntu 18.4 lts, I am getting following 
> error.
> chgrp: cannot access 'critical.cfg': No such file or directory
> chgrp: cannot access 'critical.cfg.bak': No such file or directory
> dpkg: error processing package xymon (--configure):
>  installed xymon package post-installation script subprocess returned error 
> exit status 1
[...]
> modified.conffile..etc.xymon.alerts.cfg: [deleted]
> modified.conffile..etc.xymon.analysis.cfg: [deleted]
> modified.conffile..etc.xymon.cgioptions.cfg: [deleted]
> modified.conffile..etc.xymon.client-local.cfg: [deleted]
> modified.conffile..etc.xymon.columndoc.csv: [deleted]
> modified.conffile..etc.xymon.combo.cfg: [deleted]
> modified.conffile..etc.xymon.critical.cfg: [deleted]
> modified.conffile..etc.xymon.critical.cfg.bak: [deleted]
> modified.conffile..etc.xymon.graphs.cfg: [deleted]

This is caused by the following (IMHO rather uncommon) case that

* the package xymon had been installed beforehand (not explicitly
  mentioned, but obvious due to the deleted conffiles),
* has been removed again (but not purged, otherwise dpkg wouldn't know
  about the conffiles),
* then someone deleted /etc/xymon/ manually (otherwise not all
  conffiles would have been deleted),
* and tried to install xymon again.

Removing /etc/xymon/ (or any other conffile of any other package)
without purging ("apt-get purge" or "apt-get remove --purge") a
package makes dpkg think that the system administrator on purpose
remove these conffiles and hence respects this decision and doesn't
unpack them again.

While having removed _all_ conffiles manually without purging the
package, too, is theoretically a valid setup, it's nevertheless a
broken setup and breakage has to be expected then IMHO with most
packages.

So I'm not sure if I really should add support to the xymon package
for such a broken environment.

This breakage is btw. easily fixed: Do an "apt-get purge xymon" before
installing the package again. Be aware that this may also remove
monitoring data previously collected with xymon.

Thomas wrote:
> coping critical.cfg to critical.cfg.bak bypassed the error.

I think Thomas' case is slightly different, alone because in the above
case critical.cfg had been deleted, too. I actually expect further
breakage in the above case even if critical.cfg and critical.cfg.bak
are restored.

But Back to Thomas' case:

I though must admit that the file "critical.cfg.bak" (and _only_ that
file) doesn't really look like being relevant and might be deleted by
a local admin.

And this is actually a case we definitely need to handle better. I've
filed https://bugs.debian.org/924665 in Debian for that.

P.S.: Thanks to Thomas' variant of this issue, I became aware of the
fact that this issue might also happen if you just tried to clean up
your /etc/ from seemingly unnecessary backup files.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


** Bug watch added: Debian Bug tracker #924665
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924665

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

Title:
  package xymon 4.3.28-3build1 failed to install/upgrade: installed
  xymon package post-installation script subprocess returned error exit
  status 1

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

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

[Bug 1819378] Re: package xymon 4.3.28-3build1 failed to install/upgrade: installed xymon package post-installation script subprocess returned error exit status 1

[Axel Beckert]

** Changed in: xymon (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  package xymon 4.3.28-3build1 failed to install/upgrade: installed
  xymon package post-installation script subprocess returned error exit
  status 1

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

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

[Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Axel Meunier via ubuntu-bugs]

I am also experiencing this bug. It should be noted that it does not
happen in Fedora 29 (it is mentioned here by a F29 user :
https://gitlab.gnome.org/GNOME/gtk/issues/1572 and I have also checked
it myself) so it seems to be Ubuntu specific.

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

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

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

[Bug 1800280] Re: Setting ZSH as login shell causes various issues because it doesn't source /etc/profile

[Axel Beckert]

> > What do you exactly mean by "setting ZSH as the default shell"?
>
> I just mean using chsh to set the default login shell. /bin/sh is left 
> unchanged.

JFTR: "default" is still the wrong term for this. There is only _one_
login shell per user. "default" always suggests that there are others to
use if you don't like the default value. But there is none. The "default
login shell" is still bash because that's what new users get as their
login shell _by default_.

I changed the title of the bug report accordingly as it just confused me
again.

** Summary changed:

- Setting ZSH as the default shell causes various issues because it doesn't 
source /etc/profile
+ Setting ZSH as login shell causes various issues because it doesn't source 
/etc/profile

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

Title:
  Setting ZSH as login shell causes various issues because it doesn't
  source /etc/profile

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

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

[Bug 1813061] Re: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2

[Axel Beckert]

Pull-request at upstream (with commits from someone with a canonical.com
e-mail address :-): https://github.com/aabc/ipt-netflow/pull/110

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

Title:
  iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1813061/+subscriptions

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

[Bug 1813061] Re: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2

[Axel Beckert]

** Changed in: iptables-netflow (Ubuntu)
 Assignee: (unassigned) => Axel Beckert (xtaran)

** Changed in: iptables-netflow (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1813061/+subscriptions

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

[Bug 1813061] Re: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2

[Axel Beckert]

Forwarded to upstream at https://github.com/aabc/ipt-netflow/issues/108

** Bug watch added: github.com/aabc/ipt-netflow/issues #108
   https://github.com/aabc/ipt-netflow/issues/108

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

Title:
  iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1813061/+subscriptions

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

[Bug 1813061] Re: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2

[Axel Beckert]

Attached a dkms.log from iptables-netflows-dkms 2.3-5 building against
linux-headers-5.0.0-3-generic and linux-libc-dev version 5.0.0-3.4.

Will report this issue to upstream.

** Attachment added: "dkms.log of building against linux 5.0.0-3.4"
   
https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1813061/+attachment/5236406/+files/iptables-netflow-dkms_2.3-5_dkms.log

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

Title:
  iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1813061/+subscriptions

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

[Bug 1813061] Re: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2

[Axel Beckert]

I think I found them at https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/unstable

** Changed in: iptables-netflow (Ubuntu)
   Status: Incomplete => New

** Changed in: iptables-netflow (Ubuntu)
   Status: New => Confirmed

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

Title:
  iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1813061/+subscriptions

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

[Bug 1813061] Re: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2

[Axel Beckert]

Where can I get these linux-*-5.0.0-1.2 packages for debugging this
issue? Can't find them in a standard disco pbuilder chroot.

And unfortunately the above download links don't seem to contain
relevant artifacts like the DKMS build log.

** Changed in: iptables-netflow (Ubuntu)
   Status: New => Incomplete

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

Title:
  iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1813061/+subscriptions

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

[Bug 1812778] Re: internet connection randomly stops working

[Axel Beckert]

Why is network-manager running while wicd is being used? They likely
interfere which each other. Does this also happen if you stop network-
manager (i.e. "sudo service network-manager stop") and then connect to a
wifi with wicd?

(They're co-installable on purpose, to be able to switch between them,
but they shouldn't be running at the same time.)

** Changed in: wicd (Ubuntu)
   Status: New => Incomplete

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

Title:
  internet connection randomly stops working

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

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