The GTK2_RC_FILES theme workaround doesn't help me, nor does
UBUNTU_MENUPROXY.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade f
@daff Why would you assume a different bug? I have tried it with both forms
UBUNTU_MENUPROXY='' GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc
./adt-bundle-linux-x86_64-20131030/eclipse/eclipse -data .
and setting the theme in System Settings, and I _can_ use Eclipse for a while,
but s
AND on 13.10. Four years, and nobody gives a damn about making it
REALLY work.
So, what you're saying is "we introduced a "guest" login, but we don't
really want it to be able to do anything (who on earth suggested
"Firefox" was a reasonable workaround?).
So, I have a workaround. Forget about ev
Nice idea, David but no luck for me.
I start Eclipse with:
GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc
./adt-bundle-linux-x86_64-20131030/eclipse/eclipse -data .
and do Ctrl-F, and click on Find, Find, Close. Eclipse aborts at
g_object_get_qdata+0x18
I restart Eclipse, find the PID
I'll add that my test was not using Kepler, but David's suggesting
Kepler doesn't change things.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.
Fingers crossed, David! Simply installing libgtk-3-0 worked for the
trivial case I described above, where I could always make it fail (I
haven't upgraded oxygen, yet, and probably won't if this works without
it—I'm still using the override
GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc).
We used to have this. I'm sure, a decade ago, I could actually tell
whatever was managing the hibernate/suspend, in the gui, to remove certain
kernel modules on suspend and load them on resume. Now we're right back to
needing it.
derek
On Thu, Nov 17, 2016 at 1:59 PM, Hans Deragon wrote:
> This
btw, merely restarting Network Manager never worked for me. I have to
remove iwlwifi and reload it.
derek
On Thu, Nov 17, 2016 at 2:18 PM, Derek Broughton
wrote:
> We used to have this. I'm sure, a decade ago, I could actually tell
> whatever was managing the hibernate/suspend, in the gui, to r
@JaSauders I think the downside is that restarting NetworkManager, on a
system that doesn't have any problem with network connections after a
suspend event (and that surely must be most systems, or this would be
fixed already) will result in a much slower reconnection to the network.
--
You recei
You're kidding? "no longer affects:network-manager"
It certainly did as recently as yesterday!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1585863
Title:
WiFi malfunc
Seems to me that if NM stalls due to a race condition, then restarting NM
*is* a workaround, so yes, adding additional scripts to systemd is a
solution, but not the "answer".
derek
On Fri, Feb 3, 2017 at 1:11 AM, Tony Espy <1585...@bugs.launchpad.net>
wrote:
> @Kevin
>
> NetworkManager already h
I did have to upgrade oxygen as specified by David, too, as even with
the Raleigh theme I was getting failures (much less frequent or
reproducible than before upgrading libgtk, though). After upgrading
oxygen, I didn't experience any further failures.
Of course, now I'm in the process of upgradin
What would have fixed it? Given that there are all kinds of things that
have worked for some, and not for others, unless we know a specific
change that should fix the behaviour, I'd say there's still a bug.
--
You received this bug notification because you are a member of Desktop
Packages, which
because restarting network-manager from sleep.d isn't even a workaround,
let alone a fix. With that, my network successfully reconnects just
about as often as if there is nothing in sleep.d.
Which, apparently, would be because /etc/pm/sleep.d is never invoked.
--
You received this bug notifica
I finally worked around my problem by adding a script in /lib/systemd
/system-sleep/:
$ cat /lib/systemd/system-sleep/12_wifi
#!/bin/bash
case $1 in
"post")
# disable/enable wifi
rfkill block wifi; rfkill unblock wifi
logger "reenabled wifi"
;;
You can try having the script do "modprobe -r" and "modprobe" on your wifi
module. That should always work, but seemed like overkill in my case. In
any case, these are workarounds, not fixes.
On 4 Aug 2016 6:01 a.m., "Aleve Sicofante" wrote:
> @auspex: Your
Please don't suggest installing non-standard packages as a "fix" for
broken packages in the default setup. Yeah, Network-manager is a pain
and always has been, but until the distros choose to focus on Wicd
rather than network-manager, NM is the tool that HAS to work to keep
interest in Linux up.
-
17 matches
Mail list logo
