[Desktop-packages] [Bug 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all

2020-09-05 Thread Bogutsky Yaroslav
@bcanderson Try to add string 'options snd-hda-intel index=0 model
=headset-mode,asus-g73jw' to file /etc/modprobe.d/alsa-base.conf and
turn off your laptop. After power on sound should work correctly
everywhere. But, external mic disappear. :( I think sound + internal mic
is better then no sound at all.

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

Title:
  [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Built-in speakers work fine. When testing headphones in sound
  settings, The sound indicator bar in Pulse-Audio moves.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 17 12:05:57 2019
  InstallationDate: Installed on 2019-05-16 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  root   8064 F pulseaudio
galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL703VD.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL703VD
  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.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL703VD
  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/1829568/+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 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all

2020-09-04 Thread Bogutsky Yaroslav
The same issue on ASUS GL703GE, headphones doesn't work. It was working
some how on Ubuntu 18.04. Now I have installed Ubuntu 20 and this
headache back again. Anybody, please help.

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

Title:
  [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Built-in speakers work fine. When testing headphones in sound
  settings, The sound indicator bar in Pulse-Audio moves.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 17 12:05:57 2019
  InstallationDate: Installed on 2019-05-16 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  root   8064 F pulseaudio
galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL703VD.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL703VD
  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.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL703VD
  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/1829568/+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 1791981] Re: X Server session crash for "No space left on device"

2019-11-29 Thread Yaroslav Halchenko
Filed a question within nvidia forum:
https://devtalk.nvidia.com/default/topic/1066963/linux/if-laptop-lid-is-
closed-during-suspend-quot-failed-to-set-mode-no-space-left-on-device-
quot-upon-resume/post/5406357/  so far no closure

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

Title:
  X Server session crash for "No space left on device"

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Release: Ubuntu 18.04.1 LTS
  Package version: xserver-xorg: 1:7.7+19ubuntu7.1

  When my laptop resumes after suspend, the desktop session crashes and a new 
one is started. So each time I lose all open applications and unsaved data!
  The expected behavior would be obviously to restore the suspended session.

  I had a look through log files and found that Xorg.0.log ends with the
  following error lines:

  [  6004.019] (II) NVIDIA(0): Setting mode "NULL"
  [  6004.026] (EE) modeset(G0): failed to set mode: No space left on device
  [  6004.026] (EE) 
  Fatal server error:
  [  6004.026] (EE) EnterVT failed for gpu screen 0
  [  6004.027] (EE) 
  [  6004.027] (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  [  6004.027] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [  6004.027] (EE) 
  [  6004.065] (EE) Server terminated with error (1). Closing log file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+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 1791981] Re: X Server session crash for "No space left on device"

2019-11-20 Thread Yaroslav Halchenko
exactly the same issue as for Ben Echols on a Debian system with recent
nvidia drivers. Initially I suspected some racing within systemd, thus
filed (and later closed for now) https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=945158 which has supporting documentation.  Did
not find a workaround yet, besides making sure that laptop is fully
suspended before closing the lid.

Here is the relevant diff of journalctl output (with dates etc replaceD)
between two sessions (-good, +bad) which highlights the disconnect Ben
was talking about and then "out of cheese" error:

- lena gnome-shell[]: Window manager warning: Overwriting existing 
binding of keysym 60 with keysym 2f7259c9 (keycode 31).
+ lena systemd-logind[]: Lid closed.
+ lena gsd-color[]: failed to set screen _ICC_PROFILE: Failed to 
open file 
“/home/yoh/.local/share/icc/edid-aae8f9ad98a49dd9b5e20a8dfbf85689.icc”: 
Permission denied
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-0: 
disconnected
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-0: 
Internal DisplayPort
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-0: 
2660.0 MHz maximum pixel clock
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0):
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-1: 
disconnected
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-1: 
Internal DisplayPort
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-1: 
2660.0 MHz maximum pixel clock
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0):
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-2: 
disconnected
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-2: 
Internal TMDS
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-2: 
165.0 MHz maximum pixel clock
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0):
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-0: 
disconnected
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-0: 
Internal DisplayPort
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-0: 
2660.0 MHz maximum pixel clock
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0):
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-1: 
disconnected
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-1: 
Internal DisplayPort
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-1: 
2660.0 MHz maximum pixel clock
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0):
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-2: 
disconnected
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-2: 
Internal TMDS
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0): DFP-2: 
165.0 MHz maximum pixel clock
+ lena /usr/lib/gdm3/gdm-x-session[]: (--) NVIDIA(GPU-0):
  lena systemd[]: Reached target Sleep.
  lena systemd[]: Starting NVIDIA system suspend actions...
  lena suspend[]: nvidia-suspend.service
...
  lena acpid[]: 1 client rule loaded
+ lena /usr/lib/gdm3/gdm-x-session[]: (EE) modeset(G0): failed to 
set mode: No space left on device
+ lena /usr/lib/gdm3/gdm-x-session[]: (EE)
+ lena /usr/lib/gdm3/gdm-x-session[]: Fatal server error:
+ lena /usr/lib/gdm3/gdm-x-session[]: (EE) EnterVT failed for gpu 
screen 0
+ lena /usr/lib/gdm3/gdm-x-session[]: (EE)
+ lena /usr/lib/gdm3/gdm-x-session[]: Please consult the The X.Org 
Foundation support
+ lena /usr/lib/gdm3/gdm-x-session[]:  at http://wiki.x.org
+ lena /usr/lib/gdm3/gdm-x-session[]:  for help.
+ lena /usr/lib/gdm3/gdm-x-session[]: (EE) Please also check the log 
file at "/var/log/Xorg.1.log" for additional information.
+ lena /usr/lib/gdm3/gdm-x-session[]: (EE)
+ lena systemd[]: Starting Refresh fwupd metadata and update motd...
+ lena fwupdmgr[]: Fetching metadata 
https://cdn.fwupd.org/downloads/firmware.xml.gz
...
  lena avahi-daemon[]: Leaving mDNS multicast group on interface 
wlp82s0.IPv4 with address 10.31.123.112.
- lena /usr/lib/gdm3/gdm-x-session[]: (II) event1  - Sleep Button: 
is tagged by udev as: Keyboard
- lena /usr/lib/gdm3/gdm-x-session[]: (II) event1  - Sleep Button: 
device is a keyboard
+ lena /usr/lib/gdm3/gdm-x-session[]: (EE) Server terminated with 
error (1). Closing log file.
  lena avahi-daemon[]: Interface wlp82s0.IPv4 no longer relevant for 
mDNS.



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

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

Title:
  X Server session crash for "No space left on device"

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Release: Ubuntu 18.04.1 LTS
  Package version: xserver-xorg: 1:7.7+19ubuntu7.1

  When my laptop resumes after suspend, the desktop session crashes and a new 
one is started. So each time I lose all open applications and unsaved data!
  The expected 

[Desktop-packages] [Bug 1769137] Re: after 17.10->18.4 upgrade, the system did not start due to missing libGL.so.1 and libGLESv2.so.2 files

