date:20150518

[Desktop-packages] [Bug 1456452] Re: Works with stylus but not finger: HP Elitebook 2740P Tablet PC

2015-05-18 Thread whitis

Fix was to install this PPA:
https://launchpad.net/~onboard/+archive/ubuntu/stable
As suggested from this bug report
https://bugs.launchpad.net/onboard/+bug/1304573

However, that bug report suggests multitouch should work.   Specifically, that 
you should be able to hold the shift key while typing.  This does not work.  
The second touch may or may not cause the shift to be released, but in either 
case characters will not be typed.
This isn't a big issue for me.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1456452

Title:
  Works with stylus but not finger: HP Elitebook 2740P Tablet PC

Status in onboard package in Ubuntu:
  New

Bug description:
  As I will explain below, it appears that this bug is probably a
  manifestation of onboard using a completely incorrect algorithm for
  detecting button presses and releases that only accidentally works on
  legacy input devices and fails completely on a touchscreen.

  HP EliteBook 2740p is a convertible Tablet PC with a screen that can rotate 
from Laptop mode into tablet mode.   In tablet mode, the screen covers the 
keyboard and an on screen keyboard is a necessity.   This machine has 4+ input 
devices:
 - multitouch touch screen
 - stylus on screen
 - pointing stick
 - trackpad
 - also, 3D accelerometer which could theoretically be used to move cursor.
  These are without plugging in an external 3D space navigator, mouse, 
joystick, gamepad, eyemouse, etc.

  
  I can type with:
 - Touch screen stylus on screen
 - Touchpad (cumbersome and not at all useful in tablet mode)
 - pointing stick  (AKA erasor/clitoris/trackpoint(tm)/etc) (cumbersome and 
not at all useful in tablet mode)
 - (physical keyboard)
  I can not type using
- Finger on multitouch screen

  This is not a calibration issue.This is not a rotation issue; even
  though I have been playing with rotation, the screen  and input
  devices are currently unrotated and I can type in xvkbd or florence on
  screen keyboards with stylus or finger.

  onboard complet

   xsetwacom --list
  Serial Wacom Tablet WACf00e stylusid: 13  type: STYLUS
  Serial Wacom Tablet WACf00e eraserid: 15  type: ERASER
  Serial Wacom Tablet WACf00e touch id: 16  type: TOUCH# finger
  # Not shown: synaptics touchpad

  
  The following error message appears frequently in the terminal tab from which 
onboard was started (enough to render the tab unusable):  
  (onboard:5529): Gdk-CRITICAL **: gdk_device_get_axis_use: assertion 'index_ < 
device->axes->len' failed
  This error appears whether using stylus or finger (but not touchpad or stick) 
 and occurs more than once per key press as you hover.

  Note the following  potentially relevant general behavior differences
  between these 4 pointing devices.   With the three that work, the
  cursor tracks movement when not clicking/dragging.The one that
  doesn't warps the mouse directly to the point touched and generates
  events at that point and hides the mouse cursor since the mouse cursor
  can't track a raised finger.

  Default onboard preferences were used.

  xev shows Button Press, Motion Notify, and Button release events when 
touching with finger.   Similar with stylus.
  Differences, stylus sends motion notify updates when near screen, finger 
doesn't.
  Finger sends motion notify updates while being held still touching screen, 
stylus does not.

  Here are events captured with both buton and stylus:
  stylus:
  ButtonRelease event, serial 37, synthetic NO, window 0x561,
  root 0x80, subw 0x0, time 9012106, (110,108), root:(175,676),
  state 0x100, button 1, same_screen YES

  Finger:
  ButtonRelease event, serial 37, synthetic NO, window 0x561,
  root 0x80, subw 0x0, time 9065337, (96,85), root:(161,653),
  state 0x100, button 1, same_screen YES

  Another difference is the "state" in the motion notify events:
 Stylus:  0x0, 0x0, ... 0x100, 0x100, 0x100, ... 0x0, 0x0, 
 Finger:  0x100 events only.
