[Touch-packages] [Bug 1593720] [NEW] package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned

2016-06-17 Thread George Karakostas
Public bug reported:

While upgrading from 15.10 to 16.04.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20160104ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Jun 17 11:49:22 2016
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2015-11-13 (216 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: ca-certificates
Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to xenial on 2016-06-17 (0 days ago)

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


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  While upgrading from 15.10 to 16.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jun 17 11:49:22 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-11-13 (216 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-06-17 (0 days ago)

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

-- 
Mailing list: https://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 1286910] Re: Lock screen uses last active window's language instead of default keyboard language

2014-10-01 Thread George Karakostas
The solution in
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/comments/19
for other bug seems to affect this one as well.

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

Title:
  Lock screen uses last active window's language instead of default
  keyboard language

Status in Unity:
  New
Status in “gnome-screensaver” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Lock screen (gnome-screensaver) uses last active window's language
  (keyboard layout) instead of default keyboard language.

  Steps to reproduce this bug:
  1. In the system Text Entry settings:
1a. add two or more languages to the input sources list, e.g. English (as 
first and default) and Russian (as second);
1b. Set hotkeys to switch sources (e.g. Ctrl+Shift or CapsLock).
1c. Select "Allow different sources for each window" radio button.
1d. Select "New windows use the default source" radio button.
  2. Run any application (e.g. gedit) and switch keyboard to second input 
language (Russian).
  3. Lock the screen (Ctrl+Alt+L) or just wait idle time.
  4. See what language set by default for password input in the lock screen.

  Expected: lock screen uses first input language (English) by default.
  What happened instead: lock screen uses last active window's language 
(Russian).

  Ubuntu versions affected: Ubuntu 13.10, Ubuntu 14.04 (daily builds)
  gnome-screensaver versions: 3.6.1-0ubuntu7, 3.6.1-0ubuntu9

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

-- 
Mailing list: https://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 1266672] Re: Wrong key input after boot, although right language set

2014-10-01 Thread George Karakostas
Possible duplicate of
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198

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

Title:
  Wrong key input after boot, although right language set

Status in “ibus” package in Ubuntu:
  New

Bug description:
  Ever since the 13.10 Ubuntu upgrade I have this problem when I boot to
  my computer: although Slovenian input is set on login screen the
  keyboard is actually US. If I go to the keyboard settings I only see
  that the right (Slovenian) language is set.

  I can get back to my keyboard if I click 'lock/switch' account, and
  then click the 'Switch user' button to login to my account again.
  After that Slovenian keyboard is back.

  This problem doesn't appear on every (re)boot, but mostly (some 80%).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ibus 1.5.3-6ubuntu2.1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Jan  7 09:00:27 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-05 (276 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402)
  MarkForUpload: True
  SourcePackage: ibus
  UpgradeStatus: Upgraded to saucy on 2013-09-28 (100 days ago)

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

-- 
Mailing list: https://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 1240198] Re: Wrong keyboard layout active after booting into desktop

2014-10-01 Thread George Karakostas
#19 works for me. Also fixes other issues too such as wrong language
indication and occasional slight delay in switch. Wonder if this setting
should be default as suggested. See
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1303005/comments/7

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

Title:
  Wrong keyboard layout active after booting into desktop

Status in “ibus” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  I upgraded from raring to saucy.

  After booting into the desktop (unity), the english keyboard layout is
  active, although everything on the system is set to be german
  (keyboard layout, language...)

  Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and
  changes the layout to the german layout.

  all the time, the new input settings indicator says the german layout
  is active.

  locale says: 
  LANG=de_DE.UTF-8
  LANGUAGE=de_DE
  LC_CTYPE="de_DE.UTF-8"
  LC_NUMERIC="de_DE.UTF-8"
  LC_TIME="de_DE.UTF-8"
  LC_COLLATE="de_DE.UTF-8"
  LC_MONETARY="de_DE.UTF-8"
  LC_MESSAGES="de_DE.UTF-8"
  LC_PAPER="de_DE.UTF-8"
  LC_NAME="de_DE.UTF-8"
  LC_ADDRESS="de_DE.UTF-8"
  LC_TELEPHONE="de_DE.UTF-8"
  LC_MEASUREMENT="de_DE.UTF-8"
  LC_IDENTIFICATION="de_DE.UTF-8"
  LC_ALL=

  /etc/default/keyboard says:
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL="pc105"
  XKBLAYOUT="de"
  XKBVARIANT=""
  XKBOPTIONS=""

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:49:03 2013
  InstallationDate: Installed on 2013-04-26 (171 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago)

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

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