** Changed in: gedit
Status: Confirmed => Fix Released
** Changed in: gedit
Importance: Unknown => Medium
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this bug notification because you are a member of Ubuntu
Deskt
I just had a very similar problem. gedit was consuming 100% CPU usage
every time I started it. I tried removing the config file with no
improvement. I then found this bug report and investigated the side pane
file browser. This was pointing at a point in the dvb source tree. When
I changed this to
** Branch linked: lp:ubuntu/gedit
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
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
** Changed in: gedit (Ubuntu)
Assignee: nikhil (nikhilkumarverma1122) => Ubuntu Desktop Bugs
(desktop-bugs)
** Changed in: gedit (Ubuntu Intrepid)
Assignee: nikhil (nikhilkumarverma1122) => Ubuntu Desktop Bugs
(desktop-bugs)
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg
** Changed in: gedit (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => nikhil
(nikhilkumarverma1122)
** Changed in: gedit (Ubuntu Intrepid)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => nikhil
(nikhilkumarverma1122)
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg
Copied to intrepid-updates.
** Changed in: gedit (Ubuntu Intrepid)
Status: Fix Committed => Fix Released
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this bug notification because you are a member of Ubuntu
Desktop B
intrepid-proposed package copied to jaunty.
** Changed in: gedit (Ubuntu)
Status: Fix Committed => Fix Released
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this bug notification because you are a member of Ubuntu
De
I had the problem even after updating with the new pre-released one as
suggested, yet disabling the filebrowser plugin solved it.
Regards,
Kevin
danielhollocher wrote:
> Martin Pitt and mac_v, because of the nature of the bug that I
> originally reported, I'm curious which folder you are testin
Ah, I can confirm that the filebrowser now takes *much* less CPU; having
/var/lib/dpkg/info in the filebrowser is bearable with the update now,
whereas it completely blocked gedit in intrepid final.
Thus re-marking as verified.
I originally tested this with "gedit /var/lib/dpkg/info/adduser.list"
well, the original bug was in the filebrowser plugin So, disabling
it is the workaround, but it is also an indicator if you have the same
bug. Anyway, I don't know.
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this bug
danielhollocher> actually i filed a separate bug>
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/292486
but sebastien bacher marked my bug as a duplicate of this... so i
continued here...
BUT WOW... ur suggestion of disabling the file browser plugin , worked... now i
have no wait times...
Martin Pitt and mac_v, because of the nature of the bug that I
originally reported, I'm curious which folder you are testing gedit on.
This bug ended up being about the file browser plugin, and the negative
behaviour was wholly dependent on what folder the file resided in. This
patch aims to addre
I tested it as well, and with 2.24.0 and 2.24.1 it behaves exactly the
same way: gedit opens the file in a matter of seconds, but after that it
constantly uses 50 to 70% CPU.
** Tags removed: verification-done
** Changed in: gedit (Ubuntu Intrepid)
Status: Fix Committed => Confirmed
--
g
danielhollocher> i have a 1.66GHz DUO core, which i dont think is a slow
CPU...
when i used ubuntu 8.04 the gedit used to open in 4-6 secs... almost
instantaneoulsy
now since i'v upgraded to 8.10 it takes 35-40 secs... before the gedit
update it was around 30 secs... so this update has increased
** Tags added: verification-done
** Tags removed: fix-needed
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mai
you might have an issue different of the one described there
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mail
well, It just hit the repos as I wrote that message. I confirm that the
patch works as intended. 177 second cpu burn is now a 10 second cpu
burn. I also opened up the filebrowser pane, and it seemed to be
working. I then went to /var/lib/dpkg/info, and the same 10 second burn
took place, but it
** Tags added: fix needs
** Tags removed: verification-needed
** Tags added: fix-needed
** Tags removed: fix needs
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this bug notification because you are a member of Ubuntu
Desk
just for reference, I've tested with the old gedit. I get about 177
seconds load time on my computer. I ran it twice. I'll test the
loading speed of the new package, as soon as it hits the repos.
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/
NO... still the CPU bump exists for me, if i may say it time for the
gedit to start takes even longer now, with this new[2.24.1-0ubuntu1]
version check the attached screenshot of both the version and the
duration of the CPU hogging...
problem not yet solved
** Attachment added: "Screenshot.png"
Verification done. Reproduced the constant cpu usage with
2.24.0-0ubuntu1, and verified it was gone with 2.24.1-0ubuntu1. Checked
some basic gedit functionality as well and everything seems ok.
** Tags added: verification-done
** Tags removed: verification-needed
--
gedit uses %100 CPU when ope
Accepted into intrepid-proposed, please test and give feedback here.
Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
** Changed in: gedit (Ubuntu Intrepid)
Status: Confirmed => Fix Committed
** Tags added: v
** Attachment added: "debdiff for the new stable version update"
http://launchpadlibrarian.net/19280662/gedit.debdiff.gz
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this bug notification because you are a member of Ubun
** Changed in: gedit (Ubuntu Intrepid)
Importance: Undecided => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: New => Confirmed
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this bug n
i can also confirm... it happens for any file which opens gedit the
first time...
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
** Changed in: gedit
Status: Unknown => Confirmed
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
** Changed in: gedit (Ubuntu)
Status: Confirmed => Triaged
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
** Bug watch added: GNOME Bug Tracker #554362
http://bugzilla.gnome.org/show_bug.cgi?id=554362
** Also affects: gedit via
http://bugzilla.gnome.org/show_bug.cgi?id=554362
Importance: Unknown
Status: Unknown
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https:/
I can confirm the additional breakage that Pablo is describing. I will
file an upstream bug report.
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
I can confirm it under Intrepid fully updated.
Then everytime that I run gedit from terminal, it consumed 100% of cpu
until I have opened an old txt file that I had in my desktop. I can
still reproduce this behaviour
** Changed in: gedit (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs)
confirmed on intrepid, it goes through all the files in the directory,
that's an upstream issue and should be opened on bugzilla.gnome.org too
** Changed in: gedit (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: New => Confi
31 matches
Mail list logo
