[Touch-packages] [Bug 566381] Re: Lag when using module-loopback

2024-01-22 Thread I. T. Pohjalainen
Still exists in Ubuntu 22.04.3 LTS. Measured exactly 148 ms delay with
wired headphones and an usb microphone.

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

Title:
  Lag when using module-loopback

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  Using
  pactl load-module module-loopback
  I can route the mic input through output. However, the audio that comes out 
is about half a second behind the audio coming in. This is okay for some 
things, but for others, like musical instruments, game consoles, etc., the lag 
makes it pretty much unusable for these uses.
  Back in alsa this used to work fine without lag.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic x86_64
  NonfreeKernelModules: nls_iso8859_1 nls_cp437 btrfs zlib_deflate crc32c 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs 
reiserfs pata_jmicron acpiphp michael_mic arc4 hidp rfcomm binfmt_misc sco 
bridge stp bnep l2cap vboxnetadp vboxnetflt dm_crypt snd_hda_codec_idt 
snd_hda_codec_intelhdmi snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss 
snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi vboxdrv 
snd_rawmidi joydev snd_seq_midi_event lp snd_seq snd_timer snd_seq_device 
lib80211_crypt_tkip snd parport soundcore wl dell_wmi btusb psmouse dell_laptop 
dcdbas ricoh_mmc snd_page_alloc lib80211 sdhci_pci sdhci led_class serio_raw 
bluetooth dm_raid45 xor fbcon tileblit font bitblit softcursor vga16fb vgastate 
usbhid hid i915 drm_kms_helper ohci1394 drm i2c_algo_bit ieee1394 sky2 
intel_agp ahci video output
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matthew   10508 F pulseaudio
   /dev/snd/pcmC0D0c:   matthew   10508 F...m pulseaudio
   /dev/snd/pcmC0D0p:   matthew   10508 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 21'
 Mixer name : 'SigmaTel STAC9228'
 Components : 'HDA:14f12c06,14f1000f,0010 
HDA:10951392,1028022f,0010 HDA:83847616,1028022f,00100402'
 Controls  : 23
 Simple ctrls  : 12
  Date: Sun Apr 18 21:42:33 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 03/10/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0U990C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd03/10/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/566381/+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 1952934] Re: Intel HDA Sound Card not detected on Ubuntu 20.04

2021-12-01 Thread I-Cat
your media dir is incorrect
media.filename = "/usr/share//sounds/Yaru/stereo/dialog-question.oga

** Changed in: alsa-driver (Ubuntu)
 Assignee: (unassigned) => I-Cat (i-cat)

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

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

Title:
  Intel HDA Sound Card not detected on Ubuntu 20.04

Status in alsa-driver package in Ubuntu:
  Opinion

Bug description:
  the intel sound card is not detected and only "dummy output" is
  available

  I've tested on kernel 5.15 but it s the same on default 5.11 kernel

  Also tried without success :

  - Booted the 5.4 
  - added snd_intel_dspcfg.dsp_driver=1 boot param

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.15.6-051506-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem2217 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Wed Dec  1 17:35:25 2021
  InstallationDate: Installed on 2021-11-19 (12 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2021
  dmi.bios.release: 85.176
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: TN1V5.03_PCS
  dmi.board.asset.tag: Board Asset Tag
  dmi.board.name: WN1
  dmi.board.vendor: IP3
  dmi.board.version: V20
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PCSpecialist
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M:
  dmi.product.family: Notebook
  dmi.product.name: TN1-156M
  dmi.product.sku: TN1-156M
  dmi.product.version: V10
  dmi.sys.vendor: PCSpecialist
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+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 1949909] Re: Bluetooth crashes on resume from suspend

2021-11-04 Thread I-Cat
sudo apt install bluz
snap install bluz

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

