[Touch-packages] [Bug 1535058] Re: applications close instantly when launched from the launcher or dash

[David Planella]

I had another go at it, without success. After checking the status of
the cgmanager service on tty1 (not started), I manually started the
service.

I then logged into the Unity 8 session, but apps were still crashing.
Here is some output showing cgmanager errors:

http://pastebin.ubuntu.com/15400866

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

Title:
  applications close instantly when launched from the launcher or dash

Status in cgmanager package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Invalid

Bug description:
  xenial
  applications close instantly when launched from the launcher or dash
  but... if i launch the apps from a VT (for ex firefox using Xmir or gedit 
native --), the app loads ok.

  what close instantly means.. it opens the window and then it closes
  instantly in ~0.3s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1535058/+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 1552693] Re: Radeon driver only provides 1024x768 resolution

[iceboy]

** Also affects: xserver-xorg-video-radeonhd (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Radeon driver only provides 1024x768 resolution

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-radeonhd package in Ubuntu:
  New

Bug description:
  I'm using the latest development version of xenial. My graphics card
  is AMD HD7950 and I use an mini-DP to DP converter to connect it to an
  Acer XB240H monitor. The system works well in Windows 7.

  While using the open source radeon driver, the system was only able to
  detect resolution up to 1024x768:

  $ xrandr
  Screen 0: minimum 320 x 200, current 1024 x 768, maximum 16384 x 16384
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1024x768+0+0 (normal left inverted right x 
axis y axis) 0mm x 0mm
 1024x768  60.00* 
 800x600   60.3256.25  
 848x480   60.00  
 640x480   59.94  
  HDMI-0 disconnected (normal left inverted right x axis y axis)
  DVI-0 disconnected (normal left inverted right x axis y axis)

  $ dmesg | grep drm
  [0.615419] [drm] Initialized drm 1.1.0 20060810
  [0.630977] [drm] radeon kernel modesetting enabled.
  [0.633712] fb: switching to radeondrmfb from VESA VGA
  [0.633863] [drm] initializing kernel modesetting (TAHITI 0x1002:0x679A 
0x1682:0x3221).
  [0.633870] [drm] register mmio base: 0xF7E0
  [0.633870] [drm] register mmio size: 262144
  [0.633935] [drm] Changing default dispclk from 500Mhz to 600Mhz
  [0.633942] [drm] Detected VRAM RAM=3072M, BAR=256M
  [0.633943] [drm] RAM width 384bits DDR
  [0.633980] [drm] radeon: 3072M of VRAM memory ready
  [0.633980] [drm] radeon: 2048M of GTT memory ready.
  [0.633985] [drm] Loading tahiti Microcode
  [0.634037] [drm] Internal thermal controller with fan control
  [0.634064] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
  [0.638427] [drm] radeon: dpm initialized
  [0.639773] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
  [0.639776] [drm] GART: num cpu pages 524288, num gpu pages 524288
  [0.640486] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
  [0.640489] [drm] PCIE gen 3 link speeds already enabled
  [0.655393] [drm] PCIE GART of 2048M enabled (table at 0x002E8000).
  [0.675799] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [0.675800] [drm] Driver supports precise vblank timestamp query.
  [0.675874] [drm] radeon: irq initialized.
  [0.816685] [drm] ring test on 0 succeeded in 1 usecs
  [0.816689] [drm] ring test on 1 succeeded in 1 usecs
  [0.816692] [drm] ring test on 2 succeeded in 1 usecs
  [0.816697] [drm] ring test on 3 succeeded in 3 usecs
  [0.816701] [drm] ring test on 4 succeeded in 2 usecs
  [1.002289] [drm] ring test on 5 succeeded in 1 usecs
  [1.002294] [drm] UVD initialized successfully.
  [1.111494] [drm] ring test on 6 succeeded in 21 usecs
  [1.111505] [drm] ring test on 7 succeeded in 4 usecs
  [1.111505] [drm] VCE initialized successfully.
  [1.111627] [drm] ib test on ring 0 succeeded in 0 usecs
  [1.111648] [drm] ib test on ring 1 succeeded in 0 usecs
  [1.111673] [drm] ib test on ring 2 succeeded in 0 usecs
  [1.111688] [drm] ib test on ring 3 succeeded in 0 usecs
  [1.111702] [drm] ib test on ring 4 succeeded in 0 usecs
  [1.780603] [drm] ib test on ring 5 succeeded
  [2.280602] [drm] ib test on ring 6 succeeded
  [2.780592] [drm] ib test on ring 7 succeeded
  [2.781353] [drm] Radeon Display Connectors
  [2.781354] [drm] Connector 0:
  [2.781354] [drm]   DP-1
  [2.781355] [drm]   HPD5
  [2.781356] [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 
0x653c
  [2.781357] [drm]   Encoders:
  [2.781357] [drm] DFP1: INTERNAL_UNIPHY2
  [2.781358] [drm] Connector 1:
  [2.781358] [drm]   DP-2
  [2.781359] [drm]   HPD4
  [2.781360] [drm]   DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 
0x654c
  [2.781360] [drm]   Encoders:
  [2.781361] [drm] DFP2: INTERNAL_UNIPHY2
  [2.781361] [drm] Connector 2:
  [2.781362] [drm]   HDMI-A-1
  [2.781362] [drm]   HPD1
  [2.781363] [drm]   DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 
0x655c
  [2.781363] [drm]   Encoders:
  [2.781364] [drm] DFP3: INTERNAL_UNIPHY1
  [2.781364] [drm] Connector 3:
  [2.781365] [drm]   DVI-I-1
  [2.781365] [drm]   HPD3
  [2.781366] [drm]   DDC: 0x6580 0x6580 0x6584 0x6584 0x6588 0x6588 0x658c 
0x658c
  [2.781367] [drm]   Encoders:
  [2.781367] [drm] DFP4: INTERNAL_UNIPHY
  [2.781368] [drm] CRT1: INTERNAL_KLDSCP_DAC1
  [2.821395] [drm] fb 

[Touch-packages] [Bug 1558018] Re: Scrolling of icons in Toolbar

[Femma]

** Changed in: ubuntu-ux
 Assignee: (unassigned) => Femma (femma)

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

Title:
  Scrolling of icons in Toolbar

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

Bug description:
  Currently, when the icons do not all fit in the toolbar, an overflow
  button is shown. This needs to be replaced by icon scrolling instead.

  See https://docs.google.com/document/d/1F-zD6CF8YFfA-
  nAtpdRniCqwUNJhSDJVFrRO76A1M-Q/edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1558018/+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 1554616] Re: Shell and dash visual issues with new UITK and palette

[Michael Zanetti]

ok, I've walked through all the issues and what's left for unity8 is

* the notifications text being dark on dark (there's a linked branch for this)
* the launcher quicklist going transparent on pressed

The messaging menu is not a bug. Some changes are expected to happen on
theme changes. The TextFiel Component does now have black background on
the dark theme so that's what it is now.

The others (title in settings page & online account login) are not part
of unity8 and should be addressed by the respective teams.

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

Title:
  Shell and dash visual issues with new UITK and palette

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  There is a set of UI issues with the new UITK and palette, I will
  attach screenshots for each of them with a comment.

  The new UITK is landing here: https://requests.ci-
  train.ubuntu.com/#/ticket/905

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.11+15.04.20160304-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-050]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Tue Mar  8 17:59:10 2016
  InstallationDate: Installed on 2016-03-08 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160308-020304)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554616/+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 1551041] Re: snd_au8820 0000:01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024

[sudodus]

olle@xenial32 ~/tiwai/alsa-driver-build/alsa $ ./gitcompile 
--enable-dynamic-minors --with-oss=no --with-cards=au8820,hda-intel 
--with-sequencer=yes make: Inget behöver göras för ”all-deps”.
./gitcompile: rad 59: aclocal: kommandot finns inte
[1] olle@xenial32 ~/tiwai/alsa-driver-build/alsa $ ./gitcompile 
--enable-dynamic-minors --with-oss=no --with-cards=au8820 --with-sequencer=yes 
make: Inget behöver göras för ”all-deps”.
./gitcompile: rad 59: aclocal: kommandot finns inte

-o-

Where can I find/install aclocal? What about all-deps?

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

Title:
  snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384,
  period size = 1024

Status in alsa-driver package in Ubuntu:
  Triaged

Bug description:
  Kernel oops in a new installed system, that I configuring ...

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic i686
  NonfreeKernelModules: nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  olle   1606 F pulseaudio
   /dev/snd/controlC0:  olle   1606 F pulseaudio
  Date: Mon Feb 29 00:00:56 2016
  Failure: oops
  HibernationDevice: RESUME=UUID=03bed9e9-e39b-4107-8cd6-c2612af9a6aa
  InstallationDate: Installed on 2016-02-28 (0 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160226)
  IwConfig:
   enp31s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP xw8400 Workstation
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=2160f8ed-4aa3-4243-b5d6-f87c1967e253 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9
  RfKill:
   
  SourcePackage: linux
  Title: snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384, 
period size = 1024
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786D5 v02.37
  dmi.board.name: 0A08h
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: NA
  dmi.chassis.asset.tag: CZC722497N
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786D5v02.37:bd07/09/2009:svnHewlett-Packard:pnHPxw8400Workstation:pvr:rvnHewlett-Packard:rn0A08h:rvrNA:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP xw8400 Workstation
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551041/+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 1558018] [NEW] Scrolling of icons in Toolbar

[Tim Peeters]

Public bug reported:

Currently, when the icons do not all fit in the toolbar, an overflow
button is shown. This needs to be replaced by icon scrolling instead.

See https://docs.google.com/document/d/1F-zD6CF8YFfA-
nAtpdRniCqwUNJhSDJVFrRO76A1M-Q/edit

