[Desktop-packages] [Bug 1864281] [NEW] Xorg freeze

2020-02-21 Thread Avanish Kumar
Public bug reported:

After recently upgrade, Initial I am getting nothing on my desktop,
after that, I manually set everything from gnome tweak tool , but my
lock screen has some issue- " I am unable to lock my system and while
rebooting I am getting sched_error_20"

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Feb 22 13:10:10 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: I don't know
GpuHangStarted: Since before I upgraded
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:39f1]
   Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:39f1]
InstallationDate: Installed on 2020-01-17 (36 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: LENOVO 80TV
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=8ae73105-7444-42f0-836d-b0bf892d8e47 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: 3JCN19WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Torronto 5C2
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-15IKB
dmi.modalias: 
dmi:bvnLENOVO:bvr3JCN19WW:bd08/10/2016:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnTorronto5C2:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB:
dmi.product.family: IDEAPAD
dmi.product.name: 80TV
dmi.product.sku: LENOVO_MT_80TV_BU_idea_FM_Lenovo ideapad 310-15IKB
dmi.product.version: Lenovo ideapad 310-15IKB
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.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 freeze ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1864281

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  After recently upgrade, Initial I am getting nothing on my desktop,
  after that, I manually set everything from gnome tweak tool , but my
  lock screen has some issue- " I am unable to lock my system and while
  rebooting I am getting sched_error_20"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 22 13:10:10 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: I don't know
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:39f1]
 Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:39f1]
  InstallationDate: Installed on 2020-01-17 (36 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 80TV
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=8ae73105-7444-42f0-836d-b0bf892d8e47 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3JCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Torronto 5C2
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  

[Desktop-packages] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression

2020-02-21 Thread Mathew Hodson
** Tags added: regression-release

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  [Impact]

   * IGLX is a way for an opengl application sending the 3D drawing GLX
  commands to the Xorg server for rendering instead of using the DRI
  infrastructure it is commonplace for High Performance Compute and
  Scientific institutions to use this feature of the Xorg server. (ref:
  https://www.phoronix.com/scan.php?page=news_item=Xorg-IGLX-
  Potential-Bye-Bye)

   * The feature is completely broken, currently, and any attempt to use
  it will cause the Xorg server to crash. This feature has been broken
  since a commit upstream in 2016.

   * The attached patch is from the revert commit entered into the
  upstream repository on 28 Jan 2020 following a git bisect of the bug
  discovering the offending commit.

  [Test Case]

   * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the
  following contents:

  ```
  Section "ServerFlags"
  Option "IndirectGLX" "on"
  EndSection
  ```

   * Log out of your Xorg session
   * Switch to a VT (Ctrl+Alt+F2) and login
   * Run `sudo systemctl restart gdm` to restart Xorg
   * Login to the graphical session
   * If you do not have mesa-utils installed, then install it with the terminal 
command `sudo apt install mesa-utils`
   * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears`
   * If the fix is successful then glxgears should start and remain active 
without the Xorg server or glxgears crashing/segfaulting

  [Regression Potential]

   * This change is within DRI-related functionality and so might break
  all 3D accelerated applications.

   * There is a potential that the change is insufficient to fix the
  IGLX feature and so attempts to use it may still have undesirable and
  undefined results.

   * Upstream has run the patch through their CI system, which passed
  with no errors. This does not necessarily mean the patch will achieve
  the desired results, but at least indicates that the code does compile
  cleanly and can start an Xvfb headless instance.

  [Other Info]

   * This bug affects Ubuntu releases all the way back to, and
  including, Bionic 18.04.

   Original Bug Report Follows 

  There's already an upstream bug report here:

  https://bugs.freedesktop.org/show_bug.cgi?id=99555

  Basically, with Option "IndirectGLX" "True" and
  LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear:

  steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears
  Running synchronized to the vertical refresh.  The framerate should be
  approximately the same as the monitor refresh rate.
  X Error of failed request:  255
    Major opcode of failed request:  155 (GLX)
    Minor opcode of failed request:  1 (X_GLXRender)
    Serial number of failed request:  42
    Current serial number in output stream:  936

  I am trying to run what is effectively a traditional X Terminal, but
  as the hardware I am using has a 3D accelerated chipset it seems
  sensible to try to use it..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Jun 12 10:09:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2018-05-31 (11 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: AZW S I
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/xubuntu--vg-root ro noresume
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 00.12
  dmi.board.asset.tag: Default string
  dmi.board.name: AB1
  dmi.board.vendor: IP3 Tech
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Desktop-packages] [Bug 1864274] Re: crunchy pixels

2020-02-21 Thread Seth Arnold
** Tags added: champagne

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1864274

Title:
  crunchy pixels

Status in firefox package in Ubuntu:
  New

Bug description:
  Hello, after upgrading firefox (and many other packages) on focal
  today, I've got some video artifacts in firefox.

  When typing in text boxes and text fields, the new character is drawn
  very slowly, pixel-by-pixel, and isn't complete until the cursor has
  moved on. When larger portions of the screen are updated, it looks a
  lot like the entire window is being run through a video codec or you
  can see parts of the video memory from other processes. (But it looks
  more deliberate and predictable than either of these descriptions.)

  So far Firefox is the only application I've found that is affected.
  urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.

  I did get cairo package update today, but the changelog is just:

  pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
   -- Matthias Klose   Sat, 08 Feb 2020 11:15:23 +

  And an xorg update:

  xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
   -- Matthias Klose   Sat, 08 Feb 2020 11:21:28 +

  
  So I don't believe these are involved.

  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
  (rev 07)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 73.0.1+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sarnold3296 F pulseaudio
   /dev/snd/controlC0:  sarnold3296 F pulseaudio
  BuildID: 20200217142647
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  Channel: Unavailable
  Date: Sat Feb 22 05:41:10 2020
  ForcedLayersAccel: False
  IncompatibleExtensions:
   Pentadactyl - pentadac...@dactyl.googlecode.com
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  IpRoute:
   default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100 
   10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1 
   192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric 
100 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:737
  PrefSources: prefs.js
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression

2020-02-21 Thread Mathew Hodson
** Tags removed: fixed-upstream
** Tags added: patch-accepted-upstream

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  [Impact]

   * IGLX is a way for an opengl application sending the 3D drawing GLX
  commands to the Xorg server for rendering instead of using the DRI
  infrastructure it is commonplace for High Performance Compute and
  Scientific institutions to use this feature of the Xorg server. (ref:
  https://www.phoronix.com/scan.php?page=news_item=Xorg-IGLX-
  Potential-Bye-Bye)

   * The feature is completely broken, currently, and any attempt to use
  it will cause the Xorg server to crash. This feature has been broken
  since a commit upstream in 2016.

   * The attached patch is from the revert commit entered into the
  upstream repository on 28 Jan 2020 following a git bisect of the bug
  discovering the offending commit.

  [Test Case]

   * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the
  following contents:

  ```
  Section "ServerFlags"
  Option "IndirectGLX" "on"
  EndSection
  ```

   * Log out of your Xorg session
   * Switch to a VT (Ctrl+Alt+F2) and login
   * Run `sudo systemctl restart gdm` to restart Xorg
   * Login to the graphical session
   * If you do not have mesa-utils installed, then install it with the terminal 
command `sudo apt install mesa-utils`
   * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears`
   * If the fix is successful then glxgears should start and remain active 
without the Xorg server or glxgears crashing/segfaulting

  [Regression Potential]

   * This change is within DRI-related functionality and so might break
  all 3D accelerated applications.

   * There is a potential that the change is insufficient to fix the
  IGLX feature and so attempts to use it may still have undesirable and
  undefined results.

   * Upstream has run the patch through their CI system, which passed
  with no errors. This does not necessarily mean the patch will achieve
  the desired results, but at least indicates that the code does compile
  cleanly and can start an Xvfb headless instance.

  [Other Info]

   * This bug affects Ubuntu releases all the way back to, and
  including, Bionic 18.04.

   Original Bug Report Follows 

  There's already an upstream bug report here:

  https://bugs.freedesktop.org/show_bug.cgi?id=99555

  Basically, with Option "IndirectGLX" "True" and
  LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear:

  steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears
  Running synchronized to the vertical refresh.  The framerate should be
  approximately the same as the monitor refresh rate.
  X Error of failed request:  255
    Major opcode of failed request:  155 (GLX)
    Minor opcode of failed request:  1 (X_GLXRender)
    Serial number of failed request:  42
    Current serial number in output stream:  936

  I am trying to run what is effectively a traditional X Terminal, but
  as the hardware I am using has a 3D accelerated chipset it seems
  sensible to try to use it..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Jun 12 10:09:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2018-05-31 (11 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: AZW S I
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/xubuntu--vg-root ro noresume
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 00.12
  dmi.board.asset.tag: Default string
  dmi.board.name: AB1
  dmi.board.vendor: IP3 Tech
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Desktop-packages] [Bug 1864274] [NEW] crunchy pixels

2020-02-21 Thread Seth Arnold
Public bug reported:

Hello, after upgrading firefox (and many other packages) on focal today,
I've got some video artifacts in firefox.

When typing in text boxes and text fields, the new character is drawn
very slowly, pixel-by-pixel, and isn't complete until the cursor has
moved on. When larger portions of the screen are updated, it looks a lot
like the entire window is being run through a video codec or you can see
parts of the video memory from other processes. (But it looks more
deliberate and predictable than either of these descriptions.)

So far Firefox is the only application I've found that is affected.
urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.

I did get cairo package update today, but the changelog is just:

pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
  * No-change rebuild with fixed binutils on arm64.
 -- Matthias Klose   Sat, 08 Feb 2020 11:15:23 +

And an xorg update:

xorg (1:7.7+19ubuntu14) focal; urgency=medium
  * No-change rebuild with fixed binutils on arm64.
 -- Matthias Klose   Sat, 08 Feb 2020 11:21:28 +


So I don't believe these are involved.

00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
(rev 07)

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 73.0.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic.
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  sarnold3296 F pulseaudio
 /dev/snd/controlC0:  sarnold3296 F pulseaudio
BuildID: 20200217142647
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
   Mixer name   : 'Realtek ALC285'
   Components   : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
   Controls  : 53
   Simple ctrls  : 15
Card1.Amixer.info:
 Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-:00:14.0-4.2.4, 
high speed'
   Mixer name   : 'USB Mixer'
   Components   : 'USB17ef:306f'
   Controls  : 9
   Simple ctrls  : 4
Channel: Unavailable
Date: Sat Feb 22 05:41:10 2020
ForcedLayersAccel: False
IncompatibleExtensions:
 Pentadactyl - pentadac...@dactyl.googlecode.com
 English (GB) Language Pack - langpack-en...@firefox.mozilla.org
 English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
 Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
IpRoute:
 default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100 
 10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1 
 192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric 
100 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:737
PrefSources: prefs.js
ProcEnviron:
 TERM=rxvt-unicode-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET69W (1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KHCTO1WW
dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1864274

Title:
  crunchy pixels

Status in firefox package in Ubuntu:
  New

Bug description:
  Hello, after upgrading firefox (and many other packages) on focal
  today, I've got some video artifacts in firefox.

  When typing in text boxes and text fields, the new character is drawn
  very slowly, pixel-by-pixel, and isn't complete until the cursor has
  moved on. When larger portions of the screen are updated, it looks a
  lot like the entire window is being run through a video codec or you
  can see parts of the video memory from other processes. (But it looks
  more deliberate and predictable than either of these 

[Desktop-packages] [Bug 1863514]

2020-02-21 Thread Adw-mozilla
I searched my browser history to find where some recent shield icon work
was being done, and it was this component. I considered Site Identity
too, but I don't know which is more appropriate. Let's move it to site
identity if you object so much then.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1863514

Title:
  Red fill address bar if the website is insecure.

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) Firefox 72
  3) When visiting an insecure website, the address bar should be red filled.
  4) The lock icon with a red slash is not very noticeable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1863514/+subscriptions

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