Title:
  Bluetooth crashes on resume from suspend

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Crash on resume from suspend. The following messages appear and the
  computer stops responding:

  ```
  [   26.227264] Bluetooth: hci0: Reading supported features failed (-16)
  [   26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask 
failed (-95)
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  4 22:50:23 2021
  InstallationDate: Installed on 2021-09-16 (49 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949909/+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 1949909] Re: Bluetooth crashes on resume from suspend

2021-11-04 Thread I-Cat
uhh, wow The cpu info dont match and proc info let me look at the
package. This looks more like a driver issue. I Have seen this before.

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

Title:
  Bluetooth crashes on resume from suspend

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Crash on resume from suspend. The following messages appear and the
  computer stops responding:

  ```
  [   26.227264] Bluetooth: hci0: Reading supported features failed (-16)
  [   26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask 
failed (-95)
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  4 22:50:23 2021
  InstallationDate: Installed on 2021-09-16 (49 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949909/+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 1949909] Re: Bluetooth crashes on resume from suspend

2021-11-04 Thread I-Cat
** Changed in: bluez (Ubuntu)
   Status: In Progress => Incomplete

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

Title:
  Bluetooth crashes on resume from suspend

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Crash on resume from suspend. The following messages appear and the
  computer stops responding:

  ```
  [   26.227264] Bluetooth: hci0: Reading supported features failed (-16)
  [   26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask 
failed (-95)
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  4 22:50:23 2021
  InstallationDate: Installed on 2021-09-16 (49 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949909/+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 1949909] Re: bluetooth crashes on resume from suspend

2021-11-04 Thread I-Cat
** Tags added: bluz

** Changed in: bluez (Ubuntu)
   Status: New => In Progress

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => I-Cat (i-cat)

** Summary changed:

- bluetooth crashes on resume from suspend
+ Bluetooth crashes on resume from suspend

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

Title:
  Bluetooth crashes on resume from suspend

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Crash on resume from suspend. The following messages appear and the
  computer stops responding:

  ```
  [   26.227264] Bluetooth: hci0: Reading supported features failed (-16)
  [   26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask 
failed (-95)
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  4 22:50:23 2021
  InstallationDate: Installed on 2021-09-16 (49 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949909/+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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

2021-08-29 Thread I-Cat
It is the Blue-Tooth Driver.
I Got This Too on my 
Acer Aspire F5-573 series "Laptop"
There is a sticker that says "Intel i-5 core" Know amd is a possablity ?
I Do not think My Processor Is an amd?
Also It set my Screen Res to like 1377x768 (Its a 6k screen) 17" screen
When I was On Windows "Yes I had to switch off Windows Because my Windows 11 os 
failed"
It was installed When I installed viurtalbox or kodi.
It is like a nightmare.
I lost function of my usb 1.0 driver.
It installs a pnp driver that do not exsist.
The pnp Driver is a printer driver that is pointing to your desktop. 

I Think This Is a Virus That is effecting other systems like My Self.
Thanks -- I-Cat

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

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1928393/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2021-06-20 Thread I And
@Hui Wang

Any chance to get working verbs for Yoga C930? )
I have managed to run Win10 into QEMU with working bass speakers and got the 
RtHDDump.txt
Maybe it will be useful..

** Attachment added: "RtHDDump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+attachment/5505829/+files/RtHDDump.txt

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  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:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2021-05-31 Thread I And
@Hui Wang
I've tested. Verbs from #17 have no effect, verbs from set-verbs-c930.sh 
completely disable all speakers, no sound.

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  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:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2021-05-30 Thread I And
@Hui Wang
Eventually, i have applied your patch to the kernel.
I have DAC1 and DAC2 now and somehow sound is better now than before, but rear 
speakers are not working.
If i change the level of DAC1 - the sound volume changes, but the changing of 
DAC2 level does nothing.

Update:
The alsa-info is here
http://alsa-project.org/db/?f=08f7b48d840592556650cb156e51831780127958

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  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:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2021-05-24 Thread I And
@Hui Wang,
the alsa-info.txt for Yoga C930 is here
http://alsa-project.org/db/?f=1ffb1551a46965865ee272cef105769e879397c7

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  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:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2021-05-21 Thread I And
@Hui Wang

if you will have time to make the same script for Lenovo C930 i'll be
glad to help with testing

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  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:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1866347] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_ad

2020-05-07 Thread Kirill I.
workaround which worked for me:
cd /tmp
git clone https://git.launchpad.net/ubuntu/+source/apport
sudo cp  apport/apport/report.py  /usr/lib/python3/dist-packages/apport/

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

Title:
  /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport
  /whoopsie-upload-
  
all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_address_to_offset:_build_proc_maps_cache

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu17, the problem page at 
https://errors.ubuntu.com/problem/5cc81a1cde2a921ad2adcc00e2f8d13f2c9f76e8 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866347/+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 1866347] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_ad

2020-05-07 Thread Kirill I.
How can I find 2.20.11-0ubuntu19 ?

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

Title:
  /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport
  /whoopsie-upload-
  
all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_address_to_offset:_build_proc_maps_cache

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu17, the problem page at 
https://errors.ubuntu.com/problem/5cc81a1cde2a921ad2adcc00e2f8d13f2c9f76e8 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866347/+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 1866347] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_ad

2020-05-07 Thread Kirill I.
Installed apport 2.20.11-0ubuntu8.8 in bionic, still same problem.

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

Title:
  /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport
  /whoopsie-upload-
  
all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_address_to_offset:_build_proc_maps_cache

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu17, the problem page at 
https://errors.ubuntu.com/problem/5cc81a1cde2a921ad2adcc00e2f8d13f2c9f76e8 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866347/+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 1866347] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_ad

2020-05-07 Thread Kirill I.
** Tags added: bionic

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

Title:
  /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport
  /whoopsie-upload-
  
all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_address_to_offset:_build_proc_maps_cache

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu17, the problem page at 
https://errors.ubuntu.com/problem/5cc81a1cde2a921ad2adcc00e2f8d13f2c9f76e8 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866347/+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 1866347] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_ad

2020-05-07 Thread Kirill I.
Can anybody advise any workaround for bionic with apport 2.20.9-ubuntu7.14 ?
For example, if I create empty maps file, can it hepl? If yes, what exact it's 
location?
When approximately package update for bionic may apper?
Thanks in advance.

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

Title:
  /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport
  /whoopsie-upload-
  
all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_address_to_offset:_build_proc_maps_cache

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu17, the problem page at 
https://errors.ubuntu.com/problem/5cc81a1cde2a921ad2adcc00e2f8d13f2c9f76e8 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

2020-02-23 Thread D-i-j
Can be closed now.

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

Title:
  gzip in Ubuntu Eoan results in Exec format error on WSL1

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in gzip package in Ubuntu:
  Fix Released
Status in binutils source package in Eoan:
  Fix Released
Status in gzip source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * Running gzip on WSL1 results in the following error:
     $ gzip
     -bash: /bin/gzip: cannot execute binary file: Exec format error
   * The error occurs frequently in package updates and makes gzip inoperable 
on WSL1
   * The problem is caused by PT_LOAD offset pointing past the end of file and 
the fix is fixing strip to not generate such ELF files and recompiling gzip 
with the fixed strip.

  [Test Case]

   * Check the gzip binary for wrong offset:
    $ FILE=/usr/bin/gzip; readelf -W --program-headers $FILE | awk -v 
size=$(stat -c %s $FILE) '/^  LOAD/ {if (strtonum($2) > size) {print "wrong 
offset ("$2" ("strtonum($2)") points past EOF:" size; exit 1;}}'

  [ Regression Potential ]

   * The binutils fix could cause binutils to generate invalid ELF files. The 
fix is very small and isolated and has been tested and accepted by upstream, 
which makes such problems unlikely.
   * Bugs in the toolchain in general can make the rebuilt gzip show new 
errors, but this generally applies to many SRUs and security updates. The 
testing period in proposed should mitigate this risk.

  [Other Info]

   * Binutils 2.33.1-6ubuntu1.1 was accidentally built in -proposed
  instead of in a PPA. I've rebuilt it in https://launchpad.net/~ci-
  train-ppa-service/+archive/ubuntu/3878 for the -security pocket as
  2.33-2ubuntu1.2.

  [Originial Bug Text]

  Summary:

  Running gzip on WSL1 results in the following error:

  $ gzip
  -bash: /bin/gzip: cannot execute binary file: Exec format error

  What I expect to happen:

  gzip executes correctly on WSL1.

  What happens instead:

  gzip fails with an Exec format error.

  Notes:

  I suspect a change in how gzip is being built for Eoan is causing
  issues with ELF parsing on the WSL1 translation layer. For example:

  On Disco with gzip 1.9-3:

  $ file /bin/gzip
  /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 
3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped

  On Eoan with gzip 1.10-0ubuntu3:

  $ file /bin/gzip
  /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, 
BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, 
stripped

  Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do
  not believe this is an issue in 1.10 because this error does not occur
  when building gzip from GNU project source on Ubuntu Eoan.

  Justifications:

  WSL1 will need to be patched in future Windows builds for this change
  in ELF. However that patch will likely not be backported to older
  builds of Windows, including Windows Enterprise/Server 2019.

  To ensure Eoan can run on current and older builds of Windows Ubuntu
  should consider looking at how it's building gzip and see if it can be
  made to 'play nice' until WSL1 can be updated.

  This was originally reported here:
  https://github.com/microsoft/WSL/issues/4461

  Details:

  Description:Ubuntu Eoan Ermine (development branch)
  Release:19.10

  gzip:
    Installed: 1.10-0ubuntu3
    Candidate: 1.10-0ubuntu3
    Version table:
   *** 1.10-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1843479/+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 1811531]

2019-01-25 Thread Meissner-i
released

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

Title:
  remote execution vulnerability

Status in zeromq3 package in Ubuntu:
  Fix Released
Status in zeromq3 package in Debian:
  Fix Released
Status in zeromq package in Suse:
  Fix Released

Bug description:
  Dear Maintainer,

  A remote execution vulnerability has been reported in zeromq. Full
  details can be found on the upstream issue tracker [1].

  The issue is fixed in upstream version v4.3.1, just released, or with
  the attached patch which is targeted for v4.2.5 (bionic and cosmic).

  The latest version will hopefully arrive in disco via debian unstable
  soon, but I would recommend patching older releases.

  As mentioned in the upstream tracker and the changelog, the issue can
  be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as
  I am aware no CVEs have been assigned nor have been requested as of
  now.

  [1] https://github.com/zeromq/libzmq/issues/3351

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1810388] [NEW] syslog filled with drm messages 40 times per second

2019-01-03 Thread I
Public bug reported:

Hi all,

I don't really know when it exactly began.
>From /var/log/syslog :
Jan  3 09:42:42 localhost kernel: [32659.271016] [drm:drm_mode_addfb2 [drm]] 
[FB:74]
Jan  3 09:42:42 localhost kernel: [32659.300800] [drm:drm_mode_addfb2 [drm]] 
[FB:89]

There are similar bugs that have been already noticed, but none of them
helped me.

Changing desktop environment to a non-gnome desktop stops messages.

My environment (export cmd) :
declare -x XDG_CONFIG_DIRS="/etc/xdg/xdg-ubuntu:/etc/xdg"
declare -x XDG_CURRENT_DESKTOP="ubuntu:GNOME"
declare -x 
XDG_DATA_DIRS="/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop"
declare -x XDG_GREETER_DATA_DIR="/var/lib/lightdm-data/userprofile"
declare -x XDG_MENU_PREFIX="gnome-"
declare -x XDG_RUNTIME_DIR="/run/user/1000"
declare -x XDG_SEAT="seat0"
declare -x XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0"
declare -x XDG_SESSION_DESKTOP="ubuntu"
declare -x XDG_SESSION_ID="c2"
declare -x XDG_SESSION_PATH="/org/freedesktop/DisplayManager/Session0"
declare -x XDG_SESSION_TYPE="x11"
declare -x XDG_VTNR="7"

