Thanks for the update, Pedro.
GDB and Valgrind are attached.
** Attachment added: "Valgrind"
http://launchpadlibrarian.net/30272643/valgrind-logs-nautilus.tar.gz
--
Nautilus crashes with gvfs-error on "connect to server"
https://bugs.launchpad.net/bugs/411790
You received this bug notificati
** Attachment added: "GDB-Backtrace"
http://launchpadlibrarian.net/30272649/gdb-nautilus.txt
--
Nautilus crashes with gvfs-error on "connect to server"
https://bugs.launchpad.net/bugs/411790
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug ass
okay, this was due to the options set in the Backtrace-explanation in
the wiki, causing gdb to stop debugging before the crash. I skipped all
the pre-run statements and now it did catch everything.
** Attachment removed: "GDB-Backtrace"
http://launchpadlibrarian.net/30272649/gdb-nautilus.txt
*
Yup - I just noticed, that this problem is not of jaunty, but of karmic
(I installed mono-2.4 and seem to have messed up my preferences, so that
it updated everything to karmic).
I added the new backtrace with libglib2.0-0--2.21.4-0ubuntu1, nautilus
is still jaunty installation (nautilus--2.26.2-0
okay, after completely upgrading to karmic, I can connect to servers
without crashes again. I have some problems with remote userrights, but
that's another story.
As for this bug, I recommend setting the dependency of the jauntypackage
of nautilus as incompatible with the libglib-version of karmic
Public bug reported:
Binary package hint: gvfs
Affected release: Karmic 9.10 (i386)
Affected version: gvfs 1.3.4-0ubuntu1
I am able to mount a sharepoint on a winXP with Domain Authentication. I
can see all files, and add files or remove files from nautilus or from
console.
However, if I want t
whatever done, the last update fixed this bug.
** Changed in: gvfs (Ubuntu)
Status: New => Fix Released
--
can't access samba-mount via gvfs ("Invalid Argument)
https://bugs.launchpad.net/bugs/415279
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
still affected in 10.04 lucid alpha3 (Package version 2.29.92)
--
the connect server dialog should not close on error
https://bugs.launchpad.net/bugs/352569
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Public bug reported:
Binary package hint: gnome-power-manager
ubuntu 10.04 lucid alpha 3
package: "Power Manager Brightness Applet 2.29.91" (in Gnome-Power-Manager)
The Applet may be added properly to the dock. Upon click, the slider
opens but (a) does not show the correct current brightness (al
unfortunately not - seems to be okay now (Indicator-applet is version
0.3.2-0ubuntu3). But I do have another problem, I'll file that into a
different bug for now, since it seems to be unrelated.
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete => Invalid
--
indicator-applet
Triaged: https://bugzilla.gnome.org/show_bug.cgi?id=612399
** Bug watch added: GNOME Bug Tracker #612399
https://bugzilla.gnome.org/show_bug.cgi?id=612399
--
Power Manager Brightness Applet not working
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a
Public bug reported:
Binary package hint: gdm
Ubuntu 10.04 alpha 3, package version 2.29.92-0ubuntu1
Lucid uses the very nice new feature of kernel mode setting, already
setting the video mode correctly during boot time. However, when the
boot is through and gdm takes over, the system freezes (s
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: gnome-power-manager
Ubuntu 10.04 lucid
package: "Power Manager Brightness Applet 2.29.91" (in Gnome-Power-Manager)
Steps to reproduce:
1. Right click on a panel and press add to panel.
apport information
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/42040269/CurrentDmesg.txt
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bu
apport information
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42040275/Dependencies.txt
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bu
apport information
** Attachment added: "DevkitPower.txt"
http://launchpadlibrarian.net/42040277/DevkitPower.txt
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
apport information
** Attachment added: "GConfNonDefault.txt"
http://launchpadlibrarian.net/42040279/GConfNonDefault.txt
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
apport information
** Attachment added: "Lspci.txt"
http://launchpadlibrarian.net/42040280/Lspci.txt
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
-
apport information
** Attachment added: "Lsusb.txt"
http://launchpadlibrarian.net/42040281/Lsusb.txt
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
-
apport information
** Attachment added: "ProcCpuinfo.txt"
http://launchpadlibrarian.net/42040283/ProcCpuinfo.txt
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
apport information
** Attachment added: "ProcInterrupts.txt"
http://launchpadlibrarian.net/42040284/ProcInterrupts.txt
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
apport information
** Attachment added: "ProcModules.txt"
http://launchpadlibrarian.net/42040287/ProcModules.txt
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
apport information
** Attachment added: "UdevDb.txt"
http://launchpadlibrarian.net/42040288/UdevDb.txt
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
apport information
** Attachment added: "UdevLog.txt"
http://launchpadlibrarian.net/42040290/UdevLog.txt
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee
apport information
** Attachment added: "gnome-power-bugreport.txt"
http://launchpadlibrarian.net/42040291/gnome-power-bugreport.txt
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ubuntu
Desktop B
here you go. There is an upstream patch available, but it breaks the
compile process.
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mai
I've just upgraded gnome-power-manager to version 2.29.91-0ubuntu8 -bug
persists.
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
Hi Paul,
thanks for the advise - I was able to compile and make install it after
uninstalling the original gnome-power-manager-package. However, the
brightness panel doesn't show up in the "add to panel"-dialog. From the
installation process I noticed, that the applets are copied to
/usr/share/loc
** Attachment added: "_usr_bin_nautilus.1000.crash"
http://launchpadlibrarian.net/30146759/_usr_bin_nautilus.1000.crash
** Package changed: ubuntu => nautilus (Ubuntu)
--
Nautilus crashes with gvfs-error on "connect to server"
https://bugs.launchpad.net/bugs/411790
You received this bug noti
I would, but the only install candidate of nautilus-dbg is
2.26.2-0ubuntu1, which is bound to the same nautilus version, but only
install candidate for nautilus is 2.26.2-0ubuntu2.
--
Nautilus crashes with gvfs-error on "connect to server"
https://bugs.launchpad.net/bugs/411790
You received this
Thanks for the work, Ali.
I've updated my Dell Studio XPS 1640 with your version, but no good. I
still can't change the brightness of my screen with the brightness-
applet. On a sidenote, the applet shows a red "not-available"-circle
across the icon, so I guess some check for reading the current
b
Hi Paul,
no solution there, that directory doesn't exist on ubuntu... hrmmm. Any
other ideas, why the Applet might not be listed?
Best Regards,
Lars
--
Power Manager Brightness not clickable
https://bugs.launchpad.net/bugs/535097
You received this bug notification because you are a member of Ub
Public bug reported:
Binary package hint: gnome-settings-daemon
I have a USB Microsoft Media Keyboard with Mediakeys and a wireless
Logitech Revolution MX attached to my Dell StudioXPS 1640 Laptop. Every
time I press a mediakey on the external keyboard, the left mouse click
doesn't work on neithe
*** This bug is a duplicate of bug 636311 ***
https://bugs.launchpad.net/bugs/636311
** This bug has been marked a duplicate of bug 636311
Keyboard special keys interfere with mouse
* You can subscribe to bug 636311 by following this link:
https://bugs.launchpad.net/ubuntu/+source/xserver
confirmed in Jaunty
--
[MTP] ugly behavior if device is full
https://bugs.launchpad.net/bugs/393182
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
https://lists.ubuntu.com/ma
Public bug reported:
Binary package hint: seahorse
Given an own ssh-key, the user may choose to install this key on a
remote machine to be able to connect via ssh without having to provide a
password. If the process of copying the key over to the remote machine
(after providing an url, a loginnam
Public bug reported:
Binary package hint: gdm
ubuntu maverick 10.10 beta
gdm 2.30.5-0ubuntu2
The system has been upgraded from lucid to maverick beta.
Every time I boot the computer, gdm greets me with the login screen and
asks for my username. On the moment I hit "ok" or the enter-key, the
sys
** Attachment added: "Xorg.log of current run"
https://bugs.launchpad.net/bugs/630056/+attachment/1542150/+files/Xorg.0.log
--
gdm restarts on password enter screen
https://bugs.launchpad.net/bugs/630056
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
why is the importance of this bug set to "low"? If I can't read PDFs, I
basically can stop working... Sure, it's not a kernel OOPS, but could
you put the importance higher please?
--
evince crashed with signal 5 in g_object_newv()
https://bugs.launchpad.net/bugs/621507
You received this bug notif
okay, the problem is based in not having Empathy installed, as there is
a dependency in /usr/share/glib-2.0/schemas/ubuntu-
artwork.gschema.override. This prevents the schemas from being built
correctly, if Empathy is not installed (like on my system):
r...@host:~# glib-compile-schemas /usr/share/
forgot: gcalctool works fine after installing Empathy again and
recompiling the schemas, as given in the example.
--
gcalctool crashed with signal 5 in g_object_newv()
https://bugs.launchpad.net/bugs/630460
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
okay, the problem is based in not having Empathy installed, as there is
a dependency in /usr/share/glib-2.0/schemas/ubuntu-
artwork.gschema.override. This prevents the schemas from being built
correctly, if Empathy is not installed (like on my system):
r...@host:~# glib-compile-schemas /usr/share/
@John: I'm not sure which package will install the correct schema. If
you don't use Empathy, simple move the /usr/share/glib-2.0/schemas
/ubuntu-artwork.gschema.override file to some backup and you should be
fine after recompiling the schemas. Worked for me, and the file's
contents indicate only st
43 matches
Mail list logo