[Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
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. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
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 these commands 2020-07-24T22:46:28.8786226Z sudo dpkg --add-architecture i386 2020-07-24T22:46:28.8786352Z sudo apt-get update 2020-07-24T22:46:28.8786474Z sudo apt-get --assume-yes install \ 2020-07-24T22:46:28.8786604Z automake bc bsdmainutils bzip2 curl cvs default-jre \ 2020-07-24T22:46:28.8786724Z g++-mingw-w64-i686 g++-multilib git jing libarchive-tools \ 2020-07-24T22:46:28.8786866Z libtool libxml2-utils libxslt1-dev make patch pkg-config rsync \ 2020-07-24T22:46:28.8787006Z shellcheck sudo trang unzip wine32 wget xsltproc I get, after many snipped lines, the following error: 2020-07-24T22:50:38.3418072Z Processing triggers for libc-bin (2.31-0ubuntu9) ... 2020-07-24T22:50:38.4346359Z Processing triggers for libgdk-pixbuf2.0-0:i386 (2.40.0+dfsg-3) ... 2020-07-24T22:50:38.4858494Z Processing triggers for wine (5.0-3ubuntu1) ... 2020-07-24T22:50:40.0498037Z E: Could not configure 'libc6:i386'. 2020-07-24T22:50:40.0499968Z E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) 2020-07-24T22:50:40.0526698Z ##[error]Process completed with exit code 100. and there don't seem to be any other errors in the output until these lines, so I have no idea why does this happen. FWIW the same step of this workflow succeeds when run in Ubuntu 18.04-based GitHub virtual environment, but it doesn't have sufficiently up-to-date packages for building this software, so I can't use it and would really appreciate any workaround for this problem under 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078694] Re: Modal dialog broken on Unity
This bug is absolutely trivial to reproduce, here is a minimal GTK+
program which shows it:
#include gtk/gtk.h
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);
gtk_dialog_run(GTK_DIALOG(dialog));
gtk_widget_destroy(dialog);
}
int main(int argc, char** argv)
{
gtk_init(argc, argv);
GtkWidget* window = gtk_window_new(GTK_WINDOW_TOPLEVEL);
GtkWidget* menu = gtk_menu_new();
GtkWidget* mi = gtk_menu_item_new_with_mnemonic(_Test);
g_signal_connect(mi, activate, G_CALLBACK(activate_test), window);
gtk_menu_shell_append(GTK_MENU_SHELL(menu), mi);
mi = gtk_menu_item_new_with_mnemonic(E_xit);
g_signal_connect(mi, activate, G_CALLBACK (gtk_main_quit), NULL);
gtk_menu_shell_append(GTK_MENU_SHELL(menu), mi);
mi = gtk_menu_item_new_with_mnemonic(_File);
gtk_menu_item_set_submenu(GTK_MENU_ITEM(mi), menu);
GtkWidget* menubar = gtk_menu_bar_new();
gtk_menu_shell_append(GTK_MENU_SHELL(menubar), mi);
gtk_widget_show_all(menubar);
gtk_container_add(GTK_CONTAINER(window), menubar);
g_signal_connect(window, destroy, G_CALLBACK(gtk_main_quit), NULL);
gtk_widget_show(window);
gtk_main();
return 0;
}
The menu stays enabled while the message box is shown and so multiple
message boxes can be opened.
Ubuntu behaviour here totally breaks the application logic and is
incompatible with GTK+ on all the other systems. It's amazing that this
is apparently not considered to be a problem at all.
** Changed in: compiz (Ubuntu)
Status: Expired = Confirmed
--
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 Unity
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-gtk/+bug/1078694/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078694] Re: Modal dialog broken on Unity
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 Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-gtk/+bug/1078694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078694] Re: Modal dialog broken on Unity
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 people would have complained about this already) but it's not flexible enough to be used in wxWidgets. -- 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 Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1078694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984738] Re: Problem inhibiting the screensaver
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 a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984738 Title: Problem inhibiting the screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/984738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041888] [NEW] Several GTK menu signals not generated
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 being shown by themselves at all but by Unity. This has an unfortunate consequence of preventing us from enabling/disabling menu items dynamically when the menu is about to be shown in wxWidgets and I don't see how could we possibly work around this without some help from dbusmenu. Ideal would be if it could just forward these signals back to the application from which the menus were taken. ** Affects: libdbusmenu (Ubuntu) Importance: Undecided Status: New ** Tags: wxwidgets -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041888 Title: Several GTK menu signals not generated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/1041888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932067] [NEW] Minus associativity not correct in arithmetic expansions
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 factor being 0 neither 11 This can be worked around by using additional parentheses, e.g. % /bin/sh -c 'echo $(((10-2*1)-3))' 5 FWIW the bug doesn't exist in dash 0.5.7-2 from Debian but I can't find any mention of it being fixed in dash change log so I'm not sure whether it's a dash bug or something Ubuntu-specific. ** Affects: dash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932067 Title: Minus associativity not correct in arithmetic expansions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/932067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662077] Re: WxWidgets apps don't have menus
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, at GTK+ level, for menu proxying to work? We don't seem to do anything obviously wrong in our menu code which just uses the usual GTK menu functions. Thanks in advance for any ideas (or even pointers to better places for discussing this). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662077 Title: WxWidgets apps don't have menus -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 473702] Re: hpet driver backtraces when hyperthreading enabled
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89860] Re: /proc/acpi/button/lid/*/state always says open
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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 371197] [NEW] hal hangs for several minutes on startup
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 above
the one saying that HAL is being started. I don't know if the problem is
that it's started for the second time (FWIW doing /etc/init.d/hal
start later is instantaneous) or that hald hangs for some reason but in
any case it seems it ought not be ran the second time at all. And it
definitely shouldn't hang for so long.
Here is pstree output while it is hanging:
init-+-acpid
|-console-kit-dae---63*[{console-kit-dae}]
|-dbus-daemon
|-dd
|-4*[getty]
|-gpm
|-hald---hald-runner-+-hald-addon-acpi
||-hald-addon-cpuf
||-hald-addon-inpu
|`-hald-addon-stor
|-2*[ifplugd]
|-klogd
|-login---zsh---pstree
|-nmbd
|-rc---S24hal---hald---hald
|-smbd---smbd
|-sshd
|-syslogd
`-udevd
As you can see, hald is already running, yet it tries to launch another
one and blocks for what seems like ever (but in reality is just a
couple of minutes) when doing it.
Killing S24hal from another console allows the boot process to continue
[apparently] normally.
** Affects: hal (Ubuntu)
Importance: Undecided
Status: New
** Tags: boot regression
--
hal hangs for several minutes on startup
https://bugs.launchpad.net/bugs/371197
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 267141] Re: suspend button disappears after pm-utils upgraded to 1.1.2.4-1ubuntu2
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 make it completely useless on this machine (it's already on a good way after somehow dropping support for its videocard in fglrx which worked without problems for 4 years...). The ideological purity of kernel-based suspend is all very nice but some of us want to suspend their notebook *now*, not in a couple of years. -- suspend button disappears after pm-utils upgraded to 1.1.2.4-1ubuntu2 https://bugs.launchpad.net/bugs/267141 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 45920] Re: wxGetPasswordFromUser and wxGetTextFromUser return only one character.
This bug is invalid as wxGTK package is built in Unicode mode and so c_str() returns a wchar_t string which can't be printed with printf(). Use either wprintf() or wxPrintf() or use mb_str() (which you need to cast to const char * when using with a vararg function such as printf()) instead 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.net/bugs/45920 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 150318] Re: FileZilla crashes just after the start
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 (trivial) patch is here: http://svn.wxwidgets.org/viewvc/wx/wxWidgets/branches/WX_2_8_BRANCH/src/gtk/window.cpp?r1=45963r2=46514 HTH, VZ -- FileZilla crashes just after the start https://bugs.launchpad.net/bugs/150318 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68792] Re: amule crashes when trying to download kad nodes
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 there besides) and not in wx, so I believe this bug package field should be changed and that it should be closed when the new aMule version becomes available in Ubuntu. -- amule crashes when trying to download kad nodes https://bugs.launchpad.net/bugs/68792 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 123242] Re: Enable libwxmsw (with unicode and amd64)
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 minutes to each build is highly undesirable. -- Enable libwxmsw (with unicode and amd64) https://bugs.launchpad.net/bugs/123242 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114595] Re: Feisty HAL upgrade broke suspend on lid close
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/C138; FWIW acpid notices lid close/open just fine). So nothing happens when the lid is closed and this is a pretty serious bug which is especially jarring because it's a regression compared to Feisty. -- Feisty HAL upgrade broke suspend on lid close https://bugs.launchpad.net/bugs/114595 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89860] Re: /proc/acpi/button/lid/*/state always says open
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 is opened. Notice that this used to work just fine under Dapper and Feisty so this is definitely a regression. I'd be happy to provide any addition information which may be needed to narrow this down, for now I attach dmidecode output. ** Attachment added: output of dmidecode http://launchpadlibrarian.net/10244323/dmi-20071102 -- /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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 35375] Re: Scorched3d SIGSEGV on startup
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://launchpad.net/bugs/35375 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
