[Bug 1264115] Re: Gedit hangs while searching in large file
It seems to be notable in html files when highlighting is on. -- 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/1264115 Title: Gedit hangs while searching in large file To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1264115/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1460997] [NEW] Wastebasket / Trash can't handle long file names
Public bug reported: Can't delete files with names longer than 131 characters. Thunar says: File operation in progress Moving files into the wastebasket... Unable to create wastebasket info file File name too long Using 'rm' on the command line does delete the file. gvfs-trash, however, produces the same error on the command line: Error deleting file: Unable to create wastebasket info file: File name too long. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- 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/1460997 Title: Wastebasket / Trash can't handle long file names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1460997/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 406373] Re: rhythmbox crashed with SIGSEGV in rb_encoder_encode()
This bug appears to have been fixed! It seems so. I installed Rhythbox the other day, completely on the off-chance because I had got fed up with being unable to update my ipod. And it worked! I just did it again too! This is brilliant. Linux is brilliant. We are really not worthy of such greatness, us miserable ungrateful, scrounging users. What have we done to deserve such gifts? I am sorry for ever doubting linux. I am sorry for every foul word. I just wish I had consulted a clairvoyant months ago, because I might have discerned sooner that the bug had been fixed and it was possible to update my ipod again. Don't mind us, we'll just talk amongst ourselves. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/406373 Title: rhythmbox crashed with SIGSEGV in rb_encoder_encode() To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/406373/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 376073] Re: Pdf search doesn't find strings running over lines
This error is still effecting me. It has been this way for four years. I have a pdf open in Okular. If I search for a term with two words, Okular will not find it if the term runs over a line. So you have to remember to search for either of the words in the term, and lug past all those matches where the single word was found but the term wasn't there. Linux pdf search can't handle two words. It's a joke. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/376073 Title: Pdf search doesn't find strings running over lines To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/376073/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1230231] [NEW] gnome-sound-recorder does not record
Public bug reported: gnome-sound-recorder not working. Failure was, initially, an attempt to get it recording streaming audio out of the box. That having failed, I tried changing its options, and my (alsa) sound options. Failing that I started looking for help online: the problem looked horribly complex and the way to a solution looked frought with difficulty, with a horrendously steep learning curve. It looked like I might have to learn all about Linux's underlying sound system just to get the recording device to work. I gave up and went back to my work without the hope that I might go an as before, doing the recording of streaming audio that had been an essential part of it. That was nearly a year ago when I upgraded to Xubuntu, and I have recovered the same steps again occassionally, just to check it still wasn't working, and just to check that I've not seen an easy solution because I'm stupid. I think I have come to understand that I'm not stupid; I'm a user. And the sound recorder doesn't work. In the sound-recorder interface, the options are stuck. 'Record from input' offers only one option: Master 'Record as' offers no options: it is blank. Pressing record does nothing. The sound level indicator is flat. I have played with some of the settings in the user interface for (Alsa) sound preferences. But it has acheived nothing. Most of the settings in the Alsa interface are not written in English anyway. They are written in some sort of arcane sound architecture language that can be understood by nobody but sound software experts, programmers and perhaps linux computer administrators. The Alsa output options are actually refreshingly comprehensible. They are written in plain English. But it's input options are gibberish. The Campaign for Plain English are worth a ganders. The idea of plain English is not that you have to write everything in goo-goo baby- language, or spell it out as if it is thought that users are idiots. You just have to write user interfaces in a way that allows people not immersed in the arcane world of sound architectures to use them. This is a bug because it doesn't work and because there is no way for a sensible user to find any reasonable way of getting it working. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-media 3.4.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Wed Sep 25 10:15:30 2013 InstallationDate: Installed on 2012-11-28 (300 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: gnome-media UpgradeStatus: Upgraded to raring on 2013-05-14 (133 days ago) ** Affects: gnome-media (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-media in Ubuntu. https://bugs.launchpad.net/bugs/1230231 Title: gnome-sound-recorder does not record To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-media/+bug/1230231/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1230231] Re: gnome-sound-recorder does not record
Woah there though. My description of Alsa user interface settings is only the *impression* I have after being unable to make any sense of them. The input settings are actually described in fairly plain English. All of the settings are not. And in combination, the effect is to overwhlem the user with technical gibberish. The programmers have obviously put a lot of effort into making an user-friendly interface. It just seems there's work to be done because it doesn't work and the interface doesn't help. So you are left with two choices: blame the sound interface or blame the sound recorder. I blame both. The one fails to work, the other fails to make any sense. And that is the crucial thing about the sound interface - it's hard to make sense of what should be a simple thing. I simply need to record streaming audio. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in Ubuntu. https://bugs.launchpad.net/bugs/1230231 Title: gnome-sound-recorder does not record To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-media/+bug/1230231/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1230231] Re: gnome-sound-recorder does not record
Something else of note regarding the actual bug. The user interface for my (alsa) sound settings seems to only offer options when there is a sound programme active. The 'Recording' tab in my sound settings interface says: No application is currently recording audio. It says this even after I open Sound Recorder. Opening Audacity doesn't make any difference. Input devices has a thicket of options. So try this: You are a user. You want to record streaming audio. You find the recorder doesn't work. You go to input devices in the sound settings user interface. It has two lots of options. I.e. each option has a multitude of options. Ok, Fine. So lets see the 'Show' options: ' All input devices All except monitors Hardware input devices Virtual input devices Monitors ' So your first question is, where's streaming audio? I consider it a sign of my relative technical sophistication that the phrase 'streaming audio' makes sense to me. Just think how many people don't. How far would they get? Anyway, back to me. I can't see streaming audio. I don't even have any input device as far as I know. I have a computer. I don't have a microphone. I have an earphonse socket. I record my music on it. I listen to it in my earphones. I use the web. That's it. Devices? I dread to know the difference between hardware, virtual and monitor devices. I'm sure its interesting. But I don't have the luxury of spare time. Would that I had. So you select 'All devices' of course. It offers you then two other options. It offers you a volume control for Monitor of built in audio analogue stereo. And one for Built in audio analogue stereo. I don't even know what that is. Is it my sound card? Does my computer even have a sound card? I consider it a mark of my technical superiority over most nobby users that I even know that my computer *probably* doesn't have a sound card. It *probably* has a sound chip! Aren't I clever. If I had time to spare, I even might look it up. But I don't, so I'll get back to trying to get my sound recorder to work. As for what built in audio analogue stereo is, the prospect of looking it up online fills me with despair. This is just the first option. That could take a whole evening on its own. There's a whole thicket of options to get through yet. I mean, elsewhere it offers me an option for digital stereo. Isn't it all digital? How do I get it to record streaming audio? Anyway, built in audio analogue stereo is offers me some other options: microphone 1, microphone 2, line in, analogue input, video. None of them seem to describe anything I know. As far as I'm aware, I don't have any analogue input devices. What is an analogue input device? I don't have any microphones (being a superior sort of computer user, I know my computer *probably* has a mic built in somewhere, but I don't use it). I don't have a video connected. I don't even have a DVD playing. And 'line in' - is that like if you have an audio line going *in* to the back of your computer. I think I may have a line in. But I think last time I looked there may have only been a mic input. I don't remember. But I just need to record streaming audio anyway. I tried various options. Nothing seems to make any difference. It seems the sound settings user interface wants to be told about input devices. Is my sound card an input device? Is the web an input device? Dare I try and find the answer when the ground ahead looks very much like quicksand that will suck you in up to your neck in sound architecture before you know it? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in Ubuntu. https://bugs.launchpad.net/bugs/1230231 Title: gnome-sound-recorder does not record To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-media/+bug/1230231/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 575877] Re: gnome-keyring mysteriously asks for keyring password on startup
That was nonsense, what I said about Tor. It's not Tor at all. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/575877 Title: gnome-keyring mysteriously asks for keyring password on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/575877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 575877] Re: gnome-keyring mysteriously asks for keyring password on startup
The problem appears to be the Tor network. The keyring does not perk up when not connected to the Tor network. This is still a problem because Tor network users have it connected routinely. The software updater also checks in routinely. The keyring problem will therefore occur routinely. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/575877 Title: gnome-keyring mysteriously asks for keyring password on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/575877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 575877] Re: gnome-keyring mysteriously asks for keyring password on startup
Further info. The keyring password request started appearing after I opened a Software Centre account. It seems to appear when the Software Updater runs. This might suggest - in relation to kwill's question - that the problem is related to different passwords. The Software Centre asks for a new username and password. The request is for a low security setting: a software feeback forum on the web. It is sensible to give it a password other than your primary/root password. It is therefore most likely to be different to your keyring password. This, by the way, is the only time the system ever makes mention of a keyring password. The request for a keyring password is meaningless to the user. The error is therefore twofold: a failure of the Update and password manager - if, that is, they are indeed using a software forum password for software updates; and a failure of the user interface/experience - in that the request for a keyring password is a breakdown of usual user protocol. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/575877 Title: gnome-keyring mysteriously asks for keyring password on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/575877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 575877] Re: gnome-keyring mysteriously asks for keyring password on startup
Please see this related report: https://bugs.launchpad.net/ubuntu/+source/xfce4-power- manager/+bug/1193595 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/575877 Title: gnome-keyring mysteriously asks for keyring password on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/575877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 575877] Re: gnome-keyring mysteriously asks for keyring password on startup
This problem has arisen periodically for years. It has just arisen again on my computer. I've been running Xubuntu 13.04 since April. It just now started to ask me for a keyring password. It says (and apologies - I shall have to report the precise message at next startup) - it says something like 'keyring password not set at startup'. The keyring password request occurs apparenlty randomly. And when it comes it prevents user access to all other programs. Unless you shut down the computer, you have to give it your system password. I second Alroger: this is most offensive behaviour. I don't want to give my password out to any popup - especially one that is random, erroneous and unexplained. Every time it happens I feel like I'm being fleeced by some phishing scam. I suspect it may have something to do with the Ubuntu Software Centre. The keyring problem started happening after I accessed the Software Centre's user account recently. It asked for a keyring password. It came up again when subsequently I opened the Software Centre just to download some software. And now it has stuck around. The kering just pops up at random in a session. It's been a few days, at a guess. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/575877 Title: gnome-keyring mysteriously asks for keyring password on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/575877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189095] [NEW] gedit IBUS-WARNING - The owner of .. /.config/ibus/bus is not root!
Public bug reported: This is ubuntu-bug report and further info is meant to be added to another bug, but Launchpad could not find it by even a part of its title (odd name must have thown it): https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1125944 - (gedit:3366): IBUS-WARNING **: The owner of /home/oem/.config/ibus/bus is not root! Issue occured for me in very specific circumstances: attempt to run two sudo gedit commands running simultaneously. The second failed with the error: (gedit:3214): IBUS-WARNING **: The owner of /home/username/.config/ibus/bus is not root! It failed in the sense that gedit did not open. It may have been significant that a related command was already running in another terminal (xfce4-terminal 0.6.1) window: sudo iptables -L iptables_rules_.txt This comand takes a while to chug through its output. So gedit, or whatver, was already occupied. While that was happening, I had issued another sudo gedit command in another terminal window: sudo gedit /etc/firewall.bash It was that comand reported the above-quoted error. The failed sudo gedit command was resissued after the first had finished. Gedit opened the (new) file this time. It appeared, in other words, to have worked. It nevertheless repeated the error: (gedit:3301): IBUS-WARNING **: The owner of /home/username/.config/ibus/bus is not root!. The file meanwhile, was edited and saved without a problem. Xubuntu 13.04 i686 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun Jun 9 08:41:29 2013 InstallationDate: Installed on 2012-11-28 (192 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to raring on 2013-05-14 (25 days ago) ** Affects: gedit (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 gedit in Ubuntu. https://bugs.launchpad.net/bugs/1189095 Title: gedit IBUS-WARNING - The owner of .. /.config/ibus/bus is not root! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1189095/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 406373] Re: rhythmbox crashed with SIGSEGV in rb_encoder_encode()
I got something like this problem. It gives me a kernel error. The problem occurs when I try to use Rythmbox to copy tracks to my ipod. i686 xubuntu 12.10 and 13.04 the same. I filed as crash report. It has been like this for many months. I had been waiting for upgrade in the hope that this would correct the problem. It has not. I have meanwhile been copying tracks for my ipod onto a usb and then doing the transfer using Rhythmbox on another machine running Xubuntu 12.04 i386. The later Xubuntu version did not install on this machine because the kernel dropped support for non-PAE CPUs. This may suggest a kernal problem. The following line appeared in kern.log when Rhythmbox crashed: May 21 19:46:03 Bonzo kernel: [36390.947600] rhythmbox[5566]: segfault at 30 ip 7f5a9122ecd0 sp 7fff127575e8 error 4 in libgstpbutils-1.0.so.0.6.0[7f5a9121f000+22000] This may be a different error to the one being dealt with here. Please advise if so and I will file it as a separate report, if necessary. Perhaps you will be kind enough to deal with accordingly? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/406373 Title: rhythmbox crashed with SIGSEGV in rb_encoder_encode() To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/406373/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 376073] Re: Pdf search doesn't find strings running over lines
This fix should be high priority. It can be hard to prove a negative. The same goes for documents. I.e. Professional people who use .pdf readers sometimes have a need to prove something does not exist in a document. They can do this by searching for the thing they need to disprove. But if the search does not work properly because it can't spot strings that fall over lines, and they don't know that this fault exists, they will end up making decisions based on faulty information given them by the software. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/376073 Title: Pdf search doesn't find strings running over lines -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 670341] Re: Find keyboard shortcut does not deliver subsequent keypresses into Find dialogue box
Ah, I don't know what this upstream lark is. I would presume it means that its someone else's problem. All I know as a user, is when you report a bug, you are taken to Launchpad. So you file your bug reports in Launchpad. I've just clicked your link and it says I need to log into yet another bug reporting website called Bugzilla. Fair enough. I shall have a look at this Bugzilla thing when I've got the time. -- 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/670341 Title: Find keyboard shortcut does not deliver subsequent keypresses into Find dialogue box -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 185928] Re: Pressing Space key should toggle play/pause (pause when playing; play when paused)
I'd second the call for SPACE to activate play/pause in Rhythm Box. A one-touch play/pause is essential. Try this: playing your guitar, learning a song. You have to play/pause. You can't be fiddling around with CTRL+SPACE or whatever when you are trying to pin down a riff. Or what happens if the phone rings when you are rocking out? Or you're eating cornflakes in your best suit? As for accessibility, having SPACE as play/pause is a darn sight more accessible than having to fumble all over CTRL+SPACE or whatever. Also regarding accessibility, if SPACE needs commandeering for accessibility applications, surely it can so be without stopping SPACE being used for play/pause when accessibility applications are not active. -- 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/185928 Title: Pressing Space key should toggle play/pause (pause when playing; play when paused) -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 670341] Re: Find keyboard shortcut does not deliver subsequent keypresses into Find dialogue box
Thanks for changing it back. I have some further info. I have now got a faster machine with more memory. The problem does not occur any more because my processing is no longer slow enough to trigger it. If, however, the issue has not been addressed in the code, I would suggest that there are people out there with slower machines who this may effect. It could be fixed for their sake, perhaps? -- 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/670341 Title: Find keyboard shortcut does not deliver subsequent keypresses into Find dialogue box -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 698109] Re: Nautilus freezes when separate File Operation is interrupted with Error
** Summary changed: - Nautilus froze + Nautilus freezes when separate File Operation is interrupted with Error -- 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/698109 Title: Nautilus freezes when separate File Operation is interrupted with Error -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 698109] [NEW] Nautilus froze
Public bug reported: Binary package hint: nautilus This problem occured within a day of performing a clean install of Ubuntu 10.10. 1) Ubuntu Release 10.10 2) Nautilus version: 1:2.32.0-0ubuntu1.1 3) What expected to happen: I was just moving a few folders around. I expected this to proceed as usual. There were a few things going on simultaneously. Nautilus had three tabs open. Gedit was open in my second workspace area. I was doing some file copying In my fourth workspace: 20Gb of files were being copied from an external HD using NTFS, over USB to my local ext4 HD. The process was occasionally being interrupted with filenames that were too long. 4) Nautilus in the first workspace froze. A folder was selected in its frozen state. I cannot deselect the folder nor select another folder. Neither can I select another tab or the Nautilus menu or toolbars. Please note, however, that Nautilus did not report an Error. It just froze. Please note also that my 20Gb copy in Workspace 4 was not interrupted. It carried on just fine. I have reported this as a separate bug as well as adding it as a comment at this similar RESOLVED bug #428564. I did this so that my Apport data could be filed. (https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/428564) ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: nautilus 1:2.32.0-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8 Uname: Linux 2.6.35-24-generic i686 Architecture: i386 Date: Thu Jan 6 13:01:23 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: nautilus ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- 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/698109 Title: Nautilus froze -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 698109] Re: Nautilus froze
-- 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/698109 Title: Nautilus froze -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 428564] Re: nautilus crashed while copying a set of large files
I have experienced a similar problem with the latest release. This problem occured within a day of performing a clean install of Ubuntu 10.10. 1) Ubuntu Release 10.10 2) Nautilus version: 1:2.32.0-0ubuntu1.1 3) What expected to happen: I was just moving a few folders around. I expected this to proceed as usual. There were a few things going on simultaneously. Nautilus had three tabs open. Gedit was open in my second workspace area. I was doing some file copying In my fourth workspace: 20Gb of files were being copied from an external HD using NTFS, over USB to my local ext4 HD. The process was occasionally being interrupted with filenames that were too long. 4) Nautilus in the first workspace froze. A folder was selected in its frozen state. I cannot deselect the folder nor select another folder. Neither can I select another tab or the Nautilus menu or toolbars. Please note, however, that Nautilus did not report an Error. It just froze. Please note also that my 20Gb copy in Workspace 4 was not interrupted. It carried on just fine. Should I report this as a separate bug? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/428564 Title: nautilus crashed while copying a set of large files -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 428564] Re: nautilus crashed while copying a set of large files
I have added this as a separate bug here: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/698109 I did so in order for my Apport data to be filed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/428564 Title: nautilus crashed while copying a set of large files -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 698109] Re: Nautilus froze
I've narrowed this down to the nub. The specific bug as can thus far be certain: Nautilus freezes when separate File Operation interrupted with Error caused by over-long filename. To recap: I have Nautilus running in Ubuntu Workspace 1. I have a large File Operation running in Workspace 4. When the File Operation in Workspace 4 is interrupted with an error such as File name too long, my instance of Nautilus in Workspace 1 freezes. When I clear the File Operation error in Workspace 4, Nautilus becomes operative again in Workspace 1. Perhaps it is normal behaviour for a File Operation error message to prevent other actions. But I can use other programs while the FO Error is waiting for my attention in Workspace 4. I can, for example, use Firefox and Update Manager or run a terminal. I just can't use the Nautilus window I already had open. Note that I can open a new Nautilus window while the FO Error is waiting my attention. But once the new Nautilus Window has opened I am unable to use it. Neither can I close it. If, however, I tell the File Operation Error dialogue in Workspace 4 to [Skip], Nautilus starts working again in Workspace 1. -- 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/698109 Title: Nautilus froze -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 428564] Re: nautilus crashed while copying a set of large files
Note: my problem appears to be directly related to File Operations. What follows is a copy of related comment I just added to Bug 698109: I've narrowed this down to the nub. The specific bug as can thus far be certain: Nautilus freezes when separate File Operation interrupted with Error caused by over-long filename. To recap: I have Nautilus running in Ubuntu Workspace 1. I have a large File Operation running in Workspace 4. When the File Operation in Workspace 4 is interrupted with an error such as File name too long, my instance of Nautilus in Workspace 1 freezes. When I clear the File Operation error in Workspace 4, Nautilus becomes operative again in Workspace 1. Perhaps it is normal behaviour for a File Operation error message to prevent other actions. But I can use other programs while the FO Error is waiting for my attention in Workspace 4. I can, for example, use Firefox and Update Manager or run a terminal. I just can't use the Nautilus window I already had open. Note that I can open a new Nautilus window while the FO Error is waiting my attention. But once the new Nautilus Window has opened I am unable to use it. Neither can I close it. If, however, I tell the File Operation Error dialogue in Workspace 4 to [Skip], Nautilus starts working again in Workspace 1. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/428564 Title: nautilus crashed while copying a set of large files -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 670341] Re: Find keyboard shortcut does not deliver subsequent keypresses into Find dialogue box
I'm sorry to see this has been given status Opinion. Will it actually get discussed or merely ignored? I fear my report is too verbose. The fact remains that keypresses made immediately after the invocation of the Find function using the keyboard short are not captured. This is a problem. -- Find keyboard shortcut does not deliver subsequent keypresses into Find dialogue box https://bugs.launchpad.net/bugs/670341 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 670341] [NEW] Find keyboard shortcut does not deliver subsequent keypresses into Find dialogue box
Public bug reported: Binary package hint: gedit When using the keyboard shortcut to Find text, it is usual to deploy it on the fly. That is, seemlessly. There is unfortunately a seem in Gedit's Find shortcut. The process, while in the midst of working in the text editor, takes a split second, and it usually goes like this: - Establish a need to find text - Press the keyboard shortcut to Find - Enter the text to be found - Press return - Find the text - Continue working Gedit, however, does not capture keypresses made immediately following the invocation of the Find function with the keyboard shortcut. It begins capturing keypresses and putting them in the Search field of the Find dialogue only after the dialogue has opened. Since the dialogue can take a while to open there is an unnatural pause between the Find invocation and the dialogue's appearance. Any keypresses that are made in this space are channelled into whatever document is open in Gedit. But it is normal to start typing the text to be found immediately after the Find function has been invoked with the keyboard shortcut. It is not only frustrating to have to wait for the dialogue to open, it is unintuitive. The result is that text intended for the Search field is forever being entered the document because the Find function is taking too long to catch up. The resulting processes looks like this: - Establish a need to find text - Press the keyboard shortcut to Find - Enter the text to be found - See that the Find dialogue has opened slowly and the find text has not appeared in the Search field - Press Esc to close the Find dialogue again - Delete the text that has been put in the document instead of the Find dialogue - Press the keyboard shortcut to Find again - What patiently for the Find dialogue to open - Enter the text to be found - Press return - Find the text - Continue working You might think that I should learn to wait. But I do find this is happening time and again because I have an unshakable expectation that keypresses made after the invocation of a function will go to that function. Or this may be because my machine is slow. This should not, however, prevent my keypresses being captured at the right time and put in the right place so that my use of the keyboard operates as it ought, which is seemlessly. Excellent text editor all the same. Markling. ProblemType: Bug Architecture: i386 Date: Wed Nov 3 11:49:56 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: gedit 2.28.0-0ubuntu2 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-22.67-generic SourcePackage: gedit Uname: Linux 2.6.31-22-generic i686 ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Find keyboard shortcut does not deliver subsequent keypresses into Find dialogue box https://bugs.launchpad.net/bugs/670341 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 670341] Re: Find keyboard shortcut does not deliver subsequent keypresses into Find dialogue box
-- Find keyboard shortcut does not deliver subsequent keypresses into Find dialogue box https://bugs.launchpad.net/bugs/670341 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 376073] Re: Pdf search doesn't find strings running over lines
This should be high priority. As it stands, the Ubuntu Document viewer cannot be trusted. The search function does that work. How many professions can you think of where it is crucial to know whether a string occurs in a document or not? Law, journalism, health, security, law enforcement. Need I go on? Can anyone trust to use the search in Ubuntu's document viewer? Of course they can't they shall have to manually read a document before they can establish whether the text they are looking for is there or not. Now consider an instance where one of these professionals has to establish that a string DOES NOT appear in a document. These documents can stretch to hundreds of pages. Are you going to sit down and search through manually and trust your judgment when you need to establish the absence of something as a matter of life and death, of national security, of legal importance? Of course you're not. You are going to get another piece of software to do it, aren't you? -- Pdf search doesn't find strings running over lines https://bugs.launchpad.net/bugs/376073 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 376073] [NEW] Pdf search doesn't find strings running over lines
Public bug reported: Binary package hint: evince E.g. in the following pdf: http://www.ico.gov.uk/upload/documents/library/data_protection/detailed_specialist_guides/review_of_eu_dp_directive.pdf On page 33, paragraph 6: The string 13 years runs over the first and onto the second line of this paragraph. Searching for 13 years finds no results. Searching for 13 will find the incidence of this string on this page. o/s:- Jaunty App:- Evince 2.26.1 Using poppler 0.10.5 (cairo) ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- Pdf search doesn't find strings running over lines https://bugs.launchpad.net/bugs/376073 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 315678] Re: evince crashed while searching in the PDF
I've got the same problem on both Evince and ePDF Document: 268-page .pdf Link: http://www.hm-treasury.gov.uk/d/Budget2009/bud09_completereport_2591.pdf 1. Evince Document Viewer 2.2 Search term: office Result: search counts back from 99% and crashes out when it reaches 66% Search term: office of Result: search counts back from 99% and crashes out when it reaches 66% Search term: office of government Result: search counts back from 99% and crashes out when it reaches 66% 2. ePDFViewer 0.1.6 (Emma's Software) Search term: office Result: searching one word at a time, the last occurrence of the word it is able to reach is on page 90, after which it drops out Search term: office of Result: finds the first occurrence on page 2. It drops out if I attempt to find next after that point. Search term: office of government Result: Drops out after a brief pause on page 2 where it finds office of during typing SYSTEM INFORMATION Running Ubuntu Linux, the Ubuntu 8.10 (intrepid) release. GNOME: 2.24.1 (Ubuntu 2008-10-24) Kernel version: 2.6.27-11-generic (#1 SMP Wed Apr 1 20:57:48 UTC 2009) GCC: 4.3.2 (i486-linux-gnu) Xorg: unknown (09 March 2009 10:48:54AM) (09 March 2009 10:48:54AM) Hostname: mark-laptop Uptime: 0 days 0 h 50 min CPU INFORMATION GenuineIntel, Intel(R) Pentium(R) M processor 1200MHz Number of CPUs: 1 CPU clock currently at 600.000 MHz with 1024 KB cache Numbering: family(6) model(9) stepping(5) Bogomips: 1196.10 Flags: fpu vme de pse tsc msr mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 tm pbe up bts est tm2 MEMORY INFORMATION Total memory: 1000 MB Total swap: 1608 MB STORAGE INFORMATION SCSI device - scsi0 Vendor: ATA Model: HITACHI_DK13FA-4 HARDWARE INFORMATION MOTHERBOARD Host bridge Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02) Subsystem: IBM Device 055c PCI bridge(s) Intel Corporation 82801 Mobile PCI Bridge (rev 81) USB controller(s) Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01) Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01) Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01) Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01) (prog-if 20) ISA bridge Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01) IDE interface Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01) (prog-if 8a [Master SecP PriP]) Subsystem: IBM Device 052d GRAPHIC CARD VGA controller Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) Subsystem: IBM Device 0557 SOUND CARD Multimedia controller Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01) Subsystem: IBM Device 0558 NETWORK Ethernet controller Atheros Communications Inc. AR5212 802.11abg NIC (rev 01) Subsystem: Phillips Components Device 8331 Modem Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01) Subsystem: IBM Device 0559 (I can supply logs if you tell me which ones you need and how far back they need to be copied) -- evince crashed while searching in the PDF https://bugs.launchpad.net/bugs/315678 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
