Updated to nautilus - 1:3.6.3-0ubuntu16.
The bug is still present. Please fix it again.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1085320
Title:
White borders around
Alt A of Matthew seems to be fine!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown from greeter does nothing when multiple accounts open
To manage
@Kai,
You're right. We have found that both behaviors, the one you describe
and the main related to this bug, have the same root: policykit
I haven't tried the patch commented by James (comment #33), but it's
maybe the solution you're searching for.
Anyway, if you want to do it by hand, the
Thank you so much to all the people that moved this bug the last week
!!!
But I think that most of you are moving in a different direction, and
all of the examples in the comments could been solved by the expected
behavior commented in post #20
(https://bugs.launchpad.net/ubuntu/+source/unity-
@Marius,
Maybe kdm handles it better. That's why we're asking for improve this
feature in lightdm.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown
@ethanay,
Terminal or tty shouldn't be the only way to solve this problem. There's
a lot of people that hasn't this knowledge. And request that the system
does what it seems to be doing (but it doesn't) is, imho, the simple way
to solve it.
Regards,
--
You received this bug notification
@Matthew,
Your approach related to the prompt / secondary text seems to be fine.
In addition, more information related to other users logged before halt or
reboot could be useful. You can see some examples at comments #20 and #22. By
the way, I'm not so sure if this behavior is about
@Matthew,
Maybe you should add what we were talking about in this bug:
Allow to a 'no admin user' to shutdown/reboot the system if he/she is
the only user logged in.
Kind Regards,
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
@Florian,
Nice idea!!
Some examples for the notification if there are some users are logged:
You and Florian are logged.
You, Florian, ethanay, daniel, Lionel and 3 more are logged.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Ernst,
If you follow the comments you'll figure out that some time the computer
should shut down and some time it shouldn't, depending on the user
requesting the shut down and the amount of users logged in.
After some comments, we're proposing some ideas of how it could be shown
or communicated
@ethanay
I agree with you.
This is just an example of the expected behavior, imho:
a. Normal user + other users logged:
You just can't turn off the computer because there are more users logged.
Please talk to an admin. [ok]
b. Admin user + other users logged:
There are more users logged in
@Florian,
You're right!! This isn't a full solution.
It's only a workaround for those (like me) that want a partial solution
and accept the (high) risk.
As I have said in a previous comment
(https://bugs.launchpad.net/ubuntu/+source/unity-
greeter/+bug/861171/comments/13) the full solution is
@Matthew,
At least bug #86 seems to have the same core problem.
I've published a workaround in bug #86 that i'm going to copy here,
and fix this bug (#861171) and bug #86.
I think the problem is only related to PolicyKit, because this doesn't
handle correctly the 'auth_admin_keep'
Workaround:
As I've commented previously, this partial solution is to modify this
file:
/usr/share/polkit-1/actions/org.freedesktop.consolekit.policy
and change:
auth_admin_keep
to:
yes
Edit the file /usr/share/polkit-1/actions/org.freedesktop.consolekit.policy
using your favorite text
I see this bug has triaged a lot of packages/apps.
I think this is a PolicyKit only behavior, and could be some related
issue with greeter (lightdm o gnome) related on how to handle the
request of admin password from PolicyKit.
The rest of packages/apps should be, imho, freed from this bug.
--
También he publicado cómo resolver este problema en español:
http://elblogdeparq.blogspot.com.es/2012/08/ubuntu-no-se-puede-
reiniciarapagar-si.html
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
*** This bug is a duplicate of bug 861171 ***
https://bugs.launchpad.net/bugs/861171
Workaround:
Edit the file
/usr/share/polkit-1/actions/org.freedesktop.consolekit.policy using your
favorite text editor. You will need root permissions.
Change the section relating to shutdown when others
Same bug on jaunty.
(nautilus:27232): Unique-DBus-WARNING **: Error while sending message:
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 reply timeout expired, or the network connection was
Same bug.
More info:
$ dbus-launch nautilus
Initializing nautilus-dropbox 0.6.1
** (nautilus:2146): WARNING **: Unable to add monitor: No soportado
Nautilus-Share-Message: Called net usershare info but it failed: La «red
compartida» devolvió el error 255: info_fn: file
Anyone who has the same bug, please report it in gnome, at the link that
Sebastien says.
By now, the bug is mark as unconfirmed.
--
there is no unmatch vfolder in the ondisk summary version
https://bugs.launchpad.net/bugs/293017
You received this bug notification because you are a member of
Same bug. Same annoying!
--
gnome session does not start window manager nor restores the previous session
https://bugs.launchpad.net/bugs/249373
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
This bug has crashed the ubuntu update from 7.10 to 8.04.
--
file-roller crashed with SIGSEGV
https://bugs.launchpad.net/bugs/150465
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Happens when upgrading 7.10 to 8.04.
--
nautilus crashed with SIGSEGV
https://bugs.launchpad.net/bugs/192457
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Some step by step guide:
1) Network issue:
Try to ping localhost:
# ping localhost
If you can't have a response, so check network issues as described
above.
2) Sound issue
Go to sound preferences and uncheck ESD support, as described above.
Following these steps i was able to solve the
The bug is still happening with beryl instaled but not working (i mean
metacity is the window manager).
And mostly it happens when i start the session.
The attached file is the last crash report.
** Attachment added: gaim-crash
http://librarian.launchpad.net/6439419/_usr_bin_gaim.1000.crash
I've did a network configuration and store it as 'home'. Someday I manually add
another dns plus the detected from the dhcp server.
Other time I delete that dns, so there was only 1 dns from dhcp server.
From time to time (less than 1 hour) the 'phantom' dns appears. so i have to
delete it
Sebastien,
the page https://launchpad.net/ubuntu/+source/gaim/+filebug doesn't let
me (and other people, i think) to attach anything.
the page where i'm now
(https://launchpad.net/ubuntu/+source/gaim/+bug/81762) let me do it, so
i'm attaching an screenshot from
Public bug reported:
Binary package hint: gaim
Gaim was just opened for a while, waiting in the panel for some incoming
message, and suddently it crash.
It happens from time to time.
I'm using beryl, just in case.
As I can't attached the crash report, it's pasted next:
** Affects: gaim
Public bug reported:
Binary package hint: gaim
Gaim was just opened for a while, waiting in the panel for some incoming
message, and suddently it crash.
It happens from time to time.
I'm using beryl, just in case.
As I can't attached the crash report, it's pasted next:
** Affects: gaim
29 matches
Mail list logo