** Affects: ubuntu-ux
 Importance: Undecided
 Assignee: Femma (femma)
 Status: New

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: High
 Assignee: Tim Peeters (tpeeters)
 Status: New

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Tim Peeters (tpeeters)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

** Description changed:

  Currently, when the icons do not all fit in the toolbar, an overflow
  button is shown. This needs to be replaced by icon scrolling instead.
+ 
+ See https://docs.google.com/document/d/1F-zD6CF8YFfA-
+ nAtpdRniCqwUNJhSDJVFrRO76A1M-Q/edit

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

Title:
  Scrolling of icons in Toolbar

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

Bug description:
  Currently, when the icons do not all fit in the toolbar, an overflow
  button is shown. This needs to be replaced by icon scrolling instead.

  See https://docs.google.com/document/d/1F-zD6CF8YFfA-
  nAtpdRniCqwUNJhSDJVFrRO76A1M-Q/edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1558018/+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 1558010] Re: Sections keyboard control

[Tim Peeters]

** Description changed:

  Using the TAB key it must be possible to focus the Sections component in
  the header. The next TAB will go to the next focus item, and does not
  change the selected section. To change the selected section, the left
  and right arrow keys must be used.
  
- See
- 
https://docs.google.com/document/d/1235LE15c9YDBkma1BSBdK5_S9MeZkXs0RncfqIVPJQs/edit
+ UX to be added to:
+ 
https://docs.google.com/document/d/13JoVlVNqn7t5mnwyLc1wa7daozqdGwWj1AqH9LJMid4/edit#heading=h.4nyzngok3pt5

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

Title:
  Sections keyboard control

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

Bug description:
  Using the TAB key it must be possible to focus the Sections component
  in the header. The next TAB will go to the next focus item, and does
  not change the selected section. To change the selected section, the
  left and right arrow keys must be used.

  UX to be added to:
  
https://docs.google.com/document/d/13JoVlVNqn7t5mnwyLc1wa7daozqdGwWj1AqH9LJMid4/edit#heading=h.4nyzngok3pt5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1558010/+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 1558010] [NEW] Sections keyboard control

[Tim Peeters]

Public bug reported:

Using the TAB key it must be possible to focus the Sections component in
the header. The next TAB will go to the next focus item, and does not
change the selected section. To change the selected section, the left
and right arrow keys must be used.

UX to be added to:
https://docs.google.com/document/d/13JoVlVNqn7t5mnwyLc1wa7daozqdGwWj1AqH9LJMid4/edit#heading=h.4nyzngok3pt5

** Affects: ubuntu-ux
 Importance: Undecided
 Assignee: Femma (femma)
 Status: New

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: High
 Assignee: Tim Peeters (tpeeters)
 Status: New

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Tim Peeters (tpeeters)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

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

Title:
  Sections keyboard control

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

Bug description:
  Using the TAB key it must be possible to focus the Sections component
  in the header. The next TAB will go to the next focus item, and does
  not change the selected section. To change the selected section, the
  left and right arrow keys must be used.

  UX to be added to:
  
https://docs.google.com/document/d/13JoVlVNqn7t5mnwyLc1wa7daozqdGwWj1AqH9LJMid4/edit#heading=h.4nyzngok3pt5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1558010/+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 1558010] Re: Sections keyboard control

[Femma]

** Changed in: ubuntu-ux
 Assignee: (unassigned) => Femma (femma)

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

Title:
  Sections keyboard control

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

Bug description:
  Using the TAB key it must be possible to focus the Sections component
  in the header. The next TAB will go to the next focus item, and does
  not change the selected section. To change the selected section, the
  left and right arrow keys must be used.

  UX to be added to:
  
https://docs.google.com/document/d/13JoVlVNqn7t5mnwyLc1wa7daozqdGwWj1AqH9LJMid4/edit#heading=h.4nyzngok3pt5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1558010/+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 1399289] Re: Subtitle support in Header

[Tim Peeters]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Medium => High

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

Title:
  Subtitle support in Header

Status in Ubuntu Document Viewer App:
  Fix Released
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  In the PdfView we are using a multi-line header, that provides
  informations about the name of the file and the current page (as sub-
  text).

  For UX consistence, we should extend the custom header to the Image
  Viewer and the Text Viewer. However it's not clear which information
  should be provided as sub-text.

  See attached screenshot.

  UX:
  This is going to be available in the SDK. The Header title slot might have 
two lines of text

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-docviewer-app/+bug/1399289/+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 1554616] Re: Shell and dash visual issues with new UITK and palette

[Michael Zanetti]

** Branch linked: lp:~unity-team/unity8/more-palette-fixes

** Branch linked: lp:~mzanetti/ubuntu-settings-components/progress-
label-color

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

Title:
  Shell and dash visual issues with new UITK and palette

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  There is a set of UI issues with the new UITK and palette, I will
  attach screenshots for each of them with a comment.

  The new UITK is landing here: https://requests.ci-
  train.ubuntu.com/#/ticket/905

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.11+15.04.20160304-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-050]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Tue Mar  8 17:59:10 2016
  InstallationDate: Installed on 2016-03-08 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160308-020304)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554616/+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 1551041] Re: snd_au8820 0000:01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024

[sudodus]

Following comment #71 caused the following error:

olle@xenial32 ~/linux $ cd ..
olle@xenial32 ~ $ mkdir tiwai; cd tiwai
olle@xenial32 ~/tiwai $ git clone git://github.com/tiwai/alsa-driver-build.git
Klonar till "alsa-driver-build"...
remote: Counting objects: 159995, done.
remote: Total 159995 (delta 0), reused 0 (delta 0), pack-reused 159995
Tar emot objekt: 100% (159995/159995), 37.39 MiB | 4.04 MiB/s, klart.
Analyserar delta: 100% (113780/113780), klart.
Kontrollerar om vi fick alla objekt... klart.
olle@xenial32 ~/tiwai $ git clone git://github.com/tiwai/sound.git
Klonar till "sound"...
remote: Counting objects: 4600984, done.
remote: Compressing objects: 100% (17/17), done.
remote: Total 4600984 (delta 8), reused 8 (delta 8), pack-reused 4600959
Tar emot objekt: 100% (4600984/4600984), 1.42 GiB | 3.51 MiB/s, klart.
Analyserar delta: 100% (3802354/3802354), klart.
Kontrollerar om vi fick alla objekt... klart.
Checkar ut filer: 100% (52938/52938), klart.
olle@xenial32 ~/tiwai $ cd alsa-driver-build
olle@xenial32 ~/tiwai/alsa-driver-build $ git checkout build
Grenen build ställdes in att spåra fjärrgrenen build från origin.
Växlade till en ny gren "build"
olle@xenial32 ~/tiwai/alsa-driver-build $ cd alsa
olle@xenial32 ~/tiwai/alsa-driver-build/alsa $ ./utils/setup-alsa-kernel -c 
../../sound
olle@xenial32 ~/tiwai/alsa-driver-build/alsa $ ./gitcompile --with-debug=full 
gcc utils/mod-deps.c -o utils/mod-deps
utils/mod-deps.c: In function ‘output_card_list’:
utils/mod-deps.c:1086:4: warning: format not a string literal and no format 
arguments [-Wformat-security]
printf(card_name);
^
utils/mod-deps --basedir /home/olle/tiwai/alsa-driver-build/alsa/alsa-kernel 
--hiddendir /home/olle/tiwai/alsa-driver-build/alsa --versiondep 
/home/olle/tiwai/alsa-driver-build/alsa/kconfig-vers --makeconf > 
toplevel.config.in
can't handle 'default SND_SEQUENCER && SND_RAWMIDI', translating as depends on
can't handle 'default SND_SEQUENCER && SND_OPL3_LIB', translating as depends on
can't handle 'default SND_SEQUENCER && SND_OPL4_LIB', translating as depends on
can't handle 'default SND_SEQUENCER && SND_SBAWE', translating as depends on
can't handle 'default SND_SEQUENCER && SND_EMU10K1', translating as depends on
can't handle word INPUT=y properly, supposing it's OK
can't handle word INPUT=SND_ES1968 properly, supposing it's OK
can't handle word VIDEO_V4L2=y properly, supposing it's OK
can't handle word VIDEO_V4L2=SND_ES1968 properly, supposing it's OK
can't handle word VIDEO_V4L2=y properly, supposing it's OK
can't handle word VIDEO_V4L2=SND_FM801 properly, supposing it's OK
can't handle word INPUT=y properly, supposing it's OK
can't handle word INPUT=SND_MAESTRO3 properly, supposing it's OK
can't handle word INPUT=y properly, supposing it's OK
can't handle word INPUT=SND_HDA properly, supposing it's OK
can't handle word SND_HDA_INPUT_BEEP=y properly, supposing it's OK
can't handle word INPUT=y properly, supposing it's OK
can't handle word INPUT=SND_USB_CAIAQ properly, supposing it's OK
can't handle word DW_DMAC_CORE=y properly, supposing it's OK
can't handle word DW_DMAC_CORE=y properly, supposing it's OK
Wrong condition =
Makefile:152: receptet för målet ”toplevel.config.in” misslyckades
make: *** [toplevel.config.in] Fel 1

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

Title:
  snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384,
  period size = 1024

Status in alsa-driver package in Ubuntu:
  Triaged

Bug description:
  Kernel oops in a new installed system, that I configuring ...

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic i686
  NonfreeKernelModules: nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  olle   1606 F pulseaudio
   /dev/snd/controlC0:  olle   1606 F pulseaudio
  Date: Mon Feb 29 00:00:56 2016
  Failure: oops
  HibernationDevice: RESUME=UUID=03bed9e9-e39b-4107-8cd6-c2612af9a6aa
  InstallationDate: Installed on 2016-02-28 (0 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160226)
  IwConfig:
   enp31s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP xw8400 Workstation
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=2160f8ed-4aa3-4243-b5d6-f87c1967e253 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9
  RfKill:
   
  