2018-05-04 Thread yaroslav
returning to bug discussion as suggested

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

Title:
  after 17.10->18.4 upgrade, the system did not start due to missing
  libGL.so.1 and libGLESv2.so.2 files

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  laptop: Dell XPS12
  More or less a standard Ubuntu 17.10 was upgraded to 18.4
  gnome-session-bin 3.28.1-0ubuntu2 could not find some libs.

  After the upgrade, the system did not start with the following error
  and blinking screen:

  May  4 14:21:02 Dell gnome-session[7085]: 
/usr/lib/gnome-session/gnome-session-check-accelerated-gl-helper: error while 
loading shared libraries: libGL.so.1: cannot open shared object file: No such 
file or directory
  May  4 14:21:02 Dell gnome-session[7085]: gnome-session-check-accelerated: GL 
Helper exited with code 32512
  May  4 14:21:02 Dell gnome-session[7085]: 
/usr/lib/gnome-session/gnome-session-check-accelerated-gles-helper: error while 
loading shared libraries: libGLESv2.so.2: cannot open shared object file: No 
such file or directory
  May  4 14:21:02 Dell gnome-session[7085]: gnome-session-check-accelerated: 
GLES Helper exited with code 32512
  May  4 14:21:02 Dell at-spi-bus-launcher[3520]: dbus-daemon[3525]: 
Successfully activated service 'org.a11y.atspi.Registry'

  To fix the issue, I had to SSH to this laptop (I was brought to the
  load screen from other TTYs every 2 seconds) and make symlinks:

  root@Dell:~# #ln -s /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 
/usr/lib/x86_64-linux-gnu/libGL.so.1
  root@Yarik-Dell:~# #ln -s /usr/lib/x86_64-linux-gnu/mesa/libGLESv2.so.2 
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2

  missing dependency?

  other info from the laptop:

  root@Yarik-Dell:~# lspci | grep -i VGA
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)

  root@Dell:~# ldd 
/usr/lib/gnome-session/gnome-session-check-accelerated-gl-helper | egrep 
"libGL.so.1|libGLESv2.so.2"
libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1 (0x7ffac7ca8000)

  
  root@Dell:~# apt-file search /usr/lib/x86_64-linux-gnu/libGL.so.1
  libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1
  libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1.0.0
  nvidia-340: /usr/lib/x86_64-linux-gnu/libGL.so.1
  root@Dell:~# apt-cache policy nvidia-340
  nvidia-340:
Installed: (none)
Candidate: 340.106-0ubuntu3
Version table:
   340.106-0ubuntu3 500
  500 http://at.archive.ubuntu.com/ubuntu bionic/restricted amd64 
Packages
  root@Dell:~# apt-cache policy libgl1
  libgl1:
Installed: (none)
Candidate: 1.0.0-2ubuntu2
Version table:
   1.0.0-2ubuntu2 500
  500 http://at.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session-bin 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 14:51:33 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-15 (323 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1769137/+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 1769137] Re: after 17.10->18.4 upgrade, the system did not start due to missing libGL.so.1 and libGLESv2.so.2 files

2018-05-04 Thread yaroslav
I am not sure if this a bug and if yes, then in which package. Better to
discuss first.

** Changed in: gnome-session (Ubuntu)
   Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/gnome-session/+question/668590

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

Title:
  after 17.10->18.4 upgrade, the system did not start due to missing
  libGL.so.1 and libGLESv2.so.2 files

Status in gnome-session package in Ubuntu:
  Invalid

Bug description:
  laptop: Dell XPS12
  More or less a standard Ubuntu 17.10 was upgraded to 18.4
  gnome-session-bin 3.28.1-0ubuntu2 could not find some libs.

  After the upgrade, the system did not start with the following error
  and blinking screen:

  May  4 14:21:02 Dell gnome-session[7085]: 
/usr/lib/gnome-session/gnome-session-check-accelerated-gl-helper: error while 
loading shared libraries: libGL.so.1: cannot open shared object file: No such 
file or directory
  May  4 14:21:02 Dell gnome-session[7085]: gnome-session-check-accelerated: GL 
Helper exited with code 32512
  May  4 14:21:02 Dell gnome-session[7085]: 
/usr/lib/gnome-session/gnome-session-check-accelerated-gles-helper: error while 
loading shared libraries: libGLESv2.so.2: cannot open shared object file: No 
such file or directory
  May  4 14:21:02 Dell gnome-session[7085]: gnome-session-check-accelerated: 
GLES Helper exited with code 32512
  May  4 14:21:02 Dell at-spi-bus-launcher[3520]: dbus-daemon[3525]: 
Successfully activated service 'org.a11y.atspi.Registry'

  To fix the issue, I had to SSH to this laptop (I was brought to the
  load screen from other TTYs every 2 seconds) and make symlinks:

  root@Dell:~# #ln -s /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 
/usr/lib/x86_64-linux-gnu/libGL.so.1
  root@Yarik-Dell:~# #ln -s /usr/lib/x86_64-linux-gnu/mesa/libGLESv2.so.2 
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2

  missing dependency?

  other info from the laptop:

  root@Yarik-Dell:~# lspci | grep -i VGA
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)

  root@Dell:~# ldd 
/usr/lib/gnome-session/gnome-session-check-accelerated-gl-helper | egrep 
"libGL.so.1|libGLESv2.so.2"
libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1 (0x7ffac7ca8000)

  
  root@Dell:~# apt-file search /usr/lib/x86_64-linux-gnu/libGL.so.1
  libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1
  libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1.0.0
  nvidia-340: /usr/lib/x86_64-linux-gnu/libGL.so.1
  root@Dell:~# apt-cache policy nvidia-340
  nvidia-340:
Installed: (none)
Candidate: 340.106-0ubuntu3
Version table:
   340.106-0ubuntu3 500
  500 http://at.archive.ubuntu.com/ubuntu bionic/restricted amd64 
Packages
  root@Dell:~# apt-cache policy libgl1
  libgl1:
Installed: (none)
Candidate: 1.0.0-2ubuntu2
Version table:
   1.0.0-2ubuntu2 500
  500 http://at.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session-bin 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 14:51:33 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-15 (323 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1769137/+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 1769137] [NEW] after 17.10->18.4 upgrade, the system did not start due to missing libGL.so.1 and libGLESv2.so.2 files

2018-05-04 Thread yaroslav
Public bug reported:

laptop: Dell XPS12
More or less a standard Ubuntu 17.10 was upgraded to 18.4
gnome-session-bin 3.28.1-0ubuntu2 could not find some libs.

After the upgrade, the system did not start with the following error and
blinking screen:

May  4 14:21:02 Dell gnome-session[7085]: 
/usr/lib/gnome-session/gnome-session-check-accelerated-gl-helper: error while 
loading shared libraries: libGL.so.1: cannot open shared object file: No such 
file or directory
May  4 14:21:02 Dell gnome-session[7085]: gnome-session-check-accelerated: GL 
Helper exited with code 32512
May  4 14:21:02 Dell gnome-session[7085]: 
/usr/lib/gnome-session/gnome-session-check-accelerated-gles-helper: error while 
loading shared libraries: libGLESv2.so.2: cannot open shared object file: No 
such file or directory
May  4 14:21:02 Dell gnome-session[7085]: gnome-session-check-accelerated: GLES 
Helper exited with code 32512
May  4 14:21:02 Dell at-spi-bus-launcher[3520]: dbus-daemon[3525]: Successfully 
activated service 'org.a11y.atspi.Registry'

To fix the issue, I had to SSH to this laptop (I was brought to the load
screen from other TTYs every 2 seconds) and make symlinks:

root@Dell:~# #ln -s /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 
/usr/lib/x86_64-linux-gnu/libGL.so.1
root@Yarik-Dell:~# #ln -s /usr/lib/x86_64-linux-gnu/mesa/libGLESv2.so.2 
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2

missing dependency?

other info from the laptop:

root@Yarik-Dell:~# lspci | grep -i VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)

root@Dell:~# ldd 
/usr/lib/gnome-session/gnome-session-check-accelerated-gl-helper | egrep 
"libGL.so.1|libGLESv2.so.2"
libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1 (0x7ffac7ca8000)


root@Dell:~# apt-file search /usr/lib/x86_64-linux-gnu/libGL.so.1
libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1
libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1.0.0
nvidia-340: /usr/lib/x86_64-linux-gnu/libGL.so.1
root@Dell:~# apt-cache policy nvidia-340
nvidia-340:
  Installed: (none)
  Candidate: 340.106-0ubuntu3
  Version table:
 340.106-0ubuntu3 500
500 http://at.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages
root@Dell:~# apt-cache policy libgl1
libgl1:
  Installed: (none)
  Candidate: 1.0.0-2ubuntu2
  Version table:
 1.0.0-2ubuntu2 500
500 http://at.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-session-bin 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May  4 14:51:33 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-06-15 (323 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-session
UpgradeStatus: Upgraded to bionic on 2018-05-04 (0 days ago)

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  after 17.10->18.4 upgrade, the system did not start due to missing
  libGL.so.1 and libGLESv2.so.2 files

Status in gnome-session package in Ubuntu:
  New

Bug description:
  laptop: Dell XPS12
  More or less a standard Ubuntu 17.10 was upgraded to 18.4
  gnome-session-bin 3.28.1-0ubuntu2 could not find some libs.

  After the upgrade, the system did not start with the following error
  and blinking screen:

  May  4 14:21:02 Dell gnome-session[7085]: 
/usr/lib/gnome-session/gnome-session-check-accelerated-gl-helper: error while 
loading shared libraries: libGL.so.1: cannot open shared object file: No such 
file or directory
  May  4 14:21:02 Dell gnome-session[7085]: gnome-session-check-accelerated: GL 
Helper exited with code 32512
  May  4 14:21:02 Dell gnome-session[7085]: 
/usr/lib/gnome-session/gnome-session-check-accelerated-gles-helper: error while 
loading shared libraries: libGLESv2.so.2: cannot open shared object file: No 
such file or directory
  May  4 14:21:02 Dell gnome-session[7085]: gnome-session-check-accelerated: 
GLES Helper exited with code 32512
  May  4 14:21:02 Dell at-spi-bus-launcher[3520]: dbus-daemon[3525]: 
Successfully activated service 'org.a11y.atspi.Registry'

  To fix the issue, I had to SSH to this laptop (I was brought to the
  load screen from other TTYs every 2 seconds) and make symlinks:

  root@Dell:~# #ln -s /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 
/usr/lib/x86_64-linux-gnu/libGL.so.1
  root@Yarik-Dell:~# #ln -s /usr/lib/x86_64-linux-gnu/mesa/libGLESv2.so.2 
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2

  missing dependency?

  other info from the laptop:

  root@Yarik-Dell:~# lspci | grep -i VGA
  00:02.0 VGA compatible controller: Intel 

[Desktop-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

2017-04-07 Thread Yaroslav
to David Ford (djfordz-q) thank for help, but it doesn't make external mic to 
work
I've setup option:
`options snd-hda-intel model=laptop-dmic,headset-mic`
and reboot notebook - doesn't help, internal working, external not.

Searching an internet, help to find a solution that works.
So then I've install "alsa-tools-gui" launch "HDAJackRetask", select codec 
ALC256, 
checked "Show unconnected pins" then check pin ID: 0x19 and select "Microphone" 
then hit "Apply now".
Started pavucontrol for checks and it work. 
Both of them built-in, and external headset microphone works now.
So launch "HDAJackRetask" and make a permanent change, hit "Install boot 
override"
After reboot it work for all users on notebook.

P.S. As for other models and codecs it may be other pins number in
"HDAJackRetask" utility.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  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/1596381/+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 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

2017-04-04 Thread Yaroslav
Hello everyone.
Notebook ASUS X541s, audio chipset ALC256, audio jack output combined with 
microphone input . Kubuntu 16.04.2 LTS. Have a sound output, but microphone not 
working. 
Solution in post #8 help me bring to work built-in microphone. But when I'm 
switch to external headset microphone, it doesn't work, it say microphone 
(Unplugged). 
How can I start using external headset microphone? (Headset tested itself on 
other PC and it's working fine).
Thanks for any help.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  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/1596381/+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 1303508] Re: privacy settings: remove history datetimepicker not working

2016-06-27 Thread Yaroslav Chagovets
I confirm that the issue affects Ubuntu 16.04. Dear Ubuntu maintainers,
please review the patch above.

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

Title:
  privacy settings: remove history datetimepicker not working

Status in activity-log-manager package in Ubuntu:
  In Progress

Bug description:
  Setting a custom date is not possible because datetimepicker does not
  react on input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1303508/+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 1078272] Re: It's impossible to configure multiple touchscreens using evdev

2014-11-21 Thread Yaroslav Sterkhov
It is still a problem, partially.It  is possible to use coordinate
transformation matrix property (TransformationMatrix option in
InputClass section) to assign touchscreens to different displays, but
not to different X screens. But, unless system is SLI , or , or Mosaic
enabled - that is , it is supported by GPU and chipset -and that is
NVIDIA specific, then even with xinerama enabled every GPU is separate X
display. In that case , e.g, on x server :0 with screens :0.0, :0.1 and
0:0.2  even with proper matrix, mouse cursor simply jumps to bottom edge
of screen, if coordinates do not correspond to to :0.0 - i suspect it is
a bug on evdev side.

realistically that makes multiple touchscreen configuration possible
only with NVIDIA cards (twinview joins displays into one X screen), and
in case of 3 or more displays - only with SLI or BaseMosaic

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

Title:
  It's impossible to configure multiple touchscreens using evdev

Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Expired