My kernel : 4.15.0-43-generic
Ubuntu 18.04.01 LTS
Graphic : Intel Haswell Mobile

Any help is appreciated
Thanks

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Jan  3 09:38:35 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.18, 4.15.0-42-generic, x86_64: installed
 virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed
 virtualbox, 5.2.18, 4.19.0-041900-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:060a]
InstallationDate: Installed on 2016-12-20 (743 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. XPS13 9333
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=19d7298f-74c8-4a78-9f17-88b9f04bbc3a ro net.ifnames=0 biosdevname=0 
acpi=force plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0GFTRT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/31/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.family: Shark Bay System
dmi.product.name: XPS13 9333
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic third-party-packages ubuntu

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

Title:
  syslog filled with drm messages 40 times per second

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi all,

  I don't really know when it exactly began.
  From /var/log/syslog :
  Jan  3 09:42:42 localhost kernel: [32659.271016] [drm:drm_mode_addfb2 [drm]] 
[FB:74]
  Jan  3 09:42:42 localhost kernel: [32659.300800] [drm:drm_mode_addfb2 [drm]] 
[FB:89]

  There are similar bugs that have been already noticed, but none of
  them helped me.

  Changing desktop environment to a non-gnome desktop stops messages.

  My environment (export cmd) :
  declare -x XDG_CONFIG_DIRS="/etc/xdg/xdg-ubuntu:/etc/xdg"
  declare -x XDG_CURRENT_DESKTOP="ubuntu:GNOME"
  declare -x 
XDG_DATA_DIRS="/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop"
  declare -x XDG_GREETER_DATA_DIR="/var/lib/lightd

[Touch-packages] [Bug 1726075] Re: [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal] No sound at all

2018-12-29 Thread M I
Same issue, HP Pavilion 15-cc178cl.

Tried:
- checking that speakers aren't muted in alsamixer & pavucontrol
- renaming /etc/modprobe.d/alsa-base.conf
- model={generic,auto,hp} in /etc/modprobe.d/alsa-base.conf
- adding these lines to ~/.config/pulse/default.pa: 
https://askubuntu.com/a/1068198 (this caused pulse to fail to start)
- remapping each output pin to "Internal Speakers" in hdajackretask

Have not tried:
- uninstalling and reinstalling alsa and pulse (this appears to want to 
uninstall ubuntu-desktop--is that expected?)

alsa-info: http://www.alsa-
project.org/db/?f=50bc75eae4b64a7d838f66b581e79cf696920eeb

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

Title:
  [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal]
  No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I cannot hear anything without headphone, the speaker don't work at
  all, even though after i set the speaker volume bar in the alsamixer
  panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  remaincool   1862 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 23 00:57:26 2017
  InstallationDate: Installed on 2017-07-06 (108 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: 内置音频 - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  remaincool   1862 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 836B
  dmi.board.vendor: HP
  dmi.board.version: 46.20
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.09:bd06/02/2017:svnHP:pnHPPavilionPowerLaptop15-cb0xx:pvrType1ProductConfigId:rvnHP:rn836B:rvr46.20:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Power Laptop 15-cb0xx
  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/1726075/+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 1793555] Re: networkd tears down bridge ip address when the last device is pulled out from the bridge

2018-11-29 Thread Scati Labs I+D
This issue has been fixed upstream:
https://github.com/systemd/systemd/pull/10597

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

Title:
  networkd tears down bridge ip address when the last device is pulled
  out from the bridge

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 18.04.1 LTS (systemd 237) pulling out the last device out of
  the bridge removes the bridge ip address.

  given the following config:

  # cat /etc/systemd/network/vmbr0.netdev
  [NetDev]
  Name=vmbr0
  Kind=bridge

  [Bridge]
  HelloTimeSec=0
  ForwardDelaySec=0
  STP=no

  # cat /etc/systemd/network/vmbr0.network
  [Match]
  Name=vmbr0

  [Network]
  Address=10.10.0.1/16
  ConfigureWithoutCarrier=yes
  DHCP=no
  IPForward=yes
  IPv6AcceptRA=no
  LinkLocalAddressing=no

  networkd would bring up vmbr0 with 10.10.0.1/16 on system boot despite
  it not having any devices, allowing services to bind to 10.10.0.1.

  However, if you add a device and then remove it (e.g. by starting and
  then stopping a virtual machine connected to the bridge), networkd
  would tear down the interface:

  3: vmbr0:  mtu 1500 qdisc noqueue state 
DOWN group default qlen 1000
  link/ether 16:19:4c:7f:e8:c4 brd ff:ff:ff:ff:ff:ff

  thus making any service listening on 10.10.0.1 inaccessible.

  previously on Xenial the bridge would stay intact.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1793555/+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 1787867] Re: Ubuntu 18.04 LTS bluetooth left discoverable

2018-09-13 Thread Peter I. Linkp
Can confirm this bug. After activating Bluetooth via Setting menu in
Ubuntu 18.04.1 the computer stay in a permanent bluetooth discoverable
mode and is connectable by external bluetooth devices until the next
system reboot.

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

