date:20181003

Dropped severity.

While there are no updates to snapd newer than your ISO, this bug won't
occur at all. Also there is a simple workaround documented at the top.
And alternative workarounds are possible too.

** Changed in: snapd (Ubuntu)
   Importance: Critical => High

** Summary changed:

- snapd on cosmic never finishes installing/updating. Can't install any other 
updates.
+ snapd updates on cosmic never finish installing. Can't install any other 
updates.

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

Title:
  snapd updates on cosmic never finish installing. Can't install any
  other updates.

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1776622/+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 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop

@jibel, as a workaround can you please test if switching VTs kicks the
machine into action? Just Alt+F2, Alt+F1, and maybe then the login
screen will appear. If that works for you then maybe we can declare bug
1795637 a duplicate of this one.

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

Title:
  gdm doesn't start on a fresh installation of Cosmic Desktop

Status in gdm3 package in Ubuntu:
  Won't Fix
Status in kmod package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed
Status in gdm3 source package in Cosmic:
  Won't Fix
Status in kmod source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in xorg-server source package in Cosmic:
  Confirmed

Bug description:
  ubuntu cosmic desktop 20180925

  After installation gdm fails to start and there is only a black screen
  with a blinking cursor on the top left of the screen.

  gdm3 can be started manually from a tty

  When this issue happens there is a plymouth crash reported in bug
  1794292


  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Tue Sep 25 13:54:45 2018
  InstallationDate: Installed on 2018-09-25 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+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 1720693] Re: [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at all

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  There is no sound from the front jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D2', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/by-path', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sun Oct  1 17:49:29 2017
  InstallationDate: Installed on 2017-06-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', 
'/dev/snd/by-path', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Symptom_amixerStderr: a m i x e r :   M i x e r   h w : P C H   l o a d   e r 
r o r :   I n v a l i d   a r g u m e n t
  Title: [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M1AKT17A
  dmi.board.name: 310B
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259612472445
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM1AKT17A:bd04/13/2017:svnLENOVO:pn10MVCTO1WW:pvrThinkCentreM910q:rvnLENOVO:rn310B:rvrSDK0J40709WIN3259612472445:cvnLENOVO:ct3:cvrNone:
  dmi.product.name: 10MVCTO1WW
  dmi.product.version: ThinkCentre M910q
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1720693/+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 455734] Re: Cups prompts for authorization on a network printer even though it is not required

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Cups prompts for authorization on a network printer even though it is
  not required

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  Description:  Ubuntu karmic (development branch)
  Release:  9.10

  cups:
Installed: 1.4.1-5ubuntu2
Candidate: 1.4.1-5ubuntu2
Version table:
   *** 1.4.1-5ubuntu2 0
  500 http://ftp.usf.edu karmic/main Packages
  100 /var/lib/dpkg/status

  What I expected to happen:  Printing to a network printer without being asked 
for authorization
  What actually happened: Authorization was requested when trying to print to 
the network printer

  The printer in question is on a Windows XP machine and is accessed
  through a Samba share.

  Steps to reproduce:

  1. Install a Samba shared printer that does not require authorization by 
going to System->Administration->Printing
  2. On the wizard screen under Authorization leave the default setting, 
"Prompt user if authentication is required"
  3. Print and be prompted for authorization

  Details:

  I get asked for authorization with every print.  I can leave the
  password blank or put anything at all in the username and password
  fields and the document will print.  It shows up as "Guest" user on
  the XP machine.

  Workaround:

  I tried changing the setting for the authorization to guest with no
  password but the change did not persist.  This seems to be another bug
  which I will file separately.  I got rid of the prompt by deleting and
  recreating the printer and setting the username to "guest" and leaving
  the password blank under authorization.

  ProblemType: Bug
  Architecture: i386
  Date: Mon Oct 19 13:07:47 2009
  DistroRelease: Ubuntu 9.10
  Lpstat: device for HP-Deskjet-d1500: smb://SHARING/ATEC0/HPDeskje
  MachineType: LENOVO 2613CTO
  NonfreeKernelModules: slamr
  Package: cups 1.4.1-5ubuntu2
  Papersize: letter
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  PpdFiles: HP-Deskjet-d1500: HP Deskjet d1500 Series hpijs, 3.9.8
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic 
root=UUID=8c74d8a1-9b66-4b02-a171-842c754ea8ad ro quiet splash
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: cups
  Uname: Linux 2.6.31-14-generic i686
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE3WW (2.23 )
  dmi.board.name: 2613CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn2613CTO:pvrThinkPadT60:rvnLENOVO:rn2613CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2613CTO
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/455734/+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 473899] Re: OpenOffice Writer paragraph alignment wrong

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  OpenOffice Writer paragraph alignment wrong

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: openoffice.org

  if I change page preferences (e.g. lenght to 10,00 cm) then a left
  aligned paragraph will be centered

  ProblemType: Bug
  Architecture: amd64
  CheckboxSubmission: 2fd728019e04834938da25a1f45bdb30
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Wed Nov  4 09:32:48 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: ath_hal nvidia
  Package: openoffice.org-core 1:3.1.1-5ubuntu1
  ProcEnviron:
   LANGUAGE=de_DE.UTF-8
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: openoffice.org
  Uname: Linux 2.6.31-14-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/473899/+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 456181] Re: cyrillic glyph 'Й' skipped in printed documents

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  cyrillic glyph 'Й' skipped in printed documents

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  Description:  Ubuntu karmic (development branch)
  Release:  9.10

  When printng documents from OpenOffice.Org (or any other application
  with rich text) text contains cyrillic 'Й' (I KRATKOE CAPITAL) prints
  without that symbol.

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: 1afde1366a7b1795bb99068a39ded88f
  CheckboxSystem: 2ac50da664fc513894ca7032810c84ee
  Date: Tue Oct 20 18:52:25 2009
  DistroRelease: Ubuntu 9.10
  Lpstat: device for SCX4200: ipp://192.168.0.2:631/printers/SCX-4200
  MachineType: TOSHIBA Satellite L40
  Package: cups 1.4.1-5ubuntu2
  Papersize: a4
  PpdFiles: SCX4200: Samsung SCX-4200 Series
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-386 
root=UUID=7fd6e07c-a55e-4585-9ce3-80b38ace25c8 ro quiet splash security=selinux 
selinux=1
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.47-386
  SourcePackage: cups
  UdevDb: Error: [Errno 2] No such file or directory
  Uname: Linux 2.6.31-14-386 i686
  dmi.bios.date: 09/19/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.60
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Satellite L40
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.60:bd09/19/2007:svnTOSHIBA:pnSatelliteL40:pvr:rvnTOSHIBA:rnSatelliteL40:rvr1.0:cvnTOSHIBA:ct10:cvr:
  dmi.product.name: Satellite L40
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/456181/+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 466258] Re: Brother HL-1430 USB printer will only print once

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Brother HL-1430 USB printer will only print once

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  This is kind of a followup of bug #57050, but launchpad didn't give me the 
option to continue on this bug. so here is a new one.
  I'm on Ubuntu Karmic 64bit. My usb printer brother HL-1430 is installed 
automatically after plugin, but I followed several guidelines and installed the 
package brother-cups-wrapper-laser1 and choose the new ppd from 
/usr/share/ppd/Brother/brhl1430_cups.ppd in printer config.
  But still I have the problem: I can only print once. Sometimes it helps to 
just unplug and plugin again. Sometimes I have to power down the printer, 
sometimes I do a /etc/init.d/cups.d restart - sometimes only everything 
together helps.

  ProblemType: Bug
  Architecture: amd64
  CheckboxSubmission: 968105946532eaaa78880cfbbb811d4f
  CheckboxSystem: e704f33cc0866ff0f0256a33de39ea1c
  Date: Sat Oct 31 10:03:04 2009
  DistroRelease: Ubuntu 9.10
  Lpstat: device for HL-1430-series: usb://Brother/HL-1430%20series
  MachineType: Hewlett-Packard HP Pavilion tx2500 Notebook PC
  NonfreeKernelModules: wl
  Package: cups 1.4.1-5ubuntu2
  Papersize: a4
  PpdFiles: HL-1430-series: Brother HL-1430 for CUPS
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic 
root=UUID=d1e5bdc4-a9cf-4d9d-8f25-86e32491f2ca ro quiet
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: cups
  Tags:  ubuntu-unr
  Uname: Linux 2.6.31-14-generic x86_64
  XsessionErrors:
   (gnome-settings-daemon:1917): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (nautilus:1950): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (polkit-gnome-authentication-agent-1:1980): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (gnome-panel:1945): Gdk-CRITICAL **: gdk_x11_colormap_foreign_new: assertion 
