[Touch-packages] [Bug 1449783] Re: [arale] intermittent sound effect playback issues in pathwind

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  [arale] intermittent sound effect playback issues in pathwind

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 26
  device name: arale
  channel: ubuntu-touch/tangxi-vivid-proposed
  last update: 2015-04-28 13:54:53
  version version: 26
  version ubuntu: 20150428
  version device: 
c13f0f3134089c610eefdde737c4198d378f627cfae001f7db055d2b84be986d
  version custom: 
3ed576bc5513430feab7a10b370d1d5fcade19fb00bf1d7f39b0d6451c7f26a5

  
  Playing pathwind without sound muted, the sound effects that are played 
intermittently stutter or completely fail to play.  For example the jetpack 
sound while flying, sometimes will just stop playing and later start again.  
Same for the effects when you hit an obstacle.  These are using SoundEffect 
from Qt.Multimedia.  I was unable to reproduce this on mako vivid-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1449783/+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 1455107] Re: Creating and destroying SoundEffects causes crashes

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Creating and destroying SoundEffects causes crashes

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Won't Fix
Status in qtmultimedia-opensource-src package in Ubuntu:
  New

Bug description:
  I keep on receiving bug reports about Machines vs. Machines being
  crashy on Ubuntu Phones and I tracked it down to the SoundEffect item.
  When playing without sound effects enabled, the game seems very
  stable.

  To get to the bottom of this I created an app that simulates a bit how
  a game works with sound effects. It's a bit more aggressive than
  Machines-vs-Machines (still not really far fetched from a real game
  scenario) and reliably triggers some crashers in less than a minute
  here.

  So far I've seen crashes in creating SoundEffects items as well as
  removing them from the scene.

  Please find the example here: lp:~mzanetti/+junk/soundcrasher

  You should be able to run it on any vivid powered device by just
  opening the .pro file in QtCreator and hit the play button. The logs
  vary a lot between crashes. Sometimes I get some PulseAudio messages,
  sometimes it just crashes without any. Probably some raciness. Anyhow,
  this example app should give the system a hard time and reveal most of
  the crashes eventually.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1455107/+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 1519809] Re: No sound is routed to bluetooth headset after a call

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Fix Committed => Won't Fix

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

Title:
  No sound is routed to bluetooth headset after a call

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  After the latest update to bluez5 no sound is routed to the connected
  bluetooth headset after a call is ended.

  Steps to reproduce:

  1) connect a bluetooth headset
  2) Receive a call
  3) End the call
  4) Try to play music

  Expected behavior:
  Music is routed to the connected headset

  Current behavior:
  No sound is routed, although music player behaves as it was playing normally.

  Additional info.
  If you receive a second call, the audio is again routed normally to the 
headset after it's finished.
  Just tried with old images with bluez4 and it works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1519809/+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 1487111] Re: camera app unresponsive if trusted prompt left for some time

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  camera app unresponsive if trusted prompt left for some time

Status in camera-app:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  image95/arale (also on mako)
  i see this for both the audio trust prompt and the video trust prompt
  steps
  1. launch camera
  2. don't touch trust prompt - set phone down for 5 min
  3. after time, select "accept"
  (alternately - select accept on camera, hit record and wait for audio prompt, 
step2)

  expected - app continues
  result - app is frozen, shell is still responsive, camera service spinning 
50% cpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1487111/+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 1480865] Re: Phone plays music via bluetooth instead of recently connected headset

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Phone plays music via bluetooth instead of recently connected headset

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Prerequisite:
  1. The phone can play music via a car's bluetooth stereo.
  2. Be in car and let the phone connect to it by bluetooth.

  Reproduce:
  Connect the phone to a headset via jack

  What happens:
  No music plays in the headset

  What should happen:
  The headset should play music; or I should be able to select where the music 
should be played.

  * Note that the music was actually played _nowhere_, but I know that
  it tried to play it via bluetooth since by disconnecting the headset
  sound was not played through the phone speakers.

  : "Whenever headphones
  or a headset are connected, they should be the primary output for as
  long as they are connected."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480865/+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 1543179] Re: Audio does not get routed to BT headset/speaker

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Audio does not get routed to BT headset/speaker

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  STEPS:
  1. Flash the latest daily rc-proposed image to a phone
  2. Connect a bluetooth headset to the phone
  3. Connect a speaker to the phone.

  EXPECTED:
  I expect the devices to connect and play audio

  ACTUAL:
  Speakers just connect and instantly disconnect

  Headsets don't get trusted and disconnect instantly, Once you trust it
  and then turn the headset off and back on again it connect can accept
  calls but the audio from both the mic and earpiece don't function.

  Image: 242

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543179/+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 1519594] Re: No sounds for ongoing call in both sides when connecting a BT speaker

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Fix Committed => Won't Fix

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

Title:
  No sounds for ongoing call in both sides when connecting a BT speaker

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Test Env:
  current build number: 185
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-11-23 03:35:34
  version version: 185
  version ubuntu: 20151120.1
  version device: 20151028-869191d
  version custom: 2015

  BT speaker:
  Philips BT25

  Steps:
  1.Connect a BT speaker
  2.Play a music file
  >Music plays from speaker
  3.Make a call to DUT
  >Ringtone sounds from the phone
  4.Answer the call, then listen and talk

  Actual: 
  No sounds for the call in both sides

  Expected:
  The calling should sound from the phone

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1519594/+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 1521288] Re: Having a TV connected via SlimPort/HDMI does not route sound to it

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Having a TV connected via SlimPort/HDMI does not route sound to it

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  While a TV is connected to the phone via SlimPort/HDMI, audio should
  be routed to the TV.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1521288/+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 1487129] Re: camera-app mic permission item blank

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Won't Fix

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

Title:
  camera-app mic permission item blank

Status in Canonical System Image:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Won't Fix
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  Working through camera/mic trust issues, discovering that the camera-
  app's mic item under "Other app access" is blank, will attach a
  screenie.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487129/+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 1555307] Re: Audio recording does not work on flo and mako

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Audio recording does not work on flo and mako

Status in pulseaudio package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu RTM:
  Won't Fix

Bug description:
  With the latest rc-proposed image, #382, audio recording from the
  camera-app doing video recording and from the messaging-app doing memo
  recording no longer functions.

  Steps to reproduce:

  1. Open camera-app and begin recording a video
  2. Record for a few seconds and make some noise that it can record
  3. From the camera roll, tap the new video so that it plays back
  4. Notice that only the video was captured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1555307/+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 1546310] Re: In CAR bluetooth not working

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Fix Committed => Won't Fix

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

Title:
  In CAR bluetooth not working

Status in Canonical System Image:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  I have paired my phone with my car as always (connection did work in
  the past). Connection runs as expected and everything like display,
  phone book, ... but this evening I wanted to place a call from my car
  and it did not work. I was then also not able to take a call (I could
  not hear the conterpart and the counterpart could not hear me).

  Since yesterday I am on:

  current build number: 259
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-02-16 12:09:18
  version version: 259
  version ubuntu: 20160216
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid

  With OTA9 I did not have the issue. I have attached my logs. I have
  enabled the following bug-settings for bluetooth:

  sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec
  \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf

  sudo sed -i 's/--start/--start --log-level=debug/g'
  /usr/share/upstart/sessions/pulseaudio.conf

  I have modified the line in ofono.override to:

  exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap

  I hope my reporting helps to trace down this issue.

  Uranicus

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+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 1555873] Re: Sound crackles when using time slider

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Sound crackles when using time slider

Status in Ubuntu Music App:
  Invalid
Status in media-hub package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Sound crackles on handle release when using time slider to fast
  forward or fast backward the track.

  Device: mako

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1555873/+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 1479449] Re: IN CAR: Bluetooth connected but ring happens through the DUT and not the Bluetooth audio

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  IN CAR: Bluetooth connected but ring happens through the DUT and not
  the Bluetooth audio

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  STEPS:
  Requirements: DUT, a second device, a car with bluetooth phone support (Skoda 
Supberb 2013 in my case)

  1. Connect the DUT to the car
  2. From the second device call the car
  3. The ringer starts

  EXPECTED:
  I expect all audio to come through the car speakers

  ACTUAL:
  The ringer is routed through the loud speaker of the phone not the car audio

  VERSIONS:
  current build number: 71
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-28 18:01:08
  version version: 71
  version ubuntu: 20150728
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  MODIFICATIONS:
  Installation of silo19 for in car bt fix

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479449/+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 1565957] Re: Issue pairing with BTLE "Smart technology" mouse

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Issue pairing with BTLE "Smart technology" mouse

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  I have a Gearhead MBT9950
  Testing with M10 running r75

  I started bluetoothd with --experimental.
  I did not see the device in the UI
  I was able to pair it using bluetoothctl, (the only issue is the mouse 
movement is rather laggy, the velocity is weird and it overshoots)
  The UI still does not show the device connected.

  Device 84:EB:18:2B:47:28
Name: MBT9950
Alias: MBT9950
Appearance: 0x03c2
Icon: input-mouse
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565957/+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 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: canonical-devices-system-image
   Status: Confirmed => Won't Fix

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

