Blacklist QtOctave
Bug #761571 reported by
Sebastian Rühl
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AppMenu GTK+ |
Fix Released
|
Medium
|
Charles Kerr | ||
appmenu-gtk (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: appmenu-qt
Blacklist QtOctave because the inner windows will overlap the main window menu
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: appmenu-qt 0.1.2-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Fri Apr 15 11:48:47 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
LANGUAGE=de_DE:en
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: appmenu-qt
UpgradeStatus: Upgraded to natty on 2011-04-14 (0 days ago)
Related branches
lp:~charlesk/appmenu-gtk/lp-761571
- Lars Karlitski (community): Approve
- jenkins (community): Approve (continuous-integration)
-
Diff: 11 lines (+1/-0)1 file modifiedsrc/bridge.c (+1/-0)
Changed in appmenu-qt (Ubuntu): | |
assignee: | nobody → Charles Kerr (charlesk) |
Changed in appmenu-qt (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in appmenu-qt (Ubuntu): | |
status: | Confirmed → In Progress |
Changed in appmenu-qt (Ubuntu): | |
assignee: | Charles Kerr (charlesk) → nobody |
status: | In Progress → New |
Changed in appmenu-gtk: | |
importance: | Undecided → Medium |
status: | New → In Progress |
assignee: | nobody → Charles Kerr (charlesk) |
milestone: | none → 12.10.0 |
affects: | appmenu-qt (Ubuntu) → appmenu-gtk (Ubuntu) |
Changed in appmenu-gtk (Ubuntu): | |
status: | New → Fix Committed |
Changed in appmenu-gtk (Ubuntu): | |
status: | New → Confirmed |
Changed in appmenu-gtk (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in appmenu-gtk: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
I have just upgraded to Nutty from Maverick (64bit). I also now experience problems with the windows in QtOctave. It just worked perfectly under Maverick. Any progress on this bug?