[Touch-packages] [Bug 2060034] Re: /usr/bin/ld: error: /lib/x86_64-linux-gnu/libkeyutils.so.1: file too short

[Vitor Luis]

** Description changed:

  Trying to compile weechat from source:
- 
+ 
  root@voltron ~/weechat/build # cmake .. -DCMAKE_BUILD_TYPE=Debug
  -- Checking for one of the modules 'php8;php7'
  -- Configuring done
  -- Generating done
  -- Build files have been written to: /root/weechat/build
  
  
  
  root@voltron ~/weechat/build # make -j7
  Consolidate compiler generated dependencies of target buflist
  Consolidate compiler generated dependencies of target weechat_plugins_scripts
  Consolidate compiler generated dependencies of target alias
  Consolidate compiler generated dependencies of target weechat_plugins
  Consolidate compiler generated dependencies of target charset
  File config-git.h is up-to-date (git version: "v4.2.0-194-gf3f9dc388")
  [  4%] Built target translations
  [  4%] Built target version_git
  Consolidate compiler generated dependencies of target exec
  Consolidate compiler generated dependencies of target fifo
  [  5%] Built target weechat_plugins_scripts
  [  7%] Built target weechat_plugins
  [  9%] Built target exec
  [ 11%] Built target alias
  [ 13%] Built target buflist
  Consolidate compiler generated dependencies of target logger
  Consolidate compiler generated dependencies of target fset
  Consolidate compiler generated dependencies of target irc
  Consolidate compiler generated dependencies of target script
  Consolidate compiler generated dependencies of target relay
  [ 16%] Built target logger
  Consolidate compiler generated dependencies of target perl
  [ 17%] Built target perl
  Consolidate compiler generated dependencies of target python
  [ 18%] Built target python
  Consolidate compiler generated dependencies of target ruby
  [ 22%] Built target script
  [ 24%] Built target ruby
  [ 37%] Built target irc
  [ 42%] Built target relay
  Consolidate compiler generated dependencies of target tcl
  Consolidate compiler generated dependencies of target lua
  [ 43%] Built target charset
  Consolidate compiler generated dependencies of target guile
  Consolidate compiler generated dependencies of target php
  Consolidate compiler generated dependencies of target spell
  [ 45%] Built target tcl
  [ 45%] Built target lua
  [ 46%] Built target guile
  Consolidate compiler generated dependencies of target trigger
  Consolidate compiler generated dependencies of target typing
  Consolidate compiler generated dependencies of target xfer
  [ 49%] Built target spell
  [ 50%] Built target php
  [ 51%] Built target typing
  [ 54%] Built target trigger
  Consolidate compiler generated dependencies of target 
weechat_gui_curses_normal
  Consolidate compiler generated dependencies of target weechat_gui_common
  Consolidate compiler generated dependencies of target weechat_gui_headless
  Consolidate compiler generated dependencies of target weechat_ncurses_fake
  [ 60%] Built target xfer
  [ 60%] Built target weechat_ncurses_fake
  [ 63%] Built target fset
  [ 65%] Built target fifo
  [ 68%] Built target weechat_gui_headless
  [ 71%] Built target weechat_gui_curses_normal
  [ 80%] Built target weechat_gui_common
  Consolidate compiler generated dependencies of target weechat_core
  [ 98%] Built target weechat_core
  Consolidate compiler generated dependencies of target weechat
  Consolidate compiler generated dependencies of target weechat-headless
  [100%] Linking C executable weechat
  [100%] Linking C executable weechat-headless
  /usr/bin/ld: error: /lib/x86_64-linux-gnu/libkeyutils.so.1: file too short
  collect2: error: ld returned 1 exit status
  make[2]: *** 
[src/gui/curses/headless/CMakeFiles/weechat-headless.dir/build.make:109: 
src/gui/curses/headless/weechat-headless] Error 1
  make[1]: *** [CMakeFiles/Makefile2:1952: 
src/gui/curses/headless/CMakeFiles/weechat-headless.dir/all] Error 2
  make[1]: *** Waiting for unfinished jobs
  /usr/bin/ld: error: /lib/x86_64-linux-gnu/libkeyutils.so.1: file too short
  collect2: error: ld returned 1 exit status
  make[2]: *** [src/gui/curses/normal/CMakeFiles/weechat.dir/build.make:108: 
src/gui/curses/normal/weechat] Error 1
  make[1]: *** [CMakeFiles/Makefile2:1870: 
src/gui/curses/normal/CMakeFiles/weechat.dir/all] Error 2
  make: *** [Makefile:146: all] Error 2
- 
+ 
  
  
  Reinstalling libkeyutils1 with `apt install --reinstall libkeyutils1`:
  
- root@voltron ~ # apt install --reinstall libkeyutils1 
+ root@voltron ~ # apt install --reinstall libkeyutils1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
  Need to get 10.4 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Get:1 http://mirror.hetzner.com/ubuntu/packages jammy/main amd64 libkeyutils1 