Title:
  [Jawbone ERA] HFP features not working with Bluez5 when phone
  initiates connection

Status in Canonical System Image:
  Won't Fix
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  While debugging some re-factoring work on the ofono upower plugin, I
  noticed that I wasn't able to answer or terminate calls using my
  Jawbone ERA headset.  I bought this headset last year, and although
  it's an older model, it's spec sheet states that it supports HSP 1.1,
  and HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+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 1491284] Re: Two spinners showing and the status will become "Not discoverable" after BT enabled for a while

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Two spinners showing and the status will become "Not discoverable"
  after BT enabled for a while

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  $ system-image-cli -i
  current build number: 114
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-09-02 06:52:45
  version version: 114
  version ubuntu: 20150902
  version device: 20150821-736d127
  version custom: 20150821-887-33-32-vivid

  Steps to reproduce:
  1.Enable Bluetooth from System Settings -->Bluetooth-->Enabled
  2.The status will show as "Discoverable -->Aquaris E4.5 Ubuntu Edition" and 
the spinner appears in 10 seconds
  3.Waiting for a while then check the status again

  Expected results:
  The status should be kept as "Discoverable" with device name shown, and only 
one spinner shows in every 10 seconds 

  Actual results:
  The status will become "Not discoverable" and two spinners showing after for 
a while, attached the screenshot and the dmesg output bellow:

  [ 1050.241914] BT ON <>sec=1441177892, usec=884713
  [ 1050.241939] [WMT-STP-EXP][I]mtk_wcn_wmt_func_on: mtk_wcn_wmt_func_on_f 
type(0)
  [ 1050.241959] [HCI-STP][I]hci_stp_open:WMT turn on BT OK!
  [ 1050.241978] Flush type = 0 Rx Queue
  [ 1050.242119] [HCI-STP][I]hci_stp_dev_init_work:Load custom BT config success
  [ 1050.275283] [HCI-STP][I]hci_stp_open:hci_stp_dev_init ok
  [ 1050.275315] Flush type = 0 Rx Queue
  [ 1078.037588] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx 
data(200)
  [ 1591.020633] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx 
data(200)
  [ 1761.020828] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx 
data(200)
  [ 1813.890670] [mtk_net][sched]dev_deactivate dev = wlan0 
  [ 1813.904681] cfg80211: Calling CRDA for country: US
  [ 1825.479625] [mtk_net][sched]dev_activate dev = wlan0 
  [ 1825.500057] --> mtk_cfg80211_set_default_key()
  [ 1921.031722] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx 
data(200)
  [ 2161.026379] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx 
data(200)
  [ 2511.029227] [STP-BTIF][I]mtk_wcn_consys_stp_btif_tx:special case for 
STP-CORE,pbuf(c1001e98)
  [ 2511.036971] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx 
data(200)
  [ 3424.024060] [WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx 
data(200)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1491284/+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 1532980] Re: have to "forget" device sometimes

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: canonical-devices-system-image
   Status: Confirmed => Won't Fix

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  have to "forget" device sometimes

Status in Canonical System Image:
  Won't Fix
Status in Canonical Pocket Desktop:
  New
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  while testing pd, had trouble connecting a previously connected mouse.
  attempted the restart indicator-bluetooth trick, this didn't help.
  I could see the mouse in the list, but never would connect when selecting the 
"connect" button.
  in the end had to "forget device" then refresh list, then device would 
connect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532980/+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 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Won't Fix
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+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 1555608] Re: Bluetooth "Connection timed out" during a longer call

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Bluetooth "Connection timed out" during a longer call

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Issue:
  Phone disconnected bluetooth connection during a longer call.

  I am on:
  current build number: 275
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-03-08 06:14:58
  version version: 275
  version ubuntu: 20160308
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid

  I was in a longer telephone call. All of a sudden the bluetooth
  connection got interrupted. At the time when the bluetooth connection
  got disconnected the following statement from bluetooth was logged:

  Mar 9 08:26:31 ubuntu-phablet bluetoothd[899]: Start: Connection timed out 
(110)
  + following logs (see attached)

  The call itself still was active just the phone disconnected from my
  car.

  Logs are attached.

  Matthias

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1555608/+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 1576951] Re: System hangs if apple magic mouse is connected via bluetooth

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  System hangs if apple magic mouse is connected via bluetooth

Status in Canonical System Image:
  Confirmed
Status in frieza:
  New
Status in turbo:
  New
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  If you connect apple magic mouse via bluetooth the system hangs
  completely. After 1 minute the system restarts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1576951/+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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Fix Released
Status in bluez package in Ubuntu:
  Won't Fix
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1552410] Re: Cannot pair mako with 2014 Subaru Forester

[Daniel van Vugt]

Ubuntu Touch is no longer supported.

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Cannot pair mako with 2014 Subaru Forester

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  Since the bluez5 transition my mako has not been able to pair with the
  radio in my 2014 Subaru Forester. When the radio is put into pairing
  mode the phone sees the CAR_M_MEDIA device, but when I click "connect"
  the radio immediately shows "failed" and no PIN prompt is shown on the
  phone. Additionally, the entry in system-settings for the car stereo
  is left in a limbo state with the "forget" button inactive. The only
  way to remove the entry is to use bluetoothctl from the command line.

  Here's what the phone is currently running:
  current build number: 252
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-03-02 00:31:33
  version version: 252
  version ubuntu: 20160302
  version device: 20160112
  version custom: 20160201-5-vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+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 1764108] Re: A lots of errors after install gnome-desktop

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  A lots  of errors after install gnome-desktop

Status in Ubuntu:
  Incomplete

Bug description:
  Frist, thanks for all ubuntu's team for their great efforts in developing 
this awesome os & platform. 
  after install gnome3 desktop beside xfce4 in ubuntu-studio 16,04 .
  I faced a lot of errors such in gnome-tweak ubuntu-tweak and many other 
issues about more than 10 systemd-crash-notification at every start-up. all of 
them related to sh -e /proc/self/fd/9
  I know that many of those back to being a beginner with ubuntu .so I could be 
grateful if someone help to solve those issues

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Apr 15 13:31:29 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Tonga PRO [Radeon R9 
285/380] [174b:e306]
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=2fab0ad1-9fc6-4072-8130-62b13bbb8f0e rw pci=nomsi drm.debug=0x4 
plymouth:debug modprobe radeon VIDEO_CARDS= amdgpu radeonsi radeon 
radeon.agpmode=-1 radeon.modeset=1 radeon.dpm=-1 radeon.runpm=-1 radeon.uvd=1 
radeon.vce=1 pci=nomsi amdgpu.si_support=1 amdgpu.cik_support=0 
radeon.si_support=0 radeon.cik_support=1 vblank_mode=1 glxgears
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-D3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd08/06/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-D3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu1~xenial
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91+git1804061830.cb850c~oibaf~x
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1804140730.6a519a~oibaf~x
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1804140730.6a519a~oibaf~x
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.0.1+git1803151933.fdba53~oibaf~x
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1803090733.ac8f7b~oibaf~x
  xserver.bootTime: Sun Apr 15 13:11:40 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: amdgpu

To manage notifications about this bug go to:

[Touch-packages] [Bug 1802806] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1802806

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Unable to connect to wifi network after lubuntu install

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  I had ubuntu 16 and my home wifi never had issues. Now i installed lubuntu 
bionic now i can never connect to my home wifi.
  I am getting below message on running command - 
  nmcli dev wifi connect myssid password mypassword

  Error: Connection activation failed: (5) IP configuration could not be
  reserved (no available address, timeout, etc.)

  I can not use my system any more and any help will be appreciated to
  resolve the issue. I posted this issues in askubuntu and no response
  so far.

  Please help. Please let me know any more information needed.

  System details :
  Laptop - hp

  "Realtek RTL8188EE Wireless Network Adapter (RTL8188EE mini-PCIe card)"
  wifi (rtl8188ee), 40:B8:9A:09:D7:9E, hw, mtu 1500

  
  Note - I can connect to hotspot network on my phone with no issues.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-37.40-generic 4.15.18
  Uname: Linux 4.15.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sun Nov 11 19:59:39 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-22 (81 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 172.20.10.1 dev wlo1 proto dhcp metric 600 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   172.20.10.0/28 dev wlo1 proto kernel scope link src 172.20.10.7 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlo1 wifi  connected/org/freedesktop/NetworkManager/Devices/4  
iPhone 1eaf289fc-1e98-4e6b-a075-766c11fc9d49  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   docker0  bridgeconnected/org/freedesktop/NetworkManager/Devices/2  
docker0 f03e7a66-563b-4936-ad48-1cc0b87e14f7  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp3s0   ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802806/+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 1802806] Re: Unable to connect to wifi network after lubuntu install

[Kai-Heng Feng]

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

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

Title:
  Unable to connect to wifi network after lubuntu install

