[Touch-packages] [Bug 1828665] Re: [regression] Reboot after dpkg update set invalid Graphics resolutions (Dual Monitor) since ~7th/8th May

2019-05-12 Thread Daniel van Vugt
** Summary changed:

- Reboot after dpkg update set invalid Graphics resolutions (Dual Monitor)
+ [regression] Reboot after dpkg update set invalid Graphics resolutions (Dual 
Monitor) since ~7th/8th May

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

** Tags added: regression-update

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

Title:
  [regression] Reboot after dpkg update set invalid Graphics resolutions
  (Dual Monitor) since ~7th/8th May

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Now at Ubuntu 18.04.2 LTS, Gnome 3.28.2

  Deduction.  The user device settings menu for desktop control dual
  monitors offer the correct modes available.  The Bionic Beaver update
  does something different.

  Dual monitor configuration (Formerly Primary on Display Port 3840x2160
  30Hz, Secondary on HDMI 3840x2160 30Hz on a three video output Intel
  HD620) for Cancer Research using LibreOffice Calc across both.
  Upgrades permitted manually rather than auto and usually done within a
  day.  Since five months both monitors were operating HDMI (Display
  port not connected, not used) with Primary on HDMI2 and Secondary on
  HDMI1, both at 3840x2160 30Hz.  Neither monitor is capable of 60Hz at
  UHD which is quite alright for office work.  When installing such
  devices, strictly only the 3840x2160 30Hz mode is available on the
  settings page.

  After the most recent update (7/8th may), the primary screen was blank
  on reboot (abnormal) and the secondary screen showed the extended
  desktop without menus (as usual). Rebooting to see the primary was
  unsuccessful and then the secondary monitor failed completely
  (confirmed the next day as graphics card hardware, broken).  Cold
  disconnect of the secondary (awaiting repair), another boot brought up
  Primary display only yet flickering occasionally.

  Primary Display.   Considering the possibility of error in the
  graphics since the update - the Device settings (normal user page)
  revealed that the update had changed the output to HDMI 4096 lines
  (which the PC monitor can't do and the user can't select - outside
  specification).  I was in such a hurry to save it also from damage
  that I put back the resolution to 3840x2160 30Hz immediately, without
  looking at which frequency had been set with the 4096 value.  Now on
  rebooting, the display settings menu shows appropriately only
  3840x2160 30 Hz as choice.   It seems the Bionic Beaver update needed
  something else and set 4096 (which the user can't and notwithstanding
  the original user configuration).

  Secondary Display.  I don't know what it set, but it blew the monitor
  card.  The linux sent either 3840 at 60 Hz or 4096 at any frequency
  without negociation, without being able to respect the user settings.
  It's also possible that it used a very low resolution for a few
  seconds which the secondary monitor can't do either;  it's (well, it
  was) a real PC monitor with choices of DP or HDMI yet can jump into
  various modes (such as 60/75Hz for gamers). After some Ubuntu upgrades
  in the past (blank secondary screen), it was necessary to go back into
  the monitor menu to switch off again the gamer mode.

  Something similar happened in 2017 with Light Ubuntu Update.   The
  Secondary (very expensive) display making very alarming noises and
  staying blank for half a day.  Now it's truly broken (I know it's the
  driver circuit and which parts). Waiting for repair or replacement,
  the system is in use now with the same Primary PC monitor and a UHD
  television as secondary to get by.

  I worked 20 years on PC systems and monitors (for ship control) and
  accept that in the past we nearly always used a simple basic portable
  VGA monitor for system upgrades, then reconnected the user's gear
  later.  I think I'll only do (and postpone) Linux upgrades from now
  using a spare single desktop monitor at 1920x1080. That was a very
  worrying experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat May 11 11:21:30 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 620 