erasor or touchpad: generate 0x0 events.

  This suggests that the bug in the software is to look at the "state"
  variable in motion notify events to determine presses and releases
  instead of using the correct algorithm of  looking at buttonpress and
  buttonrelease events.State can tell you the difference between a
  drag and a mere traverse but it is not a valid source of press/release
  event detection.

  The stylus can report its position when hovering over, but near, the
  glass.   The finger is only reported when it is actually pressing.
  Thus, there are no motion notify events when the finger is withdrawn.

  
  Multitouch trivia: double finger pan movements get converted to buttons 
4,5,6,7.In other words, they are converted to scrollwheel motion.   The 
finger motion is not reported as cursor motion.  pinch zoom in/out and

[Desktop-packages] [Bug 1456375] Re: Sync xserver-xorg-input-vmmouse 1:13.0.99-1 (main) from Debian unstable (main)

2015-05-18 Thread Daniel Holbach

This bug was fixed in the package xserver-xorg-input-vmmouse - 1:13.0.99-1
Sponsored for Artur Rona (ari-tczew)

---
xserver-xorg-input-vmmouse (1:13.0.99-1) unstable; urgency=medium

* Let uscan verify tarball signatures.
* New upstream release.
+ drop 01-enable-detect-in-kvm.diff, no longer necessary
* Bump debhelper compat level to 9.
* Remove Drew and Cyril from Uploaders.

-- Julien Cristau Sat, 02 May 2015 22:44:15
+0200

** Changed in: xserver-xorg-input-vmmouse (Ubuntu)
Status: New => Fix Released

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-vmmouse in Ubuntu.
https://bugs.launchpad.net/bugs/1456375

Title:
Sync xserver-xorg-input-vmmouse 1:13.0.99-1 (main) from Debian
unstable (main)

Status in xserver-xorg-input-vmmouse package in Ubuntu:
Fix Released

Bug description:
Please sync xserver-xorg-input-vmmouse 1:13.0.99-1 (main) from Debian
unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
* 0001-vmmouse_client.h-Include-xorg-server.h-before-xf86_O.patch:
Cherry-pick from upstream. Include xorg-server.h before xf86_OSproc.h to
get HAVE_STRNDUP set & resolve FTBFS.
* 0001-vmmouse_client.h-Include-xorg-server.h-before-xf86_O.patch:
Cherry-pick from upstream. Include xorg-server.h before xf86_OSproc.h to
get HAVE_STRNDUP set & resolve FTBFS.
* Rebuild to pick up new Xserver dependencies
* Rebuild to pick up new Xserver dependencies
* Rebuild for xorg 1.15 abi.
* Rebuild for xorg 1.15 abi.

0001-vmmouse_client.h-Include-xorg-server.h-before-xf86_O.patch is already
fixed upstream which is included now in Debian.
Bump Build-Depends is no needed anymore since in archive is much newer
version of binary xserver-xorg-dev.

Changelog entries since current wily version 1:13.0.0-1ubuntu1:

xserver-xorg-input-vmmouse (1:13.0.99-1) unstable; urgency=medium

* Let uscan verify tarball signatures.
* New upstream release.
+ drop 01-enable-detect-in-kvm.diff, no longer necessary
* Bump debhelper compat level to 9.
* Remove Drew and Cyril from Uploaders.

-- Julien Cristau Sat, 02 May 2015 22:44:15
+0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-vmmouse/+bug/1456375/+subscriptions

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

[Desktop-packages] [Bug 1456452] [NEW] Works with stylus but not finger: HP Elitebook 2740P Tablet PC

2015-05-18 Thread whitis

Public bug reported:

As I will explain below, it appears that this bug is probably a
manifestation of onboard using a completely incorrect algorithm for
detecting button presses and releases that only accidentally works on
legacy input devices and fails completely on a touchscreen.