[Touch-packages] [Bug 1551041] Re: snd_au8820 0000:01:04.0: BUG: , pos = 16386, buffer size = 16384, period size = 1024

[sudodus]

I don't understand the talk about another computer in the link from
comment #71. Does it apply for me?

And the directory structure does not match the instructions. I'm lost
again.

Trying to follow comment #112 caused the following error:

olle@xenial32 ~/linux $ cd ~/tiwai/alsa-driver-build/
olle@xenial32 ~/tiwai/alsa-driver-build $ git checkout build
Redan på "build"
Din gren är à jour med "origin/build".
olle@xenial32 ~/tiwai/alsa-driver-build $ utils/setup-alsa-kernel -c. 
../../sound
bash: utils/setup-alsa-kernel: Filen eller katalogen finns inte
[127] olle@xenial32 ~/tiwai/alsa-driver-build $ utils/setup-alsa-kernel -c. 
../../sound ./gitcompile --enable-dynamic-minors --with-oss=no --with-cards=all 
--with-sequencer=yes
bash: utils/setup-alsa-kernel: Filen eller katalogen finns inte
[127] olle@xenial32 ~/tiwai/alsa-driver-build $ utils/setup-alsa-kernel -c. 
../../sound ./gitcompile --enable-dynamic-minors --with-oss=no --with-cards=all 
--with-sequencer=yes
bash: utils/setup-alsa-kernel: Filen eller katalogen finns inte
[127] olle@xenial32 ~/tiwai/alsa-driver-build $

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

Title:
  snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384,
  period size = 1024

Status in alsa-driver package in Ubuntu:
  Triaged

Bug description:
  Kernel oops in a new installed system, that I configuring ...

  ProblemType: KernelOops
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic i686
  NonfreeKernelModules: nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  olle   1606 F pulseaudio
   /dev/snd/controlC0:  olle   1606 F pulseaudio
  Date: Mon Feb 29 00:00:56 2016
  Failure: oops
  HibernationDevice: RESUME=UUID=03bed9e9-e39b-4107-8cd6-c2612af9a6aa
  InstallationDate: Installed on 2016-02-28 (0 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160226)
  IwConfig:
   enp31s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP xw8400 Workstation
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=2160f8ed-4aa3-4243-b5d6-f87c1967e253 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu9
  RfKill:
   
  SourcePackage: linux
  Title: snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384, 
period size = 1024
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786D5 v02.37
  dmi.board.name: 0A08h
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: NA
  dmi.chassis.asset.tag: CZC722497N
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786D5v02.37:bd07/09/2009:svnHewlett-Packard:pnHPxw8400Workstation:pvr:rvnHewlett-Packard:rn0A08h:rvrNA:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP xw8400 Workstation
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551041/+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 1556860] Re: Blank left panel header after resizing AdaptivePageLayout from two panels to one and back

[Tim Peeters]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Blank left panel header after resizing AdaptivePageLayout from two
  panels to one and back

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  UITK r1888

  Environment:
  Windowed mode, Vivid+OverlayPPA

  Steps to reproduce:
  1) Launch UI Toolkit Gallery
  2) Scroll left panel until the header animates out of screen
  3) Resize window so that only the left panel is shown
  4) Resize window until it shows both left and right panels

  Expected Outcome:
  The Header comes back into view

  Actual Outcome:
  Header doesn't show, and its place is taken by a blank box.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1556860/+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 1536632] Re: MMS is only received from "unknown sender"

[Patrick Poulin]

Sorry for late reply, as I have not used the E5 for quite some time. I
have just switched carrier and now tested MMS and are now receiving MMS'
with correct sender ID.

Problem solved :) Thanks Pat

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

Title:
  MMS is only received from "unknown sender"

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New

Bug description:
  When I receive a MMS, the message is received and put under "Unknown
  sender" in the app.

  Expected behaviour would be either to show the contact name or telefon
  number of the sender.

  Might add that I am using SIM2 only, due to hardware fail in my SIM1
  tray.

  Device: BQ E5
  Build number: 229 - but have had this issue since release of the phone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536632/+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 1554897] Re: With silo050 if an app has a black background it flickers temporarily to white at startup

[Tim Peeters]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  With silo050 if an app has a black background it flickers temporarily
  to white at startup

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  With silo050 if an app has a black background it flickers temporarily
  to white at startup

  What happened:
  1) Ensure you are using the latest UITK from silo050
  2) Install the linked [0] branch which has a black/dark background (similar 
to the Music app)
  3) Launch the application
  4) Notice as it is launched that once the splash disappears, it temporarily 
goes to a white backgound causing a large flicker

  What I expected to happen:
  At step 4) for there to be no flicker

  Note, I've also noticed that the indicators and scopes do the same at
  startup of the device.

  0 - https://code.launchpad.net/~ahayzen/+junk/test-black-bg-startup-
  white

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1554897/+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 1557707] Re: [Sections] selectedIndex binding is broken if the model changes

[Tim Peeters]

What is the use case for the behavior requested in this bug?

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Incomplete

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

Title:
  [Sections] selectedIndex binding is broken if the model changes

Status in Canonical System Image:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  If I assign a default value for the selectedIndex, it is expected that
  the binding for this value will be kept until the user selects a
  different section. Changing the model should not affect that, but it
  does, as this example shows:

  import QtQuick 2.0
  import Ubuntu.Components 1.3

  MainView {
  width: 720
  height: 1280

  Page {
  id: myPage
  anchors.fill: parent
  title: "Click the page"
  header: PageHeader {
  id: pageHeader
  title: myPage.title

  extension: Sections {
  id: pageSections

  model: [ "one", "two", "three" ]
  selectedIndex: 1
  }
  }
  MouseArea {
  anchors.fill: parent
  onClicked: pageSections.model = [ "first", "second", "third" ]
  }
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557707/+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 1557988] Re: Crash after resuming from hibernate

[Apport retracing service]

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

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 #1543292, 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/1557988/+attachment/4600950/+files/CoreDump.gz

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1543292

** 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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1557988

Title:
  Crash after resuming from hibernate

Status in network-manager package in Ubuntu:
  New

Bug description:
  Computer hibernated due to low power, on resume the system report
  appeared.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar 15 21:36:40 2016
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-07-22 (238 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x4c3a4d:  mov0x168(%rax),%r11d
   PC (0x004c3a4d) ok
   source "0x168(%rax)" (0x0168) not located in a known VMA region (needed 
readable region)!
   destination "%r11d" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-03-02 (14 days ago)
  UserGroups:
   
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1557988/+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 1557984] Re: lightdm.override: Please start lightdm after urandom (init script) has executed

[Daniel van Vugt]

Although I'm not sure the phone is actually running urandom on normal start-up. 
In that case, lightdm might have to explicitly call:
   /etc/init.d/urandom start

** Also affects: lightdm
   Importance: Undecided
   Status: New

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

Title:
  lightdm.override: Please start lightdm after urandom (init script) has
  executed

Status in Light Display Manager:
  New
Status in ubuntu-touch-session package in Ubuntu:
  New

Bug description:
  lightdm.override: Please start lightdm after urandom (init script) has
  executed

  The next version of Mir needs this to ensure /dev/urandom has been
  initialized before lightdm spawns unity-system-compositor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1557984/+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 1557984] [NEW] lightdm.override: Please start lightdm after urandom (init script) has executed

[Daniel van Vugt]

Public bug reported:

lightdm.override: Please start lightdm after urandom (init script) has
executed

The next version of Mir needs this to ensure /dev/urandom has been
initialized before lightdm spawns unity-system-compositor.

** Affects: lightdm
 Importance: Undecided
 Status: New

** Affects: ubuntu-touch-session (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  lightdm.override: Please start lightdm after urandom (init script) has
  executed

Status in Light Display Manager:
  New
Status in ubuntu-touch-session package in Ubuntu:
  New

Bug description:
  lightdm.override: Please start lightdm after urandom (init script) has
  executed

  The next version of Mir needs this to ensure /dev/urandom has been
  initialized before lightdm spawns unity-system-compositor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1557984/+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 1281580] Re: glib-compile-schemas doesn't compile relocatable schemas

[ksamak]

Hi,
We at hypra make accessibility features, and a configuration package suite, 
mate-accessibility.
This bug is seriously jeopardising any attempt at a clean default set of 
relocatable schemas, and forces us to configure each impaired user machine by 
hand, or remotely.
We use compiz, and are currently engaged in re-introducing it in debian 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816652).
We aim at introducing the mate-accessibility packages in debian, and flow it 
into ubuntu as soon as possible. For now, this option is unfortunately closed 
to us.
https://git.hypra.fr/hypra/mate-accessibility

please consider fixing this. thank you for reading

** Bug watch added: Debian Bug tracker #816652
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816652

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

Title:
  glib-compile-schemas doesn't compile relocatable schemas

Status in GLib:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Dear Developers,

  I am using the Ubuntu 14.04 development release with the GNOME Shell 3.10 
and, because my wife is using this system as well, I defined some settings in a 
gschema.override file.
  Everything is working right, except applying settings related to custom 
key-bindings.

  I added following lines my gschema.override file:
  [org.gnome.settings-daemon.plugins.media-keys]
  www='w'
  email='e'
  custom-keybindings = 
['/org/gnome/settings-daemon/plugins/media-keys/custom-keybinding/custom0']

  
[org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/]
  name = 'Launch Gedit'
  command = 'gedit'
  binding = 'g'

  I put my gschema.override file in the '/usr/share/glib-2.0/schemas' 
