[Touch-packages] [Bug 1754692] Re: [regression] Tabs in Settings of Thunderbird not visible

2018-03-11 Thread Daniel van Vugt
** 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/1754692

Title:
  [regression] Tabs in Settings of Thunderbird not visible

Status in thunderbird package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  I am on Ubuntu 18.04 Bionic right now and noticed a little theme
  missbehavior. (i think)

  >> Open 'Thunderbird'...go into 'Settings'...go to 'Security' (for
  example)

  There the Tabs below (Junk, Password, ...) are not visible.
  There is just text with no background (see screenhot)

  
  Sidenote: The same i noticed on Xubuntu with greybird-theme. But with other 
themes (numix, arc) they are visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.389
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 15:26:35 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1754692/+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 1603183] Re: Bottom right area of touchpad no longer treated as right click

2018-03-11 Thread Daniel van Vugt
Triaged, thanks to comment #18.

Upstream bug:
https://bugs.freedesktop.org/show_bug.cgi?id=105446

** Bug watch added: freedesktop.org Bugzilla #105446
   https://bugs.freedesktop.org/show_bug.cgi?id=105446

** Also affects: libinput via
   https://bugs.freedesktop.org/show_bug.cgi?id=105446
   Importance: Unknown
   Status: Unknown

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

** Changed in: libinput (Ubuntu)
   Status: New => Triaged

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

Title:
  Bottom right area of touchpad no longer treated as right click

Status in Canonical System Image:
  Fix Released
Status in libinput:
  Confirmed
Status in Mir:
  Triaged
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Fix Released
Status in libinput package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Using the touchpad I was not able to trigger any right click (with a
  single finger in the bottom right area), and I tought it was a problem
  of how unity8 handled the right clicks. Instead I just tried with a
  mouse and right click trigger different actions from left clicks.

  In the end the problem is that my touchpad right click is considered a
  left click by the system. This does not happen with an usb mouse.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603183/+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 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

2018-03-11 Thread Gunnar Hjalmarsson
Let's consider this completed now, and open new bugs for possible
issues.

** Changed in: language-selector (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Switch to Noto Sans as default font for Japanese and/or Korean?

Status in language-selector package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu 16.04 Noto Sans CJK is the default font for rendering
  Chinese. After having struggled with a few issues, I believe that we
  finally achieved the desired improvement of the rendering experience.

  So now I ask: Is there an interest from Japanese and Korean users to
  consider a switch to Noto Sans? (The fonts are already installed for
  all users on Ubuntu 16.04.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-03-11 Thread Branchus
I have a different issue.

it happened in Arch linux, Manjaro, Ubuntu 18.04 beta. if I didn't
install the nvidia 390 driver, everything run smooth, after I installed
nvidia 390 driver, I have no problem with GUI, however, the system
doesn't turn off, restart itself properly. my monitor goes into sleep
(power saving mode - no signal) while the fan and all leds are still on.

I initially thought it is a kernel or systemd issue, after asking
questions on different forums and trying different distros, I think now
I confirm it is a display driver issue.

my graphic card is nvidia quodra k2200

anyone got the same issue?

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1742123] Re: obscure slapd configuration

2018-03-11 Thread Launchpad Bug Tracker
[Expired for openldap (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  obscure slapd configuration

Status in openldap package in Ubuntu:
  Expired

Bug description:
  Hi,

  the openldap server slapd comes with two configuration options, the
  old one based on slapd.conf, and a new one based on ldifs.

  The debian/ubuntu package performs some obscure magic to generate a
  ldif based config in /etc/slapd/slapd.d, but does not provide any hint
  or documentation about how to change/adjust it. E.g. if the package
  was installed non-interactively through puppet or ansible, it is not
  obvious where the root password comes from or how to change it or how
  to re-setup.

  Furthermore it is a security gap to create something like

  dn: dc=buero,dc=danisch,dc=de
  objectClass: top
  objectClass: dcObject
  objectClass: organization
  o: buero.danisch.de
  dc: buero
  structuralObjectClass: organization
  entryUUID: 4f765744-85aa-1037-9ee9-1db94ae2a6d4
  creatorsName: cn=admin,dc=buero,dc=danisch,dc=de
  createTimestamp: 20180104145011Z
  entryCSN: 20180104145011.817411Z#00#000#00
  modifiersName: cn=admin,dc=buero,dc=danisch,dc=de
  modifyTimestamp: 20180104145011Z

  dn: cn=admin,dc=buero,dc=danisch,dc=de
  objectClass: simpleSecurityObject
  objectClass: organizationalRole
  cn: admin
  description: LDAP administrator
  userPassword:: e1NTSEF9aUlUVXlxNE9ZWFFuZjA1ejhqem0yWnJpY09xaGxBc0Y=
  structuralObjectClass: organizationalRole
  entryUUID: 4f79fd9a-85aa-1037-9eea-1db94ae2a6d4
  creatorsName: cn=admin,dc=buero,dc=danisch,dc=de
  createTimestamp: 20180104145011Z
  entryCSN: 20180104145011.841518Z#00#000#00
  modifiersName: cn=admin,dc=buero,dc=danisch,dc=de
  modifyTimestamp: 20180104145011Z

  and

  olcRootDN: cn=admin,dc=buero,dc=danisch,dc=de
  olcRootPW:: e1NTSEF9aUlUVXlxNE9ZWFFuZjA1ejhqem0yWnJpY09xaGxBc0Y=

  
  that contains an admin password without me ever having set it or having a 
randomly generated one.

  Since I do not see how to cleanly change this with ldapmodify, I do
  not see an option to remove this all and restart with an old-style
  slapd.conf.

  
  regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1742123/+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 1754836] Re: Failed to activate service

2018-03-11 Thread Daniel van Vugt
The 25 second delay is a standard dbus timeout. I assume you're talking
about:

Mar 10 11:30:25 username-MBB-44608 pulseaudio[1308]: [pulseaudio] pid.c: Daemon 
already running.
Mar 10 11:30:49 username-MBB-44608 pulseaudio[1150]: [pulseaudio] 
bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: 
Failed to activate service 'org.bluez': timed out 
(service_start_timeout=25000ms)

It sounds like maybe your system is launching too many instances of
pulseaudio. The first works and the second fails. I'm not sure how
Xubuntu differs in this respect but I don't think we see the same bug in
standard Ubuntu.

** Summary changed:

- Failed to activate service 
+ Xubuntu: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': 
timed out (service_start_timeout=25000ms)

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Xubuntu: [pulseaudio] bluez5-util.c: GetManagedObjects() failed:
  org.freedesktop.DBus.Error.TimedOut: Failed to activate service
  'org.bluez': timed out (service_start_timeout=25000ms)

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Possibly also causing the long time to desktop from try/install
  livesession dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:
   
  rfkill:
   
  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]:   
[1520681416.8951] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+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 1740273] Re: package libpam-systemd:amd64 229-4ubuntu21 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

