[Touch-packages] [Bug 1801264] Re: Wifi drops out 1-30 minutes after boot on Ubuntu 18.10

2019-01-01 Thread Launchpad Bug Tracker 
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1801264

Title:
  Wifi drops out 1-30 minutes after boot on Ubuntu 18.10

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  I will boot, Wifi connects fine, and then the wifi drops out and no
  connection can be made until a restart. When I try to reconnect it
  "Connection Failed: Activation of network connection failed".  The
  Wifi works fine on phone and on Fedora 29.

  Network Manager 1.12.4

  Expected:

  Wifi stays connected

  Happened:

  Wifi drops out after 1-30 minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 13:38:42 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-02 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IpRoute:
   default via 192.168.42.129 dev enp0s20f0u2 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s20f0u2 scope link metric 1000 
   192.168.42.0/24 dev enp0s20f0u2 proto kernel scope link src 192.168.42.66 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION  CON-UUID  CON-PATH
   
   enp0s20f0u2  ethernet  connected
/org/freedesktop/NetworkManager/Devices/3  Wired connection 1  
a79e5d9a-26c0-34c5-a20d-5a371d0eafd6  
/org/freedesktop/NetworkManager/ActiveConnection/9 
   wlp1s0   wifi  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.12.4   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1801264/+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 1809438] Re: systemd-resolved segfaults

2019-01-01 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

-- 
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/1809438

Title:
  systemd-resolved segfaults

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I regularly (once almost every hour) get segfaults resported in
  systemd-resolved. The syslog is not always the same:

  Dec 21 06:59:21 marshall kernel: [988042.071003] systemd-resolve[15794]: 
segfault at e60e8ad514 ip 00e60e8ad514 sp 7ffe0376e748 error 14 in 
systemd-resolved[556f74bcf000+59000]
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 08:17:47 marshall kernel: [992748.334333] systemd-resolve[16943]: 
segfault at 2a11d9b0 ip 7f4810f5ad26 sp 7fff544db0f0 error 4 in 
libsystemd-shared-237.so[7f4810e1f000+1b5000]
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:22:45 marshall systemd-resolved[15727]: Assertion 'p->n_ref > 0' 
failed at ../src/resolve/resolved-dns-packet.c:210, function 
dns_packet_unref(). Aborting.
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:17:46 marshall systemd-resolved[15662]: Assertion 
'DNS_TRANSACTION_IS_LIVE(q->state)' failed at 
../src/resolve/resolved-dns-query.c:540, function dns_query_complete(). 
Aborting.
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  The system in question uses dnsmasq as local DNS server. Logging that is 
probably unrelated, but often seen (possibly due to the setup with dnsmasq) is:
  dec 21 10:22:00 marshall systemd-resolved[3183]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.
  dec 21 10:17:15 marshall systemd-resolved[3183]: Using degraded feature set 
(TCP) for DNS server 127.0.0.1.

  
  # dpkg --status systemd
  Package: systemd
  Installed-Size: 12444
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Multi-Arch: foreign
  Version: 237-3ubuntu10.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809438/+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 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs

2019-01-01 Thread fusillator 
hi again, not sure if the most sensible approach 
anyway in bionic I tried to revert the last two patches from the source of 
systemd_237-3ubuntu10.9.debian with the following commands:

export QUILT_PATCHES=debian/patches
export QUILT_REFRESH_ARGS="-p ab --no-timestamps --no-index"
quilt pop 
quilt pop 
sed 's/^CVE-2018-6954.*/#&/' debian/patches/series

Then I recompiled and installed the new package and the error disappear. 
Anyway the involved patches were there to fix some issues:

$ quilt header patches/CVE-2018-6954
Description: tmpfiles: don't resolve pathnames when traversing recursively
 through directory trees

 Otherwise we can be fooled if one path component is replaced underneath