directory. After I added these lines, I ran 'glib-compile-schemas 
/usr/share/glib2.0/schemas' and no error was reported.
  For testing purposes I created a new user, logged out, and logged in with the 
new user. In the best case, the custom key-binding were applied automatically, 
but this has not happened. Other defined key-bindings were applied correctly.
  In the gnome-control-center's key-bindings tab, the table containing  custom 
shortcuts is empty, containing one row with empty columns.

  Running 'gsettings list-recursively org.gnome.settings-daemon.plugins
  .media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins
  /media-keys/custom-keybindings/custom0/' shows, the name, command, and
  binding key pairs contain empty ('') values.

  If I manually run following commands, the custom key-binding is created 
correctly:
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 name "Launch Gedit"
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 command "gedit"
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 binding "g"

  Am I doing anything wrong when I want to add a custom key-bindings in
  my schema file, or  is 'glib-compile-schemas' really not applying this
  part from the schema file?

  Attila

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libglib2.0-bin 2.39.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Feb 18 13:58:37 2014
  InstallationDate: Installed on 2013-12-13 (67 days ago)
  InstallationMedia: BeLin 3.02 i386
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1281580/+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 1557259] Re: typo in the property definitions

[Timo Jyrinki]

** Also affects: qttools-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: qttools-opensource-src (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: qttools-opensource-src (Ubuntu)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

** Changed in: qttools-opensource-src (Ubuntu RTM)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

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

Title:
  typo in the property definitions

Status in qttools-opensource-src package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in qttools-opensource-src package in Ubuntu RTM:
  New

Bug description:
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.ScrollView/

  on the page:

  defaultcontentItem : Item
  The contentItem of the ScrollView. This is set by the user. Note that the 
definition of contentItem is somewhat different to that of a Flickable, where 
the contentItem is implicitly created.

  read-onlyflickableItem : Item

  There should be a space in the property defintions.

  default contentItem: Item

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qttools-opensource-src/+bug/1557259/+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 818737] Re: validity error : ID already defined

[Launchpad Bug Tracker]

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

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

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

Title:
  validity error : ID  already defined

Status in libxslt package in Ubuntu:
  Confirmed

Bug description:
  Hi!
  I have an xhtml I want to transform. It was processed by html tidy, so it is 
a valid xhtml. But It fails to transform with 
  o.xml:845: element a: validity error : ID top already defined

  This is a single top id in the whole doc.
  I extracted the part
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
  http://www.w3.org/1999/xhtml;>
  
  
  
  
  
  
  The Developer's Guide
  
  
  
   but still get the error.
  cmd is
  xsltproc --novalid --html -o out.htm  t.xsl /tmp/3.htm
  if I skip --html it works. (I'm not sure what --html does, but without it 
xsltproc complains on named entities)
  Anyway, having name and id with same value in the same tag is VALID, so it 
shouldn't complain. 
  see http://www.w3.org/TR/html4/struct/links.html#h-12.2.3

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: xsltproc 1.1.26-6
  ProcVersionSignature: Ubuntu 2.6.35-30.54-generic 2.6.35.13
  Uname: Linux 2.6.35-30-generic x86_64
  NonfreeKernelModules: nvidia wl
  Architecture: amd64
  Date: Sun Jul 31 07:03:17 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: libxslt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/818737/+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 1541057] Re: unity8-dash crashed with SIGSEGV in QOpenGLContext::shareGroup()

[Daniel van Vugt]

** Information type changed from Private to Public

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

Title:
  unity8-dash crashed with SIGSEGV in QOpenGLContext::shareGroup()

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  the unity8 dash crashed on closing it. now unable to access apps
  scope. installed on desktop

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.11+16.04.20160129-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Feb  2 23:22:36 2016
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2015-12-26 (38 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  SegvAnalysis:
   Segfault happened at: 0x7febf0037370 <_ZNK14QOpenGLContext10shareGroupEv>:   
mov0x8(%rdi),%rax
   PC (0x7febf0037370) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   QOpenGLContext::shareGroup() const () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
  Title: unity8-dash crashed with SIGSEGV in QOpenGLContext::shareGroup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1541057/+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 1557259] Re: typo in the property definitions

[Andrea Bernabei]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Pierre Bertet (bpierre)

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

Title:
  typo in the property definitions

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

Bug description:
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.ScrollView/

  on the page:

  defaultcontentItem : Item
  The contentItem of the ScrollView. This is set by the user. Note that the 
definition of contentItem is somewhat different to that of a Flickable, where 
the contentItem is implicitly created.

  read-onlyflickableItem : Item

  There should be a space in the property defintions.

  default contentItem: Item

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1557259/+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 1557538] Re: Quickmenu initially empty when focusing a textarea

[cm-t arudy]

Rebooted in the while, with the new proposed-rc, same issue, but on some
website, it shouw a full tooltip ("select all/copy") instead of a blank
( " "). webchat.freenode.net or hubl.in for example

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

Title:
  Quickmenu initially empty when focusing a textarea

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Open browser
  Focus an input (in the web content, not browser itself such as url input)
  A tooltip will appear.
  It's a blank tooltip.
  On input text, textarea,...

  
  Arale proposedrc r269

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1557538/+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 1556043] Re: Xorg crash

[lastpokemon]

issue still there despite updating the bios it even got worst

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  xorg crashes and I have to restart the PC, i'm not sure these logs
  collected the new ones after restart or the ones before restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13
  Uname: Linux 3.19.0-51-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  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: Fri Mar 11 11:16:16 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XT [Radeon HD 7470/8470 / R5 
235/310 OEM] [1002:6778] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 7470 [1028:2120]
  InstallationDate: Installed on 2015-08-18 (205 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. OptiPlex 9010
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-51-generic 
root=UUID=c72e9eae-4b5e-496b-bd50-b8e2f78a8f8d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 051FJ8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/10/2013:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA01:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Mar 11 11:06:18 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Optical Mouse MOUSE, id 8
   inputPlantronics Plantronics C310 KEYBOARD, id 9
   inputDell Dell USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3.1~trusty1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1556043/+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 1557607] Re: Xenial container fails to start

[Andrea Bernabei]

~$ pwd=/sys/fs/cgroup/systemd/`awk -F: '/systemd/ { print $3 }' 
/proc/self/cgroup`
~$ echo $pwd
/sys/fs/cgroup/systemd//user.slice/user-1000.slice/session-3.scope
~$ ls -ld $pwd
drwxr-xr-x 2 design design 0 Mar 16 09:29 
/sys/fs/cgroup/systemd//user.slice/user-1000.slice/session-3.scope


** Changed in: lxc (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Xenial container fails to start

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  Environment: 
  Xenial Xurus, 16.04, latest updates as of 14th March 2016, plus a bunch of 
additional silos/ppas that I can provide on request (this is the laptop used by 
the whole team so I wouldn't be surprised if this bug is the result of 
conflicting packages).

  LXC package version:
  lxc 2.0.0~rc10-0ubuntu2

  How to reproduce:
  1) Create a xenial container, I was trying to setup Libertine ( 
https://wiki.ubuntu.com/Touch/Libertine ) so I used 
  libertine-container-manager create -i libertine-test -n "Libertine Test" -t 
lxc -d xenial

  At the end of the creation process I got an error "failed to start
  container".

  ChrisTownsend on IRC #ubuntu-touch suggested using 
  lxc-start -n libertine-test -P ~/.cache/libertine-container --logfile 
start_xenial.out --logpriority DEBUG
  to get some debug output.

  Please find the log at:
  http://pastebin.ubuntu.com/15392545/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1557607/+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 1556043] Re: Xorg crash

[lastpokemon]

I did update the bios but thing got worst!, instead of getting an Xorg
crash once a week now I got it more that two or three times a day, I'm
not doing anything that demands in graphic its just normal operation at
work mainly web browsing and one virtual machine.

[nasho@nasho-OptiPlex-9010:~] 
 $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for nasho: 
A22
12/21/2015
[nasho@nasho-OptiPlex-9010:~]

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  xorg crashes and I have to restart the PC, i'm not sure these logs
  collected the new ones after restart or the ones before restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13
  Uname: Linux 3.19.0-51-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  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: Fri Mar 11 11:16:16 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XT [Radeon HD 7470/8470 / R5 
235/310 OEM] [1002:6778] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 7470 [1028:2120]
  InstallationDate: Installed on 2015-08-18 (205 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. OptiPlex 9010
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-51-generic 
root=UUID=c72e9eae-4b5e-496b-bd50-b8e2f78a8f8d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 051FJ8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/10/2013:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA01:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Mar 11 11:06:18 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Optical Mouse MOUSE, id 8
   inputPlantronics Plantronics C310 KEYBOARD, id 9
   inputDell Dell USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3.1~trusty1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1556043/+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 1540423] Re: QQuickRepeater breaks in asynchronous component creation.

[Timo Jyrinki]

** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => 11

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

Title:
  QQuickRepeater breaks in asynchronous component creation.

Status in Canonical System Image:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  The Repeater QtQuick component causes rendering issues as well as
  problems in the order the components are created, or expected to be
  created by Repeater.

  Upstream bug reported: https://bugreports.qt.io/browse/QTBUG-36826

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540423/+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 1556842] Re: Backport patch so that forceLayout calls layout on more occasions

[Timo Jyrinki]

** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => 11

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

Title:
  Backport patch so that forceLayout calls layout on more occasions

Status in Canonical System Image:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  It is already approved upstream at https://codereview.qt-
  project.org/#/c/151559/

  It will help us with an unstable test (unstable code really) we have
  in unity8 at
  
https://code.launchpad.net/~aacid/unity8/testComboEnsureVisibleFix/+merge/288284

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1556842/+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 1541346] Re: qmlplugindump can not correctly handle singleton types

[Timo Jyrinki]

** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => 11

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

