gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
Bug #276094 reported by
Daniel Hollocher
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gedit |
Fix Released
|
Medium
|
|||
gedit (Ubuntu) |
Fix Released
|
Low
|
Ubuntu Desktop Bugs | ||
Intrepid |
Fix Released
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: gedit
I don't know why, or if any other folder is affected. But, I tried to open a few files in /var/lib/dpkg/info/ and they all caused the cpu burn.
A condition for this to happen is that gedit must be closed prior to opening the file. If gedit is already open, it doesn't happen.
Example command: gedit /var/lib/
The problem happens if you try to open the file through nautilus too. And with gksu. The only time it doesn't happen is if gedit is already open.
Related branches
Changed in gedit: | |
status: | Confirmed → Triaged |
Changed in gedit: | |
status: | Unknown → Confirmed |
Changed in gedit: | |
assignee: | nobody → desktop-bugs |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in gedit: | |
assignee: | desktop-bugs → nikhilkumarverma1122 |
assignee: | desktop-bugs → nikhilkumarverma1122 |
Changed in gedit: | |
assignee: | nikhilkumarverma1122 → desktop-bugs |
assignee: | nikhilkumarverma1122 → desktop-bugs |
Changed in gedit: | |
importance: | Unknown → Medium |
status: | Confirmed → Fix Released |
To post a comment you must log in.
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