Bug description:
  We're trying to get a multi-touchscreen (multiple touchscreens not
  multi touch) setup working with the evdev driver in Natty Narwhal.
  Basically, the touchscreens are configured and working except that the
  mapping to the correct X screen is wrong. We set up 5 touchscreens in
  a row (Xorg ServerLayout RightOf) and their corresponding
  touchscreen inputdevices. Using xinput we are able to create a pointer
  for each of the touchscreens. The following is observed then: When
  touching any screen, the resulting movement of the pointer is only
  displayed on the first X screen (there are 5 pointers visible then on
  this screen.). This is not at all the desired behavior. We would like
  to attach a touchscreen to a specific X screen.

  Unfortunately, we found no way to tell the evdev driver to map a
  InputDevice to a X screen. Older versions of the driver (1.1.2)
  provided an option AbsoluteScreen (see
  http://manpages.ubuntu.com/manpages/dapper/en/man4/evdev.4.html)  but
  the latest version hasn't anything like this. I know that the evtouch
  driver would provide a ScreenNo option, however evtouch is not
  available for Natty Narwhal. We also experimented with the Xorg
  coordinate transformation matrix, but with the result that the mouse
  movements where still on the first X screen.

  So my question is:
  How do I tell the evdev driver to map an InputDevice to a specific X screen? 
Is there an option line in xorg.conf or is there any method via xinput?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1078272/+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 1395195] [NEW] Evdev doesn't map touch coordinates properly to secondary X screens

2014-11-21 Thread Yaroslav Sterkhov
Public bug reported:

On system with several X screens on same server, e.g.  several GPU cards that 
doesn't support functions similar to TwinView or BaseMosaic of NVIDIA, evdev 
doesn't map coordinates of touch events properly.
For example if  on server :0 there are  two displays  connected to one GPU as 
screen 0 (:0.0) , using TwinView,  and third connected to second GPU as screen 
1 (:0.1) set below of screen 0.

1st display  1920x1080 +0+0
2nd: 1920x1080 +0+1080
3nd: 1920x1080 +0+2160

All three are touchscreens, mapped with coordinate transformation
matrices, like this:

Section InputClass
Identifier  Touch1
MatchIsTouchscreen  on
MatchTagctouch-1
Option  TransformationMatrix  1 0 0 0 0. 0 0 0 1
Driver  evdev
EndSection

Section InputClass
Identifier  Touch2
MatchIsTouchscreen  on
MatchTagctouch-2
Option  TransformationMatrix  1 0 0 0 0.3334 0. 0 0 1
Driver  evdev
EndSection

Section InputClass
Identifier  Touch3
MatchIsTouchscreen  on
MatchTagctouch-3
Option  TransformationMatrix  1 0 0 0 0. 0.6667 0 0 1
Driver  evdev
EndSection

Two upper touchscreen work as intended, if I touch third,  cursor got
placed on bottom edge of display. Same hardware, displays arranged in
horizontal pattern from left to right, result in cursor clinging  on
rightmost edge. Relative coordinates pointer device, like mouse, work
perfectly with no err. It loos like evdev reports global coordinates
instead of calculating coordinates relative to origin of second X
screen, and they get restrained by actual size of that screen. I.e. it
reported {x=500, y=2200}  instead of {x=500, y =40}.

 I just realized that could confirm that theory, by attaching two
displays to second GPU, while having only one connected to first . In
that case  if I'm right,  while touching second screen , cursor appeared
on corresponding spot of third one. Can't check it until next Monday
now.

** Affects: xserver-xorg-input-evdev (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Evdev doesn't map touch coordinates properly to secondary X screens

Status in “xserver-xorg-input-evdev” package in Ubuntu:
  New

Bug description:
  On system with several X screens on same server, e.g.  several GPU cards that 
doesn't support functions similar to TwinView or BaseMosaic of NVIDIA, evdev 
doesn't map coordinates of touch events properly.
  For example if  on server :0 there are  two displays  connected to one GPU as 
screen 0 (:0.0) , using TwinView,  and third connected to second GPU as screen 
1 (:0.1) set below of screen 0.

  1st display  1920x1080 +0+0
  2nd: 1920x1080 +0+1080
  3nd: 1920x1080 +0+2160

  All three are touchscreens, mapped with coordinate transformation
  matrices, like this:

  Section InputClass
Identifier  Touch1
MatchIsTouchscreen  on
MatchTagctouch-1
Option  TransformationMatrix  1 0 0 0 0. 0 0 0 1
Driver  evdev
  EndSection

  Section InputClass
Identifier  Touch2
MatchIsTouchscreen  on
MatchTagctouch-2
Option  TransformationMatrix  1 0 0 0 0.3334 0. 0 0 1
Driver  evdev
  EndSection

  Section InputClass
Identifier  Touch3
MatchIsTouchscreen  on
MatchTagctouch-3
Option  TransformationMatrix  1 0 0 0 0. 0.6667 0 0 1
Driver  evdev
  EndSection

  Two upper touchscreen work as intended, if I touch third,  cursor got
  placed on bottom edge of display. Same hardware, displays arranged in
  horizontal pattern from left to right, result in cursor clinging  on
  rightmost edge. Relative coordinates pointer device, like mouse, work
  perfectly with no err. It loos like evdev reports global coordinates
  instead of calculating coordinates relative to origin of second X
  screen, and they get restrained by actual size of that screen. I.e. it
  reported {x=500, y=2200}  instead of {x=500, y =40}.

   I just realized that could confirm that theory, by attaching two
  displays to second GPU, while having only one connected to first . In
  that case  if I'm right,  while touching second screen , cursor
  appeared on corresponding spot of third one. Can't check it until next
  Monday now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1395195/+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 1016004] Re: gnome-terminal broken in 12.04 on ThinkPad T61 with Nvidia graphics

2013-10-25 Thread Yaroslav Zaremba
same for me on Dell Vostro 3300 with NVidia card and proprietary drivers
(319.32)

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

Title:
  gnome-terminal broken in 12.04 on ThinkPad T61 with Nvidia graphics

Status in “gnome-terminal” package in Ubuntu:
  Confirmed

Bug description:
  We are running Gnome 3 on 12.04.
  The gnome terminal output is kind of broken. When reaching the last line it 
somehow begins acting strange.
  For example typing ls you don't get any output unless you press Enter again. 
Lines are overlapping and stuff like that.
  Sometimes Ctrl+l helps, sometimes not.
  Difficult to describe but the shell is not usable in this state.
  I installed an alternative shell (terminator) to circumvent the problem and 
it seems to be working fine.

  Package version is 3.4.1.1-0ubuntu1

  Also it affects other applications, for instance emacs
  (/usr/bin/emacs23-x).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1016004/+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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade

2013-05-11 Thread Sydoruk Yaroslav
Solved in Ubuntu 13.04
Need install:
AMD Catalyst™ 13.4 Proprietary Linux x86 Display Driver from ati.com
and 
http://launchpadlibrarian.net/111621157/xserver-xorg-video-intel_2.20.2-1ubuntu1_amd64.deb
If install xserver-xorg-video-intel_2:2.21.6-0ubuntu4_amd64.deb X server crashes

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