Title:
  qmlplugindump can not correctly handle singleton types

Status in Canonical System Image:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  When exporting singleton types in qmldir files, qmplugindump creates invalid 
output and breaks autocompletion in QtCreator for those qml modules.
  The exports and exportMetaObjectRevisions have invalid values.

  For example:

  Component {
  prototype: "QObject"
  name: "Palette"
  exports: ["Palette -1.-1"]
  exportMetaObjectRevisions: [-1]
  isComposite: true
  Property { name: "normal"; type: "PaletteValues_QMLTYPE_2"; 
isPointer: true }
  Property { name: "selected"; type: "PaletteValues_QMLTYPE_2"; 
isPointer: true }
  }

  Upstream Bug: https://bugreports.qt.io/browse/QTBUG-49284

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1541346/+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 1528082] Re: [regression] Mir servers choose graphics-dummy (or no driver at all) over mesa-kms on a desktop

[Daniel van Vugt]

** Changed in: mir/0.18
   Status: Fix Committed => Won't Fix

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

Title:
  [regression] Mir servers choose graphics-dummy (or no driver at all)
  over mesa-kms on a desktop

Status in Mir:
  Fix Released
Status in Mir 0.18 series:
  Won't Fix
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Mir demo servers fail to start without additional help.

  Running the latest code on a xenial system, I find the Mir demo
  servers fail to start when run from ssh and I am logged into X (or on
  the login screen):

  [1450665937.536318] mirserver: Selected driver: dummy (version 0.19.0)
  ...
  ERROR: /home/dan/bzr/mir/trunk/src/renderers/gl/renderer.cpp(51): Throw in 
function 
mir::renderer::gl::CurrentRenderTarget::CurrentRenderTarget(mir::graphics::DisplayBuffer*)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: DisplayBuffer does not support GL rendering

  This is obviously wrong, because for Mir to choose the dummy driver
  means mesa-kms has returned a platform priority of zero (unsupported).
  Mesa-kms is not "unsupported", it's the right platform!

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1528082/+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 1398984] Re: Bootloop with system language Turkish on the Nexus 4

[Daniel van Vugt]

** Changed in: mir/0.8
   Status: Triaged => Won't Fix

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

Title:
  Bootloop with system language Turkish on the Nexus 4

Status in Mir:
  Fix Released
Status in Mir 0.8 series:
  Won't Fix
Status in Mir 0.9 series:
  Won't Fix
Status in mir package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu RTM:
  Triaged

Bug description:
  Lately, a member (Ümit) of the XDA Developers forum reported that his Nexus 4 
always goes into a bootloop when he sets the system language to Turkish.
  It doesn't matter whether he sets it in the system settings wizard which is 
shown on first boot or in the system settings application.
  If he sets it in the system settings wizard, he won't get to see the OS after 
finishing the setup process, and if he changes the language in the system 
settings application, the phone will hang after a reboot.
  In any case, he will see the spinning "circle of friends" logo but the Unity8 
dash will never appear.

  Here's the link to his first forum post regarding it issue. The discussion 
continues on the next few pages:
  
http://forum.xda-developers.com/nexus-4/general/rom-ubuntu-touch-14-10-utopic-unico-t2324683/post57093935#post57093935

  He's running build #10 in the stable Ubuntu RTM channel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1398984/+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 1378995] Re: "citrain upgrade-device" fails to upgrade mir properly (Mesa driver installed instead of Android makes the phone unbootable).

[Daniel van Vugt]

** Changed in: mir/0.8
   Status: Triaged => Won't Fix

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

Title:
  "citrain upgrade-device" fails to upgrade mir properly (Mesa driver
  installed instead of Android makes the phone unbootable).

Status in Mir:
  Fix Released
Status in Mir 0.8 series:
  Won't Fix
Status in mir package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu RTM:
  Triaged

Bug description:
  When testing a silo, QA folks use the following command :

  citrain upgrade-device  

  However Mir fails to be upgraded properly. Specifically Mesa libs are
  picked up instead of android libs. Details can be found in the
  following log :

  https://pastebin.canonical.com/118445/

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1378995/+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 1523900] Re: Buffer leak during repeated mirscreencasts causes server to be killed

[Daniel van Vugt]

** Changed in: mir/0.18
   Status: Fix Committed => Won't Fix

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

Title:
  Buffer leak during repeated mirscreencasts causes server to be killed

Status in Mir:
  Fix Released
Status in Mir 0.18 series:
  Won't Fix
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Nexus 4 running latest stable image -

  current build number: 25
  device name: mako
  channel: ubuntu-touch/stable/ubuntu
  last update: 2015-12-08 11:53:16
  version version: 25
  version ubuntu: 20151118.2
  version tag: OTA-8
  version device: 20150911
  version custom: 20151118.2

  I'm running the following command to capture a screenshot of a running
  app, the unity shell, the splash screen when apps load etc.

adb shell mirscreencast -m /var/run/mir_socket  -n1

  I'm doing this in a script, across many hundreds of apps, so I'm doing
  it a lot. I'm seeing my script get wedged fairly often with errors
  such as this one:-

  [1449575031.562843]  MirConnectionAPI: Caught exception at client 
library boundary (in release): 
/build/mir-AHj2eT/mir-0.17.1+15.04.20151105.1/src/client/rpc/stream_socket_transport.cpp(168):
 Throw in function virtual void 
mir::client::rpc::StreamSocketTransport::send_message(const 
std::vector&, const std::vector&)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorE
  std::exception::what: Failed to send message to server: Broken pipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1523900/+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 1557707] Re: [Sections] selectedIndex binding is broken if the model changes

[Tim Peeters]

No, changing the model will reset the selectedIndex. We frequently got
(conflicting) requests from apps to change the behavior in the past, to
either keep the value, or to reset it to -1, or to reset it to 0. After
several iterations and discussions, we decided to reset the
selectedIndex to 0 (or -1 for an empty model) when the model changes,
see this bug and the bugs linked in the comments there
https://bugs.launchpad.net/ubuntu-rtm/+source/ubuntu-ui-
toolkit/+bug/1513933

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

Title:
  [Sections] selectedIndex binding is broken if the model changes

Status in Canonical System Image:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  If I assign a default value for the selectedIndex, it is expected that
  the binding for this value will be kept until the user selects a
  different section. Changing the model should not affect that, but it
  does, as this example shows:

  import QtQuick 2.0
  import Ubuntu.Components 1.3

  MainView {
  width: 720
  height: 1280

  Page {
  id: myPage
  anchors.fill: parent
  title: "Click the page"
  header: PageHeader {
  id: pageHeader
  title: myPage.title

  extension: Sections {
  id: pageSections

  model: [ "one", "two", "three" ]
  selectedIndex: 1
  }
  }
  MouseArea {
  anchors.fill: parent
  onClicked: pageSections.model = [ "first", "second", "third" ]
  }
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557707/+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 1557970] Re: systemd crashed with SIGABRT in __GI_raise()

[Apport retracing service]

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

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 #1546886, 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/1557970/+attachment/4600921/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1546886

** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1557970

Title:
  systemd crashed with SIGABRT in __GI_raise()

Status in systemd package in Ubuntu:
  New

Bug description:
  No idea what happened at that time :-(

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-2ubuntu1 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Wed Mar 16 08:21:12 2016
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2016-02-03 (42 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: Dell Inc. XPS 13 9343
  ProcCmdline: /sbin/init splash
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=47f52069-e356-4b2b-bdcb-d7e1b65f3385 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
   __GI_abort () at abort.c:89
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  Title: systemd crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1557970/+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 1517597] Re: [regression] mouse pointer support on emulator is broken

[Daniel van Vugt]

** Changed in: mir/0.19
   Status: Triaged => Won't Fix

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

Title:
  [regression] mouse pointer support on emulator is broken

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.18 series:
  Won't Fix
Status in Mir 0.19 series:
  Won't Fix
Status in Mir 0.20 series:
  Fix Released
Status in android package in Ubuntu:
  In Progress
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu 
rc-test
  2. Wait for it to build
  3. Run with ubuntu-emulator run rc-test
  4. Starts up but the mouse never moves meaning you can't leave the first page 
of the welcome wizard

  EXPECTED:
  I expect the emulator cursor to follow the mouse cursor and be able to click 
on things

  ACTUAL:
  Emulator cursors stay in the top left preventing movement.

  As noted below F6 toggles the input mode.
  The pointer movement is quite slow and jerky.
  You also can no longer initiate an edge swipe even in trackball mode.

  This is a major regression from how the emulator used to perform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1517597/+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 1556684] Re: gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

[Tim]

well I fixed the two places that I found causing warnings, but maybe
there are more in the less utilised code paths. Though pretty sure I
squished the one that was causing the issues (when accountservice didnt
yet have a language registered)

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

Title:
  gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

Status in Ubuntu GNOME:
  New
Status in accountsservice package in Ubuntu:
  New

Bug description:
  I wanted to install Japanese through the gnome-control-center, so I
  opened it, went to the "Region & Language" section, clicked
  "Language", searched for "Japanese", when I found it I clicked on it
  (a tick appeared next to it), and finally I clicked "Done". Now what
  then should have happened is it should have asked me if I wanted to
  install the language packs it would then present to me and I would be
  able to continue with the installation... What instead happened was it
  hanged for a while and then finally outputted in Terminal:

  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
  Segmentation fault (core dumped)

  The full output in Terminal was:

  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)
  
  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
language-selector (missing desktop file)
  
  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)
  
  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't 
get LANG locale -- Copying interrupted
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_country_from_locale: assertion '*locale != '\0'' failed

  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't 
