[Touch-packages] [Bug 1243642] Re: .Xmodmap not automatically loaded on start

2016-06-10 Thread Uriel Tunz
@Hélio, only thing I did was upgrade to 16.04 (clean install), copy my
xkb file over and load it (xkbcomp $HOME/.xkb/xkb-map $DISPLAY). That's
it.

Well, it *does* get loaded on each boot via .bashrc (as noted in post
14) when a terminal is auto-opened (put in startup prefs) so not sure it
will survive a reboot on its own. Will check that.

But once loaded, it remains in effect after all suspends and hibernates,
same as .Xmodmap used to work. I can live with the minor inconvenience
of setting up the auto-load. Just have to remember what I did after a
year or more passes.

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

Title:
  .Xmodmap not automatically loaded on start

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm using a ~/.Xmodmap file to define two keycode mappings.

  13.10 doesn't seem to automatically load this file any more.
  13.04 did. (same file, same laptop)

  manual execution of "xmodmap ~/.Xmodmap" works on 13.10!
  That means I'm e.g. able to use this key in a terminal or in geany.

  I discovered, that by switching the keyboard layouts using "gnome-
  control-center region layouts" the mappings of the "xmodmap
  ~/.Xmodmap" will be lost again. Then another manual execution of
  "xmodmap ~/.Xmodmap" has to be executed and it works again.

  Perhaps the ~/.Xmodmap is loaded and lost by the the gnome-control-
  center () later.

  Sorry, I can't figure out which packet this bug has to be asigned to.
  By using apport-bug "xorg" was choosen, but it could be "xorg-server"
  or "gnome-control-center", also.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 12:05:11 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
  InstallationDate: Installed on 2013-10-18 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Acer Extensa 5630
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic 
root=/dev/mapper/vg01-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.34
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.34:bd08/11/2009:svnAcer:pnExtensa5630:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5630
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Wed Oct 23 11:15:16 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5459 
   vendor CMO
  xserver.version: 2:1.14.3-3ubuntu2

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

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


[Touch-packages] [Bug 1243642] Re: .Xmodmap not automatically loaded on start

2016-06-08 Thread Uriel Tunz
Bug is gone in 16.04!

.Xmodmap (which IS deprecated) still needs to be converted to xkb (post
14,
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1243642/comments/14),
but then everything works as before: keyboard map reloads automatically
after any number of suspend/hibernate cycles. Seriously happy about
this. Anyone see different behavior?

I'm keeping .Xmodmap as a kind of original source file file for
reference, but editing the xkb file directly now (rarely).

Many thanks to the devs for fixing the bug.

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

Title:
  .Xmodmap not automatically loaded on start

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm using a ~/.Xmodmap file to define two keycode mappings.

  13.10 doesn't seem to automatically load this file any more.
  13.04 did. (same file, same laptop)

  manual execution of "xmodmap ~/.Xmodmap" works on 13.10!
  That means I'm e.g. able to use this key in a terminal or in geany.

  I discovered, that by switching the keyboard layouts using "gnome-
  control-center region layouts" the mappings of the "xmodmap
  ~/.Xmodmap" will be lost again. Then another manual execution of
  "xmodmap ~/.Xmodmap" has to be executed and it works again.

  Perhaps the ~/.Xmodmap is loaded and lost by the the gnome-control-
  center () later.

  Sorry, I can't figure out which packet this bug has to be asigned to.
  By using apport-bug "xorg" was choosen, but it could be "xorg-server"
  or "gnome-control-center", also.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 12:05:11 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
  InstallationDate: Installed on 2013-10-18 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Acer Extensa 5630
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic 
root=/dev/mapper/vg01-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.34
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.34:bd08/11/2009:svnAcer:pnExtensa5630:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5630
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Wed Oct 23 11:15:16 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5459 
   vendor CMO
  xserver.version: 2:1.14.3-3ubuntu2

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

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


[Touch-packages] [Bug 1371919] Re: kern.log flooded with HDMI ATI/AMD: no speaker allocation for ELD

2015-03-06 Thread Uriel Tunz
Joined this bug thread, then found the cause of the problem -- in my
case at least.

The connection from PC through AVR to TV was marginal (due to cable
length, one coupling connector, cable quality, routing, etc.). The
problem was undetectable except by these no speaker allocation for ELD
messages, but of course they gave no hint of the root cause.

When an inadvertent jostle made the intermittent connection obvious
(noticeable flickering), I redid the cabling and found no more of these
messages.

Should emphasize that this is the only action I took. It's likely, I
think, that these messages were generated by partial reinitializations
from interrupted signals in the connection.

The drivers and hardware have been rock solid. But without the
confidence of knowing that, I've spent way too many hours (in the past)
tinkering, when the trouble was simply in the link between devices.

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