Status in linux package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  I had ubuntu 16 and my home wifi never had issues. Now i installed lubuntu 
bionic now i can never connect to my home wifi.
  I am getting below message on running command - 
  nmcli dev wifi connect myssid password mypassword

  Error: Connection activation failed: (5) IP configuration could not be
  reserved (no available address, timeout, etc.)

  I can not use my system any more and any help will be appreciated to
  resolve the issue. I posted this issues in askubuntu and no response
  so far.

  Please help. Please let me know any more information needed.

  System details :
  Laptop - hp

  "Realtek RTL8188EE Wireless Network Adapter (RTL8188EE mini-PCIe card)"
  wifi (rtl8188ee), 40:B8:9A:09:D7:9E, hw, mtu 1500

  
  Note - I can connect to hotspot network on my phone with no issues.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-37.40-generic 4.15.18
  Uname: Linux 4.15.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sun Nov 11 19:59:39 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-22 (81 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 172.20.10.1 dev wlo1 proto dhcp metric 600 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   172.20.10.0/28 dev wlo1 proto kernel scope link src 172.20.10.7 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlo1 wifi  connected/org/freedesktop/NetworkManager/Devices/4  
iPhone 1eaf289fc-1e98-4e6b-a075-766c11fc9d49  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   docker0  bridgeconnected/org/freedesktop/NetworkManager/Devices/2  
docker0 f03e7a66-563b-4936-ad48-1cc0b87e14f7  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp3s0   ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802806/+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 1788081] Re: Cannot connect to "shared" ipv4 network ("Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)"

[Tyler Johnson]

@ajkan001:

Actually, I think I did. Apparently, 18.04 needs dnsmasq to be running,
whereas 16.04 didn't seem to require the user to even have dnsmasq
installed. So, make sure you have dnsmasq installed, using (without
quotes) "sudo apt install dnsmasq-base". Sometimes, however, dnsmasq
just doesn't want to play nice. In that case, use (again, without
quotes) "sudo pkill -x dnsmasq" or "sudo killall dnsmasq" (either one
will work), and try again.

PS: I probably should have mentioned something on this bug report
before, but I guess I forgot. My apologies.

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

Title:
  Cannot connect to "shared" ipv4 network ("Error: Connection activation
  failed: IP configuration could not be reserved (no available address,
  timeout, etc.)"

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a connection profile which is supposed to allow my computers to
  talk to eachother over an ad-hoc ethernet connection. For me, this is
  mostly useful for when I need to transfer large files over from one
  computer to another (the only network I have is WiFi, and it's
  painfully slow). So, If I need to transfer files from machine A to
  machine B, I just use an ethernet cable. Easy-peasy.

  However, after upgrading one of my machines from Ubuntu 16.04 to
  18.04, I find that said machine can no longer create such a network.
  If I try to active the profile graphically using nm-applet, it fails
  without displaying any error messages. However, If I try to activate
  it from the command line with "nmcli con up id Wired\ Connection\ 2",
  it fails with the following message:

  Error: Connection activation failed: IP configuration could not be
  reserved (no available address, timeout, etc.)

  While typing this bug report, I ran the "ubuntu-bug network-manager"
  command, and will post the results below. If there's anything else I
  can do (I can't read/write code very well, but I can test code, and
  get any additional information, so long as I'm given clear
  instructions on how to do so), please let me know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1788081/+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 1764333] Re: Nach dem Neustart

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Nach dem Neustart

Status in Ubuntu:
  Incomplete

Bug description:
  Begleiterscheinung kann auf der Maschine kein Ubuntu 17.04 oder 17.10
  installieren.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-120.144-generic 4.4.117
  Uname: Linux 4.4.0-120-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Apr 16 10:49:18 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.34, 4.4.0-118-generic, x86_64: installed
   virtualbox, 5.1.34, 4.4.0-120-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation NV43 [GeForce 6600 GT] [10de:0140] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. NV43 [GeForce 6600 GT] [1043:81cf]
  InstallationDate: Installed on 2016-06-22 (662 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: FUJITSU SIEMENS ESPRIMO P
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-120-generic 
root=UUID=e5cf3fb8-1082-4bca-a343-3fc7ac7f335a ro drm.debug=0xe quiet splash 
plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2007
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 6.00 R1.15.2461.A1
  dmi.board.name: D2461-A1
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D2461-A1
  dmi.chassis.type: 2
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: ESPP
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.15.2461.A1:bd10/22/2007:svnFUJITSUSIEMENS:pnESPRIMOP:pvr:rvnFUJITSUSIEMENS:rnD2461-A1:rvrS26361-D2461-A1:cvnFUJITSUSIEMENS:ct2:cvrESPP:
  dmi.product.name: ESPRIMO P
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 16 10:38:12 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1764333/+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 1764896] Re: System will not display using displayport from AMD GPU

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => xorg-server (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/1764896

Title:
  System will not display using displayport from AMD GPU

Status in xorg-server package in Ubuntu:
  New

Bug description:
  There are 2 monitors connected to 1 GPU. The monitor connected via a
  digital connection always comes up correctly. The monitor connected
  via DISPLAYPORT does not come up, even though the machine is booting
  correctly.

  It's almost like the DP path isn't recognized by xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Apr 17 18:02:09 2018
  DistUpgraded: 2018-03-30 21:12:37,078 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-13-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 
470/480/570/580] [1462:3417]
  InstallationDate: Installed on 2017-03-11 (402 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170222)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic 
root=UUID=68755ecb-0ee0-46a1-8a3e-c027d0cbac65 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-31 (17 days ago)
  dmi.bios.date: 12/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.20
  dmi.board.name: Z170M Pro4S
  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.:bvrP7.20:bd12/13/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170MPro4S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1764896/+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] Re: xorg does not work

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

-- 
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-server package in Ubuntu:
  Incomplete

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: 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1802512/+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 1802600] Re: ??????

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  ??

Status in Ubuntu:
  Incomplete

Bug description:
  just installed this OS and its not working properly

  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
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Nov  9 17:14:34 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2018-11-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 4314DDU
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=aa171a08-3cce-474b-ba1c-6a3ec3af6327 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET92WW (1.52 )
  dmi.board.name: 4314DDU
  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:bvr6MET92WW(1.52):bd09/26/2012:svnLENOVO:pn4314DDU:pvrThinkPadT510:rvnLENOVO:rn4314DDU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T510
  dmi.product.name: 4314DDU
  dmi.product.version: ThinkPad T510
  dmi.sys.vendor: LENOVO
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1802600/+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 1802774] Re: Bluetooth (bluez) in 18.10 hangs xfce4 for upwards of 30 seconds, notifyd / stuff crashes

[Daniel van Vugt]

It sounds like some part of the XFCE desktop is waiting for Bluetooth,
which indeed your kernel is taking 107 seconds to realize it's not
present. So a fix will have to occur in one of the XFCE packages.

** Package changed: bluez (Ubuntu) => xfce (Ubuntu)

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

Title:
  Bluetooth (bluez) in 18.10 hangs xfce4 for upwards of 30 seconds,
  notifyd / stuff crashes

Status in xfce package in Ubuntu:
  New

Bug description:
  I recently upgraded from 18.04 to 18.10, and after the upgrade I
  immediately started seeing very long delays after login. Not only
  that, the xfce4-notifyd aspect would just time out and never complete
  loading.

  The solution was

  systemctl disable bluetooth

  So, to disable the bluetooth daemon.

  Now, my computer doesn't have bluetooth, and I don't plug bluetooth
  devices/radios into it really ever.

  During the "wait" time, things like "ctrl esc" and other ways to bring
  up the application menu simply didn't respond. And I would have to
  manually run and fork the xfce4-notifyd proccess.

  I suspect bluetooth is timing out looking for devices that don't/never
  exist(ed), but I don't know why that behaviour changed drastically in
  18.10. This is a very poor user experience, and it took me weeks on
  and off to figure out.

  * Ubuntu 18.10 + XFCE4
  * i7 980x
  * 24GB RAM
  * Asus Xonar DGX
  * GTX 960
  * 3x1920x1080 monitors (all in landscape)

  Hope this gets solved, because there's seriously no good solutions on
  the internet that I could find. This seriously was stabbing in the
  dark here.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov 11 11:57:12 2018
  InstallationDate: Installed on 2015-07-20 (1209 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterestingModules: bluetooth
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=3557b89b-06a6-4e9f-8538-41be167eede8 ro quiet splash vga=789 
nomodeset mode_option=1280x1024-24,mtrr=3,scroll=ywrap
  SourcePackage: bluez
  UpgradeStatus: Upgraded to cosmic on 2018-10-30 (11 days ago)
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1701
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Rampage II GENE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 2.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1701:bd09/19/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnRampageIIGENE:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  hciconfig:
   
  rfkill:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce/+bug/1802774/+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 1802573] Re: Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen

[Daniel van Vugt]

Can you please try logging into "Ubuntu on Wayland" and tell us if that
has the same problem?

** Tags added: multimonitor

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

-- 
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-server package in Ubuntu:
  Incomplete

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1802573/+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 1802609] Re: alot of freezing

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Tags added: nvidia

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  alot of freezing

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu worked perfectly with me twice only i don't know why its
  freezing when i open any app cant even access ctrl alt f1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 10 02:14:25 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:39d1]
 Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39d1]
  InstallationDate: Installed on 2018-11-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b57e Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80WK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=d82157c0-ebe8-41dc-a55d-30ee1b736357 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4KCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y520-15IKBN
  dmi.modalias: 