us.

 The patch achieves that by always operating at file descriptor level (by using
 *at() helpers) and by making sure we do not any path resolution when traversing
 direcotry trees.

 However this is not always possible, for instance when listing the content of a
 directory or some operations don't provide the *at() helpers or others (such as
 fchmodat()) don't have the AT_EMPTY_PATH flag. In such cases we operate on
 /proc/self/fd/%i pseudo-symlink instead, which works the same for all kinds of
 objects and requires no checking of type beforehand.

 Also O_PATH flag is used when opening file objects in order to prevent
 undesired behaviors: device nodes from reacting, automounts from
 triggering, etc...

 Fixes: CVE-2018-6954

Origin: upstream, 
https://github.com/systemd/systemd/commit/936f6bdb803c432578e2cdcc5f93f3bfff93aff0
Bug: https://github.com/systemd/systemd/issues/7986

$ quilt header patches/CVE-2018-6954_2
Description: Make tmpfiles safe

 In addition to backporting the changesets in #8822, this also backports
 e04fc13 (test: add tests for systemd-tmpfiles), as well as empty_to_root()
 from v239.

Origin: upstream, https://github.com/systemd/systemd/pull/8822/commits
Bug: https://github.com/systemd/systemd/issues/7986

So I'm not sure if it's a secure/stable workaround
Maybe it would be better mixixing up the releases installing the patched 
package from cosmic-proposed... I will test on another snapshot to see what 
happens.. 
Just a curiosity: is bionic still supported?  

** Bug watch added: github.com/systemd/systemd/issues #7986
   https://github.com/systemd/systemd/issues/7986

-- 
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/1804603

Title:
  systemd-tmpfiles-setup.service fails on btrfs

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Confirmed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * Last security update introduced a regression on btrfs based systems, 
causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded 
machines.
   * Cherrypick upstream fixes to resolve this.

  [Test Case]

   * Install VM using btrfs for /
   * Boot, check that systemd-tmpfiles-setup.service is started successfully 
with:
  $ systemctl status systemd-tmpfiles-setup.service

  [Regression Potential]

   * btrfs fd doesn't support the set of flags that systemd used, with
  this patch, a compat set of flags is set instead, thus resolving the
  introduced regression. The worst case scenario is that creating
  subvolumes/directories is still broken (as in, the current status
  quo).

  [Other Info]
   
   * Example bad output

  
  After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails 
with:

  Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and 
Directories...
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/var": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/home": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/srv": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main 
process exited, code=exited, status=1/FAILURE
  Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed 
with result 'exit-code'.
  Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files 
and Directories.

  This happens on btrfs root filesystems in real hardware and on our
  virtualized servers as well. 237-3ubuntu10.6 didnt show this errors
  and going back to 237-3ubuntu10 removes them as well.

  # lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  # apt-cache policy systemd
  systemd:
    Installiert:   237-3ubuntu10.9
    Installationskandidat: 237-3ubuntu10.9
    Versionstabelle:
   *** 237-3ubuntu10.9 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
    