HP EliteBook 2740p is a convertible Tablet PC with a screen that can rotate 
from Laptop mode into tablet mode.   In tablet mode, the screen covers the 
keyboard and an on screen keyboard is a necessity.   This machine has 4+ input 
devices:
   - multitouch touch screen
   - stylus on screen
   - pointing stick
   - trackpad
   - also, 3D accelerometer which could theoretically be used to move cursor.
These are without plugging in an external 3D space navigator, mouse, joystick, 
gamepad, eyemouse, etc.


I can type with:
   - Touch screen stylus on screen
   - Touchpad (cumbersome and not at all useful in tablet mode)
   - pointing stick  (AKA erasor/clitoris/trackpoint(tm)/etc) (cumbersome and 
not at all useful in tablet mode)
   - (physical keyboard)
I can not type using
  - Finger on multitouch screen

This is not a calibration issue.This is not a rotation issue; even
though I have been playing with rotation, the screen  and input devices
are currently unrotated and I can type in xvkbd or florence on screen
keyboards with stylus or finger.

onboard complet

 xsetwacom --list
Serial Wacom Tablet WACf00e stylus  id: 13  type: STYLUS
Serial Wacom Tablet WACf00e eraser  id: 15  type: ERASER
Serial Wacom Tablet WACf00e touch   id: 16  type: TOUCH# finger
# Not shown: synaptics touchpad


The following error message appears frequently in the terminal tab from which 
onboard was started (enough to render the tab unusable):  
(onboard:5529): Gdk-CRITICAL **: gdk_device_get_axis_use: assertion 'index_ < 
device->axes->len' failed
This error appears whether using stylus or finger (but not touchpad or stick)  
and occurs more than once per key press as you hover.

Note the following  potentially relevant general behavior differences
between these 4 pointing devices.   With the three that work, the cursor
tracks movement when not clicking/dragging.The one that doesn't
warps the mouse directly to the point touched and generates events at
that point and hides the mouse cursor since the mouse cursor can't track
a raised finger.

Default onboard preferences were used.

xev shows Button Press, Motion Notify, and Button release events when touching 
with finger.   Similar with stylus.
Differences, stylus sends motion notify updates when near screen, finger 
doesn't.
Finger sends motion notify updates while being held still touching screen, 
stylus does not.

Here are events captured with both buton and stylus:
stylus:
ButtonRelease event, serial 37, synthetic NO, window 0x561,
root 0x80, subw 0x0, time 9012106, (110,108), root:(175,676),
state 0x100, button 1, same_screen YES

Finger:
ButtonRelease event, serial 37, synthetic NO, window 0x561,
root 0x80, subw 0x0, time 9065337, (96,85), root:(161,653),
state 0x100, button 1, same_screen YES

Another difference is the "state" in the motion notify events:
   Stylus:  0x0, 0x0, ... 0x100, 0x100, 0x100, ... 0x0, 0x0, 
   Finger:  0x100 events only.
  erasor or touchpad: generate 0x0 events.

This suggests that the bug in the software is to look at the "state"
variable in motion notify events to determine presses and releases
instead of using the correct algorithm of  looking at buttonpress and
buttonrelease events.State can tell you the difference between a
drag and a mere traverse but it is not a valid source of press/release
event detection.

The stylus can report its position when hovering over, but near, the
glass.   The finger is only reported when it is actually pressing.
Thus, there are no motion notify events when the finger is withdrawn.


Multitouch trivia: double finger pan movements get converted to buttons 
4,5,6,7.In other words, they are converted to scrollwheel motion.   The 
finger motion is not reported as cursor motion.  pinch zoom in/out and rotate 
don't seem to be meaningfully reported.   You apparently have to register for 
xinput 2.2 events or something to get the position of each finger.


