date:20171028

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  systemd RestartSec does not seem to work consistently

Status in systemd package in Ubuntu:
  Expired

Bug description:
  The unit file for my service -33005.service:

  [Unit]
  Description=product  33005 service
  Wants=some.mount
  After=some.mount
  PartOf=product.target
  PartOf=someother.service
  [Service]
  Type=simple
  ExecStart=/opt/product/bin/ -conf=/etc/product.conf
  Restart=on-failure
  User=product
  Group=product
  LimitCORE=infinity
  LimitNOFILE=1
  Slice=.slice
  WatchdogSec=120
  RestartSec=10
  StartLimitInterval=120
  StartLimitBurst=10
  [Install]
  WantedBy=product.target

  specifies RestartSec=10, which is also what systemd sees:

  $ systemctl show -33005.service
  Type=simple
  Restart=on-failure
  NotifyAccess=main
  RestartUSec=10s
  ...

  However, today I saw in the journalctl log:
  $ journalctl -u -33005.service
  ...
  Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Watchdog timeout 
(limit 2min)!
  Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Main process 
exited, code=exited, status=2/INVALIDARGUMENT
  Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Unit entered 
failed state.
  Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Failed with result 
'exit-code'.
  Aug 15 23:28:39 a-hostname systemd[1]: -33005.service: Service hold-off 
time over, scheduling restart.
  Aug 15 23:28:39 a-hostname systemd[1]: Stopped product  33005 service.
  Aug 15 23:28:39 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:28:45 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:28:45 a-hostname systemd[1]: Stopping product  33005 service...
  Aug 15 23:28:45 a-hostname systemd[1]: Stopped product  33005 service.
  Aug 15 23:33:51 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:33:51 a-hostname [3629]: Get http://127.0.0.1:8081/: dial tcp 
127.0.0.1:8081: getsockopt: connection refused
  Aug 15 23:33:51 a-hostname systemd[1]: -33005.service: Main process 
exited, code=exited, status=2/INVALIDARGUMENT
  Aug 15 23:33:51 a-hostname systemd[1]: -33005.service: Unit entered 
failed state.
  Aug 15 23:33:51 a-hostname systemd[1]: -33005.service: Failed with result 
'exit-code'.
  Aug 15 23:34:01 a-hostname systemd[1]: -33005.service: Service hold-off 
time over, scheduling restart.
  Aug 15 23:34:02 a-hostname systemd[1]: Stopped product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: Started product  33005 service.
  Aug 15 23:34:02 a-hostname systemd[1]: -33005.service: Start request 
repeated too quickly.
  Aug 15 23:34:02 a-hostname systemd[1]: Failed to start product  33005 
service.

  Everything looks to me that systemd is behaving as expected until Aug
  15 23:34:02 when it attempts to start -33005.service not at the
  rate I specified in RestartSec, but possibly at the default 100ms
  rate.  This excerpt shows both the expected 10s restart rate as well
  as the unexpected restart rate.

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  $ uname -a
  Linux a-hostname 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  $ apt-cache policy systemd
  systemd:
    Installed: 229-4ubuntu16
    Candidate: 229-4ubuntu19
    Version table:
   229-4ubuntu19 500
  500 http://internal-repo/ubuntu xenial-updates/main amd64 Packages
   *** 229-4ubuntu16 100
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://internal-repo/ubuntu xenial-security/main amd64 Packages
   229-4ubuntu4 500
  500 http://internal-repo/ubuntu xenial/main amd64 Packages

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

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

[Touch-packages] [Bug 1711870] Re: Praticamente todas as atualizações apresentaram erro.

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Praticamente todas as atualizações apresentaram erro.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  As atualizações não poderam ser concluidas. Varios erros surgiram
  durante o processo de atualização

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  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: Sat Aug 19 20:46:32 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2017-08-08 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=689bf1e6-7c78-4ddc-bfd6-07b7238d444c ro locale=pt_BR quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0P8H6J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Aug 19 20:31:02 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1110 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1711870/+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 1656979] Re: No support for DHE ciphers (TLS)

[Expired for openldap (Ubuntu) because there has been no activity for 60
days.]

