[Touch-packages] [Bug 460897] Re: Tracker not returning known results

2019-06-29 Thread Launchpad Bug Tracker
[Expired for tracker (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Tracker not returning known results

Status in tracker package in Ubuntu:
  Expired

Bug description:
  Binary package hint: tracker

  Tracker is not giving me results when I query a known-existing string.
  I have a large collection of MP3s that are indexed on a mdadm RAID5
  array that are shared through Samba. I have many ZZ Top albums on this
  share but Tracker will return 0 results when the query "zz top" is
  used. A similar search for "acdc" also returns 0 results even though
  many songs exist in the indexed locations. The total files indexed by
  the Tracker daemon is 337951, 49562 of them being identified as music
  in the "Statistics" dialog. Most queries return correct results, these
  were just two that I tried to verify that the Tracker was working
  correctly, and it isn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/460897/+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 402741] Re: Tracker not indexing all files it should

2019-06-29 Thread Launchpad Bug Tracker
[Expired for tracker (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Tracker not indexing all files it should

Status in tracker package in Ubuntu:
  Expired

Bug description:
  Binary package hint: tracker

  I Have tracker indexing my home folder and, according to nautilus, it
  has 32,143 items but tracker only indexed 31943 items. I could found
  some files that were not indexed in the same folder as files that were
  indexed I included some screen shots of this search

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/402741/+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 1826968] Re: tzdata package contains invalid entry for Asia/Novosibirsk

2019-06-29 Thread Launchpad Bug Tracker
[Expired for tzdata (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  tzdata package contains invalid entry for Asia/Novosibirsk

Status in tzdata package in Ubuntu:
  Expired

Bug description:
  Ubuntu version: 16.04.6

  Problem: in the latest release of tzdata (2019a-0ubuntu0.16.04) the
  entry for Asia/Novosibirsk consists of text file with the below line
  only:

  Asia/Novosibirsk

  Apart from not working as /etc/localtime, it also creates cryptic
  errors in other packages (such as PHP complaining on invalid date/time
  database).

  After I replaced the above file with the one from Ubuntu 18.04.2
  tzdata's latest release, the error was gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1826968/+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 1826902] Re: /usr/sbin/usbmuxd:free(): invalid pointer

2019-06-29 Thread Launchpad Bug Tracker
[Expired for usbmuxd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  /usr/sbin/usbmuxd:free(): invalid pointer

Status in usbmuxd package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
usbmuxd.  This problem was most recently seen with package version 
1.1.0-2ubuntu0.1, the problem page at 
https://errors.ubuntu.com/problem/0ab3146f9a13cc10682e6a4210ead867d649869f 
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 and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1826902/+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 1834761] Re: monitor refresh rates higher than 120 Hz not detected/cannot be set

2019-06-29 Thread Jason T Brockdorf
Attached edid output.  Notice "Mode 1" is apparently the modeline that
specifies 144 Hz native resolution, but I don't see this mode in xorg
log.

** Attachment added: "Attached edid output"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1834761/+attachment/5274195/+files/edid.txt

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

Title:
  monitor refresh rates higher than 120 Hz not detected/cannot be set

Status in xorg package in Ubuntu:
  New

Bug description:
  using this monitor: https://www.pixiogaming.com/px329
  and this video card: 
https://www.gigabyte.com/us/Graphics-Card/GV-RX580GAMING-4GD-rev-10-11

  I am unable to set any refresh rates higher than 120 Hz.  The video
  card and the monitor both support 144 Hz and 165 Hz yet those refresh
  rates are not available as options to choose in the settings app.
  I've tried a couple of online guides using xrandr to add and set a
  custom display resolution/refresh rate but I can't get it to go any
  higher than 120 Hz.  I have the exact same hardware running macOS
  Mojave 10.14.4 and it allows me to set the refresh rate to 144 Hz and
  165 Hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 29 18:13:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 
470/480/570/580] [1458:22fd]
  InstallationDate: Installed on 2019-06-28 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=8d1eef58-5823-4ca0-abb0-d2c79b140e40 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z390-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd01/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1834761/+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 1782275] Re: Conflict between resolvconf and systemd-resolved dhclient scripts

2019-06-29 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 resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1782275

Title:
  Conflict between resolvconf and systemd-resolved dhclient scripts

Status in resolvconf package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am setting up an Ubuntu 18.04 (bionic) system with ifupdown instead
  of netplan, as the latter does not meet my needs. I am using
  resolvconf to update /etc/resolv.conf from DHCP, as in earlier
  releases.

  Unfortunately, I am not seeing /etc/resolv.conf (actually a symlink to
  /run/resolvconf/resolv.conf) being updated; it is only the boilerplate
  from /etc/resolvconf/resolv.conf.d/head with no server information
  appended. (My "base" and "tail" files are empty.)

  I poked around the scripts in /etc, and believe I have found the
  problem.

  When resolvconf is installed, the following two files are present:

  /etc/dhcp/dhclient-enter-hooks.d/resolvconf
  /etc/dhcp/dhclient-enter-hooks.d/resolved

  Both of these scripts define the make_resolv_conf() shell function.
  What I am seeing is that dhclient runs these two scripts in the
  (alphabetical) order shown, and as the resolved script runs second, it
  overwrites the resolvconf version of the shell function with its own.
  As a result, dhclient does not invoke the appropriate update command
  for resolvconf, even though the hook script was installed correctly.

  Normally, I would remove the package that is providing the "resolved"
  script, but this package is systemd, which cannot be removed. I am not
  sure which of the two packages (resolvconf or systemd) needs to make
  an accommodation for the other, but it is clear that the current
  approach does not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1782275/+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 1782275] Re: Conflict between resolvconf and systemd-resolved dhclient scripts

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

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

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

Title:
  Conflict between resolvconf and systemd-resolved dhclient scripts

Status in resolvconf package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am setting up an Ubuntu 18.04 (bionic) system with ifupdown instead
  of netplan, as the latter does not meet my needs. I am using
  resolvconf to update /etc/resolv.conf from DHCP, as in earlier
  releases.

  Unfortunately, I am not seeing /etc/resolv.conf (actually a symlink to
  /run/resolvconf/resolv.conf) being updated; it is only the boilerplate
  from /etc/resolvconf/resolv.conf.d/head with no server information
  appended. (My "base" and "tail" files are empty.)

  I poked around the scripts in /etc, and believe I have found the
  problem.

  When resolvconf is installed, the following two files are present:

  /etc/dhcp/dhclient-enter-hooks.d/resolvconf
  /etc/dhcp/dhclient-enter-hooks.d/resolved

  Both of these scripts define the make_resolv_conf() shell function.
  What I am seeing is that dhclient runs these two scripts in the
  (alphabetical) order shown, and as the resolved script runs second, it
  overwrites the resolvconf version of the shell function with its own.
  As a result, dhclient does not invoke the appropriate update command
  for resolvconf, even though the hook script was installed correctly.

  Normally, I would remove the package that is providing the "resolved"
  script, but this package is systemd, which cannot be removed. I am not
  sure which of the two packages (resolvconf or systemd) needs to make
  an accommodation for the other, but it is clear that the current
  approach does not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1782275/+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 1801540] Re: Microphone distorted sound on ALC892/1220 on AMD chipsets