get LANG locale -- Copying interrupted
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed
  
  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
  Segmentation fault (core dumped)

  I have tested this bug and it is present in Ubuntu GNOME 15.10 with
  GNOME 3.18 and 16.04 with GNOME 3.19 VMs, however I cannot reproduce
  it on the host (15.10 with GNOME 3.18).

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.19.90-0ubuntu1~xenial1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 13 20:45:54 2016
  ExecutablePath: /usr/bin/gnome-control-center.real
  InstallationDate: Installed on 2016-03-04 (9 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha i386 
(20160225.1)
  ProcCmdline: /usr/bin/gnome-control-center.real
  SegvAnalysis:
   Segfault happened at: 0xb5b30c10 :  movzbl 
(%ebx),%eax
   PC (0xb5b30c10) ok
   source "(%ebx)" (0x13e9c381) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_utf8_validate () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_variant_new_string () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_variant_new_strv () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1556684/+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 1556842] Re: Backport patch so that forceLayout calls layout on more occasions

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: New => In Progress

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

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

Title:
  Backport patch so that forceLayout calls layout on more occasions

Status in Canonical System Image:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  It is already approved upstream at https://codereview.qt-
  project.org/#/c/151559/

  It will help us with an unstable test (unstable code really) we have
  in unity8 at
  
https://code.launchpad.net/~aacid/unity8/testComboEnsureVisibleFix/+merge/288284

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1556842/+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 1499134] Re: Mir suddenly no longer builds since Mesa 11.0 was introduced: /usr/include/EGL/eglplatform.h:100:35: fatal error: android/native_window.h: No such file or directory

[Daniel van Vugt]

Fix committed but never going to be released.

** Changed in: mir/0.15
   Status: Fix Committed => Won't Fix

** Changed in: mir/0.15
Milestone: 0.15.2 => None

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

Title:
  Mir suddenly no longer builds since Mesa 11.0 was introduced:
  /usr/include/EGL/eglplatform.h:100:35: fatal error:
  android/native_window.h: No such file or directory

Status in Mir:
  Fix Released
Status in Mir 0.15 series:
  Won't Fix
Status in Mir 0.16 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Mir suddenly no longer builds on wily desktop:

  In file included from /usr/include/EGL/egl.h:39:0,
   from 
/home/dan/bzr/mir/trunk/include/platform/mir/graphics/platform.h:24,
   from 
/home/dan/bzr/mir/trunk/src/platforms/android/server/android_buffer_allocator.cpp:20:
  /usr/include/EGL/eglplatform.h:100:35: fatal error: android/native_window.h: 
No such file or directory
  compilation terminated.
  
src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/build.make:77:
 recipe for target 
'src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/android_buffer_allocator.cpp.o'
 failed
  make[2]: *** 
[src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/android_buffer_allocator.cpp.o]
 Error 1
  CMakeFiles/Makefile2:2322: recipe for target 
'src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/all'
 failed
  make[1]: *** 
[src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/all]
 Error 2
  make[1]: *** Waiting for unfinished jobs

  Did build-deps change?

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1499134/+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 1541346] Re: qmlplugindump can not correctly handle singleton types

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: New => In Progress

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

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

Title:
  qmlplugindump can not correctly handle singleton types

Status in Canonical System Image:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  When exporting singleton types in qmldir files, qmplugindump creates invalid 
output and breaks autocompletion in QtCreator for those qml modules.
  The exports and exportMetaObjectRevisions have invalid values.

  For example:

  Component {
  prototype: "QObject"
  name: "Palette"
  exports: ["Palette -1.-1"]
  exportMetaObjectRevisions: [-1]
  isComposite: true
  Property { name: "normal"; type: "PaletteValues_QMLTYPE_2"; 
isPointer: true }
  Property { name: "selected"; type: "PaletteValues_QMLTYPE_2"; 
isPointer: true }
  }

  Upstream Bug: https://bugreports.qt.io/browse/QTBUG-49284

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1541346/+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 1425307] Re: [regression] Exception when running phablet-screenshot [std::exception::what: Attempt to set swap interval on screencast is invalid]

[Daniel van Vugt]

** Changed in: mir/0.13
   Status: Confirmed => Won't Fix

** Changed in: mir/0.14
   Status: Confirmed => Won't Fix

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

Title:
  [regression] Exception when running phablet-screenshot
  [std::exception::what: Attempt to set swap interval on screencast is
  invalid]

Status in Mir:
  Confirmed
Status in Mir 0.12 series:
  Won't Fix
Status in Mir 0.13 series:
  Won't Fix
Status in Mir 0.14 series:
  Won't Fix
Status in mir package in Ubuntu:
  Confirmed
Status in phablet-tools package in Ubuntu:
  New

Bug description:
  current build number: 110
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-02-24 22:35:35
  version version: 110
  version ubuntu: 20150224
  version device: 20150210
  version custom: 20150224

  rsalveti@evasys:~$ phablet-screenshot /tmp/foo.png
  I: Dumping fb0 ...
  [1424817826.846470] Loader: Loading modules from: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/
  [1424817826.847569] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so
  [1424817826.848393] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so
  [1424817826.849583] Loader: Loading module: 
/usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so
  [1424817826.944654]  mircommon: Caught exception at Mir/EGL driver 
boundary (in setSwapInterval): 
/build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp(283): 
Throw in function virtual void 
mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error
  std::exception::what: Attempt to set swap interval on screencast is invalid

  3004 KB/s (3932160 bytes in 1.278s)
  I: Done

  phablet-tools - 1.1+15.04.20150218-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1425307/+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 1540423] Re: QQuickRepeater breaks in asynchronous component creation.

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: New => In Progress

** Changed in: canonical-devices-system-image
   Importance: Undecided => Medium

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

Title:
  QQuickRepeater breaks in asynchronous component creation.

Status in Canonical System Image:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  The Repeater QtQuick component causes rendering issues as well as
  problems in the order the components are created, or expected to be
  created by Repeater.

  Upstream bug reported: https://bugreports.qt.io/browse/QTBUG-36826

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540423/+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 1468027] Re: change default CJK fonts to Noto CJK

[Gunnar Hjalmarsson]

ping

On 2016-03-15 02:39, Gunnar Hjalmarsson wrote:
> ... I'd appreciate if a few Chinese users could install 
> language-selector from the PPA and let us know how Chinese
> characters look in a session with a non-Chinese locale.

Anyone?

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

Title:
  change default CJK fonts to Noto CJK

Status in Fontconfig:
  Fix Released
Status in kubuntu-meta package in Ubuntu:
  In Progress
Status in language-selector package in Ubuntu:
  Fix Released
Status in lubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  just realize that fonts-noto-cjk is available in the repository, finally its 
packaged.
  i don't really know about korean community.
  But for Chinese and Japanese community, i think that the answer is clear.
  noto-cjk is definitely better what we had before, like fonts- wqy and 
fonts-droid.
  Android community had received these complains for years, finally they got 
them fixed on lollipop.
  Fedora also set it as default chinese font start from F21.
  and of course, i still hope that ubuntu could drop those 69-language-selector 
fontconfig files, just like what F13 did.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1468027/+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 1556842] Re: Backport patch so that forceLayout calls layout on more occasions

[Timo Jyrinki]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016

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

Title:
  Backport patch so that forceLayout calls layout on more occasions

Status in Canonical System Image:
  New
Status in qtdeclarative-opensource-src package in Ubuntu:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  It is already approved upstream at https://codereview.qt-
  project.org/#/c/151559/

  It will help us with an unstable test (unstable code really) we have
  in unity8 at
  
https://code.launchpad.net/~aacid/unity8/testComboEnsureVisibleFix/+merge/288284

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1556842/+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 1540423] Re: QQuickRepeater breaks in asynchronous component creation.

[Timo Jyrinki]

** Also affects: qtdeclarative-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qtdeclarative-opensource-src (Ubuntu)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: New => Fix Released

** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
   Status: New => In Progress

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016

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

Title:
  QQuickRepeater breaks in asynchronous component creation.

Status in Canonical System Image:
  New
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  The Repeater QtQuick component causes rendering issues as well as
  problems in the order the components are created, or expected to be
  created by Repeater.

  Upstream bug reported: https://bugreports.qt.io/browse/QTBUG-36826

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540423/+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 1541346] Re: qmlplugindump can not correctly handle singleton types

[Timo Jyrinki]

** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

** Changed in: qtdeclarative-opensource-src (Ubuntu)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: New => In Progress

** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
   Status: New => In Progress

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016

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

Title:
  qmlplugindump can not correctly handle singleton types

Status in Canonical System Image:
  New
Status in qtdeclarative-opensource-src package in Ubuntu:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  When exporting singleton types in qmldir files, qmplugindump creates invalid 
output and breaks autocompletion in QtCreator for those qml modules.
  The exports and exportMetaObjectRevisions have invalid values.

  For example:

  Component {
  prototype: "QObject"
  name: "Palette"
  exports: ["Palette -1.-1"]
  exportMetaObjectRevisions: [-1]
  isComposite: true
  Property { name: "normal"; type: "PaletteValues_QMLTYPE_2"; 
isPointer: true }
  Property { name: "selected"; type: "PaletteValues_QMLTYPE_2"; 
isPointer: true }
  }

  Upstream Bug: https://bugreports.qt.io/browse/QTBUG-49284

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1541346/+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 1556684] Re: gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

[Gunnar Hjalmarsson]

On 2016-03-16 08:29, Tim wrote:
> could it instead just return the inputted locale?

Yes, it would be an easy fix, and wouldn't hurt anywhere else AFAICT.
Would the change help in 16.04 (i.e. are we in a hurry)?

** Package changed: language-selector (Ubuntu) => accountsservice
(Ubuntu)

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

Title:
  gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

Status in Ubuntu GNOME:
  New
Status in accountsservice package in Ubuntu:
  New