[1297:4052]
  InstallationDate: Installed on 2018-09-13 (239 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0

[Touch-packages] [Bug 1828682] Re: Utility applications are not placed in the Utilities folder

2019-05-12 Thread Daniel van Vugt
Per the upstream bug:

  https://gitlab.gnome.org/GNOME/gnome-software/issues/642

The designation of apps in the Utilities folder is the job of gnome-
software:

  https://gitlab.gnome.org/GNOME/gnome-software/blob/master/src/gs-
folders.c#L535

So we can remove the other tasks...

** Also affects: gnome-software via
   https://gitlab.gnome.org/GNOME/gnome-software/issues/642
   Importance: Unknown
   Status: Unknown

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

** Changed in: gnome-software (Ubuntu)
   Status: New => Opinion

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => Low

** No longer affects: gnome-power-manager (Ubuntu)

** No longer affects: gnome-session (Ubuntu)

** No longer affects: gnome-system-monitor (Ubuntu)

** No longer affects: im-config (Ubuntu)

** No longer affects: language-selector (Ubuntu)

** No longer affects: seahorse (Ubuntu)

** No longer affects: software-properties (Ubuntu)

** No longer affects: update-manager (Ubuntu)

** No longer affects: usb-creator (Ubuntu)

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

Title:
  Utility applications are not placed in the Utilities folder

Status in GNOME Software:
  Unknown
Status in gnome-software package in Ubuntu:
  Opinion

Bug description:
  Some utility applications used in Ubuntu are not placed in the
  Utilities folder. These applications are:

  Language Support
  Software & Updates
  Livepatch
  Software Updater
  Power Statistics
  Startup Applications
  Startup Disk Creator
  Passwords and Keys
  Input Method

  Please, consider moving them to the Utilities folder.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1828682/+subscriptions

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


[Touch-packages] [Bug 1828569] Re: Popping sound when audio driver engaged

2019-05-12 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1828613 ***
https://bugs.launchpad.net/bugs/1828613

Moved to bug 1828613

** This bug has been marked a duplicate of bug 1828613
   See - [Bug 1828569] [NEW] Popping sound when audio driver engaged - [, 
Realtek ALC889, Green Line Out, Rear] Playback problem

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

Title:
  Popping sound when audio driver engaged

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Fresh install of Disco over the weekend on new hard drive.  Any time a
  sound plays, whether it's from a browser (both Firefox and Chromium),
  Slack, video or MP3 file, sound in VirtualBox OS, etc.  Any sound,
  even an alert sound or even just opening an app that may make a sound
  (e.g. opening a browser page that may have alerts or sounds (like a
  game) makes the same popping sound just when browsing to that page).

  It's preceded by a pop or a click from the speakers, a fast pop-pop
  sound.

  When said audio is finished, about 25% of the time there is another
  audible pop or click.

  I have 18.04.x LTS on another hard drive and when I boot to that
  instance I do not have the pop sound.

  I believe it's probably driver related, but I'm not sure where to
  look.

  Fresh disco install, have performed apt updates, and rebooted several
  times.  Has persisted for several weeks.

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

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


[Touch-packages] [Bug 1828613] Re: See - [Bug 1828569] [NEW] Popping sound when audio driver engaged - [, Realtek ALC889, Green Line Out, Rear] Playback problem

2019-05-12 Thread Daniel van Vugt
This sounds like bug 1821663. But because the fix for that bug is
specific to laptop/motherboard models, we should keep this bug separate.

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

** Summary changed:

- See - [Bug 1828569] [NEW] Popping sound when audio driver engaged - [, 
Realtek ALC889, Green Line Out, Rear] Playback problem
+ [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged

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

Title:
  [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver
  engaged

Status in linux package in Ubuntu:
  New

Bug description:
  I had logged bug 1828569 and then ran this test to provide the
  driver/hardware info.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sidboswell   1591 F pulseaudio
   /dev/snd/controlC2:  sidboswell   1591 F pulseaudio
   /dev/snd/controlC0:  sidboswell   1591 F pulseaudio
   /dev/snd/controlC3:  sidboswell   1591 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 10 12:03:10 2019
  InstallationDate: Installed on 2019-04-20 (19 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080016
  dmi.board.name: EVGA P55 3X SLI E658
  dmi.board.vendor: EVGA
  dmi.board.version: Ibex Peak
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr:

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

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


[Touch-packages] [Bug 1828718] Re: [HP Notebook, Realtek ALC3227, Speaker, Internal] sound is very low

2019-05-12 Thread Daniel van Vugt
** Summary changed:

- [HP Notebook, Realtek ALC3227, Speaker, Internal] Playback problem. 
+ [HP Notebook, Realtek ALC3227, Speaker, Internal] sound is very low

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

Title:
  [HP Notebook, Realtek ALC3227, Speaker, Internal] sound is very low

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  sound is very low for videos both hevc and h264 . even with
  amplification.  and fine in youtube. overall sound is very much less
  than when i was in windows 10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thanveer   1898 F pulseaudio
   /dev/snd/controlC0:  thanveer   1898 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 12 14:45:17 2019
  InstallationDate: Installed on 2019-05-12 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [HP Notebook, Realtek ALC3227, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EF
  dmi.board.vendor: HP
  dmi.board.version: 63.47
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd08/29/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EF:rvr63.47:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Notebook
  dmi.product.sku: W6T33PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Touch-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

2019-05-12 Thread Daniel van Vugt
User 'gdm' is normal and not a bug. That's the user which runs the login
screen.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

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

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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


[Touch-packages] [Bug 1788807] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565]

2019-05-12 Thread Daniel van Vugt
This bug is closed so if you have any ongoing problems then please open
a new bug by running:

  ubuntu-bug bluez

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

Title:
  Bluetooth device not detected after resume from suspend [Qualcomm
  Atheros QCA9565]

Status in bluez package in Ubuntu:
  Expired
Status in gnome-bluetooth package in Ubuntu:
  Expired

Bug description:
  When I suspend my laptop, it often happens that the bluetooth stops
  working. From gnome settings it is shown like if I had no bluetooth
  device at all.

  $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 
'blue|firm'
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: AzureWave QCA9565 / AR9565 Wireless Network Adapter 
[1a3b:2130]
Kernel driver in use: ath9k
Kernel modules: ath9k
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader [10ec:5287] (rev 01)
  --
  04:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit 
Ethernet Controller [1043:200f]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
  Bus 001 Device 006: ID 13d3:3408 IMC Networks 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  4.15.0-32-generic
  [0.024000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.048030] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [2.758768] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
  [   35.407491] Bluetooth: Core ver 2.22
  [   35.407504] Bluetooth: HCI device and connection manager initialized
  [   35.407506] Bluetooth: HCI socket layer initialized
  [   35.407507] Bluetooth: L2CAP socket layer initialized
  [   35.407510] Bluetooth: SCO socket layer initialized
  [   53.501780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   53.501780] Bluetooth: BNEP filters: protocol multicast
  [   53.501783] Bluetooth: BNEP socket layer initialized
  [   87.220137] Bluetooth: RFCOMM TTY layer initialized
  [   87.220143] Bluetooth: RFCOMM socket layer initialized
  [   87.220149] Bluetooth: RFCOMM ver 1.11
  [ 1675.503865] usb 1-5: device firmware changed
  [ 1681.095543] Bluetooth: Can't get version to change to load ram patch err
  [ 1681.095546] Bluetooth: Loading patch file failed
  [ 4105.994687] audit: type=1107 audit(1534926184.213:339): pid=1258 uid=105 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=10248 
label="snap.signal-desktop.signal-desktop" peer_pid=1314 peer_label="unconfined"


  Trying to use bluetooth from bluetoothctl
  $ bluetoothctl
  Agent registered
  [bluetooth]# scan on
  No default controller available

  
  Trying to restart the bluetooth service doesn't produce any effect:
  $ sudo service bluetooth restart

  
  Getting bluetooth service status:
  $ sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Fri 2018-08-24 11:23:17 EEST; 1min 35s ago
   Docs: man:bluetoothd(8)
   Main PID: 24999 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/bluetooth.service
 └─24999 /usr/lib/bluetooth/bluetoothd

  elo 24 11:23:17 fabio-X550JK systemd[1]: Stopping Bluetooth service...
  elo 24 11:23:17 fabio-X550JK systemd[1]: Stopped Bluetooth service.
  elo 24 11:23:17 fabio-X550JK systemd[1]: Starting Bluetooth service...
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth daemon 5.48
  elo 24 11:23:17 fabio-X550JK systemd[1]: Started Bluetooth service.
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Starting SDP server
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth management 
interface 1
  lines 1-17/17 (END)

  
  Reloading the driver:
  $ sudo modprobe -r btusb; sudo modprobe btusb;
  $ sudo service bluetooth restart

  
  None of these attempts could solve the issue.


  What happens?
  Bluetooth is working, I suspend my laptop, I resume my laptop -> Bluetooth 
controller is no longer recognised and bluetooth service cannot be used anymore.

  What would you expect?
  Bluetooth controller to be recognised and working also after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Pac

[Touch-packages] [Bug 1828749] Re: ifconfig dummy0 : Device not found

2019-05-12 Thread John Denker
I put the attached file in if-pre-up.d/dummy-workaround
to make my system work reliably.

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

Title:
  ifconfig dummy0 : Device not found

Status in net-tools package in Ubuntu:
  New

Bug description:
  Desired behavior:
The ifconfig command should be able to deal with the
dummy device.  This worked fine until recently.

  Observed behavior:
:; ifconfig dummy0
dummy0: error fetching interface information: Device not found

This problem appeared when I upgraded to bionic.

  Highly informative workaround:
:; ip link add dummy0 type dummy
That command works, and makes the problem go away permanently.
The ifconfig command works fine after that.
The ifup and ifdown commands also work fine after that.

For convenient debugging, you can use the command:
:; ip link del dummy0 type dummy
which makes the problem come back.
You can also experiment with dummy1 et cetera.

  Package ownership issues:
Compare: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909204
That report was filed against ippusbxd, which is almost certainly
not the relevant package.

For that matter, I have no idea whether the root cause is in the
net-tools package or the kernel networking stack.  All I know is
the ip command plays nicely with the kernel while the ifconfig
command does not.

  
  Notes:
The kernel module for the dummy interface is preloaded in
all situations described here.  That's not the issue.

An apport file is attached, to describe the environment.
Also, since you asked:

:; apt-cache policy net-tools
  net-tools:
Installed: 1.60-26ubuntu1
Candidate: 1.60-26ubuntu1
Version table:
   *** 1.60-26ubuntu1 500
  500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

:; lsb_release -rd
Description:Ubuntu 16.04.6 LTS
Release:16.04

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

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


[Touch-packages] [Bug 1828749] Re: ifconfig dummy0 : Device not found

2019-05-12 Thread John Denker
Here's the workaround.

** Attachment added: "workaround for ifconfig dummy0 bug"
   
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1828749/+attachment/5263317/+files/dummy-workaround

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

Title:
  ifconfig dummy0 : Device not found

Status in net-tools package in Ubuntu:
  New

Bug description:
  Desired behavior:
The ifconfig command should be able to deal with the
dummy device.  This worked fine until recently.

  Observed behavior:
:; ifconfig dummy0
dummy0: error fetching interface information: Device not found

This problem appeared when I upgraded to bionic.

  Highly informative workaround:
:; ip link add dummy0 type dummy
That command works, and makes the problem go away permanently.
The ifconfig command works fine after that.
The ifup and ifdown commands also work fine after that.

For convenient debugging, you can use the command:
:; ip link del dummy0 type dummy
which makes the problem come back.
You can also experiment with dummy1 et cetera.

  Package ownership issues:
Compare: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909204
That report was filed against ippusbxd, which is almost certainly
not the relevant package.

For that matter, I have no idea whether the root cause is in the
net-tools package or the kernel networking stack.  All I know is
the ip command plays nicely with the kernel while the ifconfig
command does not.

  
  Notes:
The kernel module for the dummy interface is preloaded in
all situations described here.  That's not the issue.

An apport file is attached, to describe the environment.
Also, since you asked:

:; apt-cache policy net-tools
  net-tools:
Installed: 1.60-26ubuntu1
Candidate: 1.60-26ubuntu1
Version table:
   *** 1.60-26ubuntu1 500
  500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

:; lsb_release -rd
Description:Ubuntu 16.04.6 LTS
Release:16.04

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

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


[Touch-packages] [Bug 1828749] [NEW] ifconfig dummy0 : Device not found

2019-05-12 Thread John Denker
Public bug reported:

Desired behavior:
  The ifconfig command should be able to deal with the
  dummy device.  This worked fine until recently.

Observed behavior:
  :; ifconfig dummy0
  dummy0: error fetching interface information: Device not found

  This problem appeared when I upgraded to bionic.

Highly informative workaround:
  :; ip link add dummy0 type dummy
  That command works, and makes the problem go away permanently.
  The ifconfig command works fine after that.
  The ifup and ifdown commands also work fine after that.

  For convenient debugging, you can use the command:
  :; ip link del dummy0 type dummy
  which makes the problem come back.
  You can also experiment with dummy1 et cetera.

Package ownership issues:
  Compare: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909204
  That report was filed against ippusbxd, which is almost certainly
  not the relevant package.

  For that matter, I have no idea whether the root cause is in the
  net-tools package or the kernel networking stack.  All I know is
  the ip command plays nicely with the kernel while the ifconfig
  command does not.


Notes:
  The kernel module for the dummy interface is preloaded in
  all situations described here.  That's not the issue.

  An apport file is attached, to describe the environment.
  Also, since you asked:

  :; apt-cache policy net-tools
net-tools:
  Installed: 1.60-26ubuntu1
  Candidate: 1.60-26ubuntu1
  Version table:
 *** 1.60-26ubuntu1 500
500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

  :; lsb_release -rd
  Description:Ubuntu 16.04.6 LTS
  Release:16.04

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

** Attachment added: "apport file describing the system"
   
https://bugs.launchpad.net/bugs/1828749/+attachment/5263315/+files/apport.net-tools.yuq36yqq.apport

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

Title:
  ifconfig dummy0 : Device not found

Status in net-tools package in Ubuntu:
  New

Bug description:
  Desired behavior:
The ifconfig command should be able to deal with the
dummy device.  This worked fine until recently.

  Observed behavior:
:; ifconfig dummy0
dummy0: error fetching interface information: Device not found

This problem appeared when I upgraded to bionic.

  Highly informative workaround:
:; ip link add dummy0 type dummy
That command works, and makes the problem go away permanently.
The ifconfig command works fine after that.
The ifup and ifdown commands also work fine after that.

For convenient debugging, you can use the command:
:; ip link del dummy0 type dummy
which makes the problem come back.
You can also experiment with dummy1 et cetera.

  Package ownership issues:
Compare: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909204
That report was filed against ippusbxd, which is almost certainly
not the relevant package.

For that matter, I have no idea whether the root cause is in the
net-tools package or the kernel networking stack.  All I know is
the ip command plays nicely with the kernel while the ifconfig
command does not.

  
  Notes:
The kernel module for the dummy interface is preloaded in
all situations described here.  That's not the issue.

An apport file is attached, to describe the environment.
Also, since you asked:

:; apt-cache policy net-tools
  net-tools:
Installed: 1.60-26ubuntu1
Candidate: 1.60-26ubuntu1
Version table:
   *** 1.60-26ubuntu1 500
  500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

:; lsb_release -rd
Description:Ubuntu 16.04.6 LTS
Release:16.04

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

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


[Touch-packages] [Bug 1827391] Re: Japanese era Reiwa SRU

2019-05-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Japanese era  Reiwa SRU

Status in icu package in Ubuntu:
  Fix Released
Status in icu source package in Precise:
  Confirmed
Status in icu source package in Trusty:
  Confirmed
Status in icu source package in Xenial:
  Confirmed
Status in icu source package in Bionic:
  Confirmed
Status in icu source package in Cosmic:
  Confirmed
Status in icu source package in Disco:
  Confirmed
Status in icu source package in Eoan:
  Fix Released
Status in icu package in Debian:
  Fix Released

Bug description:
  Japanese era  Reiwa SRU

  $ rmadison icu
  4.8.1.1-3ubuntu0.7 | precise-updates
  52.1-3ubuntu0.8| trusty-updates
  55.1-7ubuntu0.4| xenial-updates
  60.2-3ubuntu3  | bionic
  60.2-6ubuntu1  | cosmic
  63.1-6 | disco
  63.1-6 | eoan

  Note reported abi break / crash of chromium at

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933

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

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


[Touch-packages] [Bug 1827391] Re: Japanese era Reiwa SRU

2019-05-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Japanese era  Reiwa SRU

Status in icu package in Ubuntu:
  Fix Released
Status in icu source package in Precise:
  Confirmed
Status in icu source package in Trusty:
  Confirmed
Status in icu source package in Xenial:
  Confirmed
Status in icu source package in Bionic:
  Confirmed
Status in icu source package in Cosmic:
  Confirmed
Status in icu source package in Disco:
  Confirmed
Status in icu source package in Eoan:
  Fix Released
Status in icu package in Debian:
  Fix Released

Bug description:
  Japanese era  Reiwa SRU

  $ rmadison icu
  4.8.1.1-3ubuntu0.7 | precise-updates
  52.1-3ubuntu0.8| trusty-updates
  55.1-7ubuntu0.4| xenial-updates
  60.2-3ubuntu3  | bionic
  60.2-6ubuntu1  | cosmic
  63.1-6 | disco
  63.1-6 | eoan

  Note reported abi break / crash of chromium at

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933

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

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


[Touch-packages] [Bug 1827391] Re: Japanese era Reiwa SRU

2019-05-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Japanese era  Reiwa SRU

Status in icu package in Ubuntu:
  Fix Released
Status in icu source package in Precise:
  Confirmed
Status in icu source package in Trusty:
  Confirmed
Status in icu source package in Xenial:
  Confirmed
Status in icu source package in Bionic:
  Confirmed
Status in icu source package in Cosmic:
  Confirmed
Status in icu source package in Disco:
  Confirmed
Status in icu source package in Eoan:
  Fix Released
Status in icu package in Debian:
  Fix Released

Bug description:
  Japanese era  Reiwa SRU

  $ rmadison icu
  4.8.1.1-3ubuntu0.7 | precise-updates
  52.1-3ubuntu0.8| trusty-updates
  55.1-7ubuntu0.4| xenial-updates
  60.2-3ubuntu3  | bionic
  60.2-6ubuntu1  | cosmic
  63.1-6 | disco
  63.1-6 | eoan

  Note reported abi break / crash of chromium at

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933

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

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


[Touch-packages] [Bug 1827391] Re: Japanese era Reiwa SRU

2019-05-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Japanese era  Reiwa SRU

Status in icu package in Ubuntu:
  Fix Released
Status in icu source package in Precise:
  Confirmed
Status in icu source package in Trusty:
  Confirmed
Status in icu source package in Xenial:
  Confirmed
Status in icu source package in Bionic:
  Confirmed
Status in icu source package in Cosmic:
  Confirmed
Status in icu source package in Disco:
  Confirmed
Status in icu source package in Eoan:
  Fix Released
Status in icu package in Debian:
  Fix Released

Bug description:
  Japanese era  Reiwa SRU

  $ rmadison icu
  4.8.1.1-3ubuntu0.7 | precise-updates
  52.1-3ubuntu0.8| trusty-updates
  55.1-7ubuntu0.4| xenial-updates
  60.2-3ubuntu3  | bionic
  60.2-6ubuntu1  | cosmic
  63.1-6 | disco
  63.1-6 | eoan

  Note reported abi break / crash of chromium at

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933

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

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


[Touch-packages] [Bug 1827391] Re: Japanese era Reiwa SRU

2019-05-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Japanese era  Reiwa SRU

Status in icu package in Ubuntu:
  Fix Released
Status in icu source package in Precise:
  Confirmed
Status in icu source package in Trusty:
  Confirmed
Status in icu source package in Xenial:
  Confirmed
Status in icu source package in Bionic:
  Confirmed
Status in icu source package in Cosmic:
  Confirmed
Status in icu source package in Disco:
  Confirmed
Status in icu source package in Eoan:
  Fix Released
Status in icu package in Debian:
  Fix Released

Bug description:
  Japanese era  Reiwa SRU

  $ rmadison icu
  4.8.1.1-3ubuntu0.7 | precise-updates
  52.1-3ubuntu0.8| trusty-updates
  55.1-7ubuntu0.4| xenial-updates
  60.2-3ubuntu3  | bionic
  60.2-6ubuntu1  | cosmic
  63.1-6 | disco
  63.1-6 | eoan

  Note reported abi break / crash of chromium at

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933

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

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


[Touch-packages] [Bug 1827391] Re: Japanese era Reiwa SRU

2019-05-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Japanese era  Reiwa SRU

Status in icu package in Ubuntu:
  Fix Released
Status in icu source package in Precise:
  Confirmed
Status in icu source package in Trusty:
  Confirmed
Status in icu source package in Xenial:
  Confirmed
Status in icu source package in Bionic:
  Confirmed
Status in icu source package in Cosmic:
  Confirmed
Status in icu source package in Disco:
  Confirmed
Status in icu source package in Eoan:
  Fix Released
Status in icu package in Debian:
  Fix Released

Bug description:
  Japanese era  Reiwa SRU

  $ rmadison icu
  4.8.1.1-3ubuntu0.7 | precise-updates
  52.1-3ubuntu0.8| trusty-updates
  55.1-7ubuntu0.4| xenial-updates
  60.2-3ubuntu3  | bionic
  60.2-6ubuntu1  | cosmic
  63.1-6 | disco
  63.1-6 | eoan

  Note reported abi break / crash of chromium at

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933

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

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


[Touch-packages] [Bug 1760910] Re: Gdebi crash in Ubuntu Studio 18.04

2019-05-12 Thread Singtoh
A bit of a work around that worked for me is in the gdebi.desktop file
where it says "Terminal=false" change it to "Terminal=true" minus the
quotes of course. A "terminal window"(sort of) pops up behind the gdebi
window and allows you to install, reinstall ect. Don't know but it
installs packages for me in this way. A bit easier this way than
pointing to the package you want to install through the terminal. Kind
of works normal this way.

Singtoh

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

Title:
  Gdebi crash in Ubuntu Studio 18.04

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Gdebi opens normal, but when you click install package, it closes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdebi 0.9.5.7+nmu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-lowlatency 4.15.10
  Uname: Linux 4.15.0-13-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Apr  3 12:31:17 2018
  InstallationDate: Installed on 2018-03-29 (4 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180328)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1817637] Re: a52 DigitalAC-3Pulseaudio not working on 19.04

2019-05-12 Thread kenjo
** Changed in: alsa-plugins (Ubuntu)
   Status: New => Fix Released

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

Title:
  a52 DigitalAC-3Pulseaudio not working on 19.04

Status in alsa-plugins package in Ubuntu:
  Fix Released

Bug description:
  So I upgraded to 19.04 and now I no longer can get the a52 working.

  It worked fine on 18.10.

  this is the description I follow https://help.ubuntu.com/community
  /DigitalAC-3Pulseaudio

  also the package libasound2-plugins-extra that is supposed to do this
  for you is not working.

  I use the same kernel version so it's only userspace that has changed.

  There looks to only be small changes in the driver and I'm not sure if
  the driver code is even called before you actually try to use it but I
  never get so far I can  not select the a52 device as it do not show up
  anywhere so I think its the configuraton that no longer works. or
  something, the configuration format is impossible to understand.

  https://git.alsa-project.org/?p=alsa-
  
plugins.git;a=history;f=a52/pcm_a52.c;h=b005bc2040c0113f69ca081e6f7f75d69616f64c;hb=HEAD

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

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


[Touch-packages] [Bug 1788048] Re: systemd journald failed unmounting var

2019-05-12 Thread Bug Watch Updater
** Changed in: systemd
   Status: New => Fix Released

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

Title:
  systemd journald failed unmounting var

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When the system is shut down or restarted the systemd-journal does not
  disassemble the disks correctly.

  On this thread https://unix.stackexchange.com/questions/378678/why-
  do-i-get-the-error-failed-unmounting-var-during-shutdown

  I checked what editing /etc/systemd/journald.conf
  to change the Storage = line to Storage = volatile the problem is solved, but 
some of the logs on the shutdown are lost.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Aug 20 18:15:07 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-08-20 (0 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=65cb761b-4881-4031-9113-e6bb6a1437b4 ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  mtime.conffile..etc.systemd.journald.conf: 2018-08-20T18:00:58.586165

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

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


[Touch-packages] [Bug 1828725] Re: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries)

2019-05-12 Thread Khurshid Alam
By "we" do you mean official ubuntu-mate team ? In that case, contact me
on community.ubuntu.com.

Indicator-datetime requires lots of changes including the upcoming api
break from eds. Someone from community proposed to remove phone realted
code and go back to c. Not sure if it is still possible.

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

Title:
  indicator-datetime does not have color squares for different calendars
  and dates from contacts (birthdays & anniversaries)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu with `indicator-datetime` and `evolution`
  2. Add event to *Personal* calendar (default color)
  3. Add new calendar and name it for example *Work* (red color)
  4. Create contact with two dates - birthday and anniversary (it is pink color)

  Expected results:
  * `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 
LTS (see screenshot - ubuntu-12-04.png)

  Actual results:
  * `indicator-datetime` show for event without color squares in the left of 
them (see screenshot - ubuntu-19-10.png)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun May 12 14:54:43 2019
  InstallationDate: Installed on 2019-04-28 (13 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1828725/+subscriptions

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


[Touch-packages] [Bug 1827391] Re: Japanese era Reiwa SRU

2019-05-12 Thread Dimitri John Ledkov
** Changed in: icu (Ubuntu Eoan)
   Status: New => Fix Released

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

Title:
  Japanese era  Reiwa SRU

Status in icu package in Ubuntu:
  Fix Released
Status in icu source package in Precise:
  New
Status in icu source package in Trusty:
  New
Status in icu source package in Xenial:
  New
Status in icu source package in Bionic:
  New
Status in icu source package in Cosmic:
  New
Status in icu source package in Disco:
  New
Status in icu source package in Eoan:
  Fix Released
Status in icu package in Debian:
  Fix Released

Bug description:
  Japanese era  Reiwa SRU

  $ rmadison icu
  4.8.1.1-3ubuntu0.7 | precise-updates
  52.1-3ubuntu0.8| trusty-updates
  55.1-7ubuntu0.4| xenial-updates
  60.2-3ubuntu3  | bionic
  60.2-6ubuntu1  | cosmic
  63.1-6 | disco
  63.1-6 | eoan

  Note reported abi break / crash of chromium at

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933

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

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


[Touch-packages] [Bug 1828725] Re: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries)

2019-05-12 Thread Norbert
** No longer affects: evolution-data-server (Ubuntu)

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

Title:
  indicator-datetime does not have color squares for different calendars
  and dates from contacts (birthdays & anniversaries)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu with `indicator-datetime` and `evolution`
  2. Add event to *Personal* calendar (default color)
  3. Add new calendar and name it for example *Work* (red color)
  4. Create contact with two dates - birthday and anniversary (it is pink color)

  Expected results:
  * `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 
LTS (see screenshot - ubuntu-12-04.png)

  Actual results:
  * `indicator-datetime` show for event without color squares in the left of 
them (see screenshot - ubuntu-19-10.png)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun May 12 14:54:43 2019
  InstallationDate: Installed on 2019-04-28 (13 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1828725/+subscriptions

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


[Touch-packages] [Bug 1788807] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565]

2019-05-12 Thread peacecop kalmer:
This bug reappears in 19.04 on ProBook 4520s.

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

Title:
  Bluetooth device not detected after resume from suspend [Qualcomm
  Atheros QCA9565]

Status in bluez package in Ubuntu:
  Expired
Status in gnome-bluetooth package in Ubuntu:
  Expired

Bug description:
  When I suspend my laptop, it often happens that the bluetooth stops
  working. From gnome settings it is shown like if I had no bluetooth
  device at all.

  $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 
'blue|firm'
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: AzureWave QCA9565 / AR9565 Wireless Network Adapter 
[1a3b:2130]
Kernel driver in use: ath9k
Kernel modules: ath9k
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader [10ec:5287] (rev 01)
  --
  04:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit 
Ethernet Controller [1043:200f]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
  Bus 001 Device 006: ID 13d3:3408 IMC Networks 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  4.15.0-32-generic
  [0.024000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.048030] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [2.758768] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
  [   35.407491] Bluetooth: Core ver 2.22
  [   35.407504] Bluetooth: HCI device and connection manager initialized
  [   35.407506] Bluetooth: HCI socket layer initialized
  [   35.407507] Bluetooth: L2CAP socket layer initialized
  [   35.407510] Bluetooth: SCO socket layer initialized
  [   53.501780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   53.501780] Bluetooth: BNEP filters: protocol multicast
  [   53.501783] Bluetooth: BNEP socket layer initialized
  [   87.220137] Bluetooth: RFCOMM TTY layer initialized
  [   87.220143] Bluetooth: RFCOMM socket layer initialized
  [   87.220149] Bluetooth: RFCOMM ver 1.11
  [ 1675.503865] usb 1-5: device firmware changed
  [ 1681.095543] Bluetooth: Can't get version to change to load ram patch err
  [ 1681.095546] Bluetooth: Loading patch file failed
  [ 4105.994687] audit: type=1107 audit(1534926184.213:339): pid=1258 uid=105 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=10248 
label="snap.signal-desktop.signal-desktop" peer_pid=1314 peer_label="unconfined"


  Trying to use bluetooth from bluetoothctl
  $ bluetoothctl
  Agent registered
  [bluetooth]# scan on
  No default controller available

  
  Trying to restart the bluetooth service doesn't produce any effect:
  $ sudo service bluetooth restart

  
  Getting bluetooth service status:
  $ sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Fri 2018-08-24 11:23:17 EEST; 1min 35s ago
   Docs: man:bluetoothd(8)
   Main PID: 24999 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/bluetooth.service
 └─24999 /usr/lib/bluetooth/bluetoothd

  elo 24 11:23:17 fabio-X550JK systemd[1]: Stopping Bluetooth service...
  elo 24 11:23:17 fabio-X550JK systemd[1]: Stopped Bluetooth service.
  elo 24 11:23:17 fabio-X550JK systemd[1]: Starting Bluetooth service...
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth daemon 5.48
  elo 24 11:23:17 fabio-X550JK systemd[1]: Started Bluetooth service.
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Starting SDP server
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth management 
interface 1
  lines 1-17/17 (END)

  
  Reloading the driver:
  $ sudo modprobe -r btusb; sudo modprobe btusb;
  $ sudo service bluetooth restart

  
  None of these attempts could solve the issue.


  What happens?
  Bluetooth is working, I suspend my laptop, I resume my laptop -> Bluetooth 
controller is no longer recognised and bluetooth service cannot be used anymore.

  What would you expect?
  Bluetooth controller to be recognised and working also after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-bluetooth 3.28.0-2
  ProcVersionSignature: Ubuntu 4.15.0

[Touch-packages] [Bug 1828725] Re: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries)

2019-05-12 Thread Norbert
There are color squares in Ubuntu 12.04 LTS for both GTK2 and GTK3 versions of 
`indicator-datetime`.
Squares are in place on 12.10, 13.04, 13.10.

There are no color squares in Ubuntu 14.04 LTS. So it first release
without them.

@Krusrshid, on Ubuntu MATE 19.10 we plan to use `indicator-datetime`.

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

Title:
  indicator-datetime does not have color squares for different calendars
  and dates from contacts (birthdays & anniversaries)

Status in evolution-data-server package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu with `indicator-datetime` and `evolution`
  2. Add event to *Personal* calendar (default color)
  3. Add new calendar and name it for example *Work* (red color)
  4. Create contact with two dates - birthday and anniversary (it is pink color)

  Expected results:
  * `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 
LTS (see screenshot - ubuntu-12-04.png)

  Actual results:
  * `indicator-datetime` show for event without color squares in the left of 
them (see screenshot - ubuntu-19-10.png)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun May 12 14:54:43 2019
  InstallationDate: Installed on 2019-04-28 (13 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1828725/+subscriptions

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


[Touch-packages] [Bug 1828725] Re: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries)

2019-05-12 Thread Khurshid Alam
Why this is relevant in 19.10 ? Trusty already had eol.

Indicator-datetime was ported from C to C++ (r: 298) to work with
unity-8 and that feature gone missing with that. But there is no unity-8
anymore and the code doesn't work.

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

Title:
  indicator-datetime does not have color squares for different calendars
  and dates from contacts (birthdays & anniversaries)

Status in evolution-data-server package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu with `indicator-datetime` and `evolution`
  2. Add event to *Personal* calendar (default color)
  3. Add new calendar and name it for example *Work* (red color)
  4. Create contact with two dates - birthday and anniversary (it is pink color)

  Expected results:
  * `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 
LTS (see screenshot - ubuntu-12-04.png)

  Actual results:
  * `indicator-datetime` show for event without color squares in the left of 
them (see screenshot - ubuntu-19-10.png)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun May 12 14:54:43 2019
  InstallationDate: Installed on 2019-04-28 (13 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1828725/+subscriptions

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


[Touch-packages] [Bug 1828725] Re: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries)

2019-05-12 Thread Norbert
** Also affects: evolution-data-server (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  indicator-datetime does not have color squares for different calendars
  and dates from contacts (birthdays & anniversaries)

Status in evolution-data-server package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu with `indicator-datetime` and `evolution`
  2. Add event to *Personal* calendar (default color)
  3. Add new calendar and name it for example *Work* (red color)
  4. Create contact with two dates - birthday and anniversary (it is pink color)

  Expected results:
  * `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 
LTS (see screenshot - ubuntu-12-04.png)

  Actual results:
  * `indicator-datetime` show for event without color squares in the left of 
them (see screenshot - ubuntu-19-10.png)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun May 12 14:54:43 2019
  InstallationDate: Installed on 2019-04-28 (13 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1828725/+subscriptions

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


[Touch-packages] [Bug 538097] Re: +storeblob fails with "500 Internal server error" on production (works on edge)

2019-05-12 Thread petr
** Also affects: apport (Linux From Scratch)
   Importance: Undecided
   Status: New

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

Title:
  +storeblob fails with "500 Internal server error" on production (works
  on edge)

Status in Launchpad itself:
  Fix Released
Status in apport package in Ubuntu:
  Invalid
Status in apport package in Linux From Scratch:
  New

Bug description:
  Binary package hint: apport

  On latest lucid, apport will not connect via a verified establish
  Internet connection.

  STR:
  1) Attempt to submit a crash report from /var/crash
  2) Apport dialog titled "Network Problem" with the text, "Cannot connect to 
crash database, please check your internet connection."

  Ubuntu forum discussion  & confirmation here:
  http://ubuntuforums.org/showthread.php?t=1428033

  Let me know what debugging information I may provide to assist in
  this.

  The actual error that apport gets is: HTTP Error 500: Internal Server
  Error

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

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


[Touch-packages] [Bug 1828725] Re: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries)

2019-05-12 Thread Norbert
** Tags added: trusty

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

Title:
  indicator-datetime does not have color squares for different calendars
  and dates from contacts (birthdays & anniversaries)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu with `indicator-datetime` and `evolution`
  2. Add event to *Personal* calendar (default color)
  3. Add new calendar and name it for example *Work* (red color)
  4. Create contact with two dates - birthday and anniversary (it is pink color)

  Expected results:
  * `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 
LTS (see screenshot - ubuntu-12-04.png)

  Actual results:
  * `indicator-datetime` show for event without color squares in the left of 
them (see screenshot - ubuntu-19-10.png)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun May 12 14:54:43 2019
  InstallationDate: Installed on 2019-04-28 (13 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1828725/+subscriptions

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


[Touch-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

2019-05-12 Thread Adrian Mariano
On my ubuntu 18.04 system I only have

/usr/bin/pulseaudio --start --log-target=syslog

owned by me.  On my 19.04 system

/usr/bin/pulseaudio --daemonize=no

also owned by me.  Note gdm is not running.  I assume lightdm, which is
running, is the alternative.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

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

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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


[Touch-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

2019-05-12 Thread Hui Wang
my system is ubuntu 18.04. And from log ps:

The user of "/usr/bin/pulseaudio --daemonize=no" is gdm

The user of "/usr/bin/pulseaudio --start --log-target=syslog" is my
account.


If the user is differnt, I have no idea, maybe we should report the problem to 
pulseaudio-disc...@lists.freedesktop.org.

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

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

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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


[Touch-packages] [Bug 1828725] Re: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries)

2019-05-12 Thread Norbert
Seems to be regression.

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

Title:
  indicator-datetime does not have color squares for different calendars
  and dates from contacts (birthdays & anniversaries)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu with `indicator-datetime` and `evolution`
  2. Add event to *Personal* calendar (default color)
  3. Add new calendar and name it for example *Work* (red color)
  4. Create contact with two dates - birthday and anniversary (it is pink color)

  Expected results:
  * `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 
LTS (see screenshot - ubuntu-12-04.png)

  Actual results:
  * `indicator-datetime` show for event without color squares in the left of 
them (see screenshot - ubuntu-19-10.png)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun May 12 14:54:43 2019
  InstallationDate: Installed on 2019-04-28 (13 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1828725/+subscriptions

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


[Touch-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

2019-05-12 Thread Adrian Mariano
>From ps I see that "/usr/bin/pulseaudio --daemonize=no" is running with
user "adrian" and also my home directory is owned by "adrian".

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

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

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

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

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


[Touch-packages] [Bug 1828725] Re: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries)

2019-05-12 Thread Sebastien Bacher
** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Confirmed

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

Title:
  indicator-datetime does not have color squares for different calendars
  and dates from contacts (birthdays & anniversaries)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu with `indicator-datetime` and `evolution`
  2. Add event to *Personal* calendar (default color)
  3. Add new calendar and name it for example *Work* (red color)
  4. Create contact with two dates - birthday and anniversary (it is pink color)

  Expected results:
  * `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 
LTS (see screenshot - ubuntu-12-04.png)

  Actual results:
  * `indicator-datetime` show for event without color squares in the left of 
them (see screenshot - ubuntu-19-10.png)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun May 12 14:54:43 2019
  InstallationDate: Installed on 2019-04-28 (13 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1828725/+subscriptions

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


[Touch-packages] [Bug 1733002] Re: Google Online Account Two Factor with hardware key fails immediately

2019-05-12 Thread Bug Watch Updater
Launchpad has imported 18 comments from the remote bug at
https://bugs.webkit.org/show_bug.cgi?id=143491.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-04-07T18:39:36+00:00 Ry5n wrote:

The FIDO Universal Second Factor (U2F) protocol is an open specification
that was recently finalized.  The FINAL spec can be downloaded here:
https://fidoalliance.org/specs/fido-u2f-v1.0-ps-20141009.zip

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1733002/comments/0


On 2016-05-19T18:49:02+00:00 E-alice wrote:

Created attachment 279408
U2F request flow diagram.

U2F is beginning to see more wide-spread deployment, with Github being
one notable example site that utilizes it.  Currently, Chrome integrates
support, but lower-level integration in WebKit would broadly increase
the potential user base.

There exists a cross-platform (Windows, Linux, Mac OS X) C reference
implementation, https://developers.yubico.com/libu2f-host/, supported by
a manufacturer (Yubico) of U2F-compliant tokens. They also provide a
test server for interactive experimentation
(https://demo.yubico.com/u2f), reference server integration
implementation, and cURL-able test endpoints.

This client (device host) reference implementation depends on: pkg-
config, JSON-C, and HIDAPI for USB communication.

I very strongly desire U2F support both for my own site use, as well as
for token-secured access to Github.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1733002/comments/1


On 2017-02-17T05:23:32+00:00 Ysuzuki-z wrote:

What is the difference from the Web Authentication[1,2]?

[1]: https://github.com/w3c/webauthn
[2]: https://w3c.github.io/webauthn/

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1733002/comments/2


On 2018-01-22T21:28:13+00:00 Jiewen-tan wrote:

(In reply to Yusuke Suzuki from comment #2)
> What is the difference from the Web Authentication[1,2]?
> 
> [1]: https://github.com/w3c/webauthn
> [2]: https://w3c.github.io/webauthn/

WebAuthN is effectively FIDO 2.0. See Bug 181943 for status update
regarding to WebAuthN.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1733002/comments/7


On 2018-05-26T19:28:37+00:00 John+webkit wrote:

Does the work on WebAuthN contain FIDO 1.0 support as well? If not, this
ticket is probably still valid on it's own.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1733002/comments/8


On 2018-10-29T07:20:48+00:00 Dwaite-b wrote:

FWIW, Edge has no intention to support U2F and only support WebAuthn.

The U2F JavaScript API unfortunately doesn't fully document how to get
access to the objects needed to use the MessagePort and u2f interface
API.

U2F supports CTAP1 devices, while WebAuthn supports CTAP1 and CTAP2
devices.

There is an extension for WebAuthn to work with existing U2F
registrations (such as those created via another browser, or the Safari
App Extension) with the new API, so that users can still authenticate
when a site upgrades from using the U2F to WebAuthn javascript
interfaces.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1733002/comments/9


On 2018-10-29T18:06:14+00:00 Jiewen-tan wrote:

(In reply to john+webkit from comment #4)
> Does the work on WebAuthN contain FIDO 1.0 support as well? If not, this
> ticket is probably still valid on it's own.

WebAuthN will support CTAP1/U2F devices.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1733002/comments/10


On 2018-10-29T18:08:50+00:00 Jiewen-tan wrote:

(In reply to David Waite from comment #5)
> FWIW, Edge has no intention to support U2F and only support WebAuthn.
> 
> The U2F JavaScript API unfortunately doesn't fully document how to get
> access to the objects needed to use the MessagePort and u2f interface API.
> 
> U2F supports CTAP1 devices, while WebAuthn supports CTAP1 and CTAP2 devices.
> 
> There is an extension for WebAuthn to work with existing U2F registrations
> (such as those created via another browser, or the Safari App Extension)
> with the new API, so that users can still authenticate when a site upgrades
> from using the U2F to WebAuthn j

[Touch-packages] [Bug 1828124] Re: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor

2019-05-12 Thread Alex Murray
>From a security PoV this is basic security by obscurity and effectively
pointless - they are simply XORing each byte with a fixed value and then
base64 encoding it - since the source code is public anyone can easily
find this out and hence easily decode it - the only way to do this
securely would be to have the DBus peers negotiate a session key and
encrypt it properly using this - so I don't think there is any point
adding this faux-encryption in this case.

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

Title:
  org.gnome.evolution.dataserver.Source completely unveils account
  credentials in plain text while using dbus-monitor

Status in evolution-data-server:
  New
Status in evolution-data-server package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 16.04 LTS
  2. Install Evolution
  3. Set-up Google account with default settings (this will end with e-mail and 
calendar)
  4. Reboot
  5. Open evolution Calendar and/or indicator-datetime
  6. Launch `dbus-monitor`

  Expected results:
  * Evolution does not show account credentials in plain text in `dbus-monitor` 
output

  Actual results:
  * Evolution shows account credentials in plain text in `dbus-monitor` output:

  
  method call time=1557268474.383095 sender=:1.74 -> destination=:1.40 
serial=939 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; 
interface=org.gnome.evolution.dataserver.Source; member=InvokeAuthenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
 ]
  method return time=1557268474.383686 sender=:1.40 -> destination=:1.74 
serial=366 reply_serial=939
  signal time=1557268474.389206 sender=:1.40 -> destination=(null destination) 
serial=367 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
 ]

  signal time=1557268520.956861 sender=:1.40 -> destination=(null destination) 
serial=408 path=/org/gnome/evolution/dataserver/SourceManager/Source_19; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]
  signal time=1557268520.960443 sender=:1.40 -> destination=(null destination) 
serial=409 path=/org/gnome/evolution/dataserver/SourceManager/Source_18; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]
  signal time=1557268520.964374 sender=:1.40 -> destination=(null destination) 
serial=410 path=/org/gnome/evolution/dataserver/SourceManager/Source_20; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]

  -
  This is huge security flaw. The malicious script can parse `dbus-monitor` 
output...
  Not sure about more recent Ubuntu and Evolution versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evolution-data-server-common 3.18.5-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  8 01:40:27 2019
  InstallationDate: Installed on 2018-01-04 (488 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: evolution-data-server
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1828124/+subscriptions

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


[Touch-packages] [Bug 1828725] Re: indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries)

2019-05-12 Thread Norbert
** Attachment added: "indicator-datetime from Ubuntu 19.10 without coloured 
squares"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1828725/+attachment/5263242/+files/ubuntu-19-10.png

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

Title:
  indicator-datetime does not have color squares for different calendars
  and dates from contacts (birthdays & anniversaries)

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu with `indicator-datetime` and `evolution`
  2. Add event to *Personal* calendar (default color)
  3. Add new calendar and name it for example *Work* (red color)
  4. Create contact with two dates - birthday and anniversary (it is pink color)

  Expected results:
  * `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 
LTS (see screenshot - ubuntu-12-04.png)

  Actual results:
  * `indicator-datetime` show for event without color squares in the left of 
them (see screenshot - ubuntu-19-10.png)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun May 12 14:54:43 2019
  InstallationDate: Installed on 2019-04-28 (13 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1828725/+subscriptions

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


[Touch-packages] [Bug 1828725] [NEW] indicator-datetime does not have color squares for different calendars and dates from contacts (birthdays & anniversaries)

2019-05-12 Thread Norbert
Public bug reported:

Steps to reproduce:
1. Install Ubuntu with `indicator-datetime` and `evolution`
2. Add event to *Personal* calendar (default color)
3. Add new calendar and name it for example *Work* (red color)
4. Create contact with two dates - birthday and anniversary (it is pink color)

Expected results:
* `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 LTS 
(see screenshot - ubuntu-12-04.png)

Actual results:
* `indicator-datetime` show for event without color squares in the left of them 
(see screenshot - ubuntu-19-10.png)

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
Uname: Linux 5.0.0-14-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: MATE
Date: Sun May 12 14:54:43 2019
InstallationDate: Installed on 2019-04-28 (13 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426)
SourcePackage: indicator-datetime
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug bionic cosmic disco eoan xenial

** Attachment added: "indicator-datetime from Ubuntu 12.04 LTS with coloured 
squares"
   
https://bugs.launchpad.net/bugs/1828725/+attachment/5263238/+files/ubuntu-12-04.png

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

Title:
  indicator-datetime does not have color squares for different calendars
  and dates from contacts (birthdays & anniversaries)

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu with `indicator-datetime` and `evolution`
  2. Add event to *Personal* calendar (default color)
  3. Add new calendar and name it for example *Work* (red color)
  4. Create contact with two dates - birthday and anniversary (it is pink color)

  Expected results:
  * `indicator-datetime` show four coloured events as it was in Ubuntu 12.04 
LTS (see screenshot - ubuntu-12-04.png)

  Actual results:
  * `indicator-datetime` show for event without color squares in the left of 
them (see screenshot - ubuntu-19-10.png)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: indicator-datetime 15.10+19.10.20190507-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun May 12 14:54:43 2019
  InstallationDate: Installed on 2019-04-28 (13 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan EANIMAL" - Alpha amd64 (20190426)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1828725/+subscriptions

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


[Touch-packages] [Bug 1799265] Re: avahi-daemon high cpu, unusable networking

2019-05-12 Thread Eyal Lotem
A similar bug happened here on 2 different Ubuntu installs once they
upgraded to Ubuntu 18.10.

Another symptom of the bug was periodic addition of IPv6 addresses to
the `ip addr` listing. If you wait a while, the list had thousands of
IPv6 entries in it!

Apparently every time it decided to fetch new IPv6 addresses it also did
a RST on all the IPv4 connections, which is why webpages fail to load a
lot of the time.

Once I completely disabled IPv6 support on my machine via:

/etc/sysctl.d/99-sysctl.conf:net.ipv6.conf.all.disable_ipv6 = 1
/etc/sysctl.d/99-sysctl.conf:net.ipv6.conf.default.disable_ipv6 = 1
/etc/sysctl.d/99-sysctl.conf:net.ipv6.conf.lo.disable_ipv6 = 1

The problem went away.

So I don't know what the exact problem is -- but this narrows it down.

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

Title:
  avahi-daemon high cpu, unusable networking

Status in Avahi:
  New
Status in avahi package in Ubuntu:
  Triaged

Bug description:
  Currently running Kubuntu 18.10, Dell XPS 13 9350

  Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
  consistently hampering network performance and using CPU for long
  periods of time.

  When booting machine from off state, avahi-daemon uses an entire CPU
  at max load for approx 10 minutes. During this time, internet
  connectivity via wifi is essentially unusable. The wifi connection is
  good, but it seems that http transactions are cutoff mid-way so no
  webpage is able to load.

  When waking from sleep, the avahi-daemon causes similar symptoms, but
  with less than 1 full cpu usage, and with somewhat less degraded
  network performance, but still quite unusable.

  I have never had issues with avahi prior to the 18.10 upgrade, so I am
  fairly confident the issue is rooted in that change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: avahi-daemon 0.7-4ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 22 10:00:34 2018
  InstallationDate: Installed on 2017-07-24 (455 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   LD_PRELOAD=
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

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

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


[Touch-packages] [Bug 1828569] Re: Popping sound when audio driver engaged

2019-05-12 Thread Sebastien Bacher
Could you also use the command
$ apport-collect -p alsa-base 1828569
To add the details of you soundcard/driver to the report?

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

Title:
  Popping sound when audio driver engaged

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Fresh install of Disco over the weekend on new hard drive.  Any time a
  sound plays, whether it's from a browser (both Firefox and Chromium),
  Slack, video or MP3 file, sound in VirtualBox OS, etc.  Any sound,
  even an alert sound or even just opening an app that may make a sound
  (e.g. opening a browser page that may have alerts or sounds (like a
  game) makes the same popping sound just when browsing to that page).

  It's preceded by a pop or a click from the speakers, a fast pop-pop
  sound.

  When said audio is finished, about 25% of the time there is another
  audible pop or click.

  I have 18.04.x LTS on another hard drive and when I boot to that
  instance I do not have the pop sound.

  I believe it's probably driver related, but I'm not sure where to
  look.

  Fresh disco install, have performed apt updates, and rebooted several
  times.  Has persisted for several weeks.

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

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


[Touch-packages] [Bug 1828569] Re: Popping sound when audio driver engaged

2019-05-12 Thread Sebastien Bacher
Thank you for your bug report, could you try if adding that option to the 
kernel boot line helps?
snd_hda_intel.power_save=0 
(https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter/19487
 has tip on how to do that if you need directions)

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  Popping sound when audio driver engaged

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Fresh install of Disco over the weekend on new hard drive.  Any time a
  sound plays, whether it's from a browser (both Firefox and Chromium),
  Slack, video or MP3 file, sound in VirtualBox OS, etc.  Any sound,
  even an alert sound or even just opening an app that may make a sound
  (e.g. opening a browser page that may have alerts or sounds (like a
  game) makes the same popping sound just when browsing to that page).

  It's preceded by a pop or a click from the speakers, a fast pop-pop
  sound.

  When said audio is finished, about 25% of the time there is another
  audible pop or click.

  I have 18.04.x LTS on another hard drive and when I boot to that
  instance I do not have the pop sound.

  I believe it's probably driver related, but I'm not sure where to
  look.

  Fresh disco install, have performed apt updates, and rebooted several
  times.  Has persisted for several weeks.

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

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


[Touch-packages] [Bug 1828649] Re: Wayland freeze

2019-05-12 Thread Sebastien Bacher
Thank you for your bug report. Could you add your journalctl log from a
boot that got the issue?

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- Wayland freeze
+ Wayland session freezes

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

Title:
  Wayland session freezes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I switch to wayland the gnome desktop locks up before I see my desktop.
  It doesn't lock up when I have my laptop closed and only one display 
connected.
  When I connect up the second display, it locks up every time.
  I tried deleting my monitors.xml file..  that doesn't make any difference.

  I was able to get it to work by connecting one display via DisplayPort.
  When I connect the second display, via active HDMI to DisplayPort on dock, it 
doesn't work if I select Wayland.  This wire configuration works fine with Xorg.

  Additionally, when I lift my laptop screen, one of my monitors goes
  out and re-enabling it causes another to go off.  Linux kernel is not
  smart enough to drive the 3 displays.  I am able to drive two monitors
  and have my laptop screen open in Windows just fine.

  Of importance is that my DisplayPort to HDMI adaptor is ACTIVE.  If I
  was to use a PASSIVE adaptor, I cannot drive two external displays and
  the laptop display.

  With my laptop screen closed, I was able to drive both displays in
  Wayland just fine in 18.10 so this is a regression.  The GNU/Linux
  kernel has always (as far as I know) been lacking in smarts to drive
  all three displays.

  This work system is has Intel 4000 Integrated video (Lenovo ThinkPad
  laptop).

  Main screen is 2560x1600 via DisplayPort to laptop.
  Secondary screen is 1920x1200 via DisplayPort to laptop dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 10 16:55:27 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2019-03-25 (46 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=7e84182c-37f4-407a-91ca-1b6bbec80a00 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB2WW (2.72 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB2WW(2.72):bd11/15/2018:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.sku: LENOVO_MT_3435
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1828124] Re: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor

2019-05-12 Thread Sebastien Bacher
** Changed in: evolution-data-server (Ubuntu)
   Importance: Undecided => High

** Changed in: evolution-data-server (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  org.gnome.evolution.dataserver.Source completely unveils account
  credentials in plain text while using dbus-monitor

Status in evolution-data-server:
  New
Status in evolution-data-server package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 16.04 LTS
  2. Install Evolution
  3. Set-up Google account with default settings (this will end with e-mail and 
calendar)
  4. Reboot
  5. Open evolution Calendar and/or indicator-datetime
  6. Launch `dbus-monitor`

  Expected results:
  * Evolution does not show account credentials in plain text in `dbus-monitor` 
output

  Actual results:
  * Evolution shows account credentials in plain text in `dbus-monitor` output:

  
  method call time=1557268474.383095 sender=:1.74 -> destination=:1.40 
serial=939 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; 
interface=org.gnome.evolution.dataserver.Source; member=InvokeAuthenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
 ]
  method return time=1557268474.383686 sender=:1.40 -> destination=:1.74 
serial=366 reply_serial=939
  signal time=1557268474.389206 sender=:1.40 -> destination=(null destination) 
serial=367 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
 ]

  signal time=1557268520.956861 sender=:1.40 -> destination=(null destination) 
serial=408 path=/org/gnome/evolution/dataserver/SourceManager/Source_19; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]
  signal time=1557268520.960443 sender=:1.40 -> destination=(null destination) 
serial=409 path=/org/gnome/evolution/dataserver/SourceManager/Source_18; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]
  signal time=1557268520.964374 sender=:1.40 -> destination=(null destination) 
serial=410 path=/org/gnome/evolution/dataserver/SourceManager/Source_20; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]

  -
  This is huge security flaw. The malicious script can parse `dbus-monitor` 
output...
  Not sure about more recent Ubuntu and Evolution versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evolution-data-server-common 3.18.5-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  8 01:40:27 2019
  InstallationDate: Installed on 2018-01-04 (488 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: evolution-data-server
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1828124/+subscriptions

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


[Touch-packages] [Bug 1828682] Re: Utility applications are not placed in the Utilities folder

2019-05-12 Thread Sebastien Bacher
It would be good to have design input on that, I'm not convinced that
things like the system monitor, language-selector or usb creater should
be moved outside the main list. That folder split seems a bit random,
maybe it should be removed?

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

Title:
  Utility applications are not placed in the Utilities folder

Status in gnome-power-manager package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  New
Status in gnome-system-monitor package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New
Status in seahorse package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in usb-creator package in Ubuntu:
  New

Bug description:
  Some utility applications used in Ubuntu are not placed in the
  Utilities folder. These applications are:

  Language Support
  Software & Updates
  Livepatch
  Software Updater
  Power Statistics
  Startup Applications
  Startup Disk Creator
  Passwords and Keys
  Input Method

  Please, consider moving them to the Utilities folder.

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

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


[Touch-packages] [Bug 1733002] Re: Google Online Account Two Factor with hardware key fails immediately

2019-05-12 Thread Sebastien Bacher
GNOME upstream pointed out webkitgtk as the place where the works needs
to happen and to https://bugs.webkit.org/show_bug.cgi?id=143491 and a
fix was recently commited, hopefully it means it's going to be resolved
next cycle

** Bug watch added: bugs.webkit.org/ #143491
   https://bugs.webkit.org/show_bug.cgi?id=143491

** Also affects: webkit via
   https://bugs.webkit.org/show_bug.cgi?id=143491
   Importance: Unknown
   Status: Unknown

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

Title:
  Google Online Account Two Factor with hardware key fails immediately

Status in gnome-online-accounts:
  Unknown
Status in Webkit:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  The hardware key authentication two factor fails immediately with a
  web based retry dialogue when connecting a Google account to the
  online accounts in settings using a hardware key second factor.

  Steps to reproduce:
  1. Set Google Account to default to a hardware security key like a Yubikey or 
other FIDO standard key after having two factor authentication enabled on your 
Google Account.
  2. Open Online accounts
  3. Add a Google Account
  4. Enter google email address
  5. Enter google password
  6. (this is the login flow of two factor, if default is the hardware key the 
error should appear).

  Work around:
  Choose use another method to authenticate: enter the authentication code and 
you will proceed.

  Expectations were:
  The ability to use the hardware key to authenticate as the second factor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 17 16:01:11 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbo

2019-05-12 Thread Sebastian Ramacher
** Changed in: libva (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  i965_drv_video.so doesn't load any more if a Wayland server is present
  [failed to resolve wl_drm_interface(): /lib/x86_64-linux-
  gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface]

Status in Libva:
  Fix Released
Status in intel-vaapi-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released

Bug description:
  If a Wayland server is present (anywhere on the system including even
  the gdm3 login screen) then i965_drv_video.so fails to initialize:

  $ vainfo 
  libva info: VA-API version 1.3.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_2
  error: failed to resolve wl_drm_interface(): 
/lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit

  $ mpv bbb_sunflower_2160p_60fps_normal.mp4 
  Playing: bbb_sunflower_2160p_60fps_normal.mp4
   (+) Video --vid=1 (*) (h264 3840x2160 60.000fps)
   (+) Audio --aid=1 (*) (mp3 2ch 48000Hz)
   Audio --aid=2 (*) (ac3 6ch 48000Hz)
  File tags:
   Artist: Blender Foundation 2008, Janus Bager Kristensen 2013
   Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net
   Composer: Sacha Goedegebure
   Genre: Animation
   Title: Big Buck Bunny, Sunflower version
  error: failed to resolve wl_drm_interface(): 
/lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface
  [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed

  Meanwhile, it continues to work after you have logged into a Xorg
  session.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: i965-va-driver 2.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  Date: Thu Jan 24 16:54:21 2019
  InstallationDate: Installed on 2018-12-04 (51 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1828718] [NEW] [HP Notebook, Realtek ALC3227, Speaker, Internal] Playback problem.

2019-05-12 Thread thanveer ali
Public bug reported:

sound is very low for videos both hevc and h264 . even with
amplification.  and fine in youtube. overall sound is very much less
than when i was in windows 10

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  thanveer   1898 F pulseaudio
 /dev/snd/controlC0:  thanveer   1898 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun May 12 14:45:17 2019
InstallationDate: Installed on 2019-05-12 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [HP Notebook, Realtek ALC3227, Speaker, Internal] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.33
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81EF
dmi.board.vendor: HP
dmi.board.version: 63.47
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd08/29/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EF:rvr63.47:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Notebook
dmi.product.sku: W6T33PA#ACJ
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug disco

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

Title:
  [HP Notebook, Realtek ALC3227, Speaker, Internal] Playback problem.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  sound is very low for videos both hevc and h264 . even with
  amplification.  and fine in youtube. overall sound is very much less
  than when i was in windows 10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  thanveer   1898 F pulseaudio
   /dev/snd/controlC0:  thanveer   1898 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 12 14:45:17 2019
  InstallationDate: Installed on 2019-05-12 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [HP Notebook, Realtek ALC3227, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EF
  dmi.board.vendor: HP
  dmi.board.version: 63.47
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd08/29/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EF:rvr63.47:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Notebook
  dmi.product.sku: W6T33PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Touch-packages] [Bug 1828713] [NEW] [Inspiron 3650, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] No sound at all

2019-05-12 Thread ludo33200
Public bug reported:

This is an ubuntu 19.04 fresh [re]install
Previous installation was an upgrade 18.04 LTS (at least) -> 18.10 -> 19.04 and 
the sound worked

Sound is expected on HDMI screen Dell S2415H
Sound level on screen is set to max

In system settings>sound , every sound entry is set to mute (speaker slashed)
On output settings we can see (fresh install, english translation below)

Sortie
Périphériques de sortie : Sortie fictive- (<-- option sélectionnée / seule 
option disponible)

[translation]
Output
Output peripheral : Fictive output - (<-- selected option / only available 
option)

Button "Test" will give no sound (seems normal because of Sortie fictive
?)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ludovic1955 F pulseaudio
 /dev/snd/controlC0:  ludovic1955 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun May 12 09:54:36 2019
InstallationDate: Installed on 2019-05-10 (1 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm1550 F pulseaudio
  ludovic1955 F pulseaudio
 /dev/snd/controlC0:  gdm1550 F pulseaudio
  ludovic1955 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [Inspiron 3650, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 3.7.0
dmi.board.name: 0C2XKD
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr3.7.0:bd07/13/2018:svnDellInc.:pnInspiron3650:pvrX00:rvnDellInc.:rn0C2XKD:rvrA01:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3650
dmi.product.sku: 06F7
dmi.product.version: X00
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug disco

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

Title:
  [Inspiron 3650, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This is an ubuntu 19.04 fresh [re]install
  Previous installation was an upgrade 18.04 LTS (at least) -> 18.10 -> 19.04 
and the sound worked

  Sound is expected on HDMI screen Dell S2415H
  Sound level on screen is set to max

  In system settings>sound , every sound entry is set to mute (speaker slashed)
  On output settings we can see (fresh install, english translation below)

  Sortie
  Périphériques de sortie : Sortie fictive- (<-- option sélectionnée / seule 
option disponible)

  [translation]
  Output
  Output peripheral : Fictive output - (<-- selected option / only available 
option)

  Button "Test" will give no sound (seems normal because of Sortie
  fictive ?)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ludovic1955 F pulseaudio
   /dev/snd/controlC0:  ludovic1955 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 12 09:54:36 2019
  InstallationDate: Installed on 2019-05-10 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1550 F pulseaudio
ludovic1955 F pulseaudio
   /dev/snd/controlC0:  gdm1550 F pulseaudio
ludovic1955 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at a

[Touch-packages] [Bug 1828713] Re: [Inspiron 3650, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] No sound at all

2019-05-12 Thread ludo33200
In system settings>sound , every sound entry is set to mute (speaker slashed)
... and this can't be changed

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

Title:
  [Inspiron 3650, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This is an ubuntu 19.04 fresh [re]install
  Previous installation was an upgrade 18.04 LTS (at least) -> 18.10 -> 19.04 
and the sound worked

  Sound is expected on HDMI screen Dell S2415H
  Sound level on screen is set to max

  In system settings>sound , every sound entry is set to mute (speaker slashed)
  On output settings we can see (fresh install, english translation below)

  Sortie
  Périphériques de sortie : Sortie fictive- (<-- option sélectionnée / seule 
option disponible)

  [translation]
  Output
  Output peripheral : Fictive output - (<-- selected option / only available 
option)

  Button "Test" will give no sound (seems normal because of Sortie
  fictive ?)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ludovic1955 F pulseaudio
   /dev/snd/controlC0:  ludovic1955 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 12 09:54:36 2019
  InstallationDate: Installed on 2019-05-10 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1550 F pulseaudio
ludovic1955 F pulseaudio
   /dev/snd/controlC0:  gdm1550 F pulseaudio
ludovic1955 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Inspiron 3650, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.7.0
  dmi.board.name: 0C2XKD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.7.0:bd07/13/2018:svnDellInc.:pnInspiron3650:pvrX00:rvnDellInc.:rn0C2XKD:rvrA01:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3650
  dmi.product.sku: 06F7
  dmi.product.version: X00
  dmi.sys.vendor: Dell Inc.

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

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