[Desktop-packages] [Bug 1890382] Re: Gnome-terminal maximize loses one line of terminal output

2020-08-06 Thread Richard Bruce Baxter
Attaching original screenshots:
gnomeTerminalMaximiseBugScreenshot1-afterLScommand.png
gnomeTerminalMaximiseBugScreenshot2-afterMaximize.png

** Attachment added: "gnomeTerminalMaximiseBugScreenshots.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1890382/+attachment/5399148/+files/gnomeTerminalMaximiseBugScreenshots.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1890382

Title:
  Gnome-terminal maximize loses one line of terminal output

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Gnome-terminal maximize loses one line of terminal output.

  Summary:
  1. Assume the gnome-terminal currently contains output that exceeds the 
maximum number of characters of its current display area (ie the text is 
wrapped)
  2. Maximise the gnome-terminal
  3. Note that one line of the original content is lost

  Replication:
  cd ~/gnomeTerminalBug/replicationTest
  touch 
01.txt
  touch 
02.txt
  touch 
03.txt
  touch 
04.txt
  touch 
05.txt
  touch 
06.txt
  touch 
07.txt
  touch 
08.txt
  touch 
09.txt
  touch 
10.txt
  touch 
11.txt
  touch 
12.txt
  touch 
13.txt
  touch 
14.txt
  touch 
15.txt
  touch 
16.txt
  touch 
17.txt
  touch 
18.txt
  touch 
19.txt
  touch 
20.txt
  touch 
21.txt
  touch 
22.txt
  touch 
23.txt
  touch 
24.txt
  touch 
25.txt
  touch 
26.txt
  touch 
27.txt
  touch 
28.txt
  touch 
29.txt
  touch 
30.txt
  touch 
31.txt
  touch 
32.txt
  touch 
33.txt
  touch 
34.txt
  touch 
35.txt
  touch 
36.txt
  touch 
37.txt
  touch 
38.txt
  touch 
39.txt
  touch 
40.txt
  touch 
41.txt
  touch 
42.txt
  touch 
43.txt
  touch 

[Desktop-packages] [Bug 1890382] Re: Gnome-terminal maximize loses one line of terminal output

2020-08-06 Thread Richard Bruce Baxter
I have encountered a seemingly related issue where ls is sometimes
displaying different output depending on the terminal display size (and
when the function is called), independent of maximisation.

** Attachment added: "gnomeTerminalDisplayBugScreenshot.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1890382/+attachment/5399141/+files/gnomeTerminalDisplayBugScreenshot.png

** Attachment removed: "gnomeTerminalMaximiseBugScreenshots.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1890382/+attachment/5398803/+files/gnomeTerminalMaximiseBugScreenshots.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1890382

Title:
  Gnome-terminal maximize loses one line of terminal output

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Gnome-terminal maximize loses one line of terminal output.

  Summary:
  1. Assume the gnome-terminal currently contains output that exceeds the 
maximum number of characters of its current display area (ie the text is 
wrapped)
  2. Maximise the gnome-terminal
  3. Note that one line of the original content is lost

  Replication:
  cd ~/gnomeTerminalBug/replicationTest
  touch 
01.txt
  touch 
02.txt
  touch 
03.txt
  touch 
04.txt
  touch 
05.txt
  touch 
06.txt
  touch 
07.txt
  touch 
08.txt
  touch 
09.txt
  touch 
10.txt
  touch 
11.txt
  touch 
12.txt
  touch 
13.txt
  touch 
14.txt
  touch 
15.txt
  touch 
16.txt
  touch 
17.txt
  touch 
18.txt
  touch 
19.txt
  touch 
20.txt
  touch 
21.txt
  touch 
22.txt
  touch 
23.txt
  touch 
24.txt
  touch 
25.txt
  touch 
26.txt
  touch 
27.txt
  touch 
28.txt
  touch 
29.txt
  touch 
30.txt
  touch 
31.txt
  touch 
32.txt
  touch 
33.txt
  touch 
34.txt
  touch 
35.txt
  touch 
36.txt
  touch 
37.txt
  touch 
38.txt
  touch 
39.txt
  touch 
40.txt
  touch 

[Desktop-packages] [Bug 1890382] [NEW] Gnome-terminal maximize loses one line of terminal output

2020-08-05 Thread Richard Bruce Baxter
Public bug reported:

Gnome-terminal maximize loses one line of terminal output.

Summary:
1. Assume the gnome-terminal currently contains output that exceeds the maximum 
number of characters of its current display area (ie the text is wrapped)
2. Maximise the gnome-terminal
3. Note that one line of the original content is lost