Title:
  Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx
  upgrade

Status in X.org xf86-video-intel:
  Won't Fix
Status in “fglrx-installer” package in Ubuntu:
  In Progress
Status in “fglrx-installer-updates” package in Ubuntu:
  Triaged
Status in “fglrx-installer” source package in Quantal:
  Confirmed
Status in “fglrx-installer-updates” source package in Quantal:
  Triaged
Status in “xserver-xorg-video-intel” package in openSUSE:
  In Progress

Bug description:
  [Impact]

   * Hybrid systems with ATI/intel GPUs using fglrx get a segmentation
  fault in X when using 12.10. In stock 12.04.1 these systems were
  working fine.

   * This bug represents a severe regression from precise to quantal,
  since is crashing on startup

   * The proposed patch updates the driver to version 13.2beta3 of
  upstream which seems to resolve this issue

  [Test Case]

   * Get an hybrid ATI/intel system.
     Install quantal: The system should boot fine
     Install the proprietary fglrx package and reboot: The X server crashes on 
startup

  [Regression Potential]

   * This solution does not need any change on the intel driver (as a previous 
workaround needed).
   * No regressions have been reported so far using this most recent fglrx 
upstream, by the people affected by this bug

  ==

  After installing the latest fglrx-updates package on Ubuntu 12.10
  (fglrx-updates_9.000-0ubuntu3_amd64) I have the same issue that was
  present before AMD fixed switchable graphics on PowerXpress 4.0 cards
  (such as my HD 6470M coupled with the intel HD Graphics 3000 of my
  intel Core i5-2430M). The X server has a segmentation fault and the
  low graphics mode is activated.

  WORKAROUND: Follow carefully the instructions here:
  https://help.ubuntu.com/community/BinaryDriverHowto/ATI#WORKAROUND

  As per Nick Andrik, this is a version regression of xserver-xorg-
  video-intel from 2.20.2 (working and in below mentioned PPA) and
  2.20.3. The regression commit is
  http://cgit.freedesktop.org/xorg/driver/xf86-video-
  intel/commit/?id=05dcc5f1699ba90fc14c50882e8d4be89bc4a4f9 .

  Upstream fglrx has published a new version ( 13.1 ) of the driver
  which seems to solve this issue. No need to revert the commit in the
  Intel driver any more.

  ATTENTION:
  1. If you choose the integrated GPU (via Catalyst or via amdconfig --px-igpu) 
and your X server crashes on startup, then your are probably affected by this 
bug:
  https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1088220

  2. If your system includes an old ATI GPU card (Radeon HD 2x00 3x00 4x00) 
which is not supported any more by fglrx drivers, then probably you suffer from 
this bug:
  https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1058040
  Subscribe and comment there please.

  If the X server loads (so you see no low graphics mode window) but you get no 
menu bars, window decorations, etc, then press Ctrl+Shift+T to open a terminal, 
write in there:
  unity --replace 
  and post a comment with the result.

  The logs from the intial bug report follow:

  Here is the Xorg log:
  [20.924]
  X.Org X Server 1.13.0
  Release Date: 2012-09-05
  [20.924] X Protocol Version 11, Revision 0
  [20.924] Build Operating System: Linux 3.2.0-30-generic x86_64 Ubuntu
  [20.924] Current Operating System: Linux marco-HP-Pavilion-g6-Notebook-PC 
3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64
  [20.924] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=5374f779-2ae8-4842-a390-e21317364c6c ro quiet splash vt.handoff=7
  [20.924] Build Date: 08 October 2012  03:34:01PM
  [20.924] xorg-server 2:1.13.0-0ubuntu6 (For technical support please see 
http://www.ubuntu.com/support)
  [20.924] Current version of pixman: 0.26.0
  [20.924]  Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [20.924] Markers: (--) probed, (**) from config file, (==) default 
setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [20.924] (==) Log file: /var/log/Xorg.0.log, Time: Fri Oct 19 02:42:21 
2012
  [20.924] (==) Using config file: /etc/X11/xorg.conf
  [20.924] (==) Using system config directory /usr/share/X11/xorg.conf.d
  [20.924] (==) ServerLayout aticonfig Layout
  [20.924] (**) |--Screen aticonfig-Screen[0]-0 (0)
  [20.924] (**) |   |--Monitor aticonfig-Monitor[0]-0
 

[Desktop-packages] [Bug 692039] Re: New memory function not clear

2013-04-26 Thread Yaroslav
It would be great if memory registers back into gcalctool

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

Title:
  New memory function not clear

Status in “gcalctool” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: gcalctool

  Up until 10.10 the built-in calculator had a memory facility which was better 
than the one in Windows, with multiple registers. Now the whole thing seems to 
have gone, and it's not just me, there are at least three other sufferers on 
this thread:
  http://ubuntuforums.org/showthread.php?p=10226158

  This makes the whole thing almost useless as a simple calculator. Is
  it a deliberate crippling of the app, an accidental regression or a
  bug that only affects certain people?

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: gcalctool 5.32.0-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
  Uname: Linux 2.6.35-23-generic i686
  Architecture: i386
  Date: Sat Dec 18 21:47:21 2010
  ExecutablePath: /usr/bin/gcalctool
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: gcalctool

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcalctool/+bug/692039/+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 1005321] Re: Several pointing device related problems occur when a touchscreen is installed

2013-01-31 Thread Yaroslav Sterkhov
https://launchpad.net/ubuntu/+source/xorg-server/2:1.13.0-0ubuntu6.1/+build/4015022
last build still too old, so seem it doesn't contain this? e.t.a. for update?

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

Title:
  Several pointing device related problems occur when a touchscreen is
  installed

Status in “xorg-server” package in Ubuntu:
  Triaged

