[Bug 675165] Re: External mediakeys Block Left Mouse button input on Some Microsoft Keyboards
*** 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-xorg-input-evdev/+bug/636311/+subscribe -- External mediakeys Block Left Mouse button input on Some Microsoft Keyboards https://bugs.launchpad.net/bugs/675165 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 675165] [NEW] External mediakeys block mouse input
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 neither the external mouse nor the internal touchpad. Right mouse click does work fine. If I press any mediakeys on the laptop itself, everything is working fine. The only way to get the mouse working again is to pull the keyboard for a second and reattach it. The next left mouse click is not recognized then, but all following are recognized again. I've worked through https://wiki.ubuntu.com/Hotkeys/Troubleshooting, but had to skip the sed-filter on xev to get any results at all. Here is the abbrived output: [...] Pressed LAPTOP volume up-hotkey MappingNotify event, serial 33, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 FocusOut event, serial 33, synthetic NO, window 0x6c1, mode NotifyGrab, detail NotifyAncestor FocusIn event, serial 34, synthetic NO, window 0x6c1, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 34, synthetic NO, window 0x0, keys: 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Pressed KEYBOARD volume up-hotkey FocusOut event, serial 34, synthetic NO, window 0x6c1, mode NotifyGrab, detail NotifyAncestor VisibilityNotify event, serial 34, synthetic NO, window 0x6c1, state VisibilityFullyObscured FocusOut event, serial 34, synthetic NO, window 0x6c1, mode NotifyWhileGrabbed, detail NotifyNonlinear MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 [...] My global hotkeys are mapped to the according XF86-Keys (e.g. Volume Up = XF86AudioRaiseVolume). This is a regression from Ubuntu Lucid, where everything worked fine. I have this faulty behavior since Maverick alpha-3 or -4. Any Ideas how to tackle this? ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- External mediakeys block mouse input https://bugs.launchpad.net/bugs/675165 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 621507] Re: evince crashed with signal 5 in g_object_newv()
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 notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 630460] Re: gcalctool crashed with signal 5 in g_object_newv()
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/glib-2.0/schemas/ No such schema `org.gnome.Empathy.conversation' specified in override file `/usr/share/glib-2.0/schemas/ubuntu-artwork.gschema.override' Installing Empathy again or deleting the ubuntu- artwork.gschema.override, gcalctool works normally. As does Evince, which as the same problems: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/621507 This seems directly related to this bug: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/602175 -- 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 is subscribed to gcalctool in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 630460] Re: gcalctool crashed with signal 5 in g_object_newv()
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 is subscribed to gcalctool in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 621507] Re: evince crashed with signal 5 in g_object_newv()
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/glib-2.0/schemas/ No such schema `org.gnome.Empathy.conversation' specified in override file `/usr/share/glib-2.0/schemas/ubuntu-artwork.gschema.override' Installing Empathy again or deleting the ubuntu- artwork.gschema.override, Evince works normally after recompiling the schemas. As does gcacltool, which as the same problems: https://bugs.launchpad.net/ubuntu/+source/gcalctool/+bug/630460 This seems directly related to this bug: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/602175 -- evince crashed with signal 5 in g_object_newv() https://bugs.launchpad.net/bugs/621507 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 630460] Re: gcalctool crashed with signal 5 in g_object_newv()
@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 stuff dealing with Empathy anyways. -- 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 is subscribed to gcalctool in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 630056] [NEW] gdm restarts on password enter screen
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 system drops back to console for two or three seconds and presents me with the same loginscreen. Now everything works fine and I can login to my gnome desktop. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- 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 is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 630056] Re: gdm restarts on password enter screen
** 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 is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 393182] Re: [MTP] ugly behavior if device is full
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/mailman/listinfo/desktop-bugs
[Bug 610119] [NEW] remote ssh key - success without message
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 loginname and a password for the remote sshd), the user is not notified of a success. The user should instead be presented with a key successfully installed-message to avoid unnecessary waiting time and confusion. ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- remote ssh key - success without message https://bugs.launchpad.net/bugs/610119 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] Re: Power Manager Brightness not clickable
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 brightness failed. This is backed up through the fact, that the applet's slider is on 0 (absolutely down), while my screen's brightness is on a high setting. -- 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 list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] Re: Power Manager Brightness not clickable
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 Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] Re: Power Manager Brightness not clickable
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. Add brightness applet 2. Click on the new applet to show the slider, now try to move the slider using a mouse click. 3. The slider simply vanishes. Setting the brightness with the keyboard commands or with mouse wheel works fine though. + + + --- + Architecture: amd64 + DistroRelease: Ubuntu 10.04 + GnomeSessionIdleInhibited: Unknown + GnomeSessionInhibitors: Failed to acquire + GnomeSessionSuspendInhibited: Unknown + InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100223.2) + MachineType: Dell Inc. Studio XPS 1640 + Package: gnome-power-manager 2.29.91-0ubuntu6 + PackageArchitecture: amd64 + ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-16-generic root=/dev/mapper/sda6_crypt ro quiet splash + ProcEnviron: + PATH=(custom, no user) + LANG=de_DE.utf8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-16.25-generic + Tags: lucid + Uname: Linux 2.6.32-16-generic x86_64 + UserGroups: + + dmi.bios.date: 11/19/2009 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A12 + dmi.board.name: 0W497D + dmi.board.vendor: Dell Inc. + dmi.board.version: A12 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: A12 + dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2009:svnDellInc.:pnStudioXPS1640:pvrA123:rvnDellInc.:rn0W497D:rvrA12:cvnDellInc.:ct8:cvrA12: + dmi.product.name: Studio XPS 1640 + dmi.product.version: A123 + dmi.sys.vendor: Dell Inc. ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/42040267/BootDmesg.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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] CurrentDmesg.txt
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 bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] Dependencies.txt
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 bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] DevkitPower.txt
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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] GConfNonDefault.txt
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 is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] Lspci.txt
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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] Lsusb.txt
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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] ProcCpuinfo.txt
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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] ProcInterrupts.txt
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 a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] ProcModules.txt
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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] UdevDb.txt
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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] UdevLog.txt
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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] gnome-power-bugreport.txt
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 Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] Re: Power Manager Brightness not clickable
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 mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] Re: Power Manager Brightness not clickable
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 list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] Re: Power Manager Brightness not clickable
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/local/gnome-2.0/ui, while the rest is in /usr/share/gnome-2.0/ui. I moved them over, but they still don't show up. Any hints? -- 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 list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535100] Re: indicator-applet for battery status not showing any information
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 for battery status not showing any information https://bugs.launchpad.net/bugs/535100 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] Re: Power Manager Brightness Applet not working
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 member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535606] [NEW] lucid: GDM resets video mode, although it's already set by kernel
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 (sometimes with boot messages still visible, sometimes with an incomplete gdm login screen) until a button is pressed. Then, gdm (or X?) resets the video mode, as far as I can tell to the same settings as the kernel already did. The login-screen is only usable after this reset. This behavior was appropriate when the the bootscreen and gdm use different video modes, but should not happen when they are same (which is what we presumably want anyways). I'm not sure where to file this bug, so feel free to move it to kernel or X. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- lucid: GDM resets video mode, although it's already set by kernel https://bugs.launchpad.net/bugs/535606 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 352569] Re: the connect server dialog should not close on error
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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535097] [NEW] Power Manager Brightness Applet not working
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 (always on max) and (b) is not always showing up below the applets icon but on the upper left corner of the screen. Pressing anywhere on the slider or buttons does not change anything but makes the slider disappear. Setting the brightness with the keyboard commands works fine, though, the notifications on the changes are also correct. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- Power Manager Brightness Applet not working https://bugs.launchpad.net/bugs/535097 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 415279] Re: can't access samba-mount via gvfs (Invalid Argument)
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 is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 415279] [NEW] can't access samba-mount via gvfs (Invalid Argument)
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 to access a file's content, I get an error Invalid argument. This happens no matter how small a file is (tested with 12 byte and 25gb), and seems to be a problem arising at the end of a file (when I try to copy the 25gb-file to a local directory, it always crashes on the last 14kb). Since this poses a serious problem in mixed environments, I propose to mark this bug as severe importance to be fixed before releasing karmic. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- 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 is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 411790] Re: Nautilus crashes with gvfs-error on connect to server
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 ** Attachment added: GDB-Backtrace #2 http://launchpadlibrarian.net/30299818/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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 411790] Re: Nautilus crashes with gvfs-error on connect to server
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-0ubuntu2) I'll upgrade completely to karmic now and see if the problem still exists. ** Attachment added: GDB-Backtrace with libglib2.0-0-dbgsym http://launchpadlibrarian.net/30302856/gdb-nautilus2.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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 411790] Re: Nautilus crashes with gvfs-error on connect to server
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. -- 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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 411790] Re: Nautilus crashes with gvfs-error on connect to server
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 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/mailman/listinfo/desktop-bugs
[Bug 411790] Re: Nautilus crashes with gvfs-error on connect to server
** 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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 411790] Re: Nautilus crashes with gvfs-error on connect to server
** 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 notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 411790] Re: Nautilus crashes with gvfs-error on connect to server
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 bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
