pinning geary to launcher reorders other entries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Expired
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Hi, if you pin geary to launcher, it changes order of others icons
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: unity 6.10.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.5.0-18-generic x86_64
.tmp.unity.
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
CompizPlugins: [core,composite
CompositorRunning: compiz
Date: Tue Nov 20 23:38:34 2012
DistUpgraded: 2012-11-14 20:23:17,125 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
EcryptfsInUse: Yes
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:2114]
Subsystem: Lenovo Device [17aa:2114]
InstallationDate: Installed on 2012-11-14 (6 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MachineType: LENOVO 208253G
MarkForUpload: True
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=sk_SK.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: unity
UpgradeStatus: Upgraded to quantal on 2012-11-14 (6 days ago)
dmi.bios.date: 05/15/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET71WW (3.01 )
dmi.board.name: 208253G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 208253G
dmi.product.
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.8.
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.