[Bug 1381415] Re: Can't create new folder in List view
Bug in bugzilla.gnome.org #739194 https://bugzilla.gnome.org/show_bug.cgi?id=739194 ** Bug watch added: GNOME Bug Tracker #739194 https://bugzilla.gnome.org/show_bug.cgi?id=739194 -- 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/1381415 Title: Can't create new folder in List view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1381415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1223181]
Created attachment 248041 Gdb core backtrace Parts of the gdb core backtrace with lots of oxygen calls. Frames 8 are just the usual java crash signal handling. This is from an Rcp 3.8.2 application crashing on OpenSuse 13.1 with oxygen-gtk theme. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1223181 Title: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1223181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1385882] [NEW] Unable to mount iPad with IOS 8
Public bug reported: I can't mount my iPad after I upgraded to IOS 8. After plugging in I get a series of error messages, also my iPad keep asking wether I trust my computer. I get messages like: Unable to mount ...'s iPad: Location is already mounted - (it's not) Unable to mount iPhone: Unhandled lockdown error (-3) (also sometimes -20) If I remember correctly this happened last year after I upgraded to iOS 7. The problem exists in Utopic too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libimobiledevice4 1.1.5+git20140313.bafe6a9e-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 26 14:36:14 2014 InstallationDate: Installed on 2014-01-10 (288 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: libimobiledevice UpgradeStatus: Upgraded to trusty on 2014-04-10 (198 days ago) ** Affects: libimobiledevice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty utopic ** Tags added: utopic ** Description changed: I can't mount my iPad after I upgraded to IOS 8. After plugging in I get a series of error messages, also my iPad keep asking wether I trust my computer. I get messages like: Unable to mount ...'s iPad: Location is already mounted - (it's not) Unable to mount iPhone: Unhandled lockdown error (-3) (also sometimes -20) If I remember correctly this happened last year after I upgraded to iOS 7. + + The problem exists in Utopic too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libimobiledevice4 1.1.5+git20140313.bafe6a9e-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 26 14:36:14 2014 InstallationDate: Installed on 2014-01-10 (288 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: libimobiledevice UpgradeStatus: Upgraded to trusty on 2014-04-10 (198 days ago) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1385882 Title: Unable to mount iPad with IOS 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1385882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1384437] Re: 8086:088e [Asus UX32VD] bluetooth problems
Hey Christopher, I knew that this is a gnome problem, but how shall I continue. Is this the wrong place now? What do you recommend me doing? Best, David -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1384437 Title: 8086:088e [Asus UX32VD] bluetooth problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1384437/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292282] Re: background transparency is not working on gnome terminal
I can confirm that PinGUY's solution works fine, but I don't like devilspie running on the background all the time -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1292282 Title: background transparency is not working on gnome terminal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1292282/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 874241] Re: Wrong resolutions in lightdm login screen when using external monitor connected to laptop
This bug still affects in xubuntu 14.10. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/874241 Title: Wrong resolutions in lightdm login screen when using external monitor connected to laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm-guest-session/+bug/874241/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1385919] [NEW] when create folder on ftp server, loose connection
Public bug reported: Ubuntu 14.10 - Nautilus 3.10.1 - upgrade from 14.04 FTP Server is provider web-space (11) Files open, save, rename, delete work. Folder open, rename, delete work. Problem: On create new folder/file nautilus crash or change view to home folder. When i reopen the ftp, a new folder is there and can be renamed (and name is selected for rename) so i think nautilus has trouble with ftp refresh. Tested on samba share - work Tested on sftp - work Tested with fresh install of ubuntu 14.10 (ftp) - still fail lsb_release : Description: Ubuntu 14.10 / Release: 14.10 nautilus version: 1:3.10.1-0ubuntu15 addon: folder-color (deinstalled and tested again - still reopen home folder) Error in terminal (start) ** (nautilus:27013): WARNING **: Couldn't register with accessibility bus: 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 broken. no output on terminal when crash/reload of home folder ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1385919 Title: when create folder on ftp server, loose connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1385919/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1072363] Re: Minimize window default shortcut Ctrl-Alt-0 doesn't work
It's almost two years to the day of the original post and in Ubuntu Gnome 14.10, this has not been fixed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1072363 Title: Minimize window default shortcut Ctrl-Alt-0 doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1072363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1385944] [NEW] 52_xdg_current_desktop.patch
Public bug reported: This patch does bad thing - it will overwrite XDG_CURRENT_DESKTOP if it was set before. There is new standard - DesktopNames that is used to set XDG_CURRENT_DESKTOP. LightDM will set XDG_CURRENT_DESKTOP if DesktopNames has been added in session .desktop file. But it will be overwritten by GNOME if gnome-session will not find DesktopName in .session file. Fix should be simple - set to default value - GNOME - only if XDG_CURRENT_DESKTOP is not set. This probably should be fixed in vivid and utopic. ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- 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/1385944 Title: 52_xdg_current_desktop.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1385944/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1384437] Re: 8086:088e [Asus UX32VD] bluetooth problems
David, you would want to report it upstream via https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-bluetooth . Once a report is generated, please post the URL to this report. ** Changed in: gnome-bluetooth (Ubuntu) Status: New = Triaged ** Description changed: - After booting up the computer the bluetooth applet is not able to turn on bluetooth (the slider slides, for an instance of a second my paired devices show up, and then the slider is on OFF again). The error is the same when: + After booting up the computer the GNOME bluetooth applet is not able to turn on bluetooth (the slider slides, for an instance of a second my paired devices show up, and then the slider is on OFF again). The error is the same when: - closing and opening the lid - Turning BT off and trying to turn it on again using the applet + + WORKAROUND: The blueman-applet allows me to turn on and off bluetooth + without any modifications. WORKAROUND: Execute: rfkill unblock all (im in the bluetooth group) the bluetooth applet displays bluetooth being on and Im able to connect to my BT devices. Im using 'rfkill unblock all' in /etc/rc.local before the 'exit 0' line s.t. I have BT always on after starting up the system. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: david 2549 F...m pulseaudio /dev/snd/controlC0: david 2549 F pulseaudio CurrentDesktop: X-Cinnamon Date: Wed Oct 22 22:06:15 2014 EcryptfsInUse: Yes MachineType: ASUSTeK COMPUTER INC. UX32VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed root=UUID=d8d7556a-05ca-4e18-899c-52b7cfd06204 ro quiet splash pcie_aspm=force rootfstype=ext4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-10-15 (7 days ago) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1384437 Title: 8086:088e [Asus UX32VD] bluetooth problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1384437/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1385957] [NEW] smb:// shares broken if sudo nautilus
Public bug reported: If I open nautilus via the command: nautilus, I can navigate smb shares fine. If I open nautilus via the commond: sudo nautilus, I get the following message: Sorry, could not display all the contents of “192.168.3.235 (smb)”: Operation not supported ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nautilus 1:3.10.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 26 16:18:11 2014 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2014-10-14 (11 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to utopic on 2014-10-25 (1 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- 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/1385957 Title: smb:// shares broken if sudo nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1385957/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1361906] Re: gvfsd-ftp crashed with SIGABRT in g_mutex_unlock_slowpath()
Same bug. Ubuntu 14.10 fresh install. While copying 1 file with Nautilus gvfsd-ftp, it suddenly stops, and closes the ftp connection too. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1361906 Title: gvfsd-ftp crashed with SIGABRT in g_mutex_unlock_slowpath() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1361906/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1361906] Re: gvfsd-ftp crashed with SIGABRT in g_mutex_unlock_slowpath()
Unfortunately I have to confirm the bug still persists with the final Ubuntu 14.10. Very frustrating if you are used to access ftp through Nautilus which I do a lot. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1361906 Title: gvfsd-ftp crashed with SIGABRT in g_mutex_unlock_slowpath() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1361906/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 551950] Re: gnome-bluetooth cannot use pin = 1234
Still a problem in 14.04LTS. Had to revert to using bluetooth manager, again. Works every time with bluetooth manager. Why has this not been addressed?!?!?!?! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/551950 Title: gnome-bluetooth cannot use pin = 1234 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/551950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 551950] Re: gnome-bluetooth cannot use pin = 1234
KeithG: Why has this not been addressed?!?!?!?! Because we didn't know if this bug was still affecting any currently supported Ubuntu release till you commented :) Thank you. ** Tags added: trusty ** Changed in: gnome-bluetooth (Ubuntu) Status: Incomplete = Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/551950 Title: gnome-bluetooth cannot use pin = 1234 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/551950/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1359242] Re: No Help or Preferences
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1359242 Title: No Help or Preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1359242/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1254851] Re: qpdfview renders black pages after poppler update
[Expired for poppler (Ubuntu) because there has been no activity for 60 days.] ** Changed in: poppler (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1254851 Title: qpdfview renders black pages after poppler update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1254851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
