date:20170707

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Rhythmbox + Lexicon Omega External Soundcard = One has to start
  playback twice to start playback

Status in pulseaudio package in Ubuntu:
  Expired
Status in ubuntuone-client package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: ubuntuone-client

  When I try to start playback of a song in Rhythmbox, playback routed to my 
Lexicon Omega External Soundcard, I have to press play, stop, and play again to 
get Rhytmbox to start playing the song.
  This is not a problem when playing through my laptops internal sound card.

  Sincerely
  Trond Haram Klykken

  (I am new to ubuntu. If there is a way to properly format the bug-
  feedback, please let me know)

  ProblemType: Bug
  .home.elektrond..config.ubuntuone.ubuntuone.client.conf:
   [ubuntuone]
   bookmarked = True
   connected = False
   connect = 2
   show_applet = 0
  Architecture: i386
  Date: Thu Dec 17 12:15:43 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  NonfreeKernelModules: nvidia
  Package: ubuntuone-client 1.0.2-0ubuntu2
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: ubuntuone-client
  Uname: Linux 2.6.31-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/497721/+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 487712] Re: pulseaudio dies several times per day

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  pulseaudio dies several times per day

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  I frequently find that sound suddenly stops when I am using Amarok and
  I get a message saying that the connection has been broken. Once this
  has happened, if I then try to make a Skype call, or play a test sound
  in Skype, Skype will freeze. I say that PulseAudio dies because I
  assume that it dies and respawns, but I do not know this for certain.

  I am using Amarok 1.4 from a PPA, as opposed to the version that
  shipped with Kubuntu Jaunty, but I am using the standard Karmic
  PulseAudio.

  One thing I have also noticed is that quite often I try to play a
  Flash video on the Web and I find that the web player is silent. Only
  running killall npviewer.bin and starting again brings the sound back.
  Obviously I suspect this might be connected, but I don't know this for
  certain.

  I have not observed any such misbehaviour AFAIR in connection with any
  other app,

  ProblemType: Bug
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert13725 F pulseaudio
robert22350 F kmix
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe10 irq 17'
 Mixer name : 'Conexant CX20549 (Venice)'
 Components : 'HDA:14f15045,17aa20db,00100100'
 Controls  : 18
 Simple ctrls  : 8
  Date: Tue Nov 24 18:07:37 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31.6-rt19 x86_64
  UserAsoundrc:
   # ALSA library configuration file
   
   # Include settings that are under the control of asoundconf(1).
   # (To disable these settings, comment out this line.)
   

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/487712/+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 515993] Re: Login sound even with disabled/muted internal sound card

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Login sound even with disabled/muted internal sound card

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: alsa-base

  In Sound Preferences, I have disabled and muted my internal sound card
  as I use a headset and simply turn sound back on when required.
  However, even with no headset connected and the internal sound card
  disabled and muted, the short drum sound still plays at a reasonable
  volume from the laptop speakers whenever I start the computer and
  reach the login screen.

  I am running Karmic on a Dell Inspiron 6400 with Intel 82801G (ICH7
  Family) internal audio.

  Thanks,
  James

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/515993/+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 505428] Re: PulseAudio doesn't automatically use surround profile when available

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  PulseAudio doesn't automatically use surround profile when available

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  ALSA by default in Ubuntu 9.10 duplicates front speakers output to the
  rear speakers when in stereo mode (so one can attach headphones to the
  rear output and switch between speakers and headphones easily or use
  less noisy rear output on SBLive! cards). But PulseAudio doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/505428/+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 496354] Re: amixer doesn't seem to unmute audio

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  amixer doesn't seem to unmute audio

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  When i run
  amixer -Dhw:0 set 'Master' unmute
  The volume appears to be unmuted in alsamixer, but the sound is not actually 
unmuted, and all the GUI tools show the sound is muted. 

  I've attached a log, of the following...
  pressing the mute button on my keyboard, so the sound is muted.
  using the unmute command so the sound should be unmuted.
  playing a sound in pidgin, getting no sound, because the sound is still muted.
  hitting the mute button on my keyboard again, which actually unmutes the 
sound.
  playing a sound in pidgin, and getting sound

  I've also attached a screenshot, showing the GUI saying the sound is
  muted, while alsamixer is saying that it isn't.

  Note that while unmute doesn't work, setting the volume does.
  amixer -Dhw:0 set 'Master' 100%
  Works as expected, for example.

  I'm also affected by #352732, maybe related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/496354/+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 511326] Re: crackling sound after installing audio bluetooth headset

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  crackling sound after installing audio bluetooth headset

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: gdm

  Ubuntu 9.10
  Sound plays fine thru speakers.
  I connect audio bluetooth -> sound plays fine thru bluetooth headset
  I disconnect the bluetooth -> no more sound on any choosen device for audio 
output

  ProblemType: Package
  AptOrdering:
   ubuntu-desktop: Purge
   indicator-applet-session: Purge
   indicator-session: Purge
   gdm-guest-session: Purge
   gdm: Purge
  Architecture: i386
  Date: Fri Jan 22 19:58:32 2010
  DistroRelease: Ubuntu 9.10
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: gdm (not installed)
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: gdm
  Title: package gdm (not installed) failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 1
  Uname: Linux 2.6.31-14-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/511326/+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 492136] Re: Empathy Crashes on Video Call

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Empathy Crashes on Video Call

Status in Empathy:
  Invalid
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: empathy

  1) Description: Ubuntu 9.10
  Release: 9.10
  Gnome-Desktop

  2) empathy:
Installed: 2.28.1.1-0ubuntu1
Candidate: 2.28.1.1-0ubuntu1
Version table:
   *** 2.28.1.1-0ubuntu1 0
  500 http://es.archive.ubuntu.com karmic-updates/main Packages
  100 /var/lib/dpkg/status
   2.28.1-1ubuntu1 0
  500 http://es.archive.ubuntu.com karmic/main Packages
  3) Call windows would appear so I could see/hear user
  4) Empathy crashes leaving this error, program trace;

  user@user:~$ empathy
  (empathy:12800): tp-fs-DEBUG: GetSessionHandlers replied: 
  (empathy:12800): tp-fs-DEBUG:   - session 
/org/freedesktop/Telepathy/Connection/gabble/jabber/user_40gmail_2ecom_2fTelepathy_2e81b9e9b9/MediaChannel1
  (empathy:12800): tp-fs-DEBUG: type rtp
  (empathy:12800): tp-fs-DEBUG: adding session handler 
/org/freedesktop/Telepathy/Connection/gabble/jabber/user_40gmail_2ecom_2fTelepathy_2e81b9e9b9/MediaChannel1,
 type rtp
  (empathy:12800): tp-fs-DEBUG: calling MediaSessionHandler::Ready
  (empathy:12800): tp-fs-DEBUG: New stream, stream_id=1, media_type=0, 
direction=3
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
get_all_properties_cb: Adding STUN server 209.85.229.126:19302
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
get_all_properties_cb: Adding relay (udp) 209.85.229.126:19295 
Z61D09ju3YDjMae4:p5n1Yn1DXiieqHgN 1
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
get_all_properties_cb: Adding relay (tcp) 209.85.229.126:19294 
Z61D09ju3YDjMae4:p5n1Yn1DXiieqHgN 1
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
get_all_properties_cb: Adding relay (tls) 209.85.229.126:443 
Z61D09ju3YDjMae4:p5n1Yn1DXiieqHgN 1
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
get_all_properties_cb: Adding relay (udp) 209.85.229.126:19295 
H3fLMg0Do24XF9fg:tTAu6BkB8BWbcQvz 2
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
get_all_properties_cb: Adding relay (tcp) 209.85.229.126:19294 
H3fLMg0Do24XF9fg:tTAu6BkB8BWbcQvz 2
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
get_all_properties_cb: Adding relay (tls) 209.85.229.126:443 
H3fLMg0Do24XF9fg:tTAu6BkB8BWbcQvz 2
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
_tf_stream_try_sending_codecs: called (send_local:1 send_supported:0)
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
_tf_stream_try_sending_codecs: 102: audio SPEEX clock:8000 channels:1
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
_tf_stream_try_sending_codecs: 103: audio SPEEX clock:16000 channels:1
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
_tf_stream_try_sending_codecs: 96: audio SIREN clock:16000 channels:0 
bitrate=16000
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
_tf_stream_try_sending_codecs: 0: audio PCMU clock:8000 channels:0
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
_tf_stream_try_sending_codecs: 8: audio PCMA clock:8000 channels:0
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
_tf_stream_try_sending_codecs: 3: audio GSM clock:8000 channels:0
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
_tf_stream_try_sending_codecs: 99: audio telephone-event clock:16000 channels:0 
events=0-15
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
_tf_stream_try_sending_codecs: 100: audio telephone-event clock:8000 channels:0 
events=0-15
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) fs_codecs_to_tp: 
adding codec SPEEX [102]
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) fs_codecs_to_tp: 
adding codec SPEEX [103]
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) fs_codecs_to_tp: 
adding codec SIREN [96]
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) fs_codecs_to_tp: 
adding codec PCMU [0]
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) fs_codecs_to_tp: 
adding codec PCMA [8]
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) fs_codecs_to_tp: 
adding codec GSM [3]
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) fs_codecs_to_tp: 
adding codec telephone-event [99]
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) fs_codecs_to_tp: 
adding codec telephone-event [100]
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140 (audio) 
_tf_stream_try_sending_codecs: calling MediaStreamHandler::Ready
  (empathy:12800): tp-fs-DEBUG: New stream, stream_id=2, media_type=1, 
direction=3
  (empathy:12800): tp-fs-DEBUG: stream 1 0x86ad140

[Touch-packages] [Bug 410787] Re: totem gives pulseaudio error

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  totem gives pulseaudio error

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Koala Alpha 3
  totem:
Installed: 2.27.2-0ubuntu2
  Expected: Jump to next track in list
  Happened: "pa_stream_get_sink_input_info() failed: Invalid argument" Error 
dialog

  More info about audio here
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/410765
  If something else needed, just ask for it. I've noticed Red Hat guys have 
same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/410787/+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 518851] Re: pulseaudio crash on assertion failure

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  pulseaudio crash on assertion failure

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  I received an email with a realaudio small attachement with kmail
  I double click on the attachement and choose to open it with realplayer
  realplayer opens and starts playing but pulseaudio crashes almost immediately

  ProblemType: Bug
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pascal 3201 F kmix
pascal12233 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfdff4000 irq 22'
 Mixer name : 'Realtek ALC888'
 Components : 'HDA:10ec0888,a0a0062d,0011'
 Controls  : 24
 Simple ctrls  : 14
  Date: Mon Feb  8 15:47:39 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4.1
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-19-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/518851/+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 502493] Re: Configuring the process priorites of pulseaudio is buggy

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Configuring the process priorites of pulseaudio is buggy

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  I still have issues with crackling startup sound and occasional
  stutters in xine. I tried to fix it by reconfiguring pulseaudio. Doing
  this I think I found several small bugs.

  I read about the ongoing changes in pulseaudio and rtkit. Some of the
  bugs might get solved anyway. I opened this bug report to find out if
  my findings are bugs and that they all get fixed in 10.04. I use
  Ubuntu 9.10 (Karmic) with pulseaudio 1:0.9.19-0ubuntu4. For my
  pulseaudio config see bug #265010, comment 12 and 13.

  Bug A: "high-priority = no" doesn't work. It's always enabled.
  Bug B: "realtime-scheduling = yes" doesn't work in Karmic, even if log says 
it does!
  Bug C: rlimit-nice > 31 is clipped down to 31, which is weird and needless 
IMHO.

  To verify bug B, I invoke "chrt -p -v $(ps -C pulseaudio -o pid=)".
  According to http://pulseaudio.org/wiki/UbuntuBugs bug B is already
  known, but the misleading log message should be corrected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/502493/+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 526201] Re: No sound from Analog Devices AD1884

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  No sound from Analog Devices AD1884

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Codec: Analog Devices AD1884

  00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/526201/+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 496304] Re: Sound's not working

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Sound's not working

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  Toten sound our moovida sound don't work, I coudn't identify what was
  missing.

  ProblemType: Bug
  Architecture: i386
  Date: Sun Dec 13 19:02:30 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/totem
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANGUAGE=pt_BR.UTF-8
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/496304/+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 543448] Re: module-loopback falls back to looping mic to speakers

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  module-loopback falls back to looping mic to speakers

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  I'm using module-loopback to hear A2DP music from my phone, as
  described at:

  http://jprvita.wordpress.com/2009/12/15/1-2-3-4-a2dp-stream/

  This works, but when my phone disconnects from A2DP for any reason
  (e.g. I walk away or turn bluetooth off) module-loopback remains
  loaded and decides instead to play audio from my microphone to my
  speakers, giving horrible feedback noises as you would expect.

  I would like a parameter for this module, perhaps fallback=[boolean],
  so I can say that when the phone goes away, just get rid of this
  module/instance instead of moving to another source. For now I will
  locally patch may_move_to to return false.

  ProblemType: Bug
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cmb2197 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
 Mixer name : 'Realtek ALC888'
 Components : 'HDA:10ec0888,1458e601,0011'
 Controls  : 39
 Simple ctrls  : 21
  Date: Sun Mar 21 14:24:41 2010
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: pulseaudio 1:0.9.19-0ubuntu4.1
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-20-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/543448/+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 534482] Re: PulseAudio: Unable to create stream: Too large

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  PulseAudio: Unable to create stream: Too large

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  I have been frustrated with sound failures for as long as pulseaudio
  has been a part of Linux, and I'm trying my best to diagnose problems.
  In Ubuntu 9.10, I'm finding that when some apps run, no other app can
  output sound, and they just freeze. If I am running mythfrontend, and
  try to play a video from gnome-terminal, the video doesn't even start.
  When I exit mythfrontend, the video starts. Likewise, any alert sounds
  (like from pidgin) all play after mythfrontend exits, which is
  extremely annoying.  If I play a streamed Flash movie in Firefox, most
  of the time any app that tries to output sound after it will be
  silent, and eventually sound won't work from Flash either.

  I tried running firefox in debug mode, and saw some interesting
  output. The relevant portion is HUNDREDS of lines saying

  "ALSA lib pcm_pulse.c:724:(pulse_prepare) PulseAudio: Unable to create
  stream: Too large".

  I searched the PA bug database and didn't find that phrase in any
  existing bugs. I did see mention of that error in Fedora
  https://bugzilla.redhat.com/show_bug.cgi?id=554568 but with different
  circumstances.

  This is supposedly fixed in PA itself according to lennart.  See
  http://pulseaudio.org/ticket/797

  $ lsb_release -rd
  Description:  Ubuntu 9.10  Release:   9.10

  $ apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:0.9.19-0ubuntu4.1
Candidate: 1:0.9.19-0ubuntu4.1
Version table:
   *** 1:0.9.19-0ubuntu4.1 0
  500 http://us.archive.ubuntu.com karmic-updates/main Packages
  100 /var/lib/dpkg/status
   1:0.9.19-0ubuntu4 0
  500 http://us.archive.ubuntu.com karmic/main Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/534482/+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 410047] Re: totem not playing video files "Disconnected: Connection terminated"

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  totem not playing video files "Disconnected: Connection terminated"

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: totem

  i install jaunty and upgraded to karmic today (karmic's installed
  gives me grub grief), so the system is pretty clean, and i have not
  altered any settings related to audio/video.

  i tried to play an ogg video file big_buck_bunny_1080p_stereo.ogg from 
blender.org. it struggles to play a few frames, and then i get a dialog
  "An error occurred
  Disconnected: Connection terminated"

  i see the following in xsession-errors,
  ** Message: Error: Disconnected: Connection terminated
  pulsesink.c(266): gst_pulsering_is_dead (): 
/GstPlayBin2:play/GstPlaySink:playsink0/GstBin:abin/GstBin:audiosinkbin/GstGConfAudioSink:audio-sink/GstBin:bin5/GstAutoAudioSink:autoaudiosink1/GstPulseSink:autoaudiosink1-actual-sink-pulse
  (whole log attached).

  this may be related to   Bug #348002

  ProblemType: Bug
  Architecture: amd64
  Date: Thu Aug  6 21:08:45 2009
  DistroRelease: Ubuntu 9.10
  Package: totem 2.27.2-0ubuntu2
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SourcePackage: totem
  Uname: Linux 2.6.31-5-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/410047/+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 475997] Re: after upgrade to karmic during audio playback a high-frequency whistling can be heard

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  after upgrade to karmic during audio playback a high-frequency
  whistling can be heard

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  with pulseaudio configured for 5.1 sound output there is a high-frequency 
whistle when playing audio files, independent from the application. when i turn 
the 5.1 sound output to normal stereo output the whistle is gone.
  sound onboard: (Mainboard)ALiveSATA2-GLAN (Soundchip)Premium Level HD Audio 
