Ubuntu
compiz package

Unable to set 4 horizontal desktops

Bug #522102 reported by Brian Buchanan on 2010-02-15

This bug report is a duplicate of: Bug #345387: Horizontal size slider fault. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	compiz (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: compiz

When setting the number of Horizontal Desktops to 4 it jumps down to 2.
There is no problem setting any other number of desktops.

I am able to set it to 4 horizontal desktops through Gconf-editor -
/apps/compiz/general/screen0/options/hsize.

ProblemType: Bug
Architecture: amd64
CompizPlugins: [core,ccp,move,resize,place,decoration,session,imgjpeg,text,fadedesktop,ring,workarounds,png,mousepoll,widget,commands,regex,neg,shift,kdecompat,vpswitch,svg,gnomecompat,dbus,resizeinfo,wobbly,animation,fade,obs,snap,cube,animationaddon,expo,3d,rotate,scale,ezoom,staticswitcher,scaleaddon]
Date: Mon Feb 15 11:47:03 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
MachineType: Phoenix/SiS M7X0SU
NonfreeKernelModules: nvidia
Package: compiz-core 1:0.8.4-0ubuntu13
PciDisplay: 01:00.0 VGA compatible controller [0300]: nVidia Corporation G98 [GeForce 9300M GS] [10de:06e9] (rev a1)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-13-generic root=UUID=73f6770b-a84b-4fc3-917f-51c2f0eae433 ro quiet splash
ProcEnviron:
LANG=C
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
RelatedPackageVersions:
xserver-xorg 1:7.5+1ubuntu2
libgl1-mesa-glx 7.7-0ubuntu8
libdrm2 2.4.17-0ubuntu2
xserver-xorg-video-intel 2:2.9.1-1ubuntu4
xserver-xorg-video-ati 1:6.12.99+git20100126.e5933fd7-0ubuntu1
SourcePackage: compiz
Uname: Linux 2.6.32-13-generic x86_64
dmi.bios.date: 08/28/0892
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.asset.tag: 1234567890
dmi.board.name: M7X0SU
dmi.board.vendor: SiS
dmi.board.version: Bottom
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: SiS
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd08/28/0892:svnPhoenix/SiS:pnM7X0SU:pvrRev.A1:rvnSiS:rnM7X0SU:rvrBottom:cvnSiS:ct1:cvrN/A:
dmi.product.name: M7X0SU
dmi.product.version: Rev. A1
dmi.sys.vendor: Phoenix/SiS
glxinfo: Error: [Errno 2] No such file or directory
system: distro = Ubuntu, architecture = x86_64, kernel = 2.6.32-13-generic

See original description

Tags:

Revision history for this message

Brian Buchanan (nighthawk-uk) wrote on 2010-02-15:

BootDmesg.txt Edit (40.9 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (6.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.4 KiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (45.5 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (9.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (405 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (47.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (796 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (108.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (225.6 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.3 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (15.6 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (16.2 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (9.3 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (9.1 KiB, text/plain; charset="utf-8")

Brian Buchanan (nighthawk-uk) on 2010-02-15

description:

updated

Revision history for this message

cactaur (vahag1991) wrote on 2010-03-22:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #345387, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.