dmi:bvnLENOVO:bvr4KCN40WW:bd10/17/2017:svnLENOVO:pn80WK:pvrLenovoY520-15IKBN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY520-15IKBN:
  dmi.product.family: Y520-15IKBN
  dmi.product.name: 80WK
  dmi.product.version: Lenovo Y520-15IKBN
  dmi.sys.vendor: LENOVO
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1802609/+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] Re: A good amount of pulseaudio modules can't be loaded

[Daniel van Vugt]

Please run this command to send us more information about the system:

  apport-collect 1802584

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

** Tags added: bionic

-- 
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:
  Incomplete

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 1802714] Re: dont know

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  dont know

Status in Ubuntu:
  Incomplete

Bug description:
  dont know

  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: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 11 15:23:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83f9]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:83f9]
  InstallationDate: Installed on 2018-10-18 (23 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0408:51e9 Quanta Computer, Inc. 
   Bus 001 Device 004: ID 2d95:6006  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Laptop 15-cc1xx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=3198d22f-18f8-4fc6-8db2-0581755ea025 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83F9
  dmi.board.vendor: HP
  dmi.board.version: 46.53
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.30:bd06/22/2018:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.53:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1802714/+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 1802700] Re: Cannot install graphic drivers

[Daniel van Vugt]

It appears you do have graphics drivers installed.

Can you please describe in more detail (maybe with a photo) what problem
you see?

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Cannot install graphic drivers

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  i just instal linux 18.04 but the graphic drivers not installed, so my
  maximum resolution is 360p. I use Lenovo G50-80 with graphic AMR
  radeon M330

  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: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 11 12:01:41 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 18.20-673703, 4.15.0-29-generic, x86_64: installed
   amdgpu, 18.20-673703, 4.15.0-38-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:390c]
 Subsystem: Lenovo Radeon R5 M330 [17aa:390c]
  InstallationDate: Installed on 2018-11-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO INVALID
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=2c4eae76-fae9-48ac-98de-2dfbd276535b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN93WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANA NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: INVALID
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvrNANANANANODPK:cvnLENOVO:ct10:cvrINVALID:
  dmi.product.family: IDEAPAD
  dmi.product.name: INVALID
  dmi.product.version: INVALID
  dmi.sys.vendor: LENOVO
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802700/+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 1802636] Re: REGRESSION: only one displayport fron docking station is used at a time

[Daniel van Vugt]

Can you please try logging into "Ubuntu on Wayland" and tell us if the
problem still occurs there?

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  REGRESSION: only one displayport fron docking station is used at a
  time

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  When my HP 840 G3 is connected to its docking station only one
  DisplayPort is used at a time. If I disconnect the one in use, the
  other is enabled. Only one display is detected. I'm using a fresh
  installation of Ubuntu 18.10. Before, on 18.04, it worked.

  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
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 10 12:49:30 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
  InstallationDate: Installed on 2018-11-01 (9 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04ca:7054 Lite-On Technology Corp.
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 03f0:521d Hewlett-Packard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 840 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=1203967d-3709-4fd4-966f-4c08b53203ce ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.16
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.76
  dmi.chassis.asset.tag: 5CG7320Q91
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.16:bd06/08/2017:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.76:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: L3C65AV
  dmi.sys.vendor: HP
  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.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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1802636/+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 1802669] Re: brightness controll didn't work

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => linux (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/1802669

Title:
  brightness controll didn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 16.04.5 lts
  asus x55u with amd c-60 & radeon graphic hd6290

  -> the brightness volume seems be set to 100 % and it is not possible
  to change it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-105.128-generic 4.4.98
  Uname: Linux 4.4.0-105-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Nov 10 19:42:47 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Wrestler [Radeon HD 6290] [1043:14e7]
  InstallationDate: Installed on 2017-12-12 (333 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 002: ID 1bcf:2883 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X55U
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-105-generic 
root=UUID=38a3e077-62b8-4d4a-98f6-6a371e67801c ro quiet splash acpi_osi=Linux 
acpi_backlight=vendor
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X55U.410
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X55U
  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.:bvrX55U.410:bd09/03/2012:svnASUSTeKCOMPUTERINC.:pnX55U:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55U:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X55U
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov 10 19:35:24 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802669/+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] Re: xorg does not work

[Daniel van Vugt]

The attached logs seem to be from a system that was running for a couple
of hours so maybe are not from a boot where the problem occurred(?)

Can you please describe in more detail what problem you see?

** Tags added: nvidia

-- 
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: 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1802512/+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] Re: Xorg freeze

[Daniel van Vugt]

It appears your system is stuck in recovery mode:

[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic
root=UUID=2a4451ed-b3fe-405b-8626-01fa361e7b98 ro recovery nomodeset

To fix that, please reboot and tap Esc as soon as you see the purple
screen appear. Now choose a normal (non-recovery) kernel option in the
menus to boot.

When done, let us know if the problem is fixed and if not then run:

  dmesg > newdmesg.txt

and attach newdmesg.txt here.

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Summary changed:

- Xorg freeze
+ After upgrading to Ubuntu 18.10, the system won't boot any more correctly.

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu)

** Summary changed:

- After upgrading to Ubuntu 18.10, the system won't boot any more correctly.
+ Nvidia driver crashes the kernel on boot

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

Title:
  Nvidia driver crashes the kernel on boot

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

Bug description:
  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: 

[Touch-packages] [Bug 1802497] Re: cannot open a VT2

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

-- 
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-server package in Ubuntu:
  Incomplete

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: 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1802497/+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 1802504] Re: TILIX INFO

[Daniel van Vugt]

Those are just warnings that your /etc/apt/sources.list and
/etc/apt/sources.list.d/ have become slightly broken due to the use of
PPAs. Unfortunately this is not a bug in regular Ubuntu so you will need
to fix those errors yourself.

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Invalid

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

Title:
  TILIX INFO

Status in Ubuntu:
  Invalid

Bug description:
  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
  

[Touch-packages] [Bug 1802402] Re: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound

[Daniel van Vugt]

Please try this:

sudo apt remove libjack-jackd2-0:amd64

and then reboot.

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