(ALC888 Audio Codec)
  with a Creative 5.1 speaker system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/475997/+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 529853] Re: pulseaudio reports asyncq overrun and ratelimit.c supressed messages

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  pulseaudio reports asyncq overrun and ratelimit.c supressed messages

Status in pulseaudio package in Ubuntu:
  Expired
Status in pulseaudio source package in Lucid:
  Won't Fix

Bug description:
  Binary package hint: pulseaudio

  This could be similar to bug 480802, however I didn't see any
  indication of the asyncq.c overrun messages, so I'm opening a new one.

  I noticed this while looking into an Xorg crash on Karmic 64bit.  In
  addition to the thousands of lines of ratelimit.c supressed messages,
  I noticed a few that said this:

  Feb 28 23:01:45 klaatu pulseaudio[2034]: asyncq.c: q overrun, queuing locally
  Feb 28 23:01:51 klaatu pulseaudio[2034]: last message repeated 10 times

  See attached files for hardware specs.

  This affects pulesaudio.
  My expectations:
  1: eliminate the flooding of syslogd wtih those ratelimit.c messages
  2: understand the asyncq.c overrun messages

  Audio can be somewhat choppy regardless of whether I'm streaming or
  playing files locally.  I normally would expect that of a system
  running as many apps as I may be running at any given moment, however,
  on this system:

  Core i7 Quadcore w/ HT - 16 cores total
  4GB ram

  I would really not expect choppy audio at all unless I was doing
  something incredibly extreme.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bladernr  12444 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf0f2 irq 22'
 Mixer name : 'IDT 92HD83C1X5'
 Components : 'HDA:111d7604,102802a2,00100104'
 Controls  : 28
 Simple ctrls  : 17
  CheckboxSubmission: 89874cc6062c150ee1cec9632b63a0a3
  CheckboxSystem: 5f30ac82cc48ed91bb5240b61cb4e295
  Date: Sun Feb 28 23:34:44 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  NonfreeKernelModules: nvidia
  Package: pulseaudio 1:0.9.19-0ubuntu4.1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-19-generic x86_64
  XsessionErrors:
   (gnome-settings-daemon:12459): GLib-CRITICAL **: g_propagate_error: 
assertion `src != NULL' failed
   (gnome-settings-daemon:12459): GLib-CRITICAL **: g_propagate_error: 
assertion `src != NULL' failed
   (polkit-gnome-authentication-agent-1:12574): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:12555): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (firefox:12718): GLib-WARNING **: g_set_prgname() called multiple times

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/529853/+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 511562] Re: When sound at remote sink, sound doesn't work

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  When sound at remote sink, sound doesn't work

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  I'm not sure if this bug is in flashplugin-installer or pulseaudio.

  Problem:

  When I use Firefox or Chrome for watching a flash video from Youtube
  for example, all works good. I then transfer the sound to a remote
  sink using Sound Preferences > Output > Internal Audio Analog Stereo
  on myuser@otherhost.

  After this is done, the flash video halts. This is also true if I
  restart firefox and start a new video, already having transferred the
  sound. Sometimes you can see the video taking huge skips forward. For
  example, on a 3 minute music video, I see 3-4 different frames from
  different places in the video.

  The sound is OK though!

  100% reproducible and if I transfer the sound back to local speakers
  the video resumes and plays perfectly.

  Edit:

  This doesn't affect just flash, it affects pretty much all
  applications I can think of.

  I have narrowed it down to a buffer underrun problem and I can
  reproduce it by starting a mp3 with rhythmbox, a Xvid video with VLC,
  a wav-file with aplay etc.

  ProblemType: Bug
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thnov 10738 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf910 irq 22'
     Mixer name : 'Realtek ALC889A'
     Components : 'HDA:10ec0885,1458a002,00100101'
     Controls  : 43
     Simple ctrls  : 24
  Date: Sat Jan 23 14:17:18 2010
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_DK.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/511562/+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 481213] Re: pulseaudio-module-lirc : NO Notifications on screen

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  pulseaudio-module-lirc : NO Notifications on screen

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: notify-osd

  I've successfully configured Karmic to change volume via my MCE remote, LIRC.
  The only missing piece is ON SCREEN NOTIFICATIONS:

  - When I press volume+ / volume- on keyboard, the notification comes
  up nicely as it should. OK.

  - When I press volume+ / volume- on REMOTE, volume goes up/down, but
  NO notification is shown on screen. BUG.

  In my opinion, very important piece for those who use Ubuntu as a
  living room mediacenter.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: ALC1200 Analog [ALC1200 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  living 1840 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xefff4000 irq 29'
 Mixer name : 'Realtek ALC1200'
 Components : 'HDA:10ec0888,103c2a65,00100101'
 Controls  : 31
 Simple ctrls  : 19
  Date: Thu Nov 12 10:48:38 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 
(20091028.4)
  NonfreeKernelModules: nvidia
  Package: pulseaudio-module-lirc 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
  SourcePackage: pulseaudio
  Tags:  ubuntu-unr
  Uname: Linux 2.6.31-15-generic i686
  XsessionErrors:
   (gnome-settings-daemon:1887): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:1887): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (nautilus:1912): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (polkit-gnome-authentication-agent-1:1940): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
  mtime.conffile..etc.pulse.daemon.conf: 2009-11-12T09:33:55.216262
  mtime.conffile..etc.pulse.default.pa: 2009-11-12T10:16:58.051574

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/481213/+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 545592] Re: dummy output, no sound on HDA Intel internal sound card

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  dummy output, no sound on HDA Intel internal sound card

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  On Lucid Lynx daily build from 22th march, my sound card is detected
  as HDA Intel, but there is no input device, there is only one output
  device called Dummy output, and there is no sound anymore. Two weeks
  ago with Alpha 3 everything worked, so this might be a regression, if
  I understand the term correctly.

  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', 
'/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 21'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,102801cc,00102201 
HDA:14f12bfa,14f100c3,0009'
 Controls  : 12
 Simple ctrls  : 7
  Date: Tue Mar 23 23:40:39 2010
  DistroRelease: Ubuntu 10.04
  LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100322)
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu12
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  SourcePackage: pulseaudio
  Uname: Linux 2.6.32-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/545592/+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 408784] Re: [karmic] No sound output with pulseaudio

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [karmic] No sound output with pulseaudio

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  Ubuntu 9.10 a3 updated on 04.08.2009
  pulseaudio 0.9.15-4ubuntu3
  alsa-base-1.0.20+dfsg-1ubuntu4

  According to sound preferences I have output source as it says "Internal 
sound card". I have HDA Intel ICH8 internal audio on HP Pavilion dv2530. When 
my laptop starts I hear a "click" from the speakers like the device is in 
power-saving mode (it is because it has such row in 
/etc/modprobe.d/alsa-base.conf). Also I hear it every time I click on an icon 
in the gnome-panel for example.
  The strange thing is that Rhythmbox and other apps are runnig well like there 
IS all OK with the sound - but I can't hear it at all. I've installed all 
pulseaudio related GUI tools to view the output levels - there're acceptable 
high.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/408784/+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 570015] Re: Fast respawning when module-alsa-sink can't be loaded

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Fast respawning when module-alsa-sink can't be loaded

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Ah, got it. Pulseaudio won't start (under my user's account) because
  of:

  E: module.c: Failed to load module "module-alsa-sink" (argument: 
"device=plughw:0 rate=44100"): initialization failed.
  E: main.c: Module load failed.
  E: main.c: Failed to initialize daemon.

  And that module was specified in ~/.pulse/default.pa, which is a
  leftover from the time when pulseaudio wasn't working and I was trying
  to do something about it.

  So I deleted ~/.pulse/default.pa, stopped pulseaudio that was started
  by hand and polkitd is still behaving perfectly fine. Even the music
  is playing, although I have no pulseaudio running. :-)

  Then I killed polkitd and it wasn't restarted. So I started pulseudio
  by hand (from my user's account) and then polkitd appeared. It's
  peacefully sleeping in poll() and isn't leaking memory.

  --

  Original report:

  
  Binary package hint: policykit-1

  Upon upgrading to the new build of Lucid, a problem I thought I had
  fixed with policykit has reappeared.  i am getting high CPU usage and
  a memory leak from the process polkitd, run under policykit-1.  Upon
  boot and logging into a fresh account, I get no problems, but once I
  log into my main account, the problem appears.  Logging out and back
  into the fresh account carries the problem over to the fresh account
  as well.  I noticed that there were three carry-over processes from
  the main account: indicator-sound, pulseaudio, and the root process
  polkitd.  I thought I had fixed this through removing respawnable
  hidden directories in my home folder, but that hasn't worked this
  time.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: policykit-1 0.96-2
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Mon Apr 26 00:17:42 2010
  ExecutablePath: /usr/lib/policykit-1/polkitd
  ProcEnviron:

  SourcePackage: policykit-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/570015/+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 575910] Re: "sudo pactl list" fails with "Connection refused"

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  "sudo pactl list" fails with "Connection refused"

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  since jaunty, I used a script which check whether music is played.
  It uses the following command:

  
  $ pactl list | grep RUNNING

  
  The script is called from rc.local, and as such, it is run by root.
  While in jaunty and karmic, everything works great,
  a fresh install of Lucid lets the script die.

  If I type in

  $ sudo pactl list | grep RUNNING

  it gives me the error:

  Home directory /home/produnis not ours.
  Connection refused

  I don't know what this means, as the script isn't stored in my home-
  folder, and it does no actions in my home-folder

  In sum:
  Running the comand as user "produnis", everything works well
  Running the comand as root, it gives me the error.
  Unfortunately, I MUST run the script as root (due to other action it does),
  so, is there any hint why it is not working any longer?
  [Running Lucid 64bit with current updates]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/575910/+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 577490] Re: After upgrade to Lucid, muting one channel mutes all

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  After upgrade to Lucid, muting one channel mutes all

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: alsa-utils

  When I mute any of channels(Front, Surround, Center, LFE, Side) in alsamixer 
of kmix the effect is the same as muting channel Master or all seperately - no 
sound at all. In karmic those worked properly. I'm using following entry in 
/etc/modprobe.d/alsa-base.conf:
  options snd-hda-intel model=lenovo-sky power_save=10 power_save_controller=Y

  and have loaded following modules:
  lsmod | grep snd
  snd_hda_codec_nvhdmi 4760  1 
  snd_hda_codec_si3054 4236  1 
  snd_hda_codec_realtek   278890  1 
  snd_seq_dummy   1782  0 
  snd_hda_intel  25645  10 
  snd_seq_oss31219  0 
  snd_hda_codec  85727  4 
snd_hda_codec_nvhdmi,snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel
  snd_seq_midi5829  0 
  snd_pcm_oss41394  0 
  snd_mixer_oss  16299  1 snd_pcm_oss
  snd_rawmidi23388  1 snd_seq_midi
  snd_pcm87850  8 
snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec,snd_pcm_oss
  snd_seq_midi_event  7267  2 snd_seq_oss,snd_seq_midi
  snd_hwdep   6924  1 snd_hda_codec
  snd_seq57417  6 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
  snd_timer  23553  2 snd_pcm,snd_seq
  snd_seq_device  6824  5 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
  snd70978  29 
snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel,snd_seq_oss,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_rawmidi,snd_pcm,snd_hwdep,snd_seq,snd_timer,snd_seq_device
  soundcore   8052  1 snd
  snd_page_alloc  8500  2 snd_hda_intel,snd_pcm

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-utils 1.0.22-0ubuntu5
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sat May  8 17:28:34 2010
  ProcEnviron:
   LANGUAGE=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-utils

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/577490/+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 570984] Re: [Realtek ALC883] pactl stat failed to find default card

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [Realtek ALC883] pactl stat failed to find default card

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  There is no audio in Lucid AMD64 with this audio controller.

  The sound worked when I first installed, then simply stopped working.
  I can get sound if I forcibly remove Pulseaudio, but of course I'd
  rather not take that drastic step.  I am only mentioning it because it
  might help debug the issue.

  When I look in my sound properties under Hardware, I see a "Dummy
  Output" device, but the real hardware is not found.

  Again, sound is completely unusable (nonexistent) unless I remove
  Pulseaudio.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfccf4000 irq 22'
 Mixer name : 'Silicon Image SiI1392 HDMI'
 Components : 'HDA:10ec0883,1043829f,0012 
HDA:10951392,,0010'
 Controls  : 40
 Simple ctrls  : 22
  Date: Tue Apr 27 18:29:40 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 
(20100419.1)
  PactlStat:
   
  PactlStatStderr:
   C o n n e c t i o n   f a i l u r e :   C o n n e c t i o n   r e f u s e d 
p a _ c o n t e x t _ c o n n e c t ( )   f a i l e d :   C o n n e c t i o 
n   r e f u s e d
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: pulseaudio
  Symptom: audio
  Title: [Realtek ALC883] pactl stat failed to find default card
  dmi.bios.date: 07/16/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0604
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5E-VM HDMI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.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.:bvr0604:bd07/16/2008:svnSystemmanufacturer:pnP5E-VMHDMI:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E-VMHDMI:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5E-VM HDMI
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/570984/+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 575840] Re: Bad pulseaudio volumen levels

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Bad pulseaudio volumen levels

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  My computer is a Dell Studio XPS 16 with Ubuntu 9.10 (also affects
  Lucid 10.04).

  The volume levels setted by Pulseaudio are incorrectly sent to Alsa. It 
causes to mute volume with 15% of the volume shown by pulseaudio; at that 
value, the master control of alsa is set to 0.
  The soundcard is IDT 92HD73C1X5

  ProblemType: Bug
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc40 irq 22'
 Mixer name : 'IDT 92HD73C1X5'
 Components : 'HDA:111d7675,10280272,00100103'
 Controls  : 24
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xcfeec000 irq 17'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [off]
  Date: Wed May  5 17:01:24 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  NonfreeKernelModules: fglrx
  Package: pulseaudio 1:0.9.19-0ubuntu4.1
  ProcEnviron:
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-20-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/575840/+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 572580] Re: Video Playback in lucid stuttering

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Video Playback in lucid stuttering

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I reinstalled (not upgraded) from Karmic to Lucid yesterday, and I
  have serious issues now when trying to playback videos.

  I tried several players, including Totem, Mplayer and VLC, and all of
  them show the same symptoms. When playing a video, every minute or so
  the video hangs for half a second and the audio stutters, then the
  playback resumes until the next hang. So much about the symptoms.

  When looking at "top", I also saw that the CPU usage of of Xorg and
  compiz raises from 5%/5% to about 20%/20%. I surely already tried to
  disable compiz, but that didn't solve the problem. When looking at
  various logfiles, I also recognized the following error message
  repeating in /var/log/messages, but it those messages did not appear
  in sync with the stuttering:

  pulseaudio[2049]: ratelimit.c: 2 events suppressed

  I am using the NVidia binary driver by the way, running a GeForce GTX
  240, if that is in any way relevant.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/572580/+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 574137] Re: Toshiba NB30500F pulseaudio problem

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
Toshiba NB30500F pulseaudio problem

Status in pulseaudio package in Ubuntu:
Expired

Bug description:
Binary package hint: pulseaudio

Toshiba NB305007 netbook. Ubuntu 10.04 LTS - lucid.
2.6.32.21-generic, running ubuntu-netbook-remix. Problem with
pulseaudio (1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14) . Boot
machine and open a gnome-terminal window. At the CLI, hit backspace.
You will hear the normal ping/bong. Hit the backspace key a few more
times and the sound suddenly changes to a scratchy peep, or may
disappear altogether. If I wait 10 seconds the sound returns to
normal but repeatedly hitting the key causes the same effect. If I
play a song using Rhythmbox the sound goes crappy after a few minutes.
Or I can purposefully make it go bad by hitting the backspace key a
few times in the gnome terminal window.

I have tried all of the common remedies of adding asus-mode4 to the
end of the options snd-hda-intel line in /etc/modprobe.d/alsa-
base.conf. I tried many different combinations of default-fragments
and default-fragments-size-msec in /etc/pulse/daemon.conf, all to no
avail.

If I purge pulseaudio (apt-get purge pulseaudio) and reboot, the sound
is fine although some other sound things do not work as expected (no
volume control). But rhythmbox, sound recorder and twinkle all work.

NOTE: Purging pulseaudio removes ubuntu-desktop, ubuntu-netbook and
ubuntu-netbook remix. But rebooting brings the machine up just fine.

If I reinstall pulseaduio, the problems come back... leading me to
believe that the problem is with pulseaudio.

