[Touch-packages] [Bug 1801538] Re: no sound after upgrading to ubuntu 18.10 from 18.04

2019-03-30 Thread Dennis Shimer
*** This bug is a duplicate of bug 1793640 ***
https://bugs.launchpad.net/bugs/1793640

Same thing for me with a Lenovo L520 and Intel chipset.  Some relevant
information just in case

sudo lshw -c sound
  *-multimedia  
   description: Audio device
   product: 6 Series/C200 Series Chipset Family High Definition Audio 
Controller
   vendor: Intel Corporation
   physical id: 1b
   bus info: pci@:00:1b.0
   version: 04
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list
   configuration: driver=snd_hda_intel latency=0
   resources: irq:28 memory:f090-f0903fff
  *-usb:1
   description: Video
   product: Integrated Camera
   vendor: Chicony Electronics Co., Ltd.
   physical id: 4
   bus info: usb@2:1.4
   version: 2.22
   capabilities: usb-2.00
   configuration: driver=uvcvideo maxpower=200mA speed=480Mbit/s
---
lspci -nnk | grep -A2 Audio
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset 
Family High Definition Audio Controller [8086:1c20] (rev 04)
Subsystem: Lenovo 6 Series/C200 Series Chipset Family High Definition 
Audio Controller [17aa:21dd]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
---
lsmod | grep snd_hda_intel
snd_hda_intel  40960  3
snd_hda_codec 126976  4 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core   81920  5 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_pcm98304  5 
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
snd81920  17 
snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,thinkpad_acpi,snd_pcm,snd_rawmidi
d

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

Title:
  no sound after upgrading to ubuntu 18.10 from 18.04

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.10 does not recognize sound devices. After upgrading there
  is only a dummy device known. All others are gone. In tune there is no
  sound output to nowhere.

  It does not mater it headphones are plugged or not while booting. It
  does not matter if any usb-sound device is plugged or not. The only
  device show for output in mixer is "Dummy device".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity   8931 F timidity
   /dev/snd/pcmC0D0p:   timidity   8931 F...m timidity
   /dev/snd/seq:timidity   8931 F timidity
   /dev/snd/timer:  timidity   8931 f timidity
  Date: Sat Nov  3 17:25:55 2018
  InstallationDate: Installed on 2011-10-19 (2571 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)
  dmi.bios.date: 10/21/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TravelMate P643-M
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: TravelMate P643-M
  dmi.product.name: TravelMate P643-M
  dmi.product.sku: TravelMate P643-M_0681_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1633319] Re: memory leak in indicator-datetime

2017-01-26 Thread Dennis Shimer
I completely removed my google account and it still didn't help. Is
there any way to set this service to not start at all?

At this point the only thing I have found to even make my laptop usable
is 'killall unity-panel-service'

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+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 1652789] Re: indicator-datetime-service using high volumes of ram/memory

2017-01-26 Thread Dennis Shimer
I completely removed my google account and it still didn't help.  Is
there any way to set this service to not start at all?  At this point
the only thing I have found to even make my laptop usable is 'killall
unity-panel-service'

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

Title:
  indicator-datetime-service using high volumes of ram/memory

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I have noticed every time my computer boots into Ubuntu, it freezes up
  with the mouse lagging and then unfreezes. I notice the SSD making
  huge amounts of read/writes (which I imagine is into virtual
  memory/swap space). I have to leave the computer for 15 mins or so
  before coming back to it.

  I noticed `indicator-datetime-service` was using a lot of RAM in
  `System Monitor`. So I killed it, and it comes back again each time I
  kill the process. So I clicked 'Stop' with has seemed to have
  temporary fixed the problem. Obviously now the correct time is not
  displayed on the task bar.

  indicator-datetime:
    Installed: 15.10+16.10.20160820.1-0ubuntu1
    Candidate: 15.10+16.10.20160820.1-0ubuntu1
    Version table:
   *** 15.10+16.10.20160820.1-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  Description:Ubuntu 16.10
  Release:16.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1652789/+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 1445630] Re: Can't connect to Wifi network secured with long PSK

2016-08-05 Thread Dennis Shimer
I had the exact same problem with a much less complex password that was
comprised of 8 mixed case characters followed by and underscore which
was followed by 4 numbers

Cccc_ (just the format, not the password)

Copying and pasting worked great and it connected first try.
Nexus 4 15.04 OTA-12

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

Title:
  Can't connect to Wifi network secured with long PSK

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Device: BQ Aquaris E5.4 Ubuntu Edition

  I just got this device and wanted to connect to my WPA2 WiFi network
  which happens to have a 54 characters-long PSK. However, after
  entering my password (which naturally takes a little while) and
  clicking on "connect", it just simply returns me to the overview of
  WiFi networks near me. No error message.

  The following askubuntu.com questions appear to be related to this problem:
  http://askubuntu.com/questions/597333/get-wifi-password-into-ubuntu-touch
  
http://askubuntu.com/questions/306734/unable-to-connect-to-secured-wi-fi-from-nexus-7-running-ubuntu-touch-13-04

  I have enabled developer mode and edited the network manager file in
  /etc/NetworkManager/system-connections/ using adb shell. After that, I
  was able to connect to my network.

  Steps to reproduce:
  1. Set up a WPA2 network and give it a long password
  2. Click on your SSID on the list
  3. Enter your password
  4. Click "Connect".

  Expected result:
  Connected to the WiFi network

  Actual result:
  You see the list again and no indications that you are connected to the 
network. You aren't connected to the network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445630/+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