`GDK_IS_VISUAL (visual)' failed
   (nautilus:3811): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
  dmi.bios.date: 09/23/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30F1
  dmi.board.vendor: Quanta
  dmi.board.version: 97.19
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd09/23/2008:svnHewlett-Packard:pnHPPaviliontx2500NotebookPC:pvrRev1:rvnQuanta:rn30F1:rvr97.19:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion tx2500 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/466258/+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 479221] Re: Evolution printed e-mails can't be printed

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Evolution printed e-mails can't be printed

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: evolution

  When I attempt to print through cups, the printed e-mails come out as
  a type of dump and not the actual e-mail.  Do I need to download some
  fonts, possibly?

  ProblemType: Bug
  Architecture: i386
  Date: Mon Nov  9 07:12:33 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/evolution
  Package: evolution 2.28.1-0ubuntu1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: evolution
  Uname: Linux 2.6.31-14-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/479221/+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 471650] Re: system-config-printer can't find dbus module

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  system-config-printer can't find dbus module

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  Using the menus Admin/Printing  hangs for a bit, then 
  just dies silently.  running from the command line:

  > rik@monk:~$ system-config-printer
  > Traceback (most recent call last):
  >   File "/usr/share/system-config-printer/system-config-printer.py", line 
30, in ?
  > import dbus
  > ImportError: No module named dbus

  i tried to manually check to see what sys.path is available, but
  don't really know what system-config-printer requires?

  rik@monk:~$ /usr/bin/env python
  Python 2.4.4 (#1, Nov  8 2008, 19:16:01) 
  [GCC 4.3.2] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import dbus
  Traceback (most recent call last):
File "", line 1, in ?
  ImportError: No module named dbus
  >>> import sys
  >>> sys.path
  ['', '/usr/local/lib/python24.zip', '/usr/local/lib/python2.4', 
'/usr/local/lib/python2.4/plat-linux2', '/usr/local/lib/python2.4/lib-tk', 
'/usr/local/lib/python2.4/lib-dynload', 
'/usr/local/lib/python2.4/site-packages', 
'/usr/local/lib/python2.4/site-packages/PIL']

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  MachineType: LENOVO 2055W1W
  Package: cups 1.3.9-17ubuntu3.2
  Papersize: letter
  PpdFiles: hp1200: HP LaserJet 1200 Foomatic/hpijs, hpijs 2.8.7
  ProcCmdLine: root=UUID=7e2488f5-5963-409b-9069-39f19996edc8 ro quiet splash
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.28-16.55-generic
  SourcePackage: cups

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/471650/+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 466577] Re: First character of every line and the top half of the header is missing when printing with gedit

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  First character of every line and the top half of the header is
  missing when printing with gedit

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: gedit

  I use a brother DCP-150C printer with a paper size set to A4.

  ProblemType: Bug
  Architecture: i386
  Date: Sat Oct 31 13:45:42 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gedit
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: gedit 2.28.0-0ubuntu2
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: gedit
  Uname: Linux 2.6.31-14-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/466577/+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 472466] Re: lprm broken in Karmic

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lprm broken in Karmic

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups-bsd

  ==> lsb_release -rd
 Description:   Ubuntu 9.10
 Release:   9.10

  ==> apt-cache policy cups-bsd
 cups-bsd:
   Installed: 1.4.1-5ubuntu2
   Candidate: 1.4.1-5ubuntu2
   Version table:
  *** 1.4.1-5ubuntu2 0
 500 http://ftp.crihan.fr karmic/main Packages
 100 /var/lib/dpkg/status

  "lprm job_id" should remove this job from the queue
  Instead, since my upgrade to Karmic, I get:
 lprm: The printer or class was not found.

  ProblemType: Bug
  Architecture: i386
  Date: Tue Nov  3 11:02:57 2009
  DistroRelease: Ubuntu 9.10
  Lpstat:
   device for ij: usb://HP/Business%20Inkjet%201200?serial=TH4BF120P7
   device for phsm: hp:/net/Photosmart_C4380_series?ip=192.168.1.9
   device for sam: ipp://192.168.1.11
  MachineType: System manufacturer P5E-VM HDMI
  Package: cups-bsd 1.4.1-5ubuntu2
  Papersize: A4
  ProcCmdLine: BOOT_IMAGE=(hd0,2)/boot/vmlinuz-2.6.31-14-generic 
root=UUID=5b3fa41c-9349-4136-80fe-5a6f20b11cf9 ro quiet splash LOC!pfrb!
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/ksh
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: cups
  Uname: Linux 2.6.31-14-generic i686
  dmi.bios.date: 12/17/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5E-VM HDMI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd12/17/2007:svnSystemmanufacturer:pnP5E-VMHDMI:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E-VMHDMI:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5E-VM HDMI
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/472466/+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 483032] Re: CUPS-Move-Job don't work from http; lpmove ok

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  CUPS-Move-Job don't work from http; lpmove ok

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  Ubuntu 9.10
  cups: 1.4.1-5ubuntu2.1

  from http://localhost:631/ CUPS-Move-Job response Forbidden
  on same job lpmove working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/483032/+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 486131] Re: random system restarts with the message "Reloading Common Unix Printing System: cupsd

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  random system restarts with the message "Reloading Common Unix
  Printing System: cupsd

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  Description:  Ubuntu 9.10
  Release:  9.10

  
  Package files:
   100 /var/lib/dpkg/status
   release a=now
   500 http://security.ubuntu.com karmic-security/multiverse Packages
   release v=9.10,o=Ubuntu,a=karmic-security,n=karmic,l=Ubuntu,c=multiverse
   origin security.ubuntu.com
   500 http://security.ubuntu.com karmic-security/universe Packages
   release v=9.10,o=Ubuntu,a=karmic-security,n=karmic,l=Ubuntu,c=universe
   origin security.ubuntu.com
   500 http://security.ubuntu.com karmic-security/restricted Packages
   release v=9.10,o=Ubuntu,a=karmic-security,n=karmic,l=Ubuntu,c=restricted
   origin security.ubuntu.com
   500 http://security.ubuntu.com karmic-security/main Packages
   release v=9.10,o=Ubuntu,a=karmic-security,n=karmic,l=Ubuntu,c=main
   origin security.ubuntu.com
   500 http://us.archive.ubuntu.com karmic-updates/multiverse Packages
   release v=9.10,o=Ubuntu,a=karmic-updates,n=karmic,l=Ubuntu,c=multiverse
   origin us.archive.ubuntu.com
   500 http://us.archive.ubuntu.com karmic-updates/universe Packages
   release v=9.10,o=Ubuntu,a=karmic-updates,n=karmic,l=Ubuntu,c=universe
   origin us.archive.ubuntu.com
   500 http://us.archive.ubuntu.com karmic-updates/restricted Packages
   release v=9.10,o=Ubuntu,a=karmic-updates,n=karmic,l=Ubuntu,c=restricted
   origin us.archive.ubuntu.com
   500 http://us.archive.ubuntu.com karmic-updates/main Packages
   release v=9.10,o=Ubuntu,a=karmic-updates,n=karmic,l=Ubuntu,c=main
   origin us.archive.ubuntu.com
   500 http://us.archive.ubuntu.com karmic/multiverse Packages
   release v=9.10,o=Ubuntu,a=karmic,n=karmic,l=Ubuntu,c=multiverse
   origin us.archive.ubuntu.com
   500 http://us.archive.ubuntu.com karmic/universe Packages
   release v=9.10,o=Ubuntu,a=karmic,n=karmic,l=Ubuntu,c=universe
   origin us.archive.ubuntu.com
   500 http://us.archive.ubuntu.com karmic/restricted Packages
   release v=9.10,o=Ubuntu,a=karmic,n=karmic,l=Ubuntu,c=restricted
   origin us.archive.ubuntu.com
   500 http://us.archive.ubuntu.com karmic/main Packages
   release v=9.10,o=Ubuntu,a=karmic,n=karmic,l=Ubuntu,c=main
   origin us.archive.ubuntu.com
  Pinned packages:

  i don't expect anything to happen.. i would like the random restarts
  to stop

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: b90bad4f14b0f68986131655e51d5b0a
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  CupsErrorLog:
   W [20/Nov/2009:17:10:57 -0500] Unknown LogLevel warning on line 1.
   W [20/Nov/2009:17:10:57 -0500] No limit for CUPS-Get-Document defined in 
policy default - using Send-Document's policy
  Date: Fri Nov 20 20:40:56 2009
  DistroRelease: Ubuntu 9.10
  Lpstat: device for allinone: hp:/net/Photosmart_C7200_series?ip=192.168.1.201
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Inc. MM061
  Package: cups 1.4.1-5ubuntu2.1
  Papersize: letter
  PpdFiles: allinone: HP Photosmart c7200 Series hpijs, 3.9.8
  ProcCmdLine: root=UUID=e37b6ee1-cad2-4ad6-be36-89a6aad52b9d ro quiet splash
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: cups
  Uname: Linux 2.6.31-14-generic i686
  dmi.bios.date: 04/02/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0KD882
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd04/02/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/486131/+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 487546] Re: Printing fails, no error shown

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Printing fails, no error shown

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  I did a fresh install of kubuntu 9.10.
  Installed my printer (Minolta PagePro 8L via parallel port) via the kde 
printer system settings. It was detected automatically.
  Printing any document (including the test page) results in following:
  - the system tray printer applet is shown very shortly
  - no error message is displayed
  - no document appears at the printer

  Previous versions of Kubuntu worked with this printer.

  Description:Ubuntu 9.10
  Release:9.10
  cups:
Installiert: 1.4.1-5ubuntu2.1
Kandidat: 1.4.1-5ubuntu2.1
Versions-Tabelle:
   *** 1.4.1-5ubuntu2.1 0
  500 http://de.archive.ubuntu.com karmic-updates/main Packages
  500 http://security.ubuntu.com karmic-security/main Packages
  100 /var/lib/dpkg/status
   1.4.1-5ubuntu2 0
  500 http://de.archive.ubuntu.com karmic/main Packages

  lsmod | grep lp
  lp 11908  0
  parport40528  3 ppdev,parport_pc,lp

  lsmod | grep ppdev
  ppdev   8232  0
  parport40528  3 ppdev,parport_pc,lp

  lpinfo -v
  network beh
  direct scsi
  network http
  network smb
  serial serial:/dev/ttyS0?baud=115200
  network socket
  network ipp
  network lpd
  direct parallel:/dev/lp0
  direct hpfax
  direct hp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/487546/+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 487681] Re: cups builtin filters produce cropped printouts

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  cups builtin filters produce cropped printouts

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  Printing an A4 portrait PostScript document from the command line (lpr
  document.ps) produces cropped printout: the top of the page is
  cropped. When converting this to PDF format using ghostscript, and
  printing via lpr, the printout is correct.

  A related problem might be: setting 10mm page margins in openoffice I
  get the warning that this is outside of the printable region. The
  printed document is cropped at the top, but not on the other 3 sides.
  If I export the document to PDF, and print it from the command line
  via lpr, the printout is correct, not cropped.

  The used printer is a Xerox Phaser 8560 Foomatic/Postscript
  (recommended)

  Description:Ubuntu 9.10
  Release:9.10
  cups, cups-client, cups-common:  1.4.1-5ubuntu2.1
  foomatic-db: 20090825-0ubuntu4
  foomatic-filters: 4.0.3-0ubuntu2
  ghostscript-cups: 8.70.dsfg.1-0ubuntu3

  (latest versions as of today, 24.11.2009)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/487681/+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 489750] Re: Plug'n'print fails - HP LaserJet 1018 doesn't print anything

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Plug'n'print fails - HP LaserJet 1018 doesn't print anything

Status in foo2zjs:
  Incomplete
Status in cups package in Ubuntu:
  Expired

Bug description:
  Using Release: 9.10
  Using Cups 1.4.1

  I was trying to print a test page, it was put into the printer queue,
  but nothing happens next. The task sits in the queue for a long time.

  Before this bug I experienced the problem that the task quickly
  disappeared from the queue. Then I had the similar problem as
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/450513

  Reinstalling printer was done as described here:
  http://foo2zjs.rkkda.com/.

  After reinstalling the printer I have what I've described.

To manage notifications about this bug go to:
https://bugs.launchpad.net/foo2zjs/+bug/489750/+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 494644] Re: Samba printer installed in cups, can't print

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
Status: Incomplete => Expired

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

Title:
Samba printer installed in cups, can't print

Status in cups package in Ubuntu:
Expired

Bug description:
I belive this is a CUPS-problem, but I'm not shure.

How I installed the printer:
=
Since my Ubuntu-installation is in Norwegian, I will try to translate the
menu into English.
From the desktop, I selected System-->Administration-->Printer-->New-->Printer
Then I selected Windows Printer via SAMBA and typed
"smb://terne.hials.no/gbl1-r4500" where "terne" is a servername in the domain
"hials.no" (In Windows i can select the printer by typing \\terne and my
usern...@hials.no and password.)
"gbl1-r4500" is the network name for the Ricoh Aficio MP-4500 printer.
The I selected the Autenification and entered my usern...@hials.no and my
password in the respective textfields before pressing Comfirm.
Then I got the information that the printer is acessable.
Pressing OK.

PROBLEM PART:
=
Then I was trying to print a test-page from the properties menu for the
printer.
Then I got the Username and password dialog for this network printer and
entered usern...@hials.no and my password.
ERROR: Access denied.
usern...@terne.hials.no and password
ERROR: Access denied.
username and password
ERROR: Access denied.
ERROR: Access denied.

Any idea how to fix this?
I belive that the domain workgroup is dominating above the domain hials.no
When I type usern...@hials.no, then the domain shuld be hials.no and not
workgroup.
So the server might belive that I'm trying to log on by using
usern...@hials.no@workgroup
This is only my idea aboute the bug.

But this login dialog wiondow should have a domain-field so I can
replace "workgroup" with hials.no

Regards
Gjermund Buset

ProblemType: Bug
Architecture: i386
Date: Wed Dec 9 18:30:42 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2)
Lpstat: device for Ricoh-Aficio-MP-4500: smb://terne.hials.no/gbl1-r4500
MachineType: Dell Inc. Latitude E4200
Package: cups 1.4.1-5ubuntu2.1
Papersize: a4
PpdFiles: Ricoh-Aficio-MP-4500: Ricoh Aficio MP 4500 - CUPS+Gutenprint v5.2.4
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-16-generic
root=UUID=ed1b8136-d4cd-4dfc-9e67-4aba56685b85 ro quiet splash
ProcEnviron:
LANGUAGE=nn_NO.UTF-8
LANG=nn_NO.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
SourcePackage: cups
Uname: Linux 2.6.31-16-generic i686
dmi.bios.date: 10/29/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0D516F
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA12:bd10/29/2009:svnDellInc.:pnLatitudeE4200:pvr:rvnDellInc.:rn0D516F:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E4200
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/494644/+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 509702] Re: USB printer only available to root

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  USB printer only available to root

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: software-center

  I expect to be able to print via usb from my Gnome desktop logged in as 
'john'.
  However my printer does not show up.

  When I open a terminal console, I do

  john@beeblebrox:~$ lsusb
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 002: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 005: ID 413c:8103 Dell Computer Corp. Wireless 350 Bluetooth
  Bus 001 Device 002: ID 413c:a005 Dell Computer Corp. Internal 2.0 Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  john@beeblebrox:~$ su -
  Password: 
  root@beeblebrox:~# lsusb
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 002: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 005: ID 413c:8103 Dell Computer Corp. Wireless 350 Bluetooth
  Bus 001 Device 003: ID 0924:3d60 Xerox 
  Bus 001 Device 002: ID 413c:a005 Dell Computer Corp. Internal 2.0 Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  Check out the 'Xerox' entry which only shows up when logged in as
  root.

  Other info:
  * Description:Ubuntu 9.10
  * Release:9.10

  * updated to the latest pathlevel

  Finally.. I did a Vaniilla install and reproduced this problem
  instantly before the first patches arrived and after the Vanilla
  install was fully patched.

  ProblemType: Bug
  Architecture: i386
  Date: Tue Jan 19 16:17:48 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  NonfreeKernelModules: wl
  Package: software-center 1.0.2
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: software-center
  Uname: Linux 2.6.31-17-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/509702/+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 491205] Re: Upgrading to Karmic breaks printing for Canon UFRII printers with canon drivers MF4140 etc

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Upgrading to Karmic breaks printing for Canon UFRII printers with
  canon drivers MF4140 etc

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: cups

  I installed the Canon printer driver under Jaunty (9.04) and printing to the 
Canon MF4140 worked perfectly.
  I upgraded to Karmic (9.10) and printing no longer worked. I downgraded only 
the hal-cups-util package and it works again.

  I am reporting this as a bug on cups as it seems to cover several packages.
  It appears the ability to execute /usr/lib/cups/backend/hal is _essential_ 
for canon UFR II drivers.

  Canon's UFR II printer driver is widely used to support their low cost
  printers that do not run a PDL (PS/PDF/PCL) interpreter.

  
  The installed driver package was 

  > Canon UFR II Printer Driver for Linux. This printer driver provides 
printing functions for Canon printers operating under the
  > CUPS (Common UNIX Printing System) environment, a printing system that 
operates on Linux operating systems.

  $> dpkg --info 
UFR_II_Printer_Driver_for_Linux_Driver_V180_uk_EN/32-bit_Driver/Debian/cndrvcups-common_1.80-1_i386.deb
 
   new debian package, version 2.0.
   Package: cndrvcups-common
   Version: 1.80-1
   Section: net
   Priority: optional
   Architecture: i386
   Depends: libatk1.0-0 (>= 1.7.2), libc6 (>= 2.3.2.ds1-21), libglib2.0-0 (>= 
2.6.0), libgtk2.0-0 (>= 2.6.0), libpango1.0-0 (>= 1.8.1), cupsys, gs-esp, 
libcupsys2 (>= 1.1.23)
   Installed-Size: 3576
   Maintainer: Canon Inc. 
   Description: Canon Printer Driver Common Modules Ver.1.80
Canon Printer Driver Common Modules.

  $> dpkg --info 
UFR_II_Printer_Driver_for_Linux_Driver_V180_uk_EN/32-bit_Driver/Debian/cndrvcups-ufr2-uk_1.80-1_i386.deb
 
   new debian package, version 2.0.
   Package: cndrvcups-ufr2-uk
   Version: 1.80-1
   Section: net
   Priority: optional
   Architecture: i386
   Depends: libc6 (>= 2.3.2.ds1-21), cndrvcups-common (>= 1.80)
   Replaces: cndrvcups-ufr2-us, cndrvcups-lipslx, cndrvcups-capt
   Installed-Size: 7748
   Maintainer: Canon Inc. 
   Source: cndrvcups-lb
   Description: Canon UFR2 Printer Driver for Linux
Canon UFR2 Printer Driver for Linux.
This UFR2 printer driver provides printing functions for Canon LBP/iR
printers operating under the CUPS (Common UNIX Printing System) environment.

  The error messages in /var/log/cups/error_log were
  > Unable to execute /usr/lib/cups/backend/hal: No such file or directory

  I [02/Dec/2009:14:09:08 +1100] [Job 197] Started filter 
/usr/lib/cups/filter/pdftopdf (PID 3915)
  I [02/Dec/2009:14:09:08 +1100] [Job 197] Started filter 
/usr/lib/cups/filter/cpdftocps (PID 3916)
  I [02/Dec/2009:14:09:08 +1100] [Job 197] Started filter 
/usr/lib/cups/filter/pstoufr2cpca (PID 3917)
  E [02/Dec/2009:14:09:08 +1100] Unable to execute /usr/lib/cups/backend/hal: 
No such file or directory
  D [02/Dec/2009:14:09:08 +1100] cupsdMarkDirty(P-)
  D [02/Dec/2009:14:09:08 +1100] cupsdMarkDirty(-S)
  D [02/Dec/2009:14:09:08 +1100] cupsdMarkDirty(-S)
  E [02/Dec/2009:14:09:08 +1100] [Job 197] Stopping job because the sheduler 
could not execute the backend.
  D [02/Dec/2009:14:09:08 +1100] cupsdMarkDirty(J-)
  D [02/Dec/2009:14:09:08 +1100] cupsdMarkDirty(-S)
  D [02/Dec/2009:14:09:08 +1100] Returning IPP successful-ok for Print-Job 
(ipp://localhost:631/printers/Canon-MF4100-UFRII-LT) from localhost
  D [02/Dec/2009:14:09:08 +1100] PID 3915 (/usr/lib/cups/filter/pdftopdf) was 
terminated normally with signal 15.
  D [02/Dec/2009:14:09:08 +1100] PID 3916 (/usr/lib/cups/filter/cpdftocps) was 
terminated normally with signal 15.
  D [02/Dec/2009:14:09:08 +1100] PID 3917 (/usr/lib/cups/filter/pstoufr2cpca) 
was terminated normally with signal 15.

  This was the consistent problem. As described in it's README, the
  package hal-cups-utils was a place holder as the ubuntu developers
  have mode to udev and system-config-printer-udev. This unfortunately
  breaks this printer driver.

  Checking Ubuntu Packages I found that Jaunty's hal-cups-utils might be
  installable. So I purged the current and downloaded and installed the
  previous.

  $> sudo ap-get purge hal-cups-utils
  $> sudo dpkg --force-all -i 
hal-cups-utils_0.6.19+git20090217-0ubuntu7_i386.deb 
  dpkg: regarding hal-cups-utils_0.6.19+git20090217-0ubuntu7_i386.deb 
containing hal-cups-utils:
   system-config-printer-udev conflicts with hal-cups-utils (<< 1.1.10)
hal-cups-utils (version 0.6.19+git20090217-0ubuntu7) is to be installed.
  dpkg: warning: ignoring conflict, may proceed anyway!
  (Reading database ... 366186 files and directories currently installed.)
  Un

[Touch-packages] [Bug 510007] Re: Can't print again after A4 paper ends

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Can't print again after A4 paper ends

Status in cups package in Ubuntu:
  Expired

Bug description:
  Binary package hint: kdeutils

  Printer Epson Stylus DX7400 can't print after normal A4 paper ends.
  Printer-applet shows jobs pending but cancel them and try again to print is 
useless.
  I need to restart computer to get control of the printer and do the work 
again.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Jan 20 09:50:53 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/share/kde4/apps/printer-applet/printer-applet.py
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  InterpreterPath: /usr/bin/python2.6
  Package: printer-applet 4:4.3.4-0ubuntu1~karmic1
  ProcEnviron:
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-18.55-generic
  SourcePackage: kdeutils
  Uname: Linux 2.6.31-18-generic i686
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:1918): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (firefox:2837): GLib-WARNING **: g_set_prgname() called multiple times

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/510007/+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 1786574] Re: remove i2c-i801 from blacklist

2018-10-03 Thread Anthony Wong

On Wed, 19 Sep 2018 at 22:01,  Christian Ehrhardt  <
1786...@bugs.launchpad.net> wrote:

> Hi,
> first of all this package seems to have quite some issues in the merges
> that are done - it doesn't list all remaining changes and the i2c blacklist
> is one of them.
> It comes from like back in 2005 and I agree, it might or is safe to be
> removed.
>
> Thanks to Stefan Bader for cleaning this up, as the MP linked here has
> e.g. on changelog entries.
> I'd ack to his branch at [1] for Cosmic, is it would be an MP to ack on.
>

Thanks!


>
> But for the actual sponsoring, as I never really touched kmod before I'd
> be happy if you'd ask one of the foundations Team that is here this week
> that touched it recently as they might have extra considerations. OTOH
> the change really looks right for cosmic IMHO, so if no one responds get
> back to me.
>
> SRUs of this are quite a different topic for the following reasons:
> - if the issues still exists, it might regress somebody due to the SRU
> then.
> - If you can prove that the old issue really does no more exist with e.g.
> the oldest kernel in Bionic, then it might be done. But you'd have to
> outline that in detail when completing the SRU template for this bug [2]
> Without the prove I'd be concerned and as a SRU member would reject it, so
> really make sure you
> get this documented right.
>

I have added the SRU justification, hope that helps.


** Description changed:

+ SRU justification
+ 
+ 
+ [Impact]
+ Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.
+ 
+ [Test case]
+ 1. Install Ubuntu
+ 2. Check touchpad works or not
+ 3. Install the fixed kmod package
+ 4. Confirm touchpad works
+ 
+ [Regression Potential]
+ i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.
+ 
+ Besides, there look like to be a quirk in linux kernel that fixes it:
+ https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434
+ 
+ [Other Info]
+ rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329
+ 
+ 
---
+ Original bug report:
+ 
  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To
  use the touchpad, users have to remove the i2c-i801 line manually.
  
  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.
  
  There is also another bug (Bug #1475945) that needs this module for Acer
  trackpad to work.

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Confirmed
Status in kmod source package in Xenial:
  Confirmed
Status in kmod source package in Bionic:
  Confirmed
Status in kmod source package in Cosmic:
  Confirmed

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Origi

[Touch-packages] [Bug 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo

2018-10-03 Thread Eric Desrochers

We cannot cherrypick the fix as is. It has been introduced upstream[1]
inside a function and structure that not yet exist in 229[1].

Instead of backporting the whole thing (which seems unnecessary) we can
possibly mimic the upstream fix.

Basically, the upstream fix adds a "|| MOUNT(u)->just_mounted;" where
just_mounted is a boolean. A boolean only has two possible values
("true" and "false").

Definition of "just_mounted" : 
# src/core/mount.h 
bool just_mounted:1; 

Full upstream code line : 
flags->just_mounted = !MOUNT(u)->from_proc_self_mountinfo || 
MOUNT(u)->just_mounted; 


The current 229 (xenial code) is as follow : 
MOUNT(u)->just_mounted = !MOUNT(u)->from_proc_self_mountinfo; 

Considering the boolean explain above, If we add "|| true;" it should
suffice.

Full systemd xenial code line (theory): 
MOUNT(u)->just_mounted = !MOUNT(u)->from_proc_self_mountinfo || true ; 

A colleague of mine and myself have separately tested my theory in my PPA that 
I have built, and so far it seems to work fine : 
$ mount --bind bind-test bind-test 
$ mount -t tmpfs tmpfs bind-test/abc 
$ umount bind-test/abc 
$ systemctl list-unites --all | grep bind-test 
home-ubuntu-bind/x2dtest.mount loaded active mounted /home/ubuntu/bind-test 

Could you please give the test package a try to make sure you arrive at the 
same result as us ? 
$ sudo add-apt-repository ppa:slashd/case199975 
$ sudo apt-get update 
$ sudo apt-get install systemd 

Please allow a few hours for the package to build again.

Eric

[1] git describe --contains 65d36b495 
v237~140

** Tags added: sts

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Description changed:

  From the PR:
  Currently, if there are two /proc/self/mountinfo entries with the same
  mount point path, the mount setup flags computed for the second of
  these two entries will overwrite the mount setup flags computed for
  the first of these two entries. This is the root cause of issue #7798.
  This patch changes mount_setup_existing_unit to prevent the
  just_mounted mount setup flag from being overwritten if it is set to
  true. This will allow all mount units created from /proc/self/mountinfo
  entries to be initialized properly.
  
  One line fix in https://github.com/systemd/systemd/pull/7811/files
  
  Referenced issue: https://github.com/systemd/systemd/issues/7798
  
  Related kubernetes issue:
  https://github.com/kubernetes/kubernetes/issues/57345
  
  systemd v237 has this fix, but we'd like to have it fixed in 16.04.
+ 
+ [Other Informations]
+ 
+ It only affect systemd for Xenial, later release already has the fix:
+ 
+ $ git describe --contains 65d36b495
+ v237~140
+ 
+ ==>  systemd | 229-4ubuntu21.4  | xenial-updates  
+  systemd | 237-3ubuntu10.3  | bionic-updates  
+  systemd | 239-7ubuntu9 | cosmic

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

** Changed in: systemd (Ubuntu Xenial)
   Importance: Undecided => Medium

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

Title:
  systemd: core: Fix edge case when processing /proc/self/mountinfo

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed

Bug description:
  From the PR:
  Currently, if there are two /proc/self/mountinfo entries with the same
  mount point path, the mount setup flags computed for the second of
  these two entries will overwrite the mount setup flags computed for
  the first of these two entries. This is the root cause of issue #7798.
  This patch changes mount_setup_existing_unit to prevent the
  just_mounted mount setup flag from being overwritten if it is set to
  true. This will allow all mount units created from /proc/self/mountinfo
  entries to be initialized properly.

  One line fix in https://github.com/systemd/systemd/pull/7811/files

  Referenced issue: https://github.com/systemd/systemd/issues/7798

  Related kubernetes issue:
  https://github.com/kubernetes/kubernetes/issues/57345

  systemd v237 has this fix, but we'd like to have it fixed in 16.04.

  [Other Informations]

  It only affect systemd for Xenial, later release already has the fix:

  $ git describe --contains 65d36b495
  v237~140

  ==>  systemd | 229-4ubuntu21.4  | xenial-updates  
   systemd | 237-3ubuntu10.3  | bionic-updates  
   systemd | 239-7ubuntu9 | cosmic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1795764/+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 1795853] Re: Assembler crashes when building ndiswrapper

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

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

Title:
  Assembler crashes when building ndiswrapper

Status in binutils package in Ubuntu:
  Incomplete

Bug description:
  > lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  --
  > apt-cache policy ndiswrapper-dkms
  ndiswrapper-dkms:
Installato: 1.60-6
Candidato:  1.60-6
Tabella versione:
   *** 1.60-6 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://it.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  100 /var/lib/dpkg/status

  --
  when installing via apt-get:

  Loading new ndiswrapper-1.60 DKMS files...
  Building for 4.15.0-34-generic 4.15.0-36-generic
  Building initial module for 4.15.0-34-generic
  Done.

  ndiswrapper:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.15.0-34-generic/updates/dkms/

  depmod...

  DKMS: install completed.
  Building initial module for 4.15.0-36-generic
  Error! Bad return status for module build on kernel: 4.15.0-36-generic 
(x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information.

  ---
  contents of the log file:
  DKMS make.log for ndiswrapper-1.60 for kernel 4.15.0-36-generic (x86_64)
  mer  3 ott 2018, 12.29.37, CEST
  make: ingresso nella directory "/usr/src/linux-headers-4.15.0-36-generic"
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/loader.o
  symbolmap: sezione: invalid section
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/proc.o
  symbolmap: sezione: invalid section
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/rtl.o
  symbolmap: sezione: invalid section
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapper.o
  Assembler messages:
  Internal error (Errore di segmentazione).
  Please report this bug.
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/usb.o
AS [M]  /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.o
  scripts/Makefile.build:332: recipe for target 
'/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o] Error 2
  make[1]: *** Attesa per i processi non terminati
  symbolmap: sezione: invalid section
  symbolmap: sezione: invalid section
  Makefile:1551: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.60/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.60/build] Error 2
  make: uscita dalla directory "/usr/src/linux-headers-4.15.0-36-generic"

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ndiswrapper-dkms 1.60-6
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linu

[Touch-packages] [Bug 1795853] Re: ndiswrapper-dkms 1.60-6: ndiswrapper kernel module failed to build when istalling from apt-get

It looks like the assembler is crashing:

Assembler messages:
Internal error (Errore di segmentazione).
Please report this bug.

So this would be a bug in 'binutils'.

** Package changed: ndiswrapper (Ubuntu) => binutils (Ubuntu)

** Summary changed:

- ndiswrapper-dkms 1.60-6: ndiswrapper kernel module failed to build when 
istalling from apt-get
+ Assembler crashes when building ndiswrapper

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

Title:
  Assembler crashes when building ndiswrapper

Status in binutils package in Ubuntu:
  Incomplete

Bug description:
  > lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  --
  > apt-cache policy ndiswrapper-dkms
  ndiswrapper-dkms:
Installato: 1.60-6
Candidato:  1.60-6
Tabella versione:
   *** 1.60-6 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://it.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  100 /var/lib/dpkg/status

  --
  when installing via apt-get:

  Loading new ndiswrapper-1.60 DKMS files...
  Building for 4.15.0-34-generic 4.15.0-36-generic
  Building initial module for 4.15.0-34-generic
  Done.

  ndiswrapper:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.15.0-34-generic/updates/dkms/

  depmod...

  DKMS: install completed.
  Building initial module for 4.15.0-36-generic
  Error! Bad return status for module build on kernel: 4.15.0-36-generic 
(x86_64)
  Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information.

  ---
  contents of the log file:
  DKMS make.log for ndiswrapper-1.60 for kernel 4.15.0-36-generic (x86_64)
  mer  3 ott 2018, 12.29.37, CEST
  make: ingresso nella directory "/usr/src/linux-headers-4.15.0-36-generic"
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h
MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h
MKSTUBS /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.h
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/crt.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/hal.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/loader.o
  symbolmap: sezione: invalid section
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/pe_linker.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/pnp.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/proc.o
  symbolmap: sezione: invalid section
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/rtl.o
  symbolmap: sezione: invalid section
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapmem.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapper.o
  Assembler messages:
  Internal error (Errore di segmentazione).
  Please report this bug.
CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/usb.o
AS [M]  /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.o
  scripts/Makefile.build:332: recipe for target 
'/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o' failed
  make[1]: *** [/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o] Error 2
  make[1]: *** Attesa per i processi non terminati
  symbolmap: sezione: invalid section
  symbolmap: sezione: invalid section
  Makefile:1551: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.60/build' failed
  make: *** [_module_/var/lib/dkms/ndiswrapper/1.60/build] Error 2
  make: uscita dalla directory "/usr/src/linux-headers-4.15.0-36-generic"

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ndiswrapper-dkms 1.60-6
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-36-generic
  Date: Wed Oct  3 12:29:45 2018
  InstallationDate: Installed on 2016-01-25 (981 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  PackageVersion: 1.60-6
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  Relat

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

2018-10-03 Thread David Dombrowsky

Here's what I did to "solve" it on 18.04

{{{
git clone https://github.com/curl/curl.git
cd curl
git checkout curl-7_58_0
autoreconf -i
sudo mkdir /opt/curl
./configure --prefix=/opt/curl
make
sudo make install
ln -s /opt/curl/bin/curl* /usr/local/bin/
}}}

Of course, that doesn't really fix anything, but it gets a compatible
version of curl on to this system.

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop
  mongodb

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1795853] [NEW] ndiswrapper-dkms 1.60-6: ndiswrapper kernel module failed to build when istalling from apt-get

You have been subscribed to a public bug:

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

--
> apt-cache policy ndiswrapper-dkms
ndiswrapper-dkms:
  Installato: 1.60-6
  Candidato:  1.60-6
  Tabella versione:
 *** 1.60-6 500
500 http://it.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
500 http://it.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
100 /var/lib/dpkg/status

--
when installing via apt-get:

Loading new ndiswrapper-1.60 DKMS files...
Building for 4.15.0-34-generic 4.15.0-36-generic
Building initial module for 4.15.0-34-generic
Done.

ndiswrapper:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.15.0-34-generic/updates/dkms/

depmod...

DKMS: install completed.
Building initial module for 4.15.0-36-generic
Error! Bad return status for module build on kernel: 4.15.0-36-generic (x86_64)
Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information.

---
contents of the log file:
DKMS make.log for ndiswrapper-1.60 for kernel 4.15.0-36-generic (x86_64)
mer  3 ott 2018, 12.29.37, CEST
make: ingresso nella directory "/usr/src/linux-headers-4.15.0-36-generic"
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h
  MKSTUBS /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.h
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/crt.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/hal.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/loader.o
symbolmap: sezione: invalid section
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ndis.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/pe_linker.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/pnp.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/proc.o
symbolmap: sezione: invalid section
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/rtl.o
symbolmap: sezione: invalid section
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapmem.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapper.o
Assembler messages:
Internal error (Errore di segmentazione).
Please report this bug.
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/usb.o
  AS [M]  /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.o
scripts/Makefile.build:332: recipe for target 
'/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o' failed
make[1]: *** [/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o] Error 2
make[1]: *** Attesa per i processi non terminati
symbolmap: sezione: invalid section
symbolmap: sezione: invalid section
Makefile:1551: recipe for target '_module_/var/lib/dkms/ndiswrapper/1.60/build' 
failed
make: *** [_module_/var/lib/dkms/ndiswrapper/1.60/build] Error 2
make: uscita dalla directory "/usr/src/linux-headers-4.15.0-36-generic"

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ndiswrapper-dkms 1.60-6
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
DKMSKernelVersion: 4.15.0-36-generic
Date: Wed Oct  3 12:29:45 2018
InstallationDate: Installed on 2016-01-25 (981 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
PackageVersion: 1.60-6
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: ndiswrapper
Title: ndiswrapper-dkms 1.60-6: ndiswrapper kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic
-- 
ndiswrapper-dkms 1.60-6: ndiswrapper kernel module failed to build when 
istalling from apt-get
https://bugs.launchpad.net/bugs/1795853
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to binutils in Ubuntu.

-- 
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 1793092] Re: [FFe] openssl 1.1.1

https://launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2

** Changed in: openssl (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: python2.7 (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: python3.6 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [FFe] openssl 1.1.1

Status in openssl package in Ubuntu:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.6 package in Ubuntu:
  Fix Released

Bug description:
  Merge openssl 1.1.1 from debian unstable.

  OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream
  LTS release.

  Resulting in the following changes in Ubuntu:

  - openssl moves from 1.1.0 series to 1.1.1 LTS series

  - TLS1.3 is enabled, and used by default, when possible. Major
  feature.

  - All existing delta, and minimally accepted key sizes, and minimally
  accepted protocol versions remain the same.

  Proposed package is in
  https://launchpad.net/~xnox/+archive/ubuntu/openssl with a rebuild of
  all the reverse dependencies. It demonstrates that openssl compiled as
  above is more compatible and has less issues than debian config. There
  are a few FTBFS, which are also present in cosmic-release; there are
  some test-suite expectations mismatch (connectivity succeeds with
  tls1.3 even though lower/different algos are expected); there are very
  little connectivity tests thus connectivity interop are the biggest
  issues which will be unavoidable with introducing 1.3.

  ===

  Ubuntu delta summary versus debian unstable in this merge:
  - Replace duplicate files in the doc directory with symlinks.
  - debian/libssl1.1.postinst:
    + Display a system restart required notification on libssl1.1
  upgrade on servers.
    + Use a different priority for libssl1.1/restart-services depending
  on whether a desktop, or server dist-upgrade is being performed.
  - Revert "Enable system default config to enforce TLS1.2 as a
    minimum" & "Increase default security level from 1 to 2".
  - Further decrease security level from 1 to 0, for compatibility with
    openssl 1.0.2.

  These mitigate most of the runtime incompatibilities, and ensure
  client<->server compatibility between 1.1.1, 1.1.0, and 1.0.2 series
  and thus one can continue to mix & match xenial/bionic/cosmic
  releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092/+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 1795895] Re: Accelerators on selected menu-items are not readable

** Summary changed:

- Accelerators on selected menu-items are not visible
+ Accelerators on selected menu-items are not readable

** Tags added: visual-quality

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

Title:
  Accelerators on selected menu-items are not readable

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  As visible in the attached screenshot in the nautilus context menu,
  the accelerator is not readable when the item is selected:
  https://i.imgur.com/xabntIH.png

  [ Test case ]

  1. Open Nautilus
  2. Right-click on the files view
  3. Select an item with an accelerator
  4. The accelerator should be visible (white in Ambiance theme)

  [ Possible regressions ]

  Accelerators on menuitems on menubars might always be painted as when
  hovered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1795895/+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 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]

Now affecting cosmic too, only just:

bionic: 156
cosmic: 1

** Tags added: cosmic

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

Title:
  Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when
  running Skype or Slack snaps]

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 16 18:18:18 2017
  xserver.configfile: default
  xserver.devices:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.19.3-1ubuntu1.2

To manage notifications about this bug go to:
https://bugs.launc

[Touch-packages] [Bug 1775068] Re: Volume control not working Dell XPS 27 (7760)

** No longer affects: pulseaudio (Ubuntu)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  Volume control not working Dell XPS 27 (7760)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Pressing vol up/vol down show OSD change up/down but volume all time
  is at 100%.

  I found temporary fix:

  Add section:
  [Element Master]
  switch = mute
  volume = ignore

  To:
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trolinka   1610 F pulseaudio
   /dev/snd/controlC1:  trolinka   1610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-02 (121 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner 
sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0T12MX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 7760 AIO
  dmi.sys.vendor: Dell Inc.
  ---
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trolinka   1846 F pulseaudio
   /dev/snd/controlC1:  trolinka   1846 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-02 (122 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. XPS 7760 AIO
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner 
sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0T12MX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 7760 AIO
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]

2018-10-03 Thread Benoit Lamarche

I have the same problem. How to provide additional information?

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

Title:
  Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when
  running Skype or Slack snaps]

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 16 18:18:18 2017
  xserver.configfile: default
  xserver.devices:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.19.3-1ubuntu1.2

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

[Touch-packages] [Bug 1793092] Re: [FFe] openssl 1.1.1

** Tags removed: block-proposed

** Changed in: openssl (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: python2.7 (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: python3.6 (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  [FFe] openssl 1.1.1

Status in openssl package in Ubuntu:
  Fix Committed
Status in python2.7 package in Ubuntu:
  Fix Committed
Status in python3.6 package in Ubuntu:
  Fix Committed

Bug description:
  Merge openssl 1.1.1 from debian unstable.

  OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream
  LTS release.

  Resulting in the following changes in Ubuntu:

  - openssl moves from 1.1.0 series to 1.1.1 LTS series

  - TLS1.3 is enabled, and used by default, when possible. Major
  feature.

  - All existing delta, and minimally accepted key sizes, and minimally
  accepted protocol versions remain the same.

  Proposed package is in
  https://launchpad.net/~xnox/+archive/ubuntu/openssl with a rebuild of
  all the reverse dependencies. It demonstrates that openssl compiled as
  above is more compatible and has less issues than debian config. There
  are a few FTBFS, which are also present in cosmic-release; there are
  some test-suite expectations mismatch (connectivity succeeds with
  tls1.3 even though lower/different algos are expected); there are very
  little connectivity tests thus connectivity interop are the biggest
  issues which will be unavoidable with introducing 1.3.

  ===

  Ubuntu delta summary versus debian unstable in this merge:
  - Replace duplicate files in the doc directory with symlinks.
  - debian/libssl1.1.postinst:
    + Display a system restart required notification on libssl1.1
  upgrade on servers.
    + Use a different priority for libssl1.1/restart-services depending
  on whether a desktop, or server dist-upgrade is being performed.
  - Revert "Enable system default config to enforce TLS1.2 as a
    minimum" & "Increase default security level from 1 to 2".
  - Further decrease security level from 1 to 0, for compatibility with
    openssl 1.0.2.

  These mitigate most of the runtime incompatibilities, and ensure
  client<->server compatibility between 1.1.1, 1.1.0, and 1.0.2 series
  and thus one can continue to mix & match xenial/bionic/cosmic
  releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092/+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 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

2018-10-03 Thread Anders Kaseorg

1.12.4 is in cosmic-proposed now with the upstream fix.

** Changed in: network-manager (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: network-manager (Ubuntu)
 Assignee: Anders Kaseorg (andersk) => (unassigned)

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1792745/+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 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop

2018-10-03 Thread Timo Aaltonen

well, bisected already, will discuss with upstream tomorrow

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

Title:
  gdm doesn't start on a fresh installation of Cosmic Desktop

Status in gdm3 package in Ubuntu:
  Won't Fix
Status in kmod package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed
Status in gdm3 source package in Cosmic:
  Won't Fix
Status in kmod source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in xorg-server source package in Cosmic:
  Confirmed

Bug description:
  ubuntu cosmic desktop 20180925

  After installation gdm fails to start and there is only a black screen
  with a blinking cursor on the top left of the screen.

  gdm3 can be started manually from a tty

  When this issue happens there is a plymouth crash reported in bug
  1794292


  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Tue Sep 25 13:54:45 2018
  InstallationDate: Installed on 2018-09-25 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+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 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop

2018-10-03 Thread Timo Aaltonen

the issue seen with kvm -vga std is a regression in x-x-v-fbdev 0.5.0,
same thing happens on bionic if that version is used there. It doesn't
have a huge number of commits, so it should be easy to bisect.

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

Title:
  gdm doesn't start on a fresh installation of Cosmic Desktop

Status in gdm3 package in Ubuntu:
  Won't Fix
Status in kmod package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed
Status in gdm3 source package in Cosmic:
  Won't Fix
Status in kmod source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in xorg-server source package in Cosmic:
  Confirmed

Bug description:
  ubuntu cosmic desktop 20180925

  After installation gdm fails to start and there is only a black screen
  with a blinking cursor on the top left of the screen.

  gdm3 can be started manually from a tty

  When this issue happens there is a plymouth crash reported in bug
  1794292


  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  Date: Tue Sep 25 13:54:45 2018
  InstallationDate: Installed on 2018-09-25 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+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 1766872] Re: 'Enable Network' in recovery mode not working properly.

2018-10-03 Thread Eric Desrochers

I've been told that the "resume" doesn't resume boot.

Can someone validate ?

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

Title:
  'Enable Network' in recovery mode not working properly.

Status in friendly-recovery package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Won't Fix
Status in friendly-recovery source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Won't Fix
Status in friendly-recovery source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Won't Fix
Status in friendly-recovery source package in Cosmic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in friendly-recovery source package in DD-Series:
  Invalid
Status in systemd source package in DD-Series:
  Won't Fix

Bug description:
  This bug has been noticed after the introduction of the fix of (LP:
  #1682637) in Bionic.

  I have notice a block in Bionic when choosing 'Enable Network' option
  in recovery mode on different bionic vanilla system and I can
  reproduce all the time.

  I also asked colleagues to give it a try (for a second pair of eye on
  this) and they have the same result as me.

  Basically, when choosing 'Enable Network' it get block or lock.
  If we hit 'ctrl-c', then a shell arrive and the system has network 
connectivity.

  Here's what I find while enabling "systemd.debug-shell=1" from vtty9 :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask
  |-systemd-journal
  

  # ps
  root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent

  root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket

  root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery-
  mode/options/network

  Additionally,

  systemd-analyze blame:
  "Bootup is not yet finished. Please try again later"

  "systemctl list-jobs" is showing a 100 jobs in 'waiting' state

  The only 'running' unit is friendly-recovery.service :
  52 friendly-recovery.service start running

  The rest are all "waiting". My understanding is that "waiting" units
  will be executed only after those which are "running" are completed.
  Which explain why the "ctlr-c" allow the boot to continue.

  All the systemd special unit important at boot-up are waiting.
  7 sysinit.target start waiting
  3 basic.target   start waiting
  .

  Seems like systemd is not fully initialise in 'Recovery Mode' and
  doesn't allow any 'systemctl start' operation without
  password/passphrase request, which I suspect is hidden by the
  recovery-mode menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1795614] Re: packagekit frontend locking

2018-10-03 Thread Robie Basak

The updated description explains why frontend locking is necessary, but
how does this particular bug impact users? What's wrong for users as a
consequence of this bug? Eg. what user story is broken? I need to
understand this in order to judge whether an SRU is warranted, which I'm
supposed to consider as part of my SRU review.

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

Title:
  packagekit frontend locking

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Xenial:
  Triaged
Status in packagekit source package in Bionic:
  Triaged
Status in packagekit source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  PackageKit needs an adjustment for frontend locking, so it does not release 
the frontend lock during dpkg invocations, but only the normal dpkg lock.

  Frontend locking prevents race conditions between multiple dpkg
  frontends, which can cause other frontends to be interrupted while
  they are installing stuff.

  [Test case]
  1. Install a package
  2. Modify prerm to sleep
  3. Remove package via pkcon and check that packagekitd process holds 
lock-frontend and dpkg holds lock (we release lock by closing the lock files, 
so just check if the files are open).

  [Regression potential]
  Changing the code to call UnLockInner() vs UnLock() makes it do less steps 
and only release "lock" as before, and not "lock-frontend". That should not be 
causing any regressions.

  The patch also adds a call to LockInner() after the dpkg execution to
  make it reacquire "lock", this could fail. It should not have much
  impact however, as it only affects a single transaction AFAICT. It
  does reduce the risk of some frontend not implementing frontend
  locking from racing while we still hold the frontend lock, though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1795614/+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 1794690] Re: Backport 0.8.2 for a CVE update

2018-10-03 Thread Robie Basak

This is in the SRU queue but it looks like the security pocket might be
a better target? I asked Timo to liase with the security team to get a
decision on that.

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

Title:
  Backport 0.8.2 for a CVE update

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  In Progress

Bug description:
  [Impact]
  0.8.2 has completed the fuzzing work started in 0.8.1, so backport the 
package from cosmic to fix these CVE's:

  CVE-2018-15853 CVE-2018-15854 CVE-2018-15855 CVE-2018-15856
  CVE-2018-15857 CVE-2018-15858 CVE-2018-15859 CVE-2018-15861
  CVE-2018-15862 CVE-2018-15863 CVE-2018-15864.

  upstream NEWS:

  libxkbcommon 0.8.2 - 2018-08-05
  ==

  - Fix various problems found with fuzzing (see commit messages for
    more details):

  - Fix a few NULL-dereferences, out-of-bounds access and undefined behavior
    in the XKB text format parser.

  libxkbcommon 0.8.1 - 2018-08-03
  ==

  - Fix various problems found in the meson build (see commit messages for more
    details):

  - Fix compilation on Darwin.

  - Fix compilation of the x11 tests and demos when XCB is installed in a
    non-standard location.

  - Fix xkbcommon-x11.pc missing the Requires specification.

  - Fix various problems found with fuzzing and Coverity (see commit messages 
for
    more details):

  - Fix stack overflow in the XKB text format parser when evaluating boolean
    negation.

  - Fix NULL-dereferences in the XKB text format parser when some 
unsupported
    tokens appear (the tokens are still parsed for backward compatibility).

  - Fix NULL-dereference in the XKB text format parser when parsing an
    xkb_geometry section.

  - Fix an infinite loop in the Compose text format parser on some
  inputs.

  - Fix an invalid free() when using multiple keysyms.

  - Replace the Unicode characters for the leftanglebracket and 
rightanglebracket
    keysyms from the deprecated LEFT/RIGHT-POINTING ANGLE BRACKET to
    MATHEMATICAL LEFT/RIGHT ANGLE BRACKET.

  - Reject out-of-range Unicode codepoints in xkb_keysym_to_utf8 and
    xkb_keysym_to_utf32.

  [Test case]
  install the update, check that nothing breaks wrt keyboard handling

  [Regression potential]
  slim, this has been in cosmic for some time already, and upstream 
specifically asked to backport this to stable releases

  There are some other changes to the packaging, but these are harmless
  and won't regress anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1794690/+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 1795973] [NEW] package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: installed gconf2 package post-installation script subprocess returned error exit status 1 lors de la mise

2018-10-03 Thread biscans

Public bug reported:

lors de la mise à jour de ubuntu 16.04 à ubuntu 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gconf2 3.2.6-4ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Wed Oct  3 21:19:59 2018
ErrorMessage: installed gconf2 package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2016-02-06 (970 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: gconf
Title: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: installed 
gconf2 package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: installed
  gconf2 package post-installation script subprocess returned error exit
  status 1 lors de la mise à jour de ubuntu 16.04 a ubuntu 18.04

Status in gconf package in Ubuntu:
  New

Bug description:
  lors de la mise à jour de ubuntu 16.04 à ubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gconf2 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Wed Oct  3 21:19:59 2018
  ErrorMessage: installed gconf2 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2016-02-06 (970 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: installed 
gconf2 package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1795973/+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 1784347] Re: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath

2018-10-03 Thread Mathieu Trudel-Lapierre

I'm not convinced that this patch is necessarily what's the right thing
to do -- in your examples, you have mpatha1, for instance -- using no
sparator at all. In this case, fdisk would still display the device
incorrectly.

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

Title:
  ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting
  partitions name for the mpath

Status in The Ubuntu-power-systems project:
  Triaged
Status in util-linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-09 11:14:07 
==
  We have the Ubuntu1804 installed on our BostonLC system. Create a SAN via the 
Emulex adapter to have the mpath disk. 
  Running the fdisk -l and ls -l showing the conflict name for the mpath. 

  :~# uname -a
  Linux boslcp4 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp4:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part1   2048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2  419432448  838862847 419430400  200G 83 Linux
  /dev/mapper/mpatha-part3  838862848 1258291199 419428352  200G 83 Linux

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:04 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:03 /dev/mapper/mpatha3 -> ../dm-3

  == Comment: #2 - Chanh H. Nguyen  - 2018-01-09 11:35:04 
==
  I just modify the partitions and it is still showing the conflicting name on 
partitions.

  :~# ls -l /dev/mapper/mpatha*
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha -> ../dm-0
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha1 -> ../dm-1
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha2 -> ../dm-2
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha3 -> ../dm-3
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha4 -> ../dm-4
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha5 -> ../dm-5
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha6 -> ../dm-6
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha7 -> ../dm-7
  lrwxrwxrwx 1 root root 7 Jan  9 04:33 /dev/mapper/mpatha8 -> ../dm-8

  :~# fdisk -l /dev/mapper/mpatha
  Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 32768 bytes / 32768 bytes
  Disklabel type: dos
  Disk identifier: 0xa5be904b

  Device   Boot  StartEnd   Sectors  Size Id Type
  /dev/mapper/mpatha-part12048  419432447 419430400  200G 83 Linux
  /dev/mapper/mpatha-part2   419432448  838862847 419430400  200G 83 Linux
  /dev/mapper/mpatha-part3   838862848  964691967 125829120   60G 83 Linux
  /dev/mapper/mpatha-part4   964691968 1258291199 293599232  140G  5 
Extended
  /dev/mapper/mpatha-part5   964694016 1006637055  41943040   20G 83 Linux
  /dev/mapper/mpatha-part6  1006639104 1048582143  41943040   20G 83 Linux
  /dev/mapper/mpatha-part7  1048584192 1090527231  41943040   20G 83 Linux
  /dev/mapper/mpatha-part8  1090529280 1132472319  41943040   20G 83 Linux

  == Comment: #5 - Kyle Mahlkuch  - 2018-06-26 13:50:12 
==
  I have created and submitted a patch that should help with this bug. I will 
update when/if the patch is accepted.

  == Comment: #9 - Kyle Mahlkuch  - 2018-07-27 09:10:44 
==
  Here is the patch: 
  
https://github.com/karelzak/util-linux/commit/73775189767195f1d9f5b6b6f6a54e51f61c4356

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1784347/+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 1748280] Re: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower

2018-10-03 Thread Corey Bryant

** Changed in: nova (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  'nova reboot' on arm64 is just 'nova reboot --hard' but slower

Status in OpenStack Compute (nova):
  Confirmed
Status in nova package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Within Canonical's multi-architecture compute cloud, I observed that
  arm64 instances were taking an unreasonable amount of time to return
  from a 'nova reboot' (2 minutes +, vs. ~16s for POWER in the same
  cloud region).

  Digging into this, I find that a nova soft reboot request is doing
  nothing at all on arm64 (no events visible within the qemu guest, and
  no reboot is triggered within the guest), and then after some sort of
  timeout (~2m), 'nova reboot' falls back to a hard reset of the guest.

  Since this is entirely predictable on the arm64 platform (because
  there's no implementation of ACPI plumbed through), 'nova reboot' on
  arm64 should just skip straight to the hard reboot and save everyone
  some clock time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1748280/+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 1793092] Re: [FFe] openssl 1.1.1

** Tags added: block-proposed

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

Title:
  [FFe] openssl 1.1.1

Status in openssl package in Ubuntu:
  Triaged
Status in python2.7 package in Ubuntu:
  Triaged
Status in python3.6 package in Ubuntu:
  Triaged

Bug description:
  Merge openssl 1.1.1 from debian unstable.

  OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream
  LTS release.

  Resulting in the following changes in Ubuntu:

  - openssl moves from 1.1.0 series to 1.1.1 LTS series

  - TLS1.3 is enabled, and used by default, when possible. Major
  feature.

  - All existing delta, and minimally accepted key sizes, and minimally
  accepted protocol versions remain the same.

  Proposed package is in
  https://launchpad.net/~xnox/+archive/ubuntu/openssl with a rebuild of
  all the reverse dependencies. It demonstrates that openssl compiled as
  above is more compatible and has less issues than debian config. There
  are a few FTBFS, which are also present in cosmic-release; there are
  some test-suite expectations mismatch (connectivity succeeds with
  tls1.3 even though lower/different algos are expected); there are very
  little connectivity tests thus connectivity interop are the biggest
  issues which will be unavoidable with introducing 1.3.

  ===

  Ubuntu delta summary versus debian unstable in this merge:
  - Replace duplicate files in the doc directory with symlinks.
  - debian/libssl1.1.postinst:
    + Display a system restart required notification on libssl1.1
  upgrade on servers.
    + Use a different priority for libssl1.1/restart-services depending
  on whether a desktop, or server dist-upgrade is being performed.
  - Revert "Enable system default config to enforce TLS1.2 as a
    minimum" & "Increase default security level from 1 to 2".
  - Further decrease security level from 1 to 0, for compatibility with
    openssl 1.0.2.

  These mitigate most of the runtime incompatibilities, and ensure
  client<->server compatibility between 1.1.1, 1.1.0, and 1.0.2 series
  and thus one can continue to mix & match xenial/bionic/cosmic
  releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092/+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 1795899] Re: Update grilo-plugins to 0.3.8

This bug was fixed in the package grilo-plugins - 0.3.8-1ubuntu1

---
grilo-plugins (0.3.8-1ubuntu1) cosmic; urgency=medium

  * Sync with Debian (LP: #1795899). Remaining change:
- Split package into -base and -extra (Closes: #805609)
  * Have grilo-plugins-0.3-base install the pkg-config .pc file

grilo-plugins (0.3.8-2) unstable; urgency=medium

  * debian/rules:
- Run dh_missing with --fail-missing.
  * debian/install:
- Install the pkg-config .pc file (Closes: #910123).

grilo-plugins (0.3.8-1) unstable; urgency=medium

  * New upstream release.
  * debian/control:
- List new plugin in the package description: TheAudioDB Cover.
- Update Standards-Version to 4.2.1 (no changes).
- Replace build dependencies on autoconf-archive and intltool with
  meson.
  * autoconf-macros.patch:
- Drop patch, this package doesn't use autotools anymore.
  * debian/rules:
- Remove the dh_auto_configure and dh_makeshlibs overrides, none of
  them are needed.

 -- Jeremy Bicha   Wed, 03 Oct 2018 09:42:42 -0400

** Changed in: grilo-plugins (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update grilo-plugins to 0.3.8

Status in grilo-plugins package in Ubuntu:
  Fix Released

Bug description:
  This is required by gnome-music 3.30.1. (We already have gnome-music
  3.30.0).

  https://gitlab.gnome.org/GNOME/grilo-plugins/blob/master/NEWS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1795899/+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 1795857] Re: enable CONFIG_DRM_BOCHS

2018-10-03 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1795857

** Tags added: iso-testing

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

Title:
  enable CONFIG_DRM_BOCHS

Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CONFIG_DRM_BOCHS got disabled for
  https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648

  but doing so regressed running qemu with the 'std' VGA driver, where
  it'd fail to start X after install, as mentioned on bug 1794280

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1795959] [NEW] [FFe] Seed xdg-desktop-portal-gtk

2018-10-03 Thread Ken VanDine

Public bug reported:

Security and MIR reviews have been completed for xdg-desktop-portal-
gtk[1] and xdg-desktop-portal[2].

These packages can improve desktop integration of snap packages.  The
risk is low as nothing in the default desktop install actually exercises
the portals at this time.  We need to seed the portals so they are
available when snaps are installed that can utilize them.  Flatpak
packages will also benefit.

1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069
2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: xdg-desktop-portal-gtk (Ubuntu) => ubuntu-meta
(Ubuntu)

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

Title:
  [FFe] Seed xdg-desktop-portal-gtk

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Security and MIR reviews have been completed for xdg-desktop-portal-
  gtk[1] and xdg-desktop-portal[2].

  These packages can improve desktop integration of snap packages.  The
  risk is low as nothing in the default desktop install actually
  exercises the portals at this time.  We need to seed the portals so
  they are available when snaps are installed that can utilize them.
  Flatpak packages will also benefit.

  1. 
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069
  2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+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 1795959] [NEW] [FFe] Seed xdg-desktop-portal-gtk

You have been subscribed to a public bug:

Security and MIR reviews have been completed for xdg-desktop-portal-
gtk[1] and xdg-desktop-portal[2].

These packages can improve desktop integration of snap packages.  The
risk is low as nothing in the default desktop install actually exercises
the portals at this time.  We need to seed the portals so they are
available when snaps are installed that can utilize them.  Flatpak
packages will also benefit.

1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069
2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

-- 
[FFe] Seed xdg-desktop-portal-gtk
https://bugs.launchpad.net/bugs/1795959
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-meta in Ubuntu.

-- 
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 1794690] Re: Backport 0.8.2 for a CVE update

2018-10-03 Thread Leonidas S. Barbosa

Hi Timo,

Are you planning to update only for bionic or will you do this also for trusty 
and xenial? 
Asking that because I was/am planning to put that update in my stack for xenial 
and trusty.

[]'s

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

Title:
  Backport 0.8.2 for a CVE update

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  In Progress

Bug description:
  [Impact]
  0.8.2 has completed the fuzzing work started in 0.8.1, so backport the 
package from cosmic to fix these CVE's:

  CVE-2018-15853 CVE-2018-15854 CVE-2018-15855 CVE-2018-15856
  CVE-2018-15857 CVE-2018-15858 CVE-2018-15859 CVE-2018-15861
  CVE-2018-15862 CVE-2018-15863 CVE-2018-15864.

  upstream NEWS:

  libxkbcommon 0.8.2 - 2018-08-05
  ==

  - Fix various problems found with fuzzing (see commit messages for
    more details):

  - Fix a few NULL-dereferences, out-of-bounds access and undefined behavior
    in the XKB text format parser.

  libxkbcommon 0.8.1 - 2018-08-03
  ==

  - Fix various problems found in the meson build (see commit messages for more
    details):

  - Fix compilation on Darwin.

  - Fix compilation of the x11 tests and demos when XCB is installed in a
    non-standard location.

  - Fix xkbcommon-x11.pc missing the Requires specification.

  - Fix various problems found with fuzzing and Coverity (see commit messages 
for
    more details):

  - Fix stack overflow in the XKB text format parser when evaluating boolean
    negation.

  - Fix NULL-dereferences in the XKB text format parser when some 
unsupported
    tokens appear (the tokens are still parsed for backward compatibility).

  - Fix NULL-dereference in the XKB text format parser when parsing an
    xkb_geometry section.

  - Fix an infinite loop in the Compose text format parser on some
  inputs.

  - Fix an invalid free() when using multiple keysyms.

  - Replace the Unicode characters for the leftanglebracket and 
rightanglebracket
    keysyms from the deprecated LEFT/RIGHT-POINTING ANGLE BRACKET to
    MATHEMATICAL LEFT/RIGHT ANGLE BRACKET.

  - Reject out-of-range Unicode codepoints in xkb_keysym_to_utf8 and
    xkb_keysym_to_utf32.

  [Test case]
  install the update, check that nothing breaks wrt keyboard handling

  [Regression potential]
  slim, this has been in cosmic for some time already, and upstream 
specifically asked to backport this to stable releases

  There are some other changes to the packaging, but these are harmless
  and won't regress anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1794690/+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 1795242] Re: Digicert certificate is not included

2018-10-03 Thread Seth Arnold

On Wed, Oct 03, 2018 at 05:55:59AM -, Stan Janssen wrote:
> (I wonder why DigiCert has not been able to convice Mozilla to include
> this certificate, yet they still sign certificates that are intended for

Most CAs have multiple levels of certificates. The ones that the browsers
include in trust bundles are normally stored off-line in locked vaults in
multiple shards and are only reconstructed once every few years for use,
to sign intermediary certificates.

The intermediary certificates are the ones that are used to sign end-user
certificates. These are not included in the browser bundles. Every site
that uses them is expected to include them in their certificate chains.

> public verification using this. And, to make matters worse, why most
> other browsers do seem to include the certificate by default or a least
> trust the certificate chain enough to load the pages.)

The trouble is, browser authors have seen incomplete chains before, and
have gone to some efforts to try to remediate the problem themselves. They
will *store* intermediate certificates as they discover them around the
wider web. If a misconfigured site forgets to include the full chain of
certificates, quite often site admins won't even notice because the
intermediate certs will be in their *local* user configuration.

This is what makes a service like Qualys's TLS checker so wonderful: it's
a well-written neutral third-party that knows how to diagnose a suprising
number of deployment and implementation mistakes.

Thanks

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

Title:
  Digicert certificate is not included

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  EDIT: This post originally mentioned the "DigiCert High Assurance EV
  Root CA", which was the wrong name. The "DigiCert SHA2 Secure Server"
  was intended. This post has been edited for clarity.

  -

  The "DigiCert SHA2 Secure Server" certificate is missing, which means
  that the system does not trust web sites that are using SSL
  certificates signed by that root. An example is a popular website in
  the Netherlands https://marktplaats.nl. The result is that no
  resources other that the text-only homepage is loaded.

  Installing the Digicert root certificte manually from Digicert solves
  the problem:

  ```
  wget https://dl.cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt
  mv DigiCertSHA2SecureServerCA.crt DigiCertSHA2SecureServerCA.der
  openssl x509 -inform DER -outform PEM -in DigiCertSHA2SecureServerCA.der  
-out DigicertSHA2SecureServerCA.pem.crt
  sudo mkdir -p /usr/share/ca-certificates/extra
  sudo cp DigicertSHA2SecureServerCA.pem.crt /usr/share/ca-certificates/extra/
  sudo dpkg-reconfigure ca-certificates
  ```

  Maybe there is a valid reason for not including this certificate by
  default, or maybe this certificate can be included by default, since
  it seems like it's assumed to be included on every machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1795242/+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 1795789] Re: package libjpeg-turbo8:i386 1.4.2-0ubuntu3.1 failed to install/upgrade: package libjpeg-turbo8:i386 is not ready for configuration cannot configure (current status '

2018-10-03 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 libjpeg-turbo in Ubuntu.
https://bugs.launchpad.net/bugs/1795789

Title:
  package libjpeg-turbo8:i386 1.4.2-0ubuntu3.1 failed to
  install/upgrade: package libjpeg-turbo8:i386 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in libjpeg-turbo package in Ubuntu:
  New

Bug description:
  error after half update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-turbo8:i386 1.4.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   composer: Purge
   libjpeg-turbo8: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Tue Oct  2 12:32:43 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu9
  DpkgTerminalLog:
   Removing composer (1.0.0~beta2-1) ...
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libjpeg-turbo8:i386 (--configure):
package libjpeg-turbo8:i386 is not ready for configuration
cannot configure (current status 'half-installed')
  DuplicateSignature:
   package:libjpeg-turbo8:i386:1.4.2-0ubuntu3.1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libjpeg-turbo8:i386 (--configure):
package libjpeg-turbo8:i386 is not ready for configuration
  ErrorMessage: package libjpeg-turbo8:i386 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2018-09-22 (10 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8:i386 1.4.2-0ubuntu3.1 failed to 
install/upgrade: package libjpeg-turbo8:i386 is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1795789/+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 1795789] Re: package libjpeg-turbo8:i386 1.4.2-0ubuntu3.1 failed to install/upgrade: package libjpeg-turbo8:i386 is not ready for configuration cannot configure (current status '

2018-10-03 Thread Seth Arnold

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libjpeg-turbo8:i386 1.4.2-0ubuntu3.1 failed to
  install/upgrade: package libjpeg-turbo8:i386 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in libjpeg-turbo package in Ubuntu:
  New

Bug description:
  error after half update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-turbo8:i386 1.4.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   composer: Purge
   libjpeg-turbo8: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Tue Oct  2 12:32:43 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu9
  DpkgTerminalLog:
   Removing composer (1.0.0~beta2-1) ...
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libjpeg-turbo8:i386 (--configure):
package libjpeg-turbo8:i386 is not ready for configuration
cannot configure (current status 'half-installed')
  DuplicateSignature:
   package:libjpeg-turbo8:i386:1.4.2-0ubuntu3.1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libjpeg-turbo8:i386 (--configure):
package libjpeg-turbo8:i386 is not ready for configuration
  ErrorMessage: package libjpeg-turbo8:i386 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2018-09-22 (10 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8:i386 1.4.2-0ubuntu3.1 failed to 
install/upgrade: package libjpeg-turbo8:i386 is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1795789/+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 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

2018-10-03 Thread Keith Myers

I am having this issue.  I can't get rid of the error.
● apport-autoreport.service - Process error reports when automatic reporting is 
enabled
   Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2018-10-03 10:55:24 PDT; 1min 
42s ago
  Process: 1007 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, 
status=1/FAILURE)
 Main PID: 1007 (code=exited, status=1/FAILURE)

Oct 03 10:55:24 Serenity systemd[1]: Starting Process error reports when 
automatic reporting is enabled...
Oct 03 10:55:24 Serenity whoopsie-upload-all[1007]: ERROR: whoopsie is not 
running
Oct 03 10:55:24 Serenity systemd[1]: apport-autoreport.service: Main process 
exited, code=exited, status=1/FAILURE
Oct 03 10:55:24 Serenity systemd[1]: apport-autoreport.service: Failed with 
result 'exit-code'.
Oct 03 10:55:24 Serenity systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.

keith@Serenity:~$ whoopsie
keith@Serenity:~$ systemctl status apport-autoreport.service
● apport-autoreport.service - Process error reports when automatic reporting is 
enabled
   Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2018-10-03 10:55:24 PDT; 3min 
13s ago
  Process: 1007 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, 
status=1/FAILURE)
 Main PID: 1007 (code=exited, status=1/FAILURE)

Oct 03 10:55:24 Serenity systemd[1]: Starting Process error reports when 
automatic reporting is enabled...
Oct 03 10:55:24 Serenity whoopsie-upload-all[1007]: ERROR: whoopsie is not 
running
Oct 03 10:55:24 Serenity systemd[1]: apport-autoreport.service: Main process 
exited, code=exited, status=1/FAILURE
Oct 03 10:55:24 Serenity systemd[1]: apport-autoreport.service: Failed with 
result 'exit-code'.
Oct 03 10:55:24 Serenity systemd[1]: Failed to start Process error reports when 
automatic reporting is enabled.

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

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Attached image.

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+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 1795946] [NEW] package libicu55 55.1-7ubuntu0.3 failed to install/upgrade: impossibile copiare i dati estratti per "./usr/lib/x86_64-linux-gnu/libicudata.so.55.1" in "/usr/lib/x8

2018-10-03 Thread Stefano Ierardi

Public bug reported:

 I don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libicu55 55.1-7ubuntu0.3
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-lowlatency 4.13.13
Uname: Linux 4.13.0-32-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Tue Oct  2 18:48:29 2018
Dependencies:
 gcc-5-base 5.4.0-6ubuntu1~16.04.10
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu10
 libgcc1 1:6.0.1-0ubuntu1
 libstdc++6 5.4.0-6ubuntu1~16.04.10
ErrorMessage: impossibile copiare i dati estratti per 
"./usr/lib/x86_64-linux-gnu/libicudata.so.55.1" in 
"/usr/lib/x86_64-linux-gnu/libicudata.so.55.1.dpkg-new": fine del file o dello 
stream inattesa
InstallationDate: Installed on 2017-08-26 (401 days ago)
InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: icu
Title: package libicu55 55.1-7ubuntu0.3 failed to install/upgrade: impossibile 
copiare i dati estratti per "./usr/lib/x86_64-linux-gnu/libicudata.so.55.1" in 
"/usr/lib/x86_64-linux-gnu/libicudata.so.55.1.dpkg-new": fine del file o dello 
stream inattesa
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libicu55 55.1-7ubuntu0.3 failed to install/upgrade:
  impossibile copiare i dati estratti per "./usr/lib/x86_64-linux-
  gnu/libicudata.so.55.1" in "/usr/lib/x86_64-linux-
  gnu/libicudata.so.55.1.dpkg-new": fine del file o dello stream
  inattesa

Status in icu package in Ubuntu:
  New

Bug description:
   I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libicu55 55.1-7ubuntu0.3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Oct  2 18:48:29 2018
  Dependencies:
   gcc-5-base 5.4.0-6ubuntu1~16.04.10
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
   libstdc++6 5.4.0-6ubuntu1~16.04.10
  ErrorMessage: impossibile copiare i dati estratti per 
"./usr/lib/x86_64-linux-gnu/libicudata.so.55.1" in 
"/usr/lib/x86_64-linux-gnu/libicudata.so.55.1.dpkg-new": fine del file o dello 
stream inattesa
  InstallationDate: Installed on 2017-08-26 (401 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: icu
  Title: package libicu55 55.1-7ubuntu0.3 failed to install/upgrade: 
impossibile copiare i dati estratti per 
"./usr/lib/x86_64-linux-gnu/libicudata.so.55.1" in 
"/usr/lib/x86_64-linux-gnu/libicudata.so.55.1.dpkg-new": fine del file o dello 
stream inattesa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1795946/+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 1795936] Re: linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable

2018-10-03 Thread hackeron

** Package changed: apport (Ubuntu) => linux (Ubuntu)

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

Title:
   linux-image-generic : Depends: linux-image-4.15.0-37-generic but it
  is not installable

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This was working an hour ago, but at the moment I get the following
  when I run: apt-get install linux-image-generic:

  ```
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not 
installable
 Recommends: thermald but it is not going to be 
