date:20150116

As nick stated in comment #7 we need more detailed API than the current
GAction based one. I'm thinking something along the line of having QML
API's that return a progress object when you call methods such as
enableFlightMode. The caller would then use the object to track the
status of the operation.

Once we do have the ability to track the progress of an Operation in the
UI level we can either disable the switches for the duration of the
ongoing operation or animate them with a progress spinner or
something.

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

Title:
  need a transition state for indicators reflecting laggy backends

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged
Status in indicator-network source package in Utopic:
  Confirmed
Status in ubuntu-system-settings source package in Utopic:
  Confirmed
Status in indicator-network source package in Vivid:
  Confirmed
Status in ubuntu-system-settings source package in Vivid:
  Confirmed
Status in unity8 source package in Vivid:
  Triaged
Status in indicator-network package in Ubuntu RTM:
  New
Status in ubuntu-system-settings package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  spawned from efforts in bug 1336715

  because the user's input toggle for airplane mode is both a reflection
  of user intent  the state of the backendand the backend is
  unfortunately variable  lengthy to change (anywhere from 1 to ~10+
  seconds sometimes) we need to have an intermediate/transition
  statee.g. toggle to airplane mode onthen animate somehow that
  there's a transition happening, until it either fails/succeeds

  comment from dizzypaty

  Between the user’s action of toggling the airplane switcher on and/or
  off and the backend updating the state, the indicator icon displayed
  on the statusbar should be the following: network-idle.svg

  
(https://drive.google.com/drive/#folders/0BzbnWoHmYF3aZTA4WHNPYW1jeUE/0BzbnWoHmYF3aS2pVejVicktrdm8/0BzbnWoHmYF3ablBITVByRnpzdEk).

  
  Desired resolution

  Summary: the interface should immediately respond to user input
  confirming the action, even if the backend takes up to 20 seconds to
  actually change state.  Having the UI and backend out of sync for up
  to 30 seconds is not a problem, as long as it always goes back into
  sync after this delay.

  1.When the user changes the flight mode toggle switch it should
  instantly change state.

  2.The backend should then be informed of the state change.

  3.Up to 30 seconds later the backend completes the state change

  Note: The cellular connection indicator should always display the
  backend state, not the current flight mode toggle switch state

  
  Variation - user switches the flight mode toggle on and off rapidly.

  Once a flight mode state change request has been sent to the backend
  but before a conformation that the state change is complete is
  received, all further user interactions should be buffered on the
  client.  When the client receives conformation of the state change
  from the backend it should check to see if the state is in sync with
  its buffer.  If it is in sync nothing happens and the buffer is
  cleared.  If it is not in sync another state change signal is sent to
  the backend and the buffer is cleared.

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

2015-01-16 Thread madbiologist

Posted in the downstream bug report by the original bug reporter on 17th
September 2014:

This problem is still here in Ubuntu 14.04 LTS ... and it has become a serious 
matter.
More and more of my own customers are switching to Ubuntu, which is a positive 
thing IMO. But with the increasing use of online web-services to handle 
billing, document exchanges and online-shopping ... more and more streaming-PDF 
files are being created on-the-fly as everyone is expected to be able to read 
that particular format. But when people can't read the amount due on an invoice 
or the delivery-date on a webshopping receipt, because the font-rendering of 
the pre-installed document viewer in Ubuntu won't display them correctly (or 
sometimes not at all), it really becomes highly inconvenient for both regular 
users as well as more experienced user. The Adobe Reader installation package 
is no longer available in ubuntu 14.04's standard repositories, which was a 
go-to option for the more experienced user.
SO BUCKLE UP PEOPLE, let's see if we can't fix this issue. And hopefully before 
we use a couple of gigabytes on the web in forum- and chatlogs about the 
subject of creating temporary fixes and work-arounds of such a basic thing.

best of luck to all

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

Title:
  Non-embedded standard fonts in PDF files are not displayed/rendered
  correctly

Status in Evince document viewer:
  Unknown
Status in libcairo  -  cairo vector graphics library:
  Confirmed
Status in cairo package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  1)
  Natty:
  lsb_release -rd
  Description:  Ubuntu Natty (development branch)
  Release:  11.04

  Maverick:
  lsb_release -rd
  Description: Ubuntu 10.10
  Release: 10.10

  Lucid:
  Ubuntu 10.04 Lucid Lynx (amd64)

  2)
  Natty:
  apt-cache policy acroread
  acroread:
Installed: 9.4.2-0natty1
Candidate: 9.4.2-0natty1
Version table:
   *** 9.4.2-0natty1 0
  500 http://archive.canonical.com/ubuntu/ natty/partner i386 Packages 
100 /var/lib/dpkg/status

  apt-cache policy evince
  evince:
Installed: 2.32.0-0ubuntu12.1
Candidate: 2.32.0-0ubuntu12.1
Version table:
   *** 2.32.0-0ubuntu12.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386
  Packages
  100 /var/lib/dpkg/status
   2.32.0-0ubuntu12 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  apt-cache policy libcairo2
  libcairo2:
Installed: 1.10.2-2ubuntu2
Candidate: 1.10.2-2ubuntu2
Version table:
   *** 1.10.2-2ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100 
/var/lib/dpkg/status

  Maverick:
  apt-cache policy evince
  evince:
    Installed: 2.32.0-0ubuntu1
    Candidate: 2.32.0-0ubuntu1
    Version table:
   *** 2.32.0-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
  100 /var/lib/dpkg/status

  apt-cache policy libcairo2
  libcairo2:
    Installed: 1.10.0-1ubuntu3
    Candidate: 1.10.0-1ubuntu3
    Version table:
   *** 1.10.0-1ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ maverick-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.10.0-1ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages

  apt-cache policy acroread
  acroread:
    Installed: 9.4-1maverick1
    Candidate: 9.4-1maverick1
    Version table:
   *** 9.4-1maverick1 0
  500 http://archive.canonical.com/ubuntu/ maverick/partner i386 
Packages
  100 /var/lib/dpkg/status

  3) When viewing PDF attachment PDF sample for Evince, which has font
  Times Roman or Helvetica, the text looks different in Evince in
  comparison to Adobe Reader.

  4) What is expected is that it looks the same in both.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: evince 2.30.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic x86_64
  Architecture: amd64
  Date: Thu Oct 28 13:51:21 2010
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Release Candidate amd64 
(20100419.1)
  ProcEnviron:
   LANG=en_DK.utf8
   SHELL=/bin/bash
  SourcePackage: evince

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/667752/+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 1309915] Re: foreground app should keep wakelock open until actual suspend happens (aka camera takes ~5 seconds to be responsive after waking phone)

** Branch linked: lp:~unity-team/qtmir/rtm-20150116

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

Title:
  foreground app should keep wakelock open until actual suspend happens
  (aka camera takes ~5 seconds to be responsive after waking phone)

Status in the base for Ubuntu mobile products:
  In Progress
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu RTM:
  Triaged
Status in unity8 package in Ubuntu RTM:
  Invalid

Bug description:
  while apps that you put in the background are properly SIGSTOPed 
  (this is easy to verify with a music streaming website atm (while the browser 
does not use media-hub it will/should stop playback)).
   An app that is in the foreground will try to play on when the system is 
suspended (easy to verify with the same method, music plays on but becomes 
stuttery if the browser was in the foreground. This indicates the system tries 
to suspend but the running app tries to keep it alive. 

  Unity should send s SIGSTOP/SIGCONT sequence on suspend/resume to the
  app in foreground when the system goes into suspend and resumes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1309915/+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 1223653] Re: CMake: Build pot file

We have translations, there is a .pot which is generated with a custom
target pot_file

** Changed in: indicator-network
   Status: Confirmed = Fix Released

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  CMake: Build pot file

Status in Network Menu:
  Fix Released
Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  
  CMake doesn't seem to be building the indicator-network.pot file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1223653/+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 1365729] Re: On some reboots wifi indicator is missing

Is this still happening?

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed = Incomplete

** Changed in: indicator-network (Ubuntu)
 Assignee: Antti Kaijanmäki (kaijanmaki) = (unassigned)

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) = Omer Akram (om26er)

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

Title:
  On some reboots wifi indicator is missing

Status in indicator-network package in Ubuntu:
  Incomplete

Bug description:
  rtm image 22 mako
  unity8 8.00+14.10.20140827.2-0ubuntu1

  My SIM is working and I am connected to a Wifi network but the wifi
  icon does not appear in the top panel. This happens frequently by re
  multiple reboots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1365729/+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 1300332] Re: [cpp] Manager::createInstance() should return a shared pointer

not relevant anymore.

** Changed in: indicator-network
   Status: Triaged = Won't Fix

** Changed in: indicator-network (Ubuntu)
   Status: Triaged = Won't Fix

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

Title:
  [cpp] Manager::createInstance() should return a shared pointer

Status in Network Menu:
  Won't Fix
Status in indicator-network package in Ubuntu:
  Won't Fix

Bug description:
  Just to be consistent.
  Also then Manager should typedef std::shared_ptrManager Ptr.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1300332/+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 1411581] [NEW] HP CP4525 printer confused by evince (libcairo 1.13.0~20140204-0ubuntu1) font naming mismatch

2015-01-16 Thread Sergio Gelato

Public bug reported:

I have an HP Color LaserJet Enterprise CP4525 with firmware 07.164.1,
which supports PDF files natively (@PJL LANGUAGE=PDF), and a print
server running Debian 7 (cups-filters 1.0.18 and its pdftopdf, and a
PDF-enabled PPD).

I have been given a PDF file (from pdflatex) that uses four Type 1 font
subsets (of four different simple fonts). This file gets printed
correctly with /usr/bin/lp . Not so when using evince on Ubuntu trusty:
then the printer substitutes a different font (but keeping the glyph
widths from the font object in the PDF file, so the letter spacings look
all wrong).

I've inspected the PDF file evince sends to the printer (which is not
identical to the original PDF file: evince rewrites it) and noticed that
the value of /FontName in the font program object doesn't match that of
/FontName in the font descriptor object; the latter does match /BaseFont
in the font object and has the form prescribed in §9.6.4 of the PDF 1.7
specification for font subsets. The /FontName in the font program
object, on the other hand, is of the form /CairoFont-N-M, where N and M
are integers.

If I hand-edit the PDF output by evince, replacing /CairoFont-N-M with
the value of /FontName in the corresponding font descriptor object (and
adjusting /Length and /Length1 as needed), the result gets printed with
the correct fonts.