[Touch-packages] [Bug 1810214] [NEW] [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound at all

2019-01-01 Thread Oran Gol 
Public bug reported:

There is no sound whatsoever while the controls all seems to indicate
the playback is working. The patop's internal speaker, headphones, even
bluetooth is not outputting any sound. Trying to upgrade the kernel to
two different versions had no effect. There simply is no sound output
nor is there any indication the microphone is working either, but
without sound output that's hard to confirm. There are not issues with
sounds when I boot into Windows

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.19.13-041913-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mac1193 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan  1 14:18:09 2019
InstallationDate: Installed on 2018-12-30 (2 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mac1193 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX433FA.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX433FA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FA.204:bd09/19/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FA_UX433FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX433FA_UX433FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  There is no sound whatsoever while the controls all seems to indicate
  the playback is working. The patop's internal speaker, headphones,
  even bluetooth is not outputting any sound. Trying to upgrade the
  kernel to two different versions had no effect. There simply is no
  sound output nor is there any indication the microphone is working
  either, but without sound output that's hard to confirm. There are not
  issues with sounds when I boot into Windows

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.19.13-041913-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mac1193 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  1 14:18:09 2019
  InstallationDate: Installed on 2018-12-30 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mac1193 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook UX433FA_UX433FA, Realtek ALC294, Speaker, Internal] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FA.204:bd09/19/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FA_UX433FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook

[Touch-packages] [Bug 1810165] Re: Some black colors are shown in orange

2019-01-01 Thread Josy 
But what is strange is that even the laptops start window or the screen
shown when removing the boot hard disk from the laptop and starting the
laptop without boot hard disk shows an orange background. Thus this
might be a very strange hardware failure of the laptops graphics card.

** Attachment added: "Laptop screen photos made with camera without starting 
linux."
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1810165/+attachment/5226141/+files/Pictures2.zip

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

Title:
  Some black colors are shown in orange

Status in xorg package in Ubuntu:
  New

Bug description:
  During booting the usually black screen background is shown orange
  instead of black, the text is not readable and when the Laptop is
  running some pictures show black colour sections in orange colour.

  lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu8
Candidate: 1:7.7+19ubuntu8
Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 31 17:33:11 2018
  DistUpgraded: 2018-10-30 13:42:44,629 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.18.0-13-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780M [Mobility Radeon HD 3200] 
[1002:9612] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RS780M [Mobility Radeon HD 3200] 
[103c:30e4]
  InstallationDate: Installed on 2016-12-24 (736 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP Compaq 6735s
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=27521009-c2c8-4fb5-97ee-c05ae44cfcd0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-10-30 (62 days ago)
  dmi.bios.date: 10/02/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68GPP Ver. F.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30E4
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 94.1C
  dmi.chassis.asset.tag: CNU842079D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68GPPVer.F.06:bd10/02/2008:svnHewlett-Packard:pnHPCompaq6735s:pvrF.06:rvnHewlett-Packard:rn30E4:rvrKBCVersion94.1C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6735s
  dmi.product.sku: NA777ES#ABD
  dmi.product.version: F.06
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1810165/+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 1810165] Re: Some black colors are shown in orange

2019-01-01 Thread Josy 
This is the way the Linux debug output looks like. See attachment.

** Attachment added: "Linux debug output"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1810165/+attachment/5226133/+files/20190101_192329.jpg

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

Title:
  Some black colors are shown in orange

Status in xorg package in Ubuntu:
  New

Bug description:
  During booting the usually black screen background is shown orange
  instead of black, the text is not readable and when the Laptop is
  running some pictures show black colour sections in orange colour.

  lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu8
Candidate: 1:7.7+19ubuntu8
Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 31 17:33:11 2018
  DistUpgraded: 2018-10-30 13:42:44,629 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.18.0-13-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780M [Mobility Radeon HD 3200] 
[1002:9612] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RS780M [Mobility Radeon HD 3200] 
[103c:30e4]
  InstallationDate: Installed on 2016-12-24 (736 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP Compaq 6735s
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=27521009-c2c8-4fb5-97ee-c05ae44cfcd0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-10-30 (62 days ago)
  dmi.bios.date: 10/02/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68GPP Ver. F.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30E4
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 94.1C
  dmi.chassis.asset.tag: CNU842079D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68GPPVer.F.06:bd10/02/2008:svnHewlett-Packard:pnHPCompaq6735s:pvrF.06:rvnHewlett-Packard:rn30E4:rvrKBCVersion94.1C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6735s
  dmi.product.sku: NA777ES#ABD
  dmi.product.version: F.06
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1810165/+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 1774029] Re: Unable to boot after upgrade to 18.04 (only works with 16.04 kernel)

2019-01-01 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

-- 
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/1774029

Title:
  Unable to boot after upgrade to 18.04 (only works with 16.04 kernel)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from 16.04 my ASUS X201E laptop to 18.04, but now I can only boot 
with the 16.04 kernel (4.4.0.x), I can't seem to boot with the 4.15 kernel (I 
tried 4.14 & 4.16 as well, to no avail).
  Booting with the 4.4 kernel leads to the login screen and everything works 
OK, while booting with the 4.15 kernel remains stalled on the Ubuntu startup 
screen with dots, ESC shows traces stuck? on "Reached target Network is Online"
  I can successfully boot the 18.04 desktop image though, so I am assuming the 
issue comes from configuration files and not from the kernel itself. Any help 
would be highly appreciated !

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Tue May 29 19:05:08 2018
  InstallationDate: Installed on 2014-11-19 (1286 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2018-05-22 20:51:41.459776
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774029/+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 1807627] Re: package systemd 237-3ubuntu10.9 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1