2018-03-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package libpam-systemd:amd64 229-4ubuntu21 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  error al iniciar

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpam-systemd:amd64 229-4ubuntu21
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  AptOrdering:
   freetuxtv: Install
   libpam-systemd: Configure
   ubuntu-standard: Configure
   freetuxtv: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Dec 23 18:34:47 2017
  DpkgHistoryLog:
   Start-Date: 2017-12-23  18:34:40
   Commandline: aptdaemon role='role-install-packages' sender=':1.53'
   Install: freetuxtv:amd64 (0.6.6~dfsg1-1)
  DuplicateSignature:
   package:libpam-systemd:amd64:229-4ubuntu21
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package libpam-systemd:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-09-19 (97 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 229-4ubuntu21 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1740273/+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 1754692] Re: [regression] Tabs in Settings of Thunderbird not visible

2018-03-11 Thread Daniel van Vugt
Yeah.

It's fine in 16.04 and broken in 18.04. Not quite sure when it broke.

** Summary changed:

- Tabs in Settings of Thunderbird not visible
+ [regression] Tabs in Settings of Thunderbird not visible

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

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [regression] Tabs in Settings of Thunderbird not visible

Status in thunderbird package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  I am on Ubuntu 18.04 Bionic right now and noticed a little theme
  missbehavior. (i think)

  >> Open 'Thunderbird'...go into 'Settings'...go to 'Security' (for
  example)

  There the Tabs below (Junk, Password, ...) are not visible.
  There is just text with no background (see screenhot)

  
  Sidenote: The same i noticed on Xubuntu with greybird-theme. But with other 
themes (numix, arc) they are visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.389
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 15:26:35 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1754692/+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 1754692] Re: Tabs in Settings of Thunderbird not visible

2018-03-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  [regression] Tabs in Settings of Thunderbird not visible

Status in thunderbird package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  I am on Ubuntu 18.04 Bionic right now and noticed a little theme
  missbehavior. (i think)

  >> Open 'Thunderbird'...go into 'Settings'...go to 'Security' (for
  example)

  There the Tabs below (Junk, Password, ...) are not visible.
  There is just text with no background (see screenhot)

  
  Sidenote: The same i noticed on Xubuntu with greybird-theme. But with other 
themes (numix, arc) they are visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.389
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 15:26:35 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1754692/+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 1754692] Re: Tabs in Settings of Thunderbird not visible

2018-03-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [regression] Tabs in Settings of Thunderbird not visible

Status in thunderbird package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  I am on Ubuntu 18.04 Bionic right now and noticed a little theme
  missbehavior. (i think)

  >> Open 'Thunderbird'...go into 'Settings'...go to 'Security' (for
  example)

  There the Tabs below (Junk, Password, ...) are not visible.
  There is just text with no background (see screenhot)

  
  Sidenote: The same i noticed on Xubuntu with greybird-theme. But with other 
themes (numix, arc) they are visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.389
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 15:26:35 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1754692/+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 1754692] Re: Tabs in Settings of Thunderbird not visible

2018-03-11 Thread Daniel van Vugt
** Also affects: thunderbird (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [regression] Tabs in Settings of Thunderbird not visible

Status in thunderbird package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  I am on Ubuntu 18.04 Bionic right now and noticed a little theme
  missbehavior. (i think)

  >> Open 'Thunderbird'...go into 'Settings'...go to 'Security' (for
  example)

  There the Tabs below (Junk, Password, ...) are not visible.
  There is just text with no background (see screenhot)

  
  Sidenote: The same i noticed on Xubuntu with greybird-theme. But with other 
themes (numix, arc) they are visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.389
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 15:26:35 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1754692/+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 1569068] Re: mate-settings-daemon: ERROR: pulse/glib-mainloop.c:407: glib_defer_free: assertion failed: (!e->dead)

2018-03-11 Thread Daniel van Vugt
Also mention 'mate-settings-daemon' so other people can find the bug,
for now.

** Summary changed:

- 
/usr/bin/mate-settings-daemon:ERROR:pulse/glib-mainloop.c:407:glib_defer_free: 
assertion failed: (!e->dead)
+ mate-settings-daemon: ERROR: pulse/glib-mainloop.c:407: glib_defer_free: 
assertion failed: (!e->dead)

** Also affects: mate-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  mate-settings-daemon: ERROR: pulse/glib-mainloop.c:407:
  glib_defer_free: assertion failed: (!e->dead)

Status in mate-settings-daemon package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-settings-daemon.  This problem was most recently seen
  with version 1.12.1-2build1, the problem page at
  https://errors.ubuntu.com/problem/1b3afc018f02173501b79b75651ec747d69300b7
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-settings-daemon/+bug/1569068/+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 1627564] Re: crash due to assertion in ensure_surface_for_gicon

2018-03-11 Thread Daniel van Vugt
** Tags added: artful

** Summary changed:

- crash due to assertion in ensure_surface_for_gicon
+ Crash due to assertion failure in ensure_surface_for_gicon 
[gtkiconhelper.c:493]

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

Title:
  Crash due to assertion failure in ensure_surface_for_gicon
  [gtkiconhelper.c:493]

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  bubble opened up indicating there was a failure during the latest
  update.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.4.0-9136-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  Date: Sun Sep 25 20:37:06 2016
  ExecutablePath: /usr/sbin/lightdm-gtk-greeter
  InstallationDate: Installed on 2016-08-04 (52 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
  ProcCmdline: /usr/sbin/lightdm-gtk-greeter
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: lightdm-gtk-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
   [greeter]
   theme-name = Lubuntu-dark-panel
  mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 
2016-08-14T22:33:57.293011

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1627564/+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 1366418] Re: Bluetooth BCM43142A0 doesn’t work

2018-03-11 Thread Daniel van Vugt
** Tags added: xenial

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