Title:
  [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I expected speaker and headphones to work.
  I found speaker silent and headphones slight popping sound only.
  But HDMI audio works, also speaker and headphones work on my dualbooted 
windows 10.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jita   1798 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 22:45:36 2018
  InstallationDate: Installed on 2018-11-07 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jita   1798 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [UX430UNR, Realtek ALC294, Black Headphone Out, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.T157
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UNR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Tarasovic Jiri
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UNR.T157:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnUX430UNR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UNR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UNR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-11-08T22:34:00.520280

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

[Daniel van Vugt]

Verified this bug is fixed in bionic version 3.28.3-0ubuntu0.18.04.3,
but it introduces a rather bad regression where the login screen is now
the upstream grey theme.

-- 
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 1802806] [NEW] Unable to connect to wifi network after lubuntu install

[Ajay Kanse]

Public bug reported:

Hi,

I had ubuntu 16 and my home wifi never had issues. Now i installed lubuntu 
bionic now i can never connect to my home wifi.
I am getting below message on running command - 
nmcli dev wifi connect myssid password mypassword

Error: Connection activation failed: (5) IP configuration could not be
reserved (no available address, timeout, etc.)

I can not use my system any more and any help will be appreciated to
resolve the issue. I posted this issues in askubuntu and no response so
far.

Please help. Please let me know any more information needed.

System details :
Laptop - hp

"Realtek RTL8188EE Wireless Network Adapter (RTL8188EE mini-PCIe card)"
wifi (rtl8188ee), 40:B8:9A:09:D7:9E, hw, mtu 1500


Note - I can connect to hotspot network on my phone with no issues.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-37.40-generic 4.15.18
Uname: Linux 4.15.0-37-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Sun Nov 11 19:59:39 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-08-22 (81 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
 default via 172.20.10.1 dev wlo1 proto dhcp metric 600 
 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
 172.20.10.0/28 dev wlo1 proto kernel scope link src 172.20.10.7 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlo1 wifi  connected/org/freedesktop/NetworkManager/Devices/4  
iPhone 1eaf289fc-1e98-4e6b-a075-766c11fc9d49  
/org/freedesktop/NetworkManager/ActiveConnection/6 
 docker0  bridgeconnected/org/freedesktop/NetworkManager/Devices/2  
docker0 f03e7a66-563b-4936-ad48-1cc0b87e14f7  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp3s0   ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/3  --  
----
 
 lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --  
----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  Unable to connect to wifi network after lubuntu install

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  I had ubuntu 16 and my home wifi never had issues. Now i installed lubuntu 
bionic now i can never connect to my home wifi.
  I am getting below message on running command - 
  nmcli dev wifi connect myssid password mypassword

  Error: Connection activation failed: (5) IP configuration could not be
  reserved (no available address, timeout, etc.)

  I can not use my system any more and any help will be appreciated to
  resolve the issue. I posted this issues in askubuntu and no response
  so far.

  Please help. Please let me know any more information needed.

  System details :
  Laptop - hp

  "Realtek RTL8188EE Wireless Network Adapter (RTL8188EE mini-PCIe card)"
  wifi (rtl8188ee), 40:B8:9A:09:D7:9E, hw, mtu 1500

  
  Note - I can connect to hotspot network on my phone with no issues.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-37.40-generic 4.15.18
  Uname: Linux 4.15.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sun Nov 11 19:59:39 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-22 (81 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 172.20.10.1 dev wlo1 proto dhcp metric 600 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   172.20.10.0/28 dev wlo1 proto kernel scope link 

[Touch-packages] [Bug 1788081] Re: Cannot connect to "shared" ipv4 network ("Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)"

[Launchpad Bug Tracker]

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

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

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

Title:
  Cannot connect to "shared" ipv4 network ("Error: Connection activation
  failed: IP configuration could not be reserved (no available address,
  timeout, etc.)"

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a connection profile which is supposed to allow my computers to
  talk to eachother over an ad-hoc ethernet connection. For me, this is
  mostly useful for when I need to transfer large files over from one
  computer to another (the only network I have is WiFi, and it's
  painfully slow). So, If I need to transfer files from machine A to
  machine B, I just use an ethernet cable. Easy-peasy.

  However, after upgrading one of my machines from Ubuntu 16.04 to
  18.04, I find that said machine can no longer create such a network.
  If I try to active the profile graphically using nm-applet, it fails
  without displaying any error messages. However, If I try to activate
  it from the command line with "nmcli con up id Wired\ Connection\ 2",
  it fails with the following message:

  Error: Connection activation failed: IP configuration could not be
  reserved (no available address, timeout, etc.)

  While typing this bug report, I ran the "ubuntu-bug network-manager"
  command, and will post the results below. If there's anything else I
  can do (I can't read/write code very well, but I can test code, and
  get any additional information, so long as I'm given clear
  instructions on how to do so), please let me know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1788081/+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 1788081] Re: Cannot connect to "shared" ipv4 network ("Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)"

[Ajay Kanse]

Hi Guys

I am facing this issue after lubuntu bionic install. Does anyone know
how to resolve this issue ?

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

Title:
  Cannot connect to "shared" ipv4 network ("Error: Connection activation
  failed: IP configuration could not be reserved (no available address,
  timeout, etc.)"

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a connection profile which is supposed to allow my computers to
  talk to eachother over an ad-hoc ethernet connection. For me, this is
  mostly useful for when I need to transfer large files over from one
  computer to another (the only network I have is WiFi, and it's
  painfully slow). So, If I need to transfer files from machine A to
  machine B, I just use an ethernet cable. Easy-peasy.

  However, after upgrading one of my machines from Ubuntu 16.04 to
  18.04, I find that said machine can no longer create such a network.
  If I try to active the profile graphically using nm-applet, it fails
  without displaying any error messages. However, If I try to activate
  it from the command line with "nmcli con up id Wired\ Connection\ 2",
  it fails with the following message:

  Error: Connection activation failed: IP configuration could not be
  reserved (no available address, timeout, etc.)

  While typing this bug report, I ran the "ubuntu-bug network-manager"
  command, and will post the results below. If there's anything else I
  can do (I can't read/write code very well, but I can test code, and
  get any additional information, so long as I'm given clear
  instructions on how to do so), please let me know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1788081/+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 1802600] Re: ??????

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  ??

Status in xorg package in Ubuntu:
  New

Bug description:
  just installed this OS and its not working properly

  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
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Nov  9 17:14:34 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2018-11-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 4314DDU
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=aa171a08-3cce-474b-ba1c-6a3ec3af6327 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET92WW (1.52 )
  dmi.board.name: 4314DDU
  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:bvr6MET92WW(1.52):bd09/26/2012:svnLENOVO:pn4314DDU:pvrThinkPadT510:rvnLENOVO:rn4314DDU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T510
  dmi.product.name: 4314DDU
  dmi.product.version: ThinkPad T510
  dmi.sys.vendor: LENOVO
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1802600/+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 1802804] [NEW] crash due to assertion failure on busy VM host

[Paul Collins]

Public bug reported:

Version: 1:4.2.8p4+dfsg-3ubuntu5.9

We've observed the following crash on an Ubuntu 16.04 s390x nova-compute
host, apparently related to the VMs network interfaces coming and going:

Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542170 qvo8dd4fc29-b8 
[fe80::2c99:58ff:fefa:b081%616530]:123
Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542171 qvb8dd4fc29-b8 
[fe80::b809:4ff:fefc:1b17%616531]:123
Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542172 tap3ca379f2-d1 
[fe80::fc16:3eff:fe6e:5ef7%616532]:123
Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542173 tap8dd4fc29-b8 
[fe80::fc16:3eff:fedf:c527%616533]:123
Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542174 qvo92509b39-cf 
[fe80::a489:5ff:fe82:d27%616535]:123
Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542175 qvb92509b39-cf 
[fe80::d8b1:d4ff:fe48:a44d%616536]:123
Nov 11 01:40:34 s0lp3 ntpd[2426]: Deleting interface #542166 tap3ca379f2-d1, 
fe80::fc16:3eff:fe6e:5ef7%616526#123, interface stats: received=0, sent=0, 
dropped=0, active_time=57 secs
Nov 11 01:40:34 s0lp3 ntpd[2426]: new interface(s) found: waking up resolver
Nov 11 01:40:37 s0lp3 ntpd[2426]: bind(122) AF_INET6 
fe80::fc16:3eff:fea1:a01c%616537#123 flags 0x11 failed: Cannot assign requested 
address
Nov 11 01:40:37 s0lp3 ntpd[2426]: unable to create socket on tap92509b39-cf 
(542176) for fe80::fc16:3eff:fea1:a01c%616537#123
Nov 11 01:40:37 s0lp3 ntpd[2426]: failed to init interface for address 
fe80::fc16:3eff:fea1:a01c%616537
Nov 11 01:40:39 s0lp3 ntpd[2426]: Listen normally on 542177 tap92509b39-cf 
[fe80::fc16:3eff:fea1:a01c%616537]:123
Nov 11 01:40:39 s0lp3 ntpd[2426]: new interface(s) found: waking up resolver
Nov 11 01:40:52 s0lp3 ntpd[2426]: Deleting interface #542172 tap3ca379f2-d1, 
fe80::fc16:3eff:fe6e:5ef7%616532#123, interface stats: received=0, sent=0, 
dropped=0, active_time=18 secs
Nov 11 01:40:54 s0lp3 ntpd[2426]: Deleting interface #542163 qvo3ca379f2-d1, 
fe80::14ad:deff:fe5b:4165%616523#123, interface stats: received=0, sent=0, 
dropped=0, active_time=81 secs
Nov 11 01:40:54 s0lp3 ntpd[2426]: Deleting interface #542164 qvb3ca379f2-d1, 
fe80::7cf6:4dff:fe23:b119%616524#123, interface stats: received=0, sent=0, 
dropped=0, active_time=81 secs
Nov 11 01:41:05 s0lp3 ntpd[2426]: ./../lib/isc/unix/ifiter_getifaddrs.c:163: 
INSIST(ifa->ifa_name != ((void *)0)) failed
Nov 11 01:41:05 s0lp3 ntpd[2426]: exiting (due to assertion failure)

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

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

Title:
  crash due to assertion failure on busy VM host

Status in ntp package in Ubuntu:
  New

Bug description:
  Version: 1:4.2.8p4+dfsg-3ubuntu5.9

  We've observed the following crash on an Ubuntu 16.04 s390x nova-
  compute host, apparently related to the VMs network interfaces coming
  and going:

  Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542170 qvo8dd4fc29-b8 
[fe80::2c99:58ff:fefa:b081%616530]:123
  Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542171 qvb8dd4fc29-b8 
[fe80::b809:4ff:fefc:1b17%616531]:123
  Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542172 tap3ca379f2-d1 
[fe80::fc16:3eff:fe6e:5ef7%616532]:123
  Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542173 tap8dd4fc29-b8 
[fe80::fc16:3eff:fedf:c527%616533]:123
  Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542174 qvo92509b39-cf 
[fe80::a489:5ff:fe82:d27%616535]:123
  Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542175 qvb92509b39-cf 
[fe80::d8b1:d4ff:fe48:a44d%616536]:123
  Nov 11 01:40:34 s0lp3 ntpd[2426]: Deleting interface #542166 tap3ca379f2-d1, 
fe80::fc16:3eff:fe6e:5ef7%616526#123, interface stats: received=0, sent=0, 
dropped=0, active_time=57 secs
  Nov 11 01:40:34 s0lp3 ntpd[2426]: new interface(s) found: waking up resolver
  Nov 11 01:40:37 s0lp3 ntpd[2426]: bind(122) AF_INET6 
fe80::fc16:3eff:fea1:a01c%616537#123 flags 0x11 failed: Cannot assign requested 
address
  Nov 11 01:40:37 s0lp3 ntpd[2426]: unable to create socket on tap92509b39-cf 
(542176) for fe80::fc16:3eff:fea1:a01c%616537#123
  Nov 11 01:40:37 s0lp3 ntpd[2426]: failed to init interface for address 
fe80::fc16:3eff:fea1:a01c%616537
  Nov 11 01:40:39 s0lp3 ntpd[2426]: Listen normally on 542177 tap92509b39-cf 
[fe80::fc16:3eff:fea1:a01c%616537]:123
  Nov 11 01:40:39 s0lp3 ntpd[2426]: new interface(s) found: waking up resolver
  Nov 11 01:40:52 s0lp3 ntpd[2426]: Deleting interface #542172 tap3ca379f2-d1, 
fe80::fc16:3eff:fe6e:5ef7%616532#123, interface stats: received=0, sent=0, 
dropped=0, active_time=18 secs
  Nov 11 01:40:54 s0lp3 ntpd[2426]: Deleting interface #542163 qvo3ca379f2-d1, 
fe80::14ad:deff:fe5b:4165%616523#123, interface stats: received=0, sent=0, 
dropped=0, active_time=81 secs
  Nov 11 01:40:54 s0lp3 ntpd[2426]: Deleting interface 

[Touch-packages] [Bug 1789502] Re: Update to 0.6.50

[Launchpad Bug Tracker]

This bug was fixed in the package accountsservice - 0.6.50-0ubuntu1

---
accountsservice (0.6.50-0ubuntu1) disco; urgency=medium

  * New upstream release (LP: #1789502)
  * debian/control:
- Bump minimum version of libglib2.0-dev
  * debian/rules:
  * debian/patches/0005-gdm_config_file_path.patch:
- Set config file using configure args
  * debian/libaccountsservice0.symbols:
- Updated
  * 
debian/patches/0001-Move-cache-cleanup-out-into-a-common-function-and-cl.patch:
  * debian/patches/0002-On-startup-clean-out-the-data-of-removed-users.patch:
  * debian/patches/1002-dont-override-standardoutput.patch:
- Applied upstream
  * debian/patches/0015-debian-nologin-path.patch:
- No longer needed
  * debian/patches/0008-nopasswdlogin-group.patch:
  * debian/patches/2001-filtering_out_users.patch:
- Remove unused patches

 -- Robert Ancell   Mon, 12 Nov 2018
10:52:43 +1300

** Changed in: accountsservice (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update to 0.6.50

Status in accountsservice package in Ubuntu:
  Fix Released

Bug description:
  The upstream changes are non trivial and there is work to update the
  patches but that would be useful to do

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1789502] Re: Update to 0.6.50

[Robert Ancell]

** Changed in: accountsservice (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Update to 0.6.50

Status in accountsservice package in Ubuntu:
  Fix Committed

Bug description:
  The upstream changes are non trivial and there is work to update the
  patches but that would be useful to do

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1724919] Re: Bluetooth headphones only use A2DP when connected manually

[marcostr...@hotmail.com]

Same problem here using Ubuntu 18.04 with Sony MDR1000X, also with the
Sony MDR XB50BS

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

Title:
  Bluetooth headphones only use A2DP when connected manually

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1281580] Re: glib-compile-schemas doesn't compile relocatable schemas

[Lorenzo]

It is possible that this bug is open from 2014 and no one fixed the bug?

I've been last couple of days trying to create a gschema.override file
with relocatable schemas and now I understands that there is a bug
unfixed.

I'm on Debian 9.5

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

Title:
  glib-compile-schemas doesn't compile relocatable schemas

Status in GLib:
  Expired
Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Dear Developers,

  I am using the Ubuntu 14.04 development release with the GNOME Shell 3.10 
and, because my wife is using this system as well, I defined some settings in a 
gschema.override file.
  Everything is working right, except applying settings related to custom 
key-bindings.

  I added following lines my gschema.override file:
  [org.gnome.settings-daemon.plugins.media-keys]
  www='w'
  email='e'
  custom-keybindings = 
['/org/gnome/settings-daemon/plugins/media-keys/custom-keybinding/custom0']

  
[org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/]
  name = 'Launch Gedit'
  command = 'gedit'
  binding = 'g'

  I put my gschema.override file in the '/usr/share/glib-2.0/schemas' 
directory. After I added these lines, I ran 'glib-compile-schemas 
/usr/share/glib2.0/schemas' and no error was reported.
  For testing purposes I created a new user, logged out, and logged in with the 
new user. In the best case, the custom key-binding were applied automatically, 
but this has not happened. Other defined key-bindings were applied correctly.
  In the gnome-control-center's key-bindings tab, the table containing  custom 
shortcuts is empty, containing one row with empty columns.

  Running 'gsettings list-recursively org.gnome.settings-daemon.plugins
  .media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins
  /media-keys/custom-keybindings/custom0/' shows, the name, command, and
  binding key pairs contain empty ('') values.

  If I manually run following commands, the custom key-binding is created 
correctly:
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 name "Launch Gedit"
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 command "gedit"
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 binding "g"

  Am I doing anything wrong when I want to add a custom key-bindings in
  my schema file, or  is 'glib-compile-schemas' really not applying this
  part from the schema file?

  Attila

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libglib2.0-bin 2.39.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Feb 18 13:58:37 2014
  InstallationDate: Installed on 2013-12-13 (67 days ago)
  InstallationMedia: BeLin 3.02 i386
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1281580/+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 1528139] Re: serialize_profile_from_old_profile() crash if file contains multiple profiles

[Christian Boltz]

Also backported to the 2.12 and 2.13 branch, will be in 2.12.2 and
2.13.2.

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

Title:
  serialize_profile_from_old_profile() crash if file contains multiple
  profiles

Status in AppArmor:
  Fix Released
Status in AppArmor 2.10 series:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  = Changed Local Profiles =

  The following local profiles were changed. Would you like to save
  them?

   [1 - /sbin/dhclient]
2 - /usr/sbin/nmbd 
3 - /usr/bin/snx 
4 - /usr/sbin/dnsmasq 
5 - /{usr/,}bin/ping 
6 - /usr/sbin/smbd 
7 - /usr/lib/telepathy/mission-control-5 
  (S)ave Changes / Save Selec(t)ed Profile / [(V)iew Changes] / View Changes 
b/w (C)lean profiles / Abo(r)t
  Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2197, in 
do_logprof_pass
  save_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2277, in 
save_profiles
  newprofile = serialize_profile_from_old_profile(aa[which], which, '')
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3961, in 
serialize_profile_from_old_profile
  if write_prof_data[hat]['network'].is_covered(network_obj, True, True):
  AttributeError: 'collections.defaultdict' object has no attribute 'is_covered'

  
  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-v7wx9fu9.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

  When I pressed V button aa-logprof exits with error.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: apparmor 2.10-0ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
  Uname: Linux 4.2.0-21-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Dec 21 09:54:51 2015
  InstallationDate: Installed on 2014-04-19 (611 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.2.0-21-generic 
root=/dev/mapper/ubuntu-root ro splash elevator=cfq nomdmonddf nomdmonisw 
crashkernel=384M-:128M
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to wily on 2015-11-14 (36 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1528139/+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 1802775] Re: packagekitd crashed with SIGABRT

[Agustin Covarrubias]

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

** Description changed:

  Random crashing present on a fresh installation of Ubuntu Cosmic. Note
  the custom kernel installed. (4.18.18-custom, only diff is a touchscreen
  patch for my pc).
  
- 
- Similar bug at 
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790680 but report 
was marked as invalid due to corruption in the debug files. The bug had uname 
Linux 4.17.0-9-generic x86_64, which suggests the bug probably isn't isolated 
to my custom kernel (which btw only has a patch for ACPI).
+ Similar bug at 1790680 but report was marked as invalid due to
+ corruption in the debug files. The bug had uname Linux 4.17.0-9-generic
+ x86_64, which suggests the bug probably isn't isolated to my custom
+ kernel (which btw only has a patch for ACPI).
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: packagekit 1.1.10-1ubuntu7
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Nov  9 22:57:19 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  ExecutableTimestamp: 1539610664
  InstallationDate: Installed on 2018-11-10 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  ProcCwd: /
  Signal: 6
  SourcePackage: packagekit
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: packagekitd crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

** Description changed:

  Random crashing present on a fresh installation of Ubuntu Cosmic. Note
  the custom kernel installed. (4.18.18-custom, only diff is a touchscreen
  patch for my pc).
  
- Similar bug at 1790680 but report was marked as invalid due to
- corruption in the debug files. The bug had uname Linux 4.17.0-9-generic
- x86_64, which suggests the bug probably isn't isolated to my custom
- kernel (which btw only has a patch for ACPI).
+ Similar bug at
+ https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790680 but
+ report was marked as invalid due to corruption in the debug files. The
+ bug had uname Linux 4.17.0-9-generic x86_64, which suggests the bug
+ probably isn't isolated to my custom kernel (which btw only has a patch
+ for ACPI).
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: packagekit 1.1.10-1ubuntu7
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Nov  9 22:57:19 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  ExecutableTimestamp: 1539610664
  InstallationDate: Installed on 2018-11-10 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  ProcCwd: /
  Signal: 6
  SourcePackage: packagekit
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: packagekitd crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

Title:
  packagekitd crashed with SIGABRT

Status in packagekit package in Ubuntu:
  New

Bug description:
  Random crashing present on a fresh installation of Ubuntu Cosmic. Note
  the custom kernel installed. (4.18.18-custom, only diff is a
  touchscreen patch for my pc).

  Similar bug at
  https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790680 but
  report was marked as invalid due to corruption in the debug files. The
  bug had uname Linux 4.17.0-9-generic x86_64, which suggests the bug
  probably isn't isolated to my custom kernel (which btw only has a
  patch for ACPI).

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: packagekit 1.1.10-1ubuntu7
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Nov  9 22:57:19 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  ExecutableTimestamp: 1539610664
  InstallationDate: Installed on 2018-11-10 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  ProcCwd: /
  Signal: 6
  SourcePackage: packagekit
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   

[Touch-packages] [Bug 1802775] Re: packagekitd crashed with SIGABRT

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Tags removed: need-amd64-retrace

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

Title:
  packagekitd crashed with SIGABRT

Status in packagekit package in Ubuntu:
  New

Bug description:
  Random crashing present on a fresh installation of Ubuntu Cosmic. Note
  the custom kernel installed. (4.18.18-custom, only diff is a
  touchscreen patch for my pc).

  Similar bug at
  https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790680 but
  report was marked as invalid due to corruption in the debug files. The
  bug had uname Linux 4.17.0-9-generic x86_64, which suggests the bug
  probably isn't isolated to my custom kernel (which btw only has a
  patch for ACPI).

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: packagekit 1.1.10-1ubuntu7
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Nov  9 22:57:19 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  ExecutableTimestamp: 1539610664
  InstallationDate: Installed on 2018-11-10 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  ProcCwd: /
  Signal: 6
  SourcePackage: packagekit
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: packagekitd crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1802775/+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 1802775] [NEW] packagekitd crashed with SIGABRT

