[Touch-packages] [Bug 1383184] Business Opportunity

2024-04-17 Thread Kamatera Support
-- 
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/1383184

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Status in HWE Next:
  Fix Released
Status in HWE Next wily series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Fix Released
Status in linux-firmware source package in Wily:
  Fix Released

Bug description:
  =

  CURRENT STATUS:

  Wily(15.10) could not work with and don't need Adam's dkms package 1.0
  or 1.1

  Wily(15.10) has already fixed the driver part, and the firmware part
  is in progress.

  For now, you guys could use 15.10(purge the ath10k-dkms if you tried
  installing it), and make a copy of
  https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/

  15.10 will work in a week by a simple `apt upgrade`

  Distros before 15.10(lower than 4.2 kernel) please keep using the
  dkms(which will be relocated soon)

  =

  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  ---
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.

   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

  Qualcomm Atheros Device [168c:003e] (rev 20)

  mainline commit d63955b33b3bee45d784ffdfafeb93076c765660

  [6.221281] ath10k_pci :02:00.0: pci irq msi interrupts 1 irq_mode 0 
reset_mode 0
  [6.417386] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [6.417404] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2
  [6.417407] ath10k_pci :02:00.0: failed to load spec board file, 
falling back to generic: -2
  [6.417416] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board.bin failed with error -2
  [6.417418] ath10k_pci :02:00.0: failed to fetch generic board data: -2
  [6.417420] ath10k_pci :02:00.0: failed to fetch board file: -2
  [6.417421] ath10k_pci :02:00.0: could not fetch firmware files (-2)
  [6.417423] ath10k_pci :02:00.0: could not probe fw (-2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1383184/+subscriptions


-- 
Mailing list: https://launchpad.

[Touch-packages] [Bug 1207812] Business Opportunity

2024-04-17 Thread Kamatera Support
-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs/1207812

Title:
  [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt
  Looping

Status in Linux Mint:
  Fix Released
Status in libimobiledevice package in Ubuntu:
  Fix Released
Status in libimobiledevice package in Debian:
  Fix Released

Bug description:
  The latest libimobiledevice release 1.1.5 is a year old and does not
  support iOS7 devices. Most iOS devices have been updated to iOS7 by
  now, so currently the library is broken in functionality for most
  users. The git snapshot has been tested to work, but there seems to be
  no new upstream release being prepared for the time being.

  The new git snapshot includes several fixes, including the security
  fix that was previously patched on top of 1.1.5 in Ubuntu.

  Packaging branch merge request attached to this bug report.

  --- Original report ---

  The iPhone reporting "Trust the currently connected computer?" Trust/Don't 
Trust.
  This then happens in a continous loop when clicking Trust.

  ---
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nrawlins   2068 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb
  InstallationDate: Installed on 2013-08-15 (3 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Sony Corporation VGN-SR29XN_S
  MarkForUpload: True
  Package: linux 3.8.0.27.45
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/28/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1130Y1
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-SR29XN_S
  dmi.product.version: C6017UKK
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1207812/+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 1207812] Enquiry-Please attend to this.

2024-04-15 Thread Kamatera Support
-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs/1207812

Title:
  [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt
  Looping

Status in Linux Mint:
  Fix Released
Status in libimobiledevice package in Ubuntu:
  Fix Released
Status in libimobiledevice package in Debian:
  Fix Released

Bug description:
  The latest libimobiledevice release 1.1.5 is a year old and does not
  support iOS7 devices. Most iOS devices have been updated to iOS7 by
  now, so currently the library is broken in functionality for most
  users. The git snapshot has been tested to work, but there seems to be
  no new upstream release being prepared for the time being.

  The new git snapshot includes several fixes, including the security
  fix that was previously patched on top of 1.1.5 in Ubuntu.

  Packaging branch merge request attached to this bug report.

  --- Original report ---

  The iPhone reporting "Trust the currently connected computer?" Trust/Don't 
Trust.
  This then happens in a continous loop when clicking Trust.

  ---
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nrawlins   2068 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb
  InstallationDate: Installed on 2013-08-15 (3 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Sony Corporation VGN-SR29XN_S
  MarkForUpload: True
  Package: linux 3.8.0.27.45
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/28/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1130Y1
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-SR29XN_S
  dmi.product.version: C6017UKK
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1207812/+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 1638395] Re: Unable to locate remote printer when printing

2019-01-07 Thread Brother Printer Support
Hi We are brother printer technical support provider who provide best
Brother Printer Customer Service For Usa brother Printer customer. Dial
1800-436-0509 to help or Visit>> https://www.printertollfreenumber.com
/brother-printer-support

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

Title:
  Unable to locate remote printer when printing

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  My printer (EPSON Stylus Photo RX520) is connected to a  Yakkety station 
called "paris" which is the printing server. 
  Printing is fine from the server.

  When i configure another Yakkety station to print via this server, the 
printer is detected OK via dnssd, the driver is installed OK. But i can't 
print. 
  I get the following message "Unable to locate printer "paris.local"."

  I used to work on xenial but the connection was through ipps. I tried
  to configure the connection as in xenial, to no avail ...

  What i did: 
  add "192.168.1.4 paris.local" in /etc/hosts
  remove printer from cups, reinstalled it and i finally was able to print on 
the remote printer!

  Don't know if this problem is related to cups or avahi ...

  Ubuntu 16.10
  cups 2.2.0-2

  What i expected to happen: printing successful
  What happened: client cannot locate remote printer, add to add a line in 
/etc/hosts to make it work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1638395/+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


Re: [Touch-packages] [Bug 1699360] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-08-31 Thread Support
Unfortunately not.

Mit freundlichen Grüßen

Erics Computerlädchen
Eric Lehnen
Tel +49 6103 9886688
Fax +49 6103 3721612
email: i...@erics-computerlaedchen.de
Webseite: www.erics-computerlaedchen.de

Am 31.08.2017 um 00:26 schrieb Robert Ancell:
> Did the problem resolve after updating to zesty-proposed?
>
> ** Changed in: gnome-software (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Changed in: gnome-software (Ubuntu)
> Importance: Undecided => Medium
>

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

Title:
  package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in debconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Incomplete
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  this all

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libpam-systemd:amd64 232-21ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jun 21 00:45:00 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-19 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1699360/+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 1700344] [NEW] package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-06-25 Thread Support
*** This bug is a duplicate of bug 1699360 ***
https://bugs.launchpad.net/bugs/1699360

Public bug reported:

Failure appeared during installing the bluegriffon software on Ubuntu
17.04

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libpam-systemd:amd64 232-21ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Sun Jun 25 11:37:24 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-04-15 (70 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: systemd
Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in systemd package in Ubuntu:
  New

Bug description:
  Failure appeared during installing the bluegriffon software on Ubuntu
  17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libpam-systemd:amd64 232-21ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sun Jun 25 11:37:24 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-04-15 (70 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1700344/+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 1691961] Re: Ubuntu 16.04 freezes

2017-05-19 Thread inhouse-support
** Package changed: alsa-driver (Ubuntu) => ubuntu

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

Title:
  Ubuntu 16.04 freezes

Status in Ubuntu:
  New

Bug description:
  I've two machines with a
  Asus Z170M-PLUS
  Core i5 6600
  Samsung SSD 850 Pro 

  Both systems suffer from the same problem:

  Installation works fine. After having the system idling around for a while 
the system freezes or behaves strange. It looks like as if the SSD becomes 
inaccessible.
  I had cases where the whole GUI was frozen or situations where the terminal 
showed "I/O errors".

  I also tried different SSD (Samsung SSD pro with 256GB and 512GB) and
  updated the BIOS on one of the systems.

  Problem happens with stock Ubuntu 16.04 LTS install.

  Attached is a syslog from the rare cases where the system is able to
  somehow operate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1691961/+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 1691961] [NEW] Ubuntu 16.04 freezes

2017-05-19 Thread inhouse-support
Public bug reported:

I've two machines with a
Asus Z170M-PLUS
Core i5 6600
Samsung SSD 850 Pro 

Both systems suffer from the same problem:

Installation works fine. After having the system idling around for a while the 
system freezes or behaves strange. It looks like as if the SSD becomes 
inaccessible.
I had cases where the whole GUI was frozen or situations where the terminal 
showed "I/O errors".

I also tried different SSD (Samsung SSD pro with 256GB and 512GB) and
updated the BIOS on one of the systems.

Problem happens with stock Ubuntu 16.04 LTS install.

Attached is a syslog from the rare cases where the system is able to
somehow operate.

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

** Attachment added: "culd-test02-syslog.txt.gz"
   
https://bugs.launchpad.net/bugs/1691961/+attachment/4879409/+files/culd-test02-syslog.txt.gz

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

Title:
  Ubuntu 16.04 freezes

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've two machines with a
  Asus Z170M-PLUS
  Core i5 6600
  Samsung SSD 850 Pro 

  Both systems suffer from the same problem:

  Installation works fine. After having the system idling around for a while 
the system freezes or behaves strange. It looks like as if the SSD becomes 
inaccessible.
  I had cases where the whole GUI was frozen or situations where the terminal 
showed "I/O errors".

  I also tried different SSD (Samsung SSD pro with 256GB and 512GB) and
  updated the BIOS on one of the systems.

  Problem happens with stock Ubuntu 16.04 LTS install.

  Attached is a syslog from the rare cases where the system is able to
  somehow operate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1691961/+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


Re: [Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

2017-05-05 Thread PcB Computer Support
give more space for /boot 1gb ?

PcB-iPhone Communication

Am 05.05.2017 um 13:09 schrieb Bill Meier <798...@bugs.launchpad.net>:

Why not just write a little GUI app for us , so that we "command line 
illiterates" can take  care of this. We need to select what we want 
deleted, just getting rid of the old, I understand, may not be what is 
wanted.


Bill


> On 05/05/2017 03:13 AM, Michael Baker wrote:
> On booting I am told that a system program has encountered an error and asked 
> if I want to send a report. On saying yes I'm told that the bug has already 
> been reported and that it is "update-initramfs should produce a more helpful 
> error when there isn't enough free space".
> This is so far from what is happening that it is infuriating.
> The basis of the problem is that /boot is not being cleaned up automatically.
> This was a bug which was supposedly fixed in 16.04 UTS, but apparently not.
> As a retired software engineer I know that I can clean up /boot manually, and 
> have done so many times.
> However I shouldn't have to.
> Please stop classifying the /boot partition being full as "update-initramfs 
> should produce a more helpful error when there isn't enough free space".
> This bug (/boot not being cleaned up automatically) should be given the 
> highest possible importance.
> It must be a complete turn of to any ubuntu user who does not have computer 
> science skills (and to many who do).

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

Title:
 update-initramfs should produce a more helpful error when there isn't
 enough  free space

Status in initramfs-tools:
 Confirmed
Status in Software Updater:
 New
Status in dpkg package in Ubuntu:
 Invalid
Status in initramfs-tools package in Ubuntu:
 In Progress

Bug description:
 Binary package hint: initramfs-tools

 When generating a new initramfs there is no check for available free
 space, subsequently its possible for update-initramfs to fail due to a
 lack of free space.  This is resulting in package installation
 failures for initramfs-tools.  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

 WORKAROUND:

 Remove unused kernels using computer janitor (not in repositories for
 14.04 or later) or manually free space on your partition containing
 the /boot file system.

 See instructions here
 https://help.ubuntu.com/community/RemoveOldKernels

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

-- 
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 when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in Software Updater:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  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

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions 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 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

2016-07-19 Thread HP Printer Technical Support
Any printer installation is the problems you confront allow the
professional to take a step ahead to fix the driver, install it well and
ensure that it is compatible with your computer software and works well.
The specialist guide you well how to make over it well. To get quotes
for your queries dial toll free number 1-888-924-5460 now OR Visit your
website for more details : https://www.vfix365.us/hp

** Also affects: lsb
   Importance: Undecided
   Status: New

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud <o...@debian.org>  Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

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