Title:
  Ubuntu 18.04 LTS bluetooth left discoverable

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays
  discoverable which opens up unnecessary vulnerability surface. There
  should be a separate UI switch for discoverability with auto timeout.
  Leaving bluetooth on (using a Bluetooth mouse) should not leave the
  computer always discoverable.

  Current behavior does not match documentation
  https://help.ubuntu.com/stable/ubuntu-help/bluetooth-
  visibility.html.en, even without Bluetooth panel open, the computer is
  still discoverable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+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 1768232] Re: [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while booting after installing

2018-06-06 Thread d a i s y
** Changed in: xorg (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while
  booting after installing

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  My system stuck at ubuntu logo while booting. This issue occurred only
  after installing it, not when I choose 'Try without Installing'. This
  doesn't happen in 16.04.4.

  xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
     1024x768  76.00*

  Output of sudo lshw -c display

  *-display UNCLAIMED
     description: VGA compatible controller
     product: 82945G/GZ Integrated Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 02
     width: 32 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d

  WORKAROUND: Using the following kernel boot parameter allows me to boot but 
the maximum resolution is limited to 1024x768:
  nomodeset

  WORKAROUND: Edit the file /etc/gdm3/custom.conf and change:
  #WaylandEnable=false

  to:
  WaylandEnable=false

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: V1.03
  dmi.board.name: 0AD8h
  dmi.board.vendor: Board Manufacturer
  dmi.chassis.asset.tag: INA8100LFY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP dx2080 MT(KS826PA)
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768232/+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 1768232] Re: [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while booting after installing

2018-06-05 Thread d a i s y
Shane Semanek

I've tried disabling Wayland in GDM3.

sudo vi /etc/gdm3/custom.conf

Change #WaylandEnable=false to WaylandEnable=false and reboot

It worked !

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

Title:
  [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while
  booting after installing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My system stuck at ubuntu logo while booting. This issue occurred only
  after installing it, not when I choose 'Try without Installing'. This
  doesn't happen in 16.04.4.

  xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
     1024x768  76.00*

  Output of sudo lshw -c display

  *-display UNCLAIMED
     description: VGA compatible controller
     product: 82945G/GZ Integrated Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 02
     width: 32 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d

  WORKAROUND: Using the following kernel boot parameter allows me to boot but 
the maximum resolution is limited to 1024x768:
  nomodeset

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: V1.03
  dmi.board.name: 0AD8h
  dmi.board.vendor: Board Manufacturer
  dmi.chassis.asset.tag: INA8100LFY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP dx2080 MT(KS826PA)
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768232/+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 1768232] Re: [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while booting after installing

2018-06-05 Thread d a i s y
Christopher M. Penalver

1. I've tried debugging kernel boot option other than nomodeset but it did not 
work, it shows started all the services and then pause there, no process after 
then.
2. I've installed kernel 4.16 and 4.17 but it also didn't work and I have to 
boot up with nomodeset option.

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

Title:
  [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while
  booting after installing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My system stuck at ubuntu logo while booting. This issue occurred only
  after installing it, not when I choose 'Try without Installing'. This
  doesn't happen in 16.04.4.

  xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
     1024x768  76.00*

  Output of sudo lshw -c display

  *-display UNCLAIMED
     description: VGA compatible controller
     product: 82945G/GZ Integrated Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 02
     width: 32 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d

  WORKAROUND: Using the following kernel boot parameter allows me to boot but 
the maximum resolution is limited to 1024x768:
  nomodeset

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: V1.03
  dmi.board.name: 0AD8h
  dmi.board.vendor: Board Manufacturer
  dmi.chassis.asset.tag: INA8100LFY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP dx2080 MT(KS826PA)
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768232/+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 1768232] Re: Stuck at ubuntu logo while booting after installing Ubuntu 18.04 (i915 driver issue)

2018-05-08 Thread d a i s y
** Summary changed:

- i915 driver issue in Ubuntu 18.04
+ Stuck at ubuntu logo while booting after installing Ubuntu 18.04 (i915 driver 
issue)

** Summary changed:

- Stuck at ubuntu logo while booting after installing Ubuntu 18.04 (i915 driver 
issue)
+ Stuck at ubuntu logo while booting after installing Ubuntu 18.04 (Resolution 
1024x768 after nomodeset, i915 driver issue)

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

Title:
  Stuck at ubuntu logo while booting after installing Ubuntu 18.04
  (Resolution 1024x768 after nomodeset, i915 driver issue)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My system stuck at ubuntu logo while booting. To resolve it, I've set
  nomodeset.

  But now it occurs a resolution issue to 1024x768. Here are the
  necessary information:

  lspci -nnk | grep -iA2 vga
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
  Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  Kernel modules: i915, intelfb

  and

  xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
     1024x768  76.00*

  Output of sudo lshw -c display

  *-display UNCLAIMED
     description: VGA compatible controller
     product: 82945G/GZ Integrated Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 02
     width: 32 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d

  This issue occurred only after installing it, not when I choose 'Try
  without Installing', I don't need to set nomodeset in that case.

  Intel Graphics Update Tool shows:

  Checking if Intel graphics card available...
    • checking for i915 module in /sys/module
    • i915 module found
  Checking if Intel graphics card available... OK
  Retrieving information from 01.org...
    • fetching https://download.01.org/gfx/ilg-config.cfg
    • saving to /home/test/.ilg-config
    • fetched 1626 bytes
    • fetched 9818 bytes
    • fetched 12301 bytes
    • looking up [Ubuntu bionic] configuration
  Retrieving information from 01.org... OK
  Checking distribution... Failed

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: V1.03
  dmi.board.name: 0AD8h
  dmi.board.vendor: Board Manufacturer
  dmi.chassis.asset.tag: INA8100LFY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP dx2080 MT(KS826PA)
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
  version.xserver-xorg-core

[Touch-packages] [Bug 1749630] [NEW] package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade: 10.4193:subprocess installed post-installation script returned error exit status 1

2018-02-14 Thread Ricardo I Soto
Public bug reported:

An error occurred while upgrading to a new version of Bash on Ubuntu on
Windows. Report was given and I decided to send the report.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libuuid1 2.27.1-6ubuntu3.4
ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
Uname: Linux 4.4.0-43-Microsoft x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Wed Feb 14 21:05:15 2018
DuplicateSignature: package:libuuid1:2.27.1-6ubuntu3.4:10.4193:subprocess 
installed post-installation script returned error exit status 1
ErrorMessage: 10.4193:subprocess installed post-installation script returned 
error exit status 1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.0.1ubuntu2.17
SourcePackage: util-linux
Title: package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade: 
10.4193:subprocess installed post-installation script returned error exit 
status 1
UpgradeStatus: Upgraded to xenial on 2018-02-15 (0 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package dist-upgrade third-party-packages uec-images 
xenial

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

Title:
  package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade:
  10.4193:subprocess installed post-installation script returned error
  exit status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  An error occurred while upgrading to a new version of Bash on Ubuntu
  on Windows. Report was given and I decided to send the report.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libuuid1 2.27.1-6ubuntu3.4
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Wed Feb 14 21:05:15 2018
  DuplicateSignature: package:libuuid1:2.27.1-6ubuntu3.4:10.4193:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: 10.4193:subprocess installed post-installation script returned 
error exit status 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.0.1ubuntu2.17
  SourcePackage: util-linux
  Title: package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade: 
10.4193:subprocess installed post-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to xenial on 2018-02-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1749630/+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 1663989] [NEW] Screen flickering

2017-02-12 Thread I-mail-3
Public bug reported:

Since upgrading from ubuntu 16.04 to 16.10 the screen (backlight?) is
flickering irregularly. It only happens with kernel 4.8.x. No flickering
problems when manually switching back to kernel versions 4.4.x at boot.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
 GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Feb 12 11:29:15 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:502a]
   Subsystem: Lenovo GK208M [GeForce GT 740M] [17aa:502a]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:07dc Intel Corp. 
 Bus 001 Device 004: ID 04f2:b398 Chicony Electronics Co., Ltd 
 Bus 001 Device 003: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20C600JAGE
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed 
root=UUID=1728272d-15ec-4b09-b728-f2f4878b5120 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: J9ET98WW (2.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C600JAGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET98WW(2.18):bd03/04/2015:svnLENOVO:pn20C600JAGE:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600JAGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C600JAGE
dmi.product.version: ThinkPad Edge E540
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Sun Feb 12 11:28:27 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety

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

Title:
  Screen flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  Since upgrading from ubuntu 16.04 to 16.10 the screen (backlight?) is
  flickering irregularly. It only happens with kernel 4.8.x. No
  flickering problems when manually switching back to kernel versions
  4.4.x at boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 6.2.0 

[Touch-packages] [Bug 1617395] [NEW] package account-plugin-identica 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/identi.ca.conf', which

2016-08-26 Thread Kirill I.
Public bug reported:

#

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: account-plugin-identica 0.12+16.04.20160126-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Aug 26 19:16:46 2016
DuplicateSignature:
 package:account-plugin-identica:0.12+16.04.20160126-0ubuntu1
 Unpacking account-plugin-google (0.13+16.04.20160719-0ubuntu1) over 
(0.12+16.04.20160126-0ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.13+16.04.20160719-0ubuntu1_all.deb
 (--unpack):
  trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/identi.ca.conf', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
InstallationDate: Installed on 2012-05-25 (1553 days ago)
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: account-plugins
Title: package account-plugin-identica 0.12+16.04.20160126-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/identi.ca.conf', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict third-party-packages xenial

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

Title:
  package account-plugin-identica 0.12+16.04.20160126-0ubuntu1 failed to
  install/upgrade: trying to overwrite '/etc/signon-ui/webkit-
  options.d/identi.ca.conf', which is also in package kaccounts-
  providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  #

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-identica 0.12+16.04.20160126-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Aug 26 19:16:46 2016
  DuplicateSignature:
   package:account-plugin-identica:0.12+16.04.20160126-0ubuntu1
   Unpacking account-plugin-google (0.13+16.04.20160719-0ubuntu1) over 
(0.12+16.04.20160126-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.13+16.04.20160719-0ubuntu1_all.deb
 (--unpack):
trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:15.12.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/identi.ca.conf', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2012-05-25 (1553 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: account-plugins
  Title: package account-plugin-identica 0.12+16.04.20160126-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/identi.ca.conf', which is also in package 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1617395/+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 1486061] Re: Long descriptions missing from apt cache - affects software-center etc

2015-09-27 Thread Pau Garcia i Quiles
Same problem here.

If you delete the /var/lib/apt/lists, then apt-cache show will show the
long description.

If you apt-get update, then apt-cache show will once more not show the
long description.

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

Title:
  Long descriptions missing from apt cache - affects software-center etc

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  apt 1.0.9.10ubuntu6 and 1.0.9.10ubuntu7 - ubuntu wily

  It appears that on wily the long package descriptions are missing from
  the apt-cache. As a result of this bug full package descriptions are
  missing (amongst others) in software-center, update-manager, synaptic
  etc.

  The files like /var/lib/apt/lists/archive.ubuntu
  .com_ubuntu_dists_wily_universe_i18n_Translation-en do exist with a
  recent timestamp, so it looks the downloading of the translations has
  taken place.

  Using the python bindings cache['gimp'].candidate.description returns
  an empty string.

  Apt-cache also seems to be missing the 'Description-en' key:

  $ apt-cache show gimp
  Package: gimp
  Priority: optional
  Section: graphics
  Installed-Size: 15538
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Ari Pollak 
  Architecture: amd64
  Version: 2.8.14-1ubuntu2
  Replaces: gimp-plugin-registry (<< 4.20120506)
  Provides: gimp-python
  Depends: libgimp2.0 (>= 2.8.14), libgimp2.0 (<= 2.8.14-z), gimp-data (>= 
2.8.14), gimp-data (<= 2.8.14-z), python-gtk2 (>= 2.8.0), libgdk-pixbuf2.0-0 
(>= 2.24.1), libaa1 (>= 1.4p5), libbabl-0.1-0 (>= 0.1.10), libbz2-1.0, libc6 
(>= 2.15), libcairo2 (>= 1.10.2), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 
0.88), libexif12 (>= 0.6.21-1~), libfontconfig1 (>= 2.9.0), libfreetype6 (>= 
2.2.1), libgegl-0.3-0 (>= 0.3.0), libglib2.0-0 (>= 2.41.1), libgs9 (>= 
8.61.dfsg.1), libgtk2.0-0 (>= 2.24.10), libgudev-1.0-0 (>= 146), libjasper1, 
libjpeg8 (>= 8c), liblcms2-2 (>= 2.2+git20110628), libmng2 (>= 1.0.10), 
libpango-1.0-0 (>= 1.29.4), libpangocairo-1.0-0 (>= 1.29.4), libpangoft2-1.0-0 
(>= 1.29.4), libpng12-0 (>= 1.2.13-4), libpoppler-glib8 (>= 0.18.0), librsvg2-2 
(>= 2.14.4), libtiff5 (>= 4.0.3), libwmf0.2-7 (>= 0.2.8.4), libx11-6, 
libxcursor1 (>> 1.1.2), libxext6, libxfixes3, libxmu6, libxpm4, zlib1g (>= 
1:1.1.4), python:any (>= 2.6.6-7~), python2.7
  Recommends: ghostscript
  Suggests: gimp-help-en | gimp-help, gimp-data-extras, gvfs-backends, 
libasound2
  Breaks: gimp-plugin-registry (<< 4.20120506)
  Filename: pool/main/g/gimp/gimp_2.8.14-1ubuntu2_amd64.deb
  Size: 3476280
  MD5sum: d33d0d48362d03767f486185fa3e21cf
  SHA1: 8f65b842f5ec4a07b8ebf71c13ed9f97ed886474
  SHA256: 92eebf090c4f7f7e7ec5d9a06f3fe34f35221c44602d290201b05aa73b2ff2e1
  Description: The GNU Image Manipulation Program
  Description-md5: ad6dd18a09fb86ea4529ac53f33168b9
  Homepage: http://www.gimp.org/
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Origin: Ubuntu
  Supported: 9m
  Task: ubuntu-usb, edubuntu-desktop-gnome, edubuntu-usb, 
ubuntustudio-publishing, ubuntustudio-photography, ubuntustudio-graphics

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

2015-08-09 Thread Arunkumar-thondapu-i
*** Bug 474112 has been marked as a duplicate of this bug. ***

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

Title:
  OpenHAB designer causes crash in soup_session_feature_detach

Status in Eclipse:
  Fix Released
Status in libsoup:
  Unknown
Status in libsoup2.4 package in Ubuntu:
  Invalid
Status in libsoup2.4 package in Debian:
  New

Bug description:
  Running OpenHAB designer through any Java VM (tried 1.7, 1.8 and
  Oracle 1.8), causes a crash in libsoup:

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fb377829451, pid=11209, tid=140412652816128
  #
  # JRE version: Java(TM) SE Runtime Environment (8.0_25-b17) (build 
1.8.0_25-b17)
  # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode 
linux-amd64 compressed oops)
  # Problematic frame:
  # C  [libsoup-2.4.so.1+0x6f451]  soup_session_feature_detach+0x11
  #
  # Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try ulimit -c unlimited before starting Java again
  #
  # An error report file with more information is saved as:
  # /home/marius_priv/projects/openHAB/designer/hs_err_pid11209.log
  #
  # If you would like to submit a bug report, please visit:
  #   http://bugreport.sun.com/bugreport/crash.jsp
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libsoup2.4-1 2.46.0-3
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jan  1 20:51:53 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  InstallationDate: Installed on 2014-03-12 (295 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: libsoup2.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse-eclipsers/+bug/1406981/+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 1438003] Re: (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-glib.

2015-07-22 Thread Guido I
I'm hitting this bug too, and so far working around it by going to Edit
connections - Edit the network you want to connect to - manually input
the WPA2 password in the Wi-Fi Security tab - Save, then it connects
without problems.

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

Title:
  (1) Creating object for path
  '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-
  glib.

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  While attempting to connect to an SSID for the first time, it fails, and I 
consistently get:
  (1) Creating object for path 
'/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-glib.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Mar 29 23:08:37 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-03-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.2
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlan0   wifi  connected /org/freedesktop/NetworkManager/Devices/4  
www.ubuntu.com  71c36534-c491-4479-aa91-9238b10f3945  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlan1   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   eth0ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

2015-05-31 Thread Arunkumar-thondapu-i
(In reply to Marco Rietveld from comment #46)
 This bug (or very similar one) appears to have reappeared in the latest
 update to Luna (20150219-0600). The same workaround also works there (e.g. 
 -Dorg.eclipse.swt.browser.DefaultType=mozilla).

Please provide more details - which OS, what are the versions of GTK+
and webkit etc. and the crash logs too if possible.

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

Title:
  OpenHAB designer causes crash in soup_session_feature_detach

Status in Eclipse:
  Fix Released
Status in Soup HTTP Library:
  Unknown
Status in libsoup2.4 package in Ubuntu:
  Invalid
Status in libsoup2.4 package in Debian:
  New

Bug description:
  Running OpenHAB designer through any Java VM (tried 1.7, 1.8 and
  Oracle 1.8), causes a crash in libsoup:

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fb377829451, pid=11209, tid=140412652816128
  #
  # JRE version: Java(TM) SE Runtime Environment (8.0_25-b17) (build 
1.8.0_25-b17)
  # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode 
linux-amd64 compressed oops)
  # Problematic frame:
  # C  [libsoup-2.4.so.1+0x6f451]  soup_session_feature_detach+0x11
  #
  # Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try ulimit -c unlimited before starting Java again
  #
  # An error report file with more information is saved as:
  # /home/marius_priv/projects/openHAB/designer/hs_err_pid11209.log
  #
  # If you would like to submit a bug report, please visit:
  #   http://bugreport.sun.com/bugreport/crash.jsp
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libsoup2.4-1 2.46.0-3
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jan  1 20:51:53 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  InstallationDate: Installed on 2014-03-12 (295 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: libsoup2.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse-eclipsers/+bug/1406981/+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 1241101]

2015-05-04 Thread Arunkumar-thondapu-i
*** Bug 466326 has been marked as a duplicate of this bug. ***

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

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Invalid
Status in gtk+2.0 package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1447917] Re: popup volume previewer should not show up when adjusting volume using a volume slider

2015-04-27 Thread I Ahmad
** Changed in: indicator-sound (Ubuntu)
   Status: New = Confirmed

** Changed in: indicator-sound (Ubuntu)
   Importance: Undecided = High

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

Title:
  popup volume previewer should not show up when adjusting volume using
  a volume slider

Status in indicator-sound package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  $ system-image-cli -i
  current build number: 21
  device name: arale
  channel: ubuntu-touch/tangxi-vivid-proposed
  last update: 2015-04-24 06:07:50
  version version: 21

  
  Steps
  1. swipe down from Sound Indicator
  2. slide on the volume slider
  = a popup volume previewer shows up
  3. enter System Settings - Sound
  4. slide on the Ringer volume slider
  = a popup volume previewer shows up

  Expect
  In step2 and step4, 
  The popup previewer is unexpected, as there is already a slider shows the 
current volume status.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1447917/+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 1428584] [NEW] Autopilot tests are failing due to wrong coordinates for key

