[Bug 978573] Re: Password Prompt Always Loses Focus Upon Launch
** Description changed: - Each time I launch Synaptic Package Manager in Ubuntu2D, the - Authenticate (password) dialog pops up, and THEN *immediately* loses - focus. + Each time I launch Synaptic Package Manager in Ubuntu, the Authenticate + (password) dialog pops up, and THEN *immediately* loses focus. Someone not recognizing this, might CONTINUE typing their password (inadvertently) into whatever application DOES have focus. Because of this, this could be considered a security related bug. The Authenticate (password) dialog SHOULD pop up and REMAIN focused, until the user finishes entering the password, or until the user intentionally changes the focus in some explicit manner. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: synaptic 0.75.9 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 11 00:05:22 2012 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: synaptic UpgradeStatus: Upgraded to precise on 2012-04-05 (5 days ago) ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/978573 Title: Password Prompt Always Loses Focus Upon Launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/978573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949194] Re: Urgent Security Vulnerability [upgrade-software-version]
See Roland Kaufmann's comment here: https://bugzilla.mozilla.org/show_bug.cgi?id=1739919 ** Bug watch added: Mozilla Bugzilla #1739919 https://bugzilla.mozilla.org/show_bug.cgi?id=1739919 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949194 Title: Urgent Security Vulnerability [upgrade-software-version] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1949194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949194] Re: Urgent Security Vulnerability [upgrade-software-version]
Instead of patching that old version, why can't they just upgrade the package that's in the repository instead? Debian 11 stable has a reputation for running older packages for stability's sake, yet even they are running Firejail 0.9.64.4 ! Recently, I've run into other another issue that would benefit from this upgrade as well: https://askubuntu.com/questions/1373963/firefox-94-broke-my-hot-keys -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949194 Title: Urgent Security Vulnerability [upgrade-software-version] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1949194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949194] Re: Urgent Security Vulnerability [upgrade-software-version]
Thanks for discovering this and patching it. Given that this is a security related bug, I consider its importance High (not medium). But, perhaps others see it different. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949194 Title: Urgent Security Vulnerability [upgrade-software-version] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1949194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949194] Re: Urgent Security Vulnerability [upgrade-software-version]
Well, I guess you would know. As I recall, you're the guy who discovered this. I see you wrote a patch in 1916767; Is that live now? Do I still need to set "overlayfs no"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949194 Title: Urgent Security Vulnerability [upgrade-software-version] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1949194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949194] Re: Urgent Security Vulnerability [upgrade-software-version]
Invalid? Did you follow the link that reveals that version 0.9.62 (the latest available in the repository) has a security vulnerability that wasn't fixed until version 0.9.64.4? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949194 Title: Urgent Security Vulnerability [upgrade-software-version] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1949194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949194] [NEW] Urgent Security Vulnerability [upgrade-software-version]
Public bug reported: Firejail needs to be upgraded as soon as possible: https://github.com/netblue30/firejail#security-vulnerabilities ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firejail 0.9.62-3 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Oct 29 07:21:09 2021 InstallationDate: Installed on 2020-04-26 (551 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firejail UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.firejail.firejail.config: [modified] mtime.conffile..etc.firejail.firejail.config: 2021-10-29T07:20:36.256854 ** Affects: firejail (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949194 Title: Urgent Security Vulnerability [upgrade-software-version] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1949194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947306] Re: Touch Pad Cursor Speed Degreases Dramatically at Desired Resolution
After installing this: sudo apt install kde-plasma-desktop I'm able to enjoy 1920x1080 resolution with fast and smooth touch-pad responsiveness. Also, I didn't have to adjust any settings; it seems optimal by default. This confirms to me that this is a bug GNOME3. Again, in GNOME3, even on the fastest touchpad setting, it takes numerous finger lifts to move across the entire screen at a 1920x1080 resolution. Also, each move of the mouse cursor seems to lag slightly. However, at 1440x900 GNOME3's touchpad speed and responsiveness works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947306 Title: Touch Pad Cursor Speed Degreases Dramatically at Desired Resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1947306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947306] [NEW] Touch Pad Cursor Speed Degreases Dramatically at Desired Resolution
Public bug reported: Although I'm able set resolution to 1920x1080, upon doing so, the touchpad on my Logitech K400 Wireless keyboard/touchpad becomes so slow and laggy, that I cannot enjoy the better looking resolution. I've tried adjusting the touchpad speed to its max setting in GNOME3's settings panel, but this has an almost unnoticeable influence. When I set resolution to 1440x900, the same touchpad is very fast and responsive. The bug is that nothing in the touchpad settings addresses this issue: I either have to endure less than optimal resolution, or endure less than optimal touchpad sensitivity. I'm currently installing this: sudo apt install kde-plasma-desktop I'll report back soon as to notify whether or not this allows me to have decent touchpad sensitivity at a 1920x1080 resolution. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-gnome-desktop (not installed) ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 22:20:01 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-gnome-meta UpgradeStatus: Upgraded to focal on 2021-05-26 (141 days ago) ** Affects: ubuntu-gnome-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947306 Title: Touch Pad Cursor Speed Degreases Dramatically at Desired Resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1947306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
This is still an issue in Ubuntu 20.04. Instead of remembering my preference of wanting to use my television's speakers as output, each time I reboot, the laptop's internal speakers are set to be the output device instead. I'm astonished that after all this time this is still not fixed. How hard can this be to fix? When someone changes the output device, save that setting to a file! When the user reboots, access that file and set it to whatever their saved preference was if that device is currently connected. The status of this is Fix Released? Then why doesn't this still not work in Ubuntu 20.04 LTS. LTS stands for Long Term Support, not Long Tardy Support! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936219] [NEW] 4k Monitor Support is Missing
Public bug reported: Someone needs to buy the developers of LMMS some 4K displays, so that they'll understand how small the user interface is to users with 4K monitors: https://i.imgur.com/orNMXvR.png The UI is too small on 4K monitors. In Kubuntu 20.04, my other applications scale up to accommodate 4K, but for some reason LMMS does not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lmms 1.2.1+dfsg1-4build2 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Jul 14 09:18:17 2021 InstallationDate: Installed on 2020-04-26 (444 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lmms UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lmms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936219 Title: 4k Monitor Support is Missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lmms/+bug/1936219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934684] [NEW] Can't Move, Resize or Maximize Firefox Anymore
Public bug reported: Since the most recent Firefox update, I've lost the ability to control Firefox's window in Kubuntu 20.04. Upon launch, it launches in a un-maximized state where I cannot drag it by its title bar. I have to hold down the alt-key an click the window to move it. Hovering the mouse-cursor on any corner of window doesn't produce any indication that you can resize the Firefox window and "clicking an dragging corners" does nothing (which should resize instead). The maximize button is completely missing from the title bar of Firefox and the superKey+pageUp doesn't maximize the window either. I realize that I'm pointing out multiple things in one post, but I suspect all of these things are stemming from the same source problem, because all these problems started happening after the latest Firefox update in Kubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 89.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lonnie 1629 F pulseaudio /dev/snd/controlC0: lonnie 1629 F pulseaudio BuildID: 20210622155641 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Mon Jul 5 11:28:01 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-04-26 (435 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=89.0.2/20210622155641 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04RSA5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Bonobo WS dmi.board.vendor: System76 dmi.board.version: bonw13 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Bonobo WS dmi.product.sku: Not Applicable dmi.product.version: bonw13 dmi.sys.vendor: System76 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934684 Title: Can't Move, Resize or Maximize Firefox Anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1934684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929871] Re: Export to PDF isn't Working
I made a comment here: https://github.com/LibreCAD/LibreCAD/issues/553#issuecomment-850514373 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929871 Title: Export to PDF isn't Working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librecad/+bug/1929871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929871] [NEW] Export to PDF isn't Working
Public bug reported: LibreCAD was able to import my dxf file fine and it even showed a very nice print preview, but I'm unable to print to PDF. I tried both the "Export to PDF" feature and print to PDF. Both produced a blank pdf document. We also tried installing LibreCAD onto Windows 10, but had the same issue getting dxf files to become PDF. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: librecad 2.1.3-1.2build1 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu May 27 16:24:33 2021 InstallationDate: Installed on 2020-04-26 (396 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: librecad UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: librecad (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: LibreCAD was able to import my dxf file fine and it even showed a very nice print preview, but I'm unable to print to PDF. I tried both the "Export to PDF" feature and print to PDF. Both produced a blank pdf - page. + document. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: librecad 2.1.3-1.2build1 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu May 27 16:24:33 2021 InstallationDate: Installed on 2020-04-26 (396 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: librecad UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: LibreCAD was able to import my dxf file fine and it even showed a very nice print preview, but I'm unable to print to PDF. I tried both the "Export to PDF" feature and print to PDF. Both produced a blank pdf document. + + We also tried installing LibreCAD onto Windows 10, but had the same + issue getting dxf files to become PDF. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: librecad 2.1.3-1.2build1 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu May 27 16:24:33 2021 InstallationDate: Installed on 2020-04-26 (396 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: librecad UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929871 Title: Export to PDF isn't Working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librecad/+bug/1929871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917512] Re: Add support of AVIF images
Upstream? : https://github.com/hellosiyan/Viewnior/issues/95 ** Bug watch added: github.com/hellosiyan/Viewnior/issues #95 https://github.com/hellosiyan/Viewnior/issues/95 ** Summary changed: - Add support of AVIF images + Add support for AVIF images ** Description changed: - Please add support of AVIF image file format: + Please add support for AVIF image file format: - https://en.wikipedia.org/wiki/AV1#AV1_Image_File_Format_(AVIF) - It is inevitable that viewnior will support AVIF, so why not sooner than - later? + The latest Chrome and Firefox 87 support AVIF images, but Viewnior won't + open/display them. + + Compare AVIF images to jpg, and webp: + https://jakearchibald.com/2020/avif-has-landed/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: viewnior 1.6-1build2 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 2 12:59:24 2021 InstallationDate: Installed on 2020-04-26 (310 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: viewnior UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917512 Title: Add support for AVIF images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/viewnior/+bug/1917512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917519] [NEW] Add support for AVIF images
Public bug reported: Please add support of the AVIF image file format: - https://en.wikipedia.org/wiki/AV1#AV1_Image_File_Format_(AVIF) The latest Chrome and Firefox 87 support AVIF images, but Scribus won't accept them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: scribus 1.5.5+dfsg-6build1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 2 13:50:31 2021 InstallationDate: Installed on 2020-04-26 (310 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: scribus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: scribus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917519 Title: Add support for AVIF images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scribus/+bug/1917519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917518] [NEW] Add support for AVIF images
Public bug reported: Please add support of AVIF image file format: - https://en.wikipedia.org/wiki/AV1#AV1_Image_File_Format_(AVIF) The latest Chrome and Firefox 87 support avif images, but gwenview won't open them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gwenview 4:19.12.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 2 13:44:06 2021 InstallationDate: Installed on 2020-04-26 (310 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gwenview UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gwenview (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917518 Title: Add support for AVIF images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwenview/+bug/1917518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917514] Re: Add support for AVIF images
** Summary changed: - Add support of AVIF images + Add support for AVIF images ** Description changed: - Please add support of AVIF image file format: + Please add support for the AVIF image file format: - https://en.wikipedia.org/wiki/AV1#AV1_Image_File_Format_(AVIF) The latest Chrome and Firefox 87 support AVIF images, but GIMP won't open them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gimp 2.10.18-1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 2 13:17:37 2021 InstallationDate: Installed on 2020-04-26 (310 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gimp UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917514 Title: Add support for AVIF images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1917514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917514] [NEW] Add support of AVIF images
Public bug reported: Please add support of AVIF image file format: - https://en.wikipedia.org/wiki/AV1#AV1_Image_File_Format_(AVIF) The latest Chrome and Firefox 87 support AVIF images, but GIMP won't open them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gimp 2.10.18-1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 2 13:17:37 2021 InstallationDate: Installed on 2020-04-26 (310 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gimp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917514 Title: Add support of AVIF images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1917514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917512] [NEW] Add support of AVIF images
Public bug reported: Please add support of AVIF image file format: - https://en.wikipedia.org/wiki/AV1#AV1_Image_File_Format_(AVIF) It is inevitable that viewnior will support AVIF, so why not sooner than later? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: viewnior 1.6-1build2 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 2 12:59:24 2021 InstallationDate: Installed on 2020-04-26 (310 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: viewnior UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: viewnior (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917512 Title: Add support of AVIF images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/viewnior/+bug/1917512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915076] [NEW] Upgrade Fails
Public bug reported: During attempt to upgrade to 20.04, the upgrade process tells me it cannot complete the upgrade. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 15:33:40 2021 InstallationDate: Installed on 2019-03-11 (700 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-02-08 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915076 Title: Upgrade Fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1915076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912190] [NEW] k4dirstat overriding default file manager in Firefox
Public bug reported: In Kubuntu 20.04, if I install k4dirstat, Firefox chooses k4dirstat as the default file manager when I attempt to "Open Containing Folder" for a downloaded file. Here's a screenshot of where I'm clicking in Firefox that launches k4dirstat: https://i.imgur.com/xR6T5ap.png If I uninstall k4dirstat, Firefox will instead open my file manager at the correct location (where the file was downloaded to, instead of launching k4dirstat). How can I have both k4dirstat and a Firefox that acts right when I click "Open Containing Folder"? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: k4dirstat 3.2.0-1build1 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 18 04:39:48 2021 InstallationDate: Installed on 2020-04-26 (267 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: k4dirstat UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: k4dirstat (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: In Kubuntu 20.04, if I install k4dirstat, Firefox chooses k4dirstat as the default file manager when I attempt to "Open Containing Folder" for a downloaded file. Here's a screenshot of where I'm clicking in Firefox that launches k4dirstat: https://i.imgur.com/xR6T5ap.png If I uninstall k4dirstat, Firefox will instead open my file manager at the correct location (where the file was downloaded to, instead of launching k4dirstat). - How can I have both k4dirstat and a Firefox that act right when I click + How can I have both k4dirstat and a Firefox that acts right when I click "Open Containing Folder"? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: k4dirstat 3.2.0-1build1 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 18 04:39:48 2021 InstallationDate: Installed on 2020-04-26 (267 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: k4dirstat UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912190 Title: k4dirstat overriding default file manager in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k4dirstat/+bug/1912190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890791] Re: Dolphin isn't Noticing Newly Created Files
** Tags added: 20.04 dolphin focal kubuntu ** Description changed: Kubuntu 20.04 is a long term support release that currently uses Dolphin 19.12.3. For the last few weeks, Dolphin has not been recognizing newly added files and I have to type ctrl-F5 constantly in order to see what's really in the folder I'm working from. Weirdly, even if I navigate to a folder AFTER a new file was just added to that folder, then too do I have to hit ctrl-F5 to see that recently added file (I wouldn't expect this problem to go to that degree; you'd think that navigating to any folder should always show the latest state of that folder). Previously, Dolphin seemed to maintain almost real-time awareness of the folder I already have opened. For example, If I'd use some other - application to save a file to a folder that I'm already have open in + application to save a file to a folder that I already have open in Dolphin, that newly saved file would pop into the list, sorted an everything (if I recall correctly). I tried to get help with this here: https://askubuntu.com/questions/1264620/ But, no one offered any suggestions. I see you guys have already made later releases of Dolphin, but I really hope that the Kubuntu team will give special attention to Kubuntu 20.04 (since it is a long term support release) and do what it takes to keep Kubuntu 20.04 using a version of Dolphin that works well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890791 Title: Dolphin isn't Noticing Newly Created Files To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/1890791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890791] Re: Dolphin isn't Noticing Newly Created Files
Upstream: https://bugs.kde.org/show_bug.cgi?id=425098 Question: https://askubuntu.com/questions/1264620/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890791 Title: Dolphin isn't Noticing Newly Created Files To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/1890791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890791] [NEW] Dolphin isn't Noticing Newly Created Files
Public bug reported: Kubuntu 20.04 is a long term support release that currently uses Dolphin 19.12.3. For the last few weeks, Dolphin has not been recognizing newly added files and I have to type ctrl-F5 constantly in order to see what's really in the folder I'm working from. Weirdly, even if I navigate to a folder AFTER a new file was just added to that folder, then too do I have to hit ctrl-F5 to see that recently added file (I wouldn't expect this problem to go to that degree; you'd think that navigating to any folder should always show the latest state of that folder). Previously, Dolphin seemed to maintain almost real-time awareness of the folder I already have opened. For example, If I'd use some other application to save a file to a folder that I'm already have open in Dolphin, that newly saved file would pop into the list, sorted an everything (if I recall correctly). I tried to get help with this here: https://askubuntu.com/questions/1264620/ But, no one offered any suggestions. I see you guys have already made later releases of Dolphin, but I really hope that the Kubuntu team will give special attention to Kubuntu 20.04 (since it is a long term support release) and do what it takes to keep Kubuntu 20.04 using a version of Dolphin that works well. ** Affects: dolphin Importance: Unknown Status: Unknown ** Affects: dolphin (Ubuntu) Importance: Undecided Status: New ** Tags: 20.04 dolphin focal kubuntu ** Bug watch added: KDE Bug Tracking System #425098 https://bugs.kde.org/show_bug.cgi?id=425098 ** Also affects: dolphin via https://bugs.kde.org/show_bug.cgi?id=425098 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to dolphin in Ubuntu. https://bugs.launchpad.net/bugs/1890791 Title: Dolphin isn't Noticing Newly Created Files To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/1890791/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1866880] Re: Firefox Speech Synthesis Not Working in Kubuntu
** Description changed:
Modern web browsers, by spec, are supposed to support Speech Synthesis.
Although Firefox does indeed support it, it doesn't work in Kubuntu
- 19.10.
+ 20.04.
On this very page, you should be able to have Firefox read it aloud by
typing shift-ctrl-I and then entering this code-line into the console
(and pressing enter):
speechSynthesis.speak(new
SpeechSynthesisUtterance(document.getElementsByTagName("body")[0].innerText));
Something shorter, that you could type into the console (for testing)
is:
speechSynthesis.speak(new SpeechSynthesisUtterance("testing 1, 2, 3");
You should be able to hear the browser say "testing 1, 2, 3" after doing
- this, but it doesn't working Kubuntu 19.10.
+ this, but it doesn't working Kubuntu 20.04.
- This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu
- 19.10. I'm reporting this in hopes that it gets fixed before Kubuntu
- 20.04.
+ This works in Ubuntu 20.04 and Windows 10, but doesn't work in Kubuntu
+ 20.04. I'm reporting this in hopes that it gets fixed in a manner where
+ all Kubuntu user can enjoy Speech Synthesis by default.
+
+ Currently, to enable Speech Synthesis in Firefox, on Kubuntu 20.04, you
+ have to manually install speech-dispatcher and restart Firefox:
+
+ sudo apt install speech-dispatcher
+
+ The main purpose of this bug is to request that speech-dispatcher be
+ installed by default because Firefox needs it to be complaint with
+ modern web standards.
+
+ Additionally, the Kubuntu team should put this task into their release-
+ checklist, for all future builds of Kubuntu, so that the desktop's
+ speech-dispatcher is always there for the applications that expect its
+ availability.
ProblemType: Bug
- DistroRelease: Ubuntu 19.10
- Package: firefox 73.0.1+build1-0ubuntu0.19.10.1
- ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
- Uname: Linux 5.3.0-40-generic x86_64
+ DistroRelease: Ubuntu 20.04
+ Package: firefox 78.0.2+build2-0ubuntu0.20.04.1
+ ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
+ Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
- ApportVersion: 2.20.11-0ubuntu8.5
+ ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
- AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC1: lonnie 1850 F pulseaudio
- /dev/snd/controlC0: lonnie 1850 F pulseaudio
- BuildID: 20200217142647
+ BuildID: 20200708170202
+ CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: KDE
- Date: Tue Mar 10 13:25:31 2020
+ Date: Sun Jul 26 03:51:21 2020
+ DefaultProfileExtensions: extensions.sqlite corrupt or missing
+ DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
+ DefaultProfileLocales: extensions.sqlite corrupt or missing
+ DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:730
+ DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
- InstallationDate: Installed on 2020-02-03 (36 days ago)
- InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
- NoProfiles: True
+ InstallationDate: Installed on 2020-04-26 (91 days ago)
+ InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
- TERM=xterm-256color
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
+ Profile0Extensions: extensions.sqlite corrupt or missing
+ Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
+ Profile0Locales: extensions.sqlite corrupt or missing
+ Profile0PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:730
+ Profile0PrefSources: prefs.js
+ Profile0Themes: extensions.sqlite corrupt or missing
+ Profiles:
+ Profile1 (Default) - LastVersion=None/None (Out of date)
+ Profile0 - LastVersion=78.0.2/20200708170202 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04RSA5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Bonobo WS
dmi.board.vendor: System76
dmi.board.version: bonw13
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Bonobo WS
dmi.product.sku: Not Applicable
dmi.product.vers
[Bug 1792300] Re: Speech Synthesis Not Working
I was able to get Speech Synthesis working in Kubuntu via Firefox: https://askubuntu.com/a/1262310/256054 However, I still can't get it working in Chromium. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792300 Title: Speech Synthesis Not Working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1792300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866880] Re: Firefox Speech Synthesis Not Working in Kubuntu
@kia-kasurinen Thank you so much! sudo apt-get install speech-dispatcher After the command above, and restarting Firefox, Speech Synthesis is working in Firefox. Please advocate getting this package into the default install of Kubuntu 20.04. The browser will use it if it is there, and other OS desktops make sure a speech-dispatcher is provided. Kubuntu should also. This will help all web developers who use speech synthesis and keep Kubuntu users from scratching their heads on web pages that are supposed to be speaking to them, but are not. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1866880 Title: Firefox Speech Synthesis Not Working in Kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1866880/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1866880] Re: Firefox Speech Synthesis Not Working in Kubuntu
Kubuntu team, Can you please address this issue and add it to a checklist of testing for all future releases? Is there any way you'll be fixing this in Kubuntu 20.04 LTS? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866880 Title: Firefox Speech Synthesis Not Working in Kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/1866880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888984] Re: Please Fix SpeechSynthesis in LTS Releases of Kubuntu and Ubuntu
*** This bug is a duplicate of bug 1866880 *** https://bugs.launchpad.net/bugs/1866880 ** This bug has been marked a duplicate of bug 1866880 Firefox Speech Synthesis Not Working in Kubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888984 Title: Please Fix SpeechSynthesis in LTS Releases of Kubuntu and Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1888984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888984] Re: Please Fix SpeechSynthesis in LTS Releases of Kubuntu and Ubuntu
** Description changed:
- This bug is more the fault of the Kubuntu and Ubuntu than it is Mozilla.
- Firefox supports the web standard for speechSynthesis, but it doesn't
- work in Kubuntu 20.04. This did work in Ubuntu 16.04 and does also
- currently work in Window 10. Like I said, it is web standard that should
- work in every browser.
+ This bug is more the fault of the Kubuntu and Ubuntu teams than it is
+ the fault of Mozilla. Firefox indeed supports the web standard for
+ speechSynthesis, but it doesn't work in Kubuntu 20.04. This does work in
+ Ubuntu 16.04 and in Window 10. Like I said, it is web standard that
+ should work in every browser. This bug is a regression compared to
+ 16.04.
- To reproduce this bug, open up any web page using Firefox and hit ctrl-
+ To reproduce this bug, open up any web page using Firefox and type ctrl-
shift-I (to bring up the console of Firefox). Then, copy and paste the
following text into the console and press enter:
speechSynthesis.speak(new SpeechSynthesisUtterance("Hello, I can
- speak");
+ speak.");
+
+ You should hear your browser say "Hello, I can speak.", but it doesn't
+ work in the latest LTS releases.
This bug means that all web pages, on the internet, that use
speechSynthesis do not function as intended on Kubuntu 20.04 and Ubuntu
20.04.
- If you'd like to hear speechSynthesis in action, go to this web page using
Firefox on Windows 10 or Ubuntu 16.04 (where the instructions will be spoken to
you using Speech Synthesis web standard):
+ If you'd like to hear speechSynthesis in action, go to this web page using
Firefox on Windows 10 or in Ubuntu 16.04 (where the trick's instructions will
be spoken to you via Speech Synthesis):
http://www.lonniebest.com/CardTrick/
- 20.04 is a Long Term Support release. Please fix this!
+ 20.04 is a Long Term Support release. Please fix this, or I'm going to
+ ask for my money back! Wait, scratch that last sentence.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 78.0.2+build2-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BuildID: 20200708170202
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: KDE
Date: Sun Jul 26 03:51:21 2020
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:730
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2020-04-26 (91 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:730
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 (Default) - LastVersion=None/None (Out of date)
Profile0 - LastVersion=78.0.2/20200708170202 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04RSA5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Bonobo WS
dmi.board.vendor: System76
dmi.board.version: bonw13
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Bonobo WS
dmi.product.sku: Not Applicable
dmi.product.version: bonw13
dmi.sys.vendor: System76
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888984
Title:
Please Fix SpeechSynthesis in LTS Releases of Kubuntu and Ubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1888984/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888984] [NEW] Please Fix SpeechSynthesis in LTS Releases of Kubuntu and Ubuntu
Public bug reported:
This bug is more the fault of the Kubuntu and Ubuntu than it is Mozilla.
Firefox supports the web standard for speechSynthesis, but it doesn't
work in Kubuntu 20.04. This did work in Ubuntu 16.04 and does also
currently work in Window 10. Like I said, it is web standard that should
work in every browser.
To reproduce this bug, open up any web page using Firefox and hit ctrl-
shift-I (to bring up the console of Firefox). Then, copy and paste the
following text into the console and press enter:
speechSynthesis.speak(new SpeechSynthesisUtterance("Hello, I can
speak");
This bug means that all web pages, on the internet, that use
speechSynthesis do not function as intended on Kubuntu 20.04 and Ubuntu
20.04.
If you'd like to hear speechSynthesis in action, go to this web page using
Firefox on Windows 10 or Ubuntu 16.04 (where the instructions will be spoken to
you using Speech Synthesis web standard):
http://www.lonniebest.com/CardTrick/
20.04 is a Long Term Support release. Please fix this!
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 78.0.2+build2-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BuildID: 20200708170202
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: KDE
Date: Sun Jul 26 03:51:21 2020
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:730
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2020-04-26 (91 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profile0Extensions: extensions.sqlite corrupt or missing
Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile0Locales: extensions.sqlite corrupt or missing
Profile0PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:730
Profile0PrefSources: prefs.js
Profile0Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 (Default) - LastVersion=None/None (Out of date)
Profile0 - LastVersion=78.0.2/20200708170202 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04RSA5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Bonobo WS
dmi.board.vendor: System76
dmi.board.version: bonw13
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Bonobo WS
dmi.product.sku: Not Applicable
dmi.product.version: bonw13
dmi.sys.vendor: System76
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
** Description changed:
- This bug is more the fault of the Kubuntu and Ubuntu than it is Mozilla.
- Firefox supports the web standard for speechSynthesis, but it doesn't
- work in Kubuntu 20.04. This did work in Ubuntu 16.04 and does also
- currently work in Window 10. Like I said, it is web standard that should
- work in every browser.
+ This bug is more the fault of the Kubuntu and Ubuntu distribution teams
+ than it is fault of Mozilla. Firefox supports the web standard for
+ speechSynthesis, but it doesn't work in Kubuntu 20.04. This did work in
+ Ubuntu 16.04 and does also currently work in Windows 10. Like I said, it
+ is web standard that should work in every browser. It is a big help to
+ the visually impaired.
To reproduce this bug, open up any web page using Firefox and hit ctrl-
shift-I (to bring up the console of Firefox). Then, copy and paste the
following text into the console and press enter:
speechSynthesis.speak(new SpeechSynthesisUtterance("Hello, I can
speak");
This bug means that all web pages, on the internet, that use
- speechSynthesis do not function as intended on Kubuntu 20.04 and Ubuntu
- 20.04.
+ speechSynthesis cannot be properly used Kubuntu 20.04 LTS and Ubuntu
+ 20.04 LTS.
- If you'd like to hear speechSynthesis in action, go to this web page using
Firefox on Windows 10 or Ubuntu 16.04:
+ If you'd like to hear speechSynthesis in action, go to this web
[Bug 1792300] Re: Speech Synthesis Not Working
User activation has been added to my trick for Chromium:
http://www.lonniebest.com/CardTrick/
As Olivier pointed out, the issue remains that speechSynthesis (a web
standard that major browsers support in other operating systems) is not
working Kubuntu 20.04 or Ubuntu 20.04. These are long term support
releases. Where is the support? I reported this two years ago. What
about the visual impaired people that depend on speechSynthesis?
To reproduce this bug, open Chromium on any web page and then hit ctrl-shift-I.
At the console type (or copy/paste):
speechSynthesis.speak(new SpeechSynthesisUtterance("Testing 1 2 3"));
If you do not hear your browser speak "Testing 1 2 3", the bug is not
fixed. Try the same test on Windows 10 to experience speechSynthesis
working as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792300
Title:
Speech Synthesis Not Working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1792300/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175882]
A lot has changed since I originally submitted this bug report. That page no longer contains PNG images, and it seems that LibreOffice Writer doesn't support the new webp standard images that the page contains. Read about webp here: https://en.wikipedia.org/wiki/WebP Additionally, I'm now using Kubuntu 20.04, which is less likely to lock up when a single applications has a problem. I created a png version of the page again, so that I could test this in Kubuntu 20.04. I don't want to post a hyperlink of that page here, because I don't want google to index it. To get to the png version of the page, add "png/" onto the end of this URL: http://www.amorosity.com/SlingBlade/ >From there, you can test this yourself by following steps 2 and 3 given at the top of this report. In Kubuntu 20.04, LibreOffice Writer does a poor job at scaling the png images (that the page contains), but it doesn't crash in Kubuntu 20.04. I can no longer speak for GNOME 3, but you can easily test it yourself from the png version of the page that I made exclusively for this bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175882 Title: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883463] Re: upgrade-software-version to pgadmin4
I also submitted this bug to pgadmin4, in hopes that they may be able to offer some assistance: https://redmine.postgresql.org/issues/5606 ** Bug watch added: redmine.postgresql.org/issues #5606 https://redmine.postgresql.org/issues/5606 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883463 Title: upgrade-software-version to pgadmin4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pgadmin3/+bug/1883463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883463] Re: upgrade-software-version to pgadmin4
Thanks Kai Kasurinen, for associating this bug with its upstream issue at Debian. It seems like they're having an issue with some of the technology that pgadmin4 uses to install its Javascript bundles. pgadmin4 uses yarn to install its javascript bundles and debian already has a program named yarn that is a totally different thing than JS package manager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883463 Title: upgrade-software-version to pgadmin4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pgadmin3/+bug/1883463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883463] [NEW] upgrade-software-version to pgadmin4
Public bug reported: Can someone please get pgadmin4 into the repos? : https://www.pgadmin.org/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pgadmin3 (not installed) ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Jun 14 19:33:31 2020 InstallationDate: Installed on 2020-04-26 (49 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pgadmin3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pgadmin3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883463 Title: upgrade-software-version to pgadmin4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pgadmin3/+bug/1883463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881953] [NEW] Speech API Doesn't Work
Public bug reported:
Modern web browsers, by spec, are supposed to support Speech Synthesis:
https://developer.mozilla.org/en-US/docs/Web/API/Window/speechSynthesis
Although Chromium does indeed support it:
https://caniuse.com/#feat=speech-synthesis
It doesn't work in Ubuntu or Kubuntu 20.04.
On this vary page, you should be able to have Chromium read it aloud by
typing shift-ctrl-I and then entering this code-line into the console
(and pressing enter):
speechSynthesis.speak(new
SpeechSynthesisUtterance(document.getElementsByTagName("body")[0].innerText));
Something shorter, that you could type into the browser-console (for
testing) is:
speechSynthesis.speak(new SpeechSynthesisUtterance("testing 1, 2, 3");
You should be able to hear the browser say "testing 1, 2, 3" after doing
this, but it doesn't working via the Chromium snap package for Ubuntu
20.04.
Another example, is this Card Trick (it should speak to your during the trick):
http://www.lonniebest.com/CardTrick/
(Try it in Windows 10 Chromium to hear what it is supposed to do)
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881953
Title:
Speech API Doesn't Work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1881953/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792300] Re: Speech Synthesis Not Working
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792300 Title: Speech Synthesis Not Working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1792300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866880] Re: Firefox Speech Synthesis Not Working in Kubuntu
Can someone please confirm this bug. It's been 3 months and no one yet has taken the 30 seconds that's required reproduce it and confirm it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866880 Title: Firefox Speech Synthesis Not Working in Kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/1866880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854676] Re: [snap] Web Midi API doesn't work
** Description changed: With aspirations of creating a web based Midi tool, using Ubuntu 19.10, I'm trying to test out the Web Midi API: https://www.w3.org/TR/webmidi/ - Although it is supposed to be supported in Chromium, none of these samples work in Ubuntu 19.10's snap-package installation of Chromium: + It is supposed to be supported in Chromium (and therefore Brave too): + https://caniuse.com/#feat=midi + + Yet, none of these samples work in Ubuntu 19.10's snap-package installations of Chromium or Brave: https://webaudio.github.io/demo-list/ In the meantime, please recommend a work-around of how I can work with the Web Midi API while using Ubuntu Linux as my operating system. ** Description changed: With aspirations of creating a web based Midi tool, using Ubuntu 19.10, I'm trying to test out the Web Midi API: https://www.w3.org/TR/webmidi/ - It is supposed to be supported in Chromium (and therefore Brave too): + The Web Midi API is supposed to be supported in Chromium (and therefore Brave too because Brave is based on Chromium): https://caniuse.com/#feat=midi Yet, none of these samples work in Ubuntu 19.10's snap-package installations of Chromium or Brave: https://webaudio.github.io/demo-list/ In the meantime, please recommend a work-around of how I can work with the Web Midi API while using Ubuntu Linux as my operating system. ** Tags added: focal ** Description changed: - With aspirations of creating a web based Midi tool, using Ubuntu 19.10, I'm trying to test out the Web Midi API: + With aspirations of creating a web based Midi tool, using Ubuntu 20.04 LTS, I'm trying to test out the Web Midi API: https://www.w3.org/TR/webmidi/ The Web Midi API is supposed to be supported in Chromium (and therefore Brave too because Brave is based on Chromium): https://caniuse.com/#feat=midi Yet, none of these samples work in Ubuntu 19.10's snap-package installations of Chromium or Brave: https://webaudio.github.io/demo-list/ In the meantime, please recommend a work-around of how I can work with the Web Midi API while using Ubuntu Linux as my operating system. ** Description changed: With aspirations of creating a web based Midi tool, using Ubuntu 20.04 LTS, I'm trying to test out the Web Midi API: https://www.w3.org/TR/webmidi/ The Web Midi API is supposed to be supported in Chromium (and therefore Brave too because Brave is based on Chromium): https://caniuse.com/#feat=midi - Yet, none of these samples work in Ubuntu 19.10's snap-package installations of Chromium or Brave: + Yet, none of these samples work in Ubuntu 20.04's snap-package installations of Chromium or Brave: https://webaudio.github.io/demo-list/ In the meantime, please recommend a work-around of how I can work with the Web Midi API while using Ubuntu Linux as my operating system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854676 Title: [snap] Web Midi API doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1854676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871030] Re: There's no Option to Disable the Startup of KDEConnect
** Bug watch added: KDE Bug Tracking System #417615 https://bugs.kde.org/show_bug.cgi?id=417615 ** Also affects: kdeconnect-desktop via https://bugs.kde.org/show_bug.cgi?id=417615 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdeconnect in Ubuntu. https://bugs.launchpad.net/bugs/1871030 Title: There's no Option to Disable the Startup of KDEConnect To manage notifications about this bug go to: https://bugs.launchpad.net/kdeconnect-desktop/+bug/1871030/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1871030] [NEW] There's no Option to Disable the Startup of KDEConnect
Public bug reported: In Kubuntu 19.10 (and likely Kubuntu 20.04), why is KDEConnect not listed as a Background Service here?: https://i.stack.imgur.com/FtRl2.jpg Run this command in Kubuntu 19.10: lsof -i You'll see that KDEConnect is listening on UDP 1716 and TCP 1716. I want to prevent KDEConnect from running each time I reboot my computer, because I do not use this service and I do not appreciate unused services that run each time my computer starts (especially ones that hide themselves from official lists like that of Startup Services -- screenshot linked above). What is so special about KDEConnect that it should run all the time, whether you need it or not (and without the GUI-level-ability to toggle it off)? Is this something that can be addressed before Kubuntu 20.04 is released? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: kdeconnect 1.3.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 01:52:24 2020 InstallationDate: Installed on 2020-02-03 (62 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kdeconnect UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kdeconnect (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871030 Title: There's no Option to Disable the Startup of KDEConnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1871030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854676] Re: [snap] Web Midi API doesn't work
I'll need some time. I already have the debian repo version of Chromium installed and I'm concerned that if I also install the snap version of Chromium it might corrupt that setup. I have another computer that I can set up to test this, I'll post back when I do. I'll try to do it tonight. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854676 Title: [snap] Web Midi API doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1854676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864112] Re: Configure Icon Sizes Dialog is Too Small
** Description changed: Kubuntu > System Settings > Icons > Icons > Configure Icon Sizes - The Configure Icon Sizes button should display a dialog that's wide - enough to show all the *full names of the icons* (without ellipses) - you're able to resize, instead of placing priority on being the same - width as the button you've clicked. Screenshot: + The "Configure Icon Sizes" button should display a dialog that's wide + enough to show the *entire name* of the icon-category's name (without + ellipses), instead of placing priority on the dialogs width being the + same width as the button you've clicked to open the dialog. + + Screenshot: https://i.stack.imgur.com/RghPw.png ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: kubuntu-desktop 1.387 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Thu Feb 20 15:13:03 2020 InstallationDate: Installed on 2020-02-03 (17 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: kubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Configure Icon Sizes Dialog is Too Small + "Configure Icon Sizes" Dialog is Too Small ** Description changed: Kubuntu > System Settings > Icons > Icons > Configure Icon Sizes The "Configure Icon Sizes" button should display a dialog that's wide enough to show the *entire name* of the icon-category's name (without ellipses), instead of placing priority on the dialogs width being the same width as the button you've clicked to open the dialog. Screenshot: + https://i.stack.imgur.com/RghPw.png - https://i.stack.imgur.com/RghPw.png + To reproduce/emphasize the problem set your system fonts to a size + larger than default (14pt for example). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: kubuntu-desktop 1.387 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Thu Feb 20 15:13:03 2020 InstallationDate: Installed on 2020-02-03 (17 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864112 Title: "Configure Icon Sizes" Dialog is Too Small To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/1864112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866880] Re: Firefox Speech Synthesis Not Working in Kubuntu
Here's another example that doesn't work in Kubuntu, but should: https://mdn.github.io/web-speech-api/speak-easy-synthesis/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866880 Title: Firefox Speech Synthesis Not Working in Kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/1866880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866880] Re: Firefox Speech Synthesis Not Working in Kubuntu
** Description changed:
Modern web browsers, by spec, are supposed to support Speech Synthesis.
Although Firefox does indeed support it, it doesn't work in Kubuntu
19.10.
On this very page, you should be able to have Firefox read it aloud by
typing shift-ctrl-I and then entering this code-line into the console
(and pressing enter):
speechSynthesis.speak(new
SpeechSynthesisUtterance(document.getElementsByTagName("body")[0].innerText));
-
- Something shorter, that you could type into the console (for testing) is:
+ Something shorter, that you could type into the console (for testing)
+ is:
speechSynthesis.speak(new SpeechSynthesisUtterance("testing 1, 2, 3");
You should be able to hear the browser say "testing 1, 2, 3" after doing
this, but it doesn't working Kubuntu 19.10.
-
- This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu 19.10.
I'm reporting this in hopes that it gets fixed before Kubuntu 20.04.
+ This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu
+ 19.10. I'm reporting this in hopes that it gets fixed before Kubuntu
+ 20.04.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 73.0.1+build1-0ubuntu0.19.10.1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC1: lonnie 1850 F pulseaudio
- /dev/snd/controlC0: lonnie 1850 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: lonnie 1850 F pulseaudio
+ /dev/snd/controlC0: lonnie 1850 F pulseaudio
BuildID: 20200217142647
Channel: Unavailable
CurrentDesktop: KDE
Date: Tue Mar 10 13:25:31 2020
ForcedLayersAccel: False
InstallationDate: Installed on 2020-02-03 (36 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
NoProfiles: True
ProcEnviron:
- TERM=xterm-256color
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04RSA5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Bonobo WS
dmi.board.vendor: System76
dmi.board.version: bonw13
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Bonobo WS
dmi.product.sku: Not Applicable
dmi.product.version: bonw13
dmi.sys.vendor: System76
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866880
Title:
Firefox Speech Synthesis Not Working in Kubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/1866880/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866880] Re: Firefox Speech Synthesis Not Working in Kubuntu
Another example: Here's a card trick I made, where the browser should speak during the trick: http://www.lonniebest.com/CardTrick/ This speaking can be heard in both Firefox and Chrome on Windows 10. It also works in Ubuntu Firefox. However, it does NOT work in Kubuntu 19.10 Firefox (you don't hear anything). Hopefully this will be fixed by Kubuntu 20.04 LTS. ** Also affects: kde-baseapps Importance: Undecided Status: New ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866880 Title: Firefox Speech Synthesis Not Working in Kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/1866880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866880] [NEW] Firefox Speech Synthesis Not Working in Kubuntu
Public bug reported:
Modern web browsers, by spec, are supposed to support Speech Synthesis.
Although Firefox does indeed support it, it doesn't work in Kubuntu
19.10.
On this very page, you should be able to have Firefox read it aloud by
typing shift-ctrl-I and then entering this code-line into the console
(and pressing enter):
speechSynthesis.speak(new
SpeechSynthesisUtterance(document.getElementsByTagName("body")[0].innerText));
Something shorter, that you could type into the console (for testing) is:
speechSynthesis.speak(new SpeechSynthesisUtterance("testing 1, 2, 3");
You should be able to hear the browser say "testing 1, 2, 3" after doing
this, but it doesn't working Kubuntu 19.10.
This works in Ubuntu 19.10 and Windows 10, but doesn't work in Kubuntu 19.10.
I'm reporting this in hopes that it gets fixed before Kubuntu 20.04.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 73.0.1+build1-0ubuntu0.19.10.1
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: lonnie 1850 F pulseaudio
/dev/snd/controlC0: lonnie 1850 F pulseaudio
BuildID: 20200217142647
Channel: Unavailable
CurrentDesktop: KDE
Date: Tue Mar 10 13:25:31 2020
ForcedLayersAccel: False
InstallationDate: Installed on 2020-02-03 (36 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
NoProfiles: True
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04RSA5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Bonobo WS
dmi.board.vendor: System76
dmi.board.version: bonw13
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Bonobo WS
dmi.product.sku: Not Applicable
dmi.product.version: bonw13
dmi.sys.vendor: System76
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866880
Title:
Firefox Speech Synthesis Not Working in Kubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1866880/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075405] Re: Sound Only From Right Speaker after Upgrade
No Marcus. I was just teasing. All is well. Thanks for your concern. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075405 Title: Sound Only From Right Speaker after Upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1075405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075405] Re: Sound Only From Right Speaker after Upgrade
That's ok. I've had 8 years to acclimate myself to right-speaker-only audio. At this point, I wouldn't have it any other way! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075405 Title: Sound Only From Right Speaker after Upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1075405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864851] Re: Adjust On-Screen Font Size using CTRL+MouseWheelScrolling
Upstream Feature Request: https://github.com/mate- desktop/pluma/issues/527 ** Description changed: I'm using Pluma 1.22.2 in Kubuntu 19.10. This is a feature request to provide the ability for font-size adjustment by simply holding down your CTRL key while scrolling the mouse-wheel. I'm not talking about the printed font-size, I'm simply referring to the on-screen font-size. - For example, Kate has this feature and it sure is a quick way of - adjusting the font-size to an exact preference in the fewest number of - steps. It offers real-time feedback as you're adjusting (which is way - better than alternative methods I've seen). + For example, Kate [ https://kate-editor.org/ ] has this feature and it + sure is a quick way of adjusting the font-size to an exact preference in + the fewest number of steps. It offers real-time feedback as you're + adjusting (which is way better than alternative methods I've seen). This feature should offer enough granularity so that you never are in a situation where the available sizes seem either too big or too small, but not so granular that it take several rotations of the scroll-wheel to reach your desired font-size. I realize that Pluma is intended to be a simple text editor, and I do like it for that purpose. Yet, this is the only advanced feature I really wish it had. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pluma 1.22.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Feb 26 07:23:27 2020 InstallationDate: Installed on 2020-02-03 (22 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864851 Title: Adjust On-Screen Font Size using CTRL+MouseWheelScrolling To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1864851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864851] [NEW] Adjust On-Screen Font Size using CTRL+MouseWheelScrolling
Public bug reported: I'm using Pluma 1.22.2 in Kubuntu 19.10. This is a feature request to provide the ability for font-size adjustment by simply holding down your CTRL key while scrolling the mouse-wheel. I'm not talking about the printed font-size, I'm simply referring to the on-screen font-size. For example, Kate [ https://kate-editor.org/ ] has this feature and it sure is a quick way of adjusting the font-size to an exact preference in the fewest number of steps. It offers real-time feedback as you're adjusting (which is way better than alternative methods I've seen). This feature should offer enough granularity so that you never are in a situation where the available sizes seem either too big or too small, but not so granular that it take several rotations of the scroll-wheel to reach your desired font-size. I realize that Pluma is intended to be a simple text editor, and I do like it for that purpose. Yet, this is the only advanced feature I really wish it had. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pluma 1.22.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Feb 26 07:23:27 2020 InstallationDate: Installed on 2020-02-03 (22 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mate-desktop Importance: Unknown Status: Unknown ** Affects: pluma (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Bug watch added: github.com/mate-desktop/pluma/issues #527 https://github.com/mate-desktop/pluma/issues/527 ** Also affects: mate-desktop via https://github.com/mate-desktop/pluma/issues/527 Importance: Unknown Status: Unknown ** Description changed: + I'm using Pluma 1.22.2 in Kubuntu 19.10. + This is a feature request to provide the ability for font-size adjustment by simply holding down your CTRL key while scrolling the mouse-wheel. I'm not talking about the printed font-size, I'm simply referring to the on-screen font-size. For example, Kate has this feature and it sure is a quick way of adjusting the font-size to an exact preference in the fewest number of steps. It offers real-time feedback as you're adjusting (which is way - better any other alternative methods I've seen). + better than alternative methods I've seen). - This feature should over enough granularity so that you never are in a + This feature should offer enough granularity so that you never are in a situation where the available sizes seem either too big or too small, but no so granular that it take several rotations of the scroll-wheel to reach your desired font-size. I realize that Pluma is intended to be a simple text editor, and I do like it for that purpose. Yet, this is the only advanced feature I really wish it had. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pluma 1.22.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Feb 26 07:23:27 2020 InstallationDate: Installed on 2020-02-03 (22 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: I'm using Pluma 1.22.2 in Kubuntu 19.10. This is a feature request to provide the ability for font-size adjustment by simply holding down your CTRL key while scrolling the mouse-wheel. I'm not talking about the printed font-size, I'm simply referring to the on-screen font-size. For example, Kate has this feature and it sure is a quick way of adjusting the font-size to an exact preference in the fewest number of steps. It offers real-time feedback as you're adjusting (which is way better than alternative methods I've seen). This feature should offer enough granularity so that you never are in a situation where the available sizes seem either too big or too small, - but no so granular that it take several rotations of the scroll-wheel to - reach your desired font-size. + but not so granular that it take several rotations of the scroll-wheel + to reach your desired font-size. I realize that Pluma is intended to be a simple text
[Bug 1864540] Re: Auto-Size Left Pane Wider Than Longest Text
Upstream Bug Report: https://bugs.kde.org/show_bug.cgi?id=418151 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864540 Title: Auto-Size Left Pane Wider Than Longest Text To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kinfocenter/+bug/1864540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864540] [NEW] Auto-Size Left Pane Wider Than Longest Text
Public bug reported: When kinfocenter launches, the left page is too narrow to display the entirety of all the phrases listed in its left pane. The user can drag the left pane wider, but the very next time kinfocenter is launched, it resorts back to a left-pane-width that's more narrow than the phrases it contains. Watch this Video: https://www.youtube.com/watch?v=RDNWBFx1NKY Keeping in mind, that KDE users can set their font-sizes to be much larger than the 10pt font you get from a fresh installation of Kubuntu. So, the larger the font-size-setting, the more truncation of letters that result from this left pane being too narrow. Therefore, I propose that each time kinfocenter launches, it should take the user's font-size into consideration, and auto-size the left pane to a size that's wide enough to show all phrases in their entirety. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: kinfocenter 4:5.16.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Feb 24 13:35:31 2020 InstallationDate: Installed on 2020-02-03 (21 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kinfocenter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kinfocenter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Bug watch added: KDE Bug Tracking System #418151 https://bugs.kde.org/show_bug.cgi?id=418151 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864540 Title: Auto-Size Left Pane Wider Than Longest Text To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kinfocenter/+bug/1864540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864112]
Actually, my problem is your lack of empathy regarding the matter. I have tried the desktop scaling at 2X and it worked very poorly compared to doubling the DPI. For example, Flameshot didn't work with the desktop scaling feature enabled, while it works great at a 192 DPI. Also, in my three 4K monitor setup, if I moved my mouse past the bottom edge of the bottom middle monitor, the whole desktop would scroll down as though that desktop had an additional 2160 pixels that shouldn't even be there. So your suggestions offer more bugs than the DPI solution I've discovered. I use to be a fan of desktop scaling, but not now. I'm a fan of increasing DPI. It works better. Try it in a multiple 4K monitors setup like mine. You'll see. The bottom line is, whether you are sympathetic or not, is that the dialog shouldn't place priority on being the exact same width of the button that's clicked. Instead it should accommodate what ever the font- size is (even if the font-size is due to a 192 DPI). I wish you had 3 or 4 4K monitors to deal with. Until then, I don't expect to persuade you much. Believe it or not, I report this stuff to help make KDE better. This is minor issue, but the developers need to take what I'm saying into consideration as they design these GUIs, instead of wasting the available horizontal space to ensure the dialog is not bigger than the button that was clicked to launch the dialog. Anyway, I doubt I've persuaded you, but thanks anyways for at least reading what I've wrote. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864112 Title: Configure Icon Sizes Dialog is Too Small To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/1864112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864112]
Nate, You don't have to increase the DPI in order to reproduce this issue. All that is necessary is to increase the default font-size, as I show here: https://www.youtube.com/watch?v=dxgBJaI5yRQ Hopefully, you agree that people should be able to increase the font- size of their desktop environment and that dialogs should be able to accommodate those larger font-sizes in a reasonable way. To me, ellipsifying should be a last resort way for dealing with larger font- sizes (especially given that there is not tool-tip to even reveal the entirety of what's been ellipsified). Utilizing available screen space should come before ellipsification. Yes, I'm making these words up as I go, but you know what I mean. I'll take your advise on reporting those other issues as well. However, I firmly believe that what I'm reporting here is a legitimate inflexibility, (minor and petty as it seems). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864112 Title: Configure Icon Sizes Dialog is Too Small To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/1864112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864112]
Created attachment 126277 Forced DPI to 192 Hi Nate. Please see the attachment "Forced DPI to 192". This may be necessary to reproduce the issue. I run KDE on 4K monitors and it is necessary to increase DPI to 192 else GTK applications are too small for my eyes to use them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864112 Title: Configure Icon Sizes Dialog is Too Small To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/1864112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864112] Re: Configure Icon Sizes Dialog is Too Small
** Bug watch added: KDE Bug Tracking System #417954 https://bugs.kde.org/show_bug.cgi?id=417954 ** Also affects: kdelibs via https://bugs.kde.org/show_bug.cgi?id=417954 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864112 Title: Configure Icon Sizes Dialog is Too Small To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/1864112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864112] [NEW] Configure Icon Sizes Dialog is Too Small
Public bug reported: Kubuntu > System Settings > Icons > Icons > Configure Icon Sizes The Configure Icon Sizes button should display a dialog that's wide enough to show all the *full names of the icons* (without ellipses) you're able to resize, instead of placing priority on being the same width as the button you've clicked. Screenshot: https://i.stack.imgur.com/RghPw.png ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: kubuntu-desktop 1.387 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Thu Feb 20 15:13:03 2020 InstallationDate: Installed on 2020-02-03 (17 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kdelibs Importance: Unknown Status: Unknown ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages ** Attachment added: "IconSizes.png" https://bugs.launchpad.net/bugs/1864112/+attachment/5329895/+files/IconSizes.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864112 Title: Configure Icon Sizes Dialog is Too Small To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/1864112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862467]
Created attachment 126143 Forced DPI to 192 In order to get GNOME applications to not be too small on my 4K monitors, I had to force DPI to 192, but even before I did that, the font utility still didn't make good use of the available horizontal space. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1862467 Title: Utilize More Horizontal During Font Adjustment To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/1862467/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1175882]
BTW, when I first reported this bug, in 2013, the web page (referenced in step 1) contained only png images. Today, it contains webp images exclusively: http://www.amorosity.com/SlingBlade/ All modern web browsers support webp images: https://developers.google.com/speed/webp However, Libre Office doesn't support webp. Despite this lack of webp support, it is not the cause of the bug being reported here. The bug would still happen even if those images were still PNGs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175882 Title: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175882]
A separate bug, related to webp support, has been submitted here: https://bugs.documentfoundation.org/show_bug.cgi?id=130759 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175882 Title: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175882]
I can still reproduce this on Kubuntu 19.10. Here's a video of me reproducing it: https://youtu.be/EM26C_Q-hKA I was using GNOME when I first reported this bug. KDE is handling this better than GNOME did, but Libre Office Writer still becomes unusable after following the exact steps I outlined above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175882 Title: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016866] Re: Script Engine "Browse" button Crashes AutoKey
Awesome! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016866 Title: Script Engine "Browse" button Crashes AutoKey To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autokey/+bug/1016866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075429] Re: autokey-gtk crashes when clipboard.get_clipboard() is invoked
Fantastic! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075429 Title: autokey-gtk crashes when clipboard.get_clipboard() is invoked To manage notifications about this bug go to: https://bugs.launchpad.net/autokey/+bug/1075429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862526] Re: Detailed Memory Information - Not Honoring System Font-Sizes
Upstream: https://bugs.kde.org/show_bug.cgi?id=417346 ** Bug watch added: KDE Bug Tracking System #417346 https://bugs.kde.org/show_bug.cgi?id=417346 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862526 Title: Detailed Memory Information - Not Honoring System Font-Sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ksysguard/+bug/1862526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862526] [NEW] Detailed Memory Information - Not Honoring System Font-Sizes
Public bug reported: If you right-click on a process in ksysguard, and click then "Detailed Memory Information", the window that pops up contains text that doesn't honor the font-size preferences set via KDE's system settings utility. This accessibility issue is especially pronounced on 4K monitors. Screenshot: http://neartalk.com/ss/ksysguardMemoryDetails.png ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ksysguard 4:5.16.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 9 10:02:59 2020 InstallationDate: Installed on 2020-02-03 (6 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ksysguard UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ksysguard (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862526 Title: Detailed Memory Information - Not Honoring System Font-Sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ksysguard/+bug/1862526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862467] Re: Utilize More Horizontal During Font Adjustment
** Bug watch added: KDE Bug Tracking System #417314 https://bugs.kde.org/show_bug.cgi?id=417314 ** Also affects: kdelibs via https://bugs.kde.org/show_bug.cgi?id=417314 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862467 Title: Utilize More Horizontal During Font Adjustment To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/1862467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862467] [NEW] Utilize More Horizontal During Font Adjustment
Public bug reported: In Kubuntu's system settings, the GUI interface should utilize more of the available horizontal space, so that font-names can be seen in their entirety, while viewing them. Screenshot: http://neartalk.com/ss/useMoreHorizonalSpaceForAdjustFonts.png ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: kubuntu-desktop 1.387 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Sat Feb 8 12:14:30 2020 InstallationDate: Installed on 2020-02-03 (5 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862467 Title: Utilize More Horizontal During Font Adjustment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1862467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861088]
If not by default, add a feature called: "Clone Default Monitor's Panels and Widgets to All Monitors". If you have 3 or 4 monitors, and want to have the same panels and widgets on all monitors, repeating the same task 3 or 4 times, for each panel and widget, begs for automation. At the very least, you should be able to right-click on any panel and clone it and all of its widgets and drag it to the desired screen edge. I wish every KDE developers had about four 4K monitors to set up on each install. At least the guy calling the shots at KDE ought to have this setup (not some guy with one 1080p laptop monitor). Sorry, these are my honest thoughts; repetitive tasks beg for automation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861088 Title: Include Default Panels on All Monitors By Default To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/1861088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861088]
"all that is required is moving the mouse further" - David Edmundson Respectfully, here me out. As a new user of KDE, I have no clue what that means (above). Is there some implicitly hidden gesture that produces the Application Menu on Additional Monitors? If so, why is this gesture not required on the default monitor? That's an inconsistency guaranteed to confuse a new users of KDE (like myself). Closing this ticket on the grounds that "defaults are subjective" ignores the fact that "sensible default increase new user adoption". I'm making the effort to push this point because I've just started using KDE and I want it to become the goto desktop for all types of users. Obviously, I can see that it is the goto desktop for power users, but if you'd give my suggestions deeper consideration KDE will evolve into the desktop that's preferred by power users AND new users. This can be accomplished by making defaults explicit instead of hidden: "Show it until they know it". I donated $20.00 to KDE.org the other day because of the potential I see in KDE. That doesn't make what I'm saying unquestionable, but I want you to know my sincerity. Here's my primary desktop history: Windows 3.1 Windows 98 Window XP GNOME 2 (April 2007 is when I started using Linux exclusively) Unity 7 GNOME 3 KDE Out of all of these GNOME 2 was the easiest to use as a new user, but Unity 7 had the most sensible defaults when it comes to panels in a Multiple Monitors environment: In Unity 7, if you installed that desktop onto a computer having multiple monitors, each additional monitor had all the same panels as the default monitor. In its day, Unity 7 had more users than GNOME and KDE combined. When it came to new user adoption, they were doing something right. Here's why KDE should do this too by default: 1) Concept of "Burden of Configuration". The burden of configuration is best placed on users that already have the knowledge of how to configure KDE. New users benefit from explicit interfaces that show things (on screen) by default. Auto-hide and gesture-driven access to menus are NOT sensible defaults for new users. This is NOT subjective. It is a fact. Once new users know where things are, at that point they can give more priority to saving screen real-estate with auto-hide and learning shortcuts such as mouse gestures and hot-keys. Those things are not intuitive to new users. Until they know it, show it! 2) Concept of "Lowest Number of Steps Required". It requires less steps to remove a panel than it does to 1) Learn what a panel is 2) Learn the KDE names of each type of panel 3) Learn the KDE idiosyncrasies of new panel creation in a multiple monitor setup (see #4 in my original post; its a bug in and of itself). 3) Concept of "Less Steps Drive New User Adoption". In Web Marketing, it is a known fact that you lose sales for each additional step that's required to purchase your product online. Example, if it requires one step maybe 20% of the people that see it will buy it. If it requires 2 steps: only 15% will buy it. 3 steps 7% will buy it. Amazon.com knows this, and that's why they created the feature (one click purchasing). The point is, with each additional set required, you lose people. The same is probably true for New User adoption of a desktop environments. How many people have run into the problem I'm reporting here, and decided to put no effort into trying to change it? How many people evaluate KDE and after not seeing an application menu on an additional monitor, just assume wrongly that KDE is inadequate and quit evaluating it?. How many people get to step 1 (of learning about panels) and then give up. How many people add a panel, and give up because they don't want to take the next step to configure it to their liking. Each additional step a new user has to endure could be the step they give up on. Give the new user everything on all monitors by default and I promise you it will benefit new user adoption. I can't prove it, but I intelligible know it (based on the concepts above). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861088 Title: Include Default Panels on All Monitors By Default To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/1861088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861088] Re: Include Default Panels on All Monitors By Default
** Bug watch added: KDE Bug Tracking System #416852 https://bugs.kde.org/show_bug.cgi?id=416852 ** Also affects: kdelibs via https://bugs.kde.org/show_bug.cgi?id=416852 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1861088 Title: Include Default Panels on All Monitors By Default To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/1861088/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1861088] [NEW] Include Default Panels on All Monitors By Default
Public bug reported: Currently, when you install Kubuntu 19.10 onto a computer that has multiple monitors, KDE only puts panels onto the default monitor and the user has to add panels to all additional monitors. I want to make my case that this should NOT be the default practice. I think all panels, that are visible in a one-monitor setup, should also be on each additional monitor until they are decidedly remove. I'll make my case with the "Application Menu Panel", but I have the same opinion for all other panels. Because KDE doesn't put an Application Menu Panel onto each monitor, the new KDE user will not know how to access an Application's main menu if they have the window open on one of the additional monitors. For new users of KDE, like myself, it is very clear that the burden of customization should be on the advanced user and not the new user. The advanced KDE user will know instantly how to remove an unwanted panel, but the new user is burdened with a task that is way more difficult than removing an unwanted panel: Please let me help you see this from the eyes of a new user who has an application open on one of the additional monitors. 1) First I looked at the top of the application window and didn't see the application's main menu where I expected it to be (either in that window's title bar, or at the top of the entire monitor window). 2) I hit the alt-key (a common MS shortcut), hoping that the Application's main menu was just hidden and that alt would bring it up. 3) I had to do an internet search and learn about panels in KDE and then proceed to create my first panel. 4) When I right-clicked on the additional monitor's desktop and selected Panel > Application Menu, nothing happened on the vary monitor I did this on, instead it added an additional Application Menu panel to the default monitor, and worse: it added it on top of the existing Application Menu that was already on that monitor (making it practically invisible that anything had occurred). Now, I ask you this. Is this the type of user experience that produces new user adoption? Wouldn't it be better to put all the panels, that are on the default monitor, onto each and every additional monitor by default? Put the burden of customization onto the advanced user. After all, the burden of removing a panel is easier that creating and customizing a new one from scratch AND the advance user will already know all about panels. You don't need to put the burden onto the new user who can't access the main menu of an application their using because it is open within and additional monitor. Who on the KDE development team thinks this is an acceptable default behavior (to not make Application Menus of an application accessible until you create and customize a panel onto that monitor)? I love the KDE is so customizable, but you guys need to couple that richness with sensible defaults and this is an area that is not sensible (to the new user)! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: kubuntu-desktop 1.387 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jan 28 03:13:51 2020 InstallationDate: Installed on 2020-01-27 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861088 Title: Include Default Panels on All Monitors By Default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1861088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery
Will that fix change this issue?: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 Other links: - https://askubuntu.com/questions/1187437/override-gnome-3s-slow-screen- lock-recovery - https://www.reddit.com/r/gnome/comments/eocpga/unnecessary_delays_recovering_from_screen_lock/ ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #757 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832812 Title: Locking and unlocking the screen is slow and stuttery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713238] Re: gufw will not open in ubuntu wayland 17.10
Although gufw works in Ubuntu 19.10 by default, I'm not sure that 19.10 uses wayland like (I've read) 20.04 will. Those who confirm this works, really need to make sure you're logged in using Wayland and not X. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713238 Title: gufw will not open in ubuntu wayland 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gui-ufw/+bug/1713238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855913] Re: VirtualBox Unusable in Ubuntu 19.10
https://askubuntu.com/questions/1195232/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855913 Title: VirtualBox Unusable in Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1855913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855913] [NEW] VirtualBox Unusable in Ubuntu 19.10
Public bug reported: Hopefully you are already aware that VirtualBox is practically unusable in Ubuntu 19.10. In Ubuntu 19.04, all my virtual machines worked great, but after upgrading all of them crash so frequently that I cannot use them. I'll try to collected some details to add here, but I'm not putting off reporting this any longer. I had to make this post as a start Surely others have reported this. Can you direct me to a proper work- around that gets virtualbox stable in 19.10? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: virtualbox (not installed) ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 10 12:23:22 2019 InstallationDate: Installed on 2019-10-30 (40 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855913 Title: VirtualBox Unusable in Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1855913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 684977] Re: [needs-packaging] Grub Customizer
That's great! Yeah, I confirm it installs right from the main repositories in Ubuntu 19.10: sudo apt install grub-customizer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/684977 Title: [needs-packaging] Grub Customizer To manage notifications about this bug go to: https://bugs.launchpad.net/grub-customizer/+bug/684977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854676] [NEW] Web Midi API Doesn't Work in Snap-Version of Chromium
Public bug reported: With aspirations of creating a web based Midi tool, using Ubuntu 19.10, I'm trying to test out the Web Midi API: https://www.w3.org/TR/webmidi/ Although it is supposed to be supported in Chromium, none of these samples work in Ubuntu 19.10's snap-package installation of Chromium: https://webaudio.github.io/demo-list/ In the meantime, please recommend a work-around of how I can work with the Web Midi API while using Ubuntu Linux as my operating system. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854676 Title: Web Midi API Doesn't Work in Snap-Version of Chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1854676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
This work-around is working for me: https://askubuntu.com/a/1183074/256054 However, this is only a work-around and the bug remains. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849069] Re: Wrong Clipboard Item Promoted
** Description changed: I don't have the exact steps to reproduce this behavior, but any long- time user of clip-it knows VERY well what I'm about to say it true. Too often, when you select (from clipit) a previously copied item from the list it provides, it promote the wrong item to your computer's clipboard memory (AND NOT THE ITEM YOU SELECTED). I've been putting up with this BUG for years now, I'm finally reporting it and hoping that someone will go into that code and figure out why this annoying behavior it occurring. I'm quite sure you can reproduce this behavior by simply having a 10 - minute session of copying and pasting various text. After you copied 10 - or so items, try to use clip it to bring an item you copied about 5 or - 10 turns back. You find that the wrong item gets put in to clipboard - memory and you'll have to do select from clip-it twice before it - retrieves the item you selected actually selected the first time. + minute session of copying and pasting various text. After you've copied + 10 or so items, try to use clip it to promote (to your clip-board + memory) an item you copied about 5 or 10 turns back". You find that the + wrong item gets put into the clipboard's memory and you'll have to + select it from clip-it twice before it retrieves the actual item you + selected both times. I hope some kind soul combs through the code and figures out why this happens. This is one of those bugs that you just put up with hoping it finally gets fixed, but like I said, I've been enduring this for YEARS, and it never gets fixed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: clipit 1.4.4+git20190202-1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 21 01:48:55 2019 InstallationDate: Installed on 2019-10-19 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: clipit UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849069 Title: Wrong Clipboard Item Promoted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clipit/+bug/1849069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)
I recently submitted a bug about this topic for Ubuntu 19.10: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #757 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774188 Title: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851067] Re: Screen Lock Recovery has Unnecessary Delays
** Description changed: You can turn "Sreen Lock" off using gnome-control-center > Privacy > - Screen Lock : Off. + Screen Lock : Off: - However, this is bad terminology because you screen will still go into - the exact same "Screen Lock" state upon an inactivity timeout, but the - only difference is that you don't have to enter your password to regain - access to the desktop. + https://gitlab.gnome.org/GNOME/gnome-control- + center/uploads/62e176ed49faf1defaf6e4a36ad86f77/ScreenLock.png + + **Side-note:** this is bad terminology because your screen will still go + into the exact same state that "Screen Lock: On" accomplishes (upon an + inactivity timeout), but the only difference is that you won't have to + enter your password to regain access to the desktop. I would have named + this "Require Password Authentication After Inactivity Timeout" (to me + wordy is better than unclear). While this accomplishes "not having to re-enter your password when coming back from an inactivity timeout", I'm very dissatisfied with a - couple of behaviors. + couple of things. 1) After reaching an "inactivity timeout" that "locks" your screen, you cannot unlock your screen by simply moving your mouse; you have to press - enter. I want to be able to accomplish this also by moving my mouse. + the "enter" key. I want to be able to accomplish this also by moving my + mouse. 2) Even if you press the enter key, to come out of "lock mode", it takes too long before you can interact with the applications you had open. I expect this to be instantaneous! If I were coming out of a suspended state, I could understand some delay. However, I'm not coming out of a suspended state, I just coming out of a screen lock. I do not like how this works. The whole purpose of this, as far as I'm concerned, is to increase the lifespan of my display monitors. All I want this to do, when a inactivity timeout occurs, is turn off all my monitor, and the only delay I expect, when coming back to my desktop, is what ever delay my monitor causes; the desktop should be fully available even before my monitor starts to display the desktop again. Having to press Enter and waiting 5 or 10 seconds before I can start working is NOT something that anyone wants. + Also, there should be separate setting for "blank screen x time", and + "monitor power off after x time". + + My ideal settings would to make the screen go black after 5 minutes of + inactively and to turn my monitors completely off after 15 minutes of + inactively, and I'd like to control whether each of these requires + password authentication or not. On the 5 minute one, I personally would + note require a password, but I would require a password after monitor + going off. However, on either of these, I expect the desktop to be fully + functional immediately after coming out of these states. At the very + least please remove these unnecessary delays. + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:58:25 2019 InstallationDate: Installed on 2019-10-30 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Screen Lock Recovery has Unnecessary Delays + Unnecessary Delays Recovering from Screen Lock -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851067 Title: Unnecessary Delays Recovering from Screen Lock To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1851067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851067] Re: Screen Lock Recovery has Unnecessary Delays
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #757 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851067 Title: Unnecessary Delays Recovering from Screen Lock To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1851067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851067] [NEW] Screen Lock Recovery has Unnecessary Delays
Public bug reported: You can turn "Sreen Lock" off using gnome-control-center > Privacy > Screen Lock : Off. However, this is bad terminology because you screen will still go into the exact same "Screen Lock" state upon an inactivity timeout, but the only difference is that you don't have to enter your password to regain access to the desktop. While this accomplishes "not having to re-enter your password when coming back from an inactivity timeout", I'm very dissatisfied with a couple of behaviors. 1) After reaching an "inactivity timeout" that "locks" your screen, you cannot unlock your screen by simply moving your mouse; you have to press enter. I want to be able to accomplish this also by moving my mouse. 2) Even if you press the enter key, to come out of "lock mode", it takes too long before you can interact with the applications you had open. I expect this to be instantaneous! If I were coming out of a suspended state, I could understand some delay. However, I'm not coming out of a suspended state, I just coming out of a screen lock. I do not like how this works. The whole purpose of this, as far as I'm concerned, is to increase the lifespan of my display monitors. All I want this to do, when a inactivity timeout occurs, is turn off all my monitor, and the only delay I expect, when coming back to my desktop, is what ever delay my monitor causes; the desktop should be fully available even before my monitor starts to display the desktop again. Having to press Enter and waiting 5 or 10 seconds before I can start working is NOT something that anyone wants. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:58:25 2019 InstallationDate: Installed on 2019-10-30 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851067 Title: Screen Lock Recovery has Unnecessary Delays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1851067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849992] Re: Phrase-Editor has no typing cursor when using Gnome3 dark themes
A more concise work-around has been updated here: https://askubuntu.com/a/1185312/256054 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849992 Title: Phrase-Editor has no typing cursor when using Gnome3 dark themes To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-tweaks/+bug/1849992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
I confirm that the packages provided by Douglas Kosovic's PPA work successfully: https://github.com/nm-l2tp/NetworkManager-l2tp/issues/112#issuecomment-548593238 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional L2TP VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789715] Re: VLC Won't Play AV1
I wouldn't say he is completely out of luck. The snap package of VLC may play AV1 on Ubuntu 18.04: https://snapcraft.io/vlc It's worth a try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789715 Title: VLC Won't Play AV1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1789715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849992] Re: Phrase-Editor has no typing cursor when using Gnome3 dark themes
Ultimately, this remains a bug, because Autokey-GTK's phrase-editor does
not inherit a dark background from dark themes, yet it does inherit
cursor-color from dark themes.
Compare this to Autokey's script editor, it inherits both background-
color and caret-color from dark themes.
Autokey-GTK's phrase-editor keeps a white background no matter what the
theme says to do. Yet it complies with the caret-color specified by the
themes.
Since the dark theme calls for a white cursor, white on white makes the
caret-cursor invisible.
I was given a work-around here:
https://askubuntu.com/questions/1185289/
The work-around was to change the dark theme's caret color to a color
that would show up on both light and dark backgrounds.
Since I'm using the Yaru-dark theme now, I changed the cursor color to
red by appending the following text to the file /usr/share/themes/Yaru-
dark/gtk-3.20/.gtk-dark.css :
*
{
padding: 0;
-GtkToolButton-icon-spacing: 4;
-GtkTextView-error-underline-color: #cc;
-GtkScrolledWindow-scrollbar-spacing: 0;
-GtkToolItemGroup-expander-size: 11;
-GtkWidget-text-handle-width: 20;
-GtkWidget-text-handle-height: 24;
-GtkDialog-button-spacing: 4;
-GtkDialog-action-area-border: 0;
outline-color: alpha(currentColor,0.3);
outline-style: dashed; outline-offset: -3px;
outline-width: 1px;
-gtk-outline-radius: 3px;
-gtk-secondary-caret-color: #456789;
caret-color: red;
}
The key line above is
caret-color: red;
A similar work-around could be applied to the "Adwaita-dark" theme.
This work-around is not ideal, because all applications have to have
this red caret-color, just so I can get Autokey-gtk to work with a dark
theme.
Perhaps someone can modify the autokey-gtk code so that its phrase-
editor acts like its script-editor with respect to inheriting both
background-color AND caret-color from the GNOME 3 themes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849992
Title:
Phrase-Editor has no typing cursor when using Gnome3 dark themes
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-tweaks/+bug/1849992/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849992] Re: Phrase-Editor has no typing cursor when using Gnome3 dark themes
I'm looking for a work-around here: https://askubuntu.com/questions/1185289/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849992 Title: Phrase-Editor has no typing cursor when using Gnome3 dark themes To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-tweaks/+bug/1849992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849992] Re: Autokey-GTK : Can't see typing cursor when using Gnome-Tweaks dark themes
This is still an issue. There seems to be no issue with the script-editor in autokey; script editors shows a typing cursor as expected while using a dark theme. However, the issue is with the phrase editor; it does NOT show a typing cursor while using a GNOME 3 dark theme. Yesterday, I was mistaken. I edited a script and saw a typing cursor, but I didn't edit any phrases yesterday. Today, as I edit phrases, I confirm that the issue remains. I will edit the issue to reflect this discovery. ** Description changed: - Autokey-gtk's phrase editor (and script editor too) does not show a - typing-cursor when you're running Ubuntu 19.10 with dark themes. + Autokey-gtk's phrase editor does not show a typing-cursor when you're + running Ubuntu 19.10 with a dark theme. The script editor shows a typing + cursor as expected, but you do not see a typing cursor when editing a + "phrase". Steps to reproduce: 1) Launch GNOME-TWEAKs: sudo apt install gnome-tweaks ; gnome-tweaks & 2) Click "Appearance". - 3) Under Themes > Applications, change it to either Adwaita-dark or - Yaru-dark. + 3) Under Themes > Applications, change it to "Adwaita-dark" or any other + dark theme. 4) Launch Autokey-gtk sudo apt install autokey-gtk ; autokey-gtk - 5) In the left pane of Autokey-gtk, select any phrase or script (or - create a new phrase or script) and then left-click your mouse at any - point within the text. + 5) In the left pane of Autokey-gtk, select any phrase (or create a new + phrase) and then left-click your mouse at any point within the text. Expected Result: You should see a typing cursor that allows you to use your arrow keys to navigate to any location within the text shown in the editor. Actual Result: The typing cursor is completely invisible. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: autokey-gtk 0.90.4-1.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 15:28:37 2019 InstallationDate: Installed on 2019-10-19 (7 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: autokey UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Autokey-GTK : Can't see typing cursor when using Gnome-Tweaks dark themes + Phrase-Editor has no typing cursor when using Gnome3 dark themes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849992 Title: Phrase-Editor has no typing cursor when using Gnome3 dark themes To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-tweaks/+bug/1849992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850563] Re: [snap] Google Search via Microphone says No Internet Connection
Interesting. Any work-rounds at the user-level? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850563 Title: [snap] Google Search via Microphone says No Internet Connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849992] Re: Autokey-GTK : Can't see typing cursor when using Gnome-Tweaks dark themes
Today, I can see the cursor again (for the first time since installing Ubuntu 19.10 and using a dark theme). I hope I'm not speaking too soon, but (right at this moment), it is working. I don't expect this to last. If I stop seeing the cursor again, I'll try to think deeply about what changed. One thing that comes to mind, is that today I have a freshly rebooted computer, while often times I "suspend" my computer instead of just turning it off. Maybe the issue occurs after powering up from a suspended state; I've seen other graphical artifacts in the past from doing this. I'll report back soon with a comment to let you know if this lasts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849992 Title: Autokey-GTK : Can't see typing cursor when using Gnome-Tweaks dark themes To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-tweaks/+bug/1849992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850563] [NEW] Google Search via Microphone says No Internet Connection
Public bug reported: In Ubuntu 19.10, I have Chromium installed via this snap package: sudo snap install chromium With a working internet connect, if I attempt to search google, using the microphone-icon (on the right-side of the google search box), it says I do not have an internet connection. Video: https://youtu.be/pNDKydvUL74 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: 19.10 eoan snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850563 Title: Google Search via Microphone says No Internet Connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
The actual programmer of this module says we need to upgrade-software- version. 1) https://gitlab.gnome.org/GNOME/gnome-control-center/issues/746#note_634394 2) https://github.com/nm-l2tp/NetworkManager-l2tp/issues/112#issuecomment-547218557 He believes that this issue is fixed in NetworkManager-l2tp 1.2.12 and later. Who at Ubuntu can accomplish getting this upgraded in 19.10 instead of having to wait for 20.04? Ideally, the upgrade should just be provided via the standard Ubuntu Update GUI or CLI: sudo apt update ; sudo apt upgrade At this point, upstream has already addressed this bug in a later version, and it is now up to Ubuntu to upgrade the package in the repositories. What is the likelihood that this will be upgraded in Upgraded 19.10? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional L2TP VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional L2TP VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849992] Re: Autokey-GTK : Can't see typing cursor when using Gnome-Tweaks dark themes
The reason I've submitted this as an Autokey-GTK bug, is because this behavior doesn't happen in any other application I use upon using dark themes, except autokey-gtk. Any suggestions for a work-around that would still allow me to use a dark theme? I see no configuration to address this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849992 Title: Autokey-GTK : Can't see typing cursor when using Gnome-Tweaks dark themes To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-tweaks/+bug/1849992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
@seb128 : By default, GNOME provides the gnome-control-center for accomplishing this in Ubuntu 19.10. I didn't know I could still use the nm-connection-editor GUI in Ubuntu 19.10. I was simply using what GNOME provided. I'm a big fan of Unity 7, so I'm glad to see that nm-connection-editor GUI again. Thanks. Here are the VPN related packages that I've added to the default Ubuntu 19.10 installation: sudo apt install network-manager-l2tp network-manager-l2tp-gnome strongswan Of these packages, launchpad will not allow specifying these two packages: network-manager-l2tp network-manager-l2tp-gnome I submitted a bug here, but couldn't associate it in the bug header above: https://github.com/nm-l2tp/NetworkManager-l2tp/issues/112 ** Bug watch added: github.com/nm-l2tp/NetworkManager-l2tp/issues #112 https://github.com/nm-l2tp/NetworkManager-l2tp/issues/112 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional L2TP VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
** Also affects: l2tp-ipsec-vpn Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849930 Title: Additional L2TP VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