amd64 1.6.1-2ubuntu3 [10.4 kB]
- Fetched 10.4 kB in 0s (129 kB/s)
+ Fetched 10.4 kB in 0s (129 kB/s)
  (Reading database ... 209307 files and 

[Touch-packages] [Bug 2060034] [NEW] /usr/bin/ld: error: /lib/x86_64-linux-gnu/libkeyutils.so.1: file too short

[Vitor Luis]

Public bug reported:

Trying to compile weechat from source:

root@voltron ~/weechat/build # cmake .. -DCMAKE_BUILD_TYPE=Debug
-- Checking for one of the modules 'php8;php7'
-- Configuring done
-- Generating done
-- Build files have been written to: /root/weechat/build



root@voltron ~/weechat/build # make -j7
Consolidate compiler generated dependencies of target buflist
Consolidate compiler generated dependencies of target weechat_plugins_scripts
Consolidate compiler generated dependencies of target alias
Consolidate compiler generated dependencies of target weechat_plugins
Consolidate compiler generated dependencies of target charset
File config-git.h is up-to-date (git version: "v4.2.0-194-gf3f9dc388")
[  4%] Built target translations
[  4%] Built target version_git
Consolidate compiler generated dependencies of target exec
Consolidate compiler generated dependencies of target fifo
[  5%] Built target weechat_plugins_scripts
[  7%] Built target weechat_plugins
[  9%] Built target exec
[ 11%] Built target alias
[ 13%] Built target buflist
Consolidate compiler generated dependencies of target logger
Consolidate compiler generated dependencies of target fset
Consolidate compiler generated dependencies of target irc
Consolidate compiler generated dependencies of target script
Consolidate compiler generated dependencies of target relay
[ 16%] Built target logger
Consolidate compiler generated dependencies of target perl
[ 17%] Built target perl
Consolidate compiler generated dependencies of target python
[ 18%] Built target python
Consolidate compiler generated dependencies of target ruby
[ 22%] Built target script
[ 24%] Built target ruby
[ 37%] Built target irc
[ 42%] Built target relay
Consolidate compiler generated dependencies of target tcl
Consolidate compiler generated dependencies of target lua
[ 43%] Built target charset
Consolidate compiler generated dependencies of target guile
Consolidate compiler generated dependencies of target php
Consolidate compiler generated dependencies of target spell
[ 45%] Built target tcl
[ 45%] Built target lua
[ 46%] Built target guile
Consolidate compiler generated dependencies of target trigger
Consolidate compiler generated dependencies of target typing
Consolidate compiler generated dependencies of target xfer
[ 49%] Built target spell
[ 50%] Built target php
[ 51%] Built target typing
[ 54%] Built target trigger
Consolidate compiler generated dependencies of target weechat_gui_curses_normal
Consolidate compiler generated dependencies of target weechat_gui_common
Consolidate compiler generated dependencies of target weechat_gui_headless
Consolidate compiler generated dependencies of target weechat_ncurses_fake
[ 60%] Built target xfer
[ 60%] Built target weechat_ncurses_fake
[ 63%] Built target fset
[ 65%] Built target fifo
[ 68%] Built target weechat_gui_headless
[ 71%] Built target weechat_gui_curses_normal
[ 80%] Built target weechat_gui_common
Consolidate compiler generated dependencies of target weechat_core
[ 98%] Built target weechat_core
Consolidate compiler generated dependencies of target weechat
Consolidate compiler generated dependencies of target weechat-headless
[100%] Linking C executable weechat
[100%] Linking C executable weechat-headless
/usr/bin/ld: error: /lib/x86_64-linux-gnu/libkeyutils.so.1: file too short
collect2: error: ld returned 1 exit status
make[2]: *** 
[src/gui/curses/headless/CMakeFiles/weechat-headless.dir/build.make:109: 
src/gui/curses/headless/weechat-headless] Error 1
make[1]: *** [CMakeFiles/Makefile2:1952: 
src/gui/curses/headless/CMakeFiles/weechat-headless.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs
/usr/bin/ld: error: /lib/x86_64-linux-gnu/libkeyutils.so.1: file too short
collect2: error: ld returned 1 exit status
make[2]: *** [src/gui/curses/normal/CMakeFiles/weechat.dir/build.make:108: 
src/gui/curses/normal/weechat] Error 1
make[1]: *** [CMakeFiles/Makefile2:1870: 
src/gui/curses/normal/CMakeFiles/weechat.dir/all] Error 2
make: *** [Makefile:146: all] Error 2

##

Reinstalling libkeyutils1 with `apt install --reinstall libkeyutils1`:

root@voltron ~ # apt install --reinstall libkeyutils1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
Need to get 10.4 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://mirror.hetzner.com/ubuntu/packages jammy/main amd64 libkeyutils1 
amd64 1.6.1-2ubuntu3 [10.4 kB]
Fetched 10.4 kB in 0s (129 kB/s)
(Reading database ... 209307 files and directories currently installed.)
Preparing to unpack .../libkeyutils1_1.6.1-2ubuntu3_amd64.deb ...
Unpacking libkeyutils1:amd64 (1.6.1-2ubuntu3) over (1.6.1-2ubuntu3) ...
dpkg: warning: symbolic link '/lib/x86_64-linux-gnu/libkeyutils.so.1' size 

[Touch-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10

[Luis Alvarado]

Same thing is happening here with an Asus Z790. It was working properly
on 23.04. Not on 23.10 the sound works like this:

HiFi 2.0 - Very low sound. I have to crank the sound to max to barely hear it.
HiFi 5.1 - Only the front ones sound (but they sound around 60% when the volume 
is at 100%, meaning, the actual volume of them is not full). The rear speakers 
dont even sound. You have to put your ear to the actual speaker to hear it.
HiFi 7.1 - The front ones work correctly but any others do not.

The headphones still work correctly via bluetooth, but the whole sound
experience basically is dead. Everything is either very low or speaker
mode or nothing at all.

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

Title:
  audio disappeared after upgrade to Ubuntu 23.10

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except
  there is no audio output on streaming functions. The external
  bluetooth speaker is connected and detected. It is charged and
  responds to testing. Just no sound when playing videos or podcasts.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owner   975 F wireplumber
   /dev/snd/seq:owner   971 F pipewire
  CasperMD5CheckResult: fail
  CurrentDesktop: KDE
  Date: Tue Nov 14 17:50:17 2023
  InstallationDate: Installed on 2023-04-15 (213 days ago)
  InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago)
  dmi.bios.date: 07/04/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P31/W8 (MS-7788)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7788
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


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

[Touch-packages] [Bug 2038717] [NEW] Built-in speackers don't sound

[Juan Luis]

Public bug reported:

Built-in speackers don't produce any sound in HP Envy, although the
system settings and pavucontrol detect them and the sound is displayed
in the sound bars.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1
ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct  7 10:49:46 2023
InstallationDate: Installed on 2023-04-12 (177 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/13/2023
dmi.bios.release: 15.20
dmi.bios.vendor: Insyde
dmi.bios.version: F.20
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8A2C
dmi.board.vendor: HP
dmi.board.version: 23.43
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 23.43
dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd04/13/2023:br15.20:efr23.43:svnHP:pnHPENVYLaptop16-h0xxx:pvrType1ProductConfigId:rvnHP:rn8A2C:rvr23.43:cvnHP:ct10:cvrChassisVersion:sku6H668EA#ABE:
dmi.product.family: 103C_5335M8 HP ENVY
dmi.product.name: HP ENVY Laptop 16-h0xxx
dmi.product.sku: 6H668EA#ABE
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug jammy

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

Title:
  Built-in speackers don't sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Built-in speackers don't produce any sound in HP Envy, although the
  system settings and pavucontrol detect them and the sound is displayed
  in the sound bars.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  7 10:49:46 2023
  InstallationDate: Installed on 2023-04-12 (177 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2023
  dmi.bios.release: 15.20
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8A2C
  dmi.board.vendor: HP
  dmi.board.version: 23.43
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 23.43
  dmi.modalias: 
dmi:bvnInsyde:bvrF.20:bd04/13/2023:br15.20:efr23.43:svnHP:pnHPENVYLaptop16-h0xxx:pvrType1ProductConfigId:rvnHP:rn8A2C:rvr23.43:cvnHP:ct10:cvrChassisVersion:sku6H668EA#ABE:
  dmi.product.family: 103C_5335M8 HP ENVY
  dmi.product.name: HP ENVY Laptop 16-h0xxx
  dmi.product.sku: 6H668EA#ABE
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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


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

[Touch-packages] [Bug 2018656] Re: login process frozen in between username and password

[Luis Carlos Nogueira Mijias]

Still with the same error, I have already uninstalled Ubuntu and it
continues to freeze when logging in.

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

Title:
  login process frozen in between username and password

Status in gnome-online-accounts package in Ubuntu:
  Expired

Bug description:
   MY SYSTEM 
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

  gnome-online-accounts:
Installed: 3.48.0-1
Candidate: 3.48.0-1
Version table:
   *** 3.48.0-1 500
  500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I have tested this on my desktop running 23.04 on Intel I-9, and the second 
desktop running the same (23.04) but on Intel I-7, and both of them show the 
same problem.

  -PROBLEM---

  When I entered my email address in my Google account, I could provide
  my email address, and after I clicked on the following form to enter
  my password.  The form was able to pick up my email address and moved
  to the following form for password entry; it just froze in between.
  Sometimes, the password form could pick up the first keyboard
  character but never go past 2nd character.  Sometimes, it just froze
  without being able to pick up the first keyboard character.

  Then a bit later, the whole box of gnome-online-accounts blacks out.
  Closing with X didn't work, so I had to xkill the app.

  -TYPICAL BEHAVIOR---

  Usually, on 22.04, I never had a problem adding online accounts,
  particularly for Google accounts.   The first form asked for my email
  address, and quickly moved on to the following form asking for a
  password.  Once the password is accepted, it will move on to the next
  form requesting my authorization for GNOME to connect to my account on
  Google before adding it to my Ubuntu system (I'd see the drive folder
  on the bar on Nautilus).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-online-accounts 3.48.0-1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  6 13:51:07 2023
  InstallationDate: Installed on 2023-05-04 (2 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2033210] Re: Client-side window decoration rendering glitch

[Luis Capriles]

Hi!
Just in case, the glitch can be seen  when off focus in: Nautilus(files 42.6), 
System Monitor(42.0), Help (yelp), Characters(41.0), Web 42.4(Epiphany), 
Logs(42.0), Image Viewer(42.0), Calculator(41.1), Calendar(41.2), Disk Usage 
Analyzer(41.0).  

For Terminal(3.44.0) and Text Editor(gedit 41.0), there is no glitch.

On non Gnome apps (e.g.: LibreOffice), is not observed.

Regards

** Attachment added: "Image showing rendering glitch"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2033210/+attachment/5697282/+files/Screenshot%20from%202023-09-02%2015-18-58.png

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

Title:
  Client-side window decoration rendering glitch

Status in gtk+3.0 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  When the windows of the aforesaid applications loose focus, a pixel
  wide line of the same color as the style (light/dark) appear at the
  top of the window title bar.  While using Xorg/X11, the glitch doesn't
  occur.

  Ubuntu Desktop 22.04.3
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-04-01 (514 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  Package: gnome-shell 42.9-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  RelatedPackageVersions: mutter-common 42.9-0ubuntu4
  Tags:  wayland-session jammy
  Uname: Linux 6.2.0-26-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-08-19 (374 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2033210/+subscriptions


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

[Touch-packages] [Bug 1927192] Re: gdb ftbfs on armhf, testsuite timeouts

[Luis Machado]

Although this has been fixed for focal (20.04), it looks like the fix
wasn't applied to jammy (22.04). So we're still stripping symbols off of
ld.so for armhf.

Maybe I should open a new ticket to track this?

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

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Fix Released
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in gdb source package in Focal:
  Fix Released
Status in glibc source package in Focal:
  Fix Released
Status in gdb source package in Groovy:
  Won't Fix
Status in glibc source package in Groovy:
  Won't Fix
Status in gdb source package in Hirsute:
  Won't Fix
Status in glibc source package in Hirsute:
  Won't Fix
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Released

Bug description:
  [Impact]

  * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is
  not installed.

  [Test Plan]

  * Check that ld.so is not stripped on armhf:
  $  /lib/*/ld-2.31.so
  libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, 
EABI5 version 1 (SYSV), dynamically linked, 
BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not 
stripped

  * Check that ld.so is stripped on amd64:

  $ file /lib/x86_64-linux-gnu/ld-2.31.so
  /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, 
version 1 (SYSV), dynamically linked, 
BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped

  [Where problems could occur]

  * The fix is not stripping ld.so on armhf. Not stripping it comes with
  a notable increase in file size and it may be performance critical
  109K stripped vs 1.3M unstripped. Accidentally ld.so could be left
  unstripped on other architectures, but the test plan covers checking
  that, at least on amd64. Other than those not stripping ld.so should
  not cause any issue.

  [Original Bug Text]

  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

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


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

[Touch-packages] [Bug 1815494] Re: May remove autoremovable non-kernel packages matching pattern from APT::VersionedKernelPackages

[Luis Alvarez Pinilla]

** Changed in: update-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  May remove autoremovable non-kernel packages matching pattern from
  APT::VersionedKernelPackages

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  * Non-kernel related autoremovable packages may be removed by 
unattended-upgrades due to their name matching generic patterns like 
'.*-modules' which should be applied to versioned kernel packages only.
  * The fix corrects the way those patterns are handled.

  [Test Case]

  * test/test_remove_unused.py checks for correct pattern usage now.

  [Regression Potential]

  * Unattended-upgrades may stop removing autoremovable kernels, but the
  tests also contain cases covering this and u-u's kernel autoremoval
  still works.

  [Original Bug Text]

  Unattended-upgrades and Update Manager use the patterns from the
  APT::VersionedKernelPackages list directly for finding kernel packages
  to remove while APT uses patterns by attaching version and flavor to
  them.

  As a result in APT's script ".*-modules" becomes
  "^.*-modules-4\.15\.0-45-generic$":

  ...
  for package in $(apt-config dump --no-empty --format '%v%n' 
'APT::VersionedKernelPackages'); do
  for kernel in $kernels; do
  echo "   \"^${package}-${kernel}$\";"
    done
  ...

  In unattended-upgrades and update-manager ".*-modules" is used
  directly for matching and may false  identify autoremovable packages
  as kernel-related ones and remove them (of just offer the removal in
  case of update-manager):

  ...
  Removing unused kernel packages: extra-cmake-modules
  marking extra-cmake-modules for removal
  (Reading database ... 31149 files and directories currently installed.)
  Removing extra-cmake-modules (5.44.0-0ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  Packages that were successfully auto-removed: extra-cmake-modules
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1815494/+subscriptions


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

[Touch-packages] [Bug 2018290] [NEW] Clicking on the top right corner fails

[Luis Alvarado]

Public bug reported:

Problem is that when any app gets maximized, or uses the half screen
technique (eg: Drag a window to the left or right side of the screen so
it half-screen maximizes itself) the top portion of the window can not
be clicked (left or right clicked). So any button on that area do not
work. Like something is overlapping the buttons. The solution is to drag
the window back to a smaller size to use those buttons again.

It also has a similar issue where, when clicking on the gnome extensions
at the top or even the options of ubuntu at the top, you need to
slightly click below them a bit for them to actually register the click.


The problem has been mentioned here which is the same one:
https://askubuntu.com/questions/1464858/right-corner-at-chrome-not-response-to-mouse-click

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  530.41.03  Thu Mar 16 19:48:20 
UTC 2023
 GCC version:  gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1)
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue May  2 03:55:34 2023
DistUpgraded: Fresh install
DistroCodename: lunar
DistroVariant: ubuntu
DkmsStatus: nvidia/530.41.03, 6.2.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation AD102 [GeForce RTX 4090] [10de:2684] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. AD102 [GeForce RTX 4090] 
[19da:4675]
InstallationDate: Installed on 2023-04-20 (11 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: ASUS System Product Name
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=276e1671-8c73-42fc-bf30-ea9c79e82647 ro mitigations=off pci=nommconf 
nvidia-drm.modeset=1 intel_idle.max_cstate=1 ibt=off
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2023
dmi.bios.release: 9.4
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0904
dmi.board.asset.tag: Default string
dmi.board.name: ROG MAXIMUS Z790 HERO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0904:bd03/29/2023:br9.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSZ790HERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
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: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug lunar ubuntu

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

Title:
  Clicking on the top right corner fails

Status in xorg package in Ubuntu:
  New

Bug description:
  Problem is that when any app gets maximized, or uses the half screen
  technique (eg: Drag a window to the left or right side of the screen
  so it half-screen maximizes itself) the top portion of the window can
  not be clicked (left or right clicked). So any button on that area do
  not work. Like something is overlapping the buttons. The solution is
  to drag the window back to a smaller size to use those buttons again.

  It also has a similar issue where, when clicking on the gnome
  extensions at the top or even the options of ubuntu at the top, you
  need to slightly click below 

[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Luis Alberto Pabón]

Christian, it should only be using msbc when the headset's microphone is
in use, otherwise it should automatically fall back to A2DP.

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 1623530] Re: Apport should be disabled by default

[Luis Alvarado]

Hi team, wasn't this already done since on the new 23.04 and maybe
before, there is a specific question that asks if you would like to
report or not to ubuntu? I think that is related to this directly no?

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

Title:
  Apport should be disabled by default

Status in Apport:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I work with large communities (US, India, Latin America) and almost
  the number one issue they have with Ubuntu or simply scares them off
  is the fact that errors keep popping up every time. Some times
  multiples times per minutes, per hour, per day.

  The reason is how apport works by default. The "solution" is going to
  /etc/default/apport and setting the option to 0 (Disable). I do
  understand the full benefit or submitting automatically all bug
  reports, but this has gotten (And most Ubuntu users will be able to
  confirm) out of hand with some many popup questions about some bug or
  another that are simply fixed the moment the report is going to be
  send (eg: Compiz issue that was fixed a couple of milliseconds later,
  unity issue, dash issue, firefox issue, etc..). All of them have
  mechanism to handle failures and basically heal themselves.

  The question regarding this is:

  Leaving apport enable by default on an Ubuntu installation simply
  scares or annoys end users (a lot may I add). Leaving it disabled, it
  will not send a bug report, but there is no issue in simply creating
  an ubuntu-bug report through the terminal. So the sending of the
  report is still valid, but is not forced onto the user (And not forced
  so many times).

  This report is back by about 3 years going back and forth with the
  same apport issue and seeing probably around 500 users I have helped
  myself with the same issue, since this makes Ubuntu less productive to
  the actual user, even from start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 14 08:16:03 2016
  InstallationDate: Installed on 2016-04-22 (144 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273

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


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

[Touch-packages] [Bug 2011837] Re: Nvidia with Wayland or Xorg issue

[Luis Alvarado]

Sorry, did not know it was filed against launchpad. Did not even know
the option to set it was set to launchpad. This issue is also related to
this one
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2012983 just in
case. Same hardware.

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

Title:
  Nvidia with Wayland or Xorg issue

Status in wayland package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  I will summarize here what I put at
  https://discourse.ubuntu.com/t/ubuntu-23-04-testing-week/34246/6

  On Ubuntu 23.04, if I install it, it works fine but there is a
  considerable lag for everything. This is when using Wayland. If I do
  not change the custom.conf gdm to not use wayland, I can get in but I
  can not interact with any windows. Context menus and sub menus open
  but do not do anything. The only way for me to get to the terminal was
  to open nautilus/files from the Dock, then right click any empty space
  and select terminal. The moment I did that I had a couple of seconds
  before it crashed the terminal. But was able to get a picture of the
  hardware after my 3rd attempt.

  If I do put in on xorg, then an image I posted on the 1st link happens
  and it stays there, does not matter if I change tty, it always shows
  and needed to reinstall 23.04 to be able to go back to wayland. But if
  I use wayland I can actually feel the lag and the interaction with
  windows and all. This started happening all today after applying all
  the latest updates for 23.04 (I did not update since I think since
  several days back).

  The hardware that I was using for testing is:

  CPU - 13900k
  MOBO - Asus Z790 Hero
  RAM: DDR5 128GB
  VID: Nvidia 4090 (Drivers were automatically installed during setup)
  SSD - SN850x

  It is a computer just for Ubuntu 23.04 testing right now.

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


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

[Touch-packages] [Bug 2000917] Re: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound

[Luis Alberto Pabón]

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

Ah my apologies, I didn't realise I had already reported this a few
months back when updating to jammy here
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965750

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

Title:
  [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers
  but no sound

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Every now and then, after boot, I get no sounds at all coming from the
  speakers. Everything seems normal - the control center reports the
  output as active, and if I play anything with sound I can see the VU
  meter going back and forth. I've attached a screenshot showing as
  much.

  The internal microphone does not pick up any sounds either when this
  happens.

  If I connect my Bose NC700 bluetooth headset, I get sound out of it
  just fine, and the mike on it also works.

  Sometimes the internal sound will start working after a few times of
  switching back and forth internal audio / bluetooth headset.

  Restarting the systemd pipewire and pipewire-pulse user services
  doesn't help. Nor does killing & respawning wireplumber.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire-pulse 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: sway
  Date: Tue Jan  3 11:25:23 2023
  InstallationDate: Installed on 2023-01-03 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago)

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


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

[Touch-packages] [Bug 2000917] Re: [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers but no sound

[Luis Alberto Pabón]

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

That does sound like it could be an issue for sure.

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

Title:
  [Dell XPS 15 9560] Pipewire correctly detects laptop sound & speakers
  but no sound

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Every now and then, after boot, I get no sounds at all coming from the
  speakers. Everything seems normal - the control center reports the
  output as active, and if I play anything with sound I can see the VU
  meter going back and forth. I've attached a screenshot showing as
  much.

  The internal microphone does not pick up any sounds either when this
  happens.

  If I connect my Bose NC700 bluetooth headset, I get sound out of it
  just fine, and the mike on it also works.

  Sometimes the internal sound will start working after a few times of
  switching back and forth internal audio / bluetooth headset.

  Restarting the systemd pipewire and pipewire-pulse user services
  doesn't help. Nor does killing & respawning wireplumber.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire-pulse 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: sway
  Date: Tue Jan  3 11:25:23 2023
  InstallationDate: Installed on 2023-01-03 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2023-01-03 (0 days ago)

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


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

[Touch-packages] [Bug 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)

[Luis Alberto Pabón]

Works for me.

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

Title:
  [jammy regression] webkit apps do not display content (yelp, epiphany,
  gnome-online-accounts etc)

Status in Gnome DevHelp:
  Invalid
Status in Mesa:
  Fix Released
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Invalid

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

Re: [Touch-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

[Luis Augusto Xavier Cruz]

Unfortunately I do not know the answer. It's been a while since I stopped
using ubuntu on raspberrypi and i went back to using the official system
for the device and since then I haven't changed system anymore. Also, for
other personal interests I haven't used raspberrypi so often lately.

Em qua., 12 de out. de 2022 às 22:45, Daniel van Vugt <
1924...@bugs.launchpad.net> escreveu:

> Which package should be marked as Fix Released for 22.10?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1946664).
> https://bugs.launchpad.net/bugs/1924251
>
> Title:
>   Embedded browser display corruption under Wayland on Pi desktop
>
> Status in gtk+3.0 package in Ubuntu:
>   Confirmed
> Status in webkit2gtk package in Ubuntu:
>   Confirmed
> Status in yelp package in Ubuntu:
>   Confirmed
>
> Bug description:
>   On the jammy Pi desktop, under a wayland session, the body of a window
>   containing an HTML renderer (e.g. help text or a login page) displays
>   corruption.
>
>   These reproduction cases may not be entirely reliable given that
>   *some* pages appear to render correctly, but I'll include a couple in
>   the hopes of making it reliably reproducible:
>
>   1. Open the Lights Off game
>   2. Select "Help" from the menu
>   3. In the help window that appears, select any link
>
>   "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
>   me, but "Help Translate" doesn't so you may need to click around some
>   links until the corruption appears -- however, once it does even
>   navigating back to the prior page which rendered happily now displays
>   the same corruption.
>
>   Another reproduction case:
>
>   1. Open the Settings application
>   2. Select the Online Applications option from the left
>   3. Select the Google entry in the list
>   4. The login window that appears always displays corruption for me
>
>   The Microsoft option always reliably corrupts for me, but the Facebook
>   one doesn't so again I wonder how reproducible this may be for others
>   (might be worth trying several options if the first doesn't display
>   corruption).
>
>   The corruption appears in the form of "shredded" content as if a
>   horizontal stride is set incorrectly somewhere, but only appears in
>   the body of the window; the window decorations are unaffected. I'll
>   attach a screenshot of the corrupted help window to illustrate.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions
>
>

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  On the jammy Pi desktop, under a wayland session, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions


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

[Touch-packages] [Bug 1990668] [NEW] package python3-oauthlib 3.2.0-1ubuntu0.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[Luis Rodriguez]

Public bug reported:

Failed to get installed

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: python3-oauthlib 3.2.0-1ubuntu0.1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
Date: Fri Sep 23 06:58:07 2022
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2022-06-22 (92 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.7
SourcePackage: python-oauthlib
Title: package python3-oauthlib 3.2.0-1ubuntu0.1 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-oauthlib (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy need-duplicate-check

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

Title:
  package python3-oauthlib 3.2.0-1ubuntu0.1 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

Status in python-oauthlib package in Ubuntu:
  New

Bug description:
  Failed to get installed

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: python3-oauthlib 3.2.0-1ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Fri Sep 23 06:58:07 2022
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2022-06-22 (92 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: python-oauthlib
  Title: package python3-oauthlib 3.2.0-1ubuntu0.1 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-oauthlib/+bug/1990668/+subscriptions


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

[Touch-packages] [Bug 1987520] [NEW] package libxslt1.1 1.1.34-4ubuntu0.22.04.1 failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2

[Luis Gomez]

Public bug reported:

I dont know anything about this error

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libxslt1.1 1.1.34-4ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
AptOrdering:
 perl-modules-5.30:amd64: Remove
 libxslt1.1:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Aug 22 18:07:00 2022
ErrorMessage: el subproceso dpkg-deb --fsys-tarfile devolvió el código de 
salida de error 2
InstallationDate: Installed on 2021-10-02 (325 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.7
SourcePackage: libxslt
Title: package libxslt1.1 1.1.34-4ubuntu0.22.04.1 failed to install/upgrade: el 
subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2
UpgradeStatus: Upgraded to jammy on 2022-08-14 (9 days ago)

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


** Tags: amd64 apport-package jammy

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

Title:
  package libxslt1.1 1.1.34-4ubuntu0.22.04.1 failed to install/upgrade:
  el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de
  error 2

Status in libxslt package in Ubuntu:
  New

Bug description:
  I dont know anything about this error

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libxslt1.1 1.1.34-4ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering:
   perl-modules-5.30:amd64: Remove
   libxslt1.1:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Aug 22 18:07:00 2022
  ErrorMessage: el subproceso dpkg-deb --fsys-tarfile devolvió el código de 
salida de error 2
  InstallationDate: Installed on 2021-10-02 (325 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: libxslt
  Title: package libxslt1.1 1.1.34-4ubuntu0.22.04.1 failed to install/upgrade: 
el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2
  UpgradeStatus: Upgraded to jammy on 2022-08-14 (9 days ago)

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


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

[Touch-packages] [Bug 1986631] [NEW] package linux-image-5.14.0-1048-oem 5.14.0-1048.55 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[José Luis Torres]

Public bug reported:

happened on startup

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.14.0-1048-oem 5.14.0-1048.55
ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Aug 13 11:35:12 2022
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2021-10-07 (312 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: initramfs-tools
Title: package linux-image-5.14.0-1048-oem 5.14.0-1048.55 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to focal on 2022-08-13 (2 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package linux-image-5.14.0-1048-oem 5.14.0-1048.55 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  happened on startup

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1048-oem 5.14.0-1048.55
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Aug 13 11:35:12 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-10-07 (312 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.14.0-1048-oem 5.14.0-1048.55 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to focal on 2022-08-13 (2 days ago)

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


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

[Touch-packages] [Bug 1927192]

[Luis-machado]

Fixed based on
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1927192

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

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Fix Released
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in gdb source package in Focal:
  Fix Released
Status in glibc source package in Focal:
  Fix Released
Status in gdb source package in Groovy:
  Won't Fix
Status in glibc source package in Groovy:
  Won't Fix
Status in gdb source package in Hirsute:
  Won't Fix
Status in glibc source package in Hirsute:
  Won't Fix
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Released

Bug description:
  [Impact]

  * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is
  not installed.

  [Test Plan]

  * Check that ld.so is not stripped on armhf:
  $  /lib/*/ld-2.31.so
  libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, 
EABI5 version 1 (SYSV), dynamically linked, 
BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not 
stripped

  * Check that ld.so is stripped on amd64:

  $ file /lib/x86_64-linux-gnu/ld-2.31.so
  /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, 
version 1 (SYSV), dynamically linked, 
BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped

  [Where problems could occur]

  * The fix is not stripping ld.so on armhf. Not stripping it comes with
  a notable increase in file size and it may be performance critical
  109K stripped vs 1.3M unstripped. Accidentally ld.so could be left
  unstripped on other architectures, but the test plan covers checking
  that, at least on amd64. Other than those not stripping ld.so should
  not cause any issue.

  [Original Bug Text]

  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

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


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

[Touch-packages] [Bug 1970279] [NEW] My monitor image turned yellow.

[Breno Luis da Silva Xavier]

Public bug reported:

I had to switch from Wayland to Xorg on the login screen, and after
login the screen had a yellow filter.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 25 18:59:04 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev c9) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8]
InstallationDate: Installed on 2022-04-23 (2 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=6abdccf1-2e9d-4265-a466-6dcef0abc427 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.40
dmi.board.name: A320M-HD
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd07/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HD:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session

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

Title:
  My monitor image turned yellow.

Status in xorg package in Ubuntu:
  New

Bug description:
  I had to switch from Wayland to Xorg on the login screen, and after
  login the screen had a yellow filter.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 18:59:04 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev c9) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8]
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=6abdccf1-2e9d-4265-a466-6dcef0abc427 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: A320M-HD
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd07/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HD:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To 

[Touch-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore

[Luis Alberto Pabón]

Added `gnome-control-center` to affected - GNOME online accounts
requires a web browsing session to auth into some services.

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  New
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Touch-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore

[Luis Alberto Pabón]

`WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution` works around the issue for
me on a Sway wayland session and running evolution in native wayland
mode.

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in liferea package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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

[Touch-packages] [Bug 1965750] [NEW] [jammy regression] No sound from onboard audio (playback / record)

[Luis Alberto Pabón]

Public bug reported:

After updates I applied last friday, my onboard audio has ceased to
function. No audio comes out the laptop speakers and no audio goes in
the internal microphone (built in audio).

If I connect my bluetooth headset (Bose NC700) the audio works, but only
ever in mono. I cannot switch to the A2DP sink, it stays on HPF mono.

I tried switching from pulseaudio to pipewire and pipewire-pulse, and I
kind of made it work - the bluetooth headset works correctly, and the
onboard audio works again after switching default inputs and outputs a
number of times.

I just want to stress my laptop's audio has worked fine for years in all
versions of ubuntu including Jammy, but only up until Friday Jan the
18th 2022.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: sway
Date: Mon Mar 21 11:48:25 2022
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: Upgraded to jammy on 2022-03-01 (20 days ago)
dmi.bios.date: 11/17/2019
dmi.bios.release: 1.18
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.18.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  [jammy regression] No sound from onboard audio (playback / record)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After updates I applied last friday, my onboard audio has ceased to
  function. No audio comes out the laptop speakers and no audio goes in
  the internal microphone (built in audio).

  If I connect my bluetooth headset (Bose NC700) the audio works, but
  only ever in mono. I cannot switch to the A2DP sink, it stays on HPF
  mono.

  I tried switching from pulseaudio to pipewire and pipewire-pulse, and
  I kind of made it work - the bluetooth headset works correctly, and
  the onboard audio works again after switching default inputs and
  outputs a number of times.

  I just want to stress my laptop's audio has worked fine for years in
  all versions of ubuntu including Jammy, but only up until Friday Jan
  the 18th 2022.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Mon Mar 21 11:48:25 2022
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (20 days ago)
  dmi.bios.date: 11/17/2019
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.

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


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

[Touch-packages] [Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63

[Luis Alberto Pabón]

Thank you, I was plagued by this issue on my Bose NC700 cans. In my case
bluetoothd isn't crashing btw.

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

Title:
  [jammy] Bluetooth headphones unable to connect after suspend in BlueZ
  5.63

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Bose quietcomfort 35 is a common headset that can no longer connect to
  a jammy system after just one suspend. This started at the end of
  January but just now really debugging the issue.

  Side note that my bluetooth mouse works fine without problem after any
  amount of suspends.

  The headset is only trying to connect to the jammy system (no other
  bluetooth devices it's paired with has active bluetooth, to isolate
  only the jammy <-> headset issue). This is jammy running on a T590, up
  to date, not proposed.

  heather@fenrir:~$ dpkg -l | grep bluetooth
  ii  gir1.2-gnomebluetooth-1.0:amd643.34.5-4   
amd64Introspection data for GnomeBluetooth
  ii  gnome-bluetooth3.34.5-4   
amd64GNOME Bluetooth tools
  ii  libbluetooth-dev:amd64 5.63-0ubuntu1  
amd64Development files for using the BlueZ Linux Bluetooth 
library
  ii  libbluetooth3:amd645.63-0ubuntu1  
amd64Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth13:amd64 3.34.5-4   
amd64GNOME Bluetooth tools - support library
  ii  pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1   
amd64Bluetooth module for PulseAudio sound server

  On a fresh boot (not suspended yet), I can connect the headset
  successfully. Here are the logs of that:

  Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input30
  Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on 
/dev/input/event22 (Bose QuietComfort 35 (AVRCP))
  Mar 01 09:44:03 fenrir NetworkManager[1536]:   [1646124243.8660] 
platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 
(Permission denied)
  Mar 01 09:44:04 fenrir bluetoothd[1532]: 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of 
process 2708 owned by '1000' RT at priority 5.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: 
org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume'
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70%
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked

  But then if I close the laptop lid and reopen, login, and try to
  connect the headset the device is found invalid with the following
  logs:

  Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input152
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on 
/dev/input/event19 (Bose QuietComfort 35 (AVRCP))
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F
  Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() 
Hands-Free Voice gateway replied with an error: 
org.bluez.Error.InvalidArguments, Unable to handle new connection
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist 

Re: [Touch-packages] [Bug 1946664] Re: account setup window becomes unconfigured

[Luis Augusto Xavier Cruz]

Sebastian,
I have not noticed any similar problem in any other application that I have
used on the system.
I am sorry but I am new to using the system and I did not understand if the
rendering problems you mentioned refer to any application that I need to
test? (...rendering problems in yelp , devhelp or epiphany-browser?)

Em ter., 12 de out. de 2021 às 11:35, Sebastien Bacher <
1946...@bugs.launchpad.net> escreveu:

> Thank you for your bug report, it seems corruption in webkitgtk views.
> Do you get similar rendering problems in yelp , devhelp or epiphany-
> browser?
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> ** Summary changed:
>
> - account setup window becomes unconfigured
> + [raspi] screen correct on online accounts webviews
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1946664
>
> Title:
>   [raspi] screen correct on online accounts webviews
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I installed ubuntu desktop on my Raspberrypi 4b. I set up the ubuntu
>   sign-one account, but to set up the Google and Microsoft account, the
>   window to enter the account data gets misconfigured on the screen and
>   does not read the fields to enter the data and set up access to my
>   accounts.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: xorg 1:7.7+22ubuntu1
>   ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22
>   Uname: Linux 5.11.0-1019-raspi aarch64
>   ApportVersion: 2.20.11-0ubuntu65.3
>   Architecture: arm64
>   BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
>   CasperMD5CheckResult: unknown
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Oct 11 12:12:33 2021
>   DistUpgraded: Fresh install
>   DistroCodename: hirsute
>   DistroVariant: ubuntu
>   GraphicsCard:
>
>   ImageMediaBuild: 20210421
>   Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805
> USB 3.0 Host Controller
>   ProcEnviron:
>LANGUAGE=pt_BR:pt:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=pt_BR.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0
> snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1
> video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:BB:4B:64
> vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0
> console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait
> fixrtc quiet splash
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   acpidump:
>
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.105-3~21.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1946664/+subscriptions
>
>

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

Title:
  [raspi] screen corruption on online accounts webviews

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I installed ubuntu desktop on my Raspberrypi 4b. I set up the ubuntu
  sign-one account, but to set up the Google and Microsoft account, the
  window to enter the account data gets misconfigured on the screen and
  does not read the fields to enter the data and set up access to my
  accounts.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22
  Uname: Linux 5.11.0-1019-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: arm64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 11 12:12:33 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  GraphicsCard:
   
  ImageMediaBuild: 20210421
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:BB:4B:64 
vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0 
console=tty1 

[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

[Luis Oliveira]

I upgraded yesterday from 20.10 to 21.04.

In 20.10 I had trouble pairing with my current headphones (Havit 162) - I had 
to repair through the terminal.
Now, in 21.04, the repairing works in the GUI.

However, today I turned off the bluetooth in the GUI and when I tried to
turn it on again the toggle did not work.

I had to input in the terminal
```systemctl restart bluetooth```

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  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 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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

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

[Touch-packages] [Bug 1927192]

[Luis]

3) is fine, but can you guarantee the detached information will always
be available?

Having the required data in the ld.so file itself would be best.

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

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Incomplete
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Committed
Status in gdb source package in Focal:
  New
Status in glibc source package in Focal:
  New
Status in gdb source package in Groovy:
  New
Status in glibc source package in Groovy:
  New
Status in gdb source package in Hirsute:
  New
Status in glibc source package in Hirsute:
  New
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Committed

Bug description:
  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

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

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

[Touch-packages] [Bug 1927192]

[Luis]

After investigating this, the root cause of the timeouts is caused by
GDB using the wrong type of breakpoint (between a 4 bytes ARM breakpoint
and a 2 bytes thumb breakpoint), which causes some unexpected results.

The reason why this is happening is a bit more complex though. GDB has a
couple mechanisms for tracking loading/unloading of shared libraries in
dynamically-linked binaries. Via _dl_debug_state and r_brk and via stap
probes.

Up until Ubuntu 18.04 (glibc 2.27), GDB could not use the stap probes
mechanism because it ran into a bug when parsing stap expression, thus
failing the check and falling back to using the old _dl_debug_state and
r_brk mechanism.

The _dl_debug_state/r_brk mechanism works because we have an entry for
_dl_debug_state in the .dynsym section of ld.so.  Even though ld.so is
completely stripped of mapping symbols (another way to tell arm/thumb
modes apart), which are only available via the debug symbols file, GDB
can still tell _dl_debug_state is arm or thumb mode because the ELF
symbol carries a flag indicating so. That's why this fallback mechanism
works.

On Ubuntu 20.04, running glibc 2.31, GDB no longer runs into problems
with stap probes. Thus GDB decides to use this mechanism instead of the
old _dl_debug_state/r_brk one.

Both mechanisms function by having GDB insert breakpoints at specific
location so shared library events can be tracked. But in the stap probes
case there are no real symbols.

What we have is metadata that contains the name of the probe and its
address. This address falls within a particular function. For example,
init_start and init_complete are probe points that fall within dl_main.
The probe points do not seem to carry any information about whether we
have arm or thumb mode.

As before, the mapping symbols should tell us what the mode is, but
ld.so is stripped and doesn't carry those. But GDB could look at the ELF
symbol of the function the probe is sitting at, except that these
symbols (not considered special in any way) have been stripped as well.
So the arm/thumb information is completely gone and GDB can no longer
make the correct decision.

So GDB defaults to assuming arm mode for the breakpoint to use, which is
obviously wrong for thumb code.

There are two possible solutions:

1 - Fallback to using _dl_debug_state/r_brk for armhf in GDB. This is
considered bad by GDB's maintainers, because it means using an outdated
mechanism instead of better interfaces.

2 - Don't strip glibc/ld.so function symbols that have stap probes
installed in them.

Right now, these are the functions that contain probes and that GDB
wants to breakpoint in a special way:

_dl_main, _dl_map_object_from_fd, lose, dl_open_worker and
_dl_close_worker

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

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Incomplete
Status in gdb package in Ubuntu:
  Confirmed
Status in gdb source package in Impish:
  Confirmed

Bug description:
  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

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

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

[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Luis Alberto Pabón]

I haven't got any pulseaudio updates on 21.04, to which version of
ubuntu was the fix released to?

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Luis Alberto Pabón]

That would be for 21.10 at this point yes?

I wonder, how close/far is Ubuntu to swap PA for Pipewire? After next
lts? I do believe this particular issue is not present on current
Pipewire.

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Luis]

Issue:

- I can switch profiles, but when I chose HSP/HFP I get no sound and the 
microphone doesn't work.
- I didn't have this issue in 18.04 LTS or 16.04 LTS (same hardware)

Environment:

- Kernel: Linux 5.8.0-44-generic
- OS: Ubuntu 20.04.1 LTS
- Headset: WC-CH500
- BT Dongle: Plugable USB Bluetooth 4.0

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1916349] [NEW] pkgconfig --libs flags

[Luis de Arquer]

Public bug reported:

After installing the development version, the file:

/usr/lib/x86_64-linux-gnu/pkgconfig/libjpeg.pc

contains the line:

libdir=/build/libjpeg-turbo-6HlDLQ/libjpeg-turbo-2.0.3/obj-x86_64-linux-
gnu/lib/x86_64-linux-gnu

which points to no valid directory in the system. It probably should
look like:

libdir=/usr/lib/x86_64-linux-gnu

Otherwise, it breaks any build using pkg-config for this library

** Affects: libjpeg-turbo (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  pkgconfig --libs flags

Status in libjpeg-turbo package in Ubuntu:
  New

Bug description:
  After installing the development version, the file:

  /usr/lib/x86_64-linux-gnu/pkgconfig/libjpeg.pc

  contains the line:

  libdir=/build/libjpeg-turbo-6HlDLQ/libjpeg-turbo-2.0.3/obj-x86_64
  -linux-gnu/lib/x86_64-linux-gnu

  which points to no valid directory in the system. It probably should
  look like:

  libdir=/usr/lib/x86_64-linux-gnu

  Otherwise, it breaks any build using pkg-config for this library

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1916349/+subscriptions

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

[Touch-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

[Luis Alberto Pabón]

Fix will come with network-manager-gnome 1.20.0.

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

Title:
  NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were 
created by Docker.
  Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged 
under the gnome system tray icon which is kind of annoying.
  I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 24 14:22:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-29 (632 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
   192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.40
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-08-19T11:46:06.705439
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

[Luis Alberto Pabón]

I managed to get Campbell's patch to hide unmanaged devices upstreamed:

https://gitlab.gnome.org/GNOME/network-manager-
applet/-/merge_requests/93

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

Title:
  NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were 
created by Docker.
  Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged 
under the gnome system tray icon which is kind of annoying.
  I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 24 14:22:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-29 (632 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
   192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.40
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-08-19T11:46:06.705439
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1623530] Re: Apport should be disabled by default

[Luis Alvarado]

Hi Brian, yes it works but in the installer it should have that option,
so that when installing ubuntu for the first time for example, the user
can stop reports from the beginning.

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

Title:
  Apport should be disabled by default

Status in Apport:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I work with large communities (US, India, Latin America) and almost
  the number one issue they have with Ubuntu or simply scares them off
  is the fact that errors keep popping up every time. Some times
  multiples times per minutes, per hour, per day.

  The reason is how apport works by default. The "solution" is going to
  /etc/default/apport and setting the option to 0 (Disable). I do
  understand the full benefit or submitting automatically all bug
  reports, but this has gotten (And most Ubuntu users will be able to
  confirm) out of hand with some many popup questions about some bug or
  another that are simply fixed the moment the report is going to be
  send (eg: Compiz issue that was fixed a couple of milliseconds later,
  unity issue, dash issue, firefox issue, etc..). All of them have
  mechanism to handle failures and basically heal themselves.

  The question regarding this is:

  Leaving apport enable by default on an Ubuntu installation simply
  scares or annoys end users (a lot may I add). Leaving it disabled, it
  will not send a bug report, but there is no issue in simply creating
  an ubuntu-bug report through the terminal. So the sending of the
  report is still valid, but is not forced onto the user (And not forced
  so many times).

  This report is back by about 3 years going back and forth with the
  same apport issue and seeing probably around 500 users I have helped
  myself with the same issue, since this makes Ubuntu less productive to
  the actual user, even from start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 14 08:16:03 2016
  InstallationDate: Installed on 2016-04-22 (144 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273

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

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

[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Luis Antonio Dias de Sá Junior]

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

Problem has NOT been fixed for my setup:

- Kernel: 5.4.0-58-generic #64
- OS: Ubuntu 20.04.1 LTS
- Machine: Lenovo ThinkPad
- Headset: JBL 500BT

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Touch-packages] [Bug 1901966] Re: Unable to stop at breakpoint in 32-bit executable

[Luis]

This doesn't seem to be related to the previous bugs.

I tried to reproduce this on 18.04.4 (I don't have 20.04) and a fresh
build of GDB master, and I couldn't.

(gdb) disass _start
Dump of assembler code for function _start:
   0x00010074 <+0>: mov r7, #4
   0x00010078 <+4>: mov r0, #1
   0x0001007c <+8>: ldr r1, [pc, #12]   ; 0x10090 <_start+28>
   0x00010080 <+12>:ldr r2, [pc, #12]   ; 0x10094 <_start+32>
   0x00010084 <+16>:svc 0x
   0x00010088 <+20>:mov r7, #1
   0x0001008c <+24>:svc 0x
   0x00010090 <+28>:muleq   r2, r8, r0
   0x00010094 <+32>:andeq   r0, r0, lr
End of assembler dump.
(gdb) b _start
Breakpoint 1 at 0x10074: file /tmp/hello.S, line 4.
(gdb) r
Starting program: /tmp/hello

Breakpoint 1, _start () at /tmp/hello.S:4
4   MOV R7, #4


With Ubuntu 18.04.4's GDB it also works.

Can you please turn on debugging and paste the log?

Use "set debug infrun 1" before the run command.

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

Title:
  Unable to stop at breakpoint in 32-bit executable

Status in gdb package in Ubuntu:
  New

Bug description:
  I believe I'm having the problem described in #1846557 and #1848200.
  Those bugs were reported fixed in 8.1.1 but I'm observing them in 9.2
  so I suspect a regression (in fact, if I read the notes correctly, the
  earlier reports were from another regression!).

  I create a new EC2 server on AWS with Ubuntu Server 20.04 LTS (64-bit
  Arm) then perform the following installs (not sure what is needed or
  if something is missing):

  ```
  sudo dpkg --add-architecture armhf
  sudo apt update
  sudo apt upgrade -y
  sudo apt install -y build-essential vim binutils-arm-linux-gnueabi \
    gdb libc6:armhf libstdc++6:armhf
  ```

  Then I create hello.s:

  ```
  .text
  .global _start
  _start:
  MOV R7, #4
  MOV R0, #1
  LDR R1, =hello
  LDR R2, =hello_size
  SWI 0
  MOV R7, #1
  SWI 0

  .data
  hello:  .asciz  "Hello world!\n"
  .equhello_size, (.-hello)
  ```

  Then I assemble, link, and run, all with success. Finally, I try to
  debug:

  ```
  $ arm-linux-gnueabi-as -ggdb -mcpu=cortex-a57 -o out.o hello.s
  $ arm-linux-gnueabi-ld out.o -dynamic-linker=/usr/lib/ld-linux-armhf.so.3 -o 
out
  $ rm out.o
  $ ./out
  Hello world!
  $ gdb out
  GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
  ...
  Reading symbols from out...
  (gdb) b _start
  Breakpoint 1 at 0x10074: file hello.s, line 4.
  (gdb) run
  Starting program: /home/ubuntu/280/out
  ```

  At this point everything hangs until I press ^C:

  ```
  ^C
  Program received signal SIGINT, Interrupt.
  0xba072284 in ?? ()
  (gdb) bt
  #0  0xba072284 in ?? ()
  #1  0x7232 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)
  (gdb) l
  1 .text
  2 .global _start
  3 _start:
  4 MOV R7, #4
  5 MOV R0, #1
  6 LDR R1, =hello
  7 LDR R2, =hello_size
  8 SWI 0
  9 MOV R7, #1
  10SWI 0
  (gdb) q
  A debugging session is active.

   Inferior 1 [process 29234] will be killed.

  Quit anyway? (y or n) y
  $
  ```

  It appears that gdb generally works and recognizes the executable, but
  breakpoints don't work. I'm new at Arm and don't have a lot of
  experience with assembly (at least not since the early 1970s), so it
  could easily be my problem but it seems suspiciously like an earlier
  problem and I think what I've done should work.

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

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

[Touch-packages] [Bug 1901026] Re: [GDB] No socket file connection support

[Luis]

What exactly are the regressions? I checked the logs and I don't really
know how to parse them. They don't seem to be GDB tests, but rather some
other components' tests.

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

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

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

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

[Touch-packages] [Bug 1901026] Re: [GDB] No socket file connection support

[Luis]

Nevermind. I double checked the package I was using, and turns out I
used an old package without the socket patch (the non-temporal sorting
of packages threw me off).

Testing this on x86-64, I can now see the following:

GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set debug remote 1
(gdb) tar rem /var/run/dbus/system_bus_socket
Remote debugging using /var/run/dbus/system_bus_socket
Sending packet: 
$qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;no-resumed+;xmlRegisters=i386#6a...Remote
 communication error.  Target disconnected.: Connection reset by peer.

As opposed to the previous error message. So this looks good! Thanks for
considering this backport.

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

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

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

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

[Touch-packages] [Bug 1901026] Re: [GDB] No socket file connection support

[Luis]

I gave this a try and, unfortunately, it didn't work right. It seems
there may be more patches require to make this work. I'm investigating
what those are.

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

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

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

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

[Touch-packages] [Bug 1901908] [NEW] [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem

[Luis Ramírez]

Public bug reported:

The volume keys of my keyboard not working since the last ubuntu update
release.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  lumantar   3208 F pulseaudio
 /dev/snd/controlC0:  lumantar   3208 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 28 10:01:27 2020
InstallationDate: Installed on 2018-09-14 (775 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Audio Interno - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
 oct 28 09:15:18 lumantar dbus-daemon[776]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.37' (uid=120 pid=1243 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
 oct 28 09:15:23 lumantar pulseaudio[1243]: No UCM verb is valid for hw:0
 oct 28 09:15:26 lumantar pulseaudio[1243]: No UCM verb is valid for hw:2
 oct 28 09:19:41 lumantar systemd[1199]: pulseaudio.service: Succeeded.
 oct 28 09:19:51 lumantar systemd[1199]: pulseaudio.socket: Succeeded.
Symptom_Type: Volume slider, or mixer problems
Title: [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem
UpgradeStatus: Upgraded to focal on 2020-10-21 (7 days ago)
dmi.bios.date: 04/20/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 9BCN31WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lancer 5A5
dmi.board.vendor: LENOVO
dmi.board.version: 31900059WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Z50-70
dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN31WW:bd04/20/2015:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
dmi.product.family: IDEAPAD
dmi.product.name: 20354
dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70
dmi.product.version: Lenovo Z50-70
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The volume keys of my keyboard not working since the last ubuntu
  update release.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lumantar   3208 F pulseaudio
   /dev/snd/controlC0:  lumantar   3208 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 28 10:01:27 2020
  InstallationDate: Installed on 2018-09-14 (775 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Audio Interno - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   oct 28 09:15:18 lumantar dbus-daemon[776]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.37' (uid=120 pid=1243 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   oct 28 09:15:23 lumantar pulseaudio[1243]: No UCM verb is valid for hw:0
   oct 28 09:15:26 lumantar pulseaudio[1243]: No UCM verb is valid for hw:2
   oct 28 09:19:41 lumantar systemd[1199]: pulseaudio.service: Succeeded.
   oct 28 09:19:51 lumantar systemd[1199]: pulseaudio.socket: Succeeded.
  Symptom_Type: Volume slider, or mixer problems
  Title: [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem
  UpgradeStatus: Upgraded to focal on 2020-10-21 (7 days ago)
  dmi.bios.date: 04/20/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900059WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 

[Touch-packages] [Bug 1901026] [NEW] [GDB] No socket file connection support

[Luis]

Public bug reported:

GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2) 8.1.0.20180409-git)
does not support connecting to a remote target via a socket file.

This is the error we get:

(gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
/run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB. It
would be nice to have it backported.

Here's the commit link: https://sourceware.org/git/?p=binutils-
gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

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

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

Title:
  [GDB] No socket file connection support

Status in gdb package in Ubuntu:
  New

Bug description:
  GDB on Ubuntu 18.04 (GNU gdb (Ubuntu 8.1-0ubuntu3.2)
  8.1.0.20180409-git) does not support connecting to a remote target via
  a socket file.

  This is the error we get:

  (gdb) target remote /run/user/1000/at-spi2-QTZBS0/socket
  /run/user/1000/at-spi2-QTZBS0/socket: No such device or address.

  Commit c1168a2f66553cd4730931cf59e3be8378a1a03f enables this in GDB.
  It would be nice to have it backported.

  Here's the commit link: https://sourceware.org/git/?p=binutils-
  gdb.git;a=commit;h=c1168a2f66553cd4730931cf59e3be8378a1a03f

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

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

[Touch-packages] [Bug 1888101] Re: 'unsupported protocol' error when using PyMySQL

[Luis Alfredo Contreras]

Hi, I had the same issue but I found a solution.

I was creating a docker container based on ubuntu 20.04 and Python3.8.2.
It installed openssl by default. The version from 2020-Mar-31 12:41:55
openssl-1.1.1f.tar.gz was giving me an this error: ssl.SSLError: [SSL:
UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:1108). After looking
for solutions, I found this link: https://cloudwafer.com/blog
/installing-openssl-on-ubuntu-16-04-18-04/. In that link, you can find
how to install openssl from the source. It shows you how to install the
version from 2019-May-28 13:26:28 openssl-1.1.1c.tar.gz. First I built
my container as originally and logged in and I followed the steps in the
link. It solved my problem. The latest version from March 2020 was
causing the issue.

I added the lines of code below when building the docker container to
automate the steps. See:

RUN apt install build-essential checkinstall zlib1g-dev -y
WORKDIR /usr/local/src/
RUN wget https://www.openssl.org/source/openssl-1.1.1c.tar.gz && tar -xf 
openssl-1.1.1c.tar.gz
WORKDIR openssl-1.1.1c
RUN ./config --prefix=/usr/local/ssl --openssldir=/usr/local/ssl shared zlib && 
make && make install
COPY ./openssl-1.1.1c.conf /etc/ld.so.conf.d/
RUN ldconfig -v && mv /usr/bin/c_rehash /usr/bin/c_rehash.backup && mv 
/usr/bin/openssl /usr/bin/openssl.backup
ENV 
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/ssl/bin"


* Note that I created the openssl-1.1.1c.conf file before building the 
container. The file is copied from the same directory where the dockerfile is 
saved. Create the file with that name and paste this inside: /usr/local/ssl/lib

I hope this helps.

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

Title:
  'unsupported protocol' error when using PyMySQL

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  1)
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2)
  openssl:
Installiert:   1.1.1f-1ubuntu2
Installationskandidat: 1.1.1f-1ubuntu2
Versionstabelle:
   *** 1.1.1f-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) + 4)
  I am trying to connect to my MariaDB with python package "PyMySQL" and SSL 
enabled. On my old installation (Kubuntu 19.10) this worked. With the new 
installation (also new PC: Xubuntu 20.04) I get this error message:

  ssl.SSLError: [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol
  (_ssl.c:1108)

  Here are my installation details:
  Old installation: python 3.7.5, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1c 
28 May 2019
  New installation: python 3.8.2, pymysql 0.9.3, ssl.OPENSSL_VERSION = 1.1.1f 
31 Mar 2020

  When I use python with a different SSL version...:
  this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.0m-dev xx XXX 
  this works: python 3.7.5, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX 
  this works: python 3.8.2, ssl.OPENSSL_VERSION = OpenSSL 1.1.1h-dev xx XXX 

  
  It seems, like the one specific version of openSSL (1.1.1f 31 Mar 2020) does 
not work together with PyMySQL.

  Some more details I have posted here:
  
https://stackoverflow.com/questions/62964998/unsupported-protocol-error-when-using-pymysql

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1f-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Jul 18 15:42:27 2020
  InstallationDate: Installed on 2020-07-13 (4 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Luis Alberto Pabón]

You can manually select the output to use from gnome-settings until the
fix lands.

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Luis Alvarado]

Confirmed, after adding the nvidia-drm.modeset=1 to the GRUB file it
worked. I tested 3 cases:

1. Reboot without Log out afterwards.
2. Reboot with a Log out afterwards and then try to log in again.
3. Reboot with a Log out afterwards, try to log in again and then reboot.

It worked for all cases. Of course this is still a workaround, but it
works for the time being.

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  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:

[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Luis Alvarado]

This is exactly what is happening to me. I installed Ubuntu 20.04 today
(The official released version, not beta), and if I set the auto login
on, it will give me the same issue the original poster said. You can't
login afterwards and if your logout, it enter a loop where you will
never come out from unless you purge gdm3 and install it back or other
workarounds that I can't guarantee work alone. I have an Nvidia GTX 1080
running on the Proprietary 440 Driver. My user is "luis" and the
password is "x" in case anyone would want to literally try it out with
the same user/pass/hardware combination.

If I disable the auto login then everything related to logout/login
works correctly.

The hardware is down below of an Asus Hero Alpha VII, Intel 6700k and 64
GB of RAM. The SSD is a Samsung 850 Pro 1TB.

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core 
Processor Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core 
Processor PCIe Controller (x16) (rev 07)
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family 
USB 3.0 xHCI Controller (rev 31)
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series 
Chipset Family MEI Controller #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 
Chipset SATA Controller [AHCI Mode] (rev 31)
00:1b.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI 
Express Root Port #17 (rev f1)
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI 
Express Root Port #1 (rev f1)
00:1c.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI 
Express Root Port #3 (rev f1)
00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI 
Express Root Port #5 (rev f1)
00:1c.7 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI 
Express Root Port #8 (rev f1)
00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI 
Express Root Port #9 (rev f1)
00:1d.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI 
Express Root Port #13 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Z170 Chipset LPC/eSPI Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset 
Family Power Management Controller (rev 31)
00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family 
HD Audio Controller (rev 31)
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus 
(rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V 
(rev 31)
01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] 
(rev a1)
01:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller 
(rev a1)
03:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine 
Ridge 4C 2015]
04:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine 
Ridge 4C 2015]
04:01.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine 
Ridge 4C 2015]
04:02.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine 
Ridge 4C 2015]
04:04.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine 
Ridge 4C 2015]
07:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine 
Ridge]
09:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network 
Adapter (rev 32)
0a:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller 
(rev 02)
0b:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10)

I will try the removing of splash and then adding nvidia-drm.modeset=1
to see how it goes.

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in throug

[Touch-packages] [Bug 1573720] Re: Unencrypted private keys are insecure error reported even when key is encrypted

[Luis Pose Gomez]

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Unencrypted private keys are insecure error reported even when key is
  encrypted

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  When I enter an EAP-TLS wifi config, I get the error:

  "Unencrypted private keys are insecure
  The selected private key does not appear to be protected by a password.  This 
could allow your security credentials to be compromised.  Please select a 
password-protected private key.

  (You can password-protect your private key with openssl)"

  I have verified that my key is, in fact, encrypted, and I have tried
  using both des3 and aes256. I have also verified the password used to
  encrypt the key.

  For a while, it wouldn't even let me save the config. I managed to
  save it eventually, but now when I try to connect to the saved
  connection, I get the same error.

  I am on Ubuntu mate 16.04

  network-manager 1.1.93

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  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
  CurrentDesktop: MATE
  Date: Fri Apr 22 13:25:16 2016
  InstallationDate: Installed on 2015-08-19 (246 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  IpRoute:
   default via 192.168.151.254 dev eth1  proto static  metric 100 
   169.254.0.0/16 dev eth1  scope link  metric 1000 
   192.168.151.0/24 dev eth1  proto kernel  scope link  src 192.168.151.95  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eth1ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  ed50d4f9-c810-4be0-b06c-8acd58015c50  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   eth0ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1573720/+subscriptions

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

[Touch-packages] [Bug 1623530] Re: Apport should be disabled by default

[Luis Alvarado]

Guys, this has created more issues to newcomers than anything else I
teach them. It should not be alerting the user EVERY TIME an app crashes
(which simply comes back up after a second). It apport needs to be
enabled to send or gather information it should ask ONCE during the
installation process if the user wants to sent the information without
being prompted every time an app crashes (and an option if they do want
to be prompted). This basically promotes a new comer to leave ubuntu
because they think the whole thing is broken. From a usability stand
point, it is still the worse idea ever when trying to promote the
system, The suggestions mentioned 12+ months ago have not being applied
nor a feedback (which would be welcomed) received. It is very
frustrating to explain to every new ubuntu user I teach or bring to use
ubuntu (which already tops 5000+ users) that they need to disable apport
to avoid the bug report popups.

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

Title:
  Apport should be disabled by default

Status in Apport:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I work with large communities (US, India, Latin America) and almost
  the number one issue they have with Ubuntu or simply scares them off
  is the fact that errors keep popping up every time. Some times
  multiples times per minutes, per hour, per day.

  The reason is how apport works by default. The "solution" is going to
  /etc/default/apport and setting the option to 0 (Disable). I do
  understand the full benefit or submitting automatically all bug
  reports, but this has gotten (And most Ubuntu users will be able to
  confirm) out of hand with some many popup questions about some bug or
  another that are simply fixed the moment the report is going to be
  send (eg: Compiz issue that was fixed a couple of milliseconds later,
  unity issue, dash issue, firefox issue, etc..). All of them have
  mechanism to handle failures and basically heal themselves.

  The question regarding this is:

  Leaving apport enable by default on an Ubuntu installation simply
  scares or annoys end users (a lot may I add). Leaving it disabled, it
  will not send a bug report, but there is no issue in simply creating
  an ubuntu-bug report through the terminal. So the sending of the
  report is still valid, but is not forced onto the user (And not forced
  so many times).

  This report is back by about 3 years going back and forth with the
  same apport issue and seeing probably around 500 users I have helped
  myself with the same issue, since this makes Ubuntu less productive to
  the actual user, even from start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 14 08:16:03 2016
  InstallationDate: Installed on 2016-04-22 (144 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273

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

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

[Touch-packages] [Bug 1385292] Re: can't rename files in nautilus

[Luis Fonseca]

Distro: Ubuntu 16.04.4 LTS xenial
GNOME nautilus 3.14.3

I have the same problem that I can not rename files and folders by pressing the 
F2 key.
I work on a laptop and I have connected an external keyboard (Microsoft Wired 
Keyboard 400 with number pad). I Identify that if the "Num Lock" key is active, 
the bug is executed, but if the "Num Lock" key is disabled the bug is no longer 
present.

** Attachment added: "Keyboard bloqnum"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1385292/+attachment/5234453/+files/keyboard.png

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

Title:
  can't rename files in nautilus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Triaged

Bug description:
  sometimes can't rename files with F2 button. It is higlight changing,
  but nothing gonna happen, it is not responding

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 24 17:48:33 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-10-24 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[Luis Perez]

Hi:

I'm also impacted by this bug.

[HD 4.50BTNC]# info
Device 00:16:94:32:40:CD (public)
Name: HD 4.50BTNC
Alias: HD 4.50BTNC
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: bluetooth:v0A12p0001d

When i select HSP/HFP as profile to use headset microphone, device
restarts and switches back again to A2DP profile.

There's any news about this bug?
Has anyone tried to apply any workarround?

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

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

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

[Touch-packages] [Bug 1800065] [NEW] package tzdata 2018f-0ubuntu0.18.10 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128

[Luis Antonio]

Public bug reported:

Al momento de actualizar aplicaciones desde el actualizador marca este
error y detiene la actualización.

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: tzdata 2018f-0ubuntu0.18.10
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
Date: Thu Oct 25 19:17:40 2018
DuplicateSignature:
 package:tzdata:2018f-0ubuntu0.18.10
 Setting up tzdata (2018f-0ubuntu0.18.10) ...
 Use of uninitialized value $ret in string eq at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134.
 dpkg: error processing package tzdata (--configure):
  installed tzdata package post-installation script subprocess returned error 
exit status 128
ErrorMessage: installed tzdata package post-installation script subprocess 
returned error exit status 128
InstallationDate: Installed on 2018-10-25 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.0
SourcePackage: tzdata
Title: package tzdata 2018f-0ubuntu0.18.10 failed to install/upgrade: installed 
tzdata package post-installation script subprocess returned error exit status 
128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package cosmic

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

Title:
  package tzdata 2018f-0ubuntu0.18.10 failed to install/upgrade:
  installed tzdata package post-installation script subprocess returned
  error exit status 128

Status in tzdata package in Ubuntu:
  New

Bug description:
  Al momento de actualizar aplicaciones desde el actualizador marca este
  error y detiene la actualización.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: tzdata 2018f-0ubuntu0.18.10
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Thu Oct 25 19:17:40 2018
  DuplicateSignature:
   package:tzdata:2018f-0ubuntu0.18.10
   Setting up tzdata (2018f-0ubuntu0.18.10) ...
   Use of uninitialized value $ret in string eq at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134.
   dpkg: error processing package tzdata (--configure):
installed tzdata package post-installation script subprocess returned error 
exit status 128
  ErrorMessage: installed tzdata package post-installation script subprocess 
returned error exit status 128
  InstallationDate: Installed on 2018-10-25 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: tzdata
  Title: package tzdata 2018f-0ubuntu0.18.10 failed to install/upgrade: 
installed tzdata package post-installation script subprocess returned error 
exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1787025] [NEW] package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

[Alexandre Luis Sbaraini]

Public bug reported:

Ocorreu na instalação

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Aug 14 11:19:54 2018
ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
InstallationDate: Installed on 2013-12-03 (1715 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: systemd
Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago)

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


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

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

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Ocorreu na instalação

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Aug 14 11:19:54 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-12-03 (1715 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago)

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

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

[Touch-packages] [Bug 1787024] [NEW] package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Alexandre Luis Sbaraini]

Public bug reported:

Problem in instalation

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: dbus 1.12.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Aug 14 08:33:35 2018
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2013-12-03 (1715 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: dbus
Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers
  looping, abandoned

Status in dbus package in Ubuntu:
  New

Bug description:
  Problem in instalation

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: dbus 1.12.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Aug 14 08:33:35 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2013-12-03 (1715 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: dbus
  Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago)

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

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

[Touch-packages] [Bug 1785273] [NEW] Problem installing Intel drivers

[Luis De Armas]

Public bug reported:

I'm trying to install intel drivers in ubuntu and and that error shows
up

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Aug  3 16:40:50 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07e1]
   Subsystem: Dell Device [1028:07e1]
InstallationDate: Installed on 2018-08-03 (0 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
MachineType: Dell Inc. Inspiron 5577
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=e78f51c6-fb02-4b78-b42a-e180057b2edc ro nomodeset vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.9
dmi.board.name: 090HMC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd01/25/2018:svnDellInc.:pnInspiron5577:pvr1.0.9:rvnDellInc.:rn090HMC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5577
dmi.product.version: 1.0.9
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
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
xserver.bootTime: Fri Aug  3 16:33:27 2018
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4~16.04.1

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  Problem installing Intel drivers

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm trying to install intel drivers in ubuntu and and that error shows
  up

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Aug  3 16:40:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07e1]
 Subsystem: Dell Device [1028:07e1]
  InstallationDate: Installed on 2018-08-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: Dell Inc. Inspiron 5577
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=e78f51c6-fb02-4b78-b42a-e180057b2edc ro nomodeset vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.9
  dmi.board.name: 090HMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 

[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

[Luis Alberto Pabón]

Indeed disabling sysrq seems to fix the problem, but this has worked for
donkey's ages so what exactly changed?

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

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in systemd package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  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.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1774055] [NEW] package python-dbg 2.7.12-1~16.04 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[JOSE LUIS SANCHEZ SANCHEZ]

Public bug reported:

No further information.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-dbg 2.7.12-1~16.04
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
Date: Tue May 29 17:10:35 2018
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2016-10-13 (592 days ago)
InstallationMedia: Bio‑Linux 8 based on Ubuntu 14.04 LTS "Trusty Tahr" - 
Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: python-defaults
Title: package python-dbg 2.7.12-1~16.04 failed to install/upgrade: problemas 
de dependencias - se deja sin configurar
UpgradeStatus: Upgraded to xenial on 2017-07-16 (317 days ago)

** Affects: python-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package python-dbg 2.7.12-1~16.04 failed to install/upgrade: problemas
  de dependencias - se deja sin configurar

Status in python-defaults package in Ubuntu:
  New

Bug description:
  No further information.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-dbg 2.7.12-1~16.04
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Tue May 29 17:10:35 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2016-10-13 (592 days ago)
  InstallationMedia: Bio‑Linux 8 based on Ubuntu 14.04 LTS "Trusty Tahr" - 
Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: python-defaults
  Title: package python-dbg 2.7.12-1~16.04 failed to install/upgrade: problemas 
de dependencias - se deja sin configurar
  UpgradeStatus: Upgraded to xenial on 2017-07-16 (317 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1774055/+subscriptions

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

[Touch-packages] [Bug 1772025] [NEW] package libssl1.1 1.1.0g-2ubuntu4 failed to install/upgrade: no package named 'libssl1.1' is installed, cannot configure

[Yunior Luis]

Public bug reported:

When upgrading from 17.10 to 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libssl1.1 1.1.0g-2ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri May 18 14:22:48 2018
DuplicateSignature:
 package:libssl1.1:1.1.0g-2ubuntu4
 Unpacking python3-minimal (3.6.5-3) over (3.6.3-0ubuntu2) ...
 dpkg: error processing package libssl1.1 (--configure):
  no package named 'libssl1.1' is installed, cannot configure
ErrorMessage: no package named 'libssl1.1' is installed, cannot configure
InstallationDate: Installed on 2017-04-07 (405 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: openssl
Title: package libssl1.1 1.1.0g-2ubuntu4 failed to install/upgrade: no package 
named 'libssl1.1' is installed, cannot configure
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libssl1.1 1.1.0g-2ubuntu4 failed to install/upgrade: no
  package named 'libssl1.1' is installed, cannot configure

Status in openssl package in Ubuntu:
  New

Bug description:
  When upgrading from 17.10 to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libssl1.1 1.1.0g-2ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 18 14:22:48 2018
  DuplicateSignature:
   package:libssl1.1:1.1.0g-2ubuntu4
   Unpacking python3-minimal (3.6.5-3) over (3.6.3-0ubuntu2) ...
   dpkg: error processing package libssl1.1 (--configure):
no package named 'libssl1.1' is installed, cannot configure
  ErrorMessage: no package named 'libssl1.1' is installed, cannot configure
  InstallationDate: Installed on 2017-04-07 (405 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: openssl
  Title: package libssl1.1 1.1.0g-2ubuntu4 failed to install/upgrade: no 
package named 'libssl1.1' is installed, cannot configure
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1756721] [NEW] package libsmartcols1 2.30.1-0ubuntu4.1 failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2

[Luis Arias]

Public bug reported:

bug

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsmartcols1 2.30.1-0ubuntu4.1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Sun Mar 18 19:29:33 2018
Dependencies:
 gcc-7-base 7.2.0-8ubuntu3.2
 libc6 2.26-0ubuntu2.1
 libgcc1 1:7.2.0-8ubuntu3.2
DpkgTerminalLog:
 Preparando para desempaquetar .../libsmartcols1_2.30.1-0ubuntu4.1_amd64.deb ...
 Desempaquetando libsmartcols1:amd64 (2.30.1-0ubuntu4.1) sobre 
(2.30.1-0ubuntu4) ...
 dpkg-deb: error: fallo al leer el archivo 
`/var/cache/apt/archives/libsmartcols1_2.30.1-0ubuntu4.1_amd64.deb': No existe 
el archivo o el directorio
 dpkg: error al procesar el archivo 
/var/cache/apt/archives/libsmartcols1_2.30.1-0ubuntu4.1_amd64.deb (--unpack):
  el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2
ErrorMessage: el subproceso dpkg-deb --fsys-tarfile devolvió el código de 
salida de error 2
InstallationDate: Installed on 2017-12-09 (98 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: util-linux
Title: package libsmartcols1 2.30.1-0ubuntu4.1 failed to install/upgrade: el 
subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package libsmartcols1 2.30.1-0ubuntu4.1 failed to install/upgrade: el
  subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de
  error 2

Status in util-linux package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsmartcols1 2.30.1-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Mar 18 19:29:33 2018
  Dependencies:
   gcc-7-base 7.2.0-8ubuntu3.2
   libc6 2.26-0ubuntu2.1
   libgcc1 1:7.2.0-8ubuntu3.2
  DpkgTerminalLog:
   Preparando para desempaquetar .../libsmartcols1_2.30.1-0ubuntu4.1_amd64.deb 
...
   Desempaquetando libsmartcols1:amd64 (2.30.1-0ubuntu4.1) sobre 
(2.30.1-0ubuntu4) ...
   dpkg-deb: error: fallo al leer el archivo 
`/var/cache/apt/archives/libsmartcols1_2.30.1-0ubuntu4.1_amd64.deb': No existe 
el archivo o el directorio
   dpkg: error al procesar el archivo 
/var/cache/apt/archives/libsmartcols1_2.30.1-0ubuntu4.1_amd64.deb (--unpack):
el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 
2
  ErrorMessage: el subproceso dpkg-deb --fsys-tarfile devolvió el código de 
salida de error 2
  InstallationDate: Installed on 2017-12-09 (98 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: util-linux
  Title: package libsmartcols1 2.30.1-0ubuntu4.1 failed to install/upgrade: el 
subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1722708] Re: Crash when setting laptop display resolution

[Luis Alberto Pabón]

I have the same problem. I can set my laptop display to FHD down from 4K to 
match my external monitor, but as soon as I click on "scale 100%" button the 
apply button disappears and I get 
"Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: 
Logical monitor scales must be identical" on the console.

A workaround that works in the meantime is to use arandr, arrange your
screens, and apply any changes - this will reset scale back to 1 and
gnome display control panel works again. Arandr bottom snap can make
both displays overlap, bear that in mind if you get the gnome panel
repeated.

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

Title:
  Crash when setting laptop display resolution

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  This system has a 4k laptop screen with resolution 3840x2160, and an
  external HP monitor connected via HDMI, resolution 1920x1200. Windows,
  fonts etc are not scaled properly on the external monitor (too large,
  etc), and the only workaround I've found with earlier versions and
  other distros is to set the laptop display to 1920x1080 mode, so
  that's what I'm trying here as well.

  However, when doing that, the X (wayland, not sure if the package is
  correct here) session crashes and brings me back to login screen.

  So to summarize: connect the external monitor, go to Settings >
  Devices > Displays, click primary built in display, observe that it
  shows Resolution 3840x2160 (16:9) and Scale 200%, change resolution to
  1920x1080 (16:9), click Apply --> crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 07:49:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:2248]
 Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:2248]
  InstallationDate: Installed on 2017-10-10 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171008)
  MachineType: LENOVO 20H9004MMX
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=182b5236-fa96-4fb5-bea9-f90769b65f3c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1VET35W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20H9004MMX
  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:bvrN1VET35W(1.25):bd09/06/2017:svnLENOVO:pn20H9004MMX:pvrThinkPadT570:rvnLENOVO:rn20H9004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T570
  dmi.product.name: 20H9004MMX
  dmi.product.version: ThinkPad T570
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1747487] [NEW] Sonido