2019-06-29 Thread Bug Watch Updater
Launchpad has imported 97 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=195303.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-04-09T18:55:48+00:00 icebalm wrote:

Audio playback seems to be fine, however audio capture results in
crackling.

- all values of position_fix have been tried and do not help
- power_save=0 does not help
- align_buffer_size does not help
- enable_msi does not help

Hardware is onboard ALC1220 codec sound chipset on the ASUS Crosshair VI
Hero motherboard.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801540/comments/0


On 2017-06-18T18:46:14+00:00 kernel wrote:

Created attachment 257067
alsa-info of offending hardware

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801540/comments/1


On 2017-06-18T18:52:22+00:00 kernel wrote:

To elaborate on this bug:

- I've found someone on reddit who went into more detail (including futile 
pulseaudio sorcery): 
https://www.reddit.com/r/linuxquestions/comments/68rirb/mic_cracklingstatic/
- He was kind enough to upload an audio sample: 
https://drive.google.com/open?id=0B1kXCJ6A8v29N3lBT0c4TGdRbFE

I have encountered the same problem. It is present from 4.11 to
4.12.0-rc5 (most recent rc as of this writing). I tried a few distros;
all have the same problem.

Windows 10 records without distortion.

This device identifies as "Vendor Id: 0x10ec1168". See attached alsa-
info file and ignore the ATI HDMI and Audioengine noise as best as
possible.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801540/comments/2


On 2017-08-12T08:24:35+00:00 luca.ricciolo wrote:

Same problem, audio microphone capture results a little crackling/noisy
kernel 4.12.5

 description: Motherboard
   product: CROSSHAIR VI HERO
   vendor: ASUSTeK COMPUTER INC.

Codec: Realtek ALC1220
Address: 0
AFG Function Id: 0x1 (unsol 1)
Vendor Id: 0x10ec1220
Subsystem Id: 0x10438735
Revision Id: 0x13

!!Kernel Information
!!--

Kernel release:4.12.5-041205-generic
Operating System:  GNU/Linux
Architecture:  x86_64
Processor: x86_64
SMP Enabled:   Yes


!!ALSA Version
!!

Driver version: k4.12.5-041205-generic
Library version:1.1.0
Utilities version:  1.1.0


!!Loaded ALSA modules
!!---

snd_hda_intel
snd_hda_intel

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801540/comments/3


On 2017-08-12T08:51:14+00:00 luca.ricciolo wrote:

The same on 4.12.6 and previous, just tried.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801540/comments/4


On 2017-09-06T12:08:49+00:00 frederic.epitre wrote:

Hi,

I also had the same problem with my ASROCK X370 Gaming K4 (ALC1220):

1st case: Booting FIRST Linux: Sound with noise/crackling.
2nd case: Booting FIRST Windows and SECOND Linux: Sound is perfect.

I suceed in solving the problem by comparing the Coeff values in both
cases and assign the values of the second case in a script at boot time.
How to:

- Install alsa-tools.
- In both cases, you have to: echo 1 > 
/sys/module/snd_hda_codec/parameters/dump_coefs
- Then, in the first case,  alsa-info --no-upload --output infos_bad
- Then, in the second case, alsa-info --no-upload --output infos_good
- Finally, you compare the coef values: diff infos_bad infos_good | grep Coeff

For changing the value of each different Coeff, you need to proceed as
follow: for example, changing Coeff 0x67 to value 0x3000

hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x67
hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x3000

You have to do this in the growing order of Coeff. Remark that hwC0D0
refers to your sound card. In case of HDMI output like me, my sound card
if hwC1D0.

Here is a quick script:


#!/bin/bash

coeffs=($(echo 0x{16,43,44,5d,5e,63,67}))
values=($(echo 0x{8020,3405,fa10,0606,,e430,3000}))

for i in `seq 0 $(( ${#coeffs[@]} - 1 ))`
do
hda-verb /dev/snd/hwC1D0 0x20 SET_COEF_INDEX ${coeffs[$i]} && hda-verb 
/dev/snd/hwC1D0 0x20 SET_PROC_COEF ${values[$i]}
done


Just change the coeffs to change in the array 'coeffs' and the new
values in array 'values' and exec this script. A remark, while I do not
shutdown the power 