§9.6.2.1 of the PDF 1.7 specification (PDF 32000-1:2008, retrieved from
Adobe's web site) does say that [f]or Type 1 fonts, [BaseFont] is
always the value of the FontName entry in the font program. One
wonders, then, why Cairo changes the name. I could understand it if it
wanted to make the font descriptors for two different subsets of the
same font share the same font program object; but it doesn't take
advantage of this. The sample file I have contains ligatures and
accented letters, originally represented in a single font subset by
using a non-standard encoding, and evince splits these font subsets into
two parts, one of which uses /WinAnsiEncoding; each of the subsets gets
its own font program object (with a different value of M in
/CairoFont-N-M). So this is not the explanation.

I think it would be prudent, in light of HP's PDF interpreter's
behaviour, for Cairo to adhere more strictly to the wording of §9.6.2.1
and use the same /FontName in the font program object as in the font
descriptor object.

I think I'd also like for pdftopdf to incorporate a workaround for this,
simply because I have more control over the print server than over the
clients. But that's for another (wishlist) bug report.

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

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

Title:
  HP CP4525 printer confused by evince (libcairo
  1.13.0~20140204-0ubuntu1) font naming mismatch

Status in cairo package in Ubuntu:
  New

Bug description:
  I have an HP Color LaserJet Enterprise CP4525 with firmware 07.164.1,
  which supports PDF files natively (@PJL LANGUAGE=PDF), and a print
  server running Debian 7 (cups-filters 1.0.18 and its pdftopdf, and a
  PDF-enabled PPD).

  I have been given a PDF file (from pdflatex) that uses four Type 1
  font subsets (of four different simple fonts). This file gets printed
  correctly with /usr/bin/lp . Not so when using evince on Ubuntu
  trusty: then the printer substitutes a different font (but keeping the
  glyph widths from the font object in the PDF file, so the letter
  spacings look all wrong).

  I've inspected the PDF file evince sends to the printer (which is not
  identical to the original PDF file: evince rewrites it) and noticed
  that the value of /FontName in the font program object doesn't match
  that of /FontName in the font descriptor object; the latter does match
  /BaseFont in the font object and has the form prescribed in §9.6.4 of
  the PDF 1.7 specification for font subsets. The /FontName in the font
  program object, on the other hand, is of the form /CairoFont-N-M,
  where N and M are integers.

  If I hand-edit the PDF output by evince, replacing /CairoFont-N-M with
  the value of /FontName in the corresponding font descriptor object
  (and adjusting /Length and /Length1 as needed), the result gets
  printed with the correct fonts.

  §9.6.2.1 of the PDF 1.7 specification (PDF 32000-1:2008, retrieved
  from Adobe's web site) does say that [f]or Type 1 fonts, [BaseFont]
  is always the value of the FontName entry in the font program. One
  wonders, then, why Cairo changes the name. I could understand it if it
  wanted to make the font descriptors for two different subsets of the
  same font share the same font program object; but it doesn't take
  advantage of this. The sample file I have contains ligatures and
  accented letters, originally represented in a single font subset by
  using a non-standard encoding, and evince splits these font

[Touch-packages] [Bug 1389861] Re: [dialer-app] can't unlock phone during an incoming call

** Package changed: indicator-network (Ubuntu) = unity8 (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/1389861

Title:
  [dialer-app] can't unlock phone during an incoming call

Status in Dialer app for Ubuntu Touch:
  Incomplete
Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  New

Bug description:
  While testing krillin rtm image 142, I noticed that the phone remains
  locked during an incoming call if the screen was off when the call
  came in.  There is no way to unlock the phone to access other
  functions until after the call is done.

  It seems like a common use case to be able to do other things on the
  phone during a call, looking up someone's number or checking a map or
  whatever, but this currently is only possible during outgoing calls.

  During an incoming call I can't even access the indicators to change
  brightness or check today's date or even see what time it is, so it
  actually ends up being more locked than the lock screen.

  Could we add the ability to unlock the phone during a call received
  while locked?

To manage notifications about this bug go to:
https://bugs.launchpad.net/dialer-app/+bug/1389861/+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 1340206] Re: [Network Menu] Enabling flight mode still shows the wifi icon

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

** Changed in: indicator-network (Ubuntu Utopic)
   Status: New = Confirmed

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

Title:
  [Network Menu] Enabling flight mode still shows the wifi icon

Status in Network Menu:
  Triaged
Status in Ubuntu UX bugs:
  Triaged
Status in indicator-network package in Ubuntu:
  Confirmed
Status in indicator-network source package in Utopic:
  Confirmed
Status in indicator-network source package in Vivid:
  Confirmed
Status in Ubuntu RTM:
  New

Bug description:
  When we enable flight mode the wifi icon is still shown.

  https://wiki.ubuntu.com/Networking#Title: On the phone ... the
  title ... should consist of: Flight Mode indication: ✈ the Flight Mode
  icon, if Flight Mode is on, otherwise nothing at all. ... Finally, Wi-
  Fi status indication: ... nothing at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1340206/+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 1408741] Re: [network indicator] tapping the currently connected wifi network cause connection to drop and reconnect

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

** This bug has been marked a duplicate of bug 1322490
   [indicators] Clicking on a connected network's checkbox  disconnects  
re-connects

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

Title:
  [network indicator] tapping the currently connected wifi network cause
  connection to drop and reconnect

Status in Ubuntu UX bugs:
  New
Status in indicator-network package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Not sure if this desirable or not, but I noticed when I opened the
  networking indicator, and tapped on the currently connected network
  (the green one) that the connection was broken and re-established.

  To see, open shell on device and run ping 8.8.8.8. Watch the output,
  then open network indicator and tap on the currently connected
  network. I see the pings fail for a few seconds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1408741/+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 1374082] Re: no API to unlock a specific sim

** Changed in: indicator-network
   Status: In Progress = Fix Released

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

Title:
  no API to unlock a specific sim

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Network Menu:
  Fix Released
Status in indicator-network package in Ubuntu:
  Fix Released
Status in indicator-network source package in Utopic:
  Triaged
Status in indicator-network source package in Vivid:
  Fix Released
Status in indicator-network package in Ubuntu RTM:
  Fix Released

Bug description:
  In dialer-app on dual sim phones users will be given an option to unlock a 
specific modem.
  The current api only supports unlocking all modems at once: 
UnlockAllModems(). We need a way to invoke the unlock screen to a specific 
modem, like UnlockModem(objectPath).

  clients:
  https://bugs.launchpad.net/messaging-app/+bug/1371661

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1374082/+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 1322490] Re: [indicators] Clicking on a connected network's checkbox disconnects re-connects

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

** Changed in: ubuntu-settings-components (Ubuntu)
   Status: New = Confirmed

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

Title:
  [indicators] Clicking on a connected network's checkbox  disconnects 
  re-connects

Status in Network Menu:
  New
Status in Ubuntu UX bugs:
  Triaged
Status in indicator-network package in Ubuntu:
  Triaged
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed

Bug description:
  indicator-network 0.5.1+14.10.20140516.2-0ubuntu1, Ubuntu Utopic

  1. Unlock the phone
  2. Drag down the indicator for networking
  3. Select a wifi AP sign into it
  4. Drag down the indicator for networking
  5. Try to uncheck it.

  What happens: The network disconnects and reconnects.

  What should happen: Nothing.

  https://wiki.ubuntu.com/Networking#wi-fi-menu: 2. If the card is
  powered on, up to 6 (phone) or 20 (PC) radio items representing known
  Wi-Fi networks...

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1322490/+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 1407938] Re: Empty WiFi icon displayed in Flight Mode

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

** This bug has been marked a duplicate of bug 1340206
   [Network Menu] Enabling flight mode still shows the wifi icon

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

Title:
  Empty WiFi icon displayed in Flight Mode

Status in indicator-network package in Ubuntu:
  New

Bug description:
  In line with https://wiki.ubuntu.com/Networking#Title

  Steps:
  * enable Flight mode

  Expected:
  * there is only a plane icon for the networking menu

  Current:
  * there are a plane and a disconnected WiFi icons

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Tue Jan  6 12:01:55 2015
  InstallationDate: Installed on 2014-12-18 (18 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141218-163635)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)
  indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
  upstart.indicator-network.log:
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered
   Attempted to unregister path (path[0] = org path[1] = freedesktop) which 
isn't registered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1407938/+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 1354544] Re: entering WiFi range doesn't switch indicator icon to WiFi

** Changed in: indicator-network
   Status: Incomplete = Invalid

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

Title:
  entering WiFi range doesn't switch indicator icon to WiFi

Status in Network Menu:
  Invalid
Status in indicator-network package in Ubuntu:
  Invalid

Bug description:
  * Connect your phone to a wifi. Make sure connection works.
  * Walk away from the WiFi until the connection drops. The icon in the panel 
will switch to mobile data, in my case show a H. Make sure mobile data 
connection works.
  * Go back to the WiFi. It'll connect automatically and switch traffic over to 
to the faster WiFi connection.

  = The icon in the panel stays on mobile data forever.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1354544/+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 1223652] Re: CMake: Reenable network manager tests

** Changed in: indicator-network
   Status: Confirmed = Fix Released

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

Title:
  CMake: Reenable network manager tests

Status in Network Menu:
  Fix Released
Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  
  The Python based tests were removed to get a C++ implementation.  That needs 
to happen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1223652/+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 1378712] Re: extended data for xCanonicalPinPopup should also have xCanonicalPinPopupTitle

** Changed in: indicator-network
   Status: New = Triaged

** Changed in: unity8 (Ubuntu)
   Status: New = Triaged

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

Title:
  extended data for xCanonicalPinPopup should also have
  xCanonicalPinPopupTitle

Status in Network Menu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  In order to visually align the SIM entry warning popup with the
  passcode warning popup, the text would need to be split into title and
  text.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1378712/+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 1411597] [NEW] [G75VW, VIA VT1802, Speaker, Internal] fails after a while

2015-01-16 Thread Erwan Georget

Public bug reported:

Rhythmbox sound lost, I had to restart it to ear my music again.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  dremor 2198 F pulseaudio
 /dev/snd/pcmC0D0p:   dremor 2198 F...m pulseaudio
 /dev/snd/controlC0:  dremor 2198 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Jan 16 11:00:03 2015
InstallationDate: Installed on 2015-01-15 (1 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Audio interne - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_Type: Sound works for a while, then breaks
Title: [G75VW, VIA VT1802, Speaker, Internal] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/07/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G75VW.223
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G75VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG75VW.223:bd01/07/2013:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G75VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug utopic

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

Title:
  [G75VW, VIA VT1802, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Rhythmbox sound lost, I had to restart it to ear my music again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dremor 2198 F pulseaudio
   /dev/snd/pcmC0D0p:   dremor 2198 F...m pulseaudio
   /dev/snd/controlC0:  dremor 2198 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Jan 16 11:00:03 2015
  InstallationDate: Installed on 2015-01-15 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [G75VW, VIA VT1802, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G75VW.223
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G75VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG75VW.223:bd01/07/2013:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G75VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1411597/+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 1351421] Re: 1 songs played today is not grammatically correct

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

** Changed in: libusermetrics (Ubuntu)
   Status: New = Confirmed

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

Title:
  1 songs played today is not grammatically correct

Status in Music application for Ubuntu devices:
  Confirmed
Status in libusermetrics package in Ubuntu:
  Confirmed

Bug description:
  If I play a single song in the music app, the welcome shows 1 songs
  played today. This is not grammatically correct.

  Here's the relevant chunk from the music-app.qml:

  Metric {
  id: songsMetric
  name: music-metrics
  format: b%1/b  + i18n.tr(songs played today)
  emptyFormat: i18n.tr(No songs played today)
  domain: com.ubuntu.music
  }

  FWICS, it looks like the problem is due to a limitation of
  libusermetrics. If so, two possible solutions come to mind:

  1) Extending libusermetrics to allow the specification of a
  singleFormat: which in this case would be:

  singleFormat: b%1/b  + i18n.tr(song played today)  // It's
  now song, not songs

  2) Having some JS construct the format dynamically based on the value
  somehow? The problem there being that every app that wanted to get
  this right would need to implement the JS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1351421/+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 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

2015-01-16 Thread AndreK

how to get these files from  Ubuntu 15.04 (Vivid)  - whithout installing
it ?

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

Title:
  Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

Status in steam package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am cross-posting this issue, which I reported to Valve's Source GIT
  issue tracker, because it was suggested that the regression may be due
  to Ubuntu Xorg changes rather than changes on the Steam end.

  Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822


  Symptom --
  DoD:Source loads normally. But after a few minutes of playing (not a specific 
time as far as I can tell), the game freezes in place. A short clip (maybe a 
quarter of a second) of the last audio that played then repeats over and over 
on a loop. The process has to be killed manually with a QUIT or HUP signal for 
good measure. This is a new issue that just arose today.

  I have included system info, kernel log, and output when game is run
  from terminal and crashes.

  X info --
  X.Org X Server 1.16.0
  Release Date: 2014-07-16
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu
  Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu 
SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug
  Build Date: 10 September 2014  01:10:01PM
  xorg-server 2:1.16.0-1ubuntu1 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.32.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.

  
  System --

  OS: Ubuntu 14.10 (latest updates)
  Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Model: HP Envy x360
  lspci:
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev 
e4)
  00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev 
e4)
  00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev 
e4)
  00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev 
e4)
  00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI 
mode
  00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b)
  09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)


  Kernel log excerpt (from game start through crash end) --

  Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open]
  Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] 
HW context 1 destroyed
  Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open]
  Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] 
[CONNECTOR:14:?]
  Sep 12 19:11:25 kernel: [ 4447.852796] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] 
[CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP 
VDD on
  Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vdd_on] PP_STATUS: 
0x8008 PP_CONTROL: 0xabcd000f
  Sep 12 19:11:25 kernel: [ 4447.853257] [drm:intel_dp_probe_oui] Sink OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853695] [drm:intel_dp_probe_oui] Branch OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853708] [drm:drm_edid_to_eld] ELD: no CEA 
Extension found
  Sep 12 19:11:25 kernel: [ 4447.853711] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] 
probed modes :
  Sep 12 19:11:25 kernel: [ 4447.853715] [drm:drm_mode_debug_printmodeline]

[Touch-packages] [Bug 1411620] [NEW] Unity requires restart after enabling always-show-menus or LIM

2015-01-16 Thread Alin Andrei

Public bug reported:

Unity requires restart after enabling always-show-menus or LIM. When I
first tested the always-show-menus (about 3-4 weeks ago, by using
Marco's branch), I don't remember it requiring a restart.

Also, enabling LIM in Ubuntu 14.04 and 14.10 doesn't require restarting
Unity but it does with the latest Unity in Ubuntu 15.04 Vivid Vervet.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity 7.3.1+15.04.20150115-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
Uname: Linux 3.18.0-9-generic i686
ApportVersion: 2.15.1-0ubuntu2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Fri Jan 16 13:23:00 2015
InstallationDate: Installed on 2015-01-16 (0 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20150116)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 vivid

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

Title:
  Unity requires restart after enabling always-show-menus or LIM

Status in unity package in Ubuntu:
  New

Bug description:
  Unity requires restart after enabling always-show-menus or LIM. When
  I first tested the always-show-menus (about 3-4 weeks ago, by using
  Marco's branch), I don't remember it requiring a restart.

  Also, enabling LIM in Ubuntu 14.04 and 14.10 doesn't require
  restarting Unity but it does with the latest Unity in Ubuntu 15.04
  Vivid Vervet.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150115-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic i686
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Jan 16 13:23:00 2015
  InstallationDate: Installed on 2015-01-16 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20150116)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1411620/+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 1411621] Re: British English -ize endings not in dictionary