** Changed in: openldap (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  No support for DHE ciphers (TLS)

Status in openldap package in Ubuntu:
  Expired

Bug description:
  Hi,

  Seems the OpenLDAP shipped with Xenial (and prior) built against
  GnuTLS does not support DHE cipher suites.

  | hloeung@ldap-server:~$ apt-cache policy slapd
  | slapd:
  |   Installed: 2.4.42+dfsg-2ubuntu3.1
  |   Candidate: 2.4.42+dfsg-2ubuntu3.1
  |   Version table:
  |  *** 2.4.42+dfsg-2ubuntu3.1 500
  | 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  2.4.42+dfsg-2ubuntu3 500
  | 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Our LDAP server is configured with the following:

  | TLSCertificateFile /etc/ssl/certs/ldap-server.crt
  | TLSCertificateKeyFile /etc/ssl/private/ldap-server.key
  | TLSCACertificateFile /etc/ssl/certs/ldap-server_chain.crt
  | TLSProtocolMin 1.0
  | TLSCipherSuite 
PFS:-VERS-SSL3.0:-DHE-DSS:-ARCFOUR-128:-3DES-CBC:-CAMELLIA-128-GCM:-CAMELLIA-256-GCM:-CAMELLIA-128-CBC:-CAMELLIA-256-CBC:%SERVER_PRECEDENCE
  | TLSDHParamFile /etc/ssl/private/dhparams.pem

  I know TLSDHParamFile isn't used by OpenLDAP when built with GnuTLS,
  but thought I'd try anyways. cipherscan[1] shows the following list of
  cipher suites:

  | prio  ciphersuite  protocols  pfs   
  curves
  | 1 ECDHE-RSA-AES128-GCM-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 2 ECDHE-RSA-AES256-GCM-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 3 ECDHE-RSA-AES128-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 4 ECDHE-RSA-AES128-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 5 ECDHE-RSA-AES256-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 6 ECDHE-RSA-AES256-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1

  Even with TLSCipherSuite config commented out, we see the following
  cipher suites:

  | prio  ciphersuite  protocols  pfs   
  curves
  | 1 ECDHE-RSA-AES256-GCM-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 2 ECDHE-RSA-AES256-SHA384  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 3 ECDHE-RSA-AES256-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 4 AES256-GCM-SHA384TLSv1.2None  
  None
  | 5 AES256-SHA256TLSv1.2None  
  None
  | 6 AES256-SHA   TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 7 CAMELLIA256-SHA  TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 8 ECDHE-RSA-AES128-GCM-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 9 ECDHE-RSA-AES128-SHA256  TLSv1.2
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 10ECDHE-RSA-AES128-SHA TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 11AES128-GCM-SHA256TLSv1.2None  
  None
  | 12AES128-SHA256TLSv1.2None  
  None
  | 13AES128-SHA   TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 14CAMELLIA128-SHA  TLSv1,TLSv1.1,TLSv1.2  None  
  None
  | 15ECDHE-RSA-DES-CBC3-SHA   TLSv1,TLSv1.1,TLSv1.2  
ECDH,P-256,256bits  prime192v1,secp224r1,prime256v1,secp384r1,secp521r1
  | 16DES-CBC3-SHA TLSv1,TLSv1.1,TLSv1.2  None  
  None

  I think the fix is in the patch below that's released in 2.4.39:

  
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commitdiff;h=622d13a32ec8d623c26a11b60b63e443dc86df99

  
  Thanks,

  Haw

  
  [1]https://github.com/jvehent/cipherscan

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

[Touch-packages] [Bug 1713248] Re: pubkey auth hangs on high latency networks

[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]

** Changed in: openssh (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  pubkey auth hangs on high latency networks

Status in openssh package in Ubuntu:
  Expired

Bug description:
  This is a weird one. I use a small fleet of laptops to do professional
  network testing, and I wrote some tools that use SSH with pubkey auth
  to run simultaneous tests.

  The problem is, if the wifi connection isn't superb, the auth times
  out more often than not. For example, if I've got a long range 5 GHz
  connection which returns 100% of pings but has a median latency of
  100ms or so, auth hangs after send packet: type 50, never receiving
  the packet type 51 to complete the auth.

  debug2: key: /root/.ssh/id_ecdsa ((nil))
  debug2: key: /root/.ssh/id_ed25519 ((nil))
  debug3: send packet: type 5
  debug3: receive packet: type 6
  debug2: service_accept: ssh-userauth
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug3: send packet: type 50

  This is where it hangs; after approximately a 30 second timeout
  (haven't clocked it precisely) it falls through to any remaining
  available authentication methods - other keys, hostbased, password,
  whatever hasn't been explicitly disabled.

  Yes, UseDNS no is on, on both client and sender. I've also disabled
  all non-essential PAM modules, and disabled HostBasedAuth, RSAAuth,
  and GSSAPI on both client and sender.

  The same two laptops in the same location will complete password
  authentication without a problem - if a pubkey is present for the user
  on the client side, it'll have to time that out first before it fails
  through and asks for the password (which will be promptly accepted and
  work normally); but if there is no pubkey for the client user, it'll
  prompt for the password and accept it immediately.

  If I move the server laptop closer to the router, so that the median
  latency falls in something more like the 50ms range, the pubkey auth
  works fine. I want to reiterate here that we're talking about high
  latency, but we're *not* talking about dropped packets - pings between
  the laptops when they're having problems range from 100ms-900ms
  latency, but with 100% returns. (And, again, password auth works fine,
  it's only pubkey that has the issue - and only when latency is high.)

  I can't find anything on the internets referring to a problem with
  high latency pubkey authentication on machines where pubkey auth works
  fine with lower latency, but here I am.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Aug 26 12:04:22 2017
  InstallationDate: Installed on 2016-11-05 (293 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1713248/+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 1713435] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]

** Changed in: openssh (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Expired

Bug description:
  invoke-rc.d: initscript ssh, action "start" failed.
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Mon 2017-08-28 14:36:40 IST; 9ms 
ago
Process: 21687 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255)
   Main PID: 21687 (code=exited, status=255)

  Aug 28 14:36:40 LinuxMachine systemd[1]: Starting OpenBSD Secure Shell 
server...
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Main process exited, 
c...a
  Aug 28 14:36:40 LinuxMachine systemd[1]: Failed to start OpenBSD Secure 
Shel
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Unit entered failed 
state.
  Aug 28 14:36:40 LinuxMachine systemd[1]: ssh.service: Failed with result 
'ex

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Aug 28 14:36:40 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-12 (258 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1713435/+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 1713363] Re: package systemd 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package systemd 232-21ubuntu5 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

Status in systemd package in Ubuntu:
  Expired

Bug description:
  -Computer-
  Processor : Intel(R) Celeron(R) M processor  900MHz
  Memory: 2052MB (940MB used)
  Operating System  : Ubuntu 17.04
  User Name : casaserra (casaserra)
  Date/Time : dom 27 ago 2017 22:21:26 CEST
  -Display-
  Resolution: 1280x1024 pixels
  OpenGL Renderer   : Unknown
  X11 Vendor: The X.Org Foundation
  -Multimedia-
  Audio Adapter : HDA-Intel - HDA Intel
  -Input Devices-
   Lid Switch
   Sleep Button
   Power Button
   Power Button
   AT Translated Set 2 keyboard
   Video Bus
   SynPS/2 Synaptics TouchPad
   Asus EeePC extra buttons
   HDA Intel Mic
   HDA Intel Headphone
   UVC Camera (eb1a:2761)
  -Printers-
  No printers found
  -SCSI Disks-
  ATA SILICONMOTION SM
   USB DISK 3.0
  USB2.0 CardReader SD0

  systemd:
Installato: 232-21ubuntu5
Candidato:  232-21ubuntu5
Tabella versione:
   *** 232-21ubuntu5 500
  500 http://it.archive.ubuntu.com/ubuntu zesty-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu zesty-security/main i386 
Packages
  100 /var/lib/dpkg/status
   232-21ubuntu2 500
  500 http://it.archive.ubuntu.com/ubuntu zesty/main i386 Packages
  3) What you expected to happen: software updates should be got installed
  4) What happened instead: I got a masseage saying some pacakages couldn't be 
installed

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  Date: Sun Aug 27 20:27:49 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-08-27 (0 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  MachineType: ASUSTeK Computer INC. 701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=dffd559d-cd18-4fee-a7c2-7a0504a4b587 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: systemd
  Title: package systemd 232-21ubuntu5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 701
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1302:bd03/11/2009:svnASUSTeKComputerINC.:pn701:pvrx.x:rvnASUSTeKComputerINC.:rn701:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.name: 701
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713363/+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 1728337] [NEW] watchdog: BUG: soft lockup & general instability

2017-10-28 Thread Patrick Jeeves

Public bug reported:

I've included the only time that the logs produced any output around the
time of the crashes; which was a soft lockup error.

Regardless, i've had a lot of instability ever since installing artful;
to me that suggests a kernel issue. Although lots of applications crash
for no discernible reason with nothing in the logs to suggest why, and
no pattern at all. Doing a clean install didn't help matters, although
it was necessary, my system was bricked by one of the crashes.

Ubuntu bug doesn't work correctly, at all.  I selected "other problem"
and it brought up display issues; then brought of a dialog titled "text"
with the message "text" and asked me yes or no, i selected no, and that
didn't seem to matter.  I selected that i didn't know if i could provide
more information, and in the report it listed that as willing to do
something with git, etc.  It would be much easier to report bugs, if the
bug reporter worked correctly, for instance.

$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Sat Oct 28 23:18:52 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: kubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480 [1002:0b37]
InstallationDate: Installed on 2017-10-25 (3 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3b4ce692-60a9-44c0-8ba4-7bbc83853047 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F7a
dmi.board.asset.tag: Default string
dmi.board.name: AB350-Gaming-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7a:bd09/15/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350-Gaming
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful kubuntu

** Attachment added: "kern.log"
   https://bugs.launchpad.net/bugs/1728337/+attachment/4999202/+files/kern.log

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

Title:
  watchdog: BUG: soft lockup & general instability

Status in xorg package in Ubuntu:
  New

Bug description:
  I've included the only time that the logs produced any output around
  the time of the crashes; which was a soft lockup error.

  Regardless, i've had a lot of instability ever since installing
  artful; to me that suggests a kernel issue. Although lots of
  applications crash for no discernible reason with nothing in the logs
  to suggest why, and no pattern at all. Doing a clean install didn't
  help matters, although it was necessary, my system was bricked by one
  of the crashes.

  Ubuntu bug doesn't work correctly, at all.  I selected "other problem"
  and it brought up display issues; then brought of a dialog titled
  "text" with the message "text" and asked me yes or no, i selected no,
  and that didn't seem to matter.  I selected that i didn't know if i
  could provide more information, and in the report it listed that as
  willing to do something with git, etc.  It would be much easier to
  report bugs, if the bug reporter worked correctly, for instance.

  $ lsb_rele

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

We can't update freetype to 2.8.1 in Ubuntu 17.10 because it will break
Electron apps (LP: #1728329). But Ubuntu 18.04 LTS will likely get
freetype 2.8.1 (or possibly a newer version).

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+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 1728329] Re: Update freetype to 2.8.1

** Tags added: block-proposed

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

Title:
  Update freetype to 2.8.1

Status in freetype package in Ubuntu:
  Triaged

Bug description:
  We should merge freetype 2.8.1 from Debian Testing.

  freetype (2.8.1-0.1) unstable; urgency=medium

* Non-maintainer upload.
* New upstream release (Closes: #876132)
  - Refresh debian/patches-ft2demos/compiler_hardening_fixes.patch,
partially fixed upstream
  - debian/libfreetype6.symbols: Add newly export symbol

  
  However, there is a regression in Electron apps.

  https://bugs.chromium.org/p/skia/issues/detail?id=6663
  https://github.com/Microsoft/vscode/issues/35675
  https://github.com/atom/atom/issues/15737

  https://github.com/electron/electron/pull/10213

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1728329/+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 1728329] [NEW] Update freetype to 2.8.1

Public bug reported:

We should merge freetype 2.8.1 from Debian Testing.

freetype (2.8.1-0.1) unstable; urgency=medium

  * Non-maintainer upload.
  * New upstream release (Closes: #876132)
- Refresh debian/patches-ft2demos/compiler_hardening_fixes.patch,
  partially fixed upstream
- debian/libfreetype6.symbols: Add newly export symbol


However, there is a regression in Electron apps.

https://bugs.chromium.org/p/skia/issues/detail?id=6663
https://github.com/Microsoft/vscode/issues/35675
https://github.com/atom/atom/issues/15737

https://github.com/electron/electron/pull/10213

** Affects: freetype (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: bionic upgrade-software-version

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

Title:
  Update freetype to 2.8.1

Status in freetype package in Ubuntu:
  Triaged

Bug description:
  We should merge freetype 2.8.1 from Debian Testing.

  freetype (2.8.1-0.1) unstable; urgency=medium

* Non-maintainer upload.
* New upstream release (Closes: #876132)
  - Refresh debian/patches-ft2demos/compiler_hardening_fixes.patch,
partially fixed upstream
  - debian/libfreetype6.symbols: Add newly export symbol

  
  However, there is a regression in Electron apps.

  https://bugs.chromium.org/p/skia/issues/detail?id=6663
  https://github.com/Microsoft/vscode/issues/35675
  https://github.com/atom/atom/issues/15737

  https://github.com/electron/electron/pull/10213

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1728329/+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 191654] Re: Activate font auto hinting by default

Quoting from the Arch Linux wiki:

"The autohinter attempts to do automatic hinting and disregards any
existing hinting information. Originally it was the default because
TrueType2 fonts were patent-protected but now that these patents have
expired there is very little reason to use it. It does work better with
fonts that have broken or no hinting information but it will be strongly
sub-optimal for fonts with good hinting information. Generally common
fonts are of the later kind so autohinter will not be useful. Autohinter
is disabled by default."

https://wiki.archlinux.org/index.php/font_configuration#Autohinter

If you disagree (ideally with evidence to support your position), please
contact the Ubuntu Desktop Team to discuss.

For now, I'm closing this bug.

** Changed in: fontconfig (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 fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/191654

Title:
  Activate font auto hinting by default

Status in fontconfig package in Ubuntu:
  Won't Fix

Bug description:
  Activate autohinting by default on fonts, preferably system wide. It makes a 
huge difference qua font quality.
  In hardy alpha4 it's not on by default e.g.

  More information on http://ubuntuforums.org/showthread.php?t=4456

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/191654/+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 1728326] [NEW] package python-apt 0.9.3.5ubuntu2 failed to install/upgrade: dependency problems - leaving unconfigured

2017-10-28 Thread Luis Fernando Lara

Public bug reported:

me sale error en el sistemas y me da muchos problemas

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python-apt 0.9.3.5ubuntu2
Uname: Linux 3.13.0-133-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Sat Oct 28 18:20:15 2017
ErrorMessage: dependency problems - leaving unconfigured
InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 
20120718-04:29
LiveMediaBuild: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 20120718-04:29
SourcePackage: python-apt
Title: package python-apt 0.9.3.5ubuntu2 failed to install/upgrade: dependency 
problems - leaving unconfigured

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


** Tags: apport-package i386

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

Title:
  package python-apt 0.9.3.5ubuntu2 failed to install/upgrade:
  dependency problems - leaving unconfigured

Status in python-apt package in Ubuntu:
  New

Bug description:
  me sale error en el sistemas y me da muchos problemas

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-apt 0.9.3.5ubuntu2
  Uname: Linux 3.13.0-133-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Sat Oct 28 18:20:15 2017
  ErrorMessage: dependency problems - leaving unconfigured
  InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 
20120718-04:29
  LiveMediaBuild: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 20120718-04:29
  SourcePackage: python-apt
  Title: package python-apt 0.9.3.5ubuntu2 failed to install/upgrade: 
dependency problems - leaving unconfigured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1728326/+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 1715599] Re: 2.26-0ubuntu1 breaks compliation of several KDE sources

** Changed in: libxslt (Debian)
   Status: Unknown => Fix Committed

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

Title:
  2.26-0ubuntu1 breaks compliation of several KDE sources

Status in libxslt package in Ubuntu:
  Fix Released
Status in libxslt package in Debian:
  Fix Committed

Bug description:
  gblic 2.26-0ubuntu1 which removed xlocale.h:  breaks compliation of
  several KDE sources, but libxslt still requires that header.

  Including so far, but maybe not limited to is autotests:

  kde4libs
  kio
  kopete

  with the error

  In file included from /usr/include/libxslt/xsltInternals.h:24:0,
   from /usr/include/libxslt/xsltutils.h:23,
   from 
/tmp/autopkgtest.U99BLh/build.W2l/kde4libs-4.14.34/kdoctools/kio_help.cpp:61:
  /usr/include/libxslt/xsltlocale.h:20:10: fatal error: xlocale.h: No such file 
or directory
   #include 
    ^~~
  compilation terminated.

  Confirmed also in kio package rebuild in our staging ppa

  https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-
  frameworks/+sourcepub/8240685/+listing-archive-extra

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1715599/+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 1192175] Re: Use of mode="assign" in default configuration

This bug was fixed in the package fontconfig - 2.12.6-0ubuntu1

---
fontconfig (2.12.6-0ubuntu1) bionic; urgency=medium

  * Merge with Debian (LP: #1638959, LP: #1702544). Remaining changes:
- debian/source_fontconfig.py, debian/fontconfig.install:
  + Install apport hook
- Add 03_prefer_dejavu.patch:
  + Prefer DejaVu to Bitstream Vera
- Add 04_ubuntu_monospace_lcd_filter_conf.patch:
  + Use legacy lcdfilter with smaller monospace fonts
- Add 05_ubuntu_add_antialiasing_confs.patch:
  + Add config file for antialiasing
- Add 05_lcdfilterlegacy.patch: Recognize const value "lcdfilterlegacy",
  used in Ubuntu before upstream introduced "lcdlegacy"
- Add 07_no_bitmaps.patch:
  + Install 70-no-bitmaps.conf
- Drop debian/fontconfig.NEWS, debian/fontconfig-config.templates,
  debian/fontconfig-config.config, and associatedpo files.
  Modify debian/rules, debian/fontconfig-config.postinst,
  debian/fontconfig-config.postrm, and debian/README.Debian.
  + Don't provide debconf prompts
- Modify debian/rules, debian/fontconfig-config.install,
  debian/fontconfig-config.links, debian/fontconfig-config.postrm,
  and debian/fontconfig-udeb.install:
  + Delay doing the transition from /etc to /usr
  * New upstream release
  * Refresh patches
  * Update Ubuntu patches to use mode="append" and target="pattern"
(LP: #1192175)
  * Drop patches applied in new release:
- 01_fonts_nanum.patch
- 03_locale_c.utf8.patch
- 06_cross.patch
- CVE-2016-5384.patch

fontconfig (2.12.3-1) unstable; urgency=low

  * Rebuild current bits as maintainer upload
  * Add dependency on python2.7, python-lxml, python-six
  * Add dependency on docbook, docbook-utils, texlive-formats-extra
  * Set FREETYPE_PROPERTIES=truetype:interpreter-version=35 iff
selected hintstyle is hintfull. This produces fully hinted glyphs
with current FreeType bits.

fontconfig (2.12.3-0.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Add a NEWS file to describe the change in the default hinting style. Also
add a debconf question to allow the administrator to change it (Closes:
#866950)

fontconfig (2.12.3-0.1) unstable; urgency=medium

  * Non-maintainer upload.
  * New upstream release
- Do not FTBFS if docbook-utils is installed (Closes: #862483)
- Drop debian/patches/01_path_max.patch, merged upstream
- Refresh debian/patches/06_cross.patch
  * debian/watch: Switch to .bz2 tarballs
  * debian/control: Bump Standards-Version to 4.0.0 (no further changes)

fontconfig (2.12.1-0.1) experimental; urgency=medium

  * Non-maintainer upload.
  * New upstream release (Closes: #816045)
- d/p/01_path_max.patch, d/p/06_cross.patch: Refreshed
- Drop patches/05_doc_files.patch, the tarball already contains the
  pre-generated documentation
- Drop d/p/07_CVE-2016-5384-Properly-validate-offsets-in-cache-files.patch:
  Applied upstream
  * Drop -dbg package and rely on the -dbgsym ones, bump debhelper dependency
to be sure that dh_stip has --dbgsym-migration flag
  * debian/rules: Pass --enable-static flag to also build the static library
  * Updated debconf questions translations: debian/po/tr.po, debian/po/it.po
and debian/po/pt_BR.po (Closes: #756715, 760203, 799416)
  * debian/control: Remove duplicate Section fields to please lintian
  * Adjust several lintian-overrides files
  * debian/fontconfig-config.postrm: Do not hardcode ucf path

fontconfig (2.11.0-6.7) unstable; urgency=medium

  * Non-maintainer upload.
  * Modifiy /etc/fontconfig/fonts.conf to ignore *.dpkg-new files.
(Closes: #835142)

fontconfig (2.11.0-6.6) unstable; urgency=medium

  * Non-maintainer upload.
  * Modifiy /etc/fontconfig/fonts.conf to ignore *.dpkg-tmp files.
(Closes: #828037)

fontconfig (2.11.0-6.5) unstable; urgency=high

  * Non-maintainer upload.
  * CVE-2016-5384: Possible double free due to insufficiently validated cache
files (Closes: #833570)

fontconfig (2.11.0-6.4) unstable; urgency=medium

  * Non-maintainer upload.
  * Drop versioned Build-Depends: binutils which is satisfied even in
oldstable (Closes: #779460).
  * Compile build-tool edit-sgml with CC_FOR_BUILD. (Closes: #779461)

fontconfig (2.11.0-6.3) unstable; urgency=medium

  * Non-maintainer upload.
  * Modify fontconfig-config.postinst to not touch the symlinks unless it's
a first install or a reconfigure was issued (Closes: #758973).

fontconfig (2.11.0-6.2) unstable; urgency=medium

  * Non-maintainer upload to delayed
  * Switch to noawait triggers to allow self-triggering; will still need
Breaks from dpkg to resolve this (closes: #768599)
  * Add Pre-Depends on dpkg to allow for noawait just in case this gets
backported to squeeze.

fontconfig (2.11.0-6.1) unstable; urgency=low

  * Non-maintainer upload to delayed.
  * Add dh-autoreconf to support ppc64el. Closes: #748378

fontconfig (2.11.0-6) unstable; urgency=m

[Touch-packages] [Bug 1638959] Re: Update to 2.12.3

This bug was fixed in the package fontconfig - 2.12.6-0ubuntu1

---
fontconfig (2.12.6-0ubuntu1) bionic; urgency=medium

  * Merge with Debian (LP: #1638959, LP: #1702544). Remaining changes:
- debian/source_fontconfig.py, debian/fontconfig.install:
  + Install apport hook
- Add 03_prefer_dejavu.patch:
  + Prefer DejaVu to Bitstream Vera
- Add 04_ubuntu_monospace_lcd_filter_conf.patch:
  + Use legacy lcdfilter with smaller monospace fonts
- Add 05_ubuntu_add_antialiasing_confs.patch:
  + Add config file for antialiasing
- Add 05_lcdfilterlegacy.patch: Recognize const value "lcdfilterlegacy",
  used in Ubuntu before upstream introduced "lcdlegacy"
- Add 07_no_bitmaps.patch:
  + Install 70-no-bitmaps.conf
- Drop debian/fontconfig.NEWS, debian/fontconfig-config.templates,
  debian/fontconfig-config.config, and associatedpo files.
  Modify debian/rules, debian/fontconfig-config.postinst,
  debian/fontconfig-config.postrm, and debian/README.Debian.
  + Don't provide debconf prompts
- Modify debian/rules, debian/fontconfig-config.install,
  debian/fontconfig-config.links, debian/fontconfig-config.postrm,
  and debian/fontconfig-udeb.install:
  + Delay doing the transition from /etc to /usr
  * New upstream release
  * Refresh patches
  * Update Ubuntu patches to use mode="append" and target="pattern"
(LP: #1192175)
  * Drop patches applied in new release:
- 01_fonts_nanum.patch
- 03_locale_c.utf8.patch
- 06_cross.patch
- CVE-2016-5384.patch

fontconfig (2.12.3-1) unstable; urgency=low

  * Rebuild current bits as maintainer upload
  * Add dependency on python2.7, python-lxml, python-six
  * Add dependency on docbook, docbook-utils, texlive-formats-extra
  * Set FREETYPE_PROPERTIES=truetype:interpreter-version=35 iff
selected hintstyle is hintfull. This produces fully hinted glyphs
with current FreeType bits.

fontconfig (2.12.3-0.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Add a NEWS file to describe the change in the default hinting style. Also
add a debconf question to allow the administrator to change it (Closes:
#866950)

fontconfig (2.12.3-0.1) unstable; urgency=medium

  * Non-maintainer upload.
  * New upstream release
- Do not FTBFS if docbook-utils is installed (Closes: #862483)
- Drop debian/patches/01_path_max.patch, merged upstream
- Refresh debian/patches/06_cross.patch
  * debian/watch: Switch to .bz2 tarballs
  * debian/control: Bump Standards-Version to 4.0.0 (no further changes)

fontconfig (2.12.1-0.1) experimental; urgency=medium

  * Non-maintainer upload.
  * New upstream release (Closes: #816045)
- d/p/01_path_max.patch, d/p/06_cross.patch: Refreshed
- Drop patches/05_doc_files.patch, the tarball already contains the
  pre-generated documentation
- Drop d/p/07_CVE-2016-5384-Properly-validate-offsets-in-cache-files.patch:
  Applied upstream
  * Drop -dbg package and rely on the -dbgsym ones, bump debhelper dependency
to be sure that dh_stip has --dbgsym-migration flag
  * debian/rules: Pass --enable-static flag to also build the static library
  * Updated debconf questions translations: debian/po/tr.po, debian/po/it.po
and debian/po/pt_BR.po (Closes: #756715, 760203, 799416)
  * debian/control: Remove duplicate Section fields to please lintian
  * Adjust several lintian-overrides files
  * debian/fontconfig-config.postrm: Do not hardcode ucf path

fontconfig (2.11.0-6.7) unstable; urgency=medium

  * Non-maintainer upload.
  * Modifiy /etc/fontconfig/fonts.conf to ignore *.dpkg-new files.
(Closes: #835142)

fontconfig (2.11.0-6.6) unstable; urgency=medium

  * Non-maintainer upload.
  * Modifiy /etc/fontconfig/fonts.conf to ignore *.dpkg-tmp files.
(Closes: #828037)

fontconfig (2.11.0-6.5) unstable; urgency=high

  * Non-maintainer upload.
  * CVE-2016-5384: Possible double free due to insufficiently validated cache
files (Closes: #833570)

fontconfig (2.11.0-6.4) unstable; urgency=medium

  * Non-maintainer upload.
  * Drop versioned Build-Depends: binutils which is satisfied even in
oldstable (Closes: #779460).
  * Compile build-tool edit-sgml with CC_FOR_BUILD. (Closes: #779461)

fontconfig (2.11.0-6.3) unstable; urgency=medium

  * Non-maintainer upload.
  * Modify fontconfig-config.postinst to not touch the symlinks unless it's
a first install or a reconfigure was issued (Closes: #758973).

fontconfig (2.11.0-6.2) unstable; urgency=medium

  * Non-maintainer upload to delayed
  * Switch to noawait triggers to allow self-triggering; will still need
Breaks from dpkg to resolve this (closes: #768599)
  * Add Pre-Depends on dpkg to allow for noawait just in case this gets
backported to squeeze.

fontconfig (2.11.0-6.1) unstable; urgency=low

  * Non-maintainer upload to delayed.
  * Add dh-autoreconf to support ppc64el. Closes: #748378

fontconfig (2.11.0-6) unstable; urgency=m

[Touch-packages] [Bug 1702544] Re: Merge fontconfig 2.12.3-0.1 (main) from Debian unstable (main)

This bug was fixed in the package fontconfig - 2.12.6-0ubuntu1

---
fontconfig (2.12.6-0ubuntu1) bionic; urgency=medium

  * Merge with Debian (LP: #1638959, LP: #1702544). Remaining changes:
- debian/source_fontconfig.py, debian/fontconfig.install:
  + Install apport hook
- Add 03_prefer_dejavu.patch:
  + Prefer DejaVu to Bitstream Vera
- Add 04_ubuntu_monospace_lcd_filter_conf.patch:
  + Use legacy lcdfilter with smaller monospace fonts
- Add 05_ubuntu_add_antialiasing_confs.patch:
  + Add config file for antialiasing
- Add 05_lcdfilterlegacy.patch: Recognize const value "lcdfilterlegacy",
  used in Ubuntu before upstream introduced "lcdlegacy"
- Add 07_no_bitmaps.patch:
  + Install 70-no-bitmaps.conf
- Drop debian/fontconfig.NEWS, debian/fontconfig-config.templates,
  debian/fontconfig-config.config, and associatedpo files.
  Modify debian/rules, debian/fontconfig-config.postinst,
  debian/fontconfig-config.postrm, and debian/README.Debian.
  + Don't provide debconf prompts
- Modify debian/rules, debian/fontconfig-config.install,
  debian/fontconfig-config.links, debian/fontconfig-config.postrm,
  and debian/fontconfig-udeb.install:
  + Delay doing the transition from /etc to /usr
  * New upstream release
  * Refresh patches
  * Update Ubuntu patches to use mode="append" and target="pattern"
(LP: #1192175)
  * Drop patches applied in new release:
- 01_fonts_nanum.patch
- 03_locale_c.utf8.patch
- 06_cross.patch
- CVE-2016-5384.patch

fontconfig (2.12.3-1) unstable; urgency=low

  * Rebuild current bits as maintainer upload
  * Add dependency on python2.7, python-lxml, python-six
  * Add dependency on docbook, docbook-utils, texlive-formats-extra
  * Set FREETYPE_PROPERTIES=truetype:interpreter-version=35 iff
selected hintstyle is hintfull. This produces fully hinted glyphs
with current FreeType bits.

fontconfig (2.12.3-0.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Add a NEWS file to describe the change in the default hinting style. Also
add a debconf question to allow the administrator to change it (Closes:
#866950)

fontconfig (2.12.3-0.1) unstable; urgency=medium

  * Non-maintainer upload.
  * New upstream release
- Do not FTBFS if docbook-utils is installed (Closes: #862483)
- Drop debian/patches/01_path_max.patch, merged upstream
- Refresh debian/patches/06_cross.patch
  * debian/watch: Switch to .bz2 tarballs
  * debian/control: Bump Standards-Version to 4.0.0 (no further changes)

fontconfig (2.12.1-0.1) experimental; urgency=medium

  * Non-maintainer upload.
  * New upstream release (Closes: #816045)
- d/p/01_path_max.patch, d/p/06_cross.patch: Refreshed
- Drop patches/05_doc_files.patch, the tarball already contains the
  pre-generated documentation
- Drop d/p/07_CVE-2016-5384-Properly-validate-offsets-in-cache-files.patch:
  Applied upstream
  * Drop -dbg package and rely on the -dbgsym ones, bump debhelper dependency
to be sure that dh_stip has --dbgsym-migration flag
  * debian/rules: Pass --enable-static flag to also build the static library
  * Updated debconf questions translations: debian/po/tr.po, debian/po/it.po
and debian/po/pt_BR.po (Closes: #756715, 760203, 799416)
  * debian/control: Remove duplicate Section fields to please lintian
  * Adjust several lintian-overrides files
  * debian/fontconfig-config.postrm: Do not hardcode ucf path

fontconfig (2.11.0-6.7) unstable; urgency=medium

  * Non-maintainer upload.
  * Modifiy /etc/fontconfig/fonts.conf to ignore *.dpkg-new files.
(Closes: #835142)

fontconfig (2.11.0-6.6) unstable; urgency=medium

  * Non-maintainer upload.
  * Modifiy /etc/fontconfig/fonts.conf to ignore *.dpkg-tmp files.
(Closes: #828037)

fontconfig (2.11.0-6.5) unstable; urgency=high

  * Non-maintainer upload.
  * CVE-2016-5384: Possible double free due to insufficiently validated cache
files (Closes: #833570)

fontconfig (2.11.0-6.4) unstable; urgency=medium

  * Non-maintainer upload.
  * Drop versioned Build-Depends: binutils which is satisfied even in
oldstable (Closes: #779460).
  * Compile build-tool edit-sgml with CC_FOR_BUILD. (Closes: #779461)

fontconfig (2.11.0-6.3) unstable; urgency=medium

  * Non-maintainer upload.
  * Modify fontconfig-config.postinst to not touch the symlinks unless it's
a first install or a reconfigure was issued (Closes: #758973).

fontconfig (2.11.0-6.2) unstable; urgency=medium

  * Non-maintainer upload to delayed
  * Switch to noawait triggers to allow self-triggering; will still need
Breaks from dpkg to resolve this (closes: #768599)
  * Add Pre-Depends on dpkg to allow for noawait just in case this gets
backported to squeeze.

fontconfig (2.11.0-6.1) unstable; urgency=low

  * Non-maintainer upload to delayed.
  * Add dh-autoreconf to support ppc64el. Closes: #748378

fontconfig (2.11.0-6) unstable; urgency=m

[Touch-packages] [Bug 1560114] Re: Bitmap fonts are disabled by default

2017-10-28 Thread Björn Lindqvist

Jeremy, I know that the behaviour is intentional but it is still dumb.
As I wrote, there is no good reason to disable bitmap fonts.

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

Title:
  Bitmap fonts are disabled by default

Status in fontconfig package in Ubuntu:
  Invalid

Bug description:
  By default, fontconfig-config installs a file called
  "/etc/fonts/conf.d/70-no-bitmaps.conf". It disables bitmap fonts. What
  good for, I don't know. Though if you later install a bitmap font
  "apt-get install xfonts-terminus" then that font wont show up in
  menus. That is not what you expect. The workaround is:

  sudo rm /etc/fonts/conf.d/70-no-bitmaps.conf
  sudo ln -s /etc/fonts/conf.avail/70-yes-bitmaps.conf 
/etc/fonts/conf.d/70-yes-bitmaps.conf

  But you shouldn't need that and bitmap founds shouldn't be disabled.

  The bug is present in Ubuntu wily, 15.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1560114/+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 1728317] Re: package libqt4-opengl:amd64 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: package libqt4-opengl:amd64 is already installed and configured

2017-10-28 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 qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1728317

Title:
  package libqt4-opengl:amd64 4:4.8.7+dfsg-5ubuntu2 failed to
  install/upgrade: package libqt4-opengl:amd64 is already installed and
  configured

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  Esse erro e constante. nao tenho esse problema na versao 14.06

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt4-opengl:amd64 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Sat Oct 28 15:59:04 2017
  DuplicateSignature:
   package:libqt4-opengl:amd64:4:4.8.7+dfsg-5ubuntu2
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package dkms (--configure):
package dkms is already installed and configured
  ErrorMessage: package libqt4-opengl:amd64 is already installed and configured
  InstallationDate: Installed on 2017-10-28 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: qt4-x11
  Title: package libqt4-opengl:amd64 4:4.8.7+dfsg-5ubuntu2 failed to 
install/upgrade: package libqt4-opengl:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1728317/+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 1728317] [NEW] package libqt4-opengl:amd64 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: package libqt4-opengl:amd64 is already installed and configured

2017-10-28 Thread George Santos

Public bug reported:

Esse erro e constante. nao tenho esse problema na versao 14.06

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqt4-opengl:amd64 4:4.8.7+dfsg-5ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Sat Oct 28 15:59:04 2017
DuplicateSignature:
 package:libqt4-opengl:amd64:4:4.8.7+dfsg-5ubuntu2
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package dkms (--configure):
  package dkms is already installed and configured
ErrorMessage: package libqt4-opengl:amd64 is already installed and configured
InstallationDate: Installed on 2017-10-28 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: qt4-x11
Title: package libqt4-opengl:amd64 4:4.8.7+dfsg-5ubuntu2 failed to 
install/upgrade: package libqt4-opengl:amd64 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: already-installed 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 qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1728317

Title:
  package libqt4-opengl:amd64 4:4.8.7+dfsg-5ubuntu2 failed to
  install/upgrade: package libqt4-opengl:amd64 is already installed and
  configured

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  Esse erro e constante. nao tenho esse problema na versao 14.06

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt4-opengl:amd64 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Sat Oct 28 15:59:04 2017
  DuplicateSignature:
   package:libqt4-opengl:amd64:4:4.8.7+dfsg-5ubuntu2
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package dkms (--configure):
package dkms is already installed and configured
  ErrorMessage: package libqt4-opengl:amd64 is already installed and configured
  InstallationDate: Installed on 2017-10-28 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: qt4-x11
  Title: package libqt4-opengl:amd64 4:4.8.7+dfsg-5ubuntu2 failed to 
install/upgrade: package libqt4-opengl:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1728317/+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 1728313] Re: integrated intel GPU doesn't work with wayland on ubuntu 17.10

2017-10-28 Thread giannione

** Description changed:

  I've got a CPU with integrated GPU, it's the intel i5-8400; I've also
  installed an old asus [Radeon HD 6670/7670] GPU. OS: ubuntu 17.10
  
  The first problem is that the integrated GPU doesn't work unless you edit 
grub enabling the i915 driver support.
  I had to modify GRUB to load the intel driver:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"
  
  This GPU works perfectly with wayland (gnome and ubuntu session):
  Turks XT [Radeon HD 6670/7670]
  
  But when I enable the integrated GPU (by disabling the Radeon pci GPU from 
the bios), I can't use wayland, which disappears from the login screen.
  My question is why the integrated intel GPU doesn't work with wayland: I can 
only use X.
  
+ If I switch from gdm3 to lightdm, I can see the wayland gnome and ubuntu
+ sessions in the list of the available sessions, but I can't login. To be
+ precise, using lightdm I can't login at all.
+ 
  When logging, there are some errors, for example:
  [OK] Starting session manager for UID 121
- Stopping session manager for UID 121 
- 
- 
- 
+ Stopping session manager for UID 121
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: weston (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 29 00:22:36 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:03f2]
  InstallationDate: Installed on 2017-10-25 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8946514c-0547-4d93-8cf6-bad6b91fa7dc ro quiet splash 
i915.alpha_support=1 vt.handoff=7
  Renderer: Software
  SourcePackage: weston
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0419
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0419:bd10/18/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
   integrated intel GPU doesn't work with wayland on ubuntu 17.10

Status in wayland package in Ubuntu:
  New
Status in weston package in Ubuntu:
  New

Bug description:
  I've got a CPU with integrated GPU, it's the intel i5-8400; I've also
  installed an old asus [Radeon HD 6670/7670] GPU. OS: ubuntu 17.10

  The first problem is that the integrated GPU doesn't work unless you edit 
grub enabling the i915 driver support.
  I had to modify GRUB to load the intel driver:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"

  This GPU works perfectly with wayland (gnome and ubuntu session):
  Turks XT [Radeon HD 6670/7670]

  But when I enable the integrated GPU (by disabling the Radeon pci GPU from 
the bios), I can't use wayland, which disappears from the login screen.
  My question is why the integrated intel GPU doesn't work with wayland: I can 
only use X.

  If I switch from gdm3 to lightdm, I can see the wayland gnome and
  ubuntu sessions in the list of the available sessions, but I can't
  login. To be precise, using lightdm I can't login a

[Touch-packages] [Bug 1715599] Re: 2.26-0ubuntu1 breaks compliation of several KDE sources

2017-10-28 Thread Mattia Rizzolo

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

** Also affects: libxslt (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880038
   Importance: Unknown
   Status: Unknown

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

Title:
  2.26-0ubuntu1 breaks compliation of several KDE sources

Status in libxslt package in Ubuntu:
  Fix Released
Status in libxslt package in Debian:
  Unknown

Bug description:
  gblic 2.26-0ubuntu1 which removed xlocale.h:  breaks compliation of
  several KDE sources, but libxslt still requires that header.

  Including so far, but maybe not limited to is autotests:

  kde4libs
  kio
  kopete

  with the error

  In file included from /usr/include/libxslt/xsltInternals.h:24:0,
   from /usr/include/libxslt/xsltutils.h:23,
   from 
/tmp/autopkgtest.U99BLh/build.W2l/kde4libs-4.14.34/kdoctools/kio_help.cpp:61:
  /usr/include/libxslt/xsltlocale.h:20:10: fatal error: xlocale.h: No such file 
or directory
   #include 
    ^~~
  compilation terminated.

  Confirmed also in kio package rebuild in our staging ppa

  https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-
  frameworks/+sourcepub/8240685/+listing-archive-extra

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1715599/+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 1728313] Re: integrated intel GPU doesn't work with wayland on ubuntu 17.10

2017-10-28 Thread giannione

** Also affects: wayland (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
   integrated intel GPU doesn't work with wayland on ubuntu 17.10

Status in wayland package in Ubuntu:
  New
Status in weston package in Ubuntu:
  New

Bug description:
  I've got a CPU with integrated GPU, it's the intel i5-8400; I've also
  installed an old asus [Radeon HD 6670/7670] GPU. OS: ubuntu 17.10

  The first problem is that the integrated GPU doesn't work unless you edit 
grub enabling the i915 driver support.
  I had to modify GRUB to load the intel driver:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"

  This GPU works perfectly with wayland (gnome and ubuntu session):
  Turks XT [Radeon HD 6670/7670]

  But when I enable the integrated GPU (by disabling the Radeon pci GPU from 
the bios), I can't use wayland, which disappears from the login screen.
  My question is why the integrated intel GPU doesn't work with wayland: I can 
only use X.

  When logging, there are some errors, for example:
  [OK] Starting session manager for UID 121
  Stopping session manager for UID 121 



  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: weston (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 29 00:22:36 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:03f2]
  InstallationDate: Installed on 2017-10-25 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8946514c-0547-4d93-8cf6-bad6b91fa7dc ro quiet splash 
i915.alpha_support=1 vt.handoff=7
  Renderer: Software
  SourcePackage: weston
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0419
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0419:bd10/18/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1728313/+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 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c

Please see bug #228077 for information on the report upstream rejected
for gnome-control-center.

Leandro, I don't have a US keyboard anymore (nor did a read all the
comments here), but if this is still an issue, I don't think a fix will
appear anytime soon.

Good luck on this.

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

Title:
  cedilla appears as accented c (ć instead of ç) when typing 'c

Status in xkeyboard-config:
  Won't Fix
Status in xlibs:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in libx11 package in Ubuntu:
  Fix Released

Bug description:
  
  When typing in a US-international keyboard with dead-keys (or 
UK-international), 
  typing 'c results in an accented c instead of a cedilla.

  There is a workaround, which is editing the

  /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules

  file and changing the line

  "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
  "az:ca:co:fr:gv:oc:pt:sq:tr:wa"

  to

  "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
  "az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"

  (add the 'en' at the end).

  However, every time some update on this file is applied, one looses the 
change,
  and we get back to the accented c. That means having to modify the file again,
  logout and login.

  For me this is no problem. But for my brother, mom, dad, etc, it is always 
something
  that at least makes me less proud of having convinced them to use Ubuntu, 
because
  they don't know what to do each time this happens.

  I think we really need a configurable keyboard layout, or at least (and that 
would
  be very easy), the inclusion of alternate layouts on install that for the 
dead-key
  options (as US-deadkey and UK-deakey), alternate layouts as 
US-deadkey-cedilla.

  This change is relevant for at least Portuguese and French.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+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 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c

This is a duplicate of bug #228077 (which was reported some two years
before this one).

This one, however, draw much more attention than the first one, and has
some attempts on patches. For these reasons I am marking #228077 (and
its other dups) as duplicate of this one.

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

Title:
  cedilla appears as accented c (ć instead of ç) when typing 'c

Status in xkeyboard-config:
  Won't Fix
Status in xlibs:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in libx11 package in Ubuntu:
  Fix Released

Bug description:
  
  When typing in a US-international keyboard with dead-keys (or 
UK-international), 
  typing 'c results in an accented c instead of a cedilla.

  There is a workaround, which is editing the

  /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules

  file and changing the line

  "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
  "az:ca:co:fr:gv:oc:pt:sq:tr:wa"

  to

  "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
  "az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"

  (add the 'en' at the end).

  However, every time some update on this file is applied, one looses the 
change,
  and we get back to the accented c. That means having to modify the file again,
  logout and login.

  For me this is no problem. But for my brother, mom, dad, etc, it is always 
something
  that at least makes me less proud of having convinced them to use Ubuntu, 
because
  they don't know what to do each time this happens.

  I think we really need a configurable keyboard layout, or at least (and that 
would
  be very easy), the inclusion of alternate layouts on install that for the 
dead-key
  options (as US-deadkey and UK-deakey), alternate layouts as 
US-deadkey-cedilla.

  This change is relevant for at least Portuguese and French.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+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 1728168] Re: integrated intel GPU doesn't work on ubuntu 17.10

2017-10-28 Thread giannione

I submitted a new bug.

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

** Tags removed: amd64 apport-bug artful performance ubuntu wayland-
session

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

Title:
  integrated intel  GPU doesn't work on ubuntu 17.10

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I've got a CPU with integrated GPU, it's the intel i5-8400; I've also
  installed an old asus [Radeon HD 6670/7670] GPU.

  If I run ubuntu connecting the monitor to the integrated GPU, after
  phisically removing the Asus Radeon card, the performance is very
  sluggish, unusable both in a wayland session and in an X session.

  If I run ubuntu without phisically removing the Asus Radeon Card
  (disabled from the bios), there is an error that prevents me from
  logging in, and that makes the TTY consoles unusable: all I get is a
  blank screen with infos about /dev/sda1

  If I use the radeon card, the performace is more or less ok.

  My question is why the integrated intel GPU doesn't work.

  OS:
  ubuntu 17.10

  graphic card:
   description: VGA compatible controller
 product: Turks XT [Radeon HD 6670/7670]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:131 memory:c000-cfff memory:dfe2-dfe3 
ioport:e000(size=256) memory:c-d

  integrated GPU, which doesn't work very well;
  intel i5-8400 cpu

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Oct 27 23:37:35 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:03f2]
  InstallationDate: Installed on 2017-10-25 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8946514c-0547-4d93-8cf6-bad6b91fa7dc ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0419
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0419:bd10/18/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1728168/+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 46226] Re: It'd be nice to have some way to overwrite /etc/gtk-2.0/gtk.immodules

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

** This bug is no longer a duplicate of bug 228077
   libgtk2 immodules has cedilla disabled in en locales
** This bug has been marked a duplicate of bug 518056
   cedilla appears as accented c (ć instead of ç) when typing 'c

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

Title:
  It'd be nice to have some way to overwrite /etc/gtk-2.0/gtk.immodules

Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  I use en_US as my locale but I hate having to use Alt-gr "," + c to
  get a cedilla, so I usually hack that file myself and add the "en"
  locale to the list under the cedilla module.

  This is not optimal because I have to do that every time a new version
  of gtk is installed, so it'd be great if I could overwrite that
  somewhere that is not touched by gtk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/46226/+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 228077] Re: libgtk2 immodules has cedilla disabled in en locales

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

** This bug has been marked a duplicate of bug 518056
   cedilla appears as accented c (ć instead of ç) when typing 'c

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

Title:
  libgtk2 immodules has cedilla disabled in en locales

Status in gnome-control-center:
  Confirmed
Status in GTK+:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gtk+2.0 package in Ubuntu:
  Invalid
Status in gnome-control-center package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: libgtk2.0-0

  philsf@philsf-laptop:~$ lsb_release -rd
  Description:  Ubuntu 8.04
  Release:  8.04

  philsf@philsf-laptop:~$ apt-cache policy libgtk2.0-0
  libgtk2.0-0:
Installed: 2.12.9-3ubuntu3

  One can't use dead keys to input a c+cedilla in en_US (probably other
  en_* locales). I had this on Gutsy. Now in Hardy, I thought I should
  report, since it's annoying, and the fix is documented.

  Steps to reproduce: 
  - enable deadkeys
  - Open gnome-terminal (or firefox) and enter ' + c 

  What you should get: ç
  What you do get: ć 

  Fix (got from http://ubuntuforums.org/showthread.php?p=3652628 ):

  
  Edit /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules, and 
include ":en" in the cedilla line

  6c6
  < "cedilla" "Cedilla" "gtk20" "/usr/share/locale" 
"az:ca:co:fr:gv:oc:pt:sq:tr:wa" 
  ---
  > "cedilla" "Cedilla" "gtk20" "/usr/share/locale" 
"az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/228077/+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 1401744] Re: PCI/internal sound card not detected no AFG or MFG node found

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  PCI/internal sound card not detected no AFG or MFG node found

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  sound output detected dummy output...i guess that resulted to no sound
  heard from speakers..

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Dec 12 11:24:51 2014
  InstallationDate: Installed on 2014-08-07 (126 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to utopic on 2014-12-03 (9 days ago)
  dmi.bios.date: 06/04/2007
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.70
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.70:bd06/04/2007:svnTOSHIBA:pnPORTEGEM500:pvrPPM51L-02100H:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE M500
  dmi.product.version: PPM51L-02100H
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1401744/+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 1042211] Re: [quantal] [regression] [i915] Corrupted display, desktop and menus don't repaint correctly using Mesa 9.0 (8.0.4 works)

** Changed in: mesa
   Status: Confirmed => Invalid

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

Title:
  [quantal] [regression] [i915] Corrupted display, desktop and menus
  don't repaint correctly using Mesa 9.0 (8.0.4 works)

Status in Compiz:
  Invalid
Status in Mesa:
  Invalid
Status in compiz package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  WORKAROUND:
  Download and install the old Mesa 8.0.4 packages for quantal from:
  https://launchpad.net/ubuntu/+source/mesa/8.0.4-1ubuntu1

  or add the Unity staging PPA:

  sudo add-apt-repository ppa:unity-team/staging

  ORIGINAL DESCRIPTION:
  After installing the latest updates on Quantal, desktop fails to repaint 
correctly:
  - moving a window leave trails
  - plain color is displayed instead of custom background
  - menus are flickering

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: compiz 1:0.9.8+bzr3319-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-12.12-generic 3.5.2
  Uname: Linux 3.5.0-12-generic i686
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Aug 27 10:38:41 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
     Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
  MachineType: ASUSTeK Computer INC. 1015PE
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-12-generic 
root=UUID=014cdf46-1d84-4e78-a68e-5d6de3419ad9 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1015PE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd05/31/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1015PE
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.
  version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu2
  version.libdrm2: libdrm2 2.4.38-0ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.1-4~ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1042211/+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 1728214] Re: Cannot adjust screen brightness after upgrading from 17.04 to 17.10

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

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

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

Title:
  Cannot adjust screen brightness after upgrading from 17.04 to 17.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  References:

  https://help.ubuntu.com/stable/ubuntu-help/display-brightness.html

  The screen is unusably bright and I cannot adjust its brightness by
  any of the following methods:

  "To change the brightness of your screen, click the system menu on the
  right side of the top bar and adjust the screen brightness slider to
  the value you want to use. The change should take effect immediately".

  "You can also adjust the screen brightness by using the Power panel".

  Prior to upgrade, the brightness controller app worked
  (https://github.com/LordAmit/Brightness).

  After the upgrade, it does not.

  Related posts are on Ubuntu stack exchange etc:

  https://askubuntu.com/questions/966557/how-do-we-turn-down-the-insane-
  brightness-on-ubuntu-17-10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 18:36:39 2017
  DistUpgraded: 2017-10-22 07:25:03,053 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 520 [8086:2063]
  InstallationDate: Installed on 2016-03-22 (585 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=306db387-b854-4d8f-8382-9727ad6ce642 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-21 (6 days ago)
  dmi.bios.vendor: Intel Corp.
  dmi.board.vendor: Intel corporation
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Oct 21 20:19:52 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.3
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1728214/+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 1721936] Re: package cups-common 2.1.3-4ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

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

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

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

Title:
  package cups-common 2.1.3-4ubuntu0.3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Every time I want to update the software

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-common 2.1.3-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Oct  7 12:25:55 2017
  Dependencies:
   
  DuplicateSignature:
   package:cups-common:2.1.3-4ubuntu0.3
   Setting up cups-server-common (2.1.3-4ubuntu0.3) ...
   dpkg: error processing package cups-common (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-10-06 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  PackageArchitecture: all
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=7edbc14a-918b-4b5a-909e-2db90e8382e7 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=7edbc14a-918b-4b5a-909e-2db90e8382e7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: cups
  Title: package cups-common 2.1.3-4ubuntu0.3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.12
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.02:bd03/14/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr058F10204910002620100:rvnHewlett-Packard:rn3577:rvr24.12:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 058F10204910002620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1721936/+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 1727269] Re: Window buttons and window edges are not rendered/designed cleanly - Ubuntu 17.10 Gnome

2017-10-28 Thread Ragnar Dunbar

The above mentioned darker window edges in 17.10 do not appear in all
windows. They appear in Firefox, Thunderbird and e.g. the Gnome Terminal
(maybe this has to do with gnome-terminal being at 2.24). The window
decorations in for example the file-manager are not affected.

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

Title:
  Window buttons and window edges are not rendered/designed cleanly -
  Ubuntu 17.10 Gnome

Status in gnome-shell package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Window buttons and window edges are not rendered/designed cleanly -
  Ubuntu 17.10 Gnome. This is really just a cosmetic issue. The window
  edges (mostly only top left) and window buttons were sharper and
  clearer in Ubuntu 16.04 und the versions before. The rough window
  egdges do not appear in all windows, it is especially obvious with
  Firfox. The impression with the buttons is always present.

  This is apparent in stock Ubuntu 17.10 on various laptops (Thinkpad
  x220, Acer Aspire 5253, Macbook Pro late 2010).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727269/+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 1560114] Re: Bitmap fonts are disabled by default

Yes, this is intentional.

See /usr/share/doc/fontconfig/README.Debian for instructions on how to enable 
bitmap fonts. I copied the instructions below.
-

If you wish to enable bitmapped fonts manually, remove the
/etc/fonts/conf.d/70-no-bitmaps.conf symbolic link and add a symlink named
70-yes-bitmaps.conf pointing to ../conf.avail/70-yes-bitmaps.conf:

  cd /etc/fonts/conf.d && \
rm -f 70-no-bitmaps.conf && \
ln -s ../conf.avail/70-yes-bitmaps.conf

** Changed in: fontconfig (Ubuntu)
   Status: New => Invalid

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

Title:
  Bitmap fonts are disabled by default

Status in fontconfig package in Ubuntu:
  Invalid

Bug description:
  By default, fontconfig-config installs a file called
  "/etc/fonts/conf.d/70-no-bitmaps.conf". It disables bitmap fonts. What
  good for, I don't know. Though if you later install a bitmap font
  "apt-get install xfonts-terminus" then that font wont show up in
  menus. That is not what you expect. The workaround is:

  sudo rm /etc/fonts/conf.d/70-no-bitmaps.conf
  sudo ln -s /etc/fonts/conf.avail/70-yes-bitmaps.conf 
/etc/fonts/conf.d/70-yes-bitmaps.conf

  But you shouldn't need that and bitmap founds shouldn't be disabled.

  The bug is present in Ubuntu wily, 15.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1560114/+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 1192175] Re: Use of mode="assign" in default configuration

Thank you for taking the time to report this bug! This bug will be fixed
in Ubuntu 18.04 LTS.

** Changed in: fontconfig (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Use of mode="assign" in default configuration

Status in fontconfig package in Ubuntu:
  Fix Committed

Bug description:
  The additional .conf files that Ubuntu's patches create in conf.avail/ use 
mode="assign" to set preferences.
  But in this upstream bug report:
  https://bugs.freedesktop.org/show_bug.cgi?id=17722
  it's said that the default configurations should use mode="append", and the 
use of "assign" should be limited to user configuration. The original 
fontconfig .conf files in Ubuntu already use "append", as correction of this 
bug.

  Ubuntu versions that present this bug: all.
  fontconfig versions that present this bug: all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1192175/+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 1702544] Re: Merge fontconfig 2.12.3-0.1 (main) from Debian unstable (main)

** Tags added: bionic upgrade-software-version

** Changed in: fontconfig (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: fontconfig (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Merge fontconfig 2.12.3-0.1 (main) from Debian unstable (main)

Status in fontconfig package in Ubuntu:
  Fix Committed

Bug description:
  Please merge fontconfig 2.12.3-0.1 (main) from Debian unstable (main)

  I cannot work on this merge myself. I am reporting this for reference.

  Explanation of the Ubuntu delta:
* SECURITY UPDATE: double free when handling cache files
  - debian/patches/CVE-2016-5384.patch: properly validate offsets in
cache files in src/fccache.c.
  - CVE-2016-5384
* New upstream release (LP: #1556457)
  - Fixes blurry fonts regression from previous upload (LP: #1566651)
* d/p/0001-Revert-Bug-73291-poppler-does-not-show-fl-ligature.patch,
  d/p/0002-demilight.patch:
  - Dropped, applied in new release
* Bump freetype build dep to 2.5.1 as per configure.ac.
* Drop gperf build dep again, not necessary any more.
* debian/control:
  - Add gperf to build dependencies
  - Bump FreeType build dependency version to 2.5.1
[ Mingye Wang ]
* debian/patches/0002-demilight.patch:
  - Handle Demilight sensibly (LP: #1556457)
* Make things depend on ≥ version-of-libfontconfig1-they-were-built-with, so
  that on new releases the library is upgraded before its rdeps. (LP:
  #1540591)
* debian/source_fontconfig.py:
  - include fontconfig.log in the bug reports to try to get more info
on some of the xenial upgrade issues
* 0001-Revert-Bug-73291-poppler-does-not-show-fl-ligature.patch: Now poppler
  is fixed, revert the alias of TeX Gyre Termes to Times. (LP: #1379375)
* Merge changes from Debian 2.11.0-6.1 and 2.11.0-6.2:
[ Don Armstrong ]
* Switch to noawait triggers to allow self-triggering; will still need
  Breaks from dpkg to resolve this (closes: #768599)
* Add Pre-Depends on dpkg to allow for noawait just in case this gets
  backported to squeeze.
[ Andreas Barth ]
* Add dh-autoreconf to support ppc64el. Closes: #748378
* No change rebuild to get debug symbols on all architectures.
* Merge from Debian 2.11.0-2:
  - 03_locale_c.utf8.patch: based on a patch from Martin Dickopp. Treat
C.UTF-8 and C.utf8 locales as built in the C library.
Closes: #717423.
* Merge from Debian 2.11.0-2:
  - 03_locale_c.utf8.patch: based on a patch from Martin Dickopp. Treat
C.UTF-8 and C.utf8 locales as built in the C library.
Closes: #717423.
* Make libfontconfig1-dev Multi-Arch: same.
* New upstream release
* Pass --enable-static to continue building the static library since the
  default changed in this release.
* 0001-Bug-73291-poppler-does-not-show-fl-ligature.patch: Drop, applied
  upstream in this release.
* 0001-Bug-73291-poppler-does-not-show-fl-ligature.patch: Don't alias TeX
  Gyre Termes to Times as it has a broken 'fi' ligature. (LP: #1325230)
* debian/rules:
  - don't add /usr/X11R6/lib/X11/fonts to the fonts path, that's a
deprecated location and it leads to polling on the directory,
which means wakeups and extra power usage (lp: #1266873)
* Build using dh-autoreconf.
* Update font dependencies (ttf-dejavu-core -> fonts-dejavu-core and
  ttf-freefont -> fonts-freefont-ttf).
* New upstream version
* Refresh debian patches
* git_obtain_fonts_via_FT-face.patch:
  - dropped, included in the new version
* debian/patches/series: list the patch from the previous revision...
  (lp: #1177995)
* New upstream version
* Refreshed patches
* debian/patches/git_obtain_fonts_via_FT-face.patch
  - cherrypick patch from git to fix webfonts (LP: #1177995) (Thanks Tim)
* Remove versioned build dependency on binutils.
* New upstream version:
  - includes the typo fixes for lp: #1037509
* Fix fontconfig-config postinst to ignore rmdir failures when removing
  /var/lib/defoma/fontconfig.d/ as some systems have files in there.
  (LP: #1039828)
* debian/control: build-depends on pkg-config
* Cherry pick from Debian experimental: Remove defoma support.
  Closes: #651493.
* Drop 08_ug_us_orth.patch again, as per Eagle Burkut. (Locale was renamed
  to ug_CN@latin).
* Add 08_ug_us_orth.patch: Add ug_US orthography.
* Add 00git_ughur_orthography.patch: Complete Uighur orthography. Patch
  taken from upstream git head. (LP: #736413)
* debian/patches/01_fonts_nanum.patch: Fix typo, thanks Felix Geyer for
  spotting!
* debian/patches/01_fonts_nanum.patch
  - Restore Baekmuk fonts because it's

[Touch-packages] [Bug 210921] Re: Fontconfig should default to full hinting

fontconfig defaults to slight hinting both in Ubuntu and upstream. This
seems to produce the best results for the most people.

** Changed in: fontconfig (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 fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/210921

Title:
  Fontconfig should default to full hinting

Status in One Hundred Papercuts:
  Invalid
Status in fontconfig package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: fontconfig

  
  dpkg -S /etc/fonts/conf.avail/10-hinting-medium.conf 
  fontconfig-config: /etc/fonts/conf.avail/10-hinting-medium.conf

  Ubuntu Hardy has the following symlink by default:
  lrwxrwxrwx 1 root root  34 2008-04-02 19:17 10-hinting-medium.conf -> 
../conf.avail/10-hinting-medium.conf

  This really should (instead) be:
  lrwxrwxrwx 1 root root  34 2008-04-02 19:17 10-hinting-full.conf -> 
../conf.avail/10-hinting-full.conf

  This default is causing issue like this:
  https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/190848

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/210921/+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 293643] Re: font settings in .fonts.conf ignored

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

Reassigning to cairo per comment #6

** Package changed: fontconfig (Ubuntu) => cairo (Ubuntu)

** Changed in: cairo (Ubuntu)
   Status: Incomplete => Triaged

** Also affects: cairo via
   https://bugs.freedesktop.org/show_bug.cgi?id=11838
   Importance: Unknown
   Status: Unknown

** This bug has been marked a duplicate of bug 161058
   some ~/.fonts.conf settings do no override desktop-wide gnome settings 
(hinting style)

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

Title:
  font settings in .fonts.conf ignored

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: fontconfig

  The following doesn't work unless I use;

  true

  What I thought should work;

  
  
  Consolas
  
  
  hintslight
  
  

  What actually works;

  
  
  Consolas
  
  rgb
  true
  true
  true
  hintslight
  http://forums.fedoraforum.org/showthread.php?t=186789&page=7 for more 
information and my old .fonts.conf; http://pastebin.com/m1b3fbe51 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/293643/+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 1638959] Re: Update to 2.12.3

** Project changed: inkscape-devlibs64 => freetype (Ubuntu)

** No longer affects: freetype (Ubuntu)

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

Title:
  Update to 2.12.3

Status in fontconfig package in Ubuntu:
  Fix Committed

Bug description:
  Debian unstable now has 2.12.3. Please consider merging.
  

  Current 16.04+ releases uses fc 2.11.94 (2.12 RC4) for an early fix for bug 
#1556457. It sounds saner to move to 2.12.1, a non-RC release which contains 
some Unicode table updates, memory leak fixes, and the original fix for 
CVE-2016-5384, for the next Ubuntu release. The ABI appears unchanged since 
2.11.94.
  ---

  README (with ChangeLog): https://cgit.freedesktop.org/fontconfig/tree/README
  ABI diff: https://abi-laboratory.pro/tracker/timeline/fontconfig/

  2.12.3

  Akira TAGOH (1):
Fix make check fail with freetype-2.7.1 and 2.8 with 
PCF_CONFIG_OPTION_LONG_FAMILY_NAMES enabled.

  2.12.2

  Akira TAGOH (8):
Don't call perror() if no changes happens in errno
Fix FcCacheOffsetsValid()
Fix the build issue with gperf 3.1
Fix the build issue on GNU/Hurd
Update a bit for the changes in FreeType 2.7.1
Add the description of FC_LANG envvar to the doc
Bug 101202 - fontconfig FTBFS if docbook-utils is installed
Update libtool revision

  Alan Coopersmith (1):
Correct cache version info in doc/fontconfig-user.sgml

  Khem Raj (1):
Avoid conflicts with integer width macros from TS 18661-1:2014

  Masamichi Hosoda (2):
Fix PostScript font alias name
Update aliases for URW June 2016

  2.12.1

  Akira TAGOH (6):
Add --with-default-hinting to configure
Update CaseFolding.txt to Unicode 9.0
Check python installed in autogen.sh
Fix some errors related to python3
Bug 96676 - Check range of FcWeightFromOpenType argument
Update libtool revision

  Tobias Stoeckmann (1):
Properly validate offsets in cache files.

  2.12

  Akira TAGOH (8):
Modernize fc-blanks.py
Update URL
Bug 95477 - FcAtomicLock fails when SELinux denies link() syscall with 
EACCES
45-latin.conf: Add some Windows fonts to categorize them properly
Correct one for the previous change
Bug 95481 - Build fails on Android due to broken lconv struct
Add the static raw data to generate fcblanks.h
Remove unused code

  Erik de Castro Lopo (1):
Fix a couple of minor memory leaks

  Petr Filipsky (1):
Fix memory leak in FcDirCacheLock

  2.11.95 (2.12 RC5)

  Akira TAGOH (22):
Add one more debugging option to see transformation on font-matching
Fix a crash when no objects are available after filtering
No need to be public
mark as private at this moment
Don't return FcFalse even when no fonts dirs is configured
Add a warning for blank in fonts.conf
Fix a memory leak in FcFreeTypeQueryFace
Update CaseFolding.txt to Unicode 8.0
Bug 90867 - Memory Leak during error case in fccharset
Fix the broken cache more.
Fail on make runtime as needed instead of configure if no python 
installed
Use long long to see the same size between LP64 and LLP64
Fix build issue on MinGW
Use int64_t instead of long long
Fix compiler warnings on MinGW
Fix assertion on 32bit arch
remomve unnecessary code
Bug 93075 - Possible fix for make check failure on msys/MinGW...
Avoid an error message on testing when no fonts.conf installed
Add hintstyle templates and make hintslight default
Revert "Workaround another race condition issue"
Update libtool revision

  Behdad Esfahbod (6):
Revert changes made to FcConfigAppFontAddDir() recently
Call FcFreeTypeQueryFace() from fcdir.c, instead of FcFreeTypeQuery()
[GX] Support instance weight, width, and style name
[GX] Enumerate all named-instances in TrueType GX fonts
Improve OpenType to Fontconfig weight mapping
[GX] Improve weight mapping

  Patrick Haller (1):
Optimizations in FcStrSet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1638959/+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 1638959] Re: Update to 2.12.3

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

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

Title:
  Update to 2.12.3

Status in fontconfig package in Ubuntu:
  Fix Committed

Bug description:
  Debian unstable now has 2.12.3. Please consider merging.
  

  Current 16.04+ releases uses fc 2.11.94 (2.12 RC4) for an early fix for bug 
#1556457. It sounds saner to move to 2.12.1, a non-RC release which contains 
some Unicode table updates, memory leak fixes, and the original fix for 
CVE-2016-5384, for the next Ubuntu release. The ABI appears unchanged since 
2.11.94.
  ---

  README (with ChangeLog): https://cgit.freedesktop.org/fontconfig/tree/README
  ABI diff: https://abi-laboratory.pro/tracker/timeline/fontconfig/

  2.12.3

  Akira TAGOH (1):
Fix make check fail with freetype-2.7.1 and 2.8 with 
PCF_CONFIG_OPTION_LONG_FAMILY_NAMES enabled.

  2.12.2

  Akira TAGOH (8):
Don't call perror() if no changes happens in errno
Fix FcCacheOffsetsValid()
Fix the build issue with gperf 3.1
Fix the build issue on GNU/Hurd
Update a bit for the changes in FreeType 2.7.1
Add the description of FC_LANG envvar to the doc
Bug 101202 - fontconfig FTBFS if docbook-utils is installed
Update libtool revision

  Alan Coopersmith (1):
Correct cache version info in doc/fontconfig-user.sgml

  Khem Raj (1):
Avoid conflicts with integer width macros from TS 18661-1:2014

  Masamichi Hosoda (2):
Fix PostScript font alias name
Update aliases for URW June 2016

  2.12.1

  Akira TAGOH (6):
Add --with-default-hinting to configure
Update CaseFolding.txt to Unicode 9.0
Check python installed in autogen.sh
Fix some errors related to python3
Bug 96676 - Check range of FcWeightFromOpenType argument
Update libtool revision

  Tobias Stoeckmann (1):
Properly validate offsets in cache files.

  2.12

  Akira TAGOH (8):
Modernize fc-blanks.py
Update URL
Bug 95477 - FcAtomicLock fails when SELinux denies link() syscall with 
EACCES
45-latin.conf: Add some Windows fonts to categorize them properly
Correct one for the previous change
Bug 95481 - Build fails on Android due to broken lconv struct
Add the static raw data to generate fcblanks.h
Remove unused code

  Erik de Castro Lopo (1):
Fix a couple of minor memory leaks

  Petr Filipsky (1):
Fix memory leak in FcDirCacheLock

  2.11.95 (2.12 RC5)

  Akira TAGOH (22):
Add one more debugging option to see transformation on font-matching
Fix a crash when no objects are available after filtering
No need to be public
mark as private at this moment
Don't return FcFalse even when no fonts dirs is configured
Add a warning for blank in fonts.conf
Fix a memory leak in FcFreeTypeQueryFace
Update CaseFolding.txt to Unicode 8.0
Bug 90867 - Memory Leak during error case in fccharset
Fix the broken cache more.
Fail on make runtime as needed instead of configure if no python 
installed
Use long long to see the same size between LP64 and LLP64
Fix build issue on MinGW
Use int64_t instead of long long
Fix compiler warnings on MinGW
Fix assertion on 32bit arch
remomve unnecessary code
Bug 93075 - Possible fix for make check failure on msys/MinGW...
Avoid an error message on testing when no fonts.conf installed
Add hintstyle templates and make hintslight default
Revert "Workaround another race condition issue"
Update libtool revision

  Behdad Esfahbod (6):
Revert changes made to FcConfigAppFontAddDir() recently
Call FcFreeTypeQueryFace() from fcdir.c, instead of FcFreeTypeQuery()
[GX] Support instance weight, width, and style name
[GX] Enumerate all named-instances in TrueType GX fonts
Improve OpenType to Fontconfig weight mapping
[GX] Improve weight mapping

  Patrick Haller (1):
Optimizations in FcStrSet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1638959/+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 1638959] Re: Update to 2.12.3

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

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

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

Title:
  Update to 2.12.3

Status in fontconfig package in Ubuntu:
  Fix Committed

Bug description:
  Debian unstable now has 2.12.3. Please consider merging.
  

  Current 16.04+ releases uses fc 2.11.94 (2.12 RC4) for an early fix for bug 
#1556457. It sounds saner to move to 2.12.1, a non-RC release which contains 
some Unicode table updates, memory leak fixes, and the original fix for 
CVE-2016-5384, for the next Ubuntu release. The ABI appears unchanged since 
2.11.94.
  ---

  README (with ChangeLog): https://cgit.freedesktop.org/fontconfig/tree/README
  ABI diff: https://abi-laboratory.pro/tracker/timeline/fontconfig/

  2.12.3

  Akira TAGOH (1):
Fix make check fail with freetype-2.7.1 and 2.8 with 
PCF_CONFIG_OPTION_LONG_FAMILY_NAMES enabled.

  2.12.2

  Akira TAGOH (8):
Don't call perror() if no changes happens in errno
Fix FcCacheOffsetsValid()
Fix the build issue with gperf 3.1
Fix the build issue on GNU/Hurd
Update a bit for the changes in FreeType 2.7.1
Add the description of FC_LANG envvar to the doc
Bug 101202 - fontconfig FTBFS if docbook-utils is installed
Update libtool revision

  Alan Coopersmith (1):
Correct cache version info in doc/fontconfig-user.sgml

  Khem Raj (1):
Avoid conflicts with integer width macros from TS 18661-1:2014

  Masamichi Hosoda (2):
Fix PostScript font alias name
Update aliases for URW June 2016

  2.12.1

  Akira TAGOH (6):
Add --with-default-hinting to configure
Update CaseFolding.txt to Unicode 9.0
Check python installed in autogen.sh
Fix some errors related to python3
Bug 96676 - Check range of FcWeightFromOpenType argument
Update libtool revision

  Tobias Stoeckmann (1):
Properly validate offsets in cache files.

  2.12

  Akira TAGOH (8):
Modernize fc-blanks.py
Update URL
Bug 95477 - FcAtomicLock fails when SELinux denies link() syscall with 
EACCES
45-latin.conf: Add some Windows fonts to categorize them properly
Correct one for the previous change
Bug 95481 - Build fails on Android due to broken lconv struct
Add the static raw data to generate fcblanks.h
Remove unused code

  Erik de Castro Lopo (1):
Fix a couple of minor memory leaks

  Petr Filipsky (1):
Fix memory leak in FcDirCacheLock

  2.11.95 (2.12 RC5)

  Akira TAGOH (22):
Add one more debugging option to see transformation on font-matching
Fix a crash when no objects are available after filtering
No need to be public
mark as private at this moment
Don't return FcFalse even when no fonts dirs is configured
Add a warning for blank in fonts.conf
Fix a memory leak in FcFreeTypeQueryFace
Update CaseFolding.txt to Unicode 8.0
Bug 90867 - Memory Leak during error case in fccharset
Fix the broken cache more.
Fail on make runtime as needed instead of configure if no python 
installed
Use long long to see the same size between LP64 and LLP64
Fix build issue on MinGW
Use int64_t instead of long long
Fix compiler warnings on MinGW
Fix assertion on 32bit arch
remomve unnecessary code
Bug 93075 - Possible fix for make check failure on msys/MinGW...
Avoid an error message on testing when no fonts.conf installed
Add hintstyle templates and make hintslight default
Revert "Workaround another race condition issue"
Update libtool revision

  Behdad Esfahbod (6):
Revert changes made to FcConfigAppFontAddDir() recently
Call FcFreeTypeQueryFace() from fcdir.c, instead of FcFreeTypeQuery()
[GX] Support instance weight, width, and style name
[GX] Enumerate all named-instances in TrueType GX fonts
Improve OpenType to Fontconfig weight mapping
[GX] Improve weight mapping

  Patrick Haller (1):
Optimizations in FcStrSet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1638959/+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 1700319] Re: GTK3 menus don't work over SSH forwarding

** Changed in: gtk
   Status: Confirmed => Fix Released

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

Title:
  GTK3 menus don't work over SSH forwarding

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  When connecting remotely (either SSH X11 forwarding or direct to X11
  server), drop down menus do not display properly.

  Bug upstream in gtk3:
  https://bugzilla.gnome.org/show_bug.cgi?id=780101

  Client: Ubuntu 17.04 - gtk3-3.22.11-0ubuntu3
  Server: Windows 10 Cygwin/X 1.19.2-1

  Programs exhibiting this problem:
  evince 3.24.0 (and any other gtk3 apps with menus along the top).

  Patch applied to gtk3 in cygwin to fix this problem and attached to this post:
  https://github.com/cygwinports/gtk3/blob/master/3.22.10-xrandr12-compat.patch

  Console errors:

  (evince:7390): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner:
  assertion 'G_IS_DBUS_PROXY (proxy)' failed

  (evince:7390): GLib-WARNING **: GError set over the top of a previous GError 
or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: The name org.freedesktop.portal.Desktop is 
not owned

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: 
assertion 'width >= 0' failed
  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  
  (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, 
extents 4x4) while allocating gadget (node arrow, owner GtkMenu)

  (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, 
extents 4x4) while allocating gadget (node arrow, owner GtkMenu)
  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  
  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1, 
extents 6x6) while allocating gadget (node menuitem, owner GtkModelMenuItem)

  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation
  1, extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)

  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation
  1, extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1700319/+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 1728259] [NEW] Update ubuntu specific applications gui with gnome3/gtk3 concept

2017-10-28 Thread Ahmet Aksoy

Public bug reported:

update-manager, software-properties-gtk, gnome-language-selector, 
usb-creator-gtk... 
These applications looks like gtk2 applications. I think these apps interfaces 
need to be refreshed with Gnome3/GTK3 concept

** Affects: language-selector (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: usb-creator (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: language-selector (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: usb-creator (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubiquity (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Update ubuntu specific applications gui with gnome3/gtk3 concept

Status in language-selector package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in usb-creator package in Ubuntu:
  New

Bug description:
  update-manager, software-properties-gtk, gnome-language-selector, 
usb-creator-gtk... 
  These applications looks like gtk2 applications. I think these apps 
interfaces need to be refreshed with Gnome3/GTK3 concept

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1728259/+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 1728253] [NEW] package dictionaries-common 1.27.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-10-28 Thread Daniel Formhals

Public bug reported:

freezing on upgrade clock ,processes  etc...

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: dictionaries-common 1.27.2
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: i386
Date: Sat Oct 28 10:33:01 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
InstallationDate: Installed on 2017-10-28 (0 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170829.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: dictionaries-common
Title: package dictionaries-common 1.27.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dictionaries-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package artful i386

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

Title:
  package dictionaries-common 1.27.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in dictionaries-common package in Ubuntu:
  New

Bug description:
  freezing on upgrade clock ,processes  etc...

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: dictionaries-common 1.27.2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  Date: Sat Oct 28 10:33:01 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-10-28 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170829.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: dictionaries-common
  Title: package dictionaries-common 1.27.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1728253/+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 1710754] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

2017-10-28 Thread Scott Palmer

This was fixed for a while by an update that came in, but now this
problem has come back.

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710754/+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 1727243] Re: pam_systemd

2017-10-28 Thread latimerio

Upon investigating further I now suspect it is systemd-logind which causes the 
problem.
As can be seen in auth.log, the system-logind tries to start a new session 
every second for an unknown reason.
In /var/log/syslog I see corresponding messages like this:
Oct 27 07:42:39 h2... systemd[19421]: Startup finished in 5ms.
Oct 27 07:42:39 h2... systemd[19421]: Stopped target Default.
Oct 27 07:42:39 h2... systemd[19421]: Stopped target Basic System.
Oct 27 07:42:39 h2... systemd[19421]: Stopped target Timers.
Oct 27 07:42:39 h2... systemd[19421]: Stopped target Sockets.
Oct 27 07:42:39 h2... systemd[19421]: Reached target Shutdown.
Oct 27 07:42:39 h2... systemd[19421]: Starting Exit the Session...
Oct 27 07:42:39 h2... systemd[19421]: Stopped target Paths.
Oct 27 07:42:39 h2... systemd[19421]: Received SIGRTMIN+24 from PID 19447 
(kill).
Oct 27 07:42:40 h2... systemd[19468]: Reached target Paths.
Oct 27 07:42:40 h2... systemd[19468]: Reached target Timers.
Oct 27 07:42:40 h2... systemd[19468]: Reached target Sockets.
Oct 27 07:42:40 h2... systemd[19468]: Reached target Basic System.
Oct 27 07:42:40 h2... systemd[19468]: Reached target Default.
Oct 27 07:42:40 h2... systemd[19468]: Startup finished in 6ms.


** Summary changed:

- pam_systemd
+ systemd-logind

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

Title:
  systemd-logind

Status in systemd package in Ubuntu:
  New

Bug description:
  my auth.log is full of messages like below.
  The 79.247.. is my own address and there seems to be something which tries to 
reconnect every other second although I am already in a running session.
  What is going on here?

  Oct 25 10:38:57 h... sshd[6506]: Accepted publickey for root from 79.247... 
port 52067 ssh2: RSA SHA256:pru...
  Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session opened for 
user root by (uid=0)
  Oct 25 10:38:57 h... systemd-logind[285]: New session 2373897 of user root.
  Oct 25 10:38:57 h... sshd[6506]: pam_systemd(sshd:session): Cannot create 
session: Already running in a session
  Oct 25 10:38:57 h... sshd[6506]: Received disconnect from 79.247... port 
52067:11: disconnected by user
  Oct 25 10:38:57 h... sshd[6506]: Disconnected from 79.247... port 52067
  Oct 25 10:38:57 h... sshd[6506]: pam_unix(sshd:session): session closed for 
user root
  Oct 25 10:38:57 h... systemd-logind[285]: Removed session 2373897.
  Oct 25 10:38:59 h... sshd[6524]: Accepted publickey for root from 79.247... 
port 52068 ssh2: RSA SHA256:pru...
  Oct 25 10:38:59 h... sshd[6524]: pam_unix(sshd:session): session opened for 
user root by (uid=0)
  Oct 25 10:38:59 h... systemd-logind[285]: New session 2373898 of user root.
  Oct 25 10:38:59 h... sshd[6524]: pam_systemd(sshd:session): Cannot create 
session: Already running in a session
  Oct 25 10:38:59 h... sshd[6524]: Received disconnect from 79.247... port 
52068:11: disconnected by user
  Oct 25 10:38:59 h... sshd[6524]: Disconnected from 79.247... port 52068
  Oct 25 10:38:59 h... sshd[6524]: pam_unix(sshd:session): session closed for 
user root
  Oct 25 10:38:59 h... systemd-logind[285]: Removed session 2373898.
  Oct 25 10:39:01 h... CRON[6565]: pam_unix(cron:session): session opened for 
user root by (uid=0)
  Oct 25 10:39:01 h... CRON[6564]: pam_unix(cron:session): session opened for 
user root by (uid=0)
  Oct 25 10:39:01 h... sshd[6562]: Accepted publickey for root from 79.247... 
port 52069 ssh2: RSA SHA256:pru...
  Oct 25 10:39:01 h... sshd[6562]: pam_unix(sshd:session): session opened for 
user root by (uid=0)
  Oct 25 10:39:01 h... systemd-logind[285]: New session 2373904 of user root.
  Oct 25 10:39:01 h... sshd[6562]: pam_systemd(sshd:session): Cannot create 
session: Already running in a session
  Oct 25 10:39:01 h... sshd[6562]: Received disconnect from 79.247... port 
52069:11: disconnected by user
  Oct 25 10:39:01 h... sshd[6562]: Disconnected from 79.247... port 52069
  Oct 25 10:39:01 h... sshd[6562]: pam_unix(sshd:session): session closed for 
user root
  Oct 25 10:39:01 h... systemd-logind[285]: Removed session 2373904.
  Oct 25 10:39:01 h... CRON[6565]: pam_unix(cron:session): session closed for 
user root
  Oct 25 10:39:02 h... sshd[6665]: Accepted publickey for root from 79.247... 
port 52070 ssh2: RSA SHA256:pru...
  Oct 25 10:39:02 h... sshd[6665]: pam_unix(sshd:session): session opened for 
user root by (uid=0)
  Oct 25 10:39:02 h... systemd-logind[285]: New session 2373945 of user root.
  Oct 25 10:39:03 h... sshd[6665]: pam_systemd(sshd:session): Cannot create 
session: Already running in a session
  Oct 25 10:39:03 h... sshd[6665]: Received disconnect from 79.247... port 
52070:11: disconnected by user
  Oct 25 10:39:03 h... sshd[6665]: Disconnected from 79.247... port 52070
  Oct 25 10:39:03 h... sshd[6665]: pam_unix(sshd:session): session closed for 
user root
  Oct 25 10:39:03 h... sy

[Touch-packages] [Bug 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks

2017-10-28 Thread Ragnar Dunbar

The problem persists in 16.04.3

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

Title:
  network-manager after suspend showing arrow icon instead of wifi icon
  and showing no wifi networks

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401
  I'm creating my own bug report.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy network-manager
  network-manager:
Installiert:   1.2.2-0ubuntu0.16.04.3
Installationskandidat: 1.2.2-0ubuntu0.16.04.3
Versionstabelle:
   *** 1.2.2-0ubuntu0.16.04.3 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) What you expected to happen
  I'm connected by WiFi only, not by a wired connection. I expect to see the 
WiFi icon anytime while being connected to my WiFi network. Also, I expect to 
see all the WiFi networks around me (at least one other network with good 
reception and about 3 with bad reception).

  4) What happened instead
  After waking up the laptop from suspend, there appears the ethernet icon 
(arrow symbols) instead of the WiFi icon.
  Also, in this state there are no other WiFi networks visible in the 
network-manager.
  However, the laptop is still connected with my WiFi and the connection works 
as usual.
  Using "service network-manager restart" in the console I can get the wireless 
icon back and all the other networks around me are visible again.
  This can be reproduced anytime and with 100% "success rate". The problem 
appeared with Ubuntu 16.10 and was persistent since.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 24 20:06:09 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-15 (161 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlo1  proto static  metric 600 
   169.254.0.0/16 dev wlo1  scope link  metric 1000 
   192.168.1.0/24 dev wlo1  proto kernel  scope link  src 192.168.1.244  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlo1wifi  connected/org/freedesktop/NetworkManager/Devices/2  
WiNet 2 162de978-4466-46b0-957b-5f9c141d702a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eno1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636282/+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 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

** Description changed:

  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All files
  exist.  I've also verified the Kabylake GuC firmware matches the correct
  file size and md5 listed on 01.org.
  
  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.
  
- I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10.  Perhaps
- Broxton systems might have the same issue?
+ I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
+ initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
+ same issue?
  
  Output and logs:
  -
  
  ls -al /lib/firmware/i915/kbl_*
  
  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin
  
  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status
  
  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0
  
  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0
  
  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0
  
  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status
  
  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256
  
  HuC status 0x6000:
  
  dmesg
  
  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.695657] usb 1-2: Product: USB Receiver
  [1.695658] usb 1-2: Manufacturer: Logitech
  [1.702641] logitech-djreceiver 0003:046D:C52B.0005: hiddev0,hidraw2: USB 
HID v1.11 Device [Logitech USB Receiver] on usb-:00:14.0-2/input2
  [1.820317] usb 1-3: new full-speed USB device number 4 using xhci_hcd
  [1.835948] input: Logitech M510 as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.2/0003:046D:C52B.0005/0003:046D:4051.0006/input/input9
  [1.836129] logite

[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

** Tags added: broxton kabylake

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

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10.  Perhaps
  Broxton systems might have the same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.695657] usb 1-2: Product: USB Receiver
  [1.695658] usb 1-2: Manufacturer: Logitech
  [1.702641] logitech-djreceiver 0003:046D:C52B.0005: hiddev0,hidraw2: USB 
HID v1.11 Device [Logitech USB Receiver] on usb-:00:14.0-2/input2
  [1.820317] usb 1-3: new full-speed USB device number 4 using xhci_hcd
  [

[Touch-packages] [Bug 1728245] [NEW] [software-properties-gtk] Cannot enable/disable PPAs - checkmark button non-responsive

2017-10-28 Thread The Bright Side

Public bug reported:

Steps to Reproduce:
1. Launch software-properties-gtk on Ubuntu 17.10 (Xorg)
2. Select "Other Software" tab
3. Click on checkmark to the left of any PPA (e.g. Ubuntu Partners)

Current Behaviour:
When clicking the checkmark to enable or disable a PPA, the window becomes 
inactive (greyed out). Clicking on the title bar bring the window back into 
focus.

Expected Behaviour:
A password prompt should pop up. Then, the PPA should be enabled/disabled when 
clicking the button.

Repro Rate: 90%
In 17.04, after a while, this started working on its own.
In 17.10, it won't work.

Notes:
>From my memory, this has been happening at least since Ubuntu GNOME 17.04, and 
>is happening in 17.10.
Workaround: gksu software-properties-gtk does the trick.
It seems the issue is that software-properties-gtk doesn't trigger the password 
prompt.

See the bug in action:
https://youtu.be/ke6ZR6aKrQ0

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [software-properties-gtk] Cannot enable/disable PPAs - checkmark
  button non-responsive

Status in software-properties package in Ubuntu:
  New

Bug description:
  Steps to Reproduce:
  1. Launch software-properties-gtk on Ubuntu 17.10 (Xorg)
  2. Select "Other Software" tab
  3. Click on checkmark to the left of any PPA (e.g. Ubuntu Partners)

  Current Behaviour:
  When clicking the checkmark to enable or disable a PPA, the window becomes 
inactive (greyed out). Clicking on the title bar bring the window back into 
focus.

  Expected Behaviour:
  A password prompt should pop up. Then, the PPA should be enabled/disabled 
when clicking the button.

  Repro Rate: 90%
  In 17.04, after a while, this started working on its own.
  In 17.10, it won't work.

  Notes:
  From my memory, this has been happening at least since Ubuntu GNOME 17.04, 
and is happening in 17.10.
  Workaround: gksu software-properties-gtk does the trick.
  It seems the issue is that software-properties-gtk doesn't trigger the 
password prompt.

  See the bug in action:
  https://youtu.be/ke6ZR6aKrQ0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1728245/+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 1719612] Re: non-us keyboard layout not setup in initramfs

2017-10-28 Thread Romain Fluttaz

Thanks !
So quick solve :

Open a terminal [Ctrl]+[Maj]+[t]

sudo ln -s /etc/console-setup/cached_UTF-8_del.kmap.gz 
/etc/console-setup/cached.kmap.gz
sudo update-initramfs -u

So now we can come back to a complex encryption disk password without to
have to find/guess the us correspondence !

I just remember, but in the installer, the keyboard setup is after we
choose disk encryption password. So some people who didn't know this bug
and that their keyboard where in English keyboard layout, they might not
really now their real password ! Fun !

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

Title:
  non-us keyboard layout not setup in initramfs

Status in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Artful Aardvark (development branch)
  Release:17.10

  In Artful the /etc/console/cached.kmap.gz file does not exists, in its place, 
it uses some files with more precise names susch as cached_UTF-8_del.kmap.gz. 
However the initramfs scripts still uses cached.kmap.gz . The consequence is 
that the keyboard layout remains US in the initramfs which is a problem for 
full encrypted installation when entering passphrase.
  Proposed solution is to make a symbolic link from  cached_UTF-8_del.kmap.gz 
to cached.kmap.gz. Then the initramfs tools will find the 
/etc/console/cached.kmap.gz file and includes it in the initramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1719612/+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 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

** Summary changed:

- initramfs not adding i915 GuC firmware, firmware fails to load
+ update-initramfs not adding i915 GuC firmware, firmware fails to load

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

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10.  Perhaps
  Broxton systems might have the same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.695657] usb 1-2: Product: USB Receiver
  [1.695658] usb 1-2: Manufacturer: Logitech
  [1.702641] logitech-djreceiver 0003:046D:C52B.0005: hiddev0,hidraw2: USB 
HID v1.11 Device [Logit

[Touch-packages] [Bug 1728238] Re: initramfs not adding i915 GuC firmware, firmware fails to load

** Description changed:

  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All files
  exist.  I've also verified the Kabylake GuC firmware matches the correct
  file size and md5 listed on 01.org.
  
  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.
  
+ I'm running a Dell XPS 13 9360 w/ Kabylake.  Perhaps Broxton systems
+ might have the same issue?
+ 
  Output and logs:
  -
-  
+ 
  ls -al /lib/firmware/i915/kbl_*
-  
+ 
  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin
  
  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status
-  
+ 
  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0
-  
+ 
  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0
-  
+ 
  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0
-  
+ 
  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status
-  
+ 
  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256
-  
+ 
  HuC status 0x6000:
-  
+ 
  dmesg
-  
+ 
  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
  [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
  [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.695657] usb 1-2: Product: USB Receiver
  [1.695658] usb 1-2: Manufacturer: Logitech
  [1.702641] logitech-djreceiver 0003:046D:C52B.0005: hiddev0,hidraw2: USB 
HID v1.11 Device [Logitech USB Receiver] on usb-:00:14.0-2/input2
  [1.820317] usb 1-3: new full-speed USB device number 4 using xhci_hcd
  [1.835948] input: Logitech M510 as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.2/0003:046D:C52B.0005/0003:046D:4051.0006/input/input9
  [1.836129] logitech-hidpp-device 0003:046D:4051.0006: input,hidraw3: USB 
HID v1.11 Mouse [Logitech M510] on usb-:00:14.0-2:1
  [1.838085

[Touch-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop

2017-10-28 Thread Rudi Daemen

I have a very useful update on the Skylake/nvidia GTX1060 case where the
HDMI Audio device does not show up in lspci. Based on information found
on the NVidia Developer forum, I was able to get my HDMI audio device
show up in Ubuntu 17.10 as per my posting there:

https://devtalk.nvidia.com/default/topic/1024022/linux/gtx-1060-no-
audio-over-hdmi-only-hda-intel-detected-azalia/post/5216905/#5216905

Crossposting the information here so affected people can try this as
well:

Create the file "/etc/systemd/system/fix-hdmi-audio.service" as per below:
[Unit]
Description=nVidia HDMI Audio Fixer
Before=systemd-logind.service display-manager.service
After=module-init-tools.service

[Service]
Type=oneshot
ExecStart=/root/fix-hdmi-audio.sh

[Install]
WantedBy=multi-user.target


Create the file "/root/fix-hdmi-audio.sh" as per below (Note, adjust the PCI 
device paths to the PCI ID of the PCIe Bride and NVidia card):

#!/bin/sh
setpci -s 01:00.0 0x488.l=0x200:0x200
rmmod nvidia-uvm nvidia-drm nvidia-modeset nvidia
sh -c 'echo 1 > /sys/bus/pci/devices/:01:00.0/remove'
sh -c 'echo 1 > /sys/bus/pci/devices/:00:01.0/rescan'
modprobe nvidia nvidia-modeset nvidia-drm nvidia-uvm


And then execute the following commands (as root) to make it do this at boot:

chmod +x /root/fix-hdmi-audio.sh
systemctl enable fix-hdmi-audio.service


After each reboot, I now see the HDMI audio device on my laptop:

fludizz@tongerlo:~$ lspci | grep "PCIe Controller\|NVIDIA"
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07)
01:00.0 VGA compatible controller: NVIDIA Corporation GP106M [GeForce GTX 1060 
Mobile] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller 
(rev a1)

fludizz@tongerlo:~$ aplay -l | grep NVidia
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]

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

Title:
  HDMI sound output not detected / NVIDIA optimus laptop

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  not sure if this is an alsa or nvidia/nouveau bug.
  HDMI audio output doesn't appear in sound settings output panel.
  Audio works well on internal speakers, but it seems there is no way to make 
it output to hdmi...

  The laptop has optimus NVIDIA+Intel.
  The behaviour is the same with nouveau or nvidia proprietary driver.

  Please let me know if further testing is required

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam2295 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Sun Oct  5 17:05:35 2014
  InstallationDate: Installed on 2014-04-21 (166 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.215
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  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.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ
  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/1377653/+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 1728238] [NEW] initramfs not adding i915 GuC firmware, firmware fails to load

Public bug reported:

The i915 Kabylake GuC firmware is failing to load on boot, and
generating dmesg errors.  The Kabylake HuC firmware succeeds.  All files
exist.  I've also verified the Kabylake GuC firmware matches the correct
file size and md5 listed on 01.org.

I then ran update-initramfs verbosely, and see that only
/lib/firmware/i915/skl_guc_ver6_1.bin is being added.
/lib/firmware/i915/bxt_guc_ver8_7.bin and
/lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

Output and logs:
-
 
ls -al /lib/firmware/i915/kbl_*
 
-rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
lrwxrwxrwx 1 root root 19 Aug 17 11:08 /lib/firmware/i915/kbl_dmc_ver1.bin 
-> kbl_dmc_ver1_01.bin
-rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
-rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status
 
GuC firmware status:
path: i915/kbl_guc_ver9_14.bin
fetch: FAIL
load: NONE
version wanted: 9.14
version found: 0.0
header: offset is 0; size = 0
uCode: offset is 0; size = 0
RSA: offset is 0; size = 0
 
GuC status 0x0001:
Bootrom status = 0x0
uKernel status = 0x0
MIA Core status = 0x0
 
Scratch registers:
0: 0x0
1: 0x0
2: 0x0
3: 0x0
4: 0x0
5: 0x0
6: 0x0
7: 0x0
8: 0x0
9: 0x0
10: 0x0
11: 0x0
12: 0x0
13: 0x0
14: 0x0
15: 0x0
 
sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status
 
HuC firmware status:
path: i915/kbl_huc_ver02_00_1810.bin
fetch: SUCCESS
load: SUCCESS
version wanted: 2.0
version found: 2.0
header: offset is 0; size = 128
uCode: offset is 128; size = 218304
RSA: offset is 218432; size = 256
 
HuC status 0x6000:
 
dmesg
 
[1.052879] hidraw: raw HID events driver (C) Jiri Kosina
[1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control method 
not found
[1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
[1.082308] nvme nvme0: pci function :3c:00.0
[1.095073] Setting dangerous option enable_guc_loading - tainting kernel
[1.095075] Setting dangerous option enable_guc_submission - tainting kernel
[1.097867] [drm] Memory usable by graphics device = 4078M
[1.097869] checking generic (9000 1fb) vs hw (9000 1000)
[1.097869] fb: switching to inteldrmfb from EFI VGA
[1.097899] Console: switching to colour dummy device 80x25
[1.098049] [drm] Replacing VGA console driver
[1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[1.104157] [drm] Driver supports precise vblank timestamp query.
[1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
[1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
[1.298572]  nvme0n1: p1 p2
[1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
[1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[1.433243] usb 1-1: Product: USB+PS2 Keyboard
[1.433244] usb 1-1: Manufacturer: Generic
[1.446460] usbcore: registered new interface driver usbhid
[1.446461] usbhid: USB HID core driver
[1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
[1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
[1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
[1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
[1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 
Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1
[1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b
[1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[1.695657] usb 1-2: Product: USB Receiver
[1.695658] usb 1-2: Manufacturer: Logitech
[1.702641] logitech-djreceiver 0003:046D:C52B.0005: hiddev0,hidraw2: USB 
HID v1.11 Device [Logitech USB Receiver] on usb-:00:14.0-2/input2
[1.820317] usb 1-3: new full-speed USB device number 4 using xhci_hcd
[1.835948] input: Logitech M510 as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.2/0003:046D:C52B.0005/0003:046D:4051.0006/input/input9
[1.836129] logitech-hidpp-device 0003:046D:4051.0006: input,hidraw3: USB 
HID v1.11 Mouse [Logitech M510] on usb-:00:14.0-2:1
[1.838085] input: Logitech K750 as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.2/0003:046D:C52B.0005/0003:046D:4002.0007/input/input10
[1.838283] logitech-hidpp-device 0003:046D:4002.0007: input,hidraw4: USB 
HID v1.11 Keyboard [Logitech K750] on usb-:00:14.0-2:2
[1.896270] psmouse serio1: synaptics: queried max coordinates: x [..5666], 
y [..47

[Touch-packages] [Bug 1718139] Re: Update to version 1.2.1

** Changed in: opus (Debian)
   Status: New => Fix Released

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

Title:
  Update to version 1.2.1

Status in opus package in Ubuntu:
  New
Status in opus package in Debian:
  Fix Released

Bug description:
  The package should be updated to the current last stable version
  (1.2.1).

  The current package version is 1.1.2 (the same as in xenial).
  Version from 1.1.2 to 1.1.5 bring various bug fixes.
  Version 1.2 brings improvements described here:
  https://people.xiph.org/~jm/opus/opus-1.2/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opus/+bug/1718139/+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 1722151] Re: Incorrect syntax when writing to ~/.pam_environment

This bug was fixed in the package accountsservice - 0.6.42-0ubuntu4

---
accountsservice (0.6.42-0ubuntu4) bionic; urgency=medium

  * debian/patches/0009-language-tools.patch:
- Modification of the update-langlist script due to new
  ~/.pam_environment syntax (LP: #1722151).

 -- Gunnar Hjalmarsson   Fri, 27 Oct 2017 22:02:00
+0200

** Changed in: accountsservice (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Incorrect syntax when writing to ~/.pam_environment

Status in accountsservice package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in accountsservice source package in Artful:
  In Progress
Status in language-selector source package in Artful:
  In Progress

Bug description:
  [Impact]

  When the syntax for the entries in ~/.pam_environment was changed, the
  GUI in language-selector-gnome for maintaining the language priority
  list was broken since language-selector-gnome reads from
  ~/.pam_environment. The language-selector upload to artful makes
  language-selector-gnome handle both the old and the new syntax
  correctly.

  An additional similar change to accountsservice (the update-langlist
  script) is needed; hence also an accountsservice upload to artful.

  [Test Case]

  * Log in to an "Ubuntu on Xorg" session.
  * Open Language Support and find that it appears as if you can only
    set one item before the "English" item in the language list.

  With the new version, it works as expected again.

  [Regression Potential]

  Low. This is necessary to fix the regression caused by the change in
  accountsservice.

  [Original description]

  While investigating bug #1662031, I found out that /usr/share
  /language-tools/save-to-pam-env writes to ~/.pam_environment using an
  incorrect syntax: "VARIABLE=value" on each line. The expected syntax
  is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: accountsservice 0.6.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 06:57:17 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (463 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: accountsservice
  UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1722151/+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 1728145] Re: gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10

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

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

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

Title:
  gnome-terminal does not fill screen when window snapping on Wayland in
  Ubuntu 17.10

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu
  17.10, gnome-terminal (v3.24.2 is the version in the 17.10
  repositories) does not fill the screen at all when snapping the window
  to the right or left side. There are large gaps on the right and
  bottom edges of the terminal window in Wayland. On the same computer,
  with the same version of gnome-terminal in an Xorg gnome-session or
  Xorg ubuntu-session, the window fills screen space entirely and there
  is no problem. I am not using display scaling or hidpi features at
  all, my display resolution is set at default 1080p. This needs to be
  fixed or I'm ditching gnome-terminal.

  Expected behavior: gnome-terminal window should fill right/left of screen 
when snapped to corner in a Wayland session
  What happened instead: gnome-terminal window does not fill screen space when 
snapped to right or left edge of desktop on Wayland session, there are large 
gaps below and to the right of the snapped window on either side.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1728145/+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 1728145] Re: gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10

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

** Changed in: gnome-terminal (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-terminal does not fill screen when window snapping on Wayland in
  Ubuntu 17.10

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu
  17.10, gnome-terminal (v3.24.2 is the version in the 17.10
  repositories) does not fill the screen at all when snapping the window
  to the right or left side. There are large gaps on the right and
  bottom edges of the terminal window in Wayland. On the same computer,
  with the same version of gnome-terminal in an Xorg gnome-session or
  Xorg ubuntu-session, the window fills screen space entirely and there
  is no problem. I am not using display scaling or hidpi features at
  all, my display resolution is set at default 1080p. This needs to be
  fixed or I'm ditching gnome-terminal.

  Expected behavior: gnome-terminal window should fill right/left of screen 
when snapped to corner in a Wayland session
  What happened instead: gnome-terminal window does not fill screen space when 
snapped to right or left edge of desktop on Wayland session, there are large 
gaps below and to the right of the snapped window on either side.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1728145/+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 1728145] Re: gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10

2017-10-28 Thread Egmont Koblinger

This is a bug in GTK+, just recently fixed in git. For details, see
https://bugzilla.gnome.org/show_bug.cgi?id=789356
https://bugzilla.gnome.org/show_bug.cgi?id=789357


** Bug watch added: GNOME Bug Tracker #789356
   https://bugzilla.gnome.org/show_bug.cgi?id=789356

** Bug watch added: GNOME Bug Tracker #789357
   https://bugzilla.gnome.org/show_bug.cgi?id=789357

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

Title:
  gnome-terminal does not fill screen when window snapping on Wayland in
  Ubuntu 17.10

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu
  17.10, gnome-terminal (v3.24.2 is the version in the 17.10
  repositories) does not fill the screen at all when snapping the window
  to the right or left side. There are large gaps on the right and
  bottom edges of the terminal window in Wayland. On the same computer,
  with the same version of gnome-terminal in an Xorg gnome-session or
  Xorg ubuntu-session, the window fills screen space entirely and there
  is no problem. I am not using display scaling or hidpi features at
  all, my display resolution is set at default 1080p. This needs to be
  fixed or I'm ditching gnome-terminal.

  Expected behavior: gnome-terminal window should fill right/left of screen 
when snapped to corner in a Wayland session
  What happened instead: gnome-terminal window does not fill screen space when 
snapped to right or left edge of desktop on Wayland session, there are large 
gaps below and to the right of the snapped window on either side.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1728145/+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 1727811] Re: signon-ui crashes when trying to use KDE systemsettings to add a google account

This bug was fixed in the package signon-ui -
0.17+18.04.20171027+really20160406-0ubuntu1

---
signon-ui (0.17+18.04.20171027+really20160406-0ubuntu1) bionic; urgency=medium

  * Rebuild of 0.17+16.04.20160406-0ubuntu1 source. Versions later than
this crash when trying to add a Google account in KDE
systemsettings. An upstream solution requires unimplemented changes
to KDE Kaccounts KCM, so for now revert to last good working
version. (LP: #1727811)
  * Re-drop build dependency on libgstreamer-plugins-base0.10-dev
  * Re-drop transitional signon-ui package (package was renamed for Utopic)

 -- Rik Mills   Fri, 27 Oct 2017 15:57:25 +0100

** Changed in: signon-ui (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  signon-ui crashes when trying to use KDE systemsettings to add a
  google account

Status in signon-ui package in Ubuntu:
  Fix Released
Status in signon-ui source package in Artful:
  In Progress
Status in signon-ui source package in Bionic:
  Fix Released

Bug description:
  0.17+17.10.20170606-0ubuntu1 in Artful & Bionic crash when trying to
  use KDE systemsettings to add a google account

  "There was an error while trying to process the request:
  userActionFinished error: 2"

  This results in no Google account be added.

  This appears to be the result of changes implemented for Unity.

  A WIP solution is discussed in the reported issue upstream:

  https://gitlab.com/accounts-sso/signon-ui/issues/1

  However, that solution requires KDE upstream to adapt it's Kaccounts
  KCM.

  As KDE is now the only user of signon-ui (Unity dropping it's use) in
  Artful and abovea temporary solution is to revert to the last working
  version 0.17+17.04.20161109-0ubuntu1

  This has been built here:

  https://launchpad.net/~rikmills/+archive/ubuntu/kio-grive

  and tested successfully, allowing the the addition of Google accounts,
  and the use of kio-gdrive to access google drive from Dolphin file
  manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1727811/+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 1722151] Re: Incorrect syntax when writing to ~/.pam_environment

This bug was fixed in the package language-selector - 0.181

---
language-selector (0.181) bionic; urgency=medium

  * LanguageSelector/LocaleInfo.py:
Adapt to changed syntax in ~/.pam_environment (LP: #1722151).
  * LanguageSelector/ImConfig.py:
Prevent crash if LC_CTYPE is 'C' (LP: #1723318).
  * debian/control:
Bump Standards-Version to 4.1.1.

 -- Gunnar Hjalmarsson   Fri, 27 Oct 2017 19:40:00
+0200

** Changed in: language-selector (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Incorrect syntax when writing to ~/.pam_environment

Status in accountsservice package in Ubuntu:
  Fix Committed
Status in language-selector package in Ubuntu:
  Fix Released
Status in accountsservice source package in Artful:
  In Progress
Status in language-selector source package in Artful:
  In Progress

Bug description:
  [Impact]

  When the syntax for the entries in ~/.pam_environment was changed, the
  GUI in language-selector-gnome for maintaining the language priority
  list was broken since language-selector-gnome reads from
  ~/.pam_environment. The language-selector upload to artful makes
  language-selector-gnome handle both the old and the new syntax
  correctly.

  An additional similar change to accountsservice (the update-langlist
  script) is needed; hence also an accountsservice upload to artful.

  [Test Case]

  * Log in to an "Ubuntu on Xorg" session.
  * Open Language Support and find that it appears as if you can only
    set one item before the "English" item in the language list.

  With the new version, it works as expected again.

  [Regression Potential]

  Low. This is necessary to fix the regression caused by the change in
  accountsservice.

  [Original description]

  While investigating bug #1662031, I found out that /usr/share
  /language-tools/save-to-pam-env writes to ~/.pam_environment using an
  incorrect syntax: "VARIABLE=value" on each line. The expected syntax
  is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: accountsservice 0.6.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 06:57:17 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (463 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: accountsservice
  UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1722151/+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 1728226] [NEW] package apt 1.2.20 failed to install/upgrade: underprocessen nytt pre-removal-skript gav felkod 5

2017-10-28 Thread Kurt Svensson

Public bug reported:

Will not upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apt 1.2.20
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Sat Oct 28 14:12:05 2017
ErrorMessage: underprocessen nytt pre-removal-skript gav felkod 5
InstallationDate: Installed on 2017-03-23 (218 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.20
SourcePackage: apt
Title: package apt 1.2.20 failed to install/upgrade: underprocessen nytt 
pre-removal-skript gav felkod 5
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package apt 1.2.20 failed to install/upgrade: underprocessen nytt pre-
  removal-skript gav felkod 5

Status in apt package in Ubuntu:
  New

Bug description:
  Will not upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.20
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Oct 28 14:12:05 2017
  ErrorMessage: underprocessen nytt pre-removal-skript gav felkod 5
  InstallationDate: Installed on 2017-03-23 (218 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.20
  SourcePackage: apt
  Title: package apt 1.2.20 failed to install/upgrade: underprocessen nytt 
pre-removal-skript gav felkod 5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1728226/+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 1722319] Re: Totem Player not working correctly on 17.10 Beta 2

2017-10-28 Thread Eldar Khayrullin

Ubuntu 17.10
In the wayland session the standart Video Player give error message "Input 
error stream". (VLC plays video).
In Xorg session - OK.

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

Title:
  Totem Player not working correctly on 17.10 Beta 2

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh install of Ubuntu 17.10 Beta 2 on my laptop - Dell
  Inspiron N4110, Intel Sandybridge Mobile Graphics, Intel® Core™
  i3-2350M CPU @ 2.30GHz × 4, 6GB of RAM.  If I try to play ANY video on
  the Totem movie player (the default GNOME player), I get sound and
  subtitles but no picture. VLC works just fine. This did not happen on
  my previous 14.04 install on the same laptop. Is this a beta OS bug or
  just a bad media player?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.3-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 08:31:37 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-10-06 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1722319/+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 1728225] [NEW] correct translation denied because of format specifications

2017-10-28 Thread Rodrigo

Public bug reported:

I can't translate string 4668 and 4674 into spanish. It doesn't matter what I 
write in I keep getting the error: "number of format specifications in 'msgid' 
and 'msgstr' does not match".
Note that both 4668 and 4674 have a % simbol in it.

If I write "100 %" I get the error: 
'msgstr' is not a valid C format string, unlike 'msgid'. Reason: The string 
ends in the middle of a directive.

If I write "100 percent" I get: 
number of format specifications in 'msgid' and 'msgstr' does not match

I can write "Tomato" and still get an error.

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

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

Title:
  correct translation denied because of format specifications

Status in exiv2 package in Ubuntu:
  New

Bug description:
  I can't translate string 4668 and 4674 into spanish. It doesn't matter what I 
write in I keep getting the error: "number of format specifications in 'msgid' 
and 'msgstr' does not match".
  Note that both 4668 and 4674 have a % simbol in it.

  If I write "100 %" I get the error:   
  'msgstr' is not a valid C format string, unlike 'msgid'. Reason: The string 
ends in the middle of a directive.

  If I write "100 percent" I get: 
  number of format specifications in 'msgid' and 'msgstr' does not match

  I can write "Tomato" and still get an error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1728225/+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 1217230] Re: [Regression] Can't copy files from digital camera (Operation not supported by backend)

Launchpad has imported 21 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=984913.

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 2013-07-16T11:07:49+00:00 markm wrote:

Description of problem:

When trying to copy files from the camera using any software relaying on
gvfs-gphoto2, I get the following error: "Operation not supported by
backend"

Version-Release number of selected component (if applicable):

gvfs-ghoto2-1.16.3-2.fc19.x86_64

How reproducible:

always (on two different machines, tested with Caja, Nautilus, Thunar)

Steps to Reproduce:
1. Install gvfs-gphoto2
2. Connect camera
3. Browse images
4. Attempt to copy images

Actual results:

A popup error message appears "Operation not supported by backend"

Expected results:

Files copied without error message

Additional info:

$ gphoto2 -P
downloads all files with no issues

also installing any software capable of importing images (darktable,
shotwell) will import them without any issues too, though none of these
apps are installed by default on MATE Desktop, separate bug was filled
for it: https://bugzilla.redhat.com/show_bug.cgi?id=984908 ).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1217230/comments/0


On 2013-07-22T13:45:40+00:00 Jeff wrote:

Created attachment 776906
screenshot of error message

"Me too..."

Here's a screenshot showing the error. Marking with a priority of "high"
due to wife grief factor ;).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1217230/comments/1


On 2013-07-26T13:57:43+00:00 Paul wrote:

Ditto.

Opening the files directly in various editing packages and there is no
issue.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1217230/comments/2


On 2013-07-30T10:11:50+00:00 Cornelia wrote:

I have the same problem now, but only with a Canon Power Shot SX 260 HS,
while I don't have this problem with the old Nikon Coolpix 4100.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1217230/comments/3


On 2013-09-07T06:46:57+00:00 smanocch wrote:

Same problem with canon 50d

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1217230/comments/11


On 2013-09-18T04:47:14+00:00 Denis wrote:

Same problem with iPhone 5. The gvfs mount works fine in a terminal, but
copying the files in nautilus, which used to be the easiest way to
download the photos on F17, now just gives "Operation not supported by
backend" after upgrading to F19.

I am pretty sure the problem is with either gvfs or nautilus, not with
specific cameras. In fact, I am also not completely sure but I think the
iPhone uses gvfs-afc, not gvfs-gphoto2 -- so this may be a general
problem that affects more than one backend. gvfs-gphoto2 is probably not
the main culprit -- I'd look at the nautilus/gvfs interaction.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1217230/comments/14


On 2013-09-18T04:58:32+00:00 Denis wrote:

Ah, in fact, here's a lower-level manifestation of the same problem,
still on iPhone -- no nautilus or other file manager involved, it's
clearly 100% a gvfs problem. Someone with a camera with a gvfs-gphoto2
mount could try to confirm whether the same issue happens with gvfs-
gphoto2 as with gvfs-afc -- I suspect that's probably the case.

~ > gvfs-ls afc://e545[...]c3df/DCIM/100APPLE/
[...]
IMG_0462.JPG
IMG_0463.JPG
~ > gvfs-copy afc://e545[...]c3df/DCIM/100APPLE/IMG_0463.JPG .
Error copying file afc://e545[...]c3df/DCIM/100APPLE/IMG_0463.JPG: Operation 
not supported by backend
~ > ls /run/user/500/gvfs/afc:host=e545[...]c3df/DCIM/100APPLE/
[...]
IMG_0462.JPG
IMG_0463.JPG
~ > cp /run/user/500/gvfs/afc:host=e545[...]c3df/DCIM/100APPLE/IMG_0463.JPG .
[file copies successfully]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1217230/comments/15


On 2013-09-26T15:04:57+00:00 Ejner wrote:

I have the same problem in Thunar filemanager.

Connecting a camera (eg. canon 50d) shows up immediately in Thunar
device list, and browsing images on the camera is possible, even
thumbnails are created. Trying to open an image in eg. Geeqie, by
double-clicking it in the filemanager, does not work however, and
neither does copy/paste from the gphoto2 location via the file

[Touch-packages] [Bug 1355111] Re: newgrp fails with "crypt: Invalid argument"

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=988184.

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 2013-07-25T02:56:36+00:00 Eric wrote:

Description of problem:
newgrp fails with "crypt: Invalid argument" even when the correct password is 
given

Version-Release number of selected component (if applicable):
shadow-utils-4.1.5.1-5.fc19
glibc-2.17.11.fc19

How reproducible:
100%

Steps to Reproduce:
1. Create a new group without a password, or use an existing group that doesn't 
have a password.  I happened to discover this using the "mock" group.
2. Add a already logged-in user to a group in /etc/group.
3. Note that the current user login session is not a member of that group, 
i.e., by using the "id" command at a shell prompt
4. Issue a "newgrp " command.
5. When prompted, enter the user's password.

Actual results:
crypt: Invalid argument

Expected results:
user gets a subshell with the group in the group list (as shown by the "id" 
command)

Additional info:
This is due to a change in behavior in crypt() in glibc 2.17.  It has been 
reported upstream along with a patch that fixes it:
https://alioth.debian.org/tracker/index.php?func=detail&aid=314234
I have locally rebuilt the RPM with that patch added, and it solves the crypt 
problem.  The patch applied cleanly with -p1.

Note that with the crypt problem solved, newgrp then gives different errors:
setgroups: Operation not permitted
setgid: Operation not permitted
However, that is a completely independent bug or configuration error that I am 
still investigating.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1355111/comments/0


On 2013-07-25T02:58:20+00:00 Eric wrote:

Oops, this is in the Debian Alioth tracker, not bugs.debian.org.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1355111/comments/1


On 2013-07-25T12:12:38+00:00 Tomas wrote:

It is really weird how you could get this error. If the user is member
of the group, he will never be prompted for a password when newgrp
groupname is issued. And when he is not and there is no password in
group/gshadow set this bug will just affect the message issued. Though
applying the patch is correct thing as crypt: Invalid argument is not a
particularly good message.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1355111/comments/2


On 2013-07-25T15:46:54+00:00 Eric wrote:

The case is that the user was not a member of the group at login, but
was added to /etc/group after login, then using newgrp to get a subshell
with that group added. Doesn't the user get prompted for their own
password in that case?  I think I last experienced this use case with
F14, and I don't remember whether I was prompted for a password or not.
I might fire up F14 in a VM to check.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1355111/comments/3


On 2013-07-25T18:27:59+00:00 Tomas wrote:

Nope, there should not be a prompt in such situation and it isn't
according to my testing.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1355111/comments/4


** Changed in: shadow
   Status: Unknown => Invalid

** Changed in: shadow
   Importance: Unknown => Undecided

** Bug watch added: alioth.debian.org/ #314234
   http://alioth.debian.org/support/tracker.php?aid=314234

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

Title:
  newgrp fails with "crypt: Invalid argument"

Status in Shadow:
  Invalid
Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  entry from /etc/passwd:
  user:x:1000:1000:User,,,:/home/user:/bin/bash

  entry from /etc/group:
  dummy:x:200:user

  entry from /etc/gshadow:
  dummy:*::

  logged on as user the command
  "newgrp dummy" asks for a password and fails with "crypt: Invalid argument"

  after removing the line for dummy from gshadow newgrp works

  
  A similar bug was reported on the redhat tracker: 
https://bugzilla.redhat.com/show_bug.cgi?id=988184

  
  cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu 14.04 LTS"

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@

[Touch-packages] [Bug 1190581] Re: Support logind's automatic multiseat feature

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=974458.

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 2013-06-14T08:36:31+00:00 Jonathan wrote:

Description of problem:
Lightdm doesn't seem to properly support systemd multiseat. The first seat is
properly opened on seat0, but lightdm's other seats aren't tied to any of
logind's seats

Version-Release number of selected component (if applicable):
lightdm-1.7.0-2.fc19.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Set up four seats using udev (I named mine seat-1, seat-2 and seat-3, as
well as leaving the default seat0)
1. Configure lightdm to use the four seats
2. Start lightdm.service
3. Run loginctl

Actual results:
SESSIONUID USER SEAT
10 0 root
c14990 lightdm seat0
c16990 lightdm
c17990 lightdm
c18990 lightdm

Expected results:
SESSIONUID USER SEAT
10 0 root
c14990 lightdm seat0
c16990 lightdm seat-1
c17990 lightdm seat-2
c18990 lightdm seat-3

Additional info:
Lightdm does start correctly and does use all four seats, but, because the
seats aren't registered correctly with logind, USB devices don't automatically
get sent to the right seat.

Reply at: https://bugs.launchpad.net/lightdm/+bug/1190581/comments/1

On 2013-06-14T10:49:55+00:00 Christoph wrote:

Shouldn't this go upstream? Looks more like a feature request than a
bug.

Reply at: https://bugs.launchpad.net/lightdm/+bug/1190581/comments/2

On 2013-06-14T10:59:51+00:00 Jonathan wrote:

Yes, it is actually open at
https://bugs.launchpad.net/lightdm/+bug/1190581. I want to use this bug
to track its progress in Fedora, but forgot to add the link.

Reply at: https://bugs.launchpad.net/lightdm/+bug/1190581/comments/3

On 2013-06-14T16:48:25+00:00 Christoph wrote:

Thanks for bringing this upstream.

Reply at: https://bugs.launchpad.net/lightdm/+bug/1190581/comments/4

On 2014-11-11T14:27:25+00:00 Fedora wrote:

lightdm-kde-0.3.2.1-8.fc19, lightdm-gtk-1.8.5-9.fc19, lightdm-1.10.3-1.fc19 has
been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/FEDORA-2014-14034/lightdm-kde-0.3.2.1-8.fc19,lightdm-gtk-1.8.5-9.fc19,lightdm-1.10.3-1.fc19

Reply at: https://bugs.launchpad.net/lightdm/+bug/1190581/comments/29

On 2015-01-09T22:34:31+00:00 Fedora wrote:

This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Reply at: https://bugs.launchpad.net/lightdm/+bug/1190581/comments/34

On 2015-01-10T05:54:28+00:00 Jonathan wrote:

This has been fixed in the version of lightdm in F20.

Reply at: https://bugs.launchpad.net/lightdm/+bug/1190581/comments/35

** Changed in: lightdm (Fedora)
Status: Unknown => Invalid

** Changed in: lightdm (Fedora)
Importance: Unknown => Undecided

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

Title:
Support logind's automatic multiseat feature

Status in Light Display Manager:

[Touch-packages] [Bug 1258089] Re: Build python3 package

Launchpad has imported 15 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=976427.

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 2013-06-20T14:30:38+00:00 Zbigniew wrote:

Created attachment 763480
patch to build also systemd-python3

Description of problem:
We have very nice Python 3 compatible modules in the systemd package, and 
they're not packaged for Fedora!

Attached patches enable the build with Python3.3 in addition to the one
with Python2.7. New rpm systemd-python3 is created.

http://koji.fedoraproject.org/koji/taskinfo?taskID=5524116
http://koji.fedoraproject.org/koji/taskinfo?taskID=5524110

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1258089/comments/0

On 2013-06-20T14:31:40+00:00 Zbigniew wrote:

Created attachment 763481
fix for bug visible only in Python3 branch

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1258089/comments/1

On 2013-08-09T16:44:06+00:00 Orion wrote:

I need this to try to build fail2ban with python3.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1258089/comments/2

On 2013-08-09T18:21:53+00:00 Zbigniew wrote:

I will push the update with python3 today or tomorrow. Please wait a
bit.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1258089/comments/3

On 2013-08-15T19:02:49+00:00 Zbigniew wrote:

Patch is applied upstream in
http://cgit.freedesktop.org/systemd/systemd/commit/?id=c2748ce.

Orion, can you check if the rpms from
http://koji.fedoraproject.org/koji/getfile?taskID=5819840 or
http://koji.fedoraproject.org/koji/getfile?taskID=5819880 work for you?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1258089/comments/4

On 2013-08-15T19:04:29+00:00 Zbigniew wrote:

... http://koji.fedoraproject.org/koji/taskinfo?taskID=5819880 or
http://koji.fedoraproject.org/koji/taskinfo?taskID=5819840

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1258089/comments/5

On 2013-08-15T19:45:03+00:00 Orion wrote:

That seems to work nicely.  Thanks.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1258089/comments/6

On 2013-09-04T16:43:00+00:00 David wrote:

In the package git repository, you've added a changelog for 204-11
without actually bumping the release to 11.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1258089/comments/7

On 2013-09-10T02:36:50+00:00 Zbigniew wrote:

(In reply to David Woodhouse from comment #7)
> In the package git repository, you've added a changelog for 204-11 without
> actually bumping the release to 11.
I didn't actually build the package (in non-scratch mode) either :)
The idea was to have something in the changelog, without actually
bumping the release number, so that we somebody does a release at some
point, with more significant changes, the release number will be bumped and the 
changelog will work as expected.

Does this generate problems? I'm not aware of any except a warning
during build.

Anyway, 206-11 contains the python3 changes, so this bug can be closed.
I'm not sure why bugzilla didn't pick this up automatically... Does it
only look at the bugs referenced in the latest release in the changelog?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1258089/comments/8

On 2013-09-10T02:51:44+00:00 Orion wrote:

Bodhi will close bugs explicitly noted in the bug field.  Otherwise
there is no automatic connection between builds and bugzilla.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1258089/comments/9

On 2013-09-10T12:10:12+00:00 Zbigniew wrote:

(In reply to Orion Poplawski from comment #9)
> Bodhi will close bugs explicitly noted in the bug field.  Otherwise there is
> no automatic connection between builds and bugzilla.
I have the following in %changelog:

%changelog
...

* Sun Aug 11 2013 Zbigniew Jędrzejewski-Szmek  - 204-10
- New systemd-python3 package (#976427).

I thought that should suffice to have this bug closed...

Reply at:
https://bugs.launchpad.net/ubu

[Touch-packages] [Bug 1709708] Re: [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on an HDMI TV until power cycled.

2017-10-28 Thread Rael Gugelmin Cunha

Well, to be honest, it was your tip about the dpms that I followed!
Thanks!

I just made a bit different: I've added a line to the xset call in the
pulseaudio startup script (the sleep call was not required, just the
xset one). Details here: https://askubuntu.com/a/969935/138621

And now sound is working on retroarch! Again, thanks!

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

Title:
  [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on an HDMI TV until power cycled.

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  9 21:48:39 2017
  InstallationDate: Installed on 2017-08-06 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709708/+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 1725729] Re: Trying to add a google account with the kubuntu online account manager

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

** This bug is no longer a duplicate of private bug 1723230
** This bug has been marked a duplicate of bug 1727811
   signon-ui crashes when trying to use KDE systemsettings to add a google 
account

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

Title:
  Trying to add a google account  with the kubuntu online account
  manager

Status in signon-ui package in Ubuntu:
  New

Bug description:
  no account configured
  fresh kubuntu 17.10 install or live usb.
  Also seen on kubuntu 17.04
  when trying to use the instant messenger embedded with kubuntu, icon on 
bottom right of the screen, I first need to add an existing google account.
  In the "online accounts" tab, I click on "create", then select "google".
  after a few seconds I get the following error:
  Il y a une eu une erreur durant le traitement de la requête : 
userActionFinished error: 2
  -> there has been an error while processing the request : userActionFinished 
error: 2

  Adding an existing jabber account works fine.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: signon-ui-x11 0.17+17.10.20170606-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Oct 21 17:10:15 2017
  ExecutablePath: /usr/bin/signon-ui
  InstallationDate: Installed on 2017-09-23 (28 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/signon-ui
  ProcEnviron:
   LANGUAGE=fr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f50af6585a0 
<_ZN7QWindow11setModalityEN2Qt14WindowModalityE>:   mov0x8(%rdi),%rax
   PC (0x7f50af6585a0) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: signon-ui
  StacktraceTop:
   QWindow::setModality(Qt::WindowModality) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? ()
   ?? ()
   ?? ()
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: signon-ui crashed with SIGSEGV in QWindow::setModality()
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   (kerneloops-applet:1609): Gtk-WARNING **: Unable to locate theme engine in 
module_path: "adwaita",
   (kerneloops-applet:1609): Gtk-WARNING **: Unable to locate theme engine in 
module_path: "adwaita",

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1725729/+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 1725392] Re: signon-ui crashed with SIGSEGV in QWindow::setModality()

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

** This bug is no longer a duplicate of private bug 1723230
** This bug has been marked a duplicate of bug 1727811
   signon-ui crashes when trying to use KDE systemsettings to add a google 
account

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

Title:
  signon-ui crashed with SIGSEGV in QWindow::setModality()

Status in signon-ui package in Ubuntu:
  New

Bug description:
  Simply trying to add online accounts in Kubuntu 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: signon-ui-x11 0.17+17.10.20170606-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Oct 20 11:21:22 2017
  ExecutablePath: /usr/bin/signon-ui
  InstallationDate: Installed on 2017-09-18 (31 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/signon-ui
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f54c5cfe5a0 
<_ZN7QWindow11setModalityEN2Qt14WindowModalityE>:   mov0x8(%rdi),%rax
   PC (0x7f54c5cfe5a0) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: signon-ui
  StacktraceTop:
   QWindow::setModality(Qt::WindowModality) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? ()
   ?? ()
   ?? ()
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: signon-ui crashed with SIGSEGV in QWindow::setModality()
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  XsessionErrors:
   (kerneloops-applet:2014): Gtk-WARNING **: Unable to locate theme engine in 
module_path: "adwaita",
   (kerneloops-applet:2014): Gtk-WARNING **: Unable to locate theme engine in 
module_path: "adwaita",

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1725392/+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 1723709] Re: signon-ui crashed with SIGSEGV in QWindow::setModality()

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

** This bug is no longer a duplicate of private bug 1723230
** This bug has been marked a duplicate of bug 1727811
   signon-ui crashes when trying to use KDE systemsettings to add a google 
account

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

Title:
  signon-ui crashed with SIGSEGV in QWindow::setModality()

Status in signon-ui package in Ubuntu:
  New

Bug description:
  i was trying to sign in into google using online accounts (which I had
  to install separately) in Kubuntu 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: signon-ui-x11 0.17+17.10.20170606-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Oct 15 13:22:36 2017
  ExecutablePath: /usr/bin/signon-ui
  ProcCmdline: /usr/bin/signon-ui
  SegvAnalysis:
   Segfault happened at: 0x7ff8b131e5a0 
<_ZN7QWindow11setModalityEN2Qt14WindowModalityE>:   mov0x8(%rdi),%rax
   PC (0x7ff8b131e5a0) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: signon-ui
  StacktraceTop:
   QWindow::setModality(Qt::WindowModality) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? ()
   ?? ()
   ?? ()
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: signon-ui crashed with SIGSEGV in QWindow::setModality()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Re: [Touch-packages] [Bug 1727306] Re: window appears informing you need root privileges

2017-10-28 Thread Александр

https://youtu.be/qqwMvxReyTA
org.freedesktop.PolicyKit.Error.NotAuthorized: ('system-bus-name', {'name':
':1.878'}): org.debian.apt.install-or-remove-packages

2017-10-28 5:36 GMT+05:00 Robert Ancell :

> Can you describe what you were trying to install and the method you were
> using?
>
> ** Changed in: lightdm (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1727306
>
> Title:
>   window appears informing you need root privileges
>
> Status in lightdm package in Ubuntu:
>   Incomplete
>
> Bug description:
>   when you try to install the application window appears informing you
>   need root privileges, enter your password, only responds to the close
>   button
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: lightdm 1.24.0-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
>   Uname: Linux 4.10.0-33-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Oct 25 17:01:48 2017
>   InstallationDate: Installed on 2015-08-27 (789 days ago)
>   InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
>   SourcePackage: lightdm
>   UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/
> 1727306/+subscriptions
>

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

Title:
  window appears informing you need root privileges

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  when you try to install the application window appears informing you
  need root privileges, enter your password, only responds to the close
  button

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lightdm 1.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 17:01:48 2017
  InstallationDate: Installed on 2015-08-27 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1727306/+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 1727811] Re: signon-ui crashes when trying to use KDE systemsettings to add a google account

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

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

Title:
  signon-ui crashes when trying to use KDE systemsettings to add a
  google account

Status in signon-ui package in Ubuntu:
  Fix Committed
Status in signon-ui source package in Artful:
  In Progress
Status in signon-ui source package in Bionic:
  Fix Committed

Bug description:
  0.17+17.10.20170606-0ubuntu1 in Artful & Bionic crash when trying to
  use KDE systemsettings to add a google account

  "There was an error while trying to process the request:
  userActionFinished error: 2"

  This results in no Google account be added.

  This appears to be the result of changes implemented for Unity.

  A WIP solution is discussed in the reported issue upstream:

  https://gitlab.com/accounts-sso/signon-ui/issues/1

  However, that solution requires KDE upstream to adapt it's Kaccounts
  KCM.

  As KDE is now the only user of signon-ui (Unity dropping it's use) in
  Artful and abovea temporary solution is to revert to the last working
  version 0.17+17.04.20161109-0ubuntu1

  This has been built here:

  https://launchpad.net/~rikmills/+archive/ubuntu/kio-grive

  and tested successfully, allowing the the addition of Google accounts,
  and the use of kio-gdrive to access google drive from Dolphin file
  manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1727811/+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 1709708] Re: [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on an HDMI TV until power cycled.

2017-10-28 Thread Olivier Doriath

@Rael That is odd. My TV and cable are way too old to be 2.0 (circa
2008-2009 I believe) and yet the firmware went through and the version
number changed. Then again the 2.0 update doesn’t fix anything for this
issue. I am also using the 1 second workaround for now!

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

Title:
  [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on an HDMI TV until power cycled.

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  9 21:48:39 2017
  InstallationDate: Installed on 2017-08-06 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709708/+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 1112907] Re: abort with wireless HID devices: A handler is already registered for

Launchpad has imported 15 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=962080.

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 2013-05-11T14:41:15+00:00 Lawrenc wrote:

Version-Release number of selected component:
upower-0.9.20-1.fc19

Additional info:
reporter:   libreport-2.1.4
backtrace_rating: 4
cmdline:/usr/libexec/upowerd
crash_function: dbus_g_connection_register_g_object
executable: /usr/libexec/upowerd
kernel: 3.9.1-301.fc19.x86_64
runlevel:   N 5
uid:0

Truncated backtrace:
Thread no. 1 (6 frames)
 #2 dbus_g_connection_register_g_object at dbus-gobject.c:2859
 #3 up_device_register_device at up-device.c:838
 #4 up_device_coldplug at up-device.c:564
 #5 up_backend_device_new at up-backend.c:175
 #6 up_backend_device_add at up-backend.c:258
 #11 monitor_event at src/gudev/gudevclient.c:103

Potential duplicate: bug 817352

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/20


On 2013-05-11T14:41:17+00:00 Lawrenc wrote:

Created attachment 746570
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/21


On 2013-05-11T14:41:18+00:00 Lawrenc wrote:

Created attachment 746571
File: cgroup

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/22


On 2013-05-11T14:41:19+00:00 Lawrenc wrote:

Created attachment 746572
File: core_backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/23


On 2013-05-11T14:41:21+00:00 Lawrenc wrote:

Created attachment 746573
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/24


On 2013-05-11T14:41:23+00:00 Lawrenc wrote:

Created attachment 746574
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/25


On 2013-05-11T14:41:24+00:00 Lawrenc wrote:

Created attachment 746575
File: limits

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/26


On 2013-05-11T14:41:26+00:00 Lawrenc wrote:

Created attachment 746576
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/27


On 2013-05-11T14:41:27+00:00 Lawrenc wrote:

Created attachment 746577
File: open_fds

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/28


On 2013-05-11T14:41:29+00:00 Lawrenc wrote:

Created attachment 746578
File: proc_pid_status

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/29


On 2013-05-11T14:41:30+00:00 Lawrenc wrote:

Created attachment 746579
File: var_log_messages

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/30


On 2013-06-29T06:57:15+00:00 Mikhail wrote:

Occurs every time when my Apple Magic Mouse reconnect to Bluetooth.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/31


On 2013-09-20T16:41:57+00:00 Martin wrote:

For the record, I track this in https://launchpad.net/bugs/1112907 . I
am now able to reproduce this in a new test case, based on udev monitor
logs that reporters sent me.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/comments/39


On 2015-01-09T18:06:27+00:00 Fedora wrote:

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora versi

[Touch-packages] [Bug 1233760] Re: Sure way to crash Gnome-Shell in Ubuntu 13.10 and Ubuntu Gnome 13.10

** Changed in: dconf (Fedora)
   Status: Unknown => Won't Fix

** Changed in: dconf (Fedora)
   Importance: Unknown => Undecided

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

Title:
  Sure way to crash Gnome-Shell in Ubuntu 13.10 and Ubuntu Gnome 13.10

Status in d-conf package in Ubuntu:
  Confirmed
Status in dconf package in Fedora:
  Won't Fix

Bug description:
  This affects Gnome-Shell 3.8 up to the latest build from
  Gnome3-Staging Gnome-Shell 3.10 on Ubuntu 13.10 and Ubuntu Gnome 13.10
  daily builds, as of today!

  1. Start gnome-terminal (has to be gnome-terminal - other term apps don't 
appear to produce this bug).
  2. run sudo su and enter your password
  3. run gedit or nautilus but definitely gedit is confirmed by 1 other person
  4. Flick your mouse up to Activities
  5. Gnome-Shell is dead

  ctrl+alt+f1 - login and run stop gdm or stop lightdm depending on your Ubuntu 
build
  start lightdm or gdm - attempt to login to gnome - no desktop will appear and 
if you switch back to the console you can see gnome-shell running like crazy.

  I've tried killing X, and confirmed all gnome service aren't running
  then tried start gdm or start lightdm and still nothing works.

  Have to restart PC to recover.

  Happy to test this and give you any logs you need.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1233760/+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 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=923349.

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 2013-03-19T16:05:11+00:00 nicu wrote:

When you don't use the mouse for a long enough time, the mouse
disconnects and won't reconnect. I have to go into bluetooth settings,
remove it, and re-pair it.

This is the same bug as here:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744

I have bluez-4.101-6.fc18.x86_64


How reproducible:
every time

Steps to Reproduce:
1. wait to enter standby
2. exit standby by pressing any key
3. try to move mouse, mouse is disconnected
  
Expected results:
mouse pointer should move


Additional info:

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744/comments/7


On 2013-03-19T16:32:19+00:00 nicu wrote:

dmesg output when first connecting:

[25476.140823] hid-generic 0005:045E:077C.000A: unknown main item tag 0x0
[25476.141156] input: Microsoft Sculpt Touch Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input26
[25476.141905] hid-generic 0005:045E:077C.000A: input,hidraw0: BLUETOOTH HID 
v1.1e Mouse [Microsoft Sculpt Touch Mouse] on 9c:b7:0d:ab:1c:ee

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744/comments/8


On 2013-03-20T19:34:57+00:00 nicu wrote:

I have observed that the pairing is also lost when a new device is
inserted, like a usb stick. Otherwise, the pairing lasts 20 minutes
max...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744/comments/9


On 2013-06-28T02:06:38+00:00 Dimitris wrote:

I see what I think is the same problem with:

bluez-4.101-8.fc19.x86_64.rpm
kernel 3.9.5-301.fc19.x86_64
Thinkpad Laser Mouse

- [Re-]discover mouse and pair:

Jun 27 18:48:45 gaspode bluetoothd[10091]: bluetoothd[10091]: Discovery session 
0x7f898f20a5c0 with :1.453 activated
Jun 27 18:48:45 gaspode bluetoothd[10091]: Discovery session 0x7f898f20a5c0 
with :1.453 activated
Jun 27 18:48:47 gaspode bluetoothd[10091]: bluetoothd[10091]: Unknown command 
complete for opcode 37
Jun 27 18:48:47 gaspode bluetoothd[10091]: Unknown command complete for opcode 
37
Jun 27 18:48:50 gaspode bluetoothd[10091]: bluetoothd[10091]: Unknown command 
complete for opcode 37
Jun 27 18:48:50 gaspode bluetoothd[10091]: Unknown command complete for opcode 
37
Jun 27 18:48:54 gaspode bluetoothd[10091]: bluetoothd[10091]: Stopping discovery
Jun 27 18:48:54 gaspode bluetoothd[10091]: Stopping discovery
Jun 27 18:48:56 gaspode kernel: hid-generic 0005:17EF:6038.0006: unknown main 
item tag 0x0
Jun 27 18:48:56 gaspode kernel: input: ThinkPad Bluetooth Laser Mouse as 
/devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/bluetooth/hci0/hci0:11/input22
Jun 27 18:48:56 gaspode kernel: hid-generic 0005:17EF:6038.0006: input,hidraw3: 
BLUETOOTH HID v2.00 Mouse [ThinkPad Bluetooth Laser Mouse] on 00:27:13:96:48:a
Jun 27 18:48:56 gaspode /etc/gdm/Xsession[1422]: ** Message: has_config_widget 
F0:65:DD:67:A2:B9 HumanInterfaceDeviceService

- After using the mouse for a little, bit, turn it off (hardware
switch); then, a little while later:

Jun 27 18:49:35 gaspode kernel: power_supply hid-f0:65:dd:67:a2:b9-battery: 
driver failed to report `capacity' property: -5
Jun 27 18:49:40 gaspode kernel: power_supply hid-f0:65:dd:67:a2:b9-battery: 
driver failed to report `capacity' property: -5
Jun 27 18:51:22 gaspode bluetoothd[10091]: bluetoothd[10091]: Adapter 
/org/bluez/10091/hci0 has been disabled
Jun 27 18:51:22 gaspode bluetoothd[10091]: Adapter /org/bluez/10091/hci0 has 
been disabled
Jun 27 18:51:22 gaspode bluetoothd[10091]: bluetoothd[10091]: Unregister path: 
/org/bluez/10091/hci0
Jun 27 18:51:22 gaspode bluetoothd[10091]: Unregister path: 
/org/bluez/10091/hci0

- Turn mouse back on; Nothing happens (was expecting it to reconnect).  The 
machine is a Thinkpad X200s using a:
Bus 004 Device 009: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
built-in adapter.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744/comments/24


On 2013-12-21T12:17:56+00:00 Fedora wrote:

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open wit

[Touch-packages] [Bug 1196523] Re: gedit crashed with SIGSEGV in magazine_chain_pop_head()

Launchpad has imported 21 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=957434.

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 2013-04-28T07:01:54+00:00 Cheng-Chia wrote:

Description of problem:
1. I use gedit to edit a existing file ( I am upload it later)
2. I selected one of Chinese characters
3. I pressed Super + Space to switch to ibus-chewing input engine which I set 
with GNOME Settings.
4. I pressed "j" key with ibus-chewing
5. gedit crashed

Version-Release number of selected component:
gedit-3.8.1-1.fc19

Additional info:
backtrace_rating: 4
cmdline:gedit /home/zerng07/Translations/anjuta.gnome-3-8.zh_TW.po
crash_function: magazine_chain_pop_head
executable: /usr/bin/gedit
kernel: 3.9.0-0.rc8.git0.2.fc19.x86_64
runlevel:   N 5
uid:1000
ureports_counter: 1
xsession_errors: 

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 magazine_chain_pop_head at gslice.c:532
 #1 thread_memory_magazine1_alloc at gslice.c:835
 #2 g_slice_alloc at gslice.c:994
 #3 pango_attr_list_new at pango-attributes.c:1113
 #4 pango_attr_list_filter at pango-attributes.c:1992
 #5 filter_no_shape_attributes at pango-layout.c:3812
 #6 pango_layout_check_lines at pango-layout.c:3872
 #7 pango_layout_get_extents_internal at pango-layout.c:2534
 #8 pango_layout_get_extents at pango-layout.c:2729
 #9 gtk_text_layout_get_line_display at gtktextlayout.c:2438

Potential duplicate: bug 750087

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/0


On 2013-04-28T07:02:07+00:00 Cheng-Chia wrote:

Created attachment 741062
File: backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/1


On 2013-04-28T07:02:10+00:00 Cheng-Chia wrote:

Created attachment 741063
File: cgroup

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/2


On 2013-04-28T07:02:17+00:00 Cheng-Chia wrote:

Created attachment 741064
File: core_backtrace

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/3


On 2013-04-28T07:02:21+00:00 Cheng-Chia wrote:

Created attachment 741065
File: dso_list

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/4


On 2013-04-28T07:02:25+00:00 Cheng-Chia wrote:

Created attachment 741066
File: environ

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/5


On 2013-04-28T07:02:27+00:00 Cheng-Chia wrote:

Created attachment 741068
File: limits

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/6


On 2013-04-28T07:02:43+00:00 Cheng-Chia wrote:

Created attachment 741069
File: maps

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/7


On 2013-04-28T07:02:48+00:00 Cheng-Chia wrote:

Created attachment 741070
File: open_fds

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/8


On 2013-04-28T07:02:50+00:00 Cheng-Chia wrote:

Created attachment 741071
File: proc_pid_status

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/9


On 2013-04-28T07:02:55+00:00 Cheng-Chia wrote:

Created attachment 741072
File: var_log_messages

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/10


On 2013-04-28T07:50:55+00:00 Cheng-Chia wrote:

Created attachment 741083
The file which I edited from.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1196523/comments/11


On 2013-07-01T16:15:58+00:00 Jiro wrote:

Steps to reproduce
==
1. Launch gedit
2. Open a file in any format whose syntax gedit can recognize to highlight the 
text
3. Move the cursor to any position where strings highlighted
4. Input Japanese characters through ibus and try to convert them with the 
space key there, and gedit cranshes

reporter:   libreport-2.1.5
backtrace_ra

[Touch-packages] [Bug 1178026] Re: ubuntu-13.04-desktop-amd64 freezes at startup [solved, hardware bug]

Launchpad has imported 12 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=948641.

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 2013-04-04T22:16:55+00:00 schaefi wrote:

Description of problem:
Xorg freezes after the system is several minutes idle.

Hardware:
- HP envy 23
- Video graphics: Radeon HD 7450A
- Multi-touch enabled 58.42 cm (23 inch) diagonal widescreen full 
high-definition LED backlit display
- Details on: 
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c03683196&cc=ad&dlc=en&lc=en&jumpid=reg_r1002_usen_c-001_title_r0001#N1445

Version-Release number of selected component (if applicable):
Freeze occures in base installation of Fedora 18 as well as in updated version 
of Fedora 18 on the 03.04.13

How reproducible:
Always reproducible. System freezes after some minutes idle.
After being frozen, Strg + Alt + F1 does not lead to a new shell and the system 
needs to be rebooted by switching of power.

Additional info:
The bug could be a duplicate of 
https://bugzilla.redhat.com/show_bug.cgi?id=928549

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1178026/comments/0

On 2013-04-04T22:21:30+00:00 schaefi wrote:

Created attachment 731759
/var/log/Yorg.0.log

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1178026/comments/1

On 2013-04-04T22:22:54+00:00 schaefi wrote:

Created attachment 731760
su -c 'lspci -nn' > lspci.log

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1178026/comments/2

On 2013-04-04T22:29:03+00:00 schaefi wrote:

Created attachment 731761
/var/log/dgm/:0.log.4

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1178026/comments/3

On 2013-04-08T10:09:51+00:00 Fedora wrote:

nodejs-oauth-sign-0.2.0-1.fc18,nodejs-tunnel-agent-0.2.0-1.fc18 has been 
submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/nodejs-oauth-sign-0.2.0-1.fc18,nodejs-tunnel-agent-0.2.0-1.fc18

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1178026/comments/4

On 2013-04-08T10:10:28+00:00 Fedora wrote:

nodejs-json-stringify-safe-4.0.0-2.fc19 has been submitted as an update for 
Fedora 19.
https://admin.fedoraproject.org/updates/nodejs-json-stringify-safe-4.0.0-2.fc19

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1178026/comments/5

On 2013-04-08T10:12:29+00:00 Fedora wrote:

nodejs-json-stringify-safe-4.0.0-2.fc19, nodejs-aws-sign-0.2.0-1.fc19, 
nodejs-oauth-sign-0.2.0-1.fc19, nodejs-tunnel-agent-0.2.0-1.fc19, 
nodejs-tobi-cookie-0.2.0-1.fc19, nodejs-npm-registry-client-0.2.20-1.fc19, 
nodejs-tar-0.1.17-1.fc19, nodejs-lru-cache-2.3.0-1.fc19, node-gyp-0.9.5-1.fc19, 
npm-1.2.17-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/FEDORA-2013-4914/nodejs-tobi-cookie-0.2.0-1.fc19,nodejs-npm-registry-client-0.2.20-1.fc19,nodejs-tar-0.1.17-1.fc19,nodejs-lru-cache-2.3.0-1.fc19,node-gyp-0.9.5-1.fc19,npm-1.2.17-1.fc19,nodejs-json-stringify-safe-4.0.0-2.fc19,nodejs-aws-sign-0.2.0-1.fc19,nodejs-oauth-sign-0.2.0-1.fc19,nodejs-tunnel-agent-0.2.0-1.fc19

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1178026/comments/6

On 2013-04-08T10:16:47+00:00 T.C. wrote:

Sorry for the noise, I accidentally fat-fingered the bug number in an
related Bodhi update.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1178026/comments/7

On 2013-04-08T17:52:32+00:00 schaefi wrote:

(In reply to comment #7)
> Sorry for the noise, I accidentally fat-fingered the bug number in an
> related Bodhi update.

Hi T.C.

I did not quite understand your comment. Are all comments 4, 5, and 6 nto 
relevant or is comment 4 (Fedora 18) ok?
Should I update the mentioned packages?

Please let me know, because I desperately look for an answer and my
system still freezes regurlarly.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1178026/comments/8

On 2013-04-13T13:09:07+00:00 schaefi wrote:

Here some additional information on this bug:

1. The same machine works ok on Windows 8
This means that it pretty sure, that this is not a hardware

[Touch-packages] [Bug 1346043] Re: PerlIO dead-locks with threaded fork

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=947444.

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 2013-04-02T12:52:22+00:00 Petr wrote:

Created attachment 730746
Test case

As reported to upstream, there is a possible dead lock when using fork
from threads and PerlIO
.

This has been fixed in commit:

>From 4da80956418bbe1fdc23cad0b1cbb24cd7b87609 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Patrik=20H=C3=A4gglund?= 
Date: Sat, 2 Feb 2013 20:21:05 +0100
Subject: [PATCH] PATCH [perl #106212] Add PL_perlio_mutex to
 atfork_lock/unlock

Using threads + fork() on Linux, and IO operations in the threads, the
PL_perlio_mutex may be left in a locked state at the call of fork(),
potentially leading to deadlock in the child process at subsequent IO
operations. (Threads are pre-empted and not continued in the child
process after the fork.)

Therefore, ensure that the PL_perlio_mutex is unlocked in the child
process, right after fork(), by using atfork_lock/unlock.

(The RT text gives ways to reproduce the problem, but are not easily
added to Perl's test suite)


Probably all Fedoras are affected.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1346043/comments/0


On 2013-04-11T11:02:53+00:00 Fedora wrote:

perl-5.16.3-262.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/perl-5.16.3-262.fc19

Reply at:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1346043/comments/1


On 2013-04-11T11:10:11+00:00 Fedora wrote:

perl-5.16.3-242.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/perl-5.16.3-242.fc18

Reply at:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1346043/comments/2


On 2013-04-11T13:06:07+00:00 Fedora wrote:

perl-5.14.4-225.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/perl-5.14.4-225.fc17

Reply at:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1346043/comments/3


On 2013-04-20T19:15:07+00:00 Fedora wrote:

perl-5.16.3-262.fc19, perl-Sys-Syslog-0.32-1.fc19 has been pushed to the
Fedora 19 stable repository.  If problems still persist, please make
note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1346043/comments/4


On 2013-04-25T00:45:38+00:00 Fedora wrote:

perl-5.16.3-242.fc18, perl-Sys-Syslog-0.32-1.fc18 has been pushed to the
Fedora 18 stable repository.  If problems still persist, please make
note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1346043/comments/5


On 2013-04-27T00:11:08+00:00 Fedora wrote:

perl-5.14.4-225.fc17 has been pushed to the Fedora 17 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1346043/comments/6


** Changed in: perl (Fedora)
   Status: Unknown => Fix Released

** Changed in: perl (Fedora)
   Importance: Unknown => Undecided

** Bug watch added: rt.perl.org/rt3/Public/ #106212
   http://rt.perl.org/rt3/Public/Ticket/Display.html?id=106212

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

Title:
  PerlIO dead-locks with threaded fork

Status in perl package in Ubuntu:
  New
Status in perl package in Fedora:
  Fix Released

Bug description:
  This bug can be found on Fedora or Perl bug tracking system and fixed
  there.

  https://bugzilla.redhat.com/show_bug.cgi?id=947444
  https://rt.perl.org/Public/Bug/Display.html?id=106212

  I have same issue with Ubuntu 12.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1346043/+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 1727269] Re: Window buttons and window edges are not rendered/designed cleanly - Ubuntu 17.10 Gnome

2017-10-28 Thread Ragnar Dunbar

In the attached screenshot one can see that there is a difference in the
color of the outer pixels of the screen edge. In 17.10 there is a darker
grey. Both windows were in the front, when the screenshots were taken.
To me, due to the less smooth transition of colors, the screen edges in
17.10 look somewhat rough, ripped.

** Attachment added: "window_edges.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727269/+attachment/4998650/+files/window_edges.png

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

Title:
  Window buttons and window edges are not rendered/designed cleanly -
  Ubuntu 17.10 Gnome

Status in gnome-shell package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Window buttons and window edges are not rendered/designed cleanly -
  Ubuntu 17.10 Gnome. This is really just a cosmetic issue. The window
  edges (mostly only top left) and window buttons were sharper and
  clearer in Ubuntu 16.04 und the versions before. The rough window
  egdges do not appear in all windows, it is especially obvious with
  Firfox. The impression with the buttons is always present.

  This is apparent in stock Ubuntu 17.10 on various laptops (Thinkpad
  x220, Acer Aspire 5253, Macbook Pro late 2010).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727269/+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 1728215] [NEW] After upgrading from 17.04 to 17.10 mouse cursor shows on both screens

2017-10-28 Thread no

Public bug reported:

My main monitor is on the right.

When my cursor is on the right monitor, the cursor also displays on the
left monitor.

When i move the cursor:

- rightwards on the right monitor, the cursor on the left monitor moves
downwards

- leftwards on the right monitor, the cursor on the left monitor moves
upwards

- downwards on the right monitor, the cursor on the left monitor moves
leftwards

- upwards on the right monitor, the cursor on the left monitor moves
rightwards

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 19:12:36 2017
DistUpgraded: 2017-10-22 07:25:03,053 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation HD Graphics 520 [8086:2063]
InstallationDate: Installed on 2016-03-22 (585 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for 
Bluetooth
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=306db387-b854-4d8f-8382-9727ad6ce642 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-10-21 (6 days ago)
dmi.bios.vendor: Intel Corp.
dmi.board.vendor: Intel corporation
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat Oct 21 20:19:52 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  After upgrading from 17.04 to 17.10 mouse cursor shows on both screens

Status in xorg package in Ubuntu:
  New

Bug description:
  My main monitor is on the right.

  When my cursor is on the right monitor, the cursor also displays on
  the left monitor.

  When i move the cursor:

  - rightwards on the right monitor, the cursor on the left monitor
  moves downwards

  - leftwards on the right monitor, the cursor on the left monitor moves
  upwards

  - downwards on the right monitor, the cursor on the left monitor moves
  leftwards

  - upwards on the right monitor, the cursor on the left monitor moves
  rightwards

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 19:12:36 2017
  DistUpgraded: 2017-10-22 07:25:03,053 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 520 [8086:2063]
  InstallationDate: Installed on 2016-03-22 (585 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=306db387-b854-4d8f-83

[Touch-packages] [Bug 613809] Re: [FFe] gnomeradio NO SOUND, no /dev/mixer present

Launchpad has imported 11 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=904775.

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 2013-01-27T13:49:46+00:00 triniton wrote:

Description of problem:

When will alsa support to gnomeradio?
Currently, you can not use the up and down arrow keys for volume management.
The new systems, throwing the OSS, and there is no /dev/mixer.

It possible like someone implement alsa support ( including alsa mixer )
like in tvtime.

Thanks

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/613809/comments/42


On 2013-01-29T18:05:54+00:00 POJAR wrote:

I write a patch ( ubuntu gnomeradio version ) to support for looping
back audio through alsa devices ( including mixer control ).

Should be tested in several types of tv/fm tuners and then all the work
will be made public.

Package for ubuntu is here:
https://launchpad.net/~geoubuntu/+archive/test

Best regards.

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/613809/comments/43


On 2013-01-30T01:20:52+00:00 Raymond wrote:

post the output of alsa-info.sh


did you connect your radio to line in or aux of your onboard sound ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/613809/comments/45


On 2013-01-30T07:34:40+00:00 POJAR wrote:

My radio tuner is connected to line in.

In function of your tuner, change "Mixer Source" from "Preference" to:

default/Line or
default/CD or
hw:0/Line or
etc.

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/613809/comments/46


On 2013-01-30T07:45:24+00:00 POJAR wrote:

Created attachment 690203
alsa info

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/613809/comments/47


On 2013-01-30T08:27:03+00:00 Raymond wrote:

you have to unmute  line playback switch and change line playback volume
using alsamixer -c0

no need to change capture source to line since you are using the analog
mixer of AC97 codec to mix the input signal from line in to line out

set line playback to 0dB

amixer -c 0 set Line playback 72% unmute


the output volume is controlled by master playback volume and switch


Simple mixer control 'Line',0
  Capabilities: pvolume pswitch pswitch-joined cswitch cswitch-exclusive penum
  Capture exclusive group: 0
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Front Left: Playback 0 [0%] [-34.50dB] [off] Capture [off]
  Front Right: Playback 0 [0%] [-34.50dB] [off] Capture [off]


control.18 {
iface MIXER
name 'Line Playback Switch'
value false
comment {
access 'read write'
type BOOLEAN
count 1
}
}
control.19 {
iface MIXER
name 'Line Playback Volume'
value.0 0
value.1 0
comment {
access 'read write'
type INTEGER
count 2
range '0 - 31'
dbmin -3450
dbmax 1200
dbvalue.0 -3450
dbvalue.1 -3450
}
}

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/613809/comments/48


On 2013-03-27T15:33:03+00:00 POJAR wrote:

Probably one of the most popular questions I see new users ask about
gnomeradio is along the lines of the following:

"It looks like gnomeradio is working (showing me gui), but for some
reason I am not hearing any audio. What is wrong with my tuner?"

Unfortunately, in the vast majority of cases, there is nothing wrong
with the tuner. The problem is that gnomeradio was originally designed
to be used with older tuner cards that have a dedicated audio output
cable, which you are expected to connect to speakers. Most newer tuner
products deliver their audio via an ALSA device, for which gnomeradio
has no mechanism to route the audio to soundcard.

As a result, users end to run sox or arecord/aplay in a separate
terminal window (which always seemed like a rather ridiculous
workaround).

Solution: Added support for loopin

[Touch-packages] [Bug 1175091] Re: Cable Ethernet conn. "die" with Atheros Network Card in Ubuntu 13.04

** Changed in: fedora
   Status: Unknown => Invalid

** Changed in: fedora
   Importance: Unknown => Medium

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

Title:
  Cable Ethernet conn. "die" with Atheros Network Card in Ubuntu 13.04

Status in network-manager package in Ubuntu:
  Confirmed
Status in Fedora:
  Invalid
Status in openSUSE:
  Fix Released

Bug description:
  In New Ubuntu 13.04 the network connections crash on 13.04 in cable Ethernet 
connection.
  The connection works for about 2-3 minutes, and after "die".
  Unplug/plug the cable sometimes helps to re-work the connection manager.

  I suppose the problem in the Atheros drivers
  In Ubuntu 12.10 the network works perfectly.
  The bug is confermed by many other users.

  The problem seems to be more present when using static IP (type of
  network configuration : manual)

  WIFI works perfectly (Card is Atheros too)

  My network Ethernet card is  ATHEROS AR8152

  command : lshw -C network

  -network   
 description: Wireless interface
 product: AR9285 Wireless Network Adapter (PCI-Express)
 vendor: Atheros Communications Inc.
 physical id: 0
 bus info: pci@:0c:00.0
 logical name: wlan0
 version: 01
 serial: 90:a4:de:4a:7a:28
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list ethernet physical wireless
 configuration: broadcast=yes driver=ath9k 
driverversion=3.8.0-19-generic firmware=N/A ip=10.173.129.175 latency=0 
link=yes multicast=yes wireless=IEEE 802.11bgn
 resources: irq:17 memory:f69f-f69f
*-network
 description: Ethernet interface
 product: AR8152 v2.0 Fast Ethernet
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:09:00.0
 logical name: eth0
 version: c1
 serial: 78:2b:cb:f0:56:35
 capacity: 100Mbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=atl1c 
driverversion=1.0.1.1-NAPI latency=0 link=no multicast=yes port=twisted pair
 resources: irq:47 memory:f68c-f68f ioport:df00(size=128)

  
  Without this 13.04 is unuseful.

  Thanx
  Stefano Pecchenino
  pe...@fastwebnet.it

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: network-manager 0.9.8.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  CRDA:
   country IT:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  Date: Wed May  1 10:23:15 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-04-30 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  IpRoute:
   default via 10.173.128.1 dev wlan0  proto static 
   10.173.128.0/20 dev wlan0  proto kernel  scope link  src 10.173.129.175  
metric 9 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   FASTWEB-PEKKE e24676af-073a-4071-8e25-a3dc1c022421   
802-11-wireless   1367396634   mer 01 mag 2013 10:23:54 CEST  yes   
no /org/freedesktop/NetworkManager/Settings/1
   ADSL Ufficio  8db2aff6-e740-4f53-81de-e260b2c883db   
802-3-ethernet0never  no
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
htt

[Touch-packages] [Bug 1235446] Re: evolution-calendar-factory crashed with SIGSEGV in socket_connected()

Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=908465.

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 2013-02-06T18:43:32+00:00 Andrea wrote:

Version-Release number of selected component:
evolution-data-server-3.4.4-4.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:/usr/libexec/evolution-calendar-factory
crash_function: socket_connected
kernel: 3.7.3-101.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 socket_connected at soup-socket.c:675
: #1 soup_socket_connect_sync at soup-socket.c:829
: #2 soup_connection_connect_sync at soup-connection.c:664
: #3 get_connection at soup-session-sync.c:209
: #4 process_queue_item at soup-session-sync.c:297
: #5 send_message at soup-session-sync.c:390
: #6 send_and_handle_redirection at e-cal-backend-caldav.c:1010
: #7 caldav_server_list_objects at e-cal-backend-caldav.c:1343
: #8 synchronize_cache at e-cal-backend-caldav.c:1951
: #9 caldav_synch_slave_loop at e-cal-backend-caldav.c:2310

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/0


On 2013-02-06T18:43:36+00:00 Andrea wrote:

Created attachment 694090
File: core_backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/1


On 2013-02-06T18:43:38+00:00 Andrea wrote:

Created attachment 694091
File: environ

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/2


On 2013-02-06T18:43:41+00:00 Andrea wrote:

Created attachment 694092
File: limits

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/3


On 2013-02-06T18:43:44+00:00 Andrea wrote:

Created attachment 694093
File: backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/4


On 2013-02-06T18:43:46+00:00 Andrea wrote:

Created attachment 694094
File: cgroup

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/5


On 2013-02-06T18:43:49+00:00 Andrea wrote:

Created attachment 694095
File: smolt_data

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/6


On 2013-02-06T18:43:51+00:00 Andrea wrote:

Created attachment 694096
File: executable

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/7


On 2013-02-06T18:43:54+00:00 Andrea wrote:

Created attachment 694097
File: maps

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/8


On 2013-02-06T18:43:57+00:00 Andrea wrote:

Created attachment 694098
File: dso_list

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/9


On 2013-02-06T18:43:59+00:00 Andrea wrote:

Created attachment 694099
File: proc_pid_status

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/10


On 2013-02-06T18:44:01+00:00 Andrea wrote:

Created attachment 694100
File: var_log_messages

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/11


On 2013-02-06T18:44:04+00:00 Andrea wrote:

Created attachment 694101
File: open_fds

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/12


On 2013-02-07T08:17:31+00:00 Milan wrote:

Thanks for a bug report. There had been reported a similar bug report
already, thus I'm marking it as a duplicate.

*** This bug has been marked as a duplicate of bug 892913 ***

Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution-data-
server/+bug/1235446/comments/13


** Changed in: evolution-data-server (Fedo

[Touch-packages] [Bug 1728214] [NEW] Cannot adjust screen brightness after upgrading from 17.04 to 17.10

2017-10-28 Thread no

Public bug reported:

References:

https://help.ubuntu.com/stable/ubuntu-help/display-brightness.html

The screen is unusably bright and I cannot adjust its brightness by any
of the following methods:

"To change the brightness of your screen, click the system menu on the
right side of the top bar and adjust the screen brightness slider to the
value you want to use. The change should take effect immediately".

"You can also adjust the screen brightness by using the Power panel".

Prior to upgrade, the brightness controller app worked
(https://github.com/LordAmit/Brightness).

After the upgrade, it does not.

Related posts are on Ubuntu stack exchange etc:

https://askubuntu.com/questions/966557/how-do-we-turn-down-the-insane-
brightness-on-ubuntu-17-10

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 18:36:39 2017
DistUpgraded: 2017-10-22 07:25:03,053 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation HD Graphics 520 [8086:2063]
InstallationDate: Installed on 2016-03-22 (585 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for 
Bluetooth
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=306db387-b854-4d8f-8382-9727ad6ce642 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-10-21 (6 days ago)
dmi.bios.vendor: Intel Corp.
dmi.board.vendor: Intel corporation
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat Oct 21 20:19:52 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  Cannot adjust screen brightness after upgrading from 17.04 to 17.10

Status in xorg package in Ubuntu:
  New

Bug description:
  References:

  https://help.ubuntu.com/stable/ubuntu-help/display-brightness.html

  The screen is unusably bright and I cannot adjust its brightness by
  any of the following methods:

  "To change the brightness of your screen, click the system menu on the
  right side of the top bar and adjust the screen brightness slider to
  the value you want to use. The change should take effect immediately".

  "You can also adjust the screen brightness by using the Power panel".

  Prior to upgrade, the brightness controller app worked
  (https://github.com/LordAmit/Brightness).

  After the upgrade, it does not.

  Related posts are on Ubuntu stack exchange etc:

  https://askubuntu.com/questions/966557/how-do-we-turn-down-the-insane-
  brightness-on-ubuntu-17-10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 18:36:39 2017
  DistUpgraded: 2017-10-22 07:25:03,053 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphi

[Touch-packages] [Bug 1012211] Re: NetworkManager mishandles multiple interfaces on same subnet

Launchpad has imported 12 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=886312.

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 2012-12-12T01:51:42+00:00 Konstantin wrote:

Description of problem:
If, while connected over wifi, ethernet connection is made, routing table is 
not properly updated

Version-Release number of selected component (if applicable):


How reproducible:
Every time


Steps to Reproduce:
1. Boot a laptop without ethernet, have it connected to a wifi network
2. Connect ethernet cable (same network)
3. Browse pages/check email/etc.
  
Actual results:
Wifi route is stuck as the default in the routing table, so network connection 
is not working right.


Expected results:
routing table should become exactly same as it would've been if laptop was 
booted up with wifi and ethernet enabled and plugged in, respectively.


Additional info:
Turning wifi off and then back on seems to work around the problem because the 
wifi interface gateway is removed when wifi is disabled. When re-added, wifi 
doesn't override ethernet gateway (correct behavior)

Reply at: https://bugs.launchpad.net/linuxmint/+bug/1012211/comments/1


On 2012-12-14T10:58:52+00:00 Jirka wrote:

It works for me. 
What NM version do you use?

Make sure "Use this connection only for resources on its networks" is
not checked in the editor (IPv4 Settings, Routes...).

Would you, please, collect more information for us?
1. your connections data
nmcli -f connection,ipv4 con l id "your ethernet connection name"
nmcli -f connection,ipv4 con l id "your Wi-Fi connection name"

'never-default' option should be 'no'.

2. /var/log/messages

Reply at: https://bugs.launchpad.net/linuxmint/+bug/1012211/comments/2


On 2012-12-14T12:16:45+00:00 Konstantin wrote:

0.9.6.4
not checked

connection.id:  Wired connection 1
connection.uuid:8f8ffb67-599c-45fb-8c2d-98410ca064c1
connection.type:802-3-ethernet
connection.autoconnect: yes
connection.timestamp:   1355487105
connection.read-only:   no
connection.permissions: 

connection.id:  Auto CoRouter
connection.uuid:bf23e0e8-2ce4-4b80-8a8e-4ac8dca8303e
connection.type:802-11-wireless
connection.autoconnect: yes
connection.timestamp:   1355486879
connection.read-only:   no
connection.permissions: 
ipv4.method:auto
ipv4.dns:   
ipv4.dns-search:
ipv4.addresses: 
ipv4.routes:
ipv4.ignore-auto-routes:no
ipv4.ignore-auto-dns:   no
ipv4.dhcp-client-id:--
ipv4.dhcp-send-hostname:yes
ipv4.dhcp-hostname: --
ipv4.never-default: no
ipv4.may-fail:  no


don't see a never-default option anywhere


on inserting the ethernet cable:

Dec 14 04:11:44 mireille kernel: [102378.251074] r8169 :05:00.0: p1p1: link 
up
Dec 14 04:11:44 mireille kernel: [102378.251096] IPv6: ADDRCONF(NETDEV_CHANGE): 
p1p1: link becomes ready
Dec 14 04:11:44 mireille NetworkManager[540]:  (p1p1): carrier now ON 
(device state 20)
Dec 14 04:11:44 mireille NetworkManager[540]:  (p1p1): device state 
change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Dec 14 04:11:44 mireille NetworkManager[540]:  Auto-activating connection 
'Wired connection 1'.
Dec 14 04:11:44 mireille NetworkManager[540]:  Activation (p1p1) starting 
connection 'Wired connection 1'
Dec 14 04:11:44 mireille NetworkManager[540]:  (p1p1): device state 
change: disconnected -> prepare (reason 'none') [30 40 0]
Dec 14 04:11:44 mireille NetworkManager[540]:  Activation (p1p1) Stage 1 
of 5 (Device Prepare) scheduled...
Dec 14 04:11:44 mireille NetworkManager[540]:  Activation (p1p1) Stage 1 
of 5 (Device Prepare) started...
Dec 14 04:11:44 mireille NetworkManager[540]:  Activation (p1p1) Stage 2 
of 5 (Device Configure) scheduled...
Dec 14 04:11:44 mireille NetworkManager[540]:  Activation (p1p1) Stage 1 
of 5 (Device Prepare) complete.
Dec 14 04:11:44 mireille NetworkManager[540]:  Activation (p1p1) Stage 2 
of 5 (Device Configure) starting...
Dec 14 04:11:44 mireille NetworkManager[540]:  (p1p1): device state 
change: prepare -> config (reason 'none') [40 50 0]
Dec 14 04:11:44 mireille NetworkManager[540]:  Activa

[Touch-packages] [Bug 1109298] Re: [Regression] error when trying to compile a program which uses alsa/asoundlib.h with EGLIBC 2.17

Launchpad has imported 12 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=885306.

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 2012-12-08T14:29:54+00:00 Richard wrote:

Description of problem:
While trying to build the latest mythtv on RPM Fusion for rawhide I ran into 
the following issue:

g++ -c -pipe -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DPIC -O2 -g
-pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -fomit-frame-pointer
-fomit-frame-pointer -fPIC -pthread -g -Wall -Wpointer-arith
-Wno-non-virtual-dtor -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS
-fvisibility-inlines-hidden -Wmissing-declarations -Wno-switch
-Wredundant-decls -funit-at-a-time -D_REENTRANT -fPIC -DMMX
-D_GNU_SOURCE -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_SHARED
-I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/usr/include/QtCore
-I/usr/include -I/usr/include -I/usr -I/usr/include/libxml2
-I../../zeromq/include -I../../nzmqt/include/nzmqt -I../include -I.
-I. -o parser.o parser.cpp
In file included from /usr/include/alsa/asoundlib.h:49:0,
 from libavdevice/alsa-audio-common.c:31:
/usr/include/alsa/pcm.h:944:1: error: unknown type name 'u_int8_t'
/usr/include/alsa/pcm.h:945:1: error: unknown type name 'u_int16_t'
/usr/include/alsa/pcm.h:946:1: error: unknown type name 'u_int32_t'
/usr/include/alsa/pcm.h:947:1: error: unknown type name 'u_int64_t'
In file included from /usr/include/alsa/asoundlib.h:49:0,
 from libavdevice/alsa-audio-common.c:31:
/usr/include/alsa/pcm.h:1052:1: error: unknown type name 'int16_t'
make[2]: *** [libavdevice/alsa-audio-common.o] Error 1
make[2]: Leaving directory
`/builddir/build/BUILD/MythTV-mythtv-d2f9798/mythtv/external/FFmpeg'
make[1]: *** [FFmpeg-all] Error 2


Version-Release number of selected component (if applicable):
alsa-lib-devel-1.0.26-1.fc19.x86_64


A mythtv dev suggested the following *might* be the fix. Since I build mythtv 
in mock/rpmbuild I don't think it's possible/practical to test this patch:

--- /usr/include/alsa/asoundlib.h   2012-09-06 06:18:02.0 -0700
+++ asoundlib.h 2012-12-07 19:30:53.131751067 -0800
@@ -31,6 +31,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1109298/comments/0


On 2012-12-10T17:02:58+00:00 Richard wrote:

Created attachment 660967
Git diff from master

I have verified that the patch essentially works (I had to actually
patch asoundlib-head.h)

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1109298/comments/1


On 2012-12-10T17:04:16+00:00 Richard wrote:

Created attachment 660968
Patch to asoundlib.h

Attaching since I couldn't get it to show up in the git diff...

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1109298/comments/2


On 2012-12-10T18:44:22+00:00 Gary wrote:

(In reply to comment #0)
.
> A mythtv dev suggested the following *might* be the fix. 

I believe the (root) cause is that stdlib.h no longer
includes sys/types.h, and the alsa includes depend on
the u_int... types being defined (which were being
defined in sys/types.h, no longer included).

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1109298/comments/3


On 2012-12-20T21:55:10+00:00 Richard wrote:

As it's been 10 days since the last comment on this bug I just wanted to
ping you guys to see if anyone is working on a fix.

I would think that breaking a program from building would be considered
a serious, though not urgent, bug.

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1109298/comments/4


On 2013-03-23T04:29:02+00:00 Gary wrote:

It appears that this has been addressed upstream http://git.alsa-
project.org/?p=alsa-
lib.git;a=commit;h=3e7dc283ed2d3ed2341f0657811c588f4dbcba6d

Reply at: https://bugs.launchpad.net/ubuntu/+source/alsa-
lib/+bug/1109298/comments/15


On 2013-04-03T15:18:49+00:00 Fedora wrote:

This bug appears to have been reported against 'rawhide' during the Fedora 19 
development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 
19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 
End Of

[Touch-packages] [Bug 1117411] Re: CVE-2013-0240: fails to verify SSL certificates when creating accounts

Launchpad has imported 8 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=894352.

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 2013-01-14T13:16:09+00:00 Jan wrote:

This issue affects the versions of the gnome-online-accounts package, as
shipped with Fedora release of 16 and 17.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1117411/comments/0


On 2013-02-05T15:51:01+00:00 Jan wrote:

It was found that Gnome Online Accounts (GOA) did not perform SSL
certificate validation, when performing Windows Live and Facebook
accounts creation. A remote attacker could use this flaw to conduct man-
in-the-middle (MiTM) attacks, possibly leading to their ability to
obtain sensitive information.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1117411/comments/1


On 2013-02-05T15:53:06+00:00 Jan wrote:


Acknowledgements:

Red Hat would like to thank Simon McVittie for reporting this issue.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1117411/comments/2


On 2013-02-05T16:04:47+00:00 Jan wrote:

Relevant upstream patch:
[1] 
http://git.gnome.org/browse/gnome-online-accounts/commit/?id=edde7c63326242a60a075341d3fea0be0bc4d80e

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1117411/comments/3


On 2013-02-05T16:06:14+00:00 Jan wrote:

Created gnome-online-accounts tracking bugs for this issue

Affects: fedora-all [bug 908000]

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1117411/comments/4


On 2013-02-27T02:41:22+00:00 Fedora wrote:

gnome-online-accounts-3.4.2-3.fc17 has been pushed to the Fedora 17
stable repository.  If problems still persist, please make note of it in
this bug report.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1117411/comments/6


On 2013-03-19T20:00:45+00:00 Fedora wrote:

gnome-online-accounts-3.6.3-1.fc18 has been pushed to the Fedora 18
stable repository.  If problems still persist, please make note of it in
this bug report.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1117411/comments/7


On 2013-03-28T18:04:17+00:00 Vincent wrote:

Just to note that CVE-2013-1799 was assigned to the incomplete fix
present in 3.6.3 and 3.7.5 (I'm presuming some beta or pre-releases).


Common Vulnerabilities and Exposures assigned an identifier CVE-2013-0240 to
the following vulnerability:

Name: CVE-2013-0240
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0240
Assigned: 20121206
Reference: 
https://mail.gnome.org/archives/gnome-announce-list/2013-March/msg7.html
Reference: https://bugzilla.redhat.com/show_bug.cgi?id=894352
Reference: https://bugzilla.gnome.org/show_bug.cgi?id=693214
Reference: 
https://git.gnome.org/browse/gnome-online-accounts/commit/?h=gnome-3-6&id=ecad8142e9ac519b9fc74b96dcb5531052bbffe1
Reference: 
https://git.gnome.org/browse/gnome-online-accounts/commit/?id=bc10fdb68f75f8be84eb698ada08743b9c7c248f
Reference: 
https://git.gnome.org/browse/gnome-online-accounts/commit/?id=edde7c63326242a60a075341d3fea0be0bc4d80e

Gnome Online Accounts (GOA) 3.4.x, 3.6.x before 3.6.3, and 3.7.x
before 3.7.5, does not properly validate SSL certificates when
creating accounts such as Windows Live and Facebook accounts, which
allows man-in-the-middle attackers to obtain sensitive information
such as credentials by sniffing the network.


Common Vulnerabilities and Exposures assigned an identifier CVE-2013-1799 to
the following vulnerability:

Name: CVE-2013-1799
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-1799
Assigned: 20130219
Reference: 
https://mail.gnome.org/archives/gnome-announce-list/2013-March/msg7.html
Reference: 
https://mail.gnome.org/archives/gnome-announce-list/2013-March/msg00020.html
Reference: https://bugzilla.gnome.org/show_bug.cgi?id=693214
Reference: https://bugzilla.gnome.org/show_bug.cgi?id=695106
Reference: 
https://git.gnome.org/browse/gnome-online-accounts/commit/?id=9cf4bc0ced2c53bcdd36922caa65afc8a167bbd8


Gnome Online Accounts (GOA) 3.6.x before 3.6.3 and 3.7.x before
3.7.91, does not properly validate SSL certificates when creating
ac

[Touch-packages] [Bug 1053539] Re: lscpu crashed with SIGFPE in read_topology()

** Changed in: util-linux-ng
   Status: Unknown => Fix Released

** Changed in: util-linux-ng
   Importance: Unknown => Undecided

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

Title:
  lscpu crashed with SIGFPE in read_topology()

Status in Util-Linux-ng:
  Fix Released
Status in util-linux package in Ubuntu:
  Triaged

Bug description:
  when I run in the terminal lscpu gives me an error "floating point
  exception (`core 'generated)"

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: util-linux 2.20.1-5.1ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Date: Thu Sep 20 19:44:38 2012
  ExecutablePath: /usr/bin/lscpu
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120917)
  ProcCmdline: lscpu
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
  Signal: 8
  SourcePackage: util-linux
  StacktraceTop:
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
   ?? ()
   ?? ()
  Title: lscpu crashed with SIGFPE in __libc_start_main()
  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/util-linux-ng/+bug/1053539/+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 1140716] Re: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge

** Changed in: linux (Fedora)
   Status: Unknown => Won't Fix

** Changed in: linux (Fedora)
   Importance: Unknown => Undecided

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

Title:
  [regression] 3.5.0-26-generic and  3.2.0-39-generic GPU hangs on
  Sandybridge

Status in DRI:
  Fix Released
Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-quantal source package in Precise:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in mesa source package in Precise:
  Triaged
Status in linux source package in Quantal:
  Invalid
Status in linux-lts-quantal source package in Quantal:
  Invalid
Status in linux source package in Raring:
  Invalid
Status in linux-lts-quantal source package in Raring:
  Invalid
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Won't Fix

Bug description:
  I'm getting errors about GPU hangs every minute or so (usually only
  when using FF and scrolling a webpage or something). I also get an
  annoying ubuntu dialog saying there is a "system error".

  This didn't happen with 3.5.0-24-generic.

  Here is the dmesg:
  [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.658405] [ cut here ]
  [26285.658472] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26285.658474] Hardware name: SATELLITE Z830
  [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm 
arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel 
snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep 
iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi 
rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer 
snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap 
soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei 
video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc 
lp parport e1000e ahci libahci [last unloaded: sdhci]
  [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic 
#40-Ubuntu
  [26285.658539] Call Trace:
  [26285.658549]  [] warn_slowpath_common+0x7f/0xc0
  [26285.658553]  [] warn_slowpath_null+0x1a/0x20
  [26285.658569]  [] gen6_enable_rps+0x706/0x710 [i915]
  [26285.658584]  [] intel_modeset_init_hw+0x66/0xa0 [i915]
  [26285.658595]  [] i915_reset+0x1a4/0x6e0 [i915]
  [26285.658601]  [] ? __switch_to+0x12b/0x420
  [26285.658612]  [] i915_error_work_func+0xc3/0x110 [i915]
  [26285.658618]  [] process_one_work+0x12a/0x420
  [26285.658629]  [] ? gen6_pm_rps_work+0xe0/0xe0 [i915]
  [26285.658632]  [] worker_thread+0x12e/0x2f0
  [26285.658636]  [] ? manage_workers.isra.26+0x200/0x200
  [26285.658640]  [] kthread+0x93/0xa0
  [26285.658644]  [] kernel_thread_helper+0x4/0x10
  [26285.658649]  [] ? kthread_freezable_should_stop+0x70/0x70
  [26285.658652]  [] ? gs_change+0x13/0x13
  [26285.658654] ---[ end trace 59c6162fdfcbffee ]---
  [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26932.376544] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.384285] [ cut here ]
  [26932.384354] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26932.384356] Ha

[Touch-packages] [Bug 1048203] Re: (CVE-2012-4412) glibc: strcoll() integer overflow leading to buffer overflow

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=855385.

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 2012-09-07T14:59:00+00:00 Jan wrote:

An integer overflow, leading to buffer overflow flaw was found in the
way the implementation of strcoll() routine, used to compare two strings
based on the current locale, of glibc, the GNU libc libraries, performed
calculation of memory requirements / allocation, needed for storage of
the strings. If an application linked against glibc was missing an
application-level sanity checks for validity of strcoll() arguments and
accepted untrusted input, an attacker could use this flaw to cause the
particular application to crash or, potentially, execute arbitrary code
with the privileges of the user running the application.

Upstream bug report (including reproducer):
[1] http://sourceware.org/bugzilla/show_bug.cgi?id=14547

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1048203/comments/3


On 2012-09-07T15:31:44+00:00 Jan wrote:

CVE request:
[2] http://www.openwall.com/lists/oss-security/2012/09/07/9

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1048203/comments/4


On 2012-09-07T15:32:49+00:00 Jan wrote:

This issue affects the versions of the glibc package, as shipped with
Red Hat Enterprise Linux 5 and 6.

--

This issue affects the versions of the glibc package, as shipped with
Fedora release of 16 and 17. Please schedule an update (once there is
final upstream patch available).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1048203/comments/5


On 2012-09-07T15:34:15+00:00 Jan wrote:

Created glibc tracking bugs for this issue

Affects: fedora-all [bug 855399]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1048203/comments/6


On 2012-09-07T17:29:07+00:00 Jan wrote:

The CVE identifier of CVE-2012-4412 has been assigned to this issue:
http://www.openwall.com/lists/oss-security/2012/09/07/12

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1048203/comments/7


On 2013-08-22T00:49:36+00:00 Fedora wrote:

glibc-2.17-13.fc19 has been pushed to the Fedora 19 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1048203/comments/14


On 2013-09-05T09:05:48+00:00 Huzaifa wrote:

Statement:

This issue affects the version of glibc as shipped with Red Hat
Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated
this issue as having moderate security impact, a future update may
address this flaw.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1048203/comments/15


** Changed in: fedora
   Status: Unknown => Confirmed

** Changed in: fedora
   Importance: Unknown => Medium

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

Title:
  (CVE-2012-4412) glibc: strcoll() integer overflow leading to buffer
  overflow

Status in GLibC:
  Fix Released
Status in eglibc package in Ubuntu:
  Fix Released
Status in eglibc package in Debian:
  Fix Released
Status in Fedora:
  Confirmed
Status in Gentoo Linux:
  Fix Released

Bug description:
  An integer overflow, leading to buffer overflow flaw was found in the
  way the implementation of strcoll() routine, used to compare two
  strings based on the current locale, of glibc, the GNU libc libraries,
  performed calculation of memory requirements / allocation, needed for
  storage of the strings. If an application linked against glibc was
  missing an application-level sanity checks for validity of strcoll()
  arguments and accepted untrusted input, an attacker could use this
  flaw to cause the particular application to crash or, potentially,
  execute arbitrary code with the privileges of the user running the
  application.

  Upstream bug report (including reproducer):
  [1] http://sourceware.org/bugzilla/show_bug.cgi?id=14547

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

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

[Touch-packages] [Bug 1103747] Re: Totem could not startup.

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=858538.

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 2012-09-19T04:55:18+00:00 Adam wrote:

As per summary. Current F18 with updates-testing. Console output:

[adamw@adam Downloads]$ totem

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstpng.so': /lib64/libgstvideo-1.0.so.0:
undefined symbol: gst_buffer_map

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstdebug.so':
/usr/lib64/gstreamer-1.0/libgstdebug.so: undefined symbol:
gst_query_has_scheduling_mode_with_flags

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstspeex.so': /lib64/libgsttag-1.0.so.0:
undefined symbol: gst_query_has_scheduling_mode_with_flags

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstrtpmux.so': /lib64/libgstrtp-1.0.so.0:
undefined symbol: gst_buffer_map

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstossaudio.so': /lib64/libgsttag-1.0.so.0:
undefined symbol: gst_query_has_scheduling_mode_with_flags

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstsegmentclip.so':
/lib64/libgsttag-1.0.so.0: undefined symbol:
gst_query_has_scheduling_mode_with_flags

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstvideomixer.so':
/lib64/libgstvideo-1.0.so.0: undefined symbol: gst_buffer_map

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstequalizer.so':
/lib64/libgsttag-1.0.so.0: undefined symbol:
gst_query_has_scheduling_mode_with_flags

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstgdp.so':
/usr/lib64/gstreamer-1.0/libgstgdp.so: undefined symbol: gst_buffer_map

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstalaw.so': /lib64/libgsttag-1.0.so.0:
undefined symbol: gst_query_has_scheduling_mode_with_flags

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstadder.so': /lib64/libgsttag-1.0.so.0:
undefined symbol: gst_query_has_scheduling_mode_with_flags

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstlevel.so': /lib64/libgsttag-1.0.so.0:
undefined symbol: gst_query_has_scheduling_mode_with_flags

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstfragmented.so':
/usr/lib64/gstreamer-1.0/libgstfragmented.so: undefined symbol:
gst_buffer_map

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstsoundtouch.so':
/lib64/libgsttag-1.0.so.0: undefined symbol:
gst_query_has_scheduling_mode_with_flags

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstshm.so':
/usr/lib64/gstreamer-1.0/libgstshm.so: undefined symbol: gst_buffer_map

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstflac.so': /lib64/libgsttag-1.0.so.0:
undefined symbol: gst_query_has_scheduling_mode_with_flags

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstmultipart.so':
/usr/lib64/gstreamer-1.0/libgstmultipart.so: undefined symbol:
gst_buffer_get_size

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgsty4menc.so': /lib64/libgstvideo-1.0.so.0:
undefined symbol: gst_buffer_map

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstid3demux.so': /lib64/libgsttag-1.0.so.0:
undefined symbol: gst_query_has_scheduling_mode_with_flags

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstmpegtsdemux.so':
/lib64/libgsttag-1.0.so.0: undefined symbol:
gst_query_has_scheduling_mode_with_flags

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstsouphttpsrc.so':
/lib64/libgsttag-1.0.so.0: undefined symbol:
gst_query_has_scheduling_mode_with_flags

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstreamer-1.0/libgstisomp4.so': /lib64/libgsttag-1.0.so.0:
undefined symbol: gst_query_has_scheduling_mode_with_flags

(gst-plugin-scanner:31454): GStreamer-WARNING **: Failed to load plugin
'/usr/lib64/gstre

[Touch-packages] [Bug 1236510] Re: udisksd crashed with SIGSEGV in udisks_daemon_util_check_authorization_sync()

** Changed in: policykit-1 (Fedora)
   Status: Unknown => Fix Released

** Changed in: policykit-1 (Fedora)
   Importance: Unknown => Undecided

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

Title:
  udisksd crashed with SIGSEGV in
  udisks_daemon_util_check_authorization_sync()

Status in PolicyKit:
  Fix Released
Status in policykit-1 package in Ubuntu:
  Fix Released
Status in policykit-1 package in Fedora:
  Fix Released

Bug description:
  I didn't see anything strange.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: udisks2 2.1.0-4
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sun Oct  6 15:01:23 2013
  ExecutablePath: /usr/lib/udisks2/udisksd
  InstallationDate: Installed on 2013-10-02 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MachineType: Dell Inc. XPS 2720
  MarkForUpload: True
  ProcCmdline: /usr/lib/udisks2/udisksd --no-debug
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-11-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x4348a5:  mov(%rax),%ebp
   PC (0x004348a5) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ebp" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: udisks2
  StacktraceTop:
   ?? ()
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: udisksd crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 05R2TK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd03/28/2013:svnDellInc.:pnXPS2720:pvr00:rvnDellInc.:rn05R2TK:rvrA00:cvnDellInc.:ct13:cvr00:
  dmi.product.name: XPS 2720
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit/+bug/1236510/+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 1172692] Re: Please implement in-kernel suspend to both

Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=866487.

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 2012-10-15T13:40:20+00:00 Jaroslav wrote:

Description of problem:
After pm-suspend-hybrid the hibernation method doesn't return to previous state

Version-Release number of selected component (if applicable):
pm-utils-1.4.1-21.fc18.x86_64

How reproducible:
Always

Steps to Reproduce:
1. pm-hibernate
2. pm-suspend-hybrid
3. pm-hibernate
  
Actual results:
On step 3 hybrid suspend is done instead of hibernation.

Expected results:
The hibernation on step 3.

Additional info:

Reply at: https://bugs.launchpad.net/ubuntu/+source/pm-
utils/+bug/1172692/comments/1


On 2012-10-15T14:34:20+00:00 Jaroslav wrote:

Created attachment 627462
Proposed fix

Reply at: https://bugs.launchpad.net/ubuntu/+source/pm-
utils/+bug/1172692/comments/2


On 2012-10-17T14:46:01+00:00 Jaroslav wrote:

Updated upstream ticket:
https://bugs.freedesktop.org/show_bug.cgi?id=52572

Reply at: https://bugs.launchpad.net/ubuntu/+source/pm-
utils/+bug/1172692/comments/4


On 2012-10-17T14:55:43+00:00 Fedora wrote:

pm-utils-1.4.1-22.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/pm-utils-1.4.1-22.fc18

Reply at: https://bugs.launchpad.net/ubuntu/+source/pm-
utils/+bug/1172692/comments/5


On 2012-10-17T17:35:21+00:00 Fedora wrote:

Package pm-utils-1.4.1-22.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing pm-utils-1.4.1-22.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16321/pm-utils-1.4.1-22.fc18
then log in and leave karma (feedback).

Reply at: https://bugs.launchpad.net/ubuntu/+source/pm-
utils/+bug/1172692/comments/6


On 2012-12-20T16:22:09+00:00 Fedora wrote:

pm-utils-1.4.1-22.fc18 has been pushed to the Fedora 18 stable
repository.  If problems still persist, please make note of it in this
bug report.

Reply at: https://bugs.launchpad.net/ubuntu/+source/pm-
utils/+bug/1172692/comments/7


** Changed in: pm-utils (CentOS)
   Status: Unknown => Fix Released

** Changed in: pm-utils (CentOS)
   Importance: Unknown => Undecided

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

Title:
  Please implement in-kernel suspend to both

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project precise series:
  Fix Released
Status in pm-utils:
  Confirmed
Status in pm-utils package in Ubuntu:
  Fix Released
Status in pm-utils source package in Precise:
  Fix Released
Status in pm-utils source package in Quantal:
  Fix Released
Status in pm-utils source package in Trusty:
  Fix Released
Status in pm-utils package in CentOS:
  Fix Released

Bug description:
  From kernel-3.6 there is in-kernel support for suspend to both (AKA
  hybrid suspend). Working patches can be found at
  https://bugs.freedesktop.org/show_bug.cgi?id=52572 (or links).

  
  [Impact] 

   * Ubuntu 12.04 implements hybrid suspend differently. It suspends first and 
wakes up
 the computer for hibernation 15 minutes later. This is risky since the 
computer may be
 carried when the wakeup happens. The hard disk may experience physical 
shocks and get
 damaged.

   * Thus, it is desirable to have a real hybrid suspend implementation. 
In-kernel hybrid
 suspend has been supported since kernel 3.6+. pm-utils only needs a small 
patch to
 enable this feature. 

  
  [Test Case]

   * Ensure all Ubuntu 12.04 packages are up-to-date in the test environment.
 Install pm-utils 1.4.1-9ubuntu1
 Install linux-image-lts-raring

   * Reboot the computer with lts-raring kernel. Run the command: 
'pm-suspend-hybrid' from a 
 terminal. After the computer suspends, press the power button. It should 
be able to
 resume from suspension correctly. 

   * Run the command above again. After it suspends, remove and reconnect its 
power supply 
 (or its battery). Press the power button. It should be able to resume from 
hibernation
 correctly.

   * Reboot with the default 3.2 kerne

[Touch-packages] [Bug 1726309] Re: avahi-daemon[590]: chroot.c: open() failed: No such file or directory