[Touch-packages] [Bug 1834761] Re: monitor refresh rates higher than 120 Hz not detected/cannot be set

2019-06-29 Thread Jason T Brockdorf
Sorry, I realize I left out some detail.  I can get 144 Hz if I change
the resolution to 1920x1080 but that's not the native resolution for the
monitor.  I'm trying to get 144 Hz / 165 Hz using the monitor's native
resolution, 2560x1440.

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

Title:
  monitor refresh rates higher than 120 Hz not detected/cannot be set

Status in xorg package in Ubuntu:
  New

Bug description:
  using this monitor: https://www.pixiogaming.com/px329
  and this video card: 
https://www.gigabyte.com/us/Graphics-Card/GV-RX580GAMING-4GD-rev-10-11

  I am unable to set any refresh rates higher than 120 Hz.  The video
  card and the monitor both support 144 Hz and 165 Hz yet those refresh
  rates are not available as options to choose in the settings app.
  I've tried a couple of online guides using xrandr to add and set a
  custom display resolution/refresh rate but I can't get it to go any
  higher than 120 Hz.  I have the exact same hardware running macOS
  Mojave 10.14.4 and it allows me to set the refresh rate to 144 Hz and
  165 Hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 29 18:13:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 
470/480/570/580] [1458:22fd]
  InstallationDate: Installed on 2019-06-28 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=8d1eef58-5823-4ca0-abb0-d2c79b140e40 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z390-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd01/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1834761/+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 1834761] [NEW] monitor refresh rates higher than 120 Hz not detected/cannot be set

2019-06-29 Thread Jason T Brockdorf
Public bug reported:

using this monitor: https://www.pixiogaming.com/px329
and this video card: 
https://www.gigabyte.com/us/Graphics-Card/GV-RX580GAMING-4GD-rev-10-11

I am unable to set any refresh rates higher than 120 Hz.  The video card
and the monitor both support 144 Hz and 165 Hz yet those refresh rates
are not available as options to choose in the settings app.  I've tried
a couple of online guides using xrandr to add and set a custom display
resolution/refresh rate but I can't get it to go any higher than 120 Hz.
I have the exact same hardware running macOS Mojave 10.14.4 and it
allows me to set the refresh rate to 144 Hz and 165 Hz.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-25-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 29 18:13:05 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 
470/480/570/580] [1458:22fd]
InstallationDate: Installed on 2019-06-28 (1 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=8d1eef58-5823-4ca0-abb0-d2c79b140e40 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0805
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z390-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0805:bd01/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: ASUS_MB_CNL
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic resolution ubuntu

** Attachment added: "settings"
   
https://bugs.launchpad.net/bugs/1834761/+attachment/5274180/+files/Screenshot%20from%202019-06-29%2018-23-16.png

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

Title:
  monitor refresh rates higher than 120 Hz not detected/cannot be set

Status in xorg package in Ubuntu:
  New

Bug description:
  using this monitor: https://www.pixiogaming.com/px329
  and this video card: 
https://www.gigabyte.com/us/Graphics-Card/GV-RX580GAMING-4GD-rev-10-11

  I am unable to set any refresh rates higher than 120 Hz.  The video
  card and the monitor both support 144 Hz and 165 Hz yet those refresh
  rates are not available as options to choose in the settings app.
  I've tried a couple of online guides using xrandr to add and set a
  custom display resolution/refresh rate but I can't get it to go any
  higher than 120 Hz.  I have the exact same hardware running macOS
  Mojave 10.14.4 and it allows me to set the refresh rate to 144 Hz and
  165 Hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 29 18:13:05 

[Touch-packages] [Bug 1777094] Re: dnsmasq started too early, not getting all interfaces

2019-06-29 Thread Terrence Houlahan
In respect to my above post, the correct target of the sed expression
should be as follows:


sed -i 's/After=network.target/After=NetworkManager-wait-online.service/' 
/lib/systemd/system/dnsmasq.service


Please note the fix remains nonetheless valid and ensures that dnsmasq rises up 
correctly on boot-

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

Title:
  dnsmasq started too early, not getting all interfaces

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Expired

Bug description:
  Hi,

  I'm still struggling with 18.04 and the move from ifupdown to netplan.

  I am running a local virtual linux bridge as a network for several
  virtual machines and containers, which is to be serviced with dhcp and
  dns by dnsmasq.

  Conforming to latest designs from Ubuntu the bridge is now started by
  netplan and configured in /etc/netplan/60-vlan0.yaml straightforward.

  Since there is no ifupdown-scripts anymore, I've configured the
  default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that
  bridge.

  
  This works only when started manually. 

  When booting ubuntu the normal way, the bridge is correctly generated,
  and dnsmasq is running, but it does *not* offer DNS for the bridge and
  does not occupy its port 53. But just a manual systemctl restart
  dnsmasq.service make it run as expected, then everything is fine.

  So my guess is that my configuration is correct, but dnsmasq simply
  started to early, i.e. before the bridge is created, and thus does not
  see the bridge when starting up.

  There's something wrong in the dependencies of the startup
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun 15 10:59:43 2018
  InstallationDate: Installed on 2018-04-30 (45 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+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 1834755] [NEW] Fails to connect to printer after reboot, rebooting Router and reconnecting printer.

2019-06-29 Thread DNK
Public bug reported:

Fails to connect to printer after reboot, rebooting Router and
reconnecting printer.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.6
ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
Uname: Linux 4.15.0-52-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 29 13:59:12 2019
Lpstat: device for DCPL2550DW: 
dnssd://Brother%20DCP-L2550DW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4a0ce62
MachineType: Dell Inc. Inspiron 3135
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DCPL2550DW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DCPL2550DW.ppd: Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet noresume
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/03/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 001GW6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A02
dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd01/03/2014:svnDellInc.:pnInspiron3135:pvr:rvnDellInc.:rn001GW6:rvrA00:cvnDellInc.:ct8:cvrA02:
dmi.product.name: Inspiron 3135
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  Fails to connect to printer after reboot, rebooting Router and
  reconnecting printer.

Status in cups package in Ubuntu:
  New

Bug description:
  Fails to connect to printer after reboot, rebooting Router and
  reconnecting printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.6
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 29 13:59:12 2019
  Lpstat: device for DCPL2550DW: 
dnssd://Brother%20DCP-L2550DW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4a0ce62
  MachineType: Dell Inc. Inspiron 3135
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DCPL2550DW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DCPL2550DW.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet noresume
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/03/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 001GW6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A02
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd01/03/2014:svnDellInc.:pnInspiron3135:pvr:rvnDellInc.:rn001GW6:rvrA00:cvnDellInc.:ct8:cvrA02:
  dmi.product.name: Inspiron 3135
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1834755/+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 1810346] Re: VLC interface not displayed correctly