installed
  ```

  My sources.list look like this:

  ```
  ## Ubuntu Main Repos
  deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe 
multiverse
  deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe 
multiverse

  ## Ubuntu Update Repos
  deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted 
universe multiverse
  deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe 
multiverse
  deb http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted 
universe multiverse
  deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted 
universe multiverse
  deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted 
universe multiverse
  deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted 
universe multiverse
  deb-src http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted 
universe multiverse
  deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted 
universe multiverse

  ## Ubuntu Partner Repo
  deb http://archive.canonical.com/ubuntu bionic partner
  deb-src http://archive.canonical.com/ubuntu bionic partner
  ```

  Any ideas?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795936/+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 1795936] [NEW] linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not installable

2018-10-03 Thread hackeron

Public bug reported:

This was working an hour ago, but at the moment I get the following when
I run: apt-get install linux-image-generic:

```
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not 
installable
   Recommends: thermald but it is not going to be installed
```

My sources.list look like this:

```
## Ubuntu Main Repos
deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe 
multiverse

## Ubuntu Update Repos
deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted universe 
multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe 
multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted universe 
multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe 
multiverse
deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted 
universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted 
universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted 
universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted 
universe multiverse

## Ubuntu Partner Repo
deb http://archive.canonical.com/ubuntu bionic partner
deb-src http://archive.canonical.com/ubuntu bionic partner
```

Any ideas?

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

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

Title:
   linux-image-generic : Depends: linux-image-4.15.0-37-generic but it
  is not installable

Status in apport package in Ubuntu:
  New

Bug description:
  This was working an hour ago, but at the moment I get the following
  when I run: apt-get install linux-image-generic:

  ```
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-image-generic : Depends: linux-image-4.15.0-37-generic but it is not 
installable
 Recommends: thermald but it is not going to be 