2015-03-05 Thread I Ahmad
Public bug reported:

Autopilot tests are failing on dashboard http://rtm-
dashboard.ci.ubuntu.com/smokeng/vivid/touch/krillin/122:20150225:20150210-95b6a9f/352/ubuntu_keyboard/

I did some investigation and it seems the x coordinate for top left key
(1, q, Q etc) are wrong and as a result AP taps on the wrong coordinate.

This started happening around 25th Feb 2015 and is pretty consistent
since then as well as I am able to reproduce it locally.

** Affects: ubuntu-keyboard
 Importance: Undecided
 Assignee: Michael Sheldon (michael-sheldon)
 Status: New

** Affects: ubuntu-keyboard (Ubuntu)
 Importance: Undecided
 Assignee: Michael Sheldon (michael-sheldon)
 Status: New

** Description changed:

  Autopilot tests are failing on dashboard http://rtm-
  
dashboard.ci.ubuntu.com/smokeng/vivid/touch/krillin/122:20150225:20150210-95b6a9f/352/ubuntu_keyboard/
  
- I did a some investigation and it seems the x coordinate for top left
- key (1, q, Q etc) are wrong and as a result AP taps on the wrong
- coordinate.
+ I did some investigation and it seems the x coordinate for top left key
+ (1, q, Q etc) are wrong and as a result AP taps on the wrong coordinate.
  
  This started happening around 25th Feb 2015 and is pretty consistent
  since then as well as I am able to reproduce it locally.

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

