Sorry for the "me, too" comment but I just want to press how much of an
oversight this is for a very common use case. I was close to giving up
before I finally found a page detailing the "set as default" button's
hiding place.
--
You received this bug notification because you are a member of
Dammit, I missed the tenth birthday of this incredibly annoying bug.
Anyway, belated happy birthday!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/30378
Title:
Joystick
Public bug reported:
My system has been running quite smoothly for a while now but several
days ago, package operations kept failing. This is the output of apt-
get:
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1194254 is probably
the same bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1194253
Title:
package gconf2 3.2.5-0ubuntu2
*** This bug is a duplicate of bug 1194253 ***
https://bugs.launchpad.net/bugs/1194253
Public bug reported:
This is probably the same bug as
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1194253 but I don't
know which package is the culprit. Everything I said there applies to
this
... nd https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1194276
and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1194275.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gconf in Ubuntu.
I'm getting the exact same errors with a Crucial SSD (M4-CT064M4SSD2).
It happens spontaneously as far as I can see and I can't even shut down
the machine anymore. After a hard shutoff and rebooting, everything
works fine again. Until the next event. SMART doesn't show any problems
but I haven't
So in the latest version this is fixed? In that case this can be closed
I guessed :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1087722
Title:
inkscape crashes on open clipart
Public bug reported:
Steps to reproduce:
1. Open import from open clipart library dialogue
2. search for clock
3. click on roman clock
Inkscape will crash when trying to show a preview for (probably) this
clipart: http://openclipart.org/detail/79933
** Affects: inkscape
Importance:
The inkscape version string is: Inkscape 0.48.3.1 r9886 (Mar 29 2012)
on Ubuntu 12.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1087722
Title:
inkscape crashes on open clipart
*** This bug is a duplicate of bug 548992 ***
https://bugs.launchpad.net/bugs/548992
Same here on a Dell Vostro 1015 with an AR9285 Atheros card. Thomas'
power off/power on line only makes things worse (reconnect happens
immediately). On this machine there is practically no connection at all
** Also affects: network-manager-applet via
https://bugzilla.gnome.org/show_bug.cgi?id=540995
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** This bug has been flagged as a security vulnerability
** Visibility changed to: Private
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/969359
Title:
[keyboard]:
Zsolt, in terms of documentation there is http://docs.redhat.com/docs
/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1
-networkscripts-interfaces.html of course. NetworkManager is graphical
configuration tool which provides an easy way to make changes to the
various network interface
Mlx, but can I configure a device there, that NM *can* use? I always
took it that the devices there kind of supersede NM. So if I configure
eth0 and wlan0 to *not* do DHCP so that bond0 can, what will happen when
I'm in an environment where my static bonding configuration does not
apply and I need
I experience this bug with my thinkpad-x40 too. But i can only reproduce
it with this setting:
1. on my desktop (12.04) is a synergy server running (1.4.8-1~getdeb1)
2. on my laptop (12.04) is a synergy client running (1.4.8-1~getdeb1)
3. on my desktop the numlock is activated
4. I go from the
This would not only be awesome and dearly needed to seamlessly switch
between fast Ethernet and relatively slow wifi but also to speed up
networking where there is no gigabit (like on netbook hardware). Heck,
you could even add USB Ethernet adapters to the mix as you wished.
--
You received this
Sorry, maybe I'm slow but how is using 0.9.3.995+git201203081848
.bba834f-0ubuntu1whatever a fix to please use 0.9.4? I see it has many
if not all of the features of 0.9.4 but shouldn't a stable release be
used instead of a git build? LTS and all?
--
You received this bug notification because
Great this was fixed so quickly and thanks for the feedback Mathieu :)
--
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/956238
Title:
network-manager is almost unusable since
It seems fixed for me with the latest update.
--
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/956238
Title:
network-manager is almost unusable since the latest update
Status
I'm seeing slightly different symptoms. My nm-applet reports that there
are no network devices and I can't enable networking. Sometimes it also
says that network-manager is not running. It started today and luckily I
still get Ethernet although wifi is completely down.
I don't see the extremely
Oh, in the syslog only this turns up on *starting* the network manager
service:
Mar 15 23:15:35 Saffron kernel: [16250.034467] init: network-manager main
process (13864) terminated with status 1
Mar 15 23:15:35 Saffron kernel: [16250.034556] init: network-manager main
process ended, respawning
Here's what nm-applet says when started on a freshly booted system:
** WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager:
Did not receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply, the
For me this is easy to reproduce:
Just do a killall wpa_supplicant. Network Manager will reconnect
successfully (and a new wpa_supplicant process will be created) but from
now on nm-applet will wake up ten times per second to poll for something
that doesn't seem to be there.
--
You received
24 matches
Mail list logo