Any help or ideas would be much appreciated. Thanks

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
AlsaVersion:
Advanced Linux Sound Architecture Driver Version 1.0.22.1.
Compiled on Apr 14 2010 for kernel 2.6.32-21-generic (SMP).
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jim1171 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x40a0 irq 30'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,1179ff30,0011'
Controls : 18
Simple ctrls : 11
Date: Sun May 2 18:41:51 2010
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386
(20091028.4)
ProcEnviron:
PATH=(custom, no user)
LANG=en_CA.utf8
SHELL=/bin/bash
SourcePackage: pulseaudio
dmi.bios.date: 01/14/2010
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.30
dmi.board.name: NPVAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnTOSHIBA:bvrV1.30:bd01/14/2010:svnTOSHIBA:pnTOSHIBANB305:pvrPLL3AC-00F014:rvnTOSHIBA:rnNPVAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: TOSHIBA NB305
dmi.product.version: PLL3AC-00F014
dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/574137/+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 572378] Re: Apr 26 19:53:22 sat-inder-laptop pulseaudio[1694]: alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Apr 26 19:53

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Apr 26 19:53:22 sat-inder-laptop pulseaudio[1694]: alsa-sink.c: ALSA
  woke us up to write new data to the device, but there was actually
  nothing to write! Apr 26 19:53:22 sat-inder-laptop pulseaudio[1694]:
  alsa-sink.c: Most likely this is a bug in the ALSA driver
  'snd_hda_intel'.

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: gnome-utils

  Apr 26 19:53:22 sat-inder-laptop pulseaudio[1694]: alsa-sink.c: ALSA woke us 
up to write new data to the device, but there was actually nothing to write!
  Apr 26 19:53:22 sat-inder-laptop pulseaudio[1694]: alsa-sink.c: Most likely 
this is a bug in the ALSA driver 'snd_hda_intel'.

  ProblemType: Bug
  Architecture: i386
  Date: Fri Apr 30 19:57:15 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gnome-system-log
  InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 
(20091028.4)
  Package: gnome-utils 2.28.1-0ubuntu1
  ProcEnviron:
   LANG=en_IN
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
  SourcePackage: gnome-utils
  Tags:  ubuntu-unr
  Uname: Linux 2.6.31-20-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/572378/+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 572063] Re: [NO SOUND] 10.04 - Intel Corporation 82801H HD Audio Controller (rev 03)

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [NO SOUND] 10.04 - Intel Corporation 82801H HD Audio Controller (rev
  03)

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  1)
  rprice@alienware:~/Desktop$ lsb_release -rd
  Description:  Ubuntu 10.04 LTS
  Release:  10.04

  -
  2)
  rprice@alienware:~/Desktop$ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
    Candidate: 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
    Version table:
   *** 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 0
  500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
  100 /var/lib/dpkg/status

  -
  3)
  Audio to work after installation with both analog and digital (HDMI)

  -
  4)
  Audio does not work after installation.  I have been able to get it working 
by making a file under /etc/modprobe.d with the following:

  $ cat /etc/modprobe.d/sound
  options snd_hda_intel model=mbp3

  The problem with this is when I go to use HDMI out to my TV, I have to
  change analog to digital.  When I am done, if I want audio back on the
  laptop, I have to switch from digital to analog.  It doesn't "Just
  work".  Please let me know if I need to upload any other information.
  I am not very good with audio issues.  ;(

  
  -


  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rprice 1447 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf060 irq 22'
     Mixer name : 'Realtek ALC889A'
     Components : 'HDA:10ec0885,152d0770,00100103'
     Controls  : 22
     Simple ctrls  : 12
  Date: Fri Apr 30 01:58:26 2010
  ExecutablePath: /usr/bin/pulseaudio
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:1466): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (gnome-terminal:1562): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion 
`entry != NULL && entry->lock_count > 0' failed
  dmi.bios.date: 08/29/2008
  dmi.bios.vendor: Quanta
  dmi.bios.version: vX36 P3
  dmi.board.name: m15x
  dmi.board.vendor: Alienware
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnQuanta:bvrvX36P3:bd08/29/2008:svnAlienware:pnm15x:pvrNotApplicable:rvnAlienware:rnm15x:rvrNotApplicable:cvnAlienware:ct1:cvrN/A:
  dmi.product.name: m15x
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/572063/+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 574504] Re: Regression, system does not capture sound from microphone

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Regression, system does not capture sound from microphone

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  Looks like its a regression on 10.04.

  1. Boot Karmic 9.04 LiveCD (Kubuntu). Install skype, turn up all bars
  in KMix. Make test call - skype works well, it hears my voice.

  
  2. Boot Lucid Lynx 10.04. Do the same - skype does not hear my voice. At the 
same time I can hear my voice in headset in real time. But for some reason it 
does not be recordered.

  
  Tried:

  1. Install pulseaudio - no effect

  2. Installed linux-backports-modules-alsa-lucid-generic, no effect.

  3. Tried to set mono input using pavucontrol - no effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  AlsaVersion:
   Advanced Linux Sound Architecture Driver Version 1.0.22.1.
   Compiled on Apr 14 2010 for kernel 2.6.32-21-generic (SMP).
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: ALC262 Analog [ALC262 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: ALC262 Analog [ALC262 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alexey 1574 F pulseaudio
alexey 1598 F kmix
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xc000 irq 16'
 Mixer name : 'Realtek ALC262'
 Components : 'HDA:11c11040,2118144d,00100200 
HDA:10ec0262,144dc036,0012'
 Controls  : 17
 Simple ctrls  : 11
  Date: Mon May  3 17:02:27 2010
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427)
  ProcEnviron:
   LANGUAGE=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UserAsoundrc:
   pcm.pulse { type pulse }
   ctl.pulse { type pulse }
  dmi.bios.date: 04/30/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 04YE
  dmi.board.name: R40P/R41P
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr04YE:bd04/30/2007:svnSAMSUNGELECTRONICSCO.,LTD.:pnR40P/R41P:pvr04YE:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR40P/R41P:rvr:cvnSAMSUNGELECTRONICSCO.,LTD.:ct1:cvrN/A:
  dmi.product.name: R40P/R41P
  dmi.product.version: 04YE
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/574504/+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 571987] Re: Only first 20% of the volume slider works

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Only first 20% of the volume slider works

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  In Karmic, the volume slider worked correctly. Now in Lucid pulse is
  setting PCM to 100%, and the first 20% of the volume applet slider
  controls 100% of the 'front' channel. This means that you can't get
  much granularity in the control and it's very easy to have it far too
  loud.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: VT1708S Analog [VT1708S Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robin  1778 F pulseaudio
   /dev/snd/pcmC0D0p:   robin  1778 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xf7ff4000 irq 16'
 Mixer name : 'VIA VT1708S'
 Components : 'HDA:11060397,104383b7,0010'
 Controls  : 28
 Simple ctrls  : 16
  Date: Fri Apr 30 13:42:16 2010
  ProcEnviron:
   LANGUAGE=nl_NL:nl
   PATH=(custom, user)
   LANG=nl_NL.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 07/17/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2A74-AM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd07/17/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A74-AM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/571987/+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 574513] Re: Sound mute by default on fresh installation

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Sound mute by default on fresh installation

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  This is a fresh installation of Ubuntu on my PC. On starting the PC
  after installation I observed that sound is muted by default. Not a
  major problem but can be confusing to new users.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  onkar  1283 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'V8237'/'VIA 8237 with ALC658D at 0xe000, irq 22'
 Mixer name : 'Realtek ALC658D'
 Components : 'AC97a:414c4781'
 Controls  : 45
 Simple ctrls  : 27
  CurrentDmesg:
   [   22.480041] eth0: no IPv6 routers present
   [   27.320048] end_request: I/O error, dev fd0, sector 0
   [   27.364081] end_request: I/O error, dev fd0, sector 0
  Date: Mon May  3 19:44:10 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 12/19/2003
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 3.06
  dmi.board.name: Kamet2
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 2.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr3.06:bd12/19/2003:svnCompaqPresario061:pnDT381A-ACJS6020ILIN430:pvr01H0411LX101KAME210:rvnASUSTekComputerINC.:rnKamet2:rvr2.01:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: DT381A-ACJ S6020IL IN430
  dmi.product.version: 01H0411LX101KAME210
  dmi.sys.vendor: Compaq Presario 061

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/574513/+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 577587] Re: installing earcandy brokes pulseaudio server

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  installing earcandy brokes pulseaudio server

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  I've installed Earcandy and it broken my pulseaudio server. I couldn't
  hear any music from Rhythmbox or the login sound.

  I'm running Ubuntu 10.04 LTS 64bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/577587/+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 577727] Re: Ubuntu 10.04 sound lag with enemy territory quake wars

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Ubuntu 10.04 sound lag with enemy territory quake wars

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  To reproduce:
  Install Ubuntu 10.04 x64
  Install drivers and update ubuntu
  Install enemy territory quake wars demo or full game
  Start a game vs computer
  Fire gun in air
  Sometimes takes a moment or 2 to start lagging.  Starts lagging when the 
sound apparently disappears.

  demo available at http://www.fileplanet.com/181742/18/fileinfo
  /Enemy-Territory:-Quake-Wars-Demo-%28Linux%29

  Apparently works on Kubuntu according to 
http://ubuntuforums.org/showpost.php?p=9246877=5
  I've not been able to get it to even start on Kubuntu (executable not found) 
however

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  2085 F pulseaudio
   /dev/snd/controlC1:  chris  2085 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'D2'/'Asus Virtuoso 200 (rev 2) at 0xe800, irq 16'
 Mixer name : 'AV200'
 Components : 'PCM1796 CS5381 AV200'
 Controls  : 23
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'Intel'/'HDA Intel at 0xf7ff8000 irq 22'
 Mixer name : 'VIA ID 4441'
 Components : 'HDA:11064441,104383d0,00100100'
 Controls  : 4
 Simple ctrls  : 3
  Date: Sun May  9 09:09:53 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1207
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D LE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.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.:bvr1207:bd12/07/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DLE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/577727/+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 1689825] Re: gnome-keyring not unlocked on boot

2017-07-07 Thread 513G3

FWIW, my problem started after installing PPAs about a week before I
first posted here (June 17).  I just checked my /etc/apt/sources.list
and it was last modified June 10.  Perhaps it is coincidence... but
right when some PPAs went in, my problem started.

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1689825] Re: gnome-keyring not unlocked on boot

2017-07-07 Thread 513G3

@MikeRushton... do you have any PPAs installed on your machines without
flatpak?

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1689825] Re: gnome-keyring not unlocked on boot

2017-07-07 Thread Mike Rushton

It does not have anything to do with flatpack or pitivi. I have several
machines experiencing this issue and have never installed either of the
mentioned packages on any of them in any point in time.

** Changed in: flatpak (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1597909] Re: systemd-timesyncd unit still running after installation of ntp package

2017-07-07 Thread David Britton

@andreserl -- does this just fill up the error log on old releases or is
there a functional impact?

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

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

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

Title:
  systemd-timesyncd unit still running after installation of ntp package

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Incomplete
Status in ntp source package in Zesty:
  Incomplete

Bug description:
  I recently installed the ntp package on a fairly vanilla installed-
  from-DVD Xenial system, and noticed that after the package
  installation both systemd-timesyncd and ntp were running:

  # systemctl status ntp systemd-timesyncd.service --no-pager
   ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: active (running) since Tue 2016-06-28 19:21:16 HDT; 6min ago
   Docs: man:systemd-sysv-generator(8)
 CGroup: /system.slice/ntp.service
 3364 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 112:118

  [...log lines...]

   systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 `-disable-with-time-daemon.conf
 Active: active (running) since Sun 2016-06-26 06:53:05 HDT; 2 days ago
   Docs: man:systemd-timesyncd.service(8)
   Main PID: 821 (systemd-timesyn)
 Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)."
 CGroup: /system.slice/systemd-timesyncd.service
 821 /lib/systemd/systemd-timesyncd

  [...log lines...]

  I was able to do "systemctl stop systemd-timesyncd.service" manually
  without any trouble, but presumably if I hadn't noticed the situation
  I might have had problems with the two services both running
  simultaneously until my next reboot.

  (Once the systemd-timesyncd service is stopped, it is prevented from
  starting again by the constraint in the disable-with-time-daemon.conf
  file.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1597909/+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 1597909] Re: systemd-timesyncd unit still running after installation of ntp package

2017-07-07 Thread Andres Rodriguez

FWIW, this issue is still present in older releases. Effectively, if NTP
is installed and configured to access X ntp server and timesyncd would
still try to fallback to ntp.ubuntu.com.

In proxied environments, this will result in ntp.ubuntu.com being
unavailable.

** Also affects: ntp (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: ntp (Ubuntu Xenial)
   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/1597909

Title:
  systemd-timesyncd unit still running after installation of ntp package

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Incomplete
Status in ntp source package in Zesty:
  Incomplete

Bug description:
  I recently installed the ntp package on a fairly vanilla installed-
  from-DVD Xenial system, and noticed that after the package
  installation both systemd-timesyncd and ntp were running:

  # systemctl status ntp systemd-timesyncd.service --no-pager
   ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: active (running) since Tue 2016-06-28 19:21:16 HDT; 6min ago
   Docs: man:systemd-sysv-generator(8)
 CGroup: /system.slice/ntp.service
 3364 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 112:118

  [...log lines...]

   systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 `-disable-with-time-daemon.conf
 Active: active (running) since Sun 2016-06-26 06:53:05 HDT; 2 days ago
   Docs: man:systemd-timesyncd.service(8)
   Main PID: 821 (systemd-timesyn)
 Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)."
 CGroup: /system.slice/systemd-timesyncd.service
 821 /lib/systemd/systemd-timesyncd

  [...log lines...]

  I was able to do "systemctl stop systemd-timesyncd.service" manually
  without any trouble, but presumably if I hadn't noticed the situation
  I might have had problems with the two services both running
  simultaneously until my next reboot.

  (Once the systemd-timesyncd service is stopped, it is prevented from
  starting again by the constraint in the disable-with-time-daemon.conf
  file.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1597909/+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 1597909] Re: systemd-timesyncd unit still running after installation of ntp package

2017-07-07 Thread David Britton

Hi There, thanks for the bug report --

This is fixed in the Ubuntu development release: Artful.  ntpd now ships
a systemd job that conflicts with systemd-timesyncd.service that
prevents the duplicate service running.  Confirmed on a deployment of
the latest Artful as of this comment.


** Changed in: ntp (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  systemd-timesyncd unit still running after installation of ntp package

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Incomplete
Status in ntp source package in Zesty:
  Incomplete

Bug description:
  I recently installed the ntp package on a fairly vanilla installed-
  from-DVD Xenial system, and noticed that after the package
  installation both systemd-timesyncd and ntp were running:

  # systemctl status ntp systemd-timesyncd.service --no-pager
   ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: active (running) since Tue 2016-06-28 19:21:16 HDT; 6min ago
   Docs: man:systemd-sysv-generator(8)
 CGroup: /system.slice/ntp.service
 3364 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 112:118

  [...log lines...]

   systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 `-disable-with-time-daemon.conf
 Active: active (running) since Sun 2016-06-26 06:53:05 HDT; 2 days ago
   Docs: man:systemd-timesyncd.service(8)
   Main PID: 821 (systemd-timesyn)
 Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)."
 CGroup: /system.slice/systemd-timesyncd.service
 821 /lib/systemd/systemd-timesyncd

  [...log lines...]

  I was able to do "systemctl stop systemd-timesyncd.service" manually
  without any trouble, but presumably if I hadn't noticed the situation
  I might have had problems with the two services both running
  simultaneously until my next reboot.

  (Once the systemd-timesyncd service is stopped, it is prevented from
  starting again by the constraint in the disable-with-time-daemon.conf
  file.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1597909/+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 1664352] Re: dhclient-script doesn't use configured metric for rfc3442 classless routes

2017-07-07 Thread Bug Watch Updater

** Changed in: isc-dhcp (Debian)
   Status: Unknown => New

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

Title:
  dhclient-script doesn't use configured metric for rfc3442 classless
  routes

Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Debian:
  New

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  apt-cache policy isc-dhcp-client
  isc-dhcp-client:
Installed: 4.3.3-5ubuntu12.6
Candidate: 4.3.3-5ubuntu12.6
Version table:
   *** 4.3.3-5ubuntu12.6 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.3.3-5ubuntu12 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  If the metric option is set in interfaces(5), dhclient is executed
  with the variable IF_METRIC set to the configured administrative
  metric. The exit-hook rfc3442-classless-routes doesn't use the
  variable; thus, a multi-interface box will experience a race condition
  if multiple interfaces are supplied with one or more duplicate rfc3442
  routes. The attached patch adds support for IF_METRIC handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1664352/+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 1702362] Re: problems

2017-07-07 Thread Emily Ratliff

** 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/1702362

Title:
  problems

Status in xorg package in Ubuntu:
  New