Bug description:
  I'm running Kubuntu 12.04 64 bits on a Dell Inspiron One 2320, which
  has a touchscreen. Whenever the touchscreen is active, several weird
  problems related to the pointing device show up. Some examples:

  1. In Libreoffice Calc, if I hover the mouse over the zoom control bar
  in the bottom right corner of Calc's window, the mouse grabs the zoom
  control by itself, without me clicking any button. If I move the mouse
  left and right, without ever touching its buttons, it drags the zoom
  control left and right.

  2. In Libreoffice Calc, if I left-click a tab other than the currently
  selected one, the new tab is selected as expected, but the mouse
  behaves as if the clicked button had stuck. When I move the mouse
  after selecting another tab, the mouse cursor changes to the arrow
  with the little rectangle, as if it was dragging a cell.

  3. In Chromium, if I right-click a link and left-click Open link in
  new tab,  the mouse behaves as if the left-click stuck. When I move
  the mouse after opening the new tab, the mouse cursor changes to the
  little hand grabbing a sheet, as if I was moving the clicked link.

  4. In Chromium, if I middle-click a link to open it in a new tab and
  then left-click the newly opened tab, the mouse cursor changes to the
  cross with arrowed points (the move window cursor) and the window is
  restored, as if I had started to drag it and let it go right after.

  5. In Handbrake, when a dialog opens, hovering the mouse over its text
  without pressing any button selects the text.

  Until now I haven't noticed similar problems with native KDE
  applications, except that in Kontact/KMail the mouse cursor image does
  not change according to the context (arrow cursor, text insertion
  cursor, etc.).

  Besides, there are several other problems related to the touchscreen
  itself:

  1. I can drag objects around the screen using the touchscreen, but I
  can't click anywhere. When I tap the touchscreen to click, the mouse
  cursor goes under my finger, but as long as I stop touching the cursor
  goes to some random place of the screen and the click is not
  registered.

  2. While I'm dragging objects using the touchscreen or while I'm
  drawing in Gimp or Kolourpaint using the touchscreen, the mouse cursor
  keeps jumping down and going back to where my finger is. For example,
  if I'm drawing an horizontal line with my finger, what I really get on
  the screen is almost a filled in rectangle, because as I slide the
  finger to one side, the mouse jumps down drawing a vertical line and
  then goes back to my finger and keeps doing that while I'm sliding my
  finger horizontally. I get several vertical lines very close to each
  other. If I'm dragging a window horizontally, it keeps jumping down
  and up again while I'm sliding the finger horizontally on the
  touchscreen.

  3. Multitouch does not work

  After I got these results, I installed the following packages:
  utouch and its dependencies
  xinput-calibrator

  They made no difference at all.

  I then tried the following package:
  xserver-xorg-input-tslib

  After a reboot, this package disabled the touchscreen completely (?!)
  and that was how I found out that the problems with Libreoffice,
  Chromium, Handbrake and Kontact/KMail mentioned above were related to
  the touchscreen. All problems were gone, but no touchscreen either.
  Before I installed this package, xinput --list returned one device
  named Quanta OpticalTouchScreen. After I installed the package,
  xinput --list shows two devices with exactly this name and the
  touchscreen stopped responding.

  Then I removed the previous package and installed this one:
  xserver-xorg-input-multitouch

  Which made no difference at all. The system returned to the previous
  state, i.e., the touchscreen is responding but all the above mentioned
  problems are back.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 20:25:09 2012
  InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120423)
  ProcEnviron:
   LANGUAGE=pt_BR
   PATH=(custom, user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 774938] Re: Erratic cursor movement when using Coordinate Transformation Matrix

2013-01-30 Thread Yaroslav Sterkhov
Addition to bug info:
 Without a fix, users cannot reliably use a rotated touchscreen.

Without fix users unable to use  serveral screens one or more of which
are touchscreens, on systems or drivers which do not support separate
coordinate systems for each physical screen, e.g. ATI FireGL or NVIDIA
adapters with two or more displays attached to single adapter, because
that requires  set a scaling+transition CTM.

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

Title:
  Erratic cursor movement when using Coordinate Transformation Matrix

Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “xorg-server” source package in Natty:
  Fix Released

Bug description:
  SRU Justification:
  ==
  In previous releases of xserver-xorg-input-evdev there was an option to 
invert and/or swap axes. This allowed for simple screen rotation support. In 
the latest version of the module in Ubuntu, this option has been deprecated in 
favor of the server-side input coordinate transformation matrix support. See 
https://wiki.ubuntu.com/X/InputCoordinateTransformation for details. 
Unfortunately, the XInput 2.1 changes caused the input coordinate 
transformation matrix support to cause erratic pointer behavior. Without a fix, 
users cannot reliably use a rotated touchscreen.

  The fix involves maintaining and using the proper previous states of
  the X and Y event coordinates when performing the input coordinate
  transformation. If one coordinate is updated but not the other, the
  other's previous untransformed coordinate must be used to compute the
  correct new transformed coordinates. Then, the new transformed
  coordinates must be compared to the previous transformed coordinates
  to see if they should be reported to the client. Unchanged values are
  not reported in some XI 1.x and 2.x events. The current X server
  conflates the previous untransformed and previous transformed values
  and ends up calculating the new transformed values incorrectly.

  TEST CASE:
  To reproduce, use xinput to set a new coordinate transformation matrix with a 
rotation. For example, use a 90 degree turn by setting the input coordinate 
transformation matrix to 0 -1 1 1 0 0 0 0 1. See the above wiki page for 
details on how to set the matrix. Then, try to touch the touchscreen and move 
the cursor. The cursor will jump arround erratically when moving in pure 
horizontal or pure vertical motions.

  The risk of regression is minimal because the only time the fix will
  cause a change is when the transformation matrix has been modified
  from the identity matrix to a matrix including some amount of
  rotation. The patch was also tested in the xorg-edgers ppa for a few
  weeks before it was even uploaded to Oneiric.

  Original Bug Report:
  

  When using something like `xinput set-float-prop $INPUTDEV Coordinate
  Transformation Matrix 0.0 -1.0 1.0 1.0 0.0 0.0 0.0 0.0 1.0` to match
  the coordinates of a touchscreen/tablet to a rotated (transformed)
  screen, the cursor moves around erratically.

  From the original report of david-dklevine 
(https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/742567/comments/32):
  when a horizontal or vertical drag is performed the cursor jumps wildly - it 
appears to jump between what it should be according to the coordinate 
transformation and what it would be if x=0 and y=1 (that is if the second line 
of the matrix was the identity). With a diagonal drag or a touch the cursor 
appears where it should be.

  In addition to the Cando Multi Touch Panel reported at
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
  evdev/+bug/742567/comments/32, it also affects me with a AsusTek, Inc.
  MultiTouch(TTI) (on Asus EeePC T101MT)

  lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  $ apt-cache policy xserver-xorg-input-evdev
  xserver-xorg-input-evdev:
    Installed: 1:2.6.0-1ubuntu12
    Candidate: 1:2.6.0-1ubuntu12
    Version table:
   *** 1:2.6.0-1ubuntu12 0
  500 http://gd.tuwien.ac.at/opsys/linux/ubuntu/archive/ natty/main 
amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/774938/+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 832624] Re: cursor jumping to screen border