2019-06-29 Thread roussel geoffrey
Hey, Thanks Jean Luc, the QT_AUTO_SCREEN_SCALE_FACTOR=0 does the trick here too!
I wonder if this only affects Ubuntu or other Linux distributions too.

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

Title:
  VLC interface not displayed correctly

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

Bug description:
  I use vlc on a Dell E-5530 laptop seated on its docking station.
  The laptop display cover is closed, the output is sent on an external LG TV 
with 1920x1080.
  This system has been working flawlessly for many years, resp. under late 
14.04 and 16.04.
  After recently upgrading to 18.04, I noticed VLC wouldn't display correctly - 
see attachment.
  This only occurs on the external display ; if I open the cover and use the 
internal display, there is no problem - except I cannot work on the internal 
display.
  regards,
  J.-Luc

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vlc-bin 3.0.4-1ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 23:38:36 2019
  ExecutablePath: /usr/bin/vlc
  InstallationDate: Installed on 2018-12-19 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+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 1833532] Re: systemd-backlight does not restore screen brightness after reboot

2019-06-29 Thread Luca Mastromatteo
After resetting the BIOS this doesn't happen anymore...

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

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

Title:
  systemd-backlight does not restore screen brightness after reboot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  As the title says, on this laptop the brightness controls are NOT
  saved after reboot.

  What is saved instead, is only the keyboard brightness.

  I have tested two distros, Ubuntu 18.04.2 LTS and 19.04, happens on
  both systems. But there is a difference

  On 19.04, "systemctl status systemd-backlight@:*intel_screen_backlight_*" 
shows:
  "Saved brightness 20 too low, increasing to 75"

  On 18.04.2 does not show anything rather than the service starting
  normally

  The laptop is a Dell XPS 15 9550, the screen backlight driver is the
  intel one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833532/+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 1810346] Re: VLC interface not displayed correctly

2019-06-29 Thread FalCT60
Oops ! I hit the return key unintentionally !
So, I make take some time to do some testings, but you have to tell me what to 
do exactly, and how.

Regards,

J.-Luc

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

Title:
  VLC interface not displayed correctly

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

Bug description:
  I use vlc on a Dell E-5530 laptop seated on its docking station.
  The laptop display cover is closed, the output is sent on an external LG TV 
with 1920x1080.
  This system has been working flawlessly for many years, resp. under late 
14.04 and 16.04.
  After recently upgrading to 18.04, I noticed VLC wouldn't display correctly - 
see attachment.
  This only occurs on the external display ; if I open the cover and use the 
internal display, there is no problem - except I cannot work on the internal 
display.
  regards,
  J.-Luc

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vlc-bin 3.0.4-1ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 23:38:36 2019
  ExecutablePath: /usr/bin/vlc
  InstallationDate: Installed on 2018-12-19 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+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 1810346] Re: VLC interface not displayed correctly

2019-06-29 Thread FalCT60
This is the behaviour I have been describing from the beginning : the video is 
useable, but most of the controls are not.
This happens on *every* laptop used with an external TV as main screen since 
18.04 - it was fine until 16.04.
I would event bet it alson happens on every computer using a second monitor as 
main display unit.
In order to be able to use vlc correctly, I have to launch it from terminal 
with the command QT_AUTO_SCREEN_SCALE_FACTOR=0 vlc, which I could find in many 
of the thousands posts about this on the net since 2010 or so.
Which tends to prove that the bug has never been reported, otherwise no doubt 
the devs would have fixed it already.
And would not have thought that I was the only one to encounter it.
To the devs : I am ready to help you trying to trace this, but keep in mind 
that, just like you, I have a real life beside, which makes I may not react as 
quickly as one would expect.
This is also why I did not give any reminder though there was no reaction after 
a long time : I know you have many things to do, that may be more important (or 
valualble), and 24 hours per day are not enough for many of us.
This bug kind of puzzles me, and I sometimes wonder if I did not install 
something the wrong way : many things changed since 16.04, so being able to 
tell what is good or not is not that easy for a poor end user.
If I find some time, I plan to load the latest 16.04 LTS iso and reinstall it 
from scratch, but without preserving my /home. This means I will have to do 
some savings before, and be very carefull, and it will take me far more time 
then just upgrading my distro.
However, I may take some time to do some testings, a

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

Title:
  VLC interface not displayed correctly

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

Bug description:
  I use vlc on a Dell E-5530 laptop seated on its docking station.
  The laptop display cover is closed, the output is sent on an external LG TV 
with 1920x1080.
  This system has been working flawlessly for many years, resp. under late 
14.04 and 16.04.
  After recently upgrading to 18.04, I noticed VLC wouldn't display correctly - 
