*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
OK, the problem is obvious and exactly the same as for the other report.
/lib/dbus-1.0/dbus-daemon-launch-helper shouldn't be owned by the
'avahi' group, but by 'messagebus'.
See my comment at
Cool, much thanks Maxim!
The bug should not be closed though, since it's not fixed in Maverick
yet. I've also opened a task for Lucid since the patch could be
backported to benefit Acer users.
For kernel developers, here's the commit message:
ACPI: Store NVS state even when entering suspend to
What problem still exists? ;-) There were three of them, and I got no
answer to confirm. So I'm closing it, please open a new report with
detailed explanations.
David: feel free to reopen when you can answer my question.
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete =
Please don't reopen a fixed bug at random. Why on earth do you believe
this is the same problem?! None of the symtoms you describe is similar.
It's not because it has high priority that people will fix your bug more
quickly. As you said yourself, I checked and /etc/groups did not appear
to be
Gerry, does the procedure explained here fixes your probem? Of course,
this feels wrong, but one explanation can be that some files on the
system still have the GID corresponding to the messagebus UID, and going
back to that value fixes the problem. You could also find those files
and fix their
As I suggested on the other report (bug 295405), could you try setting
UID for user messagebus to 102 (if that's not used by another one)? More
generally, please follow the procedures I described there to check that
it's not the same problem (very likely).
(BTW, when I said liboobs, I thought
True, but you have to find a better place for it! ;-) The only other
area I could think of was behind the users list, but that wasn't really
nice either.
Anyway, users-admin is going to be replaced by accounts-dialog, so this
will probably never be fixed. Thanks for reporting, though.
** Changed
** Bug watch added: GNOME Bug Tracker #619588
https://bugzilla.gnome.org/show_bug.cgi?id=619588
** Also affects: gdm via
https://bugzilla.gnome.org/show_bug.cgi?id=619588
Importance: Unknown
Status: Unknown
--
ampersand in user real name freezes login screen
I tried to apply the patch mentioned in #11:
http://www.mail-archive.com/linuxwacom-de...@lists.sourceforge.net/msg00736.html
to the current version of linuxwaxom in Lucid and recompiled the deb package.
The buttons on my Intuos3 work, but the left and right touchpad not -
nothing happens and
Thanks for your report. Could you run the command:
'sudo apt-get install --reinstall gnome-system-tools'
and see if that fixes your problem?
The file triggerring the error is a file present in 2.28 but not in
2.30. But I don't know why it makes the upgrade fail. Nobody has
reported this problem
*** This bug is a duplicate of bug 570828 ***
https://bugs.launchpad.net/bugs/570828
If you're not using Ubuntu Studio, you have NetworkManager, else you can
install it, or wait for the tab to come back (hopefully). The decision
was made by developers that didn't know Studio wasn't installing
'sudo update-rc.d cups defaults'
And for the tool, a new one is being developed ATM. See
http://jacob.peddicord.net/blog.html
--
System Administration Services (services-admin) missing
https://bugs.launchpad.net/bugs/437905
You received this bug notification because you are a member of Ubuntu
Any pointers to the discussion? I can't see anything new on the upstream
report.
--
Acer Aspire 5720 hangs on second resume from suspend, i.e. suspends only once
[BIOS PROBLEM]
https://bugs.launchpad.net/bugs/160763
You received this bug notification because you are a member of Ubuntu
Bugs,
So that's bug 552221. Just add gnome-voume-control-applet to
System-Preferences-Startup Applications. We should find something for
the Shell since it won't use indicators.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed = Triaged
** Changed in: gnome-shell (Ubuntu)
Importance:
no!chance: See bug 160862 rather. This is a know problem that is fixed
in Lucid and should be fixed at some point in Hardy too. Though the
original issue is that you had weird characters in your /etc/group file,
nowadays users-admin shouldn't get crazy when it encounters this kind of
thing.
I'm
*** This bug is a duplicate of bug 433654 ***
https://bugs.launchpad.net/bugs/433654
** This bug has been marked a duplicate of bug 433654
[Karmic][Lucid] Only one user has sound; no hw shows in Sound Preferences
--
[Users and Groups] Advanced Settings: User Privileges on using
No, that's really the same bug. users-admin shouldn't show that group at
all since it's plainly broken. This behavior doesn't make sense. That's
why I said we should remove the audio group, which would fix the bug for
all people that were added to it without noticing.
If that doesn't seem right,
Przemysław: edit /etc/network/interfaces (e.g. with 'sudo pico
/etc/network/interfaces'), and remove everything BUT the first lines:
auto lo
iface lo inet loopback
Then you can add the interface using System-Preferences-Network
Connections
--
gnome-network-admin on UbuntuStudio doesnt allow to
Chauncellor: at least, if you were able to play with permissions, you
should be able to find this bug report. With the new users-admin, it's
harder to tweak fine-grained permissions, so hopefully nobody will do
this anymore.
--
[Karmic][Lucid] Only one user has sound; no hw shows in Sound
Please don't open new tasks against random projects without explanation
and actual reasons. Thanks!
** Changed in: acpi-support
Status: New = Invalid
--
High frequency of load/unload cycles on some hard disks may shorten lifetime
https://bugs.launchpad.net/bugs/59695
You received this
Fix released and uploaded for a long time.
** Changed in: liboobs
Status: Fix Committed = Fix Released
** Changed in: liboobs (Ubuntu)
Status: Triaged = Fix Released
--
shares-admin crashes on start when udev has been restarted without reboot
That would be interesting, indeed. But are you sure that's the same bug?
** Changed in: gdm (Ubuntu)
Status: Incomplete = Triaged
--
gdm-simple-greeter always crashes on start
https://bugs.launchpad.net/bugs/573099
You received this bug notification because you are a member of Ubuntu
Confirmed with 2.6.34 here, no hope, it's been like that for more than a
year...
--
[i915] Crash after suspending (NULL pointer dereference in intel_crt_detect())
https://bugs.launchpad.net/bugs/553176
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for the report. Do you mean you were removing two accounts by
selecting them both at the same time, and clicking Delete once? Did the
crash happen before or after the confirmation dialog asking whether to
remove user files?
** Changed in: gnome-system-tools (Ubuntu)
Status: New =
** Changed in: duplicity (Ubuntu)
Importance: Undecided = Medium
** Changed in: duplicity (Ubuntu)
Status: New = Triaged
--
Assertion error time not moving forward at appropriate pace
https://bugs.launchpad.net/bugs/579958
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 579958 ***
https://bugs.launchpad.net/bugs/579958
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 579958
Assertion error time not moving forward at appropriate pace
--
duplicity crashed with AssertionError in
HP: and what does 'ps x | grep keyring' returns on your box after
booting without your script?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Seems to be the same issue then. Are you using autologin or password-
less login?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Ah, so it boils down to the password-less login case, see bug 525642.
Fingerprints can't be used to unlock keyrings because no external data
is provided: the system has to know your fingerprint to check it's the
same. So gnome-keyring-daemon must be hanging waiting for a password
that is not
I've just realized that since the beginning I'm saying bug 525642 when I
meant bug 583428.
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Yes, but that doesn't change the problem. Bug 583428 is about g-k-d
hanging when started without a password, whether it actually needs one
or not. ;-) BTW, let's comment this on that report rather than here,
which may not be the same issue.
--
gnome-keyring-daemon fails to start
use_md5 parameters has been removed in 2.10, we now use chpasswd to set
the password, and don't play with encryption methods.
** Changed in: system-tools-backends (Ubuntu)
Status: New = Fix Released
--
including a file leads to confusion about whether md5 is being used
That would be a different bug then. Could you paste here the line from
/etc/passwd which was the problem? National characters shouldn't be an
issue as long as they are in UTF-8; if they aren't, then some strange
tool must have gone wrong when writing to it.
Closing the bug since in Lucid we no
** Changed in: gdm (Ubuntu)
Status: Confirmed = Triaged
--
Unable to change options on passwordless login
https://bugs.launchpad.net/bugs/508552
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Package changed: gnome-system-tools (Ubuntu) = gnome-control-center
(Ubuntu)
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided = Low
--
Proxy auto-config (PAC) not usable by some applications
https://bugs.launchpad.net/bugs/587097
You received this bug notification
Nice to see hard bugs in U1 are getting fixed! ;-)
--
nautilus crash in IA__g_str_hash() when running u1sdtool --subscribe-folder
https://bugs.launchpad.net/bugs/570261
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
g-k-d should be started by it's PAM module. If it's not started on login
before any app tries to use it, then it's the problem. What does
/etc/pam.d/gdm contains?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a
Yeah, the problem is that the menu is shared with the groups, so fixing
this would require splitting it from there. It may be easier to remove
completely this menu, since it's mainly redundant. But definitely not a
very serious issue...
Don't bother reporting this upstream, I manage the bugs here
Upstream has committed a fix which should be made available with gnome-
keyring 2.30.2.
--
if ( users-admin - password: Not asked on login) gnome-keyring-daemon hangs
https://bugs.launchpad.net/bugs/583428
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Maybe you should remove the .service file you added manually. Bug 525642
is fixed now, and manual tweaks like that can lead to problems. It's
possible that gnome-keyring is started via D-Bus before the PAM module
loads it, so it lacks the --login option that automatically unlocks the
keyring. But
That's because Samba and NFS no longer use SysV boot script, but Upstart
jobs. Thus, they are not detected even if they are installed. We need a
temporary fix in Lucid for that, possibly a ugly hack.
In the long term, though, that's going to be a problem: we need minimal
support for Upstart jobs,
** Branch linked: lp:~nalimilan/ubuntu/lucid/gnome-system-tools/shares-
services
--
shares-admin doesn't see NFS and SMB installed (no support for Upstart jobs)
https://bugs.launchpad.net/bugs/574046
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Yeah, I know, normally the --login option should be present in your case, but
for some reason it's not. I don't really see why it should work differently on
your system than on mine (say). Do you have a personal config starting g-k?
e.g. check with:
ls ~/.config/autostart/*keyring*
Else, you
But that's not a problem with time-admin, which is not supposed to
control ntpdate at all. It's just that ntpdate shouldn't run by ifup
when interfaces are enabled. Else, there's no point in optionally
installing the ntp daemon.
I suspect ntpdate is not run when your connections are managed using
*** This bug is a duplicate of bug 322518 ***
https://bugs.launchpad.net/bugs/322518
OK, I've just found bug 322518 which is about the same issue.
** This bug has been marked a duplicate of bug 322518
No obvious way to prevent ntpdate to be run when interface are brought up
--
ntpdate
I'd argue ntpdate shouldn't be started at all by default. I can see no
reason why people would prefer using ntpdate rather than ntpd. Desktops
should ship without NTP enabled (i.e. ntp package not installed, but
installable via time-admin), and server should ship with it installed.
Current
See also bug 322518. I think we want to get rid of ntpdate, and use ntpd
everywhere, which would be more consistent.
** Changed in: ntp (Ubuntu)
Status: New = Triaged
** Changed in: ntp (Ubuntu)
Importance: Undecided = Low
--
Consider replacing ntpdate calls by 'ntpd -g'
Is this still buggy in Lucid?
Anyway, I think fixing bug 583994 by replacing ntpdate with ntpd would
solve this the right way.
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
https://bugs.launchpad.net/bugs/83604
You received this bug notification because you are a member
ntpdate is not supposed to be run all the time AFAIK, it's mainly here
to allow synchronizing the clock manually (what the Sync Now button is
time-admin does), and creating scripts to do that. On my box, syslog
doesn't contain anything related to ntpdate... Can't you think of any
package you may
Is that without autologin and without password-less enabled?! That seems
very similar to what we get when it's on.
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
But that's not a problem with time-admin, which is not supposed to
control ntpdate at all. It's just that ntpdate shouldn't run by ifup
when interfaces are enabled. Else, there's no point in optionally
installing the ntp daemon.
I suspect ntpdate is not run when your connections are managed using
*** This bug is a duplicate of bug 322518 ***
https://bugs.launchpad.net/bugs/322518
OK, I've just found bug 322518 which is about the same issue.
** This bug has been marked a duplicate of bug 322518
No obvious way to prevent ntpdate to be run when interface are brought up
--
ntpdate
I'd argue ntpdate shouldn't be started at all by default. I can see no
reason why people would prefer using ntpdate rather than ntpd. Desktops
should ship without NTP enabled (i.e. ntp package not installed, but
installable via time-admin), and server should ship with it installed.
Current
See also bug 322518. I think we want to get rid of ntpdate, and use ntpd
everywhere, which would be more consistent.
** Changed in: ntp (Ubuntu)
Status: New = Triaged
** Changed in: ntp (Ubuntu)
Importance: Undecided = Low
--
Consider replacing ntpdate calls by 'ntpd -g'
Is this still buggy in Lucid?
Anyway, I think fixing bug 583994 by replacing ntpdate with ntpd would
solve this the right way.
--
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
https://bugs.launchpad.net/bugs/83604
You received this bug notification because you are a member
Kangaroo: See comment #7 above. You just have to mark the connection as
Available to all users.
--
Wifi auto-connection asks for keyring password
https://bugs.launchpad.net/bugs/388593
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
*** This bug is a duplicate of bug 573387 ***
https://bugs.launchpad.net/bugs/573387
OK, this is actually a duplicate. We're debugging this upstream ATM.
** This bug has been marked a duplicate of bug 573387
gnome-keyring-daemon fails to start
--
if ( users-admin - password: Not asked
** Summary changed:
- gnome-keyring-daemon fails to start
+ gnome-keyring-daemon fails to start when password-less login is enabled
** Changed in: gnome-keyring (Ubuntu)
Status: New = Triaged
** Changed in: gnome-keyring (Ubuntu)
Importance: Low = Medium
--
gnome-keyring-daemon
** This bug is no longer a duplicate of bug 573387
gnome-keyring-daemon fails to start
--
if ( users-admin - password: Not asked on login) gnome-keyring-daemon hangs
https://bugs.launchpad.net/bugs/583428
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ah, that was what I feared: your bug is different from the password-less
issue. So let's say the latter is bug 525642, and deal with your problem
here. What does 'ps x|grep keyring' return, with and without autologin
enabled? What errors do you get in /var/log/auth.log in both cases?
(The logs
*** This bug is a duplicate of bug 542183 ***
https://bugs.launchpad.net/bugs/542183
** This bug has been marked a duplicate of bug 542183
[users-admin] Changing UID doesn't work
--
chainging user or group ID does nothing
https://bugs.launchpad.net/bugs/583951
You received this bug
Fix committed upstream, to be released with gnome-system-tools 2.30.2.
** Changed in: gst
Status: Confirmed = Fix Committed
** Bug watch added: GNOME Bug Tracker #619354
https://bugzilla.gnome.org/show_bug.cgi?id=619354
** Also affects: gnome-control-center via
Thanks for your report. This would be a bug in gnome-keyring-daemon,
which should start and ask for the password if there's any.
Is the keyring daemon running or not? You can check this using 'ps x |
grep gnome-keyring-daemon'. If it's not running at all, could you run
'gnome-keyring-daemon -sf'
I'm able to reproduce the problem. Actually, gnome-keyring-daemon is
hanging on login because with the --login option, it's waiting for the
password to be passed by PAM via stdin, which never happens. While it's
in this state, it won't anwser D-Bus messages, and will also prevent
D-Bus from
I think the upstream report is not related, see bug 525642 instead.
You're not using users-admin's password-less login option (Password:
Not asked on login), are you?
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are
** Changed in: openoffice.org (Ubuntu)
Status: Confirmed = Triaged
** Changed in: openoffice.org (Ubuntu)
Importance: Undecided = Medium
--
[upstream] Crash in SwRTFWriter::OutBookmarks () when saving some RTF documents
https://bugs.launchpad.net/bugs/563931
You received this bug
Le vendredi 21 mai 2010 à 12:20 +, starfear a écrit :
But it's hanging when start with ( /usr/bin/gnome-keyring-daemon --daemonize )
without --login option.
What do you mean? Have you ensured you had killed previous instances of
the daemon before starting it? How do you know it's hanging
Indeed. I thought I had seen the contrary. So the problem lies somewhere
else, we'd need to see if it's hanging in some function call, or if it's
simply not grabbing the D-Bus name. It's not impossible that when
logging in without password, the race condition described by bug 573387
happens. Just
Holden: Check your ~/.xsession-errors for the error messages printed
above. If you can't find them, please open a new bug.
--
polkit-gnome-authentication-agent-1 not started on login
https://bugs.launchpad.net/bugs/568748
You received this bug notification because you are a member of Ubuntu
** Changed in: ubuntuone-client (Ubuntu)
Status: New = Triaged
--
Can't create UDF with non-ASCII names (valid UTF-8)
https://bugs.launchpad.net/bugs/557160
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
See http://www.unixtutorial.org/2009/01/disable-service-startup-in-
ubuntu/, or install bum.
--
Support Upstart
https://bugs.launchpad.net/bugs/435935
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can confirm this bug, that's a long-known issue, I thought there was
already a bug open for that.
The problem is that access to the public WebDav folder is always done via the
guest Apache user, and I guess Apache defaults to mapping it to the 'nobody'
system user when creating new files. See
Oh, silly me! I was testing my Samba public dir when checking gnome-
user-share configuration files... I've now checked that g-u-s works
here, forget what I said.
Armando: Are you sure you're not doing the same mistake as I did? ;-)
When you go to the Network place, what's the exact label of your
I've actually identified the root cause of this bug, which is in
liboobs: runlevels list for the NTP service wasn't cleared when
updating, which caused the script to be disabled when trying to enable
it. This is fixed with liboobs 2.30.1, so the hack in 82_gst-packages-
time-admin.patch (one line)
Right, but I'd rather get services-admin back. Note there's a Google
Summer of Code project to write an Upstart configuration tool, so this
string problem may vanish before we fix it by hand.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Low
** Changed in:
** Visibility changed to: Public
** Changed in: firefox (Ubuntu)
Status: New = Triaged
** Summary changed:
- firefox-bin crashed with SIGSEGV in _init()
+ firefox-bin crashed with SIGSEGV in _init() (loading plugins)
--
firefox-bin crashed with SIGSEGV in _init() (loading plugins)
You have to install nm-applet (network-manager-gnome) package, and
maybe run it using 'nm-applet'.
--
gnome-network-admin on UbuntuStudio doesnt allow to configure either wired
networks or wireless
https://bugs.launchpad.net/bugs/570828
You received this bug notification because you are a
Ah, if you're using Ubuntu Studio, then the package is indeed installed
by default, which is a severe problem. See bug 570828.
gnome-nettool isn't the program you're thinking of, but rather a status
applet. network-admin, from the gnome-system-tools source package, and
the gnome-network-admin
** Summary changed:
- gnome-nettool: documentation describes a removed feature (connections tab)
+ [network-admin] Documentation describes a removed feature (connections tab)
--
[network-admin] Documentation describes a removed feature (connections tab)
https://bugs.launchpad.net/bugs/566811
Nathan: Please open a new bug. There's no point in mixing different
issues on the same report. I think in your case the swap partition may
be too small to hold both the RAM and already present swap memory, but
this would need investigation. Just try hibernating right after starting
the system, and
Public bug reported:
Binary package hint: kdenlive
Ubuntu 10.04 x86_64
kdenlive 0.7.7.1-0ubuntu1
ffmpeg4:0.5.1-1ubuntu1
melt 0.5.4-1
Kdenlive renders white artifacts in black areas of the image - both in
preview and output video, no matter which format is
But how do you run gdm-simple-greeter from a debugger? I've not been
able to start it manually.
--
gdm-simple-greeter always crashes on start
https://bugs.launchpad.net/bugs/573099
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Bug watch added: Gentoo Bugzilla #305309
http://bugs.gentoo.org/show_bug.cgi?id=305309
** Also affects: gentoo via
http://bugs.gentoo.org/show_bug.cgi?id=305309
Importance: Unknown
Status: Unknown
--
The function of Users and Groups can not be accessed.
Weird issue... I've found a duplicate in Gentoo, so that's not an Ubuntu
bug. Running out of ideas...
** Changed in: gnome-system-tools (Ubuntu)
Status: Incomplete = Triaged
** Summary changed:
- The function of Users and Groups can not be accessed.
+ Fails to launch modules: Can't
Upstream has backported the fix to the stable branch, will be made
available with 2.30.2 or the like.
--
anjuta-tags crashed with SIGABRT in __kernel_vsyscall() with JavaScript code
https://bugs.launchpad.net/bugs/575636
You received this bug notification because you are a member of Ubuntu
Bugs,
If you want to set specific settings for several users regularly, just
edit /etc/gnome-ssytem-tools/user-profiles.conf and change the default
profile to suit your needs. Just give me one use case where showing
settings on user creation would be really better than changing them
later.
The GDM
What do you mean? System users have to stay hidden by default.
--
[users-admin] No option to show system users
https://bugs.launchpad.net/bugs/574379
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Feel free to provide a patch, but it would have to be in line with the
cleaned UI. I don't really see the benefit, though: what on earth would
you want to do with a list cluttered with tens of system users? Change
their names? Their UIDs? That's a rare operation, and it's performed
better using
Hmm, right, that explains why it's so badly written. This file doesn't appear
to be shipped with any package.
I was misled by bug 325706, where creating this file was a workaround.
** Changed in: xorg (Ubuntu)
Status: Triaged = Invalid
--
/etc/dbus-1/system.d/xserver-xorg.conf allows
It should be OK, but:
1) it's not easy for me to see if something went wrong in that process
2) it's actually harder for you, because you could just have copied/pasted the
command to a console, without the risk of getting it wrong
So the result is?
--
The function of Users and Groups can not
Have you read the comments? I can't be sure you're experiencing the same
bug. GDM problems can be very different. Have a look at /var/log/gdm/ as
I explain above. My workaround is to remove /var/lib/gdm, as I said.
--
gdm-simple-greeter always crashes on start
And if you run:
sudo apt-get install --reinstall perl perl-base perl-modules
system-tools-backends
What does this command say:
ls /usr/lib/perl5/Net/DBus.pm
Is that a system upgraded from a previous Ubuntu version, or a clear
install?
--
The function of Users and Groups can not be accessed.
Seems to work here, but I don't think the bug is properly solved. The
problem is still the same: D-Bus configuration doesn't allow for more
than 3 X displays (:0, :1 and :2), so others will fail.
But maybe I'm missing something, because here Xephyr is on :11 and it
works...
--
[jaunty] Xephyr
** Visibility changed to: Public
** Bug watch added: GNOME Bug Tracker #617734
https://bugzilla.gnome.org/show_bug.cgi?id=617734
** Also affects: anjuta via
https://bugzilla.gnome.org/show_bug.cgi?id=617734
Importance: Unknown
Status: Unknown
** Changed in: anjuta (Ubuntu)
Public bug reported:
Binary package hint: ubuntu-docs
In Lucid, network-admin has no Connections tab, which is still mentioned
in the modems configuration page. So network-admin should be removed,
and ModemManager be presented instead. It's installed by default and
integrates correctly with
Ah, indeed. Documentation shouldn't mention it as the solution to set up
modems. Note you can use System-Preferences-Network Connections for
that. I've filed bug 575694.
--
Network Admin Tool Missing Connection Tab
https://bugs.launchpad.net/bugs/574067
You received this bug notification because
By docs, do you mean Ubuntu docs from System-Help and Support, or doc
pages you get when clicking on the Help button from the network tool
itself? See bug 575694 for the former case, which should be fixed with a
higher priority than the latter.
** Package changed: gnome-nettool (Ubuntu) =
*** This bug is a security vulnerability ***
Public security bug reported:
Binary package hint: xorg
In Lucid (xserver-xorg1:7.5+5ubuntu1), /etc/dbus-1/system.d/xserver-
xorg.conf reads:
busconfig
policy context=default
allow own=org.x.config.display0/
We don't need X.org logs and hardware information for that bug. :-)
** Changed in: xorg (Ubuntu)
Importance: Undecided = Medium
** Changed in: xorg (Ubuntu)
Status: Incomplete = Triaged
** Tags removed: needs-lspci-vvnn needs-xorglog
--
/etc/dbus-1/system.d/xserver-xorg.conf allows
You forgot the '--reinstall' option, that's why nothing happened.
--
The function of Users and Groups can not be accessed.
https://bugs.launchpad.net/bugs/574078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
701 - 800 of 2956 matches
Mail list logo