2013-01-29 Thread Yaroslav Sterkhov
Looks I'm getting same eefect with newest releases  of Ubuntu and evdev drivers 
(tried alot of combos,throughout 2012 year).
Simply, using transformation matrix with evdev driver wich inverts, scales  or 
shift  coordinates  causes either jumping to border of screen or jitter when  
touch even happening, which makes usage of multi-display configuration with one 
or more touchscreens. Tested with 26.x and 3.2.x  kernels, with all release  
since february  of 2012. Using touchscreens:  3M  MicroTouch EX II (since 3.x 
kerel their driver i sjust wrapper of evdev.. before that it calibration  
utility doesn't support multiple touchscreens) , also rugged BARQ screens 
(which supposed to be used with evdev).

This is conundrum, because even if I could even have skill to  fix it
and rebuild driver (but I have not enough knowledge to do so)our company
would accept only official distros in production.

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

Title:
  cursor jumping to screen border

Status in Unity Foundations:
  Won't Fix
Status in “xorg-server” package in Ubuntu:
  Won't Fix

Bug description:
  Even with xserver-xorg-core at version 2:1.10.1-1ubuntu1.2, incomplete
  valuators still cause the cursor to jump to the screen corners.

  
http://up.tao.at/download/c8a578b047fc4fbb205c4f0bee52532e/xev_with_new_xserver 
← Last tap (time 1494xxx) ended up with the cursor not where it should again 
(coordinates 600,675 would be correct, 1079,675 aren't).
  
http://up.tao.at/download/69e5a847d775f8fde8185fcf9345f0d9/evtest_with_new_xserver
 ← incomplete valuators, both on X and Y axis.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: xorg 1:7.6+4ubuntu3.1
  ProcVersionSignature: Ubuntu 2.6.38-11.48-server 2.6.38.8
  Uname: Linux 2.6.38-11-server x86_64
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Aug 24 10:33:26 2011
  DistUpgraded: Fresh install
  DistroCodename: natty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [8086:2a42]
 Subsystem: Intel Corporation Device [8086:2a42]
  InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64 
(20110426)
  MachineType: OEM OEM
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-server 
root=UUID=825941db-d8b4-41af-8208-b095c47eba13 ro quiet
  Renderer: Unknown
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: Cantiga
  dmi.board.vendor: Intel
  dmi.board.version: PILLAR ROCK FAB2
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/12/2009:svnOEM:pnOEM:pvrOEM:rvnIntel:rnCantiga:rvrPILLARROCKFAB2:cvnOEM:ct3:cvrOEM:
  dmi.product.name: OEM
  dmi.product.version: OEM
  dmi.sys.vendor: OEM
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs 20090808ubuntu13
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-foundations/+bug/832624/+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 774938] Re: Erratic cursor movement when using Coordinate Transformation Matrix

2013-01-29 Thread Yaroslav Sterkhov
@Cris: probably because of  it's not clear in which order they will be
applied if matrix also used.

Can you suggest link to distro which got it included,  I  need  test it
aap, as I have important project hanging which incdues about hundred
devices with multiple screens and touchscreens. Was fighting issue
about  year and a half and is near to deadline..

Personally I think that matrix should be internal  thing..  As settings
we should have visual parameters for matrix calculation, origin point,
minx, maxx, miny, maxy, rotation angle. TransformationMatrix isn't even
documented properly that it may also rotate and  invert axes, heh, info
in man is very.. lacking. Had to look into vector math books, at least I
had proper education to know that such thing exist (I'm not IT by
education, I'm engineer\industrial machinery designer). Normal user or
average IT?  They wouldn't know.

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

Title:
  Erratic cursor movement when using Coordinate Transformation Matrix

Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “xorg-server” source package in Natty:
  Fix Released

Bug description:
  SRU Justification:
  ==
  In previous releases of xserver-xorg-input-evdev there was an option to 
invert and/or swap axes. This allowed for simple screen rotation support. In 
the latest version of the module in Ubuntu, this option has been deprecated in 
favor of the server-side input coordinate transformation matrix support. See 
https://wiki.ubuntu.com/X/InputCoordinateTransformation for details. 
Unfortunately, the XInput 2.1 changes caused the input coordinate 
transformation matrix support to cause erratic pointer behavior. Without a fix, 
users cannot reliably use a rotated touchscreen.

  The fix involves maintaining and using the proper previous states of
  the X and Y event coordinates when performing the input coordinate
  transformation. If one coordinate is updated but not the other, the
  other's previous untransformed coordinate must be used to compute the
  correct new transformed coordinates. Then, the new transformed
  coordinates must be compared to the previous transformed coordinates
  to see if they should be reported to the client. Unchanged values are
  not reported in some XI 1.x and 2.x events. The current X server
  conflates the previous untransformed and previous transformed values
  and ends up calculating the new transformed values incorrectly.

  TEST CASE:
  To reproduce, use xinput to set a new coordinate transformation matrix with a 
rotation. For example, use a 90 degree turn by setting the input coordinate 
transformation matrix to 0 -1 1 1 0 0 0 0 1. See the above wiki page for 
details on how to set the matrix. Then, try to touch the touchscreen and move 
the cursor. The cursor will jump arround erratically when moving in pure 
horizontal or pure vertical motions.

  The risk of regression is minimal because the only time the fix will
  cause a change is when the transformation matrix has been modified
  from the identity matrix to a matrix including some amount of
  rotation. The patch was also tested in the xorg-edgers ppa for a few
  weeks before it was even uploaded to Oneiric.

  Original Bug Report:
  

  When using something like `xinput set-float-prop $INPUTDEV Coordinate
  Transformation Matrix 0.0 -1.0 1.0 1.0 0.0 0.0 0.0 0.0 1.0` to match
  the coordinates of a touchscreen/tablet to a rotated (transformed)
  screen, the cursor moves around erratically.

  From the original report of david-dklevine 
(https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/742567/comments/32):
  when a horizontal or vertical drag is performed the cursor jumps wildly - it 
appears to jump between what it should be according to the coordinate 
transformation and what it would be if x=0 and y=1 (that is if the second line 
of the matrix was the identity). With a diagonal drag or a touch the cursor 
appears where it should be.

  In addition to the Cando Multi Touch Panel reported at
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
  evdev/+bug/742567/comments/32, it also affects me with a AsusTek, Inc.
  MultiTouch(TTI) (on Asus EeePC T101MT)

  lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  $ apt-cache policy xserver-xorg-input-evdev
  xserver-xorg-input-evdev:
    Installed: 1:2.6.0-1ubuntu12
    Candidate: 1:2.6.0-1ubuntu12
    Version table:
   *** 1:2.6.0-1ubuntu12 0
  500 http://gd.tuwien.ac.at/opsys/linux/ubuntu/archive/ natty/main 
amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 965921] Re: gnome-shell most keyboard shortcuts not working

2012-05-10 Thread Yaroslav
@Karl

Try this:

gsettings set org.gnome.desktop.wm.keybindings toggle-shaded ['']

This shall remove the shortcut. Or you can reassign it like this:

gsettings set org.gnome.desktop.wm.keybindings toggle-shaded
['PrimarySupers']

Then restart gnome shell.

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

Title:
  gnome-shell most keyboard shortcuts not working

Status in “gnome-control-center” package in Ubuntu:
  Confirmed

Bug description:
  Updated Bug Description
  ===

  For Ubuntu 12.04, System Settings (gnome-control-center and gnome-
  settings-daemon) was patched to continue to support the gconf keyboard
  shortcuts used by Unity, Unity 2D, and the GNOME Classic sessions.
  Unfortunately, GNOME Shell now uses gsettings keyboard shortcuts so
  GNOME Shell ignores keyboard shortcut changes that get entered into
  System SettingsKeyboardShortcuts.

  This should be fixed for Ubuntu 12.10 but it's too late and
  complicated to fix for Ubuntu 12.04.

  One Workaround
  ==
  Install dconf-tools
  Run dconf-editor
  Look in org.gnome.desktop.wm.keybindings or org.gnome.mutter.keybindings

  Another Workaround
  ==
  Set a custom keyboard shortcut. This is useful if you want to set Ctrl+Alt+F 
to open Firefox for instance. In System Settings, click Keyboard. Switch to the 
Shortcuts tab and click Custom Shortcuts at the bottom of the list.

  Click the + button and add a name to remember the shortcut and  the
  specific command you want to execute. Click Apply. Find the name in
  the list and click the right half of the row. Disabled should change
  to New accelerator. Enter the keyboard shortcut you want to use.

  Ctrl+Alt+T to open the terminal and several other usual shortcuts from
  Unity have been added to GNOME Shell on April 17.

  
  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.3.92-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Tue Mar 27 07:07:44 2012SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   gnome-bluetooth3.2.2-0ubuntu4
   indicator-datetime 0.3.92-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/965921/+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 881172] Re: Graphical errors on charts in resources tab (faded bands)

