[Bug 2063049] Re: Google Chrome and Chromium 124 have a transparent window on Wayland

[Achim Behrens]

fixed with todays update chromium 124.0.6367.118

** Changed in: chromium-browser (Ubuntu)
   Status: Triaged => 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/2063049

Title:
  Google Chrome and Chromium 124 have a transparent window on Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/2063049/+subscriptions


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

[Bug 2063049] [NEW] chromium snap doesnt launch properly on 24.04

[Achim Behrens]

Public bug reported:

chromium snap only launches with titlebar and transparent window after
recent snap update on wayland and intel grafics.

Adding --ozone-platform=wayland fixes the issue for me. (workaround from
bug #1968610)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: chromium-browser 2:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
Uname: Linux 6.8.0-28-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: sway
Date: Sun Apr 21 20:25:30 2024
DiskUsage:
 FilesystemType   Size  Used Avail Use% Mounted on
 rpool/ROOT/ubuntu_gk6kaa  zfs 50G  7,7G   42G  16% /
 tmpfs tmpfs   16G  128M   16G   1% /dev/shm
 rpool/USERDATA/k1l_0tberh zfs437G  396G   42G  91% /home/k1l
InstallationDate: Installed on 2022-03-24 (760 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
Snap.Changes:
 ID   Status  Spawn  Ready  Summary
 635  Done2024-04-21T00:51:33+02:00  2024-04-21T00:52:11+02:00  Snap 
"chromium" aktualisieren
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60 
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to noble on 2024-03-25 (27 days ago)

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble 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/2063049

Title:
  chromium snap doesnt launch properly on 24.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063049/+subscriptions


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

[Bug 2052642] Re: opeanfs-modules-dkms FTBS with linux 6.5 on jammy

[Achim Bohnet]

Works for me on 6 jammy hosts:

# dpkg -l openafs\* | grep ^i
ii  openafs-client 1.8.10-2ubuntu1~22.04.1 amd64AFS distributed 
filesystem client support
ii  openafs-doc1.8.10-2ubuntu1~22.04.1 all  AFS distributed 
filesystem documentation
ii  openafs-krb5   1.8.10-2ubuntu1~22.04.1 amd64AFS distributed 
filesystem Kerberos 5 integration
ii  openafs-modules-dkms   1.8.10-2ubuntu1~22.04.1 all  AFS distributed 
filesystem kernel module DKMS source


# uname -a
Linux it01lt 6.5.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 
10:22:43 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
   opeanfs-modules-dkms FTBS with linux 6.5 on jammy

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


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

[Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1

[Achim Behrens]

tried the fix from the new package manually (removing
/lib/firmware/ath11k/WCN6855/hw2.1) and after that the update worked.

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

Title:
  linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1

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


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

[Bug 1964794] Re: Faulty linux-firmware upgrade

[Achim Behrens]

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

new package is in proposed.
if you cant wait or dont want to enable/download proposed packages rmeove 
/lib/firmware/ath11k/WCN6855/hw2.1 manually and the update will work.

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

Title:
  Faulty linux-firmware upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1964794/+subscriptions


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

[Bug 1946017] [NEW] no IPV6 from wlan0 via dhcp

[Achim Schaefer]

Public bug reported:

neither during boot nor during a manual 
sudo dhclient -6 -v wlan0
the box does get a IPv6 on WLAN0.

ipv4 works perfectly

verbose output:

Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

no link-local IPv6 address for wlan0

If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug.  These pages explain the proper
process and the information we find helpful for debugging.

exiting.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: isc-dhcp-client 4.4.1-2.2ubuntu6.2
ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22
Uname: Linux 5.11.0-1019-raspi aarch64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
ApportVersion: 2.20.11-0ubuntu65.3
Architecture: arm64
CasperMD5CheckResult: unknown
Date: Mon Oct  4 16:31:14 2021
ImageMediaBuild: 20201022
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: isc-dhcp
UpgradeStatus: Upgraded to hirsute on 2021-07-17 (78 days ago)

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug arm64 arm64-image hirsute raspi-image uec-images

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

Title:
  no IPV6 from wlan0 via dhcp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1946017/+subscriptions


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

[Bug 1929324] Re: Grub menu is not shown because of shim error message

[Achim Behrens]

looks like it was fixed in shim(-signed) package.
It works now as intended again.

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

Title:
  Grub menu is not shown because of shim error message

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


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

[Bug 1928490] Re: "Could not create MokListRT" message on boot

[Achim Behrens]

I did file a new bug here:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1929324

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

Title:
  "Could not create MokListRT" message on boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1928490/+subscriptions

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

[Bug 1929324] [NEW] Grub menu is not shown because of shim error message

[Achim Behrens]

Public bug reported:

Running 21.04 on a thinkpad x230.
There is a shim error 
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1924605 "could not create 
MokListXRT: Out of Resources" which displays this errormessage at bootup.

So Grub works, the menu works (you can still use the arrowkeys if you
know the menu order) but it doesnt show the menu but this errormessage.
The System boots up fine.

I was told to file a new bug for grub. This shim error is not going to
be resolved so we need another workaround on the grub side so people can
again access their grub menu when they need to, like when they have
other issues and need to use the recovery entries or a dualboot.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: grub2 (not installed)
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sun May 23 12:01:58 2021
InstallationDate: Installed on 2018-10-19 (946 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: grub2
UpgradeStatus: Upgraded to hirsute on 2021-03-20 (63 days ago)

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


** Tags: amd64 apport-bug hirsute 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/1929324

Title:
  Grub menu is not shown because of shim error message

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

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

[Bug 1924605] Re: Grub2 menu not loading - could not create MokListXRT: Out of Resources

[Achim Behrens]

So people say they can still navigate blindly on grub menu when this
errormessage is displayed since it only blocks the menu beeing
displayed, not grub as such.

So i wonder if there is a better way of displaying this error as a
workaround.

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

Title:
  Grub2 menu not loading - could not create MokListXRT: Out of Resources

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

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

[Bug 1928490] Re: "Could not create MokListRT" message on boot

[Achim Behrens]

The Problem is that this blocks the Grub-Menu from beeing displayed
(while some say they can use the keys to navigate blindly on the menu.
didnt test this so far myself)

So in case of some recovery beeing needed this gets a big issue.

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

Title:
  "Could not create MokListRT" message on boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1928490/+subscriptions

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

[Bug 1924605] Re: Grub2 menu not loading - could not create MokListXRT: Out of Resources

[Achim Behrens]

@julian: i understand your point. But i dont understand why it worked
some weeks ago and with a 20.04 live usb while there are no changes to
the efi or bios.

So from a rational there must be something broken on recent 21.04 state.
it may not be grub itself but something in that whole efi setup.

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

Title:
  Grub2 menu not loading - could not create MokListXRT: Out of Resources

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

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

[Bug 1924605] Re: Grub2 menu not loading - could not create MokListXRT

[Achim Behrens]

As said before it worked some weeks ago and still works on a 20.04.5
live usb. So there is something broken in the 21.04 setup of the whole
grub/kernel/efi stuff.

I stumbled about the releasenotes from 21.04 now talking about some shim
issue. and i found  https://bugs.launchpad.net/ubuntu/+source/shim-
signed/+bug/1925010 and
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1925064.

I have the error "efi: Failed to lookup EFI memory descriptor for 
0xd75f2000" in the logs like which seems to releate here: 
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1925139

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

Title:
  Grub2 menu not loading - could not create MokListXRT

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

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

[Bug 1923053] Re: [SRU] nextcloud crashed with SIGSEGV.

[Achim Behrens]

i grabbed the packages right from the launchpad building page and installed 
them:
libnextcloudsync0_3.1.1-1ubuntu1.1_amd64.deb 
nextcloud-desktop_3.1.1-1ubuntu1.1_amd64.deb 
nextcloud-desktop-common_3.1.1-1ubuntu1.1_all.deb 
nextcloud-desktop-l10n_3.1.1-1ubuntu1.1_all.deb 
nextcloud-desktop-doc_3.1.1-1ubuntu1.1_all.deb

The nextcloud desktop client now starts as intended. No segfault
anymore.

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

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

Title:
  [SRU] nextcloud crashed with SIGSEGV.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions

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

[Bug 1923053] Re: [SRU] nextcloud crashed with SIGSEGV.

[Achim Behrens]

the issue in Comment 18 comes from mixing higher versioned clients, they
are not downgradeable.

"That is because the sync database of 3.2.0-rc3 and 3.1.3 are
incompatible. In general it is not supported to downgrade. To recover
from that you need to delete the sync database while the client is not
running. The sync database are the files beginning with ._sync* in your
sync folder. The client will generate a new sync database on restart."
from
https://github.com/nextcloud/desktop/issues/2790#issuecomment-811872914

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

Title:
  [SRU] nextcloud crashed with SIGSEGV.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions

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

[Bug 1924605] Re: Grub2 menu not loading - could not create MokListXRT

[Achim Behrens]

I think there is something wrong with the whole 
uefi/grub/mokutil/efivars/kernel setup on 21.04.
I changed the attributes with chattr -i and checked with lsattr. When running 
"rm -rf ..." i dont get an error but it doesnt delete the file. Without -rf i 
get the error "invalid Argument". (Running with sudo or in a root shell)

Efivarfs is mounted rw:
root@ThinkPad:/sys/firmware/efi/efivars# mount | grep efi
efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)


I booted a 20.04.2 usb and checked the efivars there and that didnt include all 
the MoklistXRT variables.

I tried to boot with kernel parameter efi_no_storage_paranoia but that didnt 
help. kernel is right now 
Command line: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=cd3606bb-9444-4ef8-bcaa-6e21674ca895 ro quiet splash


I still can boot ubuntu because it "just" doesnt show grub but boots to ubuntu 
anyway. i also can change to the windows bootloader with choosing that on the 
boot device selection when pressing F12 at boot.
Nonetheless grub is not working as intended and that should be fixed.

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

Title:
  Grub2 menu not loading - could not create MokListXRT

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

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

[Bug 1924605] Re: Grub2 menu not loading - could not create MokListXRT

[Achim Behrens]

I cant remove those variables in /sys/firmware/efi/efivars on my thinkpad x230. 
I removed the -i kernel protection on the files but still get "invalid 
argument".
I even tried different Setup- or User-Modes in Bios for Secureboot. That only 
shrinked the dbx variable a bit but didnt solve 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/1924605

Title:
  Grub2 menu not loading - could not create MokListXRT

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

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

[Bug 1924605] Re: Grub2 menu not loading - could not create MokListXRT

[Achim Behrens]

What efivars did you delete because i am unsure what efivars i can
delete safely.

My by far largest efivars are:
-rw-r--r-- 1 root root 19308 Apr 20 22:49 
MokListXRT-605dab50-e046-4300-abb6-3dd810dd8b23
-rw-r--r-- 1 root root 13504 Apr 20 22:49 
dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f
-rw-r--r-- 1 root root  5552 Apr 20 22:49 
MokListXRT2-605dab50-e046-4300-abb6-3dd810dd8b23
-rw-r--r-- 1 root root  5360 Apr 20 22:49 
MokListXRT1-605dab50-e046-4300-abb6-3dd810dd8b23
-rw-r--r-- 1 root root  4213 Apr 20 22:49 
db-d719b2cb-3d3a-4596-a3bc-dad00e67656f
-rw-r--r-- 1 root root  2549 Apr 20 22:49 
KEK-8be4df61-93ca-11d2-aa0d-00e098032b8c
-rw-r--r-- 1 root root  2097 Apr 20 22:49 
MokListRT-605dab50-e046-4300-abb6-3dd810dd8b23

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

Title:
  Grub2 menu not loading - could not create MokListXRT

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

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

[Bug 1923053] Re: nextcloud crashed with SIGSEGV.

[Achim Behrens]

can confirm that with libnextcloudsync0_3.1.1-1_amd64.deb and nextcloud-
desktop_3.1.1-1_amd64.deb from debian bullseye it works again.

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

Title:
  nextcloud crashed with SIGSEGV.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions

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

[Bug 1924605] Re: Grub2 menu not loading - could not create MokListXRT

[Achim Behrens]

Having the same issue with 21.04 with my ubuntu and windows dualboot on my 
thinkpad x230.
But i am running not at zvs but "standard" ext4. So i doubt that is the issue 
here.

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

Title:
  Grub2 menu not loading - could not create MokListXRT

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

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

[Bug 1923053] Re: nextcloud crashed with SIGSEGV.

[Achim Behrens]

i tried with the appimage version of the client and that works ootb with
the user configs etc.

wget 
https://github.com/nextcloud/desktop/releases/download/v3.2.0/Nextcloud-3.2.0-x86_64.AppImage
chmod +x Nextcloud-3.2.0-x86_64.AppImage
./Nextcloud-3.2.0-x86_64.AppImage

So something is broken on the packaged version in the repos.

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

Title:
  nextcloud crashed with SIGSEGV.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions

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

[Bug 1923480] [NEW] Cant start Nextcloud client on sway/wayland anymore.

[Achim Behrens]

Public bug reported:

Running unstable 21.04 with sway on wayland and since end of march i
cant start the nextcloud client anymore.

First it looked like a qt/wayland issue and i installed qt5dxcb-plugin
and qtwayland5. But it still doesnt start and just prints "Segmentation
fault (core dumped)" now.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: nextcloud-desktop 3.1.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Apr 12 18:58:58 2021
InstallationDate: Installed on 2018-10-19 (905 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: nextcloud-desktop
UpgradeStatus: Upgraded to hirsute on 2021-03-20 (22 days ago)

** Affects: nextcloud-desktop (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute 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/1923480

Title:
  Cant start Nextcloud client on sway/wayland anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923480/+subscriptions

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

[Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)

[Achim Settelmeier]

As a workaround, I created the file 01x11-has_option (find it attached)
and placed it in /etc/X11/Xsession.d/. It defines has_option unless it
is already defined somewhere else. ssh-agent now runs in the background
on startup again.


** Attachment added: "/etc/X11/Xsession.d/01x11-has_option"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1922414/+attachment/5485456/+files/01x11-has_option

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

Title:
  ssh-agent fails to start (has_option: command not found)

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

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

[Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)

[Achim Settelmeier]

Looks like /etc/X11/Xsession is not executed, but the files in
/etc/X11/Xsession.d/ are sourced somehow. My best guess is that there's
some other mechanism emulating Xsession's behaviour but without defining
has_option.

Maybe this is a pending bug introduced in an earlier version of Ubuntu
that has come to light just now, after has_option has been moved as #3
points out.


BTW: I'm using lightdm with the Arctica Greeter.

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

Title:
  ssh-agent fails to start (has_option: command not found)

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

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

[Bug 1885919] [NEW] frequent crashes due to missing floating point exception handler

[Achim Schreiber]

Public bug reported:

Hello!

xfoil 6.99.dfsg-2 (xenial xerus standard installation) suffers from frequent 
crashes, always "SIGFPE: floating-point exception - erroneous arithmetic 
operation". This usually does happen during analysis (oper -> visc 10 -> 
alfa), especially with "strange" airfoils.
But first of all it does seem to be a missing error handler, because a) 
Windows(tm) version from 
http://web.mit.edu/drela/Public/web/xfoil/XFOIL6.99.zip does not crash under 
same inputs and b) it also happens in a different simple setup (also only on 
xenial xerus, not Windows(tm)):

steps to reproduce:
1. start xfoil
2. enter "naca 0100" (this is an illegal NACA code)
result: xfoil crashes
expected: no crash, error message like "LEFIND:  LE point not found.  
Continuing..." expected

n.b.: normal operation is possible with "normal" airfoils usually and
results are reasonable.

I should be able to provide some example for a "strange" airfoil if
needed.

** Affects: xfoil (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/1885919

Title:
  frequent crashes due to missing floating point exception handler

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

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

[Bug 1745829] Re: Please replace radiotray with maintained alternative(s)

[Achim Behrens]

build radiotray-ng for my 20.04 development install. works as it should. had to 
convert my old bookmarks.xml to the new json setup.
would recommend to change to radiotray-ng, too.

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

Title:
  Please replace radiotray with maintained alternative(s)

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

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

[Bug 1839890] Re: openafs 1.8.0~pre5-1ubuntu1 fails to build on 5.0 kernels

[Achim Bohnet]

5.0 is also already the HWE kernel in bionic:

# apt show linux-image-generic-hwe-18.04 | head -2
...
Package: linux-image-generic-hwe-18.04
Version: 5.0.0.23.80

Using the 1.8.3 kernel in the openafs PPA, added a few days ago,
works with the 5.0 kernel.

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

Title:
  openafs 1.8.0~pre5-1ubuntu1 fails to build on 5.0 kernels

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

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

[Bug 1832690] Re: Bionic 1.8.0~pre5 version is dangerously out of date

[Achim Bohnet]

1.8.0~pre5 also FTBFS (fails to build from source) for all bionic HWE
kernels. [Even 1.8.2 in PPA is too old for the new 5.0 HWE kernel in
bionic.]

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

Title:
  Bionic 1.8.0~pre5 version is dangerously out of date

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

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

[Bug 1810345] Re: kernel: general protection fault: 0000 [#1] SMP PTI

[Achim Behrens]

the last times the kernel panic got triggered by watching Youtube Video
in Firefox.

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

Title:
  kernel: general protection fault:  [#1] SMP PTI

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

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

[Bug 1810345] Re: kernel: general protection fault: 0000 [#1] SMP PTI

[Achim Behrens]

i tried with 4.20.0-042000-generic and got a crash again (when running
in screensaver mode/idle). even sysreq reisub didnt work, had to
hardreset. i dont know how to trigger this crash on purpose. yesterday
it worked with the 4.20 kernel without crash.

i put the journalctl -b -1 as attachment, snipped a lot of desktop stuff
out of it.

** Attachment added: "journalctl from crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810345/+attachment/5227104/+files/journal_crash_snip

** Tags added: kernel-bug-exists-upstream

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

Title:
  kernel: general protection fault:  [#1] SMP PTI

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

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

[Bug 1810345] [NEW] kernel: general protection fault: 0000 [#1] SMP PTI

[Achim Behrens]

Public bug reported:

using 18.10, all updates included. Desktop (gnome on wayland) is
crashing from time to time at idle, or on reactivating from screensaver
or while working(mostly while playing videos in browsers) where only
sysreq gets to reboot. Running kernel 4.18.0-13-generic #14-Ubuntu

Looking at the logs i found:

Jan  2 23:29:07 ThinkPad kernel: [44709.167257] general protection fault:  
[#1] SMP PTI
Jan  2 23:29:07 ThinkPad kernel: [44709.167284] CPU: 0 PID: 22311 Comm: 
kworker/u17:0 Not tainted 4.18.0-13-generic #14-Ubuntu
Jan  2 23:29:07 ThinkPad kernel: [44709.167286] Hardware name: LENOVO 
2325TZX/2325TZX, BIOS G2ETB3WW (2.73 ) 06/19/2018
Jan  2 23:29:07 ThinkPad kernel: [44709.167315] Workqueue: hci0 hci_rx_work 
[bluetooth]
Jan  2 23:29:07 ThinkPad kernel: [44709.167325] RIP: 
0010:__wake_up_common+0xb4/0x140
Jan  2 23:29:07 ThinkPad kernel: [44709.167327] Code: 4d 85 ed 74 25 41 83 c4 
01 41 83 fc 40 7e 1b 49 8d 46 18 48 39 c3 75 70 8b 45 c4 48 83 c4 18 5b 41 5c 
41 5d 41 5e 41 5f 5d c3 <49> 8b 56 18 49 8d 46 18 4c 89 f7 4c 8d 72 e8 48 39 c3 
75 94 eb d8 
Jan  2 23:29:07 ThinkPad kernel: [44709.167376] RSP: 0018:a941c3c0fbd8 
EFLAGS: 00010083
Jan  2 23:29:07 ThinkPad kernel: [44709.167379] RAX:  RBX: 
9c5d5ef42008 RCX: 
Jan  2 23:29:07 ThinkPad kernel: [44709.167381] RDX: 0001 RSI: 
0082 RDI: 0082
Jan  2 23:29:07 ThinkPad kernel: [44709.167384] RBP: a941c3c0fc18 R08: 
 R09: a941c3c0fb50
Jan  2 23:29:07 ThinkPad kernel: [44709.167386] R10: 9c5e03920400 R11: 
0a00 R12: 0002
Jan  2 23:29:07 ThinkPad kernel: [44709.167389] R13: a941c3c0fc30 R14: 
dead00e8 R15: 
Jan  2 23:29:07 ThinkPad kernel: [44709.167392] FS:  () 
GS:9c5f1e20() knlGS:
Jan  2 23:29:07 ThinkPad kernel: [44709.167395] CS:  0010 DS:  ES:  
CR0: 80050033
Jan  2 23:29:07 ThinkPad kernel: [44709.167397] CR2: 7f741dc0 CR3: 
0001cd20a005 CR4: 001606f0
Jan  2 23:29:07 ThinkPad kernel: [44709.167399] Call Trace:
Jan  2 23:29:07 ThinkPad kernel: [44709.167407]  __wake_up_common_lock+0x80/0xc0
Jan  2 23:29:07 ThinkPad kernel: [44709.167412]  __wake_up+0x13/0x20
Jan  2 23:29:07 ThinkPad kernel: [44709.167418]  sock_def_wakeup+0x36/0x40
Jan  2 23:29:07 ThinkPad kernel: [44709.167440]  
l2cap_sock_teardown_cb+0x192/0x1f0 [bluetooth]
Jan  2 23:29:07 ThinkPad kernel: [44709.167460]  l2cap_chan_del+0x4a/0x2f0 
[bluetooth]
Jan  2 23:29:07 ThinkPad kernel: [44709.167481]  l2cap_sig_channel+0xb55/0x1270 
[bluetooth]
Jan  2 23:29:07 ThinkPad kernel: [44709.167486]  ? __switch_to_asm+0x34/0x70
Jan  2 23:29:07 ThinkPad kernel: [44709.167490]  ? __switch_to_asm+0x40/0x70
Jan  2 23:29:07 ThinkPad kernel: [44709.167493]  ? __switch_to_asm+0x34/0x70
Jan  2 23:29:07 ThinkPad kernel: [44709.167513]  l2cap_recv_frame+0x280/0xc80 
[bluetooth]
Jan  2 23:29:07 ThinkPad kernel: [44709.167517]  ? __switch_to_asm+0x40/0x70
Jan  2 23:29:07 ThinkPad kernel: [44709.167519]  ? __switch_to_asm+0x34/0x70
Jan  2 23:29:07 ThinkPad kernel: [44709.167542]  l2cap_recv_acldata+0x2f6/0x300 
[bluetooth]
Jan  2 23:29:07 ThinkPad kernel: [44709.167558]  hci_rx_work+0x28f/0x380 
[bluetooth]
Jan  2 23:29:07 ThinkPad kernel: [44709.167565]  process_one_work+0x20f/0x3c0
Jan  2 23:29:07 ThinkPad kernel: [44709.167570]  worker_thread+0x34/0x400
Jan  2 23:29:07 ThinkPad kernel: [44709.167575]  kthread+0x120/0x140
Jan  2 23:29:07 ThinkPad kernel: [44709.167579]  ? 
pwq_unbound_release_workfn+0xd0/0xd0
Jan  2 23:29:07 ThinkPad kernel: [44709.167583]  ? kthread_bind+0x40/0x40
Jan  2 23:29:07 ThinkPad kernel: [44709.167586]  ret_from_fork+0x35/0x40
Jan  2 23:29:07 ThinkPad kernel: [44709.167589] Modules linked in: rfcomm hidp 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache ccm cmac bnep 
nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic 
wmi_bmof intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_intel kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
snd_hda_codec ghash_clmulni_intel snd_hda_core pcbc snd_hwdep snd_pcm 
aesni_intel aes_x86_64 crypto_simd arc4 cryptd glue_helper intel_cstate 
intel_rapl_perf iwldvm snd_seq_midi snd_seq_midi_event uvcvideo mac80211 btusb 
input_leds snd_rawmidi joydev btrtl serio_raw btbcm videobuf2_vmalloc btintel 
snd_seq videobuf2_memops thinkpad_acpi videobuf2_v4l2 iwlwifi bluetooth 
videobuf2_common i915 nvram videodev snd_seq_device ecdh_generic snd_timer 
media cfg80211 drm_kms_helper mei_me
Jan  2 23:29:07 ThinkPad kernel: [44709.167653]  mei snd wmi drm mac_hid 
soundcore i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt video 
sch_fq_codel parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 
hid_generic usbhid hid gpio_ich psmouse e1000e ahci i2c_i801 sdhci_pci libahci 
cqhci lpc_ich sdhci
Jan  2 23:29:07 ThinkPad kernel: 

[Bug 1767067] Re: Booting to live session fails with: at-spi-bus-launcher: unable to create file '/run/user/999/dconf/user': Permission denied.

[Achim Behrens]

@21:
https://lists.ubuntu.com/archives/ubuntu-announce/2018-April/000231.html
while you were demanding to be informed about every step developers and 
volunteers do at the release, they did their job and made the release happen.
If you are really that interessted in the release process, i bet the teams 
would not reject volunteers to help them. But if you are just impatient, well, 
that makes you look not that good now.

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

Title:
  Booting to live session fails with: at-spi-bus-launcher: unable to
  create file '/run/user/999/dconf/user': Permission denied.

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

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

[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10

[Achim Behrens]

so after some reboots i need to change my last comment:

right now i need to toggle the commands plugin every time i login for
the mediakeys to work. :/

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

Title:
  Volume and Mute buttons on keyboard not doing anything in Unity after
  upgrade to 17.10

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

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

[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10

[Achim Behrens]

I am running 18.04 with unity and just tested some other Desktops that
are installed long time also: LXQt, Budgie, gnome (wayland and xorg).
Gnome crashed on both. After relogin to unity the keys didnt work while
"sudo showkey" shows that the buttons are working. They even get the
function in the Shortcut dialog in the systemsettings.

Turns out it was the "commands" plugin in ccsm that was activated.
Installed ccsm, deactivated commands: Buttons work again.

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

Title:
  Volume and Mute buttons on keyboard not doing anything in Unity after
  upgrade to 17.10

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

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

[Bug 1759668] [NEW] Livepatch checkState: check-failed / Hash mismatch for URL

[Achim Behrens]

Public bug reported:

running 16.04 server with live-patch service enabled.

$ canonical-livepatch status
client-version: "7.23"
architecture: x86_64
cpu-model: Intel(R) Xeon(R) CPU E3-1225 v3 @ 3.20GHz
last-check: 2018-03-28T21:25:31.372467559+02:00
boot-time: 2018-03-18T08:08:39+01:00
uptime: 252h50m48s
status:
- kernel: 4.4.0-116.140-generic
  running: true
  livepatch:
checkState: check-failed
patchState: nothing-to-apply
version: ""
fixes: ""


in syslog i get the following:
Mar 28 20:25:30 server canonical-livepatch[3548]: Checking with livepatch 
service.
Mar 28 20:25:31 server canonical-livepatch[3548]: Hash mismatch for URL: 
http://livepatch-files.canonical.com/ubuntu/livepatch-4.4.0-116.140-generic-36.3.tar.bz2!
 Expected: 5e5806f409b6e5e9ca8754dd256d4463cc5c0d4312dd150ddf22b9562879d9d9 
Got: ed76dd42169db54a7ca7917e69bba116c46cda9ea0e8da8c2ef19df2632aa3c2
Mar 28 20:25:31 server canonical-livepatch[3548]: No payload available.


on the named url 
"http://livepatch-files.canonical.com/ubuntu/livepatch-4.4.0-116.140-generic-36.3.tar.bz2;
 i get a "Unauthorized" from the webserver.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: snapd 2.29.4.2 [modified: 
usr/share/dbus-1/services/io.snapcraft.Launcher.service]
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Wed Mar 28 21:57:39 2018
InstallationDate: Installed on 2017-05-17 (315 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: snapd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Livepatch checkState: check-failed  / Hash mismatch for URL

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

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

[Bug 1758774] [NEW] pytrainer doesnt start on 18.04: ImportError: No module named _backend_gdk

[Achim Behrens]

Public bug reported:

pytrainer doesnt start on 18.04.
output from terminal is:
> running pytrainer from egg installation
> data_path: /usr/share/pytrainer/
> gettext_path: /usr/share/locale
> site_path: /usr/lib/python2.7/site-packages
> Traceback (most recent call last):
>  File "/usr/bin/pytr", line 97, in 
>main()
>  File "/usr/bin/pytr", line 93, in main
>from pytrainer.main import pyTrainer
>  File "/usr/lib/python2.7/dist-packages/pytrainer/main.py", line 40, in 
> 
>from gui.windowmain import Main
>  File "/usr/lib/python2.7/dist-packages/pytrainer/gui/windowmain.py", line 
> 38, in 
>from pytrainer.recordgraph import RecordGraph
>  File "/usr/lib/python2.7/dist-packages/pytrainer/recordgraph.py", line 20, 
> in 
>from gui.drawArea import DrawArea
>  File "/usr/lib/python2.7/dist-packages/pytrainer/gui/drawArea.py", line 22, 
> in 
>from matplotlib.backends.backend_gtkagg import FigureCanvasGTKAgg as 
> FigureCanvasGTK
>  File 
> "/usr/lib/python2.7/dist-packages/matplotlib/backends/backend_gtkagg.py", 
> line 14, in 
>from matplotlib.backends.backend_gtk import (
>  File "/usr/lib/python2.7/dist-packages/matplotlib/backends/backend_gtk.py", 
> line 35, in 
>from matplotlib.backends.backend_gdk import RendererGDK, FigureCanvasGDK
>  File "/usr/lib/python2.7/dist-packages/matplotlib/backends/backend_gdk.py", 
> line 33, in 
>from matplotlib.backends._backend_gdk import pixbuf_get_pixels_array
> ImportError: No module named _backend_gdk

according to https://github.com/pytrainer/pytrainer/issues/114  this is
an issue with matplotlib not having GTK 2 support compiled in anymore.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pytrainer 1.11.0-1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Mar 26 03:00:03 2018
InstallationDate: Installed on 2013-09-28 (1639 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
PackageArchitecture: all
SourcePackage: pytrainer
UpgradeStatus: Upgraded to bionic on 2018-01-12 (72 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  pytrainer doesnt start on 18.04: ImportError: No module named
  _backend_gdk

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

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

[Bug 1754390] Re: cfitsio vulnerability (fixed in 3.43)

[Achim Bohnet]

Debian sid contains the fixed cfitsio version, can someone trigger a
sync to bionic?

The correspondign debian bug is closed, but nevertheless even after the sync
to bionic there are missing backport (in debian & ubuntu):

  artful
  xenial
  trusty

** Changed in: cfitsio (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  cfitsio vulnerability (fixed in 3.43)

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

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

[Bug 1754131] Re: corebird cant play videos from tweets on 18.04

[Achim Behrens]

there were some gstreamer updates the last days. that seemed to have
fixed it.

** Changed in: corebird (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/1754131

Title:
  corebird cant play videos from tweets on 18.04

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

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

[Bug 1753436] Re: radiotray doesnt start anymore on 18.04

[Achim Behrens]

there were some gstreamer updates the last days. since then radiotray is
working again.

** Changed in: radiotray (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/1753436

Title:
  radiotray doesnt start anymore on 18.04

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

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

[Bug 1754390] Re: cfitsio vulnerability (fixed in 3.43)

[Achim Bohnet]

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

** Also affects: cfitsio (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892458
   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/1754390

Title:
  cfitsio vulnerability (fixed in 3.43)

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

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

[Bug 1754131] [NEW] corebird cant play videos from tweets on 18.04

[Achim Behrens]

Public bug reported:

when clicking on embedded videos i get the error:
> Could not create gtksink. Need gst-plugins-bad >= 1.6

i do have the gstreamer bad packages installed.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: corebird 1.7.3-1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed Mar  7 19:48:49 2018
InstallationDate: Installed on 2013-09-28 (1621 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
SourcePackage: corebird
UpgradeStatus: Upgraded to bionic on 2018-01-12 (54 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  corebird cant play videos from tweets on 18.04

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

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

[Bug 1753436] [NEW] radiotray doesnt start anymore on 18.04

[Achim Behrens]

Public bug reported:

after recent updates to 18.04 radiotray doesnt start anymore.
when starting in terminal this is the output:

/usr/lib/python2.7/dist-packages/radiotray/XmlDataProvider.py:23: PyGIWarning: 
Gtk was imported without specifying a version first. Use 
gi.require_version('Gtk', '3.0') before import to ensure that the right version 
gets loaded.
  from gi.repository import Gtk
Traceback (most recent call last):
  File "/usr/bin/radiotray", line 15, in 
radiotray_runner.main(sys.argv[1:])
  File "/usr/lib/python2.7/dist-packages/radiotray/radiotray_runner.py", line 
39, in main
RadioTray()
  File "/usr/lib/python2.7/dist-packages/radiotray/RadioTray.py", line 72, in 
__init__
self.audio = AudioPlayerGStreamer(self.mediator, self.cfg_provider, 
eventManager)
  File "/usr/lib/python2.7/dist-packages/radiotray/AudioPlayerGStreamer.py", 
line 61, in __init__
self.player.set_property("video-sink", fakesink)
AttributeError: 'NoneType' object has no attribute 'set_property'

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: radiotray 0.7.3-6ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Mar  5 11:22:42 2018
InstallationDate: Installed on 2013-09-28 (1618 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
PackageArchitecture: all
SourcePackage: radiotray
UpgradeStatus: Upgraded to bionic on 2018-01-12 (51 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  radiotray doesnt start anymore on 18.04

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

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

[Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

[Achim Behrens]

running 18.04.

saw a massiv syslog file and running grep -i uread /var/log/syslog.1|grep -i 
"Feb 25 12" |wc -l:
> 63197


i dont think we need this to make syslog extra big for no reason.

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

Title:
  ureadahead reports relative path errors in journalctl output

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

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

[Bug 1751673] [NEW] nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

[Achim Behrens]

Public bug reported:

running 18.04 this message is spamming into syslog:
> nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.8.4-1ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Feb 26 01:16:49 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-09-28 (1611 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
IpRoute:
 default via 192.168.1.1 dev wlan1 proto static metric 600 
 169.254.0.0/16 dev wlan1 scope link metric 1000 
 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.34 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
SourcePackage: network-manager
UpgradeStatus: Upgraded to bionic on 2018-01-12 (44 days ago)
modified.conffile..etc.polkit-1.localauthority.50-local.d.org.freedesktop.NetworkManager.pkla:
 [deleted]
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   CONNECTION  CON-UUID  CON-PATH   

 wlan1  wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  k2l 
7df024b1-9b89-4f95-84c1-03188bb67f77  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 EC:88:92:02:17:7D  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  --  --   
 -- 
 eth1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
 lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN 
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  disabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET
  (widget)' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1751673/+subscriptions

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

[Bug 1751581] Re: systemd-udevd Process '/sbin/crda' failed with exit code 249

[Achim Behrens]

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

this might be the issue: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=871643

** This bug has been marked a duplicate of bug 1662003
   /sbin/crda failed with exit code 249

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

Title:
  systemd-udevd Process '/sbin/crda' failed with exit code 249

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

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

[Bug 1751581] [NEW] systemd-udevd Process '/sbin/crda' failed with exit code 249

[Achim Behrens]

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

Public bug reported:

running 18.04 dev and seeing this in my syslog:

> systemd-udevd[332]: Process '/sbin/crda' failed with exit code 249.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: crda 3.18-1build1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Feb 25 14:24:11 2018
InstallationDate: Installed on 2013-09-28 (1611 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
SourcePackage: crda
UpgradeStatus: Upgraded to bionic on 2018-01-12 (43 days ago)
mtime.conffile..etc.default.crda: 2015-12-16T14:54:18.828473

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


** Tags: amd64 apport-bug bionic

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

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

Title:
  systemd-udevd Process '/sbin/crda' failed with exit code 249

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

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

[Bug 1751554] [NEW] os-prober: generates buggy btrfs entries in grub.cfg

[Achim Bohnet]

Public bug reported:

17.10 & 16.04: Choosing a grub menu entry that references a parallell
installed ubuntu system on a btrfs FS does not work.

I've installed neonuser (xenial based distro) in parallel to Kubuntu artful.
It's mounted via

UUID=879cfb57-f580-4326-a2fe-8dc83e0013f4 /os-neon-user   btrfs   
defaults,subvol=@ 0   2
UUID=879cfb57-f580-4326-a2fe-8dc83e0013f4 /os-neon-user/home btrfs 
defaults,subvol=@home 0   2

Running update-grub on artful generates grub.cf entries like for the
Neon User system:

..
   linux /boot/vmlinuz-4.13.0-32-generic root=/dev/sda3
   initrd /boot/initrd.img-4.13.0-32-generic
..

with does not work.

Workaround: Edit the entry to

   linux /@/boot/vmlinuz-4.13.0-32-generic root=/dev/sda3  
rootflags=subvol=@
initrd /@/boot/initrd.img-4.13.0-32-generic

Boots the other ubuntu OS on the btrfs filesys.


I can reproduce the bug on two systems (desktop with xenial, laptop with artful)


The grub.cfg entry of the currently booted OS on a btrfs FS is okay.  So 
update-grub handles
/ on btrfs okay.  But os-prober on /whatever with btrfs does not.

Achim

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: os-prober 1.74ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
NonfreeKernelModules: openafs wl
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Feb 25 10:55:13 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-01-13 (42 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2)
SourcePackage: os-prober
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: os-prober (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

** Attachment added: "grub.cfg with buggy os-proper entry for NeonUser on btrfs"
   https://bugs.launchpad.net/bugs/1751554/+attachment/5062352/+files/grub.cfg

** Summary changed:

- os-prober: generated buggy btrfs entries in grub.cfg
+ os-prober: generates buggy btrfs entries in grub.cfg

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

Title:
  os-prober: generates buggy btrfs entries in grub.cfg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1751554/+subscriptions

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

[Bug 1747944] Re: mce errors since latest kernelupdate

[Achim Behrens]

Just saw that Dell revoked their A15 Bios Update for the Poweredge T20.
So i downgraded to Bios A14 and the /proc/cpuinfo now shows 0x22 as
microcode again. It was 0x23 on the revoked BIOS A15.

Looks like the mce errors are gone now on load.

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

Title:
  mce errors since latest kernelupdate

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

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

[Bug 1609796] Re: cant upgrade EOL 15.04

[Achim Behrens]

people still running on 15.04, which End of Life was February 2016,
really should consider to do a fresh 16.04 LTS install now and stay on
LTS versions when they dont want to upgrade every 6 months.

But dealing with those upgrade situations should still be considered
from the ubuntu side. Like the solution to create an direct upgrade path
to the next LTS like said by #2

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

Title:
  cant upgrade EOL 15.04

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

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

[Bug 1747944] [NEW] mce errors since latest kernelupdate

[Achim Behrens]

Public bug reported:

Hi, running 16.04 server on a Dell Poweredge T20. Since latest
meltdown/spectre Kernel update i get "mce: [Hardware Error]: Machine
check events logged" shown in the logs. This happens when the server is
compiling stuff scheduled per cron.

the mce-log shows entries like: 
Hardware event. This is not a software error.
MCE 0
CPU 0 BANK 0 
TIME 1517991144 Wed Feb  7 09:12:24 2018
MCG status:
MCi status:
Corrected error
Error enabled
MCA: Internal parity error
STATUS 904f0005 MCGSTATUS 0
MCGCAP c09 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 6 Model 60

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-112-generic 4.4.0-112.135
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-112-generic.
AplayDevices: aplay: device_list:268: no soundcards found...
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: arecord: device_list:268: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Wed Feb  7 16:49:09 2018
HibernationDevice: RESUME=UUID=9b654b0f-96ef-49f0-bfd8-ad7907cb7b99
InstallationDate: Installed on 2017-05-17 (266 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Dell Inc. PowerEdge T20
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9edb2ffb-791e-4988-b3a9-7ce73227802c ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-112-generic N/A
 linux-backports-modules-4.4.0-112-generic  N/A
 linux-firmware 1.157.15
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0VD5HY
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd12/26/2017:svnDellInc.:pnPowerEdgeT20:pvr00:rvnDellInc.:rn0VD5HY:rvrA07:cvnDellInc.:ct6:cvr:
dmi.product.name: PowerEdge T20
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  mce errors since latest kernelupdate

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

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

[Bug 1746071] Re: starting skycat fails: ... librtd3.2.1.so: cannot open shared object file

[Achim Bohnet]

Thx a lot Ole!

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

Title:
  starting skycat fails: ...  librtd3.2.1.so: cannot open shared object
  file

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

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

[Bug 1746071] [NEW] starting skycat fails: ... librtd3.2.1.so: cannot open shared object file

[Achim Bohnet]

Public bug reported:

$ skycat
Error in startup script: couldn't load file 
"/usr/lib/skycat/libskycat3.1.2.so": librtd3.2.1.so: cannot open shared object 
file: No such file or directory
while executing
"load /usr/lib/skycat/libskycat3.1.2.so Skycat"
("package ifneeded Skycat 3.1.2" script)
invoked from within
"package require Skycat" 
(file "/usr/share/skycat/skycat3.1.2/main.tcl" line 7)

Library is not included in skycat package:

$ dpkg -L skycat | grep -i  librtd | wc -l
0

but in the Debian version you find librdt3.2.1.so See

https://packages.debian.org/stretch/amd64/skycat/filelist

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: skycat 3.1.2+starlink1~b+dfsg-3
ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Jan 29 19:35:21 2018
InstallationDate: Installed on 2018-01-24 (5 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2)
SourcePackage: skycat
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  starting skycat fails: ...  librtd3.2.1.so: cannot open shared object
  file

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

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

[Bug 1742323] Re: Meltdown Update Kernel doesnt boot

[Achim Behrens]

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

4.4.0-109  fixed it for me. so this bug is resolved, thanks

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

Title:
  Meltdown Update Kernel doesnt boot

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

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

[Bug 1742323] Re: Meltdown Update Kernel doesnt boot

[Achim Behrens]

While trying to get the BIOS update to a USB-Pendrive i found out on my 
Thinkpad x230 running 17.10  the latest kernel update make the USB not working 
properly :/ 
It show all usb pendrives as write-protected, while with the older kernel they 
do work. i will open another bug for this, when i can reboot to that kernel 
again.

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

Title:
  Meltdown Update Kernel doesnt boot

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

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

[Bug 1742323] Re: Meltdown Update Kernel doesnt boot

[Achim Behrens]

ok, updated the BIOS, did not change.

if i boot the linux-image-4.4.0-108-generic_4.4.0-108.131~lp1741934_amd64.deb  
from #3 it hangs after:
Loading Linux 4.4.0-108-generic...
Loading initial ramdisk...

when running the recovery mode, when booting the regular mode it doesnt
show anything.

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

Title:
  Meltdown Update Kernel doesnt boot

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

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

[Bug 1742323] Re: Meltdown Update Kernel doesnt boot

[Achim Behrens]

ok, the kernel from #3 didnt work. still the same issue, just doesnt do
anything after grub.

will try the new bios from dell now.

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

Title:
  Meltdown Update Kernel doesnt boot

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

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

[Bug 1742323] Re: Meltdown Update Kernel doesnt boot

[Achim Behrens]

@3  i will try your kernel builds right now. I cant take a screenshot
since there is just a blank screen.

@4 i did run ubuntu-bug on the booting kernel, which is the older one.


I just saw Dell offering a Bios/Uefi update. I will flash that after trying the 
test-kernel from @3

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

Title:
  Meltdown Update Kernel doesnt boot

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

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

[Bug 1742323] [NEW] Meltdown Update Kernel doesnt boot

[Achim Behrens]

Public bug reported:

Using a Dell Poweredge T20 and Ubuntu 16.04 with the 4.4 Kernel.

Just got the Meltdown update to kernel linux-image-4.4.0-108-generic but this 
doesnt boot at all. It just hangs after grub. There is no logs from syslog or 
such. SysReq Keys dont work neither.
The last kernel linux-image-4.4.0-104-generic still boots fine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-104-generic 4.4.0-104.127
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-104-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Date: Wed Jan 10 01:36:01 2018
HibernationDevice: RESUME=UUID=9b654b0f-96ef-49f0-bfd8-ad7907cb7b99
InstallationDate: Installed on 2017-05-17 (237 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Dell Inc. PowerEdge T20
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic.efi.signed 
root=UUID=9edb2ffb-791e-4988-b3a9-7ce73227802c ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-104-generic N/A
 linux-backports-modules-4.4.0-104-generic  N/A
 linux-firmware 1.157.14
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0VD5HY
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/11/2017:svnDellInc.:pnPowerEdgeT20:pvr00:rvnDellInc.:rn0VD5HY:rvrA07:cvnDellInc.:ct6:cvr:
dmi.product.name: PowerEdge T20
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

** Summary changed:

- Meltdown Update doesnt boot
+ Meltdown Update Kernel doesnt boot

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

Title:
  Meltdown Update Kernel doesnt boot

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

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

[Bug 1734495] [NEW] grub2 could nor be installed while 16.04.3 LTS was installed via USB

[achim steinhagen]

Public bug reported:

as in the subject mentioned the installation failed due to the grub2
could not be installed.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity 17.10.10
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CasperVersion: 1.387
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 25 16:36:54 2017
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  grub2 could nor be installed while 16.04.3 LTS was installed via USB

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

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

[Bug 1730927] Re: Support the new 280 character limit.

[Achim Behrens]

I still think this bug falls completely under point 2.1 of the SRU wiki page.
Twitter changed the character limit for a reason, and to say: "just use the old 
limit" is not a solution, because it makes you now act differently on their 
service than the rest of the users, who can use the new limit. In the end it 
could lead to ubuntu users not use corebird anymore.

I did apply the change locally to the sources of the artful package and 
recompiled it for myself. It works as expected now. This could be done easily 
for all repos, without increasing the major version of the package.
I want to make clear that its not about me, i have a working solution. I think 
this could be and should be fixed for all ubuntu users without the need for 
them to install unstable packages or 3rd party Repos.
I think your interpretation of the SRU is wrong. Since this would make no 
package patchable in final releases.

I really dont understand why this is such a big issue to get the
packages patched to work as expected with the twitter webservice.

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

Title:
  Support the new 280 character limit.

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

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

[Bug 1730927] Re: Support the new 280 character limit.

[Achim Behrens]

This Bug is not fixed for the actual supported packages.
Since not using the correct Character Limit is a heavy bug, i think the stable 
packages should be updated/patched.


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

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

Title:
  Support the new 280 character limit.

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

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

[Bug 1730927] [NEW] Support the new 280 character limit.

[Achim Behrens]

Public bug reported:

Twitter changed to a new character limit of 280 characters:
https://blog.twitter.com/official/en_us/topics/product/2017/tweetingmadeeasier.html

The Corebird dev already changed the limit for corebird:
https://github.com/baedert/corebird/commit/d3cc0b068b4f3b1d0d97e4bd7c9e723d002636c1

please update the repo Packages to include this patch.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: corebird 1.6-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed Nov  8 11:27:10 2017
InstallationDate: Installed on 2013-09-28 (1501 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
SourcePackage: corebird
UpgradeStatus: Upgraded to artful on 2017-06-30 (131 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  Support the new 280 character limit.

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

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

[Bug 1723156] [NEW] lightdm only shows black screen with cursor on 17.10

[Achim Behrens]

Public bug reported:

after recent updates on 17.10 (development) lightdm fails. It only shows
a black screen and the cursor. Cant change to tty1 with ctrl+alt+f1.

started from grub with systemd.unit=multi-user.target into tty1 and
started gdm from there, so i could log on to unity (with broken gtk).

nothing obvious for me in the log files from syslog or lightdm.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: lightdm 1.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Oct 12 17:15:29 2017
InstallationDate: Installed on 2013-09-28 (1475 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: Upgraded to artful on 2017-06-30 (104 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  lightdm only shows black screen with cursor on 17.10

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

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

[Bug 1574670] Re: ubuntu-support-status returns inaccurate information

[Achim Behrens]

I marked the bugreports for packages affected by this on my system as 
duplicates:  
Bug #1710718
Bug #1710719
Bug #1710720
Bug #1710721

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

Title:
  ubuntu-support-status returns inaccurate information

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1574670/+subscriptions

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

[Bug 1710721] Re: This packages have the wrong timeframe set for the xenial LTS release

[Achim Behrens]

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

Hi, yeah i have no issue to mark that bugs (there are several of them
for several packages affected) as duplicates of that bug. My intention
was to document which packages are affected and need this change since
its a variety of packages and sometimes just some lone packages are
affected from the same naming-group.

I will mark my other bugs as duplicates, too.

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

Title:
  This packages have the wrong timeframe set for the xenial LTS release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsdl1.2/+bug/1710721/+subscriptions

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

[Bug 1710719] Re: python-dbg and other python packages in xenial got wrong timeframe set for support time

[Achim Behrens]

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

** This bug has been marked a duplicate of bug 1574670
   ubuntu-support-status returns inaccurate information

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

Title:
  python-dbg and other python packages in xenial got wrong timeframe set
  for support time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1710719/+subscriptions

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

[Bug 1710718] Re: x11proto* xenial packages got wrong Support timeframe tag

[Achim Behrens]

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

** This bug has been marked a duplicate of bug 1574670
   ubuntu-support-status returns inaccurate information

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

Title:
  x11proto* xenial packages got wrong Support timeframe tag

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11proto-fixes/+bug/1710718/+subscriptions

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

[Bug 1710720] Re: some libpcre3* packages have from support timeframe set for xenial LTS

[Achim Behrens]

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

** This bug has been marked a duplicate of bug 1574670
   ubuntu-support-status returns inaccurate information

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

Title:
  some libpcre3* packages have from support timeframe set for xenial LTS

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

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

[Bug 1710720] [NEW] some libpcre3* packages have from support timeframe set for xenial LTS

[Achim Behrens]

Public bug reported:

Some libpcre* packages from 16.04 have the wrong support timeframe set
into the package info. Therefore they are falsely shown as unsupported
on the "ubuntu-support-status" output:


~$ apt show libpcre3-dbg 
Package: libpcre3-dbg
Version: 2:8.38-3.1
Priority: optional
Section: libdevel
Source: pcre3
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Matthew Vernon 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 3.514 kB
Depends: libpcre3 (= 2:8.38-3.1), libpcrecpp0v5 (= 2:8.38-3.1)
Supported: 9m
Download-Size: 692 kB
APT-Sources: http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
Description: Perl 5 Compatible Regular Expression Library - debug symbols
 Dies ist eine Bibliothek von Funktionen zur Unterstützung von regulären
 Ausdrücken, deren Syntax und Semantik so ähnlich wie möglich zu denen der
 Sprache Perl 5 sind.
 .
 This package contains the debug symbols,


This should be set to the 5years LTS timeframe (since its in main) and not to 
9months.

** Affects: pcre3 (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/1710720

Title:
  some libpcre3* packages have from support timeframe set for xenial LTS

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

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

[Bug 1710721] [NEW] This packages have the wrong timeframe set for the xenial LTS release

[Achim Behrens]

Public bug reported:

The libsdl* packages from 16.04 have the wrong support timeframe set
into the package info. Therefore they are falsely shown as unsupported
on the "ubuntu-support-status" output:


~$ apt show libsdl1.2-dev
Package: libsdl1.2-dev
Version: 1.2.15+dfsg1-3
Priority: optional
Section: libdevel
Source: libsdl1.2
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian SDL packages maintainers 

Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 2.807 kB
Provides: libsdl-dev
Depends: libsdl1.2debian (= 1.2.15+dfsg1-3), libasound2-dev, libcaca-dev, 
libglu1-mesa-dev | libglu-dev, libpulse-dev, libx11-dev, libxext-dev
Conflicts: libsdl-dev
Replaces: libsdl-dev
Homepage: http://www.libsdl.org/
Supported: 9m
Download-Size: 707 kB
APT-Manual-Installed: yes
APT-Sources: http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
Description: Simple DirectMedia Layer (Entwicklungsdateien)
 SDL ist eine Bibliothek, die Programmen portablen Zugriff auf systemnaher
 Ebene auf einen Video-Bildspeicher, Audioausgaben, Maus und Tastatur
 ermöglicht.
 .
 Das Paket enthält die notwendigen Dateien zum Kompilieren und Linken von
 Programmen, die SDL nutzen.


This should be set to the 5years LTS timeframe (since its in main) and
not to 9months.

** Affects: libsdl1.2 (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/1710721

Title:
  This packages have the wrong timeframe set for the xenial LTS release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsdl1.2/+bug/1710721/+subscriptions

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

[Bug 1710719] [NEW] python-dbg and other python packages in xenial got wrong timeframe set for support time

[Achim Behrens]

Public bug reported:

The python* packages from 16.04 have the wrong support timeframe set
into the package info. Therefore they are falsely shown as unsupported
on the "ubuntu-support-status" output:


~$ apt show python-dbg
Package: python-dbg
Version: 2.7.11-1
Priority: extra
Section: python
Source: python-defaults
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Matthias Klose 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 25,6 kB
Depends: python (= 2.7.11-1), libpython-dbg (= 2.7.11-1), python2.7-dbg (>= 
2.7.11-1~)
Homepage: http://www.python.org/
Supported: 9m
Download-Size: 1.252 B
APT-Sources: http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
Description: Debugversion des Python-Interpreters (Version 2.7)
 Dieser Python-Interpreter wurde mit --pydebug konfiguriert. Dynamisch
 ladbare Module sucht er zuerst in /usr/lib/python2.7/lib-dynload/debug.


This should be set to the 5years LTS timeframe (since its in main) and not to 
9months.

** Affects: python-defaults (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/1710719

Title:
  python-dbg and other python packages in xenial got wrong timeframe set
  for support time

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1710719/+subscriptions

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

[Bug 1710718] [NEW] x11proto* xenial packages got wrong Support timeframe tag

[Achim Behrens]

Public bug reported:

The x11proto* packages from 16.04 have the wrong support timeframe set
into the package info. Therefore they are falsely shown as unsupported
on the "ubuntu-support-status" output:


~$ apt show x11proto-fixes-dev
Package: x11proto-fixes-dev
Version: 1:5.0-2ubuntu2
Priority: optional
Section: x11
Source: x11proto-fixes
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian X Strike Force 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 75,8 kB
Depends: x11proto-core-dev, x11proto-xext-dev (>= 7.0.99.1)
Task: ubuntu-sdk-libs-dev
Supported: 9m
Download-Size: 14,2 kB
APT-Manual-Installed: no
APT-Sources: http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
Description: Wire Protocol-Erweiterung für X11-Fixes
 Dieses Paket enthält Header-Dateien zur Entwicklung, welche das Wire
 Protocol für die Fixes-Erweiterung beschreiben, das einige kleinere
 Erweiterungen für das X-Protokoll enthält, einschließlich eines
 Regionentyps.
 .
 Weitere Informationen über X.Org finden Sie unter .
 .
 Dieses Paket wurde aus dem X.org-fixesproto-proto-Modul erstellt.

This should be set to the 5years LTS timeframe (since its in main) and
not to 9months.

** Affects: x11proto-fixes (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/1710718

Title:
  x11proto* xenial packages got wrong Support timeframe tag

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11proto-fixes/+bug/1710718/+subscriptions

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

[Bug 1574670] Re: ubuntu-support-status returns inaccurate information

[Achim Behrens]

The issue seems to be, that ubuntu-support-status reads the package
information about support timeframe and some maintainers get confused or
mix or forget to set the proper timeframe for the LTS releases to 5
years (for the main repo).

On a 16.04 machine it lists python-dbg as unsupported. the reason is its
set to 9month support:

> apt show python-dbg
Package: python-dbg
Version: 2.7.11-1
Priority: extra
Section: python
Source: python-defaults
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Matthias Klose 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 25,6 kB
Depends: python (= 2.7.11-1), libpython-dbg (= 2.7.11-1), python2.7-dbg (>= 
2.7.11-1~)
Homepage: http://www.python.org/
Supported: 9m
Download-Size: 1.252 B
APT-Sources: http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
Description: Debugversion des Python-Interpreters (Version 2.7)
 Dieser Python-Interpreter wurde mit --pydebug konfiguriert. Dynamisch
 ladbare Module sucht er zuerst in /usr/lib/python2.7/lib-dynload/debug.

So what is the correct path now? file bugs for every Package where the
maintainers set the Support timeframe to 9 months?

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

Title:
  ubuntu-support-status returns inaccurate information

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1574670/+subscriptions

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

[Bug 1493839] Re: overlayfs: disabling V1 support leads to compile failure

[Achim Schreiber]

fs: overlay: fix compile error when CONFIG_OVERLAY_FS_V1 is not set

Fixes Ubuntu Launchpad Bug #1493839

Added necessary #ifdef around undeclared ovl_v1_fs_type
according to CodingStyle lines 910-915

Signed-off-by: Achim Schreiber <git...@ibekas.de>


** Attachment added: "patch_launchpad_bug_1493839"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1493839/+attachment/4910248/+files/patch_launchpad_bug_1493839

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

Title:
  overlayfs: disabling  V1 support leads to compile failure

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

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

[Bug 1615482] Re: apt-daily timer runs at random hours of the day

[Achim Spangler]

According to https://ubuntuforums.org/showthread.php?t=2330407=2 I
am not the only user, where the package list is never updated due to the
default timer setting in /etc/systemd/system/timers.target.wants/apt-
daily.timer . This way, the Taskbar-GUI App never displays any available
package updates, as long as you don't call "sudo apt-get update"
manually.

This problem is caused by using the computer only for short durations
(e.g. notebook), so that the calculated random wait time is longer than
the average usage time per day (i.e. "apt-get update" is never called).

My personal solution was to use a fixed wait time after system boot of
about 5 minutes (see attachement), and use "After=network.target" to
make sure, that the network is ready for successfull call of "apt-get
update" (see attachement).

Maybe the system could get enhanced to derive the average uptime per
session / day, so that the apt-daily timer gets restricted to this
average time interval.

Or the system could detect, whether the computer is used as a
continually running system, or whether the computer is each time only
running for some hours. In the latter case, at least the package list
should get updated a short time after system start / boot.

My system is running Kubuntu 6.04 LTS _Xenial.

** Attachment added: "Call apt 5 minutes after system boot for short running 
computer"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+attachment/4865174/+files/apt-daily.timer

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

Title:
  apt-daily timer runs at random hours of the day

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

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

[Bug 1629504] Re: Compiles, but brings on Oops on load with 4.8-rc & 4.8 hwe-16.04

[Achim Bohnet]

** Tags added: 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/1629504

Title:
  Compiles, but brings on Oops on load with 4.8-rc & 4.8 hwe-16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1629504/+subscriptions

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

[Bug 1629504] Re: Compiles, but brings on Oops on load with 4.8-rc & 4.8 hwe-16.04

[Achim Bohnet]

** Summary changed:

- Compiles, but brings on Oops on load with 4.8-rc
+ Compiles, but brings on Oops on load with 4.8-rc & 4.8 hwe-16.04

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

Title:
  Compiles, but brings on Oops on load with 4.8-rc & 4.8 hwe-16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1629504/+subscriptions

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

[Bug 1663548] Re: fwupd crashed with SIGSEGV in _int_malloc()

[Achim Behrens]

Ok, the workaround with commenting out PrivateUsers=yes from
/lib/systemd/system/fwupd.service worked here, too, on the 17.04 on the
Lenovo Thinkpad x230.

fuwpd is not crashing anymore. But i dont really know what the
consequences of this workaround are.

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

Title:
  fwupd crashed with SIGSEGV in _int_malloc()

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

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

[Bug 1663548] Re: fwupd crashed with SIGSEGV in _int_malloc()

[Achim Behrens]

having the same issue on a Lenovo Thinkpad x230

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

Title:
  fwupd crashed with SIGSEGV in _int_malloc()

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

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

[Bug 1629504] Re: Compiles, but brings on Oops on load with 4.8-rc

[Achim Bohnet]

I'd NULL pointer bugs in wl_* routines in xenial + 4.8 hwe + broadcom-
sta 6.30.223.271-3~16.04.1 from xenial proposed.

Applying the patch in #1 fixes them.  I've now have wlan with hwe kernel
in xenial!!

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

Title:
  Compiles, but brings on Oops on load with 4.8-rc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1629504/+subscriptions

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

[Bug 1609796] Re: cant upgrade EOL 15.04

[Achim Behrens]

there are still users showing up with 15.04 ubuntu releases in use in
#ubuntu. Telling them to use the -d switch is still the wrong way.

Why was vivid and wily not added to the http://old-
releases.ubuntu.com/ubuntu/ repo? that would give the user the chance to
do the EOLupgrade like it used to be and shown here: http://old-
releases.ubuntu.com/ubuntu/

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

Title:
  cant upgrade EOL 15.04

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

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

[Bug 1653994] [NEW] thinkfan fails on installing on 16.10 due to systemd issue.

[Achim Behrens]

Public bug reported:

uptodate 16.10.
Tried to install thinkfan form the repos and the install fails due to some 
systemd issues:

Vorbereitung zum Entpacken von .../thinkfan_0.9.2-1_amd64.deb ...
Entpacken von thinkfan (0.9.2-1) ...
Trigger für ureadahead (0.100.0-19) werden verarbeitet ...
thinkfan (0.9.2-1) wird eingerichtet ...
Job for thinkfan.service failed because the control process exited with error 
code.
See "systemctl status thinkfan.service" and "journalctl -xe" for details.
invoke-rc.d: initscript thinkfan, action "start" failed.
● thinkfan.service - simple and lightweight fan control program
   Loaded: loaded (/lib/systemd/system/thinkfan.service; disabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Mi 2017-01-04 15:39:15 CET; 8ms ago
  Process: 12251 ExecStart=/usr/sbin/thinkfan (code=exited, status=4)

Jan 04 15:39:15 ThinkPad systemd[1]: Starting simple and lightweight fan 
control program...
Jan 04 15:39:15 ThinkPad systemd[1]: thinkfan.service: Control process exited, 
code=exited status=4
Jan 04 15:39:15 ThinkPad systemd[1]: Failed to start simple and lightweight fan 
control program.
Jan 04 15:39:15 ThinkPad systemd[1]: thinkfan.service: Unit entered failed 
state.
Jan 04 15:39:15 ThinkPad systemd[1]: thinkfan.service: Failed with result 
'exit-code'.
dpkg: Fehler beim Bearbeiten des Paketes thinkfan (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Trigger für systemd (231-9ubuntu2) werden verarbeitet ...
Trigger für man-db (2.7.5-1) werden verarbeitet ...
Trigger für ureadahead (0.100.0-19) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
 thinkfan
E: Sub-process /usr/bin/dpkg returned an error code (1)


I guess the systemd unit needs some tweaking, but this exceeds my
knowledge.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: thinkfan 0.9.2-1
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jan  4 15:52:24 2017
Dependencies:
 gcc-6-base 6.2.0-5ubuntu12
 libc6 2.24-3ubuntu2
 libgcc1 1:6.2.0-5ubuntu12
InstallationDate: Installed on 2013-09-28 (1194 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
SourcePackage: thinkfan
UpgradeStatus: Upgraded to yakkety on 2016-09-27 (99 days ago)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  thinkfan fails on installing on 16.10 due to systemd issue.

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

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

[Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs

[Achim Behrens]

installed the freshly build amd64 yakkety .debs from the link in #91 and
its working again now.

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

Title:
  chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec
  certs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+subscriptions

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

[Bug 1634977] [NEW] gedit crashes with enabled gedit-latex-plugin

[Achim Behrens]

Public bug reported:

running ubuntu 16.10, uptodate.
installed gedit-latex-plugin and enabled that in the settings menu. after that 
gedit crashes on startup. only removing the gedit-latex-plugin package helps.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gedit 3.22.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Oct 19 19:12:23 2016
InstallationDate: Installed on 2013-09-28 (1117 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
SourcePackage: gedit
UpgradeStatus: Upgraded to yakkety on 2016-09-27 (22 days ago)

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

** Affects: gedit-latex-plugin (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

** Also affects: gedit-latex-plugin (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/1634977

Title:
  gedit crashes with enabled gedit-latex-plugin

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

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

[Bug 1322968] Re: Changing country leads to invalid locale

[Achim Bohnet]

Fixed in 16.04 LTS (Xenial).

You can select the

region  (with defines the default)

and if you don't like default settings, you can set individually:

Numbers
Time
Currency
Measurement units
Collation and Sorting

Which results in settings like:

(0)ach@allee:~$ cat .config/plasma-localerc
[Formats]
LANG=en_US.UTF-8
LC_MEASUREMENT=de_DE.UTF-8
LC_MONETARY=de_DE.UTF-8
LC_TIME=en_GB.UTF-8
useDetailed=true

[Translations]
LANGUAGE=en_US
(0)ach@allee:~$ cat .config/plasma-localerc
[Formats]
LANG=en_US.UTF-8

[Translations]
LANGUAGE=en_US
(0)ach@allee:~$ cat .config/plasma-localerc
[Formats]
LANG=en_US.UTF-8

[Translations]
LANGUAGE=en_US

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

Title:
  Changing country leads to invalid locale

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1322968/+subscriptions

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

[Bug 1621336] Re: snapd.boot-ok.service hangs eternally on cloud image upgrades

[Achim Behrens]

a user just had the "snapd always hanging on install/reinstall and
blocking apt" issue.

after some fiddeling we used the workaround from Comment#4
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1621336/comments/4
:

starting a rootshell with "sudo -i". then running "echo "bash -c
'service snapd.boot-ok start'" | at now + 4 min", then "apt install
snapd" (if it argues about canceled dpkg processes use the "dpkg
--configure -a". then wait for at least 4 minutes.

the hanging should gone then.

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

Title:
  snapd.boot-ok.service hangs eternally on cloud image upgrades

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1621336/+subscriptions

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

[Bug 1609796] [NEW] cant upgrade EOL 15.04

[Achim Behrens]

Public bug reported:

A user in #ubuntu complained about no beeing able to upgrade his EOL
15.04 (cloud) server install, so i made a 15.04 server install in vbox
to test this scenario, and he is right:

Running "sudo do-release-upgrade" results in: 
"An upgrade from 'vivid' to 'xenial' is not supported with this tool."

An EOL Upgrade with changing the sources.list to use the old-releases
doesnt work since vivid is not moved to the old-releases yet: http
://old-releases.ubuntu.com/ubuntu/dists/ .

** Affects: update-manager-core (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/1609796

Title:
  cant upgrade EOL 15.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager-core/+bug/1609796/+subscriptions

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

[Bug 1609796] Re: cant upgrade EOL 15.04

[Achim Behrens]

Ok, now i just tested a "sudo do-release-upgrade -d" which seems to
work.

But this is a total desaster and must be solved differently. There are
too many bad howtos out there alread telling every user just to run the
-d upgrade which results in users ending up on devel releases when the
dont want to because most people dont know what the -d is for.

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

Title:
  cant upgrade EOL 15.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager-core/+bug/1609796/+subscriptions

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

[Bug 1608880] [NEW] systemd doesnt work with timed fsck, only with counted mount fsck

[Achim Behrens]

Public bug reported:

Updated my homserver from 14.04 to 16.04. Got a "/dev/sda1 will be
fscked on next reboot" hint in the MOTD. Did some reboots and the fsck
never happend. Tried with "sudo touch /forcefsck" but the message didnt
go away. Thought it was an error of the MOTD scripts and tried to fiddle
with them. But it reappeard ever time.

Looked at the syslogs logs and saw the fsck never happend.

Looked at the output from dumpe2fs and it showed several interesting 
informations:
 * the mount count was 12 and the maximum mountcount of 34 was not reached
 * the timed fsck date was reached
 * the last fsck was long ago (next confirmation the /forcefsck didnt work at 
all)

i changed the mount count to 35 with "sudo tune2fs -C 35 /dev/sda1"
which made the fsck on next reboot.

So what works: 
 * mount count fsck on reboot

what doesnt work:
 * setting /forcefsck manually
 * timed fsck 

what should work?
 * all 3 of them should work.

** Affects: systemd (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/1608880

Title:
  systemd doesnt work with timed fsck, only with counted mount fsck

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

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

[Bug 1605474] Re: do-release-upgrade could notify when release is expected

[Achim Behrens]

As already said in https://bugs.launchpad.net/ubuntu/+bug/1606850 :

i really suggest the release-team chases the bugs before the .1 release
and opens the LTS upgrade on the .1 release.

As you can see here on comment #2 people want to upgrade and the
internet is full of the wrong advice to use the -d, --devel-release
setting.

I dont see a technical reason to delay the  LTS upgrade.
So i hope on the next LTS release cycle the schedule will make sure the 
bugtesting is done before the .1 release. The supporter teams will give thanks 
for that.

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

Title:
  do-release-upgrade could notify when release is expected

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

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

[Bug 1606850] [NEW] LTS upgrade should be opened on Release Date of 1st Pointrelease

[Achim Behrens]

Public bug reported:

The LTS upgrade path from LTS to the next LTS should be opened on the .1
pointrelease of the next LTS.

>From the view of a Supporter the situation right now is katastrophic. We
had enough trouble telling everyone that the LTS upgrade is not opened
directly on the 16.04 release. And now a lot of users come back again
asking why the LTS upgrade is still not working.

It was told, that this delay of maybe one week is due to last bug testings. But 
this is not really acceptable for the users and the volunteer supporters. 
You can join #ubuntu on freenode and watch how many users are there beeing 
confused why the upgrade doesnt work and dont really understand why its delayed.

It should not make a difference for the release-teams when they do the
testing for the LTS upgrade. So there will be a huge benefit if this is
done before the .1 release so the LTS upgrade is working on release-
date.

** Affects: 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/1606850

Title:
  LTS upgrade should be opened on Release Date of 1st Pointrelease

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

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

[Bug 1568863] Re: vlc crashes with segfault in libvdpau_va_gl.so.1

[Achim Behrens]

Removing the libvdpau-va-gl1 package fixes this crash.
Need to test what the drawbacks are on this workaround.

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

Title:
  vlc crashes with segfault in libvdpau_va_gl.so.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvdpau-va-gl/+bug/1568863/+subscriptions

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

[Bug 1581604] Re: akonadi KF5: search email/contacts/ ... not working: libkf5akonadisearch* pkgs not installed by default

[Achim Bohnet]

** Summary changed:

- akonadi KF5:  search email/contacts/ ... not working: Missing  
libkf5akonadisearch* pkgs
+ akonadi KF5:  search email/contacts/ ... not working: libkf5akonadisearch* 
pkgs not installed by default

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

Title:
  akonadi KF5:  search email/contacts/ ... not working:
  libkf5akonadisearch* pkgs not installed by default

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

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

[Bug 1581604] [NEW] akonadi KF5: search email/contacts/ ... not working: Missing libkf5akonadisearch* pkgs

[Achim Bohnet]

Public bug reported:

Maybe this bug should be reassigned to akonadi-server (See below)

In xenial searching akonadi is no longer working.  Installed on my
system are

libkf5akonadisearchdebug5:amd64
libkf5akonadisearchpim5:amd64

missing are:

libkf5akonadisearch-bin  (which pulls in libkf5akonadisearch-data
libkf5akonadisearch-plugins libkf5akonadisearchcore5
libkf5akonadisearchxapian5)


After installation:
  * email body search works.
  * email address completion work again  (only ldap worked before)


Because libkf5akonadisearch-plugins contains several plugins 

akonadi/contactsearchstore.so
akonadi/notesearchstore.so
akonadi/emailsearchstore.so
akonadi/calendarsearchstore.so
akonadi/akonadi_search_plugin.so
krunner_pimcontacts.so

I would suggest that akonadi-server at least recommends
libkf5akonadisearch-bin


Achim

** Affects: kubuntu-meta (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/1581604

Title:
  akonadi KF5:  search email/contacts/ ... not working: Missing
  libkf5akonadisearch* pkgs

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

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

[Bug 1579070] Re: Archive removal: qt4 based baloo & akonadi pkgs

[Achim Bohnet]

One more:

 libakonadiprotocolinternals1

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

Title:
  Archive removal:  qt4 based  baloo & akonadi pkgs

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

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

[Bug 1579070] Re: Archive removal: qt4 based baloo & akonadi pkgs

[Achim Bohnet]

There are more QT4 Pim pkgs that I could purge from my system:

 libkcalcore4
 libkabc4
 libkldap4
 libkmime4
 libkpimutils4
 libkresources4

other qt4 pim pkgs can't be removed because kopete, ktorrent, amarok
kmymoney still depend on them.

Achim

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

Title:
  Archive removal:  qt4 based  baloo & akonadi pkgs

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

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

[Bug 1579814] Re: chromium browser needs an update to fix CVEs

[Achim Behrens]

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

** This bug has been marked a duplicate of bug 1573685
   Security fixes from 50.0.2661.75 and 50.0.2661.94

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

Title:
  chromium browser needs an update to fix CVEs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1579814/+subscriptions

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

[Bug 1579814] Re: chromium browser needs an update to fix CVEs

[Achim Behrens]

** Information type changed from Private Security to Public Security

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

Title:
  chromium browser needs an update to fix CVEs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1579814/+subscriptions

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

[Bug 1579070] Re: Archive removal: qt4 based baloo & akonadi pkgs

[Achim Bohnet]

** Summary changed:

- Archive removal:  qt4 based  baloo pkgs 
+ Archive removal:  qt4 based  baloo & akonadi pkgs

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

Title:
  Archive removal:  qt4 based  baloo & akonadi pkgs

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

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

[Bug 1579070] [NEW] Archive removal: qt4 based baloo pkgs

[Achim Bohnet]

Public bug reported:

As qt4 based baloo and akonadi pkgs are incompatible with the currently
used qt5 based baloo and akonadi there's no point to still have them in
the archive at all:

IMHO remove them from pkg archive

ii  baloo-utils4:4.14.3-0ubuntu5 
un  baloo4 
ii  libbaloocore4  4:4.14.3-0ubuntu5 
ii  libbaloofiles4 4:4.14.3-0ubuntu5 
ii  libbalooxapian44:4.14.3-0ubuntu5 

root@lap-allee:~# apt-cache search libakonadi-
libakonadi-calendar4 - library providing calendar helpers for Akonadi items
libakonadi-contact4 - Akonadi contacts access library
libakonadi-dev - development files for the Akonadi PIM storage service
libakonadi-kabc4 - Akonadi address book access library
libakonadi-kcal4 - Akonadi calendar access library
libakonadi-kde4 - library for using the Akonadi PIM data server
libakonadi-kf5 - transitional dummy package
libakonadi-kmime4 - Akonadi MIME handling library
libakonadi-notes4 - Akonadi notes access library
libakonadi-perl - Perl bindings for Akonadi
libakonadi-socialutils4 - Akonadi resources for handling social feeds
libakonadi-xml4 - Akonadi XML helper library

** Affects: kubuntu-meta (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/1579070

Title:
  Archive removal:  qt4 based  baloo pkgs

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

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