Title:
  Autopilot tests are failing due to wrong coordinates for key

Status in Ubuntu Keyboard:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  Autopilot tests are failing on dashboard http://rtm-
  
dashboard.ci.ubuntu.com/smokeng/vivid/touch/krillin/122:20150225:20150210-95b6a9f/352/ubuntu_keyboard/

  I did some investigation and it seems the x coordinate for top left
  key (1, q, Q etc) are wrong and as a result AP taps on the wrong
  coordinate.

  This started happening around 25th Feb 2015 and is pretty consistent
  since then as well as I am able to reproduce it locally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1428584/+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 1428000] [NEW] Dashboard reports test failures for TextInput

2015-03-03 Thread I Ahmad
Public bug reported:

There are some consistent UITK failures related to TextInput reported on
Dashboard

http://rtm-
dashboard.ci.ubuntu.com/smokeng/vivid/touch/krillin/128:20150301.1:20150210-95b6a9f/366/ubuntuuitoolkit/

Apparently these are due to object name or value changed or may be the
object type doesn't exist anymore.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Dashboard reports test failures for TextInput

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  There are some consistent UITK failures related to TextInput reported
  on Dashboard

  http://rtm-
  
dashboard.ci.ubuntu.com/smokeng/vivid/touch/krillin/128:20150301.1:20150210-95b6a9f/366/ubuntuuitoolkit/

  Apparently these are due to object name or value changed or may be the
  object type doesn't exist anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1428000/+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 1423506] Re: Continue to show spinner instead of video thumbnail preview

2015-02-19 Thread I Ahmad
** Attachment added: screenshot
   
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1423506/+attachment/4322480/+files/spinner-galleryapp.png

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

Title:
  Continue to show spinner instead of video thumbnail preview

Status in gallery-app package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Copy some photos and videos to internal storage on device
  2. Launch the gallery app
  3. Scroll to the videos under Events
  4. Tap on a video to open

  Observe that under the play button, gallery app will show a spinner
  indefintely instead of a video preview image.

  
  Device Info:

  last update: 2015-02-19 09:10:32
  version version: 240
  version ubuntu: 20150218.1
  version device: 20150216-fe747ac
  version custom: 20150216-561-29-186

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1423506/+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 1423506] [NEW] Continue to show spinner instead of video thumbnail preview

2015-02-19 Thread I Ahmad
Public bug reported:

Steps to reproduce:
1. Copy some photos and videos to internal storage on device
2. Launch the gallery app
3. Scroll to the videos under Events
4. Tap on a video to open

Observe that under the play button, gallery app will show a spinner
indefintely instead of a video preview image.


Device Info:

last update: 2015-02-19 09:10:32
version version: 240
version ubuntu: 20150218.1
version device: 20150216-fe747ac
version custom: 20150216-561-29-186

** Affects: gallery-app (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Steps to reproduce:
  1. Copy some photos and videos to internal storage on device
  2. Launch the gallery app
  3. Scroll to the videos under Events
  4. Tap on a video to open
  
  Observe that under the play button, gallery app will show a spinner
  indefintely instead of a video preview image.
+ 
+ 
+ Device Info:
+ 
+ last update: 2015-02-19 09:10:32
+ version version: 240
+ version ubuntu: 20150218.1
+ version device: 20150216-fe747ac
+ version custom: 20150216-561-29-186

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

Title:
  Continue to show spinner instead of video thumbnail preview

Status in gallery-app package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Copy some photos and videos to internal storage on device
  2. Launch the gallery app
  3. Scroll to the videos under Events
  4. Tap on a video to open

  Observe that under the play button, gallery app will show a spinner
  indefintely instead of a video preview image.

  
  Device Info:

  last update: 2015-02-19 09:10:32
  version version: 240
  version ubuntu: 20150218.1
  version device: 20150216-fe747ac
  version custom: 20150216-561-29-186

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1423506/+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 1423535] [NEW] Search doesn't work for photos scope for images on internal stograge

2015-02-19 Thread I Ahmad
Public bug reported:

Steps To reproduce:

1. Copy some image files on device under /phablet/home/Pictures and remember 
the file names
2. Navigate to Photos scope
3. Search for the image name copied on internal storage

Observe that search doesn't return the result for internal storage.

** Affects: unity-scopes-shell (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Search doesn't work for photos scope for images on internal stograge

Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  Steps To reproduce:

  1. Copy some image files on device under /phablet/home/Pictures and remember 
the file names
  2. Navigate to Photos scope
  3. Search for the image name copied on internal storage

  Observe that search doesn't return the result for internal storage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1423535/+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 1406981]

2015-02-07 Thread Arunkumar-thondapu-i
Backported this fix to 4.2.2+ via
http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?h=R4_2_maintenanceid=a644928613957d2a53e2ecb084423941ba6b8672

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

Title:
  OpenHAB designer causes crash in soup_session_feature_detach

Status in Eclipse:
  Fix Released
Status in Soup HTTP Library:
  Unknown
Status in libsoup2.4 package in Ubuntu:
  Invalid
Status in libsoup2.4 package in Debian:
  New

Bug description:
  Running OpenHAB designer through any Java VM (tried 1.7, 1.8 and
  Oracle 1.8), causes a crash in libsoup:

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fb377829451, pid=11209, tid=140412652816128
  #
  # JRE version: Java(TM) SE Runtime Environment (8.0_25-b17) (build 
1.8.0_25-b17)
  # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode 
linux-amd64 compressed oops)
  # Problematic frame:
  # C  [libsoup-2.4.so.1+0x6f451]  soup_session_feature_detach+0x11
  #
  # Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try ulimit -c unlimited before starting Java again
  #
  # An error report file with more information is saved as:
  # /home/marius_priv/projects/openHAB/designer/hs_err_pid11209.log
  #
  # If you would like to submit a bug report, please visit:
  #   http://bugreport.sun.com/bugreport/crash.jsp
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libsoup2.4-1 2.46.0-3
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jan  1 20:51:53 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  InstallationDate: Installed on 2014-03-12 (295 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130203-13:50
  SourcePackage: libsoup2.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse-eclipsers/+bug/1406981/+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 1393169] Re: Double mouse cursor

2015-01-18 Thread Scott I. Remick
I get this a lot myself. The only temporary solution is to reboot but it
comes back eventually. I'm already on my latest BIOS. Xubuntu 14.10

This also seems identical to bug 1396361.

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

Title:
  Double mouse cursor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Last up to date Xubuntu 64 bits installed on a laptop

  Since 2 days, the mouse cursor is double with only the left part as
  active and a bar just behing of both arrow (see picture joined).

  I tried to change the theme but no way to go back to a normal mouse
  cursor

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov 16 11:12:21 2014
  InstallationDate: Installed on 2013-01-03 (681 days ago)
  InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 
(20121017.1)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroRelease: Ubuntu 14.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fde0]
 Subsystem: Toshiba America Info Systems Device [1179:fde0]
  InstallationDate: Installed on 2013-01-03 (695 days ago)
  InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 
(20121017.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1659): WARNING **: Failed to load background: 
Impossible d'ouvrir le fichier « 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission 
non accordée
   
   ** (lightdm-gtk-greeter:1659): WARNING **: Failed to read wallpaper: 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1641): WARNING **: Failed to load background: 
Impossible d'ouvrir le fichier « 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission 
non accordée
   
   ** (lightdm-gtk-greeter:1641): WARNING **: Failed to read wallpaper: 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: TOSHIBA Satellite Pro C650
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic 
root=UUID=7bc86e4b-720d-4f1c-bb66-a4c08ffc1359 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1
  Tags:  utopic ubuntu
  Uname: Linux 3.16.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/01/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.30:bd07/01/2010:svnTOSHIBA:pnSatelliteProC650:pvrPSC09E-00R01YMV:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite Pro C650
  dmi.product.version: PSC09E-00R01YMV
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov 28 08:29:52 2014

[Touch-packages] [Bug 1273261] Re: Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1: can't open /dev/mapper/ubuntu--vg-root: no such file

2014-11-15 Thread I. T. Pohjalainen
My laptop ThinkPad L420 had 14.04 Ubuntu with lvm but no encryption.
Now, after doing fresh install to 14.10 with encrypted hard drive, I get
this problem. Probably unrelated issue, but I had to remove splash from
kernel boot parameters even in order to get to the enter
passphrase-part.

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

Title:
  Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1:
  can't open /dev/mapper/ubuntu--vg-root: no such file

Status in “cryptsetup” package in Ubuntu:
  Confirmed
Status in “initramfs-tools” package in Ubuntu:
  Confirmed

Bug description:
  While booting cryptsetup outputs following error: /scripts/local-
  top/cryptroot: line 1: can't open /dev/mapper/ubuntu--vg-root: no such
  file, seems to be not related to this particular installation as saw
  the same output on other machines, also seems to be nothing major as
  everything boots fine, so just reporting to let you know it's there.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: cryptsetup 2:1.4.3-4ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Jan 27 15:58:16 2014
  InstallationDate: Installed on 2014-01-18 (8 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  crypttab: sda3_crypt UUID=68851a49-83a4-41eb-84c0-27d15280bbc1 none luks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261/+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 1391065] [NEW] Search doesn't work for dashboard scope

2014-11-09 Thread I Ahmad
Public bug reported:

Search doesn't work for dashboard scope

Steps to reproduce:
1. Recieve some text messages and phone calls on DUT
2. Go to dashboard scope and refresh to reload the up to date contents (should 
reload be explicit?)
3. Search some word from earlier recieved messages
4. Search phone numbers from which calls were recieved earlier

Observe that no relevant results are shown.

Expected Result: Only relevenat results and sections should be filtered
based on search term.

** Affects: unity-scope-click (Ubuntu)
 Importance: High
 Status: New


** Tags: qa-daily-testing rtm14

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

Title:
  Search doesn't work for dashboard scope

Status in “unity-scope-click” package in Ubuntu:
  New

Bug description:
  Search doesn't work for dashboard scope

  Steps to reproduce:
  1. Recieve some text messages and phone calls on DUT
  2. Go to dashboard scope and refresh to reload the up to date contents 
(should reload be explicit?)
  3. Search some word from earlier recieved messages
  4. Search phone numbers from which calls were recieved earlier

  Observe that no relevant results are shown.

  Expected Result: Only relevenat results and sections should be
  filtered based on search term.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1391065/+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 1387959] Re: unity8 crash in image krillin rtm 139

2014-10-31 Thread I Ahmad
as well as the telephony service approver crash dump

** Attachment added: _usr_bin_telephony-service-approver.32011.crash
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387959/+attachment/4250339/+files/_usr_bin_telephony-service-approver.32011.crash

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

Title:
  unity8 crash in image krillin rtm 139

Status in “unity8” package in Ubuntu:
  New

Bug description:
  Earlier today, a few QA folks tested image krillin rtm 138 plus silo
  13, and found that it fixed the unity8 crash from bug 1382595.

  Silo 13 plus silo 10 landed in image 139.

  Now, in image 139, unity8 is crashy again.  Olli mentioned getting two
  crashes within a few minutes, and I got a unity8 crash while trying to
  accept an incoming call.  I'm not sure if it's the same crash as
  before, or if it's a new one.

  Attached is the crash dump I got just after hitting 'accept' for an
  incoming call.  I tried to pre-process it in apport-cli, but it failed
  with Sorry, the program unity8 closed unexpectedly  //  Your
  computer does not have enough free memory to automatically analyze the
  problem and send a report to the developers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387959/+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 1370884] [NEW] bluetooth icon in indicators keep showing connected

2014-09-18 Thread I Ahmad
Public bug reported:

bluetooth icon in indicators keep showing connected afer even
forgetting/disconnecting the bt headset.

Steps to reproduce:
1. Pair/Connect the bluetooth headtset with krillin
2. Note that bluetooth icon in indicators is changed, showing device is 
connected over bluetooth.
3. Now go to bluetooth settings and then further to connected headset's setting 
page.
4. Tap on Forget this device'

Observe that despite device is no longer paired and disconnected the
bluetooth icon in indicators won't change to unpaired state. (see
attached png)

Device/Build Info:

phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 1
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09
last update: 2014-09-16 17:43:20
version version: 1
version ubuntu: 20140916
version device: 20140912-238

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


** Tags: bluetooth qa-daily-testing rtm14

** Attachment added: bluetooth-paired-icon.png
   
https://bugs.launchpad.net/bugs/1370884/+attachment/4207086/+files/bluetooth-paired-icon.png

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

Title:
  bluetooth icon in indicators keep showing connected

Status in “bluez” package in Ubuntu:
  New

Bug description:
  bluetooth icon in indicators keep showing connected afer even
  forgetting/disconnecting the bt headset.

  Steps to reproduce:
  1. Pair/Connect the bluetooth headtset with krillin
  2. Note that bluetooth icon in indicators is changed, showing device is 
connected over bluetooth.
  3. Now go to bluetooth settings and then further to connected headset's 
setting page.
  4. Tap on Forget this device'

  Observe that despite device is no longer paired and disconnected the
  bluetooth icon in indicators won't change to unpaired state. (see
  attached png)

  Device/Build Info:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 1
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09
  last update: 2014-09-16 17:43:20
  version version: 1
  version ubuntu: 20140916
  version device: 20140912-238

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1370884/+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 1370911] [NEW] bluetooth headset (Motorola S10-HD) remains connected despite it appears disconnected

2014-09-18 Thread I Ahmad
Public bug reported:

bluetooth headset (Motorola S10-HD) remains connected despite it appears
disconnected

Steps to reproduce:

1. Pair the Motorola S10-HD with krillin
2. Now disconnect the headtset form bluetooth settings page.
3. Note that bt headset settings page shows that device is disconnected.
4. Now play some music track
Observe that music is still playing through bt headset while it is disconnected.

Build/Device Info:

phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 1
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09
last update: 2014-09-16 17:43:20
version version: 1
version ubuntu: 20140916
version device: 20140912-23825b8
version custom: 1410739265

Bluetooth Headset: Motorola S10-HD

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


** Tags: bluetooth qa-daily-testing rtm14

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

Title:
  bluetooth headset (Motorola S10-HD) remains connected despite it
  appears disconnected

Status in “bluez” package in Ubuntu:
  New

Bug description:
  bluetooth headset (Motorola S10-HD) remains connected despite it
  appears disconnected

  Steps to reproduce:

  1. Pair the Motorola S10-HD with krillin
  2. Now disconnect the headtset form bluetooth settings page.
  3. Note that bt headset settings page shows that device is disconnected.
  4. Now play some music track
  Observe that music is still playing through bt headset while it is 
disconnected.

  Build/Device Info:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 1
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09
  last update: 2014-09-16 17:43:20
  version version: 1
  version ubuntu: 20140916
  version device: 20140912-23825b8
  version custom: 1410739265

  Bluetooth Headset: Motorola S10-HD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1370911/+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 1363046] Re: No message/call notification tone plays through Bluetooth headset

2014-09-16 Thread I Ahmad
** Changed in: bluez (Ubuntu Utopic)
   Importance: High = Critical

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

Title:
  No message/call notification tone plays through Bluetooth headset

Status in “bluez” package in Ubuntu:
  New
Status in “bluez” source package in Utopic:
  New

Bug description:
  krillin ubuntu-rtm/14.09-proposed build 4.
  bluez  4.101-0ubuntu19 armhf

  SUMMARY:
  When a Bluetooth headset (Sony SBH50, Motorola S10-HD) is connected to 
krillin and a call/sms is received, no notification tone is played through the 
headset. Instead it plays normally through the device loud speakers.

  We have seen on some other versions of headset (Jawbone ERA, BQ Avrha
  Strauss) where a new sms notification tone is played through the
  headset, but not the call ringer tone.

  STEPS:
  1) Pair and connect the Bluetooth headset
  2) Receive an incoming sms
  3) Receive an incoming call

  EXPECTED RESULT:
  The notification tones should play through the Bluetooth headset

  ACTUAL RESULT:
  There is no notification tone played through the Bluetooth headset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1363046/+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 1363095] Re: Music playback does not re-start in Bluetooth speaker following incoming phone call

2014-09-16 Thread I Ahmad
** Changed in: bluez (Ubuntu)
   Importance: High = Critical

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

Title:
  Music playback does not re-start in Bluetooth speaker following
  incoming phone call

Status in “bluez” package in Ubuntu:
  In Progress

Bug description:
  krillin ubuntu-rtm/14.09-proposed build 4.
  bluez 4.101-0ubuntu19 armhf

  SUMMARY:
  When a Bluetooth speaker is connected to the krillin and playing music, after 
an incoming call is received, it is not possible to resume playback on the 
Bluetooth speaker without restarting the music app.

  STEPS:
  1) Pair and connect the Bluetooth speaker (BQ Altavoz Bluetooth Strauss)
  2) Start music playback
  3) During music playback receive an incoming call
  4) Reject the call from the krillin
  5) Try to resume music playback

  EXPECTED RESULT:
  The music should continue to play back through the Bluetooth speaker from the 
point when the call was received.

  ACTUAL RESULT:
  The music app indicates it is playing the track, but there is no music heard. 
It is not possible to play the music through the Bluetooth speaker without 
re-starting the music app. When the music app is re-started, music will play 
through the Bluetooth speaker again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1363095/+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 1363083] Re: Music playback does not re-route audio when Bluetooth speaker connected/disconnected

2014-09-16 Thread I Ahmad
** Changed in: bluez (Ubuntu)
   Importance: High = Critical

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

Title:
  Music playback does not re-route audio when Bluetooth speaker
  connected/disconnected

Status in “bluez” package in Ubuntu:
  Confirmed

Bug description:
  krillin ubuntu-rtm/14.09-proposed build 4.
  bluez 4.101-0ubuntu19 armhf

  SUMMARY:
  When a Bluetooth speaker is connected/disconnected to the krillin, the music 
playback route does not automatically update to accomodate this. The music app 
must be re-started for the new configuration to work.

  STEPS:
  1) Pair and connect the Bluetooth speaker (BQ Altavoz Bluetooth Strauss)
  2) Start music playback
  3) Disconnect the Bluetooth speaker on krillin from the Bluetooth settings

  EXPECTED RESULT:
  The music should play back through the Bluetooth speaker until it is 
disconnected. When the speaker is disconnected it should revert to using the 
krillin loud speaker.

  ACTUAL RESULT:
  The music plays back through the Bluetooth speaker until it is disconnected. 
When the speaker is disconnected, there is no music heard from the krillin. The 
music app is still playing the track as the progress bar is still updating, but 
there is no sound.

  When the music app is re-started, music will play through the krillin
  loud speaker.

  NOTES:
  The same problem is observed for the opposite situation where a Bluetooth 
speaker is connected to the device when it is already playing music through the 
krillin loud speaker. The Bluetooth speaker will only be used once the music 
app is restarted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1363083/+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 1366751] [NEW] Preview page keeps showing 'In Progress' even when application purchase is cancelled.

2014-09-08 Thread I Ahmad
Public bug reported:

Steps to reproduce:

1. Setup the pay-service staging account as described in test plan 
https://wiki.ubuntu.com/Process/Merges/TestPlan/pay-service
2. Now search for Delta app in Ubuntu Store
3. Tap on the price to purchase and install the app.
4. Instead of going aheadh with purchase, cancel the transaction by pressing 
Cancel button.
5. Observe that, UI will return to application preview page and will keep 
showing 'In Progress' even when transaction is cancelled.

** Affects: unity-scope-click (Ubuntu RTM)
 Importance: High
 Status: New


** Tags: qa-daily-testing rtm14

** Package changed: unity-scope-click (Ubuntu) = unity-scope-click
(Ubuntu RTM)

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

Title:
  Preview page keeps showing 'In Progress' even when application
  purchase is cancelled.

Status in “unity-scope-click” package in Ubuntu RTM:
  New

Bug description:
  Steps to reproduce:

  1. Setup the pay-service staging account as described in test plan 
https://wiki.ubuntu.com/Process/Merges/TestPlan/pay-service
  2. Now search for Delta app in Ubuntu Store
  3. Tap on the price to purchase and install the app.
  4. Instead of going aheadh with purchase, cancel the transaction by pressing 
Cancel button.
  5. Observe that, UI will return to application preview page and will keep 
showing 'In Progress' even when transaction is cancelled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-rtm/+source/unity-scope-click/+bug/1366751/+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 1241101]

2014-08-25 Thread Arunkumar-thondapu-i
(In reply to Kamil Khamitov from comment #31)
 Created attachment 246108 [details]
 full log
 
 Hello, with Eclipse 4.2.2 with ADT get this bug.  
 Core dump https://yadi.sk/d/UTGqkxJmZz6e7
 
 #
 # A fatal error has been detected by the Java Runtime Environment:
 #
 #  SIGSEGV (0xb) at pc=0x7fe3b0b716b8, pid=6629, tid=140615974131456
 #
 # JRE version: Java(TM) SE Runtime Environment (7.0_67-b01) (build
 1.7.0_67-b01)
 # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.65-b04 mixed mode
 linux-amd64 compressed oops)
 # Problematic frame:
 # C  [libgobject-2.0.so.0+0x1a6b8]  g_object_get_qdata+0x18

This crash is bug 372560 which is fixed since Eclipse 4.3.

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

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Invalid
Status in “gtk+2.0” package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

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