[Touch-packages] [Bug 1398104] Re: Support multi-arch click build (single "fat" click package)

2016-08-24 Thread Sam Segers
It should be easy.
'make install DESTDIR=..' to a tmp directory for each kit.
Then merge the folders and to click build and change the manifest.
The sdk does this already. It only needs to do it for each configured kit.

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

Title:
  Support multi-arch click build (single "fat" click package)

Status in click package in Ubuntu:
  Confirmed

Bug description:
  It should be possible for click build to target more than one
  architecture so that I can build a single package that will support
  multi-architectures. This is useful for providing a single package in
  the click store instead of maintaining separate packages.

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

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


[Touch-packages] [Bug 1585370] Re: pepper flash plugin disallowed from apparmor

2016-05-24 Thread Sam Segers
** Description changed:

  When launching webbrowser-app from unity8 under confinement, i get
  disallowed errors for /opt/google/chrome/PepperFlash/manifest.json and
  /opt/google/chrome/PepperFlash/libpepflashplayer.so
  
- When I add the following to the apparmor profile of webbrowser-app, it
- works:
+ When I add the following to the apparmor profile of webbrowser-app and
+ to the oxide_helper subprocess, it works:
  
  /opt/google/** r,
  
  /opt/google/**/*.so mr,
  
  Don't know what's exactly needed.

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

Title:
  pepper flash plugin disallowed from apparmor

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When launching webbrowser-app from unity8 under confinement, i get
  disallowed errors for /opt/google/chrome/PepperFlash/manifest.json and
  /opt/google/chrome/PepperFlash/libpepflashplayer.so

  When I add the following to the apparmor profile of webbrowser-app and
  to the oxide_helper subprocess, it works:

  /opt/google/** r,

  /opt/google/**/*.so mr,

  Don't know what's exactly needed.

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

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


[Touch-packages] [Bug 1585370] Re: pepper flash plugin disallowed from apparmor

2016-05-24 Thread Sam Segers
Should also consider https://bugs.launchpad.net/oxide/+bug/1585379

** Description changed:

  When launching webbrowser-app from unity8 under confinement, i get
  disallowed errors for /opt/google/chrome/PepperFlash/manifest.json and
  /opt/google/chrome/PepperFlash/libpepflashplayer.so
  
- When I add /opt/google/** to the apparmor profile of webbrowser-app, it
- works.
+ When I add the following to the apparmor profile of webbrowser-app, it
+ works:
+ 
+ /opt/google/** r,
+ 
+ /opt/google/**/*.so mr,
+ 
+ Don't know what's exactly needed.

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

Title:
  pepper flash plugin disallowed from apparmor

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When launching webbrowser-app from unity8 under confinement, i get
  disallowed errors for /opt/google/chrome/PepperFlash/manifest.json and
  /opt/google/chrome/PepperFlash/libpepflashplayer.so

  When I add the following to the apparmor profile of webbrowser-app, it
  works:

  /opt/google/** r,

  /opt/google/**/*.so mr,

  Don't know what's exactly needed.

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

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


[Touch-packages] [Bug 1585370] Re: pepper flash plugin disallowed from apparmor

2016-05-24 Thread Sam Segers
** Description changed:

  When launching webbrowser-app from unity8 under confinement, i get
  disallowed errors for /opt/google/chrome/PepperFlash/manifest.json and
  /opt/google/chrome/PepperFlash/libpepflashplayer.so
  
- When I add /opt/google/** to the apparmor oxide_helper profile of
- webbrowser-app, it works.
+ When I add /opt/google/** to the apparmor profile of webbrowser-app, it
+ works.

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

Title:
  pepper flash plugin disallowed from apparmor

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When launching webbrowser-app from unity8 under confinement, i get
  disallowed errors for /opt/google/chrome/PepperFlash/manifest.json and
  /opt/google/chrome/PepperFlash/libpepflashplayer.so

  When I add /opt/google/** to the apparmor profile of webbrowser-app,
  it works.

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

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


[Touch-packages] [Bug 1585370] [NEW] pepper flash plugin disallowed from apparmor

2016-05-24 Thread Sam Segers
Public bug reported:

When launching webbrowser-app from unity8 under confinement, i get
disallowed errors for /opt/google/chrome/PepperFlash/manifest.json and
/opt/google/chrome/PepperFlash/libpepflashplayer.so

When I add /opt/google/** to the apparmor oxide_helper profile of
webbrowser-app, it works.

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

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

Title:
  pepper flash plugin disallowed from apparmor

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When launching webbrowser-app from unity8 under confinement, i get
  disallowed errors for /opt/google/chrome/PepperFlash/manifest.json and
  /opt/google/chrome/PepperFlash/libpepflashplayer.so

  When I add /opt/google/** to the apparmor oxide_helper profile of
  webbrowser-app, it works.

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

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


[Touch-packages] [Bug 1553505] [NEW] ~/.local/shared/applications is not created

2016-03-05 Thread Sam Segers
Public bug reported:

I logged in to unity8 with a new user named "phablet" using the
following package:

unity8-desktop-session-mir:
  Installed: 1.0.12+15.10.20150609-0ubuntu1

I installed a click package using:
sudo click install --user=$USER --allow-unauthenticated 
deezer-scope.labsin_0.1.19_multi.click

The needed desktop file is not created in ~/.local/shared/applications
as the directory does not exist.

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

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

Title:
  ~/.local/shared/applications is not created

Status in click package in Ubuntu:
  New

Bug description:
  I logged in to unity8 with a new user named "phablet" using the
  following package:

  unity8-desktop-session-mir:
Installed: 1.0.12+15.10.20150609-0ubuntu1

  I installed a click package using:
  sudo click install --user=$USER --allow-unauthenticated 
deezer-scope.labsin_0.1.19_multi.click

  The needed desktop file is not created in ~/.local/shared/applications
  as the directory does not exist.

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

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


[Touch-packages] [Bug 1482296] Re: State handling slightly inconsistence with the qt documentation description

2015-12-15 Thread Sam Segers
*** This bug is a duplicate of bug 1504776 ***
https://bugs.launchpad.net/bugs/1504776

** This bug has been marked a duplicate of bug 1504776
   Uses deprecated QEvent::ApplicationActivate

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

Title:
  State handling slightly inconsistence with the qt documentation
  description

Status in qtubuntu:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  http://doc.qt.io/qt-5/qml-qtqml-qt.html states

  "Qt.ApplicationSuspended - The application is suspended and not
  visible to the user. On mobile platforms, the application typically
  enters this state when the user returns to the home screen or switches
  to another application."

  or in practice that nevers happen on Ubuntu Touch, the application
  state changes to ApplicationInactive only

  That's what led us to have bug #1482235 on settings, since we were
  turning off bluetooth features on Qt.ApplicationSuspended, the qt
  documentation suggests that the normal cycle should be -> Inactive ->
  Suspended, or the Suspended never reach the application it seems?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtubuntu/+bug/1482296/+subscriptions

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


[Touch-packages] [Bug 879943] Re: Synaptic messes sources.list and sources.list.d

2015-11-01 Thread Sam Segers
** Branch linked: lp:~sam-sgrs/software-properties/software-properties-
fix-879943

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

Title:
  Synaptic messes sources.list and sources.list.d

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Consider the following situation

  1) I carefully edit by hand the /etc/sources.list file or the files in 
/etc/sources.list.d files
  (this is something I do to have them aligned between different machines. In 
fact it is not a real edit, but a copy from another machine)

  2) Try the lists with apt-get update. Everything is fine.

  3) Start synaptic. Go to the settings window to edit the repos. Go to
  the other software tab.

  4) Do any possible little action. For instance activate and
  disactivate the source repo for ubuntu partners. Assure that your
  action has nothing to do with the changes you made in 1)

  5) See how synaptic has horribly restored the repo list as it was
  before your hand edit.

  6) Exit synaptic and go to the /etc/apt dir. Verify how everything has
  gone back exactly as it was before your hand edit. Repos that you
  erased are there again. Repos you edited have their changes reverted.

  IMHO this is not just wrong, but also very dangerous.
  Suppose that I had added a repo from a third party source.
  Suppose that I then find out that this repo is dangerous. For instance 
because it replaces some package with a bugged package or a package with a back 
door.
  Suppose that I consciously restore the package to the original version and I 
hand erase the crappled repo from my list of repos by removing the 
corresponding file from the /etc/apt/sources.list.d dir
  Now I feel safe. However, any time I use synaptic I risk having that repo 
back.

  To me this is a security vulnerability. Anyone can convince me to add
  a test repo to see what is in it. At the time I test that repo can be
  perfectly fine. I test, I remove the repo, I feel safe, the repo gets
  automatically added back by synaptic, the repo owner adds in a package
  that looks like an update to a package that I have in my system and
  without even realizing it I can have my system infected by a malicious
  package.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: synaptic 0.75.2ubuntu8
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 22 16:45:31 2011
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  SourcePackage: synaptic
  UpgradeStatus: Upgraded to oneiric on 2011-10-16 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/879943/+subscriptions

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


[Touch-packages] [Bug 1504776] Re: Uses depricated QEvent::ApplicationActivate

2015-10-31 Thread Sam Segers
** Package changed: qtubuntu (Ubuntu) => qtubuntu

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

Title:
  Uses depricated QEvent::ApplicationActivate

Status in qtubuntu:
  New

Bug description:
  qtubuntu plugin uses the ApplicationActivate and ApplicationDeactivate 
QEvents for life cycle management.
  These have become deprecated and been replaced by Qt::ApplicationState since 
Qt5.1

  The states should be set with:

  QWindowSystemInterface::handleApplicationStateChanged(Qt::ApplicationState
  state)

  The qtnamespace docs:
  /*!
  \enum Qt::ApplicationState

  \keyword application state

  This enum type is used to specify the current state of the
  application.

  The states are

  \value ApplicationSuspendedThe application is about to suspend. When 
entering this state, the
 application should save its state, cease 
all activities, and be
 prepared for code execution to stop. While 
suspended, the
 application can be killed at any time 
without further warnings
 (e.g. when low memory forces the OS to 
purge suspended applications).
  \value ApplicationHidden   The application is hidden and runs in the 
background. This
 is the normal state for applications that 
need to do background
 processing, like playing music, while the 
user interacts with
 other applications. The application should 
free up all graphical
 resources when entering this state.
  \value ApplicationInactive The application is visible, but not 
selected to be in front.
 On desktop platforms, this typically means 
that the user
 activated another application. On mobile 
platforms, it is
 more common to enter this state when the 
OS is interrupting
 the user with e.g. incoming calls or 
SMS-messages.
 While in this state, consider reducing 
CPU-intensive tasks.
  \value ApplicationActive   The application is visible and selected to 
be in front.

  \since 5.1
  */

  This will also make it possible to set more appropriate life cycle
  states. We can then react to Qt.ApplicationSuspended on the
  application.state object from QML to react when the application gets
  suspended.

  UbuntuClientIntegration::hasCapability should then also return true
  with ApplicationState

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtubuntu/+bug/1504776/+subscriptions

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


[Touch-packages] [Bug 1504776] Re: Uses depricated QEvent::ApplicationActivate

2015-10-28 Thread Sam Segers
Proposed a fix

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

Title:
  Uses depricated QEvent::ApplicationActivate

Status in qtubuntu package in Ubuntu:
  New

Bug description:
  qtubuntu plugin uses the ApplicationActivate and ApplicationDeactivate 
QEvents for life cycle management.
  These have become deprecated and been replaced by Qt::ApplicationState since 
Qt5.1

  The states should be set with:

  QWindowSystemInterface::handleApplicationStateChanged(Qt::ApplicationState
  state)

  The qtnamespace docs:
  /*!
  \enum Qt::ApplicationState

  \keyword application state

  This enum type is used to specify the current state of the
  application.

  The states are

  \value ApplicationSuspendedThe application is about to suspend. When 
entering this state, the
 application should save its state, cease 
all activities, and be
 prepared for code execution to stop. While 
suspended, the
 application can be killed at any time 
without further warnings
 (e.g. when low memory forces the OS to 
purge suspended applications).
  \value ApplicationHidden   The application is hidden and runs in the 
background. This
 is the normal state for applications that 
need to do background
 processing, like playing music, while the 
user interacts with
 other applications. The application should 
free up all graphical
 resources when entering this state.
  \value ApplicationInactive The application is visible, but not 
selected to be in front.
 On desktop platforms, this typically means 
that the user
 activated another application. On mobile 
platforms, it is
 more common to enter this state when the 
OS is interrupting
 the user with e.g. incoming calls or 
SMS-messages.
 While in this state, consider reducing 
CPU-intensive tasks.
  \value ApplicationActive   The application is visible and selected to 
be in front.

  \since 5.1
  */

  This will also make it possible to set more appropriate life cycle
  states. We can then react to Qt.ApplicationSuspended on the
  application.state object from QML to react when the application gets
  suspended.

  UbuntuClientIntegration::hasCapability should then also return true
  with ApplicationState

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

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


[Touch-packages] [Bug 1504776] Re: Uses depricated QEvent::ApplicationActivate

2015-10-28 Thread Sam Segers
** Project changed: qtubuntu => qtubuntu (Ubuntu)

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

Title:
  Uses depricated QEvent::ApplicationActivate

Status in qtubuntu package in Ubuntu:
  New

Bug description:
  qtubuntu plugin uses the ApplicationActivate and ApplicationDeactivate 
QEvents for life cycle management.
  These have become deprecated and been replaced by Qt::ApplicationState since 
Qt5.1

  The states should be set with:

  QWindowSystemInterface::handleApplicationStateChanged(Qt::ApplicationState
  state)

  The qtnamespace docs:
  /*!
  \enum Qt::ApplicationState

  \keyword application state

  This enum type is used to specify the current state of the
  application.

  The states are

  \value ApplicationSuspendedThe application is about to suspend. When 
entering this state, the
 application should save its state, cease 
all activities, and be
 prepared for code execution to stop. While 
suspended, the
 application can be killed at any time 
without further warnings
 (e.g. when low memory forces the OS to 
purge suspended applications).
  \value ApplicationHidden   The application is hidden and runs in the 
background. This
 is the normal state for applications that 
need to do background
 processing, like playing music, while the 
user interacts with
 other applications. The application should 
free up all graphical
 resources when entering this state.
  \value ApplicationInactive The application is visible, but not 
selected to be in front.
 On desktop platforms, this typically means 
that the user
 activated another application. On mobile 
platforms, it is
 more common to enter this state when the 
OS is interrupting
 the user with e.g. incoming calls or 
SMS-messages.
 While in this state, consider reducing 
CPU-intensive tasks.
  \value ApplicationActive   The application is visible and selected to 
be in front.

  \since 5.1
  */

  This will also make it possible to set more appropriate life cycle
  states. We can then react to Qt.ApplicationSuspended on the
  application.state object from QML to react when the application gets
  suspended.

  UbuntuClientIntegration::hasCapability should then also return true
  with ApplicationState

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

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


[Touch-packages] [Bug 879943] Re: Synaptic messes sources.list and sources.list.d

2015-10-28 Thread Sam Segers
I don't get the approach too. It's nice cause it splits GUI and back-
end. The dbus service is in software-properties-common:

$ apt-cache rdepends software-properties-common
+software-properties-common
Reverse Depends:
  ubuntu-desktop-next
  phablet-tools-citrain
  ubuntu-touch
  phablet-tools-citrain
  cloud-init
  ubuntu-touch
  ubuntu-desktop-next
  software-properties-kde
  phablet-tools-citrain
  software-properties-gtk
  cloud-init

It seems not that many packages use the service. (ofc  software-
properties-kde does)

I also think there should be a watcher or a check. Or at the very least
let the GUI represent the same sources as the back-end.

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

Title:
  Synaptic messes sources.list and sources.list.d

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Consider the following situation

  1) I carefully edit by hand the /etc/sources.list file or the files in 
/etc/sources.list.d files
  (this is something I do to have them aligned between different machines. In 
fact it is not a real edit, but a copy from another machine)

  2) Try the lists with apt-get update. Everything is fine.

  3) Start synaptic. Go to the settings window to edit the repos. Go to
  the other software tab.

  4) Do any possible little action. For instance activate and
  disactivate the source repo for ubuntu partners. Assure that your
  action has nothing to do with the changes you made in 1)

  5) See how synaptic has horribly restored the repo list as it was
  before your hand edit.

  6) Exit synaptic and go to the /etc/apt dir. Verify how everything has
  gone back exactly as it was before your hand edit. Repos that you
  erased are there again. Repos you edited have their changes reverted.

  IMHO this is not just wrong, but also very dangerous.
  Suppose that I had added a repo from a third party source.
  Suppose that I then find out that this repo is dangerous. For instance 
because it replaces some package with a bugged package or a package with a back 
door.
  Suppose that I consciously restore the package to the original version and I 
hand erase the crappled repo from my list of repos by removing the 
corresponding file from the /etc/apt/sources.list.d dir
  Now I feel safe. However, any time I use synaptic I risk having that repo 
back.

  To me this is a security vulnerability. Anyone can convince me to add
  a test repo to see what is in it. At the time I test that repo can be
  perfectly fine. I test, I remove the repo, I feel safe, the repo gets
  automatically added back by synaptic, the repo owner adds in a package
  that looks like an update to a package that I have in my system and
  without even realizing it I can have my system infected by a malicious
  package.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: synaptic 0.75.2ubuntu8
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 22 16:45:31 2011
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  SourcePackage: synaptic
  UpgradeStatus: Upgraded to oneiric on 2011-10-16 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/879943/+subscriptions

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


[Touch-packages] [Bug 879943] Re: Synaptic messes sources.list and sources.list.d

2015-10-27 Thread Sam Segers
software-properties-gtk launches a dbus service 
/usr/lib/software-properties/software-properties-dbus
This service loads the sources in memory and edits them from there and saves 
them on a change.
The service keeps running after closing the software properties.
If you change things in /etc/apt/source.list or /etc/apt/source.list.d, these 
get overwritten by the values when first launched software-properties-gtk + the 
changes you make there.
If you f.i. remove a source from source.list.d, software-properties-gtk 
indicates this correctly as deleted. But if you edit something, the file 
magically reappears from the dbus service.

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

Title:
  Synaptic messes sources.list and sources.list.d

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Consider the following situation

  1) I carefully edit by hand the /etc/sources.list file or the files in 
/etc/sources.list.d files
  (this is something I do to have them aligned between different machines. In 
fact it is not a real edit, but a copy from another machine)

  2) Try the lists with apt-get update. Everything is fine.

  3) Start synaptic. Go to the settings window to edit the repos. Go to
  the other software tab.

  4) Do any possible little action. For instance activate and
  disactivate the source repo for ubuntu partners. Assure that your
  action has nothing to do with the changes you made in 1)

  5) See how synaptic has horribly restored the repo list as it was
  before your hand edit.

  6) Exit synaptic and go to the /etc/apt dir. Verify how everything has
  gone back exactly as it was before your hand edit. Repos that you
  erased are there again. Repos you edited have their changes reverted.

  IMHO this is not just wrong, but also very dangerous.
  Suppose that I had added a repo from a third party source.
  Suppose that I then find out that this repo is dangerous. For instance 
because it replaces some package with a bugged package or a package with a back 
door.
  Suppose that I consciously restore the package to the original version and I 
hand erase the crappled repo from my list of repos by removing the 
corresponding file from the /etc/apt/sources.list.d dir
  Now I feel safe. However, any time I use synaptic I risk having that repo 
back.

  To me this is a security vulnerability. Anyone can convince me to add
  a test repo to see what is in it. At the time I test that repo can be
  perfectly fine. I test, I remove the repo, I feel safe, the repo gets
  automatically added back by synaptic, the repo owner adds in a package
  that looks like an update to a package that I have in my system and
  without even realizing it I can have my system infected by a malicious
  package.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: synaptic 0.75.2ubuntu8
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 22 16:45:31 2011
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  SourcePackage: synaptic
  UpgradeStatus: Upgraded to oneiric on 2011-10-16 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/879943/+subscriptions

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


[Touch-packages] [Bug 1482296] Re: State handling slightly inconsistence with the qt documentation description

2015-10-21 Thread Sam Segers
Connected to: https://bugs.launchpad.net/qtubuntu/+bug/1504776

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

Title:
  State handling slightly inconsistence with the qt documentation
  description

Status in qtubuntu:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  http://doc.qt.io/qt-5/qml-qtqml-qt.html states

  "Qt.ApplicationSuspended - The application is suspended and not
  visible to the user. On mobile platforms, the application typically
  enters this state when the user returns to the home screen or switches
  to another application."

  or in practice that nevers happen on Ubuntu Touch, the application
  state changes to ApplicationInactive only

  That's what led us to have bug #1482235 on settings, since we were
  turning off bluetooth features on Qt.ApplicationSuspended, the qt
  documentation suggests that the normal cycle should be -> Inactive ->
  Suspended, or the Suspended never reach the application it seems?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtubuntu/+bug/1482296/+subscriptions

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


[Touch-packages] [Bug 1181359] Re: Documents: Integers are getting corrupted

2015-10-10 Thread Sam Segers
** Changed in: u1db-qt
   Status: Confirmed => Fix Released

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

Title:
  Documents: Integers are getting corrupted

Status in U1DB Qt/ QML:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  when saving a javascript object with an integer, the integer is not
  the same after retrieved from the db.

  Saving {test_id:2911298} will result in {test_id:2911300}.  I'm using
  0.1.4bzr89quantal0

  Example:

  import QtQuick 2.0
  import U1db 1.0 as U1db

  Item{
  id: u1dbBug

  U1db.Database {
  id: testDatabase
  path: "test-database"
  }

  function testFunction() {
  testDatabase.putDoc({test_id:2911298})
  var docs = testDatabase.listDocs();
  for(var x=0;xhttps://bugs.launchpad.net/u1db-qt/+bug/1181359/+subscriptions

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


[Touch-packages] [Bug 1451554] [NEW] Every key is pressed twice on the desktop

2015-05-04 Thread Sam Segers
Public bug reported:

If I launch an app with QT_IM_MODULE=MaliitPhablet system-settings, every key 
is pressed twice.
Pressing h - a - l - l -o -  gives me:
'Hhaaoo. '

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubuntu-keyboard 0.99.trunk.phablet2+15.04.20150326-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon May  4 21:43:00 2015
InstallationDate: Installed on 2014-10-10 (206 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140922)
SourcePackage: ubuntu-keyboard
SystemImageInfo:
 current build number: 0
 device name:
 channel: daily
 last update: Unknown
UpgradeStatus: Upgraded to vivid on 2015-01-02 (122 days ago)

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


** Tags: amd64 apport-bug vivid

** Description changed:

  If I launch an app with QT_IM_MODULE=MaliitPhablet system-settings, every key 
is pressed twice.
  Pressing h - a - l - l -o -  gives me:
- 'Hhaalloo. '
+ 'Hhaaoo. '
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-keyboard 0.99.trunk.phablet2+15.04.20150326-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  4 21:43:00 2015
  InstallationDate: Installed on 2014-10-10 (206 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140922)
  SourcePackage: ubuntu-keyboard
  SystemImageInfo:
-  current build number: 0
-  device name: 
-  channel: daily
-  last update: Unknown
+  current build number: 0
+  device name:
+  channel: daily
+  last update: Unknown
  UpgradeStatus: Upgraded to vivid on 2015-01-02 (122 days ago)

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

Title:
  Every key is pressed twice on the desktop

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  If I launch an app with QT_IM_MODULE=MaliitPhablet system-settings, every key 
is pressed twice.
  Pressing h - a - l - l -o -  gives me:
  'Hhaaoo. '

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-keyboard 0.99.trunk.phablet2+15.04.20150326-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  4 21:43:00 2015
  InstallationDate: Installed on 2014-10-10 (206 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140922)
  SourcePackage: ubuntu-keyboard
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to vivid on 2015-01-02 (122 days ago)

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

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


[Touch-packages] [Bug 1397718] [NEW] Scopes not easily discovered

2014-11-30 Thread Sam Segers
Public bug reported:

It would be nice if there is an easy way to search for scopes. Either a
way to switch between apps and/or scopes or let searching for
scope/scopes list all the scopes (now the scopes need to add 'scope' to
SearchHint)

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

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

Title:
  Scopes not easily discovered

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

Bug description:
  It would be nice if there is an easy way to search for scopes. Either
  a way to switch between apps and/or scopes or let searching for
  scope/scopes list all the scopes (now the scopes need to add 'scope'
  to SearchHint)

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

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