2015-01-16 Thread Chris Taylor

** Also affects: openoffice.org-dictionaries (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  British English -ize endings not in dictionary

Status in libreoffice-dictionaries package in Ubuntu:
  New
Status in openoffice.org-dictionaries package in Ubuntu:
  New

Bug description:
  The myspell-en-gb dictionary does not contain acceptable British
  English -ize endings.

  See http://www.oxforddictionaries.com/words/ize-ise-or-yse for more
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1411621/+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 1354924] Re: Networkmanager does not autoconnect to wireless network

2015-01-16 Thread tobiasBora

Could anyone put the priority of this bug to more than medium ? Because
it has implication on everyday life... And if you have a bad wifi
connection that often disconnect is just horrible to click every ten
seconds to reconnect.

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

Title:
  Networkmanager does not autoconnect to wireless network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When adding a net wireless network and enable connect automatically'
  networkmanager does not automatically connect to the network wenever
  possible.

  I'm running kubuntu 14.10 daily.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Aug 10 21:30:03 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-11 (29 days ago)
  InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710)
  IpRoute:
   default via 192.168.0.2 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.213  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+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 1410195] Re: Ctrl+Alt+F7 bypasses the light-locker lock-screen under XFCE

2015-01-16 Thread Martin Meredith

** Bug watch added: freedesktop.org Bugzilla #88492
   https://bugs.freedesktop.org/show_bug.cgi?id=88492

** Also affects: light-locker via
   https://bugs.freedesktop.org/show_bug.cgi?id=88492
   Importance: Unknown
   Status: Unknown

** Project changed: light-locker = policykit-1

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

Title:
  Ctrl+Alt+F7 bypasses the light-locker lock-screen under XFCE

Status in One Hundred Papercuts:
  Confirmed
Status in Open LDAP server:
  New
Status in System policy:
  Unknown
Status in light-locker package in Ubuntu:
  Confirmed
Status in openldap package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Create an user account with password.
  2. Login in the new account using the XFCE desktop environment.
  3. Lock the screen.
  4. Hit the Ctrl+Alt+F7 key combination.

  EXPECTED BEHAVIOUR:
  - The user session to be unavailable due to no password being entered.

  REAL BEHAVIOUR:
  - The session is accessible without entering its password, due to the VT8 
being bypassed to the original VT using the Ctrl+Alt+F7 key combination.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: light-locker 1.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jan 13 10:34:10 2015
  InstallationDate: Installed on 2015-01-06 (6 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1410195/+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 1410195] Re: Ctrl+Alt+F7 bypasses the light-locker lock-screen under XFCE

2015-01-16 Thread Martin Meredith

Can;t seem to link the openldap bug, so

http://www.openldap.org/its/index.cgi/Incoming?id=8025

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

** Changed in: hundredpapercuts
   Status: Incomplete = Confirmed

** Changed in: light-locker (Ubuntu)
   Status: Incomplete = Confirmed

** Changed in: openldap (Ubuntu)
   Status: Incomplete = Confirmed

** Changed in: policykit-1 (Ubuntu)
   Status: Incomplete = Confirmed

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

Title:
  Ctrl+Alt+F7 bypasses the light-locker lock-screen under XFCE

Status in One Hundred Papercuts:
  Confirmed
Status in Open LDAP server:
  New
Status in System policy:
  Unknown
Status in light-locker package in Ubuntu:
  Confirmed
Status in openldap package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Create an user account with password.
  2. Login in the new account using the XFCE desktop environment.
  3. Lock the screen.
  4. Hit the Ctrl+Alt+F7 key combination.

  EXPECTED BEHAVIOUR:
  - The user session to be unavailable due to no password being entered.

  REAL BEHAVIOUR:
  - The session is accessible without entering its password, due to the VT8 
being bypassed to the original VT using the Ctrl+Alt+F7 key combination.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: light-locker 1.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jan 13 10:34:10 2015
  InstallationDate: Installed on 2015-01-06 (6 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1410195/+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 1309915] Re: foreground app should keep wakelock open until actual suspend happens (aka camera takes ~5 seconds to be responsive after waking phone)

2015-01-16 Thread Michał Sawicz

** Changed in: qtmir (Ubuntu RTM)
   Status: Triaged = In Progress

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

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

Title:
  foreground app should keep wakelock open until actual suspend happens
  (aka camera takes ~5 seconds to be responsive after waking phone)

Status in the base for Ubuntu mobile products:
  In Progress
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu RTM:
  In Progress
Status in unity8 package in Ubuntu RTM:
  Invalid

Bug description:
  while apps that you put in the background are properly SIGSTOPed 
  (this is easy to verify with a music streaming website atm (while the browser 
does not use media-hub it will/should stop playback)).
   An app that is in the foreground will try to play on when the system is 
suspended (easy to verify with the same method, music plays on but becomes 
stuttery if the browser was in the foreground. This indicates the system tries 
to suspend but the running app tries to keep it alive. 

  Unity should send s SIGSTOP/SIGCONT sequence on suspend/resume to the
  app in foreground when the system goes into suspend and resumes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1309915/+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 1020210] Re: Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap corruption

2015-01-16 Thread lezbak

After testing on our system for 12.04 LTS I can now confirm it works for
me

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

Title:
  Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap
  corruption

Status in Embedded GLIBC:
  Fix Released
Status in eglibc package in Ubuntu:
  Fix Released
Status in eglibc source package in Precise:
  In Progress

Bug description:
  [Impact]

   * This bug is likely to cause a crash with a SEGV in multithreading
  applications doing many memory deallocations with ATOMIC_FASTBINS
  feature enabled.

  [Test Case]

   * Since this is a race condition issue there is no simple path of 
reproducing it, however one could try to follow the instructions in the 
upstream bug (https://www.sourceware.org/bugzilla/show_bug.cgi?id=15073):
  https://www.sourceware.org/bugzilla/attachment.cgi?id=7331

  [Regression Potential]

   * This issue has been merged upstream with no further issues
  reported.

  [Other Info]

  * Original bug description:

  We have an application which makes heavy allocation and de-allocation
  demands from multiple threads.  We run this application continuously
  on many servers, and once every several CPU months or years, we were
  getting a crash in _int_free that did not look like vanilla heap
  corruption.  I believe I have narrowed it down to a race condition in
  _int_free due to the ATOMIC_FASTBINS feature.  Basically, in the
  lockless FASTBIN _int_free path, a chunk is pulled into a local
  variable with the intent to add it to the fastbins list.  However, the
  heap consolidation/trim code can race with this, and can coalesce the
  entire block and/or give it back to the OS before _int_free has a
  chance to try and store it into the fastbins list.

  The problem is very challenging to reproduce in situ, but using gdb I
  have a recipe which demonstrates the crash 100% of the time on my
  12.04 x64 system running eglibc 2.15.  It relies on malloc_trim,
  although in our in situ data, the consolidation is triggered as a
  result of a normal free.  malloc_trim is just easier to control.

  While I am not a glibc developer, I could not see any easy ways to fix
  the situation shy of disabling ATOMIC_FASTBINS.

  I am attaching the reproduction source.  Other pertinent information
  follows:

   jpieper@calculon:~/downloads$ lsb_release -rd
   Description:Ubuntu 12.04 LTS
   Release:12.04

   jpieper@calculon:~/downloads$ apt-cache policy libc6
   libc6:
 Installed: 2.15-0ubuntu10
 Candidate: 2.15-0ubuntu10
 Version table:
*** 2.15-0ubuntu10 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  What I expect: I expect the attached application, when run using the gdb 
script in the comments, to complete with no failures.
  What happened: A SIGSEGV after the final continue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/eglibc/+bug/1020210/+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 1411637] [NEW] apt-get command line upgrade, to know when to restart

2015-01-16 Thread Nikita Yerenkov-Scott

Public bug reported:

When you run the application Software Updater and I install some updates
which need a restart of your computer, it tells you that you need to
restart your computer. But when running this command in Terminal: sudo
apt-get upgrade

It is not clear whether or not the packages which you have upgraded
require a restart of the computer once they have finished upgrading.

So what would be really useful instead of having to go and look in your
/var/run/ folder to check if /var/run/reboot-required exists, it would
be really good if on completion of the command for it to somehow just
tell you if a restart is required. Even if it just says either:

RESTART REQUIRED = TRUE

or

RESTART REQUIRED = FALSE

Depending on whether or not a restart is needed. Or as it used to do for
it to tell you here: Restart_to_complete_updates.bmp

Image refereed to has been attached.

System information:

Description:Ubuntu 14.10
Release:14.10

Package version information:

apt:
  Installed: 1.0.9.2ubuntu2
  Candidate: 1.0.9.2ubuntu2
  Version table:
 *** 1.0.9.2ubuntu2 0
500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status

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

** Attachment added: Restart_to_complete_updates.bmp
   
https://bugs.launchpad.net/bugs/1411637/+attachment/4299932/+files/Restart_to_complete_updates.bmp

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

Title:
  apt-get command line upgrade, to know when to restart

Status in apt package in Ubuntu:
  New

Bug description:
  When you run the application Software Updater and I install some
  updates which need a restart of your computer, it tells you that you
  need to restart your computer. But when running this command in
  Terminal: sudo apt-get upgrade

  It is not clear whether or not the packages which you have upgraded
  require a restart of the computer once they have finished upgrading.

  So what would be really useful instead of having to go and look in
  your /var/run/ folder to check if /var/run/reboot-required exists, it
  would be really good if on completion of the command for it to somehow
  just tell you if a restart is required. Even if it just says either:

  RESTART REQUIRED = TRUE

  or

  RESTART REQUIRED = FALSE

  Depending on whether or not a restart is needed. Or as it used to do
  for it to tell you here: Restart_to_complete_updates.bmp

  Image refereed to has been attached.

  System information:

  Description:  Ubuntu 14.10
  Release:  14.10

  Package version information:

  apt:
Installed: 1.0.9.2ubuntu2
Candidate: 1.0.9.2ubuntu2
Version table:
   *** 1.0.9.2ubuntu2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1411637/+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 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10

2015-01-16 Thread Moses

This bug also affects me, just updated from 14.04 to 14.10 this morning
after getting in to work on my Dell XPS M1530, and development has
become impossible. Eclipse Juno has become almost totally non-
responsive.

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

Title:
  Graphics Slow After Upgrade 14.04 - 14.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics

  After upgrading from 14.04 to 14.10 there are a lot of places where
  the graphics are working much slower than they were before:

  - Gnome Shell Interface is very sluggish, visible chops (redrawing)
  when pressing the [Super] key.

  - Selecting text in Gedit takes a full second pr. line

  Experiences some subjective improvement when I booted kernel 3.13.0-37
  instead of 3.16.0-23, but that may be my imagination as the problem
  persists.

  I've searched google, forums, found a couple of relevant links that
  point to the issue being the Intel drivers.

  http://askubuntu.com/questions/53962...E2%86%92-14-10
  http://www.webupd8.org/2014/10/ubunt...ent-1652086424

  But the drivers currently in 14.10 should be newer than those supplied
  by Intel to 14.04 so that doesn't make sense to me. As one Intel
  developer wrote:

  I would like to point out that since what we do is bring more ecent
  versions of the software to the target distributions than they ship
  with, a 14.04 targeted installer is unlikely to bring much to a 14.10
  installation, which most likely has the same or more recent versions
  already anyway.

  Source: https://01.org/linuxgraphics/node/375

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 28 15:24:30 2014
  DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2014-06-14 (135 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  MachineType: Dell Inc. XPS13 9333
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Oct 28 13:44:57 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933
   vendor CMN
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+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 1411641] [NEW] package libgtk-3-0 3.10.8-0ubuntu1.3 failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to '/usr/lib/i386-li

2015-01-16 Thread Pablo W

Public bug reported:

Sorry, no further information available.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libgtk-3-0 3.10.8-0ubuntu1.3
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
Date: Fri Jan 16 09:25:54 2015
DuplicateSignature: package:libgtk-3-0:3.10.8-0ubuntu1.3:cannot copy extracted 
data for './usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
InstallationDate: Installed on 2015-01-08 (7 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
SourcePackage: gtk+3.0
Title: package libgtk-3-0 3.10.8-0ubuntu1.3 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 trusty

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

Title:
  package libgtk-3-0 3.10.8-0ubuntu1.3 failed to install/upgrade: cannot
  copy extracted data for './usr/lib/i386-linux-
  gnu/libgtk-3.so.0.1000.8' to '/usr/lib/i386-linux-
  gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file or stream

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Sorry, no further information available.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgtk-3-0 3.10.8-0ubuntu1.3
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  Date: Fri Jan 16 09:25:54 2015
  DuplicateSignature: package:libgtk-3-0:3.10.8-0ubuntu1.3:cannot copy 
extracted data for './usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2015-01-08 (7 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  SourcePackage: gtk+3.0
  Title: package libgtk-3-0 3.10.8-0ubuntu1.3 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1411641/+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 1411643] [NEW] Automatic brightness toggle switch missing on krillin/vivid

