Has this been discussed with upstream developers as mentioned in comment
#8? This issue still exists in 0.9.8.8-0ubuntu28 (14.10). Don't know
about newer NM versions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubun
Public bug reported:
Immediately after the fix for #269904 landed in trusty-updates via
compiz 1:0.9.11.3+14.04.20150122-0ubuntu1, my 14.04 machine with an
NVIDIA card and using the nvidia-304 driver became unusable -- symtoms
include compiz process high CPU (100%), UI freeze right after logging i
The version of compiz that landed in trusty-updates
(1:0.9.11.3+14.04.20150122-0ubuntu1) with the fix for this bug causes
compiz process high CPU and UI freeze right after logging in, making the
system unusable. I no longer experience these problems after downgrading
to the previoius version in tru
Hi Ryan,
Thanks for the quick reply. I indeed have a GeForce 6150SE so bug
1404015 could be a match in my case. I will upgrade to the latest
version of compiz in trusty-updates, disable x11-sync, and report back.
The question I'd have is how to explain that going back to the previous
compiz versi
Hi Christopher,
Here's my OpenGL renderer string:
$ glxinfo | grep "OpenGL renderer string"
OpenGL renderer string: GeForce 6150SE nForce 430/integrated/SSE2/3DNOW!
Cheers,
Eloy Paris.-
--
You received this bug notification because you are a member of Desktop
Packages, which i
alse
and then I ran "dconf update".
Anyway, is there a performance penalty by running with enable-x11-sync
disabled? Just wondering if I should go back to the previous Compiz
version or if it's okay to run the latest plus this workaround.
Cheers,
Eloy Paris.-
--
You received this
oid buying a machine with an NVIDA
card in the future -- I have had better luck with Intel GPUs.
Cheers!
Eloy Paris.-
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1424013
Title:
C
Is this bug about a memory leak, about the applet stopping to work, or
both? If it is about the applet stopping to work after a while then this
bug is not fixed -- the issue still exists in 12.10.
Just wondering about what exactly is being claimed is fixed.
--
You received this bug notification
I gave up trying to get the NM applet to work by using pkill nm-applet
&& nm-applet &
I mean, it works, but since I have to be in a terminal window to run
pkill anyway, it is just easier for me to use one command to connect to
the network that I want. So, I just run this, which works perfectly ev
Oh my Gosh, thank you so much for fixing this.
Will this be backported to other releases?
Cheers,
Eloy Paris.-
On 06/07/2013 07:11 AM, Launchpad Bug Tracker wrote:
> This bug was fixed in the package libdbusmenu -
> 12.10.3daily13.06.07-0ubuntu1
>
> ---
&
Agreed this should be treated as a bug since avahi-daemon is not a
dependency. Workaround is simple: edit /etc/init/cups.conf and remove
the line with "and started avahi-daemon".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubu
Output from "dbus-monitor --session --monitor
interface=com.canonical.dbusmenu | tee dbus-monitor-output.txt" that
corresponds to the nm-applet output in the previous comment, i.e. taken
at the same time. Also stopped after a few hours when the nm-applet
menus stopped working.
** Attachment added:
Output from G_MESSAGES_DEBUG=nm-applet-indicator nm-applet | tee nm-
applet-debug.txt.
Stopped running after the menus in the applet became non-functional.
This took several hours. I saw many occurrences of lines like:
(nm-applet:4661): nm-applet-indicator-DEBUG: Just set up menu for ID 36070
(nm
There are two gst-launch-xx binaries in my system (13.04): gst-
launch-0.10 and gst-launch-1.0. Playing an Asterisk-generated .wav file
with gst-launch-0.10 works fine but playing it with gst-launch-1.0
results in the garbled sound.
--
You received this bug notification because you are a member o
I've seen this too since I upgraded from 11.10 to 12.04 (never
experienced this prior to 12.04). I would add that it is not just the
VPN Connections submenu that stops working; it's any entry in the
applet's menu that stops working. When this happens, the workaround that
I use is:
kill -1 `pidof n
#985028 could be a duplicate of this bug.
I do not think the problem is related to suspend-resume cycles but
rather to the scanning and discovery of wireless networks that typically
happens during suspend-resume cycles.
--
You received this bug notification because you are a member of Desktop
Pa
This could be a duplicate of bug #933300.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/981847
Title:
nm-applet does not respond to choices I make in networking menu
Agreed, this could be a duplicate of bug #933300 (or the other way
around since this bug [bug #930563] is newer).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/930563
Ti
There seem to be lots of reports about this same behavior. Bug #930563
is the earliest bug I've been able to find, but I am still looking for
the first report, i.e. master bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manag
This bug could be a duplicate of bug #930563, since bug #930563 was
reported first and seems to be the same issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/933300
T
Could be a duplicate of bug #930563. No need to restart the machine;
just open a terminal a run:
kill -1 `pidof nm-applet`
nm-applet &
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchp
Bug #930563 is probably the master bug since it was reported before
#933300 and it's about the same issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/981847
Title:
I was having this problem with a Sansa Clip Zip. I changed USB mode (on
the Sansa's settings) from MTP to MSC and now the Sansa is mounted just
fine and shows up as a mass storage device.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gv
The fix for this bug (in gnome-desktop3 3.2.0-0ubuntu2) seems to break
my system: after getting the lightdm greeter and entering my user
password to log in, I get a black screen, the screen flickers a few
times like if X were crashing a few times. A few seconds later I do get
the Unity interface bu
setup when this happens (this is a laptop
with a single screen).
* nVidia driver.
* Might not be X crashing. Instead, it seems like whatever is running on
top of X (lightdm) is crashing. I do see the typical X-shaped cursor for
a bit.
Cheers,
Eloy Paris.-
--
You received this bug notification be
l way
and makes the issue go away.
2. There were some package upgrades. There was nothing out of the
ordinary with the possible exception of a unity upgrade.
In /var/crash, there was a core dump for check_gl_textur, but nothing
else around the same time.
Cheers,
Eloy Paris.-
--
You received
26 matches
Mail list logo