installed
  ```

  My sources.list look like this:

  ```
  ## Ubuntu Main Repos
  deb http://archive.ubuntu.com/ubuntu/ bionic main restricted universe 
multiverse
  deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted universe 
multiverse

  ## Ubuntu Update Repos
  deb http://archive.ubuntu.com/ubuntu/ bionic-security main restricted 
universe multiverse
  deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted universe 
multiverse
  deb http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted 
universe multiverse
  deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted 
universe multiverse
  deb-src http://archive.ubuntu.com/ubuntu/ bionic-security main restricted 
universe multiverse
  deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted 
universe multiverse
  deb-src http://archive.ubuntu.com/ubuntu/ bionic-proposed main restricted 
universe multiverse
  deb-src http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted 
universe multiverse

  ## Ubuntu Partner Repo
  deb http://archive.canonical.com/ubuntu bionic partner
  deb-src http://archive.canonical.com/ubuntu bionic partner
  ```

  Any ideas?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1795936/+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 1775068] Re: Volume control not working Dell XPS 27 (7760)

2018-10-03 Thread Wojciech Solarczyk

Kernel tested.
It's working now!

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

Title:
  Volume control not working Dell XPS 27 (7760)

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Pressing vol up/vol down show OSD change up/down but volume all time
  is at 100%.

  I found temporary fix:

  Add section:
  [Element Master]
  switch = mute
  volume = ignore

  To:
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trolinka   1610 F pulseaudio
   /dev/snd/controlC1:  trolinka   1610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-02 (121 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner 
sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0T12MX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 7760 AIO
  dmi.sys.vendor: Dell Inc.
  ---
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trolinka   1846 F pulseaudio
   /dev/snd/controlC1:  trolinka   1846 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-02 (122 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. XPS 7760 AIO
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner 
sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0T12MX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 7760 AIO
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 382938] Re: ufw should be enabled by default

Santeri, see comment #6. There still is no graphical tool in Ubuntu's
default desktop to enable and disable ufw. Therefore, we won't be able
to accept your patch.

I am unsubscribing ubuntu-sponsors. Please re-subscribe ubuntu-sponsors
if you have something else that needs sponsoring.

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

Title:
  ufw should be enabled by default

Status in ufw:
  Invalid
Status in ufw package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: ufw

  ufw should be enabled by default in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/382938/+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 1793092] Re: [FFe] openssl 1.1.1

Should hopefully land today... here be dragons

** Tags removed: block-proposed needs-debian-merge

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

Title:
  [FFe] openssl 1.1.1

Status in openssl package in Ubuntu:
  Triaged
Status in python2.7 package in Ubuntu:
  Triaged
Status in python3.6 package in Ubuntu:
  Triaged

Bug description:
  Merge openssl 1.1.1 from debian unstable.

  OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream
  LTS release.

  Resulting in the following changes in Ubuntu:

  - openssl moves from 1.1.0 series to 1.1.1 LTS series

  - TLS1.3 is enabled, and used by default, when possible. Major
  feature.

  - All existing delta, and minimally accepted key sizes, and minimally
  accepted protocol versions remain the same.

  Proposed package is in
  https://launchpad.net/~xnox/+archive/ubuntu/openssl with a rebuild of
  all the reverse dependencies. It demonstrates that openssl compiled as
  above is more compatible and has less issues than debian config. There
  are a few FTBFS, which are also present in cosmic-release; there are
  some test-suite expectations mismatch (connectivity succeeds with
  tls1.3 even though lower/different algos are expected); there are very
  little connectivity tests thus connectivity interop are the biggest
  issues which will be unavoidable with introducing 1.3.

  ===

  Ubuntu delta summary versus debian unstable in this merge:
  - Replace duplicate files in the doc directory with symlinks.
  - debian/libssl1.1.postinst:
    + Display a system restart required notification on libssl1.1
  upgrade on servers.
    + Use a different priority for libssl1.1/restart-services depending
  on whether a desktop, or server dist-upgrade is being performed.
  - Revert "Enable system default config to enforce TLS1.2 as a
    minimum" & "Increase default security level from 1 to 2".
  - Further decrease security level from 1 to 0, for compatibility with
    openssl 1.0.2.

  These mitigate most of the runtime incompatibilities, and ensure
  client<->server compatibility between 1.1.1, 1.1.0, and 1.0.2 series
  and thus one can continue to mix & match xenial/bionic/cosmic
  releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092/+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 1795101] Re: package unattended-upgrades 1.1ubuntu1.18.04.5 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error ex

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.5 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 10

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Fri Sep 28 23:14:39 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 10
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.5 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "7";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-09-03T13:16:10.333183

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1795101/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs

2018-10-03 Thread Joseph Salisbury

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  NTP reload failure (unable to read library) on overlayfs

Status in cloud-init:
  Won't Fix
Status in apparmor package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
  0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

  Related bugs:
   * bug 1645644: cloud-init ntp not using expected servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1795614] Re: packagekit frontend locking

2018-10-03 Thread Julian Andres Klode

** Description changed:

  [Impact]
  PackageKit needs an adjustment for frontend locking, so it does not release 
the frontend lock during dpkg invocations, but only the normal dpkg lock.
+ 
+ Frontend locking prevents race conditions between multiple dpkg
+ frontends, which can cause other frontends to be interrupted while they
+ are installing stuff.
  
  [Test case]
  1. Install a package
  2. Modify prerm to sleep
  3. Remove package via pkcon and check that packagekitd process holds 
lock-frontend and dpkg holds lock (we release lock by closing the lock files, 
so just check if the files are open).
  
  [Regression potential]
  Changing the code to call UnLockInner() vs UnLock() makes it do less steps 
and only release "lock" as before, and not "lock-frontend". That should not be 
causing any regressions.
  
  The patch also adds a call to LockInner() after the dpkg execution to
  make it reacquire "lock", this could fail. It should not have much
  impact however, as it only affects a single transaction AFAICT. It does
  reduce the risk of some frontend not implementing frontend locking from
  racing while we still hold the frontend lock, though.

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

Title:
  packagekit frontend locking

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Xenial:
  Triaged
Status in packagekit source package in Bionic:
  Triaged
Status in packagekit source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  PackageKit needs an adjustment for frontend locking, so it does not release 
the frontend lock during dpkg invocations, but only the normal dpkg lock.

  Frontend locking prevents race conditions between multiple dpkg
  frontends, which can cause other frontends to be interrupted while
  they are installing stuff.

  [Test case]
  1. Install a package
  2. Modify prerm to sleep
  3. Remove package via pkcon and check that packagekitd process holds 
lock-frontend and dpkg holds lock (we release lock by closing the lock files, 
so just check if the files are open).

  [Regression potential]
  Changing the code to call UnLockInner() vs UnLock() makes it do less steps 
and only release "lock" as before, and not "lock-frontend". That should not be 
causing any regressions.

  The patch also adds a call to LockInner() after the dpkg execution to
  make it reacquire "lock", this could fail. It should not have much
  impact however, as it only affects a single transaction AFAICT. It
  does reduce the risk of some frontend not implementing frontend
  locking from racing while we still hold the frontend lock, though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1795614/+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 1766839] Re: gio does not delete directory with samba vfs recycle

2018-10-03 Thread Karl Stenerud

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

** This bug is no longer a duplicate of bug 1777601
   can not delete a non-empty directory on remote NAS smb share
** This bug has been marked a duplicate of bug 1795772
   rmdir on non-empty samba directory fails silently

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

Title:
  gio does not delete directory with samba vfs recycle

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  steps to reproduce:
  * create samba share on ubuntu 16.04 with a recycle vfs
  * gio mount share on ubuntu 18.04
  * create directory containing one file.
  * gio remove directory

  outcome:
  no effect.

  expected:
  directory created in recycle directory on server.
  contained file moved to recycle directory.

  extra:
  when file contained in directory is 'gio-removed' file IS moved to recycle 
directory.

  extra:
  whem rm -r is used in /run/user/.../gvfs directory, file and directory are 
moved to recycle directory.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libglib2.0-bin 2.56.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Apr 25 12:06:45 2018
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to bionic on 2013-08-23 (1705 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1766839/+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 1794843] Re: New release of 'gstreamer1.0' (1.14.4)

Laney, by the way, it would be nice if we could get gstreamer 1.14.4
backported to 18.04 LTS.

It is needed to fix YouTube on Epiphany. (Epiphany also needs to be
updated to at least 3.28.5 there for the full fix but you don't need to
worry about doing that.)

https://gitlab.gnome.org/GNOME/epiphany/blob/gnome-3-28/NEWS

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

Title:
  New release of 'gstreamer1.0' (1.14.4)

Status in gstreamer1.0 package in Ubuntu:
  Triaged

Bug description:
  Hello,

  https://packages.debian.org/source/sid/gstreamer1.0

  'Source Package: gstreamer1.0 (1.14.3-1)'

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ---

  https://gstreamer.freedesktop.org/releases/1.14/#1.14.3

  == 1.14.3 ==

  The third 1.14 bug-fix release (1.14.3) was released on 16 September
  2018.

  This release only contains bugfixes and it should be safe to update
  from 1.14.x.

  Highlighted bugfixes in 1.14.3
  opusenc: fix crash on 32-bit platforms
  compositor: fix major buffer leak when doing crossfading on some but not all 
pads
  wasapi: various fixes for wasapisrc and wasapisink regressions
  x264enc: Set bit depth to fix "This build of x264 requires 8-bit depth. 
Rebuild to..." runtime errors with x264 version ≥ 153
  audioaggregator, audiomixer: caps negotiation fixes
  input-selector: latency handling fixes
  playbin, playsink: audio visualization support fixes
  dashdemux: fix possible crash if stream is neither isobmff nor isoff_ondemand 
profile
  opencv: Fix build for opencv >= 3.4.2
  h265parse: miscellaneous fixes backported from h264parse
  pads: fix changing of pad offsets from inside pad probes
  pads: ensure that pads are blocked for IDLE probes if they are called from 
the streaming thread too

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.2-2
  Uname: Linux 4.18.10-gnu x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 27 13:43:05 2018
  InstallationDate: Installed on 2017-10-13 (349 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1794843/+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 1795635] Re: Drop transitional dummy packages for qtquick2 and qttest

** Changed in: unity-api (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: unity-api (Ubuntu)
   Importance: Undecided => High

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

Title:
  Drop transitional dummy packages for qtquick2 and qttest

Status in unity-api package in Ubuntu:
  Triaged

Bug description:
  qtdeclarative5-qtquick2-plugin and qtdeclarative5-test-plugin are just
  transitional dummy packages. Instead use qml-module-qtquick2 and qml-
  module-qttest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-api/+bug/1795635/+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 1795913] [NEW] Systemd Resolver works unreliable to local DNS Names

2018-10-03 Thread Lairsdragon

Public bug reported:

systemd-resolved fails to resolve reliably local DNS names under
home.example.com. The first call succeeds but all following calls fails
to resolve the address correctly:

steve@steve-ThinkPad-T560:~$ systemd-resolve --flush-caches
steve@steve-ThinkPad-T560:~$ systemd-resolve akolus.home.example.com
akolus.home.example.com: 192.168.1.5

-- Information acquired via protocol DNS in 2.7ms.
-- Data is authenticated: no
steve@steve-ThinkPad-T560:~$ systemd-resolve akolus.home.example.com
akolus.home.example.com: resolve call failed: 'akolus.home.example.com' not 
found

A call to systemd-resolve --flush-caches get the next resolvement
working again.

The syslog show following entries

Oct  3 16:44:41 steve-ThinkPad-T560 systemd-resolved[1092]: Flushed all caches.
Oct  3 16:44:41 steve-ThinkPad-T560 systemd-resolved[1092]: Server returned 
error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.

A dig for the adresses  to all DHCP provided DNS Server works:

steve@steve-ThinkPad-T560:~$ dig akolus.home.example.com @192.168.1.1

; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> akolus.home.example.com @192.168.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61886
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;akolus.home.example.com.   IN  A

;; ANSWER SECTION:
akolus.home.example.com. 0  IN  A   192.168.1.5

;; Query time: 0 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Wed Oct 03 16:46:30 CEST 2018
;; MSG SIZE  rcvd: 70

steve@steve-ThinkPad-T560:~$ dig akolus.home.example.com
@2a04:4540:4707:a800::1

; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> akolus.home.example.com 
@2a04:4540:4707:a800::1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24202
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;akolus.home.example.com.   IN  A

;; ANSWER SECTION:
akolus.home.example.com. 0  IN  A   192.168.1.5

;; Query time: 0 msec
;; SERVER: 2a04:4540:4707:a800::1#53(2a04:4540:4707:a800::1)
;; WHEN: Wed Oct 03 16:46:33 CEST 2018
;; MSG SIZE  rcvd: 70

steve@steve-ThinkPad-T560:~$ dig akolus.home.example.com
@fd9c:9819:4c58::1

; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> akolus.home.example.com 
@fd9c:9819:4c58::1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9783
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;akolus.home.example.com.   IN  A

;; ANSWER SECTION:
akolus.home.example.com. 0  IN  A   192.168.1.5

;; Query time: 0 msec
;; SERVER: fd9c:9819:4c58::1#53(fd9c:9819:4c58::1)
;; WHEN: Wed Oct 03 16:46:38 CEST 2018
;; MSG SIZE  rcvd: 70

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Wed Oct  3 15:56:44 2018
InstallationDate: Installed on 2018-03-05 (212 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
MachineType: LENOVO 20FH002RGE
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1KET26W (1.13 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FH002RGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:svnLENOVO:pn20FH002RGE:pvrThinkPadT560:rvnLENOVO:rn20FH002RGE:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T560
dmi.product.name: 20FH002RGE
dmi.product.version: ThinkPad T560
dmi.sys.vendor: LENOVO

** Affects: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1795913

Title:
  Systemd Resolver works unreliable to local DNS Names

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-resolved fails to resolve reliably local DNS names under
  home.example.com. The first call succeeds but all following calls
  fails to resolve t

[Touch-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial

2018-10-03 Thread Nicolas Dichtel

> Note that the iproute2 patch will be needed to use this filter:
> 
> https://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/?id=d5cbf3ff0561
> (embedded headers must be updated also).

This link is dead, here is another one:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=d5cbf3ff0561

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

Title:
  sched: Match-all classifier is missing in xenial

Status in iproute2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This is implemented in linux v4.8 by the following upstream patch:
  bf3994d2ed31 ("net/sched: introduce Match-all classifier")

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31

  The backport is straightforward. It's useful in combination with
  clsact qdisc (see bug #1642510).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+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 1771783] Re: iproute2: frr route protocols are not converted to string on xenial

2018-10-03 Thread Nicolas Dichtel

It works on my side:

$ ./ip/ip r a 2.2.2.0/24 via 10.0.2.123 dev mgmt0 proto 188 metric 20
$ ./ip/ip r | grep 2.2.2
2.2.2.0/24 via 10.0.2.123 dev mgmt0  proto 188  metric 20
$ mkdir -p /etc/iproute2/rt_protos.d
$ echo "188 foo" > /etc/iproute2/rt_protos.d/bar.conf
$ ./ip/ip r | grep 2.2.2
2.2.2.0/24 via 10.0.2.123 dev mgmt0  proto foo  metric 20

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

Title:
  iproute2: frr route protocols are not converted to string on xenial

Status in iproute2 package in Ubuntu:
  New

Bug description:
  FRR puts its own proto numbers when inserting a route, example:
  $ ip route
  [snip]
  2.2.2.0/24 via 3.3.3.2 dev eth2  proto 188  metric 20 

  iproute2 defines some protocols, but not all:
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos

  A patch has been pushed upstream so that external applications can define 
their protocols numbers:
  719e331ff619 ("Add support for rt_protos.d")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+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 1795907] [NEW] In tests %s is not substituted with filename

2018-10-03 Thread Alexander Lazarević

Public bug reported:

The manual of mailcap(5) says that in the test field "The command may be
any UNIX command, using the same syntax and the same %-escapes as for
the viewing command"

So this mailcap entry should be fine:

text/plain; wc '%s'; test=grep -q somepattern %s

I would expect to whenever there's a plain text file that contains the
word somepattern, wc should be invoked by run-mailcap on it. Otherwise
this entry should not be considered by run-mailcap.

What actually happens is that the %s will be substituted for the view
field (wc '%s') but not for the test field and so this entry will be
never considered.

I've included a bash script with testcases to demonstrate the bug.
(Please keep in mind that after all the years I still do consider myself
a bash script novice)

I have no patch. I do not grok perl.

** Affects: mime-support (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: testcase

** Attachment added: "Bash script with testcases"
   
https://bugs.launchpad.net/bugs/1795907/+attachment/5196659/+files/test_test.sh

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

Title:
  In tests %s is not substituted with filename

Status in mime-support package in Ubuntu:
  New

Bug description:
  The manual of mailcap(5) says that in the test field "The command may
  be any UNIX command, using the same syntax and the same %-escapes as
  for the viewing command"

  So this mailcap entry should be fine:

  text/plain; wc '%s'; test=grep -q somepattern %s

  I would expect to whenever there's a plain text file that contains the
  word somepattern, wc should be invoked by run-mailcap on it. Otherwise
  this entry should not be considered by run-mailcap.

  What actually happens is that the %s will be substituted for the view
  field (wc '%s') but not for the test field and so this entry will be
  never considered.

  I've included a bash script with testcases to demonstrate the bug.
  (Please keep in mind that after all the years I still do consider
  myself a bash script novice)

  I have no patch. I do not grok perl.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1795907/+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 1743373] Re: Combobox arrow and color are inverted

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
bionic-3453

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
cosmic-3452

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

Title:
  Combobox arrow and color are inverted

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Open a combobox with plenty of entries. (Example: gnome-terminal ->
  Edit -> Profile Preferences -> Compatibility -> Encoding)

  Notice two bugs:

  1. Both at the top and at the bottom, the arrow (triangle) points
  downwards.

  Expected: At the top, the arrow should point upwards.

  2. Colors of sensitive and insensitive arrows are swapped. The arrow
  is black if you cannot scroll in that direction, gray if hovering
  starts to scroll.

  Expected: It should be black if you can scroll in that direction by
  hovering, and gray if you cannot.

  Adwaita doesn't suffer from either of these issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171115-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Jan 15 13:44:49 2018
  InstallationDate: Installed on 2016-11-09 (431 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-09-21 (115 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1743373/+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 1781736] Re: Typo in assets link for focused buttons in Radiance theme

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
bionic-3453

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
cosmic-3452

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

Title:
  Typo in assets link for focused buttons in Radiance theme

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  There is a typo in the file /usr/share/themes/Radiance/gtk-3.20/gtk-
  widgets.css that causes focused buttons to be drawn incorrectly in the
  radiance theme. The following change should be made to the file to fix
  the incorrect assets link:

  118c118
  <  url("assets/button-focused.png@2"));
  ---
  >  url("assets/button-focu...@2.png"));

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 [modified: 
usr/share/themes/Radiance/gtk-3.20/gtk-widgets.css]
  ProcVersionSignature: Ubuntu 4.15.0-28.30-generic 4.15.18
  Uname: Linux 4.15.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Jul 14 15:41:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-06-23 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1781736/+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 1782038] Re: Window buttons are small in a maximized Chromium window

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
bionic-3453

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
cosmic-3452

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

Title:
  Window buttons are small in a maximized Chromium window

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Repro:
  1. Use the Ambiance or Radiance themes.
  2. Launch a Chromium window.
  3. Maximize.

  The window close, minimize, and restore buttons should be normal-
  sized, but instead appear small.

  This is because the buttons have a padding of 9px on the top and
  bottom, causing Chromium to think they're taller than they really are,
  so it downsizes them to fit the smaller headerbar on the maximized
  window.

  The attached patch removes the padding.  There are no changes in
  behavior in apps other than Chromium.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1782038/+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 1758841] Re: virt-manager: Light grey menu items on light grey background are barely readable

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
bionic-3453

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
cosmic-3452

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

Title:
  virt-manager: Light grey menu items on light grey background are
  barely readable

Status in ubuntu-themes package in Ubuntu:
  In Progress
Status in virt-manager package in Ubuntu:
  Invalid

Bug description:
  With latest update of ubuntu-theme (16.10+18.04.20180322.3-0ubuntu1) menu 
items in the toolbar are barely readable (cf screenshot)
  Background should be dark. virt-manager is the only application I found with 
this issue so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: virt-manager 1:1.5.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 26 09:50:17 2018
  InstallationDate: Installed on 2014-07-15 (1349 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1758841/+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 1761684] Re: Regression in lists like gnome-boxes

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
bionic-3453

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
cosmic-3452

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

Title:
  Regression in lists like gnome-boxes

Status in gnome-boxes package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  The theme regressed the actively selected item on gnome-boxes (hover is also 
hard to read).
  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1761684/+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 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
bionic-3453

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
cosmic-3452

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

Title:
  Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
  builder.css

Status in Ubuntu theme:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Fix Committed

Bug description:
  The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
  line

  @import url("apps/gnome-builder.css");

  But this file does not exist in this package or any other, as far as I
  can tell from apt-file.  This triggers an annoying warning when
  running various applications (e.g. evince):

  (evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
  gtk-main.css:73:38: Failed to import: Error opening file
  /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
  file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 18:58:41 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1773045/+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 1795895] Re: Accelerators on selected menu-items are not visible

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
bionic-3453

** Branch linked: lp:~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-
cosmic-3452

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

Title:
  Accelerators on selected menu-items are not visible

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  As visible in the attached screenshot in the nautilus context menu,
  the accelerator is not readable when the item is selected:
  https://i.imgur.com/xabntIH.png

  [ Test case ]

  1. Open Nautilus
  2. Right-click on the files view
  3. Select an item with an accelerator
  4. The accelerator should be visible (white in Ambiance theme)

  [ Possible regressions ]

  Accelerators on menuitems on menubars might always be painted as when
  hovered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1795895/+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 1743373] Re: Combobox arrow and color are inverted

** Branch linked: lp:~3v1n0/ubuntu-themes/bionic-sru1

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

Title:
  Combobox arrow and color are inverted

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Open a combobox with plenty of entries. (Example: gnome-terminal ->
  Edit -> Profile Preferences -> Compatibility -> Encoding)

  Notice two bugs:

  1. Both at the top and at the bottom, the arrow (triangle) points
  downwards.

  Expected: At the top, the arrow should point upwards.

  2. Colors of sensitive and insensitive arrows are swapped. The arrow
  is black if you cannot scroll in that direction, gray if hovering
  starts to scroll.

  Expected: It should be black if you can scroll in that direction by
  hovering, and gray if you cannot.

  Adwaita doesn't suffer from either of these issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171115-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Jan 15 13:44:49 2018
  InstallationDate: Installed on 2016-11-09 (431 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-09-21 (115 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1743373/+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 1758841] Re: virt-manager: Light grey menu items on light grey background are barely readable

** Branch linked: lp:~3v1n0/ubuntu-themes/bionic-sru1

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

Title:
  virt-manager: Light grey menu items on light grey background are
  barely readable

Status in ubuntu-themes package in Ubuntu:
  In Progress
Status in virt-manager package in Ubuntu:
  Invalid

Bug description:
  With latest update of ubuntu-theme (16.10+18.04.20180322.3-0ubuntu1) menu 
items in the toolbar are barely readable (cf screenshot)
  Background should be dark. virt-manager is the only application I found with 
this issue so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: virt-manager 1:1.5.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 26 09:50:17 2018
  InstallationDate: Installed on 2014-07-15 (1349 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1758841/+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 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css

** Branch linked: lp:~3v1n0/ubuntu-themes/bionic-sru1

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

Title:
  Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
  builder.css

Status in Ubuntu theme:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Fix Committed

Bug description:
  The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
  line

  @import url("apps/gnome-builder.css");

  But this file does not exist in this package or any other, as far as I
  can tell from apt-file.  This triggers an annoying warning when
  running various applications (e.g. evince):

  (evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
  gtk-main.css:73:38: Failed to import: Error opening file
  /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
  file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 18:58:41 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1773045/+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 1761684] Re: Regression in lists like gnome-boxes

** Branch linked: lp:~3v1n0/ubuntu-themes/bionic-sru1

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

Title:
  Regression in lists like gnome-boxes

Status in gnome-boxes package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  The theme regressed the actively selected item on gnome-boxes (hover is also 
hard to read).
  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1761684/+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 1781736] Re: Typo in assets link for focused buttons in Radiance theme

** Branch linked: lp:~3v1n0/ubuntu-themes/bionic-sru1

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

Title:
  Typo in assets link for focused buttons in Radiance theme

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  There is a typo in the file /usr/share/themes/Radiance/gtk-3.20/gtk-
  widgets.css that causes focused buttons to be drawn incorrectly in the
  radiance theme. The following change should be made to the file to fix
  the incorrect assets link:

  118c118
  <  url("assets/button-focused.png@2"));
  ---
  >  url("assets/button-focu...@2.png"));

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 [modified: 
usr/share/themes/Radiance/gtk-3.20/gtk-widgets.css]
  ProcVersionSignature: Ubuntu 4.15.0-28.30-generic 4.15.18
  Uname: Linux 4.15.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Jul 14 15:41:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-06-23 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1781736/+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 1782038] Re: Window buttons are small in a maximized Chromium window

** Branch linked: lp:~3v1n0/ubuntu-themes/bionic-sru1

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

Title:
  Window buttons are small in a maximized Chromium window

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Repro:
  1. Use the Ambiance or Radiance themes.
  2. Launch a Chromium window.
  3. Maximize.

  The window close, minimize, and restore buttons should be normal-
  sized, but instead appear small.

  This is because the buttons have a padding of 9px on the top and
  bottom, causing Chromium to think they're taller than they really are,
  so it downsizes them to fit the smaller headerbar on the maximized
  window.

  The attached patch removes the padding.  There are no changes in
  behavior in apps other than Chromium.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1782038/+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 1795895] Re: Accelerators on selected menu-items are not visible

** Branch linked: lp:~3v1n0/ubuntu-themes/bionic-sru1

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

Title:
  Accelerators on selected menu-items are not visible

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  As visible in the attached screenshot in the nautilus context menu,
  the accelerator is not readable when the item is selected:
  https://i.imgur.com/xabntIH.png

  [ Test case ]

  1. Open Nautilus
  2. Right-click on the files view
  3. Select an item with an accelerator
  4. The accelerator should be visible (white in Ambiance theme)

  [ Possible regressions ]

  Accelerators on menuitems on menubars might always be painted as when
  hovered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1795895/+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 1782038] Re: Window buttons are small in a maximized Chromium window

2018-10-03 Thread Treviño

Thanks for the patch, that was fine for chrome, but it broke the
activation area for other apps, so I've reduced the selector to only
chrom{e,ium} buttons.

** Summary changed:

- [Patch included] Window buttons are small in a maximized Chromium window
+ Window buttons are small in a maximized Chromium window

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

Title:
  Window buttons are small in a maximized Chromium window

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Repro:
  1. Use the Ambiance or Radiance themes.
  2. Launch a Chromium window.
  3. Maximize.

  The window close, minimize, and restore buttons should be normal-
  sized, but instead appear small.

  This is because the buttons have a padding of 9px on the top and
  bottom, causing Chromium to think they're taller than they really are,
  so it downsizes them to fit the smaller headerbar on the maximized
  window.

  The attached patch removes the padding.  There are no changes in
  behavior in apps other than Chromium.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1782038/+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 1795899] [NEW] Update grilo-plugins to 0.3.8

Public bug reported:

This is required by gnome-music 3.30.1. (We already have gnome-music
3.30.0).

https://gitlab.gnome.org/GNOME/grilo-plugins/blob/master/NEWS

** Affects: grilo-plugins (Ubuntu)
 Importance: Wishlist
 Status: Fix Committed


** Tags: cosmic upgrade-software-version

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

Title:
  Update grilo-plugins to 0.3.8

Status in grilo-plugins package in Ubuntu:
  Fix Committed

Bug description:
  This is required by gnome-music 3.30.1. (We already have gnome-music
  3.30.0).

  https://gitlab.gnome.org/GNOME/grilo-plugins/blob/master/NEWS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1795899/+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 1795895] Re: Accelerators on selected menu-items are not visible

2018-10-03 Thread Eduardo Brandão de Santana Barros de Souza

** Branch linked: lp:~3v1n0/ubuntu-themes/cosmic-fixes

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

Title:
  Accelerators on selected menu-items are not visible

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  As visible in the attached screenshot in the nautilus context menu,
  the accelerator is not readable when the item is selected:
  https://i.imgur.com/xabntIH.png

  [ Test case ]

  1. Open Nautilus
  2. Right-click on the files view
  3. Select an item with an accelerator
  4. The accelerator should be visible (white in Ambiance theme)

  [ Possible regressions ]

  Accelerators on menuitems on menubars might always be painted as when
  hovered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1795895/+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 1795895] [NEW] Accelerators on selected menu-items are not visible

2018-10-03 Thread Treviño

Public bug reported:

[ Impact ]

As visible in the attached screenshot in the nautilus context menu, the
accelerator is not readable when the item is selected:
https://i.imgur.com/xabntIH.png

[ Test case ]

1. Open Nautilus
2. Right-click on the files view
3. Select an item with an accelerator
4. The accelerator should be visible (white in Ambiance theme)

[ Possible regressions ]

Accelerators on menuitems on menubars might always be painted as when
hovered

** Affects: ubuntu-themes (Ubuntu)
 Importance: Low
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

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

Title:
  Accelerators on selected menu-items are not visible

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  As visible in the attached screenshot in the nautilus context menu,
  the accelerator is not readable when the item is selected:
  https://i.imgur.com/xabntIH.png

  [ Test case ]

  1. Open Nautilus
  2. Right-click on the files view
  3. Select an item with an accelerator
  4. The accelerator should be visible (white in Ambiance theme)

  [ Possible regressions ]

  Accelerators on menuitems on menubars might always be painted as when
  hovered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1795895/+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 1795894] [NEW] package software-properties-common 0.96.24.32.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar

2018-10-03 Thread Alfredo EW

Public bug reported:

I can not install chrome

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: software-properties-common 0.96.24.32.5
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
AptOrdering:
 google-chrome-stable:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Oct  3 08:27:14 2018
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2018-10-03 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: software-properties
Title: package software-properties-common 0.96.24.32.5 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package software-properties-common 0.96.24.32.5 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

Status in software-properties package in Ubuntu:
  New

Bug description:
  I can not install chrome

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: software-properties-common 0.96.24.32.5
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   google-chrome-stable:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Oct  3 08:27:14 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2018-10-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: software-properties
  Title: package software-properties-common 0.96.24.32.5 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795894/+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 1794843] Re: New release of 'gstreamer1.0' (1.14.4)

2018-10-03 Thread Cristian Aravena Romero

** Summary changed:

- New release of 'gstreamer1.0' (1.14.3-1) in Debian
+ New release of 'gstreamer1.0' (1.14.4)

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

Title:
  New release of 'gstreamer1.0' (1.14.4)

Status in gstreamer1.0 package in Ubuntu:
  Triaged

Bug description:
  Hello,

  https://packages.debian.org/source/sid/gstreamer1.0

  'Source Package: gstreamer1.0 (1.14.3-1)'

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ---

  https://gstreamer.freedesktop.org/releases/1.14/#1.14.3

  == 1.14.3 ==

  The third 1.14 bug-fix release (1.14.3) was released on 16 September
  2018.

  This release only contains bugfixes and it should be safe to update
  from 1.14.x.

  Highlighted bugfixes in 1.14.3
  opusenc: fix crash on 32-bit platforms
  compositor: fix major buffer leak when doing crossfading on some but not all 
pads
  wasapi: various fixes for wasapisrc and wasapisink regressions
  x264enc: Set bit depth to fix "This build of x264 requires 8-bit depth. 
Rebuild to..." runtime errors with x264 version ≥ 153
  audioaggregator, audiomixer: caps negotiation fixes
  input-selector: latency handling fixes
  playbin, playsink: audio visualization support fixes
  dashdemux: fix possible crash if stream is neither isobmff nor isoff_ondemand 
profile
  opencv: Fix build for opencv >= 3.4.2
  h265parse: miscellaneous fixes backported from h264parse
  pads: fix changing of pad offsets from inside pad probes
  pads: ensure that pads are blocked for IDLE probes if they are called from 
the streaming thread too

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.2-2
  Uname: Linux 4.18.10-gnu x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 27 13:43:05 2018
  InstallationDate: Installed on 2017-10-13 (349 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1794843/+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 1795887] [NEW] package libgmp10 2:6.1.2+dfsg-2 failed to install/upgrade: não pode aceder ao arquivo '/tmp/apt-dpkg-install-8qkSxG/028-libgmp10_2%3a6.1.2+dfsg-2_i386.deb': Arquiv

Public bug reported:

Message error

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libgmp10 2:6.1.2+dfsg-2
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Wed Oct  3 09:05:41 2018
Dependencies:
 gcc-8-base 8.2.0-1ubuntu2~18.04
 libc6 2.27-3ubuntu1
 libgcc1 1:8.2.0-1ubuntu2~18.04
ErrorMessage: não pode aceder ao arquivo 
'/tmp/apt-dpkg-install-8qkSxG/028-libgmp10_2%3a6.1.2+dfsg-2_i386.deb': Arquivo 
ou diretório inexistente
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: gmp
Title: package libgmp10 2:6.1.2+dfsg-2 failed to install/upgrade: não pode 
aceder ao arquivo 
'/tmp/apt-dpkg-install-8qkSxG/028-libgmp10_2%3a6.1.2+dfsg-2_i386.deb': Arquivo 
ou diretório inexistente
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libgmp10 2:6.1.2+dfsg-2 failed to install/upgrade: não pode
  aceder ao arquivo '/tmp/apt-dpkg-install-8qkSxG/028-libgmp10_2%3a6.1.2
  +dfsg-2_i386.deb': Arquivo ou diretório inexistente

Status in gmp package in Ubuntu:
  New

Bug description:
  Message error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgmp10 2:6.1.2+dfsg-2
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Wed Oct  3 09:05:41 2018
  Dependencies:
   gcc-8-base 8.2.0-1ubuntu2~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.2.0-1ubuntu2~18.04
  ErrorMessage: não pode aceder ao arquivo 
'/tmp/apt-dpkg-install-8qkSxG/028-libgmp10_2%3a6.1.2+dfsg-2_i386.deb': Arquivo 
ou diretório inexistente
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: gmp
  Title: package libgmp10 2:6.1.2+dfsg-2 failed to install/upgrade: não pode 
aceder ao arquivo 
'/tmp/apt-dpkg-install-8qkSxG/028-libgmp10_2%3a6.1.2+dfsg-2_i386.deb': Arquivo 
ou diretório inexistente
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gmp/+bug/1795887/+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 1761684] Re: Regression in lists like gnome-boxes

2018-10-03 Thread Treviño

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Low

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Regression in lists like gnome-boxes

Status in gnome-boxes package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  The theme regressed the actively selected item on gnome-boxes (hover is also 
hard to read).
  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1761684/+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 1761684] Re: Regression in lists like gnome-boxes

** Branch linked: lp:~3v1n0/ubuntu-themes/cosmic-fixes

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

Title:
  Regression in lists like gnome-boxes

Status in gnome-boxes package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  The theme regressed the actively selected item on gnome-boxes (hover is also 
hard to read).
  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1761684/+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 1794843] Re: New release of 'gstreamer1.0' (1.14.3-1) in Debian

2018-10-03 Thread Cristian Aravena Romero

Hello,

https://gstreamer.freedesktop.org/releases/1.14/#1.14.4

The fourth 1.14 bug-fix release (1.14.4) was released on 2 October 2018.

This release only contains bugfixes and it should be safe to update from
1.14.x.

Highlighted bugfixes in 1.14.4
glviewconvert: wait and set the gl sync meta on buffers
glviewconvert: Copy composition meta from the primary buffer to both outputs
glcolorconvert: Don't copy overlay composition meta over to NULL outbufs
matroskademux: add functionality needed for MSE use case fixing youtube 
playback in epiphany/webkit-gtk
msdk: fix build on windows
opusenc: fix another crash on 32-bit x86 on windows (alignment issue in SSE 
optimisations)
osxaudio: add support for parsing more channel layouts
tagdemux: Use upstream GST_EVENT_STREAM_START (and stream-id) if present
vorbisdec: fix header handling regression: init decoder immediately once we 
have headers
wasapisink: recover from low buffer levels in shared mode
fix GstSegment unit test which would fail on some 32-bit x86 CPUs

Best regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  New release of 'gstreamer1.0' (1.14.3-1) in Debian

Status in gstreamer1.0 package in Ubuntu:
  Triaged

Bug description:
  Hello,

  https://packages.debian.org/source/sid/gstreamer1.0

  'Source Package: gstreamer1.0 (1.14.3-1)'

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ---

  https://gstreamer.freedesktop.org/releases/1.14/#1.14.3

  == 1.14.3 ==

  The third 1.14 bug-fix release (1.14.3) was released on 16 September
  2018.

  This release only contains bugfixes and it should be safe to update
  from 1.14.x.

  Highlighted bugfixes in 1.14.3
  opusenc: fix crash on 32-bit platforms
  compositor: fix major buffer leak when doing crossfading on some but not all 
pads
  wasapi: various fixes for wasapisrc and wasapisink regressions
  x264enc: Set bit depth to fix "This build of x264 requires 8-bit depth. 
Rebuild to..." runtime errors with x264 version ≥ 153
  audioaggregator, audiomixer: caps negotiation fixes
  input-selector: latency handling fixes
  playbin, playsink: audio visualization support fixes
  dashdemux: fix possible crash if stream is neither isobmff nor isoff_ondemand 
profile
  opencv: Fix build for opencv >= 3.4.2
  h265parse: miscellaneous fixes backported from h264parse
  pads: fix changing of pad offsets from inside pad probes
  pads: ensure that pads are blocked for IDLE probes if they are called from 
the streaming thread too

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libgstreamer1.0-0 1.14.2-2
  Uname: Linux 4.18.10-gnu x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 27 13:43:05 2018
  InstallationDate: Installed on 2017-10-13 (349 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1794843/+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 382938] Re: ufw should be enabled by default

2018-10-03 Thread Ubuntu Foundations Team Bug Bot

The attachment "Fix default values to enable ufw and set logging off,
and start the firewall for fresh installs" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  ufw should be enabled by default

Status in ufw:
  Invalid
Status in ufw package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: ufw

  ufw should be enabled by default in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/382938/+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 1795697] Re: Danish translation probably not synchronizing

2018-10-03 Thread Ask Hjorth Larsen

Looks like the gnome-software bug mentioned above was a false alarm.
But the Gtk module has indeed not imported those translations that were
present upstream at the time of the GNOME release deadline.  It is
essential that these imports are triggered correctly, else we will
either get duplicate work on the part of translators or ship a
distribution which is not fully translated.

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

Title:
  Danish translation probably not synchronizing

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  The Danish translation here is not complete:

  
https://translations.launchpad.net/ubuntu/cosmic/+source/gtk+3.0/+pots/gtk-3.0/da/+details

  However we always fully translate GNOME upstream for each release, so
  it should be complete.

  Something is probably wrong with the import queue again.

  See also https://bugs.launchpad.net/ubuntu/+source/gnome-
  software/+bug/1795695

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1795697/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)

2018-10-03 Thread Mario Vukelic

No stop, disregard, SORRY!!!
I don't know how, but I messed up, the update was not installed and I misread 
some check.
Now I definitely do have the update installed and IT WORKS on the Asus.

It still breaks the Dell though :)

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

Title:
  Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in
  gnome-shell (X or Wayland) but working on console (Cosmic 18.10)

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  Please forgive if filed for wrong package. Problem occurs in X and
  Wayland sessions but not on console, so does not seem to be kernel.

  Repro on Asus UX561UD with Ubuntu 18.10 up to date:
  1. Log into Gnome X or Gnome Wayland session
  2. Press Fn+F2 which is the airplane mode key

  -> Airplane mode should turn on but nothing happens

  3. Switch to console with Ctrl+Alt+F3
  4. Log into console
  5. Press Fn+F2 again
  6. Switch back to GUI session with Ctrl+Alt+F2

  -> Airplane mode is on, icon appeared in Gnome task bar

  Same for turning it off.

  No difference when booting 18.04.1 live image

  This laptop seems not the only one with this problem. I got the idea for 
trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately 
there is no solution there:
  https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond

  Please let me know whatever I can do to help debug this.

  All other Fn+Fx special keys on this laptop work (display brightness,
  touchpad off, sound etc.) except for keyboard backlight, but that
  works with Ubuntu 18.04.1 and I will file a separate bug for this

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 21:37:01 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee]
     Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:14ee]
  InstallationDate: Installed on 2018-09-05 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 13d3:5256 IMC Networks
   Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX561UD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX561UD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX561UD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: UX561UD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  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/xkeyboard-config/+bug/1791367/+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 1795226] Re: package tzdata 2018e-0ubuntu0.18.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128