Note that in order to simulate this problem without a touchscreen device, one 
could use a second trackpad or wacom digitizer with a modified driver send only 
touchscreen compatible events.   Or write a program to pop up a window in which 
mouse movements (with button down only) are sent to another window as synthetic 
mouse movements.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: onboard 1.0.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 19 00:17:18 2015
InstallationDate: Installed on 2015-05-16 (2 days ago)
InstallationMedia: Ubuntu 14.04.2 L

[Desktop-packages] [Bug 1456449] [NEW] deprecated [SeatDefaults] section, use [Seat:*] instead

2015-05-18 Thread dino99

Public bug reported:

>From journalctl on Wily i386 installation:

lightdm[1016]: Configuration file 
/usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf contains a deprecated 
[SeatDefaults] section, use [Seat:*] instead
lightdm[1016]: Configuration file 
/usr/share/lightdm/lightdm.conf.d/90-nvidia.conf contains a deprecated 
[SeatDefaults] section, use [Seat:*] instead

note: the other 'conf' files already have the [Seat:*] section set; only
the 2 above still having the old [SeatDefaults] set. So this should  be
reported against something else than lightdm (maybe). The change is
easyly done manually indeed.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: lightdm 1.15.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.0.0-1.1-generic 4.0.1
Uname: Linux 4.0.0-1-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu2
Architecture: i386
CurrentDesktop: GNOME
Date: Tue May 19 07:12:12 2015
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 third-party-packages wily

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1456449

Title:
   deprecated [SeatDefaults] section, use [Seat:*] instead

Status in lightdm package in Ubuntu:
  New

Bug description:
  From journalctl on Wily i386 installation:

  lightdm[1016]: Configuration file 
/usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf contains a deprecated 
[SeatDefaults] section, use [Seat:*] instead
  lightdm[1016]: Configuration file 
/usr/share/lightdm/lightdm.conf.d/90-nvidia.conf contains a deprecated 
[SeatDefaults] section, use [Seat:*] instead

  note: the other 'conf' files already have the [Seat:*] section set;
  only the 2 above still having the old [SeatDefaults] set. So this
  should  be reported against something else than lightdm (maybe). The
  change is easyly done manually indeed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.15.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.0.0-1.1-generic 4.0.1
  Uname: Linux 4.0.0-1-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue May 19 07:12:12 2015
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1456445] Re: fglrx-core 2:15.200-0ubuntu4: fglrx-core kernel module failed to build

2015-05-18 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1456445

Title:
  fglrx-core 2:15.200-0ubuntu4: fglrx-core kernel module failed to build

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  DKMS make.log for fglrx-core-15.200 for kernel 4.0.4-040004-generic (x86_64)
  Tue May 19 00:32:40 EDT 2015
  /usr/sbin/dkms: line 74: cd: /var/lib/dkms/fglrx/15.200/build: No such file 
or directory
  AMD kernel module generator version 2.1
  doing Makefile based build for kernel 2.6.x and higher
  rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
  make -C /lib/modules/4.0.4-040004-generic/build 
SUBDIRS=/var/lib/dkms/fglrx-core/15.200/build/2.6.x modules
  make[1]: Entering directory '/usr/src/linux-headers-4.0.4-040004-generic'
CC [M]  /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.o
  /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c: In function 
‘kcl_mem_pat_setup’:
  /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:4499:9: error: 
implicit declaration of function ‘read_cr4’ 
[-Werror=implicit-function-declaration]
   cr4 = read_cr4();
   ^
  /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:4500:9: error: 
implicit declaration of function ‘write_cr4’ 
[-Werror=implicit-function-declaration]
   write_cr4(cr4 & ~X86_CR4_PGE);
   ^
  /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c: At top level:
  /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:6424:12: warning: 
‘KCL_fpu_save_init’ defined but not used [-Wunused-function]
   static int KCL_fpu_save_init(struct task_struct *tsk)
  ^
  cc1: some warnings being treated as errors
  scripts/Makefile.build:258: recipe for target 
'/var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.o' failed
  make[2]: *** [/var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.o] 
