Transparency windows on gramps software

Bug #1460539 reported by Yionel
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ubuntu
New
Low
Unassigned

Bug Description

Hi,

I have vivid version and with old or new kernel, I have a transparency windows on gramps software. It's difficult to use it.
I found solution here : http://askubuntu.com/questions/485987/how-do-i-stop-system-monitor-from-being-transparent

With dconf setting : gsettings set com.canonical.desktop.interface scrollbar-mode normal

Scrollbar affects transparency, I don't know why (compiz or other stuff) but it's problematic.

Thank you
Lionel

$ uname -a
Linux tpx 4.1.0-040100rc1-generic #201504270235 SMP Mon Apr 27 02:36:47 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
Uname: Linux 4.1.0-040100rc1-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.17.2-0ubuntu1.1
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
CurrentDesktop: Unity
Date: Mon Jun 1 08:56:20 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus: virtualbox, 4.3.26, 3.19.0-18-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21da]
InstallationDate: Installed on 2015-05-13 (18 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 4291JM5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-040100rc1-generic root=UUID=a4898b5b-00a6-468d-a6b5-242ca4860ff1 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET69WW (1.39 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4291JM5
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn4291JM5:pvrThinkPadX220:rvnLENOVO:rn4291JM5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4291JM5
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
xserver.bootTime: Mon Jun 1 07:48:57 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 4204
 vendor AUO
xserver.version: 2:1.17.1-0ubuntu3

Revision history for this message
Yionel (yionel) wrote :
penalvch (penalvch)
tags: added: bios-outdated-1.40
Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Yionel (yionel) wrote :

Christopher, thanks for your answer.
So, I updated my bios 1.39 -> 1.40

ionl@tpx:~11h09$ uname -a
Linux tpx 4.1.0-040100rc1-generic #201504270235 SMP Mon Apr 27 02:36:47 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

ionl@tpx:~11h10$ sudo dmidecode -s bios-version
/dev/mem: No such file or directory

Apparently, dmidecode command doesn't work on new kernel 4.1.0, I have to compile it with special option to see bios version.
I don't care, I took a photo (old school method ^^)

1. I set to default (overlay-auto) com.canonical.desktop.interface scrollbar-mode option with dconf Editor
2. I started gramps software 4.1.3-1 and like you can see on screenshot here : https://lh3.googleusercontent.com/lOYQQ2u0oFApd-6H5UFs5T0r3PtQWxlajlBjGnvZRMyl=w1155-h650-no, popup is transparent

Thank you

Changed in xorg (Ubuntu):
status: Incomplete → New
Revision history for this message
penalvch (penalvch) wrote :

Yionel, if you switch GUI to GNOME Flashback (Metacity), does that WORKAROUND the problem?

tags: added: latest-bios-1.40
removed: bios-outdated-1.40
Changed in xorg (Ubuntu):
importance: Low → Medium
status: New → Incomplete
Revision history for this message
Yionel (yionel) wrote :

1. I reset to overlay-auto option and installed gnome-session-flashback package
2. I logged out
3. I logged on Gnome Flashback (Metacity) (Damn, I forgot that I loved so much this environment ^^), it's same thing on gramps. (after a restart also), windows is transparent

penalvch (penalvch)
Changed in xorg (Ubuntu):
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg (Ubuntu):
status: New → Confirmed
Revision history for this message
Sam (manzisam) wrote :

I believe this issue is the same as Gramps bug:8471: Windows Transparent - UI modals for both People and Notes have transparent backgrounds

https://gramps-project.org/bugs/view.php?id=8471

Fixed in Gramps 4.2.1

Revision history for this message
Sam (manzisam) wrote :
penalvch (penalvch)
affects: xorg (Ubuntu) → ubuntu
Changed in ubuntu:
importance: Medium → Low
status: Confirmed → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.