Bug description:
  I wanted to install Japanese through the gnome-control-center, so I
  opened it, went to the "Region & Language" section, clicked
  "Language", searched for "Japanese", when I found it I clicked on it
  (a tick appeared next to it), and finally I clicked "Done". Now what
  then should have happened is it should have asked me if I wanted to
  install the language packs it would then present to me and I would be
  able to continue with the installation... What instead happened was it
  hanged for a while and then finally outputted in Terminal:

  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
  Segmentation fault (core dumped)

  The full output in Terminal was:

  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)
  
  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
language-selector (missing desktop file)
  
  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)
  
  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't 
get LANG locale -- Copying interrupted
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_country_from_locale: assertion '*locale != '\0'' failed

  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't 
get LANG locale -- Copying interrupted
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed
  
  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
  Segmentation fault (core dumped)

  I have tested this bug and it is present in Ubuntu GNOME 15.10 with
  GNOME 3.18 and 16.04 with GNOME 3.19 VMs, however I cannot reproduce
  it on the host (15.10 with GNOME 3.18).

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.19.90-0ubuntu1~xenial1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 13 20:45:54 2016
  ExecutablePath: /usr/bin/gnome-control-center.real
  InstallationDate: Installed on 2016-03-04 (9 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha i386 
(20160225.1)
  ProcCmdline: /usr/bin/gnome-control-center.real
  SegvAnalysis:
   Segfault happened at: 0xb5b30c10 :  movzbl 
(%ebx),%eax
   PC (0xb5b30c10) ok
   source "(%ebx)" (0x13e9c381) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_utf8_validate () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_variant_new_string () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_variant_new_strv () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1556684/+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 1556684] [NEW] gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I wanted to install Japanese through the gnome-control-center, so I
opened it, went to the "Region & Language" section, clicked "Language",
searched for "Japanese", when I found it I clicked on it (a tick
appeared next to it), and finally I clicked "Done". Now what then should
have happened is it should have asked me if I wanted to install the
language packs it would then present to me and I would be able to
continue with the installation... What instead happened was it hanged
for a while and then finally outputted in Terminal:

(gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
Segmentation fault (core dumped)

The full output in Terminal was:

** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)

** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
language-selector (missing desktop file)

** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)

(gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't get 
LANG locale -- Copying interrupted

(gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed

(gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_country_from_locale: assertion '*locale != '\0'' failed

(gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't get 
LANG locale -- Copying interrupted

(gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed

(gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
Segmentation fault (core dumped)

I have tested this bug and it is present in Ubuntu GNOME 15.10 with
GNOME 3.18 and 16.04 with GNOME 3.19 VMs, however I cannot reproduce it
on the host (15.10 with GNOME 3.18).

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-control-center 1:3.19.90-0ubuntu1~xenial1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic i686
ApportVersion: 2.20-0ubuntu3
Architecture: i386
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun Mar 13 20:45:54 2016
ExecutablePath: /usr/bin/gnome-control-center.real
InstallationDate: Installed on 2016-03-04 (9 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha i386 
(20160225.1)
ProcCmdline: /usr/bin/gnome-control-center.real
SegvAnalysis:
 Segfault happened at: 0xb5b30c10 :movzbl 
(%ebx),%eax
 PC (0xb5b30c10) ok
 source "(%ebx)" (0x13e9c381) not located in a known VMA region (needed 
readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_utf8_validate () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_new_string () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_new_strv () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: ubuntu-gnome
 Importance: Undecided
 Status: New

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


** Tags: apport-crash gnome3-ppa gnome3-staging i386 patch third-party-packages 
xenial
-- 
gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()
https://bugs.launchpad.net/bugs/1556684
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to accountsservice in Ubuntu.

-- 
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 1557915] Re: bgra support broken on Mali T760

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

** Description changed:

  bgra support seems broken also on Mali T760 and should be disabled in
  qtbase.
+ 
+ The consequence of this bug are black screenshots on some devices.

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

Title:
  bgra support broken on Mali T760

Status in Canonical System Image:
  Triaged
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  bgra support seems broken also on Mali T760 and should be disabled in
  qtbase.

  The consequence of this bug are black screenshots on some devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557915/+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 1557707] Re: [Sections] selectedIndex binding is broken if the model changes

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: New => Triaged

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

Title:
  [Sections] selectedIndex binding is broken if the model changes

Status in Canonical System Image:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  If I assign a default value for the selectedIndex, it is expected that
  the binding for this value will be kept until the user selects a
  different section. Changing the model should not affect that, but it
  does, as this example shows:

  import QtQuick 2.0
  import Ubuntu.Components 1.3

  MainView {
  width: 720
  height: 1280

  Page {
  id: myPage
  anchors.fill: parent
  title: "Click the page"
  header: PageHeader {
  id: pageHeader
  title: myPage.title

  extension: Sections {
  id: pageSections

  model: [ "one", "two", "three" ]
  selectedIndex: 1
  }
  }
  MouseArea {
  anchors.fill: parent
  onClicked: pageSections.model = [ "first", "second", "third" ]
  }
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557707/+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 1557915] Re: bgra support broken on Mali T760

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: New => Triaged

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

Title:
  bgra support broken on Mali T760

Status in Canonical System Image:
  Triaged
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  bgra support seems broken also on Mali T760 and should be disabled in
  qtbase.

  The consequence of this bug are black screenshots on some devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557915/+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 1549490] Re: low resolution checkbox icons

[Adolfo Jayme]

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Triaged

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

Title:
  low resolution checkbox icons

Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  In xenial, if you use totem with some videos and use the selection
  mode the checkboxes are low resolution, it's because the theme ships
  check-selected/unslected.png as 18x18 icons only, we would need svg
  versions...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1549490/+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 1545286] Re: ubuntu-pd instability with rotation, OSK and hdmi plug/unplug

[Daniel van Vugt]

** No longer affects: mir

** No longer affects: mir (Ubuntu)

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

Title:
  ubuntu-pd instability with rotation, OSK and hdmi plug/unplug

Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  In Progress
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Not sure what change - I know I tested ubuntu-pd, specifically
  connecting/disconnecting hdmi and using OSK as part of the landing of
  mir0.19.2, maybe it was a bit of a race with the qtmir/unity8
  landings. Or possibly my image was older than i thought? seeing this
  on moako ubuntu-pd image 140

  stable phone overlay ppa says
  mir 0.19.2 published Feb 11
  qtmir Feb 9
  unity8 Feb 9
  u-s-c Feb 5

  At the moment I see
  1) the OSK won't popup on the n4-screen-as-trackpad
   2) whatever is focused app while connected to hdmi, if you hold the phone in 
portrait mode and unplug - the app will not fill the whole screen or resize 
properly
   as an example http://www.youtube.com/watch?v=9pehRcVwXnE
  and http://www.youtube.com/watch?v=5Z3MFseEBDc
   3) specifically i saw the dash become totally weird (wrong size assets and 
all jumbled) after #2 (only saw this once, haven't been able to repro)
  4) shell seemed to freeze then crash, i could interact with app...but lost 
launcher and app switcher (also only saw once, but got the file)

  one more note: i kind of wonder if this is related to rotation
  http://www.youtube.com/watch?v=0bLnGRdNxvw
  http://www.youtube.com/watch?v=vbvsLzbqofs

  logs attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545286/+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 1557915] Re: bgra support broken on Mali T760

[Timo Jyrinki]

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

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

Title:
  bgra support broken on Mali T760

Status in Canonical System Image:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  bgra support seems broken also on Mali T760 and should be disabled in
  qtbase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557915/+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 1374824] Re: unity-system-compositor crashed: double free or corruption (fasttop) in nouveau_device_del

[Daniel van Vugt]

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

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

Title:
  unity-system-compositor crashed: double free or corruption (fasttop)
  in nouveau_device_del

Status in Mir:
  Incomplete
Status in Unity System Compositor:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 14.10 upgraded from 14.04

  started ubuntu, saw no unity dash no launcher on left. saw this error
  reported. I can launch programs via TTY1 etc.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity-system-compositor 0.0.5+14.10.20140917-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/sbin/unity-system-compositor': double 