2019-01-01 Thread h1repp 
it is the post-installation script that always returns 1, after throwing
errors about unsafe symlinks encountered in /var/log/journal/. but there
are no symlinks at all. Seems it is the systemd-tmpfiles --create call
that throws this errors.

Unfortunately this leavea you with an inconsistent system in the middle
of an release upgrade and no way out of this mess. So please set the
importance to severe!

Btw, my system was a fully updated 16.04 with hwe/i386 that is now
broken an the half way to 18.04.

-- 
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/1807627

Title:
  package systemd 237-3ubuntu10.9 failed to install/upgrade: installed
  systemd package post-installation script subprocess returned error
  exit status 1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  during upgrade from 16.04 to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.9
  ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
  Uname: Linux 4.4.0-140-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sun Dec  9 17:11:50 2018
  ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2016-09-01 (829 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic 
root=UUID=aa4fc23f-9987-40c4-8278-a702ff0b99a3 ro
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.2.29
  SourcePackage: systemd
  Title: package systemd 237-3ubuntu10.9 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-12-10 (0 days ago)
  dmi.bios.date: 06/20/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.21
  dmi.board.asset.tag: 2UA142177C
  dmi.board.name: 1495
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA142177C
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.21:bd06/20/2012:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq 8200 Elite SFF PC
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1807627/+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 1807627] Re: package systemd 237-3ubuntu10.9 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1

2019-01-01 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

-- 
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/1807627

Title:
  package systemd 237-3ubuntu10.9 failed to install/upgrade: installed
  systemd package post-installation script subprocess returned error
  exit status 1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  during upgrade from 16.04 to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.9
  ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
  Uname: Linux 4.4.0-140-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sun Dec  9 17:11:50 2018
  ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2016-09-01 (829 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic 
root=UUID=aa4fc23f-9987-40c4-8278-a702ff0b99a3 ro
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.2.29
  SourcePackage: systemd
  Title: package systemd 237-3ubuntu10.9 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-12-10 (0 days ago)
  dmi.bios.date: 06/20/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.21
  dmi.board.asset.tag: 2UA142177C
  dmi.board.name: 1495
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA142177C
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.21:bd06/20/2012:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq 8200 Elite SFF PC
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1807627/+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 1791166] Re: Programs using the libqt5gui5 library do not start.

2019-01-01 Thread aroon 
Hello.
The problem is probably the files with the settings of packages in the home 
directory.
You have to uninstall the package with settings, look for files in this package 
in the home directory (partially hidden) and remove them or move them for 
security.
Should help.

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

Title:
  Programs using the libqt5gui5 library do not start.

Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Programs using the libqt5gui5 library do not start.
  Running in the terminal displays the message:
  "VirtualBox: supR3HardenedMainGetTrustedMain: 
dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: libQt5Gui.so.5: cannot 
open shared object file: No such file or directory"
  or
  "smplayer: error while loading shared libraries: libQt5Widgets.so.5: cannot 
open shared object file: No such file or directory"
  My distribution is Ubuntu 18.04.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1791166/+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 1791166] Re: Programs using the libqt5gui5 library do not start.

2019-01-01 Thread Antonio Aguillon 
btw, my problem is with SMPLAYER. Thanks

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

Title:
  Programs using the libqt5gui5 library do not start.

Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Programs using the libqt5gui5 library do not start.
  Running in the terminal displays the message:
  "VirtualBox: supR3HardenedMainGetTrustedMain: 
dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: libQt5Gui.so.5: cannot 
open shared object file: No such file or directory"
  or
  "smplayer: error while loading shared libraries: libQt5Widgets.so.5: cannot 
open shared object file: No such file or directory"
  My distribution is Ubuntu 18.04.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1791166/+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 1791166] Re: Programs using the libqt5gui5 library do not start.

2019-01-01 Thread Antonio Aguillon 
$ apt-cache policy libqt5gui5 libqt5widgets5 virtualbox-qt smplayer
libqt5gui5:
  Instalados: 5.9.5+dfsg-0ubuntu1
  Candidato:  5.9.5+dfsg-0ubuntu1
  Tabla de versión:
 *** 5.9.5+dfsg-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