2012-05-03 Thread Yaroslav
I think this is compiz bug -- just try metacity --replace

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

Title:
  Graphical errors on charts in resources tab (faded bands)

Status in “gnome-system-monitor” package in Ubuntu:
  Confirmed

Bug description:
  On my system, the charts on the system monitor resources tab are
  displayed with some graphical errors.

  The most obvious manifestation seems to be faded bands along the
  charted lines, though there is also extra white around the chart area
  (rather than the grey of the window background). The chart labels also
  end up quite blurry and hard to read. Sometimes the pink line for
  memory usage seems to hover horizontally right in one of the faded
  areas, and becomes nearly invisible.

  Bizarrely, the problem is sometimes only present on one of my
  monitors. The screenshot I have attached was taken straddling the two
  monitors; the zone on the left appears normal, while the zone on the
  right is noticeably affected. Dragging the system monitor between the
  two monitors causes the issue to appear and disappear. However, other
  times there is no difference and the system monitor is affected
  equally no matter which monitor it is on.

  Ubuntu release: Oneiric 11.10, x86_64
  gnome-system-monitor: 3.2.0-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/881172/+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 983291] Re: Screen Rotation options only Counterclockwise Clockwise

2012-04-29 Thread Yaroslav
Confirm this issue also on laptop Samsung N143

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

Title:
  Screen Rotation options only Counterclockwise  Clockwise

Status in “gnome-control-center” package in Ubuntu:
  Confirmed

Bug description:
  Hi, my Acer notebook includes an Intel Mobile 945GSE Express
  Integrated Graphics Controller graphics card. I can only change to
  Counterclockwise  Clockwise.

  I expect this:
  To also be able to change screen rotation to Normal or 180 Degrees.

  Steps I have to do to correct these:
  N/A

  Steps to reproduce:
  Install Ubuntu 12.04 LTS (Precise Pangolin) Beta 2  connect an external 
monitor with a notebook running Intel graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.3.92-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
  Uname: Linux 3.2.0-20-generic-pae i686
  ApportVersion: 1.95-0ubuntu1
  Architecture: i386
  CheckboxSubmission: e28f23d40ba6960d2759044b1acbd380
  CheckboxSystem: c69722ecac764861be52925fa50b4dcc
  Date: Mon Apr 16 19:40:42 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328)
  ProcEnviron:
   LANGUAGE=se_NO:nb_NO:nb:no_NO:no:nn_NO:nn:da:sv:en
   LANG=se_NO
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/983291/+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 965921] Re: gnome-shell most keyboard shortcuts not working

2012-04-19 Thread Yaroslav
 You'll still need to use dconf-editor though to set GNOME Shell
shortcuts for Ubuntu 12.04

Could you please explain how to set shortcut to launch terminal using
dconf-editor?

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

Title:
  gnome-shell most keyboard shortcuts not working

Status in “gnome-control-center” package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell keyboard shortcuts stopped working. Specifically,
  Ctrl+Alt+t no longer opens a terminal, my maximization shortcuts no
  longer work, navigation shortcuts don't work.

  The problem seems that gnome-shell 3.4 has switched to gsettings/dconf
  for its keyboard shortcuts but Unity still uses gconf. System Settings
  in Precise was patched to support gconf but it ought to support
  gsettings also.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.3.92-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Tue Mar 27 07:07:44 2012
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   gnome-bluetooth3.2.2-0ubuntu4
   indicator-datetime 0.3.92-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/965921/+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 965921] Re: gnome-shell most keyboard shortcuts not working

2012-04-01 Thread Yaroslav
Can't use suggested workarounds (or I don't fully understand them).

If it were possible to assign keyboard shortcuts for gnome shell via
system settings  keyboard there would be no this bug report in the
first place, I think.

Strange thing is that some assignments do work. For example I can assign
Ctrl+Alt+T to launch calculator, web browser or home folder, but not
terminal.

Even for web browser I can't use combinations with Super key. Eg.,
Ctrl+Super+T. It gets assigned OK, but does not work.

By the way I can't find neither web browser nor calculator key in
org.gnome.desktop.wm.keybindings (gsettings). It must be somewhere else.

My another observation that is different from original bug description
is that most default shortcuts actually work. Navigation, screenshots -
all work. Super+up/super+down maximizes/restores window OK. Although
Ctrl+Super+L does not lock screen, Super+S just passes 'S' letter.

My gnome shell is 3.4 already.

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

Title:
  gnome-shell most keyboard shortcuts not working

Status in “gnome-control-center” package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell keyboard shortcuts stopped working. Specifically,
  Ctrl+Alt+t no longer opens a terminal, my maximization shortcuts no
  longer work, navigation shortcuts don't work.

  The problem seems that gnome-shell 3.4 has switched to gsettings/dconf
  for its keyboard shortcuts but Unity still uses gconf. System Settings
  in Precise was patched to support gconf but it ought to support
  gsettings also.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.3.92-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Tue Mar 27 07:07:44 2012
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   gnome-bluetooth3.2.2-0ubuntu4
   indicator-datetime 0.3.92-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/965921/+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 965921] Re: gnome-shell most keyboard shortcuts not working

2012-03-30 Thread Yaroslav
Is there a workaround? Can I define shortcuts to launch terminal, web
browser, etc. using gsettings?

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

Title:
  gnome-shell most keyboard shortcuts not working

Status in “gnome-control-center” package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell keyboard shortcuts stopped working. Specifically,
  Ctrl+Alt+t no longer opens a terminal, my maximization shortcuts no
  longer work, navigation shortcuts don't work.

  The problem seems that gnome-shell 3.4 has switched to gsettings/dconf
  for its keyboard shortcuts but Unity still uses gconf. System Settings
  in Precise was patched to support gconf but it ought to support
  gsettings also.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.3.92-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Tue Mar 27 07:07:44 2012
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   gnome-bluetooth3.2.2-0ubuntu4
   indicator-datetime 0.3.92-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/965921/+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