[Desktop-packages] [Bug 1863514]

2020-02-21 Thread Gingerbread-man-2
> Component: Address Bar → Protections UI

Firefox :: Protections UI - "For bugs and feature requests in Firefox’s
Anti-Tracking Protections UI such as the Protection Panel and the
Protection Report."

Please explain this move. This is about the entirety of the address bar
and it doesn't have anything to do with anti-tracking. Even Firefox ::
Site Identity would make more sense, even though this extends beyond the
padlock.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1863514

Title:
  Red fill address bar if the website is insecure.

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) Firefox 72
  3) When visiting an insecure website, the address bar should be red filled.
  4) The lock icon with a red slash is not very noticeable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1863514/+subscriptions

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


[Desktop-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

2020-02-21 Thread Mathew Hodson
** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as 
original description.
  2. ipv6 manual, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses 
fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##
  3. ipv6 auto, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
  network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
  network-manager | 1.22.4-1ubuntu2 | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 NetworkTest 

[Desktop-packages] [Bug 1857375] Re: Regression 19.10 Less Responsiveness

2020-02-21 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1857375

Title:
  Regression 19.10 Less Responsiveness

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Latest version with all updates of 19.10 is considerably slower than
  19.04.  Gnome shell especially feels more buggier in different
  applications I use.  The behavior of the dock is not consistent with
  how it displays full screen applications as well.  One application has
  the dock not instantaneously disappear from visibility but sticks to
  the full-screen for 2 seconds before fading (it doesn't feel like
  actual fullscreen).  Inputs are laggier on the video that is rendered.
  Overall I feel like something was modified significantly on Mutter or
  Gnome shell or the visual output that I can't describe or pinpoint.
  I've reinstalled 19.04 for increased responsiveness.  I will note that
  20.04 development edition felt snappier and faster than 19.10 but it
  was still not as fast as 19.04.

  It's been frustrating because 19.04 was significantly faster than
  18.10 and noticeably so.  Please tell me what additional information
  is needed.

  19.10 feels horrible to me and like a step backwards and I've tried to
  tolerate it.  Please help.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857375/+subscriptions

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


[Desktop-packages] [Bug 1862053] Re: Compiler gets stuck (or extremely slow) on ppc64el

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package gcc-9 - 9.2.1-29ubuntu1

---
gcc-9 (9.2.1-29ubuntu1) focal; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Disable the LTO build on arm64, armhf for now, takes 24+ hours ...

gcc-9 (9.2.1-29) unstable; urgency=medium

  * Update to git 20200220 from the gcc-9 branch.
- Fix PR middle-end/92768, PR middle-end/90313, PR tree-optimization/93434,
  PR tree-optimization/92710, PR tree-optimization/92420, PR target/90724,
  PR target/93724 (x86), PR target/93743 (x86), PR tree-optimization/93744,
  PR target/93704 (SPARC), PR rtl-optimization/88879, PR middle-end/90648,
  PR tree-optimization/93381, PR tree-optimization/93439,
  PR middle-end/93054, PR debug/92763, PR tree-optimization/92704,
  PR middle-end/92674, PR target/93696 (x86), PR target/93670 (x86),
  PR target/93637 (x86), PR target/65782 (x86), PR libgomp/93515,
  PR libgomp/93515, PR middle-end/93555, PR middle-end/93505,
  PR target/93418 (x86), PR rtl-optimization/93402, PR target/85667,
  PR rtl-optimization/91838, PR c/93576, PR c++/61414, PR c++/93557,
  PR c++/91118, PR fortran/93580, PR fortran/93463, PR libgcc/85334,
  PR fortran/93714.
  * Fix PR target/93658 (PPC), proposed patch. LP: #1862053.

 -- Matthias Klose   Thu, 20 Feb 2020 10:20:02 +0100

** Changed in: gcc-9 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ghostscript in Ubuntu.
https://bugs.launchpad.net/bugs/1862053

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  In Progress
Status in gcc-9 package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Confirmed

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1862053/+subscriptions

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


[Desktop-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

2020-02-21 Thread Phuc Minh Cai
Hi Kai Heng Feng,

I've tried to install Ubuntu 18.04, also same issue.

Should I continue this bug with version 18.04 or Focal?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1860754

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 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: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1863992] Re: 32 bit libGL missing

2020-02-21 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1863992

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu.
https://bugs.launchpad.net/bugs/1863992

Title:
  32 bit libGL missing

Status in nvidia-graphics-drivers-430 package in Ubuntu:
  New

Bug description:
  Though the packages seem to be installed in the same location as
  before /usr/lib32/nvidia-430 but the system apparently doesn't pick it
  up

  ldconfig -p | grep libGL.so
libGL.so.1 (libc6,x86-64) => /usr/lib/nvidia-430/libGL.so.1
libGL.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGL.so
libGL.so (libc6,x86-64) => /usr/lib/nvidia-430/libGL.so

  a couple of wine apps stops working complaining that libGL.so not
  found.

  With Nvidia-418

  ldconfig -p | grep libGL.so
libGL.so.1 (libc6,x86-64) => /usr/lib/nvidia-418/libGL.so.1
libGL.so.1 (libc6) => /usr/lib32/nvidia-418/libGL.so.1
libGL.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGL.so
libGL.so (libc6,x86-64) => /usr/lib/nvidia-418/libGL.so
libGL.so (libc6) => /usr/lib32/nvidia-418/libGL.so

  See with Nvidia-430 the 32 bit libGL.so is not being picked up.

  Ubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1863992/+subscriptions

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


[Desktop-packages] [Bug 1864260] [NEW] TEST-UNEXPECTED-FAIL

2020-02-21 Thread Dimitri John Ledkov
Public bug reported:

## non262/Intl/RelativeTimeFormat/format.js: rc = 3, run time = 0.050082
non262/Intl/RelativeTimeFormat/format.js:61:3 Error: Assertion failed: got 
"this minute", expected "in 0 
minutes"
Stack:
  @non262/Intl/RelativeTimeFormat/format.js:61:3
TEST-UNEXPECTED-FAIL | non262/Intl/RelativeTimeFormat/format.js | (args: "") 
[0.1 s]
{"action": "test_start", "pid": 9608, "source": "jstests", "test": 
"non262/Intl/RelativeTimeFormat/format.js", "thread": "main", "time": 
1582322659.4439561}
{"action": "test_end", "extra": {"jitflags": []}, "pid": 9608, "source": 
"jstests", "status": "FAIL", "test": 
"non262/Intl/RelativeTimeFormat/format.js", "thread": "main", "time": 
1582322659.494038}

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


** Tags: champagne update-excuse

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mozjs60 in Ubuntu.
https://bugs.launchpad.net/bugs/1864260

Title:
  TEST-UNEXPECTED-FAIL

Status in mozjs60 package in Ubuntu:
  New

Bug description:
  ## non262/Intl/RelativeTimeFormat/format.js: rc = 3, run time = 0.050082
  non262/Intl/RelativeTimeFormat/format.js:61:3 Error: Assertion failed: got 
"this minute", expected "in 0 
  minutes"
  Stack:
@non262/Intl/RelativeTimeFormat/format.js:61:3
  TEST-UNEXPECTED-FAIL | non262/Intl/RelativeTimeFormat/format.js | (args: "") 
[0.1 s]
  {"action": "test_start", "pid": 9608, "source": "jstests", "test": 
"non262/Intl/RelativeTimeFormat/format.js", "thread": "main", "time": 
1582322659.4439561}
  {"action": "test_end", "extra": {"jitflags": []}, "pid": 9608, "source": 
"jstests", "status": "FAIL", "test": 
"non262/Intl/RelativeTimeFormat/format.js", "thread": "main", "time": 
1582322659.494038}

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

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


[Desktop-packages] [Bug 1861913] Re: "Strict" tracking protection sometimes causes _all_ content to fail to display on browser launch

2020-02-21 Thread Dan Watkins
Thanks Olivier!  I've filed
https://bugzilla.mozilla.org/show_bug.cgi?id=1617292

** Bug watch added: Mozilla Bugzilla #1617292
   https://bugzilla.mozilla.org/show_bug.cgi?id=1617292

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1861913

Title:
  "Strict" tracking protection sometimes causes _all_ content to fail to
  display on browser launch

Status in firefox package in Ubuntu:
  New

Bug description:
  This morning I booted my machine and launched Firefox.  I restored my
  tabs from my previous session, and _none of them_ displayed any
  content.  The tabs included pins, regular sites, and extension dialogs
  (specifically, a couple of instances of the LastPass 2FA prompt).
  Further to that, Firefox menus also wouldn't display; either via
  right-click on tabs, or via the "hamburger" menu in the top-right.  (I
  could still close tabs via Ctrl-W for non-pinned tabs, or via middle-
  click for pinned tabs.)

  favicons were displayed correctly, and I confirmed that the pages were
  actually being fetched from the remote sites because I typed the
  address for a page I know redirects and the redirect happened
  (specifically, "!g foo" in my address bar caused DuckDuckGo to
  redirect me to Google).

  Restarting the browser did not fix this.  Closing all of my tabs and
  restarting the browser did not fix this.  Closing all of my tabs and
  restarting the browser, however, _did_ allow the Firefox menus to
  render (provided I didn't try to open any web pages before using
  them), which allowed me to switch "Enhanced Tracking Protection" from
  Strict to Standard, fixing the problem.

  (This is the second time I've experienced this exact behaviour, which
  is how I knew to try modifying the tracking protection setting.  The
  last time was on an older version of Firefox in August:
  https://wrestle.town/@Odd_Bloke/102655281770357045)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 72.0.2+build1-0ubuntu1
  Uname: Linux 5.4.5-050405-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  BuildID: 20200117190643
  Channel: Unavailable
  CurrentDesktop: i3
  Date: Tue Feb  4 13:01:53 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-05-07 (273 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-94f8002b-6eb0-4faf-98c0-257a62150805
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:724
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=72.0.2/20200117190643 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2019-11-15 (80 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Desktop-packages] [Bug 1862541] Re: Ctrl+A does not always select all contents of the visited folder (can lead to permanently lost work!)

2020-02-21 Thread Linus
I have now opened an issue:

https://gitlab.gnome.org/GNOME/nautilus/issues/1389

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1389
   https://gitlab.gnome.org/GNOME/nautilus/issues/1389

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1862541

Title:
  Ctrl+A does not always select all contents of the visited folder (can
  lead to permanently lost work!)

Status in nautilus package in Ubuntu:
  New

Bug description:
  The other day I wanted to move all the files in one folder over to
  another folder using the cut + paste method. I visited the source
  folder, pressed Ctrl+A (select all) followed by Ctrl+X (cut), and then
  browsed to the target folder and pressed Ctrl+V (paste). Then I went
  and deleted the source folder, which I reasonably assumed to now be
  empty. However, it turned out that not all the files had been moved,
  and that the remaining files had been deleted along with the original
  folder (which I deleted permanently with Shift+Del, I might add).

  After some troubleshooting I've been able to determine the most likely
  cause. When visiting a folder, there is usually some delay during
  which the contents of the folder are read from disk and the thumbnails
  are being updated (for large folders this delay can be on the order of
  seconds). If Ctrl+A is pressed before this process has finished, only
  a subset of the files/folders are selected. Thus, I probably only
  cut/moved some of the files, and left the remaining files behind.

  This is a very serious bug, as it can lead to permanent loss of work
  (as it did for me).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
  Uname: Linux 4.15.0-76-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  9 21:22:24 2020
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2020-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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


[Desktop-packages] [Bug 1862544] Re: Double-clicking a folder sometimes opens another, recently visited folder

2020-02-21 Thread Linus
I have now opened an issue:

https://gitlab.gnome.org/GNOME/nautilus/issues/1390

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1390
   https://gitlab.gnome.org/GNOME/nautilus/issues/1390

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1862544

Title:
  Double-clicking a folder sometimes opens another, recently visited
  folder

Status in nautilus package in Ubuntu:
  New

Bug description:
  The following happens for me very frequently. Say I have the following
  folder structure:

  A
  |- B
  |- C
  |- some other files/folders...

  I'm currently browsing the folder B. Then I go up one level, to A, by
  pressing backspace. I then immediately double-click on the icon for
  folder C to enter into it. Very frequently, this instead takes me back
  into folder B.

  What appears to be happening is that when I go up from B to A, if I
  double-click the icon for C while the contents of A are being read
  from disk and the thumbnails are being refreshed, the program
  registers that I have double-clicked something, but after the
  thumbnail refresh has finished, the "selected folder" reverts back to
  B. Hence, the program thinks I double-clicked the icon for B instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
  Uname: Linux 4.15.0-76-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  9 21:42:19 2020
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2020-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package qt4-x11 - 4:4.8.7+dfsg-20ubuntu2

---
qt4-x11 (4:4.8.7+dfsg-20ubuntu2) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Fri, 14 Feb 2020 15:07:13
-0300

** Changed in: qt4-x11 (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  Fix Released
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  Fix Released
Status in opendnssec package in Ubuntu:
  Fix Released
Status in opensmtpd-extras package in Ubuntu:
  Fix Released
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  Fix Released
Status in pvpgn package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  Fix Released
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  Fix Released
Status in tntdb package in Ubuntu:
  Fix Released
Status in voms-mysql-plugin package in Ubuntu:
  Fix Released
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  Fix Released
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1864253] [NEW] Pulseaudio sink/source selection, weird behaviour.

2020-02-21 Thread Matthias Kohler
Public bug reported:

I have a Laptop connected to an USB-C dock. By default the docks analog
audio output is chosen as the default pulse audio sink. I want that the
analog output of the Laptop is the default, hence I configured this in
/etc/pulse/default.py

This does not work and journalctl informs me that the device chosen by me
(alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached output
from journalctl.

I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp
to prevent pulseaudio getting started in gdm to prevent device capture.

This does not work, the device does still not exist.
Restarting pulseaudio sometimes, but not always sets the configured
default sink. Furthermore plugging in the headphones in the Laptops analog input
switches audio to the dock.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.4
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  findus 3055 F pulseaudio
 /dev/snd/controlC1:  findus 3055 F pulseaudio
 /dev/snd/controlC0:  findus 3055 F pulseaudio
 /dev/snd/pcmC0D0p:   findus 3055 F...m pulseaudio
CurrentDesktop: i3
Date: Fri Feb 21 22:19:04 2020
InstallationDate: Installed on 2019-06-13 (253 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2IET80W (1.58 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20N3S0UB00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N3S0UB00:pvrThinkPadT490:rvnLENOVO:rn20N3S0UB00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T490
dmi.product.name: 20N3S0UB00
dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490
dmi.product.version: ThinkPad T490
dmi.sys.vendor: LENOVO
modified.conffile..etc.pulse.daemon.conf: [modified]
modified.conffile..etc.pulse.default.pa: [modified]
modified.conffile..etc.pulse.system.pa: [modified]
mtime.conffile..etc.pulse.daemon.conf: 2020-02-21T20:38:20.081439
mtime.conffile..etc.pulse.default.pa: 2020-02-21T19:27:57.386938
mtime.conffile..etc.pulse.system.pa: 2020-02-21T15:23:09.470494

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


** Tags: amd64 apport-bug bionic

** Attachment added: "journalctl_pulseaudio.txt"
   
https://bugs.launchpad.net/bugs/1864253/+attachment/5330136/+files/journalctl_pulseaudio.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1864253

Title:
  Pulseaudio sink/source selection, weird behaviour.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a Laptop connected to an USB-C dock. By default the docks analog
  audio output is chosen as the default pulse audio sink. I want that the
  analog output of the Laptop is the default, hence I configured this in
  /etc/pulse/default.py

  This does not work and journalctl informs me that the device chosen by me
  (alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached 
output
  from journalctl.

  I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp
  to prevent pulseaudio getting started in gdm to prevent device capture.

  This does not work, the device does still not exist.
  Restarting pulseaudio sometimes, but not always sets the configured
  default sink. Furthermore plugging in the headphones in the Laptops analog 
input
  switches audio to the dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  findus 3055 F pulseaudio
   /dev/snd/controlC1:  findus 3055 F pulseaudio
   /dev/snd/controlC0:  findus 3055 F pulseaudio
   /dev/snd/pcmC0D0p:   findus 3055 F...m pulseaudio
  CurrentDesktop: i3
  Date: Fri Feb 21 22:19:04 2020
  InstallationDate: Installed on 2019-06-13 (253 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2IET80W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20N3S0UB00
  dmi.board.vendor: 

[Desktop-packages] [Bug 1864244] [NEW] Text selection in address bar does not work as expected

2020-02-21 Thread edgarswooth
Public bug reported:

In Nautilus, I can click "Ctrl+L" to open the address bar. At this
point, the whole address will be selected, which is desirable. However,
if I then press "Right" to place my cursor at the end of the current
path, and then try to use "Shift+Ctrl+Left" to select word-by-word
(e.g., to select and delete the final folder from the path), the whole
path is again selected. It seems that the logic for preselecting the
whole path upon opening the address bar seems to trigger in more
circumstances than just upon opening, and this makes using Nautilus via
keyboard slower and more frictive than necessary. (In general, text
entry widgets that override the operating system's existing conventions
always really annoy me, on desktop or mobile.)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.4-0~ubuntu18.04.5
ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
Uname: Linux 4.15.0-76-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 21 15:44:24 2020
InstallationDate: Installed on 2018-12-17 (431 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LC_CTYPE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: dropbox 2018.11.28

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


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1864244

Title:
  Text selection in address bar does not work as expected

Status in nautilus package in Ubuntu:
  New

Bug description:
  In Nautilus, I can click "Ctrl+L" to open the address bar. At this
  point, the whole address will be selected, which is desirable.
  However, if I then press "Right" to place my cursor at the end of the
  current path, and then try to use "Shift+Ctrl+Left" to select word-by-
  word (e.g., to select and delete the final folder from the path), the
  whole path is again selected. It seems that the logic for preselecting
  the whole path upon opening the address bar seems to trigger in more
  circumstances than just upon opening, and this makes using Nautilus
  via keyboard slower and more frictive than necessary. (In general,
  text entry widgets that override the operating system's existing
  conventions always really annoy me, on desktop or mobile.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
  Uname: Linux 4.15.0-76-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 21 15:44:24 2020
  InstallationDate: Installed on 2018-12-17 (431 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: dropbox 2018.11.28

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

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


[Desktop-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

2020-02-21 Thread Pablo Rodríguez Guillén
I have the same problem on my Asus Zenbook UX430UA (Realtek ALC295)
although I have "5.3.0-40-generic" linux kernel version with Ubuntu
18.04. Comment #8 solved my problem but with "options snd-hda-intel
model=laptop-dmic" in my alsa conf, up and down volume don't change the
speakers volume.

I can only mute the speakers with 0 volume, but I get the same volume
level with 1% volume than the one I get with 100%

With "options snd-hda-intel model=auto" or "options snd-hda-intel
model=alc295" I get the expected behaviour from the speakers but no
record of the internal microphone. I have already tried combining
auto/alc295 with laptop-dmic but I get the behaviour of the first option
I write (like as it were alone)

I thought this was fixed, maybe I am doing something wrong.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  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.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  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/alsa-driver/+bug/1596381/+subscriptions

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


[Desktop-packages] [Bug 1844458] Re: Drop transitional flashplugin-downloader package

2020-02-21 Thread Steve Langasek
This is done now in focal.

** Changed in: flashplugin-nonfree (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to flashplugin-nonfree in Ubuntu.
https://bugs.launchpad.net/bugs/1844458

Title:
  Drop transitional flashplugin-downloader package

Status in flashplugin-nonfree package in Ubuntu:
  Fix Released

Bug description:
  I think the transition is done.  It's in 16.04-19.10 as a transitional
  package.

  Found this because it made this list: https://discourse.ubuntu.com/t
  /community-process-for-32-bit-compatibility/12598

  I don't want anyone thinking that 32-bit Flash is supported on Linux.

  Happy to make a debdiff (or if you point me at where the code is - the
  code here seems out of date) to make a PR.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1844458/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package tango - 9.2.5a+dfsg1-2ubuntu1

---
tango (9.2.5a+dfsg1-2ubuntu1) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Fri, 14 Feb 2020 15:20:27
-0300

** Changed in: tango (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  Fix Released
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  Fix Released
Status in opendnssec package in Ubuntu:
  Fix Released
Status in opensmtpd-extras package in Ubuntu:
  Fix Released
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  Fix Released
Status in pvpgn package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  Fix Released
Status in tntdb package in Ubuntu:
  Fix Released
Status in voms-mysql-plugin package in Ubuntu:
  Fix Released
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  Fix Released
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1862262] Re: [snap] apparmor denials on /sys/devices/virtual/dmi/id/sys_vendor and product_name

2020-02-21 Thread Simon Déziel
So this bug will be fixed when snapd's 2.43 SRU goes through. I
appreciate the pointer for the gpu-process sanboxing problem and its
workaround! Many thanks Jalon!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1862262

Title:
  [snap] apparmor denials on /sys/devices/virtual/dmi/id/sys_vendor and
  product_name

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When starting chromium's snap, those messages are logged:

  Feb  6 12:34:17 foo kernel: [106190.836260] audit: type=1400 
audit(1581010457.097:1372): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/sys_vendor" 
pid=20044 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
  Feb  6 12:34:17 foo kernel: [106190.836401] audit: type=1400 
audit(1581010457.097:1373): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/product_name" pid=20044 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Feb  6 12:34:17 foo chromium_chromium.desktop[20044]: 
[20191:20191:0206/123417.177438:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.

  Chromium seemingly behaves OK but possibly with reduced sandboxing?

  
  Additional info:

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more 
stable way for all
Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: stable
  refresh-date: yesterday at 17:45 EST
  channels:
stable:80.0.3987.87 2020-02-05 (1016) 160MB -
candidate: 80.0.3987.87 2020-02-05 (1016) 160MB -
beta:  80.0.3987.85 2020-02-04 (1014) 160MB -
edge:  81.0.4040.5  2020-02-06 (1018) 161MB -
  installed:   80.0.3987.87(1016) 160MB -

  $ uname -a
  Linux simon-lemur 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862262/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package mysqltcl - 3.052-3ubuntu1

---
mysqltcl (3.052-3ubuntu1) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Fri, 14 Feb 2020 11:36:30
-0300

** Changed in: mysqltcl (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: opensmtpd-extras (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  Fix Released
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  Fix Released
Status in opendnssec package in Ubuntu:
  Fix Released
Status in opensmtpd-extras package in Ubuntu:
  Fix Released
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  Fix Released
Status in pvpgn package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  Fix Released
Status in voms-mysql-plugin package in Ubuntu:
  Fix Released
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  Fix Released
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package opensmtpd-extras - 6.6.0-1ubuntu1

---
opensmtpd-extras (6.6.0-1ubuntu1) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Fri, 14 Feb 2020 14:45:47
-0300

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  Fix Released
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  Fix Released
Status in opendnssec package in Ubuntu:
  Fix Released
Status in opensmtpd-extras package in Ubuntu:
  Fix Released
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  Fix Released
Status in pvpgn package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  Fix Released
Status in voms-mysql-plugin package in Ubuntu:
  Fix Released
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  Fix Released
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package w1retap - 1.4.4-3ubuntu2

---
w1retap (1.4.4-3ubuntu2) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Fri, 14 Feb 2020 15:35:57
-0300

** Changed in: opendnssec (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  Fix Released
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  Fix Released
Status in opendnssec package in Ubuntu:
  Fix Released
Status in opensmtpd-extras package in Ubuntu:
  Fix Released
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  Fix Released
Status in pvpgn package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  Fix Released
Status in voms-mysql-plugin package in Ubuntu:
  Fix Released
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  Fix Released
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package opendnssec - 1:2.1.5-1ubuntu1

---
opendnssec (1:2.1.5-1ubuntu1) focal; urgency=medium

  * d/p/0016-mysql8_my_bool.patch: Reintroduce my_bool to fix build with
MySQL 8. (LP: #1863026)

 -- Andreas Hasenack   Fri, 14 Feb 2020 14:40:22
-0300

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  Fix Released
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  Fix Released
Status in opendnssec package in Ubuntu:
  Fix Released
Status in opensmtpd-extras package in Ubuntu:
  Fix Released
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  Fix Released
Status in pvpgn package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  Fix Released
Status in voms-mysql-plugin package in Ubuntu:
  Fix Released
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  Fix Released
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package tntdb - 1.3-4ubuntu1

---
tntdb (1.3-4ubuntu1) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Fri, 14 Feb 2020 15:23:28
-0300

** Changed in: tntdb (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: w1retap (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  Fix Released
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  Fix Released
Status in opendnssec package in Ubuntu:
  Fix Released
Status in opensmtpd-extras package in Ubuntu:
  Fix Released
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  Fix Released
Status in pvpgn package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  Fix Released
Status in voms-mysql-plugin package in Ubuntu:
  Fix Released
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  Fix Released
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package voms-mysql-plugin - 3.1.7-2ubuntu1

---
voms-mysql-plugin (3.1.7-2ubuntu1) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Fri, 14 Feb 2020 15:28:35
-0300

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  Fix Released
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  Fix Released
Status in pvpgn package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  Fix Released
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package pike8.0 - 8.0.702-1ubuntu1

---
pike8.0 (8.0.702-1ubuntu1) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Fri, 14 Feb 2020 15:13:41
-0300

** Changed in: voms-mysql-plugin (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  Fix Released
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  Fix Released
Status in pvpgn package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  Fix Released
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package pvpgn - 1.8.5-2.1ubuntu1

---
pvpgn (1.8.5-2.1ubuntu1) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Fri, 14 Feb 2020 15:02:47
-0300

** Changed in: pvpgn (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: pike8.0 (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  Fix Released
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  Fix Released
Status in pvpgn package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  Fix Released
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1864162] Re: Don't install snap programs.

2020-02-21 Thread Juhani Numminen
** Package changed: gnome-calendar (Ubuntu) => snap (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1864162

Title:
  Don't install snap programs.

Status in snap package in Ubuntu:
  New

Bug description:
  Goodmorning,
  For a few days I have been unable to install snap programs, both from Ubuntu 
Software but also from the command line.
  I tried with the version of 24-01-2020 but with that there are no problems.
  Please check and solve.

  ubuntu@ubuntu:/media/ubuntu/myhd/Linux/chromium$ sudo snap ack 
chromium_1036.assert
  ubuntu@ubuntu:/media/ubuntu/myhd/Linux/chromium$ sudo snap install 
chromium_1036.snap
  error: too early for operation, device model not yet acknowledged

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

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


[Desktop-packages] [Bug 1849859] Re: smb printing fails

2020-02-21 Thread Hugo
Hello, in Ubuntu 20.04 Daily Builds, the same. I had to apply
"AuthInfoRequired username,password" workarround with samba shared
printers.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1849859

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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


[Desktop-packages] [Bug 1754702] Re: Delay before you can type after switching input source

2020-02-21 Thread Klyshko Nikita
Also have this issue on Ubuntu 18.04.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1754702

Title:
  Delay before you can type after switching input source

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In ubuntu 18.04 I installed different keyboard languages: spanish
  latin american, japanese, japanese-ibus.  To change the input method
  you press the selected key, and an indicator menu appears on-screen to
  indicate which language is selected next.  The menu disapears after
  2~3 seconds and during which time typing is blocked.  If you type
  while the language input method menu is displayed, the menu will not
  disapear and stay as long as you type.

  The language input menu should not block typing, and the disapearance
  of the menu should not be delayed by typing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754702/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package libgda5 - 5.2.9-2ubuntu1

---
libgda5 (5.2.9-2ubuntu1) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Thu, 13 Feb 2020 13:41:43
-0300

** Changed in: libgda5 (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  Fix Released
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  In Progress
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1862262] Re: [snap] apparmor denials on /sys/devices/virtual/dmi/id/sys_vendor and product_name

2020-02-21 Thread Jalon Funk
The "denials on /sys/devices/virtual/dmi/id/sys_vendor and product_name"
will be fixed in next snapd release (2.43.4?):
https://github.com/snapcore/snapd/commit/3ad3e7fbba13721eeaab8dd85a5640316b1c1606

The "ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with
multiple threads in process gpu-process." is known chromium bug which
results in disabled gpu sandbox:
https://bugs.chromium.org/p/chromium/issues/detail?id=264818

This isn't related to snap and the only fix for now is to set
MESA_GLSL_CACHE_DISABLE=true environment variable.

@walterav your issues seem unrelated to those. Please open separate
report.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1862262

Title:
  [snap] apparmor denials on /sys/devices/virtual/dmi/id/sys_vendor and
  product_name

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When starting chromium's snap, those messages are logged:

  Feb  6 12:34:17 foo kernel: [106190.836260] audit: type=1400 
audit(1581010457.097:1372): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/sys_vendor" 
pid=20044 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
  Feb  6 12:34:17 foo kernel: [106190.836401] audit: type=1400 
audit(1581010457.097:1373): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/product_name" pid=20044 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Feb  6 12:34:17 foo chromium_chromium.desktop[20044]: 
[20191:20191:0206/123417.177438:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.

  Chromium seemingly behaves OK but possibly with reduced sandboxing?

  
  Additional info:

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more 
stable way for all
Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: stable
  refresh-date: yesterday at 17:45 EST
  channels:
stable:80.0.3987.87 2020-02-05 (1016) 160MB -
candidate: 80.0.3987.87 2020-02-05 (1016) 160MB -
beta:  80.0.3987.85 2020-02-04 (1014) 160MB -
edge:  81.0.4040.5  2020-02-06 (1018) 161MB -
  installed:   80.0.3987.87(1016) 160MB -

  $ uname -a
  Linux simon-lemur 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862262/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package motion - 4.2.2-1ubuntu1

---
motion (4.2.2-1ubuntu1) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Fri, 14 Feb 2020 11:25:48
-0300

** Changed in: isc-kea (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  In Progress
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package lyricue -
4.0.13.isreally.4.0.12-0ubuntu4

---
lyricue (4.0.13.isreally.4.0.12-0ubuntu4) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Fri, 14 Feb 2020 11:22:08
-0300

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  In Progress
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package libodb-mysql - 2.4.0-5ubuntu2

---
libodb-mysql (2.4.0-5ubuntu2) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Thu, 13 Feb 2020 13:53:04
-0300

** Changed in: lyricue (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  In Progress
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package kannel - 1.4.5-3ubuntu2

---
kannel (1.4.5-3ubuntu2) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Thu, 13 Feb 2020 13:28:28
-0300

** Changed in: kannel (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: motion (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  In Progress
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package isc-kea - 1.6.1-0ubuntu2

---
isc-kea (1.6.1-0ubuntu2) focal; urgency=medium

  * d/p/mysql8-mybool-ubuntu.patch: drop patch as we removed the
workaround from mysql-8.0 itself (LP: #1863026)

 -- Andreas Hasenack   Fri, 21 Feb 2020 09:28:27
-0300

** Changed in: libodb-mysql (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  Fix Released
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  Fix Released
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  Fix Released
Status in lyricue package in Ubuntu:
  Fix Released
Status in motion package in Ubuntu:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  In Progress
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1864215] [NEW] Please add webp loader to gdk-pixbuf

2020-02-21 Thread Akkana Peck
Public bug reported:

Attempting to load a webp image -- for instance, 
  
https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp
or
  
https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg
-- in a gdk-pixbuf app results in a "Couldn’t recognize the image file format" 
error.

Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in
libwebp, but isn't this really a gdk-pixbuf issue? If it really does
belong to libwebp, my apologies, please dup this bug to 1407644 (I'm
confident it doesn't belong to eog since I don't use that program; I
have other programs that use libgdk-pixbuf).

You can probably use eog to test this, or run
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i webp
(I assume the loader would mention webp if there was a loader for it).

I have these packages installed in addition to libgdk-pixbuf2.0-0:
libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes the
format:

$ file /tmp/FKK78W.jpg.webp
/tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 
1200x533, Scaling: [none]x[none], YUV color, decoders should clamp

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
Date: Fri Feb 21 08:48:36 2020
InstallationDate: Installed on 2019-10-10 (133 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
SourcePackage: gdk-pixbuf
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/1864215

Title:
  Please add webp loader to gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Attempting to load a webp image -- for instance, 

https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp
  or

https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg
  -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file 
format" error.

  Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in
  libwebp, but isn't this really a gdk-pixbuf issue? If it really does
  belong to libwebp, my apologies, please dup this bug to 1407644 (I'm
  confident it doesn't belong to eog since I don't use that program; I
  have other programs that use libgdk-pixbuf).

  You can probably use eog to test this, or run
  /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i 
webp
  (I assume the loader would mention webp if there was a loader for it).

  I have these packages installed in addition to libgdk-pixbuf2.0-0:
  libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes
  the format:

  $ file /tmp/FKK78W.jpg.webp
  /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 
1200x533, Scaling: [none]x[none], YUV color, decoders should clamp

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  Date: Fri Feb 21 08:48:36 2020
  InstallationDate: Installed on 2019-10-10 (133 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1864215/+subscriptions

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


[Desktop-packages] [Bug 1864071] Re: [SRU] libreoffice 6.3.5 for eoan

2020-02-21 Thread Marcus Tomlinson
** Changed in: libreoffice (Ubuntu)
   Status: New => In Progress

** Changed in: libreoffice (Ubuntu Eoan)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1864071

Title:
  [SRU] libreoffice 6.3.5 for eoan

Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 6.3.5 is in its fifth bugfix release of the 6.3 line.
 For a list of fixed bugs compared to 6.3.4 see the list of bugs fixed in 
the two release candidates:
   
https://wiki.documentfoundation.org/Releases/6.3.5/RC1#List_of_fixed_bugs 
   https://wiki.documentfoundation.org/Releases/6.3.5/RC2#List_of_fixed_bugs
 (that's a total of 84 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 84 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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


Re: [Desktop-packages] [Bug 1854995] Re: chromium-browser crashes on 4K system

2020-02-21 Thread John Shakespeare
Hi Olivier,

I have determined that it is a bug in the display driver.
How do I get the display driver to output something?
It gives no output even if
enabled=1
in /etc/default/apport.

Best Regards,
John.


On 21.2.2020 11.49, Olivier Tilloy wrote:
> Sorry for the lack of feedback John…
>
> The software-properties-gtk crash file is unrelated, but you might want
> to report it by running "apport software-properties".
>
> Can you please share the chromium crash file? (either attach it to the
> bug if Launchpad lets you, or share it with another file sharing
> mechanism).
>
> Thanks!
>
> ** Changed in: chromium-browser (Ubuntu)
> Status: Expired => New
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1854995

Title:
  chromium-browser crashes on 4K system

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  
  There is a bug which affects chromium-browser intermittently (it also affects 
the firefox browser, but not in necessarily the same way). It does not affect 
NFS (I use it), and is explicit to those two browsers. Opera browser or vivaldi 
browser have not been checked for the bug. 

  shakespeare@RYZEN:~$ uname -r
  5.0.0-37-generic

  shakespeare@RYZEN:~$ lsb_release -crid
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 78.0.3904.108-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec  3 22:12:30 2019
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
   
'/usr/share/xfce4:/usr/share/xubuntu:/home/shakespeare/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2019-09-25 (69 days ago)
  InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Load-Avg-1min: 0.20
  Load-Processes-Running-Percent:   0.1%
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet 
splash nouveau.modeset=0
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3805
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B350-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1854995/+subscriptions

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


[Desktop-packages] [Bug 1864057] Re: Xorg Server terminated with error (1) on Intel/18.04 Laptop

2020-02-21 Thread Michel-Ekimia
** Description changed:

  On a 18.04 ( kernel 5.3 ) Intel laptop :
  
  - At cold start Xorg keeps crashing several times
  - After Several restart , Xorg finally suceed to start
  - it seems user encounter that since kernel 5.3
+ 
+ 
+ Notes : 
+ Possible Root cause : 
+ 
+ [ 9.014] (EE) modeset(0): drmSetMaster failed: Permission denied
+ [ 9.014] (EE)
+ Fatal server error:
+ [ 9.014] (EE) AddScreen/ScreenInit failed for driver 0
+ [ 9.014] (EE)
+ 
+ 
+ It seems related to systemd :
+ 
+ https://github.com/systemd/systemd/issues/13943
+ 
+ 
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:1325]
  InstallationDate: Installed on 2019-03-04 (353 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 003: ID 04f2:b685 Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc.
   Bus 001 Device 004: ID 8087:0025 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N150ZU
  Package: xorg-server (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AG.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic ubuntu
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
  
  _MarkForUpload: True
  dmi.bios.date: 10/19/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.01
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150ZU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N150ZU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1864057

Title:
  Xorg Server terminated with error (1) on Intel/18.04 Laptop

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  On a 18.04 ( kernel 5.3 ) Intel laptop :

  - At cold start Xorg keeps crashing several times
  - After Several restart , Xorg finally suceed to start
  - it seems user encounter that since kernel 5.3

  
  Notes : 
  Possible Root cause : 

  [ 9.014] (EE) modeset(0): drmSetMaster failed: Permission denied
  [ 9.014] (EE)
  Fatal server error:
  [ 9.014] (EE) AddScreen/ScreenInit failed for driver 0
  [ 9.014] (EE)


  It seems related to systemd :

  https://github.com/systemd/systemd/issues/13943

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:1325]
  InstallationDate: Installed on 2019-03-04 (353 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 003: ID 04f2:b685 Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc.
   Bus 001 Device 004: ID 8087:0025 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N150ZU
  Package: xorg-server (not installed)
  ProcEnviron:
   

[Desktop-packages] [Bug 1864057] Re: Xorg Server terminated with error (1) on Intel/18.04 Laptop

2020-02-21 Thread Michel-Ekimia
@Daniel : similar issue here on arch

https://bbs.archlinux.org/viewtopic.php?id=250892

Says fixed with systemd 244

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1864057

Title:
  Xorg Server terminated with error (1) on Intel/18.04 Laptop

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  On a 18.04 ( kernel 5.3 ) Intel laptop :

  - At cold start Xorg keeps crashing several times
  - After Several restart , Xorg finally suceed to start
  - it seems user encounter that since kernel 5.3
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:1325]
  InstallationDate: Installed on 2019-03-04 (353 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 003: ID 04f2:b685 Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc.
   Bus 001 Device 004: ID 8087:0025 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N150ZU
  Package: xorg-server (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AG.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic ubuntu
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 10/19/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.01
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150ZU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N150ZU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.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-server/+bug/1864057/+subscriptions

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


[Desktop-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path

2020-02-21 Thread Bug Watch Updater
** Changed in: nautilus
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1726129

Title:
  nautilus crashed with SIGSEGV in widget_needs_widget_path

Status in Nautilus:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/gtk/issues/2457

  ---

  https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct 22 15:30:05 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-10-19 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcCmdline: nautilus --new-window
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax
   PC (0x7fe0115bd2a4) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  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/nautilus/+bug/1726129/+subscriptions

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


[Desktop-packages] [Bug 1864061] Re: PCI/internal sound card not detected

2020-02-21 Thread Timo Aaltonen
** Package changed: alsa-driver (Ubuntu) => linux-oem-osp1 (Ubuntu)

** Also affects: linux-oem-osp1 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  PCI/internal sound card not detected

Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed

Bug description:
  The sof-pci-dev and snd-soc-skl all contains the same pciid, if
  the soc-skl is loaded ahead of sof-pci-dev, the sof driver will
  not work anymore, in the oem project, we manually put the soc-skl
  in the blacklist.

  From kernel-5.4 (focal kernel), the driver soc-skl is disabled by
  default, and there is no users report any issues on it. So let us
  disable soc-skl in the eoan and osp1 kernel too.

  The patch for eoan kernel doesn't remove the modules because looks
  like the abi folder are not controlled by git. This will break the
  modulecheck, so if this patch could be merged, please help remove
  those modules:
  snd-soc-skl
  snd-soc-skl-ipc
  snd-soc-skl-ssp-clk

  [Impact]
  If soc-skl driver is loaded ahead of sof driver, the sof could
  not work anymore, we need to blacklist the soc-skl manually

  [Fix]
  Like the focal kernel, we disable the soc_skl driver in the kernel
  config

  [Test Case]
  Tested on Lenovo and Dell machines which has dmic, the sof driver
  could be loaded successfully.

  Tested on the machinces without the dmic, the legacy hda driver
  worked well as before.

  [Regression Risk]
  Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this
  dirver; and We have not met a machine need the soc_skl driver yet;
  and Intel claim that the sof could replace the soc_skl driver.

  Probably a kernel bug.

  The sound card isn't detected in 5.3.0-41-generic
  Booting 5.3.0-40-generic does work.

  The relevant dmesg message is:

  [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported 
HDAudio/iDisp configuration found
  [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with 
error -22

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
  Uname: Linux 5.3.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 20 16:46:21 2020
  InstallationDate: Installed on 2019-10-07 (136 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to eoan on 2019-11-19 (93 days ago)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET44W (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET44W(1.27):bd01/15/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/+subscriptions

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


[Desktop-packages] [Bug 1864057] Re: Xorg Server terminated with error (1) on Intel/18.04 Laptop

2020-02-21 Thread Michel-Ekimia
Thanks daniel

/var/crash is empty

Whoopsie did not report any crash so far on errors.ubuntu.com

For years we disabled apport to reduce end-user interaction, is this why
?

I Will try to find more logs

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1864057

Title:
  Xorg Server terminated with error (1) on Intel/18.04 Laptop

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  On a 18.04 ( kernel 5.3 ) Intel laptop :

  - At cold start Xorg keeps crashing several times
  - After Several restart , Xorg finally suceed to start
  - it seems user encounter that since kernel 5.3
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:1325]
  InstallationDate: Installed on 2019-03-04 (353 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 003: ID 04f2:b685 Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc.
   Bus 001 Device 004: ID 8087:0025 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N150ZU
  Package: xorg-server (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AG.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic ubuntu
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 10/19/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.01
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150ZU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N150ZU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.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-server/+bug/1864057/+subscriptions

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


[Desktop-packages] [Bug 1864061] Re: PCI/internal sound card not detected

2020-02-21 Thread Hui Wang
** Description changed:

  The sof-pci-dev and snd-soc-skl all contains the same pciid, if
  the soc-skl is loaded ahead of sof-pci-dev, the sof driver will
  not work anymore, in the oem project, we manually put the soc-skl
  in the blacklist.
  
  From kernel-5.4 (focal kernel), the driver soc-skl is disabled by
  default, and there is no users report any issues on it. So let us
  disable soc-skl in the eoan and osp1 kernel too.
  
  The patch for eoan kernel doesn't remove the modules because looks
  like the abi folder are not controlled by git. This will break the
  modulecheck, so if this patch could be merged, please help remove
  those modules:
- snd-soc-slk
+ snd-soc-skl
  snd-soc-skl-ipc
  snd-soc-skl-ssp-clk
- 
  
  [Impact]
  If soc-skl driver is loaded ahead of sof driver, the sof could
  not work anymore, we need to blacklist the soc-skl manually
  
  [Fix]
  Like the focal kernel, we disable the soc_skl driver in the kernel
  config
- 
  
  [Test Case]
  Tested on Lenovo and Dell machines which has dmic, the sof driver
  could be loaded successfully.
  
  Tested on the machinces without the dmic, the legacy hda driver
  worked well as before.
  
  [Regression Risk]
  Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this
  dirver; and We have not met a machine need the soc_skl driver yet;
  and Intel claim that the sof could replace the soc_skl driver.
- 
  
  Probably a kernel bug.
  
  The sound card isn't detected in 5.3.0-41-generic
  Booting 5.3.0-40-generic does work.
  
  The relevant dmesg message is:
  
  [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported 
HDAudio/iDisp configuration found
  [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with 
error -22
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
  Uname: Linux 5.3.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 20 16:46:21 2020
  InstallationDate: Installed on 2019-10-07 (136 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to eoan on 2019-11-19 (93 days ago)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET44W (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET44W(1.27):bd01/15/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The sof-pci-dev and snd-soc-skl all contains the same pciid, if
  the soc-skl is loaded ahead of sof-pci-dev, the sof driver will
  not work anymore, in the oem project, we manually put the soc-skl
  in the blacklist.

  From kernel-5.4 (focal kernel), the driver soc-skl is disabled by
  default, and there is no users report any issues on it. So let us
  disable soc-skl in the eoan and osp1 kernel too.

  The patch for eoan kernel doesn't remove the modules because looks
  like the abi folder are not controlled by git. This will break the
  modulecheck, so if this patch could be merged, please help remove
  those modules:
  snd-soc-skl
  snd-soc-skl-ipc
  snd-soc-skl-ssp-clk

  [Impact]
  If soc-skl driver is loaded ahead of sof driver, the sof could
  not work anymore, we need to blacklist the soc-skl manually

  [Fix]
  Like the focal kernel, we disable the soc_skl driver in the kernel
  config

  [Test Case]
  Tested on Lenovo and Dell machines which has dmic, the sof driver
  could be loaded successfully.

  Tested on the machinces without the dmic, the legacy hda driver
  worked well as before.

  [Regression Risk]
  Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this
  dirver; and We have not met a machine need the soc_skl driver yet;
  and Intel claim that the sof could replace the soc_skl driver.

  Probably a kernel bug.

  The sound card isn't detected in 5.3.0-41-generic
  Booting 5.3.0-40-generic does work.

  The relevant 

[Desktop-packages] [Bug 1864057] Re: Xorg Server terminated with error (1) on Intel/18.04 Laptop

2020-02-21 Thread Michel-Ekimia
@Timo : did you mean "Run 'dmesg > dmesg.txt' when booting *with
nomodeset and attach it here." ?

Because We never boot with nomodeset

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1864057

Title:
  Xorg Server terminated with error (1) on Intel/18.04 Laptop

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  On a 18.04 ( kernel 5.3 ) Intel laptop :

  - At cold start Xorg keeps crashing several times
  - After Several restart , Xorg finally suceed to start
  - it seems user encounter that since kernel 5.3
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:1325]
  InstallationDate: Installed on 2019-03-04 (353 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 003: ID 04f2:b685 Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc.
   Bus 001 Device 004: ID 8087:0025 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N150ZU
  Package: xorg-server (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AG.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic ubuntu
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 10/19/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.01
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150ZU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N150ZU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.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-server/+bug/1864057/+subscriptions

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


[Desktop-packages] [Bug 1864061] Re: PCI/internal sound card not detected

2020-02-21 Thread roland
Thank you for your response.

I've blacklisted the driver:
$ cat /etc/modprobe.d/blacklist.conf |grep snd_soc_skl
blacklist snd_soc_skl

It didn't help. Sound still has the dummy output.

I've added the dmesg log.
Which includes a call Trace and multiple errors regarding the sound driver.



** Attachment added: "DMESG"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1864061/+attachment/5330054/+files/dmesg

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The sof-pci-dev and snd-soc-skl all contains the same pciid, if
  the soc-skl is loaded ahead of sof-pci-dev, the sof driver will
  not work anymore, in the oem project, we manually put the soc-skl
  in the blacklist.

  From kernel-5.4 (focal kernel), the driver soc-skl is disabled by
  default, and there is no users report any issues on it. So let us
  disable soc-skl in the eoan and osp1 kernel too.

  The patch for eoan kernel doesn't remove the modules because looks
  like the abi folder are not controlled by git. This will break the
  modulecheck, so if this patch could be merged, please help remove
  those modules:
  snd-soc-slk
  snd-soc-skl-ipc
  snd-soc-skl-ssp-clk

  
  [Impact]
  If soc-skl driver is loaded ahead of sof driver, the sof could
  not work anymore, we need to blacklist the soc-skl manually

  [Fix]
  Like the focal kernel, we disable the soc_skl driver in the kernel
  config

  
  [Test Case]
  Tested on Lenovo and Dell machines which has dmic, the sof driver
  could be loaded successfully.

  Tested on the machinces without the dmic, the legacy hda driver
  worked well as before.

  [Regression Risk]
  Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this
  dirver; and We have not met a machine need the soc_skl driver yet;
  and Intel claim that the sof could replace the soc_skl driver.


  Probably a kernel bug.

  The sound card isn't detected in 5.3.0-41-generic
  Booting 5.3.0-40-generic does work.

  The relevant dmesg message is:

  [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported 
HDAudio/iDisp configuration found
  [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with 
error -22

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
  Uname: Linux 5.3.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 20 16:46:21 2020
  InstallationDate: Installed on 2019-10-07 (136 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to eoan on 2019-11-19 (93 days ago)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET44W (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET44W(1.27):bd01/15/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1864061/+subscriptions

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


[Desktop-packages] [Bug 1862081] Re: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling)

2020-02-21 Thread pheidrias
I'd like to add that the problem doesn't occur, when there is another
(pinned) window in the foreground! E.g., open a terminal and make it to
stay "on top" and the video plays fine in fullscreen mode (behind the
terminal).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1862081

Title:
  Gnome resizes framebuffer when playing fullscreen video over and over
  again (when using X11 fractional scaling)

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When I play a video with mpv (or e.g. Firefox), it works just fine.

  When this video is fullscreened (e.g. in mpv by pressing f), the
  screen quickly turns off, and switches resolution modes in such a rate
  the screen is unusable.

  The native resolution of the screen is 1440p, but Xorg somehow
  increases the size to 3424x1926 for the fullscreen, then quickly
  switches back to 1440p, before increasing it again.

  As soon as the video is de-fullscreened (by pressing f again in mpv,
  or esc in Firefox), the funny resolution switching stops and the
  system is usable again.

  This also happens with the modesetting 2d-driver. This does not happen
  with Wayland.

  This can be seen in the Xorg-log:
  [20.215] (II) intel(0): EDID vendor "JDI", prod id 0
  [20.215] (II) intel(0): Printing DDC gathered Modelines:
  [20.215] (II) intel(0): Modeline "2560x1440"x0.0  245.12  2560 2608 2640 
2720  1440 1443 1449 1502 +hsync -vsync (90.1 kHz eP)
  [   258.869] (II) intel(0): resizing framebuffer to 3424x1926
  [   258.905] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [   268.955] (II) intel(0): resizing framebuffer to 2560x1440
  [   269.097] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [   270.383] (II) intel(0): resizing framebuffer to 3424x1926
  [   270.400] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [   271.852] (II) intel(0): resizing framebuffer to 2560x1440
  [   271.858] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none
  [   273.294] (II) intel(0): resizing framebuffer to 3424x1926
  [   273.314] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 
0, position (0, 0), rotation normal, reflection none

  When the resolution is increased, the Kernel complains about the
  framebuffer size:

  [  269.830034] [drm] Reducing the compressed framebuffer size. This
  may lead to less power savings than a non-reduced-size. Try to
  increase stolen memory size if available in BIOS.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu13
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 00:00:07 2020
  DistUpgraded: 2020-02-05 22:21:13,002 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:2259]
  MachineType: LENOVO 20LES01W00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/hostname-ubunturoot ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-02-05 (0 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N25ET52W (1.38 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LES01W00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN25ET52W(1.38):bd11/27/2019:svnLENOVO:pn20LES01W00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES01W00:rvrNotDefined:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 3rd
  dmi.product.name: 20LES01W00
  dmi.product.sku: LENOVO_MT_20LE_BU_Think_FM_ThinkPad X1 Yoga 3rd
  dmi.product.version: ThinkPad X1 Yoga 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  

[Desktop-packages] [Bug 1863904] Re: Gimp 2.10 snap doesn't start, and you can't even reinstall it.

2020-02-21 Thread Airat Halitov
I installed the beta version. It helped

sudo snap install gimp --beta

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1863904

Title:
  Gimp 2.10 snap doesn't start, and you can't even reinstall it.

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  With Start, in Terminal:
  ln: failed to create symbolic link 
'/home/stefano/snap/gimp/227/.config/gtk-2.0/gtkfilechooser.ini': File exists

  With Install, in Software Center:
  Seguono gli errori dettagliati del gestore dei pacchetti:

  snapd operation finished with error cannot perform the following tasks:
  - Run install hook of "gimp" snap if present (run hook "install": 
  -
  mkdir: cannot create directory '/run/user/0': Permission denied
  /snap/gimp/245/usr/lib/x86_64-linux-gnu/libgtk2.0-0/gtk-query-immodules-2.0: 
error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared 
object file: No such file or directory
  ERROR: 
/snap/gimp/245/usr/lib/x86_64-linux-gnu/libgtk2.0-0/gtk-query-immodules-2.0 
exited abnormally with status 127
  + exec /snap/gimp/245/bin/build-ld-cache
  + mkdir -p /var/snap/gimp/245/etc/ld.so.conf.d
  + cp -r '/etc/ld.so.conf.d/*' /var/snap/gimp/245/etc/ld.so.conf.d
  cp: cannot stat '/etc/ld.so.conf.d/*': No such file or directory
  -)

  Now i've installed 2.08 .deb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.5-0ubuntu0.16.04.13
  ProcVersionSignature: Ubuntu 4.15.0-88.88~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb 19 15:31:33 2020
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-09-12 (525 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1863904/+subscriptions

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


[Desktop-packages] [Bug 1863904] Re: Gimp 2.10 snap doesn't start, and you can't even reinstall it.

2020-02-21 Thread Airat Halitov
I have the same error. 
I decided to reinstall Gimp but I can't install Gimp after uninstall.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1863904

Title:
  Gimp 2.10 snap doesn't start, and you can't even reinstall it.

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  With Start, in Terminal:
  ln: failed to create symbolic link 
'/home/stefano/snap/gimp/227/.config/gtk-2.0/gtkfilechooser.ini': File exists

  With Install, in Software Center:
  Seguono gli errori dettagliati del gestore dei pacchetti:

  snapd operation finished with error cannot perform the following tasks:
  - Run install hook of "gimp" snap if present (run hook "install": 
  -
  mkdir: cannot create directory '/run/user/0': Permission denied
  /snap/gimp/245/usr/lib/x86_64-linux-gnu/libgtk2.0-0/gtk-query-immodules-2.0: 
error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared 
object file: No such file or directory
  ERROR: 
/snap/gimp/245/usr/lib/x86_64-linux-gnu/libgtk2.0-0/gtk-query-immodules-2.0 
exited abnormally with status 127
  + exec /snap/gimp/245/bin/build-ld-cache
  + mkdir -p /var/snap/gimp/245/etc/ld.so.conf.d
  + cp -r '/etc/ld.so.conf.d/*' /var/snap/gimp/245/etc/ld.so.conf.d
  cp: cannot stat '/etc/ld.so.conf.d/*': No such file or directory
  -)

  Now i've installed 2.08 .deb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.5-0ubuntu0.16.04.13
  ProcVersionSignature: Ubuntu 4.15.0-88.88~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb 19 15:31:33 2020
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-09-12 (525 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1863904/+subscriptions

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


[Desktop-packages] [Bug 1862926] Re: Request for update: SANE 1.0.29

2020-02-21 Thread Till Kamppeter
The attached debdiff adds the missing Build-Depends for fixing the FTBFS
and getting all backends built.

** Patch added: "sane-backends_1.0.29-0ubuntu1_1.0.29-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1862926/+attachment/5330030/+files/sane-backends_1.0.29-0ubuntu1_1.0.29-0ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
 + adds an escl backend (theoretically supporting all AirPrint devices with 
a scan unit
 + adds support for 23 new scanner models via existing backends
 + significantly changes genesys and pixma backends
 + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and 
xerox_mfp backends
 + fixes all compiler warnings on Debian 10 (#120)
 + fixes portability issues for uClibc-ng and MacOS builds
 + adds support to record and replay USB I/O traffic
 + adds timestamps to debug logs

  debdiff attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1862926/+subscriptions

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


[Desktop-packages] [Bug 1862926] Re: Request for update: SANE 1.0.29

2020-02-21 Thread Till Kamppeter
1.0.29-0ubuntu1 does FTBFS, -0ubuntu2 with added Build-Depends: on the
way.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
 + adds an escl backend (theoretically supporting all AirPrint devices with 
a scan unit
 + adds support for 23 new scanner models via existing backends
 + significantly changes genesys and pixma backends
 + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and 
xerox_mfp backends
 + fixes all compiler warnings on Debian 10 (#120)
 + fixes portability issues for uClibc-ng and MacOS builds
 + adds support to record and replay USB I/O traffic
 + adds timestamps to debug logs

  debdiff attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1862926/+subscriptions

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


[Desktop-packages] [Bug 1864178] [NEW] Rhythmbox crashes when trying to connect to iPhone

2020-02-21 Thread Jairam Chandar
Public bug reported:

I connected my iPhone to my laptop running Ubuntu 19.10. Nautilus and Shotwell 
loaded the device fine. But when I open Rhythmbox, it crashes. 
I opened Rhythmbox from the terminal to see the error and I got this

```
(rhythmbox:15045): Gtk-WARNING **: 09:47:19.122: actionhelper: action 
app.play-repeat can't be activated due to parameter type mismatch (parameter 
type NULL, target type b)

(rhythmbox:15045): Gtk-WARNING **: 09:47:19.122: actionhelper: action 
app.play-shuffle can't be activated due to parameter type mismatch (parameter 
type NULL, target type b)
**
Rhythmbox:ERROR:rb-ipod-helpers.c:359:rb_ipod_helpers_is_ipod: assertion 
failed: (strlen (uri) >= 46)
Bail out! Rhythmbox:ERROR:rb-ipod-helpers.c:359:rb_ipod_helpers_is_ipod: 
assertion failed: (strlen (uri) >= 46)
[1]15045 abort (core dumped)  rhythmbox
```

Details of the current system:

```
lsb_release -rd
Description:Ubuntu 19.10
Release:19.10
```

```
apt-cache policy rhythmbox
rhythmbox:
  Installed: 3.4.3-2ubuntu1
  Candidate: 3.4.3-2ubuntu1
  Version table:
 *** 3.4.3-2ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
```

What I expected to happen:
I was expected Rhythmbox to show my iPhone under "devices"

What actually happned:
Rhythmbox just crashed

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1864178

Title:
  Rhythmbox crashes when trying to connect to iPhone

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  I connected my iPhone to my laptop running Ubuntu 19.10. Nautilus and 
Shotwell loaded the device fine. But when I open Rhythmbox, it crashes. 
  I opened Rhythmbox from the terminal to see the error and I got this

  ```
  (rhythmbox:15045): Gtk-WARNING **: 09:47:19.122: actionhelper: action 
app.play-repeat can't be activated due to parameter type mismatch (parameter 
type NULL, target type b)

  (rhythmbox:15045): Gtk-WARNING **: 09:47:19.122: actionhelper: action 
app.play-shuffle can't be activated due to parameter type mismatch (parameter 
type NULL, target type b)
  **
  Rhythmbox:ERROR:rb-ipod-helpers.c:359:rb_ipod_helpers_is_ipod: assertion 
failed: (strlen (uri) >= 46)
  Bail out! Rhythmbox:ERROR:rb-ipod-helpers.c:359:rb_ipod_helpers_is_ipod: 
assertion failed: (strlen (uri) >= 46)
  [1]15045 abort (core dumped)  rhythmbox
  ```

  Details of the current system:

  ```
  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10
  ```

  ```
  apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.3-2ubuntu1
Candidate: 3.4.3-2ubuntu1
Version table:
   *** 3.4.3-2ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status
  ```

  What I expected to happen:
  I was expected Rhythmbox to show my iPhone under "devices"

  What actually happned:
  Rhythmbox just crashed

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

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


[Desktop-packages] [Bug 1854995] Re: chromium-browser crashes on 4K system

2020-02-21 Thread Olivier Tilloy
Sorry for the lack of feedback John…

The software-properties-gtk crash file is unrelated, but you might want
to report it by running "apport software-properties".

Can you please share the chromium crash file? (either attach it to the
bug if Launchpad lets you, or share it with another file sharing
mechanism).

Thanks!

** Changed in: chromium-browser (Ubuntu)
   Status: Expired => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1854995

Title:
  chromium-browser crashes on 4K system

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  
  There is a bug which affects chromium-browser intermittently (it also affects 
the firefox browser, but not in necessarily the same way). It does not affect 
NFS (I use it), and is explicit to those two browsers. Opera browser or vivaldi 
browser have not been checked for the bug. 

  shakespeare@RYZEN:~$ uname -r
  5.0.0-37-generic

  shakespeare@RYZEN:~$ lsb_release -crid
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 78.0.3904.108-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Dec  3 22:12:30 2019
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
   
'/usr/share/xfce4:/usr/share/xubuntu:/home/shakespeare/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2019-09-25 (69 days ago)
  InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Load-Avg-1min: 0.20
  Load-Processes-Running-Percent:   0.1%
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet 
splash nouveau.modeset=0
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3805
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B350-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1854995/+subscriptions

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


[Desktop-packages] [Bug 1848326] Re: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules

2020-02-21 Thread Alberto Milone
Great, thanks for testing!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326

Title:
  [cosmic+] error booting with prime-select intel: prime-select does not
  update initramfs to blacklist nvidia modules

Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Triaged
Status in ubuntu-drivers-common source package in Bionic:
  Triaged
Status in nvidia-prime source package in Eoan:
  Triaged
Status in ubuntu-drivers-common source package in Eoan:
  Triaged

Bug description:
  when I try to boot with the iGPU selected, DE won't boot, with nvidia 
selected, everithing is fine.
  I tried uninstalling nvidia driver and it allowed my to access without any 
problems and intel is working fine

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nvidia-prime 0.8.13
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 16 12:41:26 2019
  Dependencies:
   
  InstallationDate: Installed on 2019-09-25 (20 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
  PackageArchitecture: all
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+subscriptions

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


[Desktop-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

2020-02-21 Thread Seyeong Kim
why bugproxy keep attaching old debdiff I've changed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as 
original description.
  2. ipv6 manual, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses 
fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##
  3. ipv6 auto, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
  network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
  network-manager | 1.22.4-1ubuntu2 | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 

[Desktop-packages] [Bug 1794478] lp1794478_bionic.debdiff

2020-02-21 Thread bugproxy
Default Comment by Bridge

** Attachment added: "lp1794478_bionic.debdiff"
   
https://bugs.launchpad.net/bugs/1794478/+attachment/5330008/+files/lp1794478_bionic.debdiff

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as 
original description.
  2. ipv6 manual, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses 
fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##
  3. ipv6 auto, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
  network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
  network-manager | 1.22.4-1ubuntu2 | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 

[Desktop-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

2020-02-21 Thread Seyeong Kim
** Description changed:

  [Impact]
+ 
+ In case creating bond interface, IPv4 address is not automatically
+ assigned when IPv6 has manual setting.
+ 
  [Test Case]
+ 
+ 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as 
original description.
+ 2. ipv6 manual, ipv4 auto
+ ##
+ sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
+ sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
+ sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses 
fe81::ff:fe97:a27f/64;
+ sudo nmcli con mod bond0 ipv4.method auto;
+ sudo nmcli con add type bond-slave ifname ens34 master bond0;
+ sudo nmcli con add type bond-slave ifname ens35 master bond0;
+ sudo nmcli con mod bond0 +bond.options mii=100
+ 
+ sleep 5
+ 
+ sudo nmcli con up bond-slave-ens34
+ sudo nmcli con up bond-slave-ens35
+ sudo nmcli con up bond0;
+ 
+ sleep 5;
+ sudo nmcli c s bond0
+ ##
+ 3. ipv6 auto, ipv4 auto
+ ##
+ sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
+ sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
+ sudo nmcli con mod bond0 ipv6.method auto;
+ sudo nmcli con mod bond0 ipv4.method auto;
+ sudo nmcli con add type bond-slave ifname ens34 master bond0;
+ sudo nmcli con add type bond-slave ifname ens35 master bond0;
+ sudo nmcli con mod bond0 +bond.options mii=100
+ 
+ sleep 5
+ 
+ sudo nmcli con up bond-slave-ens34
+ sudo nmcli con up bond-slave-ens35
+ sudo nmcli con up bond0;
+ 
+ sleep 5
+ 
+ sudo nmcli c s bond0
+ ##
+ 
+ when run #3, it is working, but with #2, it is not working.
+ 
  [Potential Regression]
  
+ Actually nothing special. fix just remove if statement. but it needs
+ Network Manager restarted.
+ 
  [Other informations]
+ 
+ After upstream fix, it is working fine with #2 and #3 above.
  
  * Upstream bug and fix:
  
  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35
  
  * Only affecting Bionic:
  
  $ git describe --contains f03ae35
  1.10.8~2
  
  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
  network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
  network-manager | 1.22.4-1ubuntu2 | focal
  
  [Original description]
  
  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.
  
  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux
  
  Machine Type = s390x
  
  ---Debugger---
  A debugger is not configured
  
  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface
  
  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface
  
  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode
  
  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121
  
  [ethernet]
  mac-address-blacklist=
  
  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0
  
  [ipv4]
  dns-search=
  method=auto
  
  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto
  
  From /var/log/syslog, we can see ip got assigned:
  
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1
  
  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute 
test_bond
     valid_lft 353sec preferred_lft 353sec
  inet6 fe80::ff:feb3:b522/64 scope link
     

[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Gianfranco Costamagna
mysql-ocaml patched.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  In Progress
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  In Progress
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  In Progress
Status in lyricue package in Ubuntu:
  In Progress
Status in motion package in Ubuntu:
  In Progress
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  In Progress
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

2020-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package mysql-8.0 - 8.0.19-0ubuntu4

---
mysql-8.0 (8.0.19-0ubuntu4) focal; urgency=medium

  * d/p/my_bool.patch: drop the my_bool workaround typedef
(LP: #1863026)

 -- Andreas Hasenack   Mon, 17 Feb 2020 11:04:18
-0300

** Changed in: mysql-8.0 (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to redland in Ubuntu.
https://bugs.launchpad.net/bugs/1863026

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  Fix Released
Status in gerbera package in Ubuntu:
  Fix Released
Status in gnokii package in Ubuntu:
  Fix Released
Status in gnunet package in Ubuntu:
  Fix Released
Status in hoel package in Ubuntu:
  Fix Released
Status in isc-kea package in Ubuntu:
  In Progress
Status in jabberd2 package in Ubuntu:
  Fix Released
Status in kannel package in Ubuntu:
  In Progress
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  In Progress
Status in lyricue package in Ubuntu:
  In Progress
Status in motion package in Ubuntu:
  In Progress
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  In Progress
Status in vtk7 package in Ubuntu:
  Fix Released
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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


[Desktop-packages] [Bug 1864162] Re: Don't install snap programs.

2020-02-21 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1864162

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

What are you referring to with "I tried with the version of 24-01-2020"
; is that the date of a DAILY image you are testing? or something else?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1864162

Title:
  Don't install snap programs.

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Goodmorning,
  For a few days I have been unable to install snap programs, both from Ubuntu 
Software but also from the command line.
  I tried with the version of 24-01-2020 but with that there are no problems.
  Please check and solve.

  ubuntu@ubuntu:/media/ubuntu/myhd/Linux/chromium$ sudo snap ack 
chromium_1036.assert
  ubuntu@ubuntu:/media/ubuntu/myhd/Linux/chromium$ sudo snap install 
chromium_1036.snap
  error: too early for operation, device model not yet acknowledged

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1864162/+subscriptions

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


[Desktop-packages] [Bug 1864061] Re: PCI/internal sound card not detected

2020-02-21 Thread Hui Wang
** Description changed:

+ The sof-pci-dev and snd-soc-skl all contains the same pciid, if
+ the soc-skl is loaded ahead of sof-pci-dev, the sof driver will
+ not work anymore, in the oem project, we manually put the soc-skl
+ in the blacklist.
+ 
+ From kernel-5.4 (focal kernel), the driver soc-skl is disabled by
+ default, and there is no users report any issues on it. So let us
+ disable soc-skl in the eoan and osp1 kernel too.
+ 
+ The patch for eoan kernel doesn't remove the modules because looks
+ like the abi folder are not controlled by git. This will break the
+ modulecheck, so if this patch could be merged, please help remove
+ those modules:
+ snd-soc-slk
+ snd-soc-skl-ipc
+ snd-soc-skl-ssp-clk
+ 
+ 
+ [Impact]
+ If soc-skl driver is loaded ahead of sof driver, the sof could
+ not work anymore, we need to blacklist the soc-skl manually
+ 
+ [Fix]
+ Like the focal kernel, we disable the soc_skl driver in the kernel
+ config
+ 
+ 
+ [Test Case]
+ Tested on Lenovo and Dell machines which has dmic, the sof driver
+ could be loaded successfully.
+ 
+ Tested on the machinces without the dmic, the legacy hda driver
+ worked well as before.
+ 
+ [Regression Risk]
+ Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this
+ dirver; and We have not met a machine need the soc_skl driver yet;
+ and Intel claim that the sof could replace the soc_skl driver.
+ 
+ 
  Probably a kernel bug.
  
  The sound card isn't detected in 5.3.0-41-generic
  Booting 5.3.0-40-generic does work.
  
  The relevant dmesg message is:
  
  [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported 
HDAudio/iDisp configuration found
  [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with 
error -22
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18
  Uname: Linux 5.3.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 20 16:46:21 2020
  InstallationDate: Installed on 2019-10-07 (136 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to eoan on 2019-11-19 (93 days ago)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET44W (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET44W(1.27):bd01/15/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The sof-pci-dev and snd-soc-skl all contains the same pciid, if
  the soc-skl is loaded ahead of sof-pci-dev, the sof driver will
  not work anymore, in the oem project, we manually put the soc-skl
  in the blacklist.

  From kernel-5.4 (focal kernel), the driver soc-skl is disabled by
  default, and there is no users report any issues on it. So let us
  disable soc-skl in the eoan and osp1 kernel too.

  The patch for eoan kernel doesn't remove the modules because looks
  like the abi folder are not controlled by git. This will break the
  modulecheck, so if this patch could be merged, please help remove
  those modules:
  snd-soc-slk
  snd-soc-skl-ipc
  snd-soc-skl-ssp-clk

  
  [Impact]
  If soc-skl driver is loaded ahead of sof driver, the sof could
  not work anymore, we need to blacklist the soc-skl manually

  [Fix]
  Like the focal kernel, we disable the soc_skl driver in the kernel
  config

  
  [Test Case]
  Tested on Lenovo and Dell machines which has dmic, the sof driver
  could be loaded successfully.

  Tested on the machinces without the dmic, the legacy hda driver
  worked well as before.

  [Regression Risk]
  Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this
  dirver; and We have not met a machine need the soc_skl driver yet;
  and Intel claim that the sof could replace the soc_skl driver.


  Probably a kernel bug.

  The sound card isn't detected in 5.3.0-41-generic
  Booting 5.3.0-40-generic does work.

  The relevant dmesg