libqt5widgets5:
  Instalados: 5.9.5+dfsg-0ubuntu1
  Candidato:  5.9.5+dfsg-0ubuntu1
  Tabla de versión:
 *** 5.9.5+dfsg-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
virtualbox-qt:
  Instalados: (ninguno)
  Candidato:  5.2.18-dfsg-2~ubuntu18.04.1
  Tabla de versión:
 5.2.18-dfsg-2~ubuntu18.04.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 
Packages
 5.2.10-dfsg-6 500
500 http://us.archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages
smplayer:
  Instalados: 18.2.2~ds0-1
  Candidato:  18.2.2~ds0-1
  Tabla de versión:
 *** 18.2.2~ds0-1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  Programs using the libqt5gui5 library do not start.

Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Programs using the libqt5gui5 library do not start.
  Running in the terminal displays the message:
  "VirtualBox: supR3HardenedMainGetTrustedMain: 
dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: libQt5Gui.so.5: cannot 
open shared object file: No such file or directory"
  or
  "smplayer: error while loading shared libraries: libQt5Widgets.so.5: cannot 
open shared object file: No such file or directory"
  My distribution is Ubuntu 18.04.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1791166/+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 1791166] Re: Programs using the libqt5gui5 library do not start.

2019-01-01 Thread Antonio Aguillon 
I have the same problem right now. I've been reinstalling both the
package and the library and nothing is solved.

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

Title:
  Programs using the libqt5gui5 library do not start.

Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Programs using the libqt5gui5 library do not start.
  Running in the terminal displays the message:
  "VirtualBox: supR3HardenedMainGetTrustedMain: 
dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: libQt5Gui.so.5: cannot 
open shared object file: No such file or directory"
  or
  "smplayer: error while loading shared libraries: libQt5Widgets.so.5: cannot 
open shared object file: No such file or directory"
  My distribution is Ubuntu 18.04.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1791166/+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 1810195] Re: package libudev1:i386 237-3ubuntu10.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio

2019-01-01 Thread Apport retracing service 
** Tags removed: need-duplicate-check

-- 
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/1810195

Title:
  package libudev1:i386 237-3ubuntu10.9 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in systemd package in Ubuntu:
  New

Bug description:
  I can't update the system

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libudev1:i386 237-3ubuntu10.9
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   linux-image-extra-4.4.0-138-generic:amd64: Remove
   linux-image-4.4.0-138-generic:amd64: Remove
   tzdata:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Jan  1 14:00:48 2019
  Dependencies:
   gcc-8-base 8.2.0-1ubuntu2~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.2.0-1ubuntu2~18.04
  DpkgHistoryLog:
   Start-Date: 2019-01-01  13:59:54
   Commandline: aptdaemon role='role-commit-packages' sender=':1.121'
   Upgrade: tzdata:amd64 (2018g-0ubuntu0.18.04, 2018i-0ubuntu0.18.04)
   Remove: linux-image-4.4.0-138-generic:amd64 (4.4.0-138.164), 