free or corruption (fasttop): 0x017c89a0 ***
  Date: Sat Sep 27 14:20:42 2014
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard:
   NVIDIA Corporation GK107M [GeForce GT 750M] [10de:0fe4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Device [17aa:3802]
  InstallationDate: Installed on 2014-02-08 (231 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140208)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --file /run/lightdm-mir-0 --from-dm-fd 12 
--to-dm-fd 21 --vt 8 --enable-hardware-cursor=true
  ProcEnviron:
   
  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fc26beb8a40 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ptr=, str=0x7fc26beb8c08 "double free or 
corruption (fasttop)", action=1) at malloc.c:4996
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3840
   ?? () from /usr/lib/x86_64-linux-gnu/gbm/gbm_gallium_drm.so
   ?? ()
  Title: unity-system-compositor assert failure: *** Error in 
`/usr/sbin/unity-system-compositor': double free or corruption (fasttop): 
0x017c89a0 ***
  UnitySystemCompositorLog:
   Warning: ignoring unrecognised arguments:
   gbm: failed to open any driver (search paths 
/usr/lib/x86_64-linux-gnu/dri:${ORIGIN}/dri:/usr/lib/dri)failed to load driver: 
nouveau
   nvc0_screen_create:652 - Error allocating PGRAPH context for M2MF: -16
  UnitySystemCompositorLogOld:
   Warning: ignoring unrecognised arguments:
   ERROR: 
/build/buildd/mir-0.7.3+14.10.20140918.1/src/platform/graphics/mesa/display_helpers.cpp(242):
 Throw in function int 
mir::graphics::mesa::helpers::DRMHelper::open_drm_device(const 
std::shared_ptr&)
   Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error
   std::exception::what: Error opening DRM device
   123, "No medium found"
  UpgradeStatus: Upgraded to utopic on 2014-09-20 (7 days ago)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.56+git20140920.77dce9a0-0ubuntu0ricotz
  version.lightdm: lightdm 1.11.9-0ubuntu2
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1374824/+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 1557915] Re: bgra support broken on Mali T760

[Timo Jyrinki]

** Changed in: qtbase-opensource-src (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: qtbase-opensource-src (Ubuntu RTM)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

** Changed in: qtbase-opensource-src (Ubuntu RTM)
   Status: New => In Progress

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

Title:
  bgra support broken on Mali T760

Status in Canonical System Image:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  bgra support seems broken also on Mali T760 and should be disabled in
  qtbase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557915/+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 1557873] Re: task btrfs-transacti:1089 blocked for more than 120 seconds

[Martin Pitt]

There is no symptom or error description in your report at all. Dmesg
shows that the btrfs task is hung, but there's still not much to go
with.

** Summary changed:

- Systemd crash
+ task btrfs-transacti:1089 blocked for more than 120 seconds

** Package changed: systemd (Ubuntu) => linux (Ubuntu)

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

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

Title:
  task btrfs-transacti:1089 blocked for more than 120 seconds

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No further information, it popped up to report a an issue, and it was
  systemd I submitted.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  Uname: Linux 4.5.0-040500rc7-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Mar 15 22:14:45 2016
  InstallationDate: Installed on 2015-05-10 (311 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.5.0-040500rc7-generic 
root=UUID=51a981ad-aeb0-4bd7-91c6-2d493155c812 ro rootflags=subvol=@ 
crashkernel=384M-2G:64M,2G-:128M crashkernel=384M-:128M
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-26 (142 days ago)
  dmi.bios.date: 01/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F18i
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-D3H
  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.:bvrF18i:bd01/06/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H: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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557873/+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 1557928] Re: package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Apport retracing service]

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

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 #1557832, 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.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1557832
   package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

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

Title:
  package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 16 00:26:05 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=5c77a969-7f91-4248-ba92-bde1e5aa245d
  InstallationDate: Installed on 2016-03-16 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 2516:0009  
   Bus 001 Device 002: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation STK1AW32SC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=543df7a3-758c-4ba1-a0a3-f3403c518e51 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-03-16 (0 days ago)
  dmi.bios.date: 11/19/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SCCHTAX5.86A.0014.2015.1119.1410
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H91596-202
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSCCHTAX5.86A.0014.2015.1119.1410:bd11/19/2015:svnIntelCorporation:pnSTK1AW32SC:pvrH93322-102:rvnIntelCorporation:rnCherryTrailCR:rvrH91596-202:cvnIntelCorporation:ct3:cvr1.0:
  dmi.product.name: STK1AW32SC
  dmi.product.version: H93322-102
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1557928/+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 1557928] [NEW] package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Redoubts]

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

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-13-generic 4.4.0-13.29
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Mar 16 00:26:05 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
HibernationDevice: RESUME=UUID=5c77a969-7f91-4248-ba92-bde1e5aa245d
InstallationDate: Installed on 2016-03-16 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 2516:0009  
 Bus 001 Device 002: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Intel Corporation STK1AW32SC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=543df7a3-758c-4ba1-a0a3-f3403c518e51 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: initramfs-tools
Title: package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UpgradeStatus: Upgraded to xenial on 2016-03-16 (0 days ago)
dmi.bios.date: 11/19/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SCCHTAX5.86A.0014.2015.1119.1410
dmi.board.name: Cherry Trail CR
dmi.board.vendor: Intel Corporation
dmi.board.version: H91596-202
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrSCCHTAX5.86A.0014.2015.1119.1410:bd11/19/2015:svnIntelCorporation:pnSTK1AW32SC:pvrH93322-102:rvnIntelCorporation:rnCherryTrailCR:rvrH91596-202:cvnIntelCorporation:ct3:cvr1.0:
dmi.product.name: STK1AW32SC
dmi.product.version: H93322-102
dmi.sys.vendor: Intel Corporation

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 16 00:26:05 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=5c77a969-7f91-4248-ba92-bde1e5aa245d
  InstallationDate: Installed on 2016-03-16 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 2516:0009  
   Bus 001 Device 002: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation STK1AW32SC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=543df7a3-758c-4ba1-a0a3-f3403c518e51 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-03-16 (0 days ago)
  dmi.bios.date: 11/19/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SCCHTAX5.86A.0014.2015.1119.1410
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H91596-202
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 

[Touch-packages] [Bug 1557915] Re: bgra support broken on Mali T760

[Timo Jyrinki]

** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016

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

Title:
  bgra support broken on Mali T760

Status in Canonical System Image:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu RTM:
  New

Bug description:
  bgra support seems broken also on Mali T760 and should be disabled in
  qtbase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557915/+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 1557915] [NEW] bgra support broken on Mali T760

[Timo Jyrinki]

Public bug reported:

bgra support seems broken also on Mali T760 and should be disabled in
qtbase.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: qtbase-opensource-src (Ubuntu RTM)
 Importance: Undecided
 Status: New

** Also affects: qtbase-opensource-src (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  bgra support broken on Mali T760

Status in Canonical System Image:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu RTM:
  New

Bug description:
  bgra support seems broken also on Mali T760 and should be disabled in
  qtbase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557915/+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 1550050] Re: repeating phantom key when bt disconnects

[Daniel van Vugt]

** Branch unlinked: lp:mir

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

Title:
  repeating phantom key when bt disconnects

Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.20 series:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Every now and then when having bt mouse/keyboard connected - you will
  see when selecting a text box there is a repeating character (there is
  no specific character, but always repeats)

  It seems to be related somehow to bt devices disconnecting
  the only cure is a reboot

  This was reproduced by turning off the keyboard while holding down a
  key. We suspect the key up event is never delivered. This mimics the
  case where the BT connection drops off momentarily or perhaps an event
  is missed over the BT connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+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 1550050] Re: repeating phantom key when bt disconnects

[Daniel van Vugt]

** 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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1550050

Title:
  repeating phantom key when bt disconnects

Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.20 series:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Every now and then when having bt mouse/keyboard connected - you will
  see when selecting a text box there is a repeating character (there is
  no specific character, but always repeats)

  It seems to be related somehow to bt devices disconnecting
  the only cure is a reboot

  This was reproduced by turning off the keyboard while holding down a
  key. We suspect the key up event is never delivered. This mimics the
  case where the BT connection drops off momentarily or perhaps an event
  is missed over the BT connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+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 1550050] Re: repeating phantom key when bt disconnects

[Launchpad Bug Tracker]

** Branch linked: lp:mir

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

Title:
  repeating phantom key when bt disconnects

Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.20 series:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Every now and then when having bt mouse/keyboard connected - you will
  see when selecting a text box there is a repeating character (there is
  no specific character, but always repeats)

  It seems to be related somehow to bt devices disconnecting
  the only cure is a reboot

  This was reproduced by turning off the keyboard while holding down a
  key. We suspect the key up event is never delivered. This mimics the
  case where the BT connection drops off momentarily or perhaps an event
  is missed over the BT connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+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 1530807] Re: [FHD] Bluetooth cannot be activated on several devices

[Jason Yen]

** Changed in: avila
Milestone: backlog => ww10-2016

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

Title:
  [FHD] Bluetooth cannot be activated on several devices

Status in The Avila project:
  In Progress
Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Using RC proposed 04/01/2016 bluetooth cannot be enabled.

  Tested on a nexus 7.

  Expected behavior:
  Bluetooth slider is moved to on
  Bluetooth activates
  Available devices appear in the list

  Experienced behavior: 
  Bluetooth slider is moved to on
  Activity spinners appear 
  Bluetooth slider moves to off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1530807/+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 1550741] Re: Upgrade failed - unauthenticated package (module-init-tools)

[Michael Vogt]

** Changed in: apt (Ubuntu)
   Status: Confirmed => Fix Committed

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

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

Title:
  Upgrade failed - unauthenticated package (module-init-tools)

Status in apt package in Ubuntu:
  Fix Committed
Status in kmod package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid

Bug description:
  Upgrading an updated (+ hwe) 14.04 to 16.04 fails on module-init-tools
  being unauthentiated

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.8
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Sat Feb 27 15:46:12 2016
  InstallationDate: Installed on 2016-02-27 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to trusty on 2016-02-27 (0 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1550741/+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 1557363] Re: package libatomic1:amd64 4.8.4-2ubuntu1~14.04.1 failed to install/upgrade: package libatomic1:amd64 is already installed and configured

[dino99]

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

** This bug has been marked a duplicate of bug 1407757
   multi-arch packages cannot be installed due to dpkg wrongly detecting them 
as already installed

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

Title:
  package libatomic1:amd64 4.8.4-2ubuntu1~14.04.1 failed to
  install/upgrade: package libatomic1:amd64 is already installed and
  configured

Status in gcc-4.8 package in Ubuntu:
  New

Bug description:
  I am not sure what this error is.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libatomic1:amd64 4.8.4-2ubuntu1~14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-76-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.14.1-0ubuntu3.19
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  Date: Tue Mar 15 13:45:27 2016
  Dependencies:
   gcc-4.8-base 4.8.4-2ubuntu1~14.04.1
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.19-0ubuntu6.7
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.7
  DuplicateSignature: package:libatomic1:amd64:4.8.4-2ubuntu1~14.04.1:package 
libatomic1:amd64 is already installed and configured
  ErrorMessage: package libatomic1:amd64 is already installed and configured
  InstallationDate: Installed on 2014-11-14 (486 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: gcc-4.8
  Title: package libatomic1:amd64 4.8.4-2ubuntu1~14.04.1 failed to 
install/upgrade: package libatomic1:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1557363/+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