[Bug 1726548] Re: Windows resized after resume
I can confirm, that this bug still exists on Ubuntu 20.04. I recently switched to Manjaro (currently 20.1.1) with the same behavior. Set the monitor to power save after 5 minutes. Desktop resolution is 3840x2160 with 200 % scaling. If I come back after some time. I move the mouse and the logon screen appears. I enter my password and I see File Manager (Files, Simple file manager for GNOME) and Firefox are resized. For instance the File Manager just shows the left half of the window, the other half is out of the screen. You can not see the Minimize/Maximize/Close buttons. Firefox looks strange as it is resized by some more factors. Want to contribute as it is pretty reproducible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726548 Title: Windows resized after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1726548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819748] Re: evolution html signature is not working
HTML-Signatures are inserted as plain text in Evolution Mail 3.36.5. 1. Go to Evolution Preferences -> Composer Preferences -> Signatures 2. Create a new signature and use HTML language like: Greetings Jack It could be intended that the text is plain text there, however it is exactly inserted in a new mail. The same applies to adding a HTML signature as a script. ** Changed in: evolution (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819748 Title: evolution html signature is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/819748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 689139] Re: Shotwell doesn't import across symbolic link
Any news? I am on Ubuntu 20.04 with Shotwell 0.30.8-0ubuntu2 and I am unable to add a folder that is a symlink to another folder.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689139 Title: Shotwell doesn't import across symbolic link To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/689139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870758] Re: [nvidia] Display scaling results in a blank screen (power save state)
*** This bug is a duplicate of bug 1869750 *** https://bugs.launchpad.net/bugs/1869750 Scaling to 200% is fine until I decide to use nvidia-driver, instead of X.Org-X-Server. Some reported that the monitor would go to power save state when they applied the scaling setting immediately. I can not confirm that. Scaling with nvidia-driver works until I reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870758 Title: [nvidia] Display scaling results in a blank screen (power save state) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871458] [NEW] No display signal if NVIDIA driver and display scaling is active
Public bug reported: I recently installed Ubuntu 20.04 (20200402) with LVM encryption and automatic logon. So I enter my encryption password and after the motherboards boot logo it will login automatically to desktop. I also chose the additional drivers and so nvidia-driver-440. Everything seems to be OK until I select a scaling above 100% (e.g. 200%) in settings. Next reboot, I enter my encryption password. When the automatic logon process should happen, the monitor turns off and says that no display signal is available. Currently I was able to return to a working setup by pressing CTRL + ALT + F4, login and enter the following commands to remove nvidia-driver and use XORG instead: sudo apt purge nvidia-driver-440 sudo apt autoremove sudo reboot I am pretty sure that the issue will occur again, if I choose NVIDIA driver again. Any thoughts? EDIT: On Ubuntu 19.04 I had a similar bug: If I started my PC and the monitor was not turned on, the monitor reported no signal available after turning it on. I was not able to see the boot-up field to enter my encryption password. Unfortunately I didn't test, if I were able to enter my password and logon anyway. Workaround was to turn the monitor on, before starting the PC. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 7 19:31:50 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP102 [GeForce GTX 1080 Ti] [1458:3762] InstallationDate: Installed on 2020-04-05 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.80 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd04/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7B45 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Description changed: I recently installed Ubuntu 20.04 (20200402) with LVM encryption and automatic logon. So I enter my encryption password and after the motherboards boot logo it will login automatically to desktop. I also chose the additional drivers and so nvidia-driver-440. Everything seems to be OK until I select a scaling above 100% (e.g. 200%) in settings. Next reboot, I enter my encryption password. When the automatic logon process should happen, the monitor turns off and says that no display signal is available. Currently I was able to return to a working setup by pressing CTRL + ALT + F4, login and enter the following commands to remove nvidia-driver and use XORG instead: sudo apt purge nvidia-driver-440 sudo apt autoremove sudo reboot I am pretty sure that the issue will occur again, if I choose NVIDIA driver again. Any thoughts? + + EDIT: On Ubuntu 19.04 I had a similar bug: If I started my PC and the + monitor was not turned on, the monitor reported no signal available + after turning it on. I was not able to see the boot-up field to enter my + encryption password. Un
[Bug 1855555] [NEW] CA0132: Only stereo with Creative Soundblaster ZxR
Public bug reported: I have a 5.1 sound system that is connected via three 3.5 mm audio cables with my Sound Blaster ZxR: Front Left, Center, Front Right, Rear Left, Rear Right, LFE I only get sound from "Front Left"/"Front Right". All other speakers don't make a sound. I tested Ubuntu 19.04, Ubuntu 19.10, Manjaro 18.10, different Kernels and the Sound Blaster Patch from reddit, nothing helped. After all these tests, I started again with a fresh Ubuntu 19.10 installation with this output from "alsa information script": http ://alsa-project.org/db/?f=c9d4adfbc5441c4975b6e6c7a6fb3cbfc201158a Only thing that I did was changing the default audio device to my ZxR. Otherwise my NVIDIA graphics card is selected. I did that with ~/.asoundrc: defaults.ctl.!card "Creative" defaults.pcm.!card "Creative" defaults.timer.!card "Creative" Interestingly I decided to install Windows 10 on my second drive in dual boot mode. I noticed that when I start Windows all speakers are working. Then I reboot to Ubuntu and all speakers are working, too. This effect will vanish if I shut down my PC and start directly to Ubuntu. So something happens on Windows that is kept while rebooting to Ubuntu.. I already reported this issue at bugzilla.kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=205315 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Package changed: flameshot (Ubuntu) => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/185 Title: CA0132: Only stereo with Creative Soundblaster ZxR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