linux-image-extra-4.4.0-138-generic:amd64 (4.4.0-138.164)
  DuplicateSignature:
   package:libudev1:i386:237-3ubuntu10.9
   Unpacking tzdata (2018i-0ubuntu0.18.04) over (2018g-0ubuntu0.18.04) ...
   dpkg: error processing package libudev1:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-02-16 (1779 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: systemd
  Title: package libudev1:i386 237-3ubuntu10.9 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to bionic on 2018-10-28 (65 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810195/+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 1810195] [NEW] package libudev1:i386 237-3ubuntu10.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat

2019-01-01 Thread s 
Public bug reported:

I can't update the system

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libudev1:i386 237-3ubuntu10.9
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
 linux-image-extra-4.4.0-138-generic:amd64: Remove
 linux-image-4.4.0-138-generic:amd64: Remove
 tzdata:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Jan  1 14:00:48 2019
Dependencies:
 gcc-8-base 8.2.0-1ubuntu2~18.04
 libc6 2.27-3ubuntu1
 libgcc1 1:8.2.0-1ubuntu2~18.04
DpkgHistoryLog:
 Start-Date: 2019-01-01  13:59:54
 Commandline: aptdaemon role='role-commit-packages' sender=':1.121'
 Upgrade: tzdata:amd64 (2018g-0ubuntu0.18.04, 2018i-0ubuntu0.18.04)
 Remove: linux-image-4.4.0-138-generic:amd64 (4.4.0-138.164), 
linux-image-extra-4.4.0-138-generic:amd64 (4.4.0-138.164)
DuplicateSignature:
 package:libudev1:i386:237-3ubuntu10.9
 Unpacking tzdata (2018i-0ubuntu0.18.04) over (2018g-0ubuntu0.18.04) ...
 dpkg: error processing package libudev1:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2014-02-16 (1779 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
PackageArchitecture: i386
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: systemd
Title: package libudev1:i386 237-3ubuntu10.9 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: Upgraded to bionic on 2018-10-28 (65 days ago)

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


** Tags: apport-package bionic i386

-- 
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/1810195

Title:
  package libudev1:i386 237-3ubuntu10.9 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in systemd package in Ubuntu:
  New

Bug description:
  I can't update the system

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libudev1:i386 237-3ubuntu10.9
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   linux-image-extra-4.4.0-138-generic:amd64: Remove
   linux-image-4.4.0-138-generic:amd64: Remove
   tzdata:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Jan  1 14:00:48 2019
  Dependencies:
   gcc-8-base 8.2.0-1ubuntu2~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.2.0-1ubuntu2~18.04
  DpkgHistoryLog:
   Start-Date: 2019-01-01  13:59:54
   Commandline: aptdaemon role='role-commit-packages' sender=':1.121'
   Upgrade: tzdata:amd64 (2018g-0ubuntu0.18.04, 2018i-0ubuntu0.18.04)
   Remove: linux-image-4.4.0-138-generic:amd64 (4.4.0-138.164), 
linux-image-extra-4.4.0-138-generic:amd64 (4.4.0-138.164)
  DuplicateSignature:
   package:libudev1:i386:237-3ubuntu10.9
   Unpacking tzdata (2018i-0ubuntu0.18.04) over (2018g-0ubuntu0.18.04) ...
   dpkg: error processing package libudev1:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-02-16 (1779 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: systemd
  Title: package libudev1:i386 237-3ubuntu10.9 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to bionic on 2018-10-28 (65 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810195/+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 1605750] Re: package udev 229-4ubuntu7 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2019-01-01 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

-- 
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/1605750

Title:
  package udev 229-4ubuntu7 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript gab den Fehlerwert 1 zurück

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  update via synaptic today (22.07.2016) resulted in error message (see
  summary)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CustomUdevRuleFiles: 99_smfpautoconf_samsung.rules 
98_smfpautoconf_samsung.rules
  Date: Fri Jul 22 21:25:58 2016
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationDate: Installed on 2016-07-15 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 3259MAG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=d7f1b4dd-fcc8-44f8-b89a-3e2275279c3b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package udev 229-4ubuntu7 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H0ET74WW (2.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3259MAG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH0ET74WW(2.08):bd11/14/2012:svnLENOVO:pn3259MAG:pvrThinkPadEdgeE530:rvnLENOVO:rn3259MAG:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3259MAG
  dmi.product.version: ThinkPad Edge E530
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1605750/+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 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files

2019-01-01 Thread Jarno Suni 
cwdruf, luckily, there are some ways.

-- 
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/798414

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space--or provide an automatic tool for
  removal of old files

Status in initramfs-tools:
  New
Status in Ubuntu Software Center:
  Invalid
Status in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files

2019-01-01 Thread BlaWhickte 
** Changed in: initramfs-tools (Ubuntu)
 Assignee: Julio Decima (j10a) => BlaWhickte (blawhickte)

-- 
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/798414

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space--or provide an automatic tool for
  removal of old files

Status in initramfs-tools:
  New
Status in Ubuntu Software Center:
  Invalid
Status in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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