Bug description:
  will not let me update system and acting really strange

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jul  4 17:08:32 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GF108GLM [NVS 5200M] [10de:0dfc] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GF108GLM [NVS 5200M] [1028:0534]
  InstallationDate: Installed on 2017-04-18 (77 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E6430
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=c36db0d7-9f05-4cd1-8ce1-00042da07481 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702362/+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 1701934] Re: Atualice ubuntu de 14.04 a 16.04

2017-07-07 Thread Emily Ratliff

** 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/1701934

Title:
  Atualice ubuntu de 14.04 a 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  El equipo se quedo sin sonido. Si me pueden ayudar se los agradecere,
  muchas gracias.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  BootLog:
   [[0;32m  OK  [0m] Started LSB: Speech Dispatcher.
   [[0;32m  OK  [0m] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
   [[0;32m  OK  [0m] Started LSB: daemon to balance interrupts for SMP 
systems.
   [[0;32m  OK  [0m] Started LSB: automatic crash report generation.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jul  2 13:12:05 2017
  DistUpgraded: 2017-07-01 00:35:39,611 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems 82945G/GZ Integrated Graphics 
Controller [1019:2624]
  InstallationDate: Installed on 2017-07-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: ECS 945GCT-M
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=e86093a6-2464-45b8-8808-4e5bd3501687 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (1 days ago)
  dmi.bios.date: 11/07/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080012
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 945GCT-M
  dmi.board.vendor: Intel
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080012:bd11/07/2007:svnECS:pn945GCT-M:pvr2.0:rvnIntel:rn945GCT-M:rvr2.0:cvnECS:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 945GCT-M
  dmi.product.version: 2.0
  dmi.sys.vendor: ECS
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  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 Jul  1 21:29:01 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSTV06xx  KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Generic Wheel Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17519 
   vendor GSM
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1701934/+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 1703048] [NEW] package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-07-07 Thread George Fisher

Public bug reported:

Preparing to unpack .../click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb ...
Cannot start click due to a conflict with a different locally-installed Python 
'click' package.  Remove it using Python packaging tools and try again.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Cannot start click due to a conflict with a different locally-installed Python 
'click' package.  Remove it using Python packaging tools and try again.
dpkg: error processing archive 
/var/cache/apt/archives/click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb 
(--unpack):
 subprocess new pre-removal script returned error exit status 1
Job for click-system-hooks.service failed because the control process exited 
with error code.
See "systemctl status click-system-hooks.service" and "journalctl -xe" for 
details.
click-system-hooks.service couldn't start.
Errors were encountered while processing:
 /var/cache/apt/archives/click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

lsb_release -rd
Description:Ubuntu 16.10
Release:16.10


apt-cache policy click
click:
  Installed: 0.4.45.1+16.10.20160916-0ubuntu1
  Candidate: 0.4.46+16.10.20170607.3-0ubuntu1
  Version table:
 0.4.46+16.10.20170607.3-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
 *** 0.4.45.1+16.10.20160916-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: click 0.4.45.1+16.10.20160916-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-54.57-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.3-0ubuntu8.3
AptOrdering:
 click:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Jul  7 13:13:19 2017
DpkgHistoryLog:
 Start-Date: 2017-07-07  13:13:18
 Commandline: apt-get -f install
 Requested-By: george (1000)
 Upgrade: click:amd64 (0.4.45.1+16.10.20160916-0ubuntu1, 
0.4.46+16.10.20170607.3-0ubuntu1)
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2017-01-10 (178 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1.1
 apt  1.3.5
SourcePackage: click
Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in click package in Ubuntu:
  New

Bug description:
  Preparing to unpack .../click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb ...
  Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
  dpkg: warning: subprocess old pre-removal script returned error exit status 1
  dpkg: trying script from the new package instead ...
  Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
  dpkg: error processing archive 
/var/cache/apt/archives/click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb 
(--unpack):
   subprocess new pre-removal script returned error exit status 1
  Job for click-system-hooks.service failed because the control process exited 
with error code.
  See "systemctl status click-system-hooks.service" and "journalctl -xe" for 
details.
  click-system-hooks.service couldn't start.
  Errors were encountered while processing:
   /var/cache/apt/archives/click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  
  apt-cache policy click
  click:
Installed: 0.4.45.1+16.10.20160916-0ubuntu1
Candidate: 0.4.46+16.10.20170607.3-0ubuntu1
Version table:
   0.4.46+16.10.20170607.3-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
   *** 0.4.45.1+16.10.20160916-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: click 0.4.45.1+16.10.20160916-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-54.57-generic 4.8.17
  Uname: Linux

Re: [Touch-packages] [Bug 1702726] [NEW] dnsmasq fails when the ARP cache is full

2017-07-07 Thread Simon Kelley

Testing this, the results are not quite as clear-cut as the example. I
don't always see the same errors.

Also, I don't understand why the send() calls in dig, which are sending
UDP packets over the loopback interface, should return the invalid
argument. ARP is not needed over loopback, surely?

Looking at an strace of dnsmasq, what I see is that either the query
never arrives at dnsmasq, or it gets answered correctly but the answers
never makes it back to dig: the UDP packets are being dropped in the
kernel. (In the later case, the send() of the reply gets the same
invalid argument error that dig is seeing)

The lesson here is that if the arp-cache overflows, UDP, (even over lo)
drops packets. There's really not much dnsmasq can do about that. I
guess the only answer is "don't let your arp-cache overflow".

(or possibly, work on getting the kernel to behave better under these
circumstances)

TL;DR not a dnsmasq bug.

Cheers,

Simon.

On 06/07/17 18:17, Christopher Berner wrote:
> Public bug reported:
> 
> Test setup:
> OS: Ubuntu 16.04
> Hardware: D15_v2 VM on Azure
> 
> Steps to reproduce:
> 1) sudo apt-get install dnsmasq
> 2) sudo sysctl -w net.ipv4.neigh.default.gc_thresh1=1
> 3) sudo sysctl -w net.ipv4.neigh.default.gc_thresh2=1
> 4) sudo sysctl -w net.ipv4.neigh.default.gc_thresh3=1
> 5) dig @127.0.0.1 google.com
> 
> Result: 
> ~$ dig @127.0.0.1 google.com
> ../../../../lib/isc/unix/socket.c:2104: internal_send: 127.0.0.1#53: Invalid 
> argument
> ../../../../lib/isc/unix/socket.c:2104: internal_send: 127.0.0.1#53: Invalid 
> argument
> ../../../../lib/isc/unix/socket.c:2104: internal_send: 127.0.0.1#53: Invalid 
> argument
> 
> ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @127.0.0.1 google.com
> ; (1 server found)
> ;; global options: +cmd
> ;; connection timed out; no servers could be reached 
> 
> However, an external DNS server still works fine (dig @8.8.8.8
> google.com, for example).
> 
> We discovered this as the default max ARP cache size is 1024, and we're
> running a large cluster with a lot of intra-cluster network traffic.
> Increasing the size of the ARP cache solves this problem, but it seems
> like dnsmasq should still work and just be slow, like other applications
> (curl for example just takes longer to connect)
> 
> ** Affects: dnsmasq (Ubuntu)
>  Importance: Undecided
>  Status: New
>

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

Title:
  dnsmasq fails when the ARP cache is full

Status in dnsmasq package in Ubuntu:
  Confirmed

Bug description:
  Test setup:
  OS: Ubuntu 16.04
  Hardware: D15_v2 VM on Azure

  Steps to reproduce:
  1) sudo apt-get install dnsmasq
  2) sudo sysctl -w net.ipv4.neigh.default.gc_thresh1=1
  3) sudo sysctl -w net.ipv4.neigh.default.gc_thresh2=1
  4) sudo sysctl -w net.ipv4.neigh.default.gc_thresh3=1
  5) dig @127.0.0.1 google.com

  Result: 
  ~$ dig @127.0.0.1 google.com
  ../../../../lib/isc/unix/socket.c:2104: internal_send: 127.0.0.1#53: Invalid 
argument
  ../../../../lib/isc/unix/socket.c:2104: internal_send: 127.0.0.1#53: Invalid 
argument
  ../../../../lib/isc/unix/socket.c:2104: internal_send: 127.0.0.1#53: Invalid 
argument

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @127.0.0.1 google.com
  ; (1 server found)
  ;; global options: +cmd
  ;; connection timed out; no servers could be reached 

  However, an external DNS server still works fine (dig @8.8.8.8
  google.com, for example).

  We discovered this as the default max ARP cache size is 1024, and
  we're running a large cluster with a lot of intra-cluster network
  traffic. Increasing the size of the ARP cache solves this problem, but
  it seems like dnsmasq should still work and just be slow, like other
  applications (curl for example just takes longer to connect)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1702726/+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 1664352] Re: dhclient-script doesn't use configured metric for rfc3442 classless routes

2017-07-07 Thread Matt Heller

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

** Also affects: isc-dhcp (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867625
   Importance: Unknown
   Status: Unknown

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

Title:
  dhclient-script doesn't use configured metric for rfc3442 classless
  routes

Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Debian:
  Unknown

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  apt-cache policy isc-dhcp-client
  isc-dhcp-client:
Installed: 4.3.3-5ubuntu12.6
Candidate: 4.3.3-5ubuntu12.6
Version table:
   *** 4.3.3-5ubuntu12.6 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.3.3-5ubuntu12 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  If the metric option is set in interfaces(5), dhclient is executed
  with the variable IF_METRIC set to the configured administrative
  metric. The exit-hook rfc3442-classless-routes doesn't use the
  variable; thus, a multi-interface box will experience a race condition
  if multiple interfaces are supplied with one or more duplicate rfc3442
  routes. The attached patch adds support for IF_METRIC handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1664352/+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 1615342] Re: variable of $new_rfc3442_classless_static_routes has spelling error in /sbin/dhclient-script

2017-07-07 Thread Matt Heller

FYI this bug is fixed in newer versions, see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748272

So perhaps this bug can be closed?

--Matt

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

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

Title:
  variable of $new_rfc3442_classless_static_routes has spelling error
  in /sbin/dhclient-script

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  version lastest ubuntu 14.04.5
  isc-dhcp-client version 4.2.4-7ubuntu12
  bug code location /sbin/dhclient-script line 275 and line 354

  
  logic of ignore the router option defined in rfc3442 is not performing 
correctly

  >   If the DHCP server returns both a Classless Static Routes option and
  >   a Router option, the DHCP client MUST ignore the Router option.
  >
  >   Similarly, if the DHCP server returns both a Classless Static Routes
  >   option and a Static Routes option, the DHCP client MUST ignore the
  >   Static Routes option.

  reason is spelling error of the variable
  "$new_rfc3442_classless_static_routes" error to
  "$new_rfc3442_classless_static_routers" . just correct the name to fix
  this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1615342/+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 1489651] Re: Bluetooth audio not working (with GDM(3))

2017-07-07 Thread Doug McMahon

For 17.10 fresh install the best solution was just the "disable pulseaudio's 
bluetooth in gdm", i.e.
Add this to /var/lib/gdm3/.config/pulse/default.pa:

#!/usr/bin/pulseaudio -nF
#

# load system wide configuration
.include /etc/pulse/default.pa

### unload driver modules for Bluetooth hardware
.ifexists module-bluetooth-policy.so
  unload-module module-bluetooth-policy
.endif

.ifexists module-bluetooth-discover.so
  unload-module module-bluetooth-discover
.endif

Nothing more needed...

It almost seems the Debian upstream bug assumes one would get audio thru 
bluetooth, just not A2DP.
Here on my speaker it's A2DP or nothing so as it stands now there is nothing..

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

Title:
  Bluetooth audio not working (with GDM(3))

Status in PulseAudio:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in gdm3 package in Debian:
  New

Bug description:
  I'm having problems with a Marshall Stanmore bluetooth speaker in
  Ubuntu GNOME 15.10 Beta.  It pairs fine and is listed as a bluetooth
  device but won't show up in the audio settings as a device nor will it
  show up with pactl list. I also had this problem in Ubuntu GNOME 15.04
  with the gnome-staging 3.16 ppa. It works fine with stock Ubuntu GNOME
  15.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1489651/+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 1652531] Re: gnuradio gqrx-sdr missing qt 5 svg dependency

2017-07-07 Thread Dmitry Shachnev

The difference between Debian and Ubuntu here is that Ubuntu uses -Wl
,--as-needed linker flag [1].

The Debian build log [2] contains this line:

