I'm having the same problem since the update on 07/27/2015. Nothing
I've tried runs under Wine 1.6 or 1.7 and Syslog says segfault.
Others are reporting the same problem at:
https://askubuntu.com/questions/653732/wine-segfault-on-ubuntu-14-04
--
You received this bug notification because you
Starting wineserver from a terminal also works for me with no apparent
issues running Lotus WordPro. TNX.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479040
Title:
wineserver segfault with
Public bug reported:
After the 2011 Nov, 9 update to 10.04 Nautilus will only sort files in
list mode by size or modification date, NOT by name or type
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Transient problem, or maybe operator error?
Nautilus menu option View - Reset to Defaults seems to have corrected the
problem.
(Seems a little strange to me that what's shown may not be the default behavior
with respect to shorting when there's no apparent way to change that in the
View menu,
I'm still seeing the problem in 10.04 LTS and have no current plans to
try the more rapidly developing versions.
On 05/27/2011 12:23 PM, Pedro Villavicencio wrote:
Thanks for the report, it has been some time without any response or
feedback in this bug report and we are wondering if this is
For the record the problem persists, now in Ubuntu 10.04, Nautilus
2.30.1
--
nautilus excessive cpu and delay opening directories
https://bugs.launchpad.net/bugs/364838
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: nautilus
Selecting a large number of files in a directory is encountering
increasingly long delays in updating their displayed status. Delay
seems to increase (at least) geometrically with the number of files
selected It can take minutes to show the
Not sure why the error system on my PC connected to this bug thread, but
immediately on starting newly installed 9.10, on this Amd64 system with
Nvidia audio and video (using, I believe ATM, the open source drivers)
I'm getting persistent, essentially constant reports of System
encountered a
Problem is still present. The time before this last time I had it I let
the system try to recover for about 2 HOURS, but it never did. The only
way I've found to recover is to reboot.
I'll try to pass it up to Gnome's bugzilla when I'm a little less brain
dead.
--
gnome-screensaver bad
And I have this maybe wild idea I might claim it's a security issue:
Denial of Service by malicious entry of false password.
--
gnome-screensaver bad password timeout
https://bugs.launchpad.net/bugs/314545
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm still seeing this, as of latest updates on 9.04. Just asked
Nautilus to expand a 650 file directory in the same window, in list
(tree?) view. The content display drew after about 75 seconds, but
Nautilus remained hung for another 3 or 4 minutes, and whatever it was
doing redispatched to
I'm seeing something very similar, but it -seems- related to how may
sites I visit, as if Firefox was caching in RAM and not freeing when tab
closes. If I let it, it will fill 4 GB RAM, then semi-hang while
thrashing the swap file.
Also reported as launchpad bug # 126012.
This system is
Amendment:
In the aprox. 1 hour since my previous post something grabbed almost 2
GB of RAM, according to gnome system monitor, but it was freed when I
closed Firefox. I had 5 tabs open, but they were static and I had not
been WWW surfing.
--
Firefox 3 memory use explodes by itself randomly
Sorry, forgot to include specific package IDs:
Firefox 3.0.11
Mozilla Firefox for Ubuntu, canonical - 1.0
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.11) Gecko/2009060309
Ubuntu/9.04 (jaunty) Firefox/3.0.11
--
Firefox memory usage increases to point of no response
I'm seeing Firefox occupying increasing memory every time I go to a new
site, as if it was caching it in RAM, but not freeing it when I leave
and close the window. This is new behavior, -maybe- only after
upgrading to 9.04, or latest Firefox upgrade. It'll go to the point of
filling my 4 GB
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/28084869/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/28084870/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/28084871/ProcStatus.txt
--
SYSTEM
Further information:
I can decrease priority of a process (specifically g-s-m) but system
hung very solidly on every attempt I've made recently to increase
priority (set less nice).
When hung the busy/wait indicator spins and tracks mouse movement, but
NOTHING ELSE responds, including mouse
Public bug reported:
Binary package hint: gnome-system-monitor
Tried to increase priority of a process using the gnome system monitor
(2.26.0.1). After clicking change priority the busy/wait wheel spins
but the system is totally hung; left it for 10+ minutes one time trying
to wait it out. Only
I confirmed the problem is NOT CONSISTENT. Today I mistyped password
and immediately got Password Incorrect, then about as fast as I could
read the message, the (re) Enter Password window redrew. That WAS when
unlocking after a Lock Screen request.
(I also frequently Suspend this system and
I'm having system hang on trying to unlock screen, after a requested
lock, -probably- only when I miss-enter password. It says checking
and the little busy/wait' symbol spins, and spins and I once tried
waiting 5 minutes before resetting hardware. It only began happening on
this box after
I've been seeing this since upgrading to 9.04 -- Never saw it before. I
reported it under Launchpad bug #181065, but what I'm seeing is better
described by the earlier notes on this one.
--
gnome-screensaver bad password timeout
https://bugs.launchpad.net/bugs/314545
You received this bug
What I've been seeing seems an exact fit to descriptions of Lunchpad bug
#314545, so I've reported it there, TOO.
--
Unable to unlock the screensaver
https://bugs.launchpad.net/bugs/181065
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes. This now seems to be GNOME bugzilla #579994, I think still
'unconfirmed'
Further update:
I've upgraded the system to Ubuntu 9.04 (going through 8.10, as required), and
the problem is still there; unchanged. It seems something in Nautilus, or
something Nautilus uses, knows how, under
Public bug reported:
Binary package hint: thunderbird
Right clicking on a message line brings up the usual menu, BUT selecting
Open message in a new window. does nothing except close the menu. I
THINK it used to work as expected on this system, but it's not an option
I use often so it's
Tried it again and now Open ... new window works normally, after
failing on 10-12 tries just before submitting the above. Nothing's
changed that I'm aware of (no updates).
Guess it heard me complaining. If Mozilla's perfected self fixing
software congratulations; meanwhile I'll keep poking at
Squeezing the problem into a smaller box:
The long delays seem very clearly associated with asking Nautilus to
expand a directory in the existing list view window by clicking on the
arrow to its left (turning the arrow down) Doing that just now on a
directory of about 700 (text) files took about
I'll surface this on Bugzilla as soon as I figure out how to.
Sorry about the confusion. I almost never use icon views so didn't
immediately realize I wasn't getting one when I selected Open new
directories as icon view in preferences, then asked it to expand in the
existing window. It seems
I understand very well a transient bug, or as in this case one
apparently affecting only a specific system, is very difficult or
impossible to address. I'll try to explore the envelope to see if I can
associate it with anything more definitive or enlightening.
At this point the problem seems
A couple quick/easy 'discoveries':
Time to open directories seems about linear in number of items (1m
20sec for 370, 2m 50sec for 670.) Anyway apparently not exponential.
(These were all text files BTW.)
A few times nautilus has remained busy/hung for several minutes
_after_ showing
A couple of minor clarifications:
Looking more extensively I now believe I experience the problem
(bug) every time I use nautilus, it's just not subjectively important on
small (10-20 file) directories, and some large directories seem less
affected than others, but I haven't discovered any
Recently (I think about the same time I began noticing bug 364838) the
Exit options window on this system) began opening BEHIND the active
window, and other windows on the desktop no longer dim out as they had
previously. I can click it on the task panel and bring the Exit window
to the front,
For what it might be worth I noticed, the Exit window on this system
now opens BEHIND the active window (Exception: NOT one for a Wine app.)
and other desktop windows no longer dim when the Exit window opens.
All probably began happening the same time as the Nautilus problem
I've attached a note
TYPO IN THE ABOVE: Last bug reference should also be to 364838.
--
Shut Down the Computer-window spawns behind active window
https://bugs.launchpad.net/bugs/317855
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/25834230/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/25834232/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/25834233/ProcStatus.txt
--
nautilus
Public bug reported:
Binary package hint: nautilus
Today Nautilus takes up to several minutes to open -some- directories. Didn't
yesterday, on same directories.
Ubuntu 8.0.4, AMD64 -- updates current as of '09/04/21, 20:00 GMT -- Quad core
2 GHz AMD 64 CPU, so nautilus is burning a LOT of
The problem's reproducible in that it's persistent and consistent. I
just now tried opening one of the directories on which I first noticed
the problem and it took about two minutes of pretty heavy CPU activity
to go from showing the directory arrow turned downward to displaying the
detail
36 matches
Mail list logo
