[Desktop-packages] [Bug 1048441] Re: gnome-terminal displays "missing font" glyph very poorly
I'm attaching a screenshot of Ubuntu 18.04.1 with gnome-terminal 3.28.2-1ubuntu1~18.04.1 having the bug. ** Attachment added: "Screenshot of the bug in Ubuntu 18.04.1" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1048441/+attachment/5225361/+files/2018-12-27-082433_398x270_scrot.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/1048441 Title: gnome-terminal displays "missing font" glyph very poorly Status in gnome-terminal package in Ubuntu: Incomplete Bug description: I was wondering why some of my log lines did not contain a final closing doublequote, if the quoted string contained some funky UTF-8. In fact, they did -- the quote glyph was just drawn in the same space as the "font missing" glyph. Attaching a screenshot to demonstrate. Run python -c "print u'\U0000X <- the X is obscured'" to see for yourself. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.4.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Sun Sep 9 19:06:35 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1048441/+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 1054808] Re: Default filename for screenshots is problematic
Please notice that default name is not compatible with default Owncloud client sync configuration client as '\', '/', '<', '>', ':', '"', '|', '?' and '*' are not allowed. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1054808 Title: Default filename for screenshots is problematic Status in Gnome Screenshot: New Status in “gnome-screenshot” package in Ubuntu: Confirmed Bug description: Press "printscreen" and you'll get a default filename of:- "Screenshot from -MM-DD HH:MM:SS.png" Fine for browsing in nautilus and double clicking on, but this format (specifically the colons) has been a bane for me for some time. 1. Tab completion fails:- -rw-rw-r-- 1 alan alan 751K Sep 23 01:10 Screenshot from 2012-09-23 01:10:33.png # tab completion works as far as here alan@deep-thought:~/Pictures$ scp Screenshot\ from\ 2012-09-2 Screenshot\ from\ 2012-09-21\ 19\:40\:46.png Screenshot\ from\ 2012-09-23\ 01\:01\:41.png Screenshot\ from\ 2012-09-23\ 01\:10\:33.png # get to here and it won't finish the filename off. alan@deep-thought:~/Pictures$ scp Screenshot\ from\ 2012-09-23\ 01\: 2. scp fails. alan@deep-thought:~/Pictures$ scp Screenshot\ from\ 2012-09-23\ 01\:10\:33.png popey.com: ssh: Could not resolve hostname Screenshot from 2012-09-23 01: Name or service not known 3. Ubuntu one file link in thunderbird fails See bug 1054803 Whilst I can see an argument for fixing the bugs in all those other applications, wouldn't it make more sense to just not have mad filenames created in the first place. I propose:- "Screenshot_from_-MM-DD_HH-MM-SS.png" ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-screenshot 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Sun Sep 23 01:15:27 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screenshot/+bug/1054808/+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 521492] Re: [Patch upstream] Dual Monitor wallpaper is not scaling across both monitors, same background is repeated on both monitors instead
It seems gconftool-2 from comment #2 is being deprecated. Here's how to fix this in 13.10: dconf write /org/gnome/desktop/background/picture-options "'spanned'" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/521492 Title: [Patch upstream] Dual Monitor wallpaper is not scaling across both monitors, same background is repeated on both monitors instead Status in GNOME Control Center: Confirmed Status in “gnome-control-center” package in Ubuntu: Triaged Status in “meta-gnome2” package in Ubuntu: Invalid Bug description: On all other Ubuntu/Gnome versions you can use a wallpaper sized for dual-monitor and it will span across both monitors, currently the same wallpaper is being repeated twice, once on each monitor. Appears to be https://bugzilla.gnome.org/show_bug.cgi?id=603551 regarding scaling wallpaper across dual monitors If Nautilus' wallpaper manager is replaced by Compiz's, the wallpaper scales correctly. ProblemType: Bug Architecture: amd64 Date: Sat Feb 13 14:45:06 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113) NonfreeKernelModules: nvidia Package: gnome (not installed) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-13.18-generic SourcePackage: meta-gnome2 Uname: Linux 2.6.32-13-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/521492/+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 771272] Re: ssh-add does not handle ECDSA keys until ssh-agent exports are manually launched
Tested on 13.04, still buggy. Manually running SSH_AUTH_SOCK=/tmp/ssh- phxl1McWvuSj/agent.20832 skips gnome-keyring for ssh-agent actions, and makes ecdsa work again -- but naturally that workaround is hard to do, as the random parts keep changing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/771272 Title: ssh-add does not handle ECDSA keys until ssh-agent exports are manually launched Status in GNOME keyring services: Confirmed Status in “gnome-keyring” package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-keyring I'm not sure I have described it correctly in the summary, but this is what happens: I run ssh-add in a new terminal and enter my passphrase, which is the same for my DSA and ECDSA key: the DSA identity is added, but the ECDSA gets the "Error reading response length from authentication socket. Could not add identity: /home/claudio/.ssh/id_ecdsa" error. I run ssh-agent, copy and paste the output in the terminal and re-run ssh-add. Both identities are correctly added: claudio@Chuck:~$ ssh-add Enter passphrase for /home/claudio/.ssh/id_dsa: Identity added: /home/claudio/.ssh/id_dsa (/home/claudio/.ssh/id_dsa) Error reading response length from authentication socket. Could not add identity: /home/claudio/.ssh/id_ecdsa claudio@Chuck:~$ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-szGWMUbE3916/agent.3916; export SSH_AUTH_SOCK; SSH_AGENT_PID=3917; export SSH_AGENT_PID; echo Agent pid 3917; claudio@Chuck:~$ SSH_AUTH_SOCK=/tmp/ssh-szGWMUbE3916/agent.3916; export SSH_AUTH_SOCK; claudio@Chuck:~$ SSH_AGENT_PID=3917; export SSH_AGENT_PID; claudio@Chuck:~$ echo Agent pid 3917; Agent pid 3917 claudio@Chuck:~$ ssh-add Enter passphrase for /home/claudio/.ssh/id_dsa: Identity added: /home/claudio/.ssh/id_dsa (/home/claudio/.ssh/id_dsa) Identity added: /home/claudio/.ssh/id_ecdsa (/home/claudio/.ssh/id_ecdsa) Here is the content of my ~/.ssh/ claudio@Chuck:~$ ls -l .ssh total 32 -rw-r--r-- 1 claudio claudio 726 2011-04-15 23:34 config -r 1 claudio claudio 751 2011-04-05 10:35 id_dsa -rw-r--r-- 1 claudio claudio 603 2011-04-05 10:34 id_dsa.pub -r 1 claudio claudio 444 2011-04-05 10:29 id_ecdsa -rw-r--r-- 1 claudio claudio 267 2011-04-05 10:23 id_ecdsa.pub -rw--- 1 claudio claudio 6402 2011-04-19 18:04 known_hosts -rw-r--r-- 1 claudio claudio 2760 2011-04-06 17:05 known_hosts.old ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-keyring 2.92.92.is.2.32.1-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Apr 26 16:27:02 2011 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to natty on 2011-04-03 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/771272/+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 1048441] Re: gnome-terminal displays "missing font" glyph very poorly
** Attachment added: "2012-09-09-190613_1198x609_scrot.png" https://bugs.launchpad.net/bugs/1048441/+attachment/3304580/+files/2012-09-09-190613_1198x609_scrot.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/1048441 Title: gnome-terminal displays "missing font" glyph very poorly Status in “gnome-terminal” package in Ubuntu: New Bug description: I was wondering why some of my log lines did not contain a final closing doublequote, if the quoted string contained some funky UTF-8. In fact, they did -- the quote glyph was just drawn in the same space as the "font missing" glyph. Attaching a screenshot to demonstrate. Run python -c "print u'\U0000X <- the X is obscured'" to see for yourself. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.4.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Sun Sep 9 19:06:35 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1048441/+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 1048441] [NEW] gnome-terminal displays "missing font" glyph very poorly
Public bug reported: I was wondering why some of my log lines did not contain a final closing doublequote, if the quoted string contained some funky UTF-8. In fact, they did -- the quote glyph was just drawn in the same space as the "font missing" glyph. Attaching a screenshot to demonstrate. Run python -c "print u'\U0000X <- the X is obscured'" to see for yourself. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.4.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Sun Sep 9 19:06:35 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- 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/1048441 Title: gnome-terminal displays "missing font" glyph very poorly Status in “gnome-terminal” package in Ubuntu: New Bug description: I was wondering why some of my log lines did not contain a final closing doublequote, if the quoted string contained some funky UTF-8. In fact, they did -- the quote glyph was just drawn in the same space as the "font missing" glyph. Attaching a screenshot to demonstrate. Run python -c "print u'\U0000X <- the X is obscured'" to see for yourself. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.4.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Sun Sep 9 19:06:35 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1048441/+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
