Public bug reported:
Flatpak seems to have serious issues on kubuntu 20.04, at least with
some applications that immediately hang when a file dialog is shown.
One of them that makes the issue well reproducible for me on kubuntu
20.04 is shotcut
On zesty the issue is still present.
A minority of the engines have transitioned to proper multiarch support
(e.g., oxygen-gtk). Most of them seem to still have conflicting amd64
and i386 packages (e.g., aurora). Some have the .so file implemented the
engine in legacy places (nodoka).
--
You
Sorry, I'm not understanding your comment.
What I understood is that the systemd developers said "It is not our
responsibility if ubuntu does not boot, this is not a systemd bug! In
fact, the issue in booting is caused by some quota related units,
shipped by Ubuntu, that are not part of systemd".
Got it! Sort of...
Misabling quotas make the system boot reliably.
No clue why. It may not be a race, rather the fact that the initial
quota check is supposed to happen only in certain cases.
No idea. Debugging boot with systemd is beyond my expertise.
Masking the systemd quota.service (the
Public bug reported:
After an upgrade from xenial to yakkety, the system does not boot
reliably. Only 1 boot over 3-4 seems to succeed.
Quite often, the system seems to hang during boot and then drops into an
emergency prompt.
Pressing esc during the boot to show what is going on reveals that
Public bug reported:
To reproduce
systemctl restart some unit
AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to manage system services or units.
Multiple identities can be used for authentication:
1. Sergio Callegari (callegar)
2. Sergio
I guess there is no hope for this. Still present in utopic.
Installing a gtk 32 bit application on a 64 bit ubuntu system gives tons
of warnings about the wrong elf class (ELFCLASS64) for the engine and
the applications shows completely unstyled.
I see this with the nodoka engine.
Furthermore,
Closed as invalid as agreed.
** Changed in: indicator-bluetooth (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to indicator-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1242462
just upgraded to 13.10. bluetooth is now totally useless.
adding device: timeouts if you tick for dun networking
selecting browse files from bluetooth indicator: does nothing at all.
does not even open nautilus
sending files: GDBus.error.org.openobex.Error.Failed:Unable to request
session
Public bug reported:
Hi. Consider the following setup. A ubuntu quantal machine with unity
and a kubuntu quantal laptop.
I want to admin the machine remotely from the laptop. I ssh into it with
X11 forwarding. Now, I realize that an extra terminal would be nice, so
I start gnome-terminal on the
Still there. As of quantal the i386 flavor of gtk engines cannot be
installed side to side to the x86_64 bit version.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk2-engines in Ubuntu.
https://bugs.launchpad.net/bugs/902128
** Package changed: ubuntu = gtk+2.0 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1075928
Title:
Please, silence IA__gdk_error_trap_pop: assertion `gdk_error_traps !=
Public bug reported:
This results from incorrectly assuming that everybody has a 96 dpi
screen.
In KDE settings you can configure gtk applications appearence to use the
qtcurve style that makes gnome apps consistent in look with kde apps and
- most important - allows their appearance to be
Public bug reported:
On 64 bit systems, running 32 bit applications that use gtk is a pain
because gtk tries to load 64 bit versions of the gtk engines.
A typical example of this is acroread.
You get tons of messages like
Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF
14 matches
Mail list logo
