Buttons blanked out in Scribus when using Unity

Bug #698172 reported by James Pursey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity
Invalid
Undecided
Unassigned
appmenu-qt
Incomplete
Undecided
Unassigned
unity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: unity

Hi,

While testing Unity in Maverick I noticed that some key buttons necessary to be able to use Scribus are blanked out, making Scribus unuseable in this environment. The buttons are Item, Insert, Page, View and Edit. I tried updating Scribus from 1.53.8 to Scribus-trunk, but the problem remains. I then upgraded the computer from Maverick to Natty to see if the problem remains in the latest version of unity, which it does. Moreover, in Natty none of the buttons are visible at all unless I click on the top panel.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: unity 3.2.8-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7
Uname: Linux 2.6.37-11-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/allscreens/options/active_plugins'
Date: Thu Jan 6 16:56:25 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
InstallationMedia_: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
MachineType: HP-Pavilion FJ393AA-ABF a6543.fr
PciDisplay: 02:00.0 VGA compatible controller [0300]: nVidia Corporation G96 [GeForce GT 120] [10de:0646] (rev a1) (prog-if 00 [VGA controller])
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.37-11-generic root=UUID=7cf93703-cd02-43da-aa65-73696d2db186 ro splash quiet vga=794 vt.handoff=7 quiet splash
ProcVersionSignature_: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7
RelatedPackageVersions:
 xserver-xorg 1:7.5+6ubuntu6
 libgl1-mesa-glx 7.9+repack-1ubuntu3
 libdrm2 2.4.22-2ubuntu1
 xserver-xorg-video-intel 2:2.13.901-2ubuntu2
 xserver-xorg-video-ati 1:6.13.2-1ubuntu2
SourcePackage: unity
dmi.bios.date: 04/23/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.17
dmi.board.name: Nettle3
dmi.board.vendor: ECS
dmi.board.version: 2.2
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.17:bd04/23/2008:svnHP-Pavilion:pnFJ393AA-ABFa6543.fr:pvr:rvnECS:rnNettle3:rvr2.2:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: FJ393AA-ABF a6543.fr
dmi.sys.vendor: HP-Pavilion
glxinfo: Error: [Errno 2] No such file or directory
system: distro = Ubuntu, architecture = x86_64, kernel = 2.6.37-11-generic

Revision history for this message
James Pursey (jamespursey) wrote :
Revision history for this message
James Pursey (jamespursey) wrote :

Additional Information
I've been playing around with Scribus in Unity and have just found that it is possible to get all the buttons to function, bar the Item button which still doesn't work. The steps are as follows:
1) Open a document using Scribus
2) Maximize the Scribus window
3) Close Scribus
4) Open up the document again (this time the document opens directly with the Window maximized).

It is now possible to use the buttons Insert, Page, View and Edit.

Conversely, the bug can be "re-enabled" using the following steps:
1) Resize the Window so that it is no longer maximized
2) Leave Scribus
3) Open the document again.

The document will open in a non-maximized window and the buttons are once again in-operational.

Revision history for this message
Gord Allott (gordallott) wrote :

Invalid for unity, appmenu bug

Changed in unity:
status: New → Invalid
Gord Allott (gordallott)
Changed in unity (Ubuntu):
status: New → Invalid
Revision history for this message
Kalle Valo (kvalo) wrote :

Scribus is using qt, moving to appmenu-qt.

James, I tried to reproduce this bug but unfortunately I'm no scribus expert. In fact, I'm using it for the first time. Can you explain in more detail how to reproduce the bug, please? Screenshot would also help.

affects: appmenu-gtk → appmenu-qt
Revision history for this message
James Pursey (jamespursey) wrote :

Sorry for the time it's taken for me to reply. I've since re-installed Maverick because the bugs in Natty make it unusable right now. I'll re-install it when I have some spare time and try to send you some screen shots.

Revision history for this message
James Pursey (jamespursey) wrote :

I have just installed the alpha-2 version of Natty and I cannot reproduce this issue. However, I think this may be because the application buttons are no longer appearing in the top panel as they did in the alpha-1 release. It is possible that I re-encounter the problem when the Scribus buttons reappear in the top panel, which I suppose they will. I'll keep this release on my computer for as long as I am able (ie until it becomes unusable) to see how things progress.

Revision history for this message
Michal (mekmar) wrote :

I checked ScribusNG (1.4, dev branch, qt4 based) a minute ago. It seems to work fine, menus work, functions, for what I checked, work. Menu items are actively changing, according to tools, I'm trying to use (that was an issue back in the times of appmenu aplet in Maverick).
Stable branch of Scribus (1.3.3) doesn't work with appmenu at all (qt3 involved I suppose)

Revision history for this message
James Pursey (jamespursey) wrote :

The problem concerned the global menu. For a while, the global menu didn't work with qt applications and so Scribus was working fine. The global menu seems to be working with Scribus now, and I can no longer reproduce the bug. It seems to be resolved (for the moment at least).

Revision history for this message
Miloš Jakovljević (milos-sd) wrote :

It doesn't work for Story Editor in Scribus. I need "Insert" menu to add bullets.

Revision history for this message
Bilal Akhtar (bilalakhtar) wrote :

Please re-open bug if this issue still persists in Precise.

Changed in appmenu-qt:
status: New → Incomplete
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.