[Agustin Covarrubias]

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

Public bug reported:

Random crashing present on a fresh installation of Ubuntu Cosmic. Note
the custom kernel installed. (4.18.18-custom, only diff is a touchscreen
patch for my pc).

Similar bug at
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790680 but
report was marked as invalid due to corruption in the debug files. The
bug had uname Linux 4.17.0-9-generic x86_64, which suggests the bug
probably isn't isolated to my custom kernel (which btw only has a patch
for ACPI).

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: packagekit 1.1.10-1ubuntu7
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
Date: Fri Nov  9 22:57:19 2018
ExecutablePath: /usr/lib/packagekit/packagekitd
ExecutableTimestamp: 1539610664
InstallationDate: Installed on 2018-11-10 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcCmdline: /usr/lib/packagekit/packagekitd
ProcCwd: /
Signal: 6
SourcePackage: packagekit
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
Title: packagekitd crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash cosmic

** Information type changed from Private to Public

** Description changed:

  Random crashing present on a fresh installation of Ubuntu Cosmic. Note
  the custom kernel installed. (4.18.18-custom, only diff is a touchscreen
  patch for my pc).
  
- Version installed: 1.1.10-1ubuntu7
  
- 
- Similar bug at 
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790680 but report is 
invalid.
+ Similar bug at 
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790680 but report 
was marked as invalid due to corruption in the debug files. The bug had uname 
Linux 4.17.0-9-generic x86_64, which suggests the bug probably isn't isolated 
to my custom kernel (which btw only has a patch for ACPI).
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: packagekit 1.1.10-1ubuntu7
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Nov  9 22:57:19 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  ExecutableTimestamp: 1539610664
  InstallationDate: Installed on 2018-11-10 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  ProcCwd: /
  Signal: 6
  SourcePackage: packagekit
  StacktraceTop:
-  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
-  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
-  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
-  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
-  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
+  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
+  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
+  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
+  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
+  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: packagekitd crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

Title:
  packagekitd crashed with SIGABRT

Status in packagekit package in Ubuntu:
  New

Bug description:
  Random crashing present on a fresh installation of Ubuntu Cosmic. Note
  the custom kernel installed. (4.18.18-custom, only diff is a
  touchscreen patch for my pc).

  Similar bug at
  https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790680 but
  report was marked as invalid due to corruption in the debug files. The
  bug had uname Linux 4.17.0-9-generic x86_64, which suggests the bug
  probably isn't isolated to my custom kernel (which btw only has a
  patch for ACPI).

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: packagekit 1.1.10-1ubuntu7
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Nov  9 22:57:19 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  ExecutableTimestamp: 1539610664
  InstallationDate: Installed on 2018-11-10 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  ProcCwd: /
  Signal: 6
  SourcePackage: packagekit
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at 

[Touch-packages] [Bug 1802774] [NEW] Bluetooth (bluez) in 18.10 hangs xfce4 for upwards of 30 seconds, notifyd / stuff crashes

[BloodyIron]

Public bug reported:

I recently upgraded from 18.04 to 18.10, and after the upgrade I
immediately started seeing very long delays after login. Not only that,
the xfce4-notifyd aspect would just time out and never complete loading.

The solution was

systemctl disable bluetooth

So, to disable the bluetooth daemon.

Now, my computer doesn't have bluetooth, and I don't plug bluetooth
devices/radios into it really ever.

During the "wait" time, things like "ctrl esc" and other ways to bring
up the application menu simply didn't respond. And I would have to
manually run and fork the xfce4-notifyd proccess.

I suspect bluetooth is timing out looking for devices that don't/never
exist(ed), but I don't know why that behaviour changed drastically in
18.10. This is a very poor user experience, and it took me weeks on and
off to figure out.

* Ubuntu 18.10 + XFCE4
* i7 980x
* 24GB RAM
* Asus Xonar DGX
* GTX 960
* 3x1920x1080 monitors (all in landscape)