dpkg-shlibdeps: warning: package could avoid a useless dependency if
debian/gqrx-sdr/usr/bin/gqrx was not linked against libQt5Svg.so.5 (it
uses none of the library's symbols)

It means that the build system links the binary with libQt5Svg.so.5, but
the dependency is not actually used. Because Ubuntu uses -Wl,--as-
needed, that library is not linked, and so the dependency does not get
added.

If the application uses SVG icons, it should add the dependency on
libqt5svg5 explicitly. I will also add that libqt5gui5 recommends
libqt5svg5, so this package will usually be installed. We cannot make it
a hard dependency because that will introduce a circular dependency.

So this is not a bug in qtsvg-opensource-src.

[1] https://wiki.ubuntu.com/ToolChain/CompilerFlags#A-Wl.2C--as-needed
[2] 
https://buildd.debian.org/status/fetch.php?pkg=gqrx-sdr=amd64=2.6-1%2Bb1=1480595463

** Changed in: qtsvg-opensource-src (Ubuntu)
   Status: New => Invalid

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

Title:
  gnuradio gqrx-sdr missing qt 5 svg dependency

Status in gqrx-sdr package in Ubuntu:
  New
Status in qtsvg-opensource-src package in Ubuntu:
  Invalid

Bug description:
  gnuradio gqrx-sdr is using SVG icons in toolbar but is not listing qt
  5 svg as a dependency. Therefore, these icons appear broken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gqrx-sdr/+bug/1652531/+subscriptions

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

Re: [Touch-packages] [Bug 1700937] Re: Heap-buffer overflow in nodeAcquire

2017-07-07 Thread Seth Arnold

On Fri, Jul 07, 2017 at 07:01:41PM -, Even Rouault wrote:
> @seth There's an error regarding the SQLite version number in the CVE
> text. It should read "in SQLite before 3.17.0" (and not 3.11.0)

Oh that's unfortuate. I didn't say it was fixed in -any- version in
my submission, because it felt to me the 3.17.0 was an accidental
no-longer-triggered case not actually fixed-case. After all, the fix
was checked into a master branch and no new releases appear to have been
tagged afterwards.

Thanks for the sharp eyes. I've submitted a change request.

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

Title:
  Heap-buffer overflow in nodeAcquire

Status in sqlite3 package in Ubuntu:
  New

Bug description:
  A heap-buffer overflow (sometimes a crash) can arise when running a
  SQL request on malformed sqlite3 databases such as the one attached to
  this ticket

  {{{
  $ valgrind sqlite3 clusterfuzz-testcase-minimized-4960347410661376 "SELECT 
pkid FROM 'idx_byte_metadata_geometry' WHERE xmax > 0 AND xmin < 0 AND ymax > 0 
AND ymin < 0"
  ==21234== Memcheck, a memory error detector
  ==21234== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==21234== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==21234== Command: sqlite3 clusterfuzz-testcase-minimized-4960347410661376 
SELECT\ pkid\ FROM\ 'idx_byte_metadata_geometry'\ WHERE\ xmax\ \>\ 0\ AND\ 
xmin\ \<\ 0\ AND\ ymax\ \>\ 0\ AND\ ymin\ \<\ 0
  ==21234== Invalid read of size 1
  ==21234==at 0x1B3945: nodeAcquire (in /usr/bin/sqlite3)
  ==21234==by 0x1B5056: rtreeFilter (in /usr/bin/sqlite3)
  ==21234==by 0x186EAA: sqlite3VdbeExec (in /usr/bin/sqlite3)
  ==21234==by 0x190316: sqlite3_step (in /usr/bin/sqlite3)
  ==21234==by 0x11886F: shell_exec.constprop.12 (in /usr/bin/sqlite3)
  ==21234==by 0x114693: main (in /usr/bin/sqlite3)
  ==21234==  Address 0x5ae5b00 is 0 bytes after a block of size 48 alloc'd
  ==21234==at 0x4C2DB8F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==21234==by 0x14C176: sqlite3MemMalloc (in /usr/bin/sqlite3)
  ==21234==by 0x128380: sqlite3Malloc (in /usr/bin/sqlite3)
  ==21234==by 0x1B38DF: nodeAcquire (in /usr/bin/sqlite3)
  ==21234==by 0x1B5056: rtreeFilter (in /usr/bin/sqlite3)
  ==21234==by 0x186EAA: sqlite3VdbeExec (in /usr/bin/sqlite3)
  ==21234==by 0x190316: sqlite3_step (in /usr/bin/sqlite3)
  ==21234==by 0x11886F: shell_exec.constprop.12 (in /usr/bin/sqlite3)
  ==21234==by 0x114693: main (in /usr/bin/sqlite3)
  }}}

  This bug is no longer reproducible with at least sqlite3 3.17

  {{{
  $ valgrind ~/install-sqlite-3.17.0/bin/sqlite3 
clusterfuzz-testcase-minimized-4960347410661376 "SELECT pkid FROM 
'idx_byte_metadata_geometry' WHERE xmax > 0 AND xmin < 0 AND ymax > 0 AND ymin 
< 0"
  ==21265== Memcheck, a memory error detector
  ==21265== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==21265== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==21265== Command: /home/even/install-sqlite-3.17.0/bin/sqlite3 
clusterfuzz-testcase-minimized-4960347410661376 SELECT\ pkid\ FROM\ 
'idx_byte_metadata_geometry'\ WHERE\ xmax\ \>\ 0\ AND\ xmin\ \<\ 0\ AND\ ymax\ 
\>\ 0\ AND\ ymin\ \<\ 0
  ==21265== 
  Error: database disk image is malformed
  }}}

  This bug has been originally uncovered by OSS-Fuzz when running on the
  GDAL library that uses libsqlite3: https://bugs.chromium.org/p/oss-
  fuzz/issues/detail?id=2405 (content not viewable during the grace
  period)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: sqlite3 3.11.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed Jun 28 11:18:29 2017
  InstallationDate: Installed on 2016-11-04 (235 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: sqlite3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1700937/+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 1702921] Re: package util-linux 2.29-1ubuntu2 [modified: bin/dmesg bin/lsblk bin/more bin/mountpoint bin/tailf bin/wdctl sbin/agetty] failed to install/upgrade: package util-linu

2017-07-07 Thread Seth Arnold

This may be a duplicate of bug 1692981.

** Information type changed from Private Security to Public

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

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

Title:
  package util-linux 2.29-1ubuntu2 [modified: bin/dmesg bin/lsblk
  bin/more bin/mountpoint bin/tailf bin/wdctl sbin/agetty] failed to
  install/upgrade: package util-linux is not ready for configuration
  cannot configure (current status 'half-installed')

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  installing update - update stalled

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2 [modified: bin/dmesg bin/lsblk bin/more 
bin/mountpoint bin/tailf bin/wdctl sbin/agetty]
  ProcVersionSignature: Ubuntu 4.10.0-26.30-lowlatency 4.10.17
  Uname: Linux 4.10.0-26-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri Jul  7 15:55:01 2017
  DpkgTerminalLog:
   dpkg: error processing package util-linux (--configure):
package util-linux is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package util-linux is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-11-03 (245 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package util-linux 2.29-1ubuntu2 [modified: bin/dmesg bin/lsblk 
bin/more bin/mountpoint bin/tailf bin/wdctl sbin/agetty] failed to 
install/upgrade: package util-linux is not ready for configuration  cannot 
configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1702921/+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 925916] Re: package libdvdread4 4.2.0-1ubuntu3 failed to install/upgrade: libdvdread4:i386 4.2.0-1ubuntu3 (Multi-Arch)

2017-07-07 Thread Sebastian Ramacher

This has been fixed.

** Changed in: libdvdread (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  package libdvdread4 4.2.0-1ubuntu3 failed to install/upgrade:
  libdvdread4:i386 4.2.0-1ubuntu3 (Multi-Arch)

Status in libdvdread package in Ubuntu:
  Fix Released

Bug description:
  If the i386 files are installed or attempted to be installed when the
  amd64 version of libdrmread4 is already installed, it can lead to
  upgrade failures.

  [Original Report]
  Used Movie Player to watch a mpeg2 video. Mplayer reported that codecs were 
missing. Got the problem report, when installing gstreamer ugly codecs.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libdvdread4 4.2.0-1ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
  Uname: Linux 3.2.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Fri Feb  3 09:07:29 2012
  DuplicateSignature:
   Unpacking libx264-120:i386 (from 
.../libx264-120_2%3a0.120.2127+gitf33c8cb-2ubuntu2_i386.deb) ...
   Selecting previously unselected package liba52-0.7.4:i386.
   dpkg: error processing 
/var/cache/apt/archives/liba52-0.7.4_0.7.4-16_i386.deb (--unpack):
    liba52-0.7.4:i386 0.7.4-16 (Multi-Arch: no) is not co-installable with 
liba52-0.7.4:amd64 0.7.4-16 (Multi-Arch: no) which is currently installed
  ErrorMessage: libdvdread4:i386 4.2.0-1ubuntu3 (Multi-Arch
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120130)
  SourcePackage: libdvdread
  Title: package libdvdread4 4.2.0-1ubuntu3 failed to install/upgrade: 
libdvdread4:i386 4.2.0-1ubuntu3 (Multi-Arch
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2017-07-07 Thread Eddie Losper

DEAR STEVE,

I DON'T KNO'W WHY THIS IS STIL ON MY COMPUTER, BECAUSE I DON'T USE UBUNTU 
ANYMORE.
I AM USING VODAFONE.

THIS CAN BE DELETED FROM MY COMPUTER PLEASE.

REGARDS,

EDDIE LOSPER  
 
From: Steve Langasek
Date: 2017-07-07 15:18
To: losper.eddie
Subject: [Bug 349469] Re: debconf: DbDriver "config": 
/var/cache/debconf/config.dat is locked by another process: Resource 
temporarily unavailable
** Changed in: debconf (Ubuntu)
 Assignee: MAYANK SHUKLA (mayankgonda) => (unassigned)
 
-- 
You received this bug notification because you are subscribed to
Aptdaemon.
https://bugs.launchpad.net/bugs/349469
 
Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable
 
Status in Aptdaemon:
  Confirmed
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Triaged
Status in debconf package in Ubuntu:
  Triaged
 
Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:
 
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable
 
To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+subscriptions

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Confirmed
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Triaged
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)

2017-07-07 Thread Robin King

Many, many thanks, Jesse, for the fix! I have been using an ASUS N-13
adaptor, and up to Ubuntu 17.04 had no trouble. At first I suspected the
adaptor and bought another one - quite unnecessarily as it turns out.
Fortunately I had my little old friend, an ASUS Eee (also running Ubuntu
17.04), to help me, and so I was able to use it to ferret about, finally
ending up at your posting. It worked! Evidently - and fortunately for me
- the "improvement" to the network manager doesn't affect the Eee wifi
card.

Couldn't agree more with the above comments about the irresponsibility
of the development team in fielding such a vital piece of software
without very careful and extensive testing. Shame on you lot! There are
probably a lot of ordinary users like me out there who just don't have a
clue what is happening now their network connection isn't working.

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

Title:
  Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi
  adapters from working (MAC Address Randomization issue)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  According to 
  
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
  there is a new privacy feature in the new version of NetworkManager.
  This privacy feature can cause some USB WiFi adapters to stop working
  while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).

  The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
  This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.

  The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
  The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.

  Original report follows:

  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every
  time I make it forget my wifi settings and try to reconnect. Weird,
  right? Any leads on a possible fix or work-around?

  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.

  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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 1700937] Re: Heap-buffer overflow in nodeAcquire

2017-07-07 Thread Even Rouault

@seth There's an error regarding the SQLite version number in the CVE
text. It should read "in SQLite before 3.17.0" (and not 3.11.0)

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

Title:
  Heap-buffer overflow in nodeAcquire

Status in sqlite3 package in Ubuntu:
  New

Bug description:
  A heap-buffer overflow (sometimes a crash) can arise when running a
  SQL request on malformed sqlite3 databases such as the one attached to
  this ticket

  {{{
  $ valgrind sqlite3 clusterfuzz-testcase-minimized-4960347410661376 "SELECT 
pkid FROM 'idx_byte_metadata_geometry' WHERE xmax > 0 AND xmin < 0 AND ymax > 0 
AND ymin < 0"
  ==21234== Memcheck, a memory error detector
  ==21234== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==21234== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==21234== Command: sqlite3 clusterfuzz-testcase-minimized-4960347410661376 
SELECT\ pkid\ FROM\ 'idx_byte_metadata_geometry'\ WHERE\ xmax\ \>\ 0\ AND\ 
xmin\ \<\ 0\ AND\ ymax\ \>\ 0\ AND\ ymin\ \<\ 0
  ==21234== Invalid read of size 1
  ==21234==at 0x1B3945: nodeAcquire (in /usr/bin/sqlite3)
  ==21234==by 0x1B5056: rtreeFilter (in /usr/bin/sqlite3)
  ==21234==by 0x186EAA: sqlite3VdbeExec (in /usr/bin/sqlite3)
  ==21234==by 0x190316: sqlite3_step (in /usr/bin/sqlite3)
  ==21234==by 0x11886F: shell_exec.constprop.12 (in /usr/bin/sqlite3)
  ==21234==by 0x114693: main (in /usr/bin/sqlite3)
  ==21234==  Address 0x5ae5b00 is 0 bytes after a block of size 48 alloc'd
  ==21234==at 0x4C2DB8F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==21234==by 0x14C176: sqlite3MemMalloc (in /usr/bin/sqlite3)
  ==21234==by 0x128380: sqlite3Malloc (in /usr/bin/sqlite3)
  ==21234==by 0x1B38DF: nodeAcquire (in /usr/bin/sqlite3)
  ==21234==by 0x1B5056: rtreeFilter (in /usr/bin/sqlite3)
  ==21234==by 0x186EAA: sqlite3VdbeExec (in /usr/bin/sqlite3)
  ==21234==by 0x190316: sqlite3_step (in /usr/bin/sqlite3)
  ==21234==by 0x11886F: shell_exec.constprop.12 (in /usr/bin/sqlite3)
  ==21234==by 0x114693: main (in /usr/bin/sqlite3)
  }}}

  This bug is no longer reproducible with at least sqlite3 3.17

  {{{
  $ valgrind ~/install-sqlite-3.17.0/bin/sqlite3 
clusterfuzz-testcase-minimized-4960347410661376 "SELECT pkid FROM 
'idx_byte_metadata_geometry' WHERE xmax > 0 AND xmin < 0 AND ymax > 0 AND ymin 
< 0"
  ==21265== Memcheck, a memory error detector
  ==21265== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==21265== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==21265== Command: /home/even/install-sqlite-3.17.0/bin/sqlite3 
clusterfuzz-testcase-minimized-4960347410661376 SELECT\ pkid\ FROM\ 
'idx_byte_metadata_geometry'\ WHERE\ xmax\ \>\ 0\ AND\ xmin\ \<\ 0\ AND\ ymax\ 
\>\ 0\ AND\ ymin\ \<\ 0
  ==21265== 
  Error: database disk image is malformed
  }}}

  This bug has been originally uncovered by OSS-Fuzz when running on the
  GDAL library that uses libsqlite3: https://bugs.chromium.org/p/oss-
  fuzz/issues/detail?id=2405 (content not viewable during the grace
  period)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: sqlite3 3.11.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed Jun 28 11:18:29 2017
  InstallationDate: Installed on 2016-11-04 (235 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: sqlite3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1700937/+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 1702985] [NEW] Change expired password dialog missing

2017-07-07 Thread Joshua Burgess

Public bug reported:

On Ubuntu-mate 16.04.2, with FreeIPA 4.3.1.0, SSSD 1.13.4-1  and LightDM
1.18.3 (with lightdm-gtk-greeter 2.0.1-2) I am not seeing the normal
prompts that should come up when a user's password has expired. When a
user attempts to log in with an expired password, they should be
notified that their password has expired, and then prompted to re-enter
their current password. If their current password is accepted, they
should then be prompted to enter a new password. If that password meets
the system's requirements, they should then be prompted to enter their
new password a second time to confirm it.

On my system I am seeing the first message, the user is informed that
their password has expired and must be changed. However, I am not seeing
any subsequent prompts. The user is presented with a blank password
field three times with no instruction. Their login will succeed if they
know they need to enter their current password, press enter, enter their
new password, press enter, and then enter their new password again, and
press enter, there is just no dialog to inform them of this.

If I install GDM on the same system and set it as the default, it works
correctly. A text notification is displayed, telling the user what to
enter in the password field (i.e "Current Password", "New Password",
"Confirm New Password"). If I install the Unity-greeter that comes with
Ubuntu 16.04 standard, it also works correctly.

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

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

Title:
  Change expired password dialog missing

Status in lightdm package in Ubuntu:
  New

Bug description:
  On Ubuntu-mate 16.04.2, with FreeIPA 4.3.1.0, SSSD 1.13.4-1  and
  LightDM 1.18.3 (with lightdm-gtk-greeter 2.0.1-2) I am not seeing the
  normal prompts that should come up when a user's password has expired.
  When a user attempts to log in with an expired password, they should
  be notified that their password has expired, and then prompted to re-
  enter their current password. If their current password is accepted,
  they should then be prompted to enter a new password. If that password
  meets the system's requirements, they should then be prompted to enter
  their new password a second time to confirm it.

  On my system I am seeing the first message, the user is informed that
  their password has expired and must be changed. However, I am not
  seeing any subsequent prompts. The user is presented with a blank
  password field three times with no instruction. Their login will
  succeed if they know they need to enter their current password, press
  enter, enter their new password, press enter, and then enter their new
  password again, and press enter, there is just no dialog to inform
  them of this.

  If I install GDM on the same system and set it as the default, it
  works correctly. A text notification is displayed, telling the user
  what to enter in the password field (i.e "Current Password", "New
  Password", "Confirm New Password"). If I install the Unity-greeter
  that comes with Ubuntu 16.04 standard, it also works correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1702985/+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 1700937] Re: Heap-buffer overflow in nodeAcquire

2017-07-07 Thread Seth Arnold

Use CVE-2017-10989.

Thanks

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-10989

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

Title:
  Heap-buffer overflow in nodeAcquire

Status in sqlite3 package in Ubuntu:
  New

Bug description:
  A heap-buffer overflow (sometimes a crash) can arise when running a
  SQL request on malformed sqlite3 databases such as the one attached to
  this ticket

  {{{
  $ valgrind sqlite3 clusterfuzz-testcase-minimized-4960347410661376 "SELECT 
pkid FROM 'idx_byte_metadata_geometry' WHERE xmax > 0 AND xmin < 0 AND ymax > 0 
AND ymin < 0"
  ==21234== Memcheck, a memory error detector
  ==21234== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==21234== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==21234== Command: sqlite3 clusterfuzz-testcase-minimized-4960347410661376 
SELECT\ pkid\ FROM\ 'idx_byte_metadata_geometry'\ WHERE\ xmax\ \>\ 0\ AND\ 
xmin\ \<\ 0\ AND\ ymax\ \>\ 0\ AND\ ymin\ \<\ 0
  ==21234== Invalid read of size 1
  ==21234==at 0x1B3945: nodeAcquire (in /usr/bin/sqlite3)
  ==21234==by 0x1B5056: rtreeFilter (in /usr/bin/sqlite3)
  ==21234==by 0x186EAA: sqlite3VdbeExec (in /usr/bin/sqlite3)
  ==21234==by 0x190316: sqlite3_step (in /usr/bin/sqlite3)
  ==21234==by 0x11886F: shell_exec.constprop.12 (in /usr/bin/sqlite3)
  ==21234==by 0x114693: main (in /usr/bin/sqlite3)
  ==21234==  Address 0x5ae5b00 is 0 bytes after a block of size 48 alloc'd
  ==21234==at 0x4C2DB8F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==21234==by 0x14C176: sqlite3MemMalloc (in /usr/bin/sqlite3)
  ==21234==by 0x128380: sqlite3Malloc (in /usr/bin/sqlite3)
  ==21234==by 0x1B38DF: nodeAcquire (in /usr/bin/sqlite3)
  ==21234==by 0x1B5056: rtreeFilter (in /usr/bin/sqlite3)
  ==21234==by 0x186EAA: sqlite3VdbeExec (in /usr/bin/sqlite3)
  ==21234==by 0x190316: sqlite3_step (in /usr/bin/sqlite3)
  ==21234==by 0x11886F: shell_exec.constprop.12 (in /usr/bin/sqlite3)
  ==21234==by 0x114693: main (in /usr/bin/sqlite3)
  }}}

  This bug is no longer reproducible with at least sqlite3 3.17

  {{{
  $ valgrind ~/install-sqlite-3.17.0/bin/sqlite3 
clusterfuzz-testcase-minimized-4960347410661376 "SELECT pkid FROM 
'idx_byte_metadata_geometry' WHERE xmax > 0 AND xmin < 0 AND ymax > 0 AND ymin 
< 0"
  ==21265== Memcheck, a memory error detector
  ==21265== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==21265== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==21265== Command: /home/even/install-sqlite-3.17.0/bin/sqlite3 
clusterfuzz-testcase-minimized-4960347410661376 SELECT\ pkid\ FROM\ 
'idx_byte_metadata_geometry'\ WHERE\ xmax\ \>\ 0\ AND\ xmin\ \<\ 0\ AND\ ymax\ 
\>\ 0\ AND\ ymin\ \<\ 0
  ==21265== 
  Error: database disk image is malformed
  }}}

  This bug has been originally uncovered by OSS-Fuzz when running on the
  GDAL library that uses libsqlite3: https://bugs.chromium.org/p/oss-
  fuzz/issues/detail?id=2405 (content not viewable during the grace
  period)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: sqlite3 3.11.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed Jun 28 11:18:29 2017
  InstallationDate: Installed on 2016-11-04 (235 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: sqlite3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1700937/+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 1701512] Re: Ambiance and Radiance Gtk theme do not properly support GtkTreeView separators