Replication:
cd ~/gnomeTerminalBug/replicationTest
touch 
01.txt
touch 
02.txt
touch 
03.txt
touch 
04.txt
touch 
05.txt
touch 
06.txt
touch 
07.txt
touch 
08.txt
touch 
09.txt
touch 
10.txt
touch 
11.txt
touch 
12.txt
touch 
13.txt
touch 
14.txt
touch 
15.txt
touch 
16.txt
touch 
17.txt
touch 
18.txt
touch 
19.txt
touch 
20.txt
touch 
21.txt
touch 
22.txt
touch 
23.txt
touch 
24.txt
touch 
25.txt
touch 
26.txt
touch 
27.txt
touch 
28.txt
touch 
29.txt
touch 
30.txt
touch 
31.txt
touch 
32.txt
touch 
33.txt
touch 
34.txt
touch 
35.txt
touch 
36.txt
touch 
37.txt
touch 
38.txt
touch 
39.txt
touch 
40.txt
touch 
41.txt
touch 
42.txt
touch 
43.txt
touch 
44.txt
touch 
45.txt
touch 
46.txt
touch 
47.txt
touch 
48.txt
touch 
49.txt
touch 
50.txt
touch 
51.txt
touch 

[Desktop-packages] [Bug 1797734] Re: slow calculator startup

2020-02-22 Thread Richard Bruce Baxter
This problem persists on Ubuntu 20.04. See this proposal to remove the
snap version of the package: https://discourse.ubuntu.com/t/proposal-
for-ubuntu-20-04lts/12969/92

Moreover, the apt package cannot currently be found on Ubuntu 20.04.
Diagnosis:

sudo snap remove gnome-calculator
sudo apt-get install gnome-calculator

Expected output:

apt gnome-calculator successfully installed.

Actual output:

No apt package "gnome-calculator", but there is a snap with that name.
Try "snap install gnome-calculator"

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1797734

