from:"Achim Behrens"

[Touch-packages] [Bug 1964794] Re: Faulty linux-firmware upgrade

2022-03-15 Thread 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
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1964794

Title:
  Faulty linux-firmware upgrade

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Can't upgrade the package:

  Préparation du dépaquetage de 
.../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ...
  Dépaquetage de linux-firmware (20220314.gitcd01f857-0ubuntu1) sur 
(20220302.gitee0667aa-0ubuntu1) ...
  dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb 
(--unpack) :
   impossible d'ouvrir « /lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new 
»: Aucun fichier ou dossier de ce type
  Aucun rapport « apport » n'a été créé car le message d'erreur rapporte un 
problème sur le système local

 update-initramfs: Generating 
/boot/initrd.img-5.15.0-22-generic
  update-initramfs: Generating /boot/initrd.img-5.15.0-18-generic
  Des erreurs ont été rencontrées pendant l'exécution :
   /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

2018-02-25 Thread 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
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1579580

Title:
  ureadahead reports relative path errors in journalctl output

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  ureadahead reports relative path errors in my journalctl output.

  This is currently 4368 lines of useless annoyances in my logs.

  To see if you have this problem, run: journalctl -b | grep ureadahead
  | grep relative | wc -l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ureadahead 0.100.0-19
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  8 15:55:18 2016
  InstallationDate: Installed on 2016-04-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

2018-02-25 Thread 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
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1751673

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

Status in network-manager package in Ubuntu:
  New

Bug description:
  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

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

2017-10-12 Thread 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
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1723156

Title:
  lightdm only shows black screen with cursor on 17.10

Status in lightdm package in Ubuntu:
  New

Bug description:
  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)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-08-16 Thread 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
Touch seeded packages, which is subscribed to python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1710719

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

Status in python-defaults package in Ubuntu:
  New

Bug description:
  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.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-08-16 Thread 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
Touch seeded packages, which is subscribed to pcre3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710720

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

Status in pcre3 package in Ubuntu:
  New

Bug description:
  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.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-08-14 Thread 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
Touch seeded packages, which is subscribed to pcre3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710720

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

Status in pcre3 package in Ubuntu:
  New

Bug description:
  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.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-08-14 Thread 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
Touch seeded packages, which is subscribed to python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1710719

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

Status in python-defaults package in Ubuntu:
  New

Bug description:
  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.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

2016-08-02 Thread 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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1608880

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

Status in systemd package in Ubuntu:
  New

Bug description:
  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.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1565483] [NEW] pulseaudio crashes while using vlc and crashes whole system

2016-04-03 Thread Achim Behrens

Public bug reported:

using uptodate 16.04

watching a dvb-t channels.conf with vlc (which worked in 15.10 and still
works on windows with same channels.conf and vlc) crashes after some
time ( <1min) and freezed whole system.

Only Sysreq reboot works.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   k1l2158 F...m pulseaudio
 /dev/snd/controlC0:  k1l2158 F pulseaudio
CurrentDesktop: Unity
Date: Sun Apr  3 16:43:51 2016
InstallationDate: Installed on 2013-09-28 (918 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to xenial on 2016-02-11 (52 days ago)
dmi.bios.date: 09/17/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ETA5WW (2.65 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2325TZX
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA5WW(2.65):bd09/17/2015:svnLENOVO:pn2325TZX:pvrThinkPadX230:rvnLENOVO:rn2325TZX:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2325TZX
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1565483

Title:
  pulseaudio crashes while using vlc and crashes whole system

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  using uptodate 16.04

  watching a dvb-t channels.conf with vlc (which worked in 15.10 and
  still works on windows with same channels.conf and vlc) crashes after
  some time ( <1min) and freezed whole system.

  Only Sysreq reboot works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   k1l2158 F...m pulseaudio
   /dev/snd/controlC0:  k1l2158 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr  3 16:43:51 2016
  InstallationDate: Installed on 2013-09-28 (918 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to xenial on 2016-02-11 (52 days ago)
  dmi.bios.date: 09/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA5WW (2.65 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325TZX
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA5WW(2.65):bd09/17/2015:svnLENOVO:pn2325TZX:pvrThinkPadX230:rvnLENOVO:rn2325TZX:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325TZX
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1565483] Re: pulseaudio crashes while using vlc and crashes whole system

2016-04-03 Thread Achim Behrens

** Attachment added: "syslog from the crash"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1565483/+attachment/4621829/+files/syslog

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1565483

Title:
  pulseaudio crashes while using vlc and crashes whole system

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  using uptodate 16.04

  watching a dvb-t channels.conf with vlc (which worked in 15.10 and
  still works on windows with same channels.conf and vlc) crashes after
  some time ( <1min) and freezed whole system.

  Only Sysreq reboot works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   k1l2158 F...m pulseaudio
   /dev/snd/controlC0:  k1l2158 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr  3 16:43:51 2016
  InstallationDate: Installed on 2013-09-28 (918 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to xenial on 2016-02-11 (52 days ago)
  dmi.bios.date: 09/17/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA5WW (2.65 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325TZX
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA5WW(2.65):bd09/17/2015:svnLENOVO:pn2325TZX:pvrThinkPadX230:rvnLENOVO:rn2325TZX:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325TZX
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1558331] Re: message "The repository is insufficiently signed by key (weak digest)" is poorly worded

2016-03-21 Thread Achim Behrens

I dont think this is a bug. The wording says what the issue is. The Key
used is only sha1 which is considered too weak. The ones using that old
Keys should fix their repos and make proper signing.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1558331

Title:
  message "The repository is insufficiently signed by key  (weak
  digest)" is poorly worded

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  The title pretty much says it all.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted install

2016-01-05 Thread Achim Behrens

This really needs to be adressed ASAP.

The Support Communites are flooded by angry users with blocked
Packagesystems due to a full /boot blocking new kernels to be installed.

In this time, when we have 5TB HDDs and even 500GB SSDs, i really dont know why 
we still need that small /boot partitions that it runs out of space that fast.
And having no automatic removing old kernels is another issue.

This really spoils the user experience, and non technical users really
dont know what to do and dont feel comfortable to delete files in /boot
manually. So best is do increase the /boot partition made on install and
have a post-install script running that removes old kernels.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted install

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1448684] Re: /var/lib/apt/lists/partial is full

2015-04-28 Thread Achim Behrens

A User reported that behaviour and on his sudo apt-get update there
were some PPAs with errors. After removing the failing PPAs the issue
seems to be resolved.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1448684

Title:
  /var/lib/apt/lists/partial is full

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  After i upgraded to Ubuntu 15.04,  my disk space become
  zero.Surprised.

  After analysing the disk space, found /var/lib/apt/lists/partial is
  full.  i removed two heaviest file manually.  system became normal
  after that. The same thing i hdd repeated in the next day. I hope some
  daily update is eating my disk space. I request a support ASAP.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1964794] Re: Faulty linux-firmware upgrade

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1565483] [NEW] pulseaudio crashes while using vlc and crashes whole system

[Touch-packages] [Bug 1565483] Re: pulseaudio crashes while using vlc and crashes whole system

[Touch-packages] [Bug 1558331] Re: message "The repository is insufficiently signed by key (weak digest)" is poorly worded

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted install

[Touch-packages] [Bug 1448684] Re: /var/lib/apt/lists/partial is full

14 matches

Site Navigation

Mail list logo

Footer information