[Touch-packages] [Bug 1317449] Re: Please update to a version > 3.8.2

[b3nmore]

I took the liberty to changed the status from 'Fix Released' -> 'In
Progress' to keep it in the open bug list. Since the issue remains for
trusty, the majority of ubuntu users is still affected (as one can see
by the still growing numbers of dups of kde bug tracker).

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

Title:
  Please update to a version > 3.8.2

Status in digiKam - digital photo management:
  Won't Fix
Status in SQLite:
  Won't Fix
Status in “sqlite3” package in Ubuntu:
  In Progress

Bug description:
  According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 
3.8.2 causes crashes in digikam (and possibly other software) in various 
situations. There are several reports, that versions > 3.8.2 fix the issue.
  I'm using the 3.8.4.3 package from debian testing right now and can't trigger 
crashes anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/digikam/+bug/1317449/+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 1317449] Re: Please update to a version > 3.8.2

[b3nmore]

** Changed in: sqlite3 (Ubuntu)
   Status: Fix Released => In Progress

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

Title:
  Please update to a version > 3.8.2

Status in digiKam - digital photo management:
  Won't Fix
Status in SQLite:
  Won't Fix
Status in “sqlite3” package in Ubuntu:
  In Progress

Bug description:
  According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 
3.8.2 causes crashes in digikam (and possibly other software) in various 
situations. There are several reports, that versions > 3.8.2 fix the issue.
  I'm using the 3.8.4.3 package from debian testing right now and can't trigger 
crashes anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/digikam/+bug/1317449/+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 1338730] Re: Store does nothing when no-internet flag is enabled

[Launchpad Bug Tracker]

This bug was fixed in the package unity-scope-click -
0.1+14.10.20140711.1-0ubuntu1

---
unity-scope-click (0.1+14.10.20140711.1-0ubuntu1) utopic; urgency=medium

  [ Alejandro J. Cura (alecu) ]
  * New upstream release.
- Display preloaded core apps at the top in a dedicated headerless
  category.
- More in line with latest designs: use big card for app of the week, pass
  search string in a canned query of Ubuntu Store link.
- Store preview: screenshots first, then the icon/header & buttons.
- Display number of results found in the Store when performing search.
- Drop the no-internet setting check, as store requires explicit search
  now. (LP: #1338730)
- Updated the autopilot tests to use the split scopes.

  [ Ubuntu daily release ]
  * New rebuild forced
 -- Ubuntu daily releaseFri, 11 Jul 2014 
22:12:19 +

** Changed in: unity-scope-click (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Store does nothing when no-internet flag is enabled

Status in “unity-scope-click” package in Ubuntu:
  Fix Released

Bug description:
  When the setting to not include network results in scopes is enabled,
  the store scope will show no results. This made some sense when we had
  a single scope that was for installed and available apps, but with the
  split into two scopes, one must explicitly go to the store scope to
  get those automatic network results.

  However, we may need to obey this flag, when searching in the
  installed apps scope, and avoid showing store results when searching
  there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1338730/+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 1314551] Re: 1002:130f [GIgabyte G1.Sniper A88X-CF] Font corruption

[Christopher M. Penalver]

Bartlomiej Ogryczak, thank you for your comment. So your hardware and problem 
may be tracked, could you please file a new report with Ubuntu by executing the 
following in a terminal while booted into the default Ubuntu kernel (not a 
mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: 
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: 
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: 
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

Title:
  1002:130f [GIgabyte G1.Sniper A88X-CF] Font corruption

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  I see the occasional corrupted letters in 14.04 using AMD Radeon R7
  graphics hardware with the radeon driver.

  fglrx is uninstallable.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Apr 30 11:09:26 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 200 Series] 
[1002:130f] (prog-if 00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0123]
  InstallationDate: Installed on 2014-04-14 (15 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: G1.Sniper A88X-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd11/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperA88X-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr 29 09:17:41 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314551/+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 1341022] Re: [Latitude E7240, Realtek ALC292, Mic, Internal] Internal Mic not visible

[Dan Poler]

Retested with latest firmware - no change.

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

Title:
  [Latitude E7240, Realtek ALC292, Mic, Internal] Internal Mic not
  visible

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  Sound Settings panel shows "Headset microphone" and "Dock microphone".
  Headset when plugged in works fine (the little dialogue pops up etc).
  Internal microphone is not visible anywhere within the GUI.

  alsamixer "sees" the internal microphone and I can adjust its levels
  but this does not affect the desktop environment.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dpoler 2022 F pulseaudio
   /dev/snd/controlC0:  dpoler 2022 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul 11 17:48:09 2014
  InstallationDate: Installed on 2014-07-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: Only some of inputs are working
  Title: [Latitude E7240, Realtek ALC292, Mic, Internal] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0414F8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/05/2013:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn0414F8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1341022/+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 1341022] Re: [Latitude E7240, Realtek ALC292, Mic, Internal] Internal Mic not visible

[Dan Poler]

(there's no dock attached to the system - I don't even own one!)

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

Title:
  [Latitude E7240, Realtek ALC292, Mic, Internal] Internal Mic not
  visible

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  Sound Settings panel shows "Headset microphone" and "Dock microphone".
  Headset when plugged in works fine (the little dialogue pops up etc).
  Internal microphone is not visible anywhere within the GUI.

  alsamixer "sees" the internal microphone and I can adjust its levels
  but this does not affect the desktop environment.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dpoler 2022 F pulseaudio
   /dev/snd/controlC0:  dpoler 2022 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul 11 17:48:09 2014
  InstallationDate: Installed on 2014-07-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: Only some of inputs are working
  Title: [Latitude E7240, Realtek ALC292, Mic, Internal] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0414F8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/05/2013:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn0414F8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1341022/+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 1341022] Re: [Latitude E7240, Realtek ALC292, Mic, Internal] Internal Mic not visible

[Raymond]

/sys/class/sound/hwC1D0/init_pin_configs:
0x12 0x90a60140
0x13 0x41f0
0x14 0x90170110
0x15 0x0221401f
0x16 0x01014020
0x18 0x41f0
0x19 0x01a19030
0x1a 0x41f0
0x1b 0x41f0
0x1d 0x4071
0x1e 0x41f0

/sys/class/sound/hwC1D0/driver_pin_configs:
0x16 0x21014020
0x19 0x21a19030
0x1a 0x01a1913c


driver seem add pin complex


   4.983518] autoconfig: line_outs=1 (0x16/0x0/0x0/0x0/0x0) type:line
[4.983522]speaker_outs=1 (0x14/0x0/0x0/0x0/0x0)
[4.983525]hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
[4.983527]mono: mono_out=0x0
[4.983529]inputs:
[4.983532]  Dock Mic=0x19
[4.983536]  Headset Mic=0x1a
[4.983539]  Internal Mic=0x12

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

Title:
  [Latitude E7240, Realtek ALC292, Mic, Internal] Internal Mic not
  visible

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  Sound Settings panel shows "Headset microphone" and "Dock microphone".
  Headset when plugged in works fine (the little dialogue pops up etc).
  Internal microphone is not visible anywhere within the GUI.

  alsamixer "sees" the internal microphone and I can adjust its levels
  but this does not affect the desktop environment.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dpoler 2022 F pulseaudio
   /dev/snd/controlC0:  dpoler 2022 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul 11 17:48:09 2014
  InstallationDate: Installed on 2014-07-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: Only some of inputs are working
  Title: [Latitude E7240, Realtek ALC292, Mic, Internal] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0414F8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/05/2013:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn0414F8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1341022/+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 1341022] Re: [Latitude E7240, Realtek ALC292, Mic, Internal] Internal Mic not visible

[Raymond]

control.19 {
iface CARD
name 'Dock Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}


dock Mic seem plugged

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

Title:
  [Latitude E7240, Realtek ALC292, Mic, Internal] Internal Mic not
  visible

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  Sound Settings panel shows "Headset microphone" and "Dock microphone".
  Headset when plugged in works fine (the little dialogue pops up etc).
  Internal microphone is not visible anywhere within the GUI.

  alsamixer "sees" the internal microphone and I can adjust its levels
  but this does not affect the desktop environment.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dpoler 2022 F pulseaudio
   /dev/snd/controlC0:  dpoler 2022 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul 11 17:48:09 2014
  InstallationDate: Installed on 2014-07-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: Only some of inputs are working
  Title: [Latitude E7240, Realtek ALC292, Mic, Internal] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0414F8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/05/2013:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn0414F8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1341022/+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 1312189] Re: No apps shown on first boot

[Launchpad Bug Tracker]