Title:
  slow calculator startup

Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  The calculator starts very slowly. It's a tiny program, but it runs
  like a very big one. In previous versions of Ubuntu, the launch was
  normal, very fast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calculator (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:40:06 2018
  InstallationDate: Installed on 2018-05-06 (160 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1369365] [NEW] Segfault on shutdown if glutMainLoop not called (fglrx)

2014-09-14 Thread Richard Bruce Baxter
Public bug reported:

Freeglut will segfault when exiting the application if glutMainLoop is not 
called (with the fglrx video drivers). A patch has been posted on Sourceforge; 
https://sourceforge.net/p/freeglut/bugs/206
https://sourceforge.net/p/freeglut/code/1640

Here is a modified version of the patch for Ubuntu 14.04
(freeglut3_2.8.1-1_amd64.deb/freeglut3-dev_2.8.1-1_amd64.deb) based on
Bruce Merry's fix.

A method to build a custom version of the freeglut3 package on Ubuntu
14.04;

sudo apt-get install freeglut3 freeglut3-dev [this should install all necessary 
dependencies for freeglut]
sudo apt-get remove freeglut3 freeglut3-dev
sudo apt-get install build-essential [in order to compile your own programs in 
Ubuntu] [+ bison debuild(?)]
sudo apt-get install autotools-dev autoconf automake libtool dh-autoreconf 
[install all build dependencies for freeglut] 
mkdir ~/freeglut3-development
cd ~/freeglut3-development
manually download freeglut_2.8.1.orig.tar.gz from 
http://packages.ubuntu.com/source/trusty/freeglut
manually download freeglut_2.8.1-1.debian.tar.gz from 
http://packages.ubuntu.com/source/trusty/freeglut
manually download freeglut_2.8.1-1.dsc from 
http://packages.ubuntu.com/source/trusty/freeglut
dpkg-source -x freeglut_2.8.1-1.dsc [this will create folder freeglut-2.8.1 
with a debian subfolder]
rm freeglut_2.8.1-1.debian.tar.gz
rm freeglut_2.8.1-1.dsc

[Ensure patch has been created; see Record of 
freeglut_2.8.1-FREEGLUT_SOURCEFORGE_BUG206_PATCH.patch patch creation below]
cp freeglut_2.8.1-FREEGLUT_SOURCEFORGE_BUG206_PATCH.patch 
freeglut-2.8.1/debian/patches/
nedit freeglut-2.8.1/debian/patches/series 
 add reference to 
freeglut_2.8.1-FREEGLUT_SOURCEFORGE_BUG206_PATCH.patch 
cd freeglut-2.8.1   
dpkg-buildpackage -uc -us
cd ..
sudo dpkg -i freeglut3_2.8.1-1_amd64.deb freeglut3-dev_2.8.1-1_amd64.deb

---
Record of freeglut_2.8.1-FREEGLUT_SOURCEFORGE_BUG206_PATCH.patch patch creation;

cd ~/freeglut3-development/virtualPatchCreationFolder/
mkdir a
mkdir b
mkdir a/src
mkdir b/src
cp orig/freeglut_init.c a/src/
cp patched/freeglut_init.c b/src/
diff -urNad a/src b/src  freeglut_2.8.1-FREEGLUT_SOURCEFORGE_BUG206_PATCH.patch

** Affects: freeglut (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: freeglut_2.8.1-FREEGLUT_SOURCEFORGE_BUG206_PATCH (Ubuntu 
14.04)
   
https://bugs.launchpad.net/bugs/1369365/+attachment/4204087/+files/freeglut_2.8.1-FREEGLUT_SOURCEFORGE_BUG206_PATCH.patch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freeglut in Ubuntu.
https://bugs.launchpad.net/bugs/1369365

Title:
  Segfault on shutdown if glutMainLoop not called (fglrx)

Status in “freeglut” package in Ubuntu:
  New

Bug description:
  Freeglut will segfault when exiting the application if glutMainLoop is not 
called (with the fglrx video drivers). A patch has been posted on Sourceforge; 
  https://sourceforge.net/p/freeglut/bugs/206
  https://sourceforge.net/p/freeglut/code/1640

  Here is a modified version of the patch for Ubuntu 14.04
  (freeglut3_2.8.1-1_amd64.deb/freeglut3-dev_2.8.1-1_amd64.deb) based on
  Bruce Merry's fix.

  A method to build a custom version of the freeglut3 package on Ubuntu
  14.04;

  sudo apt-get install freeglut3 freeglut3-dev [this should install all 
necessary dependencies for freeglut]
  sudo apt-get remove freeglut3 freeglut3-dev
  sudo apt-get install build-essential [in order to compile your own programs 
in Ubuntu] [+ bison debuild(?)]
  sudo apt-get install autotools-dev autoconf automake libtool dh-autoreconf 
[install all build dependencies for freeglut] 
  mkdir ~/freeglut3-development
  cd ~/freeglut3-development
  manually download freeglut_2.8.1.orig.tar.gz from 
http://packages.ubuntu.com/source/trusty/freeglut
  manually download freeglut_2.8.1-1.debian.tar.gz from 
http://packages.ubuntu.com/source/trusty/freeglut
  manually download freeglut_2.8.1-1.dsc from 
http://packages.ubuntu.com/source/trusty/freeglut
  dpkg-source -x freeglut_2.8.1-1.dsc   [this will create folder freeglut-2.8.1 
with a debian subfolder]
  rm freeglut_2.8.1-1.debian.tar.gz
  rm freeglut_2.8.1-1.dsc

  [Ensure patch has been created; see Record of 
freeglut_2.8.1-FREEGLUT_SOURCEFORGE_BUG206_PATCH.patch patch creation below]
  cp freeglut_2.8.1-FREEGLUT_SOURCEFORGE_BUG206_PATCH.patch 
freeglut-2.8.1/debian/patches/
  nedit freeglut-2.8.1/debian/patches/series 
 add reference to 
freeglut_2.8.1-FREEGLUT_SOURCEFORGE_BUG206_PATCH.patch 
  cd freeglut-2.8.1 
  dpkg-buildpackage -uc -us
  cd ..
  sudo dpkg -i freeglut3_2.8.1-1_amd64.deb freeglut3-dev_2.8.1-1_amd64.deb

  ---
  Record of freeglut_2.8.1-FREEGLUT_SOURCEFORGE_BUG206_PATCH.patch patch 
creation;

  cd ~/freeglut3-development/virtualPatchCreationFolder/
  mkdir a
  mkdir b
  mkdir a/src
  mkdir b/src
  cp orig/freeglut_init.c a/src/
  cp patched/freeglut_init.c b/src/
  diff -urNad a/src b/src  

[Desktop-packages] [Bug 869793] Re: Nautilus is very slow when opening folders with many files

2014-03-20 Thread Richard Bruce Baxter
Nautilus has been slow for 13 years. If Linux file browser speed can't
improve with Moore's law then it is time to drop the fancy mime based
open every file and read its header feature in my opinion. People
should not be waiting 500ms for their file browser to display 10 files
in 2014, all for the sake of random text files that don't have an
extension and should probably be opened with a text editor anyway. In my
opinion the Nautilus UI has degraded over time, and has never met the
usability standards introduced by windows explorer 95/98 (not that
Windows has kept them). It seems like the trend in application/OS user
interface development has gone towards zero-customisability; attempting
to make one UI fit the needs of both first time and power user, an
impossible task. Here are some general suggestions to improve Nautilus
efficiency;

- instantaneous folder browsing (options to disable mime extension reading and 
any other header operations which make Nautilus slow)
- the ability to add/remove standard interface buttons (eg up folder, home 
folder)
- the ability to select a real location bar (not a bubble bar)
- the ability to remove all clutter left and right of the address bar (these 
should be located in the View menu)
- the ability to position the address bar on its own row (the user needs to be 
able to see the full path at all times, even when operating with multiple 
unmaximised file manager windows)
- the ability to show the full path in the title bar (such that Nautilus 
windows containing a folder of the same name can be distinguished in the window 
manager taskbar)
- the ability to open a new Window (Ctrl-N) at the same location
- the ability to disable the sidebar without using dconf-editor
- the ability to add keyboard shortcuts for missing functions (eg Ctrl-G for go 
button operations; note in order to press Enter after a paste operation the 
user must move their right hand off the mouse)
- the ability to add keyboard shortcuts for existing functions, without 
modifying .config/nautilus/accels (eg BackSpace for ShellActions/Up)
- the ability to view full dates/times
- the ability to select an arbitrary application to open a txt file with
- the ability to create a new document (without modifying Templates)
- the ability to navigate the UI using the keyboard (given there is no longer a 
menu bar)
- the ability to stop the search bar from popping up every time the user 
presses a character on the keyboard
- the ability to close the search bar using the mouse (without knowing that you 
have to press Ctrl-f)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/869793

Title:
  Nautilus is very slow when opening folders with many files

Status in Nautilus:
  Confirmed
Status in “nautilus” package in Ubuntu:
  Triaged

Bug description:
  Opening folders with many files takes a long time with Nautilus, to the point 
it becomes unusable for folders with more than 5K files. 
  I've measured the time it takes for folders with different amount of files to 
open with Nautilus and Gnome Commander. It is ~6 times faster with GC on 
average. In folders with ~20K files, it takes 30s with nautilus versus 6! with 
GC. 

  With Nautilus
  ~3500 files tales 6 seconds
  ~7000 files takes 18 seconds
  ~15000 files takes 22 seconds
  ~2 files takes 30 seconds

  With Gnome Commander
  ~3500 files tales 1 second
  ~7000 files takes 1.5 seconds
  ~15000 files takes 3 seconds
  ~2 files takes 6 seconds

  These are mostly small dicom files (MRI images). I am using a 8 core 3.4Ghz 
and 16Gigs of RAM with Ubuntu 11.04 64-bits.
  Also, of course, things like selecting all files and copying them around is 
absurdly slow and makes nautilus unusable... but that would be another bug 
report (?).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/869793/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 82504] Re: gnome-panel autohides inconsistently

2011-10-04 Thread Richard Bruce Baxter
The developer reaction to this basic bug is a joke, and is the reason
why people are afraid of challenging quality levels offered by
monopolies. Taskbar autohide functionality has existed in window
managers for over a decade, and Linux can't get it right... Why even
support the feature if it doesn't work?

It seems people have given up all together on this issue - out of
choice perhaps?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/82504

Title:
  gnome-panel autohides inconsistently

Status in Desktop panel for GNOME:
  Confirmed
Status in NULL Project:
  Invalid
Status in “gnome-panel” package in Ubuntu:
  Triaged
Status in “metacity” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-panel

  Hi! I'm using Ubuntu Feisty (the latest version from the official
  repositories) and I have a bit of a problem with the gnome-panel.

  I set the panels in a very similar arrangement as the default one -- a
  panel on the top side of the screen and another on the bottom, with a
  few applets changed and shuffled. I set both panels to autohide, as I
  like having my full screen available for applications. I also tweaked
  a bit the settings using the configuration editor: I set the
  hide/unhide delay to zero, and the size when hidden also to zero.

  This works almost always exactly the way I wanted it: the panel
  disappear completely when not used, and appear instantly when needed.

  However, for some reason I can't determine, sometimes I notice that
  one of the panels (I've seen it happen to either at some point) remain
  unhidden, despite the mouse cursor being outside them, and even
  clicking inside the windows. If I enter the panel with the mouse (no
  click is necessary) it will then disappear when the cursor leaves it.

  Like I said, I haven't been able to notice exactly what causes the
  panel to remain up -- but it always happens after I did something with
  it (it never pops up by itself). It seems for some reason it misses
  (or doesn't receive) a mouse-leave event or something similar.

  Please let me know if I can help diagnosing this in any way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-panel/+bug/82504/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp