P.S. I've just finally found a workaround myself: doing "apt install
libgcc-s1:i386" first, before installing anything else (but after "apt
update"), allows the installation to succeed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Although this is marked as "Invalid" for 20.04, this problem has somehow
started happening in GitHub Actions Ubuntu 20.04 virtual environment
since today (2020-07-24), even though it worked correctly before. I
don't know if attaching the entire build log is desirable, but as the
result of running t
This is related to the global menu and not compiz.
** Package changed: compiz (Ubuntu) => appmenu-gtk (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078694
Title:
Modal dialog broken on Un
This bug is absolutely trivial to reproduce, here is a minimal GTK+
program which shows it:
#include
static void activate_test(GtkMenuItem*, GtkWindow* window)
{
GtkWidget* dialog = gtk_message_dialog_new(window, GTK_DIALOG_MODAL,
GTK_MESSAGE_INFO, GTK_BUTTONS_OK, "a message", NULL);
The relevant code inside wxWidgets is in
http://trac.wxwidgets.org/browser/wxWidgets/trunk/src/gtk/dialog.cpp#L102
and uses gtk_window_set_transient_for() and gtk_window_set_modal() which
doesn't seem to be enough when using Ubuntu global menu bar. Presumably
gtk_dialog_run() works (otherwise more
This not-really-a-bug makes launching evince from command line
completely impractical because it keeps spewing these not-really-helpful
warnings. It would be great if this could be fixed by the upstream (I do
agree that it's not a Ubuntu bug).
--
You received this bug notification because you are
Public bug reported:
[I am not sure if this is the correct package to report this bug
against, sorry in advance if it isn't]
In the default Ubuntu 12.04 installation, GTK applications don't receive
neither "map" nor "can_activate_accel" signals for their menus, probably
because the menus are not
Public bug reported:
It seems that arithmetic expansion is completely broken in dash
0.5.51-3ubuntu2 from 10.04.3 LTS:
% /bin/sh -c 'echo $((10-2-3))' # ok so far
5
% /bin/sh -c 'echo $((10-2*0-3))' # what??
13
% /bin/sh -c 'echo $((10-2*1-3))'# it's not limited to fa
Does anybody know if this is really an appmenu-gtk problem or a bug in
wxWidgets itself? As a wx developer I'd be interested in looking at this
if it's the latter but I can't find much information about the whole
menu proxy stuff which seems to be completely Ubuntu-specific. What
exactly is needed,
Also happens with i860 on Gigabyte GA-P55-UD5 motherboard.
This problem is discussed in this LKML thread:
http://thread.gmane.org/gmane.linux.kernel/913374/
--
hpet driver backtraces when hyperthreading enabled
https://bugs.launchpad.net/bugs/473702
You received this bug notification because you
Public bug reported:
After upgrading from 8.10 to 9.04 hal is now started twice on boot and
the second time it hangs for a couple of minutes before continuing.
It seems that hal is launched implicitly as a dependency of something
(acpid? dbus?) because I see a line about starting HAL at console a
FWIW it still doesn't work with 9.04 on HP nw8000 neither.
--
/proc/acpi/button/lid/*/state always says "open"
https://bugs.launchpad.net/bugs/89860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
I don't know if anybody cares about another vote in favour of uswsusp
but after spending a couple of hours trying to make suspend work again
after upgrading to Intrepid from Feisty (via Hardy) I was only able to
make it work by using uswsusp on HP nw8000 notebook. Removing uswsusp
from Ubuntu would
If this is a wxWidgets bug, it should be fixed since 2.8.5 (the latest
version is 2.8.7 as of this writing), quoting the changelog:
* Replaced g_free with g_border_free to fix crash with newer GTK+.
Please let us (wxWidgets developers) know if you still see the problem
with 2.8.7. The (trivia
ad of c_str(). But your code as is simply can't work.
** Changed in: wxwidgets2.6 (Ubuntu)
Assignee: (unassigned) => Vadim Zeitlin (vadim-wxwindows)
Status: Confirmed => Invalid
--
wxGetPasswordFromUser and wxGetTextFromUser return only one character.
https://bugs.launchpad.ne
AFAICS this is really not a wxWidgets bug (as I tried to explain at the
linked SF bug report, it could be a bug in wx but nothing in the
provided backtrace indicates it). The fact that there are apparently
patches to aMule fixing it also seem to show that the problem is in
aMule (and was fixed ther
FWIW I strongly agree with the comment of Matthias from 2007-07-06. We'd
like to avoid divergencies between Debian, Ubuntu and our own (i.e. from
wx svn) packages and we definitely don't want to enable wxMSW build to
our version by default because some of us to build them pretty often and
adding 20
I'm not sure if it's exactly the same bug but the symptoms look similar:
under Gutsy, my HP nw8000 never reports lid as being closed in
/proc/acpi/button/lid/C138/state and acpid doesn't generate any events
when the lid is closed, although it does generate from one up to a dozen
of them (!) when it
This doesn't work in Gutsy (although it did work in Feisty on the same
machine) with HP nw8000 neither. It seems that the new HAL simply
doesn't see the lid switch at all, at least it doesn't appear as
acpi_C138 device as I'd expect it to (the corresponding ACPI file path
is /proc/acpi/button/lid/C
This was a bug in wxWidgets and it was fixed as soon as we learnt about
it, see thread at
http://article.gmane.org/gmane.comp.lib.wxwidgets.devel/84070 for more
details. The fix will appear in (soon to be released) 2.8.2 and the
future 2.9 series.
--
Scorched3d SIGSEGV on startup
https://launchpa
20 matches
Mail list logo