2017-07-07 Thread Carlo Lobrano

I can reproduce this issue

(btw, what's the difference between the two item in "Affects" list?)

** Changed in: ubuntu-themes
   Status: New => Confirmed

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

Title:
  Ambiance and Radiance Gtk theme do not properly support GtkTreeView
  separators

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  When using a GtkTreeView with separators (via set_row_separator_func),
  the Ambiance (and Radiance) themes do not render the treeview
  correctly, and it glitches the rows as you move your mouse over it.
  This issue is not present with the default Gtk+ theme, Adwaita.

  A simple python script to show a treeview that exhibits the bug is
  attached.

  Behavior is exhibited on Ubuntu 17.04
  (https://github.com/exaile/exaile/issues/362#issuecomment-308685640)

  Originally reported to the Exaile project at
  https://github.com/exaile/exaile/issues/362.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1701512/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs

2017-07-07 Thread Andres Rodriguez

@Tyler,

The reason why this wasn't seen before is that previously in Xenial,
cloud-init did not restart 'ntp' with a new config file. Since cloud-
init recently SRU'd a fixed cloud-init that does restart 'ntp' on
overlay, the issue started to show up.

In other words, after a cloud-init bugfix , these issues started
surfacing.

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

Title:
  NTP reload failure (unable to read library) on overlayfs

Status in cloud-init:
  Incomplete
Status in apparmor package in Ubuntu:
  Confirmed
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
  0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1664352] Re: dhclient-script doesn't use configured metric for rfc3442 classless routes

2017-07-07 Thread Matt Heller

Is there something I can do to help make some progress fixing this bug?
This issue is not applicable to the upstream software source however I
did notice that it is relevant to Debian's isc-dhcp-client package which
I believe is in a sense "upstream" for the Ubuntu package. In light of
that should I pursue fixing the Debian package first?
(https://wiki.ubuntu.com/Debian/Bugs)

--Matt

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

Title:
  dhclient-script doesn't use configured metric for rfc3442 classless
  routes

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  apt-cache policy isc-dhcp-client
  isc-dhcp-client:
Installed: 4.3.3-5ubuntu12.6
Candidate: 4.3.3-5ubuntu12.6
Version table:
   *** 4.3.3-5ubuntu12.6 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.3.3-5ubuntu12 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  If the metric option is set in interfaces(5), dhclient is executed
  with the variable IF_METRIC set to the configured administrative
  metric. The exit-hook rfc3442-classless-routes doesn't use the
  variable; thus, a multi-interface box will experience a race condition
  if multiple interfaces are supplied with one or more duplicate rfc3442
  routes. The attached patch adds support for IF_METRIC handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1664352/+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 1452216] Re: libgcrypt11 not present in Vivid (15.04), Xenial (16.04) - Spotify, Brackets and other app issue.

2017-07-07 Thread Norbert

Got this issue while installing Brackets 1.10 editor from official deb 
(https://github.com/adobe/brackets/releases/tag/release-1.10).
sudo dpkg -i Brackets.Release.1.10.64-bit.deb 
[sudo] password for norbert: 
(Reading database ... 728352 files and directories currently installed.)
Preparing to unpack Brackets.Release.1.10.64-bit.deb ...
Unpacking brackets (1.10.0-17483) over (1.9.0libgcrypt11-17312+1~webupd8~0) ...
dpkg: dependency problems prevent configuration of brackets:
 brackets depends on libgcrypt11 (>= 1.4.5); however:
  Package libgcrypt11 is not installed.

dpkg: error processing package brackets (--install):
 dependency problems - leaving unconfigured
Processing triggers for menu (2.1.47ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Errors were encountered while processing:
 brackets


Temporary solution is to use previous version 
1.9.0libgcrypt11-17312+1~webupd8~0 from PPA (ppa:webupd8team/brackets).
Or install required library from trusty 
(http://archive.ubuntu.com/ubuntu/pool/main/libg/libgcrypt11/libgcrypt11_1.5.3-2ubuntu4.5_amd64.deb)
 manually.

** Summary changed:

- libgcrypt11 not present in Vivid (15.04) - Spotify and other app issue.
+ libgcrypt11 not present in Vivid (15.04), Xenial (16.04) - Spotify, Brackets 
and other app issue.

** Tags added: xenial

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

Title:
  libgcrypt11 not present in Vivid (15.04), Xenial (16.04) - Spotify,
  Brackets and other app issue.

Status in libgcrypt11 package in Ubuntu:
  Confirmed

Bug description:
  The package libgcrypt11 is not present anymore in official ubuntu
  vivid repositories.

  This cause app crash, such as spotify:
  spotify: error while loading shared libraries: libgcrypt.so.11: cannot open 
shared object file: No such file or directory

  Current workaround is to manually download the .deb package from
  launchpad/debian package such as
  https://packages.debian.org/wheezy/libgcrypt11 and manually install
  with dpkg.

  Linux SAGITTER 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.04
  Release:  15.04
  Codename: vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1452216/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs

To elaborate a bit more, the apparmor and overlayfs incompatibility has
been a known kernel issue from before 16.04's release and, at this time,
isn't something that is likely to be fixed in 16.04. I'd like to better
understand if something changed in userspace that started tickling the
incompatibility issue. Did MAAS change how it was using AppArmor in the
recent SRU that took it to version 2.1.5?

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

Title:
  NTP reload failure (unable to read library) on overlayfs

Status in cloud-init:
  Incomplete
Status in apparmor package in Ubuntu:
  Confirmed
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
  0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs

@Andres One thing that I'm struggling with is why this bug hasn't been
seen before. IIUC, it should be present in the very first ga-16.04
kernel that Ubuntu 16.04 LTS was released with (in addition to earlier
kernels while Xenial was a development release). Has MAAS 2.1.x and
ga-16.04 kernels just now been used together or could there be some
other change (in the kernel, MAAS, or maybe even something else) since
the time that Ubuntu 16.04 LTS was released that we're not considering?

Would it be possible for someone on your team to test with the ga-16.04
kernel version 4.4.0-21.37 from the xenial-release pocket with both maas
2.0.0~beta3+bzr4941-0ubuntu1 from xenial-release and maas
2.1.5+bzr5596-0ubuntu1~16.04.1 from xenial-updates? I don't know how
much effort that is but it would be helpful in understanding what
changed in 16.04 to start triggering this bug.

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

Title:
  NTP reload failure (unable to read library) on overlayfs

Status in cloud-init:
  Incomplete
Status in apparmor package in Ubuntu:
  Confirmed
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
  0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs

John is going to build a test kernel, based on the ga-16.04 kernel, with
the binfmt_elf commit cherry-picked from the hwe-16.04. That will let
someone from the MAAS team attempt to reproduce the issue with the test
kernel and, if the deployment succeeds, it'll tell us that the
binfmt_elf commit is causing the change in behavior.

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

Title:
  NTP reload failure (unable to read library) on overlayfs

Status in cloud-init:
  Incomplete
Status in apparmor package in Ubuntu:
  Confirmed
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
  0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1408106] Re: attach_disconnected not sufficient for overlayfs

@fnordahl Hi! Let's keep the discussion about bug 1701297 in that bug
since it is focused on the change in behavior between the Xenial release
kernel and the HWE kernel. That's not what this bug is about. John is
investigating the change in behavior issue. Jamie's previous
investigations of overlayfs/apparmor were solely focused on the Xenial
release kernel so we should not pull him in at the moment as it would
divert his focus from other high priority workk.

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

Title:
  attach_disconnected not sufficient for overlayfs

Status in AppArmor:
  Invalid
Status in MAAS:
  Invalid
Status in apparmor package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  With the following use of overlayfs, we get a disconnected path:

  $ cat ./profile
  #include 
  profile foo {
    #include 

    capability sys_admin,
    capability sys_chroot,
    mount,
    pivot_root,
  }

  $ cat ./overlay.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char* argv[]) {
  int i = 0;
  int len = 0;
  int ret = 0;
  char* options;

  if (geteuid())
  unshare(CLONE_NEWUSER);
  unshare(CLONE_NEWNS);

  for (i = 1; i < argc; i++) {
  if (i == 1) {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
  }
  else {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt", 
argv[i]);
  }

  mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
  }

  chdir("/mnt");
  pivot_root(".", ".");
  chroot(".");

  chdir("/");
  execl("/bin/bash", "/bin/bash", NULL);
  }

  $ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
  [255]
  ...
  Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400 
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name 
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255 
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  With the above, the expectation was for the denial to be /mnt/bin/bash. There 
are three ways forward:
  1. the correct solution is to patch overlayfs to properly track the loopback, 
but this will take a while, may ultimately be unachievable. UPDATE: upstream is 
currently working on this and Ubuntu will engage with them
  2. we could rely on the fact that overlayfs creates a private unshared 
submount, and provide a way to not mediate the path when that is present, and 
tagged. This would take a bit of time, and might be the preferred method over 1 
longer term
  3. we could extend attach_disconnected so that we can define the attach root. 
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash' 
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1408106/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2017-07-07 Thread Steve Langasek

** Changed in: debconf (Ubuntu)
 Assignee: MAYANK SHUKLA (mayankgonda) => (unassigned)

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Confirmed
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Triaged
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1702898] [NEW] package linux-image-extra-4.10.0-26-generic 4.10.0-26.30 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2017-07-07 Thread Rodrigo Gonçalves

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-extra-4.10.0-26-generic 4.10.0-26.30
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1452 F pulseaudio
  morgan 4306 F pulseaudio
Date: Sun Jul  2 13:10:33 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=317b6f78-3fd8-4c3c-ac48-0a26d1a42deb
InstallationDate: Installed on 2016-04-24 (438 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 5986:053a Acer, Inc 
 Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LNV L40-30
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed 
root=UUID=14ac0fee-0d5e-48e8-910c-52b05a0a307d ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.10.0-26-generic 4.10.0-26.30 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to zesty on 2017-06-16 (20 days ago)
dmi.bios.date: 02/28/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.02
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.vendor: LNV
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: LNV
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd02/28/2015:svnLNV:pnL40-30:pvr1.02:rvnLNV:rn:rvrTobefilledbyO.E.M.:cvnLNV:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: L40-30
dmi.product.version: 1.02
dmi.sys.vendor: LNV

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


** Tags: amd64 apport-package zesty

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

Title:
  package linux-image-extra-4.10.0-26-generic 4.10.0-26.30 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-extra-4.10.0-26-generic 4.10.0-26.30
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1452 F pulseaudio
morgan 4306 F pulseaudio
  Date: Sun Jul  2 13:10:33 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=317b6f78-3fd8-4c3c-ac48-0a26d1a42deb
  InstallationDate: Installed on 2016-04-24 (438 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:053a Acer, Inc 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LNV L40-30
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed 
root=UUID=14ac0fee-0d5e-48e8-910c-52b05a0a307d ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.10.0-26-generic 4.10.0-26.30 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to zesty on 2017-06-16 (20 days ago)
  dmi.bios.date: 02/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.vendor: LNV
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: LNV
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:

[Touch-packages] [Bug 841366] Re: jockey-backend crashed with TypeError in pulse_items(): an integer is required

2017-07-07 Thread William Grant

** Attachment removed: "10C6E5F28347FE113E8C69B50DBFD30A.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/841366/+attachment/4901859/+files/10C6E5F28347FE113E8C69B50DBFD30A.jpg

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

Title:
  jockey-backend crashed with TypeError in pulse_items(): an integer is
  required

Status in python-apt package in Ubuntu:
  Fix Released

Bug description:
  I get this error when I open software to install proprietary drivers
  for my nvidia video adapter.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: jockey-common 0.9.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  Architecture: amd64
  BootDmesg: (Nothing has been logged yet.)
  Date: Sun Sep  4 23:19:51 2011
  ExecutablePath: /usr/share/jockey/jockey-backend
  InterpreterPath: /usr/bin/python2.7
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/share/jockey/jockey-backend --debug -l 
/var/log/jockey.log
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic 
root=UUID=81c8ea82-fbcf-49f1-b7a5-fc8c37d6c4ee ro quiet splash vt.handoff=7
  PythonArgs: ['/usr/share/jockey/jockey-backend', '--debug', '-l', 
'/var/log/jockey.log']
  SourcePackage: jockey
  Title: jockey-backend crashed with TypeError in pulse_items(): an integer is 
required
  Traceback:
   Traceback (most recent call last):
 File "/usr/lib/python2.7/dist-packages/apt/progress/old.py", line 121, in 
pulse_items
   if self.currentCPS > 0:
   TypeError: an integer is required
  UpgradeStatus: Upgraded to oneiric on 2011-09-04 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 06/22/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0506
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Crosshair V Formula
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  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.:bvr0506:bd06/22/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnCrosshairVFormula:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/841366/+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 1689825] Re: gnome-keyring not unlocked on boot

2017-07-07 Thread 513G3

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

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  New
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1646739] Re: "Use of uninitialized value" in debconf via update-manager

2017-07-07 Thread MAYANK SHUKLA

** Description changed:

  During a software upgrade, process was stuck on php7.0-xml configuration
  for 20 minutes, after that I killed the process. I am not sure what
  additional info are required, will be happy to provide any.
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: php7.0-xml 7.0.13-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  Date: Fri Dec  2 09:52:06 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2016-03-11 (265 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  RelatedPackageVersions:
-  dpkg 1.18.4ubuntu1.1
-  apt  1.2.15
+  dpkg 1.18.4ubuntu1.1
+  apt  1.2.15
  SourcePackage: php7.0
  Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (209 days ago)

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

Title:
  "Use of uninitialized value" in debconf via update-manager

Status in debconf package in Ubuntu:
  Confirmed
Status in php7.0 package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  During a software upgrade, process was stuck on php7.0-xml
  configuration for 20 minutes, after that I killed the process. I am
  not sure what additional info are required, will be happy to provide
  any.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: php7.0-xml 7.0.13-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  Date: Fri Dec  2 09:52:06 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2016-03-11 (265 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: php7.0
  Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (209 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1646739/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2017-07-07 Thread MAYANK SHUKLA

** Changed in: debconf (Ubuntu)
 Assignee: (unassigned) => MAYANK SHUKLA (mayankgonda)

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Confirmed
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Triaged
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1408106] Re: attach_disconnected not sufficient for overlayfs

2017-07-07 Thread Frode Nordahl

@andreserl

There are severe security implications of doing 2) from now until all
future, and unfortunately I have seen that this is being done in the
wild.

I would be much more comfortable by actually finding the root cause of
the issue at hand and fixing that.

This is what I am currently pursuing, so please share any information
about the actual upstream kernel problem you may have.

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

Title:
  attach_disconnected not sufficient for overlayfs

Status in AppArmor:
  Invalid
Status in MAAS:
  Invalid
Status in apparmor package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  With the following use of overlayfs, we get a disconnected path:

  $ cat ./profile
  #include 
  profile foo {
    #include 

    capability sys_admin,
    capability sys_chroot,
    mount,
    pivot_root,
  }

  $ cat ./overlay.c
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char* argv[]) {
  int i = 0;
  int len = 0;
  int ret = 0;
  char* options;

  if (geteuid())
  unshare(CLONE_NEWUSER);
  unshare(CLONE_NEWNS);

  for (i = 1; i < argc; i++) {
  if (i == 1) {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/", argv[i]);
  }
  else {
  len = strlen(argv[i]) + strlen("upperdir=,lowerdir=/mnt") + 2;
  options = alloca(len);
  ret = snprintf(options, len, "upperdir=%s,lowerdir=/mnt", 
argv[i]);
  }

  mount("overlayfs", "/mnt", "overlayfs", MS_MGC_VAL, options);
  }

  chdir("/mnt");
  pivot_root(".", ".");
  chroot(".");

  chdir("/");
  execl("/bin/bash", "/bin/bash", NULL);
  }

  $ sudo apparmor_parser -r ./profile && aa-exec -p foo -- ./a.out /tmp
  [255]
  ...
  Dec 12 14:31:38 localhost kernel: [57278.040216] audit: type=1400 
audit(1418387498.613:712): apparmor="DENIED" operation="exec" info="Failed name 
lookup - disconnected path" error=-13 profile="foo" name="/bin/bash" pid=18255 
comm="a.out" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  With the above, the expectation was for the denial to be /mnt/bin/bash. There 
are three ways forward:
  1. the correct solution is to patch overlayfs to properly track the loopback, 