Hope this gets solved, because there's seriously no good solutions on
the internet that I could find. This seriously was stabbing in the dark
here.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: bluez 5.50-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Nov 11 11:57:12 2018
InstallationDate: Installed on 2015-07-20 (1209 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
InterestingModules: bluetooth
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=3557b89b-06a6-4e9f-8538-41be167eede8 ro quiet splash vga=789 
nomodeset mode_option=1280x1024-24,mtrr=3,scroll=ywrap
SourcePackage: bluez
UpgradeStatus: Upgraded to cosmic on 2018-10-30 (11 days ago)
dmi.bios.date: 09/19/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1701
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Rampage II GENE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 2.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1701:bd09/19/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnRampageIIGENE:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
hciconfig:
 
rfkill:

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

Title:
  Bluetooth (bluez) in 18.10 hangs xfce4 for upwards of 30 seconds,
  notifyd / stuff crashes

Status in bluez package in Ubuntu:
  New

Bug description:
  I recently upgraded from 18.04 to 18.10, and after the upgrade I
  immediately started seeing very long delays after login. Not only
  that, the xfce4-notifyd aspect would just time out and never complete
  loading.

  The solution was

  systemctl disable bluetooth

  So, to disable the bluetooth daemon.

  Now, my computer doesn't have bluetooth, and I don't plug bluetooth
  devices/radios into it really ever.

  During the "wait" time, things like "ctrl esc" and other ways to bring
  up the application menu simply didn't respond. And I would have to
  manually run and fork the xfce4-notifyd proccess.

  I suspect bluetooth is timing out looking for devices that don't/never
  exist(ed), but I don't know why that behaviour changed drastically in
  18.10. This is a very poor user experience, and it took me weeks on
  and off to figure out.

  * Ubuntu 18.10 + XFCE4
  * i7 980x
  * 24GB RAM
  * Asus Xonar DGX
  * GTX 960
  * 3x1920x1080 monitors (all in landscape)

  Hope this gets solved, because there's seriously no good solutions on
  the internet that I could find. This seriously was stabbing in the
  dark here.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov 11 11:57:12 2018
  InstallationDate: Installed on 2015-07-20 (1209 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterestingModules: bluetooth
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=3557b89b-06a6-4e9f-8538-41be167eede8 ro quiet splash 

[Touch-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

[Theo Linkspfeifer]

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

** This bug has been marked a duplicate of bug 1308105
   Xfce resets TV mode to NULL when power cycled

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

Title:
  Monitor remains blanked with Intel Graphics

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port 
or HDMI
  Running Xubuntu 16.04 - latest all current patches

  Sometimes the monitor remains blanked even when the session has
  reactivated.

  I have been able to reproduce this problem by letting the monitor
  remain in the 'blanked' state for > 60 minutes, or powering off the
  monitor. When the monitor is powered back on and the session is woken
  up with mouse or keyboard input, it does wake up but the monitor
  remains blanked.

  I was able to prove to myself the session was awake by leaving it with
  terminal opened to full screen with VIM running on an NFS mounted file
  system. I could type and save at the black monitor screen and see that
  the file got updates from a different system. So the session is "live"
  but the computer has forgotten to re-establish the DisplayPort link.

  An error appears in the lightdm logs about setting a CRTC, if you
  activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
  --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
  you ssh in from a different machine, tell bash to export DISPLAY=:0
  (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the
  screen turns on again! This also happens on a Gigabyte BRIX system
  (same NUC reference design but in that case a core i3 rather than a
  Core i7).

  To reproduce, turn off the monitor, wait an hour, and turn it on
  again.

  You can also kill HUP the lightdm process and that will restart a new
  session (but open windows in the previous session are lost).

  So interesting questions, why does typing xrandr "locally" give you
  the error but running it from an ssh session work?

  Since xrandr and restarting the session can both "fix" the problem,
  the driver seems to know how to turn the display on if told correctly.

  How can I find out where the code is getting the CRTC error?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 12 20:33:01 2016
  InstallationDate: Installed on 2016-05-08 (4 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
  LightdmLog:
   [+80180.09s] DEBUG: Seat seat0 changes active session to 
   [+80189.53s] DEBUG: Seat seat0 changes active session to 64
   [+80222.67s] DEBUG: Seat seat0 changes active session to c4
   [+80222.67s] DEBUG: Session c4 is already active
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581302/+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 1769936] Re: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga 720

[manfreed]

I can confirm this. I tried to record myself speaking and it was as if
everything were overamplified to the point that only distorted noise can
be heard.

Lowering the mic volume helps. Setting it to "base" in puslseaudio
volume control results in audible dialog with just a bit of noise in the
background. Still, my voice felt too quiet, and the quality is not the
best, so it's far from an ideal solution, just a workaround until a fix
comes.

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

Title:
  [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga
  720

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Happy to do further testing, fresh install of Bionic. Discovered this
  when trying to do a video conference using the built in mic and was
  able to verify the issue by installing gnome-sound-recorder.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   asif   2213 F...m pulseaudio
   /dev/snd/controlC0:  asif   2213 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  8 11:58:37 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-04-28 (9 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=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN31WW(V2.03)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN31WW(V2.03):bd03/08/2018:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.family: YOGA 720-15IKB
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1769936/+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 1769936] Re: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga 720

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga
  720

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Happy to do further testing, fresh install of Bionic. Discovered this
  when trying to do a video conference using the built in mic and was
  able to verify the issue by installing gnome-sound-recorder.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   asif   2213 F...m pulseaudio
   /dev/snd/controlC0:  asif   2213 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  8 11:58:37 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-04-28 (9 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=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN31WW(V2.03)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN31WW(V2.03):bd03/08/2018:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.family: YOGA 720-15IKB
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1769936/+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 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files

[lukedd0803]

** Also affects: initramfs-tools
   Importance: Undecided
   Status: New

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space--or provide an automatic tool for
  removal of old files

Status in initramfs-tools:
  New
Status in Ubuntu Software Center:
  Invalid
Status in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1802719] Re: package initramfs-tools 0.131ubuntu15 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  The version of update-initramfs that you likely have
installed is unable to work on a persistent usb stick.  You can resolve
this issue by upgrading the version of casper on your system. This can
be done via the commands:

sudo apt-get update; sudo apt-get install casper

Then performing the software update or installation that you were
originally trying.  If this does not resolve your bug please set its
status back to New.  Thanks in advance!

** Tags added: needs-new-casper

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  package initramfs-tools 0.131ubuntu15 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  I an installing Ubuntu Studio 18.10

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: initramfs-tools 0.131ubuntu15
  ProcVersionSignature: Ubuntu 4.18.0-10.11-lowlatency 4.18.12
  Uname: Linux 4.18.0-10-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CasperVersion: 1.399
  Date: Sun Nov 11 10:50:03 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  LiveMediaBuild: It
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.131ubuntu15 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1802719/+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 1307829] Re: /run/netns/* gets umounted on the host when a container starts

[Panagiotis Moustafellos]

What was the patch exactly, Serge? Is there a link to an upstream sha1?

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

Title:
  /run/netns/* gets umounted on the host when a container starts

Status in iproute package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  Hello,
  I am using latest stables lxc build from 
http://ppa.launchpad.net/ubuntu-lxc/stable/ubuntu on a OpenStack controller to 
run containers. The OpenStack is also using network  namespaces . When I boot 
the server without auto start the containers everything looks fine with the 
OpenStack network namespaces. If I boot lxc container with lxc-start the 
container starts and its networking is functioning, but network namespaces 
created before that , by OpenStack installation for example , become unusable 
with he following error:

   root@osctrl3dc02:~# ip netns exec vips ip a
   seting the network namespace failed: Invalid argument

  Here is the strace:

   open("/var/run/netns/vips", O_RDONLY)   = 4
   syscall_308(0x4, 0x4000, 0x7fffc4d54e83, 0x7fffc4d54bf0, 0x430af0,
   0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
   0, 0, 0) = -1 (errno 22)

   As far as I know sys call_308 should set the namespace , but it seems
  it fails on accessing the /var/run/netns/vips

  It is strange that the permissions are altered: 
  root@osctrl3dc02:~# ls -alh /var/run/netns/vips
   -- 1 root root 0 Apr 14 08:48 /var/run/netns/vips

   This file have the following permission before I start the container
   -r--r--r-- 1 root root 0 Apr 12 14:01 /var/run/netns/vips

   If I destroy the vips namespace and create it again , keeping the lxc
  containers running, everything is back to normal, both containers and
  Openstack networking are working.

  Best regards,

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: iproute 2017-1ubuntu2.1
  ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Tue Apr 15 00:30:18 2014
  InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release 
amd64 (20140204)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: iproute
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute/+bug/1307829/+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 1802719] Re: package initramfs-tools 0.131ubuntu15 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.131ubuntu15 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I an installing Ubuntu Studio 18.10

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: initramfs-tools 0.131ubuntu15
  ProcVersionSignature: Ubuntu 4.18.0-10.11-lowlatency 4.18.12
  Uname: Linux 4.18.0-10-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CasperVersion: 1.399
  Date: Sun Nov 11 10:50:03 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  LiveMediaBuild: It
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.131ubuntu15 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1802719/+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 1802719] [NEW] package initramfs-tools 0.131ubuntu15 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Art]

Public bug reported:

I an installing Ubuntu Studio 18.10

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: initramfs-tools 0.131ubuntu15
ProcVersionSignature: Ubuntu 4.18.0-10.11-lowlatency 4.18.12
Uname: Linux 4.18.0-10-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CasperVersion: 1.399
Date: Sun Nov 11 10:50:03 2018
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
LiveMediaBuild: It
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.0
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.131ubuntu15 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package cosmic

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

Title:
  package initramfs-tools 0.131ubuntu15 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I an installing Ubuntu Studio 18.10

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: initramfs-tools 0.131ubuntu15
  ProcVersionSignature: Ubuntu 4.18.0-10.11-lowlatency 4.18.12
  Uname: Linux 4.18.0-10-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CasperVersion: 1.399
  Date: Sun Nov 11 10:50:03 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  LiveMediaBuild: It
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.131ubuntu15 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1802719/+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 1802718] [NEW] Allow people to do sudo apt-get build-dep without any further configuration

[Ciro Santilli 六四事件 法轮功]

Public bug reported:

Or provide a reliable CLI method, a direct sed on /etc/atp/sources.list
does not feel clean.

Motivation: https://askubuntu.com/questions/496549/error-you-must-put-
some-source-uris-in-your-sources-list

This is specially important for Docker, but also a big annoyance on
desktop, as there is no clean CLI way of enabling it.

Why not just enable by default and save people the trouble?

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

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

Title:
  Allow people to do sudo apt-get build-dep without any further
  configuration

Status in apt package in Ubuntu:
  New

Bug description:
  Or provide a reliable CLI method, a direct sed on
  /etc/atp/sources.list does not feel clean.

  Motivation: https://askubuntu.com/questions/496549/error-you-must-put-
  some-source-uris-in-your-sources-list

  This is specially important for Docker, but also a big annoyance on
  desktop, as there is no clean CLI way of enabling it.

  Why not just enable by default and save people the trouble?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1802718/+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 1802714] [NEW] dont know

[Piyush Dangayach]

Public bug reported:

dont know

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: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 11 15:23:58 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83f9]
   Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:83f9]
InstallationDate: Installed on 2018-10-18 (23 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 0408:51e9 Quanta Computer, Inc. 
 Bus 001 Device 004: ID 2d95:6006  
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Laptop 15-cc1xx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=3198d22f-18f8-4fc6-8db2-0581755ea025 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/22/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.30
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 83F9
dmi.board.vendor: HP
dmi.board.version: 46.53
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.30:bd06/22/2018:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.53:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-cc1xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
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/1802714

Title:
  dont know

Status in xorg package in Ubuntu:
  New

Bug description:
  dont know

  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: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 11 15:23:58 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83f9]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:83f9]
  InstallationDate: Installed on 2018-10-18 (23 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0408:51e9 Quanta Computer, Inc. 
   Bus 001 Device 004: ID 2d95:6006  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Laptop 15-cc1xx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=3198d22f-18f8-4fc6-8db2-0581755ea025 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83F9
  dmi.board.vendor: HP
  dmi.board.version: 46.53
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.30:bd06/22/2018:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.53:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  

[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[hob4bit]

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

This bug still exists on Ubuntu 18.04.1. The problem is when network-
manager is upgraded this the fix in /etc/NetworkManager/conf.d/10
-globally-managed-devices.conf is over-written:

network-manager 1.10.6-2ubuntu1.1

A better workaround for this BUG that the developers refused to fix is:

   echo -e "[keyfile]\nunmanaged-devices=none\n" > \ 
   /usr/lib/NetworkManager/conf.d/11-fix-managed-devices.conf
   systemctl restart network-manager && sleep 1 && nmcli dev

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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