[Expired for unity-scope-click (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: unity-scope-click (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  No apps shown on first boot

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

Bug description:
  First boot after a flash, enable wifi, but no apps are shown in the click 
scope, including local apps
  Reboot and all is well
  Seen with 302, 303 on mako and Nexus 5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1312189/+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 1317235] Re: UI frozen and running at 100% CPU

[Launchpad Bug Tracker]

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

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

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

Title:
  UI frozen and running at 100% CPU

Status in “unity8” package in Ubuntu:
  Expired

Bug description:
  Mako running u15
  Was on the music scope, device suspended, when resumed the UI was frozen.

  Backtrace from gdb

  0  0xb6444032 in epoll_wait () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb4446bd2 in boost::asio::detail::epoll_reactor::run(bool, 
boost::asio::detail::op_queue&) 
()
 from /usr/lib/arm-linux-gnueabihf/libmirserver.so.19
  #2  0xb4448976 in 
boost::asio::detail::task_io_service::run(boost::system::error_code&) () from 
/usr/lib/arm-linux-gnueabihf/libmirserver.so.19
  #3  0xb4445b14 in mir::AsioMainLoop::run() ()
 from /usr/lib/arm-linux-gnueabihf/libmirserver.so.19
  #4  0xb44413d2 in mir::DisplayServer::run() ()
 from /usr/lib/arm-linux-gnueabihf/libmirserver.so.19
  #5  0xb443f7e8 in mir::run_mir(mir::ServerConfiguration&, std::function) () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.19
  #6  0xb452a8c6 in QMirServer::runWithClient(std::function) ()
 from /usr/lib/arm-linux-gnueabihf/libunity-mir.so.1
  #7  0xb452aa28 in runQMirServerWithClient ()
 from /usr/lib/arm-linux-gnueabihf/libunity-mir.so.1
  #8  0xb1f2 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1317235/+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 1318576] Re: [K55VD, Realtek ALC270, Speaker, Internal] No sound at all - AUDIO ICON ON TOOLBAR DISAPPEARED

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [K55VD, Realtek ALC270, Speaker, Internal] No sound at all - AUDIO
  ICON ON TOOLBAR DISAPPEARED

Status in “alsa-driver” package in Ubuntu:
  Expired

Bug description:
  I'm using Ubuntu 14.10, the package is 1.0.25+dfsg-0ubuntu4. I think
  also pulseaudio is involved with this problem. It is  pulseaudio
  1:4.0-0ubuntu11. No sound is played, neither with speakers nor with
  headphones. Sometimes it works with sudo alsa force-reload but there's
  always some problem while unloading the plugin (it seems to be used by
  some process). After an uninstall and reinstall of alsa-base and
  pulseaudio my audio icon disappeared and there's no way to get audio
  back.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michele8874 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May 12 11:55:48 2014
  InstallationDate: Installed on 2013-11-18 (174 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Audio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michele8874 F pulseaudio
    michele9464 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [K55VD, Realtek ALC270, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-04-30 (12 days ago)
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55VD.411
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55VD.411:bd03/11/2013:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K55VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1318576/+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 1316305] Re: Externa subwoofer asus sonicmaster doesn't work on Asus ux51vz

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Externa subwoofer asus sonicmaster doesn't work on Asus ux51vz

Status in “alsa-driver” package in Ubuntu:
  Expired

Bug description:
  External subwoofer asus sonicmaster doesn't work on Asus ux51vz

  I also tried the configuration below, but in this way internal
  microphone doesn't work anymore

  add to /etc/modprobe.d/alsa-base.conf
  options snd-hda-intel model=asus-mode4

  add to /usr/share/pulseaudio/alsa-mixer/profile-sets/extra-hdmi.conf
  [Mapping analog-surround-21]
  device-strings = surround21:%f surround40:%f
  channel-map = front-left,front-right,lfe,lfe
  paths-output = analog-output analog-output-lineout analog-output-speaker 
analog-output-desktop-speaker
  priority = 8
  direction = output

  make sure lfe-mixing is enabled in /etc/pulse/daemon.conf
  enable-lfe-remixing = yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1316305/+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 1311403] Re: Can't type password after resume.

[NoBugs!]

Yikes, I just noticed after clicking in the upper right dropdowns, then
clicking in the password and entering password, it worked, and what I'd
previously typed was in the terminal (which had had focus)!

So this is a security 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/1311403

Title:
  Can't type password after resume.

Status in Unity:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I couldn't type password after resume - no characters displayed this
  time.

  I had to Ctrl+alt+f2 and service lightdm restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Tue Apr 22 17:37:49 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-23 (150 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1311403/+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 1283415] Re: 1px gap between launcher and dash on high-dpi screen

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.0+14.10.20140711-0ubuntu1

---
unity (7.3.0+14.10.20140711-0ubuntu1) utopic; urgency=low

  [ Eleni Maria Stea ]
  * Previews: scale the dash preview contents to match current monitor
scaling Improved also the scaling of search-bar, spinner, categories
and many other components. (LP: #1339629)

  [ Marco Trevisan (Treviño) ]
  * Previews: scale the dash preview contents to match current monitor
scaling Improved also the scaling of search-bar, spinner, categories
and many other components. (LP: #1339629)
  * DashStyle: return RawPixel's instead of integers for sizes, and
avoid duplication in code
  * FilterWidgets: add support for scaling (LP: #1340171)
  * OverlayRendering: correctly scale the overlays borders and edges to
match settings DashStyle has been modified to return smart pointers
of textures that are loaded depending on the scale level. The cache
will make sure that we don't duplicate the textures and that they
get removed when not needed anymore. Also thanks to this the
SearchBarSpinner textures (and the other spinners as well) uses the
SVGs scaled at the proper size (I desgined a new SVG for the
magnifier, as we only had a PNG). (LP: #1283415)
  * Hud: scale to match current DPI settings for monitor (LP: #1340477)
 -- Ubuntu daily releaseFri, 11 Jul 2014 
19:59:35 +

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

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

Title:
  1px gap between launcher and dash on high-dpi screen

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  There is a 1px gap between the launcher and the dash.

  org.gnome.desktop.interface.scaling-factor = 2
  org.gnome.desktop.interface.text-scaling-factor = 1.0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.2-0ubuntu5
  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: Sat Feb 22 12:41:11 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-02-02 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Feb 22 12:08:14 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16970 
   vendor SDC
  xserver.version: 2:1.15.0-1ubuntu6

To manage

[Touch-packages] [Bug 1339629] Re: Dash Previews don't scale correctly when the scale factor changes

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.0+14.10.20140711-0ubuntu1

---
unity (7.3.0+14.10.20140711-0ubuntu1) utopic; urgency=low

  [ Eleni Maria Stea ]
  * Previews: scale the dash preview contents to match current monitor
scaling Improved also the scaling of search-bar, spinner, categories
and many other components. (LP: #1339629)

  [ Marco Trevisan (Treviño) ]
  * Previews: scale the dash preview contents to match current monitor
scaling Improved also the scaling of search-bar, spinner, categories
and many other components. (LP: #1339629)
  * DashStyle: return RawPixel's instead of integers for sizes, and
avoid duplication in code
  * FilterWidgets: add support for scaling (LP: #1340171)
  * OverlayRendering: correctly scale the overlays borders and edges to
match settings DashStyle has been modified to return smart pointers
of textures that are loaded depending on the scale level. The cache
will make sure that we don't duplicate the textures and that they
get removed when not needed anymore. Also thanks to this the
SearchBarSpinner textures (and the other spinners as well) uses the
SVGs scaled at the proper size (I desgined a new SVG for the
magnifier, as we only had a PNG). (LP: #1283415)
  * Hud: scale to match current DPI settings for monitor (LP: #1340477)
 -- Ubuntu daily releaseFri, 11 Jul 2014 
19:59:35 +

** Changed in: unity (Ubuntu)
   Status: New => Fix Released

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

Title:
  Dash Previews don't scale correctly when the scale factor changes

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  When the user performs a dash search and right clicks a result, the Preview 
is always rendered with scale factor 1.0.
  We should fix the scaling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1339629/+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 1340477] Re: The HUD doesn't support scaling on HiDPI monitors

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.0+14.10.20140711-0ubuntu1

---
unity (7.3.0+14.10.20140711-0ubuntu1) utopic; urgency=low

  [ Eleni Maria Stea ]
  * Previews: scale the dash preview contents to match current monitor
scaling Improved also the scaling of search-bar, spinner, categories
and many other components. (LP: #1339629)

  [ Marco Trevisan (Treviño) ]
  * Previews: scale the dash preview contents to match current monitor
scaling Improved also the scaling of search-bar, spinner, categories
and many other components. (LP: #1339629)
  * DashStyle: return RawPixel's instead of integers for sizes, and
avoid duplication in code
  * FilterWidgets: add support for scaling (LP: #1340171)
  * OverlayRendering: correctly scale the overlays borders and edges to
match settings DashStyle has been modified to return smart pointers
of textures that are loaded depending on the scale level. The cache
will make sure that we don't duplicate the textures and that they
get removed when not needed anymore. Also thanks to this the
SearchBarSpinner textures (and the other spinners as well) uses the
SVGs scaled at the proper size (I desgined a new SVG for the
magnifier, as we only had a PNG). (LP: #1283415)
  * Hud: scale to match current DPI settings for monitor (LP: #1340477)
 -- Ubuntu daily releaseFri, 11 Jul 2014 
19:59:35 +

** Changed in: unity (Ubuntu)
   Status: New => Fix Released

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

Title:
  The HUD doesn't support scaling on HiDPI monitors

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  The HUD is not scaled in HiDPI monitors

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1340477/+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 1340171] Re: Dash filters don't scale up/down to match the current monitor scale factor

[Launchpad Bug Tracker]

This bug was fixed in the package unity - 7.3.0+14.10.20140711-0ubuntu1

---
unity (7.3.0+14.10.20140711-0ubuntu1) utopic; urgency=low

  [ Eleni Maria Stea ]
  * Previews: scale the dash preview contents to match current monitor
scaling Improved also the scaling of search-bar, spinner, categories
and many other components. (LP: #1339629)

  [ Marco Trevisan (Treviño) ]
  * Previews: scale the dash preview contents to match current monitor
scaling Improved also the scaling of search-bar, spinner, categories
and many other components. (LP: #1339629)
  * DashStyle: return RawPixel's instead of integers for sizes, and
avoid duplication in code
  * FilterWidgets: add support for scaling (LP: #1340171)
  * OverlayRendering: correctly scale the overlays borders and edges to
match settings DashStyle has been modified to return smart pointers
of textures that are loaded depending on the scale level. The cache
will make sure that we don't duplicate the textures and that they
get removed when not needed anymore. Also thanks to this the
SearchBarSpinner textures (and the other spinners as well) uses the
SVGs scaled at the proper size (I desgined a new SVG for the
magnifier, as we only had a PNG). (LP: #1283415)
  * Hud: scale to match current DPI settings for monitor (LP: #1340477)
 -- Ubuntu daily releaseFri, 11 Jul 2014 
19:59:35 +

** Changed in: unity (Ubuntu)
   Status: New => Fix Released

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

Title:
  Dash filters don't scale up/down to match the current monitor scale
  factor

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Scale filters need scaling support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1340171/+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 1263540] Re: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg.

[leoheck]

I am having this problem too. Did someone already found the solution?

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

Title:
  Apt-get reports NO_PUBKEY gpg error for keys that are present in
  trusted.gpg.

Status in APT:
  New
Status in “apt” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 13.10
  apt  0.9.9.1~ubuntu3

  'apt-get update' has started showing several warnings like the
  following, even though the keys are present:

  W: GPG error: http://us.archive.ubuntu.com saucy Release: The
  following signatures couldn't be verified because the public key is
  not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32

  'apt-key list' shows the keys in question in its output...

  pub   1024D/437D05B5 2004-09-12
  uid  Ubuntu Archive Automatic Signing Key 

  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
  uid  Ubuntu Archive Automatic Signing Key (2012) 


  ...and its output begins with the following:

  gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-y-ppa-
  manager.gpg': resource limit

  I see the same gpg message when I manually update/remove/add the keys
  in question. E.g.:

  $ sudo apt-key update
  gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-java.gpg': 
resource limit
  gpg: keyblock resource 
`/etc/apt/trusted.gpg.d//webupd8team-y-ppa-manager.gpg': resource limit
  gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key 
" not changed
  gpg: key FBB75451: "Ubuntu CD Image Automatic Signing Key 
" not changed
  gpg: key C0B21F32: "Ubuntu Archive Automatic Signing Key (2012) 
" not changed
  gpg: key EFE21092: "Ubuntu CD Image Automatic Signing Key (2012) 
" not changed
  gpg: Total number processed: 4
  gpg:  unchanged: 4

  I asked about the "resource limit" message on the gnupg-users mailing list...
  http://www.mail-archive.com/gnupg-users@gnupg.org/msg23300.html
  Based on Werner Koch's (the dev) answer...
  http://www.mail-archive.com/gnupg-users@gnupg.org/msg23302.html
  ...the secure apt related programs might be making gpg use more than the 
maximum number of keyrings that it can handle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1263540/+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 1340448] Re: 5% reservation for root is inappropriate for large disks/arrays

[Dimitri John Ledkov]

This is not the only place where %-only based metric is not appropriate
for all sizes, the other one being default swap size is a simple
multiple of RAM still, despite extreme cases of RAM >> HDD (in e.g.
high-mem VM cases) and very fast HDD (e.g. NVMe drives or RAID-arrays
speed up with SSD cache layers).

Adding in that as well can eat up a lot of disk space, and at times even
expensive one.

Whilst we all agree that performance does degrade at the extremely full
disk-space, I don't buy that 51GB of free disk-space is degraded
performance given an e.g. RAID1 1TB filesystem and typical file-sizes /
extends. I'll poke cking, to check if he has performance degradation
results for various file-systems w.r.t. % filled for various max sizes.

5% is sensible and appropriate for a wide distribution of filesystem
sizes, but tiny disks may want more reserve and ditto large disks may
want less. Thus the calculated reserve shouldn't be a linear 5%, but
some non-linear distribution or scaled value.

One reasonable distribution algorithm for scaling disk-space limits (in
the context of nagios warning/critical levels monitoring) that I have
seen is implemented in checkmk project https://mathias-
kettner.de/checkmk_filesystems.html#H1:The df magic number . However,
the margins there increase too rapidly at the small disk-space sizes.
Thus further tweaking and/or different distributions would be needed.

Theodore, would you be open to having a tune option to make reserve
level adaptive rather than static %? (default would be static)

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

Title:
  5% reservation for root is inappropriate for large disks/arrays

Status in “e2fsprogs” package in Ubuntu:
  Confirmed

Bug description:
  mke2fs (and it's ext3 and ext4 analogs) still default to reserving 5%
  of the filesystem for root.  With the size of modern disks and arrays
  this isn't a terribly sensible default, e.g. if I have a 10Tb array,
  mke2fs will reserve 500Gb for root.

  Obviously this is both tunable at FS creation time and fixable after
  the fact but I still think we should try and improve the defaults.

  Given the size of modern disks, I think it'd make sense to either a)
  only reserve a smaller amount (e.g. 1%) or b) reserve n% if the
  filesystem is << NNN GB and otherwise reserve NN GB.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1340448/+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 1173952] Re: Suspend and hibernate not working in 13.04/13.10 with alx module

[pqwoerituytrueiwoq]

@azm1 sounds like the system is using the S1 or maybe S2 state to me,
not the usual S3 state, check your bios setting for the type of suspend

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

Title:
  Suspend and hibernate not working in 13.04/13.10 with alx module

Status in “linux” package in Ubuntu:
  Confirmed
Status in “pm-utils” package in Ubuntu:
  Fix Released
Status in “linux” source package in Precise:
  Won't Fix
Status in “pm-utils” source package in Precise:
  Invalid
Status in “linux” source package in Raring:
  Won't Fix
Status in “pm-utils” source package in Raring:
  Fix Released
Status in “linux” source package in Saucy:
  Fix Released
Status in “pm-utils” source package in Saucy:
  Fix Released

Bug description:
  Description:  Ubuntu 13.04
  Release:  13.04

  After upgrading to 13.04 suspend and hibernate do not work.
  In terminal window following error is displayed: "PM: Some devices failed to 
suspend". Then the suspend fails and the screensaver gets activated, requiring 
a password to unlock.

  dmesg

  [  893.962025] PM: Syncing filesystems ... done.
  [  894.030726] Freezing user space processes ... (elapsed 0.01 seconds) done.
  [  894.047580] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) 
done.
  [  894.064140] Suspending console(s) (use no_console_suspend to debug)
  [  894.071511] sd 0:0:0:0: [sda] Synchronizing SCSI cache
  [  894.085881] alx :03:00.0: PHY SPD/DPLX unresolved :
  [  894.085884] alx :03:00.0 eth1: shutown err(ffea)
  [  894.085886] alx :03:00.0: shutdown fail in suspend -5
  [  894.085901] pci_pm_suspend(): alx_suspend+0x0/0x90 [alx] returns -5
  [  894.085906] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -5
  [  894.085908] PM: Device :03:00.0 failed to suspend async: error -5
  [  894.47] sd 0:0:0:0: [sda] Stopping disk
  [  894.684692] PM: Some devices failed to suspend
  [  894.684903] ath: phy0: ASPM enabled: 0x43
  [  894.685198] sd 0:0:0:0: [sda] Starting disk
  [  895.442853] PM: resume of devices complete after 758.396 msecs
  [  895.443224] Restarting tasks ... done.
  [  895.445509] video LNXVIDEO:00: Restoring backlight state
  ---
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  DistroRelease: Ubuntu 13.04
  InstallationDate: Installed on 2012-12-20 (166 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  Package: pm-utils 1.4.1-9git1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Tags:  raring
  Uname: Linux 3.8.0-19-generic x86_64
  UpgradeStatus: Upgraded to raring on 2013-04-28 (37 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

  SRU INFORMATION
  ---
  * Impact: suspend regression in 13.04 with Qualcomm Atheros Gigabit ethernet 
devices
  * Test case: Suspend is broken in current raring when the alx module is 
loaded, should work again with the fix; needs to be tested on actual hardware, 
see comment 56 for positive testing result that this pm-utils workaround works.
  * Regression potential: If the script is malformed, it could potentially 
break suspend on other devices; this should generate an error in 
/var/log/pm-suspend.log. Please test suspend on devices without the alx module 
as well (for the record, Martin Pitt did that on his ThinkPad X201)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173952/+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 1340984] Re: libav-tools unpacks with dpkg errors

[Reinhard Tartler]

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

it's actually not a regression, it's a duplicate. I'll see that I fix
#1315672 soon. marking as duplicate for now

** This bug has been marked a duplicate of bug 1315672
   Installation of libav-tools produces dpkg error

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

Title:
  libav-tools unpacks with dpkg errors

Status in “libav” package in Ubuntu:
  New

Bug description:
  Installing libav-tools on utopic produces a dpkg error. Perhaps a
  regression of
  https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1315672

  Preparing to unpack .../libav-tools_6%3a9.11-2ubuntu3_amd64.deb ...
  dpkg: error: --compare-versions takes three arguments:   


  Type dpkg --help for help about installing and deinstalling packages [*];
  Use 'apt' or 'aptitude' for user-friendly package management;
  Type dpkg -Dhelp for a list of dpkg debug flag values;
  Type dpkg --force-help for a list of forcing options;
  Type dpkg-deb --help for help about manipulating *.deb files;

  Options marked [*] produce a lot of output - pipe it through 'less' or 'more' 
!
  Unpacking libav-tools (6:9.11-2ubuntu3) ...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libav-tools 6:9.11-2ubuntu3
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 11 18:00:57 2014
  InstallationDate: Installed on 2013-12-19 (204 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131218)
  SourcePackage: libav
  UpgradeStatus: Upgraded to utopic on 2014-05-09 (63 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1340984/+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 1323426] Re: HP Z8000 bluetooth mouse

[Launchpad Bug Tracker]

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

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

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

Title:
  HP Z8000 bluetooth mouse

Status in “bluez” package in Ubuntu:
  Confirmed

Bug description:
  This mouse is a HID over GAT recent HP low power mouse.

  It  is recognized as ALL types bluetooth peripherals not as a mouse!

  The mouse at the end of the installation process (automatic pin
  selection) results as PAIRED  but the connection option is not
  available in the bluetooth setting dialog.

  UBUNTU is last 14.04 full updated at filing bug time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1323426/+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 1340991] Re: [VPCZ11QGX, Realtek ALC889, Speaker, Internal] No sound at all

[Mjpatey]

Thank you for the info! My apologies in advance for my lack of
knowledge... but I'm just a regular user and don't know what to do with
that info. Is there a config file somewhere that I should paste the
chunk of text into?

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

Title:
  [VPCZ11QGX, Realtek ALC889, Speaker, Internal] No sound at all

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  This *may* be related to Bug #960124, which looks similar. But I
  didn't want to assume that, since I am running a different version of
  Ubuntu (13.10), and the computer is a Sony VPC-Z11QGX/S.

  alsa-base:
Installed: 1.0.25+dfsg-0ubuntu4
Candidate: 1.0.25+dfsg-0ubuntu4
Version table:
   *** 1.0.25+dfsg-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status
  pulseaudio:
Installed: 1:4.0-0ubuntu6
Candidate: 1:4.0-0ubuntu6
Version table:
   *** 1:4.0-0ubuntu6 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  Audio does indeed play through the headphones, but does not play at
  all through the main speakers.

  I have force-reloaded ALSA, as well as purging and reinstalling alsa-
  base and pulseaudio, just in case something had gotten out of whack.
  But this has not had any effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-24.42-generic 3.11.10.11
  Uname: Linux 3.11.0-24-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mjpatey2037 F pulseaudio
   /dev/snd/controlC0:  mjpatey2037 F pulseaudio
  Date: Fri Jul 11 17:57:52 2014
  InstallationDate: Installed on 2014-07-06 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mjpatey2037 F pulseaudio
   /dev/snd/controlC0:  mjpatey2037 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [VPCZ11QGX, Realtek ALC889, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R3031C3
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR3031C3:bd10/04/2011:svnSonyCorporation:pnVPCZ11QGX:pvrR5964106:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCZ11QGX
  dmi.product.version: R5964106
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1340991/+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 1338730] Re: Store does nothing when no-internet flag is enabled

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/utopic-proposed/unity-scope-click

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

Title:
  Store does nothing when no-internet flag is enabled

Status in “unity-scope-click” package in Ubuntu:
  Fix Committed

Bug description:
  When the setting to not include network results in scopes is enabled,
  the store scope will show no results. This made some sense when we had
  a single scope that was for installed and available apps, but with the
  split into two scopes, one must explicitly go to the store scope to
  get those automatic network results.

  However, we may need to obey this flag, when searching in the
  installed apps scope, and avoid showing store results when searching
  there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1338730/+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 996906] Re: periodic audio skips with Intel HDA

[Raymond]

ANY reason to set latency to 1ms interval when you are using 44100Hz
since 1ms contain 44.1 samples ?

you need at least 10 ms interval

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

Title:
  periodic audio skips with Intel HDA

Status in PulseAudio sound server:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  When running PulseAudio, if I'm playing music via any source (Exaile, Totem,
  Flash in Firefox or Chromium, VLC, etc.) every few minutes the audio will skip
  once or twice.  top doesn't show any process eating CPU any more when it
  happens.  dmesg doesn't show anything.  Nothing else seems to be affected.  It
  doesn't seem to happen regularly.

  I just installed Ubuntu 12.04 from scratch (with pulseaudio 1:1.1-0ubuntu15),
  but the same thing happened in 10.04 on the same hardware.  Uninstalling the
  PulseAudio packages and going back to ALSA gives me no issues whatsoever, 
which
  is how I know the issue is with PulseAudio.  I'm using my onboard audio 
device:

  $ lspci | grep Audio
  00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel
  HDA)

  Following mailing list instructions, pulseaudio - --log-time shows during 
a
  skip:

  ( 684.030|   5.000) I: [alsa-sink] alsa-sink.c: Underrun!
  ( 684.030|   0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to
  26.00 ms
  ( 684.030|   0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms
  ( 684.030|   0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952
  ( 684.030|   0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944
  ( 684.030|   0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms
  ( 684.030|   0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952
  ( 684.030|   0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944
  ( 684.031|   0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA
  Playback', 0 bytes in queue.
  ( 684.036|   0.004) D: [alsa-sink] protocol-native.c: Requesting rewind due to
  end of underrun.
  ( 684.036|   0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 10940
  bytes.
  ( 684.036|   0.000) D: [alsa-sink] alsa-sink.c: Limited to 3320 bytes.
  ( 684.036|   0.000) D: [alsa-sink] alsa-sink.c: before: 830
  ( 684.036|   0.000) D: [alsa-sink] alsa-sink.c: after: 830
  ( 684.036|   0.000) D: [alsa-sink] alsa-sink.c: Rewound 3320 bytes.
  ( 684.036|   0.000) D: [alsa-sink] sink.c: Processing rewind...
  ( 684.036|   0.000) D: [alsa-sink] sink.c: latency = 1337
  ( 684.036|   0.000) D: [alsa-sink] sink-input.c: Have to rewind 3320 bytes on
  render memblockq.
  ( 684.036|   0.000) D: [alsa-sink] source.c: Processing rewind...
  ( 696.234|  12.197) I: [alsa-sink] alsa-sink.c: Underrun!
  ( 696.234|   0.000) I: [alsa-sink] alsa-sink.c: Increasing wakeup watermark to
  15.99 ms
  ( 702.033|   5.799) I: [alsa-sink] alsa-sink.c: Underrun!
  ( 702.033|   0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to
  36.00 ms
  ( 702.033|   0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms
  ( 702.033|   0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188
  ( 702.033|   0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680
  ( 702.033|   0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms
  ( 702.034|   0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188
  ( 702.034|   0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680
  ( 702.034|   0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA
  Playback', 0 bytes in queue.

  ...and it goes on.

  The "Underrun!" messages alone happened a few times before, but it
  didn't skip.

  I'd like to use PulseAudio, but it's pretty annoying having audio skip all the
  time.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  toxite 2136 F pulseaudio
   /dev/snd/pcmC0D0p:   toxite 2136 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
 Mixer name : 'Realtek ALC889'
 Components : 'HDA:10ec0889,1458a102,0014'
 Controls  : 48
 Simple ctrls  : 22
  Date: Tue May  8 21:45:17 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-790FXTA-UD5
  dm

[Touch-packages] [Bug 1340991] Re: [VPCZ11QGX, Realtek ALC889, Speaker, Internal] No sound at all

[Raymond]

you can use SND_HDA_PIN_QUIRK for all Sony notebook with alc889 and

sys/class/sound/hwC0D0/init_pin_configs:
0x11 0x41f0
0x12 0x90a60120
0x14 0x90170110
0x15 0x0421101f
0x16 0x41f0
0x17 0x41f0
0x18 0x04a1102e
0x19 0x04a11030
0x1a 0x41f0
0x1b 0x41f0
0x1c 0x41f0
0x1d 0x41f0
0x1e 0x41f0
0x1f 0x41f0

to use the same fix in Bug #960124 similar to

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_realtek.c?id=76c2132ec9805120eb724cae4d2a8d30af27b3fd

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

Title:
  [VPCZ11QGX, Realtek ALC889, Speaker, Internal] No sound at all

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  This *may* be related to Bug #960124, which looks similar. But I
  didn't want to assume that, since I am running a different version of
  Ubuntu (13.10), and the computer is a Sony VPC-Z11QGX/S.

  alsa-base:
Installed: 1.0.25+dfsg-0ubuntu4
Candidate: 1.0.25+dfsg-0ubuntu4
Version table:
   *** 1.0.25+dfsg-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status
  pulseaudio:
Installed: 1:4.0-0ubuntu6
Candidate: 1:4.0-0ubuntu6
Version table:
   *** 1:4.0-0ubuntu6 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  Audio does indeed play through the headphones, but does not play at
  all through the main speakers.

  I have force-reloaded ALSA, as well as purging and reinstalling alsa-
  base and pulseaudio, just in case something had gotten out of whack.
  But this has not had any effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-24.42-generic 3.11.10.11
  Uname: Linux 3.11.0-24-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mjpatey2037 F pulseaudio
   /dev/snd/controlC0:  mjpatey2037 F pulseaudio
  Date: Fri Jul 11 17:57:52 2014
  InstallationDate: Installed on 2014-07-06 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mjpatey2037 F pulseaudio
   /dev/snd/controlC0:  mjpatey2037 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [VPCZ11QGX, Realtek ALC889, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R3031C3
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR3031C3:bd10/04/2011:svnSonyCorporation:pnVPCZ11QGX:pvrR5964106:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCZ11QGX
  dmi.product.version: R5964106
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1340991/+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 1341030] [NEW] Store card does not repeat searches from the Apps scope

[Alejandro J. Cura]

Public bug reported:

The orange card named "Ubuntu Store" is not working right when the user
has performed a search in the Apps scope, and the category is showing
"Search for 'X' in the store".

The card leads to the Ubuntu Store, but the search is not repeated.

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

** Description changed:

- The orange card named "Ubuntu Store" is not working right when the user has 
performed a search in the Apps scope.
- It leads to the Ubuntu Store, but the search is not repeated.
+ The orange card named "Ubuntu Store" is not working right when the user
+ has performed a search in the Apps scope, and the category is showing
+ "Search for 'X' in the store".
+ 
+ The card leads to the Ubuntu Store, but the search is not repeated.

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

Title:
  Store card does not repeat searches from the Apps scope

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

Bug description:
  The orange card named "Ubuntu Store" is not working right when the
  user has performed a search in the Apps scope, and the category is
  showing "Search for 'X' in the store".

  The card leads to the Ubuntu Store, but the search is not repeated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1341030/+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 996906] Re: periodic audio skips with Intel HDA

[Charles Lindsay]

I finally upgraded to 14.04; same exact issue.

One coincidence I noticed and am looking into is that I didn't notice
any stuttering when only 64 bit code was running, but when flash or
steam were running (both of which run some 32 bit code, if I'm not
mistaken), the stuttering began immediately.  I'm not 100% sure that's
the only time it stutters now, but it's happened enough times that I'm
not sure it's just coincidence.  Does that ring any bells for anyone?

I'm sick and tired of this issue.  Ubuntu has moved on from Alsa, and
I'd like to too.  I might get a (hopefully cheap) sound card to test out
if that can fix the issue.

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

Title:
  periodic audio skips with Intel HDA

Status in PulseAudio sound server:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  When running PulseAudio, if I'm playing music via any source (Exaile, Totem,
  Flash in Firefox or Chromium, VLC, etc.) every few minutes the audio will skip
  once or twice.  top doesn't show any process eating CPU any more when it
  happens.  dmesg doesn't show anything.  Nothing else seems to be affected.  It
  doesn't seem to happen regularly.

  I just installed Ubuntu 12.04 from scratch (with pulseaudio 1:1.1-0ubuntu15),
  but the same thing happened in 10.04 on the same hardware.  Uninstalling the
  PulseAudio packages and going back to ALSA gives me no issues whatsoever, 
which
  is how I know the issue is with PulseAudio.  I'm using my onboard audio 
device:

  $ lspci | grep Audio
  00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel
  HDA)

  Following mailing list instructions, pulseaudio - --log-time shows during 
a
  skip:

  ( 684.030|   5.000) I: [alsa-sink] alsa-sink.c: Underrun!
  ( 684.030|   0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to
  26.00 ms
  ( 684.030|   0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms
  ( 684.030|   0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952
  ( 684.030|   0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944
  ( 684.030|   0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms
  ( 684.030|   0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952
  ( 684.030|   0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944
  ( 684.031|   0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA
  Playback', 0 bytes in queue.
  ( 684.036|   0.004) D: [alsa-sink] protocol-native.c: Requesting rewind due to
  end of underrun.
  ( 684.036|   0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 10940
  bytes.
  ( 684.036|   0.000) D: [alsa-sink] alsa-sink.c: Limited to 3320 bytes.
  ( 684.036|   0.000) D: [alsa-sink] alsa-sink.c: before: 830
  ( 684.036|   0.000) D: [alsa-sink] alsa-sink.c: after: 830
  ( 684.036|   0.000) D: [alsa-sink] alsa-sink.c: Rewound 3320 bytes.
  ( 684.036|   0.000) D: [alsa-sink] sink.c: Processing rewind...
  ( 684.036|   0.000) D: [alsa-sink] sink.c: latency = 1337
  ( 684.036|   0.000) D: [alsa-sink] sink-input.c: Have to rewind 3320 bytes on
  render memblockq.
  ( 684.036|   0.000) D: [alsa-sink] source.c: Processing rewind...
  ( 696.234|  12.197) I: [alsa-sink] alsa-sink.c: Underrun!
  ( 696.234|   0.000) I: [alsa-sink] alsa-sink.c: Increasing wakeup watermark to
  15.99 ms
  ( 702.033|   5.799) I: [alsa-sink] alsa-sink.c: Underrun!
  ( 702.033|   0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to
  36.00 ms
  ( 702.033|   0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms
  ( 702.033|   0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188
  ( 702.033|   0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680
  ( 702.033|   0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms
  ( 702.034|   0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188
  ( 702.034|   0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680
  ( 702.034|   0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA
  Playback', 0 bytes in queue.

  ...and it goes on.

  The "Underrun!" messages alone happened a few times before, but it
  didn't skip.

  I'd like to use PulseAudio, but it's pretty annoying having audio skip all the
  time.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  toxite 2136 F pulseaudio
   /dev/snd/pcmC0D0p:   toxite 2136 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
 Mixer name : 'Realtek ALC889'
 Components : 'HDA:10ec0889,1458a102,00

[Touch-packages] [Bug 1341022] [NEW] [Latitude E7240, Realtek ALC292, Mic, Internal] Internal Mic not visible

[Dan Poler]

Public bug reported:

Sound Settings panel shows "Headset microphone" and "Dock microphone".
Headset when plugged in works fine (the little dialogue pops up etc).
Internal microphone is not visible anywhere within the GUI.

alsamixer "sees" the internal microphone and I can adjust its levels but
this does not affect the desktop environment.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  dpoler 2022 F pulseaudio
 /dev/snd/controlC0:  dpoler 2022 F pulseaudio
CurrentDesktop: Unity
Date: Fri Jul 11 17:48:09 2014
InstallationDate: Installed on 2014-07-11 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Mic, Internal
Symptom_Type: Only some of inputs are working
Title: [Latitude E7240, Realtek ALC292, Mic, Internal] Recording problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0414F8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/05/2013:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn0414F8:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7240
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  [Latitude E7240, Realtek ALC292, Mic, Internal] Internal Mic not
  visible

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  Sound Settings panel shows "Headset microphone" and "Dock microphone".
  Headset when plugged in works fine (the little dialogue pops up etc).
  Internal microphone is not visible anywhere within the GUI.

  alsamixer "sees" the internal microphone and I can adjust its levels
  but this does not affect the desktop environment.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dpoler 2022 F pulseaudio
   /dev/snd/controlC0:  dpoler 2022 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul 11 17:48:09 2014
  InstallationDate: Installed on 2014-07-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: Only some of inputs are working
  Title: [Latitude E7240, Realtek ALC292, Mic, Internal] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0414F8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/05/2013:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn0414F8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1341022/+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 1340991] Re: [VPCZ11QGX, Realtek ALC889, Speaker, Internal] No sound at all

[Raymond]

6.710324] WARNING: CPU: 3 PID: 431 at 
/build/buildd/linux-3.11.0/drivers/gpu/drm/i915/intel_display.c:822 
intel_wait_for_pipe_off+0xfb/0x1c0 [i915]()
[6.710325] pipe_off wait timed out
[6.710371] Modules linked in: intel_powerclamp coretemp kvm arc4 
crct10dif_pclmul crc32_pclmul iwldvm ghash_clmulni_intel aesni_intel mac80211 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev rfcomm bnep 
bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops snd_hda_intel(+) 
videobuf2_core ses videodev snd_hda_codec enclosure snd_hwdep nouveau(+) 
snd_pcm microcode snd_page_alloc snd_seq_midi psmouse snd_seq_midi_event 
i915(+) iwlwifi snd_rawmidi serio_raw intel_ips mxm_wmi snd_seq ttm 
snd_seq_device drm_kms_helper cfg80211 snd_timer drm snd i2c_algo_bit mac_hid 
mei_me soundcore mei lpc_ich sony_laptop wmi video lp parport usb_storage 
hid_generic usbhid hid ahci e1000e libahci sdhci_pci ptp sdhci pps_core
[6.710375] CPU: 3 PID: 431 Comm: systemd-udevd Not tainted 
3.11.0-24-generic #42-Ubuntu
[6.710376] Hardware name: Sony Corporation VPCZ11QGX/VAIO, BIOS R3031C3 
10/04/2011
[6.710380]  0009 8801501cd2c0 816e9d61 
8801501cd308
[6.710383]  8801501cd2f8 81061e2d 00070008 
88014fe94000
[6.710386]  fffee175 8801501cdfd8 88014ec8c470 
8801501cd358
[6.710387] Call Trace:
[6.710394]  [] dump_stack+0x45/0x56
[6.710400]  [] warn_slowpath_common+0x7d/0xa0
[6.710402]  [] warn_slowpath_fmt+0x4c/0x50
[6.710424]  [] ? i915_read32+0x66/0x140 [i915]
[6.710449]  [] intel_wait_for_pipe_off+0xfb/0x1c0 [i915]
[6.710474]  [] intel_disable_pipe+0x8d/0xa0 [i915]
[6.710499]  [] ironlake_crtc_disable+0xd6/0x8c0 [i915]
[6.710526]  [] __intel_set_mode+0x314/0x880 [i915]
[6.710530]  [] ? list_locations+0x12f/0x4a0
[6.710556]  [] intel_set_mode+0x16/0x30 [i915]
[6.710582]  [] intel_crtc_set_config+0x742/0x920 [i915]
[6.710602]  [] drm_mode_set_config_internal+0x5d/0xe0 
[drm]
[6.710610]  [] drm_fb_helper_set_par+0x71/0xf0 
[drm_kms_helper]
[6.710614]  [] fbcon_init+0x504/0x580
[6.710618]  [] visual_init+0xba/0x120
[6.710621]  [] do_bind_con_driver+0x163/0x330
[6.710624]  [] do_take_over_console+0x114/0x1c0
[6.710627]  [] do_fbcon_takeover+0x63/0xd0
[6.710630]  [] fbcon_event_notify+0x6dd/0x830
[6.710633]  [] notifier_call_chain+0x4c/0x70
[6.710637]  [] __blocking_notifier_call_chain+0x4d/0x70
[6.710640]  [] blocking_notifier_call_chain+0x16/0x20
[6.710644]  [] fb_notifier_call_chain+0x1b/0x20
[6.710647]  [] register_framebuffer+0x1dd/0x310
[6.710653]  [] drm_fb_helper_initial_config+0x32f/0x510 
[drm_kms_helper]
[6.710659]  [] ? default_spin_lock_flags+0x9/0x10
[6.710689]  [] intel_fbdev_initial_config+0x21/0x30 [i915]
[6.710710]  [] i915_driver_load+0xdc1/0xdf0 [i915]
[6.710743]  [] drm_get_pci_dev+0x166/0x2c0 [drm]
[6.710764]  [] i915_pci_probe+0x2c/0x70 [i915]
[6.710768]  [] local_pci_probe+0x3e/0x70
[6.710771]  [] pci_device_probe+0x121/0x130
[6.710777]  [] driver_probe_device+0x90/0x3d0
[6.710780]  [] __driver_attach+0x93/0xa0
[6.710783]  [] ? __device_attach+0x40/0x40
[6.710785]  [] bus_for_each_dev+0x63/0xa0
[6.710788]  [] driver_attach+0x1e/0x20
[6.710790]  [] bus_add_driver+0x1e8/0x2a0
[6.710795]  [] ? 0xa0334fff
[6.710798]  [] driver_register+0x74/0x150
[6.710802]  [] ? 0xa0334fff
[6.710805]  [] __pci_register_driver+0x4c/0x50
[6.710819]  [] drm_pci_init+0x11a/0x130 [drm]
[6.710822]  [] ? 0xa0334fff
[6.710843]  [] i915_init+0x66/0x68 [i915]
[6.710847]  [] do_one_initcall+0xfa/0x1b0
[6.710851]  [] ? set_memory_nx+0x43/0x50
[6.710857]  [] load_module+0x12bb/0x1b80
[6.710860]  [] ? store_uevent+0x40/0x40
[6.710866]  [] SyS_init_module+0xa2/0xf0
[6.710871]  [] system_call_fastpath+0x1a/0x1f
[6.710872] ---[ end trace 0e7a820a1a22f105 ]---
[7.497982] Console: switching to colour frame buffer device 180x56
[7.502286] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[7.502287] i915 :00:02.0: registered panic notifier
[7.540166] acpi device:01: registered as cooling_device5
[7.540266] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[7.540338] input: Video Bus as 
/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input8
[7.541564] acpi device:06: registered as cooling_device6
[7.541623] ACPI: Video Device [DGPU] (multi-head: yes  rom: yes  post: no)
[7.541696] input: Video Bus as 
/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:05/LNXVIDEO:01/input/input9
[7.544709] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0
[7.546208] snd_hda_intel :00:1b.0: irq 46 for MSI/MSI-X
[7.546510] nouveau  [  DEVICE][:01:00.0] BOOT0  : 0x0a5580a2
[7.546515] nouveau  [  DEVICE][:01:00.0] Chipset: GT216 (NV

[Touch-packages] [Bug 1235446] Re: evolution-calendar-factory crashed with SIGSEGV in socket_connected()

[Apport retracing service]

** Tags added: trusty

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

Title:
  evolution-calendar-factory crashed with SIGSEGV in socket_connected()

Status in “evolution-data-server” package in Ubuntu:
  Triaged
Status in “evolution-data-server” package in Fedora:
  Unknown

Bug description:
  lets the retracer decide if this is a dupe.

  It happens right at login, without doing anything special regarding
  calendar.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: evolution-data-server 3.8.5-1ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Fri Oct  4 22:23:08 2013
  ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
  InstallationDate: Installed on 2012-03-31 (552 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120331)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=de_DE
   PATH=(custom, user)
   LANG=de_DE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f89cedcbc13:mov0x90(%rax),%rdi
   PC (0x7f89cedcbc13) ok
   source "0x90(%rax)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
   soup_socket_connect_sync () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
  Title: evolution-calendar-factory crashed with SIGSEGV in 
soup_socket_connect_sync()
  UpgradeStatus: Upgraded to saucy on 2013-09-28 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1235446/+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 1341016] Re: evolution-calendar-factory crashed with SIGSEGV in soup_socket_connect_sync()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1235446, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1341016/+attachment/4150787/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1341016/+attachment/4150789/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1341016/+attachment/4150791/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1341016/+attachment/4150792/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1341016/+attachment/4150793/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1341016/+attachment/4150794/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1341016/+attachment/4150795/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1235446
   evolution-calendar-factory crashed with SIGSEGV in socket_connected()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  evolution-calendar-factory crashed with SIGSEGV in
  soup_socket_connect_sync()

Status in “evolution-data-server” package in Ubuntu:
  New

Bug description:
  I added a caldav share and resumed from suspend

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution-data-server 3.10.4-0ubuntu1.1
  Uname: Linux 3.14.0-031400rc4-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul 11 13:03:18 2014
  ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
  InstallationDate: Installed on 2014-01-22 (170 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
  SegvAnalysis:
   Segfault happened at: 0x7fd1688a5263:mov0x90(%rax),%rdi
   PC (0x7fd1688a5263) ok
   source "0x90(%rax)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
   soup_socket_connect_sync () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
  Title: evolution-calendar-factory crashed with SIGSEGV in 
soup_socket_connect_sync()
  UpgradeStatus: Upgraded to trusty on 2014-07-01 (10 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1341016/+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 1340991] [NEW] [VPCZ11QGX, Realtek ALC889, Speaker, Internal] No sound at all

[Mjpatey]

Public bug reported:

This *may* be related to Bug #960124, which looks similar. But I didn't
want to assume that, since I am running a different version of Ubuntu
(13.10), and the computer is a Sony VPC-Z11QGX/S.

alsa-base:
  Installed: 1.0.25+dfsg-0ubuntu4
  Candidate: 1.0.25+dfsg-0ubuntu4
  Version table:
 *** 1.0.25+dfsg-0ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
100 /var/lib/dpkg/status
pulseaudio:
  Installed: 1:4.0-0ubuntu6
  Candidate: 1:4.0-0ubuntu6
  Version table:
 *** 1:4.0-0ubuntu6 0
500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
100 /var/lib/dpkg/status

Audio does indeed play through the headphones, but does not play at all
through the main speakers.

I have force-reloaded ALSA, as well as purging and reinstalling alsa-
base and pulseaudio, just in case something had gotten out of whack. But
this has not had any effect.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-24.42-generic 3.11.10.11
Uname: Linux 3.11.0-24-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  mjpatey2037 F pulseaudio
 /dev/snd/controlC0:  mjpatey2037 F pulseaudio
Date: Fri Jul 11 17:57:52 2014
InstallationDate: Installed on 2014-07-06 (4 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  mjpatey2037 F pulseaudio
 /dev/snd/controlC0:  mjpatey2037 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [VPCZ11QGX, Realtek ALC889, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/04/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: R3031C3
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnINSYDE:bvrR3031C3:bd10/04/2011:svnSonyCorporation:pnVPCZ11QGX:pvrR5964106:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCZ11QGX
dmi.product.version: R5964106
dmi.sys.vendor: Sony Corporation

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


** Tags: amd64 apport-bug saucy

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

Title:
  [VPCZ11QGX, Realtek ALC889, Speaker, Internal] No sound at all

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  This *may* be related to Bug #960124, which looks similar. But I
  didn't want to assume that, since I am running a different version of
  Ubuntu (13.10), and the computer is a Sony VPC-Z11QGX/S.

  alsa-base:
Installed: 1.0.25+dfsg-0ubuntu4
Candidate: 1.0.25+dfsg-0ubuntu4
Version table:
   *** 1.0.25+dfsg-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status
  pulseaudio:
Installed: 1:4.0-0ubuntu6
Candidate: 1:4.0-0ubuntu6
Version table:
   *** 1:4.0-0ubuntu6 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  Audio does indeed play through the headphones, but does not play at
  all through the main speakers.

  I have force-reloaded ALSA, as well as purging and reinstalling alsa-
  base and pulseaudio, just in case something had gotten out of whack.
  But this has not had any effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-24.42-generic 3.11.10.11
  Uname: Linux 3.11.0-24-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mjpatey2037 F pulseaudio
   /dev/snd/controlC0:  mjpatey2037 F pulseaudio
  Date: Fri Jul 11 17:57:52 2014
  InstallationDate: Installed on 2014-07-06 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mjpatey2037 F pulseaudio
   /dev/snd/controlC0:  mjpatey2037 F pulseaudio
  Symptom_Jack: 

[Touch-packages] [Bug 1327426] Re: scopes runner should set various confinement variables

[Michi Henning]

> > XDG_RUNTIME_DIR and TMPDIR need to be the same anyway, because
TMPDIR has to be a sub-directory of /run/user/, and the scope can't
write to locations "above" that, so it doesn't make sense to set
XDG_RUNTIME_DIR to anything but TMPDIR.

> Actually, on Ubuntu XDG_RUNTIME_DIR is set to /run/user/`id -u` as part of 
> the user's login session. This should not be set to
> something else (and only explicitly set to '/run/user/`id -u`' it it isn't 
> already.

At the moment, I'm not setting it at all. It's set whatever we get from
our calling environment. But I'm a bit puzzled here: unless I
misunderstand something, a confined scope can't write to this directory,
only to sub-directories of XDG_RUNTIME_DIR as set by the Apparmor
policy. I'm wondering whether that might not be surprising for the scope
if XDG_RUNTIME_DIR is not writable? (But see below, scope-specific env
vars are not an option anyway.)

>I think this is troublesome to only implement this method without
setting TMPDIR. We set TMPDIR because well-written (ie, our system)
libraries respect this. Not setting this and only offering
tmp_directory() will make it so the developer has to know to set this
separately if using some library or similar that is creating a temporary
file.

We are really running into a much deeper issue here. Environment
variables are an idea that is three decades old, and they do not play at
all well with threads and plug-in architectures. For one, there is no
way for a thread to retrieve the value of an environment variable
without risking a crash because getenv() and setenv() are not thread-
safe. Second, environment variables affect the entire process, but that
destroys the notion of having more than one run time in the same process
because the setting would have to be scope-specific. (Note that this is
entirely orthogonal to confinement.)

> Well, again, this is all about consistency for developing on Ubuntu.
If when writing an app you get PATH set, but don't for a scope, that
seems inconsistent. I guess I just figured that all this would happen
after the fork() but before the exec() of the scope-runner or the
binary. It isn't clear to me why this would affect siblings or
parents

The issue is that several scopes can share a single process. This is not
so much because that would be an essential feature, but a software
design decision: things in libraries must have a well-defined life cycle
and must not share any hidden state. Environment variables effectively
are global variables that tie otherwise separate run time instances
together in an invisible way.

The problem here is not my design decision, the problem is TMPDIR. In a
well-defined threaded execution environment (especially when thinking
about sand-boxing) *no* library should *ever* have to read an
environment variable to decide anything. (Of course, I'm aware that
there are historical reasons for all this. But the assumptions that were
valid when TMPDIR was invented are becoming increasingly less valid, as
we are changing the security models for UNIX, and threads didn't exist
back then.)

>> That leaves UBUNTU_APPLICATION_ISOLATION. I did a Google search and
couldn't find any doc on that specific variable. But is it really
needed? It is understood that scopes are confined. If a scope really
needs to find out whether it is currently under some Apparmor profile,
it can just try doing something that won't work if confined. If the
attempt fails, the scope knows it's currently confined.

> https://wiki.ubuntu.com/SecurityTeam/Specifications/ApplicationConfinement#Launching_applications
> http://developer.ubuntu.com/publish/apps/security-policy-for-click-packages/ 
> (see 'Runtime Environment')

Thanks for the links!

I'm immediately having problems with UBUNTU_APPLICATION_ISOLATION after
reading this and following the link to the glib patch.

While I can see that this was a pragmatic fix to an immediate problem,
it is wrong in principle:

- There is a completely invisible environment variable that is being
read in the guts of a system library in order to change the way an API
call behaves in the presence of confinement.

- The variable is set by upstart, so every process that applies an
Apparmor profile before exec'ing now also needs to set the environment
variable.

Why doesn't the system call that sets the Apparmor profile set the
environment variable automatically? And, more importantly, why is
confinement being communicated by an environment variable when it really
should be a system call? I don't read an environment variable to find
out what my umask value is; I shouldn't read an environment variable to
find out whether my process is confined.

> Also, I just want to restate that none of this is a security concern
when a scope is confined since apparmor will make sure the scope is
confined regardless of environment. I filed this bug in the hopes of
making things consistent for the developer.

Jamie, I totally understand, and thanks for raising this! I'm learn

[Touch-packages] [Bug 1340984] [NEW] libav-tools unpacks with dpkg errors

[Nicholas Skaggs]

Public bug reported:

Installing libav-tools on utopic produces a dpkg error. Perhaps a
regression of
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1315672

Preparing to unpack .../libav-tools_6%3a9.11-2ubuntu3_amd64.deb ...
dpkg: error: --compare-versions takes three arguments:   


Type dpkg --help for help about installing and deinstalling packages [*];
Use 'apt' or 'aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !
Unpacking libav-tools (6:9.11-2ubuntu3) ...

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: libav-tools 6:9.11-2ubuntu3
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic x86_64
ApportVersion: 2.14.4-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jul 11 18:00:57 2014
InstallationDate: Installed on 2013-12-19 (204 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131218)
SourcePackage: libav
UpgradeStatus: Upgraded to utopic on 2014-05-09 (63 days ago)

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


** Tags: amd64 apport-bug utopic

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

Title:
  libav-tools unpacks with dpkg errors

Status in “libav” package in Ubuntu:
  New

Bug description:
  Installing libav-tools on utopic produces a dpkg error. Perhaps a
  regression of
  https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1315672

  Preparing to unpack .../libav-tools_6%3a9.11-2ubuntu3_amd64.deb ...
  dpkg: error: --compare-versions takes three arguments:   


  Type dpkg --help for help about installing and deinstalling packages [*];
  Use 'apt' or 'aptitude' for user-friendly package management;
  Type dpkg -Dhelp for a list of dpkg debug flag values;
  Type dpkg --force-help for a list of forcing options;
  Type dpkg-deb --help for help about manipulating *.deb files;

  Options marked [*] produce a lot of output - pipe it through 'less' or 'more' 
!
  Unpacking libav-tools (6:9.11-2ubuntu3) ...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libav-tools 6:9.11-2ubuntu3
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 11 18:00:57 2014
  InstallationDate: Installed on 2013-12-19 (204 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131218)
  SourcePackage: libav
  UpgradeStatus: Upgraded to utopic on 2014-05-09 (63 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1340984/+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 1340632] Re: [QtComp] Many apps open results in laggy launcher, apps scope, spread

[kevin gunn]

** Summary changed:

- [QtComp] vertical scroll in launcher is laggy
+ [QtComp] Many apps open results in laggy launcher, apps scope, spread

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

Title:
  [QtComp] Many apps open results in laggy launcher, apps scope, spread

Status in The Unity 8 shell:
  New
Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  What happened:
  I opened 9 apps, causing the launcher to be scrollable. Scrolling the 
launcher is slow and jumpy

  What should have happened:
  Luncher scrolling should be smoooth

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20140710.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-006]
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: armhf
  Date: Fri Jul 11 09:29:14 2014
  InstallationDate: Installed on 2014-07-11 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140711-020204)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8/+bug/1340632/+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 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'

[Ben Shadwick]

Adding ubuntu-meta because ntpdate lists it as a dependency, when ntpd
should be allowed as an alternative.

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Consider replacing ntpdate calls by 'ntpd -g'

Status in NTP:
  New
Status in “ntp” package in Ubuntu:
  Triaged
Status in “ubuntu-meta” package in Ubuntu:
  New

Bug description:
  Binary package hint: ntp

  Given that 'ntpdate' is being obsoleted upstream [1], we should
  replace 'ntpdate' usage by:

   * ntpd -qg (if we really want to set the time and exit), or
   * ntpd-g (if we want to keep ntpd running)

  the '-q' option will set the clock once, and exit; the 'g' allows for
  large corrections to the clock, like what is done by 'ntpdate'.

  
  [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ntp/+bug/583994/+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 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'

[Ben Shadwick]

Oops, I meant it the other way around: ubuntu-minimal lists ntpdate as a
dependency, such that ubuntu-minimal is uninstalled if you try to
replace ntpdate with ntpd.

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

Title:
  Consider replacing ntpdate calls by 'ntpd -g'

Status in NTP:
  New
Status in “ntp” package in Ubuntu:
  Triaged
Status in “ubuntu-meta” package in Ubuntu:
  New

Bug description:
  Binary package hint: ntp

  Given that 'ntpdate' is being obsoleted upstream [1], we should
  replace 'ntpdate' usage by:

   * ntpd -qg (if we really want to set the time and exit), or
   * ntpd-g (if we want to keep ntpd running)

  the '-q' option will set the clock once, and exit; the 'g' allows for
  large corrections to the clock, like what is done by 'ntpdate'.

  
  [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ntp/+bug/583994/+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 1339700] Re: [regression] Device locks randomly on welcome screen

[Alberto Aguirre]

** Branch linked: lp:~mir-team/mir/fix-1339700-take2-in-0.4

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

Title:
  [regression] Device locks randomly on welcome screen

Status in Mir:
  In Progress
Status in Mir 0.4 series:
  Triaged
Status in “mir” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Unity8 welcome screen will occasionally lock.

  Lock effects:
  No launcher available
  Can't swipe left or right
  Can't drag down indicators
  Doesn't recover from tapping the power button a couple of times.

  Randomness:
  Locks so far have been happening on and off from image U114
  The phone seems to lock up for me more on waking from suspend, however 
rsalveti pointed out that for him it happened on phone hang up.

  For me the lock happened a couple of times over the weekend images
  U114 and U115, and then not again till today U122.

  Manta seems more prone to lock ups that flo or mako.

  STEPS: (It seems flo has an issue identical when opening settings app)
  On flo update to U123
  1. Once updated, open the settings app
  This seems to land you in the state described.  Apparently this is only a 
temporary version if you leave the device for a while it will unlock.

  But I think that is possibly because you are moved away from the app
  and it is unlocked by the system waking from suspend possibly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.90+14.10.20140707-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: armhf
  Date: Wed Jul  9 13:48:14 2014
  InstallationDate: Installed on 2014-07-09 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140709-020204)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1339700/+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 1339700] Re: [regression] Device locks randomly on welcome screen

[Alberto Aguirre]

** Branch unlinked: lp:~andreas-pokorny/mir/synchronous-cancel-of-alarms

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

Title:
  [regression] Device locks randomly on welcome screen

Status in Mir:
  In Progress
Status in Mir 0.4 series:
  Triaged
Status in “mir” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Unity8 welcome screen will occasionally lock.

  Lock effects:
  No launcher available
  Can't swipe left or right
  Can't drag down indicators
  Doesn't recover from tapping the power button a couple of times.

  Randomness:
  Locks so far have been happening on and off from image U114
  The phone seems to lock up for me more on waking from suspend, however 
rsalveti pointed out that for him it happened on phone hang up.

  For me the lock happened a couple of times over the weekend images
  U114 and U115, and then not again till today U122.

  Manta seems more prone to lock ups that flo or mako.

  STEPS: (It seems flo has an issue identical when opening settings app)
  On flo update to U123
  1. Once updated, open the settings app
  This seems to land you in the state described.  Apparently this is only a 
temporary version if you leave the device for a while it will unlock.

  But I think that is possibly because you are moved away from the app
  and it is unlocked by the system waking from suspend possibly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.90+14.10.20140707-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: armhf
  Date: Wed Jul  9 13:48:14 2014
  InstallationDate: Installed on 2014-07-09 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140709-020204)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1339700/+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 1337749] Re: High CPU usage after resizing a window

[Furkan Alaca]

Abhijit, you're right scrolling in Chrome "only" uses around 40% or so.
I noticed it doesn't have smooth scrolling enabled. After disabling
smooth scrolling in Firefox (general.smoothScroll in about:config), CPU
usage dropped to about the same level as Chrome. Still extremely high
for just scrolling down a page, though.

I tested on the office computer today, which is a Core i7-920 w/ 6GB of
RAM and an Nvidia GT 9400 with the proprietary driver installed. I can
confirm that it suffers from the same problem (also running Ubuntu
14.04).

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

Title:
  High CPU usage after resizing a window

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  Background:

  Symptoms are 50-120% CPU usage when scrolling (especially Firefox),
  dragging around a window, resizing windows, basically any 2D graphics
  rendering on the desktop. This happens both in fglrx and the open
  source radeon driver. I started my debugging process by changing
  various settings, restarting, running "top" in a terminal, launching a
  Nautilus window, and quickly dragging it around with the mouse in
  circles while watching the CPU usage rise to around 50%. Resizing the
  window makes it jump to 100%+. Xorg and compiz are the culprits, with
  the CPU usage being split around 50/50 between them.

  Reproducing the issue:

  After a lot of searching I found some tips in the Arch Wiki article
  for the open source radeon driver, and I put together the following
  xorg.conf:

  Section "Module"
Load "dri2"
Load "glamoregl" 
  EndSection

  Section "Device"
  Identifier "Radeon 6670"
  Driver "radeon"
  Option  "MigrationHeuristic"  "greedy"
   Option "AccelMethod"   "glamor"
  EndSection

  After applying these settings, launching Nautilus and dragging it
  around only resulted in about 4% CPU usage each for xorg and compiz.
  Then, resizing the window (click and hold a side, and just keep moving
  the mouse left and right) made Xorg jump to 70% and compiz 50%. After
  that, when I start dragging the window around, CPU usage is back to
  around what it was originally: About 25% for compiz and 15% for Xorg.
  This exact behaviour happens after each reboot: The CPU usage is
  initially low when dragging the window around, but resizing it somehow
  messes things up and it never goes back to normal after that.

  I'm using a Radeon 6670 right now. I'll be receiving an R7 260X in
  about a week or so, so I won't be able to test with the exact same
  hardware, but I'm expecting at least similar behaviour since I also
  swapped in an R7 250 and was having the same issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.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
  Date: Fri Jul  4 03:52:17 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.13.0-29-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:2545]
  InstallationDate: Installed on 2014-06-06 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=d254b01f-2bf2-4b57-acdc-c796786f4c4c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F12
  dmi.board.name: GA-970A-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd09/03/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-970A-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-

[Touch-packages] [Bug 1339700] Re: [regression] Device locks randomly on welcome screen

[Launchpad Bug Tracker]

** Branch linked: lp:~mir-team/mir/fix-1339700-take2

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

Title:
  [regression] Device locks randomly on welcome screen

Status in Mir:
  In Progress
Status in Mir 0.4 series:
  Triaged
Status in “mir” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Unity8 welcome screen will occasionally lock.

  Lock effects:
  No launcher available
  Can't swipe left or right
  Can't drag down indicators
  Doesn't recover from tapping the power button a couple of times.

  Randomness:
  Locks so far have been happening on and off from image U114
  The phone seems to lock up for me more on waking from suspend, however 
rsalveti pointed out that for him it happened on phone hang up.

  For me the lock happened a couple of times over the weekend images
  U114 and U115, and then not again till today U122.

  Manta seems more prone to lock ups that flo or mako.

  STEPS: (It seems flo has an issue identical when opening settings app)
  On flo update to U123
  1. Once updated, open the settings app
  This seems to land you in the state described.  Apparently this is only a 
temporary version if you leave the device for a while it will unlock.

  But I think that is possibly because you are moved away from the app
  and it is unlocked by the system waking from suspend possibly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.90+14.10.20140707-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: armhf
  Date: Wed Jul  9 13:48:14 2014
  InstallationDate: Installed on 2014-07-09 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140709-020204)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1339700/+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 1337753] Re: [mako] can not create an ad-hoc network

[Tony Espy]

NM apparently has grown support for "ap" mode style hotspots.  It should
be possible to write the NM connection file with mode="ap" instead of
mode="adhoc".

So, I took Antti's connection file and modified it to use mode="ap"
instead of "adhoc".  I don't get the same stack trace when trying to
activate such a connection on mako, however it doesn't seem to work all
that well.  I initially saw the AP in the network list of my laptop (
trusty ), and an Android phone, however when I tried to connect via
Android, it appeared the defined psk in Antti's connection file is too
short for WPA-PSK ( the PSK needs to be 8 chars minimum ) so the Android
connect button was never active.

Once I corrected this by adding a few trailing characters, I tried to
connect with both OS X ( Invalid Password error ), and Android ( tries
to connect, fails, no error displayed ).

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

Title:
  [mako] can not create an ad-hoc network

Status in “linux-mako” package in Ubuntu:
  New
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “wpa” package in Ubuntu:
  Incomplete

Bug description:
  When trying to create an adhoc network using network-manager with mako
  kernel "Linux ubuntu-phablet 3.4.0-5-mako #28-Ubuntu SMP PREEMPT Fri
  Mar 28 15:20:22 UTC 2014 armv7l armv7l armv7l GNU/Linux" the creation
  fails with:

  NetworkManager[1347]:  Activation (wlan0) starting connection 'Ubuntu 
hotspot'
  wpa_supplicant[1735]: wlan0: CTRL-EVENT-SCAN-STARTED 
  kernel: [ 1202.120128] wlan: [1352:E :SME] csrMoveTempScanResultsToMainList: 
2908: 11d AP Bssid 00:1e:ab:04:92:77 chan= 1, rssi = -83, countryCode TW
  kernel: [ 1202.120341] wlan: [1352:E :SME] csrMoveTempScanResultsToMainList: 
2908: 11d AP Bssid c8:60:00:dc:42:90 chan= 8, rssi = -66, countryCode GB
  kernel: [ 1202.120616] wlan: [1352:E :SME] csrMoveTempScanResultsToMainList: 
2928: Information about current country Bssid c8:60:00:dc:42:90 chan= 8, rssi = 
-66, countryCode GB
  wpa_supplicant[1735]: wlan0: Trying to associate with SSID 'Ubuntu hotspot'
  NetworkManager[1347]:  (wlan0): supplicant interface state: 
disconnected -> associating
  kernel: [ 1202.989958] wlan: [1352:E :PE ] limMlmAddBss: 1672: TRYING TO HIDE 
SSID 0
  kernel: [ 1202.990477] wlan: [1352:E :PE ] mlm_add_sta: 1573: GF: 0, 
ChnlWidth: 0, MimoPS: 0, lsigTXOP: 0, dsssCCK: 0, SGI20: 0, SGI400
  kernel: [ 1203.007416] wlan: [1352:F :PE ] limProcessIbssMlmAddBssRsp: 2524: 
could not activate Heartbeat timer
  kernel: [ 1203.008087] VOS ASSERT in logDebug Line 219
  kernel: [ 1203.008759] [ cut here ]
  kernel: [ 1203.008850] WARNING: at 
/build/buildd/linux-mako-3.4.0/drivers/staging/prima/CORE/SYS/legacy/src/utils/src/logApi.c:219
 logDebug+0xc0/0xf4()
  kernel: [ 1203.008881] Modules linked in:
  kernel: [ 1203.008972] [] (unwind_backtrace+0x0/0xe8) from 
[] (dump_stack+0x20/0x24)
  kernel: [ 1203.009033] [] (dump_stack+0x20/0x24) from [] 
(warn_slowpath_common+0x5c/0x74)
  kernel: [ 1203.009094] [] (warn_slowpath_common+0x5c/0x74) from 
[] (warn_slowpath_null+0x2c/0x34)
  kernel: [ 1203.009186] [] (warn_slowpath_null+0x2c/0x34) from 
[] (logDebug+0xc0/0xf4)
  kernel: [ 1203.009247] [] (logDebug+0xc0/0xf4) from [] 
(limLog+0x48/0x50)
  kernel: [ 1203.009339] [] (limLog+0x48/0x50) from [] 
(limProcessMlmAddBssRsp+0x168/0xd40)
  kernel: [ 1203.009400] [] (limProcessMlmAddBssRsp+0x168/0xd40) from 
[] (limProcessMessages+0xe74/0x10ac)
  kernel: [ 1203.009491] [] (limProcessMessages+0xe74/0x10ac) from 
[] (limMessageProcessor+0x274/0x2bc)
  kernel: [ 1203.009552] [] (limMessageProcessor+0x274/0x2bc) from 
[] (peProcessMessages+0x54/0x5c)
  kernel: [ 1203.009613] [] (peProcessMessages+0x54/0x5c) from 
[] (VosMCThread+0x44c/0x68c)
  kernel: [ 1203.009705] [] (VosMCThread+0x44c/0x68c) from 
[] (kthread+0x9c/0xa8)
  kernel: [ 1203.009766] [] (kthread+0x9c/0xa8) from [] 
(kernel_thread_exit+0x0/0x8)
  kernel: [ 1203.009827] ---[ end trace 4821fc77d3719675 ]---
  NetworkManager[1347]:  Activation (wlan0/wireless): Ad-Hoc network 
creation took too long, failing activation.
  NetworkManager[1347]:  (wlan0): device state change: config -> failed 
(reason 'supplicant-timeout') [50 120 11]
  wpa_supplicant[1735]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 
reason=3 locally_generated=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1337753/+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 1339700] Re: [regression] Device locks randomly on welcome screen

[Alberto Aguirre]

** Branch unlinked: lp:~mir-team/mir/fix-1339700-in-0.4

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

Title:
  [regression] Device locks randomly on welcome screen

Status in Mir:
  In Progress
Status in Mir 0.4 series:
  Triaged
Status in “mir” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Unity8 welcome screen will occasionally lock.

  Lock effects:
  No launcher available
  Can't swipe left or right
  Can't drag down indicators
  Doesn't recover from tapping the power button a couple of times.

  Randomness:
  Locks so far have been happening on and off from image U114
  The phone seems to lock up for me more on waking from suspend, however 
rsalveti pointed out that for him it happened on phone hang up.

  For me the lock happened a couple of times over the weekend images
  U114 and U115, and then not again till today U122.

  Manta seems more prone to lock ups that flo or mako.

  STEPS: (It seems flo has an issue identical when opening settings app)
  On flo update to U123
  1. Once updated, open the settings app
  This seems to land you in the state described.  Apparently this is only a 
temporary version if you leave the device for a while it will unlock.

  But I think that is possibly because you are moved away from the app
  and it is unlocked by the system waking from suspend possibly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.90+14.10.20140707-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: armhf
  Date: Wed Jul  9 13:48:14 2014
  InstallationDate: Installed on 2014-07-09 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140709-020204)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1339700/+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 1248973] Re: The location and gps check box don't stay checked

[Selene Scriven]

Just confirming...  this seems to be fixed in the last few phone images.
Utopic 124 had no trouble keeping both location indicators checked.

Granted, I still can't get location to work, but the boxes at least stay
checked now.

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

Title:
  The location and gps check box don't stay checked

Status in Indicator Location:
  Fix Released
Status in “indicator-location” package in Ubuntu:
  Fix Released
Status in “location-service” package in Ubuntu:
  New
Status in “platform-api” package in Ubuntu:
  Confirmed

Bug description:
  If you check the location and gps checkboxes from the indicator-
  location and then after a minute view the setting again you will see
  that they are nolonger checked.

  Maguro image 14

  STEPS TO REPRODUCE:
  1. Pull down the location indicator
  2. Select the checkboxes for Location and GPS
  3. Push the indicator back up
  4. Wait a minute
  5. Pull down the location indicator.

  EXPECTED RESULTS:
  I should still have 2 boxes checked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-location/+bug/1248973/+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 1327426] Re: scopes runner should set various confinement variables

[Jamie Strandboge]

> So, I want to move away from environment variables, except for
LD_LIBRARY_PATH (and maybe PATH), which we can set easily enough before
the scope's .so is loaded.

This sounds fine. The point of both is to make things convenient for the
developer who may want to organize the code in a particular way or
exec() something that is shipped in the click.

> scope_directory() // returns the install dir, corresponds to XDG_CONFIG_HOME
> cache_directory() // returns the dir that is writable to the scope, 
> corresponds to XDG_DATA_HOME

Sure.

> This leaves PATH, TMPDIR, XDG_RUNTIME_DIR, and UBUNTU_APPLICATION_ISOLATION.
> 
> XDG_RUNTIME_DIR and TMPDIR need to be the same anyway, because TMPDIR has to 
> be a sub-directory of /run/user/, and the scope can't write to locations 
> "above" that, so it doesn't make sense to set XDG_RUNTIME_DIR to anything but 
> TMPDIR.

Actually, on Ubuntu XDG_RUNTIME_DIR is set to /run/user/`id -u` as part
of the user's login session. This should not be set to something else
(and only explicitly set to '/run/user/`id -u`' it it isn't already.

> We can add

> tmp_directory() // returns a writable tmp directory somewhere below
/run/user/

> This will take care of TMPDIR and XDG_RUNTIIME_DIR.

I think this is troublesome to only implement this method without
setting TMPDIR. We set TMPDIR because well-written (ie, our system)
libraries respect this. Not setting this and only offering
tmp_directory() will make it so the developer has to know to set this
separately if using some library or similar that is creating a temporary
file.

>For PATH, I'm not sure I see the point. The scope knows where it is
installed (in scope_directory()). If the scope wants to exec something
in its own bin directory, it can just exec it without having to rely on
PATH. We can set a defined path, no problem. But whatever we set it to
will have to be a standard path that is the same for all scopes, not
containing any scope-specific directories.

Well, again, this is all about consistency for developing on Ubuntu. If
when writing an app you get PATH set, but don't for a scope, that seems
inconsistent. I guess I just figured that all this would happen after
the fork() but before the exec() of the scope-runner or the binary. It
isn't clear to me why this would affect siblings or parents

> That leaves UBUNTU_APPLICATION_ISOLATION. I did a Google search and
couldn't find any doc on that specific variable. But is it really
needed? It is understood that scopes are confined. If a scope really
needs to find out whether it is currently under some Apparmor profile,
it can just try doing something that won't work if confined. If the
attempt fails, the scope knows it's currently confined.

https://wiki.ubuntu.com/SecurityTeam/Specifications/ApplicationConfinement#Launching_applications
http://developer.ubuntu.com/publish/apps/security-policy-for-click-packages/ 
(see 'Runtime Environment')

Also, I just want to restate that none of this is a security concern
when a scope is confined since apparmor will make sure the scope is
confined regardless of environment. I filed this bug in the hopes of
making things consistent for the developer.

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

Title:
  scopes runner should set various confinement variables

Status in API for Unity scopes integration:
  Triaged
Status in “unity-scopes-api” package in Ubuntu:
  New

Bug description:
  Click apps started with ubuntu-app-launch (or via aa-exec-click via legacy 
desktop files) have a number of environment variables set. Eg, for a test app 
of mine with APP_ID of 'com.ubuntu.developer.jdstrand.click-env_click-env_0.1', 
the following are set by ubuntu-app-launch:
  APP_ID=com.ubuntu.developer.jdstrand.click-env_click-env_0.1
  
__GL_SHADER_DISK_CACHE_PATH=/home/phablet/.cache/com.ubuntu.developer.jdstrand.click-env
  
LD_LIBRARY_PATH=/opt/click.ubuntu.com/.click/users/phablet/com.ubuntu.developer.jdstrand.click-env/lib/arm-linux-gnueabihf:/opt/click.ubuntu.com/.click/users/phablet/com.ubuntu.developer.jdstrand.click-env/lib
  
PATH=/opt/click.ubuntu.com/.click/users/phablet/com.ubuntu.developer.jdstrand.click-env/lib/arm-linux-gnueabihf/bin:/opt/click.ubuntu.com/.click/users/phablet/com.ubuntu.developer.jdstrand.click-env:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  
QML2_IMPORT_PATH=/opt/click.ubuntu.com/.click/users/phablet/com.ubuntu.developer.jdstrand.click-env/lib/arm-linux-gnueabihf
  TMPDIR=/run/user/32011/confined/com.ubuntu.developer.jdstrand.click-env
  UBUNTU_APPLICATION_ISOLATION=1
  XDG_CACHE_HOME=/home/phablet/.cache
  XDG_CONFIG_HOME=/home/phablet/.config
  
XDG_DATA_DIRS=/opt/click.ubuntu.com/.click/users/phablet/com.ubuntu.developer.jdstrand.click-env:/usr/share
  XDG_DATA_HOME=/home/phablet/.local/share
  XDG_RUNTIME_DIR=/run/user/32011

  For scopes, we should 

[Touch-packages] [Bug 1339700] Re: [regression] Device locks randomly on welcome screen

[Alberto Aguirre]

** Branch unlinked: lp:~mir-team/mir/fix-1339700

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

Title:
  [regression] Device locks randomly on welcome screen

Status in Mir:
  In Progress
Status in Mir 0.4 series:
  Triaged
Status in “mir” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Unity8 welcome screen will occasionally lock.

  Lock effects:
  No launcher available
  Can't swipe left or right
  Can't drag down indicators
  Doesn't recover from tapping the power button a couple of times.

  Randomness:
  Locks so far have been happening on and off from image U114
  The phone seems to lock up for me more on waking from suspend, however 
rsalveti pointed out that for him it happened on phone hang up.

  For me the lock happened a couple of times over the weekend images
  U114 and U115, and then not again till today U122.

  Manta seems more prone to lock ups that flo or mako.

  STEPS: (It seems flo has an issue identical when opening settings app)
  On flo update to U123
  1. Once updated, open the settings app
  This seems to land you in the state described.  Apparently this is only a 
temporary version if you leave the device for a while it will unlock.

  But I think that is possibly because you are moved away from the app
  and it is unlocked by the system waking from suspend possibly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.90+14.10.20140707-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: armhf
  Date: Wed Jul  9 13:48:14 2014
  InstallationDate: Installed on 2014-07-09 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140709-020204)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1339700/+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 1340933] [NEW] Unity does not display keyboard shortcut list when multiple workspaces are enabled

[Lex Ross]

Public bug reported:

When enabling workspaces in Unity holding down the Super does not
produce the keyboard shortcuts cheat sheet any more. This is a major
inconvenience to me as I have to write down the shortcut list now and
have it available near my laptop for the reference.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.1+14.04.20140513-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
Uname: Linux 3.13.0-6-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Fri Jul 11 23:45:59 2014
EcryptfsInUse: Yes
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Unity does not display keyboard shortcut list when multiple workspaces
  are enabled

Status in “unity” package in Ubuntu:
  New

Bug description:
  When enabling workspaces in Unity holding down the Super does not
  produce the keyboard shortcuts cheat sheet any more. This is a major
  inconvenience to me as I have to write down the shortcut list now and
  have it available near my laptop for the reference.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Jul 11 23:45:59 2014
  EcryptfsInUse: Yes
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1340933/+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 1340448] Re: 5% reservation for root is inappropriate for large disks/arrays

[Theodore Ts'o]

As the file system gets more and more full, the free space gets more and
more fragmented.  This results in disastrous performance hits for files
that are written when the file system gets full, and then when you later
try to read them, you will suffer similar disastrous performance hits.

This is of course much more notable on HDD, but even on SSD's, a random
write workload is always going to result in greater flash wear and lower
performance than a sequential write workload --- particularly on the
cheaper flash that you would expect to see in tablets and phones (i.e.,
eMMC flash) --- and even some of the crappier desktop SSD's.

Now, if you have an Intel or Samsung SSD, this might not matter as much
(although you will still see a performance hit) --- but having mke2fs
figure out whether you have a competently implemented flash translation
layer, or a spectacularly crappy one (since on phones they calculate the
BOM cost down to the hundredth or thousandth of a cent, and that extra
25 cents worth of better FTL license fees and controller memory is Just
Too Damn High :-), is just too much complexity to put into mke2fs's
program logic.It's better to have a simple, well defined default,
and then if you know for sure that you have a system where you don't
mind highly fragmented files, to adjust the root reserve.

As far as the server and the cloud, for the cloud, it won't really
matter since guest OS's generally have relatively small amounts of
space.  And Ubuntu has stopped caring about the enterprise server market
a long time ago.   As far as the cloud host OS, there's a heck of a lot
more tuning you need to do if you what a high-performing,
price/performance competitive offering, such that adjusting the root
reserve is the very least of your problems

In any case, this is not something I intend to change for upstream,
either in e2fsprogs or the Debian package.  If the Ubuntu release
engineers want to make a change, they are of course free to do so.  But
I wouldn't recomend it.

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

Title:
  5% reservation for root is inappropriate for large disks/arrays

Status in “e2fsprogs” package in Ubuntu:
  Confirmed

Bug description:
  mke2fs (and it's ext3 and ext4 analogs) still default to reserving 5%
  of the filesystem for root.  With the size of modern disks and arrays
  this isn't a terribly sensible default, e.g. if I have a 10Tb array,
  mke2fs will reserve 500Gb for root.

  Obviously this is both tunable at FS creation time and fixable after
  the fact but I still think we should try and improve the defaults.

  Given the size of modern disks, I think it'd make sense to either a)
  only reserve a smaller amount (e.g. 1%) or b) reserve n% if the
  filesystem is << NNN GB and otherwise reserve NN GB.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1340448/+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 1288346] Re: Flight Mode not available

[Pat McGowan]

Released in settings

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Flight Mode not available

Status in Network Menu:
  In Progress
Status in “indicator-network” package in Ubuntu:
  In Progress
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Trusty r188

  1. Open System Settings, or the network menu.
  2. Try to turn on Flight Mode.

  What happens: There's no such setting.

  : "The
  quick access area is a group of list items at the top of the overview
  screen. It should always contain 'Orientation Lock' and 'Flight Mode'
  items."

  : "Turning on
  Flight Mode should turn off all transmitting connection types —
  wireless, mobile, and Bluetooth..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1288346/+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 1294669] Re: bash crashed with SIGABRT in programming_error()

[Bernie Innocenti]

Confirming that the bash binary from the trace *does* include patches 9 through 
11.
Now trying to get a better trace from a binary compiled with -g

Please reopen this bug.

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

Title:
  bash crashed with SIGABRT in programming_error()

Status in “bash” package in Ubuntu:
  Fix Released
Status in “bash” source package in Trusty:
  Fix Released

Bug description:
  [Test Case]
  bdmurray@blacklightning:~$ x!
  x!: command not found
  bdmurray@blacklightning:~$ x!

  malloc: .././parse.y:2314: assertion botched
  realloc: start and end chunk sizes differ
  last command: x!
  Aborting...Aborted (core dumped)

  [Regression Potential]
  Low, this patch has been applied upstream.

  bash just died under me, I think I was just doing cursor up to get a
  previous command and it segfaulted.  This has happened several times
  this week and is getting annoying

  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: bash 4.3-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-16.36-lowlatency 3.13.5
  Uname: Linux 3.13.0-16-lowlatency x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Mar 19 14:08:22 2014
  EcryptfsInUse: Yes
  ExecutablePath: /bin/bash
  InstallationDate: Installed on 2013-12-09 (99 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131209)
  ProcCmdline: bash
  Signal: 6SourcePackage: bash
  StacktraceTop:
   programming_error ()
   ?? ()
   sh_xrealloc ()
   ?? ()
   ?? ()
  Title: bash crashed with SIGABRT in programming_error()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1294669/+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 1294669] Re: bash crashed with SIGABRT in programming_error()

[Bernie Innocenti]

I'm still seeing this exact same crash with bash_4.3-7ubuntu1. In fact,
I also see it with a bash binary built from the upstream git (bash 4.3
patch 18).

This is the stack trace I'm getting:


codewiz@xyzzy:~$ 

malloc: unknown:0: assertion botched
free: called with unallocated block argument
last command: ll webserver/sffe/config/sffe_config.proto
Aborting...
Program received signal SIGABRT, Aborted.
0x7761df79 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56  ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x7761df79 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x77621388 in __GI_abort () at abort.c:89
#2  0x0044051f in programming_error ()
#3  0x004b3bff in internal_free.isra ()
#4  0x004ae1ac in _rl_revert_all_lines ()
#5  0x00495035 in readline_internal_teardown ()
#6  0x00495f56 in readline ()
#7  0x0042158a in yy_readline_get ()
#8  0x00423716 in shell_getc ()
#9  0x004265f2 in read_token.constprop ()
#10 0x00429bd4 in yyparse ()
#11 0x00420e9b in parse_command ()
#12 0x00420f6c in read_command ()
#13 0x00421169 in reader_loop ()
#14 0x0041f749 in main ()
(gdb)

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

Title:
  bash crashed with SIGABRT in programming_error()

Status in “bash” package in Ubuntu:
  Fix Released
Status in “bash” source package in Trusty:
  Fix Released

Bug description:
  [Test Case]
  bdmurray@blacklightning:~$ x!
  x!: command not found
  bdmurray@blacklightning:~$ x!

  malloc: .././parse.y:2314: assertion botched
  realloc: start and end chunk sizes differ
  last command: x!
  Aborting...Aborted (core dumped)

  [Regression Potential]
  Low, this patch has been applied upstream.

  bash just died under me, I think I was just doing cursor up to get a
  previous command and it segfaulted.  This has happened several times
  this week and is getting annoying

  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: bash 4.3-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-16.36-lowlatency 3.13.5
  Uname: Linux 3.13.0-16-lowlatency x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Mar 19 14:08:22 2014
  EcryptfsInUse: Yes
  ExecutablePath: /bin/bash
  InstallationDate: Installed on 2013-12-09 (99 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131209)
  ProcCmdline: bash
  Signal: 6SourcePackage: bash
  StacktraceTop:
   programming_error ()
   ?? ()
   sh_xrealloc ()
   ?? ()
   ?? ()
  Title: bash crashed with SIGABRT in programming_error()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1294669/+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 1340905] [NEW] Acer Aspire E1-570-6889 brightness control not working

[Ivan Baldo]

Public bug reported:

  Cannot adjust the brightness in a Acer Aspire E1-570-6889.
  The brightness key works and the brightness configuracion in the system 
configuration allows to adjust the brightness but the display does nothing, it 
is always at full brightness.
  I may try some things esporadically since it is not my laptop, but I may take 
a long time to try them :-(.
  Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.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
Date: Fri Jul 11 15:48:22 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0835]
InstallationDate: Installed on 2014-07-07 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Acer Aspire E1-570
ProcEnviron:
 LANGUAGE=es_UY:es
 TERM=xterm
 PATH=(custom, no user)
 LANG=es_UY.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=951be93c-e59d-461a-b0e6-d7e48153b4ae ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA50_CX
dmi.board.vendor: Acer
dmi.board.version: V2.06
dmi.chassis.asset.tag: Acer Asset Tag String
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde Corp.
dmi.chassis.version: V2.06
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.06:bd10/08/2013:svnAcer:pnAspireE1-570:pvrV2.06:rvnAcer:rnEA50_CX:rvrV2.06:cvnInsydeCorp.:ct10:cvrV2.06:
dmi.product.name: Aspire E1-570
dmi.product.version: V2.06
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Jul 11 15:25:06 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   18668 
 vendor AUO
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 trusty 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/1340905

Title:
  Acer Aspire E1-570-6889 brightness control not working

Status in “xorg” package in Ubuntu:
  New

Bug description:
Cannot adjust the brightness in a Acer Aspire E1-570-6889.
The brightness key works and the brightness configuracion in the system 
configuration allows to adjust the brightness but the display does nothing, it 
is always at full brightness.
I may try some things esporadically since it is not my laptop, but I may 
take a long time to try them :-(.
Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.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
  Date: Fri Jul 11 15:48:22 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0835]
  InstallationDate: Installed on 2014-07-07 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire E1-570
  ProcE

[Touch-packages] [Bug 1304754] Re: gccgo has issues when page size is not 4kB

[Patricia Gaughen]

Matthias - does that mean it will show up in proposed on Jul 17?  I
think there are folks who would hope it would land in Trusty sooner.

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

Title:
  gccgo has issues when page size is not 4kB

Status in The GNU Compiler Collection:
  Fix Released
Status in “gcc-4.9” package in Ubuntu:
  Fix Released
Status in “gccgo-4.9” package in Ubuntu:
  Invalid
Status in “gcc-4.9” source package in Trusty:
  Invalid
Status in “gccgo-4.9” source package in Trusty:
  In Progress
Status in “gcc-4.9” source package in Utopic:
  Fix Released
Status in “gccgo-4.9” source package in Utopic:
  Invalid

Bug description:
  On kernels 3.13-18 and 3.13-23 (there may be others) the kernel is
  killing gccgo compiled binaries

  [18519.444748] jujud[19277]: bad frame in setup_rt_frame:
   nip  lr 
  [18519.673632] init: juju-agent-ubuntu-local main process (19220)
  killed by SEGV signal
  [18519.673651] init: juju-agent-ubuntu-local main process ended, respawning

  In powerpc/kernel/signal_64.c:

  sys_rt_sigreturn is jumping to the badframe: label and executing an
  unconditional force_sigsegv which is delivered to the userland
  process. Like C++, gccgo tries to decode SIGSEGV as a nil pointer
  access and blame some random function that happened to be the top
  stack frame.

  Reverting to the 3.13-08 kernel appears to resolve the issue which
  (weakly) points the finger at the recent switch to 64k pages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1304754/+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 1340888] Re: gnome

[Marc Deslauriers]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  gnome

Status in “xorg” package in Ubuntu:
  New

Bug description:
  ** (gnome-panel:2151): WARNING **: Unable to parse mouse modifier
  '(null)'

  Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 14: out of memory
  Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 23: out of memory
  Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 32: out of memory

  (gnome-panel:2151): Gtk-CRITICAL **:
  gtk_accelerator_parse_with_keycode: assertion 'accelerator != NULL'
  failed

  ** (gnome-panel:2151): WARNING **: Unable to parse mouse modifier
  '(null)'

  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  Uname: Linux 3.13.1-031301-generic i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Jul 11 13:12:10 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0039]
 Subsystem: Acer Incorporated [ALI] Device [1025:0039]
  InstallationDate: Installed on 2014-07-10 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  Lsusb:
   Bus 001 Device 002: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer TravelMate 240
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 no card
  ProcEnviron:
   LANGUAGE=es_MX
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.1-031301-generic 
root=UUID=5c5277a2-9b55-4ccb-94d3-1a4eb5a15096 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 1: Error: OpenGL rendering is not supported by the 
root visual
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/03
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.14
  dmi.board.name: TravelMate 240
  dmi.board.vendor: Acer
  dmi.board.version: Rev.A
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.14:bd10/21/03:svnAcer:pnTravelMate240:pvr-1:rvnAcer:rnTravelMate240:rvrRev.A:cvnAcer:ct1:cvrN/A:
  dmi.product.name: TravelMate 240
  dmi.product.version: -1
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1~saucy1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.6-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.904-0ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Fri Jul 11 12:51:24 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.14.6-0ubuntu1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
U

[Touch-packages] [Bug 1340063] Re: System identifier returned by GetIdentifier dbus method differs from identifier on errors.u.c

[Launchpad Bug Tracker]

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

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

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

Title:
  System identifier returned by GetIdentifier dbus method differs from
  identifier on errors.u.c

Status in “whoopsie” package in Ubuntu:
  Confirmed

Bug description:
  The identifier returned by the dbus method GetIdentifier and the key
  'SystemIdentifier' on errors.ubuntu.com for a report uploaded from the
  same device are different.

  For example on my mako:
  $ gdbus call -y -d com.ubuntu.WhoopsiePreferences -o 
/com/ubuntu/WhoopsiePreferences -m com.ubuntu.WhoopsiePreferences.GetIdentifier
  ('16942cef...3a2f37ac',)

  And on report 
https://errors.ubuntu.com/oops/4451dfac-07ff-11e4-8dae-fa163e339c81
  b5ed62e6...6a211d78

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: whoopsie 0.2.34
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: armhf
  Date: Thu Jul 10 09:16:44 2014
  InstallationDate: Installed on 2014-07-10 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140710-020204)
  RelatedPackageVersions: apport-noui 2.14.4-0ubuntu1
  SourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1340063/+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 1339916] Re: SystemIdentifier can change between reboots

[Launchpad Bug Tracker]

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

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

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

Title:
  SystemIdentifier can change between reboots

Status in “whoopsie” package in Ubuntu:
  Confirmed

Bug description:
  Here is the output of 
  'gdbus call -y -d com.ubuntu.WhoopsiePreferences -o 
/com/ubuntu/WhoopsiePreferences -m com.ubuntu.WhoopsiePreferences.GetIdentifier'

  between two different boots of a Nexus 4.

  
('2f46f0e12ac414279731800384d584fac05b4af7ffe6d4d61db115ae19c39ba2855dc36388e78349b17f49e68becdb5f2b32faff0fefaa65d519b55d98b7da0d',)

  
('5f85abf86cc6593c762adbda6ebb614f9311ef58de14fdec0e3f33a2787213c321ca05f16ebcb748535cb736945fa66468f53020d091d7ff086849d23c0c8f58',)

  This is likely related to the last upload of whoopsie.

  whoopsie (0.2.34) utopic; urgency=medium

[ John Lenton ]
* Obtain a MAC address for system identifier generation even if the network
  is not up. (LP: #1328285)
   -- Brian MurrayMon, 07 Jul 2014 11:44:26 -0700

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1339916/+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 1038479] Re: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a while

[Zsolt Lakatos]

"windows 7 x86_64 also affected for me since i use the laptop as dualboot with 
ubuntu"
sorry. this was a false information
windows works fine

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

Title:
  [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a
  while

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  Restart will fix the issue, but sound always quits from internal
  speaker. Headphones work always.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1838 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc060 irq 44'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:14f15069,1179fc50,00100302 
HDA:80862805,1179fc50,0010'
 Controls  : 24
 Simple ctrls  : 11
  Date: Sat Aug 18 11:18:34 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.20:bd07/13/2011:svnTOSHIBA:pnSatelliteL755:pvrPSK1WU-05N004:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L755
  dmi.product.version: PSK1WU-05N004
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1038479/+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 1335568] Re: Updates keep coming in while writable image is set

[Barry Warsaw]

The time machine strikes again!  LP: #1207860

The method is called FactoryReset() and it will be included in system-
image 2.3 (hopefully coming early next week).

FactoryReset() is documented here:

https://wiki.ubuntu.com/ImageBasedUpgrades/Client

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

Title:
  Updates keep coming in while writable image is set

Status in Ubuntu system image (server/client/updater):
  Invalid
Status in “system-image” package in Ubuntu:
  Invalid

Bug description:
  I've been updating whilst having writable image set.

  root@ubuntu-phablet:~# system-image-cli -i
  current build number: 104
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-06-29 04:47:42
  version version: 104
  version ubuntu: 20140629
  version device: 20140625
  root@ubuntu-phablet:~# ls -lh /userdata/.writable_image 
  -rw-rw-rw- 1 root root 0 Jun 22 14:37 /userdata/.writable_image

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: system-image-common 2.2-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: armhf
  Date: Sun Jun 29 05:00:12 2014
  InstallationDate: Installed on 2014-06-29 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140629-020204)
  PackageArchitecture: all
  SourcePackage: system-image
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-image/+bug/1335568/+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 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab

[Christopher Townsend]

** Changed in: compiz/0.9.11
   Status: In Progress => Fix Committed

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

Title:
  Lock screen is unusable when some windows have a keyboard/mouse grab

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  Fix Committed
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Released
Status in “unity” source package in Trusty:
  Confirmed

Bug description:
  [Impact]

  Some windows will grab the keyboard/mouse and when the lockscreen
  kicks in, this window will still have the grab and thusly, ou can
  enter your password in the lockscreen.

  [Test case]

  1. Open a window that will hold the grab, such as the ssh password dialog.
  2. Wait for the lock screen to activate.
  3. Enter your password to unlock the screen.

  [Regression potential]

  This particular fix doesn't fix all cases, but does fix it for some.
  That said, no new regressions are expected.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  My screen just timed out and locked when a password prompt which had a
  grab was displaying.

  I couldn't type my password or interact with the indicators.

  gnome-screensaver just refuses to lock in this situation, perhaps
  unity could do the same unless it's possible to remove and readd the
  grabs yourself, but I don't think XLib lets you do that (you can only
  remove your own grabs AFAIK).

  TEMPORARY WORKAROUND TO LOGIN AGAIN:
  Click on the guest session
  Once the guest session is started log out
  This takes you back to the lightdm session screen you can then login to your 
user session and it be in the same state

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  CurrentDesktop: Unity
  Date: Thu Apr 10 09:39:45 2014
  InstallationDate: Installed on 2012-10-07 (549 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1305586/+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 1335568] Extending system image cli for factory reset

[Sergio Schvezov]

Hey Barry, there's a design entry for providing factory reset[1]. One of 
the ideas that circles around is to add a new method, let's call it Format, 
to an existing or new interface in system image to basically do:

echo "format data" > /cache/recovery/ubuntu_command

I guess it's the right fit since this way we can easily lock an upgrade 
from a factory reset taking place at the same time.

What do you think? I can take stance later if it seems appropriate or 
people time becomes a blocking factor.

Cheers
Sergio.

[1] https://wiki.ubuntu.com/SystemSettings#A.2BIBw-Reset_Phone.2BIB0-

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

Title:
  Updates keep coming in while writable image is set

Status in Ubuntu system image (server/client/updater):
  Invalid
Status in “system-image” package in Ubuntu:
  Invalid

Bug description:
  I've been updating whilst having writable image set.

  root@ubuntu-phablet:~# system-image-cli -i
  current build number: 104
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-06-29 04:47:42
  version version: 104
  version ubuntu: 20140629
  version device: 20140625
  root@ubuntu-phablet:~# ls -lh /userdata/.writable_image 
  -rw-rw-rw- 1 root root 0 Jun 22 14:37 /userdata/.writable_image

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: system-image-common 2.2-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: armhf
  Date: Sun Jun 29 05:00:12 2014
  InstallationDate: Installed on 2014-06-29 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140629-020204)
  PackageArchitecture: all
  SourcePackage: system-image
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-image/+bug/1335568/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

[Launchpad Bug Tracker]

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

** Changed in: sublime-text (Ubuntu)
   Status: New => Confirmed

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

Status in Aptana Studio Installer:
  New
Status in Default settings for the Baltix GNU/Linux OS and desktop:
  New
Status in LibreOffice Productivity Suite:
  Confirmed
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  New
Status in MonoDevelop:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “sublime-text” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1334611] Re: Can't update click if we have previously installed packages for users that were later deleted

[Launchpad Bug Tracker]

** Branch linked: lp:click/devel

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

Title:
  Can't update click if we have previously installed packages for users
  that were later deleted

Status in “click” package in Ubuntu:
  In Progress

Bug description:
  Earlier I tried to install a new version of click and was met with the
  following error:

  brendand@brendand-yoga:~$ sudo apt-get install click
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be upgraded:
click
1 to upgrade, 0 to newly install, 0 to remove and 790 not to upgrade.
4 not fully installed or removed.
Need to get 0 B/13.4 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 351473 files and directories currently installed.)
Preparing to unpack .../click_0.4.28_amd64.deb ...
Traceback (most recent call last):
  File "/usr/bin/click", line 86, in 
sys.exit(main())
  File "/usr/bin/click", line 82, in main
return mod.run(args)
  File "/usr/lib/python3/dist-packages/click/commands/hook.py", line 63, in 
run
getattr(hook, per_hook_subcommands[subcommand])(user_name=None)
  gi._glib.GError: Cannot get password file entry for redacted: Success
  dpkg: warning: subprocess old pre-removal script returned error exit 
status 1
  dpkg: trying script from the new package instead ...
Traceback (most recent call last):
  File "/usr/bin/click", line 86, in 
sys.exit(main())
  File "/usr/bin/click", line 82, in main
return mod.run(args)
  File "/usr/lib/python3/dist-packages/click/commands/hook.py", line 63, in 
run
getattr(hook, per_hook_subcommands[subcommand])(user_name=None)
 gi._glib.GError: Cannot get password file entry for redacted: Success
 dpkg: error processing archive 
/var/cache/apt/archives/click_0.4.28_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
 Errors were encountered while processing:
 /var/cache/apt/archives/click_0.4.28_amd64.deb
 E: Sub-process /usr/bin/dpkg returned an error code (1)

  As per Colin Watsons request, here are the contents of
  /opt/click.ubuntu.com: http://paste.ubuntu.com/7705310/

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

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

Re: [Touch-packages] [Bug 1338939] Re: Alarms go off 3 times on mako and flo

[Pat McGowan]

In my case,
- the same event goes off twice in succession. (like a few secs after
dismissing the first one the second appears)
- There is only one event instance shown in the indicator
- All events are notified twice.
- These were all sync'd from google.

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

Title:
  Alarms go off 3 times on mako and flo

Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  Sync your calendar to Ubuntu device
  Have events in your calendar.
  Wait for an a event
  Alarm goes off.
  Listen to the gently plucked harp.
  Press the dismiss button on the popup
  Wait a short while.
  Alarm goes off again.
  Get annoyed at the harp
  Press the dismiss button on the popup
  Wait a short while
  Alarm goes off again
  Shout at phone.

  I would expect the alarm to go off once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1338939/+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 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application

[Launchpad Bug Tracker]

** Branch linked: lp:~compiz-team/compiz/0.9.11.2

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

Title:
  Launcher, Window management - Dragging and holding a selection over an
  entry in the Launcher should spread out windows belonging to that
  application

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in One Hundred Papercuts:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  If the user drags and hold a file over a running application in the
  Launcher, all the windows of that application should be shown with the
  spread. The user should then be able to drag and drop the file in a
  windows in the spread to load the file into that specific window.

  Bug #727903 needs to be fixed at the same time.

  ---

  History:

  This bug had been previously fixed as "buggybutclosed" for Unity on 
2011-04-18, leaving this function with other bugs:
  https://bugs.launchpad.net/ayatana-design/+bug/727903
  https://bugs.launchpad.net/ayatana-design/+bug/727904
  https://bugs.launchpad.net/ayatana-design/+bug/727902
  https://bugs.launchpad.net/ayatana-design/+bug/764424
  https://bugs.launchpad.net/ayatana-design/+bug/832988

  On 2011-10-18, it was reopened for regression in Oneiric.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/607796/+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 1009045] Re: md5sum 'backslash-in-filename' feature is not documented in man page

[C de-Avillez]

Thank you for opening this bug and helping make Ubuntu better.

This is not a bug. Coreutils (as most of GNU packages) uses Texinfo as
the primary source for documentation. The man pages are a summary
*only*; for full docs, the user is referred to 'info':

The  full  documentation  for md5sum is maintained as a Texinfo manual.
   If the info and md5sum programs are properly installed  at  your  site,
   the command

  info coreutils 'md5sum invocation'

   should give you access to the complete manual.

As such, closing this as not-a-bug.

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

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

Title:
  md5sum 'backslash-in-filename' feature is not documented in man page

Status in “coreutils” package in Ubuntu:
  Invalid

Bug description:
  Encountered in

  Description : Ubuntu 10.04.4 LTS
  Release : 10.04

  using

   md5sum (GNU coreutils) 7.4

  $ apt-cache policy coreutils
  coreutils:
Installed: 7.4-2ubuntu3
Candidate: 7.4-2ubuntu3
Version table:
   *** 7.4-2ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
  100 /var/lib/dpkg/status
   7.4-2ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages

  Related to
  https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/53584

  The following information is in "info coreutils 'md5sum invocation'"

 For each FILE, `md5sum' outputs the MD5 checksum, a flag indicating
  a binary or text input file, and the file name.  If FILE contains a
  backslash or newline, the line is started with a backslash, and each
  problematic character in the file name is escaped with a backslash,
  making the output unambiguous even in the presence of arbitrary file
  names.  If FILE is omitted or specified as `-', standard input is read.

  The corresponding section in the man page reads as follows:

 The  sums are computed as described in RFC 1321.  When checking, the 
input should be a former output of this
 program.  The default mode is to print a line with checksum, a 
character indicating type (`*' for binary,  `
 ' for text), and name for each FILE.

  The documentation of the behaviour of md5sum when given filenames
  containing backslashes is missing from the man page, and was
  unexpected behaviour when I first encountered it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1009045/+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 727904] Re: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken

[Launchpad Bug Tracker]

** Branch linked: lp:~compiz-team/compiz/0.9.11.2

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

Title:
  Launcher, Window management - Switching between spreads when dragging
  a file over the Launcher is broken

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in Unity:
  Invalid
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  To reproduce:

  Open two Chrome windows and two Firefox windows.  Drag a .html file
  over the Chrome icon in the Launcher.  A spread of the two Chrome
  windows should appear.  Then continue the same drag, and drag the file
  over the Firefox icon in the Launcher.  Nothing happens, the Chrome
  spread is still displayed.

  Desired behaviour;

  After a spread appears as a result of the user dragging a file over a
  application icon in the Launcher, if the user then drags the file over
  a different application icon (where the application is also a valid
  drop receptacle for the file type) the spread should switch to the
  newly selected application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/727904/+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 1187453] Re: DTMF tones not being generated locally

[Martti Piirainen]

Still evaluating tone-generator, some notes:
 - The volume of the DTMF sounds is set globally, via command line argument ' 
--volume-dtmf N' with N being 0 .. 100 percent of the maximum volume. The D-Bus 
interface's volume argument is ignored for DTMF sounds.
 - Two more command line arguments (buffer length; minimum recording length) 
need to be given to avoid a significant delay. "tonegend -b 100 -r 20 
--volume-dtmf 30" seems to work well.
 - Haven't figured out yet why tonegend can't connect to PulseAudio if it's 
running in session mode, only in system mode (failing in pa_context_connect() 
in ausrv.c).

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

Title:
  DTMF tones not being generated locally

Status in “dialer-app” package in Ubuntu:
  Confirmed
Status in “telephony-service” package in Ubuntu:
  Confirmed
Status in “dialer-app” source package in Saucy:
  Confirmed
Status in “telephony-service” source package in Trusty:
  Confirmed

Bug description:
  DTMF tones are not always generated when the UI shows the number was
  entered.

  Nexus 4 running build 150

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

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

Re: [Touch-packages] [Bug 1340448] Re: 5% reservation for root is inappropriate for large disks/arrays

[James Troup]

"Theodore Ts'o"  writes:

> If you try to use more than 95% of the storage, performance will
> generally suffer -- badly.

Sorry, but why is that?  And do you mean read performance, write
performance or both?  And is that a factor of the type of storage
(e.g. spinning disk vs. SSD)?

> In addition for the root file system, you really do want to leave the
> default at 5% so that root can write to critical file systems.

Sure, I didn't suggest eliminating the reservation, just reducing it.
Or is there some reason that root would need at least 5% (as opposed
to 1% or 2%) of disk available to write to that I'm missing?

> And since the vast majority of Ubuntu users are using a single root
> file system, that implies that the for the vast majority of file
> systems created by Ubuntu, the default is in fact appropriate.

While that may be true of Ubuntu on the client (desktop, laptop,
tablet, phone, etc.); I'm not sure it's true of server and cloud?

-- 
James

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

Title:
  5% reservation for root is inappropriate for large disks/arrays

Status in “e2fsprogs” package in Ubuntu:
  Confirmed

Bug description:
  mke2fs (and it's ext3 and ext4 analogs) still default to reserving 5%
  of the filesystem for root.  With the size of modern disks and arrays
  this isn't a terribly sensible default, e.g. if I have a 10Tb array,
  mke2fs will reserve 500Gb for root.

  Obviously this is both tunable at FS creation time and fixable after
  the fact but I still think we should try and improve the defaults.

  Given the size of modern disks, I think it'd make sense to either a)
  only reserve a smaller amount (e.g. 1%) or b) reserve n% if the
  filesystem is << NNN GB and otherwise reserve NN GB.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1340448/+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 1338939] Re: Alarms go off 3 times on mako and flo

[Charles Kerr]

> Reported by Alan Pope ㋛ 
>
> Wait for an a event
> Alarm goes off.
> Listen to the gently plucked harp.

This is practically a haiku.

Best bug report I've seen in ages.

Popey, just to be clear, you're saying this is the same event going off
thrice at the same time (or nearly the same time)? Does the same event
show up N times in the indicator as well or when you open up ubuntu-
clock-app, or is the multiplicity only in the notifications?

Also, would it be possible for you to attach (or mail me) your
~/.local/share/evolution/tasks/${some-long-random-name}/tasks.ics file
along with information about which task went off 3x?

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

Title:
  Alarms go off 3 times on mako and flo

Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  Sync your calendar to Ubuntu device
  Have events in your calendar.
  Wait for an a event
  Alarm goes off.
  Listen to the gently plucked harp.
  Press the dismiss button on the popup
  Wait a short while.
  Alarm goes off again.
  Get annoyed at the harp
  Press the dismiss button on the popup
  Wait a short while
  Alarm goes off again
  Shout at phone.

  I would expect the alarm to go off once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1338939/+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 1340248] Re: Multiple events at once triggers multiple sounds

[Charles Kerr]

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

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

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

Title:
  Multiple events at once triggers multiple sounds

Status in “indicator-datetime” package in Ubuntu:
  Triaged

Bug description:
  Schedule two events in your calendar at the same time.
  Wait for the time to come
  You'll get a reminder for both with the sound playing in parallel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1340248/+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 1340830] [NEW] Regression: Cannot install signatures in Utopic any more

[Till Kamppeter]

Public bug reported:

In the script /usr/share/system-config-printer/install-printerdriver.py
I use package kit to add a repository to install printer driver
packages, install the signature for te repository and finally install
the driver package from the repository, to get a secure installation and
the system's update facility also updating my printer driver package if
an update gets available.

Under Trusty this works correctly, but under Utopic it stopped working.

Under Utopic I get the following if I run the Python statements of the
script one by one at the Python prompt:

--
till@till-twist:~$ python
Python 2.7.7 (default, Jun  4 2014, 05:21:28) 
[GCC 4.8.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from gi.repository import GLib, PackageKitGlib
>>> import sys
>>> def progress(progress, type, user_data):
... pass
... 
>>> repo_gpg_id = "E5220FB7014D0FBDA50DFC2BE5E86C008AA65D56"
>>> pk = PackageKitGlib.Client()
>>> res = pk.install_signature(PackageKitGlib.SigTypeEnum.GPG, repo_gpg_id, '', 
>>> None, progress, None)
Traceback (most recent call last):
  File "", line 1, in 
GLib.Error: g-dbus-error-quark: Error calling StartServiceByName for 
org.freedesktop.PackageKit: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited 
with unknown return code 1 (25)
>>> 
--

The signature key is from Epson. I also tried with the key

F8897B6F00075648E248B7EC24CBF5474CFD1E2F

from OpenPrinting and got the same result.

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

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

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

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

Title:
  Regression: Cannot install signatures in Utopic any more

Status in “aptdaemon” package in Ubuntu:
  New
Status in “packagekit” package in Ubuntu:
  New

Bug description:
  In the script /usr/share/system-config-printer/install-
  printerdriver.py I use package kit to add a repository to install
  printer driver packages, install the signature for te repository and
  finally install the driver package from the repository, to get a
  secure installation and the system's update facility also updating my
  printer driver package if an update gets available.

  Under Trusty this works correctly, but under Utopic it stopped
  working.

  Under Utopic I get the following if I run the Python statements of the
  script one by one at the Python prompt:

  --
  till@till-twist:~$ python
  Python 2.7.7 (default, Jun  4 2014, 05:21:28) 
  [GCC 4.8.3] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> from gi.repository import GLib, PackageKitGlib
  >>> import sys
  >>> def progress(progress, type, user_data):
  ... pass
  ... 
  >>> repo_gpg_id = "E5220FB7014D0FBDA50DFC2BE5E86C008AA65D56"
  >>> pk = PackageKitGlib.Client()
  >>> res = pk.install_signature(PackageKitGlib.SigTypeEnum.GPG, repo_gpg_id, 
'', None, progress, None)
  Traceback (most recent call last):
File "", line 1, in 
  GLib.Error: g-dbus-error-quark: Error calling StartServiceByName for 
org.freedesktop.PackageKit: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited 
with unknown return code 1 (25)
  >>> 
  --

  The signature key is from Epson. I also tried with the key

  F8897B6F00075648E248B7EC24CBF5474CFD1E2F

  from OpenPrinting and got the same result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1340830/+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 1340352] Re: kern.log: "bluetooth-touch main process terminated with status 1"

[Jon Snitow Solera]

Fix worked!  I now have a Bluetooth indicator, settings behave normally,
problem seems resolved.

My BT keyboard is not detected, but cyphermox_ indicated that that's a
separate issue -- BT keyboards are not yet supported.  I'll file a
separate bug.

Leaving this bug open until /etc/init/bluetooth-touch-deb.conf ships
with the installation.

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

Title:
  kern.log: "bluetooth-touch main process terminated with status 1"

Status in “bluetooth-touch” package in Ubuntu:
  New

Bug description:
  I'm using a Nexus 7 LTE, with the July 7 utopic release.

  At the user level, nothing Bluetooth works.  I don't get the BT
  indicator.  I go to Settings and try to turn BT on, but it doesn't
  stick.

  When I tried to investigate, the only clue I found was in kern.log,
  which contains a few messages of the form "bluetooth-touch main
  process (691) terminated with status 1"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1340352/+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 1340829] [NEW] unity dash database loading is not automatic

[shantanu saha]

Public bug reported:

Unity dash takes 10-15 seconds (intel corei7) to load initial data
(applications, files etc). It only happen first time and when data
loaded, unity search performance is good and excepted. Problem is that
initial load is not automatic or doesn't start in background. Doesn't
matter how many much time you spend after log in into system, whenever
you open the dash first time, it will start the initialization.

How to regenerate:
1. Log in into desktop
2. Wait as many time as you want
3. Open dash and wait, initially no data will be available but searching 
animation. After 10-15 seconds data will be loaded and animation will stop. 
After that searching in dash in quick.

What should be the behavior?
1. As soon as user log in, system should initialized unity dash data, doesn't 
matter user open dash or not. Initialization time is acceptable but it should 
start in background automatically.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.1+14.04.20140513-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Fri Jul 11 22:12:24 2014
InstallationDate: Installed on 2014-06-08 (32 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  unity dash database loading is not automatic

Status in “unity” package in Ubuntu:
  New

Bug description:
  Unity dash takes 10-15 seconds (intel corei7) to load initial data
  (applications, files etc). It only happen first time and when data
  loaded, unity search performance is good and excepted. Problem is that
  initial load is not automatic or doesn't start in background. Doesn't
  matter how many much time you spend after log in into system, whenever
  you open the dash first time, it will start the initialization.

  How to regenerate:
  1. Log in into desktop
  2. Wait as many time as you want
  3. Open dash and wait, initially no data will be available but searching 
animation. After 10-15 seconds data will be loaded and animation will stop. 
After that searching in dash in quick.

  What should be the behavior?
  1. As soon as user log in, system should initialized unity dash data, doesn't 
matter user open dash or not. Initialization time is acceptable but it should 
start in background automatically.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Jul 11 22:12:24 2014
  InstallationDate: Installed on 2014-06-08 (32 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1340829/+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 1331224] Re: "Split Screen" with latest ubuntu kernel update

[Kamal Mostafa]

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

** This bug has been marked a duplicate of bug 1339768
   VMWare graphics driver regression

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

Title:
  "Split Screen" with latest ubuntu kernel update

Status in “xorg” package in Ubuntu:
  New

Bug description:
  ### Symptom ###
  Since, the latest automatic update via Update Manager, the screen is mirrored 
horizontally three times. Please, find the attached screen shot.

  ### Hint ###
  According to the following source an incompatibility between vmware, may be 
its graphics driver and the kernael 3.2.0-64-generic seem to be reproducable:
  https://communities.vmware.com/message/2389442

  ### System ###
  vmware 6.0.2 build-1744117
  ubuntu 12.04 LTS
  Memory: 1.4 GiB
  CPU: Intel® Core™ i5 CPU M 520 @ 2.40GHz × 2 
  Graphics: Unknown
  OS-Type: 32-bit
  Disk: 20.2 GB
  Kernel: Linux ubuntu 3.2.0-64-generic #97-Ubuntu SMP Wed Jun 4 22:03:48 UTC 
2014 i686 i686 i386 GNU/Linux
  Linux ubuntu 3.2.0-64-generic #97-Ubuntu SMP Wed Jun 4 22:03:48 UTC 2014 i686 
i686 i386 GNU/Linux

  
  Please, let me know if you need further information.

  
  Thank you.

  
  Best regards, 

  Jörg

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-64.97-generic 3.2.59
  Uname: Linux 3.2.0-64-generic i686
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  Date: Wed Jun 18 00:35:16 2014
  DistroCodename: precise
  DistroVariant: ubuntu
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  MarkForUpload: True
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to precise on 2013-01-30 (503 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1331224/+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 1311899] Re: Popup is too small to display Facebook authorization

[Launchpad Bug Tracker]

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

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

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

Title:
   Popup is too small to display Facebook authorization

Status in “gnome-online-accounts” package in Ubuntu:
  Confirmed

Bug description:
  Description of problem:
  Unable to grant permissions to Gnome application on Facebook due to window 
size.

  Version-Release number of selected component (if applicable):
  gnome-online-accounts-3.8.5-7.el7.x86_64

  How reproducible:
  always

  Steps to Reproduce:
  0. Remove Gnome from: https://www.facebook.com/settings?tab=applications
  1. Login to Facebook through Online Accounts

  Actual results:
  "Your popup is too small to display this page. Please enlarge it to proceed."
  see screenshot

  Expected results:
  Webview dialog asking to give permissions to Gnome application on Facebook.

  This bug report is copied from:
  https://bugzilla.redhat.com/show_bug.cgi?id=1081520

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-online-accounts 3.10.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Apr 23 23:47:07 2014
  InstallationDate: Installed on 2012-12-07 (502 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1311899/+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 1340814] [NEW] Cannot send or receive photos

[Michael Terry]

Public bug reported:

This is with r119.

I tried to send and receive a photo with a friend (who was using some
non-Ubuntu phone).  Neither worked.  When I sent my photo, it looked
like it worked locally.  But she never received the photo.  And when she
sent one to me, I never got it.

This may not be the right component for the bug.  But it's the user-
facing side, so I figured I'd start here.

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

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

Title:
  Cannot send or receive photos

Status in “messaging-app” package in Ubuntu:
  New

Bug description:
  This is with r119.

  I tried to send and receive a photo with a friend (who was using some
  non-Ubuntu phone).  Neither worked.  When I sent my photo, it looked
  like it worked locally.  But she never received the photo.  And when
  she sent one to me, I never got it.

  This may not be the right component for the bug.  But it's the user-
  facing side, so I figured I'd start here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1340814/+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 1308037] Re: No results from application scope

[Mateusz Stachowski]

That's this bug. Mark it as affecting you.

You could reload Unity with this command:

unity &> /dev/null & disown

But it may result in some 3rd party indicators not showing up after the
reload. Note that all the default indicators will work.

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

Title:
  No results from application scope

Status in LibUnity:
  Confirmed
Status in Unity Applications Lens:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Unity is in a state where I don't get any results from the
  applications lens. This sometimes happens for one search but either
  re-entering the search or toggling the lens has always fixed it in the
  past for me. This time neither of these steps work.

  I'm attaching a bustle log of the problem in case that's helpful. I
  searched for "spotify", which I've got installed, and got 0 results.

  The only way to fix the issue is to log out and back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 13:29:40 2014
  InstallationDate: Installed on 2012-10-07 (554 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1308037/+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 1339124] Re: Event alarm triggers twice at the event time

[Alan Pope ㋛]

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

** No longer affects: ubuntu-calendar-app

** This bug has been marked a duplicate of bug 1338939
   Alarms go off 3 times on mako and flo

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

Title:
  Event alarm triggers twice at the event time

Status in “indicator-datetime” package in Ubuntu:
  Confirmed

Bug description:
  Mako running 116

  Expected:

  Alarm for an event happens 10 mins before the event

  Actual:

  Alarm goes off at the event, gets dismissed, then goes off again right
  after

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1339124/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

[Ayala Shani]

I can confirm yh1000 approach has solved it for me too:

sudo add-apt-repository ppa:attente/java-non-latin-shortcuts
sudo apt-get update
sudo apt-get dist-upgrade
and then "restart unity-settings-daemon"

I think I'll stick with this version (14.04) of Ubuntu for a long time
now without upgrading...

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

Status in Aptana Studio Installer:
  New
Status in Default settings for the Baltix GNU/Linux OS and desktop:
  New
Status in LibreOffice Productivity Suite:
  Confirmed
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  New
Status in MonoDevelop:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “sublime-text” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1337753] Re: [mako] can not create an ad-hoc network

[Tony Espy]

By the way, here's the mako WiFi driver version info logged in the
kernel:

wlan: WCNSS WLAN version 1.4.1.2
wlan: WCNSS software version 201038
wlan: WCNSS hardware version WCN v2.0 RadioPhy vIris_TSMC_2.0 with 48MHz XO

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

Title:
  [mako] can not create an ad-hoc network

Status in “linux-mako” package in Ubuntu:
  New
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “wpa” package in Ubuntu:
  Incomplete

Bug description:
  When trying to create an adhoc network using network-manager with mako
  kernel "Linux ubuntu-phablet 3.4.0-5-mako #28-Ubuntu SMP PREEMPT Fri
  Mar 28 15:20:22 UTC 2014 armv7l armv7l armv7l GNU/Linux" the creation
  fails with:

  NetworkManager[1347]:  Activation (wlan0) starting connection 'Ubuntu 
hotspot'
  wpa_supplicant[1735]: wlan0: CTRL-EVENT-SCAN-STARTED 
  kernel: [ 1202.120128] wlan: [1352:E :SME] csrMoveTempScanResultsToMainList: 
2908: 11d AP Bssid 00:1e:ab:04:92:77 chan= 1, rssi = -83, countryCode TW
  kernel: [ 1202.120341] wlan: [1352:E :SME] csrMoveTempScanResultsToMainList: 
2908: 11d AP Bssid c8:60:00:dc:42:90 chan= 8, rssi = -66, countryCode GB
  kernel: [ 1202.120616] wlan: [1352:E :SME] csrMoveTempScanResultsToMainList: 
2928: Information about current country Bssid c8:60:00:dc:42:90 chan= 8, rssi = 
-66, countryCode GB
  wpa_supplicant[1735]: wlan0: Trying to associate with SSID 'Ubuntu hotspot'
  NetworkManager[1347]:  (wlan0): supplicant interface state: 
disconnected -> associating
  kernel: [ 1202.989958] wlan: [1352:E :PE ] limMlmAddBss: 1672: TRYING TO HIDE 
SSID 0
  kernel: [ 1202.990477] wlan: [1352:E :PE ] mlm_add_sta: 1573: GF: 0, 
ChnlWidth: 0, MimoPS: 0, lsigTXOP: 0, dsssCCK: 0, SGI20: 0, SGI400
  kernel: [ 1203.007416] wlan: [1352:F :PE ] limProcessIbssMlmAddBssRsp: 2524: 
could not activate Heartbeat timer
  kernel: [ 1203.008087] VOS ASSERT in logDebug Line 219
  kernel: [ 1203.008759] [ cut here ]
  kernel: [ 1203.008850] WARNING: at 
/build/buildd/linux-mako-3.4.0/drivers/staging/prima/CORE/SYS/legacy/src/utils/src/logApi.c:219
 logDebug+0xc0/0xf4()
  kernel: [ 1203.008881] Modules linked in:
  kernel: [ 1203.008972] [] (unwind_backtrace+0x0/0xe8) from 
[] (dump_stack+0x20/0x24)
  kernel: [ 1203.009033] [] (dump_stack+0x20/0x24) from [] 
(warn_slowpath_common+0x5c/0x74)
  kernel: [ 1203.009094] [] (warn_slowpath_common+0x5c/0x74) from 
[] (warn_slowpath_null+0x2c/0x34)
  kernel: [ 1203.009186] [] (warn_slowpath_null+0x2c/0x34) from 
[] (logDebug+0xc0/0xf4)
  kernel: [ 1203.009247] [] (logDebug+0xc0/0xf4) from [] 
(limLog+0x48/0x50)
  kernel: [ 1203.009339] [] (limLog+0x48/0x50) from [] 
(limProcessMlmAddBssRsp+0x168/0xd40)
  kernel: [ 1203.009400] [] (limProcessMlmAddBssRsp+0x168/0xd40) from 
[] (limProcessMessages+0xe74/0x10ac)
  kernel: [ 1203.009491] [] (limProcessMessages+0xe74/0x10ac) from 
[] (limMessageProcessor+0x274/0x2bc)
  kernel: [ 1203.009552] [] (limMessageProcessor+0x274/0x2bc) from 
[] (peProcessMessages+0x54/0x5c)
  kernel: [ 1203.009613] [] (peProcessMessages+0x54/0x5c) from 
[] (VosMCThread+0x44c/0x68c)
  kernel: [ 1203.009705] [] (VosMCThread+0x44c/0x68c) from 
[] (kthread+0x9c/0xa8)
  kernel: [ 1203.009766] [] (kthread+0x9c/0xa8) from [] 
(kernel_thread_exit+0x0/0x8)
  kernel: [ 1203.009827] ---[ end trace 4821fc77d3719675 ]---
  NetworkManager[1347]:  Activation (wlan0/wireless): Ad-Hoc network 
creation took too long, failing activation.
  NetworkManager[1347]:  (wlan0): device state change: config -> failed 
(reason 'supplicant-timeout') [50 120 11]
  wpa_supplicant[1735]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 
reason=3 locally_generated=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1337753/+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 1340745] Re: Cannot be cross compiled

[Launchpad Bug Tracker]

** Branch linked: lp:~dobey/unity-scope-click/cross-build

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

Title:
  Cannot be cross compiled

Status in “unity-scope-click” package in Ubuntu:
  In Progress

Bug description:
  When attempting to cross-compile unity-scope-click, it fails due to
  python3-all not being installable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1340745/+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 1339700] Re: [regression] Device locks randomly on welcome screen

[Alberto Aguirre]

** Changed in: mir
   Status: Fix Committed => In Progress

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

Title:
  [regression] Device locks randomly on welcome screen

Status in Mir:
  In Progress
Status in Mir 0.4 series:
  Triaged
Status in “mir” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Unity8 welcome screen will occasionally lock.

  Lock effects:
  No launcher available
  Can't swipe left or right
  Can't drag down indicators
  Doesn't recover from tapping the power button a couple of times.

  Randomness:
  Locks so far have been happening on and off from image U114
  The phone seems to lock up for me more on waking from suspend, however 
rsalveti pointed out that for him it happened on phone hang up.

  For me the lock happened a couple of times over the weekend images
  U114 and U115, and then not again till today U122.

  Manta seems more prone to lock ups that flo or mako.

  STEPS: (It seems flo has an issue identical when opening settings app)
  On flo update to U123
  1. Once updated, open the settings app
  This seems to land you in the state described.  Apparently this is only a 
temporary version if you leave the device for a while it will unlock.

  But I think that is possibly because you are moved away from the app
  and it is unlocked by the system waking from suspend possibly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.90+14.10.20140707-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: armhf
  Date: Wed Jul  9 13:48:14 2014
  InstallationDate: Installed on 2014-07-09 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140709-020204)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1339700/+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 1316687] Re: Unity stuck in multi window over view

[Launchpad Bug Tracker]

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

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

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

Title:
  Unity stuck in multi window over view

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I'm unable to reproduce this most of the time, it just randomly
  happens.

  Stock install of 14.04, didn't happen on 13.10. Using the nouveau
  driver.

  I've attached a screenshot of the screen as to what happens. The only
  way to get out of this is to switch to a terminal on the console and
  do kill -9 -1. Killing the app just leaves me with the desktop
  background without being able to interact with the WM.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue May  6 12:19:10 2014
  InstallationDate: Installed on 2014-05-04 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1316687/+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 1339700] Re: [regression] Device locks randomly on welcome screen

[PS Jenkins bot]

Fix committed into lp:mir/devel at revision None, scheduled for release
in mir, milestone Unknown

** Changed in: mir
   Status: In Progress => Fix Committed

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

Title:
  [regression] Device locks randomly on welcome screen

Status in Mir:
  In Progress
Status in Mir 0.4 series:
  Triaged
Status in “mir” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Unity8 welcome screen will occasionally lock.

  Lock effects:
  No launcher available
  Can't swipe left or right
  Can't drag down indicators
  Doesn't recover from tapping the power button a couple of times.

  Randomness:
  Locks so far have been happening on and off from image U114
  The phone seems to lock up for me more on waking from suspend, however 
rsalveti pointed out that for him it happened on phone hang up.

  For me the lock happened a couple of times over the weekend images
  U114 and U115, and then not again till today U122.

  Manta seems more prone to lock ups that flo or mako.

  STEPS: (It seems flo has an issue identical when opening settings app)
  On flo update to U123
  1. Once updated, open the settings app
  This seems to land you in the state described.  Apparently this is only a 
temporary version if you leave the device for a while it will unlock.

  But I think that is possibly because you are moved away from the app
  and it is unlocked by the system waking from suspend possibly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.90+14.10.20140707-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: armhf
  Date: Wed Jul  9 13:48:14 2014
  InstallationDate: Installed on 2014-07-09 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140709-020204)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1339700/+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 1339700] Re: [regression] Device locks randomly on welcome screen

[Cemil Azizoglu]

** Tags added: rtm14

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

Title:
  [regression] Device locks randomly on welcome screen

Status in Mir:
  In Progress
Status in Mir 0.4 series:
  Triaged
Status in “mir” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  Unity8 welcome screen will occasionally lock.

  Lock effects:
  No launcher available
  Can't swipe left or right
  Can't drag down indicators
  Doesn't recover from tapping the power button a couple of times.

  Randomness:
  Locks so far have been happening on and off from image U114
  The phone seems to lock up for me more on waking from suspend, however 
rsalveti pointed out that for him it happened on phone hang up.

  For me the lock happened a couple of times over the weekend images
  U114 and U115, and then not again till today U122.

  Manta seems more prone to lock ups that flo or mako.

  STEPS: (It seems flo has an issue identical when opening settings app)
  On flo update to U123
  1. Once updated, open the settings app
  This seems to land you in the state described.  Apparently this is only a 
temporary version if you leave the device for a while it will unlock.

  But I think that is possibly because you are moved away from the app
  and it is unlocked by the system waking from suspend possibly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 7.90+14.10.20140707-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: armhf
  Date: Wed Jul  9 13:48:14 2014
  InstallationDate: Installed on 2014-07-09 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140709-020204)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1339700/+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 1335481] Re: unity-system-compositor crashed with SIGABRT - assertion failed at buffer_queue.cpp:136 - "!pending_client_notifications.empty()"

[Cemil Azizoglu]

** Tags added: rtm14

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

Title:
  unity-system-compositor crashed with SIGABRT - assertion failed at
  buffer_queue.cpp:136 - "!pending_client_notifications.empty()"

Status in Mir:
  New
Status in Mir 0.4 series:
  New
Status in “unity-system-compositor” package in Ubuntu:
  New

Bug description:
  Can't say so much, opened the launched an had a crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity-system-compositor 0.0.4+14.10.20140625-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...    
[ OK ]
* Starting automatic crash report generation: apport    
[ OK ]
  Date: Sat Jun 28 20:23:03 2014
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0136]
 Subsystem: Acer Incorporated [ALI] Device [1025:0136]
  InstallationDate: Installed on 2014-06-19 (9 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64+mac (20140619)
  ProcCmdline: /usr/sbin/unity-system-compositor --file /run/mir_socket 
--from-dm-fd 10 --to-dm-fd 13 --vt 7
  ProcEnviron:
   
  Signal: 6
  SourcePackage: unity-system-compositor
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  Title: unity-system-compositor crashed with SIGABRT in __assert_fail_base()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.54-1
  version.lightdm: lightdm 1.11.3-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1335481/+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 1313443] Re: Cannot restore HDMI display after regular TV session

[Mike O'Driscoll]

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

The workaround from the following bug fixed the issue for me:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1308105

Recommend making this a duplicate.

** This bug has been marked a duplicate of bug 1308105
   Xfce resets TV mode to NULL when power cycled

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

Title:
  Cannot restore HDMI display after regular TV session

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I use my system connected to a TV screen via HDMI. The TV screen is also used 
as a regular TV, input selected to be either HDMI or "antenna". After upgrading 
to 14.04 LTS, after a while of watching regular TV and going back to HDMI 
display, the TV reports "No signal". I try to revive by moving the mouse or 
press the keyboard, but nothing happens. I try to reconnect the HDMI cable, but 
no change. The keyboard and mouse are wireless with a USB reciever/transmitter 
from Logitech. The only way to restore operation is by forced power recycling, 
or connect remotely via ssh and do "reboot".
  I have tried to set the screensaver and power manager so that the computer 
never idles, but there is no improvement.

  I have had some trouble with the NVIDIA driver, the HDMI sound
  configuration is not stable. HDMI sound units come and go between
  boots. Maybe it is connected.

  Nothing of this happened in the previous release, 13.04LTS.
  The desktop display was readily available after setting the HDMI input 
selector on the TV after watching regular channels.

  bnilsson@HTPC:~$ lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-lowlatency 3.13.9
  Uname: Linux 3.13.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Sun Apr 27 22:50:58 2014
  InstallationDate: Installed on 2013-08-24 (246 days ago)
  InstallationMedia: Ubuntu-Studio 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (9 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1313443/+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 1315777] Re: TV displays no signal have turning off then back on.

[Mike O'Driscoll]

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

** This bug is no longer a duplicate of bug 1313443
   Cannot restore HDMI display after regular TV session
** This bug has been marked a duplicate of bug 1308105
   Xfce resets TV mode to NULL when power cycled

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

Title:
  TV displays no signal have turning off then back on.

Status in “xorg” package in Ubuntu:
  New

Bug description:
  $lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  Codename: trusty

  apt-cache policy xorg
  xorg:
Installed: 1:7.7+1ubuntu8
Candidate: 1:7.7+1ubuntu8
Version table:
   *** 1:7.7+1ubuntu8 0

  -System connected to TV via HDMI.
  -Turn off TV.
  -Turn on TV.
  -TV has no signal
  -change to tty1, displays login prompt
  -change to tty7, shows black screen.
  -Must restart lightdm to get a desktop environment to display again.

  Expected that when turning on TV that desktop is shown without issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  3 21:18:41 2014
  InstallationDate: Installed on 2014-01-18 (105 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-04-28 (5 days ago)

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

[Mossroy]

It looks like it's related to a libav bug. See 
https://bugzilla.libav.org/show_bug.cgi?id=597 and 
https://bugzilla.libav.org/show_bug.cgi?id=341
It has been fixed in libav between versions 9.13 and 9.14.

So it looks like Firefox is less permissive than Gstreamer, Chromium and
VLC on WebM files...

In any case, could Firefox output an error message in such cases,
instead of silently failing?

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

Title:
  Firefox can not play some WebM videos generated by avconv on Trusty

Status in The Mozilla Firefox Browser:
  Confirmed
Status in the libav multimedia framework:
  Fix Released
Status in “firefox” package in Ubuntu:
  Invalid
Status in “libav” package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce :
  - Download the source H.264 video attached to this bug
  - On a Trusty machine, convert this video to WebM with "avconv -i 
P5270914.MOV P5270914-trusty.webm". It should give the same result as attached
  - Open this webm file in Totem or in VLC : it plays correctly
  - Open this webm file in Firefox 29. When you click on play, it goes directly 
to the end and does not show anything
  - Open this same webm file in Chromium (tested with version 34) : it plays 
correctly

  If you generate the WebM file on Precise, with the same command-line, it 
plays correctly in Firefox (see attached P5270914-precise.webm).
  So I suppose it comes from a difference in the way avconv does the 
conversion, that is not correctly supported by Firefox

  All tests are made with Precise and Trusty amd64, with all current updates.
  Firefox version 29.0 on both
  avconv 9.13-0ubuntu0.14.04.1 on Trusty, and 0.8.10-0ubuntu0.12.04.1 on Precise

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

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

Re: [Touch-packages] [Bug 1333215] Re: "Unable to find keyfile for application": Does not look for .desktop files in click pkgdir

[Ted Gould]

On Fri, 2014-07-11 at 04:22 +, Martin Pitt wrote:

> Ted Gould [2014-07-10 19:01 -]:
> > If the user session is open (for instance on the phone) the Click
> > hook is run immediately on install and the cache is up-to-date.
> 
> Ah ok, so that seems to be the bit which is broken in some cases then?


Yes, I think that it's not being run with --all-users, where it should
be run for all logged in users in that case.

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

Title:
  "Unable to find keyfile for application": Does not look for .desktop
  files in click pkgdir

Status in Ubuntu Application Launcher:
  Incomplete
Status in “click” package in Ubuntu:
  New
Status in “ubuntu-app-launch” package in Ubuntu:
  Incomplete

Bug description:
  For testing/autopkgtest I want/need to run click apps and their tests
  in a schroot or container, as the turnaround with real phones and the
  emulator is way too large. But in a container, ubuntu-app-launch fails
  with

  $ ubuntu-app-launch `ubuntu-app-triplet com.ubuntu.calculator`

  ** (process:766): WARNING **: Unable to find keyfile for application 
'com.ubuntu.calculator_calculator_1.3.283'
  init: application-legacy 
(com.ubuntu.calculator_calculator_1.3.283-1403523098604203) pre-start process 
(770) terminated with status 1

  In strace I see that it looks for the .desktop file in the following
  locations:


/home/ubuntu/.cache/ubuntu-app-launch/desktop/com.ubuntu.calculator_calculator_1.3.283.desktop

/home/ubuntu/.local/share/applications/com.ubuntu.calculator_calculator_1.3.283.desktop

/usr/local/share/applications/com.ubuntu.calculator_calculator_1.3.283.desktop
/usr/share/applications/com.ubuntu.calculator_calculator_1.3.283.desktop

  but not in the click dir:

  $ click pkgdir com.ubuntu.calculator
  /opt/click.ubuntu.com/.click/users/@all/com.ubuntu.calculator

  The workaround is to create the symlink manually, then it works:

  $  ln -s `click pkgdir com.ubuntu.calculator`/*.desktop 
.cache/ubuntu-app-launch/desktop/`ubuntu-app-triplet 
com.ubuntu.calculator`.desktop
  $ ubuntu-app-launch `ubuntu-app-triplet com.ubuntu.calculator`

  But that's certainly not something that autopkgtest should do.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-app-launch/+bug/1333215/+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 1340632] Re: [QtComp] vertical scroll in launcher is laggy

[Michael Zanetti]

@kgunn, yep, my observations too. Nothing to do with the launcher. So we
don't have screenshots in the spread any more. Its the real apps. Still,
the apps are frozen so they shouldn't update the surfaces in the spread
anyways. I rather think its the rendering engine, given that not only
the spread is slower, but also other things, like the dash and the
launcher.

Anyways, I guess we can close this as duplicate of bug #1337904 then.

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

Title:
  [QtComp] vertical scroll in launcher is laggy

Status in The Unity 8 shell:
  New
Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  What happened:
  I opened 9 apps, causing the launcher to be scrollable. Scrolling the 
launcher is slow and jumpy

  What should have happened:
  Luncher scrolling should be smoooth

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20140710.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-006]
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: armhf
  Date: Fri Jul 11 09:29:14 2014
  InstallationDate: Installed on 2014-07-11 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140711-020204)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8/+bug/1340632/+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 1328264] Re: packaging issues with the trusty Xstack in precise xserver-xorg-lts-trusty

[Guillaume Romagny]

=> confirming original comment :
"Only installing the original precice Xstack (xserver-xorg-lts-precise), which 
removes the current xstack and after that installing the trusty xstack in one 
step without restart, works."

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

Title:
  packaging issues with the trusty Xstack in precise xserver-xorg-lts-
  trusty

Status in “apt” package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've tested the trusty Xstack HWE xserver-xorg-lts-trusty in precise;

  When you have installed another Xstack (e.g.saucy), it is not possible
  to install the trusty Xstack smoothly.

  Only installing the original precice Xstack (xserver-xorg-lts-
  precise), which removes the current xstack and after that installing
  the trusty xstack in one step without restart, works.

  Please help to make that smoother!

  Thanks, Bernhard

  Error Message while trying to install trusty xstack, when saucy xstack
  is installed (in precise);

  apt-get install -V libglapi-mesa-lts-trusty libgl1-mesa-glx-lts-trusty 
xserver-xorg-lts-trusty xserver-xorg-input-all-lts-trusty 
xserver-xorg-video-all-lts-trusty libgl1-mesa-dri-lts-trusty 
x11-xserver-utils-lts-trusty libglapi-mesa-lts-trusty:i386 
libgl1-mesa-dri-lts-trusty:i386 libgl1-mesa-glx-lts-trusty:i386
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libglapi-mesa-lts-trusty : Conflicts: libglapi-mesa
   libglapi-mesa-lts-trusty:i386 : Conflicts: libglapi-mesa
   xserver-xorg-lts-trusty : Conflicts: libglapi-mesa (>= 0~)   

 
 Conflicts: libgles2-mesa (>= 0~)   

 
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1328264/+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 1340758] Re: Conflicts with non-telephony accounts

[Gustavo Pichorim Boiko]

** Changed in: telephony-service (Ubuntu)
 Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko)

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

Title:
  Conflicts with non-telephony accounts

Status in “telephony-service” package in Ubuntu:
  New

Bug description:
  Installing telephony-service means that other telepathy-based
  components (empathy and XMPP in my case) get confused (or ignored).

  Jabber messages come in as SMS, can't open the chat window...
  basically they fight for precedence.

   [...] basically I should make the telephony service components
  ignore the non-telephony accounts

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: telephony-service 0.1+14.10.20140709.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 11 15:37:38 2014
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1340758/+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 1335481] Re: unity-system-compositor crashed with SIGABRT - assertion failed at buffer_queue.cpp:136 - "!pending_client_notifications.empty()"

[Cemil Azizoglu]

** Also affects: mir/0.4
   Importance: Undecided
   Status: New

** Changed in: mir/0.4
   Importance: Undecided => Critical

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

Title:
  unity-system-compositor crashed with SIGABRT - assertion failed at
  buffer_queue.cpp:136 - "!pending_client_notifications.empty()"

Status in Mir:
  New
Status in Mir 0.4 series:
  New
Status in “unity-system-compositor” package in Ubuntu:
  New

Bug description:
  Can't say so much, opened the launched an had a crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity-system-compositor 0.0.4+14.10.20140625-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...    
[ OK ]
* Starting automatic crash report generation: apport    
[ OK ]
  Date: Sat Jun 28 20:23:03 2014
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0136]
 Subsystem: Acer Incorporated [ALI] Device [1025:0136]
  InstallationDate: Installed on 2014-06-19 (9 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64+mac (20140619)
  ProcCmdline: /usr/sbin/unity-system-compositor --file /run/mir_socket 
--from-dm-fd 10 --to-dm-fd 13 --vt 7
  ProcEnviron:
   
  Signal: 6
  SourcePackage: unity-system-compositor
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  Title: unity-system-compositor crashed with SIGABRT in __assert_fail_base()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.54-1
  version.lightdm: lightdm 1.11.3-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1335481/+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 1340758] [NEW] Conflicts with non-telephony accounts

[Michał Sawicz]

Public bug reported:

Installing telephony-service means that other telepathy-based components
(empathy and XMPP in my case) get confused (or ignored).

Jabber messages come in as SMS, can't open the chat window... basically
they fight for precedence.

 [...] basically I should make the telephony service components
ignore the non-telephony accounts

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: telephony-service 0.1+14.10.20140709.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jul 11 15:37:38 2014
SourcePackage: telephony-service
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: telephony-service (Ubuntu)
 Importance: Undecided
 Assignee: Gustavo Pichorim Boiko (boiko)
 Status: New


** Tags: amd64 apport-bug utopic

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

Title:
  Conflicts with non-telephony accounts

Status in “telephony-service” package in Ubuntu:
  New

Bug description:
  Installing telephony-service means that other telepathy-based
  components (empathy and XMPP in my case) get confused (or ignored).

  Jabber messages come in as SMS, can't open the chat window...
  basically they fight for precedence.

   [...] basically I should make the telephony service components
  ignore the non-telephony accounts

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: telephony-service 0.1+14.10.20140709.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 11 15:37:38 2014
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1340758/+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 1308540] Re: [lockscreen] the password entry is not shared between screens

[Launchpad Bug Tracker]

** Branch linked: lp:~andyrock/unity/fix-1308540

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

Title:
  [lockscreen] the password entry is not shared between screens

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  Using trusty candidate on a dual monitor config
  - log into unity
  - lock screen
  - start typing your password on one screen
  - move the pointer on the other screen

  -> the entry is displayed empty

  
  Ideally the same entry would be move so you can keep typing even if you 
happened to have move the focus, that's what lightdm/unity-greeter is doing

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1308540/+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 1304541] Re: Deprecate sheets

[Tim Peeters]

** Changed in: ubuntu-ui-toolkit
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Tim Peeters (tpeeters)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Fix Released

** Changed in: ubuntu-ux
   Status: New => Fix Released

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

Title:
  Deprecate sheets

Status in Ubuntu UI Toolkit:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Released
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Fix Released

Bug description:
  Mark all sheet components as deprecated and remove them in future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1304541/+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 1326963] Re: PageStack.push() eats header action popover close

[Tim Peeters]

** Changed in: ubuntu-ui-toolkit
   Status: Fix Committed => Fix Released

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

Title:
  PageStack.push() eats header action popover close

Status in Ubuntu UI Toolkit:
  Fix Released
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  New

Bug description:
  Simply put, if you push a new page as part of an ontriggered event for
  a toolbar button, and that button is part of a popover, the next event
  on the pushed page is eaten by the popover which fails to close.

  A simple example can be seen here:

  lp:~nskaggs/+junk/pagestack-push

  Run the included example.qml file and click the toobar button entitled
  'Click Me!'. Notice the first click event to the textfield doesn't
  transfer focus as it should.

  Including Tim's running commentary while investigating for more info
  :-)

   the popover that shows the two actions doesn't close properly after 
the new page is pushed
   so that is eating the events.
   if I remove the pageStack.push from the action, it does close the 
popover
   it seems it all works fine, except if in onTriggered, there is a 
pageStack.push().. then the Popover.close() that is called in onTriggered for 
the listitem (which represents the action) is not executed
   when pushing a new page, the list of actions in the header changes, 
which destroys the list items in the popover that shows the actions
   ^ and that happens before the onTriggered of the list item which 
should close the popover is executed
   that messes up things

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1326963/+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 1327189] Re: UITK + Qt 5.3 autopilot failure ubuntuuitoolkit.tests.custom_proxy_objects.test_toolbar.ToolbarTestCase.test_click_toolbar_button

[Tim Peeters]

** Changed in: ubuntu-ui-toolkit
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Tim Peeters (tpeeters)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  UITK + Qt 5.3 autopilot failure
  
ubuntuuitoolkit.tests.custom_proxy_objects.test_toolbar.ToolbarTestCase.test_click_toolbar_button

Status in Ubuntu UI Toolkit:
  Fix Released
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Fix Released

Bug description:
  Two failures were found (out of 249) with Ubuntu UI Toolkit Autopilot
  tests.

  The log for this one is attached.

  ---
  Refer to kept-update info on the front page of 
https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta2 regarding 
where/how to get Qt 5.3. Note that it's not necessarily that PPA itself.

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