but this will take a while, may ultimately be unachievable. UPDATE: upstream is 
currently working on this and Ubuntu will engage with them
  2. we could rely on the fact that overlayfs creates a private unshared 
submount, and provide a way to not mediate the path when that is present, and 
tagged. This would take a bit of time, and might be the preferred method over 1 
longer term
  3. we could extend attach_disconnected so that we can define the attach root. 
Eg, we can use profile foo (attach_disconnected=/mnt) {} such that '/bin/bash' 
maps to '/mnt/bin/bash'. UPDATE: THIS IS NOT VIABLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1408106/+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 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)

2017-07-07 Thread Sebastien Bacher

the new issue is bug #1700485

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

Title:
  GNOME Online Accounts breaks if you log out (until you reboot)

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Yakkety:
  Triaged
Status in gnome-session source package in Yakkety:
  In Progress
Status in gnome-online-accounts source package in Zesty:
  Triaged
Status in gnome-session source package in Zesty:
  Won't Fix

Bug description:
  Impact
  ==
  After logging out, GNOME Online Accounts doesn't work the next time you log 
in.

  This bug was a Release Blocker for Fedora 26. (Fedora 26 will be
  released in July).

  gnome-session is the only package updated in this update (not gnome-
  online-accounts).

  Test Case
  =
  From Ubuntu GNOME, click Settings>Online Accounts and add your Google 
account. Install Evolution if it's not installed. Verified that your Google 
account has synced.

  Log out. Log in. It may help to reproduce the bug log in to a
  different session (GNOME on Wayland instead of GNOME, or the other way
  around).

  Open Evolution. Verify that no errors are reported and that your
  Google account is still syncing.

  After installing the gnome-session update, I recommend rebooting once
  to clear any old lingering GNOME Online Accounts processes from
  previous sessions.

  Regression Potential
  
  This fix is the same as was accepted into Fedora 26. It is a workaround by 
killing all the user's D-Bus sessions when the user logs out. This fix has been 
backported from gnome-session 3.25.3. It has not been applied to the 3.24 git 
branch upstream.

  Since 16.10 has almost reached its end of life (July), I am not
  proposing this fix there. I believe 16.10 is the first release
  affected since Ubuntu moved many more services to systemd user
  sessions in that release.

  The patch tries to only kill the D-Bus sessions if the session being
  logged out is the final remaining session for the user.

  The workaround makes sense to me. It seems similar to the
  KillUserProcesses option that was pushed into systemd to fix this kind
  of problem but it's more limited than the systemd method so hopefully
  it won't be as controversial.

  Original Bug Report
  ===
  Can't add any online accounts in after opened Online accounts + mark is 
faded, can't click.
  After reinstalled gnome-online-accounts still has same problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.20.3-1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Aug  8 15:33:45 2016
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)

2017-07-07 Thread Sebastien Bacher

Those patches seem to create an issue where it's impossible to log back
into a session after a logout

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

Title:
  GNOME Online Accounts breaks if you log out (until you reboot)

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Yakkety:
  Triaged
Status in gnome-session source package in Yakkety:
  In Progress
Status in gnome-online-accounts source package in Zesty:
  Triaged
Status in gnome-session source package in Zesty:
  Won't Fix

Bug description:
  Impact
  ==
  After logging out, GNOME Online Accounts doesn't work the next time you log 
in.

  This bug was a Release Blocker for Fedora 26. (Fedora 26 will be
  released in July).

  gnome-session is the only package updated in this update (not gnome-
  online-accounts).

  Test Case
  =
  From Ubuntu GNOME, click Settings>Online Accounts and add your Google 
account. Install Evolution if it's not installed. Verified that your Google 
account has synced.

  Log out. Log in. It may help to reproduce the bug log in to a
  different session (GNOME on Wayland instead of GNOME, or the other way
  around).

  Open Evolution. Verify that no errors are reported and that your
  Google account is still syncing.

  After installing the gnome-session update, I recommend rebooting once
  to clear any old lingering GNOME Online Accounts processes from
  previous sessions.

  Regression Potential
  
  This fix is the same as was accepted into Fedora 26. It is a workaround by 
killing all the user's D-Bus sessions when the user logs out. This fix has been 
backported from gnome-session 3.25.3. It has not been applied to the 3.24 git 
branch upstream.

  Since 16.10 has almost reached its end of life (July), I am not
  proposing this fix there. I believe 16.10 is the first release
  affected since Ubuntu moved many more services to systemd user
  sessions in that release.

  The patch tries to only kill the D-Bus sessions if the session being
  logged out is the final remaining session for the user.

  The workaround makes sense to me. It seems similar to the
  KillUserProcesses option that was pushed into systemd to fix this kind
  of problem but it's more limited than the systemd method so hopefully
  it won't be as controversial.

  Original Bug Report
  ===
  Can't add any online accounts in after opened Online accounts + mark is 
faded, can't click.
  After reinstalled gnome-online-accounts still has same problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.20.3-1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Aug  8 15:33:45 2016
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1700485] Re: Second login always fails. I have to reboot between logins

2017-07-07 Thread Sebastien Bacher

The issue seems created by the gnome-session changes from
3.24.1-0ubuntu5

" * Backport patches from 3.25.3 to kill D-Bus clients on log out.
This works around GNOME Online Accounts not working correctly
after logging out (LP: #1610944)"

It fails every time to login it again here but downgrading gnome-session
to the previous version fixes the issue.

Note that the problem is not specific to lightdm, the behaviour is the
same using "startx -- :1" to start the session

** Package changed: lightdm (Ubuntu) => gnome-session (Ubuntu)

** Changed in: gnome-session (Ubuntu)
   Status: New => Confirmed

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

Title:
  Second login always fails. I have to reboot between logins

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  I used to be able to log in/out/in again between Gnome on Wayland and
  Xorg etc. Now it doesn't work. Any attempt to log out and in again
  fails, unless I reboot between logins.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lightdm 1.22.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  Date: Mon Jun 26 17:22:59 2017
  InstallationDate: Installed on 2017-05-03 (54 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1700485/+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 1689825] Re: gnome-keyring not unlocked on boot

2017-07-07 Thread Sébastien Tisserant

For what it's worth, as other users already mentioned that, the issue
appeared after I installed flatpack and pitivi (yesterday). I
uninstalled both of them and cleaned remaining files but the problem
still occurs...

Flatpak might be related to the issue, or at least one of the triggers.

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1702869] [NEW] package zlib1g:amd64 1:1.2.8.dfsg-2ubuntu5.1 failed to install/upgrade: package zlib1g:amd64 is already installed and configured

2017-07-07 Thread Yaron Lapidot

Public bug reported:

Ubuntu won't fully upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: zlib1g:amd64 1:1.2.8.dfsg-2ubuntu5.1
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Fri Jul  7 11:48:11 2017
Dependencies:
 gcc-6-base 6.2.0-5ubuntu12
 libc6 2.24-3ubuntu2.2
 libgcc1 1:6.2.0-5ubuntu12
ErrorMessage: package zlib1g:amd64 is already installed and configured
InstallationDate: Installed on 2015-12-22 (563 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1.1
 apt  1.2.20
SourcePackage: zlib
Title: package zlib1g:amd64 1:1.2.8.dfsg-2ubuntu5.1 failed to install/upgrade: 
package zlib1g:amd64 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package need-duplicate-check yakkety

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

Title:
  package zlib1g:amd64 1:1.2.8.dfsg-2ubuntu5.1 failed to
  install/upgrade: package zlib1g:amd64 is already installed and
  configured

Status in zlib package in Ubuntu:
  New

Bug description:
  Ubuntu won't fully upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: zlib1g:amd64 1:1.2.8.dfsg-2ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Jul  7 11:48:11 2017
  Dependencies:
   gcc-6-base 6.2.0-5ubuntu12
   libc6 2.24-3ubuntu2.2
   libgcc1 1:6.2.0-5ubuntu12
  ErrorMessage: package zlib1g:amd64 is already installed and configured
  InstallationDate: Installed on 2015-12-22 (563 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.2.20
  SourcePackage: zlib
  Title: package zlib1g:amd64 1:1.2.8.dfsg-2ubuntu5.1 failed to 
install/upgrade: package zlib1g:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1702869/+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 1593907] Re: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot; manually starting ntp service works: [FIX in DESCRIPTION], just

Version typo, the new one in Zesty unapproved is of course bumped to
ntp_4.2.8p9+dfsg-2ubuntu1.2

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

Title:
  ntpdate startup routine prevents ntp service from launching up on
  Ubuntu 16.04 server on system boot; manually starting ntp service
  works: [FIX in DESCRIPTION], just need to apply it and release a new
  version

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Trusty:
  In Progress
Status in ntp source package in Xenial:
  In Progress
Status in ntp source package in Yakkety:
  In Progress
Status in ntp source package in Zesty:
  In Progress

Bug description:
  [Impact]

   * Fixes several broken cases, those are:
   * Case 1 - ntp configured to drift time slowly, but time jumping
   - ntp is running and drifts time towards a target being way off
   - an interface comes up
   - stop ntpd
   - warp time via ntpdate-debian (static interfaces will even set -b)
   - (re-)start ntpd
   - if users relied on non-time warp they are now in trouble

   * Case 2 - ntp start/stop storms
   - ntpd comes up normally
   - the admin brings interfaces up/down rather often
   - ntp is restarted very very often due to this for no reason
   => reason for bugs like debian 823533

   * Case 3 - unintentional enablement of ntp
   - ntpd is installed but disabled (for whatever reason)
   - all is fine on any ifup/down
   - one installs ntpdate, maybe even without realizing due to a depends
   - now on the next ifup ntpd (or openntpd) will be started

   * Solution, drop the broken Delta

  [Test Case]

   * Testing Case 2/3 as it is the easiest, case 1 needs a more complex 
 setup to cause the time drift but otherwise works the same way.
 - install ntp and ntpdate
 - stop ntp
 - ifup/ifdown an interface multiple times; as simplification you can 
   also call /etc/network/if-up.d/ntpdate directly (not that this 
   spawns the change asnchronous and locks concurrency, so do that a 
   few times over the time of a minute or so)
 - the service of ntp should still be stopped and not report plenty of 
   restarts

  
  [Regression Potential] 

   * It improves a lot of cases (otherwise we wouldn't SRU), but there is 
 one regression potential I can see:

 - users that relied on starting NTP later on after other interfaces 
   got up due to that code in ntpdate which did that as a side effect. 
   But that is outweigh by Case2/3 for the majority of users. And even 
   Case1 only hits this potential regression on e.g. late network 
   intialization, but in that case please remind that the default 
   (systemd timedatectl) would handle that.

 - Since most users of ntp do not install ntpdate (which doesn't work 
   when ntp is active) we should be rather safe to assume that almost 
   no one should rely on that side effect.

 - Furthermore this is a Ubuntu Delta for very long, cause issues (see 
   the references on the git commit) but never made it into Debian - 
   in that sense another indicator it isn't an important delta to 
   have.

  [Other Info]
   
   * The original intention "what if net is available too late" fixed 
 correctly would not be part of ntpdate, but ntp and additionally 
 check if it is actually meant to be enabled - but I never seen/heard 
 of any of it since systemd is around - maybe new ordering mostly 
 avoids the original issue.


  ---

  
  I've installed ntp service on the clean ubuntu 16.04 server system. 
Configured it. Checked that it works, but, after reboot, it doesn't start 
automatically.
  When I check: 'systemctl is-enabled ntp', it shows enabled.
  If I manually start it 'systemctl start ntp' it starts just fine and woks 
correctly,
  but until I manually start it, 'systemctl status ntp' shows:

  Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
  Active: inactive (deadi)

  Installed 1.29ubuntu2 version of init-systems-helper, but it didn't
  fix the problem.

  Found a bugreport on ntpd package:

  https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596

  led to solution that involves a change to be made in file:

  /etc/network/if-up.d/ntpdate

  of ntpdate package

  After changing from:
  __CODE_START__

  invoke-rc.d --quiet $service stop >/dev/null 2>&1 || true

   # Avoid running more than one at a time
   flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null 
|| :

  invoke-rc.d --quiet $service start >/dev/null 2>&1 || true

  __CODE_END__

  to:
  __CODE_START__

  systemctl --quiet stop $service.service >/dev/null 2>&1 || true

   # Avoid running more than one at a

[Touch-packages] [Bug 1292324] Re: Support non-root X

2017-07-07 Thread Yves-Alexis Perez

Robert,

I know you weren't interested in this but would review patches if
needed. Could you point people to the right directions on where to drop
privileges before running X server and stuff like that?

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

Title:
  Support non-root X

Status in Light Display Manager:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm package in Debian:
  Confirmed
Status in lightdm package in Fedora:
  Unknown

Bug description:
  Support running X as an unprivileged user.

  Currently X servers are run as root means a large complex process has
  access to services it might not need (i.e. potential security and
  stability problems). It would be nice to run each X server as either
  an unprivileged user or in the session they are being used in.

  Logind provides a system for sharing access to the display and input
  devices so this can be done - this seems like the most likely
  implementation of non-root X.

  For more information see Hans de Goede request:
  http://lists.freedesktop.org/archives/lightdm/2014-March/000539.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1292324/+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 875713] Re: cut fails to handle correctly utf-8

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

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

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

Title:
  cut fails to handle correctly utf-8

Status in coreutils package in Ubuntu:
  Confirmed

Bug description:
  1) I'm using Lucid :
  $ lsb_release -rd
  Description:  Ubuntu 10.04.3 LTS
  Release:  10.04

  2) The version of coreutils (that contains the 'cut' utility)
  $ apt-cache policy coreutils
  coreutils:
Installé : 7.4-2ubuntu3
Candidat : 7.4-2ubuntu3
   Table de version :
   *** 7.4-2ubuntu3 0
  500 http://fr.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
  100 /var/lib/dpkg/status
   7.4-2ubuntu2 0
  500 http://fr.archive.ubuntu.com/ubuntu/ lucid/main Packages

  3) What I expect to happen, as the man says:
  $man cut
  (...)
-b, --bytes=LIST
  select only these bytes
-c, --characters=LIST
  select only these characters
  (...)

  I expect a different behavior, when in 'not-1-byte' character sets
  such as UTF-8, UTF-16, etc...

  The same of different behavior we have with wc that says:
  $man wc
  (...)
-c, --bytes
   print the byte counts
-m, --chars
   print the character counts
  (...)

  So when I have on my environment :
  $ env | grep 'LANG'
  LANG=fr_FR.UTF-8
  GDM_LANG=fr_FR.UTF-8

  I can do:
  $ printf '%s' 'déjà vu' | wc -c
  9
  $ printf '%s' 'déjà vu' | wc -m
  7

  That is CORRECT (with wc) because as the ENV variable says I'm using
  UTF-8, the 'é' and 'à' count for 1 character but 2 bytes.

  
  4) What happens instead: I get something wrong with 'cut'
  $ printf '%s' 'déjà vu' | cut -b 1-4 | hd
    64 c3 a9 6a 0a|d..j.|
  $ printf '%s' 'déjà vu' | cut -c 1-4 | hd
    64 c3 a9 6a 0a|d..j.|

  (I piped it to 'hd', so that we have a better view of what's
  happening)

  It can even be worse and give an invalid UTF-8 output
  $ printf '%s' 'déjà vu' | cut -c 1-5 | hd
    64 c3 a9 6a c3 0a |d..j..|

  That is because it 'cuts' in the middle of an UTF-8 sequence, and with the 
appended \n, it gives an incoherent UTF-8 sequence as we can prove:
  $ printf '%s' 'déjà vu' | cut -c 1-5 | iconv -f utf-8 -t iso8859-1
  d�jiconv: séquence d'échappement non permise à la position 4

  
  We can clearly see that -b or -c makes NO difference at all... but it should, 
as 'wc' does, because we are in UTF-8

  
  So either:
  -Option a) the cut program is buggy, mixes the concept of 'byte' of 
'character', and does things wrong when not in '1-byte' charset.
  -Option b) the help/man is wrong, and there is no difference when handling 
bytes and chars (but then why do we have two different options!)

  Note that some other GNU utilities seam to mix the concept of 'byte' and 