Title:
  Bluetooth BCM43142A0 doesn’t work

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
  (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
  displayed in the menu bar, if I open the bluetooth UI and switch on,
  nothing happens and the result of “hcitool dev” is empty.

  I have tried to install the windows driver with ndiswrapper, and the
  bluetooth device seems to be detected as an usb bluetooth device but
  still not working. I then add the device to the bluetooth usb device
  and was able to activate bluetooth in the UI but it does not detect
  any other devices (I’ve tested with a smartphone).

  The driver I have installed can be found in asus page =>
  http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
  Select Windows OS, then “bluetooth” section, take the Broadcom driver
  (should be the first one).

  If you extract this archive, you will find a file named “bcbtums-
  win8x64-brcm.inf” which I installed using the following command:

  ndiswrapper -i bcbtums-win8x64-brcm.inf

  Then, the result of “ndiswrapper -l” is:

  bcbtums-win8x64-brcm : driver installed
device (04CA:2006) present

  in usb-devices, I find a device which was not present before
  installation (I might have activated btusb before on this paste):

  T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=04ca ProdID=2006 Rev=01.12
  S:  Manufacturer=Broadcom Corp
  S:  Product=BCM43142A0
  S:  SerialNumber=B8EE6593D989
  C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

  then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
  can switch usb on, but no device will be detected and I’ve found this
  in the dmesg:

  [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout

  which looks pretty much like a “bluetooth not working” message which I
  don’t understand in details.

  I leave here my full dmesg:

  [0.253889] NetLabel:  domain hash size = 128
  [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
  [0.253901] NetLabel:  unlabeled traffic allowed by default
  [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
  [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
  [0.255995] Switched to clocksource hpet
  [0.260468] AppArmor: AppArmor Filesystem Enabled
  [0.260488] pnp: PnP ACPI init
  [0.260500] ACPI: bus type PNP registered
  [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved
  [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
  [0.260642] pnp 00:01: [dma 4]
  [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
  [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
  [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
  [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
  [0.260927] system 00:04: [io  0x] has been reserved
  [0.260928] system 00:04: [io  0x] has been reserved
  [0.260930] system 00:04: [io  0x] has been reserved
  [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
  [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
  [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
  [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
  [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
  [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
  [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
  [0.261012] system 00:06: [io  0x1854-0x1857] has been reserved
  [0.261014] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 
(active)
  [0.261059] system 00:07: [io  0x04d0-0x04d1] has been reserved
  [0.261061] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.261089] system 00:08: [io  0x0240-0x0259] has been reserved
  [0.261091] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.261144] pnp 00:09: Plug and Play ACPI device, IDs FLT0101 SYN0a00 
SYN0002 PNP0f03 PNP0f13 PNP0f12 (active)
  [0.261179] pnp 00:0a: Plug and Play ACPI device, 

[Touch-packages] [Bug 1750973] Re: Program sub menus dark gray on black, thus illegible

2018-03-11 Thread Nick Gammon
This issue (which did not occur with a fresh install of 16.04) appears
to be related to the contents of file:
/usr/share/themes/Ambiance/gtk-2.0/gtkrc

At line 346 (at present) there is the following:

style "menu" = "dark" {

Changing it to:

style "menu" {

... resolves this particular issue, however I'm not sure what side-
effects that would have. In the original release the line was like that
in the first place, so it would have been changed for a reason.

Screenshots of "before" and "after" that change can be seen here:

https://askubuntu.com/a/1014016/425017

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

Title:
  Program sub menus dark gray on black, thus illegible

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When using a program, for example Libre Writer, when I click on file,
  open, then in the Open menu box I have the opportunity to change the
  file type from "All files" to a specific file type, when I click on
  "All files" the selection list appears. The font color for the
  different file types is a dark grey on a black background making the
  list items illegible. As I move the cursor, the font color and
  background change to "normal" black on a white background but only for
  the item that the cursor is hovering over at that moment. This makes
  the rest of the list impossible to read and moving the cursor slowly
  down the list, pausing to read each item, is a very cumbersome way to
  get things done.

  This doesn't just happen on Libre Writer but also Inkscape, Geeqie,
  and a variety of other programs and their sub menus. The only program
  I could find where this didn't happen was Firefox (58.02). Furthermore
  this happens on 3 different machines, each with a different processor,
  different graphics card and where the machine has multiple monitors,
  it happens on all monitors.

  All machines are running 16.04, one with the latest updates, the
  others slightly behind on updates. If I go to Settings-Appearance-
  Theme and change the theme from Ambiance to anything else, the sub
  menus become legible again.  Ambiance is the default theme.   If I
  switch the Theme back to Ambiance the problem resumes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Feb 21 20:57:30 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: sysdig, 0.20.0, 4.4.0-112-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1033]
  InstallationDate: Installed on 2014-04-20 (1404 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=8f4996c0-c2f5-449f-a35c-47f301f66803 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: 970 Extreme3
  dmi.board.vendor: ASRock
  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.:bvrP1.70:bd10/12/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: 

[Touch-packages] [Bug 1750973] Re: Program sub menus dark gray on black, thus illegible

2018-03-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Program sub menus dark gray on black, thus illegible

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When using a program, for example Libre Writer, when I click on file,
  open, then in the Open menu box I have the opportunity to change the
  file type from "All files" to a specific file type, when I click on
  "All files" the selection list appears. The font color for the
  different file types is a dark grey on a black background making the
  list items illegible. As I move the cursor, the font color and
  background change to "normal" black on a white background but only for
  the item that the cursor is hovering over at that moment. This makes
  the rest of the list impossible to read and moving the cursor slowly
  down the list, pausing to read each item, is a very cumbersome way to
  get things done.

  This doesn't just happen on Libre Writer but also Inkscape, Geeqie,
  and a variety of other programs and their sub menus. The only program
  I could find where this didn't happen was Firefox (58.02). Furthermore
  this happens on 3 different machines, each with a different processor,
  different graphics card and where the machine has multiple monitors,
  it happens on all monitors.

  All machines are running 16.04, one with the latest updates, the
  others slightly behind on updates. If I go to Settings-Appearance-
  Theme and change the theme from Ambiance to anything else, the sub
  menus become legible again.  Ambiance is the default theme.   If I
  switch the Theme back to Ambiance the problem resumes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Feb 21 20:57:30 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: sysdig, 0.20.0, 4.4.0-112-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1033]
  InstallationDate: Installed on 2014-04-20 (1404 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=8f4996c0-c2f5-449f-a35c-47f301f66803 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: 970 Extreme3
  dmi.board.vendor: ASRock
  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.:bvrP1.70:bd10/12/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Feb 21 19:32:42 2018
  xserver.configfile: default
  xserver.devices:
   

[Touch-packages] [Bug 1755036] Re: package qtdeclarative5-window-plugin:amd64 5.5.1-2ubuntu6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att

2018-03-11 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 qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1755036

Title:
  package qtdeclarative5-window-plugin:amd64 5.5.1-2ubuntu6 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  I still didn't find a way to fix this error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: qtdeclarative5-window-plugin:amd64 5.5.1-2ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Mar  7 03:04:31 2018
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-02-14 (390 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: qtdeclarative-opensource-src
  Title: package qtdeclarative5-window-plugin:amd64 5.5.1-2ubuntu6 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1755036/+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 1755036] [NEW] package qtdeclarative5-window-plugin:amd64 5.5.1-2ubuntu6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a

2018-03-11 Thread U92
Public bug reported:

I still didn't find a way to fix this error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: qtdeclarative5-window-plugin:amd64 5.5.1-2ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Wed Mar  7 03:04:31 2018
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-02-14 (390 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: qtdeclarative-opensource-src
Title: package qtdeclarative5-window-plugin:amd64 5.5.1-2ubuntu6 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qtdeclarative-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package qtdeclarative5-window-plugin:amd64 5.5.1-2ubuntu6 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  I still didn't find a way to fix this error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: qtdeclarative5-window-plugin:amd64 5.5.1-2ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Mar  7 03:04:31 2018
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-02-14 (390 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: qtdeclarative-opensource-src
  Title: package qtdeclarative5-window-plugin:amd64 5.5.1-2ubuntu6 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1755036/+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 269910] Re: Netmask automatically changes to 24

2018-03-11 Thread blauhirn
This is still an issue in Ubuntu 16.04 up to the current date.
It is an interface bug, as Robin Sheat pointed out.

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

Title:
  Netmask automatically changes to 24

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: network-manager

  I have added a new wireless connection with a WPA2 password and a manual IP 
address, like this:
  IP address: 180.180.180.11, Netmask: 255.255.255.0 Gateway: 180.180.180.254
  I also added two DNS servers.
  The connection is flawless (pass my compliments to whoever responsible for 
this, I could never get it to work on Hardy). However, when I edit the wireless 
connection again, for some reason, the Netmask changes to 24. Just 24. The 
connection still works. Everything else is the same.
  network-manager version:  0.7~~svn20080908t183521+eni0-0ubuntu2
  I'm running Ubuntu Intrepid Ibex Alpha 5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/269910/+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 1755030] [NEW] Dell XPS 13 (9350) problems with suspend to memory fixed after disabling AppArmor

2018-03-11 Thread ktecho
Public bug reported:

After installing latest Kubuntu 18.04 daily ISO and upgrading to latest
packages, I've had problems with suspend functionality:

0- Kubuntu installed correctly.
1- From Plasma, choose "Suspend to memory". Screen goes off.
2- When I power on the notebook, it starts with Grub and then a new Kubuntu 
session starts.
3- After reading in forums that the problem could be SELinux, I disable 
AppArmor by doing "/etc/init.d/apparmor stop".
4- From Plasma, choose "Suspend to memory". Screen goes off.
5- When I power on the notebook, it continues in the same place where I left it.

It seems that AppArmor is screwing Suspend in any way.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
Date: Sun Mar 11 21:25:04 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: kubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704]
InstallationDate: Installed on 2018-03-11 (0 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0c45:670c Microdia 
 Bus 001 Device 003: ID 0a5c:6412 Broadcom Corp. 
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9350
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=007be772-95a8-4b68-9f65-de19978e0979 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.1
dmi.board.name: 07TYC2
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd12/14/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.family: NULL
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
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 N/A
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

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


** Tags: amd64 apport-bug bionic kubuntu

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

Title:
  Dell XPS 13 (9350) problems with suspend to memory fixed after
  disabling AppArmor

Status in xorg package in Ubuntu:
  New

Bug description:
  After installing latest Kubuntu 18.04 daily ISO and upgrading to
  latest packages, I've had problems with suspend functionality:

  0- Kubuntu installed correctly.
  1- From Plasma, choose "Suspend to memory". Screen goes off.
  2- When I power on the notebook, it starts with Grub and then a new Kubuntu 
session starts.
  3- After reading in forums that the problem could be SELinux, I disable 
AppArmor by doing "/etc/init.d/apparmor stop".
  4- From Plasma, choose "Suspend to memory". Screen goes off.
  5- When I power on the notebook, it continues in the same place where I left 
it.

  It seems that AppArmor is screwing Suspend in any way.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Mar 11 21:25:04 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: kubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704]
  InstallationDate: Installed on 2018-03-11 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 0a5c:6412 

[Touch-packages] [Bug 1747138] Re: package resolvconf 1.79ubuntu9 failed to install/upgrade: triggers looping, abandoned

2018-03-11 Thread Ben Romer
This happened to me upgrading from Artful.

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

Title:
  package resolvconf 1.79ubuntu9 failed to install/upgrade: triggers
  looping, abandoned

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  Happened on upgrade to bionic on 2/2.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: resolvconf 1.79ubuntu9
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Sat Feb  3 00:58:50 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-08-19 (899 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150818)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: resolvconf
  Title: package resolvconf 1.79ubuntu9 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-02-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1747138/+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 1755006] Re: ModemManager crashed with SIGSEGV

2018-03-11 Thread Apport retracing service
*** This bug is a duplicate of bug 1725164 ***
https://bugs.launchpad.net/bugs/1725164

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1725164, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1755006/+attachment/5076043/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1755006/+attachment/5076045/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1755006/+attachment/5076048/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1755006/+attachment/5076049/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1755006/+attachment/5076050/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1755006/+attachment/5076051/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1755006/+attachment/5076052/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1725164

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  ModemManager crashed with SIGSEGV

Status in modemmanager package in Ubuntu:
  New

Bug description:
  Dont know.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: modemmanager 1.6.8-2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Mar 11 19:02:30 2018
  ExecutablePath: /usr/sbin/ModemManager
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x55d771dd4659:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x55d771dd4659) ok
   source "%es:(%rdi)" (0x55d771e68b28) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ()
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ModemManager crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1755006/+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 1755010] [NEW] package systemd 237-3ubuntu4 failed to install/upgrade: triggers looping, abandoned

2018-03-11 Thread Ben Romer
Public bug reported:

Tried upgrading from Artful to Bionic this weekend, had problems.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Sun Mar 11 13:47:24 2018
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2017-10-08 (153 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: ASUSTeK COMPUTER INC. G752VY
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=2bbeb898-f4c5-4a25-ba8d-f7874903809e ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~beta1
SourcePackage: systemd
Title: package systemd 237-3ubuntu4 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-03-11 (0 days ago)
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VY.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VY
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VY.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VY
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  package systemd 237-3ubuntu4 failed to install/upgrade: triggers
  looping, abandoned

Status in systemd package in Ubuntu:
  New

Bug description:
  Tried upgrading from Artful to Bionic this weekend, had problems.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Mar 11 13:47:24 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-10-08 (153 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. G752VY
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=2bbeb898-f4c5-4a25-ba8d-f7874903809e ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: systemd
  Title: package systemd 237-3ubuntu4 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-03-11 (0 days ago)
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VY.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VY
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VY.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VY
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1755010/+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 1754999] [NEW] Error detected while processing /usr/share/vim/vim80/debian.vim:

2018-03-11 Thread Tomasz (Tomek) Muras
Public bug reported:

In Ubuntu Bionic Beaver (development branch).

root@ubuntu:/home/ubuntu# mc

Select an editor.  To change later, run 'select-editor'.
  1. /bin/nano< easiest
  2. /usr/bin/vim.basic
  3. /usr/bin/mcedit
  4. /usr/bin/vim.tiny
  5. /bin/ed

Choose 1-5 [1]: 4
Error detected while processing /usr/share/vim/vim80/debian.vim:
line   29:
E319: Sorry, the command is not available in this version: function! 
MapExists(name, modes)
line   30:
E319: Sorry, the command is not available in this version:   for mode in 
split(a:modes, '\zs')
line   34:
E319: Sorry, the command is not available in this version:   endfor
line   35:
E319: Sorry, the command is not available in this version:   return 0
line   36:
E319: Sorry, the command is not available in this version: endfunction
Press ENTER or type command to continue

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

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

Title:
  Error detected while processing /usr/share/vim/vim80/debian.vim:

Status in vim package in Ubuntu:
  New

Bug description:
  In Ubuntu Bionic Beaver (development branch).

  root@ubuntu:/home/ubuntu# mc

  Select an editor.  To change later, run 'select-editor'.
1. /bin/nano< easiest
2. /usr/bin/vim.basic
3. /usr/bin/mcedit
4. /usr/bin/vim.tiny
5. /bin/ed

  Choose 1-5 [1]: 4
  Error detected while processing /usr/share/vim/vim80/debian.vim:
  line   29:
  E319: Sorry, the command is not available in this version: function! 
MapExists(name, modes)
  line   30:
  E319: Sorry, the command is not available in this version:   for mode in 
split(a:modes, '\zs')
  line   34:
  E319: Sorry, the command is not available in this version:   endfor
  line   35:
  E319: Sorry, the command is not available in this version:   return 0
  line   36:
  E319: Sorry, the command is not available in this version: endfunction
  Press ENTER or type command to continue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1754999/+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 1754836] Re: Failed to activate service

2018-03-11 Thread Alistair Buxton
The same messages are logged on the live image boot.

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

Title:
  Failed to activate service

Status in bluez package in Ubuntu:
  New

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Possibly also causing the long time to desktop from try/install
  livesession dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:
   
  rfkill:
   
  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]:   
[1520681416.8951] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+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 1754686] Re: libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like slack-desktop

2018-03-11 Thread Maarten Fonville
This also affects the installation of popular 3rd party application
Spotify: https://community.spotify.com/t5/Desktop-
Linux/libcurl4/m-p/4411011#M15902

I wonder, Debian still has libcurl3 versioned library/symbols in their
'unstable' repo, their libcurl4 is only in experimental yet. I
understand that with the perspective of LTS-support upgrading to
libcurl4 can be a good move, from security perspective, but there should
be a graceful upgrade path and if possible some kind of legacy support
of packages that were built using libcurl3 (maybe the libcurl3 libs can
also be part of the libcurl4-package and that in its dpkg control it
also 'provides' libcurl3?

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

Title:
  libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like
  slack-desktop

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Updating the curl package pulls in libcurl4, which for some reason
  forces libcurl3 to be removed. This prevents 3rd party apps that still
  build against libcurl3 from being installed. Isn't there a more
  graceful way to effect the transition from libcurl3 to libcurl4?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libcurl4 7.58.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:10:10 2018
  EcryptfsInUse: Yes
  SourcePackage: curl
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754686/+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 1569068] Re: /usr/bin/mate-settings-daemon:ERROR:pulse/glib-mainloop.c:407:glib_defer_free: assertion failed: (!e->dead)

2018-03-11 Thread Vlad Orlov
** Package changed: mate-settings-daemon (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  /usr/bin/mate-settings-daemon:ERROR:pulse/glib-
  mainloop.c:407:glib_defer_free: assertion failed: (!e->dead)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-settings-daemon.  This problem was most recently seen
  with version 1.12.1-2build1, the problem page at
  https://errors.ubuntu.com/problem/1b3afc018f02173501b79b75651ec747d69300b7
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1569068/+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 1664775] Re: /usr/bin/mate-settings-daemon:11:malloc_consolidate:_int_malloc:__libc_calloc:_snd_ctl_pulse_open:snd_ctl_open_conf

2018-03-11 Thread Vlad Orlov
** Package changed: mate-settings-daemon (Ubuntu) => alsa-lib (Ubuntu)

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

Title:
  /usr/bin/mate-settings-
  
daemon:11:malloc_consolidate:_int_malloc:__libc_calloc:_snd_ctl_pulse_open:snd_ctl_open_conf

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mate-settings-daemon.  This problem was most recently seen with package version 
1.14.0-1~xenial1.01, the problem page at 
https://errors.ubuntu.com/problem/669d26d753efa0be401d9fbc9242e66634d3d763 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1664775/+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 1569068] [NEW] /usr/bin/mate-settings-daemon:ERROR:pulse/glib-mainloop.c:407:glib_defer_free: assertion failed: (!e->dead)

2018-03-11 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding mate-settings-daemon.  This problem was most recently seen
with version 1.12.1-2build1, the problem page at
https://errors.ubuntu.com/problem/1b3afc018f02173501b79b75651ec747d69300b7
contains more details.

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


** Tags: wily xenial
-- 
/usr/bin/mate-settings-daemon:ERROR:pulse/glib-mainloop.c:407:glib_defer_free: 
assertion failed: (!e->dead)
https://bugs.launchpad.net/bugs/1569068
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio 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 1664775] [NEW] /usr/bin/mate-settings-daemon:11:malloc_consolidate:_int_malloc:__libc_calloc:_snd_ctl_pulse_open:snd_ctl_open_conf

2018-03-11 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mate-settings-daemon.  This problem was most recently seen with package version 
1.14.0-1~xenial1.01, the problem page at 
https://errors.ubuntu.com/problem/669d26d753efa0be401d9fbc9242e66634d3d763 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: xenial
-- 
/usr/bin/mate-settings-daemon:11:malloc_consolidate:_int_malloc:__libc_calloc:_snd_ctl_pulse_open:snd_ctl_open_conf
https://bugs.launchpad.net/bugs/1664775
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-lib 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 1754953] [NEW] Random freezes

2018-03-11 Thread GLEPIN Cyprien
Public bug reported:

Hi,

I've random freezes, and I don't know why. When it freezes, I have to
reboot my computer by button.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: Budgie:GNOME
Date: Sun Mar 11 12:58:01 2018
DistUpgraded: 2018-03-05 20:46:37,072 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L'exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] 
[19da:1438]
InstallationDate: Installed on 2018-03-05 (5 days ago)
InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=d1f0fff5-21d0-4394-857c-339472bba87b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to artful on 2018-03-05 (5 days ago)
dmi.bios.date: 12/27/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.40
dmi.board.name: AB350M Pro4
dmi.board.vendor: ASRock
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.:bvrP3.40:bd12/27/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sun Mar 11 12:46:37 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug artful third-party-packages ubuntu

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

Title:
  Random freezes

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I've random freezes, and I don't know why. When it freezes, I have to
  reboot my computer by button.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sun Mar 11 12:58:01 2018
  DistUpgraded: 2018-03-05 20:46:37,072 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L'exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] 
[19da:1438]
  InstallationDate: Installed on 2018-03-05 (5 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=d1f0fff5-21d0-4394-857c-339472bba87b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2018-03-05 (5 days ago)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: AB350M Pro4
  dmi.board.vendor: ASRock
  

[Touch-packages] [Bug 1714667] Re: please add old hungarian letters

2018-03-11 Thread kixidevel
Sorry, I unassignee, because I work on a huge project. Here nobody help
me.

** Changed in: ubuntu-font-family-sources (Ubuntu)
 Assignee: kixidevel (kixidevel) => (unassigned)

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

Title:
  please add old hungarian letters

Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  Old Hungarian letters (U10c80-U10cff) missing from font-families

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1714667/+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 1754947] [NEW] Dell E525w Color Laser Print Driver Not Available

2018-03-11 Thread Jeb E.
Public bug reported:

Ubuntu is recognizing my Dell E525w color laser printer by default on my
network, but is not finding a suitable applicable driver to install via
gnome-control-center. Dell has an open-source driver and driver kit for
all their printers, all OSes applicable, so I do not see there being a
problem pre-packaging the Dell Open Print Driver  with Ubuntu distros.

Please pre-package Dell Open Print Driver(s) into CUPS and Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: cups 2.2.4-7ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40-lowlatency 4.13.13
Uname: Linux 4.13.0-36-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 11 05:59:42 2018
Lpstat:
 device for Dell_Color_MFP_E525w_0E_45_6A_: 
ipps://DELL0E456A.local:631/ipp/print
 device for Officejet_4620_series_F608C0_: 
ipp://HPA45D36F608C0.local:631/ipp/print
MachineType: Dell Inc. Inspiron 13-5368
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Officejet_4620_series_F608C0_.ppd', 
'/etc/cups/ppd/Dell_Color_MFP_E525w_0E_45_6A_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Officejet_4620_series_F608C0_.ppd: Permission denied
 grep: /etc/cups/ppd/Dell_Color_MFP_E525w_0E_45_6A_.ppd: Permission denied
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-lowlatency 
root=UUID=b0b38a57-52b5-4e23-be9e-85197724f378 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.name: 01DC01
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd09/14/2017:svnDellInc.:pnInspiron13-5368:pvr:rvnDellInc.:rn01DC01:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 13-5368
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug artful dell laser printing wayland-session

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

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

Title:
  Dell E525w Color Laser Print Driver Not Available

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is recognizing my Dell E525w color laser printer by default on
  my network, but is not finding a suitable applicable driver to install
  via gnome-control-center. Dell has an open-source driver and driver
  kit for all their printers, all OSes applicable, so I do not see there
  being a problem pre-packaging the Dell Open Print Driver  with Ubuntu
  distros.

  Please pre-package Dell Open Print Driver(s) into CUPS and Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cups 2.2.4-7ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-lowlatency 4.13.13
  Uname: Linux 4.13.0-36-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 11 05:59:42 2018
  Lpstat:
   device for Dell_Color_MFP_E525w_0E_45_6A_: 
ipps://DELL0E456A.local:631/ipp/print
   device for Officejet_4620_series_F608C0_: 
ipp://HPA45D36F608C0.local:631/ipp/print
  MachineType: Dell Inc. Inspiron 13-5368
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Officejet_4620_series_F608C0_.ppd', 
'/etc/cups/ppd/Dell_Color_MFP_E525w_0E_45_6A_.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Officejet_4620_series_F608C0_.ppd: Permission denied
   grep: /etc/cups/ppd/Dell_Color_MFP_E525w_0E_45_6A_.ppd: Permission denied
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-lowlatency 
root=UUID=b0b38a57-52b5-4e23-be9e-85197724f378 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.name: 01DC01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd09/14/2017:svnDellInc.:pnInspiron13-5368:pvr:rvnDellInc.:rn01DC01:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 13-5368
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1440349] Re: imaens não abrem

2018-03-11 Thread Vlad Orlov
*** This bug is a duplicate of bug 555238 ***
https://bugs.launchpad.net/bugs/555238

** Changed in: ubuntu-mate
   Status: Expired => Invalid

** Package changed: caja (Ubuntu) => jasper (Ubuntu)

** This bug has been marked a duplicate of bug 555238
   crash on .jp2 files in jpc_qmfb_join_colgrp

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

Title:
  imaens não abrem

Status in ubuntu-mate:
  Invalid
Status in jasper package in Ubuntu:
  Expired

Bug description:
  MEUS ARQUIVOS  A PASTA ABRE E FECHA QUANDO EU ESCOLHO UM ARQUIVO DE
  IMAGENS

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: caja 1.8.2-3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Sat Apr  4 11:19:46 2015
  ExecutablePath: /usr/bin/caja
  InstallationDate: Installed on 2015-04-03 (1 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta i386 (20150326)
  ProcCmdline: caja
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: caja
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1440349/+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 555238] Re: crash on .jp2 files in jpc_qmfb_join_colgrp

2018-03-11 Thread Vlad Orlov
** Summary changed:

- nautilus crashed with SIGSEGV in jpc_qmfb_join_colgrp()
+ crash on .jp2 files in jpc_qmfb_join_colgrp

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

Title:
  crash on .jp2 files in jpc_qmfb_join_colgrp

Status in jasper package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: nautilus


  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: nautilus 1:2.30.0-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic x86_64
  Architecture: amd64
  CrashCounter: 1
  Date: Sun Apr  4 13:29:52 2010
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcCmdline: nautilus
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f23eb32ae1c : mov
%r8,(%r10,%rax,1)
   PC (0x7f23eb32ae1c) ok
   source "%r8" ok
   destination "(%r10,%rax,1)" (0x7f23fabee970) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   jpc_qmfb_join_colgrp () from /usr/lib/libjasper.so.1
   jpc_ns_synthesize () from /usr/lib/libjasper.so.1
   jpc_tsfb_synthesize2 () from /usr/lib/libjasper.so.1
   jpc_tsfb_synthesize () from /usr/lib/libjasper.so.1
   ?? () from /usr/lib/libjasper.so.1
  Title: nautilus crashed with SIGSEGV in jpc_qmfb_join_colgrp()
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jasper/+bug/555238/+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 1440349] [NEW] imaens não abrem

2018-03-11 Thread Launchpad Bug Tracker
*** This bug is a security vulnerability ***

You have been subscribed to a public security bug:

MEUS ARQUIVOS  A PASTA ABRE E FECHA QUANDO EU ESCOLHO UM ARQUIVO DE
IMAGENS

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: caja 1.8.2-3
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic i686
ApportVersion: 2.17-0ubuntu1
Architecture: i386
CrashCounter: 1
CurrentDesktop: MATE
Date: Sat Apr  4 11:19:46 2015
ExecutablePath: /usr/bin/caja
InstallationDate: Installed on 2015-04-03 (1 days ago)
InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta i386 (20150326)
ProcCmdline: caja
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: caja
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: ubuntu-mate
 Importance: Undecided
 Status: Invalid

** Affects: jasper (Ubuntu)
 Importance: Medium
 Status: Expired


** Tags: apport-crash i386 vivid
-- 
imaens não abrem
https://bugs.launchpad.net/bugs/1440349
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to jasper 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 1754933] [NEW] Headphones no audio output at all

2018-03-11 Thread Brent Westguard
Public bug reported:

Went to use headphones for the first time and got no audio output. I use
Ubuntu on an iMac and the speakers work ok and the headphones work when
in osx.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   brent  2112 F...m pulseaudio
 /dev/snd/controlC0:  brent  2112 F pulseaudio
 /dev/snd/controlC1:  brent  2112 F pulseaudio
CurrentDesktop: Unity
Date: Sun Mar 11 18:20:29 2018
InstallationDate: Installed on 2018-03-07 (3 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
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:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   brent  2112 F...m pulseaudio
 /dev/snd/controlC0:  brent  2112 F pulseaudio
 /dev/snd/controlC1:  brent  2112 F pulseaudio
Symptom_Jack: Green Headphone Out, N/A
Symptom_Type: No sound at all
Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/17
dmi.bios.vendor: Apple Inc.
dmi.bios.version: IM121.88Z.004D.B00.1708080012
dmi.board.name: Mac-942B5BF58194151B
dmi.board.vendor: Apple Inc.
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-942B5BF58194151B
dmi.modalias: 
dmi:bvnAppleInc.:bvrIM121.88Z.004D.B00.1708080012:bd08/08/17:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B:
dmi.product.family: iMac
dmi.product.name: iMac12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Headphones no audio output at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Went to use headphones for the first time and got no audio output. I
  use Ubuntu on an iMac and the speakers work ok and the headphones work
  when in osx.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   brent  2112 F...m pulseaudio
   /dev/snd/controlC0:  brent  2112 F pulseaudio
   /dev/snd/controlC1:  brent  2112 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar 11 18:20:29 2018
  InstallationDate: Installed on 2018-03-07 (3 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  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:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   brent  2112 F...m pulseaudio
   /dev/snd/controlC0:  brent  2112 F pulseaudio
   /dev/snd/controlC1:  brent  2112 F pulseaudio
  Symptom_Jack: Green Headphone Out, N/A
  Symptom_Type: No sound at all
  Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/17
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM121.88Z.004D.B00.1708080012
  dmi.board.name: Mac-942B5BF58194151B
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942B5BF58194151B
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM121.88Z.004D.B00.1708080012:bd08/08/17:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B:
  dmi.product.family: iMac
  dmi.product.name: iMac12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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