Error 1
  Makefile:1390: recipe for target 
'_module_/var/lib/dkms/fglrx-core/15.200/build/2.6.x' failed
  make[1]: *** [_module_/var/lib/dkms/fglrx-core/15.200/build/2.6.x] Error 2
  make[1]: Leaving directory '/usr/src/linux-headers-4.0.4-040004-generic'
  Makefile:88: recipe for target 'kmod_build' failed
  make: *** [kmod_build] Error 2
  build failed with return value 2

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fglrx-core 2:15.200-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 4.0.4-040004-generic
  Date: Tue May 19 00:32:43 2015
  DuplicateSignature: 
dkms:fglrx-core:2:15.200-0ubuntu4:/var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:4499:9:
 error: implicit declaration of function ‘read_cr4’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2015-05-01 (17 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  PackageVersion: 2:15.200-0ubuntu4
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: fglrx-installer
  SystemImageInfo:
   current build number: 0
   device name: ?
   channel: daily
   last update: Unknown
  Title: fglrx-core 2:15.200-0ubuntu4: fglrx-core kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1456445] [NEW] fglrx-core 2:15.200-0ubuntu4: fglrx-core kernel module failed to build

2015-05-18 Thread joseph wade

Public bug reported:

DKMS make.log for fglrx-core-15.200 for kernel 4.0.4-040004-generic (x86_64)
Tue May 19 00:32:40 EDT 2015
/usr/sbin/dkms: line 74: cd: /var/lib/dkms/fglrx/15.200/build: No such file or 
directory
AMD kernel module generator version 2.1
doing Makefile based build for kernel 2.6.x and higher
rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
make -C /lib/modules/4.0.4-040004-generic/build 
SUBDIRS=/var/lib/dkms/fglrx-core/15.200/build/2.6.x modules
make[1]: Entering directory '/usr/src/linux-headers-4.0.4-040004-generic'
  CC [M]  /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.o
/var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c: In function 
‘kcl_mem_pat_setup’:
/var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:4499:9: error: 
implicit declaration of function ‘read_cr4’ 
[-Werror=implicit-function-declaration]
 cr4 = read_cr4();
 ^
/var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:4500:9: error: 
implicit declaration of function ‘write_cr4’ 
[-Werror=implicit-function-declaration]
 write_cr4(cr4 & ~X86_CR4_PGE);
 ^
/var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c: At top level:
/var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:6424:12: warning: 
‘KCL_fpu_save_init’ defined but not used [-Wunused-function]
 static int KCL_fpu_save_init(struct task_struct *tsk)
^
cc1: some warnings being treated as errors
scripts/Makefile.build:258: recipe for target 
'/var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.o' failed
make[2]: *** [/var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.o] 
Error 1
Makefile:1390: recipe for target 
'_module_/var/lib/dkms/fglrx-core/15.200/build/2.6.x' failed
make[1]: *** [_module_/var/lib/dkms/fglrx-core/15.200/build/2.6.x] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.0.4-040004-generic'
Makefile:88: recipe for target 'kmod_build' failed
make: *** [kmod_build] Error 2
build failed with return value 2

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-core 2:15.200-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
DKMSKernelVersion: 4.0.4-040004-generic
Date: Tue May 19 00:32:43 2015
DuplicateSignature: 
dkms:fglrx-core:2:15.200-0ubuntu4:/var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:4499:9:
 error: implicit declaration of function ‘read_cr4’ 