Title:
  kern.log flooded with HDMI ATI/AMD: no speaker allocation for ELD

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a gigabyte f2a88xn motherboard with built-in audio.

  In pavucontrol, under Configuration - Built-in audio (the first),
  there is Digital Stereo (HDMI) Output.

  When I disable it, the kern.log continuously reports HDMI ATI/AMD: no
  speaker allocation for ELD.

  This happens almost every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  saverio2824 F pulseaudio
   /dev/snd/controlC0:  saverio2824 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Sep 20 15:08:50 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140723)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd09/04/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371919/+subscriptions

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


Re: [Touch-packages] [Bug 1243642] Re: .Xmodmap not automatically loaded on start

2015-03-01 Thread Uriel Tunz
Yes, different. Editing those system-level files affects keyboard 
mapping for ALL users. But this bug is about .Xmodmap, which is 
per-user. My post noted that even xkb maps are lost on suspend/sleep.

Converting .Xmodmap files to xkb is straightforward. After manually 
loading the desired .Xmodmap file, then:

[[ -d $HOME/.xkb ]] || mkdir $HOME/.xkb
xkbcomp $DISPLAY $HOME/.xkb/xkb-map

Then edit $HOME/.xkb/xkb-map, which is fairly intuitive, if needed. 
Next, since the file won't load automatically no matter what, I did:

echo 'xkbcomp $HOME/.xkb/xkb-map $DISPLAY'  ~/.bashrc

This way, at least the map can be loaded by just popping open a 
terminal. (Remove the 'xmodmap .Xmodmap' line in .bashrc, if it was there.)

On single-head, multi-user systems where everyone doesn't use the same 
keyboard map, instead of just being able to switch users, it would be 
necessary to change configuration and restart (if control is only 
system-wide). Completely unacceptable. This bug really needs fixing.


On 03/01/2015 12:03 AM, Rafael Nonato wrote:
 I don't think we are talking about the same thing when we talk of XKB. To
 clarify what I am talking about, I meant editing the files under
 /usr/share/X11/xkb/


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

Title:
  .Xmodmap not automatically loaded on start

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm using a ~/.Xmodmap file to define two keycode mappings.

  13.10 doesn't seem to automatically load this file any more.
  13.04 did. (same file, same laptop)

  manual execution of xmodmap ~/.Xmodmap works on 13.10!
  That means I'm e.g. able to use this key in a terminal or in geany.

  I discovered, that by switching the keyboard layouts using gnome-
  control-center region layouts the mappings of the xmodmap
  ~/.Xmodmap will be lost again. Then another manual execution of
  xmodmap ~/.Xmodmap has to be executed and it works again.

  Perhaps the ~/.Xmodmap is loaded and lost by the the gnome-control-
  center () later.

  Sorry, I can't figure out which packet this bug has to be asigned to.
  By using apport-bug xorg was choosen, but it could be xorg-server
  or gnome-control-center, also.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 12:05:11 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
  InstallationDate: Installed on 2013-10-18 (4 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Extensa 5630
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic 
root=/dev/mapper/vg01-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.34
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.34:bd08/11/2009:svnAcer:pnExtensa5630:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5630
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Wed Oct 23 11:15:16 2013
  xserver.configfile: default
  

[Touch-packages] [Bug 1243642] Re: .Xmodmap not automatically loaded on start

2015-02-28 Thread Uriel Tunz
This bug remains, and the problem is just as bad after converting from
an .Xmodmap file to an xkb map: THE FILE MUST BE MANUALLY RELOADED ON
AWAKENING.

 - A script in /etc/pm/sleep.d does not work.
 - A script on the desktop does not work.
 - Tearing hair out does not work.

Auto-loading the map on startup is trivial. But how to auto-load even an
xkb map file after a sleep? Or maybe, how to not lose the mappings
during the sleep-wake process to begin with?

Getting ready to revert to 12.04 and not re-upgrade until this bug is
fixed.

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

Title:
  .Xmodmap not automatically loaded on start

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm using a ~/.Xmodmap file to define two keycode mappings.

  13.10 doesn't seem to automatically load this file any more.
  13.04 did. (same file, same laptop)

  manual execution of xmodmap ~/.Xmodmap works on 13.10!
  That means I'm e.g. able to use this key in a terminal or in geany.

  I discovered, that by switching the keyboard layouts using gnome-
  control-center region layouts the mappings of the xmodmap
  ~/.Xmodmap will be lost again. Then another manual execution of
  xmodmap ~/.Xmodmap has to be executed and it works again.

  Perhaps the ~/.Xmodmap is loaded and lost by the the gnome-control-
  center () later.

  Sorry, I can't figure out which packet this bug has to be asigned to.
  By using apport-bug xorg was choosen, but it could be xorg-server
  or gnome-control-center, also.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 12:05:11 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
  InstallationDate: Installed on 2013-10-18 (4 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Extensa 5630
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic 
root=/dev/mapper/vg01-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.34
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.34:bd08/11/2009:svnAcer:pnExtensa5630:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5630
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Wed Oct 23 11:15:16 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5459 
   vendor CMO
  xserver.version: 2:1.14.3-3ubuntu2

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

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