[Touch-packages] [Bug 1872235] [NEW] package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 127

2020-04-11 Thread BloodyIron
Public bug reported:

When doing a distro-upgrade from Ubuntu 16.04 to 18.04 shared-mime-info
broke the whole process throwing errors about libicu60, which was
installed as new in the upgrade process. While the system was broken, I
forced a reinstall of libicu60 (apt install --reinstall libicu60) which
then allowed shared-mime-info to be installable.

As this interrupted the distro upgrade process, I have rolled back to a
backup before the upgrade took place, so this system is not in the same
state as when the issue happened. I am not able to provide further debug
assistance here.

I've performed many upgrades from 16.04 to 18.04 and have only seen this
issue happen once so far.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shared-mime-info 1.9-2
ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214
Uname: Linux 4.4.0-177-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
Date: Sat Apr 11 13:33:07 2020
ErrorMessage: installed shared-mime-info package post-installation script 
subprocess returned error exit status 127
InstallationDate: Installed on 2016-03-14 (1489 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.12
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed 
shared-mime-info package post-installation script subprocess returned error 
exit status 127
UpgradeStatus: Upgraded to bionic on 2020-04-11 (0 days ago)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package shared-mime-info 1.9-2 failed to install/upgrade: installed
  shared-mime-info package post-installation script subprocess returned
  error exit status 127

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  When doing a distro-upgrade from Ubuntu 16.04 to 18.04 shared-mime-
  info broke the whole process throwing errors about libicu60, which was
  installed as new in the upgrade process. While the system was broken,
  I forced a reinstall of libicu60 (apt install --reinstall libicu60)
  which then allowed shared-mime-info to be installable.

  As this interrupted the distro upgrade process, I have rolled back to
  a backup before the upgrade took place, so this system is not in the
  same state as when the issue happened. I am not able to provide
  further debug assistance here.

  I've performed many upgrades from 16.04 to 18.04 and have only seen
  this issue happen once so far.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: shared-mime-info 1.9-2
  ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214
  Uname: Linux 4.4.0-177-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sat Apr 11 13:33:07 2020
  ErrorMessage: installed shared-mime-info package post-installation script 
subprocess returned error exit status 127
  InstallationDate: Installed on 2016-03-14 (1489 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed 
shared-mime-info package post-installation script subprocess returned error 
exit status 127
  UpgradeStatus: Upgraded to bionic on 2020-04-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1872235/+subscriptions

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


[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2020-01-16 Thread BloodyIron
So far it's fixed for me! Yay!!!

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  The behaviour is changed back to what it was before 19.10, some users
  might find it inconvenient and prefer the auto switch but the feedback
  we got shows it's unreliable and an annoying for the majority of our
  users so we will got back to default to safest behaviour.

  The fix proposed just reverts to the same code used in PulseAudio 12
  and earlier. It has also been released and verified on focal already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

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


[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2020-01-16 Thread BloodyIron
Woot! Thanks for rolling this out all involved! \o/ Stuff like this is
why I love FOSS.

Now to try it out!

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  The behaviour is changed back to what it was before 19.10, some users
  might find it inconvenient and prefer the auto switch but the feedback
  we got shows it's unreliable and an annoying for the majority of our
  users so we will got back to default to safest behaviour.

  The fix proposed just reverts to the same code used in PulseAudio 12
  and earlier. It has also been released and verified on focal already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

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


[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2020-01-07 Thread BloodyIron
Waiting on release for Eoan :D

Thanks for getting this fixed! \o/

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  Low. The fix proposed just reverts to the same code used in PulseAudio
  12 and earlier. It has also been released and verified on focal
  already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

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


[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2019-12-17 Thread BloodyIron
Any word how long before this might hit main repos for 19.10?

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Triaged
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

  ---

  WORKAROUND

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

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


[Touch-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

2019-11-06 Thread BloodyIron
So this is actually happening now every time I lock my computer, no
power change whatsoever (no standby, no suspend to RAM, no power
off/reboot). So this is now becoming very frustrating to work with as I
have to change my default audio device every time I use my computer now
so that my volume controls (up/down) actually work.

Can we PLEASE get this at least started to be looked at?

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

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

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

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


[Touch-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

2019-11-05 Thread BloodyIron
I just upgraded from 19.04 to 19.10 and this happens every reboot, my
default audio switches from my sound card to my HDMI audio output.

This kind of a regression is really going to turn new users off to
Ubuntu/Linux.

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

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

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

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


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

2018-11-11 Thread BloodyIron
Public bug reported:

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

The solution was

systemctl disable bluetooth

So, to disable the bluetooth daemon.

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

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

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

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

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

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

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


** Tags: amd64 apport-bug cosmic

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

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

Status in bluez package in Ubuntu:
  New

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

  The solution was

  systemctl disable bluetooth

  So, to disable the bluetooth daemon.

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

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

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

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

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

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

[Touch-packages] [Bug 1801623] [NEW] Bluetooth keeps starting by default on boot, prefer it's off by default

2018-11-04 Thread BloodyIron
Public bug reported:

Bluetooth keeps starting by default on boot, I turn it off, and it's not
set to start in startup applications. Need a way for it to be always off
by default, but still be able to turn it on when I need it.

I've been seeing this for many major Ubuntu versions for years. Finally
submitting this.

Ubuntu 18.04 currently.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Nov  4 16:03:12 2018
InstallationDate: Installed on 2017-02-18 (624 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 239242U
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=aacb9562-db8b-4a32-8e9b-47530c8c0331 ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: Upgraded to bionic on 2018-04-28 (189 days ago)
dmi.bios.date: 05/29/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G4ET37WW (1.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 239242U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG4ET37WW(1.12):bd05/29/2012:svnLENOVO:pn239242U:pvrThinkPadT530:rvnLENOVO:rn239242U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T530
dmi.product.name: 239242U
dmi.product.version: ThinkPad T530
dmi.sys.vendor: LENOVO
hciconfig:

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


** Tags: amd64 apport-bug bionic

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

Title:
  Bluetooth keeps starting by default on boot, prefer it's off by
  default

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth keeps starting by default on boot, I turn it off, and it's
  not set to start in startup applications. Need a way for it to be
  always off by default, but still be able to turn it on when I need it.

  I've been seeing this for many major Ubuntu versions for years.
  Finally submitting this.

  Ubuntu 18.04 currently.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Nov  4 16:03:12 2018
  InstallationDate: Installed on 2017-02-18 (624 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 239242U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=aacb9562-db8b-4a32-8e9b-47530c8c0331 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (189 days ago)
  dmi.bios.date: 05/29/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ET37WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 239242U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG4ET37WW(1.12):bd05/29/2012:svnLENOVO:pn239242U:pvrThinkPadT530:rvnLENOVO:rn239242U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T530
  dmi.product.name: 239242U
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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


[Touch-packages] [Bug 1694093] [NEW] VPN passwords save when they shouldn't

2017-05-27 Thread BloodyIron
Public bug reported:

I use network-manager to connect to openVPN servers.

First, when adding a new VPN config, entering a login is required, and
we are unable to save if we do not enter a username. This is a security
flaw as we need the ability to enter login and password each and every
time as an option.

Second, I enter a login username, but not a password. On first
connection it asks for a password, but never again. I have never been
asked for a password on the same VPN after entering it the first time.
This persists across reboots also. This is a substantial security flaw,
and this should be an option, not the default behaviour.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.6-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-53.56-generic 4.8.17
Uname: Linux 4.8.0-53-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.3
Architecture: amd64
CurrentDesktop: Unity
Date: Sat May 27 21:35:10 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-02-18 (99 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 tun0 tun   connected/org/freedesktop/NetworkManager/Devices/4  
tun03337e7b3-7794-4539-a5a3-0a534f60800f  
/org/freedesktop/NetworkManager/ActiveConnection/6 
 wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
notforyou   e8f5ba42-91e9-4755-b1b7-0c030961f69e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --  
----
 
 lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  --  
----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug yakkety

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

Title:
  VPN passwords save when they shouldn't

Status in network-manager package in Ubuntu:
  New

Bug description:
  I use network-manager to connect to openVPN servers.

  First, when adding a new VPN config, entering a login is required, and
  we are unable to save if we do not enter a username. This is a
  security flaw as we need the ability to enter login and password each
  and every time as an option.

  Second, I enter a login username, but not a password. On first
  connection it asks for a password, but never again. I have never been
  asked for a password on the same VPN after entering it the first time.
  This persists across reboots also. This is a substantial security
  flaw, and this should be an option, not the default behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May 27 21:35:10 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-18 (99 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   tun0 tun   connected/org/freedesktop/NetworkManager/Devices/4  
tun03337e7b3-7794-4539-a5a3-0a534f60800f  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
notforyou   e8f5ba42-91e9-4755-b1b7-0c030961f69e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo