[Touch-packages] [Bug 1528645] [NEW] Please update ca-certificates on Trusty

2015-12-22 Thread Rohan Garg
Public bug reported:

Hi
The ca-certificates package on Trusty is quite out of date, would it be 
possible for someone to update the package to the version from Xenial?

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ca-certificates 20150426ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Dec 22 18:57:08 2015
InstallationDate: Installed on 2015-10-05 (78 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825.1)
PackageArchitecture: all
SourcePackage: ca-certificates
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ca-certificates (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: amd64 apport-bug trusty upgrade-software-version

** Changed in: ca-certificates (Ubuntu)
Milestone: None => trusty-updates

** Tags removed: wily
** Tags added: trusty upgrade-software-version

** Changed in: ca-certificates (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Please update ca-certificates on Trusty

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Hi
  The ca-certificates package on Trusty is quite out of date, would it be 
possible for someone to update the package to the version from Xenial?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ca-certificates 20150426ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Dec 22 18:57:08 2015
  InstallationDate: Installed on 2015-10-05 (78 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825.1)
  PackageArchitecture: all
  SourcePackage: ca-certificates
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1464449] [NEW] libmission-control-plugins-dev should depend on libtelepathy-glib-dev

2015-06-11 Thread Rohan Garg
Public bug reported:

libmission-control-plugins-dev should depend on libtelepathy-glib-dev ,
since pkg-config doesn't pick it up otherwise

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: libmission-control-plugins-dev 1:5.16.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
Uname: Linux 3.19.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Jun 12 02:54:23 2015
InstallationDate: Installed on 2015-05-19 (23 days ago)
InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150421.1)
SourcePackage: telepathy-mission-control-5
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: telepathy-mission-control-5 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

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

Title:
  libmission-control-plugins-dev should depend on libtelepathy-glib-dev

Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  libmission-control-plugins-dev should depend on libtelepathy-glib-dev
  , since pkg-config doesn't pick it up otherwise

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libmission-control-plugins-dev 1:5.16.3-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jun 12 02:54:23 2015
  InstallationDate: Installed on 2015-05-19 (23 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150421.1)
  SourcePackage: telepathy-mission-control-5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1464449/+subscriptions

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


[Touch-packages] [Bug 1423659] Re: Qt4 applications show wrong number format, making them unusable

2015-03-21 Thread Rohan Garg
Maybe this should be reported upstream in the Qt bug tracker if its a
bug in Qt4?

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

Title:
  Qt4 applications show wrong number format, making them unusable

Status in qt4-x11 package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  I am using Scribus 1.4.2 on Ubuntu Gnome 14.04 with the locale ku_TR,
  which uses roman script, and arabic numbers like 123456789.

  All numbers in Scribus are displayed in Arabic-Indic numerals like
  ٠١٢٣٤٥٦٧٨٩ . For people who are not used to these numerals, Scribus
  becomes practically unusable.

  This is independent from the user interface language of Scribus.

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

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


[Touch-packages] [Bug 1369111] Re: baloo_file_extractor crashed with SIGSEGV in memcpy()

2015-02-18 Thread Rohan Garg
Re-assigning to the taglib package.

** Package changed: baloo (Ubuntu) = taglib (Ubuntu)

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

Title:
  baloo_file_extractor crashed with SIGSEGV in memcpy()

Status in taglib package in Ubuntu:
  New

Bug description:
  This happens during regular desktop use, after removing drives from
  Kubuntu's exlusion list, so that there were more drives to scan.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: baloo 4:4.13.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: KDE
  Date: Sat Sep 13 17:36:59 2014
  ExecutablePath: /usr/bin/baloo_file_extractor
  ProcCmdline: /usr/bin/baloo_file_extractor 4752 4751 4750 4749 4748 4747 4746 
4745 4743 4741
  SegvAnalysis:
   Segfault happened at: 0x7f52bfda1a7e __memcpy_sse2_unaligned+46:   movdqu 
-0x10(%rsi,%rdx,1),%xmm8
   PC (0x7f52bfda1a7e) ok
   source -0x10(%rsi,%rdx,1) (0x101226e6b) not located in a known VMA region 
(needed readable region)!
   destination %xmm8 ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: baloo
  StacktraceTop:
   TagLib::ByteVector::replace(TagLib::ByteVector const, TagLib::ByteVector 
const) () from /usr/lib/x86_64-linux-gnu/libtag.so.1
   TagLib::ID3v2::SynchData::decode(TagLib::ByteVector const) () from 
/usr/lib/x86_64-linux-gnu/libtag.so.1
   TagLib::ID3v2::FrameFactory::createFrame(TagLib::ByteVector const, 
TagLib::ID3v2::Header*) const () from /usr/lib/x86_64-linux-gnu/libtag.so.1
   TagLib::ID3v2::Tag::parse(TagLib::ByteVector const) () from 
/usr/lib/x86_64-linux-gnu/libtag.so.1
   TagLib::ID3v2::Tag::read() () from /usr/lib/x86_64-linux-gnu/libtag.so.1
  Title: baloo_file_extractor crashed with SIGSEGV in 
TagLib::ByteVector::replace()
  UpgradeStatus: Upgraded to trusty on 2014-08-29 (14 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse libvirtd 
lpadmin netdev plugdev pulse sambashare saned tape vboxusers video

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

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


[Touch-packages] [Bug 1413159] Re: kscreenlock incompatible with CJK input

2015-01-21 Thread Rohan Garg
Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the
KDE program itself, and not with our KDE packages. While we appreciate
your issue, it would be better if it was tracked at
https://bugs.kde.org, so that the KDE developers can deal with this
speedily and have direct communication with you as the reporter for more
effective debugging.

Thanks!

** Changed in: qt4-x11 (Ubuntu)
   Status: New = Invalid

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

Title:
  kscreenlock incompatible with CJK input

Status in qt4-x11 package in Ubuntu:
  Invalid

Bug description:
  If KDE screen is locked with CJK input system active, password input
  is no longer possible, since there is no way to change the input
  method (default keyboard shortcut would be ctrl + space)  from a
  locked screen. Hence a password named password would then become
  ぱっすぉrd. And since these two strings obviously do jot match, login is
  no longer possible.

  ubuntu 14.04 LTS

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

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


[Touch-packages] [Bug 1166102] Re: Cannot mix incompatible Qt library

2015-01-03 Thread Rohan Garg
Hi
Could you possibly pastebin the output of apt-cache policy libqt4-opengl

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

Title:
  Cannot mix incompatible Qt library

Status in qt4-x11 package in Ubuntu:
  Confirmed

Bug description:
  After an habitual system update, some Qt packages are updated to 4.8.4 and 
other stayed at 4.8.3
  Many Qt apps no more work on my x64 install

  $ qdbusviewer
  Cannot mix incompatible Qt library (version 0x40803) with this library 
(version 0x40804)
  Aborted (core dumped)

  Then to make it work, I need to do this before launching the app
  $ export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libqt4-core (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
  Uname: Linux 3.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Mon Apr  8 11:38:53 2013
  InstallationDate: Installed on 2012-01-12 (451 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: qt4-x11
  UpgradeStatus: Upgraded to quantal on 2012-11-27 (131 days ago)

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

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


[Touch-packages] [Bug 1317449] Re: sqlite3 version 3.8.2 breaks digikam

2014-09-08 Thread Rohan Garg
** Changed in: digikam (Ubuntu)
 Assignee: (unassigned) = Rohan Garg (rohangarg)

** Changed in: sqlite3 (Ubuntu)
 Assignee: (unassigned) = Rohan Garg (rohangarg)

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

Title:
  sqlite3 version 3.8.2 breaks digikam

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

Bug description:
  Please update sqlite to a version  3.8.2.

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

  Workaround:
  Install sqlite3  3.8.2, e.g. you can manually install the corresponding deb 
packages from either utopic or debian.

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

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