see attachment.
  This only occurs on the external display ; if I open the cover and use the 
internal display, there is no problem - except I cannot work on the internal 
display.
  regards,
  J.-Luc

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vlc-bin 3.0.4-1ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 23:38:36 2019
  ExecutablePath: /usr/bin/vlc
  InstallationDate: Installed on 2018-12-19 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+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 1834745] [NEW] openvpn dns leaks on 19.04

2019-06-29 Thread shiva
Public bug reported:

I have resolvconf installed
and when I visit dnsleaktest.com it shows I m using the dns vpn server
yet if I iptables allow dns only on vpn interface , resolution fails.
with wireshark I had confirmation that some queries were indeed sent-received 
from my ISP dns.

this is consistent on many vpn servers from different vpn providers.

ubuntu 19.04

openvpn:
  Installed: 2.4.6-1ubuntu3.1

openvpn should send all dns requests on the vpn interface (encrypted)
it doesn t ,worse it fails to resolve anything if the firewall blocks all dns 
on non vpn interfaces.

tried with openresolv instead resolvconf  ,dns didn t t work.

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

** Information type changed from Private Security to Public

** Package changed: network-manager (Ubuntu) => openvpn (Ubuntu)

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

Title:
  openvpn dns leaks on 19.04

Status in openvpn package in Ubuntu:
  New

Bug description:
  I have resolvconf installed
  and when I visit dnsleaktest.com it shows I m using the dns vpn server
  yet if I iptables allow dns only on vpn interface , resolution fails.
  with wireshark I had confirmation that some queries were indeed sent-received 
from my ISP dns.

  this is consistent on many vpn servers from different vpn providers.

  ubuntu 19.04

  openvpn:
Installed: 2.4.6-1ubuntu3.1

  openvpn should send all dns requests on the vpn interface (encrypted)
  it doesn t ,worse it fails to resolve anything if the firewall blocks all dns 
on non vpn interfaces.

  tried with openresolv instead resolvconf  ,dns didn t t work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1834745/+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 1834740] Re: Gmail and some other websites never open

2019-06-29 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Gmail and some other websites never open

Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  Dear sir/Madam,

  I have noticed that gmail and some other websites never open or me
  whatever the browser I am using and the browser crashes.

  Please help.

  Thanks in advance.

  Warm Regards,
  Arnab Bhattacharya

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.10
  ProcVersionSignature: Ubuntu 4.15.0-52.56~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  .var.log.unattended-upgrades.unattended-upgrades.log:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   unattended-upgrades: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Jul  1 02:10:02 2019
  DpkgHistoryLog:
   Start-Date: 2019-07-01  02:10:02
   Commandline: apt-get install gnome-panel
   Requested-By: arnab (1000)
  DpkgTerminalLog:
   dpkg: error processing package unattended-upgrades (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-03-12 (474 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.29ubuntu0.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.10 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/unattended-upgrades/+bug/1834740/+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 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly

2019-06-29 Thread Daniel Novotny
Hello, I solved this by upgrading to the HWE kernel and Xorg

https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Ubuntu_16.04_LTS_-
_Xenial_Xerus

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

Title:
  After update 2018-07-08 menus and buttons are behaving badly

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After an update to

     Description:   Ubuntu 16.04.4 LTS
     Release:   16.04

  Menus and buttons are behaving badly. This is a general issue, affecting most 
programs.
  Text in buttons is not always being displayed.
  When you mouse over an entry in a menu list the previous entry disappears
 e.g. the logout menu (power button icon at top right of panel)
  Menu items are getting red backgrounds where they were not before.

  Introduced by update done by update-manager on
     Last update Start-Date: 2018-07-08  21:25:10
  Modified packages:

   libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libapt-inst2.0:amd64 (1.2.26, 1.2.27)
   libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt:amd64 (1.2.26, 1.2.27)
   libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libapt-pkg5.0:amd64 (1.2.26, 1.2.27)
   apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 
61.0+build3-0ubuntu0.16.04.2)
   libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apt-utils:amd64 (1.2.26, 1.2.27)
   libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2)
   apt-transport-https:amd64 (1.2.26, 1.2.27)
   libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1)
   apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9)
   libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)
   libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780846/+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 1834740] [NEW] Gmail and some other websites never open

2019-06-29 Thread Arnab Bhattacharya
Public bug reported:

Dear sir/Madam,

I have noticed that gmail and some other websites never open or me
whatever the browser I am using and the browser crashes.

Please help.

Thanks in advance.

Warm Regards,
Arnab Bhattacharya

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90ubuntu0.10
ProcVersionSignature: Ubuntu 4.15.0-52.56~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-52-generic x86_64
.var.log.unattended-upgrades.unattended-upgrades.log:
 
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
 unattended-upgrades: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Jul  1 02:10:02 2019
DpkgHistoryLog:
 Start-Date: 2019-07-01  02:10:02
 Commandline: apt-get install gnome-panel
 Requested-By: arnab (1000)
