date:20181109

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/358586

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

Title:
  apparmor profile denied for kerberos client keytab and credential
  cache files

Status in openldap package in Ubuntu:
  In Progress
Status in openldap source package in Trusty:
  In Progress
Status in openldap source package in Xenial:
  In Progress
Status in openldap source package in Bionic:
  In Progress
Status in openldap source package in Cosmic:
  In Progress

Bug description:
  [Impact]
  When using syncrepl replication with openldap, the consumer needs to 
authenticate to the provider in order to perform the searches and fetch the 
data. When this authentication is a simple bind, a simple username/password 
pair is used and that can be easily supplied in a configuration file.

  When one wants to use a stronger authentication mechanism, like gssapi
  (kerberos), the authentication is based on keytab files and tickets.
  The consumer needs to obtain a ticket from the KDC, and use that
  ticket to authenticate itself with the provider.

  For users, it's a simple matter of running kinit(1) and providing a
  password. For services, the solution is to extract the key from the
  KDC and store it in a local keytab file, which is then used by the
  service to obtain the TGT.

  Problem is this TGT expires, and needs to be renewed periodically.
  Solutions have popped up for that issue, the most famous one being
  kstart (https://www.eyrie.org/~eagle/software/kstart/), but since the
  MIT kerberos 1.11 release, there is a simpler way.

  Via the default_client_keytab_name krb5.conf(5) option, one can
  specify the default location of a keytab file per local user. The
  kerberos library will then automatically use that file to obtain the
  TGT, and proceed as usual from there.

  The default value of that setting is
  /etc/krb5/user//client.keytab.

  Turns out the openldap slapd apparmor profile doesn't account for
  that, and blocks attempts to read that file. It also blocks reading
  the TGT that is obtained and stored in /tmp/krb5cc_, resulting in
  such DENIED errors in the logs:

  apparmor="DENIED" operation="open" profile="/usr/sbin/slapd"
  name="/etc/krb5/user/389/client.keytab" pid=19080 comm="slapd"
  requested_mask="r" denied_mask="r" fsuid=389 ouid=389

  apparmor="DENIED" operation="file_lock" profile="/usr/sbin/slapd"
  name="/tmp/krb5cc_389" pid=19080 comm="slapd" requested_mask="k"
  denied_mask="k" fsuid=389 ouid=389

  Since the slapd apparmor is enabled by default, this blocks the usage
  of this very helpful feature. Also considering that kerberos/gssapi
  errors are usually hard to debug, it might take a while for an admin
  to figure out what is going on.

  The fix is to update the apparmor profile and allow access to those
  files. Unfortunately there are no rich globbing rules for paths in an
  apparmor profile, nothing like @{uid} of the current process yet, or a
  regexp rule like [0-9]+, so the rules have to be a bit accomodating.
  For this bug, I came up with these two new lines:

    /etc/krb5/user/*/client.keytab kr,
    owner /tmp/krb5cc_* rwk,

  One could relax the first one perhaps into something like
  /etc/krb5/**, but the above works with the default settings.

  [Test Case]
  Setting up openldap replication via gssapi can be complicated, so I wrote 
some scripts to help.
  - setup-kdc.sh: sets up the KDC server
  - setup-provider.sh: sets up the openldap provider
  - setup-consumer.sh: sets up the openldap consumer

  The scripts expect LXD containers to be used, that have a working DNS
  setup for a ".lxd" domain. In other words, if you do:

  lxc launch ubuntu-daily:bionic bionic-provider

  The script expects the container to be reachable via "bionic-
  provider.lxd". That is the default behavior of LXD, and changing the
  scripts to work in a more generic case was deemed not worth it.

  So here we go. Here are the steps for a cosmic test, just replace
  "cosmic" with the name of the ubuntu release you are testing.

  = KDC =

  * launch the KDC container and copy the setup-kdc.sh script into it:
  lxc launch ubuntu-daily:cosmic cosmic-kdc
  lxc file push ./setup-kdc.sh cosmic-kdc/root/

  * Enter the container and run the setup-kdc.sh script:
  lxc exec cosmic-kdc bash
  bash ./setup-kdc.sh

  * The script will show two prompts: one from debconf, with just an
  "ok" option, so hit ENTER there. The second prompt will be for a
  password. Use any one you like, it won't be needed again.

  * The KDC is setup, you can exit the container.

  = PROVIDER =
  * launch the provider and copy the setup-provider.sh script into it:
  lxc launch ubuntu-daily:cosmic cosmic-provider
  lxc file push ./setup-provider.sh cosmic-provider/root/

  * Enter the container and

[Touch-packages] [Bug 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

2018-11-09 Thread Seth Arnold

Edson, you have a different issue.

If you want to use ESET then you should add:

  /tmp/esets.sock rw,

to the /etc/apparmor.d/abstractions/base file and run:

sudo systemctl reload apparmor

Thanks

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in apparmor package in Ubuntu:
  New

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 18 10:56:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1003 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100
  MachineType: LENOVO 4298R86
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4298R86
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-03-12T15:11:15.740184

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1571531/+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 1771040] Re: Bluetooth HFP/HSP profile doesn't work in 18.04

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

** This bug is no longer a duplicate of bug 1768625
   Bluetooth headset HSP/HFP mode not working in Bionic
** This bug has been marked a duplicate of bug 1576559
   Refused to switch profile to headset_head_unit: Not connected

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

Title:
  Bluetooth HFP/HSP profile doesn't work in 18.04

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Bose QC35 II

  When selecting the A2DP Sink profile these headphones work fine.
  However, with HSP/HFP selected neither the output nor the microphone
  work. The headphones will periodically say "Call from" and then break
  off, and also you can hear a low grade crackling like line noise in
  them the rest of the time.

  Potentially relevant logs:
  dmesg (the second message is repeated frequently):
  [   68.288408] input: 2C:41:A1:80:A1:C4 as /devices/virtual/input/input21
  [   78.575027] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Originally, I got an error like the following from ("journalctl -u 
bluetooth"), but then ran "rfkill unblock bluetooth" which seems to have fixed 
it:
  May 13 15:58:02 skylake bluetoothd[1023]: Failed to set mode: Blocked through 
rfkill (0x12)
  May 13 15:58:19 skylake bluetoothd[1023]: Failed to set mode: Blocked through 
rfkill (0x12)
  May 13 16:00:41 skylake bluetoothd[1023]: Unable to get io data for Headset 
Voice gateway: getpeername: Transport endpoint is not connected (107)
  May 13 16:00:41 skylake bluetoothd[1023]: Unable to get io data for Phone 
Book Access: getpeername: Transport endpoint is not connected (107)

  What additional information would be useful to debug this?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 16:33:13 2018
  InstallationDate: Installed on 2018-05-13 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3406
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170I PRO GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3406:bd07/10/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170IPROGAMING:rvrRevX.0x: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
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: C8:FF:28:31:68:E4  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:19479 acl:97 sco:0 events:730 errors:0
TX bytes:8355 acl:99 sco:3 commands:148 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1771040/+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 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic

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

** This bug has been marked a duplicate of bug 1576559
   Refused to switch profile to headset_head_unit: Not connected

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

Title:
  Bluetooth headset HSP/HFP mode not working in Bionic

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is a previous bug with almost the same title, but for Xenial
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I
  have had this issue in Artful, and when commented on the old bug, I
  was asked to raise a new one instead. I waited to see if Bionic fixed
  it for me, but it does not seem to work still. So!

  Steps to reproduce:
  1. enable bluetooth on computer and switch on the headset.
  2. pair and connect the headset
  3. go to settings to switch headset to HSP/HFP mode to enable mic
  4. save and close window.

  Expected behaviour:
  1. mic should be enabled and headset should be usable to attend calls on 
laptop.

  Behaviour in error:
  1. Headset profile switches back to A2DP and mic is not enabled.

  I am using a generic bluetooth headset on a fresh updated Kubuntu
  18.04 bionic with plasma DE.

  Software versions:
  Kernel: 4.15.0-20-generic
  Bluez version: 5.48-0ubuntu3
  pulseaudio: 1:11.1-1ubuntu7
  pulseaudio-module-bluetooth: 1:11.1-1ubuntu7

  
  Additional information:
  Running "pacmd list-cards" says that HSF/HFP is 'not available' on the 
headset:

  Output from Headset section:
  profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, 
available: no)
  off: Off (priority 0, available: yes)
  active profile: 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+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 1778331] Re: HSP bluetooth profile does not work. Only A2DP works

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

** This bug is no longer a duplicate of bug 1768625
   Bluetooth headset HSP/HFP mode not working in Bionic
** This bug has been marked a duplicate of bug 1576559
   Refused to switch profile to headset_head_unit: Not connected

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

Title:
  HSP bluetooth profile does not work. Only A2DP works

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to use Applie Airpods and a Sennheiser bluetooth headsets
  with Ubuntu (and Kubuntu) 18.04. They connect and work find in A2DP
  mode but are unable to connect in HSP mode rendering them useless for
  work as the mic only works in HSP mode.

  I can see HSP mode in the dropdown in sound settings and can switch to
  it but the headset actually remains connected in A2DP mode. If I close
  the sound settings window and re-open it, I can see the setting
  reverted to A2DP.

  I also tried pactl CLI util but it results in an error when switching
  to HSP

  ```
  pactl set-card-profile 2 headset_head_unit
  
0|16:19:50
  Failure: Input/Output error
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1778331/+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 1770773] Re: HSP/HFP not working

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

** This bug is no longer a duplicate of bug 1768625
   Bluetooth headset HSP/HFP mode not working in Bionic
** This bug has been marked a duplicate of bug 1576559
   Refused to switch profile to headset_head_unit: Not connected

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

Title:
  HSP/HFP not working

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Using the 18.04 release, paired bluetooth headsets' do not work in
  HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. Go to sound settings > output tab > try switching mode to HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  Logitech H800

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1770773/+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 1734960] Re: Bluetooth headset profile HSP/HFP doesn't work

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

** This bug has been marked a duplicate of bug 1576559
   Refused to switch profile to headset_head_unit: Not connected

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

Title:
  Bluetooth headset profile HSP/HFP doesn't work

Status in blueman package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  My bluetooth headphones Bluedio T2S has a microphone and support HSP/HFP 
profile, but when i try change sound profile in blueman-manager to HSP/HFP - 
then i get error "Failed to change profile to headset_head_unit".
  With profile a2dp headphones work good(clementine, chromium etc..), but I 
could not get work output headphones in steam games, i listen only silence(i 
think it's problem of pulseaudio)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pl7ofit3040 F pulseaudio
   /dev/snd/controlC1:  pl7ofit3040 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Nov 28 19:51:59 2017
  InstallationDate: Installed on 2016-06-22 (524 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Bluedio
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pl7ofit3040 F pulseaudio
   /dev/snd/controlC1:  pl7ofit3040 F pulseaudio
  Symptom_Type: No sound at all
  Title: [Bluedio, recording] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-11-24 (4 days ago)
  dmi.bios.date: 07/08/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L2.38
  dmi.board.name: AM2NF6G-VSTA
  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.:bvrL2.38:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM2NF6G-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-11-24T19:23:23.458810

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

I add this extra information in case it works:

I have some "Bluedio F2" brand headphones that do not activate the microphone, 
however, my Philips SHB4000 hearing aids detect them without any problem (the 
input).
Where in Windows and Android the Bluedio & Philips Microphone works for me 
without problems.

Ubuntu 18.10
nasatome at nasatome-pc in ~
$ uname -r
4.18.0-10-generic

nasatome at nasatome-pc in ~
$ bluetoothctl
Agent registered
[Bluedio F]# devices
Device 18:07:21:27:08:11 Bluedio F
Device 00:1E:7C:37:EF:22 Philips SHB4000
[Bluedio F]# info 18:07:21:27:08:11
Device 18:07:21:27:08:11 (public)
Name: Bluedio F
Alias: Bluedio F
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
[Bluedio F]# info 00:1E:7C:37:EF:22
Device 00:1E:7C:37:EF:22 (public)
Name: Philips SHB4000
Alias: Philips SHB4000
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--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:v0039p13A4d0115
ManufacturerData Key: 0x5349
ManufacturerData Value:
  53 43SC  
[Bluedio F]# 


https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625

-- 
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 1778331] Re: HSP bluetooth profile does not work. Only A2DP works

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

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

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

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

Title:
  HSP bluetooth profile does not work. Only A2DP works

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to use Applie Airpods and a Sennheiser bluetooth headsets
  with Ubuntu (and Kubuntu) 18.04. They connect and work find in A2DP
  mode but are unable to connect in HSP mode rendering them useless for
  work as the mic only works in HSP mode.

  I can see HSP mode in the dropdown in sound settings and can switch to
  it but the headset actually remains connected in A2DP mode. If I close
  the sound settings window and re-open it, I can see the setting
  reverted to A2DP.

  I also tried pactl CLI util but it results in an error when switching
  to HSP

  ```
  pactl set-card-profile 2 headset_head_unit
  
0|16:19:50
  Failure: Input/Output error
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1778331/+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 1802498] Re: AppArmor - Error Messages log files - Mensagens de Erro arquivos de log

2018-11-09 Thread Edson José dos Santos

Another Linux user with the same problem in AppArmor. Access the link.

https://forum.eset.com/topic/17266-apparmorselinux-support/

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

Title:
  AppArmor - Error Messages log files - Mensagens de Erro arquivos de
  log

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hello Canonical team - Ubuntu

  Eset Antivirus has some problems with apparmor.

  In Eset I have observed in the last weeks that the updates are being
  carried out, but the logs that have been installed successfully, where
  it was in bold, no longer appear.

  I also realize that these error messages below are constants and I
  would like to know what it is possible to do to resolve them, as they
  are due to mismatch with apparmor. Can Canonial and Eset work together
  to solve this problem?

  Here is the log of Eset Antivirus for Linux Version 4.90 installed on
  Ubuntu 18.10 Cosmic and log dmesg of Ubuntu.

  Thank you in advance for the attention and collaboration of all

  Edson Santos

  

  Obs: Most of these problems are caused by AppArmor , ESET v4 is not
  compatible with AppArmor/SELinux

  I've tried to test things here and there , ESET still does do it's job
  while AppArmor is enabled (I didn't try with AppArmor disabled) , but
  it encounters lot of errors , and while scanning AppArmor will prevent
  ESET from accessing most files as far as I have noticed.

  I don't know if there is a workaround for AppArmor to allow ESET , but
  I don't want to disable it and I don't want to remove ESET.

  
  Thank you in advance for the attention and collaboration of all

  
  Edson Santos

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1802498/+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 1802591] [NEW] Skip enslaved devices during boot

2018-11-09 Thread Marcelo Cerri

Public bug reported:

In order to support live migration in OCI, we need to filter enslaved
devices during boot.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Assignee: Marcelo Cerri (mhcerri)
 Status: In Progress

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

Title:
  Skip enslaved devices during boot

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  In order to support live migration in OCI, we need to filter enslaved
  devices during boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1802591/+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 568860] Re: init: "before" functionality should block all services mentioned, not just the first

2018-11-09 Thread Cameron Norman

It seems as though the issue is in job_class_induct_job()

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

Title:
  init: "before" functionality should block all services mentioned, not
  just the first

Status in upstart :
  Triaged
Status in upstart package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: upstart

  
  There should be a way to express that a certain service has to be started 
before a list of other services. Currently we can do either:

  a) start on (starting service1 or starting service2)

  This will start our service before either service1 or service2, but
  only one of them will be blocked until service has started. Or:

  b) start on (starting service1 and starting service2)

  Which will block service1 and service2 until out service starts, but
  showstopper is that service won't be started unless both service1 and
  service2 will start.

  We need some mechanism to block a list of services from starting until
  our service is ready, similar to the a) case from above, but where all
  services mentioned in the dependency statement have to wait for the
  service to start.

  Inability to do this reliably and generically is stopping us from
  ensuring that our service starts before any interactive login is
  possible (console, graphics, network). I am also classifying this as a
  security problem since for our customers it really is so.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/568860/+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 1802584] [NEW] A good amount of pulseaudio modules can't be loaded

2018-11-09 Thread Hadrien Titeux

Public bug reported:

I'm running ubuntu 18.04, and I've verified that this is true on two
different installs (one fresh, one updated from 16.04).

I wanted to load three modules from pulseaudio (module-ladspa-sink,
module-loopback, module-null-sink), but it kept saying "Failure on
module initialization"

I listed the available modules with "pactl list modules" but none of the
three were listed.

They still seem to be there in /usr/lib/pulse-12.2/modules/ .

Am I forgetting something? Why can't I load them? Why are they not
listed?

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

** Description changed:

  I'm running ubuntu 18.04, and I've verified that this is true on two
  different installs (one fresh, one updated from 16.04).
  
  I wanted to load three modules from pulseaudio (module-ladspa-sink,
  module-loopback, module-null-sink), but it kept saying "Failure on
  module initialization"
  
  I listed the available modules with "pactl list modules" but none of the
  three were listed.
  
  They still seem to be there in /usr/lib/pulse-12.2/modules/ .
  
- Am I forgetting something? Why can't I load them?
+ Am I forgetting something? Why can't I load them? Why are they not
+ listed?

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

Title:
  A good amount of pulseaudio modules can't be loaded

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm running ubuntu 18.04, and I've verified that this is true on two
  different installs (one fresh, one updated from 16.04).

  I wanted to load three modules from pulseaudio (module-ladspa-sink,
  module-loopback, module-null-sink), but it kept saying "Failure on
  module initialization"

  I listed the available modules with "pactl list modules" but none of
  the three were listed.

  They still seem to be there in /usr/lib/pulse-12.2/modules/ .

  Am I forgetting something? Why can't I load them? Why are they not
  listed?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1802584/+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 1787867] Re: Ubuntu 18.04 LTS bluetooth left discoverable

2018-11-09 Thread Mike Lugar

Can confirm this bug as well. Bluetooth remains discoverable from other
devices when Bluetooth is On. - Thinkpad X220

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

Title:
  Ubuntu 18.04 LTS bluetooth left discoverable

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays
  discoverable which opens up unnecessary vulnerability surface. There
  should be a separate UI switch for discoverability with auto timeout.
  Leaving bluetooth on (using a Bluetooth mouse) should not leave the
  computer always discoverable.

  Current behavior does not match documentation
  https://help.ubuntu.com/stable/ubuntu-help/bluetooth-
  visibility.html.en, even without Bluetooth panel open, the computer is
  still discoverable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+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 1774419] Re: easy_install command is missing

2018-11-09 Thread Cody Lee

Having `easy_install` available (or something similar) is likely an
ongoing need for at least one reason. If a user wants their system to
stay on the latest/upstream version of pip, one sensible way of doing
this is to install the `python-setuptools` package and use
`easy_install` to install `pip` straight from PyPi, and then from that
point forward use `pip install -U pip` to keep it up to date.

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

Title:
  easy_install command is missing

Status in python-setuptools package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  Package: python-setuptools
  Version:  39.0.1-2

  This package installs the easy_install module, but the command is
  missing:

  deploy@controller0:~$ which easy_install
  deploy@controller0:~$ echo $?
  1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1774419/+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 1740894] Re: KEY_RFKILL is not passed to userspace

2018-11-09 Thread Mario Vukelic

And your fix helps:

Still with SRU version installed:

$ cat /sys/class/dmi/id/modalias
dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr:

So, edit edit /lib/udev/hwdb.d/60-keyboard.hwdb:

evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnXPS159575:pvr*
 KEYBOARD_KEY_88=unknown

$ sudo udevadm hwdb --update
$ sudo udevadm trigger

evemu-record shows KEY_UNKNOWN:


#  Waiting for events  #

E: 0.01 0004 0004 0028  # EV_MSC / MSC_SCAN 28
E: 0.01 0001 001c   # EV_KEY / KEY_ENTER0
E: 0.01     #  SYN_REPORT (0) -- +0ms
E: 3.143316 0004 0004 0136  # EV_MSC / MSC_SCAN 136
E: 3.143316 0001 00f0 0001  # EV_KEY / KEY_UNKNOWN  1
E: 3.143316     #  SYN_REPORT (0) -- +3143ms
E: 3.143370 0004 0004 0136  # EV_MSC / MSC_SCAN 136
E: 3.143370 0001 00f0   # EV_KEY / KEY_UNKNOWN  0
E: 3.143370     #  SYN_REPORT (0) -- +0ms


>>> RESULT:
The disabling of the airplane mode works now (and enabling still works).

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

2018-11-09 Thread Jim Campbell

I've added a similar comment / request on this related launchpad bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1794655

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  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/1765304/+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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

2018-11-09 Thread Jim Campbell

The patch to resolve this bug was just accepted to upstream gnome-shell
master: see https - gitlab.gnome dot org/GNOME/gnome-
shell/merge_requests/140  (For some reason launchpad is not letting me
submit a comment with a URL).

Might it be possible to back-port this patch to GNOME Shell 3.28 for
Bionic?

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  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/1765304/+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 1740894] Re: KEY_RFKILL is not passed to userspace

2018-11-09 Thread Mario Vukelic

@Sebastien: Thank you very much. With the SRU version installed (I hope
that's right):

sudo evemu-record
Available devices:
/dev/input/event0:  Lid Switch
/dev/input/event1:  Power Button
/dev/input/event2:  Sleep Button
/dev/input/event3:  Power Button
/dev/input/event4:  AT Translated Set 2 keyboard
/dev/input/event5:  Wacom HID 486A Pen
/dev/input/event6:  Wacom HID 486A Finger
/dev/input/event7:  Intel HID events
/dev/input/event8:  Intel Virtual Button driver
/dev/input/event9:  Intel HID 5 button array
/dev/input/event10: Integrated_Webcam_HD: Integrate
/dev/input/event11: Integrated_Webcam_HD: Integrate
/dev/input/event12: DELL080D:00 06CB:7A13 Touchpad
/dev/input/event13: Dell WMI hotkeys
/dev/input/event14: Video Bus
/dev/input/event15: HDA Intel PCH Headphone Mic
/dev/input/event16: HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event17: HDA Intel PCH HDMI/DP,pcm=7
/dev/input/event18: HDA Intel PCH HDMI/DP,pcm=8
/dev/input/event19: HDA Intel PCH HDMI/DP,pcm=9
/dev/input/event20: HDA Intel PCH HDMI/DP,pcm=10
Select the device event number [0-20]: 4
# EVEMU 1.3
# Kernel: 4.18.0-11-generic
# DMI: 
dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr:
# Input device name: "AT Translated Set 2 keyboard"
# Input device ID: bus 0x11 vendor 0x01 product 0x01 version 0xab41
# Supported events:
#   Event type 0 (EV_SYN)
# Event code 0 (SYN_REPORT)
# Event code 1 (SYN_CONFIG)
# Event code 2 (SYN_MT_REPORT)
# Event code 3 (SYN_DROPPED)
# Event code 4 ((null))
# Event code 5 ((null))
# Event code 6 ((null))
# Event code 7 ((null))
# Event code 8 ((null))
# Event code 9 ((null))
# Event code 10 ((null))
# Event code 11 ((null))
# Event code 12 ((null))
# Event code 13 ((null))
# Event code 14 ((null))
# Event code 15 (SYN_MAX)
#   Event type 1 (EV_KEY)
# Event code 1 (KEY_ESC)
# Event code 2 (KEY_1)
# Event code 3 (KEY_2)
# Event code 4 (KEY_3)
# Event code 5 (KEY_4)
# Event code 6 (KEY_5)
# Event code 7 (KEY_6)
# Event code 8 (KEY_7)
# Event code 9 (KEY_8)
# Event code 10 (KEY_9)
# Event code 11 (KEY_0)
# Event code 12 (KEY_MINUS)
# Event code 13 (KEY_EQUAL)
# Event code 14 (KEY_BACKSPACE)
# Event code 15 (KEY_TAB)
# Event code 16 (KEY_Q)
# Event code 17 (KEY_W)
# Event code 18 (KEY_E)
# Event code 19 (KEY_R)
# Event code 20 (KEY_T)
# Event code 21 (KEY_Y)
# Event code 22 (KEY_U)
# Event code 23 (KEY_I)
# Event code 24 (KEY_O)
# Event code 25 (KEY_P)
# Event code 26 (KEY_LEFTBRACE)
# Event code 27 (KEY_RIGHTBRACE)
# Event code 28 (KEY_ENTER)
# Event code 29 (KEY_LEFTCTRL)
# Event code 30 (KEY_A)
# Event code 31 (KEY_S)
# Event code 32 (KEY_D)
# Event code 33 (KEY_F)
# Event code 34 (KEY_G)
# Event code 35 (KEY_H)
# Event code 36 (KEY_J)
# Event code 37 (KEY_K)
# Event code 38 (KEY_L)
# Event code 39 (KEY_SEMICOLON)
# Event code 40 (KEY_APOSTROPHE)
# Event code 41 (KEY_GRAVE)
# Event code 42 (KEY_LEFTSHIFT)
# Event code 43 (KEY_BACKSLASH)
# Event code 44 (KEY_Z)
# Event code 45 (KEY_X)
# Event code 46 (KEY_C)
# Event code 47 (KEY_V)
# Event code 48 (KEY_B)
# Event code 49 (KEY_N)
# Event code 50 (KEY_M)
# Event code 51 (KEY_COMMA)
# Event code 52 (KEY_DOT)
# Event code 53 (KEY_SLASH)
# Event code 54 (KEY_RIGHTSHIFT)
# Event code 55 (KEY_KPASTERISK)
# Event code 56 (KEY_LEFTALT)
# Event code 57 (KEY_SPACE)
# Event code 58 (KEY_CAPSLOCK)
# Event code 59 (KEY_F1)
# Event code 60 (KEY_F2)
# Event code 61 (KEY_F3)
# Event code 62 (KEY_F4)
# Event code 63 (KEY_F5)
# Event code 64 (KEY_F6)
# Event code 65 (KEY_F7)
# Event code 66 (KEY_F8)
# Event code 67 (KEY_F9)
# Event code 68 (KEY_F10)
# Event code 69 (KEY_NUMLOCK)
# Event code 70 (KEY_SCROLLLOCK)
# Event code 71 (KEY_KP7)
# Event code 72 (KEY_KP8)
# Event code 73 (KEY_KP9)
# Event code 74 (KEY_KPMINUS)
# Event code 75 (KEY_KP4)
# Event code 76 (KEY_KP5)
# Event code 77 (KEY_KP6)
# Event code 78 (KEY_KPPLUS)
# Event code 79 (KEY_KP1)
# Event code 80 (KEY_KP2)
# Event code 81 (KEY_KP3)
# Event code 82 (KEY_KP0)
# Event code 83 (KEY_KPDOT)
# Event code 85 (KEY_ZENKAKUHANKAKU)
# Event code 86 (KEY_102ND)
# Event code 87 (KEY_F11)
# Event code 88 (KEY_F12)
# Event code 89 (KEY_RO)
# Event code 90 (KEY_KATAKANA)
# Event code 91 (KEY_HIRAGANA)
# Event code 92 (KEY_HENKAN)
# Event code 93 (KEY_KATAKANAHIRAGANA)
# Event code 94 (KEY_MUHENKAN)
# Event code 95 (KEY_KPJPCOMMA)
# Event code 96 (KEY_KPENTER)
# Event code 97 (KEY_RIGHTCTRL)
# Event code 98 (KEY_KPSLASH)
# Event code 99

[Touch-packages] [Bug 1802573] [NEW] Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen

2018-11-09 Thread Adam Kessel

Public bug reported:

I have a fresh install of 18.10 on an old Thinkpad x220. Everything
works fine with the internal display or an external Dell G2410
(1920x1080) connected via VGA. But when I try to switch to an external
BenQ PD2710QC (2560x1440) I only see the screen for a few seconds at a
time and then it flashes to black. This happens consistently for minutes
--it never "settles down".

I've tried the default configuration as well as copying xorg.conf from
/usr/share/doc/xserver-xorg-video-intel into /etc/x11. I've tried both
xorg configurations with nomodeset in the bootloader and without. I have
not been able to find any configuration that allows this external
DisplayPort display to work.

The same hardware combination works fine in Windows 10.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
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: Fri Nov  9 13:10:59 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
InstallationDate: Installed on 2018-11-09 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: LENOVO 42872WU
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=cd4f21be-48dd-48e7-b289-a59a32bd0be3 ro quiet splash nomodeset 
vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf:
 Section "Device"
Identifier "Intel"
Driver "intel"
 #  Option "AccelMethod" "uxa"
 EndSection
dmi.bios.date: 06/21/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET76WW (1.46 )
dmi.board.asset.tag: Not Available
dmi.board.name: 42872WU
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn42872WU:pvrThinkPadX220:rvnLENOVO:rn42872WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X220
dmi.product.name: 42872WU
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic 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/1802573

Title:
  Thinkpad x220 - Unable to use 2560x1440 external display connected via
  DisplayPort due flashing black screen

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a fresh install of 18.10 on an old Thinkpad x220. Everything
  works fine with the internal display or an external Dell G2410
  (1920x1080) connected via VGA. But when I try to switch to an external
  BenQ PD2710QC (2560x1440) I only see the screen for a few seconds at a
  time and then it flashes to black. This happens consistently for
  minutes--it never "settles down".

  I've tried the default configuration as well as copying xorg.conf from
  /usr/share/doc/xserver-xorg-video-intel into /etc/x11. I've tried both
  xorg configurations with nomodeset in the bootloader and without. I
  have not been able to find any configuration that allows this external
  DisplayPort display to work.

  The same hardware combination works fine in Windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  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: Fri Nov  9 13:10:59 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation

[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

2018-11-09 Thread Jeremy Bicha

systemd uses pcre2 for a useful journal feature that we can't enable
until pcre2 is in main LP: #1751006

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

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

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Triaged
Status in libpam-mount package in Ubuntu:
  Triaged
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in php7.3 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 874535] Re: Volume Slider Jumps, due to rapidly changing hardware jack sense state

2018-11-09 Thread rjurado

I've also got this problem in 18.04 with a Gigabyte motherboard.

When I use front jack input the problem disappears.

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

Title:
  Volume Slider Jumps, due to rapidly changing hardware jack sense state

Status in alsa-driver package in Ubuntu:
  Triaged

Bug description:
  In Oneiric Release,  The volume slider randomly jump down a notch or
  two for fraction of  a second, even when there is no audio playing on
  the system.  If mute is selected, the menu will quickly flip out of
  mute mode and back again.  This change actually affects the audio
  output, resulting in pops correlated with the volume changes.

  nVidia GF106 Audio Controller
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC892 Analog [ALC892 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jfrorie9959 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfb9f8000 irq 54'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,1462522c,00100302'
 Controls  : 35
 Simple ctrls  : 20
  Card2.Amixer.info:
   Card hw:2 'Generic'/'HD-Audio Generic at 0xfbcf8000 irq 55'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  Package: pulseaudio 1:1.0-0ubuntu3.1
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-14-generic x86_64
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (82 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 11/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: X58A-GD45 (MS-7522)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd11/16/2010:svnMSI:pnMS-7522:pvr5.0:rvnMSI:rnX58A-GD45(MS-7522):rvr5.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr5.0:
  dmi.product.name: MS-7522
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874535/+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 1740894] Re: KEY_RFKILL is not passed to userspace

I believe the issue was originally created by that systemd change,
https://github.com/systemd/systemd/pull/8762

I've submitted a revert on https://github.com/systemd/systemd/pull/10709

That change is going to have things working as designed, at least on the
Inspiron but I'm unsure your issue is the same one at this point. We
should probably reject the SRU though, or it would need to go with the
systemd change to avoid the regression (but it might still impact on
some models)

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-11-09 Thread Abhishek Sharma

I'm also having an issue with my ux391ua running MATE18.04 with no
Windows 10 installed. There is sound output audible with headphones on
and volume >100% but it is very distorted and crackly. 18.10 was not
helpful and updating kerenel to 19 doesn't change anything.

aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

pacmd list-cards
1 card(s) available.
index: 0
name: 
driver: 
owner module: 7
properties:
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xec228000 irq 135"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1f.3"
sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "9d71"
device.product.name = "Sunrise Point-LP HD Audio"
device.form_factor = "internal"
device.string = "0"
device.description = "Built-in Audio"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"

I've tried various mixer related avenues which do nothing. I noticed
that pavucontrol shows sound btw.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1802525] Re: (s)ata disks do not have /dev/disk/by-path links created

2018-11-09 Thread Dan Streetman

** Description changed:

  [impact]
  
  udev (in trusty) does not create symlinks in /dev/disk/by-path/ for any
  disks that are connected via sata.
  
  [test case]
  
  Install trusty onto a system with sata drives, and check /dev/disk/by-
  path/ for symlink(s) to those sata drive(s).
  
  [regression potential]
  
  the (s)ata by-path symlinks were removed due to apparent possibility of 
non-uniqueness:
  https://git.kernel.org/pub/scm/linux/hotplug/udev.git/commit/?id=481dcf7c8f
  
  however that was *long* ago and it has been added back in:
  
https://github.com/systemd/systemd/commit/ba86822db70d9ffd02ad78cd02b237ff8c569c7a
  
  if there is still a possibility for non-uniqueness, then /dev/disk/by-
  path/ symlink(s) might be created that are non-deterministic as far as
  the actual disk/path they point to.
+ 
+ [other info]
+ 
+ this is 'fixed' (the by-path symlinks are created for ata disks) in
+ Xenial and later systemd/udev.
+ 
+ Also bug 1611945 indicates that sata devices connected via PMP (port
+ multiplier device) may still have incorrect by-path symlinks created,
+ even upstream.

** Description changed:

  [impact]
  
  udev (in trusty) does not create symlinks in /dev/disk/by-path/ for any
  disks that are connected via sata.
  
  [test case]
  
  Install trusty onto a system with sata drives, and check /dev/disk/by-
  path/ for symlink(s) to those sata drive(s).
  
  [regression potential]
  
  the (s)ata by-path symlinks were removed due to apparent possibility of 
non-uniqueness:
  https://git.kernel.org/pub/scm/linux/hotplug/udev.git/commit/?id=481dcf7c8f
  
  however that was *long* ago and it has been added back in:
  
https://github.com/systemd/systemd/commit/ba86822db70d9ffd02ad78cd02b237ff8c569c7a
  
  if there is still a possibility for non-uniqueness, then /dev/disk/by-
  path/ symlink(s) might be created that are non-deterministic as far as
  the actual disk/path they point to.
  
  [other info]
  
  this is 'fixed' (the by-path symlinks are created for ata disks) in
  Xenial and later systemd/udev.
  
  Also bug 1611945 indicates that sata devices connected via PMP (port
  multiplier device) may still have incorrect by-path symlinks created,
- even upstream.
+ even upstream.  However, since Xenial and later currently do have udev
+ code that creates ata by-path symlinks, that is a separate issue and not
+ a reason for keeping ata by-path symlinks about of trusty udev.

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

Title:
  (s)ata disks do not have /dev/disk/by-path links created

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  In Progress

Bug description:
  [impact]

  udev (in trusty) does not create symlinks in /dev/disk/by-path/ for
  any disks that are connected via sata.

  [test case]

  Install trusty onto a system with sata drives, and check /dev/disk/by-
  path/ for symlink(s) to those sata drive(s).

  [regression potential]

  the (s)ata by-path symlinks were removed due to apparent possibility of 
non-uniqueness:
  https://git.kernel.org/pub/scm/linux/hotplug/udev.git/commit/?id=481dcf7c8f

  however that was *long* ago and it has been added back in:
  
https://github.com/systemd/systemd/commit/ba86822db70d9ffd02ad78cd02b237ff8c569c7a

  if there is still a possibility for non-uniqueness, then /dev/disk/by-
  path/ symlink(s) might be created that are non-deterministic as far as
  the actual disk/path they point to.

  [other info]

  this is 'fixed' (the by-path symlinks are created for ata disks) in
  Xenial and later systemd/udev.

  Also bug 1611945 indicates that sata devices connected via PMP (port
  multiplier device) may still have incorrect by-path symlinks created,
  even upstream.  However, since Xenial and later currently do have udev
  code that creates ata by-path symlinks, that is a separate issue and
  not a reason for keeping ata by-path symlinks about of trusty udev.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1802525/+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 1648877] Re: Wrong include path to sphinx_config.h

2018-11-09 Thread Silvano Sallese

Hi,

Although on Xenial the problem is solved, I'm having same problem on
Bionic where is installed the libsphinxbase-dev 0.8+5prealpha+1-1.

I need to modify the following sources:

/usr/include/x86_64-linux-gnu/sphinxbase/ad.h
/usr/include/x86_64-linux-gnu/sphinxbase/prim_type.h

changing from "#include " to #include
.

Thanks.

Regards,
Silvano

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

Title:
Wrong include path to sphinx_config.h

Status in sphinxbase package in Ubuntu:
Fix Released

Bug description:
Hi,

This bug appears in more than one Ubuntu 16.04.1 system where I
install the libsphinxbase-dev package through apt.

Some include files have wrong path to the sphinx_config.h header file.

When compiling my code, the header files listed below cause to tell
that there is not a sphinx_config.h file (but it's located in
/usr/include/x86_64-linux-gnu/sphinxbase/).

In order to compile my code I had to modify the following .h files
under the /usr/include/x86_64-linux-gnu/sphinxbase/ system path.

The following corrections solved the issue.

In the file /usr/include/x86_64-linux-gnu/sphinxbase/ad.h at line 44
In the file /usr/include/x86_64-linux-gnu/sphinxbase/prim_type.h at line 88
In the file /usr/include/x86_64-linux-gnu/sphinxbase/sbthread.h at line 46

changed from this
#include
to this
#include

I hope this could help to update the package.
I use sphinxbase on other systems and I hope in the future I don't need to
touch the system files.

For completeness:
- this is not happening on Ubuntu 14.04.* systems, but I know the versions
are heavily different.

- Source:
http://archive.ubuntu.com/ubuntu/pool/universe/s/sphinxbase/sphinxbase_0.8+5prealpha.orig.tar.gz
the files are in /sphinxbase-5prealpha/include/sphinxbase/

- Package: libsphinxbase-dev

- Package version: 0.8+5prealpha-2ubuntu1

Thank you.

Best regards,
Silvano

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sphinxbase/+bug/1648877/+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 1802525] [NEW] (s)ata disks do not have /dev/disk/by-path links created

2018-11-09 Thread Dan Streetman

Public bug reported:

[impact]

udev (in trusty) does not create symlinks in /dev/disk/by-path/ for any
disks that are connected via sata.

[test case]

Install trusty onto a system with sata drives, and check /dev/disk/by-
path/ for symlink(s) to those sata drive(s).

[regression potential]

the (s)ata by-path symlinks were removed due to apparent possibility of 
non-uniqueness:
https://git.kernel.org/pub/scm/linux/hotplug/udev.git/commit/?id=481dcf7c8f

however that was *long* ago and it has been added back in:
https://github.com/systemd/systemd/commit/ba86822db70d9ffd02ad78cd02b237ff8c569c7a

if there is still a possibility for non-uniqueness, then /dev/disk/by-
path/ symlink(s) might be created that are non-deterministic as far as
the actual disk/path they point to.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: systemd (Ubuntu Trusty)
 Importance: Low
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

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

** Changed in: systemd (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu Trusty)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

Title:
  (s)ata disks do not have /dev/disk/by-path links created

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  In Progress

Bug description:
  [impact]

  udev (in trusty) does not create symlinks in /dev/disk/by-path/ for
  any disks that are connected via sata.

  [test case]

  Install trusty onto a system with sata drives, and check /dev/disk/by-
  path/ for symlink(s) to those sata drive(s).

  [regression potential]

  the (s)ata by-path symlinks were removed due to apparent possibility of 
non-uniqueness:
  https://git.kernel.org/pub/scm/linux/hotplug/udev.git/commit/?id=481dcf7c8f

  however that was *long* ago and it has been added back in:
  
https://github.com/systemd/systemd/commit/ba86822db70d9ffd02ad78cd02b237ff8c569c7a

  if there is still a possibility for non-uniqueness, then /dev/disk/by-
  path/ symlink(s) might be created that are non-deterministic as far as
  the actual disk/path they point to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1802525/+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 1740894] Re: KEY_RFKILL is not passed to userspace

@Mario, could you copy the list of devices from "sudo evemu-record" and
a log of the record from the keyboard after pressing the key once?

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1802521] [NEW] ubuntu-bug hangs when Cancel button pressed

2018-11-09 Thread Jonathan Kamens

Public bug reported:

I ran `ubuntu-bug gnome-terminal`, but then realized a second or so
later that's not what I had intended to do. I therefore clicked the
Cancel button on the "Collecting problem information / Information is
being collected that may help the developers fix the problem you
report." dialog that had popped up. It hung, i.e., the back-and-forth
progress bar in the dialog stopped moving, and nothing else happened,
and it's still sitting several minutes later doing nothing.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: apport 2.20.10-0ubuntu13
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
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov  9 09:21:14 2018
InstallationDate: Installed on 2018-09-27 (42 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to cosmic on 2018-11-08 (0 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

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


** Tags: amd64 apport-bug cosmic

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

Title:
  ubuntu-bug hangs when Cancel button pressed

Status in apport package in Ubuntu:
  New

Bug description:
  I ran `ubuntu-bug gnome-terminal`, but then realized a second or so
  later that's not what I had intended to do. I therefore clicked the
  Cancel button on the "Collecting problem information / Information is
  being collected that may help the developers fix the problem you
  report." dialog that had popped up. It hung, i.e., the back-and-forth
  progress bar in the dialog stopped moving, and nothing else happened,
  and it's still sitting several minutes later doing nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu13
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  9 09:21:14 2018
  InstallationDate: Installed on 2018-09-27 (42 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (0 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1802521/+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 604333] Re: Every second screenshot in created screenshot gallery is just a duplicate of the previous.

2018-11-09 Thread Bug Watch Updater

** Changed in: totem
   Status: Confirmed => Expired

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

Title:
  Every second screenshot in created screenshot gallery is just a
  duplicate of the previous.

Status in Totem:
  Expired
Status in gstreamer0.10 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: totem

  I attached an example.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: totem 2.30.2-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic i686
  Architecture: i386
  Date: Sun Jul 11 18:24:40 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.utf8
   SHELL=/bin/bash
  SourcePackage: totem

To manage notifications about this bug go to:
https://bugs.launchpad.net/totem/+bug/604333/+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 1802512] [NEW] xorg does not work

2018-11-09 Thread Dawid Słowik

Public bug reported:

I;m usin geforce 8800GT

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus..1c.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:1c:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
 GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
Date: Fri Nov  9 14:40:24 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus: nvidia-340, 340.107, 4.18.0-10-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) 
(prog-if 00 [VGA controller])
InstallationDate: Installed on 2018-11-09 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Micro-Star International Co., Ltd MS-7C02
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=a037c8bc-adce-4a23-9b98-d6cd7b029fe0 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.00
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450 TOMAHAWK (MS-7C02)
dmi.board.vendor: Micro-Star International Co., Ltd
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.00:bd07/02/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C02
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
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.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic 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/1802512

Title:
  xorg does not work

Status in xorg package in Ubuntu:
  New

Bug description:
  I;m usin geforce 8800GT

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..1c.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:1c:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Fri Nov  9 14:40:24 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.107, 4.18.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:

[Touch-packages] [Bug 1802504] [NEW] TILIX INFO

2018-11-09 Thread François ZOLIN

Public bug reported:

TILIX SCREEN AFTER "SUDO APT UPDATE"
Сущ:13 http://fr.archive.ubuntu.com/ubuntu bionic-proposed InRelease
  
Сущ:14 http://ppa.launchpad.net/tista/adapta/ubuntu bionic InRelease
  
Сущ:15 http://security.ubuntu.com/ubuntu artful-security InRelease  
  
Сущ:16 http://ppa.launchpad.net/ubuntubudgie/backports/ubuntu bionic InRelease  
  
Сущ:17 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu bionic InRelease  
   
Получено 83,2 kB за 2с (48,8 kB/s)   
Чтение списков пакетов… Готово
Построение дерева зависимостей   
Чтение информации о состоянии… Готово
Все пакеты имеют последние версии.
W: Цель Sources (main/source/Sources) настроена несколько раз в 
/etc/apt/sources.list:54 и /etc/apt/sources.list:55
W: Пропускается получение настроенного файла «main/source/Sources», так как 
репозиторий «https://dl.winehq.org/wine-builds/ubuntu bionic InRelease» его не 
предоставляет (возможно, репозиторий указан с ошибкой в sources.list?)
W: Цель Sources (main/source/Sources) настроена несколько раз в 
/etc/apt/sources.list.d/ubuntubudgie-ubuntu-backports-artful.list:2 и 
/etc/apt/sources.list.d/ubuntubudgie-ubuntu-backports-bionic.list:1
W: Цель Sources (main/source/Sources) настроена несколько раз в 
/etc/apt/sources.list:54 и /etc/apt/sources.list:55
W: Цель Sources (main/source/Sources) настроена несколько раз в 
/etc/apt/sources.list.d/ubuntubudgie-ubuntu-backports-artful.list:2 и 
/etc/apt/sources.list.d/ubuntubudgie-ubuntu-backports-bionic.list:1

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  410.73  Sat Oct 20 22:12:33 
CDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: Budgie:GNOME
Date: Fri Nov  9 14:11:37 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 410.73, 4.15.0-39-generic, x86_64: installed
 virtualbox, 5.2.18, 4.15.0-33-generic, x86_64: installed
 virtualbox, 5.2.18, 4.15.0-39-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GM204M [GeForce GTX 970M] [1043:22da]
InstallationDate: Installed on 2017-12-29 (314 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 
(20170926)
MachineType: ASUSTeK COMPUTER INC. G751JT
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=3b41e99c-b074-4029-826b-39ad3587 ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G751JT.202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G751JT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG751JT.202:bd09/10/2014:svnASUSTeKCOMPUTERINC.:pnG751JT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG751JT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G751JT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu Nov  8 15:34:32 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.2

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


** Tags: amd64 apport-bug bionic ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.

[Touch-packages] [Bug 1061195] Re: Evolution appears unable to create EWS or Exchange MAPI account

2018-11-09 Thread Stephan Prätsch

Confirmed on Ubuntu 18.04.1 LTS, Evolution 3.28.5-0ubuntu0.18.04.1,
using EWS.

The usual workaround (delete cfg, cache and pkill) works fine.
https://askubuntu.com/questions/459504/evolution-appears-unable-to-store-mail-account-details

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

Title:
  Evolution appears unable to create EWS or Exchange MAPI account

Status in evolution-ews:
  Expired
Status in evolution package in Ubuntu:
  Triaged
Status in evolution-data-server package in Ubuntu:
  Triaged
Status in evolution-ews package in Ubuntu:
  Triaged
Status in evolution-mapi package in Ubuntu:
  Won't Fix

Bug description:
  Evolution appears unable to create an EW or MAPI account. All the
  steps proceed normally, including fetching the URL (for EWS) or
  authenticating (for MAPI). However, at the conclusion of account
  creation process, no actual account appears in the list.

  I've tried starting Evolution from the command line using various
  DEBUG_ variables and there are no EWS- or MAPI-specific errors. So I'm
  not exactly sure what to do next.

  I am fairly certain the problem doesn't lie with my corporate Exchange
  server, as web mail works fine and any other EWS-capable client (like
  the mail app in Android).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: evolution 3.6.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  3 12:40:28 2012
  InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Beta amd64 
(20120925)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-ews/+bug/1061195/+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 1797224] Re: Stay on 2.0 for cosmic, update next cycle

2018-11-09 Thread Jeremy Bicha

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

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

Title:
  Stay on 2.0 for cosmic, update next cycle

Status in tracker package in Ubuntu:
  Triaged

Bug description:
  The new version requires the MIR situation to be sorted out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1797224/+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 1740894] Re: KEY_RFKILL is not passed to userspace

Ok, so after some debugging the fix is working but it hits a bug on some
Dell laptops

>From my Inspirong 11 debugging
- sudo evemu-record 

press the airplane key
-> double events are generated

then to fix it
- cat /sys/class/dmi/id/modalias and see what the "pn" is
- edit /lib/udev/hwdb.d/60-keyboard.hwdb and add a section (adapt the 
'Inspiron*3138' according your 'pn' from the previous command)

"#disable double airplane key events on Inspiron 3138
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnInspiron*3138:pvr*
 KEYBOARD_KEY_88=unknown"

- sudo udevadm hwdb --update
- sudo udevadm trigger

try again, the flackyness should be fixed (and the event record should
show "unknow" keys now)

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xkeyboard-config source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1802498] Re: AppArmor - Error Messages log files - Mensagens de Erro arquivos de log

2018-11-09 Thread Edson José dos Santos

** Attachment added: 
"1300661580_Capturadetelade2018-11-0715-25-33.png.8d71b9001fd8d3da9071dfeacf640e3d.png"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1802498/+attachment/5210799/+files/1300661580_Capturadetelade2018-11-0715-25-33.png.8d71b9001fd8d3da9071dfeacf640e3d.png

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

Title:
  AppArmor - Error Messages log files - Mensagens de Erro arquivos de
  log

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hello Canonical team - Ubuntu

  Eset Antivirus has some problems with apparmor.

  In Eset I have observed in the last weeks that the updates are being
  carried out, but the logs that have been installed successfully, where
  it was in bold, no longer appear.

  I also realize that these error messages below are constants and I
  would like to know what it is possible to do to resolve them, as they
  are due to mismatch with apparmor. Can Canonial and Eset work together
  to solve this problem?

  Here is the log of Eset Antivirus for Linux Version 4.90 installed on
  Ubuntu 18.10 Cosmic and log dmesg of Ubuntu.

  Thank you in advance for the attention and collaboration of all

  Edson Santos

  

  Obs: Most of these problems are caused by AppArmor , ESET v4 is not
  compatible with AppArmor/SELinux

  I've tried to test things here and there , ESET still does do it's job
  while AppArmor is enabled (I didn't try with AppArmor disabled) , but
  it encounters lot of errors , and while scanning AppArmor will prevent
  ESET from accessing most files as far as I have noticed.

  I don't know if there is a workaround for AppArmor to allow ESET , but
  I don't want to disable it and I don't want to remove ESET.

  
  Thank you in advance for the attention and collaboration of all

  
  Edson Santos

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1802498/+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 1802498] [NEW] AppArmor - Error Messages log files - Mensagens de Erro arquivos de log

2018-11-09 Thread Edson José dos Santos

Public bug reported:

Hello Canonical team - Ubuntu

Eset Antivirus has some problems with apparmor.

In Eset I have observed in the last weeks that the updates are being
carried out, but the logs that have been installed successfully, where
it was in bold, no longer appear.

I also realize that these error messages below are constants and I would
like to know what it is possible to do to resolve them, as they are due
to mismatch with apparmor. Can Canonial and Eset work together to solve
this problem?

Here is the log of Eset Antivirus for Linux Version 4.90 installed on
Ubuntu 18.10 Cosmic and log dmesg of Ubuntu.

Thank you in advance for the attention and collaboration of all

Edson Santos



Obs: Most of these problems are caused by AppArmor , ESET v4 is not
compatible with AppArmor/SELinux

I've tried to test things here and there , ESET still does do it's job
while AppArmor is enabled (I didn't try with AppArmor disabled) , but it
encounters lot of errors , and while scanning AppArmor will prevent ESET
from accessing most files as far as I have noticed.

I don't know if there is a workaround for AppArmor to allow ESET , but I
don't want to disable it and I don't want to remove ESET.


Thank you in advance for the attention and collaboration of all


Edson Santos

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

** Attachment added: "AppArmor - Error Messages log files - Mensagens de Erro 
arquivos de log"
   
https://bugs.launchpad.net/bugs/1802498/+attachment/5210798/+files/AppArmor%20-%20Error%20Messages%20log%20files%20-%20Mensagens%20de%20Erro%20arquivos%20de%20log

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

Title:
  AppArmor - Error Messages log files - Mensagens de Erro arquivos de
  log

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hello Canonical team - Ubuntu

  Eset Antivirus has some problems with apparmor.

  In Eset I have observed in the last weeks that the updates are being
  carried out, but the logs that have been installed successfully, where
  it was in bold, no longer appear.

  I also realize that these error messages below are constants and I
  would like to know what it is possible to do to resolve them, as they
  are due to mismatch with apparmor. Can Canonial and Eset work together
  to solve this problem?

  Here is the log of Eset Antivirus for Linux Version 4.90 installed on
  Ubuntu 18.10 Cosmic and log dmesg of Ubuntu.

  Thank you in advance for the attention and collaboration of all

  Edson Santos

  

  Obs: Most of these problems are caused by AppArmor , ESET v4 is not
  compatible with AppArmor/SELinux

  I've tried to test things here and there , ESET still does do it's job
  while AppArmor is enabled (I didn't try with AppArmor disabled) , but
  it encounters lot of errors , and while scanning AppArmor will prevent
  ESET from accessing most files as far as I have noticed.

  I don't know if there is a workaround for AppArmor to allow ESET , but
  I don't want to disable it and I don't want to remove ESET.

  
  Thank you in advance for the attention and collaboration of all

  
  Edson Santos

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1802498/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace

2018-11-09 Thread Ubuntu Foundations Team Bug Bot

The attachment "libnotify_0.7.7-3+snap-support.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Notifications emitted by a snap with local files or desktop files use
  wrong namespace

Status in libnotify package in Ubuntu:
  In Progress

Bug description:
  As can be tested using this example snap:
   - https://github.com/3v1n0/notify-send-test-snap

  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on
  $SNAP location.

  As we do with appindicators and libunity emblems.

  

  
  [ Impact ]

  Icons sonuds and desktop files referenced by a snapped app using
  notifications aren't exposed to the desktop in absolute paths

  [ Test case ]

  Build the test snap:
git clone https://github.com/3v1n0/notify-send-test-snap
snapcraft prime
snap try prime

  Check that icons are shown when launching:
notify-send-test-snap
notify-send-test-snap.image-path

  Running them with G_MESSAGES_DEBUG=all should provide translation
  logging

  [ Regression potential ]

  Normal applications that are run with a SNAP environment variable set,
  might use wrong paths for files or desktop file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1802497] [NEW] cannot open a VT2

2018-11-09 Thread Olivier Hallot

Public bug reported:

On switching to a new session, the existing session is closed and the
new opens at the same VT1.

Xorg crashes and restart, thus assigning VT1

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Nov  9 10:02:07 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-38-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:056e]
 Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
InstallationDate: Installed on 2018-05-10 (182 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. Vostro 3560
ProcEnviron:
 LANGUAGE=pt_BR:en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-38-generic 
root=UUID=89a47e85-475c-4f6c-a0d8-d3aae572e9a5 ro rootflags=subvol=@ 
plymouth:debug=1=1 vesafb.invalid=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/14/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0R9N46
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A17
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd04/14/2014:svnDellInc.:pnVostro3560:pvrA17:rvnDellInc.:rn0R9N46:rvrA01:cvnDellInc.:ct8:cvrA17:
dmi.product.family: 103C_5335KV
dmi.product.name: Vostro 3560
dmi.product.version: A17
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1802497

Title:
  cannot open a VT2

Status in xorg package in Ubuntu:
  New

Bug description:
  On switching to a new session, the existing session is closed and the
  new opens at the same VT1.

  Xorg crashes and restart, thus assigning VT1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Nov  9 10:02:07 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:056e]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-05-10 (182 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Vostro 3560
  ProcEnviron:
   LANGUAGE=pt_BR:en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-38-generic 
root=UUID=89a47e85-475c-4f6c-a0d8-d3aae572e9a5 ro rootflags=subvol=@ 
plymouth:debug=1=1 vesafb.invalid=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0R9N46
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version:

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-11-09 Thread Skander Guarbàa

Guys ..
I have Nvidia 1050ti with nvidia-390 driver installed.

When i boot am on 900 resolution instead of a 1920x1080 normal
resolution.

Anyone got a solution for that ??

Thanks in advance.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

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

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

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

[Touch-packages] [Bug 1783903] Re: DHCP Renewal Kills Anyconnect VPN Connections

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

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

Title:
  DHCP Renewal Kills Anyconnect VPN Connections

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When using the Cisco Anyconnect client to connect to my works VPN. The
  VPN is unstable and drops into re configuring mode when a DHCP request
  is sent. From my research if I remove the network-manager-config-
  connectivity-ubuntu package the connection is stable.

  Similar Issues for like package with FC28:
  https://bugzilla.redhat.com/show_bug.cgi?id=1576910

  Description:  Linux Mint 19 Tara
  Release:  19

  network-manager:
    Installed: 1.10.6-2ubuntu1
    Candidate: 1.10.6-2ubuntu1
    Version table:
   *** 1.10.6-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  network-manager-config-connectivity-ubuntu:
    Installed: 1.10.6-2ubuntu1
    Candidate: 1.10.6-2ubuntu1
    Version table:
   *** 1.10.6-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  Log attached next comment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1783903/+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 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia

2018-11-09 Thread Julian Gilbey

And the Qt team are now working on implementing the patch, so this
should be resolving in a forthcoming Qt release :-)  See
https://bugreports.qt.io/browse/QTBUG-71488

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

Title:
  dlopen(libGL.so) resolves to mesa rather than nvidia

Status in NVIDIA Drivers Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in pyqt5 package in Ubuntu:
  Invalid
Status in python-qt4 package in Ubuntu:
  Invalid

Bug description:
  I'm having trouble with a combination of NVIDIA + Python + Qt +
  Opengl.

  I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and 
errors like this these:
  QGLShader: could not create shader
  Vertex shader for simpleShaderProg (MainVertexShader 
) failed to compile

  This is an example application triggering the problem:
  http://pastebin.com/R0aa8ejs

  The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact 
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this 
error when trying the original demo application from python-qt4-doc. Also, 
calling
  QtGui.QApplication.setGraphicsSystem("opengl")
  produces the same errors.

  I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
  provided nvidia drivers (where 12.04 includes the most recent driver
  for now). After installing the driver using the original NVidia
  installer, the applications work as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace

** Description changed:

  As can be tested using this example snap:
-  - https://github.com/3v1n0/notify-send-test-snap
+  - https://github.com/3v1n0/notify-send-test-snap
  
  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on $SNAP
  location.
  
- As we do with appindicators and libunity emblems
+ As we do with appindicators and libunity emblems.
+ 
+ 
+ 
+ 
+ [ Impact ]
+ 
+ Icons sonuds and desktop files referenced by a snapped app using
+ notifications aren't exposed to the desktop in absolute paths
+ 
+ [ Test case ]
+ 
+ Build the test snap:
+   git clone https://github.com/3v1n0/notify-send-test-snap
+   snapcraft prime
+   snap try prime
+ 
+ Check that icons are shown when launching:
+   notify-send-test-snap
+   notify-send-test-snap.image-path
+ 
+ Running them with G_MESSAGES_DEBUG=all should provide translation
+ logging
+ 
+ [ Regression potential ]
+ 
+ Normal applications that are run with a SNAP environment variable set,
+ might use wrong paths for files or desktop file

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

Title:
  Notifications emitted by a snap with local files or desktop files use
  wrong namespace

Status in libnotify package in Ubuntu:
  In Progress

Bug description:
  As can be tested using this example snap:
   - https://github.com/3v1n0/notify-send-test-snap

  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on
  $SNAP location.

  As we do with appindicators and libunity emblems.

  

  
  [ Impact ]

  Icons sonuds and desktop files referenced by a snapped app using
  notifications aren't exposed to the desktop in absolute paths

  [ Test case ]

  Build the test snap:
git clone https://github.com/3v1n0/notify-send-test-snap
snapcraft prime
snap try prime

  Check that icons are shown when launching:
notify-send-test-snap
notify-send-test-snap.image-path

  Running them with G_MESSAGES_DEBUG=all should provide translation
  logging

  [ Regression potential ]

  Normal applications that are run with a SNAP environment variable set,
  might use wrong paths for files or desktop file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia

2018-11-09 Thread Julian Gilbey

I have found the source of the bug and provided a patch: see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913287

** Bug watch added: Debian Bug tracker #913287
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913287

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

Title:
  dlopen(libGL.so) resolves to mesa rather than nvidia

Status in NVIDIA Drivers Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in pyqt5 package in Ubuntu:
  Invalid
Status in python-qt4 package in Ubuntu:
  Invalid

Bug description:
  I'm having trouble with a combination of NVIDIA + Python + Qt +
  Opengl.

  I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and 
errors like this these:
  QGLShader: could not create shader
  Vertex shader for simpleShaderProg (MainVertexShader 
) failed to compile

  This is an example application triggering the problem:
  http://pastebin.com/R0aa8ejs

  The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact 
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this 
error when trying the original demo application from python-qt4-doc. Also, 
calling
  QtGui.QApplication.setGraphicsSystem("opengl")
  produces the same errors.

  I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
  provided nvidia drivers (where 12.04 includes the most recent driver
  for now). After installing the driver using the original NVidia
  installer, the applications work as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+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 1789924] Re: Missing Intel GPU pci-id's

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

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

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1789924] Re: Missing Intel GPU pci-id's

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

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

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1789924] Re: Missing Intel GPU pci-id's

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

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

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace

Fix for disco (but could be used for bionic too) is at:

https://code.launchpad.net/~canonical-desktop-
team/ubuntu/+source/libnotify/+git/libnotify/+ref/ubuntu/master

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

Title:
  Notifications emitted by a snap with local files or desktop files use
  wrong namespace

Status in libnotify package in Ubuntu:
  In Progress

Bug description:
  As can be tested using this example snap:
   - https://github.com/3v1n0/notify-send-test-snap

  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on
  $SNAP location.

  As we do with appindicators and libunity emblems.

  

  
  [ Impact ]

  Icons sonuds and desktop files referenced by a snapped app using
  notifications aren't exposed to the desktop in absolute paths

  [ Test case ]

  Build the test snap:
git clone https://github.com/3v1n0/notify-send-test-snap
snapcraft prime
snap try prime

  Check that icons are shown when launching:
notify-send-test-snap
notify-send-test-snap.image-path

  Running them with G_MESSAGES_DEBUG=all should provide translation
  logging

  [ Regression potential ]

  Normal applications that are run with a SNAP environment variable set,
  might use wrong paths for files or desktop file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1802489] [NEW] Xorg freeze

2018-11-09 Thread Benjamin Drung

Public bug reported:

After upgrading to Ubuntu 18.10, the system won't boot any more
correctly. When booting, it will get stuck at a purple screen and never
show the login screen. Selecting the recovery boot in GRUB and continue
the boot in the recovery boots the system correctly. dmesg shows a
kernel warning:

[   19.856655] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
[   19.856665] WARNING: CPU: 3 PID: 1742 at mm/usercopy.c:81 
usercopy_warn+0x81/0xa0
[   19.856665] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc devlink 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter 
binfmt_misc nvidia_uvm(POE) eeepc_wmi asus_wmi wmi_bmof sparse_keymap joydev 
intel_rapl cp210x usbserial x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel snd_hda_codec_hdmi input_leds snd_hda_codec_realtek kvm 
snd_hda_codec_generic irqbypass crct10dif_pclmul snd_hda_intel crc32_pclmul 
ghash_clmulni_intel pcbc snd_hda_codec snd_hda_core snd_hwdep snd_pcm 
nvidia_drm(POE) snd_seq_midi aesni_intel nvidia_modeset(POE) snd_seq_midi_event 
aes_x86_64 crypto_simd cryptd glue_helper intel_cstate snd_rawmidi
[   19.856694]  intel_rapl_perf nvidia(POE) serio_raw i915 snd_seq 
drm_kms_helper drm snd_seq_device ipmi_devintf snd_timer snd ipmi_msghandler 
i2c_algo_bit fb_sys_fops syscopyarea sysfillrect soundcore sysimgblt video 
mac_hid mei_me mei wmi sch_fq_codel parport_pc ppdev lp parport ip_tables 
x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid hid pata_acpi gpio_ich psmouse ahci libahci 
i2c_i801 lpc_ich r8169 mii pata_via
[   19.856722] CPU: 3 PID: 1742 Comm: Xorg Tainted: P   OE 
4.18.0-11-generic #12-Ubuntu
[   19.856722] Hardware name: System manufacturer System Product Name/P8H67-M 
PRO, BIOS 3904 04/27/2013
[   19.856724] RIP: 0010:usercopy_warn+0x81/0xa0
[   19.856725] Code: 90 a2 41 51 4d 89 d8 48 c7 c0 89 8d 8f a2 49 89 f1 48 89 
f9 48 0f 45 c2 48 c7 c7 f0 a1 90 a2 4c 89 d2 48 89 c6 e8 f1 cf df ff <0f> 0b 48 
83 c4 18 c9 c3 48 c7 c6 b2 8a 92 a2 49 89 f1 49 89 f3 eb 
[   19.856746] RSP: 0018:bb3002583b08 EFLAGS: 00010286
[   19.856747] RAX:  RBX: 935d57f65cb0 RCX: 0006
[   19.856748] RDX: 0007 RSI: 0096 RDI: 935d6f3964b0
[   19.856749] RBP: bb3002583b20 R08: 0001 R09: 0478
[   19.856750] R10: 0001 R11:  R12: 0003
[   19.856750] R13: 0001 R14: 935d57f65cb3 R15: 935d57f65cf8
[   19.856752] FS:  7fe7a307da80() GS:935d6f38() 
knlGS:
[   19.856752] CS:  0010 DS:  ES:  CR0: 80050033
[   19.856753] CR2: 7fe79f700110 CR3: 000414d06006 CR4: 000606e0
[   19.856754] Call Trace:
[   19.856759]  __check_heap_object+0xc2/0x110
[   19.856761]  __check_object_size+0x14c/0x178
[   19.856895]  os_memcpy_to_user+0x26/0x50 [nvidia]
[   19.857044]  _nv009384rm+0xbf/0xe0 [nvidia]
[   19.857045] WARNING: kernel stack frame pointer at 05649f90 in 
Xorg:1742 has bad value 892d8e62
[   19.857047] unwind stack type:0 next_sp:  (null) mask:0x2 graph_idx:0
[   19.857048] ec2c30aa: bb3002583b30 (0xbb3002583b30)
[   19.857049] cadd4750: a1a69a82 
(__check_heap_object+0xc2/0x110)
[   19.857050] e8e36824: bb3002583b60 (0xbb3002583b60)
[   19.857051] 3592af1f: a1a91abc 
(__check_object_size+0x14c/0x178)
[   19.857052] 86c7dd25: 0003 (0x3)
[   19.857053] 8c88b4e5: 935d57f65cb0 (0x935d57f65cb0)
[   19.857053] 92bc319f: 55de94b2491e (0x55de94b2491e)
[   19.857054] 59b96776:  ...
[   19.857055] 2c0f28f3: bb3002583b88 (0xbb3002583b88)
[   19.857141] c046880e: c078b5b6 (os_memcpy_to_user+0x26/0x50 
[nvidia])
[   19.857142] 870f32d1: 0003 (0x3)
[   19.857142] 077eb892: 55de94b2491e (0x55de94b2491e)
[   19.857143] 47ac0c10: 935d57f65cb0 (0x935d57f65cb0)
[   19.857144] 05649f90: 935d57f65ca8 (0x935d57f65ca8)
[   19.857290] d28c291e: c0d5b87f (_nv009384rm+0xbf/0xe0 
[nvidia])
[   19.857291] 0bf99a12: 935d57f65c88 (0x935d57f65c88)
[   19.857291] cc40361c:  ...
[   19.857292] 260150fd: 935d549d3f08 (0x935d549d3f08)
[   19.857293] 3bbf4a77: 935d57f65db8 (0x935d57f65db8)
[   19.857293] 76aa34db: 7ffd341175d0 (0x7ffd341175d0)
[   19.857421] 28327c08: c0955259

[Touch-packages] [Bug 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace

** Patch added: "libnotify_0.7.6-2svn1+snap-fix.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+attachment/5210729/+files/libnotify_0.7.6-2svn1+snap-fix.debdiff

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

Title:
  Notifications emitted by a snap with local files or desktop files use
  wrong namespace

Status in libnotify package in Ubuntu:
  In Progress

Bug description:
  As can be tested using this example snap:
   - https://github.com/3v1n0/notify-send-test-snap

  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on
  $SNAP location.

  As we do with appindicators and libunity emblems.

  

  
  [ Impact ]

  Icons sonuds and desktop files referenced by a snapped app using
  notifications aren't exposed to the desktop in absolute paths

  [ Test case ]

  Build the test snap:
git clone https://github.com/3v1n0/notify-send-test-snap
snapcraft prime
snap try prime

  Check that icons are shown when launching:
notify-send-test-snap
notify-send-test-snap.image-path

  Running them with G_MESSAGES_DEBUG=all should provide translation
  logging

  [ Regression potential ]

  Normal applications that are run with a SNAP environment variable set,
  might use wrong paths for files or desktop file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace

Fix for bionic (and cosmic)

** Patch added: "libnotify_0.7.7-3+snap-support.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+attachment/5210728/+files/libnotify_0.7.7-3+snap-support.debdiff

** Patch removed: "libnotify_0.7.6-2svn1-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+attachment/5210727/+files/libnotify_0.7.6-2svn1-xenial.debdiff

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

Title:
  Notifications emitted by a snap with local files or desktop files use
  wrong namespace

Status in libnotify package in Ubuntu:
  In Progress

Bug description:
  As can be tested using this example snap:
   - https://github.com/3v1n0/notify-send-test-snap

  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on
  $SNAP location.

  As we do with appindicators and libunity emblems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace

Libnotify fix for xenial

** Patch added: "libnotify_0.7.6-2svn1-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+attachment/5210727/+files/libnotify_0.7.6-2svn1-xenial.debdiff

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

Title:
  Notifications emitted by a snap with local files or desktop files use
  wrong namespace

Status in libnotify package in Ubuntu:
  In Progress

Bug description:
  As can be tested using this example snap:
   - https://github.com/3v1n0/notify-send-test-snap

  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on
  $SNAP location.

  As we do with appindicators and libunity emblems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1739931] Re: Separator lines in shell popup menus are too faint to see

2018-11-09 Thread Timo Aaltonen

Hello Fred, or anyone else affected,

Accepted gnome-shell into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.28.3-0ubuntu0.18.04.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-shell (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  Separator lines in shell popup menus are too faint to see

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix
Status in ubuntu-themes package in Ubuntu:
  Won't Fix
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock source package in Bionic:
  Won't Fix
Status in ubuntu-themes source package in Bionic:
  Won't Fix

Bug description:
  [ Impact ]

  Separators in gnome-shell menuitems are not visible

  [ Test case ]

  1. Right - Click on a dock icon
  2. Separators between menu items should be visible

  [ Regression potential ]

  Nothing known

  

  when I click on the dock icons, some of the lines in the popup menus
  are blank and some of them appear to be incorrect. see top left of
  attached screenshot.

  ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 23 22:24:40 2017
  InstallationDate: Installed on 2016-08-18 (492 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739931/+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 1802483] [NEW] Notifications emitted by a snap with local files or desktop files use wrong namespace