[Desktop-packages] [Bug 1825340] Re: Wrong date on multiday created events
** Changed in: gnome-calendar Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1825340 Title: Wrong date on multiday created events Status in GNOME Calendar: Fix Released Status in gnome-calendar package in Ubuntu: Triaged Bug description: Hello, On gnome-calendar (3.32.0), Ubuntu 19.04. 1 - Create or edit an event. 2 - Check the "Whole day" option. (French: "Toute la journée") 3 - Select the duration for 1 day or more. The event will start and end 1 day before the selected begin and the selected end, so you need to create your event one day in the future to place it on the good date. This bug happens both in local and network calendars. (Tested: Local and Nextcloud). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1825340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826400] Re: Event jumps to preceding date after edit
** Changed in: gnome-calendar Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1826400 Title: Event jumps to preceding date after edit Status in GNOME Calendar: Fix Released Status in gnome-calendar package in Ubuntu: In Progress Status in gnome-calendar source package in Disco: In Progress Bug description: [ Description ] Upstream release 3.32.2 NEWS: Major changes in 3.32.2: * Fix timezone handling of all day events (Florian Latifi) Major changes in 3.32.1: * Fix release date field in AppData * Updated translations [ QA ] Test the calendar works. Test that integration with the rest of the system works (which happens via e-d-s). Check that Google account syncing works. You do *not* have to QA the original bug (preserved below), under the terms of the micro release exception: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regression potential ] If this is really bad it could break the calendar application itself completely, but shouldn't break any parts of the wider system since all integration is via other components. [ Original report ] Full-day events jump a date back if edited and saved, even when no information about date or time is changed. Tested in local and Google calendars, happens in both. To reproduce: 1. Create a full-day event (say on May 5) 2. Click on the event to open event editor 3. Keep the date and time unchanged (full day, May 5) 4. Press "Finish" 5. The event is now registered as a full-day event on the previous date, in this case May 4. Tested on several events in different months, the result is always the same. I reproduced the bug in both month and week view. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-calendar 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 14:17:07 2019 InstallationDate: Installed on 2018-05-09 (350 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to disco on 2019-04-03 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1826400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
I followed the instructions but no log file was created. I noticed in the man page for pulse-client.conf it says extra-arguments= Extra arguments to pass to the PulseAudio daemon when autospawning. and in /etc/pulse/client.conf.d I see autospan=no I tried playing sound, running "alsa force-reload" and checking for the log file but nothing seemed to cause that file to be created. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
Then edit /etc/pulse/client.conf, change the line "; extra-arguments = --log-target=syslog" to "extra-arguments = - --log- target=file:/tmp/a.txt". reboot. you will find the /tmp/a.txt, this is the pulseaaudio log, let us try to find some clues from the log. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
The issue persists on 19.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828124] Re: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1828124 Title: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor Status in evolution-data-server: Unknown Status in evolution-data-server package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Install Ubuntu 16.04 LTS 2. Install Evolution 3. Set-up Google account with default settings (this will end with e-mail and calendar) 4. Reboot 5. Open evolution Calendar and/or indicator-datetime 6. Launch `dbus-monitor` Expected results: * Evolution does not show account credentials in plain text in `dbus-monitor` output Actual results: * Evolution shows account credentials in plain text in `dbus-monitor` output: method call time=1557268474.383095 sender=:1.74 -> destination=:1.40 serial=939 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; interface=org.gnome.evolution.dataserver.Source; member=InvokeAuthenticate array [ string "password:myrealpassword" string "ssl-trust:" ] method return time=1557268474.383686 sender=:1.40 -> destination=:1.74 serial=366 reply_serial=939 signal time=1557268474.389206 sender=:1.40 -> destination=(null destination) serial=367 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; interface=org.gnome.evolution.dataserver.Source; member=Authenticate array [ string "password:myrealpassword" string "ssl-trust:" ] signal time=1557268520.956861 sender=:1.40 -> destination=(null destination) serial=408 path=/org/gnome/evolution/dataserver/SourceManager/Source_19; interface=org.gnome.evolution.dataserver.Source; member=Authenticate array [ string "password:myrealpassword" string "ssl-trust:" string "username:real@email" ] signal time=1557268520.960443 sender=:1.40 -> destination=(null destination) serial=409 path=/org/gnome/evolution/dataserver/SourceManager/Source_18; interface=org.gnome.evolution.dataserver.Source; member=Authenticate array [ string "password:myrealpassword" string "ssl-trust:" string "username:real@email" ] signal time=1557268520.964374 sender=:1.40 -> destination=(null destination) serial=410 path=/org/gnome/evolution/dataserver/SourceManager/Source_20; interface=org.gnome.evolution.dataserver.Source; member=Authenticate array [ string "password:myrealpassword" string "ssl-trust:" string "username:real@email" ] - This is huge security flaw. The malicious script can parse `dbus-monitor` output... Not sure about more recent Ubuntu and Evolution versions. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution-data-server-common 3.18.5-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 8 01:40:27 2019 InstallationDate: Installed on 2018-01-04 (488 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1828124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1828536] Re: libreoffice styles
Ubuntu version: 19.04 amd64 I'm actually using .deb package provided by LibreOffice Document Foundation. [image: image.png] Em sex, 10 de mai de 2019 às 09:01, Marcus Tomlinson < marcus.tomlin...@canonical.com> escreveu: > Hi jacinto, please could you provide us with a little more info about > your system, such as: > > * Which version of Ubuntu you're running > * Which version of LibreOffice you have installed (e.g. "Build ID: > libreoffice-6.2.3.2-snap1") > * Which architecture you're running on (i386 / amd64) > > Please also let us know if you're using any LibreOffice extensions that > could be causing the issue. For this, I recommend first disabling all > extensions and seeing if the problem goes away. > > Thank you! > > ** Changed in: libreoffice (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1828536 > > Title: > libreoffice styles > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1828536/+subscriptions > -- -- *Prof. Jacinto José FrancoInformática - IFMT - Campus Barra do GarçasLinux user #459473* ** Attachment added: "image.png" https://bugs.launchpad.net/bugs/1828536/+attachment/5263041/+files/image.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1828536 Title: libreoffice styles Status in libreoffice package in Ubuntu: Incomplete Bug description: Create a page style from scratch in LibreOffice. Write the name --> click on page to setup page and LibreOffice crash. To Work I must write the name and click in Ok --> modify the style and click on page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1828536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828649] [NEW] Wayland freeze
Public bug reported: When I switch to wayland the gnome desktop locks up before I see my desktop. It doesn't lock up when I have my laptop closed and only one display connected. When I connect up the second display, it locks up every time. I tried deleting my monitors.xml file.. that doesn't make any difference. I was able to get it to work by connecting one display via DisplayPort. When I connect the second display, via active HDMI to DisplayPort on dock, it doesn't work if I select Wayland. This wire configuration works fine with Xorg. Additionally, when I lift my laptop screen, one of my monitors goes out and re-enabling it causes another to go off. Linux kernel is not smart enough to drive the 3 displays. I am able to drive two monitors and have my laptop screen open in Windows just fine. Of importance is that my DisplayPort to HDMI adaptor is ACTIVE. If I was to use a PASSIVE adaptor, I cannot drive two external displays and the laptop display. With my laptop screen closed, I was able to drive both displays in Wayland just fine in 18.10 so this is a regression. The GNU/Linux kernel has always (as far as I know) been lacking in smarts to drive all three displays. This work system is has Intel 4000 Integrated video (Lenovo ThinkPad laptop). Main screen is 2560x1600 via DisplayPort to laptop. Secondary screen is 1920x1200 via DisplayPort to laptop dock. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 10 16:55:27 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] InstallationDate: Installed on 2019-03-25 (46 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190325) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=7e84182c-37f4-407a-91ca-1b6bbec80a00 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GCETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCETB2WW(2.72):bd11/15/2018:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 343522U dmi.product.sku: LENOVO_MT_3435 dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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 disco freeze ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1828649 Title: Wayland freeze Status in xorg package in Ubuntu: New Bug description: When I switch to wayland the gnome desktop locks up before I see my desktop. It doesn't lock up when I have my laptop closed and only one display connected. When I connect up the second display, it locks up every time. I tried deleting my monitors.xml file.. that doesn't make any difference. I was able to get it to work by connecting one display via DisplayPort. When I connect the second display, via active HDMI to DisplayPort on dock, it doesn't work if I select Wayland. This wire configuration works fine with Xorg. Additionally, when I lift my laptop screen, one of my monitors goes out and re-enabling it causes another to go off. Linux kernel is not smart enough to drive the 3 displays. I am able to drive two monitors and have my laptop screen open in Windows just fine. Of importance
[Desktop-packages] [Bug 1828642] [NEW] /usr/bin/nautilus:11:nautilus_list_model_get_all_iters_for_file:nautilus_list_model_get_first_iter_for_file:nautilus_list_view_scroll_to_file:list_view_scroll_to
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7.2, the problem page at https://errors.ubuntu.com/problem/b602a0d844bdf5a495f5843d042e2f2b9dbb58d0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic kylin-17.10 xenial yakkety zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1828642 Title: /usr/bin/nautilus:11:nautilus_list_model_get_all_iters_for_file:nautilus_list_model_get_first_iter_for_file:nautilus_list_view_scroll_to_file:list_view_scroll_to_file:view_ended_loading Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7.2, the problem page at https://errors.ubuntu.com/problem/b602a0d844bdf5a495f5843d042e2f2b9dbb58d0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1828642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
same problem here. don't know where this is coming from but it maybe related to this: https://gitlab.gnome.org/GNOME/gvfs/commit/d7e1397854f32e793b4f65d894908d67072dcb3f my system (inxi -Fxz): System:Host: Work Kernel: 4.15.0-48-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Xfce 4.12.3 (Gtk 2.24.31) Distro: Ubuntu 18.04.2 LTS Machine: Device: desktop Mobo: ASRock model: B450M Pro4 serial: UEFI [Legacy]: American Megatrends v: P1.10 date: 06/19/2018 CPU: Quad core AMD Ryzen 5 2400G with Radeon Vega Graphics (-MT-MCP-) arch: Zen rev.0 cache: 2048 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 28746 clock speeds: max: 3600 MHz 1: 2156 MHz 2: 2065 MHz 3: 1736 MHz 4: 1732 MHz 5: 1970 MHz 6: 2145 MHz 7: 3763 MHz 8: 3765 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] bus-ID: 38:00.0 Display Server: X.Org 1.19.6 drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon) Resolution: 1920x1080@59.93hz OpenGL: renderer: AMD RAVEN (DRM 3.23.0, 4.15.0-48-generic, LLVM 7.0.0) version: 4.5 Mesa 18.2.8 Direct Render: Yes Audio: Card-1 Advanced Micro Devices [AMD] Device 15e3 driver: snd_hda_intel bus-ID: 38:00.6 Card-2 Advanced Micro Devices [AMD/ATI] Device 15de driver: snd_hda_intel bus-ID: 38:00.1 Sound: Advanced Linux Sound Architecture v: k4.15.0-48-generic Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: f000 bus-ID: 1f:00.0 IF: enp31s0 state: up speed: 1000 Mbps duplex: full mac: Drives:HDD Total Size: 1000.2GB (20.7% used) ID-1: /dev/nvme0n1 model: Samsung_SSD_970_EVO_500GB size: 500.1GB ID-2: /dev/sda model: WDC_WD5000AAKS size: 500.1GB temp: 43C Partition: ID-1: / size: 458G used: 72G (16%) fs: ext4 dev: /dev/nvme0n1p1 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 57.5C mobo: N/A gpu: 0.0 Fan Speeds (in rpm): cpu: N/A Info: Processes: 384 Uptime: 15 days Memory: 12261.7/15025.5MB Init: systemd runlevel: 5 Gcc sys: 7.4.0 Client: Shell (sudo) inxi: 2.3.56 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1752091 Title: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed Status in gvfs: Fix Released Status in gvfs package in Ubuntu: Confirmed Bug description: I have no idea about the package to blame: gvfs/udev/kernel ? This is now logged: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.35.91-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 27 14:21:10 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1752091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828638] [NEW] Support sane option --scan-area on GUI applications
Public bug reported: Several sane backends provide the option --scan-area to guarantee the scan is correctly aligned, even if the scan area with automatic document feeder (ADF) is right-aligned in contrast to the flatbed of the same device, which is normally left-aligned. Currently SimpleScan and XSane only support options -l -t -x -y, which leads to misalignment of some scanners when using the ADF. As example for this problem see: https://gitlab.com/utsushi/utsushi/issues/68 ** Affects: simple-scan Importance: Undecided Status: New ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Affects: xsane (Ubuntu) Importance: Undecided Status: New ** Also affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Support option --scan-area + Support sane option --scan-area on GUI applications ** Also affects: simple-scan Importance: Undecided Status: New ** Description changed: Several sane backends provide the option --scan-area to guarantee the scan is correctly aligned, even if the scan area with automatic document feeder (ADF) is right-aligned in contrast to the flatbed of the same - device is normally left-aligned. + device, which is normally left-aligned. Currently SimpleScan and XSane only support options -l -t -x -y, which leads to misalignment of some scanners when using the ADF. As example for this problem see: https://gitlab.com/utsushi/utsushi/issues/68 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1828638 Title: Support sane option --scan-area on GUI applications Status in Simple Scan: New Status in simple-scan package in Ubuntu: New Status in xsane package in Ubuntu: New Bug description: Several sane backends provide the option --scan-area to guarantee the scan is correctly aligned, even if the scan area with automatic document feeder (ADF) is right-aligned in contrast to the flatbed of the same device, which is normally left-aligned. Currently SimpleScan and XSane only support options -l -t -x -y, which leads to misalignment of some scanners when using the ADF. As example for this problem see: https://gitlab.com/utsushi/utsushi/issues/68 To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1828638/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
The before file was attached to the last comment. Here's the after file from pactl. ** Attachment added: "postforce" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+attachment/5263010/+files/postforce -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
I rebooted, ran pactl list cards, ran alsa force reload, then re-ran the pactl command. Results was as you predicted. The pactl outputs before and after appear below. Here's the before output: Card #0 Name: alsa_card.pci-_01_00.1 Driver: module-alsa-card.c Owner Module: 5 Properties: alsa.card = "1" alsa.card_name = "HDA NVidia" alsa.long_card_name = "HDA NVidia at 0xfe08 irq 17" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:01:00.1" sysfs.path = "/devices/pci:00/:00:01.0/:01:00.1/sound/card1" device.bus = "pci" device.vendor.id = "10de" device.vendor.name = "NVIDIA Corporation" device.product.id = "0fbc" device.string = "1" device.description = "HDA NVidia" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (sinks: 1, sources: 0, priority: 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (sinks: 1, sources: 0, priority: 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (sinks: 1, sources: 0, priority: 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (sinks: 1, sources: 0, priority: 5700, available: yes) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (sinks: 1, sources: 0, priority: 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (sinks: 1, sources: 0, priority: 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (sinks: 1, sources: 0, priority: 600, available: no) off: Off (sinks: 0, sources: 0, priority: 0, available: yes) Active Profile: off Ports: hdmi-output-0: HDMI / DisplayPort (priority: 5900, latency offset: 0 usec, not available) Properties: device.icon_name = "video-display" Part of profile(s): output:hdmi-stereo, output:hdmi-surround, output:hdmi-surround71 hdmi-output-1: HDMI / DisplayPort 2 (priority: 5800, latency offset: 0 usec, available) Properties: device.icon_name = "video-display" device.product.name = "DELL U2715H " Part of profile(s): output:hdmi-stereo-extra1 hdmi-output-2: HDMI / DisplayPort 3 (priority: 5700, latency offset: 0 usec, not available) Properties: device.icon_name = "video-display" Part of profile(s): output:hdmi-stereo-extra2, output:hdmi-surround-extra2, output:hdmi-surround71-extra2 --- Here is the after output: Card #0 Name: alsa_card.pci-_01_00.1 Driver: module-alsa-card.c Owner Module: 5 Properties: alsa.card = "1" alsa.card_name = "HDA NVidia" alsa.long_card_name = "HDA NVidia at 0xfe08 irq 17" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:01:00.1" sysfs.path = "/devices/pci:00/:00:01.0/:01:00.1/sound/card1" device.bus = "pci" device.vendor.id = "10de" device.vendor.name = "NVIDIA Corporation" device.product.id = "0fbc" device.string = "1" device.description = "HDA NVidia" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (sinks: 1, sources: 0, priority: 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (sinks: 1, sources: 0, priority: 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (sinks: 1, sources: 0, priority: 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (sinks: 1, sources: 0, priority: 5700, available: yes) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (sinks: 1, sources: 0, priority: 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (sinks: 1, sources: 0, priority: 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (sinks: 1, sources: 0, priority: 600, available: no) off:
[Desktop-packages] [Bug 1828358] modified.conffile..etc.apport.crashdb.conf.txt
apport information ** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt" https://bugs.launchpad.net/bugs/1828358/+attachment/5262988/+files/modified.conffile..etc.apport.crashdb.conf.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1828358 Title: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login Status in mutter package in Ubuntu: Incomplete Bug description: Having enabled fractional scaling on X11, I have a lot of issues with returning to a hw-suspended session, re-login screen becomes a black rectangle, and windows are being resized and there are black rectangular artifacts and a lot of weird stuff with resizing going on. Sometimes I am able to reach the login screen, but often I have to killall -HUP gnome-shell from the terminal. I will try to attach X logs etc when this happens again. Which are the most relevant log files to look into? Ubuntu 19.04, gnome-shell 3.32.0, mutter 3.32.0+git20190410-1ubuntu1, NVIDIA 418.56 Screen at 3840x2160 and 175% scaling --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-07-04 (310 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-17 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.apport.crashdb.conf: 2018-07-13T14:12:17.455274 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828358] Re: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login
** Attachment added: "(adding attachments to illustrate)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+attachment/5262990/+files/MVIMG_20190510_225124.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1828358 Title: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login Status in mutter package in Ubuntu: Incomplete Bug description: Having enabled fractional scaling on X11, I have a lot of issues with returning to a hw-suspended session, re-login screen becomes a black rectangle, and windows are being resized and there are black rectangular artifacts and a lot of weird stuff with resizing going on. Sometimes I am able to reach the login screen, but often I have to killall -HUP gnome-shell from the terminal. I will try to attach X logs etc when this happens again. Which are the most relevant log files to look into? Ubuntu 19.04, gnome-shell 3.32.0, mutter 3.32.0+git20190410-1ubuntu1, NVIDIA 418.56 Screen at 3840x2160 and 175% scaling --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-07-04 (310 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-17 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.apport.crashdb.conf: 2018-07-13T14:12:17.455274 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828358] Re: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login
apport information ** Tags added: apport-collected ** Description changed: Having enabled fractional scaling on X11, I have a lot of issues with returning to a hw-suspended session, re-login screen becomes a black rectangle, and windows are being resized and there are black rectangular artifacts and a lot of weird stuff with resizing going on. Sometimes I am able to reach the login screen, but often I have to killall -HUP gnome-shell from the terminal. I will try to attach X logs etc when this happens again. Which are the most relevant log files to look into? Ubuntu 19.04, gnome-shell 3.32.0, mutter 3.32.0+git20190410-1ubuntu1, NVIDIA 418.56 Screen at 3840x2160 and 175% scaling + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2018-07-04 (310 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + NonfreeKernelModules: nvidia_modeset nvidia + Package: mutter 3.32.0+git20190410-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 + Tags: disco + Uname: Linux 5.0.0-13-generic x86_64 + UpgradeStatus: Upgraded to disco on 2019-04-17 (23 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.apport.crashdb.conf: 2018-07-13T14:12:17.455274 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1828358/+attachment/5262985/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1828358 Title: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login Status in mutter package in Ubuntu: Incomplete Bug description: Having enabled fractional scaling on X11, I have a lot of issues with returning to a hw-suspended session, re-login screen becomes a black rectangle, and windows are being resized and there are black rectangular artifacts and a lot of weird stuff with resizing going on. Sometimes I am able to reach the login screen, but often I have to killall -HUP gnome-shell from the terminal. I will try to attach X logs etc when this happens again. Which are the most relevant log files to look into? Ubuntu 19.04, gnome-shell 3.32.0, mutter 3.32.0+git20190410-1ubuntu1, NVIDIA 418.56 Screen at 3840x2160 and 175% scaling --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-07-04 (310 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-17 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.apport.crashdb.conf: 2018-07-13T14:12:17.455274 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828358] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1828358/+attachment/5262987/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1828358 Title: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login Status in mutter package in Ubuntu: Incomplete Bug description: Having enabled fractional scaling on X11, I have a lot of issues with returning to a hw-suspended session, re-login screen becomes a black rectangle, and windows are being resized and there are black rectangular artifacts and a lot of weird stuff with resizing going on. Sometimes I am able to reach the login screen, but often I have to killall -HUP gnome-shell from the terminal. I will try to attach X logs etc when this happens again. Which are the most relevant log files to look into? Ubuntu 19.04, gnome-shell 3.32.0, mutter 3.32.0+git20190410-1ubuntu1, NVIDIA 418.56 Screen at 3840x2160 and 175% scaling --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-07-04 (310 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-17 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.apport.crashdb.conf: 2018-07-13T14:12:17.455274 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828358] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1828358/+attachment/5262986/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1828358 Title: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login Status in mutter package in Ubuntu: Incomplete Bug description: Having enabled fractional scaling on X11, I have a lot of issues with returning to a hw-suspended session, re-login screen becomes a black rectangle, and windows are being resized and there are black rectangular artifacts and a lot of weird stuff with resizing going on. Sometimes I am able to reach the login screen, but often I have to killall -HUP gnome-shell from the terminal. I will try to attach X logs etc when this happens again. Which are the most relevant log files to look into? Ubuntu 19.04, gnome-shell 3.32.0, mutter 3.32.0+git20190410-1ubuntu1, NVIDIA 418.56 Screen at 3840x2160 and 175% scaling --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-07-04 (310 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-17 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.apport.crashdb.conf: 2018-07-13T14:12:17.455274 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828358] Re: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login
** Attachment added: "(adding attachments to illustrate)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+attachment/5262991/+files/VID_20190509_224648.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1828358 Title: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login Status in mutter package in Ubuntu: Incomplete Bug description: Having enabled fractional scaling on X11, I have a lot of issues with returning to a hw-suspended session, re-login screen becomes a black rectangle, and windows are being resized and there are black rectangular artifacts and a lot of weird stuff with resizing going on. Sometimes I am able to reach the login screen, but often I have to killall -HUP gnome-shell from the terminal. I will try to attach X logs etc when this happens again. Which are the most relevant log files to look into? Ubuntu 19.04, gnome-shell 3.32.0, mutter 3.32.0+git20190410-1ubuntu1, NVIDIA 418.56 Screen at 3840x2160 and 175% scaling --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-07-04 (310 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-17 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.apport.crashdb.conf: 2018-07-13T14:12:17.455274 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828358] Re: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login
** Attachment added: "(adding attachments to illustrate)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+attachment/5262989/+files/MVIMG_20190509_110046.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1828358 Title: 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login Status in mutter package in Ubuntu: Incomplete Bug description: Having enabled fractional scaling on X11, I have a lot of issues with returning to a hw-suspended session, re-login screen becomes a black rectangle, and windows are being resized and there are black rectangular artifacts and a lot of weird stuff with resizing going on. Sometimes I am able to reach the login screen, but often I have to killall -HUP gnome-shell from the terminal. I will try to attach X logs etc when this happens again. Which are the most relevant log files to look into? Ubuntu 19.04, gnome-shell 3.32.0, mutter 3.32.0+git20190410-1ubuntu1, NVIDIA 418.56 Screen at 3840x2160 and 175% scaling --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-07-04 (310 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.32.0+git20190410-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-17 (23 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.apport.crashdb.conf: 2018-07-13T14:12:17.455274 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828606] Re: Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes'
Thank you for your bug report, the issue looks like an upsream one though, maybe you could report it to them on https://gitlab.gnome.org/GNOME/gvfs/issues ? ** Package changed: nautilus (Ubuntu) => gvfs (Ubuntu) ** Changed in: gvfs (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828606 Title: Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes' Status in gvfs package in Ubuntu: New Bug description: From Ubuntu 18.04's GUI, if I open the "Files" app and go to "Other Locations", I see my samba/SMB server. If I double click it, it then lists *some* of my shares. Specifically, it lists those where I didn't use Samba's 'access based share enumeration = yes'[1] (which allows some shares to be made completely invisible to some users). Note that Ubuntu has *not* yet asked me to authenticate, so it makes sense that I shouldn't yet be able to see shares I'm not entitled to. The bug is: even after I authenticate (and let it remember my password), then go back to Other Locations>MyServer, it *still* doesn't show the other shares. In fact, I can't find *any* way to see the other shares. Contrast this with macOS Finder. If I navigate to MyServer in the share list, it doesn't show *any* shares until I authenticate, then it shows *all* shares that the user has access to (and none of the shares the user doesn't have access to). Ubuntu could either: - adopt macOS Finder behaviour and get authentication first, or - update the share list after authentication is performed. Its current behaviour makes some shares totally inaccessible (the crux of the bug). I doubt it matters, but my server is: FreeNAS 11.2-U4 (current newest) using ZFS, running samba 4.9.6. Other users on the FreeNAS forum see the same behaviour[2], so it's not particular to my setup. [1] https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html [2] https://www.ixsystems.com/community/threads/accessing-smb-shares-from-ubuntu-18-04-doesnt-show-all-shares-in-gui.75961/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
This bug was fixed in the package kbd - 2.0.4-4ubuntu2 --- kbd (2.0.4-4ubuntu2) eoan; urgency=medium * kbd_mode: Add -f option and don't perform dangerous mode switches without it. In the back-ported fix kbd_mode exits with success, even when the dangerous mode change is skipped, just prints an error, to not break old scripts. (LP: #520546) -- Balint Reczey Thu, 09 May 2019 17:22:51 +0200 ** Changed in: kbd (Ubuntu Eoan) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: Confirmed Status in xorg-server source package in Xenial: Confirmed Status in console-setup source package in Bionic: Fix Released Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Released Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Released Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: Fix Released Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (kbd) [Impact] * kbd_mode -u is documented to break keyboards in modes other than xlate and unicode, while it is still called by some scripts. Those scripts are called transitively by maintainer scripts such as the one already fixed in console-setup. * To avoid accidentally breaking keyboards a -f option is added to force such breaking mode changes. Without -f only the safe mode changes are performed and an error is printed when the requested mode change is not safe. Next upstream version will also exit with error, but the cherry-picked fix makes kbd_mode return success even when the mode switch is not performed to avoid regressions of scripts. [Test case] * Verify that safe mode switches work and dangerous ones are skipped without -f. Please note that the test will temporarily break the system's keyboard and it is recommended to run the test in a VM. rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $? The keyboard is in Unicode (UTF-8) mode 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in xlate (8-bit) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in some unknown mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in raw (scancode) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in raw (scancode) mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 [Regression Potential] * kbd_mode stops performing breaking mode switches and this may make scripts ineffective when trying to perform a breaking change. This is the intention of the change and the emitter error helps in finding the offending script. The following packages found to call kbd_mode directly: console-setup xinit console-cyrillic initramfs-tools dracut console-tools xview ubiquity's embedded console-setup copy console-data vnc4 The console related packages are expected to execute only safe mode changes because they should operate on consoles only and the rest seem to be safe, too. (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system
[Desktop-packages] [Bug 1718719] Re: qemu can't capture keys properly under wayland
Launchpad has imported 9 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=102475. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-08-30T11:42:57+00:00 Sebastien Bacher wrote: The Ubuntu maintainer backported the recent change to add keyboard grabbing to xwayland, with that change the keyboard arrow keys stop working in kvm Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1718719/comments/0 On 2017-08-30T12:40:12+00:00 Olivier Fourdan wrote: Can you please elaborate of what exactly has been backported and the resulting patches? Which Wayland compositor do you use? It's worth noting that the xwayland patches in themselves won't make a difference *unless* the Wayland compositor implements the corresponding protocol, and I am aware of none for now (the patch for mutter is still pending). Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1718719/comments/1 On 2017-08-30T13:36:16+00:00 Sebastien Bacher wrote: The Ubuntu diff is http://launchpadlibrarian.net/334552966/xorg-server_2%3A1.19.3-1ubuntu3_2%3A1.19.3-1ubuntu4.diff.gz it looks like the backported commits are xwayland-pointer-confine.diff +d5e2f271ad93e50 xwayland: Remove two unused proc pointers. +ca17f3e9fd3b59f xwayland: Lock the pointer if it is confined and has no cursor +513e3bd3870fdb8 xwayland: Update root window size when desktop size changes +fafdb0cc9697eb5 xwayland: "Accept" confineTo on InputOnly windows +c217fcb4c4640ff xwayland: Allow pointer warp on root/None window xwayland-add-grab-protocol-support.diff https://cgit.freedesktop.org/xorg/xserver/commit/?id=0a448d133 Ubuntu doesn't have any compositor change, it's standard GNOME 3.24 so there is must be something wrong and it does make a difference without implementing the protocole. Note that reverting 0a448d133 does fix the issue Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1718719/comments/2 On 2017-08-30T14:57:34+00:00 Olivier Fourdan wrote: Tried reproducing the issue with the arrow keys using the current Xwayland from master with mutter/gnome-shell from master, using qemu-kvm with SDL backend (-display sdl) but failedto reproduce, all keys (including the arrow keys) work fine in the guest. Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1718719/comments/3 On 2017-08-31T16:26:13+00:00 Olivier Fourdan wrote: Created attachment 133910 Test patch Can you try the attached patch (this is for testing purpose *only*) and report back if that makes any difference? With this patch, if the compositor has no support for Xwayland keyboard grab protocol as you said you haven't in Ubuntu, Xwayland won't set up its grab handler at all. Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1718719/comments/4 On 2017-08-31T23:04:19+00:00 Sebastien Bacher wrote: the patch doesn't seem to make a difference Reply at: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1718719/comments/5 On 2017-09-01T07:15:06+00:00 Olivier Fourdan wrote: Well, what this patch does is disabling any specific grab handler if the Xwayland grab protocol is not available, by postponing the setup of those handler until Xwayland can bind to the relevant interface as advertised by the compositor. If the compositor doesn't support the Xwayland grab protocol, then all those routines are not "enabled" in Xwayland, I don't see how they could break anything if not used... Unfortunately, we cannot tell whether or not the compositor supports the Xwayland grab protocol using something like weston-info because, for security reasons, the compositor will (should) only advertiset he given protocl to Xwayland alone and hide it to any other client. So, if that patch makes no difference, it means that: - The Wayland compositor claim to support Xwayland grab protocol but is buggy and doesn't send all key events as expected - Or the problem is completely unrelated to this patch. So next step for you is to: - Check the actual patches applied to mutter in Ubuntu - Check what happens at the protocol level To do so, yo can use the envvar WAYLAND_DEBUG prior to start gnome-shell (which will spawn Xwayland) so that we can tell what globals are listed in the wl_registry and see if "zwp_xwayland_keyboard_grab_manager_v1" is one of them. e.g.,
[Desktop-packages] [Bug 1828613] [NEW] See - [Bug 1828569] [NEW] Popping sound when audio driver engaged - [, Realtek ALC889, Green Line Out, Rear] Playback problem
Public bug reported: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1828613 Title: See - [Bug 1828569] [NEW] Popping sound when audio driver engaged - [, Realtek ALC889, Green Line Out, Rear] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I had logged bug 1828569 and then ran this test to provide the driver/hardware info. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sidboswell 1591 F pulseaudio /dev/snd/controlC2: sidboswell 1591 F pulseaudio /dev/snd/controlC0: sidboswell 1591 F pulseaudio /dev/snd/controlC3: sidboswell 1591 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 10 12:03:10 2019 InstallationDate: Installed on 2019-04-20 (19 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, Realtek ALC889, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.name: EVGA P55 3X SLI E658 dmi.board.vendor: EVGA dmi.board.version: Ibex Peak dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/23/2010:svn:pn:pvr:rvnEVGA:rnEVGAP553XSLIE658:rvrIbexPeak:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828569] Re: Popping sound when audio driver engaged
** Tags added: disco ** Package changed: ubuntu => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1828569 Title: Popping sound when audio driver engaged Status in pulseaudio package in Ubuntu: New Bug description: Fresh install of Disco over the weekend on new hard drive. Any time a sound plays, whether it's from a browser (both Firefox and Chromium), Slack, video or MP3 file, sound in VirtualBox OS, etc. Any sound, even an alert sound or even just opening an app that may make a sound (e.g. opening a browser page that may have alerts or sounds (like a game) makes the same popping sound just when browsing to that page). It's preceded by a pop or a click from the speakers, a fast pop-pop sound. When said audio is finished, about 25% of the time there is another audible pop or click. I have 18.04.x LTS on another hard drive and when I boot to that instance I do not have the pop sound. I believe it's probably driver related, but I'm not sure where to look. Fresh disco install, have performed apt updates, and rebooted several times. Has persisted for several weeks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1828569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828569] [NEW] Popping sound when audio driver engaged
You have been subscribed to a public bug: Fresh install of Disco over the weekend on new hard drive. Any time a sound plays, whether it's from a browser (both Firefox and Chromium), Slack, video or MP3 file, sound in VirtualBox OS, etc. Any sound, even an alert sound or even just opening an app that may make a sound (e.g. opening a browser page that may have alerts or sounds (like a game) makes the same popping sound just when browsing to that page). It's preceded by a pop or a click from the speakers, a fast pop-pop sound. When said audio is finished, about 25% of the time there is another audible pop or click. I have 18.04.x LTS on another hard drive and when I boot to that instance I do not have the pop sound. I believe it's probably driver related, but I'm not sure where to look. Fresh disco install, have performed apt updates, and rebooted several times. Has persisted for several weeks. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment disco -- Popping sound when audio driver engaged https://bugs.launchpad.net/bugs/1828569 You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741027] Re: Screen sharing panels abort using an non-existent vino gsettings key
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1741027 Title: Screen sharing panels abort using an non-existent vino gsettings key Status in unity-control-center package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in vino package in Ubuntu: Invalid Bug description: [FFE] This happens because Gnome removed that particular gsettings key. The removal did not happen with the ui removal but rather much later than that. That is why it doesn't work with the latest version of vino. As of now If users try to open the new sharing panel, unity-control- center will crash. This sort behavior is not desired on LTS release (18.04). The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-control-center. This problem was most recently seen with package version 15.04.0+17.10.20171225-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/be6d095e2145d77c79a6e47e17c94dfe70bcaa0a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Specifically, the error report "Settings schema 'org.gnome.Vino' does not contain a key named 'enabled' " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828606] Re: Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes'
OK, I used "ubuntu-bug -w" and the package seems to be "nautilus 1:3.26.4-0~ubuntu18.04.4" ** Package changed: ubuntu => nautilus (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1828606 Title: Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes' Status in nautilus package in Ubuntu: New Bug description: From Ubuntu 18.04's GUI, if I open the "Files" app and go to "Other Locations", I see my samba/SMB server. If I double click it, it then lists *some* of my shares. Specifically, it lists those where I didn't use Samba's 'access based share enumeration = yes'[1] (which allows some shares to be made completely invisible to some users). Note that Ubuntu has *not* yet asked me to authenticate, so it makes sense that I shouldn't yet be able to see shares I'm not entitled to. The bug is: even after I authenticate (and let it remember my password), then go back to Other Locations>MyServer, it *still* doesn't show the other shares. In fact, I can't find *any* way to see the other shares. Contrast this with macOS Finder. If I navigate to MyServer in the share list, it doesn't show *any* shares until I authenticate, then it shows *all* shares that the user has access to (and none of the shares the user doesn't have access to). Ubuntu could either: - adopt macOS Finder behaviour and get authentication first, or - update the share list after authentication is performed. Its current behaviour makes some shares totally inaccessible (the crux of the bug). I doubt it matters, but my server is: FreeNAS 11.2-U4 (current newest) using ZFS, running samba 4.9.6. Other users on the FreeNAS forum see the same behaviour[2], so it's not particular to my setup. [1] https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html [2] https://www.ixsystems.com/community/threads/accessing-smb-shares-from-ubuntu-18-04-doesnt-show-all-shares-in-gui.75961/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1828606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828606] [NEW] Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes'
You have been subscribed to a public bug: >From Ubuntu 18.04's GUI, if I open the "Files" app and go to "Other Locations", I see my samba/SMB server. If I double click it, it then lists *some* of my shares. Specifically, it lists those where I didn't use Samba's 'access based share enumeration = yes'[1] (which allows some shares to be made completely invisible to some users). Note that Ubuntu has *not* yet asked me to authenticate, so it makes sense that I shouldn't yet be able to see shares I'm not entitled to. The bug is: even after I authenticate (and let it remember my password), then go back to Other Locations>MyServer, it *still* doesn't show the other shares. In fact, I can't find *any* way to see the other shares. Contrast this with macOS Finder. If I navigate to MyServer in the share list, it doesn't show *any* shares until I authenticate, then it shows *all* shares that the user has access to (and none of the shares the user doesn't have access to). Ubuntu could either: - adopt macOS Finder behaviour and get authentication first, or - update the share list after authentication is performed. Its current behaviour makes some shares totally inaccessible (the crux of the bug). I doubt it matters, but my server is: FreeNAS 11.2-U4 (current newest) using ZFS, running samba 4.9.6. Other users on the FreeNAS forum see the same behaviour[2], so it's not particular to my setup. [1] https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html [2] https://www.ixsystems.com/community/threads/accessing-smb-shares-from-ubuntu-18-04-doesnt-show-all-shares-in-gui.75961/ ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes' https://bugs.launchpad.net/bugs/1828606 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
It goes back to xenial. I think I found the cause on systemd, will test a fix and report back soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udisks2 package in Ubuntu: New Status in linux source package in Bionic: New Status in systemd source package in Bionic: New Status in udisks2 source package in Bionic: New Status in linux source package in Disco: New Status in systemd source package in Disco: New Status in udisks2 source package in Disco: New Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: New Status in udisks2 source package in Eoan: New Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827365] Re: ibus-setup info message contains non-human readable symbols
This bug was fixed in the package ibus - 1.5.19-1ubuntu4 --- ibus (1.5.19-1ubuntu4) eoan; urgency=medium * debian/patches/ubuntu-title-update.patch: - remove that distro patch changing the "do you want to start ibus" dialog. It's not needed/useful under Ubuntu/GNOME session since ibus is required and autostarted there. The instructions were also outdated and incorrect for GNOME and the string used was not correctly escaped and showing buggy (lp: #1827365) -- Sebastien Bacher Fri, 10 May 2019 15:28:50 +0200 ** Changed in: ibus (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1827365 Title: ibus-setup info message contains non-human readable symbols Status in ibus package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed 2. Launch `ibus-setup` 3. Confirm starting the daemon 4. See informational message (see screenshot) Expected results: * the message contains human-readable symbols Actual results: * the message contains strange - symbols ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: MATE Date: Thu May 2 14:30:43 2019 InstallationDate: Installed on 2018-04-26 (370 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1827365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826400] Re: Event jumps to preceding date after edit
Thanks for the report. This is fixed in 3.32.2. I've uploaded that to Debian. I'll sync it to eoan when it becomes available, and will upload to the queue for disco now. There will be another message here when it's accepted. ** Description changed: + [ Description ] + + Upstream release 3.32.2 + + NEWS: + + Major changes in 3.32.2: + * Fix timezone handling of all day events (Florian Latifi) + + Major changes in 3.32.1: + * Fix release date field in AppData + * Updated translations + + [ QA ] + + Test the calendar works. Test that integration with the rest of the + system works (which happens via e-d-s). Check that Google account + syncing works. + + You do *not* have to QA the original bug (preserved below), under the + terms of the micro release exception: + + https://wiki.ubuntu.com/StableReleaseUpdates/GNOME + + [ Regression potential ] + + If this is really bad it could break the calendar application itself + completely, but shouldn't break any parts of the wider system since all + integration is via other components. + + [ Original report ] + Full-day events jump a date back if edited and saved, even when no information about date or time is changed. Tested in local and Google calendars, happens in both. To reproduce: 1. Create a full-day event (say on May 5) 2. Click on the event to open event editor 3. Keep the date and time unchanged (full day, May 5) 4. Press "Finish" 5. The event is now registered as a full-day event on the previous date, in this case May 4. Tested on several events in different months, the result is always the same. I reproduced the bug in both month and week view. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-calendar 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 14:17:07 2019 InstallationDate: Installed on 2018-05-09 (350 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to disco on 2019-04-03 (21 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1826400 Title: Event jumps to preceding date after edit Status in GNOME Calendar: New Status in gnome-calendar package in Ubuntu: In Progress Status in gnome-calendar source package in Disco: In Progress Bug description: [ Description ] Upstream release 3.32.2 NEWS: Major changes in 3.32.2: * Fix timezone handling of all day events (Florian Latifi) Major changes in 3.32.1: * Fix release date field in AppData * Updated translations [ QA ] Test the calendar works. Test that integration with the rest of the system works (which happens via e-d-s). Check that Google account syncing works. You do *not* have to QA the original bug (preserved below), under the terms of the micro release exception: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regression potential ] If this is really bad it could break the calendar application itself completely, but shouldn't break any parts of the wider system since all integration is via other components. [ Original report ] Full-day events jump a date back if edited and saved, even when no information about date or time is changed. Tested in local and Google calendars, happens in both. To reproduce: 1. Create a full-day event (say on May 5) 2. Click on the event to open event editor 3. Keep the date and time unchanged (full day, May 5) 4. Press "Finish" 5. The event is now registered as a full-day event on the previous date, in this case May 4. Tested on several events in different months, the result is always the same. I reproduced the bug in both month and week view. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-calendar 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 14:17:07 2019 InstallationDate: Installed on 2018-05-09 (350 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to disco on 2019-04-03 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1826400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826400] Re: Event jumps to preceding date after edit
** Also affects: gnome-calendar (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: gnome-calendar (Ubuntu Disco) Status: New => In Progress ** Changed in: gnome-calendar (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: gnome-calendar (Ubuntu Disco) Importance: Medium => High ** Changed in: gnome-calendar (Ubuntu Disco) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gnome-calendar (Ubuntu) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: gnome-calendar (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1826400 Title: Event jumps to preceding date after edit Status in GNOME Calendar: New Status in gnome-calendar package in Ubuntu: In Progress Status in gnome-calendar source package in Disco: In Progress Bug description: [ Description ] Upstream release 3.32.2 NEWS: Major changes in 3.32.2: * Fix timezone handling of all day events (Florian Latifi) Major changes in 3.32.1: * Fix release date field in AppData * Updated translations [ QA ] Test the calendar works. Test that integration with the rest of the system works (which happens via e-d-s). Check that Google account syncing works. You do *not* have to QA the original bug (preserved below), under the terms of the micro release exception: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regression potential ] If this is really bad it could break the calendar application itself completely, but shouldn't break any parts of the wider system since all integration is via other components. [ Original report ] Full-day events jump a date back if edited and saved, even when no information about date or time is changed. Tested in local and Google calendars, happens in both. To reproduce: 1. Create a full-day event (say on May 5) 2. Click on the event to open event editor 3. Keep the date and time unchanged (full day, May 5) 4. Press "Finish" 5. The event is now registered as a full-day event on the previous date, in this case May 4. Tested on several events in different months, the result is always the same. I reproduced the bug in both month and week view. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-calendar 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 14:17:07 2019 InstallationDate: Installed on 2018-05-09 (350 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to disco on 2019-04-03 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1826400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796777] Re: Download folder settings are inconsistent between create and move
** Changed in: thunderbird
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1796777
Title:
Download folder settings are inconsistent between create and move
Status in Mozilla Thunderbird:
Confirmed
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
When "message synchronizing" is set to download messages from an IMAP
account, a newly created folder under the inbox is automatically set
to download messages as well, but when that folder is then moved
(using the mouse) under some other folder, the "download" check box on
the panel "Items for offline use" is cleared.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: thunderbird 1:52.9.1+build3-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: humphrey 2434 F pulseaudio
/dev/snd/controlC1: humphrey 2434 F pulseaudio
BuildID: 20180710085647
Channel: Unavailable
CurrentDesktop: Unity
Date: Tue Oct 9 11:41:44 2018
ExecutablePath: /usr/lib/thunderbird/thunderbird
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2017-12-13 (299 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
IpRoute:
default via 192.168.1.1 dev enp4s0 proto static metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.101
metric 100
IwConfig:
lono wireless extensions.
enp4s0no wireless extensions.
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-3f3dab64-e8aa-4350-afd1-b05560180506
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources:
prefs.js
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
Profiles: Profile0 (Default) - LastVersion=52.9.1/20180710085647 (In use)
RfKill:
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to xenial on 2018-08-28 (41 days ago)
dmi.bios.date: 06/22/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0N185P
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.3.0:bd06/22/2010:svnDellInc.:pnVostro420Series:pvr:rvnDellInc.:rn0N185P:rvrA02:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 420 Series
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1796777/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828581] Re: /usr/bin/gnome-calendar:11:gtk_image_reset:gtk_image_clear:update_weather:update_no_events_page:gcal_year_view_component_removed
** Changed in: gnome-calendar Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1828581 Title: /usr/bin/gnome- calendar:11:gtk_image_reset:gtk_image_clear:update_weather:update_no_events_page:gcal_year_view_component_removed Status in GNOME Calendar: New Status in gnome-calendar package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-calendar. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/c13a94eea4826eb85fc9ea3d284eaa906e646c07 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1828581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637988] Re: Enable the nfs backend
(removed the cosmic-proposed one as well now) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1637988 Title: Enable the nfs backend Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Fix Committed Status in gvfs source package in Cosmic: Fix Committed Bug description: * Impact The gio/nautilus nfs:// locations handling is missing * Test case Try to connect to/browse a nfs server from nautilus by using a nfs:// location * Regression potential It's a new backend being enabled, it shouldn't have an impact on the existing ones Note that the backend relies on libnfs which got promoted in disco and would need to be promoted in cosmic/bionic as well then To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1637988/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735071] Re: Ctrl + F search disengages immediately after CTRL + F pressed
It was fixed on https://gitlab.gnome.org/GNOME/gnome- software/commit/62153c4a ** Changed in: gnome-software (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gnome-software (Ubuntu) Assignee: Andrea Azzarone (azzar1) => Robert Ancell (robert-ancell) ** Description changed: + * Impact + ctrl-F doesn't open the search widget + + * Test case + - open gnome-software + - hit ctrl-F + -> the search widget should display + + * Regression potential + The change is in the event handler for the specific keybinding so it shouldn't have any side effect if that feature is working + + -- + I press Ctrl + F to open up the search bar to search but I find that immediately after I press Ctrl + F, the bar closes and resets to its original state. I can visibly see the bar show up as well as it closing immediately. I have tested this functionality in the gnome-software- center from other distributions and the master branch and this works. I think this is a theme issue. I am using the default Ubuntu theme by the way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 20:28:44 2017 InstallationDate: Installed on 2017-07-20 (131 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2017-11-23 (6 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1735071 Title: Ctrl + F search disengages immediately after CTRL + F pressed Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Fix Committed Bug description: * Impact ctrl-F doesn't open the search widget * Test case - open gnome-software - hit ctrl-F -> the search widget should display * Regression potential The change is in the event handler for the specific keybinding so it shouldn't have any side effect if that feature is working -- I press Ctrl + F to open up the search bar to search but I find that immediately after I press Ctrl + F, the bar closes and resets to its original state. I can visibly see the bar show up as well as it closing immediately. I have tested this functionality in the gnome- software-center from other distributions and the master branch and this works. I think this is a theme issue. I am using the default Ubuntu theme by the way. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 20:28:44 2017 InstallationDate: Installed on 2017-07-20 (131 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2017-11-23 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1735071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme
Hmm. Personally I prefer Colibre as I find it to be the most professional icon theme for LibreOffice. But if the Yaru team feels that Breeze fits Yaru better, then go for it. And please test the themes with the shiny new tabbed layout interface because that will be the one people will switch to over time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1827948 Title: Use libreoffice-style-breeze as the default icon theme Status in libreoffice package in Ubuntu: New Bug description: The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. So do the breeze icons for libreoffice. All in all does the breeze icon set for libre office fit very good to the look of the Yaru icons. https://i.imgur.com/tgioycv.png https://i.imgur.com/WwKvjMh.png Thus I would suggest to use it as the default icon set in Ubuntu to guarantee a consistent look and feel across the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1827948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828454] Re: i18n: Wrong french translation of "Mbits/s" as "Mo/s"
** Changed in: ubuntu-translations Status: New => Fix Committed ** Changed in: language-pack-gnome-fr (Ubuntu) Status: New => Fix Committed ** Changed in: network-manager (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1828454 Title: i18n: Wrong french translation of "Mbits/s" as "Mo/s" Status in Ubuntu Translations: Fix Committed Status in language-pack-gnome-fr package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Fix Committed Bug description: When running "nmcli device wifi", the list of avalaible SSID appears with their rate. In english (LANG=C), the rate unit is "Mbit/s". In french (LANG=fr_FR.UTF-8), it has been translated to "Mo/s", which means "MBytes/s"! Assuming the original (english) unit is correct, then it should stay "Mbit/s" in french. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1828454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828454] Re: i18n: Wrong french translation of "Mbits/s" as "Mo/s"
** Changed in: ubuntu-translations Assignee: (unassigned) => Ubuntu French Translators (ubuntu-l10n-fr) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1828454 Title: i18n: Wrong french translation of "Mbits/s" as "Mo/s" Status in Ubuntu Translations: Fix Committed Status in language-pack-gnome-fr package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Fix Committed Bug description: When running "nmcli device wifi", the list of avalaible SSID appears with their rate. In english (LANG=C), the rate unit is "Mbit/s". In french (LANG=fr_FR.UTF-8), it has been translated to "Mo/s", which means "MBytes/s"! Assuming the original (english) unit is correct, then it should stay "Mbit/s" in french. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1828454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827365] Re: ibus-setup info message contains non-human readable symbols
** Changed in: ibus (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1827365 Title: ibus-setup info message contains non-human readable symbols Status in ibus package in Ubuntu: Fix Committed Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed 2. Launch `ibus-setup` 3. Confirm starting the daemon 4. See informational message (see screenshot) Expected results: * the message contains human-readable symbols Actual results: * the message contains strange - symbols ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: MATE Date: Thu May 2 14:30:43 2019 InstallationDate: Installed on 2018-04-26 (370 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1827365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 942856] Re: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication
Resetting verification status to verification-done as the re-upload is a
trivial fix of the autopkg test which does not change anything in the
functionality of the package itself.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/942856
Title:
NetworkManager does not support AES-encrypted private keys for WPA
802.1x authentication
Status in NetworkManager:
Confirmed
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Bionic:
Fix Committed
Bug description:
* Impact
Selecting AES-{192,256}-CBC keys to connect isn't working
* Test case
1. Start with a working (cleartext or DES-3) private key/cert for a network.
Set up a connection and verify that everything works.
2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in
working-key.pem -out aes-key.pem -aes256" (the output should have a line
starting with "DEK-Info: AES-256-CBC,")
3. Delete the settings for the test network and attempt to reconnect using
the new key.
That should work
* Regression potential
That's new code for an extra type of keys, it shouldn't impact
existing options
--
NetworkManager does not appear to support private keys encrypted with
AES. At the very least, it will not validate such a key in nm-util
when setting up a WPA 802.1x TLS wifi connection.
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/942856/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809132] Re: Updated bionic to the current 1.10 stable version
Resetting verification status to verification-done as the re-upload is a trivial fix of the autopkg test which does not change anything in the functionality of the package itself. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1809132 Title: Updated bionic to the current 1.10 stable version Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: * Impact The updates in the stable serie include several fixes for misbehaviour, segfaults and security issues, those are the sort of improvements that should be in the LTS The detail of the changes can be seen in the NEWS entry https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS * Test case There is no specific test case for the update, the changelog includes some specific bugs which have their own test case, otherwise it's important to get testing/feedback from users on desktop & server, using IPv4, IPv6, VPN, wifi, eth connections, etc. * Regression potential The update is non trivial, there are several changes are IPv6 and DNS (especially in the context of VPNs) handling so it would be good to give those extra testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1809132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828581] Re: /usr/bin/gnome-calendar:11:gtk_image_reset:gtk_image_clear:update_weather:update_no_events_page:gcal_year_view_component_removed
** Changed in: gnome-calendar (Ubuntu) Importance: Undecided => High ** Changed in: gnome-calendar (Ubuntu) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/issues #299 https://gitlab.gnome.org/GNOME/gnome-calendar/issues/299 ** Also affects: gnome-calendar via https://gitlab.gnome.org/GNOME/gnome-calendar/issues/299 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1828581 Title: /usr/bin/gnome- calendar:11:gtk_image_reset:gtk_image_clear:update_weather:update_no_events_page:gcal_year_view_component_removed Status in GNOME Calendar: Unknown Status in gnome-calendar package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-calendar. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/c13a94eea4826eb85fc9ea3d284eaa906e646c07 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1828581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828581] [NEW] /usr/bin/gnome-calendar:11:gtk_image_reset:gtk_image_clear:update_weather:update_no_events_page:gcal_year_view_component_removed
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-calendar. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/c13a94eea4826eb85fc9ea3d284eaa906e646c07 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-calendar Importance: Unknown Status: Unknown ** Affects: gnome-calendar (Ubuntu) Importance: High Status: Triaged ** Tags: bionic cosmic disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1828581 Title: /usr/bin/gnome- calendar:11:gtk_image_reset:gtk_image_clear:update_weather:update_no_events_page:gcal_year_view_component_removed Status in GNOME Calendar: Unknown Status in gnome-calendar package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-calendar. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/c13a94eea4826eb85fc9ea3d284eaa906e646c07 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1828581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828577] Re: /usr/bin/gnome-calendar:11:__GI_____strtol_l_internal:__strtol:atoi:get_place_type_from_attributes:_geocode_create_place_from_attributes
** Package changed: gnome-calendar (Ubuntu) => geocode-glib (Ubuntu) ** Changed in: geocode-glib (Ubuntu) Importance: Undecided => High ** Changed in: geocode-glib (Ubuntu) Status: New => Fix Released ** Description changed: + * Impact + gnome-calendar segfaults on some weather configurations + + * Test case + Configure "Düsseldorf" as a weather location in gnome-calendar, it should indicate the info and not segfault + + * Regression potential + Check that location informations are still correctly handled in GNOME (location detection, automatic timezone, screen color shift) + + --- + The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-calendar. This problem was most recently seen with package version 3.30.0-1, the problem page at https://errors.ubuntu.com/problem/8c3d1fdecb57bc5894fdf7e312e42ed1d46f7932 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Description changed: * Impact gnome-calendar segfaults on some weather configurations * Test case Configure "Düsseldorf" as a weather location in gnome-calendar, it should indicate the info and not segfault + + The errors.u.c reports should also stop with that version * Regression potential Check that location informations are still correctly handled in GNOME (location detection, automatic timezone, screen color shift) --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-calendar. This problem was most recently seen with package version 3.30.0-1, the problem page at https://errors.ubuntu.com/problem/8c3d1fdecb57bc5894fdf7e312e42ed1d46f7932 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geocode-glib in Ubuntu. https://bugs.launchpad.net/bugs/1828577 Title: /usr/bin/gnome- calendar:11:__GI_strtol_l_internal:__strtol:atoi:get_place_type_from_attributes:_geocode_create_place_from_attributes Status in geocode-glib package in Ubuntu: Fix Released Bug description: * Impact gnome-calendar segfaults on some weather configurations * Test case Configure "Düsseldorf" as a weather location in gnome-calendar, it should indicate the info and not segfault The errors.u.c reports should also stop with that version * Regression potential Check that location informations are still correctly handled in GNOME (location detection, automatic timezone, screen color shift) --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-calendar. This problem was most recently seen with package version 3.30.0-1, the problem page at https://errors.ubuntu.com/problem/8c3d1fdecb57bc5894fdf7e312e42ed1d46f7932 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geocode-glib/+bug/1828577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828577] [NEW] /usr/bin/gnome-calendar:11:__GI_____strtol_l_internal:__strtol:atoi:get_place_type_from_attributes:_geocode_create_place_from_attributes
Public bug reported: * Impact gnome-calendar segfaults on some weather configurations * Test case Configure "Düsseldorf" as a weather location in gnome-calendar, it should indicate the info and not segfault The errors.u.c reports should also stop with that version * Regression potential Check that location informations are still correctly handled in GNOME (location detection, automatic timezone, screen color shift) --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-calendar. This problem was most recently seen with package version 3.30.0-1, the problem page at https://errors.ubuntu.com/problem/8c3d1fdecb57bc5894fdf7e312e42ed1d46f7932 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: geocode-glib (Ubuntu) Importance: High Status: Fix Released ** Tags: bionic cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1828577 Title: /usr/bin/gnome- calendar:11:__GI_strtol_l_internal:__strtol:atoi:get_place_type_from_attributes:_geocode_create_place_from_attributes Status in geocode-glib package in Ubuntu: Fix Released Bug description: * Impact gnome-calendar segfaults on some weather configurations * Test case Configure "Düsseldorf" as a weather location in gnome-calendar, it should indicate the info and not segfault The errors.u.c reports should also stop with that version * Regression potential Check that location informations are still correctly handled in GNOME (location detection, automatic timezone, screen color shift) --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-calendar. This problem was most recently seen with package version 3.30.0-1, the problem page at https://errors.ubuntu.com/problem/8c3d1fdecb57bc5894fdf7e312e42ed1d46f7932 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geocode-glib/+bug/1828577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
The autopkg test failure is now fixed in the network-manager SRU 1.10.14-0ubuntu2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Committed Status in libqmi source package in Bionic: Fix Committed Status in modemmanager source package in Bionic: Fix Committed Status in libmbim source package in Disco: Fix Released Status in libqmi source package in Disco: Fix Released Status in modemmanager source package in Disco: Fix Released Status in libmbim source package in Eoan: Fix Released Status in libqmi source package in Eoan: Fix Released Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
** Description changed: + (kbd) + [Impact] + + * kbd_mode -u is documented to break keyboards in modes other than xlate and unicode, while it is still called by some scripts. Those scripts are called transitively by maintainer scripts such as the one already fixed in console-setup. + * To avoid accidentally breaking keyboards a -f option is added to force such breaking mode changes. Without -f only the safe mode changes are performed and an error is printed when the requested mode change is not safe. Next upstream version will also exit with error, but the cherry-picked fix makes kbd_mode return success even when the mode switch is not performed to avoid regressions of scripts. + + [Test case] + + * Verify that safe mode switches work and dangerous ones are skipped + without -f. Please note that the test will temporarily break the + system's keyboard and it is recommended to run the test in a VM. + + rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $? + The keyboard is in Unicode (UTF-8) mode + 0 + rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? + 0 + rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? + 0 + rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 + The keyboard is in xlate (8-bit) mode + rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $? + 0 + rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 + The keyboard is in Unicode (UTF-8) mode + rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? + The keyboard is in some unknown mode + Changing to the requested mode may make your keyboard unusable, please use -f to force the change. + 0 + rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $? + 0 + rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 + The keyboard is in Unicode (UTF-8) mode + rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0 + rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 + The keyboard is in raw (scancode) mode + rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? + The keyboard is in raw (scancode) mode + Changing to the requested mode may make your keyboard unusable, please use -f to force the change. + 0 + + [Regression Potential] + + * kbd_mode stops performing breaking mode switches and this may make + scripts ineffective when trying to perform a breaking change. This is + the intention of the change and the emitter error helps in finding the + offending script. + + The following packages found to call kbd_mode directly: + console-setup + xinit + console-cyrillic + initramfs-tools + dracut + console-tools + xview + ubiquity's embedded console-setup copy + console-data + vnc4 + + The console related packages are expected to execute only safe mode + changes because they should operate on consoles only and the rest seem + to be safe, too. + (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ -On Xenial X runs on VT7 thus the graphical environment is not affected in the default configuration, but the keyboard-configuration postinst maintaner script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode to observe the change: -$ sudo kbd_mode -s -C /dev/tty1 -$ sudo kbd_mode -C /dev/tty1 -The keyboard is in raw (scancode) mode + On Xenial X runs on VT7 thus the graphical environment is not affected in the default configuration, but the keyboard-configuration postinst maintaner script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode to observe the change: + $ sudo kbd_mode -s -C /dev/tty1 + $ sudo kbd_mode -C /dev/tty1 + The keyboard is in raw (scancode) mode * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same (on Xenial check VT1: sudo kbd_mode -C /dev/tty1): $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in
[Desktop-packages] [Bug 1588397] Re: package gir1.2-geocodeglib-1.0 3.16.2-1 failed to install/upgrade: unable to make backup symlink for './usr/share/doc/gir1.2-geocodeglib-1.0/NEWS.gz': No such file
** Changed in: geocode-glib (Ubuntu) Importance: Undecided => Low ** Changed in: geocode-glib (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geocode-glib in Ubuntu. https://bugs.launchpad.net/bugs/1588397 Title: package gir1.2-geocodeglib-1.0 3.16.2-1 failed to install/upgrade: unable to make backup symlink for './usr/share/doc/gir1.2-geocodeglib-1.0/NEWS.gz': No such file or directory Status in geocode-glib package in Ubuntu: Invalid Bug description: Hello I encountered this at upgrade from 15.10 to 16.04. I wasn`t able to fix this by re-installing it later. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gir1.2-geocodeglib-1.0 3.16.2-1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Jun 2 13:00:22 2016 DuplicateSignature: package:gir1.2-geocodeglib-1.0:3.16.2-1 Unpacking gir1.2-geocodeglib-1.0:amd64 (3.18.2-1) over (3.16.2-1) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-geocodeglib-1.0_3.18.2-1_amd64.deb (--unpack): unable to make backup symlink for './usr/share/doc/gir1.2-geocodeglib-1.0/NEWS.gz': No such file or directory ErrorMessage: unable to make backup symlink for './usr/share/doc/gir1.2-geocodeglib-1.0/NEWS.gz': No such file or directory InstallationDate: Installed on 2016-02-27 (95 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: geocode-glib Title: package gir1.2-geocodeglib-1.0 3.16.2-1 failed to install/upgrade: unable to make backup symlink for './usr/share/doc/gir1.2-geocodeglib-1.0/NEWS.gz': No such file or directory UpgradeStatus: Upgraded to xenial on 2016-06-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geocode-glib/+bug/1588397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823630] Re: ibus ftbfs in cosmic (s390x only)
The current version builds fine ** Changed in: ibus (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1823630 Title: ibus ftbfs in cosmic (s390x only) Status in ibus package in Ubuntu: Fix Released Bug description: https://launchpadlibrarian.net/418305550/buildlog_ubuntu-cosmic- s390x.ibus_1.5.19-1ubuntu1_BUILDING.txt.gz this is different than the ftbfs in disco (LP: #1823423): gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src -I../../src -include ../../config.h -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -DG_LOG_DOMAIN=\"IBUS\" -DBINDIR=\"/usr/bin\" -DPKGDATADIR=\"/usr/share/ibus\" -DIBUS_DISABLE_DEPRECATED -Wno-unused-variable -Wno-unused-but-set-variable -Wno-unused-function -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -c -o keybindingmanager.o keybindingmanager.c gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src -I../../src -include ../../config.h -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/s390x-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -DG_LOG_DOMAIN=\"IBUS\" -DBINDIR=\"/usr/bin\" -DPKGDATADIR=\"/usr/share/ibus\" -DIBUS_DISABLE_DEPRECATED -Wno-unused-variable -Wno-unused-but-set-variable -Wno-unused-function -pthread -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -c -o panel.o panel.c In file included from ../../src/ibusobject.h:41, from ../../src/ibus.h:31, from panel.c:30: ../../src/ibusdebug.h:49:31: warning: ISO C does not permit named variadic macros [-Wvariadic-macros] #define ibus_warning(msg, args...) \ ^~~ In file included from ../../src/ibusobject.h:41, from ../../src/ibus.h:31, from keybindingmanager.c:19: ../../src/ibusdebug.h:49:31: warning: ISO C does not permit named variadic macros [-Wvariadic-macros] #define ibus_warning(msg, args...) \ ^~~ keybindingmanager.c: In function ‘_vala_XIGrabModifiers_array_free’: keybindingmanager.c:812:6: warning: statement with no effect [-Wunused-value] ([i]); ~^~ keybindingmanager.c: In function ‘keybinding_manager_grab_keycode’: keybindingmanager.c:1039:4: warning: statement with no effect [-Wunused-value] (); ~^~~~ keybindingmanager.c: At top level: keybindingmanager.c:1460:1: warning: data definition has no type or storage class ing_manager_type_id__volatile; ^ keybindingmanager.c:1460:1: warning: type defaults to ‘int’ in declaration of ‘ing_manager_type_id__volatile’ [-Wimplicit-int] keybindingmanager.c:1461:1: error: expected identifier or ‘(’ before ‘}’ token } ^ panel.c: In function ‘panel_init_status_icon’: panel.c:1796:2: warning: ‘gtk_status_icon_new’ is deprecated [-Wdeprecated-declarations] _tmp0_ = gtk_status_icon_new (); ^~ In file included from /usr/include/gtk-3.0/gtk/gtk.h:275,
[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
Precise is EOL ** Changed in: unity (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Invalid Status in gnome-screensaver package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Status in gnome-screensaver source package in Precise: Won't Fix Status in unity source package in Precise: Won't Fix Status in gnome-screensaver source package in Xenial: Triaged Status in unity source package in Xenial: Triaged Status in xorg-server package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828454] Re: i18n: Wrong french translation of "Mbits/s" as "Mo/s"
The issue is upstream as well https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/master/po/fr.po It should be reported on https://gitlab.freedesktop.org/NetworkManager/NetworkManager either as an issue reports or with a merge proposal for code change ** Also affects: language-pack-gnome-fr (Ubuntu) Importance: Undecided Status: New ** Changed in: language-pack-gnome-fr (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1828454 Title: i18n: Wrong french translation of "Mbits/s" as "Mo/s" Status in Ubuntu Translations: New Status in language-pack-gnome-fr package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: When running "nmcli device wifi", the list of avalaible SSID appears with their rate. In english (LANG=C), the rate unit is "Mbit/s". In french (LANG=fr_FR.UTF-8), it has been translated to "Mo/s", which means "MBytes/s"! Assuming the original (english) unit is correct, then it should stay "Mbit/s" in french. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1828454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
Precise is EOL ** Changed in: gnome-screensaver (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Invalid Status in gnome-screensaver package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Status in gnome-screensaver source package in Precise: Won't Fix Status in unity source package in Precise: Won't Fix Status in gnome-screensaver source package in Xenial: Triaged Status in unity source package in Xenial: Triaged Status in xorg-server package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 942856] Re: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication
Hello Walter, or anyone else affected,
Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.14-0ubuntu2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/942856
Title:
NetworkManager does not support AES-encrypted private keys for WPA
802.1x authentication
Status in NetworkManager:
Confirmed
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Bionic:
Fix Committed
Bug description:
* Impact
Selecting AES-{192,256}-CBC keys to connect isn't working
* Test case
1. Start with a working (cleartext or DES-3) private key/cert for a network.
Set up a connection and verify that everything works.
2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in
working-key.pem -out aes-key.pem -aes256" (the output should have a line
starting with "DEK-Info: AES-256-CBC,")
3. Delete the settings for the test network and attempt to reconnect using
the new key.
That should work
* Regression potential
That's new code for an extra type of keys, it shouldn't impact
existing options
--
NetworkManager does not appear to support private keys encrypted with
AES. At the very least, it will not validate such a key in nm-util
when setting up a WPA 802.1x TLS wifi connection.
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/942856/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754671] Please test proposed package
Hello dwmw2, or anyone else affected, Accepted network-manager into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.10.14-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Status in systemd source package in Bionic: Triaged Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809132] Re: Updated bionic to the current 1.10 stable version
Hello Sebastien, or anyone else affected, Accepted network-manager into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.10.14-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1809132 Title: Updated bionic to the current 1.10 stable version Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: * Impact The updates in the stable serie include several fixes for misbehaviour, segfaults and security issues, those are the sort of improvements that should be in the LTS The detail of the changes can be seen in the NEWS entry https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS * Test case There is no specific test case for the update, the changelog includes some specific bugs which have their own test case, otherwise it's important to get testing/feedback from users on desktop & server, using IPv4, IPv6, VPN, wifi, eth connections, etc. * Regression potential The update is non trivial, there are several changes are IPv6 and DNS (especially in the context of VPNs) handling so it would be good to give those extra testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1809132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
So, I tested with a 4.18 kernel and I could still reproduce the issue on
eoan. Then, I tested on a bionic system, 4.15 kernel, systemd 237, glibc
2.27, and I see a failure on malloc, also memory corruption.
This appears on the backtrace.
3738malloc_printerr ("malloc(): memory corruption");
I am going back to xenial.
Cascardo.
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: Confirmed
** Also affects: systemd (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: udisks2 (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: udisks2 (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: udisks2 (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1814373
Title:
storage / luks / dmsetup regressed (or got better) on ppc64le
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Status in udisks2 package in Ubuntu:
New
Status in linux source package in Bionic:
New
Status in systemd source package in Bionic:
New
Status in udisks2 source package in Bionic:
New
Status in linux source package in Disco:
New
Status in systemd source package in Disco:
New
Status in udisks2 source package in Disco:
New
Status in linux source package in Eoan:
Confirmed
Status in systemd source package in Eoan:
New
Status in udisks2 source package in Eoan:
New
Bug description:
in disco proposed with new systemd and v4.19 kernel it appears that
dmsetup / cryptsetup storage either got better or worse.
Devices take very long to activate, and sometimes remain in use during
test clean up.
This leads to udisks autopkgtest failing on ppc64le and systemd's
"storage" autopkgtest is also failing.
I've tried to make ppc64le test more resilient, but it's still odd
that it became unstable in disco, and used to be rock solid on
ppc64le.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769677] Re: gnome-software reads system proxy settings in a wrong way
Can confirm the issue on 19.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1769677 Title: gnome-software reads system proxy settings in a wrong way Status in gnome-software package in Ubuntu: New Bug description: After setting a proxy (e.g. http proxy) in Settings, gnome-software will show a message saying something like `E: https://mirrors.ustc.edu.cn/ubuntu bionic/universe amd64 libkf5archive5 amd64 5.44.0-0ubuntu1 is not (yet) available (Unsupported proxy configured: 127.0.0.1://1234)` when attempt to install software (not a snap package). That is to say, it parses the domain part as the protocol part, which is incorrect. The proxy settings it shows seem to come from the system proxy settings as it shows 13:59:45:0380 GsPluginPackageKit Setting proxies (http: 127.0.0.1:1234, https: (null), ftp: (null), socks: (null), no_proxy: localhost,127.0.0.0/8,::1, pac: (null)) in `gnome-software --verbose`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1769677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816004] Re: GLVND: AARCH64 : Fix address passed to clear cache
uploaded to bionic-proposed queue, with just the fix added
** Changed in: libglvnd (Ubuntu Bionic)
Status: New => In Progress
** Description changed:
[Impact]
A new fix has been merged to NVIDIA libglvnd repo at
https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e
We need to include it in bionic.
It would be ok to just include this fix even without updating to the latest
glvnd version.
This change fixes a crash seen in some GLX apps while calling
glXGetProcAddress.
Source Package :
https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2
Can we get this fix merged in current LTS 18.04 as "-updates"
[Test app]
To reproduce this failure: Install python-pyglet on 18.04 ubuntu.
And run a small test app with this piece of code.
void *handle = dlopen("libGLX.so.0", 2);
glXGetProcAddressARB = (GLXextFuncPtr (*)(const GLubyte*))dlsym(handle,
"glXGetProcAddressARB");
glXGetProcAddressARB("glXAllocateMemoryMESA");
+
+ [Regression potential]
+
+ Minimal, disco shipped with this.
** Description changed:
[Impact]
A new fix has been merged to NVIDIA libglvnd repo at
https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e
We need to include it in bionic.
It would be ok to just include this fix even without updating to the latest
glvnd version.
This change fixes a crash seen in some GLX apps while calling
glXGetProcAddress.
Source Package :
https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2
Can we get this fix merged in current LTS 18.04 as "-updates"
[Test app]
To reproduce this failure: Install python-pyglet on 18.04 ubuntu.
And run a small test app with this piece of code.
void *handle = dlopen("libGLX.so.0", 2);
glXGetProcAddressARB = (GLXextFuncPtr (*)(const GLubyte*))dlsym(handle,
"glXGetProcAddressARB");
glXGetProcAddressARB("glXAllocateMemoryMESA");
[Regression potential]
- Minimal, disco shipped with this.
+ Minimal, disco shipped with the fix.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1816004
Title:
GLVND: AARCH64 : Fix address passed to clear cache
Status in libglvnd package in Ubuntu:
Fix Released
Status in libglvnd source package in Bionic:
In Progress
Bug description:
[Impact]
A new fix has been merged to NVIDIA libglvnd repo at
https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e
We need to include it in bionic.
It would be ok to just include this fix even without updating to the latest
glvnd version.
This change fixes a crash seen in some GLX apps while calling
glXGetProcAddress.
Source Package :
https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2
Can we get this fix merged in current LTS 18.04 as "-updates"
[Test app]
To reproduce this failure: Install python-pyglet on 18.04 ubuntu.
And run a small test app with this piece of code.
void *handle = dlopen("libGLX.so.0", 2);
glXGetProcAddressARB = (GLXextFuncPtr (*)(const GLubyte*))dlsym(handle,
"glXGetProcAddressARB");
glXGetProcAddressARB("glXAllocateMemoryMESA");
[Regression potential]
Minimal, disco shipped with the fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1816004/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another
@macbreeze you might want to open a bug for the xfce4-session package or the xubuntu meta package as this one is targeting the gnome-shell package. LightDM has settings in /etc/lightdm for overriding which monitor is used for the login widget and xrandr tool may help in the session after login. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Fix Released Status in GNOME Settings Daemon: Incomplete Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823272] Re: package sgml-base 1.29 failed to install/upgrade: eindeloze triggerlus; afgebroken
I have faced the same problem, not sure what's causing this. ** Attachment added: "15574902383857410942388402630861.jpg" https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/1823272/+attachment/5262922/+files/15574902383857410942388402630861.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sgml-base in Ubuntu. https://bugs.launchpad.net/bugs/1823272 Title: package sgml-base 1.29 failed to install/upgrade: eindeloze triggerlus; afgebroken Status in sgml-base package in Ubuntu: Confirmed Bug description: upgrade from 18:10 to 19:04 ProblemType: Package DistroRelease: Ubuntu 19.04 Package: sgml-base 1.29 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Fri Apr 5 00:33:37 2019 ErrorMessage: eindeloze triggerlus; afgebroken InstallationDate: Installed on 2016-12-31 (824 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.0 SourcePackage: sgml-base Title: package sgml-base 1.29 failed to install/upgrade: eindeloze triggerlus; afgebroken UpgradeStatus: Upgraded to disco on 2019-04-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/1823272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811668] Re: oem-config fails on Nvidia GPU machine on 18.04.1
> - We add oem-priority because it affects our clients directly but we don't > have any contract with > Canonical. You didn't add it though, overlook? Also do you have anyone able to reproduce we can contact for testing/getting extra informations? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1811668 Title: oem-config fails on Nvidia GPU machine on 18.04.1 Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: More an nvidia driver fail but happens in a oem-config scenario : - Install 18.04.1 on an Nvidia GPU machine ( desktop or laptop) - full-upgrade - ubuntu-drivers autoinstall ( To get nvidia drivers) - Reboot and confirm nvidia driver work great - oem-config-prepare - Send machine to client - client goes through oem-config wizard normally - instead of going to the new desktop , client gets a blackscreen - After reboot he always get a black screen. - If he logs into TTY1 , he can login and startx to get a gnome3 desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816004] Re: GLVND: AARCH64 : Fix address passed to clear cache
Any update here? Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1816004
Title:
GLVND: AARCH64 : Fix address passed to clear cache
Status in libglvnd package in Ubuntu:
Fix Released
Status in libglvnd source package in Bionic:
New
Bug description:
[Impact]
A new fix has been merged to NVIDIA libglvnd repo at
https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e
We need to include it in bionic.
It would be ok to just include this fix even without updating to the latest
glvnd version.
This change fixes a crash seen in some GLX apps while calling
glXGetProcAddress.
Source Package :
https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2
Can we get this fix merged in current LTS 18.04 as "-updates"
[Test app]
To reproduce this failure: Install python-pyglet on 18.04 ubuntu.
And run a small test app with this piece of code.
void *handle = dlopen("libGLX.so.0", 2);
glXGetProcAddressARB = (GLXextFuncPtr (*)(const GLubyte*))dlsym(handle,
"glXGetProcAddressARB");
glXGetProcAddressARB("glXAllocateMemoryMESA");
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1816004/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828536] Re: libreoffice styles
Hi jacinto, please could you provide us with a little more info about your system, such as: * Which version of Ubuntu you're running * Which version of LibreOffice you have installed (e.g. "Build ID: libreoffice-6.2.3.2-snap1") * Which architecture you're running on (i386 / amd64) Please also let us know if you're using any LibreOffice extensions that could be causing the issue. For this, I recommend first disabling all extensions and seeing if the problem goes away. Thank you! ** Changed in: libreoffice (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1828536 Title: libreoffice styles Status in libreoffice package in Ubuntu: Incomplete Bug description: Create a page style from scratch in LibreOffice. Write the name --> click on page to setup page and LibreOffice crash. To Work I must write the name and click in Ok --> modify the style and click on page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1828536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828538] [NEW] package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Public bug reported: dpkg: ошибка при обработке пакета grub-common (--configure): подпроцесс установлен сценарий post-installation возвратил код ошибки 1 dpkg: зависимости пакетов не позволяют настроить пакет grub: grub зависит от grub-common, однако: Пакет grub-common пока не настроен. dpkg: ошибка при обработке пакета grub (--configure): проблемы зависимостей — оставляем не настроенным Отчёт apport не записан, так как сообщение об ошибке указывает на повторную ошибку от предыдущего отказа. dpkg: зависимости пакетов не позволяют настроить пакет grub-pc-bin: grub-pc-bin зависит от grub-common (= 2.02~beta2-36ubuntu3.22), однако: Пакет grub-common пока не настроен. dpkg: ошибка при обработке пакета grub-pc-bin (--configure): проблемы зависимостей — оставляем не настроенным Отчёт apport не записан, так как достигнуто значение MaxReports При обработке следующих пакетов произошли ошибки: cups-browsed grub-common grub grub-pc-bin E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-browsed 1.8.3-2ubuntu3.5 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri May 10 13:55:39 2019 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2019-04-16 (24 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 20137 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=0766966a-bb14-4a26-9fd4-14c4f4ed1605 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: cups-filters Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6CCN18WW(V1.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G585 dmi.board.vendor: LENOVO dmi.board.version: INVALID dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G585 dmi.modalias: dmi:bvnLENOVO:bvr6CCN18WW(V1.05):bd07/18/2012:svnLENOVO:pn20137:pvrLenovoG585:rvnLENOVO:rnLenovoG585:rvrINVALID:cvnLENOVO:ct10:cvrLenovoG585: dmi.product.family: IDEAPAD dmi.product.name: 20137 dmi.product.version: Lenovo G585 dmi.sys.vendor: LENOVO ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1828538 Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in cups-filters package in Ubuntu: New Bug description: dpkg: ошибка при обработке пакета grub-common (--configure): подпроцесс установлен сценарий post-installation возвратил код ошибки 1 dpkg: зависимости пакетов не позволяют настроить пакет grub: grub зависит от grub-common, однако: Пакет grub-common пока не настроен. dpkg: ошибка при обработке пакета grub (--configure): проблемы зависимостей — оставляем не настроенным Отчёт apport не записан, так как сообщение об ошибке указывает на повторную ошибку от предыдущего отказа. dpkg: зависимости пакетов не позволяют настроить пакет grub-pc-bin: grub-pc-bin зависит от grub-common (= 2.02~beta2-36ubuntu3.22), однако: Пакет grub-common пока не настроен. dpkg: ошибка при обработке пакета grub-pc-bin (--configure): проблемы зависимостей — оставляем не настроенным Отчёт apport не записан, так как достигнуто значение MaxReports При обработке следующих пакетов произошли ошибки: cups-browsed grub-common grub grub-pc-bin E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-browsed 1.8.3-2ubuntu3.5 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri May 10 13:55:39 2019 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2019-04-16 (24 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 20137 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=0766966a-bb14-4a26-9fd4-14c4f4ed1605 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg
[Desktop-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
** Changed in: mutter Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:51 2017 InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1718238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828108] Re: GNOME default to a document font not installed by Ubuntu
This bug was fixed in the package gnome-flashback - 3.32.0-1ubuntu2 --- gnome-flashback (3.32.0-1ubuntu2) eoan; urgency=medium * Set document-font-name to "Sans 11", following ubuntu-settings (LP: #1828108). -- Dmitry Shachnev Fri, 10 May 2019 12:31:23 +0300 ** Changed in: gnome-flashback (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1828108 Title: GNOME default to a document font not installed by Ubuntu Status in gnome-flashback package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Disco: Fix Committed Bug description: * Impact The document font changed in GNOME 3.31 to be 'Cantarell 11' but that font is not installed in Ubuntu so a fallback font is used instead. * Test case Install gnome-tweaks and look at the document font, it should be 'Sans 11' and not 'undefined' * Regression potential It's just changing the default value to be what it was before, the impact should be low (the UI is going to look different in place where the fallback was used but that's what the fix is about) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1828108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827735] Re: DBus/MPRIS2: Totem says it is "Paused" even the stream has ended "Stopped"
Upstream added this comment 'It is paused back at the beginning of the playlist, not stopped. I'm not sure what problem this causes, if any.' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1827735 Title: DBus/MPRIS2: Totem says it is "Paused" even the stream has ended "Stopped" Status in Totem: New Status in totem package in Ubuntu: Triaged Bug description: Hello, Question 1: === When asking status of Totem via DBus/MPRIS2, it says "Paused" even the song has ended. Shouldn't it return "Stopped" state. I am using a small bash-script to see the DBus-messages. $ ./debug1.sh org.mpris.MediaPlayer2.rhythmbox says: I AM PLAYING. Confirmed state is: (<'Playing'>,) - Then the song ends. org.mpris.MediaPlayer2.rhythmbox says: I AM PAUSED. Confirmed state is: (<'Paused'>,) Question 2: === GNOME's Music player is "org.gnome.Music". GNOME's Video player is: "org.mpris.MediaPlayer2.totem" Why this difference? I like both products. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 Uname: Linux 5.0.1-050001-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 4 19:24:02 2019 InstallationDate: Installed on 2019-03-06 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1827735/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828536] [NEW] libreoffice styles
Public bug reported: Create a page style from scratch in LibreOffice. Write the name --> click on page to setup page and LibreOffice crash. To Work I must write the name and click in Ok --> modify the style and click on page. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1828536 Title: libreoffice styles Status in libreoffice package in Ubuntu: New Bug description: Create a page style from scratch in LibreOffice. Write the name --> click on page to setup page and LibreOffice crash. To Work I must write the name and click in Ok --> modify the style and click on page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1828536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820062] Re: LibreOffice Impress embed video problem (libreoffice-gtk3)
Upgraded libreoffice to 1:6.1.6-0ubuntu0.18.10.1 from cosmic-proposed in a clean and up-to-date cosmic amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1820062 Title: LibreOffice Impress embed video problem (libreoffice-gtk3) Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: In Progress Status in libreoffice source package in Cosmic: Fix Committed Status in libreoffice-l10n source package in Cosmic: Fix Committed Bug description: LibreOffice Impress has problematic embedded video playback. In Ubuntu 18.04, 18.10 and 19.04-alpha if you insert video in Impress slide, when played video stretches in fullscreen. (LO versions affected at least 6.0.x, 6.1.y and 6.2.1.1) The video of miss-behavior: https://youtu.be/77E6IzVJ5jA The issue is with current Libre Office vlc GTK3 (libreoffice-gtk3). Solution #1 install gstreamer1.0-gtk3 (probably missing dependency) Solution #2 Remove libreoffice-gtk3 and install libreoffice-gtk2 reference to Document Funtation bugzilla: https://bugs.documentfoundation.org/show_bug.cgi?id=124068 [Impact] * This effects all libreoffice-gtk3 users wishing to embed videos into an Impress slide. * The fix is currently in LibreOffice 6.2.2+ on disco and eoan. [Test Case] 1. Insert a video into an Impress slide 2. Play the video 3. The video should play within the slide (not fullscreen like this: https://youtu.be/77E6IzVJ5jA) [Regression Potential] * The fix is one line in the control file so potential for regression is low. * A combination of autopkgtests and manual testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1820062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827451] Re: Japanese new era "Reiwa(令和)" support
Upgraded libreoffice to 1:6.1.6-0ubuntu0.18.10.1 from cosmic-proposed in a clean and up-to-date cosmic amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1827451 Title: Japanese new era "Reiwa(令和)" support Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Xenial: In Progress Status in libreoffice source package in Bionic: In Progress Status in libreoffice source package in Cosmic: Fix Committed Status in libreoffice-l10n source package in Cosmic: Fix Committed Bug description: Japanese new era "Reiwa(令和)" has began at 2019-05-01. These patches add Reiwa support for Libreoffice Bionic/Xenial. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 3 10:44:42 2019 InstallationDate: Installed on 2018-07-21 (285 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64(20180506.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) [Impact] * This effects all users who use the Japanese era date format in LibreOffice. * The fix is currently in LibreOffice 6.2.3 on eoan. [Test Case] 1. Start Calc 2. Put "01/05/2019" into a cell 3. Right-click on the cell and select "Format Cells" 4. Set “Language" to "Japanese" 5. Set “Format" to "H11.12.31" 6. Cell should show "R1.05.01" (not "N1.05.01”) [Regression Potential] * The fix is minor so potential for regression is low. * A combination of autopkgtests and manual testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1827451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828210] Re: [SRU] libreoffice 6.1.6 for cosmic
Upgraded libreoffice to 1:6.1.6-0ubuntu0.18.10.1 from cosmic-proposed in a clean and up-to-date cosmic amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1828210 Title: [SRU] libreoffice 6.1.6 for cosmic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Cosmic: Fix Committed Status in libreoffice-l10n source package in Cosmic: Fix Committed Bug description: [Impact] * LibreOffice 6.1.6 is the sixth bugfix release of the still 6.1 line. Version 6.1.5 is currently in cosmic. For a list of fixed bugs compared to 6.1.5 see the list of bugs fixed in the three release candidates: https://wiki.documentfoundation.org/Releases/6.1.6/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.1.6/RC2#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.1.6/RC3#List_of_fixed_bugs (that's a total of 57 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 57 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1828210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811668] Re: oem-config fails on Nvidia GPU machine on 18.04.1
per current oem project, we don't have this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1811668 Title: oem-config fails on Nvidia GPU machine on 18.04.1 Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: More an nvidia driver fail but happens in a oem-config scenario : - Install 18.04.1 on an Nvidia GPU machine ( desktop or laptop) - full-upgrade - ubuntu-drivers autoinstall ( To get nvidia drivers) - Reboot and confirm nvidia driver work great - oem-config-prepare - Send machine to client - client goes through oem-config wizard normally - instead of going to the new desktop , client gets a blackscreen - After reboot he always get a black screen. - If he logs into TTY1 , he can login and startx to get a gnome3 desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value
Upgraded libreoffice to 1:6.2.3-0ubuntu0.19.04.1 from disco-proposed in a clean and up-to-date disco amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1822839 Title: LibreOffice doesn't detect JVM because of unexpected java.vendor property value Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in openjdk-lts package in Ubuntu: New Status in libreoffice source package in Xenial: In Progress Status in libreoffice source package in Bionic: In Progress Status in libreoffice source package in Disco: Fix Committed Status in libreoffice-l10n source package in Disco: Fix Committed Status in openjdk-lts source package in Disco: New Status in libreoffice package in Debian: New Bug description: [Impact] * A recent OpenJDK update changes the value of the "java.vendor" property from "Oracle Corporation" to "Private Build". This breaks the code in LibreOffice that detects an installed JVM. * The fix is currently in LibreOffice 6.2.3 on eoan. [Test Case] 1. Launch the LibreOffice Start Center 2. Open Tools > Options 3. Navigate to LibreOffice > Advanced 4. A JRE should be listed with Location: /usr/lib/jvm/... [Regression Potential] * This fix is small and concentrated so potential for regression should be relatively low. * A combination of autopkgtests and manual testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1822839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811668] Re: oem-config fails on Nvidia GPU machine on 18.04.1
** No longer affects: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1811668 Title: oem-config fails on Nvidia GPU machine on 18.04.1 Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: More an nvidia driver fail but happens in a oem-config scenario : - Install 18.04.1 on an Nvidia GPU machine ( desktop or laptop) - full-upgrade - ubuntu-drivers autoinstall ( To get nvidia drivers) - Reboot and confirm nvidia driver work great - oem-config-prepare - Send machine to client - client goes through oem-config wizard normally - instead of going to the new desktop , client gets a blackscreen - After reboot he always get a black screen. - If he logs into TTY1 , he can login and startx to get a gnome3 desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826560] Re: [SRU] libreoffice 6.2.3 for disco
Upgraded libreoffice to 1:6.2.3-0ubuntu0.19.04.1 from disco-proposed in a clean and up-to-date disco amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1826560 Title: [SRU] libreoffice 6.2.3 for disco Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Disco: Fix Committed Status in libreoffice-l10n source package in Disco: Fix Committed Bug description: [Impact] * LibreOffice 6.2.3 is in its third bugfix release of the 6.2 line. Version 6.2.3 is currently in eoan. For a list of fixed bugs compared to 6.2.2 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.2.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.2.3/RC2#List_of_fixed_bugs (that's a total of 92 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 92 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1826560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811668] Re: oem-config fails on Nvidia GPU machine on 18.04.1
Just a note : - We add oem-priority because it affects our clients directly but we don't have any contract with Canonical. - Let us know what tag we could use when we want to raise a business impacting problem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1811668 Title: oem-config fails on Nvidia GPU machine on 18.04.1 Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: More an nvidia driver fail but happens in a oem-config scenario : - Install 18.04.1 on an Nvidia GPU machine ( desktop or laptop) - full-upgrade - ubuntu-drivers autoinstall ( To get nvidia drivers) - Reboot and confirm nvidia driver work great - oem-config-prepare - Send machine to client - client goes through oem-config wizard normally - instead of going to the new desktop , client gets a blackscreen - After reboot he always get a black screen. - If he logs into TTY1 , he can login and startx to get a gnome3 desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04
** No longer affects: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 Status in dolphin: Unknown Status in gvfs: Fix Released Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Invalid Bug description: Ubuntu: 18.04 clean install Nautilus: 1:3.26.3-0ubuntu4 The actions taken to produce the problem: Click on “Other Locations” in Nautilus. The expected result of these actions: Samba servers to automatically show up under “Networks”. This is the behavior in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows Network” immediately shows "Folder is Empty". The actual result of these actions: The Samba servers never show up under “Networks” and clicking on "Windows Network" always immediately comes up with "Folder is Empty". Further information: This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 17.10 machines still work like expected. I can still manually type in the Samba information in "Connect to Server" and the 18.04 machines connect just fine. From syslog: Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' (uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined") Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Successfully activated service 'org.gnome.Nautilus' Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname Service... Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service. Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on directory /var/cache/samba: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/1767454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828531] Re: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1828531 Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cups-filters package in Ubuntu: New Bug description: I just upgraded and this was the result. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-browsed 1.8.3-2ubuntu3.5 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri May 10 10:59:06 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-10-09 (577 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: device for Samsung-M2020-Series: usb://Samsung/M2020%20Series?serial=08HVB8GJ3F00DAT MachineType: CLEVO P170EM Papersize: a4 PpdFiles: Samsung-M2020-Series: Samsung M2020 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=41d53c2f-cd6a-4aea-966a-945a3d62f0cc ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: cups-filters Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Not Applicable dmi.board.name: P170EM dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: CLEVO dmi.chassis.version: Not Applicable dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/24/2012:svnCLEVO:pnP170EM:pvrNotApplicable:rvnCLEVO:rnP170EM:rvrNotApplicable:cvnCLEVO:ct10:cvrNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P170EM dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1828531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828531] [NEW] package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I just upgraded and this was the result. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-browsed 1.8.3-2ubuntu3.5 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri May 10 10:59:06 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-10-09 (577 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: device for Samsung-M2020-Series: usb://Samsung/M2020%20Series?serial=08HVB8GJ3F00DAT MachineType: CLEVO P170EM Papersize: a4 PpdFiles: Samsung-M2020-Series: Samsung M2020 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=41d53c2f-cd6a-4aea-966a-945a3d62f0cc ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: cups-filters Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Not Applicable dmi.board.name: P170EM dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: CLEVO dmi.chassis.version: Not Applicable dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/24/2012:svnCLEVO:pnP170EM:pvrNotApplicable:rvnCLEVO:rnP170EM:rvrNotApplicable:cvnCLEVO:ct10:cvrNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P170EM dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1828531 Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cups-filters package in Ubuntu: New Bug description: I just upgraded and this was the result. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-browsed 1.8.3-2ubuntu3.5 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri May 10 10:59:06 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-10-09 (577 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: device for Samsung-M2020-Series: usb://Samsung/M2020%20Series?serial=08HVB8GJ3F00DAT MachineType: CLEVO P170EM Papersize: a4 PpdFiles: Samsung-M2020-Series: Samsung M2020 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=41d53c2f-cd6a-4aea-966a-945a3d62f0cc ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: cups-filters Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Not Applicable dmi.board.name: P170EM dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: CLEVO dmi.chassis.version: Not Applicable dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/24/2012:svnCLEVO:pnP170EM:pvrNotApplicable:rvnCLEVO:rnP170EM:rvrNotApplicable:cvnCLEVO:ct10:cvrNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P170EM dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1828531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
is the part "[first mitigation completed, working on a second one]" in the bug title meanigful in any way? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Status in firefox source package in Xenial: Fix Released Status in firefox source package in Bionic: Fix Released Status in firefox source package in Cosmic: Fix Released Status in firefox source package in Disco: Fix Released Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549200 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Status in firefox source package in Xenial: Fix Released Status in firefox source package in Bionic: Fix Released Status in firefox source package in Cosmic: Fix Released Status in firefox source package in Disco: Fix Released Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827727]
*** Bug 1549679 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Status in firefox source package in Xenial: Fix Released Status in firefox source package in Bionic: Fix Released Status in firefox source package in Cosmic: Fix Released Status in firefox source package in Disco: Fix Released Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
Comment #30 notes the same thing ;) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:51 2017 InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1718238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
The upstream bug notes that it is an Ubuntu patch causing this bug. https://gitlab.gnome.org/GNOME/mutter/issues/23#note_115241 ** Tags removed: artful ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #23 https://gitlab.gnome.org/GNOME/mutter/issues/23 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/23 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** No longer affects: ubuntu-themes (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:51 2017 InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1718238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828520] Re: Terminal icon appearing too large in title bar in Ubuntu 18.04
*** This bug is a duplicate of bug 1718238 *** https://bugs.launchpad.net/bugs/1718238 Oh, no the bug is still open.. This is a duplicate of bug 1718238 so we no longer require any more information. Thanks. ** This bug has been marked a duplicate of bug 1718238 Giant terminal icon is blocking out the Terminal window buttons -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1828520 Title: Terminal icon appearing too large in title bar in Ubuntu 18.04 Status in mutter package in Ubuntu: Incomplete Bug description: Terminal icon appearing too large in title bar in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828520] Re: Terminal icon appearing too large in title bar in Ubuntu 18.04
*** This bug is a duplicate of bug 1718238 *** https://bugs.launchpad.net/bugs/1718238 Please: 1. Run 'apport-collect 1828520' in a terminal to send us more information about the system. 2. Update the system, because I thought this bug was fixed a while ago... sudo apt update sudo apt full-upgrade ** Tags added: bionic ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1828520 Title: Terminal icon appearing too large in title bar in Ubuntu 18.04 Status in mutter package in Ubuntu: Incomplete Bug description: Terminal icon appearing too large in title bar in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another
Using lightdm and xfce this problem exists as well. Additionally with this setup there are no monitors.xml in ~/.config. Although the login screen is on the main monitor, which is awkward. There are also other slightly funny situations, as when closing the lid on laptop then connecting laptop to additional monitors, the monitor setup is sometimes(?) restored. That is most likely due to that laptop was earlier connected to these monitors, then disconnected and then later connected again. Still really annoying bug when using laptop on- and off-site. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Fix Released Status in GNOME Settings Daemon: Incomplete Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828520] [NEW] Terminal icon appearing too large in title bar in Ubuntu 18.04
Public bug reported: Terminal icon appearing too large in title bar in Ubuntu 18.04 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1828520 Title: Terminal icon appearing too large in title bar in Ubuntu 18.04 Status in mutter package in Ubuntu: New Bug description: Terminal icon appearing too large in title bar in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps
Indeed, I have suspected for a long time that the color correction is being applied twice. So the final result looks wrong in such apps. If that's true then we would probably want either to: (a) Not tell apps about the color profile at all, because it's already applied full screen; or (b) Tell apps what (if any) profile is already applied full screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps Status in Eye of GNOME: New Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740180]
Created attachment 9063156 youtube 1080play video -errors console.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1740180 Title: Firefox stops loading Farmville 2 and hangs. Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: STR: Start Firefox (56 or 57), go to Facebook. Start Farmville 2. Farmville 2 hangs while loading. Never plays. The Adobe Flash Player is properly installed. Has also been re- installed. Ditto for FireFox. Does not matter if using Ubuntu 16.04 or 17.10. Farmville 2 via Facebook in Firefox hangs. Also will not work if run from the Zynga URL (the makers of Farmville 2. Other Facebook games work well. Try "Pearl's Perils." Happy to help with testing if you like. This has been tested on both desktops and laptops. Thanks, Ken Wagner ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Tue Dec 26 15:59:05 2017 InstallationDate: Installed on 2017-03-06 (295 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ken2466 F pulseaudio /dev/snd/pcmC0D0p: ken2466 F...m pulseaudio /dev/snd/controlC0: ken2466 F pulseaudio /dev/snd/controlC2: ken2466 F pulseaudio BuildID: 20180614184508 Channel: beta CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-03-28 (94 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.0.1 dev enp2s0 proto static metric 100 default via 192.168.1.1 dev wlx7cdd908b43ea proto static metric 600 169.254.0.0/16 dev wlx7cdd908b43ea scope link metric 1000 192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.10 metric 100 192.168.1.0/24 dev wlx7cdd908b43ea proto kernel scope link src 192.168.1.2 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-61ed5f93-fc76-48cc-8c5e-05d080180530 Package: firefox 61.0~b14+build1-0ubuntu0.16.04.1 [origin: LP-PPA-mozillateam-firefox-next] PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Profiles: Profile0 (Default) - LastVersion=61.0/20180614184508 (In use) RunningIncompatibleAddons: False SubmittedCrashIDs: bp-61ed5f93-fc76-48cc-8c5e-05d080180530 bp-481cf9ec-efcd-4900-93aa-4e8940180512 bp-ad49167e-7776-4ff5-8acc-5adb50180421 bp-08f026d0-e273-45fb-b355-c70ae0180402 Tags: xenial third-party-packages beta-channel Themes: extensions.sqlite corrupt or missing Uname: Linux 4.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USER
[Desktop-packages] [Bug 1740180]
Created attachment 9063148 console errors - FarmVille 2.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1740180 Title: Firefox stops loading Farmville 2 and hangs. Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: STR: Start Firefox (56 or 57), go to Facebook. Start Farmville 2. Farmville 2 hangs while loading. Never plays. The Adobe Flash Player is properly installed. Has also been re- installed. Ditto for FireFox. Does not matter if using Ubuntu 16.04 or 17.10. Farmville 2 via Facebook in Firefox hangs. Also will not work if run from the Zynga URL (the makers of Farmville 2. Other Facebook games work well. Try "Pearl's Perils." Happy to help with testing if you like. This has been tested on both desktops and laptops. Thanks, Ken Wagner ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Tue Dec 26 15:59:05 2017 InstallationDate: Installed on 2017-03-06 (295 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ken2466 F pulseaudio /dev/snd/pcmC0D0p: ken2466 F...m pulseaudio /dev/snd/controlC0: ken2466 F pulseaudio /dev/snd/controlC2: ken2466 F pulseaudio BuildID: 20180614184508 Channel: beta CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-03-28 (94 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.0.1 dev enp2s0 proto static metric 100 default via 192.168.1.1 dev wlx7cdd908b43ea proto static metric 600 169.254.0.0/16 dev wlx7cdd908b43ea scope link metric 1000 192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.10 metric 100 192.168.1.0/24 dev wlx7cdd908b43ea proto kernel scope link src 192.168.1.2 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-61ed5f93-fc76-48cc-8c5e-05d080180530 Package: firefox 61.0~b14+build1-0ubuntu0.16.04.1 [origin: LP-PPA-mozillateam-firefox-next] PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Profiles: Profile0 (Default) - LastVersion=61.0/20180614184508 (In use) RunningIncompatibleAddons: False SubmittedCrashIDs: bp-61ed5f93-fc76-48cc-8c5e-05d080180530 bp-481cf9ec-efcd-4900-93aa-4e8940180512 bp-ad49167e-7776-4ff5-8acc-5adb50180421 bp-08f026d0-e273-45fb-b355-c70ae0180402 Tags: xenial third-party-packages beta-channel Themes: extensions.sqlite corrupt or missing Uname: Linux 4.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID
[Desktop-packages] [Bug 1740180]
Created attachment 9063147 console errors - FarmVille 2 - .png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1740180 Title: Firefox stops loading Farmville 2 and hangs. Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: STR: Start Firefox (56 or 57), go to Facebook. Start Farmville 2. Farmville 2 hangs while loading. Never plays. The Adobe Flash Player is properly installed. Has also been re- installed. Ditto for FireFox. Does not matter if using Ubuntu 16.04 or 17.10. Farmville 2 via Facebook in Firefox hangs. Also will not work if run from the Zynga URL (the makers of Farmville 2. Other Facebook games work well. Try "Pearl's Perils." Happy to help with testing if you like. This has been tested on both desktops and laptops. Thanks, Ken Wagner ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Tue Dec 26 15:59:05 2017 InstallationDate: Installed on 2017-03-06 (295 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ken2466 F pulseaudio /dev/snd/pcmC0D0p: ken2466 F...m pulseaudio /dev/snd/controlC0: ken2466 F pulseaudio /dev/snd/controlC2: ken2466 F pulseaudio BuildID: 20180614184508 Channel: beta CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-03-28 (94 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.0.1 dev enp2s0 proto static metric 100 default via 192.168.1.1 dev wlx7cdd908b43ea proto static metric 600 169.254.0.0/16 dev wlx7cdd908b43ea scope link metric 1000 192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.10 metric 100 192.168.1.0/24 dev wlx7cdd908b43ea proto kernel scope link src 192.168.1.2 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-61ed5f93-fc76-48cc-8c5e-05d080180530 Package: firefox 61.0~b14+build1-0ubuntu0.16.04.1 [origin: LP-PPA-mozillateam-firefox-next] PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Profiles: Profile0 (Default) - LastVersion=61.0/20180614184508 (In use) RunningIncompatibleAddons: False SubmittedCrashIDs: bp-61ed5f93-fc76-48cc-8c5e-05d080180530 bp-481cf9ec-efcd-4900-93aa-4e8940180512 bp-ad49167e-7776-4ff5-8acc-5adb50180421 bp-08f026d0-e273-45fb-b355-c70ae0180402 Tags: xenial third-party-packages beta-channel Themes: extensions.sqlite corrupt or missing Uname: Linux 4.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID
[Desktop-packages] [Bug 1740180]
Created attachment 9063149 console errors -Slotomania .png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1740180 Title: Firefox stops loading Farmville 2 and hangs. Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: STR: Start Firefox (56 or 57), go to Facebook. Start Farmville 2. Farmville 2 hangs while loading. Never plays. The Adobe Flash Player is properly installed. Has also been re- installed. Ditto for FireFox. Does not matter if using Ubuntu 16.04 or 17.10. Farmville 2 via Facebook in Firefox hangs. Also will not work if run from the Zynga URL (the makers of Farmville 2. Other Facebook games work well. Try "Pearl's Perils." Happy to help with testing if you like. This has been tested on both desktops and laptops. Thanks, Ken Wagner ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.23 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Tue Dec 26 15:59:05 2017 InstallationDate: Installed on 2017-03-06 (295 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ken2466 F pulseaudio /dev/snd/pcmC0D0p: ken2466 F...m pulseaudio /dev/snd/controlC0: ken2466 F pulseaudio /dev/snd/controlC2: ken2466 F pulseaudio BuildID: 20180614184508 Channel: beta CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-03-28 (94 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.0.1 dev enp2s0 proto static metric 100 default via 192.168.1.1 dev wlx7cdd908b43ea proto static metric 600 169.254.0.0/16 dev wlx7cdd908b43ea scope link metric 1000 192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.10 metric 100 192.168.1.0/24 dev wlx7cdd908b43ea proto kernel scope link src 192.168.1.2 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-61ed5f93-fc76-48cc-8c5e-05d080180530 Package: firefox 61.0~b14+build1-0ubuntu0.16.04.1 [origin: LP-PPA-mozillateam-firefox-next] PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Profiles: Profile0 (Default) - LastVersion=61.0/20180614184508 (In use) RunningIncompatibleAddons: False SubmittedCrashIDs: bp-61ed5f93-fc76-48cc-8c5e-05d080180530 bp-481cf9ec-efcd-4900-93aa-4e8940180512 bp-ad49167e-7776-4ff5-8acc-5adb50180421 bp-08f026d0-e273-45fb-b355-c70ae0180402 Tags: xenial third-party-packages beta-channel Themes: extensions.sqlite corrupt or missing Uname: Linux 4.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID
[Desktop-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps
EOG also applies fullscreen profiles to image! Notice most of preinstalled color profiles in Settings->Devices->Color does not support whole screen correction (they are marked with bulb icon). So this is normal application behavior to apply system-wide color profile to image. But when fullscreen profile selected, it used firstly in EOG for certain image and secondly by the system for final correction. In my case screen has noticeable bluish cast, so ICC does significant color shift to compensate it. But when applied twice, it makes images yellowish in EOG. While Gimp and Shotwell display colors correctly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps Status in Eye of GNOME: New Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828491] Re: gnome-calendar not listed as a calendar app in default app settings
** Changed in: gnome-calendar Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1828491 Title: gnome-calendar not listed as a calendar app in default app settings Status in GNOME Calendar: New Status in gnome-calendar package in Ubuntu: Triaged Bug description: Gnome-Calendar doesn't appear in the list of default apps for calendar in gnome settings. This is probably due to the fact that, in the .desktop file, the "text/calendar" mime type is not registered? Anyway, a workaround exists: just type "gio mime text/calendar org.gnome.Calendar.desktop". To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1828491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828490] Re: no prompt when copy files from usb disk to Desktop
Thank you for your bug report, you have a round icon in the nautilus toolbar which includes the details in a popover ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1828490 Title: no prompt when copy files from usb disk to Desktop Status in nautilus package in Ubuntu: Invalid Bug description: I use ubuntu18.04, today I copy some big files from usb disk to Desktop, there are no progress bar pop to tell me the copy progress, only a small prompt from the icon of nautilus, then I close nautilus and wait, the prompt from the icon disappear but the copy progress is still the halfway. I guess the newest nautilus still have this problem. gnome cut off a lot of useful thing include the progress bar when copying files. I suggest pop the progress bar when copy files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1828490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828491] Re: gnome-calendar not listed as a calendar app in default app settings
Thank you for your bug report, indeed upstream removed that mimetype association because it would lean gnome-calendar to claim it can handle ics files which is not the case... ** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/issues #337 https://gitlab.gnome.org/GNOME/gnome-calendar/issues/337 ** Also affects: gnome-calendar via https://gitlab.gnome.org/GNOME/gnome-calendar/issues/337 Importance: Unknown Status: Unknown ** Changed in: gnome-calendar (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-calendar (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1828491 Title: gnome-calendar not listed as a calendar app in default app settings Status in GNOME Calendar: Unknown Status in gnome-calendar package in Ubuntu: Triaged Bug description: Gnome-Calendar doesn't appear in the list of default apps for calendar in gnome settings. This is probably due to the fact that, in the .desktop file, the "text/calendar" mime type is not registered? Anyway, a workaround exists: just type "gio mime text/calendar org.gnome.Calendar.desktop". To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1828491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