'char', but at least the misconception is clear in the man/help, for example 
with 'head'
  $man head
  (...)
   -c, --bytes=[-]N
   print the first N bytes of each file; with the leading `-', print all 
but the last N bytes of each file

  The -b option is unused for 'head', and yet they chosed to use -c,
  short of --bytes... Looks like they meant -c as --chars, but at the
  last moment decided to handle only bytes!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/875713/+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 91175] Re: cut gets confused with UTF-8 characters

2017-07-07 Thread Andrew McCarthy

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

** This bug has been marked a duplicate of bug 875713
   cut fails to handle correctly utf-8

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

Title:
  cut gets confused with UTF-8 characters

Status in coreutils package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: coreutils

  GNU cut gets confused about character boundaries with UTF-8 encoded
  files.

  An example, as they (almost) say, is worth a thousand words:

  nslater@hinata: ~ $ locale
  LANG=en_US.UTF-8
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC="en_US.UTF-8"
  LC_TIME="en_US.UTF-8"
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY="en_US.UTF-8"
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER="en_US.UTF-8"
  LC_NAME="en_US.UTF-8"
  LC_ADDRESS="en_US.UTF-8"
  LC_TELEPHONE="en_US.UTF-8"
  LC_MEASUREMENT="en_US.UTF-8"
  LC_IDENTIFICATION="en_US.UTF-8"
  LC_ALL=
  nslater@hinata: ~ $ cat foo.txt
  She said “I think I found a bug.”
  nslater@hinata: ~ $ cat foo.txt | cut --characters 10-
  “I think I found a bug.”
  nslater@hinata: ~ $ cat foo.txt | cut --characters 11-
  ��I think I found a bug.”
  nslater@hinata: ~ $ cat foo.txt | cut --characters 12-
  �I think I found a bug.”
  nslater@hinata: ~ $ cat foo.txt | cut --characters 13-
  I think I found a bug.”

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/91175/+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 1414316] Re: cut() does not handle unicode properly

2017-07-07 Thread Andrew McCarthy

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

** This bug has been marked a duplicate of bug 875713
   cut fails to handle correctly utf-8

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

Title:
  cut() does not handle unicode properly

Status in coreutils package in Ubuntu:
  New

Bug description:
  Hi,

  $ echo 哈哈
  哈哈

  $ echo 哈哈 | cut -c 2-
  ��哈

  Apparently, Red Hat patched this in or before FC15.
  http://unix.stackexchange.com/questions/15961/coreutils-that-are-utf-aware
  [patches@holocene ~]$ rpm -q coreutils
  coreutils-8.10-2.fc15.x86_64
  [patches@holocene ~]$ echo 哈哈 | cut -c 2-
  哈

  The patch is here:
  http://pkgs.fedoraproject.org/cgit/coreutils.git/tree/coreutils-
  i18n.patch?id=6e10f376996b64f538259091a524df2249b653fb;id2=HEAD

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: coreutils 8.21-1ubuntu5.1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jan 24 10:06:25 2015
  InstallationDate: Installed on 2013-05-22 (611 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to trusty on 2015-01-04 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1414316/+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 1702851] [NEW] My installation unfinished

2017-07-07 Thread agus

Public bug reported:

Every time i install or remove program, it wont finish until it
restarted

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.10.0-041000-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Jul  7 15:42:41 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3903]
InstallationDate: Installed on 2017-07-07 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:57c5 Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 0bda:b728 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80KU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-041000-generic 
root=UUID=57527f57-dbe3-4839-b983-25da145ad492 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: C8CN31WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Polo
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K13453WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 300S-11IBR
dmi.modalias: 
dmi:bvnLENOVO:bvrC8CN31WW:bd08/05/2016:svnLENOVO:pn80KU:pvrLenovoideapad300S-11IBR:rvnLENOVO:rnPolo:rvrSDK0K13453WIN:cvnLENOVO:ct10:cvrLenovoideapad300S-11IBR:
dmi.product.name: 80KU
dmi.product.version: Lenovo ideapad 300S-11IBR
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Jul  7 15:34:17 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

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

Title:
  My installation unfinished

Status in xorg package in Ubuntu:
  New

Bug description:
  Every time i install or remove program, it wont finish until it
  restarted

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.10.0-041000-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Jul  7 15:42:41 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3903]
  InstallationDate: Installed on 2017-07-07 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57c5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0bda:b728 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80KU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-041000-generic 
root=UUID=57527f57-dbe3-4839-b983-25da145ad492 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C8CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Polo
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K13453WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO

[Touch-packages] [Bug 1697646] Re: Long-running ping command leads to 100% CPU usage

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

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

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

Title:
  Long-running ping command leads to 100% CPU usage

Status in iputils package in Ubuntu:
  Confirmed

Bug description:
  Since I've updated my laptop to Ubuntu MATE 17.04, I notice ping
  sometimes gets into a runaway mode.

  I'm on a shaky Wi-Fi so to monitor connectivity I usually have a long
  running ping command against google's DNS server:

  > ping -s16 8.8.4.4

  Often, after leaving it for a while, I notice screaming vents and htop
  then shows the ping process consuming 100% of one CPU. It will stay
  like that until ping is killed.

  I'm not sure how to troubleshoot this issue, can someone recommend a
  protocol?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: iputils-ping 3:20161105-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Tue Jun 13 11:11:26 2017
  InstallationDate: Installed on 2017-04-05 (69 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  SourcePackage: iputils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1697646/+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 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload

2017-07-07 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  Systemd fails to serialize tasks correctly on daemon-reload

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd package in Debian:
  New

Bug description:
  Hi,
  I was initially tracking down a libvirt bug [1], but happened to realize it 
is actually a general systemd issue.
  From there I got to file, discuss and test [2].

  For now I file the bug to be ablte to do my tests correctly, but if it
  really fixes the issue I'd like to suggest to fix it in the release -
  so better file upfront and do even my test patches right.

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379
  [2]: https://github.com/systemd/systemd/issues/6299.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1702823/+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 1702606] Re: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: пакет iproute2 не готов к настройке настройка невозможна (текущее состояние: «half-installed»)

Thank you for your report.

This looks like a local configuration problem, rather than a bug in
Ubuntu.

You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration problems, I'm marking this bug as Invalid. This helps us
to focus on fixing bugs in Ubuntu.

If you believe that this is really a bug, then 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,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

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

Title:
  package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: пакет
  iproute2 не готов к настройке  настройка невозможна (текущее
  состояние: «half-installed»)

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: iproute2 4.3.0-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Jul  5 08:04:21 2017
  ErrorMessage: пакет iproute2 не готов к настройке  настройка невозможна 
(текущее состояние: «half-installed»)
  InstallationDate: Installed on 2017-07-03 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: iproute2
  Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: пакет 
iproute2 не готов к настройке  настройка невозможна (текущее состояние: 
«half-installed»)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1702606/+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 1702606] Re: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: пакет iproute2 не готов к настройке настройка невозможна (текущее состояние: «half-installed»)

Hi Nikc,

>From the log:
1981 Preparing to unpack .../iproute2_4.3.0-1ubuntu3.16.04.1_amd64.deb ...^M
  
1982 Unpacking iproute2 (4.3.0-1ubuntu3.16.04.1) over (4.3.0-1ubuntu3) ...^M
  
1983 Log ended: 2017-07-03  15:59:20
  
1984
  
1985 Log started: 2017-07-03  16:02:38 
[...]
2026 dpkg: error processing package iproute2 (--configure):^M   
  
2027  package iproute2 is not ready for configuration^M 
  
2028  cannot configure (current status 'half-installed')^M

That seems like an aborted upgrade to me.
There are similar issues reported online that can help you further if needed 
like [1]

In general I think you would just have to re-install that package to get this 
resolved.
$ apt-get install iproute2 --reinstall

[1]: https://askubuntu.com/questions/490671/fix-half-installed-package

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

Title:
  package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: пакет
  iproute2 не готов к настройке  настройка невозможна (текущее
  состояние: «half-installed»)

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: iproute2 4.3.0-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Jul  5 08:04:21 2017
  ErrorMessage: пакет iproute2 не готов к настройке  настройка невозможна 
(текущее состояние: «half-installed»)
  InstallationDate: Installed on 2017-07-03 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: iproute2
  Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: пакет 
iproute2 не готов к настройке  настройка невозможна (текущее состояние: 
«half-installed»)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1702606/+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 1692474] Re: Sound settings don't remember my preferred audio output device

2017-07-07 Thread Daniel van Vugt

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

** This bug has been marked a duplicate of bug 1702794
   Please add module-switch-on-connect to default.pa

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

Title:
  Sound settings don't remember my preferred audio output device

Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  New

Bug description:
  Sound settings don't remember my preferred audio output device.

  Every time I (manage to) connect a bluetooth audio device, the default
  output remains the built-in PC speaker. Same when I connect USB audio
  devices... Ubuntu sticks to the built-in speakers until manually set
  otherwise.

  This is a bug rather than opinion because there are at least three ways that 
Ubuntu could be better prioritizing audio devices:
1. Prefer what the user manually selected last; or
2. Prefer what the user dragged to the top of the list (a missing feature, 
but nice idea); or
3. Prefer what audio device appeared in the list most recently.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May 22 17:23:59 2017
  InstallationDate: Installed on 2017-05-19 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1692474/+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 1702794] Re: Please add module-switch-on-connect to default.pa

2017-07-07 Thread Daniel van Vugt

It seems I was requesting the same kind of fix a while back but didn't
know what the answer was: bug 1692474. Thanks!

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

Title:
  Please add module-switch-on-connect to default.pa

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  This way once a user pairs & connects a bluetooth speaker device pulseaudio 
will auto switch to it. 
  As it stands now users have to open sound settings & switch manually. It's 
bad enough that auto discover & connect don't work, (can be scripted thru 
bluetoothctl), no sense adding to frustration

  In the ### Automatically load driver modules for Bluetooth hardware
  section

  
  .ifexists module-switch-on-connect.so
  load-module module-switch-on-connect
  .endif

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doug   1843 F pulseaudio
   /dev/snd/controlC0:  doug   1843 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  6 20:02:15 2017
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-07-04T13:42:27.651527

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1702794/+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 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload

Ah in case one wants to check the issue I filed with upstream as well as
the fix there have good steps documented. No need to just copy them
until we need them for an SRU template.

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

Title:
  Systemd fails to serialize tasks correctly on daemon-reload

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd package in Debian:
  New

Bug description:
  Hi,
  I was initially tracking down a libvirt bug [1], but happened to realize it 
is actually a general systemd issue.
  From there I got to file, discuss and test [2].

  For now I file the bug to be ablte to do my tests correctly, but if it
  really fixes the issue I'd like to suggest to fix it in the release -
  so better file upfront and do even my test patches right.

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379
  [2]: https://github.com/systemd/systemd/issues/6299.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1702823/+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 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload

FYI - To help Debian as well and avoid long term Delta I supplied a
backport for debians systemd git under the debbug I linked above.

But since our delta seems rather long I'm not sure if a re-merge is
planned soon, so please consider adding the patch on Ubuntu as well
(maybe wait until after the Debian discussion acked it).

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

Title:
  Systemd fails to serialize tasks correctly on daemon-reload

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd package in Debian:
  New

Bug description:
  Hi,
  I was initially tracking down a libvirt bug [1], but happened to realize it 
is actually a general systemd issue.
  From there I got to file, discuss and test [2].

  For now I file the bug to be ablte to do my tests correctly, but if it
  really fixes the issue I'd like to suggest to fix it in the release -
  so better file upfront and do even my test patches right.

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379
  [2]: https://github.com/systemd/systemd/issues/6299.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1702823/+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 1702840] [NEW] package gir1.2-accounts-1.0 1.23+17.04.20161104-0ubuntu1 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1

2017-07-07 Thread Arsenij

Public bug reported:

gnome-terminal have been crashed then I am type new shortcut in
parameters of gnome-terminal. I have been entering shortcut based on
Shift-Alt-...

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gir1.2-accounts-1.0 1.23+17.04.20161104-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: amd64
Date: Wed Jul  5 23:34:05 2017
ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
InstallationDate: Installed on 2016-06-27 (375 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: libaccounts-glib
Title: package gir1.2-accounts-1.0 1.23+17.04.20161104-0ubuntu1 failed to 
install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libaccounts-glib (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package gir1.2-accounts-1.0 1.23+17.04.20161104-0ubuntu1 failed to
  install/upgrade: подпроцесс новый сценарий pre-removal возвратил код
  ошибки 1

Status in libaccounts-glib package in Ubuntu:
  New

Bug description:
  gnome-terminal have been crashed then I am type new shortcut in
  parameters of gnome-terminal. I have been entering shortcut based on
  Shift-Alt-...

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gir1.2-accounts-1.0 1.23+17.04.20161104-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  Date: Wed Jul  5 23:34:05 2017
  ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  InstallationDate: Installed on 2016-06-27 (375 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: libaccounts-glib
  Title: package gir1.2-accounts-1.0 1.23+17.04.20161104-0ubuntu1 failed to 
install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libaccounts-glib/+bug/1702840/+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 1695067] Re: package python3-problem-report 2.20.4-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

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

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

Title:
  package python3-problem-report 2.20.4-0ubuntu4.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I have fixed this install issue once already :(

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-problem-report 2.20.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic i686
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  CrashReports:
   644:0:119:0:2017-05-27 22:41:47.248780694 +0100:2017-05-27 
22:41:47.248780694 +0100:/var/crash/_usr_bin_py3compile.0.upload
   600:0:119:63972:2017-06-01 19:01:26.924177169 +0100:2017-06-01 
19:01:27.924177169 +0100:/var/crash/python3-problem-report.0.crash
   640:1000:119:1025742:2017-05-31 23:28:37.258940662 +0100:2017-06-01 
18:54:08.430309493 +0100:/var/crash/_usr_bin_xfce4-power-manager.1000.crash
   600:110:119:0:2017-05-27 22:41:54.488541095 +0100:2017-05-23 
20:31:36.192501415 +0100:/var/crash/_usr_bin_py3compile.0.uploaded
   640:0:119:11856:2017-06-01 19:01:27.780084923 +0100:2017-06-01 
19:01:27.780084923 +0100:/var/crash/_usr_bin_py3compile.0.crash
  Date: Thu Jun  1 19:01:27 2017
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-03 (209 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package python3-problem-report 2.20.4-0ubuntu4.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (46 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1695067/+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 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload

I was able to prove that this fixes my issue around libvirt-lxc loosing 
containers on restart.
It could have an almost random number of other effects that are broken by it 
and we don't know so I'd highly appreciate considering that fix - even for 
SRU's actually.

But OTOH I need more of a systemd Expert to look at it and consider
potential side-effects.

A test version can be found in [1] and its ppa [2].

I'll also re-file my Debian bug towards systemd to let them consider it as well.
But for Ubuntu atm - please review and consider the debdiff I attach hereby.

[1]: https://bileto.ubuntu.com/#/ticket/2857
[2]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2857/

** Patch added: "systemd-bug-1702823-fix-deserialization.debdiff"
   
https://bugs.launchpad.net/systemd/+bug/1702823/+attachment/4910732/+files/systemd-bug-1702823-fix-deserialization.debdiff

** Package changed: libvirt (Debian) => systemd (Debian)

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

Title:
  Systemd fails to serialize tasks correctly on daemon-reload

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd package in Debian:
  New

Bug description:
  Hi,
  I was initially tracking down a libvirt bug [1], but happened to realize it 
is actually a general systemd issue.
  From there I got to file, discuss and test [2].

  For now I file the bug to be ablte to do my tests correctly, but if it
  really fixes the issue I'd like to suggest to fix it in the release -
  so better file upfront and do even my test patches right.

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379
  [2]: https://github.com/systemd/systemd/issues/6299.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1702823/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs

2017-07-07 Thread John Johansen

>From an apparmor pov those 2 kernels are almost identical, with the 4.4
kernel picking up a couple of backport patches, that just do some simple
remapping and should not affect behavior.

There are however some external changes that could affect apparmor mediation
  binfmt_elf change (9f834ec18defc369d73ccf9e87a2790bfa05bf46) - that could 
very well be related to the  name="overlay/etc/ld.so.cache" failure

  there are several changes in overlayfs that may result in permission
changes.

We can build som test kernels, a 4.4 kernel with the binfmt_elf commit
cherry-picked and another one with the newer overlayfs.

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

Title:
  NTP reload failure (unable to read library) on overlayfs

Status in cloud-init:
  Incomplete
Status in apparmor package in Ubuntu:
  Confirmed
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
  0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload

** Changed in: systemd (Ubuntu)
 Assignee: ChristianEhrhardt (paelzer) => (unassigned)

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

Title:
  Systemd fails to serialize tasks correctly on daemon-reload

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New
Status in libvirt package in Debian:
  New

Bug description:
  Hi,
  I was initially tracking down a libvirt bug [1], but happened to realize it 
is actually a general systemd issue.
  From there I got to file, discuss and test [2].

  For now I file the bug to be ablte to do my tests correctly, but if it
  really fixes the issue I'd like to suggest to fix it in the release -
  so better file upfront and do even my test patches right.

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379
  [2]: https://github.com/systemd/systemd/issues/6299.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1702823/+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 1702726] Re: dnsmasq fails when the ARP cache is full