[Bug 1292113] Re: CTRL+ALT+T - shortcut to open Terminal is does not work
Same issue here. Doesn't seem fixed. I have the same issue with other Ctrl related shortcuts, like my custom shortcuts Ctrl Alt 7, Ctrl Alt 8, etc. Logging out and back in fixes it but that's hardly a suitable workaround when the missing shortcuts are only realized after you're already neck deep in work. It just seems tied to that Ctrl key, Ctrl Alt T included with terminal, though certain shortcuts are seemingly exempt, such as window management shortcuts, I.e. Ctrl Super left/right arrow or Ctrl Alt up/down arrow, etc. 14.04.2 -- 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/1292113 Title: CTRL+ALT+T - shortcut to open Terminal is does not work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1292113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 627195] Re: Window management - Apps raised from indicators sometimes dont have the focus
I couldn't see an obvious way to edit my above post, so apologies for sending out a second comment, but I do have to ask... why would the default parameter for focus-prevention-level not be 0 anyways? It doesn't seem, do I dare say, all that logical to have it set to 1 since it only ends up providing inconsistent behavior with the way things from system tray open. It being set to 0 provides that consistency. It would surely remove the "look on your launcher, see? it's there after all" comments I have to make quite often so users know that the application they tried to open from system tray isn't broken, it indeed launched, it's just... minimized and in your left launcher. Thanks for all of your work! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/627195 Title: Window management - Apps raised from indicators sometimes dont have the focus To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/627195/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 627195] Re: Window management - Apps raised from indicators sometimes dont have the focus
Running 14.04.2 here with some of the same issues. I was seeing it with ownCloud client, network manager, and a weather applet known as my- weather-indicator. The issue came up at random, but it was easy to replicate within a matter of 15-20 seconds while continuously navigating around open windows followed by opening applications with system tray icons. I brought up conversation with some other users who gave me a suggestion that has, so far, worked. Figured I'd post it here in case it can benefit anybody else until the bug can be properly fixed. I ran this in terminal, followed by a log out/log in. dconf write /org/compiz/profiles/unity/plugins/core/focus-prevention- level 0 This is a similar idea that Rael posted in response 43 above. I seem to recall Ubuntu switching to dconf over gconf at some point. I tested it in my 14.04.2 virtual machine (brand new, but fully updated install) however the gconf key didn't appear to fix the issue, as I was still able to replicate it. In the same VM, that dconf write command above seemed to fix the issue, as I have been unable to replicate it in my VM, nor my main laptop. The default focus-prevention-level is 1, which is considered "low", but appears to be the cause of this random behavior. Setting it to 0 seems to make it consistent. I haven't ran with this change for days/weeks/months, but in my tinkering so far today, the issue hasn't resurfaced a single time. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/627195 Title: Window management - Apps raised from indicators sometimes dont have the focus To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/627195/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1168582] Re: Google talk "Requires Authorization" after suspend/resume
Thanks for the tip, Phasmus. Killing the process on 14.04 seems to help my issue as well. Otherwise Empathy is downright unusable given its wildly inconsistent behavior. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1168582 Title: Google talk "Requires Authorization" after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1168582/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1344093] [NEW] Empathy unable to open instant message to a specific contact.
Public bug reported: I am using Empathy with Google Talk under Ubuntu 14.04. With one specific contact I cannot open the instant message. I can double click all day or simply highlight them and hit enter, but nothing works. Other contacts however open up right away. The user in question that I was trying to message later informed me that he had the same thing happen. In his case, the instant message was in another workspace. It seems as if Empathy and/or Unity is not respecting the different workspaces in this case, as clicking on the name should redirect you to the workspace in which the instant message resides. In my testing just prior to submitting this bug report, I had nothing on other workspaces, and I STILL was unable to message this person. This morning was a fresh boot of my system, and I had not touched workspaces since, so anything that was hung up should have been cleared if it was workspace related. Interestingly enough, as I had the entirety of this bug report typed out and I was about to hit submit, I decided to delete my Google account and re-add it. Unfortunately, this is a common occurrence with Empathy for other reasons, but I did so again just now, and clicking the contact in question as notated above now works. What is it that is continually breaking that requires users to consistently remove and re-add their accounts to maintain connectivity/messaging functionality? As of now, Empathy is not able to 'function' so I have to use other messaging applications, but I would be more than happy to test anything necessary. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: empathy 3.8.6-0ubuntu9.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 18 11:36:50 2014 InstallationDate: Installed on 2014-02-03 (164 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: empathy UpgradeStatus: Upgraded to trusty on 2014-04-17 (91 days ago) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1344093 Title: Empathy unable to open instant message to a specific contact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1344093/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287987] [NEW] Selecting "quit" from Unity bar does not close Rhythmbox.
Public bug reported: The quit functions of Rhythmbox do not act consistently, which doesn't make a lot of sense. With Rhythmbox open, CTRL + Q along with Rhythmbox (in global menu) >> Quit will actually, 100% quit the application to the point that currently playing music gets stopped immediately. On the flip side, if you right click Rhythmbox in the Unity bar and select quit, it simply closes the window, but Rhythmbox continues to function in the background and play music. It would make more sense if the quit functions would actually quit the application, as the "quit" function in the Unity bar feels a bit confusing after it doesn't truly quit Rhythmbox. Thank you! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: rhythmbox 2.99.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Mar 4 19:06:21 2014 InstallationDate: Installed on 2014-01-14 (49 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1287987 Title: Selecting "quit" from Unity bar does not close Rhythmbox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1287987/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1275856] Re: Nautilus crashes when renaming items on Samba share.
I tried to open it with the submit report utility, but it does nothing. It asks me if I want to report it, I hit continue, and nothing else happens after that. Same thing happened when I launched it via terminal as you suggested. Apport is enabled. Instead I'm attaching it here. Hope that's okay. ** Attachment added: "_usr_bin_nautilus.1000.crash" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1275856/+attachment/3967939/+files/_usr_bin_nautilus.1000.crash -- 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/1275856 Title: Nautilus crashes when renaming items on Samba share. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1275856/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1275856] [NEW] Nautilus crashes when renaming items on Samba share.
Public bug reported: Ubuntu 13.10 64 bit Fully updated When I connect to my samba server (Ubuntu Server 12.04.4 64 bit), I am able to create and move files around. I tried to rename a directory and it crashed. It crashes, seemingly, 100% of the time when I try to rename the directory. In paritcular, the relevant line of syslog is: Feb 3 12:37:53 JS-Z835 kernel: [ 203.805694] nautilus[3952]: segfault at 20 ip 00430e7f sp 7fff70930fb0 error 4 in nautilus[40+153000] The above results are on a Toshiba ultrabook. I duplicated this on a separate laptop by Lenovo, but also with Ubuntu 13.10 64 bit and fully updated. The only relevant line I saw of the syslog on that system is: Feb 3 12:45:00 JS-E430 kernel: [ 40.812722] nautilus[1981]: segfault at 30 ip 00430e7f sp 7fff91bbf280 error 4 in nautilus[40+153000] What is admittedly a little strange is when I was about to submit this report, I hopped back on the network share and for a handful of times I was able to rename a few directories without issue. I exited Nautilus, re-opened it, and now it's crashing again. Just wanted to notate that as it seemed as if it wasn't immediately replicable. If there is any sort of testing I can do please let me know. Thank you! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 3 12:39:10 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'840x550+49+24'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2014-01-28 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1275856 Title: Nautilus crashes when renaming items on Samba share. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1275856/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1262735] [NEW] Add Pantheon to "OnlyShowIn" entry in desktop file.
Public bug reported: Pantheon is a desktop environment based on GTK 3 in use by the elementary OS team. Elementary OS, for what it's worth, is based on Ubuntu 12.04. Pantheon is becoming more popular and packages for it already exist in Arch and openSUSE. Unfortunately, Pantheon's file manager has had some stability issues, so I've installed Nautilus. Like many others, we were confused as to why Nautilus was not showing up in the applications menu. After some digging I found the OnlyShowIn entry in /usr/share/applications/nautilus.desktop and, quite honestly, just commented out the whole thing. Suddenly, Nautilus worked - success! That said, countless others have looked to install an alternative file manager, such as Nautilus, only to find it doesn't show up. They assume it's not supported and move on to other alternatives. If Pantheon could be added so elementary OS could pick up Nautilus that would be tremendously useful to a lot of users. Thank you for your consideration! ** 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/1262735 Title: Add Pantheon to "OnlyShowIn" entry in desktop file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1262735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1233759] [NEW] Ubuntu GNOME 13.10, Evolution 3.8.4, crashes when in preferences to EWS account.
Public bug reported: Ubuntu GNOME 13.10 Evolution 3.8.4 No PPAs Fully updated (Tues Oct 1, 2013) I have 3 accounts associated with Gnome Online Accounts. Two Google, and One Exchange (EWS). Often times when I go into Edit - Preferences, click on my Exchange EWS account and hit edit, Evolution crashes. I have yet to see it crash when I replicate these steps to the Google email accounts, but it happens on the EWS account rather frequently. It took me 5 times to go in and change the receiving time option from 60 minutes to 1 minute, as an example. Oddly enough, just seconds ago I was preparing to close this bug report because Evolution wasn't crashing despite me clicking around in the preferences window. I left it sit untouched for about 15 seconds and it just disappeared cold turkey out of no where. Thanks for your time! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evolution 3.8.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Tue Oct 1 12:41:59 2013 InstallationDate: Installed on 2013-10-01 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Beta amd64 (20130930) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1233759 Title: Ubuntu GNOME 13.10, Evolution 3.8.4, crashes when in preferences to EWS account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1233759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 424956] Re: nautilus crashed with SIGABRT in raise()
Apport brought me here. Using Ubuntu GNOME 13.10 alpha and it came up. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/424956 Title: nautilus crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/424956/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1075923] Re: nautilus hangs copying large directories from a samba share
I'm not sure if the issue I am facing is exactly the same or not, but I figured I'd chime in. In my case, copying a single large file works, but copying a dozen files 1-2MB in size (each) locks up when using Nautilus and GVFS. Oddly enough, I only have this issue on my Lenovo, not my Toshiba. The Lenovo is an AMD APU E450 unit, so it doesn't exactly have a ton of horsepower. It does however have 6GB of RAM and an SSD. My Toshiba on the other hand has a mobile i5, 6GB RAM, and SSD. So all things compared, they stack up against each other decently with the exception of the CPU. I have yet to have a successful transfer with multiple small files on the Lenovo. Meanwhile, the Toshiba works brilliantly each and every time. Both are running Ubuntu GNOME 13.04 64 bit, fully updated. -- 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/1075923 Title: nautilus hangs copying large directories from a samba share To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1075923/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1177012] [NEW] Selecting default application in System Settings does not present predictable results.
Public bug reported: Beginning with 13.04 I've noticed that Ubuntu has been a little unpredictable with selecting the default application, particularly for videos. I have Totem, VLC, and SMPlayer installed. I am not able to change the default video application properly. Earlier I had these findings: Selected VLC to be default video player. Closed/reopene System Settings - Details - Default Applications. Totem was still default. I installed SMPlayer, and somehow was able to have success with setting SMPlayer as default. Once done, I tried to change the default away from SMPlayer. I changed it to Totem and closed/reopend System Settings. SMPlayer was still default. Changed to VLC and closed/reopend System Settings. SMPlayer was still default. I did an apt-get remove --purge smplayer, and now Totem was the default. I changed to VLC, closed/reopened, but Totem was still default. I'd like to point out that if I right click on the file and go to Properties - Open With tab, I can successfully select the new default application for that file type without issue. (at one point I did have to hit "reset", as even then it wasn't allowing me to change the default, but since then everything has worked fine) Bottom line, System Settings does not allow me to select the default video application properly, as it doesn't seem to accurately change the settings as an end user would expect. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu24 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Mon May 6 13:41:39 2013 InstallationDate: Installed on 2013-04-30 (6 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1 gnome-control-center-unity 1.2daily13.04.09-0ubuntu1 indicator-datetime 12.10.3daily13.03.26-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1177012 Title: Selecting default application in System Settings does not present predictable results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1177012/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1163674] [NEW] Adding a printer crashes Gnome Control Center (System Settings)
Public bug reported: When trying to add a printer the entire Gnome Control Center (System Settings) menu crashes. I get as far as seeing what printers are available to install. Once I click add it crashes each and every time. Something interesting I noticed is if I install system-config-printer- gnome, it works fine. If I remove system-config-printer-gnome (I actually did a remove --purge), the problem pops back up again. Seems as if that package is playing a key role with compatibility. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu18 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Wed Apr 3 00:01:57 2013 InstallationDate: Installed on 2013-04-01 (2 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha amd64 (20130331) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.5-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa raring third-party-packages -- 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/1163674 Title: Adding a printer crashes Gnome Control Center (System Settings) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1163674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1135297] [NEW] Connection times out when transferring 2 GB+ of data across network.
Public bug reported: Ubuntu 13.04 64 bit, February 27th daily image. I installed this same ISO on my laptop and desktop. On both of them if I copy at least 2 GB of data over the network to a different location, they lock up right around the 2 GB mark. The transfer stops and eventually I get an error citing that the connection timed out. Whenever this happens it seems as if I have to restart to regain network connectivity. At first I thought this was a Nautilus or Samba thing, as it first surfaced when I was pushing about 10 GB of data from my 13.04 desktop to my 12.04 Ubuntu Server. However, I tried this using rsync over SSH and it did the same thing, indicating it's not likely a Nautilus or Samba issue. I also thought it was the hardware of my desktop, but like I said, I tried my laptop over wireless and it did the same exact thing. I've seen it happen when the file transfer gets to 2.0 GB or 2.3 GB. Somewhere in there is when I've seen the error pop up. I ran dmesg on my desktop after this happened. I was spamming dmesg as the data was being pushed over the network and I was getting the same output each time, but the second the issue popped up is when the list of DMA entries popped up. [3.918858] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input7 [3.918944] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input8 [3.919017] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input9 [3.919073] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input10 [3.947169] init: udev-fallback-graphics main process (946) terminated with status 1 [4.968540] init: failsafe main process (987) killed by TERM signal [4.981107] Bluetooth: Core ver 2.16 [4.981129] NET: Registered protocol family 31 [4.981130] Bluetooth: HCI device and connection manager initialized [4.981184] Bluetooth: HCI socket layer initialized [4.981187] Bluetooth: L2CAP socket layer initialized [4.981192] Bluetooth: SCO socket layer initialized [4.986657] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [4.986661] Bluetooth: BNEP filters: protocol multicast [4.986668] Bluetooth: BNEP socket layer initialized [4.987832] Bluetooth: RFCOMM TTY layer initialized [4.987843] Bluetooth: RFCOMM socket layer initialized [4.987844] Bluetooth: RFCOMM ver 1.11 [4.999846] type=1400 audit(1362030386.924:5): apparmor="STATUS" operation="profile_load" name="/usr/lib/cups/backend/cups-pdf" pid=1079 comm="apparmor_parser" [5.000839] type=1400 audit(1362030386.924:6): apparmor="STATUS" operation="profile_load" name="/usr/sbin/cupsd" pid=1079 comm="apparmor_parser" [5.017141] type=1400 audit(1362030386.940:7): apparmor="STATUS" operation="profile_load" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=1110 comm="apparmor_parser" [5.017152] type=1400 audit(1362030386.940:8): apparmor="STATUS" operation="profile_load" name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-freerdp/freerdp-session-wrapper" pid= comm="apparmor_parser" [5.017347] type=1400 audit(1362030386.940:9): apparmor="STATUS" operation="profile_load" name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-uccsconfigure/uccsconfigure-session-wrapper" pid=1112 comm="apparmor_parser" [5.017399] type=1400 audit(1362030386.940:10): apparmor="STATUS" operation="profile_load" name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-freerdp/freerdp-session-wrapper//chromium_browser" pid= comm="apparmor_parser" [5.036613] atl1c :05:00.0: irq 54 for MSI/MSI-X [5.037121] atl1c :05:00.0: atl1c: eth0 NIC Link is Up<1000 Mbps Full Duplex> [9.898041] input: Logitech Unifying Device. Wireless PID:1024 as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.2/0003:046D:C52B.0003/input/input11 [9.898799] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1024] on usb-:00:1d.0-1.6:1 [9.900091] input: Logitech Unifying Device. Wireless PID:2011 as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.2/0003:046D:C52B.0003/input/input12 [9.900212] logitech-djdevice 0003:046D:C52B.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:2011] on usb-:00:1d.0-1.6:2 [ 1022.072341] DMA: Out of SW-IOMMU space for 30968 bytes at device :05:00.0 [ 1022.076694] DMA: Out of SW-IOMMU space for 30968 bytes at device :05:00.0 [ 1022.080899] DMA: Out of SW-IOMMU space for 13592 bytes at device :05:00.0 [ 1022.536781] DMA: Out of SW-IOMMU space for 7240 bytes at device :05:00.0 [ 1022.783313] DMA: Out of SW-IOMMU space for 7240 bytes at device :05:00.0 [ 1023.031361] DMA: Out of SW-IOMMU space for 7240 bytes at device :05:00.0 [ 1023.280154] DMA: Out of SW-IOMMU space
[Bug 775117] Re: Thunar hangs on first launch of each session
Fresh install of Xubuntu 12.04 today, bug is still present. Perhaps it's time to install an alternative file manager... -- 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/775117 Title: Thunar hangs on first launch of each session To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/775117/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 42720] Re: Copying files to webdav broken (first completely copied to RAM and then transfered)
I've done some testing around in this area as well as discovered some information that may be relevant to this bug, so I wanted to update it here. I'm doing all of this on my LAN, as my server resides on my LAN. I'm also working on a gigabit connection. I was able to push 8,000 files amounting to 30GB to my WebDAV server with 0 issues from my desktop, which is the system I mentioned above with 8GB of RAM. I saw no memory spike whatsoever. Likewise, if I sent a single 5.9GB file to my WebDAV server, it spiked and when the file had sent roughly 4GB of the 5.9GB size, it tanked the connection with the RAM nearly 100% maxed. It seemed to play significantly nicer with smaller files, such as the 8,000 above (30GB) that it had zero issues with. I have to assume that it's caching the files prior to sending them, and the system is able to let go of the cached files once they're already sent, thereby resulting in no visible memory spike. LIkewise, the singular 5.9GB file is one solid large file would have nothing to "let go" since it's one continuous file. That's probably where the 8,000 file scenario has an advantage. When I ran into this "bug" I decided to try out alternatives. I found davfs2 which mounts WebDAV shares via terminal. Davfs2 had the same issue, however I realized it was more reliant on hard disk space versus RAM. A quick read of the man page of davfs showed: ## Caching mount.davfs tries to reduce HTTP-trafic by caching and reusing data. Information about directories and files are held in memory, while downloaded files are cached on disk. mount.davfs will consider cached information about directories and file attributes valid for a configurable time and look up this information on the server only after this time has expired (or there is other evidence that this information is stale). So if somebody else creates or deletes files on the server it may take some time before the local file system reflects this. ## I can't help but to wonder... if davfs caches by default, is that to suggest Nautilus/.gvfs is actually handling WebDAV services as intended? Can any devs comment on this info? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/42720 Title: Copying files to webdav broken (first completely copied to RAM and then transfered) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-vfs/+bug/42720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 42720] Re: Copying files to webdav broken (first completely copied to RAM and then transfered)
Just ran into this myself. I have 8GB in my system, and my system locks up @ 4.3GB of RAM each and every single time. This is happening when I'm sending a single 5.9GB compressed folder to a WebDAV server I have on my LAN. I'm doing this through Nautilus. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/42720 Title: Copying files to webdav broken (first completely copied to RAM and then transfered) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-vfs/+bug/42720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