2015-01-16 Thread Michael Zanetti

Public bug reported:

I noticed that on my krillin device with devel-propsed (r70), the
automatic display brightness toggle switch is missing in the battery
indicator.

** Affects: indicator-power (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

Title:
  Automatic brightness toggle switch missing on krillin/vivid

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  I noticed that on my krillin device with devel-propsed (r70), the
  automatic display brightness toggle switch is missing in the battery
  indicator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1411643/+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 1411643] Re: Automatic brightness toggle switch missing on krillin/vivid

2015-01-16 Thread Michał Sawicz

Confirmed on emulator 68 as well.

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

Title:
  Automatic brightness toggle switch missing on krillin/vivid

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  I noticed that on my krillin device with devel-propsed (r70), the
  automatic display brightness toggle switch is missing in the battery
  indicator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1411643/+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 1411643] Re: Automatic brightness toggle switch missing on krillin/vivid

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

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

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

Title:
  Automatic brightness toggle switch missing on krillin/vivid

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  I noticed that on my krillin device with devel-propsed (r70), the
  automatic display brightness toggle switch is missing in the battery
  indicator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1411643/+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 1216128] Re: Banner pages broken in Cups 1.5.3

2015-01-16 Thread tlc

Getting these blank banners on 14.04.

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

Title:
  Banner pages broken in Cups 1.5.3

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntun used:
  Description:Ubuntu 12.04.2 LTS
  Release:12.04

  2) The version of the package
  # apt-cache policy cups
  cups:
Installed: 1.5.3-0ubuntu6

  3) Expected behavior:

  I attempted to configure my local printer to use the the
  confidential CUPS banner page through the web based gui.  I have
  included a snippet of  the /etc/cups/printers.conf file to show that
  the change was applied corectly.

  snippet from /etc/cups/printers.conf
  ...
  /Printer
  Printer ITG-1320
  Info Color Printer
  Location Printer Room
  DeviceURI lpd://PRINTSERVER/ITG-1320
  State Idle
  StateTime 1308899498
  Accepting Yes
  Shared Yes
  JobSheets confidential none
  QuotaPeriod 0
  PageLimit 0
  KLimit 0
  OpPolicy default
  ErrorPolicy stop-printer
  /Printer
  ...

  When I print a test page I get a blank template page (see attached
  jpeg) followed by the correct ubuntu modified cups test page.

  I get the same output (once again, see the attached jpeg) for any
  banner page selected and applied.

  I have even attempted to replace the contents of
  /usr/share/data/confidential with the following:

  #CUPS-BANNER
  Show job-id job-name job-originating-user-name job-originating-host-name 
job-billing
  Header Confidential
  Footer Confidential

  however I still get the blank template page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1216128/+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 1411641] Re: package libgtk-3-0 3.10.8-0ubuntu1.3 failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to '/usr/lib/i386-linu

2015-01-16 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libgtk-3-0 3.10.8-0ubuntu1.3 failed to install/upgrade: cannot
  copy extracted data for './usr/lib/i386-linux-
  gnu/libgtk-3.so.0.1000.8' to '/usr/lib/i386-linux-
  gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file or stream

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Sorry, no further information available.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgtk-3-0 3.10.8-0ubuntu1.3
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  Date: Fri Jan 16 09:25:54 2015
  DuplicateSignature: package:libgtk-3-0:3.10.8-0ubuntu1.3:cannot copy 
extracted data for './usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2015-01-08 (7 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  SourcePackage: gtk+3.0
  Title: package libgtk-3-0 3.10.8-0ubuntu1.3 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1411641/+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 1410195] Re: Ctrl+Alt+F7 bypasses the light-locker lock-screen under XFCE

2015-01-16 Thread Howard Chu

As I noted in our ITS#8025, this has nothing to do with upstream
OpenLDAP. It may be specific to the particular way you built OpenLDAP in
your distro, or it may be due to pam_ldap itself, but neither of these
are in the purview of the OpenLDAP Project. Certainly there is nothing
in vanilla OpenLDAP source code that operates at a low enough system
level to interfere with screen blanking or locking.

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

Title:
  Ctrl+Alt+F7 bypasses the light-locker lock-screen under XFCE

Status in One Hundred Papercuts:
  Confirmed
Status in Open LDAP server:
  New
Status in System policy:
  Unknown
Status in light-locker package in Ubuntu:
  Confirmed
Status in openldap package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Create an user account with password.
  2. Login in the new account using the XFCE desktop environment.
  3. Lock the screen.
  4. Hit the Ctrl+Alt+F7 key combination.

  EXPECTED BEHAVIOUR:
  - The user session to be unavailable due to no password being entered.

  REAL BEHAVIOUR:
  - The session is accessible without entering its password, due to the VT8 
being bypassed to the original VT using the Ctrl+Alt+F7 key combination.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: light-locker 1.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jan 13 10:34:10 2015
  InstallationDate: Installed on 2015-01-06 (6 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1410195/+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 1398427] Re: [dialer] + [sound] Can't use earphone to answer or disconnect a call

** Branch linked: lp:~mzanetti/unity8/earpiece-button

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

Title:
  [dialer] + [sound] Can't use earphone to answer or disconnect a call

Status in the base for Ubuntu mobile products:
  In Progress
Status in Telephony Service:
  New
Status in Ubuntu UX bugs:
  Triaged
Status in qtmir package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in qtmir package in Ubuntu RTM:
  Fix Released
Status in telephony-service package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  Triaged

Bug description:
  [Procedures]
  1.insert the earphone
  2.make a MO call to DUT
  3.use the Hook key to answer the call
  4.when connected the call use the hook key to disconnect the call

  [Expect results]
  earphone hook key can answer and disconnect the call
  [Actual results]
  can't answer and disconnect the call

  [Reproduce]
  Always

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398427/+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 1411645] Re: Keyboard should restore user input if they press backspace after auto-completing a word

2015-01-16 Thread Michael Sheldon

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

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

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

Title:
  Keyboard should restore user input if they press backspace after auto-
  completing a word

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

Bug description:
  Steps to reproduce:

  1) Enable auto-completion

  2) Type Helfn and press space, this should auto-correct to Helen

  3) Press backspace

  Expected result

  Input should be changed back to the original entry of Helfn

  Actual result

  Stays as Helen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1411645/+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 1410195] Re: Ctrl+Alt+F7 bypasses the light-locker lock-screen under XFCE

2015-01-16 Thread Martin Meredith

Howard, It's having the usernames come from ldap, rather than the local
system, that causes policykit to have weird stuff happen, that causes
screen locking.  It's all interconnected :)

The bug isn't in the parts individually, but in the integration of them
all.

** No longer affects: openldap

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

Title:
  Ctrl+Alt+F7 bypasses the light-locker lock-screen under XFCE

Status in One Hundred Papercuts:
  Confirmed
Status in System policy:
  Confirmed
Status in light-locker package in Ubuntu:
  Confirmed
Status in openldap package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Create an user account with password.
  2. Login in the new account using the XFCE desktop environment.
  3. Lock the screen.
  4. Hit the Ctrl+Alt+F7 key combination.

  EXPECTED BEHAVIOUR:
  - The user session to be unavailable due to no password being entered.

  REAL BEHAVIOUR:
  - The session is accessible without entering its password, due to the VT8 
being bypassed to the original VT using the Ctrl+Alt+F7 key combination.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: light-locker 1.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jan 13 10:34:10 2015
  InstallationDate: Installed on 2015-01-06 (6 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1410195/+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 1337956] Re: Evince can't print guillemets sometimes

2015-01-16 Thread Aleksey Vazhnov

To reproduce bug,  you can install cups-pdf package and send example.pdf to 
printer pdf in Evince.
With Okular, guillemets in example.pdf printed fine.

Versions:
evince 3.10.3-0ubuntu10.1
cups-pdf 2.6.1-9
okular 4:4.13.3-0ubuntu0.1

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

Title:
  Evince can't print guillemets sometimes

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  What is expected to happen is when one opens
  https://launchpadlibrarian.net/179309521/example.pdf in Evince and
  prints to either a Canon Pixma MG3540 or a Ricoh SP 202SN, it prints
  correctly.

  What happens instead is it is missing certain characters as noted in
  screenshot https://launchpadlibrarian.net/179309843/scan.jpg .

  WORKAROUND: Print via LibreOffice Draw.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: evince 3.10.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-24.41-generic 3.11.10.11
  Uname: Linux 3.11.0-24-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Fri Jul  4 22:12:28 2014
  InstallationDate: Installed on 2014-01-15 (169 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-01-15 (352 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: ASUSTeK COMPUTER INC. UX31A
  Package: cups 1.7.2-0ubuntu1.2
  PackageArchitecture: amd64
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed 
root=UUID=b545dc49-f30d-446d-bcf5-33e73ac1f6e7 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed 
root=UUID=b545dc49-f30d-446d-bcf5-33e73ac1f6e7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Tags:  trusty apparmor apparmor apparmor apparmor apparmor apparmor
  Uname: Linux 3.13.0-43-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-08-08 (147 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31A.219
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31A.219:bd06/14/2013:svnASUSTeKCOMPUTERINC.:pnUX31A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX31A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX31A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1337956/+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 1410195] Re: Ctrl+Alt+F7 bypasses the light-locker lock-screen under XFCE

2015-01-16 Thread Bug Watch Updater

Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=88492.

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


On 2015-01-16T11:56:51+00:00 Martin Meredith wrote:

When combined with pam_ldap, to login to a centralised server, the GUI
components of policykit fail, this means that the UI cannot shutdown,
cannot mount disks, install packages, etc (Xubuntu 14.04).

I can provide any further info, but I don't know what you require to
research this issue :).

pkexec from a terminal works fine.

Reply at: https://bugs.launchpad.net/ubuntu/+source/light-
locker/+bug/1410195/comments/14


** Changed in: policykit-1
   Status: Unknown = Confirmed

** Changed in: policykit-1
   Importance: Unknown = Medium

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

Title:
  Ctrl+Alt+F7 bypasses the light-locker lock-screen under XFCE

Status in One Hundred Papercuts:
  Confirmed
Status in System policy:
  Confirmed
Status in light-locker package in Ubuntu:
  Confirmed
Status in openldap package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Create an user account with password.
  2. Login in the new account using the XFCE desktop environment.
  3. Lock the screen.
  4. Hit the Ctrl+Alt+F7 key combination.

  EXPECTED BEHAVIOUR:
  - The user session to be unavailable due to no password being entered.

  REAL BEHAVIOUR:
  - The session is accessible without entering its password, due to the VT8 
being bypassed to the original VT using the Ctrl+Alt+F7 key combination.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: light-locker 1.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jan 13 10:34:10 2015
  InstallationDate: Installed on 2015-01-06 (6 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1410195/+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 1242285] Re: package util-linux 2.20.1-5.1ubuntu8 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 255

2015-01-16 Thread Serge van Ginderachter

We encountered this bug during a preseeded pxe/netinstall.

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

Title:
  package util-linux 2.20.1-5.1ubuntu8 failed to install/upgrade:
  ErrorMessage: subprocess new pre-installation script returned error
  exit status 255

Status in util-linux package in Ubuntu:
  Expired

Bug description:
  Ran:

  do-release-upgrade -d

  Just do-release-upgrade doesn't upgrade my Lubuntu 13.04 to 13.10

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: util-linux 2.20.1-5.1ubuntu8
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  Date: Sun Oct 20 10:47:42 2013
  DuplicateSignature: package:util-linux:2.20.1-5.1ubuntu8:ErrorMessage: 
subprocess new pre-installation script returned error exit status 255
  ErrorMessage: ErrorMessage: subprocess new pre-installation script returned 
error exit status 255
  InstallationDate: Installed on 2012-11-10 (343 days ago)
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1)
  MarkForUpload: True
  SourcePackage: util-linux
  Title: package util-linux 2.20.1-5.1ubuntu8 failed to install/upgrade: 
ErrorMessage: subprocess new pre-installation script returned error exit status 
255
  UpgradeStatus: Upgraded to raring on 2013-10-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1242285/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

** Changed in: canonical-devices-system-image
   Status: Confirmed = Fix Released

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

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu RTM:
  Fix Released

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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 1357143] Re: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:6:__gnu_cxx::__verbose_terminate_handler:cxxabiv1::terminate:std::terminate:cxxabiv1::cxa_throw:unity::

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

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

** Changed in: canonical-devices-system-image
Milestone: None = ww05-2015

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

Title:
  /usr/lib/arm-linux-gnueabihf/unity-
  
scopes/scoperunner:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:unity::scopes::Variant::get_string

Status in the base for Ubuntu mobile products:
  In Progress
Status in unity-scope-click package in Ubuntu:
  Fix Released
Status in unity-scopes-api package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu RTM:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-scopes-api.  This problem was most recently seen with
  version 0.6.1+14.10.20140809-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/c88b5501559a748cac3331be6593ccad021d1580
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1357143/+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 1408103] Re: Telephony seems to think I'm on a permanent call, ringer never plays, just the beep-beep of an awaiting call

2015-01-16 Thread Gustavo Pichorim Boiko

** Changed in: telephony-service
   Status: In Progress = Fix Released

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

Title:
  Telephony seems to think I'm on a permanent call, ringer never plays,
  just the beep-beep of an awaiting call

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Telephony Service:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu RTM:
  Fix Released

Bug description:
  For some time now, on both rtm and vivid, I don't get incoming call or
  message sounds, just the beep beep of the awaiting call, as if I was
  on a permanent call.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: telephony-service 0.1+15.04.20141212-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15-0ubuntu3
  Architecture: armhf
  Date: Tue Jan  6 22:10:47 2015
  InstallationDate: Installed on 2014-12-17 (20 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141217-020204)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

  Steps to reproduce:
  - Reboot the phone
  - From another phone, call the device

  Expected results:
  - The incoming call ringtone should be played and the snap decision should 
appear

  What happens:
  - The snap decision dialog appears, but the ringtone is not played. Instead a 
beep beep sound is heard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1408103/+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 1410500] Re: Selecting matched numbers from Recent should use the full contact's number

** Branch linked: lp:~boiko/history-service/store_remote_participant_id

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

Title:
  Selecting matched numbers from Recent should use the full contact's
  number

Status in the base for Ubuntu mobile products:
  New
Status in Dialer app for Ubuntu Touch:
  New
Status in Telephony History Service:
  New
Status in Ubuntu UX bugs:
  Triaged
Status in dialer-app package in Ubuntu:
  New
Status in history-service package in Ubuntu:
  New
Status in dialer-app package in Ubuntu RTM:
  New
Status in history-service package in Ubuntu RTM:
  New

Bug description:
  Steps:
  * store a number with the country code
  * call the contact without using the country code
  * interrupt the call
  * swipe from the bottom
  * tap on the call just made

  Expected:
  * you get the dialer keypad with the full number, including the country code

  Current:
  * you get the short number without the country code

  This was a problem for me when travelling, I couldn't use the Recent
  list to call home because it wouldn't include the country code.
  Somehow it's also remembered permanently, so now even if I call the
  full number with country code, tapping that Recent entry won't have
  the country code still.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dialer-app 0.1+15.04.20150108-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: armhf
  Date: Tue Jan 13 19:32:43 2015
  InstallationDate: Installed on 2015-01-13 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150113-020204)
  SourcePackage: dialer-app
  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/1410500/+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 1218289] Re: [dialer app] Incoming call (snap decision) not to spec

2015-01-16 Thread Gustavo Pichorim Boiko

** Changed in: telephony-service (Ubuntu RTM)
   Status: In Progress = Fix Released

** Changed in: telephony-service
   Status: Fix Committed = Fix Released

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

Title:
  [dialer app] Incoming call (snap decision) not to spec

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Telephony Service:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 source package in Saucy:
  Fix Released
Status in telephony-service package in Ubuntu RTM:
  Fix Released

Bug description:
  Current situation:
  Incoming call appears in snap decision format, but missing:
  - Decision buttons not the right visual colours and assets (missing colour 
and combo button)
  - background is currently transparent, so can see content below.

  Desired solution:
  - As per spec, when receiving an incoming call the snap decision should be 
solid background. And the notification buttons and style should be as per 
design.
  - See Notification and Snap Decision spec for full details of the final 
signed off design, 
https://docs.google.com/a/canonical.com/document/d/1puQ9Z0yKqzsQ1VQ1OOBkxgp78iWGnAhAkFXWJFTWIrE/edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1218289/+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 1394297] Re: quick reply should be disabled for unknown numbers

2015-01-16 Thread Gustavo Pichorim Boiko

** Changed in: telephony-service
   Status: In Progress = Fix Released

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

Title:
  quick reply should be disabled for unknown numbers

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Telephony Service:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu RTM:
  Fix Released

Bug description:
  testing latest vivid build

  - call the ubuntu phone from a blocked number or unknown number
  - use one of the quick reply's from the snap decision
  - you end up wtih a x-ofono-unknown in the messaging app with a failed 
message

  Expected result:
  - disable the quick reply (or don't show at all) if the caller is blocked or 
unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394297/+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 1411645] Re: Keyboard should restore user input if they press backspace after auto-completing a word

2015-01-16 Thread Michael Sheldon

** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/fix-1411645

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

Title:
  Keyboard should restore user input if they press backspace after auto-
  completing a word

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

Bug description:
  Steps to reproduce:

  1) Enable auto-completion

  2) Type Helfn and press space, this should auto-correct to Helen

  3) Press backspace

  Expected result

  Input should be changed back to the original entry of Helfn

  Actual result

  Stays as Helen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1411645/+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 1410762] Re: undefined ref to few functions.

2015-01-16 Thread Sagar Ghuge

Hey Luke,

Can you please suggest me any workaround to fix this issue ASAP.