DpkgTerminalLog:
 dpkg: error processing package unattended-upgrades (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-03-12 (474 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.29ubuntu0.1
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 0.90ubuntu0.10 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: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  Gmail and some other websites never open

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Dear sir/Madam,

  I have noticed that gmail and some other websites never open or me
  whatever the browser I am using and the browser crashes.

  Please help.

  Thanks in advance.

  Warm Regards,
  Arnab Bhattacharya

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.10
  ProcVersionSignature: Ubuntu 4.15.0-52.56~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  .var.log.unattended-upgrades.unattended-upgrades.log:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   unattended-upgrades: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Jul  1 02:10:02 2019
  DpkgHistoryLog:
   Start-Date: 2019-07-01  02:10:02
   Commandline: apt-get install gnome-panel
   Requested-By: arnab (1000)
  DpkgTerminalLog:
   dpkg: error processing package unattended-upgrades (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-03-12 (474 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.29ubuntu0.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.10 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/unattended-upgrades/+bug/1834740/+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 1679776] Re: Package FTBFS because of missing qdoc command

2019-06-29 Thread Michael Robinson
** Changed in: accounts-qml-module (Ubuntu)
 Assignee: Łukasz Zemczak (sil2100) => Michael Robinson (big2112mike)

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

Title:
  Package FTBFS because of missing qdoc command

Status in accounts-qml-module package in Ubuntu:
  Fix Released

Bug description:
  During the zesty test-rebuild the accounts-qml-module package FTBFS on
  all archs due to the following reason:

  make[3]: Entering directory 
'/<>/accounts-qml-module-0.6+16.04.20151106/tests'
  install -m 755 -p tst_plugin 
/<>/accounts-qml-module-0.6+16.04.20151106/debian/tmp/usr/bin/tst_plugin
  make[3]: Leaving directory 
'/<>/accounts-qml-module-0.6+16.04.20151106/tests'
  make[2]: Leaving directory 
'/<>/accounts-qml-module-0.6+16.04.20151106/tests'
  /usr/lib/x86_64-linux-gnu/qt5/bin/qdoc 
/<>/accounts-qml-module-0.6+16.04.20151106/doc/accounts-qml-module-ubuntu.qdocconf
  make[1]: /usr/lib/x86_64-linux-gnu/qt5/bin/qdoc: Command not found
  Makefile:266: recipe for target 'docs-html' failed
  make[1]: *** [docs-html] Error 127
  make[1]: Leaving directory 
'/<>/accounts-qml-module-0.6+16.04.20151106'
  dh_auto_install: make -j1 install 
DESTDIR=/<>/accounts-qml-module-0.6+16.04.20151106/debian/tmp 
AM_UPDATE_INFO_DIR=no 
INSTALL_ROOT=/<>/accounts-qml-module-0.6+16.04.20151106/debian/tmp 
returned exit code 2
  debian/rules:21: recipe for target 'binary' failed
  make: *** [binary] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accounts-qml-module/+bug/1679776/+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 1810346] Re: VLC interface not displayed correctly

2019-06-29 Thread roussel geoffrey
On my last test (the one where it works but is exageratly zoomed), when
switching to fullscreen mode, the VLC overlays(control buttons, volume,
etc) are not usable because too large, they don't fit on screen.

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

Title:
  VLC interface not displayed correctly

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

Bug description:
  I use vlc on a Dell E-5530 laptop seated on its docking station.
  The laptop display cover is closed, the output is sent on an external LG TV 
with 1920x1080.
  This system has been working flawlessly for many years, resp. under late 
14.04 and 16.04.
  After recently upgrading to 18.04, I noticed VLC wouldn't display correctly - 
see attachment.
  This only occurs on the external display ; if I open the cover and use the 
internal display, there is no problem - except I cannot work on the internal 
display.
  regards,
  J.-Luc

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vlc-bin 3.0.4-1ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 23:38:36 2019
  ExecutablePath: /usr/bin/vlc
  InstallationDate: Installed on 2018-12-19 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+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 1829829] Re: Ubuntu CI has been flaky for a week

2019-06-29 Thread Evgeny Vereshchagin
By the way, @ddstreet would it be OK to mention that you maintain Ubuntu
CI at https://www.freedesktop.org/wiki/Software/systemd/autopkgtest/?
Currently it's almost impossible to figure out who is responsible for
it. At some point I assumed it was @xnox but it doesn't seem the case so
I don't even try to cc @xnox any more.

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

Title:
  Ubuntu CI has been flaky for a week

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  It was originally reported in 
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days 
ago. To judge from the logs VMs can't be rebooted there:
  ```
  Ubuntu 18.04.2 LTS autopkgtest ttyS0

  autopkgtest login:
  ---
  --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
  
+--++
  | Property | Value
  |
  
+--++
  | OS-DCF:diskConfig| MANUAL   
  |
  | OS-EXT-AZ:availability_zone  | nova 
  |
  | OS-EXT-SRV-ATTR:host | euler
  |
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | euler.lcy01.scalingstack 
  |
  | OS-EXT-SRV-ATTR:instance_name| instance-003d216a
  |
  | OS-EXT-STS:power_state   | 1
  |
  | OS-EXT-STS:task_state| -
  |
  | OS-EXT-STS:vm_state  | active   
  |
  | OS-SRV-USG:launched_at   | 2019-05-16T07:00:42.00   
  |
  | OS-SRV-USG:terminated_at | -
  |
  | accessIPv4   |  
  |
  | accessIPv6   |  
  |
  | config_drive |  
  |
  | created  | 2019-05-16T07:00:33Z 
  |
  | flavor   | autopkgtest 
(f878e70e-9991-46e0-ba02-8ea159a71656) |
  | hostId   | 
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
   |
  | id   | 91e76a78-d05c-412a-b383-55a26010ae69 
  |
  | image| 
adt/ubuntu-bionic-amd64-server-20190516.img 
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
  | key_name | 
testbed-juju-prod-ues-proposed-migration-machine-11 
   |
  | metadata | {}   
  |
  | name | 
adt-bionic-amd64-systemd-upstream-20190516-051604   
   |
  | net_ues_proposed_migration network   | 10.42.40.13  
  |
  | os-extended-volumes:volumes_attached | []   
  |
  | progress | 0
  |
  | security_groups  | autopkgtest@lcy01-27.secgroup
  |
  | status   | ACTIVE   
  |
  | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 
  |
  | updated  | 2019-05-16T07:00:42Z 

[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week

2019-06-29 Thread Evgeny Vereshchagin
Regarding i386, I downloaded the log and took a look at what failed
there. Turns out all the tests except for TEST-34-DYNAMICUSERMIGRATE,
where the global timeout kicked in, passed. Apparently, to judge from
https://salsa.debian.org/systemd-
team/systemd/blob/master/debian/tests/upstream, on Ubuntu CI the tests
are still run one by one whereas on CentOS CI we started to run them in
parallel back in March (https://github.com/systemd/systemd-centos-
ci/pull/78) so it's no wonder the whole test times out sporadically. I
don't expect the script in the Debian package to be fixed any time soon
so could anyone either bump up the timeout or turn the test off?

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

Title:
  Ubuntu CI has been flaky for a week

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  It was originally reported in 
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days 
ago. To judge from the logs VMs can't be rebooted there:
  ```
  Ubuntu 18.04.2 LTS autopkgtest ttyS0

  autopkgtest login:
  ---
  --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
  
+--++
  | Property | Value
  |
  
+--++
  | OS-DCF:diskConfig| MANUAL   
  |
  | OS-EXT-AZ:availability_zone  | nova 
  |
  | OS-EXT-SRV-ATTR:host | euler
  |
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | euler.lcy01.scalingstack 
  |
  | OS-EXT-SRV-ATTR:instance_name| instance-003d216a
  |
  | OS-EXT-STS:power_state   | 1
  |
  | OS-EXT-STS:task_state| -
  |
  | OS-EXT-STS:vm_state  | active   
  |
  | OS-SRV-USG:launched_at   | 2019-05-16T07:00:42.00   
  |
  | OS-SRV-USG:terminated_at | -
  |
  | accessIPv4   |  
  |
  | accessIPv6   |  
  |
  | config_drive |  
  |
  | created  | 2019-05-16T07:00:33Z 
  |
  | flavor   | autopkgtest 
(f878e70e-9991-46e0-ba02-8ea159a71656) |
  | hostId   | 
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
   |
  | id   | 91e76a78-d05c-412a-b383-55a26010ae69 
  |
  | image| 
adt/ubuntu-bionic-amd64-server-20190516.img 
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
  | key_name | 
testbed-juju-prod-ues-proposed-migration-machine-11 
   |
  | metadata | {}   
  |
  | name | 
adt-bionic-amd64-systemd-upstream-20190516-051604   
   |
  | net_ues_proposed_migration network   | 10.42.40.13  
  |
  | os-extended-volumes:volumes_attached | []   
  |
  | progress | 0
  |
  | security_groups  | autopkgtest@lcy01-27.secgroup
  |
  | status  

[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week

2019-06-29 Thread Evgeny Vereshchagin
> Opened MR to blacklist TEST-15 and TEST-22

That PR on GitHub hasn't been merged yet so I think it's too soon to
turn those tests off.

> ah, ok - so I did look into this, or at least some failures really
similar to this, a while back, for bug 1831468.

As far as I can tell, several tests failed there because QEMU_TIMEOUT
kicked in. It's different from what is going on on i386 on GitHub where
the whole upstream test fails due to the global timeout.

> Let me know if that sounds familiar or if you have any debugging
suggestions

Depending on where the test is run it could be 300s isn't enough for it
to finish. Given that it's not particularly popular platform I assume
it's run in VMs where the upstream test also launch VMs with QEMU with
no acceleration whatsoever. Could you try bumping up QEMU_TIMEOUT to see
whether it helps?

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

Title:
  Ubuntu CI has been flaky for a week

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  It was originally reported in 
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days 
ago. To judge from the logs VMs can't be rebooted there:
  ```
  Ubuntu 18.04.2 LTS autopkgtest ttyS0

  autopkgtest login:
  ---
  --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
  
+--++
  | Property | Value
  |
  
+--++
  | OS-DCF:diskConfig| MANUAL   
  |
  | OS-EXT-AZ:availability_zone  | nova 
  |
  | OS-EXT-SRV-ATTR:host | euler
  |
  | OS-EXT-SRV-ATTR:hypervisor_hostname  | euler.lcy01.scalingstack 
  |
  | OS-EXT-SRV-ATTR:instance_name| instance-003d216a
  |
  | OS-EXT-STS:power_state   | 1
  |
  | OS-EXT-STS:task_state| -
  |
  | OS-EXT-STS:vm_state  | active   
  |
  | OS-SRV-USG:launched_at   | 2019-05-16T07:00:42.00   
  |
  | OS-SRV-USG:terminated_at | -
  |
  | accessIPv4   |  
  |
  | accessIPv6   |  
  |
  | config_drive |  
  |
  | created  | 2019-05-16T07:00:33Z 
  |
  | flavor   | autopkgtest 
(f878e70e-9991-46e0-ba02-8ea159a71656) |
  | hostId   | 
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
   |
  | id   | 91e76a78-d05c-412a-b383-55a26010ae69 
  |
  | image| 
adt/ubuntu-bionic-amd64-server-20190516.img 
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
  | key_name | 
testbed-juju-prod-ues-proposed-migration-machine-11 
   |
  | metadata | {}   
  |
  | name | 
adt-bionic-amd64-systemd-upstream-20190516-051604   
   |
  | net_ues_proposed_migration network   | 10.42.40.13  
  |
  | os-extended-volumes:volumes_attached | []   
  |
  | progress | 0
 

[Touch-packages] [Bug 1834400] Re: pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed

2019-06-29 Thread brian_p
The 8715 has been supported since HPLIP 3.16.5. I cannot understand why
you cannot use a version which is packaged by your distro. Not unless
your objective is to help test 3.19.5/3.19.6.

>From your error_log:

 > PID 11639 (/usr/lib/cups/filter/hpcups) stopped with status 127 (File
too large)

I've never seen this before and do not understand it.

 > [Job 81] Unable to open raster stream - : Broken pipe
 > [Job 81] GPL Ghostscript 9.26: Unrecoverable error, exit code 1

Perturbing. On Debian unstable (HPLIP 3.18.12) I can set up a print
queue for your printer and (as root) do

cupsfilter -p /etc/cups/ppd/8715.ppd -m printer/foo -e
/etc/nsswitch.conf > out.dat 2>log

The log shows no errors.

If your objective is to get printing working, I would set up one of
these queues:

 lpadmin -p 8715 -v ipp://HPFC3FDBEFEEC1.local:631/ipp/print -E -m
everywhere

 lpadmin -p 8715 -v ipp://HPFC3FDBEFEEC1.local:631/ipp/print -E -m
driverless:ipp://HPFC3FDBEFEEC1.local:631/ipp/print

-- 
Brian.

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

Title:
  pc reports that HP OfficeJet Pro 8715 printed file, but nothing has
  printed

Status in HPLIP:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  I attempted to print a file on a network printer which was set up via
  HPLIP. The PC reports that the print job has started and completed on
  the network printer, but in fact the network printer has not printed
  anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1834400/+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 1833450] Re: package libpython2.7-dev 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

2019-06-29 Thread vaibhav singhal
is there any update ???

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

Title:
  package libpython2.7-dev 2.7.15~rc1-1ubuntu0.1 failed to
  install/upgrade: dpkg-deb --control subprocess returned error exit
  status 2

Status in python2.7 package in Ubuntu:
  New

Bug description:
  when i opened my system, this bug occurred. I don't know what's the
  issue. I've found so many things but not working in this case.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libpython2.7-dev 2.7.15~rc1-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Jun 19 08:25:58 2019
  DuplicateSignature:
   package:libpython2.7-dev:2.7.15~rc1-1ubuntu0.1
   Unpacking python2.7-dev (2.7.15-4ubuntu4~18.04) over (2.7.15~rc1-1ubuntu0.1) 
...
   dpkg-deb: error: 
'/tmp/apt-dpkg-install-5GWLxY/20-libpython2.7-dev_2.7.15-4ubuntu4~18.04_amd64.deb'
 is not a Debian format archive
   dpkg: error processing archive 
/tmp/apt-dpkg-install-5GWLxY/20-libpython2.7-dev_2.7.15-4ubuntu4~18.04_amd64.deb
 (--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  InstallationDate: Installed on 2018-12-22 (178 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.11
  SourcePackage: python2.7
  Title: package libpython2.7-dev 2.7.15~rc1-1ubuntu0.1 failed to 
install/upgrade: dpkg-deb --control subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1833450/+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 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1

2019-06-29 Thread Andreas Amann
@ahasenack:

Yes, that ppa (in #19) also solved the problem mentinoned in my linked 
bugreport 
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833896

A big "thank you" to you and all others who helped to solve this
problem!!

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

Title:
  18.04/Apache2: rejecting client initiated renegotiation due to openssl
  1.1.1

Status in apache2 package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Incomplete
Status in apache2 source package in Bionic:
  Confirmed
Status in apache2 source package in Cosmic:
  Confirmed

Bug description:
  I am using Apache2 with client certificate authentication.
  Since recently (last week) and without any configuration changes, the 
following errors occur frequently:

  AH02042: rejecting client initiated renegotiation

  Client connections are very slow and sometimes it takes more than a minute 
until a weg page can be opened in the browser.
  Before installation of the latest security fixes last week, this error did 
not occur.

  Could it be related to
  https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689?

  
  System information:

  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  apache2:
Installiert:   2.4.29-1ubuntu4.6
Installationskandidat: 2.4.29-1ubuntu4.6
Versionstabelle:
   *** 2.4.29-1ubuntu4.6 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.4.29-1ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  openssl:
Installiert:   1.1.1-1ubuntu2.1~18.04.2
Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2
Versionstabelle:
   *** 1.1.1-1ubuntu2.1~18.04.2 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.0g-2ubuntu4.3 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   1.1.0g-2ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+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 1834731] [NEW] System hung while booting

2019-06-29 Thread Venugopal
Public bug reported:

Booting is not happening properly. Either it will display few options
like Ubnut, Advance Ubuntu or it is getting hung.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-53.57-generic 4.15.18
Uname: Linux 4.15.0-53-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Jun 29 11:54:30 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-51-generic, i686: installed
 rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-53-generic, i686: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04ab]
InstallationDate: Installed on 2013-05-06 (2244 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MachineType: Dell Inc. Vostro 460
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-53-generic 
root=UUID=37e1c2cf-5770-4b8c-af11-1fdfc29f5133 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0Y2MRG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/21/2011:svnDellInc.:pnVostro460:pvr:rvnDellInc.:rn0Y2MRG:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 460
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat Jun 29 11:52:13 2019
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputDell Dell USB Entry Keyboard KEYBOARD, id 8
 inputUSB Optical MouseMOUSE, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.3
xserver.video_driver: modeset

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


** Tags: apport-bug bionic i386 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/1834731

Title:
  System hung while booting

Status in xorg package in Ubuntu:
  New

Bug description:
  Booting is not happening properly. Either it will display few options
  like Ubnut, Advance Ubuntu or it is getting hung.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-53.57-generic 4.15.18
  Uname: Linux 4.15.0-53-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jun 29 11:54:30 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-51-generic, i686: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-53-generic, i686: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04ab]
  InstallationDate: Installed on 2013-05-06 (2244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MachineType: Dell Inc. Vostro 460
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-53-generic 
root=UUID=37e1c2cf-5770-4b8c-af11-1fdfc29f5133 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2011
  dmi.bios.vendor: Dell Inc.