[-Werror=implicit-function-declaration]
InstallationDate: Installed on 2015-05-01 (17 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
PackageVersion: 2:15.200-0ubuntu4
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4
SourcePackage: fglrx-installer
SystemImageInfo:
 current build number: 0
 device name: ?
 channel: daily
 last update: Unknown
Title: fglrx-core 2:15.200-0ubuntu4: fglrx-core kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1456445

Title:
  fglrx-core 2:15.200-0ubuntu4: fglrx-core kernel module failed to build

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  DKMS make.log for fglrx-core-15.200 for kernel 4.0.4-040004-generic (x86_64)
  Tue May 19 00:32:40 EDT 2015
  /usr/sbin/dkms: line 74: cd: /var/lib/dkms/fglrx/15.200/build: No such file 
or directory
  AMD kernel module generator version 2.1
  doing Makefile based build for kernel 2.6.x and higher
  rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
  make -C /lib/modules/4.0.4-040004-generic/build 
SUBDIRS=/var/lib/dkms/fglrx-core/15.200/build/2.6.x modules
  make[1]: Entering directory '/usr/src/linux-headers-4.0.4-040004-generic'
CC [M]  /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.o
  /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c: In function 
‘kcl_mem_pat_setup’:
  /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:4499:9: error: 
implicit declaration of function ‘read_cr4’ 
[-Werror=implicit-function-declaration]
   cr4 = read_cr4();
   ^
  /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:4500:9: error: 
implicit declaration of function ‘write_cr4’ 
[-Werror=implicit-function-declaration]
   write_cr4(cr4 & ~X86_CR4_PGE);
   ^
  /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c: At top level:
  /var/lib/dkms/fglrx-core/15.200/build/2.6.x/firegl_public.c:6424:12: warning: 
‘KCL_fpu_save_init’ defined but not used [-Wunused-function]
   static int KCL_fpu_save_init(struct task_struct *tsk)
  ^
  cc1: some warnings being treated as errors
  scripts/Makefile.build:258: recipe for

[Desktop-packages] [Bug 1434133] Re: package gimp-help-ko (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc-base/gimp-help-ko', which is also in package gimp-help-ja 2.8.2

2015-05-18 Thread Launchpad Bug Tracker

This bug was fixed in the package gimp-help - 2.8.2-0ubuntu2

---
gimp-help (2.8.2-0ubuntu2) wily; urgency=medium

  * debian/gimp-help-ja.doc-base: Typo corrected (LP: #1434133).

 -- Gunnar Hjalmarsson   Thu, 14 May 2015 04:12:00
+0200

** Changed in: gimp-help (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gimp-help in Ubuntu.
https://bugs.launchpad.net/bugs/1434133

Title:
  package gimp-help-ko (not installed) failed to install/upgrade: trying
  to overwrite '/usr/share/doc-base/gimp-help-ko', which is also in
  package gimp-help-ja 2.8.2-0ubuntu1

Status in One Hundred Papercuts:
  Confirmed
Status in gimp-help package in Ubuntu:
  Fix Released
Status in gimp-help source package in Vivid:
  Fix Committed

Bug description:
  vivid SRU request
  =

  [Impact]

  Package gimp-help-ko could not be installed under the situation that
  gimp-help-ja has been installed. The reverse is true as well. If you
  have both Korean and Japanese installed, Language Support keeps
  prompting about installing the package which failed.

  The clash is due to a typo in debian/gimp-help-ja.doc-base, which the
  patch fixes.

  [Test Case]

  Install Korean and Japanese from Language Support, and notice the
  installation failure for gimp-help-ko or gimp-help-ja.

  [Regression Potential]

  Very low.

  [Rest of the original description]

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: gimp-help-ko (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  Date: Thu Mar 19 23:31:39 2015
  DuplicateSignature: package:gimp-help-ko:(not installed):trying to overwrite 
'/usr/share/doc-base/gimp-help-ko', which is also in package gimp-help-ja 
2.8.2-0ubuntu1
  ErrorMessage: trying to overwrite '/usr/share/doc-base/gimp-help-ko', which 
is also in package gimp-help-ja 2.8.2-0ubuntu1
  InstallationDate: Installed on 2015-03-03 (16 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150301)
  SourcePackage: gimp-help
  Title: package gimp-help-ko (not installed) failed to install/upgrade: trying 
to overwrite '/usr/share/doc-base/gimp-help-ko', which is also in package 
gimp-help-ja 2.8.2-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 973932] Re: Disabling 'below' display does not reposition windows properly

2015-05-18 Thread Launchpad Bug Tracker

[Expired for Compiz because there has been no activity for 60 days.]

** Changed in: compiz
Status: Incomplete => Expired

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/973932

Title:
Disabling 'below' display does not reposition windows properly

Status in Compiz:
Expired
Status in compiz package in Ubuntu:
Expired

Bug description:
[Problem]
In a multihead config with one monitor above the other, if the lower monitor
is disabled the windows on that screen aren't moved to the still-active display.

[Test Case]
0. Attach laptop (LVDS1) to an external display (VGA1).
1. In the GNOME display properties applet, set the LVDS1 beneath VGA1.
2. Move to the lower left desktop (ctrl+alt+down)
3. Open one gnome terminal window on each monitor.
4. In the upper (VGA1) gnome terminal window type:
xrandr --output LVDS1 --off
(Alternatively, bring up the gnome display properties applet and shut the
laptop display off there)
5. With the LVDS turned off, count the number of gnome terminal windows
visible on VGA1
6. Using either xrandr or gnome, re-enable LVDS1 to the above/below
arrangement
7. With the LVDS re-enabled, count the number of gnome terminals visible on
VGA1 and LVDS1

Expected: 2, then 1/1
Actual:
Gnome Classic (No Effects): 2, then 1/1
Gnome Classic (With Effects): 2, then 1/1
Unity2D: 2, then 1/1
Unity: 1, then 1/1

Other findings...
A. On Unity, with LVDS1 off the missing gnome terminal window is
inaccessible. It can be recovered in various ways, but it's fairly confusing.

B. If step #2 is skipped and the test performed in the upper left
desktop, Unity will place the lower windows into the lower left
desktop.

C. On Unity, repeated testing of this seems to scramble the window
positions to some extent. The same effect does not appear to occur
with metacity; windows generally get placed back where they'd been
before.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.8.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic i686
ApportVersion: 2.0-0ubuntu4
Architecture: i386
CompizPlugins:
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom]
Date: Thu Apr 5 05:27:33 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2)
SourcePackage: unity
UpgradeStatus: Upgraded to precise on 2011-11-22 (135 days ago)

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

[Desktop-packages] [Bug 1361908] Re: Brother- DCP7065-DN printer not found

2015-05-18 Thread Launchpad Bug Tracker

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

** Changed in: sane-backends (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1361908

Title:
  Brother- DCP7065-DN printer not found

Status in sane-backends package in Ubuntu:
  Expired

Bug description:
  ubuntu 14.04 LTS  Lenovo H53564 bit
  I had reported, a few weeks ago that this printer was not offered on the sane 
list.
  Shortly after an update from ubuntu it did appear on the list was correctly 
identified and installed working correctly although without the scanner ability 
 "not found by any scan program.
  Recently calling for a print job brings up "printer not found" or "is printer 
connected"
   a delete and reinstall finds the printer OK but these errors continue.
   I have disconnected and reconnected printer wires powered off and on but 
problem remains.
   Initially I was able to install using the driver for 7085 and will try that 
again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: sane 1.0.14-9
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 26 16:03:53 2014
  InstallationDate: Installed on 2014-06-01 (86 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: sane-frontends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1366429] Re: no scanners reported by sane BR-7065DN

2015-05-18 Thread Launchpad Bug Tracker

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

** Changed in: sane-backends (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1366429

Title:
  no scanners reported by sane BR-7065DN

Status in sane-backends package in Ubuntu:
  Expired

Bug description:
  Printer found and operating properly;  No Scanners found

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: sane 1.0.14-9
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep  6 15:50:37 2014
  InstallationDate: Installed on 2014-06-01 (97 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: sane-frontends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 973932] Re: Disabling 'below' display does not reposition windows properly

2015-05-18 Thread Launchpad Bug Tracker

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

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