I am not able to develop anything just because of Gtk+ :(

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

Title:
  undefined ref to few functions.

Status in libcanberra package in Ubuntu:
  New

Bug description:
  make[4]: Entering directory 
'/home/sagarghuge/checkout/gnome/gtk+/demos/widget-factory'
CCLD gtk3-widget-factory
  /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/libcanberra-gtk3.so: 
undefined reference to `gdk_x11_window_get_xid'
  /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/libcanberra-gtk3.so: 
undefined reference to `gdk_x11_get_xatom_by_name_for_display'
  /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/libcanberra-gtk3.so: 
undefined reference to `gdk_x11_display_get_xdisplay'
  collect2: error: ld returned 1 exit status
  Makefile:634: recipe for target 'gtk3-widget-factory' failed
  make[4]: *** [gtk3-widget-factory] Error 1
  make[4]: Leaving directory 
'/home/sagarghuge/checkout/gnome/gtk+/demos/widget-factory'
  Makefile:548: recipe for target 'all' failed
  make[3]: *** [all] Error 2
  make[3]: Leaving directory 
'/home/sagarghuge/checkout/gnome/gtk+/demos/widget-factory'
  Makefile:525: recipe for target 'all-recursive' failed
  make[2]: *** [all-recursive] Error 1
  make[2]: Leaving directory '/home/sagarghuge/checkout/gnome/gtk+/demos'
  Makefile:707: recipe for target 'all-recursive' failed
  make[1]: *** [all-recursive] Error 1
  make[1]: Leaving directory '/home/sagarghuge/checkout/gnome/gtk+'
  Makefile:600: recipe for target 'all' failed
  make: *** [all] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1410762/+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 1411434] Re: cupsd arguments don't allow retrieval of information about reason for termination

2015-01-16 Thread Tychodickerson

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

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

Title:
  cupsd arguments don't allow retrieval of information about reason for
  termination

Status in cups package in Ubuntu:
  In Progress

Bug description:
  Invoking `/usr/sbin/cupsd -f` simply prints ~`Terminated`[1]. Assuming
  there's no output about the reason at all (i.e. neither to stdout or
  stderr nor to configured logging facilities) I'd suggest to provide it
  - it's overkill to dive into the manual to figure out why the process
  was killed - and assuming the reason is logged somewhere, it'd be nice
  to have a switch (e.g. `--debug-stdout`) to log to stdout regardless
  of which logging facility is configured in the configuration files.

  I can't say - and am not eager to know - the reason why the process
  fails at this point, I'd prefer to seem this issue fixed and see it on
  my console :)

  ---
  [1] or `Killed` or something similar, didn't investigate too deep because of 
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1411431

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: cups 1.7.5-3ubuntu2
  ProcVersionSignature: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/proc/version_signature'
  Uname: Linux 3.18.2-031802-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan 15 22:55:03 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-03 (12 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  KernLog:

  Lpstat: device for PDF: cups-pdf:/
  MachineType: LENOVO 20221
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.2-031802-generic 
root=UUID=733be919-1a8c-447d-ae30-c7b1cc533a1b ro recovery rootflags=subvol=@
  SourcePackage: cups
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1411434/+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 1391976] Re: Loading libmircommon.so twice leads to a segfault in libprotobuf.so

2015-01-16 Thread Alexandros Frantzis

Packages (for 2.6.1, vivid) with an _experimental_ patch that allows
protobuf to re-initialize properly after
google::protobuf::ShutdownProtobufLibrary() is called:

https://launchpad.net/~afrantzis/+archive/ubuntu/staging/+packages

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

Title:
  Loading libmircommon.so twice leads to a segfault in libprotobuf.so

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Can be reproduced with: load_twice libmircommon.so.1 (or .2)
  For recent versions of mir use: load_twice libmirclient.so.X (currently .8)

  load_twice.c:

  #include stdio.h
  #include dlfcn.h

  int main(int argc, char** argv)
  {
  void *dl;
  int i;

  for (i = 0; i  2; i++)
  {
     dl = dlopen (argv[1], RTLD_LAZY);
     printf (%d open dl: %p\n, i,  dl);
     if (dl)
     dlclose (dl);
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1391976/+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 1303031] Re: webapp-container crashed with SIGABRT in QMessageLogger::fatal() in VirtualBox

2015-01-16 Thread Daniel Aleksandersen

This makes it hard to test webapp deployments against various versions
of Ubuntu.

** Summary changed:

- webapp-container crashed with SIGABRT in QMessageLogger::fatal()
+ webapp-container crashed with SIGABRT in QMessageLogger::fatal() in VirtualBox

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

Title:
  webapp-container crashed with SIGABRT in QMessageLogger::fatal() in
  VirtualBox

Status in Web Browser App:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  Start a web application like GMail results in a crash of webbrowser-
  app on Trusty (only in VirtualBox)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: webapp-container 0.23+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sat Apr  5 14:20:20 2014
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2014-04-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
  ProcCmdline: webapp-container --app-id=Gmailmailgooglecom --webapp 
--enable-back-forward https://mail.google.com
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   QOpenGLContext::create() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   BrowserApplication::initialize(QString const) ()
  Title: webapp-container crashed with SIGABRT in QMessageLogger::fatal()
  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/webbrowser-app/+bug/1303031/+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 1385817] Re: initscripts package fails to upgrade if there are local init scripts on the system with no LSB headers

2015-01-16 Thread Christopher

My list of unconfigured applications is growing. Tracker is new as of
today.

 libpam-systemd:amd64
 ppp
 clamav-freshclam
 ntp
 spamassassin
 libunique-1.0-0
 dbus-x11
 cgmanager
 pppoeconf
 tracker
 udev
 shotwell
 xserver-xorg-core
 gnome-media-player
 clamav
 tracker-extract
 sa-compile
 clamtk
 systemd
 tracker-utils
 tracker-gui
 tracker-miner-fs

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

Title:
  initscripts package fails to upgrade if there are local init scripts
  on the system with no LSB headers

Status in Release Notes for Ubuntu:
  Triaged
Status in sysvinit package in Ubuntu:
  Confirmed

Bug description:
  = Release Notes =

  The dependency-based boot sequencing originally introduced upstream
  with Debian 6.0 is now always enabled in Ubuntu 14.10.

  For optimal sequencing, all init.d scripts should declare their
  dependencies in an LSB header. This is already the case for scripts
  shipped in Ubuntu, but users should check their local scripts and
  consider adding that information.

  For more information on this feature refer to the information
  available in /usr/share/doc/insserv/README.Debian.

  = bug report data =

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: initscripts 2.88dsf-41ubuntu18
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Sun Oct 26 07:52:55 2014
  DuplicateSignature: package:initscripts:2.88dsf-41ubuntu18:le sous-processus 
script post-installation installé a retourné une erreur de sortie d'état 1
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2014-08-06 (80 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: sysvinit
  Title: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: Upgraded to utopic on 2014-10-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1385817/+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 740506]

2015-01-16 Thread Albert Astals Cid

The bug importance doesn't matter, what matters is that if there's
someone with the time to work on this.

I'd say there's not much people (or noone) in the current team with such
amount of time.

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

Title:
  verify digital signatures

Status in Evince document viewer:
  Confirmed
Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  This is a feature request to verify digital signatures.  I'm receiving more 
and more digitally signed PDF's and evince already acknowledges them with:
  Signature Not Verified
  Digitally signed by signer
  Date:  time stamp
  Reason: reason
  Location: location
  but it would be great if Evince would be integrated into the distro's 
ca-certificate infrastructure to verify these signatures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+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 1020210] Re: Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap corruption

2015-01-16 Thread Dariusz Gadomski

Updated debdiff against eglibc_2.15-0ubuntu10.9.

** Patch added: precise_eglibc_2.15-0ubuntu10.10.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1020210/+attachment/4299972/+files/precise_eglibc_2.15-0ubuntu10.10.debdiff

** Patch removed: precise_eglibc_2.15-0ubuntu10.8.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1020210/+attachment/4252890/+files/precise_eglibc_2.15-0ubuntu10.8.debdiff

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

Title:
  Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap
  corruption

Status in Embedded GLIBC:
  Fix Released
Status in eglibc package in Ubuntu:
  Fix Released
Status in eglibc source package in Precise:
  In Progress

Bug description:
  [Impact]

   * This bug is likely to cause a crash with a SEGV in multithreading
  applications doing many memory deallocations with ATOMIC_FASTBINS
  feature enabled.

  [Test Case]

   * Since this is a race condition issue there is no simple path of 
reproducing it, however one could try to follow the instructions in the 
upstream bug (https://www.sourceware.org/bugzilla/show_bug.cgi?id=15073):
  https://www.sourceware.org/bugzilla/attachment.cgi?id=7331

  [Regression Potential]

   * This issue has been merged upstream with no further issues
  reported.

  [Other Info]

  * Original bug description:

  We have an application which makes heavy allocation and de-allocation
  demands from multiple threads.  We run this application continuously
  on many servers, and once every several CPU months or years, we were
  getting a crash in _int_free that did not look like vanilla heap
  corruption.  I believe I have narrowed it down to a race condition in
  _int_free due to the ATOMIC_FASTBINS feature.  Basically, in the
  lockless FASTBIN _int_free path, a chunk is pulled into a local
  variable with the intent to add it to the fastbins list.  However, the
  heap consolidation/trim code can race with this, and can coalesce the
  entire block and/or give it back to the OS before _int_free has a
  chance to try and store it into the fastbins list.

  The problem is very challenging to reproduce in situ, but using gdb I
  have a recipe which demonstrates the crash 100% of the time on my
  12.04 x64 system running eglibc 2.15.  It relies on malloc_trim,
  although in our in situ data, the consolidation is triggered as a
  result of a normal free.  malloc_trim is just easier to control.

  While I am not a glibc developer, I could not see any easy ways to fix
  the situation shy of disabling ATOMIC_FASTBINS.

  I am attaching the reproduction source.  Other pertinent information
  follows:

   jpieper@calculon:~/downloads$ lsb_release -rd
   Description:Ubuntu 12.04 LTS
   Release:12.04

   jpieper@calculon:~/downloads$ apt-cache policy libc6
   libc6:
 Installed: 2.15-0ubuntu10
 Candidate: 2.15-0ubuntu10
 Version table:
*** 2.15-0ubuntu10 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  What I expect: I expect the attached application, when run using the gdb 
script in the comments, to complete with no failures.
  What happened: A SIGSEGV after the final continue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/eglibc/+bug/1020210/+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 1372413] Re: Extensive battery drain on RTM

2015-01-16 Thread Colin Ian King

With wifi associated to a fairly busy AP that produces regular beacon
intervals with CTS protection mode enabled and also phone data enabled
I'm seeing ~24+ hours on deep sleep idle.

With wifi enabled, I'm seeing ~7.5 wifi related wakeups per minute. I
then disabled wifi and these wakeups disappear. So the bottom line is
that wifi in deep sleep is the root cause of extraneous wakeups. Now
depending on how busy the AP is and the kinds of packets, it may cause
more or less wakeups, hence different drain characteristics.

I'll recharge the phone and see how the wifi disabled case changes the
battery drain rate.

Attached is two-page spreadsheet of my drain results and also stats on
wakeups from deep sleep caused by wifi related wakeup events.

** Attachment added: wifi related battery drain stats

https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1372413/+attachment/4299973/+files/mako-rtm-battery-drain-12hrs.ods

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

Title:
Extensive battery drain on RTM

Status in the base for Ubuntu mobile products:
In Progress
Status in powerd package in Ubuntu:
Confirmed

Bug description:
Mako, RTM 1

Since upgrading to RTM the battery life is really poor. What used to
be a battery drain of 5-10% per hour (which is still high) is now
10-15% per hour. Sometimes the phone runs really hot, so there seem to
be something going on in the background that is consuming power. I
mostly have bluetooth, GPS (which isn't always working), wifi and
cellular on, but that's no difference from when I was running 'devel-
proposed' with MultiROM with much less battery consumption.

As an example, I started with a full charge at 7am. After some web
surfing (15 mins) and watching a couple of youtube videos (on wifi)
battery was down to 66% at 9:15. That's 34% in just over two hours! I
recharged again before lunch and had the phone idle until coming back
1 hour and 45 mins later to find only 75% of battery left, this time
without the phone running particularly hot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1372413/+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 1411711] [NEW] This problem occurs every now and then!

2015-01-16 Thread Munawar Ahmed

Public bug reported:

This problem occurs every now and then!

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Jan 16 20:21:43 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:167c]
InstallationDate: Installed on 2014-12-31 (16 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
MachineType: Hewlett-Packard HP ProBook 4530s
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=c02c9de0-435b-4ce4-8f5a-e212df4cb2cb ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/18/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SRR Ver. F.0A
dmi.board.name: 167C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 22.1F
dmi.chassis.asset.tag: CNU2122017
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SRRVer.F.0A:bd07/18/2011:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1F:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 4530s
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Jan 16 20:07:18 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5537 
 vendor CMO
xserver.version: 2:1.15.1-0ubuntu2.6

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


** Tags: amd64 apport-bug compiz-0.9 package-from-proposed trusty ubuntu

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

Title:
  This problem occurs every now and then!

Status in xorg package in Ubuntu:
  New

Bug description:
  This problem occurs every now and then!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Jan 16 20:21:43 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:167c]
  InstallationDate: Installed on 2014-12-31 (16 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ProBook 4530s
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=c02c9de0-435b-4ce4-8f5a-e212df4cb2cb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SRR Ver. F.0A
  dmi.board.name: 167C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 22.1F
  dmi.chassis.asset.tag: CNU2122017
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SRRVer.F.0A:bd07/18/2011:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1F:cvnHewlett-Packard:ct10:cvr:

[Touch-packages] [Bug 1411714] [NEW] indicator-network not functioning after modems reboot

2015-01-16 Thread Jonas G. Drange

Public bug reported:

1) The release of Ubuntu
current build number: 75
device name: krillin
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-01-16 13:56:36
version version: 75
version ubuntu: 20150116
version device: 20150113-9cccefe
version custom: 20150116

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
Using libqofono-0.70, ofono 1.12.bzr6882+15.04.20141126-0ubuntu1 which deviates 
from the default

3) What you expected to happen
After the modems rebooted, I expected the network indicator to function normally

4) What happened instead
Nothing works: cannot enable wifi, both SIMs are listed as Frakoblet 
(Norwegian for disconnected), cannot enable flight mode

This is the output of ofono/scripts/list-modems: 
http://pastebin.ubuntu.com/9762092/
wlan0 has gone away, see output of $ ifconfig -a: 
http://pastebin.ubuntu.com/9762104/

This appears in the network-manager.log:
http://pastebin.ubuntu.com/9762128/

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.15.1-0ubuntu2
Architecture: armhf
Date: Fri Jan 16 16:16:33 2015
InstallationDate: Installed on 2015-01-16 (0 days ago)
InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150116-020204)
SourcePackage: indicator-network
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf third-party-packages vivid

** Description changed:

  1) The release of Ubuntu
  current build number: 75
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-01-16 13:56:36
  version version: 75
  version ubuntu: 20150116
  version device: 20150113-9cccefe
  version custom: 20150116
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  Using libqofono-0.70, ofono 1.12.bzr6882+15.04.20141126-0ubuntu1 which 
deviates from the default
  
  3) What you expected to happen
  After the modems rebooted, I expected the network indicator to function 
normally
  
  4) What happened instead
  Nothing works: cannot enable wifi, both SIMs are listed as Frakoblet 
(Norwegian for disconnected), cannot enable flight mode
  
  This is the output of ofono/scripts/list-modems: 
http://pastebin.ubuntu.com/9762092/
  wlan0 has gone away, see output of $ ifconfig -a: 
http://pastebin.ubuntu.com/9762104/
  
+ This appears in the network-manager.log:
+ http://pastebin.ubuntu.com/9762128/
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: armhf
  Date: Fri Jan 16 16:16:33 2015
  InstallationDate: Installed on 2015-01-16 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150116-020204)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  indicator-network not functioning after modems reboot

Status in indicator-network package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu
  current build number: 75
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-01-16 13:56:36
  version version: 75
  version ubuntu: 20150116
  version device: 20150113-9cccefe
  version custom: 20150116

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  Using libqofono-0.70, ofono 1.12.bzr6882+15.04.20141126-0ubuntu1 which 
deviates from the default

  3) What you expected to happen
  After the modems rebooted, I expected the network indicator to function 
normally

  4) What happened instead
  Nothing works: cannot enable wifi, both SIMs are listed as Frakoblet 
(Norwegian for disconnected), cannot enable flight mode

  This is the output of ofono/scripts/list-modems: 
http://pastebin.ubuntu.com/9762092/
  wlan0 has gone away, see output of $ ifconfig -a: 
http://pastebin.ubuntu.com/9762104/

  This appears in the network-manager.log:
  http://pastebin.ubuntu.com/9762128/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: armhf
  Date: Fri Jan 16 16:16:33 2015
  InstallationDate: Installed on 2015-01-16 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150116-020204)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present

[Touch-packages] [Bug 1357143] Re: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:6:__gnu_cxx::__verbose_terminate_handler:cxxabiv1::terminate:std::terminate:cxxabiv1::cxa_throw:unity::

2015-01-16 Thread Alejandro J. Cura

** Changed in: unity-scope-click (Ubuntu RTM)
 Assignee: (unassigned) = Alejandro J. Cura (alecu)

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) = Alejandro J. Cura (alecu)

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

Title:
  /usr/lib/arm-linux-gnueabihf/unity-
  
scopes/scoperunner:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:unity::scopes::Variant::get_string

Status in the base for Ubuntu mobile products:
  In Progress
Status in unity-scope-click package in Ubuntu:
  Fix Released
Status in unity-scopes-api package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu RTM:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-scopes-api.  This problem was most recently seen with
  version 0.6.1+14.10.20140809-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/c88b5501559a748cac3331be6593ccad021d1580
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1357143/+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 1411714] Re: indicator-network not functioning after modems reboot

2015-01-16 Thread Jonas G. Drange

** Description changed:

+ NOTE: this may be caused by using UnlockAllModems from the connectivity
+ api. Investigating.
+ 
  1) The release of Ubuntu
  current build number: 75
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-01-16 13:56:36
  version version: 75
  version ubuntu: 20150116
  version device: 20150113-9cccefe
  version custom: 20150116
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  Using libqofono-0.70, ofono 1.12.bzr6882+15.04.20141126-0ubuntu1 which 
deviates from the default
  
  3) What you expected to happen
  After the modems rebooted, I expected the network indicator to function 
normally
  
  4) What happened instead
  Nothing works: cannot enable wifi, both SIMs are listed as Frakoblet 
(Norwegian for disconnected), cannot enable flight mode
  
  This is the output of ofono/scripts/list-modems: 
http://pastebin.ubuntu.com/9762092/
  wlan0 has gone away, see output of $ ifconfig -a: 
http://pastebin.ubuntu.com/9762104/
  
  This appears in the network-manager.log:
  http://pastebin.ubuntu.com/9762128/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: armhf
  Date: Fri Jan 16 16:16:33 2015
  InstallationDate: Installed on 2015-01-16 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150116-020204)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  indicator-network not functioning after modems reboot

Status in indicator-network package in Ubuntu:
  New

Bug description:
  NOTE: this may be caused by using UnlockAllModems from the
  connectivity api. Investigating.

  1) The release of Ubuntu
  current build number: 75
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-01-16 13:56:36
  version version: 75
  version ubuntu: 20150116
  version device: 20150113-9cccefe
  version custom: 20150116

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  Using libqofono-0.70, ofono 1.12.bzr6882+15.04.20141126-0ubuntu1 which 
deviates from the default

  3) What you expected to happen
  After the modems rebooted, I expected the network indicator to function 
normally

  4) What happened instead
  Nothing works: cannot enable wifi, both SIMs are listed as Frakoblet 
(Norwegian for disconnected), cannot enable flight mode

  This is the output of ofono/scripts/list-modems: 
http://pastebin.ubuntu.com/9762092/
  wlan0 has gone away, see output of $ ifconfig -a: 
http://pastebin.ubuntu.com/9762104/

  This appears in the network-manager.log:
  http://pastebin.ubuntu.com/9762128/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: armhf
  Date: Fri Jan 16 16:16:33 2015
  InstallationDate: Installed on 2015-01-16 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150116-020204)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1411714/+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 1348538] Re: [power] Display should come on when started charging

2015-01-16 Thread Ricardo Salveti

** No longer affects: indicator-power (Ubuntu)

** No longer affects: unity-system-compositor

** No longer affects: unity-system-compositor (Ubuntu)

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

** Also affects: powerd (Ubuntu RTM)
   Importance: Undecided
   Status: New

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

Title:
  [power] Display should come on when started charging

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  Triaged
Status in powerd package in Ubuntu:
  New
Status in powerd package in Ubuntu RTM:
  New

Bug description:
  The display should be triggered to turn on for a $timeout when
  connected to a charger, so that users can see charging commenced.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity-system-compositor (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
  Uname: Linux 3.16.0-5-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 25 09:45:42 2014
  SourcePackage: unity-system-compositor
  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/1348538/+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 1348538] Re: [power] Display should come on when started charging

nice UX fix

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

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

** Changed in: canonical-devices-system-image
Milestone: None = ww05-2015

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

Title:
  [power] Display should come on when started charging

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  Triaged
Status in powerd package in Ubuntu:
  New
Status in powerd package in Ubuntu RTM:
  New

Bug description:
  The display should be triggered to turn on for a $timeout when
  connected to a charger, so that users can see charging commenced.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity-system-compositor (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
  Uname: Linux 3.16.0-5-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 25 09:45:42 2014
  SourcePackage: unity-system-compositor
  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/1348538/+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 1411729] [NEW] Install path for the library incorrect when cross-building

2015-01-16 Thread Michał Sawicz

Public bug reported:

I tried to cross-build telephony-service, following, mostly,
https://wiki.ubuntu.com/SimpleSbuild#ARM.

The build failed with:

 dh_install: qtdeclarative5-ubuntu-telephony0.1 missing files
(usr/lib/*/qt5/qml/Ubuntu/Telephony/libtelephonyservice-qml.so),
aborting

This is because the file is installed in the wrong place:

 -- Installing: /«BUILDDIR»/telephony-
service-0.1+15.04.20150109/debian/tmp/Ubuntu/Telephony
/libtelephonyservice-qml.so

Please find the whole sbuild log attached.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: telephony-service 0.1+15.04.20150109-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
Uname: Linux 3.18.0-9-generic x86_64
ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jan 16 17:03:49 2015
SourcePackage: telephony-service
SystemImageInfo:
 current build number: 0
 device name: 
 channel: daily
 last update: Unknown
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: telephony-service (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

** Attachment added: telephony-service_0.1+15.04.20150109-0ubuntu1_armhf.build
   
https://bugs.launchpad.net/bugs/1411729/+attachment/4300028/+files/telephony-service_0.1%2B15.04.20150109-0ubuntu1_armhf.build

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

Title:
  Install path for the library incorrect when cross-building

Status in telephony-service package in Ubuntu:
  New

Bug description:
  I tried to cross-build telephony-service, following, mostly,
  https://wiki.ubuntu.com/SimpleSbuild#ARM.

  The build failed with:

   dh_install: qtdeclarative5-ubuntu-telephony0.1 missing files
  (usr/lib/*/qt5/qml/Ubuntu/Telephony/libtelephonyservice-qml.so),
  aborting

  This is because the file is installed in the wrong place:

   -- Installing: /«BUILDDIR»/telephony-
  service-0.1+15.04.20150109/debian/tmp/Ubuntu/Telephony
  /libtelephonyservice-qml.so

  Please find the whole sbuild log attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: telephony-service 0.1+15.04.20150109-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 16 17:03:49 2015
  SourcePackage: telephony-service
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1411729/+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 1411417] Re: Smooth transition when setting up the backlight value

** Branch linked: lp:ubuntu/vivid-proposed/powerd

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

Title:
  Smooth transition when setting up the backlight value

Status in the base for Ubuntu mobile products:
  In Progress
Status in powerd package in Ubuntu:
  In Progress
Status in powerd package in Ubuntu RTM:
  New

Bug description:
  Currently powerd is just setting the backlight value as requested,
  without doing a smooth transition, causing a weird user experience
  (even more when using auto-brightness).

  When setting up a new value, we should transition to that value
  progressively instead of radically changing to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411417/+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 1409051] Re: When using a webapp-properties file for an unamed webapp the user script does not get injected

2015-01-16 Thread Alexandre Abreu

** Branch linked: lp:~abreu-alexandre/unity-webapps-qml/rtm-fix-local-
script-handling

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

Title:
  When using a webapp-properties file for an unamed webapp the user
  script does not get injected

Status in Unity WebApps QML component:
  In Progress
Status in unity-webapps-qml package in Ubuntu:
  Fix Released
Status in unity-webapps-qml package in Ubuntu RTM:
  New

Bug description:
  When using a webapp-properties file for an unamed webapp the user
  script does not get injected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-webapps-qml/+bug/1409051/+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 1411714] Re: indicator-network not functioning after modems reboot

2015-01-16 Thread Jonas G. Drange

** Description changed:

- NOTE: this may be caused by using UnlockAllModems from the connectivity
- api. Investigating.
- 
  1) The release of Ubuntu
  current build number: 75
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-01-16 13:56:36
  version version: 75
  version ubuntu: 20150116
  version device: 20150113-9cccefe
  version custom: 20150116
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  Using libqofono-0.70, ofono 1.12.bzr6882+15.04.20141126-0ubuntu1 which 
deviates from the default
  
  3) What you expected to happen
  After the modems rebooted, I expected the network indicator to function 
normally
  
  4) What happened instead
  Nothing works: cannot enable wifi, both SIMs are listed as Frakoblet 
(Norwegian for disconnected), cannot enable flight mode
  
  This is the output of ofono/scripts/list-modems: 
http://pastebin.ubuntu.com/9762092/
  wlan0 has gone away, see output of $ ifconfig -a: 
http://pastebin.ubuntu.com/9762104/
  
  This appears in the network-manager.log:
  http://pastebin.ubuntu.com/9762128/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: armhf
  Date: Fri Jan 16 16:16:33 2015
  InstallationDate: Installed on 2015-01-16 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150116-020204)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  1) The release of Ubuntu
  current build number: 75
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-01-16 13:56:36
  version version: 75
  version ubuntu: 20150116
  version device: 20150113-9cccefe
  version custom: 20150116
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  Using libqofono-0.70, ofono 1.12.bzr6882+15.04.20141126-0ubuntu1 which 
deviates from the default
  
  3) What you expected to happen
  After the modems rebooted, I expected the network indicator to function 
normally
  
  4) What happened instead
  Nothing works: cannot enable wifi, both SIMs are listed as Frakoblet 
(Norwegian for disconnected), cannot enable flight mode
  
+ 
+ 5) Steps to reproduce
+ 
+ http://pastebin.ubuntu.com/9762300/
+ 
+ 
  This is the output of ofono/scripts/list-modems: 
http://pastebin.ubuntu.com/9762092/
  wlan0 has gone away, see output of $ ifconfig -a: 
http://pastebin.ubuntu.com/9762104/
  
  This appears in the network-manager.log:
  http://pastebin.ubuntu.com/9762128/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: armhf
  Date: Fri Jan 16 16:16:33 2015
  InstallationDate: Installed on 2015-01-16 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150116-020204)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  indicator-network not functioning after modems reboot

Status in indicator-network package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu
  current build number: 75
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-01-16 13:56:36
  version version: 75
  version ubuntu: 20150116
  version device: 20150113-9cccefe
  version custom: 20150116

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  Using libqofono-0.70, ofono 1.12.bzr6882+15.04.20141126-0ubuntu1 which 
deviates from the default

  3) What you expected to happen
  After the modems rebooted, I expected the network indicator to function 
normally

  4) What happened instead
  Nothing works: cannot enable wifi, both SIMs are listed as Frakoblet 
(Norwegian for disconnected), cannot enable flight mode

  
  5) Steps to reproduce

  http://pastebin.ubuntu.com/9762300/

  
  This is the output of ofono/scripts/list-modems: 
http://pastebin.ubuntu.com/9762092/
  wlan0 has gone away, see output of $ ifconfig -a: 
http://pastebin.ubuntu.com/9762104/

  This appears in the network-manager.log:
  http://pastebin.ubuntu.com/9762128/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: armhf
  Date: Fri Jan 16 16:16:33 2015
  InstallationDate: Installed on 2015-01-16

[Touch-packages] [Bug 1411733] [NEW] [CheckBox/Switch] not resolution independet

2015-01-16 Thread Victor Tuson Palau

Public bug reported:

Testing on a higher resolution phone (Arale) the size of the switches on
the indicators and the settings up is smaller proportionally than in the
nexus4 or Krillin.

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

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

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

** Changed in: canonical-devices-system-image
   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/1411733

Title:
  [CheckBox/Switch] not resolution independet

Status in the base for Ubuntu mobile products:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Testing on a higher resolution phone (Arale) the size of the switches
  on the indicators and the settings up is smaller proportionally than
  in the nexus4 or Krillin.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411733/+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 1411171] Re: Repeating alarms appear disabled in clock app after it went off once

2015-01-16 Thread Łukasz Zemczak

Ok, so I'm leaving it on our issue list for Ubuntu until the situation
gets cleared up - this way it will stay on our radar. Thanks!

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

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu RTM:
  Fix Released

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and 
enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next 
occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+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 1411637] Re: apt-get command line upgrade, to know when to restart

2015-01-16 Thread Henry Fleminger Thomson

** Changed in: apt (Ubuntu)
   Status: New = Confirmed

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

Title:
  apt-get command line upgrade, to know when to restart

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  When you run the application Software Updater and I install some
  updates which need a restart of your computer, it tells you that you
  need to restart your computer. But when running this command in
  Terminal: sudo apt-get upgrade

  It is not clear whether or not the packages which you have upgraded
  require a restart of the computer once they have finished upgrading.

  So what would be really useful instead of having to go and look in
  your /var/run/ folder to check if /var/run/reboot-required exists, it
  would be really good if on completion of the command for it to somehow
  just tell you if a restart is required. Even if it just says either:

  RESTART REQUIRED = TRUE

  or

  RESTART REQUIRED = FALSE

  Depending on whether or not a restart is needed. Or as it used to do
  for it to tell you here: Restart_to_complete_updates.bmp

  Image refereed to has been attached.

  System information:

  Description:  Ubuntu 14.10
  Release:  14.10

  Package version information:

  apt:
Installed: 1.0.9.2ubuntu2
Candidate: 1.0.9.2ubuntu2
Version table:
   *** 1.0.9.2ubuntu2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1411637/+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 1385817] Re: initscripts package fails to upgrade if there are local init scripts on the system with no LSB headers

2015-01-16 Thread Martin Pitt

Well, the list of affected packages is pretty arbitrary and random --
on affected systems you have to fix the broken third-party init.d
script, or it's never going to work :/

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

Title:
  initscripts package fails to upgrade if there are local init scripts
  on the system with no LSB headers

Status in Release Notes for Ubuntu:
  Triaged
Status in sysvinit package in Ubuntu:
  Confirmed

Bug description:
  = Release Notes =

  The dependency-based boot sequencing originally introduced upstream
  with Debian 6.0 is now always enabled in Ubuntu 14.10.

  For optimal sequencing, all init.d scripts should declare their
  dependencies in an LSB header. This is already the case for scripts
  shipped in Ubuntu, but users should check their local scripts and
  consider adding that information.

  For more information on this feature refer to the information
  available in /usr/share/doc/insserv/README.Debian.

  = bug report data =

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: initscripts 2.88dsf-41ubuntu18
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Sun Oct 26 07:52:55 2014
  DuplicateSignature: package:initscripts:2.88dsf-41ubuntu18:le sous-processus 
script post-installation installé a retourné une erreur de sortie d'état 1
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2014-08-06 (80 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: sysvinit
  Title: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: Upgraded to utopic on 2014-10-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1385817/+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 1410195] Re: Ctrl+Alt+F7 bypasses the light-locker lock-screen under XFCE

2015-01-16 Thread Howard Chu

Try replacing pam-ldap/nss-ldap with nslcd and/or nssov and see if the
problem persists. I'd bet it doesn't. See here
https://bugs.launchpad.net/debian/+source/sudo/+bug/423252/comments/84
for reasons why you should have abandoned pam-ldap/nss-ldap years ago.

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

Title:
  Ctrl+Alt+F7 bypasses the light-locker lock-screen under XFCE

Status in One Hundred Papercuts:
  Confirmed
Status in System policy:
  Confirmed
Status in light-locker package in Ubuntu:
  Confirmed
Status in openldap package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Create an user account with password.
  2. Login in the new account using the XFCE desktop environment.
  3. Lock the screen.
  4. Hit the Ctrl+Alt+F7 key combination.

  EXPECTED BEHAVIOUR:
  - The user session to be unavailable due to no password being entered.

  REAL BEHAVIOUR:
  - The session is accessible without entering its password, due to the VT8 
being bypassed to the original VT using the Ctrl+Alt+F7 key combination.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: light-locker 1.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jan 13 10:34:10 2015
  InstallationDate: Installed on 2015-01-06 (6 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1410195/+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 1411417] Re: Smooth transition when setting up the backlight value

This bug was fixed in the package powerd - 0.16+15.04.20150116-0ubuntu1

---
powerd (0.16+15.04.20150116-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Ricardo Salveti de Araujo ]
  * backlight: setting brightness in a progressive way (LP: #1411417)
(LP: #1411417)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Fri, 16 Jan 2015 
13:09:05 +

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

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

Title:
  Smooth transition when setting up the backlight value

Status in the base for Ubuntu mobile products:
  In Progress
Status in powerd package in Ubuntu:
  Fix Released
Status in powerd package in Ubuntu RTM:
  New

Bug description:
  Currently powerd is just setting the backlight value as requested,
  without doing a smooth transition, causing a weird user experience
  (even more when using auto-brightness).

  When setting up a new value, we should transition to that value
  progressively instead of radically changing to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411417/+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 1300182] Re: Zoom level changes when rotating

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

** Changed in: webbrowser-app (Ubuntu)
   Status: New = Confirmed

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

Title:
  Zoom level changes when rotating

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  - load a page
  - rotate the phone
  - rotate the phone back

  Expected results:
  - you see the same thing as before rotation

  Current results:
  - zoom level changed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: webbrowser-app 0.23+14.04.20140324-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: armhf
  Date: Mon Mar 31 12:15:10 2014
  InstallationDate: Installed on 2014-03-31 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140331)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   SHELL=/bin/bash
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1300182/+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 1411751] [NEW] [Arale] Attribute in news section of today scope has wrong aspect ratio

2015-01-16 Thread Victor Tuson Palau

Public bug reported:

Open the Today scope in Arale
Go to News section
BBC attribute aspect ratio is not correct.

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

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

** Changed in: unity8 (Ubuntu)
   Importance: Undecided = High

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

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

** Summary changed:

- [Arale] Emblem in news section of today scope has wrong aspect ratio
+ [Arale] Attribute in news section of today scope has wrong aspect ratio

** Description changed:

  Open the Today scope in Arale
  Go to News section
- BBC emblem aspect ratio is not correct.
+ BBC attribute aspect ratio is not correct.

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

Title:
  [Arale] Attribute in news section of today scope has wrong aspect
  ratio

Status in the base for Ubuntu mobile products:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Open the Today scope in Arale
  Go to News section
  BBC attribute aspect ratio is not correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411751/+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 1380662] Re: legacy apps re-set their notification status on reboot

** Branch linked: lp:~chipaca/ubuntu-push/fix-1376282-for-rtm

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

Title:
  legacy apps re-set their notification status on reboot

Status in the base for Ubuntu mobile products:
  Confirmed
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  In Progress
Status in ubuntu-push package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  when un-setting the notification defaults for external drives this
  setting is respected fine until i reboot my phone, after which the
  setting is auto-enabled again, regardless of what i chose before the
  reboot.

  the same seems to be true for the system-settings option in the
  notifications panel. something like gmail or facebook persits fine

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1380662/+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 1380662] Re: legacy apps re-set their notification status on reboot

** Changed in: canonical-devices-system-image
Milestone: ww51-2014 = ww05-2015

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

Title:
  legacy apps re-set their notification status on reboot

Status in the base for Ubuntu mobile products:
  Confirmed
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  In Progress
Status in ubuntu-push package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  when un-setting the notification defaults for external drives this
  setting is respected fine until i reboot my phone, after which the
  setting is auto-enabled again, regardless of what i chose before the
  reboot.

  the same seems to be true for the system-settings option in the
  notifications panel. something like gmail or facebook persits fine

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1380662/+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 1354924] Re: Networkmanager does not autoconnect to wireless network

2015-01-16 Thread Søren Holm

@tobiasBora: YEs only for the current session. But that something every
fix has in common - except for the Allow all users to access this
network-option.

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

Title:
  Networkmanager does not autoconnect to wireless network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When adding a net wireless network and enable connect automatically'
  networkmanager does not automatically connect to the network wenever
  possible.

  I'm running kubuntu 14.10 daily.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Aug 10 21:30:03 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-11 (29 days ago)
  InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710)
  IpRoute:
   default via 192.168.0.2 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.213  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+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 1330770] Re: click packages rely upon tls for integrity and authenticity

2015-01-16 Thread peterstan

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: In Progress = New

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: New = Confirmed

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: Ken VanDine (ken-vandine) = peterstan (stasnel)

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

Title:
  click packages rely upon tls for integrity and authenticity

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Click Package metadata search service:
  Fix Released
Status in Online service used by software center:
  Fix Released
Status in click package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Fix Released

Bug description:
  Hello, I just completed a quick review of the click source and the
  unity-scope-click source and behaviours, and found some opportunities
  for improvement.

  Debian, and Ubuntu, rely upon signed repository files with
  cryptographic hashes of packages to provide both integrity and
  authenticity checks for the packages hosted on that repository.

  The click framework and the unity-scope-click discovery and
  installation tool do not use signed repository files, nor do they have
  signatures of any sort on downloaded packages. The only integrity and
  authenticity checks are provided by the use of HTTPS.  The click
  verify command will check files within the archive against MD5sums
  stored inside the archive but the click verify command is not used
  during package installation. (This is suitable for validating
  integrity against accidental changes only.)

  While it appears that unity-scope-click properly uses HTTPS to
  download package metadata and packages, HTTPS alone is insufficient
  for our needs:

  - Someone in a position to create new certificates at any of several
  hundred certificate authorities could create certificates purporting
  to be our update servers. This actual problem has been discovered in
  the wild with several certificate authorities issuing wild-card
  certificates or even certificates with signing authority.

  - X.509 is extremely complicated; TLS is extremely complicated. Flaws
  in both are inevitable.

  - HTTPS prevents the use of caching.

  - HTTPS only 'works' for data-in-motion; it is useless for data-at-
  rest integrity and authenticity checks.

  I have not yet reviewed the tools that application authors will use to
  upload their packages to our distribution servers but note in passing
  that most of these issues are also issues for adding packages to our
  update servers -- packages in flight within our network can be
  corrupted for many reasons, packages on disk can be corrupted for many
  reasons. A signature mechanism can protect against internal network
  faults, storage faults, and provide assurance months or years later
  that an uploaded package was uploaded by someone in control of a
  corresponding private key.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1330770/+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 1351314] Re: powerd crashed with SIGABRT in internal::ToBackend::exit_module()

2015-01-16 Thread Apport retracing service

** Tags added: vivid

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

Title:
  powerd crashed with SIGABRT in internal::ToBackend::exit_module()

Status in powerd package in Ubuntu:
  Confirmed

Bug description:
  powerd crashed with SIGABRT in ua_sensors_proximity_new()

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: powerd 0.16+14.10.20140707-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.5-0ubuntu2
  Architecture: amd64
  Date: Fri Aug  1 13:10:15 2014
  ExecutablePath: /usr/bin/powerd
  InstallationDate: Installed on 2014-06-17 (44 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  ProcCmdline: /usr/bin/powerd
  ProcEnviron:
   PATH=(custom, no user)
   TERM=linux
  Signal: 6
  SourcePackage: powerd
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   ua_sensors_proximity_new () from 
/usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2
   powerd_sensors_init() ()
   main ()
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  Title: powerd crashed with SIGABRT in ua_sensors_proximity_new()
  UpgradeStatus: Upgraded to utopic on 2014-08-01 (0 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1351314/+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 1411768] [NEW] clippath in svg doesn't have any effect

2015-01-16 Thread Dennis O'Flaherty

Public bug reported:

I used an svg as the source for scope art which has a clippath.  This is
rendered correctly in eog and firefox, but isn't rendered correctly in a
unity8 scope.

Source for the scope is here:
https://github.com/doswdev/haca/tree/combined_logos

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

** Attachment added: devils_ducks_bad.png
   
https://bugs.launchpad.net/bugs/1411768/+attachment/4300132/+files/devils_ducks_bad.png

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

Title:
  clippath in svg doesn't have any effect

Status in unity8 package in Ubuntu:
  New

Bug description:
  I used an svg as the source for scope art which has a clippath.  This
  is rendered correctly in eog and firefox, but isn't rendered correctly
  in a unity8 scope.

  Source for the scope is here:
  https://github.com/doswdev/haca/tree/combined_logos

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1411768/+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 1407192] Re: firefox icon frequently replaced by placeholder

** Branch linked: lp:~andyrock/bamf/lp-1407192

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

Title:
  firefox icon frequently replaced by placeholder

Status in BAMF Application Matching Framework:
  In Progress
Status in Unity:
  Invalid
Status in bamf package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Several times over the last week I have noticed that the when I start 
firefox, the default icon is replaced by a grey square with a question mark in 
the center as shown in the attached image.
  The only fix I've found is to unlock firefox from the launcher, quit the 
program, search for firefox in the dash, manually drag the icon onto the 
launcher, and then open it(i.e. if I start firefox directly from the dash, the 
grey icon appears on the launcher again).
  I haven't noticed this occurring with any other program.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20141216-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-0ubuntu1
  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 Jan  2 21:38:32 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] 
(prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fb43]
  InstallationDate: Installed on 2014-12-11 (23 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141210)
  MachineType: TOSHIBA Satellite L875D
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: PLCSC8
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L875D
  dmi.product.version: PSKFQU-003034
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.916+git20141119-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Jan  1 20:07:44 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.2.901-1ubuntu3
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1407192/+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 1411768] Re: clippath in svg doesn't have any effect

2015-01-16 Thread Dennis O'Flaherty

This is what the image should look like

** Attachment added: devils_ducks_good.png
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1411768/+attachment/4300133/+files/devils_ducks_good.png

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

Title:
  clippath in svg doesn't have any effect

Status in unity8 package in Ubuntu:
  New

Bug description:
  I used an svg as the source for scope art which has a clippath.  This
  is rendered correctly in eog and firefox, but isn't rendered correctly
  in a unity8 scope.

  Source for the scope is here:
  https://github.com/doswdev/haca/tree/combined_logos

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1411768/+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 1354924] Re: Networkmanager does not autoconnect to wireless network

2015-01-16 Thread Ricardo Fabbri

@tobiasBora: +1

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

Title:
  Networkmanager does not autoconnect to wireless network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When adding a net wireless network and enable connect automatically'
  networkmanager does not automatically connect to the network wenever
  possible.

  I'm running kubuntu 14.10 daily.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Aug 10 21:30:03 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-11 (29 days ago)
  InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710)
  IpRoute:
   default via 192.168.0.2 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.213  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+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 1322490] Re: [indicators] Clicking on a connected network's checkbox disconnects re-connects

2015-01-16 Thread Alberto Salvia Novella

** Changed in: ubuntu-settings-components (Ubuntu)
   Importance: Undecided = Medium

** Changed in: ubuntu-settings-components (Ubuntu)
   Status: Confirmed = Triaged

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

Title:
  [indicators] Clicking on a connected network's checkbox  disconnects 
  re-connects

Status in Network Menu:
  New
Status in Ubuntu UX bugs:
  Triaged
Status in indicator-network package in Ubuntu:
  Triaged
Status in ubuntu-settings-components package in Ubuntu:
  Triaged

Bug description:
  indicator-network 0.5.1+14.10.20140516.2-0ubuntu1, Ubuntu Utopic

  1. Unlock the phone
  2. Drag down the indicator for networking
  3. Select a wifi AP sign into it
  4. Drag down the indicator for networking
  5. Try to uncheck it.

  What happens: The network disconnects and reconnects.

  What should happen: Nothing.

  https://wiki.ubuntu.com/Networking#wi-fi-menu: 2. If the card is
  powered on, up to 6 (phone) or 20 (PC) radio items representing known
  Wi-Fi networks...

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1322490/+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 1411620] Re: Unity requires restart after enabling always-show-menus or LIM

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

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

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

Title:
  Unity requires restart after enabling always-show-menus or LIM

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Unity requires restart after enabling always-show-menus or LIM. When
  I first tested the always-show-menus (about 3-4 weeks ago, by using
  Marco's branch), I don't remember it requiring a restart.

  Also, enabling LIM in Ubuntu 14.04 and 14.10 doesn't require
  restarting Unity but it does with the latest Unity in Ubuntu 15.04
  Vivid Vervet.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150115-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic i686
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Jan 16 13:23:00 2015
  InstallationDate: Installed on 2015-01-16 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20150116)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1411620/+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 1411620] Re: Unity requires restart after enabling always-show-menus or LIM

2015-01-16 Thread Alberto Salvia Novella

** Changed in: unity (Ubuntu)
   Importance: Undecided = Critical

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

Title:
  Unity requires restart after enabling always-show-menus or LIM

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Unity requires restart after enabling always-show-menus or LIM. When
  I first tested the always-show-menus (about 3-4 weeks ago, by using
  Marco's branch), I don't remember it requiring a restart.

  Also, enabling LIM in Ubuntu 14.04 and 14.10 doesn't require
  restarting Unity but it does with the latest Unity in Ubuntu 15.04
  Vivid Vervet.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150115-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic i686
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Jan 16 13:23:00 2015
  InstallationDate: Installed on 2015-01-16 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20150116)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1411620/+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 1409129] Re: Drop usage of udev-bridge via events-bridge