[luis Rodriguez]

Public bug reported:

No me reproduce sonido

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Feb  5 12:24:37 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0767]
InstallationDate: Installed on 2018-01-14 (21 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Inspiron 5567
ProcEnviron:
 LANGUAGE=es_CR:es
 PATH=(custom, no user)
 LANG=es_CR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed 
root=UUID=6c7bacd6-3cb7-45a1-aae6-01b254d6be95 ro splash quiet
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.9
dmi.board.name: 01W6F7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: Inspiron 5567
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Feb  5 12:20:03 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1317 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  Sonido

Status in xorg package in Ubuntu:
  New

Bug description:
  No me reproduce sonido

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Feb  5 12:24:37 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0767]
  InstallationDate: Installed on 2018-01-14 (21 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 5567
  ProcEnviron:
   LANGUAGE=es_CR:es
   PATH=(custom, no user)
   LANG=es_CR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed 
root=UUID=6c7bacd6-3cb7-45a1-aae6-01b254d6be95 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.9
  dmi.board.name: 01W6F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: 

[Touch-packages] [Bug 1747238] [NEW] package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[Jorge Luis]

Public bug reported:

See summary above

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Sat Jan 27 06:26:12 2018
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2017-07-06 (212 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: qtbase-opensource-src
Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

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

Bug description:
  See summary above

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sat Jan 27 06:26:12 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2017-07-06 (212 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: qtbase-opensource-src
  Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1747238/+subscriptions

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

[Touch-packages] [Bug 1747220] [NEW] unsatisfied dependencies installing libjack-jackd2-dev

[Juan Luis]

Public bug reported:

I have a broken package message in Ubuntu 17.10  when trying to install
libjack-jackd2-dev:

(text from console translated from spanish):

The following packages has broken links:
 libjack-jackd2-dev : Depends: libjack-jackd2-0 (= 
1.9.10+20150825git1ed50c92~dfsg-5ubuntu1) but 2:1.9.12-1~zzartful2 is going to 
be installed
E: Fatal errors couldn't be repaired, broken packages retained.

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

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

Title:
  unsatisfied dependencies installing libjack-jackd2-dev

Status in jackd2 package in Ubuntu:
  New

Bug description:
  I have a broken package message in Ubuntu 17.10  when trying to
  install libjack-jackd2-dev:

  (text from console translated from spanish):

  The following packages has broken links:
   libjack-jackd2-dev : Depends: libjack-jackd2-0 (= 
1.9.10+20150825git1ed50c92~dfsg-5ubuntu1) but 2:1.9.12-1~zzartful2 is going to 
be installed
  E: Fatal errors couldn't be repaired, broken packages retained.

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

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

[Touch-packages] [Bug 1733557] Re: Login screen showing Authentication Failed Switch to greeter...

[Luis Alberto Pabón]

I'm seeing this also upon 17.10 upgrade in unity / lightdm / unity
greeter.

It doesn't happen 100% of the time, typically takes some time time to
manifest (I only ever suspend my laptop from monday to friday), but once
it starts happening, it always happens until I shut down.

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

Title:
  Login screen showing Authentication Failed Switch to greeter...

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When I lock my machine, the login screen shows my current user with
  the message: "Authentication Failed"

  ..and in the position when the password normally exists, the option
  "Switch to greeter..."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  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.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Nov 21 10:28:47 2017
  InstallationDate: Installed on 2017-04-17 (217 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-10-23 (29 days ago)

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

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

[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

[Luis Alvarado]

Hi Daniel, thank you. How can I mark this ticket as fixed. It has been
about 10 days. No problems whatsoever. I actually lost connection
yesterday but then noticed it was because I did not charge the headset
for the last 2 days. Even with very low power, I was still able to
finish a conversation. Thank you for the help and if you would like as a
gift, I could buy one of this in Amazon and send it to you buddy. They
are pretty awesome. Big hugs friend and think positive.

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

Title:
  Logitech G930 drops connection and reconnects in 17.10 (But not in
  17.04)

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Every so many seconds / minutes the Wireless headset Logitech G930
  simply drops connection. It always reconnects but when doing a
  recording, a meeting, listening to music or a movie it simply drops
  the connection for 1 to 3 second. This happens several times an hour.
  If it helps, it was not happening in 17.04 (Never happened in more
  than 200+ hours of using the headset).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cyrex  1288 F pulseaudio
   /dev/snd/controlC2:  cyrex  1288 F pulseaudio
   /dev/snd/controlC0:  cyrex  1288 F pulseaudio
  Date: Sat Oct 21 17:55:42 2017
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1743697] [NEW] package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[Jorge Luis]

Public bug reported:

Ok That is

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Wed Jan 17 06:58:36 2018
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2017-07-06 (194 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: qtbase-opensource-src
Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

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

Bug description:
  Ok That is

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Wed Jan 17 06:58:36 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2017-07-06 (194 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: qtbase-opensource-src
  Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1743697/+subscriptions

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

[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

[Luis Alberto Pabón]

This workaround works for me, but years of muscle memory...

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

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in systemd package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  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.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1725865] Re: Network shows Cable Unplugged

[Luis Alvarado]

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

Title:
  Network shows Cable Unplugged

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  This was working perfectly on 17.04, but after installing 17.10 from
  scratch, the wired network is not detected. It simply shows as Cable
  Unplugged when in fact there is the same cable still connected
  directly to the router. This same computer has Windows 10 and it
  detects the network correctly. I also tested Fedora and it detected
  the network correctly (The wired one). I am currently using only the
  Wireless connection because of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 21 17:59:31 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.1.1 dev wlp9s0 proto static metric 600 
   169.254.0.0/16 dev wlp9s0 scope link metric 1000 
   192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   wlp9s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Linux   ecb8e125-48ff-4994-94c8-bdf3731334ce  
/org/freedesktop/NetworkManager/ActiveConnection/13 
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
  
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1725865/+subscriptions

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

[Touch-packages] [Bug 1725410] Re: Intel Integrated Card not working Asus Hero Alpha VIII

[Luis Alvarado]

It was a hardware issue with the motherboard.

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

Title:
  Intel Integrated Card not working Asus Hero Alpha VIII

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  After upgrading to the latest Kernel, the issue appeared. Basically it
  always says there is no cable detected and the LAN (Wired) connection
  never works. Only wireless. If I go back to a previous Ubuntu version
  it works, but after either 4.12 or 4.13 the issue appeared. I also
  checked the BIOS version and it works only if I stay with a previous
  Ubuntu version.

  The device that is having an issue is:

  description: Ethernet interface
 product: Ethernet Connection (2) I219-V
 vendor: Intel Corporation
 physical id: 1f.6
 bus info: pci@:00:1f.6
 logical name: enp0s31f6
 version: 31
 serial: 34:97:f6:36:cb:d6
 capacity: 1Gbit/s
 width: 32 bits
 clock: 33MHz
 capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=3.2.6-k firmware=0.7-4 latency=0 link=no multicast=yes 
port=twisted pair
 resources: irq:132 memory:df70-df71



  00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet
  Connection (2) I219-V [8086:15b8] (rev 31)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 20 11:59:57 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.1.1 dev wlp9s0 proto static metric 600 
   169.254.0.0/16 dev wlp9s0 scope link metric 1000 
   192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.13 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME   UUID  TYPE TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
   Linux  74b235bc-acdd-4fc3-a028-d960c890fbe0  802-11-wireless  1508522270  
Fri 20 Oct 2017 11:57:50 AM CST  yes  0 no
/org/freedesktop/NetworkManager/Settings/2  yes wlp9s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
   Intel  ce6b4984-a66e-306e-9a98-9487e5b3c553  802-3-ethernet   1508435911  
Thu 19 Oct 2017 11:58:31 AM CST  yes  4294966297no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
   --
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp9s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Linux   74b235bc-acdd-4fc3-a028-d960c890fbe0  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1725410/+subscriptions

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

[Touch-packages] [Bug 1725865] Re: Network shows Cable Unplugged

[Luis Alvarado]

Hi Sebastien, I have added the corresponding bug here
https://bugzilla.gnome.org/show_bug.cgi?id=792506

Is this what it was needed buddy?

** Bug watch added: GNOME Bug Tracker #792506
   https://bugzilla.gnome.org/show_bug.cgi?id=792506

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

Title:
  Network shows Cable Unplugged

Status in network-manager package in Ubuntu:
  New

Bug description:
  This was working perfectly on 17.04, but after installing 17.10 from
  scratch, the wired network is not detected. It simply shows as Cable
  Unplugged when in fact there is the same cable still connected
  directly to the router. This same computer has Windows 10 and it
  detects the network correctly. I also tested Fedora and it detected
  the network correctly (The wired one). I am currently using only the
  Wireless connection because of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 21 17:59:31 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.1.1 dev wlp9s0 proto static metric 600 
   169.254.0.0/16 dev wlp9s0 scope link metric 1000 
   192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   wlp9s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Linux   ecb8e125-48ff-4994-94c8-bdf3731334ce  
/org/freedesktop/NetworkManager/ActiveConnection/13 
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
  
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1725865/+subscriptions

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

[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

[Luis Alvarado]

Hi Daniel, today I was able to start testing because there was an issue
with the Nvidia driver once going to the 4.15 kernel version. So today I
received the Intel microcode updates + Nvidia 390 which is compatible
with 4.15 so after seeing that, I installed the 4.17 RC7 as you
proposed.

I have to say, it is working correctly "for now". I would like to do a
longer test if that is possible with you. For example a 100 hour test,
which means that since I use this about 5 hours a day for client
meetings, and about 2 hours for gaming, it would be around 2 weeks of
test so I can let you know with a final result what the outcome is.

For now, I have not had the following errors:

1. Audio cutting in and out
2. No kernel or dmesg errors of any type. It actually showed like this when 
connnecting the dongle.

[   18.167592] logitech-hidpp-device 0003:046D:4069.000A: HID++ 4.5 device 
connected.
[  117.024265] usb 1-3: new full-speed USB device number 8 using xhci_hcd
[  117.740563] usb 1-3: New USB device found, idVendor=046d, idProduct=0a1f
[  117.740569] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  117.740572] usb 1-3: Product: Logitech G930 Headset
[  117.740574] usb 1-3: Manufacturer: Logitech
[  117.759570] input: Logitech Logitech G930 Headset as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:046D:0A1F.000C/input/input24
[  117.816837] hid-generic 0003:046D:0A1F.000C: input,hiddev2,hidraw7: USB HID 
v1.01 Device [Logitech Logitech G930 Headset] on usb-:00:14.0-3/input3

So everything looking smooth so far for the past hour. Give me if
possible till the end of a 2 week test to confirm everything.

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

Title:
  Logitech G930 drops connection and reconnects in 17.10 (But not in
  17.04)

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Every so many seconds / minutes the Wireless headset Logitech G930
  simply drops connection. It always reconnects but when doing a
  recording, a meeting, listening to music or a movie it simply drops
  the connection for 1 to 3 second. This happens several times an hour.
  If it helps, it was not happening in 17.04 (Never happened in more
  than 200+ hours of using the headset).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cyrex  1288 F pulseaudio
   /dev/snd/controlC2:  cyrex  1288 F pulseaudio
   /dev/snd/controlC0:  cyrex  1288 F pulseaudio
  Date: Sat Oct 21 17:55:42 2017
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

[Luis Alvarado]

Happy new year Daniel. No worries buddy, I fully understand. I will
follow your guidelines and report back. In regards to the questions:

1. It worked for some time (I think 1 to 2 weeks which was about 30
minutes to maybe an hour if I can recall). It was on 17.10 that I did
heavy test on it. Then I moved to 16.04 and it was still there. Then I
noticed it was in all of the ones tested (Except for 18.04 which I will
test right now).

2. Will test right away per your advice.

3. Will let you know once tested.

Big hugs friend.

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

Title:
  Logitech G930 drops connection and reconnects in 17.10 (But not in
  17.04)

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Every so many seconds / minutes the Wireless headset Logitech G930
  simply drops connection. It always reconnects but when doing a
  recording, a meeting, listening to music or a movie it simply drops
  the connection for 1 to 3 second. This happens several times an hour.
  If it helps, it was not happening in 17.04 (Never happened in more
  than 200+ hours of using the headset).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cyrex  1288 F pulseaudio
   /dev/snd/controlC2:  cyrex  1288 F pulseaudio
   /dev/snd/controlC0:  cyrex  1288 F pulseaudio
  Date: Sat Oct 21 17:55:42 2017
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

[Luis Alvarado]

Hi Daniel, wanted to share my findings for the last weeks. So I tested
16.04,16.10,17.04 and 17.10. The issue is now showing on all versions.
In 17.04 I remember not seeing the issue although I might not have
enough testing as am doing right now. Previously I used it for about 5
to 20 minutes in 17.04 compared to 4 to 6 hours in 17.10 and 16.04 when
I tested. So it's giving the same error on all 4. What do you recommend
I do now to follow up with you. Merry Christmas buddy.

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

Title:
  Logitech G930 drops connection and reconnects in 17.10 (But not in
  17.04)

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Every so many seconds / minutes the Wireless headset Logitech G930
  simply drops connection. It always reconnects but when doing a
  recording, a meeting, listening to music or a movie it simply drops
  the connection for 1 to 3 second. This happens several times an hour.
  If it helps, it was not happening in 17.04 (Never happened in more
  than 200+ hours of using the headset).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cyrex  1288 F pulseaudio
   /dev/snd/controlC2:  cyrex  1288 F pulseaudio
   /dev/snd/controlC0:  cyrex  1288 F pulseaudio
  Date: Sat Oct 21 17:55:42 2017
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1733062] [NEW] package libqt5network5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti

[Jorge Luis]

Public bug reported:

A message issued while updating system

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqt5network5:i386 5.5.1+dfsg-16ubuntu7.5
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic i686
ApportVersion: 2.20.1-0ubuntu2.12
Architecture: i386
Date: Mon Nov 13 21:34:31 2017
DuplicateSignature:
 package:libqt5network5:i386:5.5.1+dfsg-16ubuntu7.5
 Setting up perl-base (5.22.1-9ubuntu0.2) ...
 dpkg: error processing package libqt5network5:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-07-06 (134 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: qtbase-opensource-src
Title: package libqt5network5:i386 5.5.1+dfsg-16ubuntu7.5 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libqt5network5:i386 5.5.1+dfsg-16ubuntu7.5 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

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

Bug description:
  A message issued while updating system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt5network5:i386 5.5.1+dfsg-16ubuntu7.5
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic i686
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: i386
  Date: Mon Nov 13 21:34:31 2017
  DuplicateSignature:
   package:libqt5network5:i386:5.5.1+dfsg-16ubuntu7.5
   Setting up perl-base (5.22.1-9ubuntu0.2) ...
   dpkg: error processing package libqt5network5:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-07-06 (134 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: qtbase-opensource-src
  Title: package libqt5network5:i386 5.5.1+dfsg-16ubuntu7.5 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1733062/+subscriptions

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

[Touch-packages] [Bug 911981] Re: tracker-store uses 100% cpu and fills all the disk space in home partition

[Luis Andrés Gonzalez]

In my case, as a workaround execting

cpulimit -l 20 -p 

Helped in reducing the process CPU usage to 20%.

Please, let me know if this is an unefficient way to do it.

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

Title:
  tracker-store uses 100% cpu and fills all the disk space in home
  partition

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  I recently noticed that several tracker related programs were using
  100% cpu on my system and in particular tracker-store filled up
  completely all the available disk space in my home partition.

  I rerun tracker-preferences to make sure that indexing would not
  proceed if less than 20% of free space is available, but it seems that
  tracker-store ignores it.  After I noticed that I had left only 44Kb
  free on the home partition,  I deleted the cache from another program
  and I noticed that tracker-store filled up again the disk space that I
  freed few minutes before.

  This is the content of my .cache/tracker/ directory:
  totale 772068
  -rw-r--r-- 1 eclipse eclipse  3072 2011-06-26 22:56 contents.db
  -rw-r--r-- 1 eclipse eclipse11 2012-01-04 21:24 db-locale.txt
  -rw-r--r-- 1 eclipse eclipse 2 2011-12-12 04:02 db-version.txt
  -rw-r--r-- 1 eclipse eclipse  3072 2010-12-05 21:29 email-contents.db
  -rw-r--r-- 1 eclipse eclipse  3072 2009-05-06 19:16 email-fulltext.db
  -rw-r--r-- 1 eclipse eclipse   2359292 2011-06-26 22:54 email-index.db
  -rw-r--r-- 1 eclipse eclipse 34816 2010-12-05 21:29 email-meta.db
  -rw-r--r-- 1 eclipse eclipse  17062912 2011-06-26 19:30 file-contents.db
  -rw-r--r-- 1 eclipse eclipse  15014912 2010-01-12 20:26 file-fulltext.db
  -rw-r--r-- 1 eclipse eclipse  75609207 2011-06-26 22:54 file-index.db
  -rw-r--r-- 1 eclipse eclipse  37027840 2011-06-26 19:31 file-meta.db
  -rw--- 1 eclipse eclipse   1180048 2009-05-05 22:57 file-update-index.db
  -rw-r--r-- 1 eclipse eclipse  28376064 2011-10-20 09:34 fulltext.db
  -rw-r--r-- 1 eclipse eclipse  1024 2012-01-04 21:24 meta.db
  -rw-r--r-- 1 eclipse eclipse   4653056 2012-01-04 21:26 meta.db-shm
  -rw-r--r-- 1 eclipse eclipse 608064304 2012-01-04 21:26 meta.db-wal
  -rw-r--r-- 1 eclipse eclipse11 2011-12-12 04:02 
miner-applications-locale.txt
  -rw-r--r-- 1 eclipse eclipse345110 2012-01-04 21:24 ontologies.gvdb

  and this is  how much space I have left on my home partition after I KILLED 
the tracker-store process:
  /dev/sda8  31G   30G  418M  99% /home
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  Package: tracker 0.10.24-1build2
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=it_IT:it:en_GB:en
   PATH=(custom, user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric
  Uname: Linux 3.0.0-14-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-20 (76 days ago)
  UserGroups: adm admin audio cdrom dip fuse lpadmin plugdev polkituser 
pulse-access sambashare src video

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

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

[Touch-packages] [Bug 1623530] Re: Apport should be disabled by default

[Luis Alvarado]

Just updating that in 17.04 and 17.10 it still shows, some times
multiple times for the same issue. The opt-in option is better suited
for end users and if a developer wants it enabled they can simply edit
the apport file. But again, a year later and 2 versions later, a simple
opt-in approach (that would actually help so many users I have talk to)
would be the way to go. Anything else like telling the user to install
something or thinking for the developer first (and forgetting the whole
idea is to make a user friendly desktop system) is so wrong.

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

Title:
  Apport should be disabled by default

Status in Apport:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I work with large communities (US, India, Latin America) and almost
  the number one issue they have with Ubuntu or simply scares them off
  is the fact that errors keep popping up every time. Some times
  multiples times per minutes, per hour, per day.

  The reason is how apport works by default. The "solution" is going to
  /etc/default/apport and setting the option to 0 (Disable). I do
  understand the full benefit or submitting automatically all bug
  reports, but this has gotten (And most Ubuntu users will be able to
  confirm) out of hand with some many popup questions about some bug or
  another that are simply fixed the moment the report is going to be
  send (eg: Compiz issue that was fixed a couple of milliseconds later,
  unity issue, dash issue, firefox issue, etc..). All of them have
  mechanism to handle failures and basically heal themselves.

  The question regarding this is:

  Leaving apport enable by default on an Ubuntu installation simply
  scares or annoys end users (a lot may I add). Leaving it disabled, it
  will not send a bug report, but there is no issue in simply creating
  an ubuntu-bug report through the terminal. So the sending of the
  report is still valid, but is not forced onto the user (And not forced
  so many times).

  This report is back by about 3 years going back and forth with the
  same apport issue and seeing probably around 500 users I have helped
  myself with the same issue, since this makes Ubuntu less productive to
  the actual user, even from start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 14 08:16:03 2016
  InstallationDate: Installed on 2016-04-22 (144 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273

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

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

[Touch-packages] [Bug 1728326] [NEW] package python-apt 0.9.3.5ubuntu2 failed to install/upgrade: dependency problems - leaving unconfigured

[Luis Fernando Lara]

Public bug reported:

me sale error en el sistemas y me da muchos problemas

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python-apt 0.9.3.5ubuntu2
Uname: Linux 3.13.0-133-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Sat Oct 28 18:20:15 2017
ErrorMessage: dependency problems - leaving unconfigured
InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 
20120718-04:29
LiveMediaBuild: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 20120718-04:29
SourcePackage: python-apt
Title: package python-apt 0.9.3.5ubuntu2 failed to install/upgrade: dependency 
problems - leaving unconfigured

** Affects: python-apt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386

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

Title:
  package python-apt 0.9.3.5ubuntu2 failed to install/upgrade:
  dependency problems - leaving unconfigured

Status in python-apt package in Ubuntu:
  New

Bug description:
  me sale error en el sistemas y me da muchos problemas

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-apt 0.9.3.5ubuntu2
  Uname: Linux 3.13.0-133-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Sat Oct 28 18:20:15 2017
  ErrorMessage: dependency problems - leaving unconfigured
  InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 
20120718-04:29
  LiveMediaBuild: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 20120718-04:29
  SourcePackage: python-apt
  Title: package python-apt 0.9.3.5ubuntu2 failed to install/upgrade: 
dependency problems - leaving unconfigured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1728326/+subscriptions

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

[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

[Luis Alvarado]

Hi Daniel, thank you for helping out. I can report that the issues are
back today (After 2 days of working). This time is crazy, it breaks more
often. I had to reinstall the whole 17.10 and of course it happens but
less often (Like the original bug report).

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

Title:
  Logitech G930 drops connection and reconnects in 17.10 (But not in
  17.04)

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

Bug description:
  Every so many seconds / minutes the Wireless headset Logitech G930
  simply drops connection. It always reconnects but when doing a
  recording, a meeting, listening to music or a movie it simply drops
  the connection for 1 to 3 second. This happens several times an hour.
  If it helps, it was not happening in 17.04 (Never happened in more
  than 200+ hours of using the headset).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cyrex  1288 F pulseaudio
   /dev/snd/controlC2:  cyrex  1288 F pulseaudio
   /dev/snd/controlC0:  cyrex  1288 F pulseaudio
  Date: Sat Oct 21 17:55:42 2017
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

[Luis Alvarado]

OK so instead of using a new or old kernel and to avoid issues with
other drivers (like Nvidia breaking with the 4.14 RC version) and based
on your feedback, I only then focused on PulseAudio. I noted that Ubuntu
17.10 is using the PulseAudio from January which is 10.0 instead of the
11.1 from September. So I grabbed the 11.1 one, downloaded the needed
dependencies and compiled the whole thing like this:


1. Make sure the Source repository is enabled since it comes disabled by 
default from the Software & Updates App.

2. Install all dependencies needed

sudo apt-get build-dep pulseaudio && sudo apt-get install checkinstall
git libpulse-dev

3. Set all the flags and settings

CFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Wformat-security -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Wformat-security -Werror=format-security -Wall"

CXXFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Wformat-security -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Wformat-security -Werror=format-security -Wall"

CPPFLAGS="-D_FORTIFY_SOURCE=2"

LDFLAGS="-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--no-as-needed -lxcb"

./configure --build=x86_64-linux-gnu  --prefix=/usr
--includedir="\${prefix}/include" --mandir="\${prefix}/share/man"
--infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var
--libexecdir="\${prefix}/lib/pulseaudio" --srcdir=. --disable-
maintainer-mode --disable-dependency-tracking --disable-silent-rules
--enable-x11 --disable-hal --libdir=\${prefix}/lib/x86_64-linux-gnu
--with-module-dir=\${prefix}/lib/pulse-11.1/modules --disable-oss-
wrapper

NOTE: The above is based on PulseAudio 11.1 so if you look at the final
line it says pulse-11.1 just to help with knowing which version is
handled.

After this a simple

make -j8 (In my case)

Then

sudo make install

then reboot or kill pulseaudio. After that I have tested during the past
3 hours and have had no issues whatsoever. This solved a crackling
issues that happened every 3-5 minutes. The disconnecting and
reconnecting issues that in 3 hours would have happened about 30 times
or more. A sound issue in calls, even other members hearing me can hear
me better and no crackling sound in the back. And while testing with
steam and youtube, there was no drop in sound.

For now this is a better solution but if other bugs appear in regards to
sound issues, most probably updating to 11.1 (The whole 11.x versions
fixed several issues I was having on both, a wireless headset and the
USB connected headset). Hope this information helps along.

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

Title:
  Logitech G930 drops connection and reconnects in 17.10 (But not in
  17.04)

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Every so many seconds / minutes the Wireless headset Logitech G930
  simply drops connection. It always reconnects but when doing a
  recording, a meeting, listening to music or a movie it simply drops
  the connection for 1 to 3 second. This happens several times an hour.
  If it helps, it was not happening in 17.04 (Never happened in more
  than 200+ hours of using the headset).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cyrex  1288 F pulseaudio
   /dev/snd/controlC2:  cyrex  1288 F pulseaudio
   /dev/snd/controlC0:  cyrex  1288 F pulseaudio
  Date: Sat Oct 21 17:55:42 2017
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  

[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

[Luis Alvarado]

Yes correct, it uses it's own wireless dongle. But since this is the
issue, shouldn't I update pulseaudio instead of the kernel?

I already have the latest stable one, 4.13, and the 4.14 is not out yet
(To avoid issues like Nvidia Module compatibility). I will try
installing 4.12 to see what happens. I also checked to see if PulseAudio
had a new version and the 11.1 (and 11.0) sure look like they fixed the
issue by checking out their changes (Not tried it yet).

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

Title:
  Logitech G930 drops connection and reconnects in 17.10 (But not in
  17.04)

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Every so many seconds / minutes the Wireless headset Logitech G930
  simply drops connection. It always reconnects but when doing a
  recording, a meeting, listening to music or a movie it simply drops
  the connection for 1 to 3 second. This happens several times an hour.
  If it helps, it was not happening in 17.04 (Never happened in more
  than 200+ hours of using the headset).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cyrex  1288 F pulseaudio
   /dev/snd/controlC2:  cyrex  1288 F pulseaudio
   /dev/snd/controlC0:  cyrex  1288 F pulseaudio
  Date: Sat Oct 21 17:55:42 2017
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1725863] [NEW] Logitech G930 Fails in 17.10 (But not in 17.04)

[Luis Alvarado]

Public bug reported:

Every so many seconds / minutes the Wireless headset Logitech G930
simply drops connection. It always reconnects but when doing a
recording, a meeting, listening to music or a movie it simply drops the
connection for 1 to 3 second. This happens several times an hour. If it
helps, it was not happening in 17.04 (Never happened in more than 200+
hours of using the headset).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  cyrex  1288 F pulseaudio
 /dev/snd/controlC2:  cyrex  1288 F pulseaudio
 /dev/snd/controlC0:  cyrex  1288 F pulseaudio
Date: Sat Oct 21 17:55:42 2017
InstallationDate: Installed on 2017-10-19 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/30/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3504
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII HERO ALPHA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug artful

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

Title:
  Logitech G930 Fails in 17.10 (But not in 17.04)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Every so many seconds / minutes the Wireless headset Logitech G930
  simply drops connection. It always reconnects but when doing a
  recording, a meeting, listening to music or a movie it simply drops
  the connection for 1 to 3 second. This happens several times an hour.
  If it helps, it was not happening in 17.04 (Never happened in more
  than 200+ hours of using the headset).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cyrex  1288 F pulseaudio
   /dev/snd/controlC2:  cyrex  1288 F pulseaudio
   /dev/snd/controlC0:  cyrex  1288 F pulseaudio
  Date: Sat Oct 21 17:55:42 2017
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1725865] [NEW] Network shows Cable Unplugged

[Luis Alvarado]

Public bug reported:

This was working perfectly on 17.04, but after installing 17.10 from
scratch, the wired network is not detected. It simply shows as Cable
Unplugged when in fact there is the same cable still connected directly
to the router. This same computer has Windows 10 and it detects the
network correctly. I also tested Fedora and it detected the network
correctly (The wired one). I am currently using only the Wireless
connection because of this.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Sat Oct 21 17:59:31 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-10-19 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
 default via 192.168.1.1 dev wlp9s0 proto static metric 600 
 169.254.0.0/16 dev wlp9s0 scope link metric 1000 
 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
 wlp9s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Linux   ecb8e125-48ff-4994-94c8-bdf3731334ce  
/org/freedesktop/NetworkManager/ActiveConnection/13 
 enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
  
 lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

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

Title:
  Network shows Cable Unplugged

Status in network-manager package in Ubuntu:
  New

Bug description:
  This was working perfectly on 17.04, but after installing 17.10 from
  scratch, the wired network is not detected. It simply shows as Cable
  Unplugged when in fact there is the same cable still connected
  directly to the router. This same computer has Windows 10 and it
  detects the network correctly. I also tested Fedora and it detected
  the network correctly (The wired one). I am currently using only the
  Wireless connection because of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 21 17:59:31 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.1.1 dev wlp9s0 proto static metric 600 
   169.254.0.0/16 dev wlp9s0 scope link metric 1000 
   192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   wlp9s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Linux   ecb8e125-48ff-4994-94c8-bdf3731334ce  
/org/freedesktop/NetworkManager/ActiveConnection/13 
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
  
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  

[Touch-packages] [Bug 1725410] [NEW] Intel Integrated Card not working Asus Hero Alpha VIII

[Luis Alvarado]

Public bug reported:

After upgrading to the latest Kernel, the issue appeared. Basically it
always says there is no cable detected and the LAN (Wired) connection
never works. Only wireless. If I go back to a previous Ubuntu version it
works, but after either 4.12 or 4.13 the issue appeared. I also checked
the BIOS version and it works only if I stay with a previous Ubuntu
version.

The device that is having an issue is:

description: Ethernet interface
   product: Ethernet Connection (2) I219-V
   vendor: Intel Corporation
   physical id: 1f.6
   bus info: pci@:00:1f.6
   logical name: enp0s31f6
   version: 31
   serial: 34:97:f6:36:cb:d6
   capacity: 1Gbit/s
   width: 32 bits
   clock: 33MHz
   capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=3.2.6-k firmware=0.7-4 latency=0 link=no multicast=yes 
port=twisted pair
   resources: irq:132 memory:df70-df71


00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet
Connection (2) I219-V [8086:15b8] (rev 31)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Fri Oct 20 11:59:57 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-10-19 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
 default via 192.168.1.1 dev wlp9s0 proto static metric 600 
 169.254.0.0/16 dev wlp9s0 scope link metric 1000 
 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.13 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME   UUID  TYPE TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
 Linux  74b235bc-acdd-4fc3-a028-d960c890fbe0  802-11-wireless  1508522270  Fri 
20 Oct 2017 11:57:50 AM CST  yes  0 no
/org/freedesktop/NetworkManager/Settings/2  yes wlp9s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
 Intel  ce6b4984-a66e-306e-9a98-9487e5b3c553  802-3-ethernet   1508435911  Thu 
19 Oct 2017 11:58:31 AM CST  yes  4294966297no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
   --
nmcli-dev:
 DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlp9s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Linux   74b235bc-acdd-4fc3-a028-d960c890fbe0  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
 lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

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

Title:
  Intel Integrated Card not working Asus Hero Alpha VIII

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrading to the latest Kernel, the issue appeared. Basically it
  always says there is no cable detected and the LAN (Wired) connection
  never works. Only wireless. If I go back to a previous Ubuntu version
  it works, but after either 4.12 or 4.13 the issue appeared. I also
  checked the BIOS version and it works only if I stay with a previous
  Ubuntu version.

  The device that is having an issue is:

  description: Ethernet interface
 product: Ethernet Connection (2) I219-V
 vendor: Intel Corporation
 physical id: 1f.6
 bus info: pci@:00:1f.6
 logical name: enp0s31f6
 version: 31

[Touch-packages] [Bug 1723049] [NEW] package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[Jorge Luis]

Public bug reported:

An error after operating system update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
Date: Wed Oct 11 17:35:12 2017
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2017-07-06 (97 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: qtbase-opensource-src
Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

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

Bug description:
  An error after operating system update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Wed Oct 11 17:35:12 2017
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2017-07-06 (97 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: qtbase-opensource-src
  Title: package libqt5gui5:i386 5.5.1+dfsg-16ubuntu7.5 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1723049/+subscriptions

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

[Touch-packages] [Bug 1715424] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar s

[Luis Galarza]

Public bug reported:

ubuntu 16.04 LTS

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
Date: Wed Sep  6 10:12:16 2017
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
InstallationDate: Installed on 2016-03-12 (542 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: openssl
Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: El 
paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
UpgradeStatus: Upgraded to xenial on 2016-07-30 (402 days ago)

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


** Tags: apport-package i386 xenial

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  El paquete está en un estado grave de inconsistencia - debe
  reinstalarlo  antes de intentar su configuración.

Status in openssl package in Ubuntu:
  New

Bug description:
  ubuntu 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Wed Sep  6 10:12:16 2017
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2016-03-12 (542 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
El paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes 
de intentar su configuración.
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (402 days ago)

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

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

[Touch-packages] [Bug 1125944] Re: (gedit:3366): IBUS-WARNING **: The owner of ~/.config/ibus/bus is not root!

[Luis]

I solved it.

gksudo nautilus

go to

~/.config/ibus/bus


Set up the owner, group as my user.

Propietary - (user)
Access - Create and delete
Group - (user)
Access -  Access to files
others - Access to files

After that. The message disappeared.

The error is regards to opening graphical applications with sudo. To
avoid this error in the future, just replace it with gksudo.

Regards.

Regards

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

Title:
  (gedit:3366): IBUS-WARNING **: The owner of ~/.config/ibus/bus is not
  root!

Status in ibus package in Ubuntu:
  Won't Fix

Bug description:
  This is "Won't Fix" because it is the symptom of a user error.

  As indicated repeatedly in the comments below, you should not use
  "sudo gedit" (or if you do, you should be able to live with this error
  message).

  The proper way to run a GUI tool with elevated privileges is with sudo
  -i or gksudo.

  Original problem description follows.

  

  RR i386 logged as gnome-classic (fallback)

  Seen that error for the first time while using a terminal:

  oem@oem-desktop:~$ sudo gedit /etc/default/grub

  (gedit:3366): IBUS-WARNING **: The owner of /home/oem/.config/ibus/bus
  is not root!

  That one is own by "Me" (screenshot joined)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ibus 1.4.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Fri Feb 15 08:33:36 2013
  MarkForUpload: True
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1705573] [NEW] [QY7, recording] No sound at all

[Luis Alvarado]

Public bug reported:

Using 17.10 and as requested, using the Bluetooth QY7, the microphone is
not working at all. The sound works but the microphone does not, so for
meeting calls, it would not work at all. Similar to this case
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1705572 where
I reported another device I have.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  cyrex  1728 F pulseaudio
 /dev/snd/controlC3:  cyrex  1728 F pulseaudio
 /dev/snd/controlC0:  cyrex  1728 F pulseaudio
 /dev/snd/controlC1:  cyrex  1728 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Thu Jul 20 14:47:16 2017
InstallationDate: Installed on 2017-05-18 (63 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: QY7
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  cyrex  1728 F pulseaudio
 /dev/snd/controlC3:  cyrex  1728 F pulseaudio
 /dev/snd/controlC0:  cyrex  1728 F pulseaudio
 /dev/snd/controlC1:  cyrex  1728 F pulseaudio
Symptom_Type: No sound at all
Title: [QY7, recording] No sound at all
UpgradeStatus: Upgraded to artful on 2017-07-18 (1 days ago)
dmi.bios.date: 01/25/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3401
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII HERO ALPHA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3401:bd01/25/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


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

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

Title:
  [QY7, recording] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Using 17.10 and as requested, using the Bluetooth QY7, the microphone
  is not working at all. The sound works but the microphone does not, so
  for meeting calls, it would not work at all. Similar to this case
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1705572
  where I reported another device I have.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  cyrex  1728 F pulseaudio
   /dev/snd/controlC3:  cyrex  1728 F pulseaudio
   /dev/snd/controlC0:  cyrex  1728 F pulseaudio
   /dev/snd/controlC1:  cyrex  1728 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Jul 20 14:47:16 2017
  InstallationDate: Installed on 2017-05-18 (63 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: QY7
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  cyrex  1728 F pulseaudio
   /dev/snd/controlC3:  cyrex  1728 F pulseaudio
   /dev/snd/controlC0:  cyrex  1728 F pulseaudio
   /dev/snd/controlC1:  cyrex  1728 F pulseaudio
  Symptom_Type: No sound at all
  Title: [QY7, recording] No sound at all
  UpgradeStatus: Upgraded to artful on 2017-07-18 (1 days ago)
  dmi.bios.date: 01/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3401
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3401:bd01/25/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System 

[Touch-packages] [Bug 1705572] [NEW] [CHORD MS 530, recording] Microphone problem

[Luis Alvarado]

Public bug reported:

For 17.10, as requested, here is a Bluetooth test using Audio
headphones. In this case I am using the CHORD MS 530. The sound works
but the microphone does not. So I can't use it for meeting calls to talk
and hear at the same time. I follow the normal steps of pairing and
indeed it auto selected the device in the output tab of the sound option
in the system settings, but on the input tab, it simply does not show as
working. It shows on the input list but there is no recording working in
there.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Thu Jul 20 14:40:23 2017
InstallationDate: Installed on 2017-05-18 (63 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: CHORD MS 530
Symptom_Type: Only some of inputs are working
Title: [CHORD MS 530, recording] Recording problem
UpgradeStatus: Upgraded to artful on 2017-07-18 (1 days ago)
dmi.bios.date: 01/25/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3401
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII HERO ALPHA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3401:bd01/25/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


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

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

Title:
  [CHORD MS 530, recording] Microphone problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  For 17.10, as requested, here is a Bluetooth test using Audio
  headphones. In this case I am using the CHORD MS 530. The sound works
  but the microphone does not. So I can't use it for meeting calls to
  talk and hear at the same time. I follow the normal steps of pairing
  and indeed it auto selected the device in the output tab of the sound
  option in the system settings, but on the input tab, it simply does
  not show as working. It shows on the input list but there is no
  recording working in there.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Jul 20 14:40:23 2017
  InstallationDate: Installed on 2017-05-18 (63 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: CHORD MS 530
  Symptom_Type: Only some of inputs are working
  Title: [CHORD MS 530, recording] Recording problem
  UpgradeStatus: Upgraded to artful on 2017-07-18 (1 days ago)
  dmi.bios.date: 01/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3401
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3401:bd01/25/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1705255] Re: what's

[celso luis da silva cavalheiro]

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

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

Title:
  what's

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  N: A ignorar o ficheiro '50unattended-upgrades.ucf-old' no directório 
'/etc/apt/apt.conf.d/' porque tem uma extensão inválida no nome do ficheiro
  N: A ignorar o ficheiro '50unattended-upgrades.ucf-dist' no directório 
'/etc/apt/apt.conf.d/' porque tem uma extensão inválida no nome do ficheiro
  celso@Kavalheiro:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.7
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul 19 08:55:37 2017
  DistUpgraded: 2017-07-15 16:24:49,980 DEBUG /openCache(), new cache size 8331
  DistroCodename: yakkety
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems 4 Series Chipset Integrated 
Graphics Controller [1019:2260]
  InstallationDate: Installed on 2014-04-19 (1186 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MachineType: MEGAWARE G41T-M7
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-59-generic 
root=UUID=ac5e70ff-59c8-4ee4-8bbe-fd2d1e46cec5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2017-07-15 (3 days ago)
  dmi.bios.date: 07/06/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 110706
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: G41T-M7
  dmi.board.vendor: MEGAWARE
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEGAWARE
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr110706:bd07/06/2011:svnMEGAWARE:pnG41T-M7:pvr1.0:rvnMEGAWARE:rnG41T-M7:rvr1.0:cvnMEGAWARE:ct3:cvr1.0:
  dmi.product.name: G41T-M7
  dmi.product.version: 1.0
  dmi.sys.vendor: MEGAWARE
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Tue Jul 18 11:55:43 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   input USB OPTICAL MOUSE   MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output   VGA-1
  xserver.version: 2:1.18.4-1ubuntu6.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1705255] [NEW] what's

[celso luis da silva cavalheiro]

Public bug reported:

N: A ignorar o ficheiro '50unattended-upgrades.ucf-old' no directório 
'/etc/apt/apt.conf.d/' porque tem uma extensão inválida no nome do ficheiro
N: A ignorar o ficheiro '50unattended-upgrades.ucf-dist' no directório 
'/etc/apt/apt.conf.d/' porque tem uma extensão inválida no nome do ficheiro
celso@Kavalheiro:~$

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
Uname: Linux 4.8.0-59-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.7
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Jul 19 08:55:37 2017
DistUpgraded: 2017-07-15 16:24:49,980 DEBUG /openCache(), new cache size 8331
DistroCodename: yakkety
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Elitegroup Computer Systems 4 Series Chipset Integrated Graphics 
Controller [1019:2260]
InstallationDate: Installed on 2014-04-19 (1186 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
MachineType: MEGAWARE G41T-M7
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-59-generic 
root=UUID=ac5e70ff-59c8-4ee4-8bbe-fd2d1e46cec5 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to yakkety on 2017-07-15 (3 days ago)
dmi.bios.date: 07/06/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 110706
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: G41T-M7
dmi.board.vendor: MEGAWARE
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MEGAWARE
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr110706:bd07/06/2011:svnMEGAWARE:pnG41T-M7:pvr1.0:rvnMEGAWARE:rnG41T-M7:rvr1.0:cvnMEGAWARE:ct3:cvr1.0:
dmi.product.name: G41T-M7
dmi.product.version: 1.0
dmi.sys.vendor: MEGAWARE
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Tue Jul 18 11:55:43 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 input USB OPTICAL MOUSE   MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output   VGA-1
xserver.version: 2:1.18.4-1ubuntu6.1
xserver.video_driver: modeset

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


** Tags: apport-bug compiz-0.9 i386 third-party-packages ubuntu yakkety

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

Title:
  what's

Status in xorg package in Ubuntu:
  New

Bug description:
  N: A ignorar o ficheiro '50unattended-upgrades.ucf-old' no directório 
'/etc/apt/apt.conf.d/' porque tem uma extensão inválida no nome do ficheiro
  N: A ignorar o ficheiro '50unattended-upgrades.ucf-dist' no directório 
'/etc/apt/apt.conf.d/' porque tem uma extensão inválida no nome do ficheiro
  celso@Kavalheiro:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.7
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul 19 08:55:37 2017
  DistUpgraded: 2017-07-15 16:24:49,980 DEBUG /openCache(), new cache size 8331
  DistroCodename: yakkety
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems 4 Series Chipset Integrated 
Graphics Controller [1019:2260]
  

[Touch-packages] [Bug 1703092] [NEW] package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2

[Luis Santos]

Public bug reported:

error shows when upgrading system
Could not install 'systemd-shim'

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: systemd-sysv 232-21ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-23.25-generic 4.10.17
Uname: Linux 4.10.0-23-generic i686
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: i386
Date: Sat Jul  8 10:37:04 2017
ErrorMessage: subprocess installed post-removal script returned error exit 
status 2
InstallationDate: Installed on 2013-05-04 (1525 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: systemd
Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 need-duplicate-check third-party-packages zesty

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

Title:
  package systemd-sysv 232-21ubuntu5 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  error shows when upgrading system
  Could not install 'systemd-shim'

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: systemd-sysv 232-21ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-23.25-generic 4.10.17
  Uname: Linux 4.10.0-23-generic i686
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: i386
  Date: Sat Jul  8 10:37:04 2017
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 2
  InstallationDate: Installed on 2013-05-04 (1525 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: systemd
  Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Jose Luis]

had somebody tryed sound with kernel 4.12?

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1696717] Re: tzdata stills apply DST for Mongolia

[Luis Filipe Domingues]

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

** This bug has been marked a duplicate of bug 1691092
   outdated timezone information for Mongolia

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

Title:
  tzdata stills apply DST for Mongolia

Status in tzdata package in Ubuntu:
  New

Bug description:
  Since 2017 Mongolia does not apply DST time.

  However, on Ubuntu 16.04, the DST time is still applied, so my
  computers are 1h ahead.

  Here you have the output of timedatectl:
Local time: Thu 2017-06-08 20:10:37 ULAST
Universal time: Thu 2017-06-08 11:10:37 UTC
  RTC time: Thu 2017-06-08 11:10:37
 Time zone: Asia/Ulaanbaatar (ULAST, +0900)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  And the same command in Debian Stretch:
Local time: jeu 2017-06-08 19:10:27 +08
Universal time: jeu 2017-06-08 11:10:27 UTC
  RTC time: jeu 2017-06-08 11:10:27
 Time zone: Asia/Ulaanbaatar (+08, +0800)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  The current installed package is:
  tzdata:
Installed: 2016j-0ubuntu0.16.04
Candidate: 2016j-0ubuntu0.16.04

  
  Please remove DST for Ulaanbaatar.

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

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

[Touch-packages] [Bug 1696717] [NEW] tzdata stills apply DST for Mongolia

[Luis Filipe Domingues]

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

Public bug reported:

Since 2017 Mongolia does not apply DST time.

However, on Ubuntu 16.04, the DST time is still applied, so my computers
are 1h ahead.

Here you have the output of timedatectl:
  Local time: Thu 2017-06-08 20:10:37 ULAST
  Universal time: Thu 2017-06-08 11:10:37 UTC
RTC time: Thu 2017-06-08 11:10:37
   Time zone: Asia/Ulaanbaatar (ULAST, +0900)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

And the same command in Debian Stretch:
  Local time: jeu 2017-06-08 19:10:27 +08
  Universal time: jeu 2017-06-08 11:10:27 UTC
RTC time: jeu 2017-06-08 11:10:27
   Time zone: Asia/Ulaanbaatar (+08, +0800)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

The current installed package is:
tzdata:
  Installed: 2016j-0ubuntu0.16.04
  Candidate: 2016j-0ubuntu0.16.04


Please remove DST for Ulaanbaatar.

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

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

Title:
  tzdata stills apply DST for Mongolia

Status in tzdata package in Ubuntu:
  New

Bug description:
  Since 2017 Mongolia does not apply DST time.

  However, on Ubuntu 16.04, the DST time is still applied, so my
  computers are 1h ahead.

  Here you have the output of timedatectl:
Local time: Thu 2017-06-08 20:10:37 ULAST
Universal time: Thu 2017-06-08 11:10:37 UTC
  RTC time: Thu 2017-06-08 11:10:37
 Time zone: Asia/Ulaanbaatar (ULAST, +0900)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  And the same command in Debian Stretch:
Local time: jeu 2017-06-08 19:10:27 +08
Universal time: jeu 2017-06-08 11:10:27 UTC
  RTC time: jeu 2017-06-08 11:10:27
 Time zone: Asia/Ulaanbaatar (+08, +0800)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  The current installed package is:
  tzdata:
Installed: 2016j-0ubuntu0.16.04
Candidate: 2016j-0ubuntu0.16.04

  
  Please remove DST for Ulaanbaatar.

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

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

[Touch-packages] [Bug 1588998] Re: [master] package console-setup-linux 1.108ubuntu15 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in packa

[luis gomes]

hello i need welp to fix de problem please, tanks

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

Title:
  [master] package console-setup-linux 1.108ubuntu15 failed to
  install/upgrade: trying to overwrite '/lib/systemd/system/console-
  setup.service', which is also in package keyboard-configuration
  1.108ubuntu15

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Preparing to unpack .../console-setup-linux_1.143_all.deb ...
  Unpacking console-setup-linux (1.143) over (1.108ubuntu15) ...
  dpkg: error processing archive 
/var/cache/apt/archives/console-setup-linux_1.143_all.deb (--unpack):
   trying to overwrite '/lib/systemd/system/console-setup.service', which is 
also in package keyboard-configuration 1.108ubuntu15
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Preparing to unpack .../console-setup_1.143_all.deb ...
  Unpacking console-setup (1.143) over (1.108ubuntu15) ...
  Preparing to unpack .../keyboard-configuration_1.143_all.deb ...
  Unpacking keyboard-configuration (1.143) over (1.108ubuntu15) ...
  Preparing to unpack .../xkb-data_2.17-1_all.deb ...
  Unpacking xkb-data (2.17-1) over (2.16-1ubuntu1) ...
  Preparing to unpack .../gcc-6-base_6.1.1-4_amd64.deb ...
  Unpacking gcc-6-base:amd64 (6.1.1-4) over (6.0.1-0ubuntu1) ...
  Processing triggers for systemd (229-4ubuntu6) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Processing triggers for doc-base (0.10.7) ...
  Processing 1 changed doc-base file...
  Errors were encountered while processing:

  ProblemType: Package
  DistroRelease: Kali 2016.1
  Package: console-setup-linux 1.108ubuntu15
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jun  3 18:24:08 2016
  DuplicateSignature:
   package:console-setup-linux:1.108ubuntu15
   Unpacking console-setup-linux (1.143) over (1.108ubuntu15) ...
   dpkg: error processing archive 
/var/cache/apt/archives/console-setup-linux_1.143_all.deb (--unpack):
trying to overwrite '/lib/systemd/system/console-setup.service', which is 
also in package keyboard-configuration 1.108ubuntu15
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15
  InstallationDate: Installed on 2016-06-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.7
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1588998/+subscriptions

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

[Touch-packages] [Bug 1688344] [NEW] package systemd 229-4ubuntu17 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2

[luis]

Public bug reported:

/bin/sh: 1: /usr/sbin/dpkg-preconfigure: Too many levels of symbolic links
dpkg: aviso: falta el fichero de lista de ficheros del paquete `lightdm', se 
supondrá que el paquete no tiene ningún fichero actualmente instalado
(Leyendo la base de datos ... 534432 ficheros o directorios instalados 
actualmente.)
Preparando para desempaquetar .../dpkg_1.18.4ubuntu1.2_amd64.deb ...
Desempaquetando dpkg (1.18.4ubuntu1.2) sobre (1.18.4ubuntu1.1) ...
Configurando dpkg (1.18.4ubuntu1.2) ...
Procesando disparadores para man-db (2.7.5-1) ...
/var/lib/dpkg/info/man-db.postinst: 22: /var/lib/dpkg/info/man-db.postinst: 
perl: Too many levels of symbolic links
dpkg: aviso: falta el fichero de lista de ficheros del paquete `lightdm', se 
supondrá que el paquete no tiene ningún fichero actualmente instalado
(Leyendo la base de datos ... 534432 ficheros o directorios instalados 
actualmente.)
Preparando para desempaquetar .../libudev1_229-4ubuntu17_amd64.deb ...
Desempaquetando libudev1:amd64 (229-4ubuntu17) sobre (229-4ubuntu16) ...
Procesando disparadores para libc-bin (2.23-0ubuntu7) ...
Configurando libudev1:amd64 (229-4ubuntu17) ...
Procesando disparadores para libc-bin (2.23-0ubuntu7) ...
dpkg: aviso: falta el fichero de lista de ficheros del paquete `lightdm', se 
supondrá que el paquete no tiene ningún fichero actualmente instalado
(Leyendo la base de datos ... 534432 ficheros o directorios instalados 
actualmente.)
Preparando para desempaquetar .../udev_229-4ubuntu17_amd64.deb ...
Desempaquetando udev (229-4ubuntu17) sobre (229-4ubuntu16) ...
Preparando para desempaquetar .../libsystemd0_229-4ubuntu17_amd64.deb ...
Desempaquetando libsystemd0:amd64 (229-4ubuntu17) sobre (229-4ubuntu16) ...
Procesando disparadores para ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
/usr/bin/env: «perl»: Demasiados niveles de enlaces simbólicos
/usr/bin/env: «perl»: Demasiados niveles de enlaces simbólicos
/usr/bin/env: «perl»: Demasiados niveles de enlaces simbólicos
Procesando disparadores para man-db (2.7.5-1) ...
/var/lib/dpkg/info/man-db.postinst: 22: /var/lib/dpkg/info/man-db.postinst: 
perl: Too many levels of symbolic links
Procesando disparadores para libc-bin (2.23-0ubuntu7) ...
Configurando libsystemd0:amd64 (229-4ubuntu17) ...
Procesando disparadores para libc-bin (2.23-0ubuntu7) ...
dpkg: aviso: falta el fichero de lista de ficheros del paquete `lightdm', se 
supondrá que el paquete no tiene ningún fichero actualmente instalado
(Leyendo la base de datos ... 534432 ficheros o directorios instalados 
actualmente.)
Preparando para desempaquetar .../systemd_229-4ubuntu17_amd64.deb ...
Desempaquetando systemd (229-4ubuntu17) sobre (229-4ubuntu16) ...
Procesando disparadores para ureadahead (0.100.0-19) ...
/usr/bin/env: «perl»: Demasiados niveles de enlaces simbólicos
/usr/bin/env: «perl»: Demasiados niveles de enlaces simbólicos
/usr/bin/env: «perl»: Demasiados niveles de enlaces simbólicos
Procesando disparadores para man-db (2.7.5-1) ...
/var/lib/dpkg/info/man-db.postinst: 22: /var/lib/dpkg/info/man-db.postinst: 
perl: Too many levels of symbolic links
Configurando systemd (229-4ubuntu17) ...
/var/lib/dpkg/info/systemd.postinst: 100: /var/lib/dpkg/info/systemd.postinst: 
addgroup: Too many levels of symbolic links
dpkg: error al procesar el paquete systemd (--configure):
 el subproceso instalado el script post-installation devolvió el código de 
salida de error 2
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu17
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Thu May  4 11:24:58 2017
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 2
InstallationDate: Installed on 2016-05-19 (349 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: Dell Inc. Latitude E6430
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=03e348db-efce-4dc1-bf5d-6be046201d31 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.18
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 
 3 overridden configuration files found.
Title: package systemd 229-4ubuntu17 failed to install/upgrade: el subproceso 
instalado el script post-installation devolvió el código de salida de error 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07

[Touch-packages] [Bug 1683479] [NEW] package libtotem-plparser18 3.10.7-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-t

[Luis Dardon]

Public bug reported:

after install katoolin tools

ProblemType: Package
DistroRelease: Kali 2017.1
Package: libtotem-plparser18 3.10.7-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Mon Apr 17 14:00:45 2017
ErrorMessage: intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-totem-pl-parser-videosite',
 que está también en el paquete libtotem-plparser-videosite:amd64 
3.10.7-1ubuntu1
InstallationDate: Installed on 2017-04-16 (1 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.23kali1
 apt  1.4
SourcePackage: totem-pl-parser
Title: package libtotem-plparser18 3.10.7-1ubuntu1 failed to install/upgrade: 
intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-totem-pl-parser-videosite',
 que está también en el paquete libtotem-plparser-videosite:amd64 
3.10.7-1ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: totem-pl-parser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package kali-rolling need-duplicate-check 
third-party-packages

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

Title:
  package libtotem-plparser18 3.10.7-1ubuntu1 failed to install/upgrade:
  intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libtotem-
  plparser18/totem-pl-parser/99-totem-pl-parser-videosite', que está
  también en el paquete libtotem-plparser-videosite:amd64
  3.10.7-1ubuntu1

Status in totem-pl-parser package in Ubuntu:
  New

Bug description:
  after install katoolin tools

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: libtotem-plparser18 3.10.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon Apr 17 14:00:45 2017
  ErrorMessage: intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-totem-pl-parser-videosite',
 que está también en el paquete libtotem-plparser-videosite:amd64 
3.10.7-1ubuntu1
  InstallationDate: Installed on 2017-04-16 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.4
  SourcePackage: totem-pl-parser
  Title: package libtotem-plparser18 3.10.7-1ubuntu1 failed to install/upgrade: 
intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/libtotem-plparser18/totem-pl-parser/99-totem-pl-parser-videosite',
 que está también en el paquete libtotem-plparser-videosite:amd64 
3.10.7-1ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1683479/+subscriptions

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

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

[Luis Michael Ibarra]

Kai-Heng, At least for me, it's working now. Btw, before changing
DNSSEC=off, I tested removing dnsmasq to keep only systemd-resolved(as
someone mentioned above), and systemd-resolved didn't resolve any
domain. I had to install dnsmasq again to have some sort of connection.

Is this bug related to this one[1]?

[1] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320

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

Title:
  systemd-resolved using 100% CPU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

[Luis Michael Ibarra]

It also happens when you are connected by wire. XPS13 9350 affected
after upgrading from 16.10(yaketti) to 17.04(zetsy(.

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

Title:
  systemd-resolved using 100% CPU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0


  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)


  
  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  dmi.chassis.asset.tag: CNU51199KV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Jose Luis]

4.8.0-22 not 4.8.22  Sorry

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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